JP4856691B2 - Failure information providing system, failure information providing method, and failure information providing program - Google Patents

Description

  The present invention relates to a failure information providing system, a failure information providing method, and a failure information providing program for providing failure information to a person in charge of each device or job when a failure occurs in a monitored device or a monitored job.

  The operating state of a system used in the company is monitored, and when a failure is detected, the person in charge is notified. Here, if a notification is made every time a failure occurs, the person in charge who receives the notification takes time to confirm the notification. Therefore, a failure notification system for efficiently reporting a failure of a monitored device has been studied. (For example, refer to Patent Document 1). In the technique described in this document, when a management computer of a monitoring system detects a failure in a monitoring target device, it identifies a notification group from the failure type management data storage unit of the failure. The management computer records a failure when the specified report group is in the process of report management or has been confirmed. When the message management process is not in progress, new report data is recorded and the message management process is performed.

On the other hand, an authentication system for detecting and eliminating unauthorized access due to a source address or password stealing has also been studied (for example, see Patent Document 2). In the technique described in this document, a plurality of passwords and setting information are stored in each of the connection device and the terminal. The time of the connection device and the terminal is synchronized, and the password is changed by changing the password with the passage of time according to the setting information. The terminal adds a password to the frame to be transmitted and sends it out, and the connection device compares the received frame password with the password of the connection device. If the passwords match, the connection device permits the communication of the terminal, and if they do not match, the communication is disallowed and the frame is discarded.
JP 2007-264907 A (first page, FIG. 5) Japanese Patent Laying-Open No. 2001-209614 (first page, FIG. 1)

  For the person in charge, it is convenient not only to receive a report about the failure but also to check the content of the failure or handle this failure using a portable terminal. However, the technique described in Patent Document 1 does not consider a method for providing failure information.

  Further, when confirming the contents of the failure or dealing with the failure, it is necessary to access the failure management system, and it is necessary to ensure security for this purpose. In this case, although it is possible to use the technique described in Patent Document 2, synchronization between the connection device and the terminal is necessary, and accurate time management is necessary to perform synchronization. In particular, it is desirable that even when such personal authentication is performed, it is possible to perform the personal authentication as easily as possible in order to quickly deal with a failure. In other words, in such a situation, it is necessary to consider accurate security and convenience for the person in charge.

  The present invention has been made in view of the above-described problems, and the object of the present invention is to efficiently and accurately provide information on failure to the person in charge of each device or job when a failure occurs in the monitored device or monitored job. Is to provide a failure information providing system, a failure information providing method, and a failure information providing program.

In order to solve the above-mentioned problem, the invention described in claim 1 is a report destination information storage means in which data relating to a user identifier and a contact person of a person in charge belonging to a group that performs a report in response to a failure message is recorded. Failure information storage means for recording failure information in which a report identifier and a failure message are associated; authentication information storage means for recording first and second access codes for each user identifier and report identifier; and a user in charge A fault information providing system comprising a control means for communicating with a terminal, wherein when the control means obtains a fault message from a monitored device, a means for assigning a notification identifier and registering it in the fault information storage means And means for identifying a person in charge belonging to the group corresponding to the failure message using the report destination information storage means, and a person in charge for making a report Means for generating first and second access codes, means for registering the first and second access codes in the authentication information storage means for each user identifier and report identifier of the person in charge of making the report, The person in charge uses a notification mail displaying the URL obtained by adding the first access code to the address for accessing the failure information stored in the failure information storage means and the second access code. When the URL is accessed from the means for transmitting to the user terminal and the user terminal, an authentication information input screen for the user identifier and the second access code is transmitted, and the URL of the accessed URL is accessed. 1 access code, a user identifier obtained via the authentication information input screen, and a second access code are registered in the authentication information storage means Expediently, allow login, and means for transmitting the reference screen on the failure information fault information recorded in the storage unit to the user terminal, the time elapsed from transmission of the alert mail is measured If the response to the failure cannot be detected even after the response reference time has elapsed, the person in charge who has already transmitted the notification mail is identified using the notification destination information storage means and another person in charge belonging to the group is identified. For the person who sends the notification mail not including the URL and the second access code, for the person who newly sends the notification mail, the first and second access codes are newly generated. A gist of the invention is that it includes means for registering in the authentication information storage means and transmitting a notification mail including a URL and a second access code .

  According to a second aspect of the present invention, in the fault information providing system according to the first aspect, when the control unit registers the fault information in the fault information storage unit, a fault message is sent to each access code. The present invention is further characterized by further comprising means for invalidating an access code associated with the failure message when the failure occurrence time acquired is recorded and the code retention reference time has elapsed from the failure occurrence time.

According to a third aspect of the present invention, in the failure information providing system according to the first or second aspect , when the control means transmits a notification mail, the person in charge uses the authentication information storage means. When a failure is searched for another group to which it belongs and another failure is registered, a link icon for outputting the failure information is added to the reference screen, and access is received using the link icon. In this case, the gist is to transmit a reference screen for another failure to the user terminal on the condition that login has already been performed.

According to a fourth aspect of the present invention, in the failure information providing system according to any one of the first to third aspects, when the user identifier input on the authentication information input screen cannot be collated, The gist of the invention is that it further comprises means for invalidating the first and second access codes.

According to a fifth aspect of the present invention, in the failure information providing system according to any one of the first to fourth aspects, if the user identifier input on the authentication information input screen cannot be verified, the authentication is performed. The gist of the present invention is that the information storage means further includes means for specifying a user identifier associated with the first and second access codes and invalidating all access codes associated with the user identifier.

According to the sixth aspect of the present invention, a report destination information storage means in which data relating to a user identifier and a contact person of a person in charge who reports in response to a fault message is recorded, and the report identifier and the fault message are associated with each other. Failure information storage means for recording the failure information, authentication information storage means for recording the first and second access codes for each user identifier and report identifier, and control means for communicating with the user terminal of the person in charge A method for providing failure information using a provided failure information providing system, wherein when the control unit acquires a failure message from a monitored device, a notification identifier is assigned and registered in the failure information storage unit Identifying the person in charge belonging to the group corresponding to the failure message using the report destination information storage means, and the person responsible for reporting Generating first and second access codes for each person, and registering the first and second access codes in the authentication information storage means for each user identifier and notification identifier of the person in charge of making the notification And the person in charge receives a notification mail displaying the URL with the first access code added to the address for accessing the failure information stored in the failure information storage means and the second access code. And when the URL is accessed from the user terminal, an authentication information input screen for the user identifier and the second access code is transmitted, and the accessed URL The first access code, the user identifier obtained through the authentication information input screen, and the second access code are registered in the authentication information storage means. If that is measured allow login, and transmitting the reference screen for failure information the recorded fault information storing unit to the user terminal, the time elapsed from transmission of the alert mail If the response to the failure cannot be detected even after the response reference time has elapsed, the notification destination information storage means is used to identify another person in charge belonging to the group, and the notification email has already been transmitted. For the person in charge, a notification mail not including the URL and the second access code is transmitted, and for the person in charge who newly transmits a notification mail, first and second access codes are newly generated. And the step of registering in the authentication information storage means and transmitting a notification mail including the URL and the second access code .

