JP4882115B2 - Remote notification system, electronic computer, and remote notification method - Google Patents

Description

  The present invention relates to a system for remotely monitoring the state of an electronic computer.

  There are services that remotely monitor a large number of devices in real time, such as online support services for electronic computers delivered to customers. In such a service system, when an abnormality occurs in a customer apparatus, error information indicating that fact is notified to the monitoring apparatus via the network. On the monitoring side that has received the error notification, the operator performs support work such as confirming details to the customer by telephone or e-mail.

  By the way, the error notified to the monitoring side may include, for example, an error due to work planned in advance on the customer side, such as restart or power failure accompanying the inspection work of the apparatus. In this case, even if the monitoring side receiving the error contacts the customer for support, the support becomes useless.

As a method for dealing with the above inconvenience, for example, there is a method described in Patent Document 1 described later. The method described in this document monitors the presence / absence of a failure in the system based on the presence / absence of a response to a message transmitted to the monitoring target. When an error occurs, the monitoring side does not determine that a failure has occurred if the monitoring flag for the system indicates that it is stopped.
JP 2003-099290 A

  According to the method described in Patent Document 1, it is possible to prevent a failure from being erroneously determined that there is no response from a stopped system.

  However, in the above method, it is necessary to regularly exchange messages between the system and a device that monitors the system in order to determine the presence or absence of a failure. This may lead to frequent congestion in the network, particularly in the case of a system with a large number of monitoring targets such as tens of thousands. On the other hand, in order to avoid congestion, for example, if the period of the regular message is set to be relatively long, there is a possibility that a failure may be detected.

  The present invention has been made to cope with the above-described problems, and an object of the present invention is to provide a technique for reliably grasping an error occurrence of a monitored apparatus on the monitoring side while preventing network congestion.

  A remote notification system according to the present invention includes a monitoring device connected to a network and a plurality of monitored devices, and each of the monitored devices records plan information input regarding a work plan for the own device in a storage medium. And means for detecting the occurrence of an error event in the own device and recording error information indicating the occurrence of the error event in a storage medium, and the monitoring device including the plan information and error information of the storage medium together with identification information of the own device Means for transmitting to the storage device, the monitoring device records the plan information and error information from each monitored device in association with the identification information of the monitored device, and the storage medium plan Means for displaying information and error information for each monitored device.

  An electronic computer according to the present invention is an electronic computer as a monitored apparatus connected to a monitoring apparatus via a network, and includes means for recording plan information input regarding a work plan for the own apparatus in a storage medium, Means for detecting occurrence of an error event in the apparatus and recording error information indicating the occurrence of the error event in a storage medium, and transmitting the plan information and error information of the storage medium together with identification information of the own apparatus to the monitoring apparatus Means.

  In the remote notification method according to the present invention, each of a plurality of monitored devices connected to a monitoring device via a network records plan information inputted regarding a work plan for the own device in a storage medium, and an error in the own device. The occurrence of an event is detected and error information indicating the occurrence of the error event is recorded in a storage medium, and the plan information and error information of the storage medium are transmitted to the monitoring apparatus together with identification information of the own apparatus, and the monitoring apparatus The plan information and error information from each monitored device are recorded on a storage medium in association with the identification information of the monitored device, and the plan information and error information of the storage medium are displayed for each monitored device. .

  According to the present invention, the monitoring device can accurately detect the occurrence of an error in the monitored device while suppressing the communication load on the network.

  FIG. 1 shows a system configuration of an embodiment of the present invention. In the present embodiment, the present invention is applied to a purpose of providing online support for an electronic computer delivered to a customer.

  The system 100 includes a plurality of electronic computers 10 as monitored devices delivered to customers, a power supply device 20 that supplies power to the corresponding electronic computers 10 uninterruptibly, a monitoring device 30 of a support organization, and a system standard And a time server 40 that provides time. In the system 100, these are connected via the network 50 so that communication is possible. Each electronic computer 10 is assigned an ID for identification (FIG. 1: ID = cal_1, ID = cal_2,...).

  In the electronic computer 10, the communication unit 11 includes a circuit that performs communication processing using the network 50, and communicates with the monitoring device 30 and the time server 40. The control unit 12 includes a control IC such as a CPU, and controls the operation of the electronic computer 10 by executing a program read from the storage unit 14 described later. The control unit 12 has a program for detecting the occurrence of an error such as a stall of the own device or a power failure of the power supply device 20, and a mechanism for executing the program. The input unit 13 includes input devices such as a keyboard and a mouse, and recognizes an operator's input operation using them. The storage unit 14 includes a storage medium such as a nonvolatile memory 14a such as a flash memory and a magnetic disk 14b such as a hard disk, and inputs / outputs data to / from them. The display unit 15 includes a display device such as an LCD, and displays a screen corresponding to an instruction from the control unit 12.

  In the monitoring device 30, the communication unit 31 includes a circuit responsible for communication processing via the network 50, and communicates with each electronic computer 10 and the time server 40. The control unit 32 includes a control IC such as a CPU, and controls the operation of the monitoring device 30. The display unit 33 includes a display device such as an LCD, and displays a screen corresponding to an instruction from the control unit 32. The screen includes, for example, a plan display window 33a and an error display window 33b. Customer data of the delivery destination of each electronic computer 10 is registered in the customer DB 34a. The notification DB 34b stores a notification message described later received from each electronic computer 10.

  The operation of the system 100 configured as above will be described. Here, it is assumed that there is an operation shown in FIG. 2 as an operation planned for the electronic computer 10. In the illustrated example, there are operations such as restart of the electronic computer 10 or power failure / shutdown accompanying work on the customer side, and IDs (1 to 12,...) Are assigned for each work. With regard to the ID “12” shown in the figure, the restriction on the startup order of the computers is, for example, in a server system having a hierarchical structure in which a predetermined startup order is set, such as starting in the order of parent server → child server → grandchild server. Thus, when either the parent server or the child server fails, this indicates a restriction that all servers are restarted or only the child server and the grandchild server are restarted.

  The operation of each electronic computer 10 will be described along the flowchart shown in FIG. The electronic computer 10 acquires the reference time from the time server 40 at the time interval of starting and at a fixed time after starting, and synchronizes the internal time of the own computer (step A1).

  The operator inputs plan information related to the work plan to the electronic computer 10. As an input form, for example, the list shown in FIG. 2 is registered in the electronic computer 10 in advance, and the IDs of all planned operations and information on the respective work time zones are input from the list. Alternatively, a form in which work information is newly input may be used. In that case, an ID is newly set.

  When the plan information is input by the operator as described above, the electronic computer 10 recognizes the input content (step A2) and records it in the nonvolatile memory 14a and the magnetic disk 14b (step A3). At this time, the status flag indicating the status of the planned work is set to “A” (not reported). The plan information is recorded, for example, in the form shown in FIG.

  In the example shown in FIG. 4, the schedule of the start schedule and the completion schedule is recorded for each work selected from the list of FIG. Further, the above-described status flag is set in each entry. In the example shown in the figure, “A” indicating that the plan information has not been reported yet, “N” indicating that the report has been completed but the work has not been completed, “Y” representing the completed state is prepared. The electronic computer 10 sets a status flag corresponding to the operator's input operation.

  The computer 10 recognizes the work whose status flag is “A” from the plan information recorded as described above, and converts it into a predetermined message format together with its own ID such as “cal_1” described above. Write and encrypt. Then, the encrypted message is transmitted as a notification message to the monitoring device 30 (step A4). Note that information that allows the monitoring device 30 to determine that the content is plan information is added to the notification message. For example, a specific identifier is described in the header of the message.

  The electronic computer 10 updates the status flag from “A” to “N” (work report completed) for the work reported to the monitoring device 30 (step A5). In the above manner, notification is made for all the operations with the status flag “A” (step A6).

  Thereafter, when the planned work is completed, the operator inputs the fact to the electronic computer 10. When the electronic computer 10 recognizes the input of work completion (step A7), it updates the status flag of the completed work from “N” to “Y” (work completion) (step A8). Then, for the work whose status flag is “Y”, the monitoring device 30 is notified that the work has been completed (step A9).

  The electronic computer 10 checks whether or not there is a work whose status flag is “N” (work is not completed) at the present time, and if not, finishes the processing (step A10: No). If it exists (step A10: Yes), it is determined whether or not the scheduled completion time (FIG. 4) of the work has passed the current time based on the reference time of the time server 40. As a result of the determination, when the scheduled time has not yet passed (step A11: No), the completion of the operation is waited.

  On the other hand, if there is an entry for which work completion has not been entered after the scheduled completion time (step A11: Yes), the electronic computer 10 displays a screen for confirming the actual situation in a pop-up or the like ( Step A12). Thereby, it is possible to alert the operator about forgetting to input or omission of work.

  The operation related to the error event in the electronic computer 10 will be described along the flowchart shown in FIG. The following operation is in parallel with the above-described operation according to FIG. 3, and the start time thereof is, for example, when all the planning work has been reported to the monitoring device 30 (FIG. 3, step A6: No). Any timing may be used.

  When the electronic computer 10 detects the occurrence of an error event such as its own stall or power failure of the power supply device 20 (step A21: Yes), it determines the type of the error (step A22), and the nonvolatile memory 14a or magnetic disk 14b Error information is recorded in (Step A23). At this time, “A” (not-reported) is set in the status flag indicating whether or not the error has been reported. The error information can be recorded, for example, in the form as shown in FIG.

  In the example shown in FIG. 6, the type and date and time of occurrence of an error that has occurred are recorded. As the status flag of each entry, “A” representing a state where error information has not been reported yet, and “P” representing a state where reporting has been completed are prepared. As will be described later, the electronic computer 10 switches the status flag in accordance with the error reporting status.

  The electronic computer 10 recognizes the entry whose status flag is “A”, describes it in a predetermined message format together with its own ID, encrypts it, and transmits it as a notification message to the monitoring device 30 (step A24). Information such that the monitoring device 30 can determine that the content of the notification message is error information is added to the header or the like.

  The electronic computer 10 updates the status flag from “A” to “P” (error notification completed) for the error reported to the monitoring device 30 (step A25). The electronic computer 10 reports error information to the monitoring device 30 in the manner described above whenever an entry whose status flag is “A” occurs.

  Next, the operation of the monitoring device 30 with respect to the above-described operation of each electronic computer 10 will be described with reference to the flowchart shown in FIG. The monitoring device 30 acquires a reference time from the time server 40 at a certain time interval at the time of activation and after activation, and synchronizes the internal time of its own device (step B1).

  When the monitoring device 30 receives the notification message from the electronic computer 10 (step B2), the monitoring device 30 decodes the message and recognizes the ID of the electronic computer 10 and the content of the notification from the decoded data (step B3).

  The monitoring device 30 searches the customer DB 34a for the data of the customer who owns the computer using the recognized computer ID as a key (step B4). Then, the retrieved customer data and the data of the current report content are associated with each other and stored in the report DB 34b (step B5). The data storage in the notification DB 34b is stored for each report, that is, the plan information and the error information are stored separately. Note that the content of the notification can be determined by an identifier added by the electronic computer 10 to the header of the notification message or the like.

  When the monitoring device 30 recognizes the update of the notification DB 34b due to the above operation (step B6), if the updated data relates to the work plan (step B7: plan information), the updated data is displayed in the plan display window 33a. An additional display is made (step B8). At this time, it adds so that the time slot | zone of the displayed work may follow a time series.

  In FIG. 8, the example of the plan display window 33a displayed on the display of the monitoring apparatus 30 is shown. In the illustrated example, for each customer, the contents of the planned work notified (work ID) and the time zone of the work (start schedule and completion schedule) are displayed in chronological order. Thereby, the operator of the monitoring device 30 can grasp the work schedule of each customer over time.

  On the other hand, when the data updated in the notification DB 34b relates to an error of the electronic computer 10 (step B7: error information), the monitoring device 30 additionally displays the updated data on the error display window 33b (step B9). Also in this case, the error occurrence time to be displayed is added in time series.

  FIG. 9 shows an example of an error display window 33b displayed on the display of the monitoring device 30. In the illustrated example, for each customer, the type of error reported and the date and time when the error occurred are displayed in chronological order. As a result, the operator of the monitoring device 30 can grasp the occurrence of errors in the electronic computer 10 at each customer over time.

  The operator of the monitoring device 30 refers to both windows (33a, 33b) displayed as shown in FIGS. 8 and 9, and determines whether the error generated in each electronic computer 10 requires support contact. . For example, when the occurrence date and time of an error is included in the time zone of the planned work, it is determined that the error is caused by the planned work, and support is not communicated. If the date and time of occurrence of the error is not included in the time zone of the planned work, it is determined that the error is not caused by the planned work, and the support may be contacted.

  According to the embodiment described above, by providing push-type information from the customer side, the monitoring device 30 can accurately detect the occurrence of an error in the electronic computer 10 while suppressing the communication load on the network 50. On the monitoring side, since the monitoring device 30 can grasp the error plan of the electronic computer 10 and the work plan related to the electronic computer 10, it is useless to confirm the error notification accompanying the planned operation to the customer side. Support operations can be reduced.