According to the seventh aspect of the present invention, a report destination information storage means in which data relating to a user identifier and a contact person of a person in charge who reports in response to a fault message is recorded, and the report identifier and the fault message are associated with each other. Failure information storage means for recording the failure information, authentication information storage means for recording the first and second access codes for each user identifier and report identifier, and control means for communicating with the user terminal of the person in charge A program for providing fault information using the provided fault information providing system, wherein when the fault message is acquired from the monitored device, the control means is assigned a report identifier and registered in the fault information storage means Means, and means for identifying the person in charge belonging to the group corresponding to the failure message, using the report destination information storage means Means for generating the first and second access codes for each person, means for registering the first and second access codes in the authentication information storage means for each user identifier of the person who makes the report and for each report identifier A notification mail displaying the URL with the first access code added to the address for accessing the failure information stored in the failure information storage means and the second access code is sent to the person in charge. When the URL is accessed from the means for transmitting to the user terminal or from the user terminal, an authentication information input screen for the user identifier and the second access code is transmitted, and the first URL of the accessed URL is transmitted. 1 access code, a user identifier obtained via the authentication information input screen, and a second access code are registered in the authentication information storage means Expediently, allow login, means for transmitting a reference screen for the failure information fault information recorded in the storage unit to the user terminal measures the time elapsed from transmission of the alert mail, If the response to the failure cannot be detected even after the response reference time has elapsed, the person in charge who has already transmitted the notification mail is identified by using the notification destination information storage means to identify another person in charge belonging to the group For the person in charge who transmits the notification mail not including the URL and the second access code, and newly generates the first and second access codes, The gist of the present invention is that it is registered in the authentication information storage means and functions as means for transmitting a notification mail including the URL and the second access code .

(Function)
According to the first, sixth, or seventh aspect of the invention, when the control unit acquires a failure message from the monitored device, the control unit assigns a notification identifier and registers it in the failure information storage unit. Next, the person in charge belonging to the group corresponding to the failure message is specified using the report destination information storage means. Then, first and second access codes are generated for each person in charge of reporting, and the first and second access codes are registered in the authentication information storage unit for each user identifier and reporting identifier of the person in charge of reporting. . Next, the user of the person in charge receives a notification mail displaying the URL obtained by adding the first access code to the address for accessing the failure information stored in the failure information storage means and the second access code. Send to the terminal. When a URL is accessed from the user terminal, an authentication information input screen for a user identifier and a second access code is transmitted. If the first access code of the accessed URL, the user identifier obtained via the authentication information input screen, and the second access code are registered in the authentication information storage means, login is permitted. Then, a reference screen for the failure information recorded in the failure information storage means is transmitted to the user terminal. By using a plurality of access codes, personal authentication can be performed accurately. Further, since the first access code is added to the URL, the operation load on the user can be reduced.

  According to the second aspect of the present invention, when the control unit registers the failure information in the failure information storage unit, the failure occurrence time when the failure message is acquired is recorded for each access code. When the code holding reference time has elapsed from the failure occurrence time, the access code associated with the failure message is invalidated. If the access code is made valid for a long period of time, the access code is more likely to leak. Therefore, security can be improved by invalidating the access code.

According to the present invention, the control unit measures the elapsed time since the transmission of the notification mail, and if the response to the failure cannot be detected even after the response reference time has elapsed, the notification destination information storage unit is used. Identify other people in the group. Then, a notification mail that does not include the URL and the second access code is transmitted to the person in charge who has already transmitted the notification mail. On the other hand, for the person in charge who newly sends the notification mail, the first and second access codes are newly generated and registered in the authentication information storage means, and the notification including the URL and the second access code is also included. send mail. Thereby, when the person in charge who transmitted the report mail cannot respond, it is possible to urge other persons in charge to respond. Furthermore, when the notification mail is retransmitted, the URL or access code is not added, so that the chance of access code leakage can be suppressed. The other person in charge can acquire the failure information by using the URL or access code added to the newly acquired notification mail.

According to the third aspect of the present invention, when the control means transmits a notification mail, the authentication information storage means is used to search for a failure in another group to which the person in charge belongs. Here, when other faults are registered, a link icon for outputting the fault information is added to the reference screen. Then, when access is received using the link icon, a reference screen for another failure is transmitted to the user terminal on the condition that login has already been performed. Thereby, the person in charge who acquired the report mail can efficiently grasp other failure situations. Further, even when an access code is set for each person in charge or for each failure, other failure information can be quickly acquired based on the identity authentication performed previously.

According to the fourth aspect of the present invention, when the user identifier input on the authentication information input screen cannot be verified, the first and second access codes are invalidated. Thereby, even when a third party other than the user is operating the user terminal, security can be maintained by denying access.

According to the fifth aspect of the present invention, when the user identifier input on the authentication information input screen cannot be collated, the user identifier associated with the first and second access codes in the authentication information storage means is displayed. Identify and invalidate all access codes associated with this user identifier. As a result, the user identifier stored in association with the first and second access codes is specified, and the other access codes for this person in charge are invalidated. Accordingly, security can be ensured even when the user terminal of the person in charge may be stolen.

  According to the present invention, when a failure occurs in a monitoring target device or a monitoring target job, a failure information providing system and a failure information providing method for efficiently and accurately providing failure information to a person in charge of each device or job And a failure information providing program can be provided.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In this embodiment, in order to monitor the monitoring target device 10, an integrated monitoring server 20 as a failure information providing system is used as shown in FIG. In the present embodiment, for example, the occurrence of a failure in the monitoring target device 10 such as a mainframe or various business system servers is monitored.

  The monitoring target device 10 is connected to the integrated monitoring server 20 via a network. Each monitored device 10 transmits an alert (failure message) to the integrated monitoring server 20 when a failure occurs. This failure message includes data relating to the content of the failure that has occurred (here, a failure code for identifying the failure) and data relating to a device code for identifying the monitoring target device 10 that is the transmission source.

  As shown in FIG. 1, a plurality of user terminals (here, mobile phone terminals 30) are connected to the integrated monitoring server 20 via a network. The mobile phone terminal 30 is a mobile terminal used by a person in charge for handling a failure. The mobile phone terminal 30 is a report destination that receives a report from the integrated monitoring server 20, and also functions as a computer terminal for the person in charge who has received the report to access the integrated monitoring server 20.

  The mobile phone terminal 30 includes a control unit, a communication processing unit, a terminal memory, a display unit, an input unit, and the like. The communication processing unit is connected to the base station of the mobile phone network by a known method, and performs communication processing for sending and receiving calls and e-mails.

The terminal memory stores application programs that can be executed by the mobile phone terminal 30 and received e-mails.
The display unit displays e-mail received by the mobile phone terminal 30, user instructions at the time of program execution, and the like.

  The input unit has a selector button and a mode change button in addition to the dial number button. The mobile phone terminal 30 has a program execution mode for executing an execution process in an e-mail mode and a browser mode for sending and receiving e-mails in addition to the normal telephone mode. When switching from each mode (for example, telephone mode) to another mode (for example, e-mail mode), a mode change button is used. The browser mode can also be switched from the email mode by selecting a link icon included in the email.

  The selector button of the mobile phone terminal 30 has a cursor movement function and a click function. By giving a direction instruction using the selector button, the cursor on the display unit can be moved, and by pressing the selector button, the item indicated by the cursor can be selected.

The integrated monitoring server 20 that monitors a failure in the monitored device 10 includes a control unit 21, a failure type management data storage unit 22, a report destination management data storage unit 23, and a report management data storage unit 24.
The authentication inquiry data storage unit 25 is provided. And the control part 21 functions as a control means comprised from CPU, RAM, ROM, etc., and processes (report management stage, access ticket registration stage, access ticket management stage, user authentication stage, failure information provision stage, etc.) to be described later (Including processing). By executing the failure information providing program for this purpose, the control unit 21 functions as a notification management unit 211, an access ticket registration unit 212, an access ticket management unit 213, a user authentication unit 214, a failure information providing unit 215, and the like.

  The notification management unit 211 executes processing for monitoring reception of an alert (failure message) transmitted by the monitoring target device 10. As will be described later, the notification management unit 211 holds data relating to a standby reference period (response reference time) for waiting for the person in charge and a reference end number of times (here, three times) for ending the notification. .

  The access ticket registration unit 212 executes processing for generating personal authentication information (access ticket) to be used when authenticating the person in charge using a random number and registering it in the authentication query data storage unit 25.

  The access ticket management unit 213 executes maintenance management processing (maintenance) for each access ticket registered in the authentication query data storage unit 25. In the present embodiment, processing for deleting an access ticket that has passed a predetermined access ticket holding reference time (code holding reference time) from transmission is executed. In the present embodiment, 24 hours are set as the access ticket holding reference time.

The user authentication means 214 acquires an access ticket from the mobile phone terminal 30 and executes an accessor's identity authentication process. The user authentication unit 214 includes a memory that records the number of unmatches in association with the user ID, the first access ticket, and the second access ticket in the access rejection process. Further, the user authentication unit 214 holds data relating to the first reference value (for example, twice) and the second reference value (for example, four times) used for determining invalidation of the access ticket.
The failure information providing unit 215 executes processing for providing failure information to the person in charge who has completed the personal authentication.

  The failure type management data storage unit 22 functions as a failure information storage unit. In the failure type management data storage unit 22, as shown in FIG. 2A, a failure type management record 220 for specifying a group of persons in charge corresponding to the failure is recorded. The failure type management record 220 is recorded when a person in charge corresponding to each failure is determined and registered. The failure type management record 220 includes data related to the failure type and report group identifier.

In the failure type data area, data related to an event that has occurred in the monitored device 10 and needs to be handled by the person in charge is recorded. In the present embodiment, a device code and data related to the failure code are recorded as the failure type.
In the report group identifier data area, data relating to an identifier for specifying a group of persons in charge who transmit a report about the failure is recorded.

  The report destination management data storage unit 23 functions as a report destination information storage unit. As shown in FIG. 2B, the report destination management data storage unit 23 stores a report destination management record 230 related to a person in charge belonging to a group that handles each failure. The report destination management record 230 is registered when the person in charge who handles the failure of the monitored device 10 is determined. The report destination management record 230 includes data regarding a report group identifier, a first report destination, a second report destination, and a third report destination.

In the report group identifier data area, data relating to an identifier for specifying a group of persons in charge for handling a failure is recorded.
In the first report destination data area, data relating to a report destination (person in charge) of the first priority to be reported first in this group is recorded. A plurality of persons in charge can be recorded in the first priority report destination data area. In this first report destination data area, data (user ID, person in charge name) for specifying each person in charge and data relating to a contact address (e-mail address) are recorded.

  In the second report destination data area, data (user ID, name of person in charge, e-mail address) regarding the second priority report destination (person in charge) to be reported second in this group is recorded. The setting of the second report destination is not essential, and a plurality of persons in charge can be set.

  In the third report destination data area, data (user ID, name of person in charge, e-mail address) regarding the third priority report destination (person in charge) to be reported third in this group is recorded. The setting of the third report destination is not essential, and a plurality of persons in charge can be set.

  As shown in FIG. 2C, the report management data storage unit 24 stores a report management record 240 related to a report about a failure that has occurred. This notification management record 240 is registered when a new notification needs to be made, and is updated in response to the subsequent occurrence of a failure. The report management record 240 includes data regarding a report identifier, a report group identifier, a failure status, a failure content, a reporter, and a report count.

Data relating to an identifier for specifying each report is recorded in the report identifier data area.
In the notification group identifier data area, data relating to an identifier for specifying a group performing a notification is recorded.

  In the failure status data area, a flag for specifying the current status of the failure is recorded. For the failure status data, a flag indicating one of the states “unconfirmed”, “confirmed” or “recovered” is used. Here, the “unconfirmed” flag indicates that the person in charge of the report destination has not yet taken action. The “confirmed” flag indicates that the person in charge at the report destination has confirmed the report. The “recovered” flag indicates that the person in charge has performed recovery processing in response to the failure.

  In the failure content data area, data relating to the content of the failure that has occurred (failure content) is recorded in correspondence with the failure occurrence time. In the failure content data area, a failure message for each notification is recorded. Each failure message includes data relating to the content of the failure (device code, failure code) when the failure occurs (date and time). If a failure status is “unconfirmed” or “confirmed” in the notification management record 240 for the same notification group, a failure message is additionally recorded in the notification management record 240 for the newly generated failure.

In the report person data area, data (here, a user ID) for specifying the person who sends the report mail is recorded. In this embodiment, when reporting to a plurality of reporting personnel, the user ID of each responsible personnel is recorded. Further, when a report mail is transmitted to the report staff, a report flag for identifying the report completion is recorded in the report staff data area in association with this user ID.
Data related to the number of times of sending the notification mail is recorded in the notification frequency data area.

  The authentication inquiry data storage unit 25 functions as an authentication information storage unit. In the authentication inquiry data storage unit 25, as shown in FIG. 2D, an authentication inquiry record 250 for authenticating the person in charge who has accessed the integrated monitoring server 20 is recorded in response to the notification. . This authentication query record 250 is registered when a person in charge who transmits a report for a failure that has occurred is determined. The authentication inquiry record 250 includes data related to a report identifier, a user ID, a first access ticket, a second access ticket, a failure occurrence time, and an invalid flag.

In the notification identifier area, data relating to an identifier for identifying each failure that has occurred is recorded.
In the user ID data area, data relating to an identifier (user ID) for specifying a person in charge who has transmitted a failure message regarding this failure is recorded.

In the first access ticket data area and the second access ticket data area, data related to an access code for performing authentication for identifying the person in charge is recorded.
In the failure occurrence time data area, data related to the time when the failure occurred is recorded. In the case where a plurality of failure messages have occurred before recovery from a series of failures, data relating to the first failure occurrence time is recorded.

  A flag for invalidating the access ticket is recorded in the invalid flag data area. This invalid flag is recorded when a predetermined time (in this case, 24 hours) has elapsed from the failure occurrence time or when an access ticket is invalidated in the access denial process.