(Other embodiments)
In the above embodiment, the operator of the monitoring device 30 determines whether the error that has occurred in the electronic computer 10 is due to work planned in advance by the customer. The embodiment of the present invention is not limited to the above form, and may be a form in which each electronic computer 10 makes the determination. The embodiment will be described below. The system configuration is the same as that shown in FIG.

  The operation of each electronic computer 10 when an error occurs will be described with reference to the flowchart shown in FIG. When the electronic computer 10 detects that an error event such as a stall or power failure has occurred (step A31: Yes), it determines the type of the error and records error information in the nonvolatile memory 14a or the magnetic disk 14b (step S31). A32). At this time, “A” (unreported) is set in the status flag indicating whether or not an error report has been made to the monitoring device 30. The error information of this embodiment can be recorded in a form as shown in FIG. 11, for example.

  In the example shown in FIG. 11, the type and date and time of occurrence of an error that has occurred are recorded. In addition to “A” indicating that the error information has not yet been reported and “P1” indicating that the notification has been completed as the status flag of each entry, the notification of the error that has occurred has been disabled. “P2” is prepared. As will be described later, the electronic computer 10 switches the status flag in accordance with the error reporting status.

  When the error information is recorded, the electronic computer 10 recognizes the error occurrence date and time and the work schedule in the previously entered plan information (step A33). Then, the recognized date / time value is analyzed to determine whether or not the error occurrence date / time is included in the planned work schedule (step A34).

  As a result of the above analysis, when the date and time of occurrence of the error is not included in the work schedule (step A35: No), it is considered that the error is not caused by the planned work, and the monitoring device 30 is subjected to the same procedure as in the above-described embodiment. An error is reported (step A36). Then, the status flag of the reported error is updated from “A” to “P1” (reported) (step A37).

  On the other hand, when the date and time of occurrence of the error is included in the work schedule (step A35: Yes), the error is considered to have occurred due to the planned work. In this case, the electronic computer 10 updates the error status flag from “A” to “P2” (not report), and does not report an error to the monitoring device 30 (step A38). Therefore, when an error associated with the planning work occurs in the electronic computer 10, the error report is invalidated.

  As described above, the electronic computer 10 according to the present embodiment performs control so as not to notify the monitoring device 30 of an error event that has occurred in association with a planned work. As a result, error notifications transmitted from the electronic computer 10 are limited, so that congestion of the network 50 can be prevented. In addition, since only the unplanned error, that is, the error that requires support to the customer is notified to the monitoring device 30, the burden on the monitoring side regarding the support work can be reduced.

  In the present invention, error events of the electronic computer 10 can be classified and monitored in categories such as hardware, software, network, planned power outage, and the like. In this case, each work of the plan information registered in the electronic computer 10 is recorded in association with the corresponding category. Specifically, for example, plan information can be registered as shown in FIG. In the illustrated example, for each work ID, a category ID indicating which category the work belongs to is recorded.

  The operation when an error occurs in the electronic computer 10 using the plan information as shown in FIG. 12 will be described with reference to the flowchart shown in FIG.

  When the electronic computer 10 detects the occurrence of an error event such as a stall or a power failure (step A41: Yes), it determines the type of the error and records error information (step A42). At this time, “A” (not reported) is set in the status flag relating to error notification. The error information of this embodiment can be recorded, for example, in the form as shown in FIG.

  In the error information shown in FIG. 14, the type of status flag is the same as that in FIG. In this embodiment, for each error that occurs, the category ID corresponding to the error is recorded in the error information. As the category ID of the error information, the same definition as the ID used in the plan information (FIG. 12) is used.

  When the error information is recorded as described above, the electronic computer 10 refers to the plan information and confirms whether or not there is a plan operation in the same category as the current error. This confirmation may be performed by determining whether or not the same error category ID as the current error exists in the plan information. As a result, when there is no planned work of the same category (step A43: No), it is considered that the current error is not caused by the planned work, and an error is reported to the monitoring device 30 in the same procedure as in the above-described embodiment. (Step A47). Then, the status flag of the notified error is updated from “A” to “P1” (reported) (step A48).

  If there is a planned work of the same category as the current error (step A43: Yes), the electronic computer 10 recognizes the date and time of occurrence of the error and the work schedule of the same category (step A44). Then, the recognized date / time value is analyzed, and it is determined whether or not the error occurrence date / time is included in the planned work schedule (step A45).

  As a result of the above analysis, if the error occurrence date / time is not included in the work schedule (step A46: No), it is considered that the error is not caused by the planned work. In this case, an error is reported to the monitoring device 30 (step A47), and the status flag of the reported error is updated from “A” to “P1” (reported) (step A48).

  On the other hand, when the date and time of occurrence of the error is included in the work schedule (step A46: Yes), the error is considered to have occurred due to the planned work. Here, taking the entry surrounded by the chain line in FIG. 14 as an example, the category of this error is “ID = c2”. In the plan information of FIG. 12, there are two work entries of the same category (ID = c2) (chain line frame). Of these two entries, it is analyzed whether or not there is one that includes the current error occurrence time in the work schedule. As a result, the work schedule (“2007/04/25 12:00” to “2007/04/25 13:00”) in the lower chain line in FIG. 12 indicates the time when the current error occurred (FIG. 14: “2007 / 04/25 12:30:00 "). Therefore, the current error is determined to be an error associated with the work entry work.

  If it is determined that the error is caused by the planned work, the electronic computer 10 updates the error status flag from “A” to “P2” (not reported), and invalidates the error reporting to the monitoring device 30 (step A49).

  According to the above embodiment, it is possible to control the error event associated with the planned work so as not to notify the monitoring device 30 as in the above-described embodiment along FIG. Further, in the present embodiment, it is possible to efficiently determine an error to be reported by classifying and managing planned work and error events into categories. Specifically, for example, when there is no planning work in the same category as the error that has occurred (step S43: No), it is possible to shift to error notification at that time without analyzing the time of occurrence of the error.

  The category classification of work and errors can be set as appropriate. For example, hardware error events may be subdivided into each storage device (14a, 14b), a cooling FAN (not shown), or the like, and managed. As a result, the error event can be analyzed in detail.

  The implementation of the present invention is not limited to the above-described embodiment, and various modifications are possible. For example, when the monitoring device 30 outputs information to each display window (33a, 33b), customer (computer ID) information may be selectively output according to an operator instruction. Thereby, visibility improves.

  Further, a removable storage medium is used as the non-volatile memory 14a of the electronic computer 10, and the non-volatile memory 14a is removed during the planning work by recording the plan information and error information in both the non-volatile memory 14a and the magnetic disk 14b. be able to. Thereby, it is possible to prevent the recorded information from being lost due to a work accident.

  In each of the embodiments described above, when the removal work (FIG. 2: ID = 10) of the electronic computer 10 is entered in the plan information, the electronic computer 10 is replaced with an input by an operator or the like to complete the work. A maximum value such as “December 31, 9999” may be automatically set.

  The present invention can be implemented as a computer program corresponding to the operation of the electronic computer (10) and a recording medium storing the program.

1 is a configuration diagram of a system in an embodiment of the present invention. It is explanatory drawing regarding the work plan in embodiment of this invention. It is a flowchart which shows operation | movement of the electronic computer in embodiment of this invention. It is explanatory drawing regarding the plan information in embodiment of this invention. It is a flowchart regarding the error event of the electronic computer in the embodiment of the present invention. It is explanatory drawing regarding the error information in embodiment of this invention. It is a flowchart which shows operation | movement of the monitoring apparatus in embodiment of this invention. It is explanatory drawing of the plan display window of the monitoring apparatus in embodiment of this invention. It is explanatory drawing of the error display window of the monitoring apparatus in embodiment of this invention. It is a flowchart regarding the error event of the electronic computer in other embodiment of this invention. It is explanatory drawing regarding the error information in other embodiment of this invention. It is explanatory drawing regarding the plan information in further another embodiment of this invention. It is a flowchart regarding the error event of the electronic computer in further another embodiment of this invention. It is explanatory drawing regarding the error information in further another embodiment of this invention.

Explanation of symbols

100: system, 10: electronic computer, 11: communication unit, 12: control unit, 13: input unit, 14: storage unit, 14a: nonvolatile memory, 14b: magnetic disk, 15: display unit, 20: power supply unit, 30 : Monitoring device, 31: Communication unit, 32: Control unit, 33: Display unit, 33a: Plan display window, 33b: Error display window, 34a: Customer DB, 34b: Notification DB, 40: Time server, 50: Network

Claims (12)

A monitoring device connected to a network and a plurality of monitored devices;
Each of the monitored devices records a plan information inputted with respect to a work plan for the own device in a storage medium, and detects the occurrence of an error event in the own device and stores error information indicating the occurrence of the error event. And means for transmitting the plan information and error information of the storage medium together with identification information of the own device to the monitoring device,
The monitoring device includes means for recording the plan information and error information from each monitored device in association with the identification information of the monitored device on a storage medium, and the plan information and error information of the storage medium for each monitored device. Means for displaying ,
Each of the monitored devices further determines whether or not an error occurrence time indicated by the error information when the error information is recorded corresponds to a work plan time zone in the plan information. A remote notification system comprising means for transmitting the error information to the monitoring device when the time does not correspond to a planned time zone, and invalidating the transmission of the error information when the time corresponds to a work plan time zone in the determination . The invalidating means further records the category to which the work plan belongs in association with the work plan of the plan information, records the category to which the error event belongs in the error information when an error event occurs, and stores the error information. When the information is recorded, it is determined whether or not the same work plan as the category exists in the plan information, and if the determination is not possible, the error information is transmitted to the monitoring device. The remote reporting system according to 1. In the determination, when the plan has the same work plan as the category of the error information in the determination, the invalidating means sets the error occurrence time indicated by the error information to the time of the work plan of the same category in the plan information. In the determination, if the time does not correspond to the work plan time zone, the error information is transmitted to the monitoring device. If the determination corresponds to the work plan time zone, the error is detected. 3. The remote notification system according to claim 2 , wherein transmission of information is invalidated. The monitoring device, when displaying the plan information and error information of the storage medium, displays the information to be displayed along a time series based on the time zone of the corresponding work plan and the time when the error occurred. The remote notification system according to any one of claims 1 to 3 . An electronic computer as a monitored device connected to a monitoring device via a network,
Means for recording plan information input on a work plan for the own device in a storage medium;
Means for detecting the occurrence of an error event in its own device and recording error information indicating the occurrence of the error event in a storage medium;
Means for transmitting plan information and error information of the storage medium together with identification information of the own device to the monitoring device ;
When the error information is recorded, it is determined whether or not the error occurrence time indicated by the error information corresponds to a work plan time zone in the plan information. Means for transmitting the error information to the monitoring device, and invalidating the transmission of the error information when the time corresponds to a work plan time zone in the determination;
An electronic computer comprising The invalidating means further records the category to which the work plan belongs in association with the work plan of the plan information, records the category to which the error event belongs in the error information when an error event occurs, and stores the error information. When the information is recorded, it is determined whether or not the same work plan as the category exists in the plan information, and if the determination is not possible, the error information is transmitted to the monitoring device. 5. The electronic computer according to 5 . In the determination, when the plan has the same work plan as the category of the error information in the determination, the invalidating means sets the error occurrence time indicated by the error information to the time of the work plan of the same category in the plan information. In the determination, if the time does not correspond to the work plan time zone, the error information is transmitted to the monitoring device. If the determination corresponds to the work plan time zone, the error is detected. 7. The electronic computer according to claim 6 , wherein transmission of information is invalidated. A program for causing a computer to function as the electronic computer according to any one of claims 5 to 7 . Each of the plurality of monitored devices connected to the monitoring device via the network records the plan information input regarding the work plan for the own device in a storage medium, detects the occurrence of an error event in the own device, and detects the error. Error information indicating the occurrence of an event is recorded in a storage medium, and the plan information and error information of the storage medium are transmitted to the monitoring device together with identification information of the own device
The monitoring device, the planning information and error information is recorded in a storage medium in association with the identification information of the monitored device from the monitored device, and displays the planning information and error information of the storage medium by the device to be monitored ,
Each of the monitored devices further determines whether or not an error occurrence time indicated by the error information when the error information is recorded corresponds to a time zone of the work plan in the plan information. A remote notification method that transmits the error information to the monitoring device when the time does not correspond to the plan time zone, and invalidates the transmission of the error information when the time corresponds to the work plan time zone in the determination. Each of the monitored devices further records a category to which the work plan belongs in association with the work plan of the plan information, records a category to which the error event belongs in error information when an error event occurs, and the error information When the information is recorded, it is determined whether or not the same work plan as the category exists in the plan information, and if the determination is not possible, the error information is transmitted to the monitoring device. 9. The remote reporting method according to 9 . When each of the monitored devices has the same work plan as the category of the error information in the determination in the plan information, the error occurrence time indicated by the error information is the time of the work plan of the same category in the plan information. In the determination, if the time does not correspond to the work plan time zone, the error information is transmitted to the monitoring device. If the determination corresponds to the work plan time zone, the error is detected. The remote notification method according to claim 10 , wherein transmission of information is invalidated. When the monitoring device displays plan information and error information of the storage medium, the information to be displayed is displayed so as to follow a time series based on a corresponding work plan time zone and an error occurrence time. The remote notification method according to any one of claims 9 to 11 .

Images