Next, the processing procedure of the integrated monitoring server 20 when a failure occurs in the system configured as described above will be described with reference to FIGS.
(Report management)
First, report management will be described with reference to FIG.

  When a failure occurs, the monitoring target device 10 alerts the integrated monitoring server 20 via the network. Specifically, the monitoring target device 10 transmits a failure message to the integrated monitoring server 20.

  The control unit 21 of the integrated monitoring server 20 executes alert monitoring processing (step S1-1). Specifically, the notification management unit 211 of the control unit 21 waits for reception of a failure message from the monitoring target device 10.

  And the control part 21 of the integrated monitoring server 20 which received the failure message from the monitoring object apparatus 10 performs an alert registration process (step S1-2). Specifically, the report management unit 211 of the control unit 21 registers the failure information of the monitoring target device in the report management data storage unit 24 as described later.

  Next, the control unit 21 of the integrated monitoring server 20 executes a process for identifying the person in charge of reporting (step S1-3). Specifically, the report management unit 211 of the control unit 21 uses the report destination management data storage unit 23 to specify the person in charge to which the report mail is transmitted, as will be described later.

  And the control part 21 of the integrated monitoring server 20 performs a report mail transmission process for every report person in charge (step S1-4). Specifically, the report management unit 211 of the control unit 21 transmits a report mail to the specified reporter as will be described later.

  When the notification to each person in charge of reporting is completed, the control unit 21 of the integrated monitoring server 20 executes standby processing (step S1-5). Specifically, the notification management unit 211 of the control unit 21 waits for a predetermined standby reference time (for example, 10 minutes).

  And the control part 21 of the integrated monitoring server 20 performs the determination process about whether it was recovered or confirmed (step S1-6). Specifically, the notification management unit 211 of the control unit 21 has a “recovered” flag or a “confirmed” flag recorded in the failure status data area of the notification management record 240 recorded in the notification management data storage unit 24. Judge by whether or not. If it has not yet been recovered or confirmed ("NO" in step S1-6), the processing from the reporting person specifying process (step S1-3) is repeated again. On the other hand, if it has been recovered (in the case of “YES” in step S1-6), the control unit 21 of the integrated monitoring server 20 ends the notification management process.

(Alert registration process)
Next, alert registration processing will be described with reference to FIG.
Here, first, the control unit 21 of the integrated monitoring server 20 executes report group identification processing (step S2-1). Specifically, the notification management unit 211 of the control unit 21 searches the failure type management data storage unit 22 for a failure type management record 220 for the detected failure content (device code and failure code). When the failure type management record 220 for this failure can be extracted from the failure type management data storage unit 22, the notification management unit 211 identifies the notification group identifier included in this failure type management record 220.

  When the failure type management record 220 cannot be extracted, the notification management unit 211 notifies the system operator. Specifically, the notification management unit 211 transmits an e-mail to the e-mail address of the system operator in order to notify the system operator that the identification of the notification group could not be specified.

  Next, the control unit 21 of the integrated monitoring server 20 executes a process for searching for a report management record for this report group (step S2-2). Specifically, the report management unit 211 of the control unit 21 searches the report management data storage unit 24 for a report management record 240 in which the specified report group identifier is recorded.

  And the control part 21 of the integrated monitoring server 20 performs the determination process about whether the notification management record 240 is registered (step S2-3). When the report management record 240 is not registered (in the case of “NO” in step S2-3), the control unit 21 of the integrated monitoring server 20 executes a new registration process of the report management record (step S2-4). Specifically, the report management unit 211 of the control unit 21 newly assigns a report identifier, generates a report management record 240 in which a report group identifier, a failure status, and a failure content are set, and stores it in the report management data storage unit 24. Record. At this stage, the reporting person data area is blank and the reporting frequency data area is set to “0”.

  On the other hand, when the report management record 240 has already been registered (in the case of “YES” in step S2-3), the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether or not the recovery has been completed (step S2). -5). Specifically, the notification management unit 211 of the control unit 21 determines whether or not a recovery flag is recorded in the failure status data area of the notification management record 240.

  Here, when the recovery flag is recorded and it is determined that the recovery has already been performed (in the case of “YES” in step S2-5), the control unit 21 of the integrated monitoring server 20 executes a new registration process of the notification management record. (Step S2-4).

  On the other hand, when the recovery flag is not recorded and it is determined that the recovery has not been completed (“NO” in step S2-5), the control unit 21 of the integrated monitoring server 20 executes an additional recording process (step S2-6). ). Specifically, the notification management unit 211 of the control unit 21 additionally records the newly acquired failure message in the failure content data area of the specified notification management record 240.

(Identification process for reporter)
Next, the identification process of the person in charge of notification will be described with reference to FIG.
Here, the control part 21 of the integrated monitoring server 20 performs the determination process about whether it is the first report (step S3-1). Specifically, the notification management unit 211 of the control unit 21 determines based on the number of notifications recorded in the notification management record 240.

  When the number of reports is not recorded in the report management record 240 and it is determined as the first report (in the case of “YES” in step S3-1), the control unit 21 of the integrated monitoring server 20 is the first reporter. A notification destination setting process is executed (step S3-2). Specifically, the report management unit 211 of the control unit 21 sets the person in charge of the first report destination as the report person in the report destination management record 230 of the identified report group, and sets the user ID of this person in charge as the report management record. Record in 240.

  On the other hand, when the number of reports is already recorded in the report management record 240 and it is determined that the report is not the first report (in the case of “NO” in step S3-1), the control unit 21 of the integrated monitoring server 20 has the number of reports. A determination process is executed as to whether the number of times is less than the end reference number (step S3-3). Specifically, the report management unit 211 of the control unit 21 determines whether or not the number of reports recorded in the report management record 240 is a reference number (here, three times).

  When the number of notifications is less than the end reference number (in the case of “YES” in step S3-3), the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether there is a next-order notification destination (step). S3-4). Specifically, the report management unit 211 of the control unit 21 determines whether or not the next-ranked report destination is registered in the report destination management record 230. In this case, when the number of reports is “1” and the person in charge of the report destination in the first rank has been reported, the report destination in the second rank or later (second report destination or third report destination) ) Is registered. When the number of reports is “2” and the person in charge of the report destination in the second rank or higher has been reported, the presence or absence of registration of the report destination in the third rank or higher is confirmed.

  When there is a registration of the next-order report destination (in the case of “YES” in step S3-4), the control unit 21 of the integrated monitoring server 20 executes a process for adding the next-order report destination (step S3-5). . Specifically, the report management unit 211 of the control unit 21 additionally records in the report management record 240 the user ID of the person in charge of the next-ranked report destination recorded in the report destination management record 230. At this stage, the notification flag is not set yet.

When there is no registration of the report destination of the next order (in the case of “NO” in step S3-4), the control unit 21 of the integrated monitoring server 20 omits the process of step S3-5.
On the other hand, when the number of notifications is equal to or greater than the end reference number (in the case of “NO” in step S3-3), the control unit 21 of the integrated monitoring server 20 executes notification processing for the system operator (step S3-6). ). Specifically, the notification management unit 211 of the control unit 21 transmits an e-mail to the e-mail address of the system operator in order to notify the system operator that no action has been taken by the person in charge.

(Report email transmission process)
Next, the notification mail transmission process will be described with reference to FIG.
Here, the control part 21 of the integrated monitoring server 20 performs the determination process about whether it has already reported (step S4-1). Specifically, the notification management unit 211 of the control unit 21 determines that the notification has been made when the authentication inquiry record 250 in which the notification identifier and the user ID are recorded is generated in the authentication reference data storage unit 25. On the other hand, when the authentication inquiry record 250 in which the notification identifier and the user ID are recorded in the authentication inquiry data storage unit 25 is not generated, it is determined that the notification has not been made.

  When not notified (in the case of “NO” in step S4-1), the control unit 21 of the integrated monitoring server 20 executes the first and second access ticket generation processing (step S4-2). Specifically, the notification management unit 211 of the control unit 21 supplies an access ticket generation instruction to the access ticket registration unit 212. In this case, the access ticket registration unit 212 generates a set of access tickets.

  Next, the control unit 21 of the integrated monitoring server 20 executes a registration process for an authentication query record (step S4-3). Specifically, the access ticket registration unit 212 of the control unit 21 acquires the report identifier recorded in the report management record 240 and the user ID of the person in charge recorded in the report destination management data storage unit 23, and records these. The authentication reference record 250 is generated and recorded in the authentication reference data storage unit 25. Then, the access ticket registration unit 212 records the generated access ticket in the authentication query record 250.

  Next, the control unit 21 of the integrated monitoring server 20 executes URL generation processing using the first access ticket as an argument (step S4-4). Specifically, the notification management unit 211 of the control unit 21 acquires an address for accessing the failure information recorded in the notification management data storage unit 24. Then, the notification management unit 211 generates a URL in which the first access ticket recorded in the authentication query record 250 is added as an argument to this address.

  Next, the control unit 21 of the integrated monitoring server 20 executes notification mail generation processing including an access ticket (step S4-5). Specifically, the notification management unit 211 of the control unit 21 generates an email in which the failure content recorded in the notification management record 240, the second access ticket, and the generated URL are recorded.

  On the other hand, when the report has already been made (in the case of “YES” in step S4-1), the control unit 21 of the integrated monitoring server 20 executes a process for generating a report mail with the failure information added (step S4-6). Specifically, the notification management unit 211 of the control unit 21 generates an e-mail in which only the failure content recorded in the notification management record 240 is recorded. In this case, the second access ticket and the URL are not included in this e-mail.

  And the control part 21 of the integrated monitoring server 20 performs the transmission process of report mail (step S4-7). Specifically, the report management unit 211 of the control unit 21 acquires the email address of the person in charge from the report destination management data storage unit 23, and sets the email address as the destination of the email. Then, the notification management unit 211 executes this e-mail transmission process. Furthermore, the notification management unit 211 adds “1” to the number of notifications in the notification management record 240 recorded in the notification management data storage unit 24 and associates the notification flag with the user ID of the person in charge of the notification who transmitted the notification mail. Record.

(Failure information provision processing)
Next, failure information provision processing performed between the mobile phone terminal 30 that has received the notification mail and the integrated monitoring server 20 will be described with reference to FIGS.

  First, the mobile phone terminal 30 executes a notification mail display process (step S5-1). Specifically, the person in charge who received the notification mail at his / her mobile phone terminal 30 outputs the received electronic mail to the display unit. Then, the person in charge selects the URL included in the notification mail and inputs an access instruction. In this case, the mobile phone terminal 30 transmits an access request for this URL. This access request is transmitted to the integrated monitoring server 20 based on the address included in the URL.

  The control unit 21 of the integrated monitoring server 20 that has received the access request executes a first access ticket verification process (step S5-2). Specifically, the user authentication unit 214 of the control unit 21 acquires an argument added to the URL. With this argument, the first access ticket can be acquired.

  Next, the control unit 21 of the integrated monitoring server 20 executes a login screen transmission process (step S5-3). Specifically, the user authentication unit 214 of the control unit 21 transmits login screen data for outputting an authentication information input screen to the mobile phone terminal 30. This login screen is provided with user ID and access ticket setting fields.

  In this case, the mobile phone terminal 30 executes a login screen display process (step S5-4). Specifically, the mobile phone terminal 30 outputs a login screen on the display unit. Then, the person in charge inputs his / her user ID and the second access ticket displayed in the notification mail in each setting field of the login screen.

  Next, the cellular phone terminal 30 executes input data transmission processing (step S5-5). Specifically, when the person in charge selects the login request button on the login screen, the mobile phone terminal 30 performs integrated monitoring of input data including data related to the user ID and the second access ticket input in the setting field. Send to server 20.

  Thereby, the control part 21 of the integrated monitoring server 20 performs the acquisition process of a user ID and a 2nd access ticket (step S5-6). Specifically, the user authentication unit 214 of the control unit 21 acquires a user ID and a second access ticket from the mobile phone terminal 30.

  And the control part 21 of the integrated monitoring server 20 performs an access ticket collation process (step S5-7). Specifically, the user authentication means 214 of the control unit 21 includes an authentication query data storage unit 25 that includes a first access ticket acquired at the time of access request, an authentication query record 250 in which the user ID and second access ticket acquired this time are recorded. Check whether it is registered in.

  If the authentication inquiry record 250 in which the user ID, the first access ticket, and the second access ticket are recorded can be extracted, this access is validated. As shown in FIG. 8, when a valid authentication query record 250 cannot be extracted (in the case of “NO” in step S6-1), the control unit 21 of the integrated monitoring server 20 performs an access rejection process as will be described later. Is executed (step S6-2). Even when an invalid flag is recorded in the authentication query record 250, the control unit 21 executes an access denial process.

When a valid authentication query record 250 can be extracted (in the case of “YES” in step S6-1), the control unit 21 of the integrated monitoring server 20 executes failure information acquisition processing (step S6-3). Specifically, the failure information providing unit 215 of the control unit 21 acquires the report identifier recorded in the authentication inquiry record 250 and stores the report management record 240 in which the report identifier is recorded from the report management data storage unit 24. get. And fault information providing means 21
5 generates alert reference screen data in which the failure state, the failure content, and the person in charge of the notification recorded in the notification management record 240 are set. In this alert reference screen, a failure response icon for selecting “confirmation” and “recovery” is added when it is unconfirmed. In the case of confirmation, only a corresponding icon “recovery” is added. In the case of “recovery”, no failure response icon is added on the alert reference screen. As the person in charge of reporting, the person in charge corresponding to the user ID recorded in the report management record 240 is acquired from the report destination management data storage unit 23 and set.

  Furthermore, the control unit 21 of the integrated monitoring server 20 executes a search process for other failure information to which this user belongs (step S6-4). Specifically, the failure information providing unit 215 of the control unit 21 checks whether or not another authentication inquiry record 250 to which this user ID is assigned is recorded.

  When other failure information is recorded (in the case of “YES” in step S6-5), the control unit 21 of the integrated monitoring server 20 executes a link generation process to other failure information (step S6-6). ). Specifically, the failure information providing unit 215 of the control unit 21 adds another failure information link icon to the alert reference screen. If no other failure information is recorded (in the case of “NO” in step S6-5), the control unit 21 of the integrated monitoring server 20 omits this step.

  And the control part 21 of the integrated monitoring server 20 performs the provision process of failure information (step S6-7). Specifically, the failure information providing unit 215 of the control unit 21 transmits the generated alert reference screen data to the mobile phone terminal 30.

  In this case, the mobile phone terminal 30 executes a failure information display process (step S6-8). Specifically, as shown in FIG. 12, the mobile phone terminal 30 outputs the received alert reference screen 510 to the display unit. This alert reference screen 510 includes a failure handling icon 511, a failure content display column 512, a reporter display column 513, and other failure information link icons 514.

  Then, the cellular phone terminal 30 executes a failure confirmation transmission process (step S6-9). Specifically, the person in charge confirming the content of the failure selects the failure handling icon 511 as necessary. In this case, the mobile phone terminal 30 transmits failure confirmation data to the integrated monitoring server 20 based on the selected failure handling icon.

  Then, the control unit 21 of the integrated monitoring server 20 executes failure confirmation registration processing (step S6-10). Specifically, the failure information providing unit 215 of the control unit 21 updates the failure status of the notification management record 240 based on the data received from the mobile phone terminal 30. Specifically, when a “confirmed” failure handling icon is selected, a “confirmed” flag is recorded in the failure status data area. When the “recovery” selection icon is selected, a “recovered” flag is recorded.

Next, provision of other fault information will be described with reference to FIG.
Here, the mobile phone terminal 30 executes another failure information link selection process (step S7-1). Specifically, when the other failure information link icon 514 of the alert reference screen 510 output to the display unit of the mobile phone terminal 30 is selected, the mobile phone terminal 30 transmits the other failure information request to the integrated monitoring server 20. To do.

In this case, the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether or not login has been completed (step S7-2). Specifically, the failure information providing means 215 of the control unit 21
Determines that the user has logged in if the session has continued since the previous failure information was provided.

  If the session is not continued and the user has not logged in (in the case of “NO” in step S7-2), the control unit 21 of the integrated monitoring server 20 executes an access rejection process (step S7-3). Specifically, the failure information providing unit 215 of the control unit 21 transmits a message indicating that information cannot be provided to the mobile phone terminal 30.

  On the other hand, if the session is continued and logged in (in the case of “YES” in step S7-2), the control unit 21 of the integrated monitoring server 20 executes another failure information acquisition process (step S7—). 4). Specifically, the failure information providing unit 215 of the control unit 21 specifies the authentication inquiry record 250 in which the user ID that has previously performed the personal authentication is recorded, and specifies the report identifier recorded in this record. Then, the failure information providing unit 215 extracts the notification management record 240 in which the notification identifier is recorded from the notification management data storage unit 24. Then, the failure information providing unit 215 generates alert reference screen data in which the content of the report management record 240 is set.

  Next, the control unit 21 of the integrated monitoring server 20 executes another failure information transmission process (step S7-5). Specifically, the failure information providing unit 215 of the control unit 21 transmits the generated alert reference screen data to the mobile phone terminal 30.

  Next, the cellular phone terminal 30 executes a failure information display process (step S7-6). Specifically, as shown in FIG. 12, the mobile phone terminal 30 outputs an alert reference screen 520 to the display unit. The alert reference screen 520 also includes a failure handling icon 521, a failure content display column 522, a reporter display column 523, and another failure information link icon 524. In the failure content display column 522, other failure information is displayed.

  Next, the cellular phone terminal 30 executes a failure confirmation transmission process (step S7-7). Also in this case, the person in charge confirms other fault information and selects the fault handling icon 521 as necessary. Thereby, the mobile phone terminal 30 transmits the failure confirmation data to the integrated monitoring server 20.

  Then, the control unit 21 of the integrated monitoring server 20 executes a failure confirmation registration process (step S7-8). Specifically, the failure information providing unit 215 of the control unit 21 records a flag corresponding to the received failure confirmation data in the failure status data area of the notification management record 240.

(Access denied processing)
Next, the access rejection process will be described with reference to FIG.
Here, the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether or not the user ID is unmatched (step S8-1). Specifically, the user authentication unit 214 of the control unit 21 searches the authentication inquiry record 250 based on the input data received from the mobile phone terminal 30. If there is no authentication query record 250 that completely matches the user ID, the first access ticket, and the second access ticket, the presence or absence of the authentication query record 250 that matches the first access ticket and the second access ticket is confirmed.

If an authentication query record 250 that matches the first access ticket and the second access ticket is recorded, it is determined that the user ID is unmatched. When such an authentication inquiry record 250 is not recorded and it is determined that the user ID does not match (“NO” in step S8-1), the control unit 21 of the integrated monitoring server 20 transmits a login screen. Processing is executed (step S8-2). Specifically, the user authentication unit 214 of the control unit 21 transmits the login screen data to the mobile phone terminal 30 again. Thereby, the accessor can input the user ID and the second access ticket again.

  On the other hand, when it is determined that the user ID is unmatched by detecting the authentication query record 250 in which only the user ID does not match and the first access ticket and the second access ticket match (in the case of “YES” in step S8-1) ) The control unit 21 of the integrated monitoring server 20 executes an addition process of “1” for the number of unmatches (step S8-3). Specifically, the user authentication unit 214 of the control unit 21 adds “1” to the number of unmatches recorded in the memory.

  Next, the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether or not the number of unmatches has exceeded the first reference value (step S8-4). Specifically, the user authentication means 214 of the control unit 21 compares the number of unmatches recorded in the memory with the first reference value.

  When the number of unmatches is equal to or less than the first reference value (in the case of “NO” in Step S8-4), the control unit 21 of the integrated monitoring server 20 executes a login screen transmission process (Step S8-2).

  On the other hand, when the number of unmatches exceeds the first reference value (in the case of “YES” in step S8-4), the control unit 21 of the integrated monitoring server 20 determines whether the number of unmatches exceeds the second reference value. The determination process about whether or not is executed (step S8-5). Specifically, the user authentication unit 214 of the control unit 21 compares the number of unmatches recorded in the memory with the second reference value.

  When the number of unmatches does not exceed the second reference value (in the case of “NO” in step S8-5), the control unit 21 of the integrated monitoring server 20 executes this access ticket invalidation process (step S8-6). ). Specifically, the user authentication means 214 of the control unit 21 records an invalid flag in the authentication inquiry record 250 in which the matched first access ticket and second access ticket are registered. Also in this case, the control unit 21 of the integrated monitoring server 20 executes a login screen transmission process (step S8-2).

  On the other hand, when the number of unmatches exceeds the second reference value (in the case of “YES” in step S8-5), the control unit 21 of the integrated monitoring server 20 executes the invalidation process for all the access tickets of this person in charge. (Step S8-7). Specifically, the user authentication means 214 of the control unit 21 records the invalid flag in all authentication inquiry records 250 in which the user IDs that have become user ID unmatched are recorded.

(Deadline management process)
Next, the term management process will be described with reference to FIG. This process is repeatedly executed for each authentication inquiry record 250 recorded in the authentication inquiry data storage unit 25.

  Here, the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether or not 24 hours (access ticket holding reference time) have elapsed from the failure occurrence time (step S9-1). Specifically, the access ticket management unit 213 of the control unit 21 compares the failure occurrence time recorded in the authentication inquiry record 250 with the current time, and determines whether 24 hours have passed.

When the current time has passed 24 hours from the failure occurrence time (in the case of “YES” in step S9-1), the control unit 21 of the integrated monitoring server 20 executes an invalidation process for the authentication query record (step S9-1). S9-2). Specifically, the access ticket management unit 213 of the control unit 21 records an invalid flag in the authentication query record 250. On the other hand, when 24 hours have not elapsed (in the case of “NO” in step S9-1), the authentication query record 250 is maintained as it is.

According to the failure information providing system of the present embodiment, the following effects can be obtained.
-In this embodiment, the control part 21 of the integrated monitoring server 20 performs an alert monitoring process (step S1-1). When the failure message from the monitoring target device 10 is received, the control unit 21 of the integrated monitoring server 20 specifies a report group (step S2-1) and searches for a report management record of this report group (step S2-2). ). When the report management record 240 is not registered (in the case of “NO” in step S2-3), the control unit 21 of the integrated monitoring server 20 executes a new registration process of the report management record (step S2-4). Thereby, when a new failure occurs, the person in charge can be notified of the failure.

  Furthermore, when the notification management record 240 has already been registered (“YES” in step S2-3) and it is determined that it has not been recovered (“NO” in step S2-5), the control unit of the integrated monitoring server 20 21 executes an additional recording process (step S2-6). Thereby, a series of failures can be managed together. Therefore, even if a new failure occurs, if a notification is made to a notification group that deals with this failure, a new notification will not be made, and duplicate notifications will be suppressed to reduce system load. be able to. In addition, since the person in charge is not individually notified when a series of failures occur continuously, the complexity of confirmation can be reduced.

  -In this embodiment, the control part 21 of the integrated monitoring server 20 performs the determination process about whether it is the first report (step S3-1). When it determines with it being the first report (in the case of "YES" in step S3-1), the control part 21 of the integrated monitoring server 20 performs the setting process of the 1st report destination as a report person (step S3-2). . On the other hand, when it is determined that it is not the first notification (in the case of “NO” in step S3-1), the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether the number of notifications is less than the end reference number ( Step S3-3). When the number of notifications is less than the end reference number (in the case of “YES” in step S3-3), the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether there is a next-order notification destination (step). S3-4). When there is a registration of the next-order report destination (in the case of “YES” in step S3-4), the control unit 21 of the integrated monitoring server 20 executes a process for adding the next-order report destination (step S3-5). . As a result, it is possible to sequentially report according to the priority order of the person in charge.

  And when it has recovered or confirmed (in the case of “YES” in step S1-6), the control unit 21 of the integrated monitoring server 20 ends the notification management process. Thereby, the report more than necessary can be suppressed.

  On the other hand, when the number of notifications is equal to or greater than the end reference number (in the case of “NO” in step S3-3), the control unit 21 of the integrated monitoring server 20 executes notification processing for the system operator (step S3-6). ). As a result, when the person in charge does not respond, it is possible to prompt the system operator to respond quickly.

In the present embodiment, when there is no notification (in the case of “NO” in step S4-1), the control unit 21 of the integrated monitoring server 20 generates first and second access tickets (step S4-2), An authentication inquiry record is registered (step S4-3). And the control part 21 of the integrated monitoring server 20 produces | generates URL which used the 1st access ticket as an argument (step S4-4), and produces | generates the report mail with respect to a person in charge (step S4-5). Specifically, the notification management unit 211 of the control unit 21 generates an email in which the failure content recorded in the notification management record 240, the second access ticket, and the generated URL are recorded. Thereby, the person in charge can access the integrated monitoring server 20 using the URL added to the notification mail.

  When there is an access using the URL added to the notification mail and the user ID and the second access ticket are acquired, the control unit 21 of the integrated monitoring server 20 executes an access ticket verification process (step S5-7). ). If a valid authentication query record 250 can be extracted (in the case of “YES” in step S6-1), the control unit 21 of the integrated monitoring server 20 executes failure information provision processing (step S6-7). . In this case, since the user authentication is performed using the first and second access tickets and the user ID, security can be ensured. On the other hand, since the first access ticket is added as an argument of the URL, it is possible to reduce the input burden for the person in charge.

  In the present embodiment, when the report has already been made (in the case of “YES” in step S4-1), the control unit 21 of the integrated monitoring server 20 executes a process for generating a report mail with the failure information added (step S4). -6). Specifically, the notification management unit 211 of the control unit 21 generates an e-mail in which only the failure content recorded in the notification management record 240 is recorded. In this case, the second access ticket and URL are not included in the e-mail. Thereby, when retransmitting the notification mail, by eliminating the information for accessing the integrated monitoring server 20, it is possible to reduce the chance of information leakage and improve the security.

  -In this embodiment, the control part 21 of the integrated monitoring server 20 performs the search process of the other fault information to which this user belongs (step S6-4). When other failure information is recorded (in the case of “YES” in step S6-5), the control unit 21 of the integrated monitoring server 20 executes a link generation process to other failure information (step S6-6). ). If the session is continued and the user has logged in ("YES" in step S7-2), the control unit 21 of the integrated monitoring server 20 executes another failure information acquisition process (step S7-). 4). Thereby, the person in charge can efficiently acquire other failure information using this link. Further, in this case, even when another access ticket is set for other failure information, the failure information can be continuously acquired based on the previous authentication. .

  In the present embodiment, when a valid authentication query record 250 cannot be extracted (in the case of “NO” in step S6-1), the control unit 21 of the integrated monitoring server 20 executes an access denial process (step S6). -2). In this case, the control unit 21 of the integrated monitoring server 20 executes a determination process as to whether or not the user ID is unmatched (step S8-1). When it is determined that the user ID is unmatched (in the case of “YES” in step S8-1), the control unit 21 of the integrated monitoring server 20 performs an addition process of “1” for the number of unmatches (step S8-3). ). If the number of unmatches exceeds the first reference value (“YES” in step S8-4) and does not exceed the second reference value (“NO” in step S8-5), the integrated monitoring server 20 The control unit 21 executes this access ticket invalidation process (step S8-6). If the user ID is mistaken many times, there is a possibility that a third party other than the person in charge is operating the mobile phone terminal 30. In this case, provision of this failure information can be refused.

  On the other hand, when the number of unmatches exceeds the second reference value (in the case of “YES” in step S8-5), the control unit 21 of the integrated monitoring server 20 executes the invalidation process for all the access tickets of this person in charge. (Step S8-7). In the case of repeatedly inputting the user ID, there is a possibility that an access ticket for another notification mail received at the mobile phone terminal 30 may be used, so that such a possibility can be avoided.

  -In this embodiment, the control part 21 of the integrated monitoring server 20 performs a term management process. If the access ticket is made valid for a long period of time, the possibility of the access ticket leaking increases. Thus, security can be ensured by invalidating the access ticket.

Moreover, you may change the said embodiment as follows.
In the above embodiment, the mobile phone terminal 30 is used as the user terminal. However, the mobile phone terminal is limited to the mobile phone terminal as long as the person in charge can communicate with the integrated monitoring server 20. is not. For example, a PHS (Personal Handy-phone System), a mobile computer terminal, or the like can be used.

  In the above embodiment, the report destination management record 230 recorded in the report destination management data storage unit 23 is configured to include data related to the report group identifier, the first report destination, the second report destination, and the third report destination. . If the number of notifications is equal to or greater than the end reference number (here, 3 times) (in the case of “NO” in step S3-3), the control unit 21 of the integrated monitoring server 20 executes notification processing for the system operator. (Step S3-6). Here, the priority number and the end reference number of the report destination are not limited to this.

  In the above embodiment, when a failure occurs, the monitoring target device 10 issues an alert to the integrated monitoring server 20 via the network. In addition to this, these monitoring target devices 10 periodically perform an operation state confirmation process, and when the confirmation process is completed, the monitoring target device 10 may transmit the completion message to the integrated monitoring server 20. . Specifically, the monitoring target device 10 periodically performs an operation check, and transmits an operation check end message to the integrated monitoring server 20. This end message includes device specifying information. When the integrated monitoring server 20 does not regularly receive an end message from the monitored device 10, the integrated monitoring server 20 determines that a failure has occurred at the time when the end message was scheduled to be received. Thereby, the operation confirmation of the monitoring object apparatus 10 can be performed.

  In the above embodiment, the monitoring target device 10 monitors the occurrence of a failure in the mainframe and various business system servers. The monitoring target device 10 is not limited to these, and may be any device that can monitor a failure occurrence via a network. For example, a common monitoring device that monitors a network, a web, a job, or the like can be used as the monitoring target device 10.

The system schematic of embodiment of this invention. It is explanatory drawing of the data recorded on each data storage part, Comprising: (a) is a failure classification management data storage part, (b) is a report destination management data storage part, (c) is a report management data storage part, (d ) Is an explanatory diagram of data recorded in the authentication inquiry data storage unit. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the display screen of the mobile telephone terminal of this embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Monitoring object apparatus, 20 ... Integrated monitoring server, 21 ... Control part, 211 ... Report management means, 212 ... Access ticket registration means, 213 ... Access ticket management means, 214 ... User authentication means, 215 ... Fault information provision means, 22 ... Failure type management data storage unit, 23 ... Report destination management data storage unit, 24 ... Report management data storage unit, 25 ... Authentication inquiry data storage unit, 30 ... Mobile phone terminal.

Claims (7)

A report destination information storage means in which data relating to the user identifier and contact information of the person in charge belonging to the group performing the report in response to the failure message is recorded;
Fault information storage means for recording fault information in which a report identifier and a fault message are associated with each other;
Authentication information storage means for recording the first and second access codes for each user identifier and report identifier;
A fault information providing system comprising a control means for communicating with a user terminal of a person in charge,
The control means is
When acquiring a failure message from the monitoring target device, a means for assigning a notification identifier and registering in the failure information storage means;
Means for identifying a person in charge belonging to the group corresponding to the failure message using the report destination information storage means;
Means for generating first and second access codes for each person making a report;
Means for registering the first and second access codes in the authentication information storage means for each user identifier and report identifier of a person who makes the report;
The person in charge uses a notification mail displaying the URL obtained by adding the first access code to the address for accessing the failure information stored in the failure information storage means and the second access code. Means for transmitting to the user terminal;
When there is access to the URL from the user terminal, an authentication information input screen for the user identifier and the second access code is transmitted,
Login is permitted when the first access code of the accessed URL, the user identifier obtained through the authentication information input screen, and the second access code are registered in the authentication information storage means Means for transmitting a reference screen for the failure information recorded in the failure information storage means to the user terminal ;
Measure the elapsed time since sending the notification email,
If the response to the failure cannot be detected even after the response reference time has passed, the other person in charge belonging to the group is identified using the report destination information storage means,
To the person in charge who has already sent the report email, send a report email that does not include the URL and the second access code,
For the person in charge who newly sends a notification mail, the first and second access codes are newly generated and registered in the authentication information storage means, and the notification mail including the URL and the second access code is also included. A failure information providing system comprising: means for transmitting the message. The control means is
When registering the failure information in the failure information storage means, record the failure occurrence time when the failure message was acquired for each access code,
The failure information providing system according to claim 1, further comprising means for invalidating an access code associated with the failure message when a code holding reference time has elapsed from the failure occurrence time. The control means is
In the case of sending a notification mail, using the authentication information storage means, search for a failure about another group to which this person in charge belongs,
If another failure is registered, a link icon for outputting this failure information is added to the reference screen,
In case of receiving an access by using the link icon, as already provided that the login has been performed, according to claim 1 or 2, characterized in that transmits a reference picture for other disorders to the user terminal Fault information providing system described in 1. The apparatus according to any one of claims 1 to 3 , further comprising means for invalidating the first and second access codes when the user identifier input on the authentication information input screen cannot be collated. The fault information providing system according to any one of the above. If the user identifier input on the authentication information input screen cannot be verified, the authentication information storage means identifies the user identifier associated with the first and second access codes and associates it with this user identifier. failure information delivery system according to any one of claims 1-4, characterized in that further comprising means for disabling all access codes that are. A report destination information storage means in which data relating to the user identifier and contact information of the person in charge belonging to the group performing the report in response to the failure message is recorded;
Fault information storage means for recording fault information in which a report identifier and a fault message are associated with each other;
Authentication information storage means for recording the first and second access codes for each user identifier and report identifier;
A method for providing failure information using a failure information providing system comprising a control means for communicating with a user terminal of a person in charge,
The control means is
When acquiring a failure message from the monitoring target device, providing a notification identifier and registering it in the failure information storage means;
Identifying the person in charge belonging to the group corresponding to the failure message using the report destination information storage means;
Generating first and second access codes for each person making a report;
Registering the first and second access codes in the authentication information storage means for each user identifier and report identifier of a person in charge who makes the report;
The person in charge uses a notification mail displaying the URL obtained by adding the first access code to the address for accessing the failure information stored in the failure information storage means and the second access code. Sending to the user terminal,
When there is access to the URL from the user terminal, an authentication information input screen for the user identifier and the second access code is transmitted,
Login is permitted when the first access code of the accessed URL, the user identifier obtained through the authentication information input screen, and the second access code are registered in the authentication information storage means And transmitting a reference screen for failure information recorded in the failure information storage means to the user terminal ;
Measure the elapsed time since sending the notification email,
If the response to the failure cannot be detected even after the response reference time has passed, the other person in charge belonging to the group is identified using the report destination information storage means,
To the person in charge who has already sent the report email, send a report email that does not include the URL and the second access code,
For the person in charge who newly sends a notification mail, the first and second access codes are newly generated and registered in the authentication information storage means, and the notification mail including the URL and the second access code is also included. A failure information providing method comprising: performing a step of transmitting a message. A report destination information storage means in which data relating to the user identifier and contact information of the person in charge belonging to the group performing the report in response to the failure message is recorded;
Fault information storage means for recording fault information in which a report identifier and a fault message are associated with each other;
Authentication information storage means for recording the first and second access codes for each user identifier and report identifier;
A program for providing fault information using a fault information providing system having a control means for communicating with a user terminal of a person in charge,
The control means;
If a failure message is acquired from the monitored device, a means for assigning a report identifier and registering in the failure information storage means,
Means for identifying a person in charge belonging to the group corresponding to the failure message using the report destination information storage means;
Means for generating first and second access codes for each person in charge of reporting;
Means for registering the first and second access codes in the authentication information storage means for each user identifier and report identifier of a person who makes the report;
The person in charge uses a notification mail displaying the URL obtained by adding the first access code to the address for accessing the failure information stored in the failure information storage means and the second access code. Means for transmitting to the user terminal,
When there is access to the URL from the user terminal, an authentication information input screen for the user identifier and the second access code is transmitted,
Login is permitted when the first access code of the accessed URL, the user identifier obtained through the authentication information input screen, and the second access code are registered in the authentication information storage means Means for transmitting a reference screen for failure information recorded in the failure information storage means to the user terminal ;
Measure the elapsed time since sending the notification email,
If the response to the failure cannot be detected even after the response reference time has passed, the other person in charge belonging to the group is identified using the report destination information storage means,
To the person in charge who has already sent the report email, send a report email that does not include the URL and the second access code,
For the person in charge who newly sends a notification mail, the first and second access codes are newly generated and registered in the authentication information storage means, and the notification mail including the URL and the second access code is also included. A failure information providing program that functions as a means for transmitting .

Images