JP4673941B1 - Screen design support system for failure handling - Google Patents

Abstract

Provided is a technology for assisting in designing various correspondence screens at the time of failure occurrence and link relations between the screens very easily.
A design screen is generated based on a design-time screen skeleton provided with at least one of a display item setting field and an input item setting field required for a failure handling screen, and is transmitted to a design terminal. When the setting data from the terminal 14 to the design screen is transmitted, the screen editing unit 34 that is stored in the component management table 20, the property table 21, and the connector table 22 in association with each setting field of the screen skeleton is designed. Generates a symbol 303 for each screen, sends a screen flow edit screen 300 on which these symbols are displayed to the design terminal 14 to prompt the user to set a link relationship between the screens, and links between the screens transmitted from the design terminal 14 A failure handling screen design support system including a flow editing unit 35 that stores relation setting data in a flow management table 23, a flow component table 24, and a transition table 25.
[Selection] Figure 4

Description

  The present invention relates to a failure handling screen design support system, and in particular, when a failure message is issued from a monitoring device of a computer system, a plurality of failure handling screens displayed on a terminal operated by an operator, and between each screen The present invention relates to an assistive technology that enables a transition flow to be designed very easily.

When a system failure occurs, an alert notifying the occurrence of the failure is usually displayed on the operator's operation terminal. In response to this, the operator pulls out a corresponding procedure document linked to the fault message code displayed on the screen, and issues a command designated there to the monitored system via the monitoring device, Such as making a call to the person in charge.
However, as the size of monitored systems increases, the amount of work to be performed by the operator in the event of a failure becomes more complex and the volume of procedure manuals to be referenced is increasing. I was approaching.

As a system for improving such a situation, a system monitoring work support system described in Patent Document 1 has already been proposed.
In the case of this system, an operation support screen corresponding to the content of the error message is automatically generated and displayed on the display when a failure occurs. This operation support screen describes the processing procedure to be executed by the operator, the list of notification destinations, and the related document list. Clicking the title of the manual listed in the related document list opens the document display screen. Since the corresponding manual is displayed, the operator can take the necessary steps efficiently by acting in accordance with the procedure described on the screen, and the trouble of opening most procedure manuals as before. Will be released.
JP 2005-276042 A JP-A-5-108324 JP 2002-229765 A

However, in the case of the support system of Patent Document 1, a number of corresponding screens are created in advance according to the type of failure message, the characteristics of the monitoring target system, and the link relationship between the screens is formed. A so-called “external design” is required, which places a heavy burden on the designer. The person in charge who is familiar with the system failure should design each screen and the link relationship between the screens. However, the expert of the system failure is not necessarily familiar with coding. In many cases, each screen was designed in cooperation with other experts, which caused cost increase.
Also, even if the person in charge of system failure is familiar with coding, creating a wide variety of screens to deal with complex events and link relationships between screens from scratch is a laborious task. It was.

  Note that there are technologies described in Patent Documents 2 and 3 as prior arts related to efficient screen generation. That is, Patent Document 2 discloses a technique for realizing efficient screen creation by automatically generating a screen by applying field information to a skeleton of a screen layout. Patent Document 3 discloses a technique for generating a screen without programming by applying screen definition information to a screen template.

Therefore, by using the techniques of Patent Documents 2 and 3, it is possible to automatically generate a target screen without coding, but the screen design still requires a high level of expertise regarding the system and business content. Is done.
For example, in the case of Patent Document 2, as a preparatory work for automatically generating the screen of FIG. 8, the designer first created an update file of “URIAGE” by referring to two files “TOKUI” and “SHOUHIN”. Later (FIG. 5), it is necessary to finely set the selection of display fields, the display order thereof, the designation of the header portion, etc. through the dialog screen of FIG. For this reason, designers are required to have deep knowledge of various database configurations and business processes.
Further, as shown in FIG. 2, the template of Patent Document 3 is merely a frame in which the presence of a plurality of parts (controls) constituting the screen is displayed. It is required to create the complex screen definition file shown in FIG. 3 after recognizing the indicated control names and their contents and the property names and their contents shown in Table 2. In short, according to the screen display device of Patent Document 3, even if the designer is freed from the coding work, the work is considerably advanced and complicated in order to generate a specific screen.

  The present invention has been devised to solve such a problem of the present situation, and is a technology for assisting in designing various correspondence screens when a failure occurs and link relations between the correspondence screens very easily. The purpose is to provide.

In order to achieve the above object, the failure handling screen design support system according to claim 1 sets a plurality of display items to be provided on a failure handling screen that is sequentially displayed on a failure handling terminal operated by an operator when a failure occurs. Stores multiple types of design screen skeletons to generate multiple types of design screens with columns and multiple types of runtime screen skeletons with display items corresponding to each setting field of each design screen When a display request for a design screen related to a specific type of failure handling screen is transmitted from the screen skeleton storage means to be stored and the design terminal operated by the designer, the design time screen skeleton related to the failure handling screen is stored in advance. by executing the included program, among the setting column of the plurality of display items, design screen having at least a portion of the setting field corresponding to the display request Design screen generation means for generating, means for sending the design screen to the design terminal and prompting the setting for each setting field, and setting data for each setting field on the design screen transmitted from the design terminal, A failure handling screen generating means for generating a failure handling screen by applying it to a corresponding display item of a runtime screen skeleton corresponding to the design screen , a means for sending the failure handling screen to the design terminal, and the design terminal When a registration request is sent for a designed failure response screen from the above, the setting data for each setting field on the design screen sent from the design terminal is displayed as the screen component ID and each unique And a means for storing in a predetermined setting data storage means in association with a setting item ID for specifying the setting field.

Failure corresponding image design support system according to claim 2, a system according to claim 1, further designed screen generated based on the screen skeleton for at the design setting of the display item field a has a plurality of blocks having respectively provided, and, at least some of the blocks are a check box for controlling the display / non-display, the screen skeleton is also a time the execution, this design A plurality of blocks each having display items corresponding to setting fields included in each block of the screen, and the failure handling screen generation means is a setting indicating that this check box is unchecked from the design terminal When data is transmitted, a failure response screen is generated in which the block is hidden according to the setting data. That.

The failure handling screen design support system according to claim 3 is the system according to claim 1 or 2, and further refers to the setting data storage means and is designed to deal with the fault that has been associated with the screen component ID. and the screen symbol generation means for generating a symbol on the screen, a plurality of screen flow editing screen symbol appears transmitted to the design terminal, and means for prompting the setting of the screen transition flow between each failure corresponds screen, the design terminal From the setting data that identifies multiple failure handling screens that make up the screen transition flow, the setting data that identifies the failure handling screen that is displayed first in the screen transition flow, and the failure that is the transition destination of each failure handling screen Means for storing the setting data in association with a unique flow ID in a predetermined storage means when setting data for specifying the corresponding screen is transmitted ; The flow edit screen includes a screen part display field in which a plurality of screen symbols are displayed in a list and a main screen, and any screen symbol is arranged on the design terminal from the screen part display field to the main screen. And setting data for specifying a plurality of failure handling screens constituting the screen transition flow by connecting at least one connector provided for each screen symbol to other screen symbols on the main screen. It is characterized in that setting data for specifying a failure handling screen displayed first in the transition flow and setting data for specifying a failure handling screen as a transition destination of each failure handling screen are generated.

  The failure handling screen design support system according to claim 4 is the system according to claim 3, and the design screen generated based on the design time screen skeleton further includes an option setting field. The screen symbol generating means generates a screen symbol having a connector corresponding to the number of options when option setting data is transmitted from the design terminal.

Failure corresponding image design support system according to claim 5, a system according to claim 1, further the procedures management table for storing a plurality of instructions name to be referenced in the event of a failure In the design screen generated based on the above design time screen skeleton, the setting column for specifying the procedure manual to be displayed on the failure handling screen and the procedure manual name stored in the procedure manual management table are called. button is provided for, the design screen generation unit, when the button is pressed in the design screen, a list screen described several procedures names stored in the instructions management table and transmits to the design terminal, when a particular procedures names in this list screen is selected, the procedure title generates a design screen inserted in the setting column, sending a child to design terminal It is characterized in.

A failure handling screen design support system according to claim 6 is the system according to claims 1 to 5, further comprising a command management table for storing a plurality of command names to be executed when a failure occurs, The design screen generated based on the design time screen skeleton has a setting field for designating a command to be displayed on the failure handling screen and a button for calling a command name stored in the command management table. provided, the design screen generation unit, when the button is pressed in the design screen, and transmits the list screen described multiple command name stored in the command management table to the design terminal together, when a specific command name in this list screen is selected, it generates design screen this command name is inserted in the setting column, set It is characterized in that to the terminal.

A failure handling screen design support system according to claim 7 is the system according to claims 1 to 6, and further, a reserved word management table for registering a plurality of reserved words whose unique meanings are defined in advance The design screen generated based on the design screen skeleton is provided with a button for calling the reserved word for a specific setting field, and the design screen generation means is provided on the design screen. When the button is pressed, a list screen of reserved words stored in the reserved word management table is transmitted to the design terminal, and when a specific reserved word is selected on the list screen, the reserved word is displayed. Generates a design screen inserted in the setting field and transmits it to the design terminal.

  According to the failure handling screen design support system described in claim 1, the failure handling screen is automatically entered by simply inputting an arbitrary setting value for a design screen having a setting field for various display items that the failure handling screen should have. Because it is generated, there is no need for design (external design) on how to design each screen, and even a general operator who does not have expertise in system structure or coding can easily handle failure screens. Can be designed.

In the failure handling screen design support system according to claim 2, the display / non-display of the block on the failure handling screen can be switched depending on whether or not the check box displayed in each block of the design screen is checked. Therefore, by forming many blocks with different setting fields from each other, it is possible to respond flexibly to the designer's various purposes and uses, but for blocks that the designer thinks unnecessary, By making it non-displayed, the visibility of the failure handling screen can be improved.

  According to the failure handling screen design support system described in claim 3, between screens in a GUI (Graphical User Interface) environment in which a screen symbol connector is connected to another screen symbol on the screen flow editing screen. Since link-related setting data is generated, the designer can design a transition flow between screens without hesitation.

  In the failure handling screen design support system according to claim 4, there is provided a mechanism in which a connector corresponding to the number of options is formed in a screen symbol by setting options in an option setting field provided on the design screen. Therefore, the designer can easily design a screen transition flow that branches according to the options.

  According to the failure handling screen design support system described in claim 5, selection of a procedure book name that becomes a failure handling standard and input to the design screen can be realized very easily, thereby further reducing the burden on the designer. It becomes possible.

  According to the failure support screen design support system described in claim 6, selection of a command name, which is an important measure for failure recovery, and input to the design screen can be realized very easily, thereby further reducing the burden on the designer. It becomes possible.

  According to the failure handling screen design support system described in claim 7, it becomes extremely easy to input a reserved word on the design screen, and thus the burden on the designer can be further reduced.

FIG. 1 is an overall configuration diagram of a system according to the present invention, which includes an editing device 11, a database group 12, and a failure handling device 28.
The editing device 11 includes a computer having an OS and a dedicated application program, and is connected to a terminal (hereinafter, “design terminal 14”) operated by a designer via a communication network.

The database group 12 is provided in the hard disk of the database server, and includes a procedure manual management table 15, a command management table 16, a reserved word management table 26, a screen skeleton storage unit 13, a screen skeleton management table 405, Customer system table 17, carving condition table 19, contact table 18, contact block table 400, parts management table 20, property table 21, connector table 22, flow management table 23, and flow configuration A component table 24 and a transition table 25 are provided.
The database group 12 is connected to the editing device 11 and the failure handling device 28 via a communication network.

The screen skeleton storage unit 13 will be described in detail later. (1) Procedure manual execution screen skeleton, (2) Command execution screen skeleton, (3) Fault report screen skeleton, (4) Contact confirmation screen skeleton , (5) Mail transmission screen skeleton and (6) General-purpose instruction screen skeleton are stored.
Each screen skeleton is specifically composed of a JSP file, and a design time screen skeleton and a runtime screen skeleton are prepared for each type of failure handling screen.
Here, "JSP" is an abbreviation for Java (registered trademark) Server Pages. A Java program is embedded in an HTML file, the program is executed in response to a client request, and an HTML file as a processing result is displayed. It means the technology to send to the client.
The screen skeleton management table 405 defines the correspondence between each screen skeleton ID and the JSP file.

The failure handling device 28 is composed of a computer, and the CPU operates in accordance with the OS and a dedicated application program, and executes various processes as a screen transition flow specifying unit, a screen generating unit, and a screen transmitting unit as described later.
A plurality of monitoring target systems 30 are connected to the failure handling device 28 via a communication network, and each monitoring target server 31 constituting the monitoring target system 30 detects a failure and sends a message to the failure handling device. A monitoring program to send to 28 is installed.
Further, a terminal operated by an operator (hereinafter referred to as “fault handling terminal 32”) is connected to the fault handling apparatus 28 via a communication network.
Two log files of a list log 401 and a report log 402 are provided in the failure handling apparatus 28.

The failure handling device 28 and the database group 12 constitute a failure handling support system.
That is, the failure handling apparatus 28 that has received the failure message from each monitored server 31 refers to the isolation condition stored in the isolation condition table 19 and identifies the flow ID applied to the failure message.
In the isolation condition table 19, as shown in FIG. 2, the isolation condition ID, isolation name, valid / invalid flag, system ID, priority, flow ID, contact block ID, message ID, source process ID, message status , Failure category, message body, time zone, valid period data items are set.

  Next, the failure handling device 28 refers to the flow management table 23 and the component management table 20 to identify the first failure handling screen, and then refers to the screen skeleton management table 405 to execute the execution time that is the basis of the failure handling screen. Specify the screen skeleton file name. Next, the failure handling apparatus 28 obtains the corresponding runtime screen skeleton from the screen skeleton storage unit 13, and applies the set value stored in the property table 21 to this to generate a failure handling screen (HTML file). The data is transmitted to the failure handling terminal 32 (the specific configuration of each table will be described later).

The operator executes necessary processing according to the description on this screen and inputs the result to the screen.
Upon receiving this, the failure handling device 28 refers to the flow component table 24, the transition table 25, the component management table 20, and the connector table 22 and identifies the next failure handling screen that matches the above execution result. Referring to the screen skeleton management table 405, the file name of the runtime screen skeleton that is the basis of the failure handling screen is specified. Next, the failure handling apparatus 28 obtains the corresponding screen skeleton from the screen skeleton storage unit 13, and applies the set value stored in the property table 21 to this to generate the next failure handling screen, and the failure handling terminal 32 (The specific configuration of each table will be described later).

Thereafter, by repeating the above processing, failure response screens are successively transmitted from the failure response device 28 to the failure response terminal 32, and the operator can be guided correctly.
FIG. 3 is a flowchart showing an example of a failure handling screen displayed on the screen of the failure handling terminal 32. A series of failure handling processes are executed by branching a plurality of different types of screens while branching. It shows how it works.

  The data entered by the operator on the various failure response screens are two in the failure response device 28. Since it is automatically stored in the recordable log file (list log file 401, report log file 402), a history of failure handling can be surely left, and can be used when a report is created.

The editing device 11 and the database group 12 constitute a failure handling screen design support system.
That is, the editing device 11 includes a screen editing unit 34, a flow editing unit 35, and a segmentation condition editing unit 403, as shown in FIG. The screen editing unit 34, the flow editing unit 35, and the separation condition editing unit 403 are realized by the CPU of the computer executing necessary processes according to the OS and a dedicated application program, respectively.

Upon receiving a request for creating a new screen from the design terminal 14, the screen editing unit 34 refers to the screen skeleton management table 405 and identifies the file name of the screen skeleton corresponding to the failure handling screen specified by the designer. Then, the corresponding design time screen skeleton is taken out from the screen skeleton storage unit 13, the program coded in the file is executed to generate a design screen (HTML file), and transmitted to the design terminal 14.
On the other hand, the designer performs various inputs and selections on the design screen displayed on the web browser of the design terminal 14. At this time, the procedure manual management table 15, the command management table 16, the reserved word management table 26, the customer system table 17, the contact table 18 and the like are referred to as appropriate. The designer who has completed input and selection on the design screen requests the screen editing unit 34 to register the customized screen.
Upon receiving this, the screen editing unit 34 updates the parts management table 20, the property table 21, and the connector table 22 based on the input data and selection data transmitted from the design terminal 14, and completes the registration of the new screen.
In the following, a specific example of each failure handling screen and a specific example of a design screen for setting it will be described.

FIG. 5 shows an example of the procedure manual execution screen 40, which is composed of four blocks: a procedure manual selection block 41, a result block 42, a free memo block 43, and a result transcription block 44.
Each block is an instruction unit for the operator, and the procedure manual selection block 41 displays a list of procedure manual names to be referred to by the operator when a specific failure message is issued from the monitored system.
Since each procedure manual name has a link to the procedure manual file, when the operator clicks a specific procedure manual in the list, the corresponding procedure manual file (PDF, etc.) is downloaded and displayed in a separate window. .
On the other hand, the operator executes necessary processing according to each procedure manual.

The result block 42 is provided with a selection field for a procedure manual execution result, and options of “procedure document execution status: normal end”, “procedure manual execution status: abnormal end”, and “procedure manual execution status: other” are provided. It is enumerated.
On the other hand, the operator selects and inputs the result processed in accordance with the procedure manual by checking a radio button of any option.

The free memo block 43 includes a special note entry field (for list) 45 and a special note entry field (for report) 46. If you have noticed something, you can enter a free word in this entry field. You can leave a note at
The data entered in the special note entry field (for list) 45 is recorded in a list log file 401 provided in the failure handling apparatus 28. The data input in the special note entry field (for report) 46 is recorded in a report log file 402 provided in the failure handling apparatus 28.

The result transcription block 44 is provided with a command execution result transcription field 47 for transcribing the execution result when a specific command is executed as an instruction item in the procedure manual.
If applicable, the operator transcribes a necessary message from the command execution result display screen to the command execution result transcription field 47 by copy and paste.
The data entered in the command execution result transcription field 47 is recorded in a list log file 401 provided in the failure handling apparatus 28.

The operator browses the necessary procedure manual according to the procedure manual execution screen 40 described above, executes the processing described therein, then finishes selecting the execution result, inputting the free memo, and posting the command execution result. Press the “Next” button 48.
As a result, the next failure handling screen is displayed on the display of the failure handling terminal 32 according to the procedure manual execution result selected and input by the operator.

When creating the procedure manual execution screen 40, the designer accesses the screen editing unit 34 from the design terminal 14 and requests a procedure manual execution screen creation service.
Upon receiving this, the screen editing unit 34 takes out the design time screen skeleton of the procedure manual execution screen from the screen skeleton storage unit 13, generates a design screen, and transmits it to the design terminal 14.

  6 and 7 show a design screen 50 for a procedure manual execution screen displayed on the web browser of the design terminal 14, and include a bibliographic item input field 51, a title input field 52, and a navigation text input field. 53, a procedure manual selection block 54, a result block 55, a free memo block 56, and a result transcription block 57.

On the other hand, the designer first inputs the ID and system name of the system to which the screen is applied, the component ID of the screen, the screen component name, and the like in the bibliographic item input field 51.
In addition, the designer inputs a key into the title input field 52 by entering “procedure manual execution” and the navigation explanation text input field 53 by a character string “execute the relevant procedure manual”.

Next, the designer shifts to an editing operation of the procedure manual selection block 54. First, the block name is entered in the block name setting field 58. “Procedure selection” is displayed by default, but the designer can change it to another name as necessary.
Note that it is originally possible to select the display / non-display of the block by unchecking the check box 59 provided on the right side of the block name setting field. Since it is grayed out with 59 checked, the designer cannot hide it. This means that the procedure manual selection block 41 in the procedure manual execution screen 40 is an indispensable display item.

Next, the designer inputs “Select a procedure manual to be executed and execute the procedure manual” in the explanatory note setting field 60 of the procedure manual selection block 54.
At this time, when the designer clicks the “reserved word list” button 61, the screen editing unit 34 transmits the reserved word list screen registered in the reserved word management table 26 and displays it on another window (not shown). ).
In this reserved word list screen, each reserved word and the defined semantic content are listed. When the designer requests insertion by clicking a specific reserved word selection button, the screen editor 34 The design screen 50 for the procedure manual execution screen in which the reserved word is inserted into the explanatory note setting field 60 is transmitted and re-displayed on the Web browser of the design terminal 14.

Next, the designer sets the specification method of the procedure manual.
First, check the radio button of “Other procedure manuals can be specified” and check the “Specify from list” checkbox. In the procedure manual selection block 41 of the procedure manual execution screen 40, “Other than candidate” “Procedure Manual Selection” button 62 is displayed (see FIG. 5). When the operator clicks this button, the procedure manual list screen is activated, and the procedure manuals other than those listed in the procedure manual execution screen 40 can be displayed. It becomes.
If the “Manual input” check box is checked, a “procedure manual number” input field 63, a “procedure manual name” input field 64, and a “reference” button 65 are displayed in the procedure manual selection block 41 on the procedure manual execution screen 40. Is displayed. On the other hand, when the operator inputs the procedure manual number or the procedure manual name and clicks the “reference” button 65, the corresponding procedure manual is displayed on another window.

On the other hand, if the designer checks the radio button for “other than display target”, it may be restricted so that only the procedure manuals displayed in the procedure manual list on the procedure manual execution screen 40 can be referenced. it can. In this case, in the procedure manual selection block 41 of the procedure manual execution screen 40, a radio button of “Select from list”, “Select a procedure manual other than candidates” button 62, “Procedure manual number” input field 63, “Procedure manual name” "Input field 64 and" reference "button 65 disappear.
Note that it is generally difficult for an operator who is not a specialist for handling failures to select the optimal procedure from the list of procedures when a failure occurs. In other cases, “other procedure manuals can be specified” is selected only in exceptional cases.

Next, the designer adds a specific procedure manual to the designation field 66 to be displayed in advance.
That is, when the designer clicks the “add to list” button 67, a list screen of procedure manuals stored in the procedure manual management table 15 is transmitted from the screen editing unit 34 and displayed on another window (not shown). .
The procedure manual list screen lists a number of procedure manual names and their outlines, and when the designer requests insertion by clicking the selection button for a particular procedure manual, the screen editor 34 will display the relevant procedure. The design screen 50 for the procedure manual execution screen in which the book name is inserted in the designation field 66 to be displayed in advance is transmitted and redisplayed on the Web browser of the design terminal 14.

  Next, the designer shifts to an editing operation of the result block 55. First, a block name is entered in the block name setting field 58 as necessary. By default, “Result” is displayed. Since the result block gray / undisplayed check box 59 is also grayed out, the designer cannot hide it.

Since the character string “Please select the procedure manual execution result” is input by default in the description block setting field 68 of the result block, the designer corrects it if necessary.
Next, the designer inputs a key such as “procedure document execution status: normal end” as a specific option in the option description column 69, and then checks the check box to validate the option. Although three options are set in the figure, the designer can set more options as needed.

Each option has a history definition (for list) setting field 70 and a history definition (for reporting) setting field 71, and an arbitrary character string can be set here. The character string set here is not displayed on the procedure manual execution screen 40, but the character string related to the option selected by the operator is displayed in the list log file 401 and the report log file 402 of the failure handling apparatus 28. Each will be recorded.
In this way, the history definition (for list) and the history definition (for reporting) are recorded in separate log files, so if you want to make a polite wording for the reporting log, it is different from the list string. Expression (for example, “successfully completed”).

Next, the designer shifts to the editing operation of the free memo block 56. First, a block name is entered in the block name setting field 58 as necessary. By default, “Free Memo” is displayed.
Since the check box 59 for selecting whether to display / hide the free memo block 56 is activated, the designer can hide the block on the procedure manual execution screen 40 by removing the check. it can.

  Next, the designer sets necessary character strings in the list comment input field 72 and the report comment input field 73. By default, “Please enter if there are special notes (for list)” and “Enter if there are special notes (for reporting)” is set. There is no need to change it.

Finally, the designer shifts to the editing operation of the result posting block 57. First, a block name is entered in the block name setting field 58 as necessary. By default, “Result Posting” is displayed.
Since the check box 59 for selecting display / non-display of the result transfer block 57 is grayed out with a check mark, the designer cannot hide it.

  Next, the designer sets a necessary character string in the explanatory note input field 74 of the result transcription block 57. By default, “If the command execution is instructed in the procedure manual, please post the command execution result” is set.

When the designer clicks the “preview” button 75 after inputting the setting data, the input data is transmitted to the screen editing unit 34.
On the other hand, the screen editing unit 34 applies the transmitted input data to the screen skeleton for execution of the procedure manual execution screen to generate a preview screen of the procedure manual execution screen, and then returns it to the design terminal 14.
As a result, another window opens on the web browser of the design terminal 14, and a preview screen of the procedure manual execution screen being edited is displayed. As a result, the designer can check the completed image of the procedure manual execution screen 40 at any time.

When the designer clicks the “Register” button 76, data input by the designer is transmitted to the screen editing unit 34.
Upon receiving this, the screen editing unit 34 registers necessary data in the component management table 20, the property table 21, and the connector table 22.

FIG. 8 shows a configuration example of the component management table 20, which includes data items of system ID, screen component ID, screen skeleton ID, and screen component name.
The screen editing unit 34 registers the system ID, screen part ID, and screen part name entered in the bibliographic entry field 51 of the design screen 50 in the corresponding items, and the design time screen skeleton of the procedure manual execution screen. Record the ID in the screen skeleton ID field.

FIG. 9 shows an example of the configuration of the property table 21, which includes screen item ID, setting item ID, and setting value data items. The setting item ID means an identification code assigned to each setting item of the design time screen skeleton.
The screen editing unit 34 stores the input data and selection data transmitted from the design terminal 14 in the setting values of the corresponding items.

FIG. 10 shows a configuration example of the connector table 22, which includes screen item ID and connector ID data items.
The connector ID is an item for registering the options set on the screen skeleton. Since three options are set in the result block 55 in the design screen 50 for this procedure manual execution screen, the screen part of BU001 IDs 1 to 3 are assigned.

  The screen skeleton for runtime of the procedure manual execution screen has items corresponding to the setting items of the screen skeleton for design time, so the setting value of each setting item stored in the property table 21 is changed to the corresponding item. By applying, the procedure manual execution screen 40 is generated as described above.

FIG. 35 schematically shows the relationship between the design time screen skeleton α of the procedure manual execution screen and the runtime screen skeleton β of the same screen. The generation procedure of each screen based on this is organized here.
First, the screen editing unit 34 of the setting data editing device 11 generates a design screen 50 for the procedure manual execution screen based on the screen skeleton α for designing the procedure manual execution screen, and transmits it to the design terminal 14.

When a preview screen display request is transmitted from the design terminal 14, the screen editing unit 34 generates the preview screen γ by applying the design data input through the design screen 50 to the runtime screen skeleton β. To the design terminal 14.
When the setting data registration request is transmitted from the design terminal 14, the screen editing unit 34 converts the setting data input through the design screen 50 into the component management table 20, the property table 21, and the connection table 22 in the database group 12. To store.

On the other hand, when the failure handling screen is generated, the failure handling device 28 generates the procedure manual execution screen 40 by applying the design data for the procedure manual execution screen registered by the designer to the screen skeleton for runtime of the relevant screen. And transmitted to the failure handling terminal 32.
When the data input through the procedure manual execution screen 40 is transmitted from the failure handling terminal 32, the failure handling device 28 registers this in the list log 401 and the report log 402, respectively.

  In FIG. 35, the design-time screen skeleton α and the run-time screen skeleton β related to the procedure manual execution screen 40 have been described, but the same applies to the screen skeletons related to other failure handling screens.

FIG. 11 partially shows an example of the command execution screen 80, and includes a command confirmation block 81, a command execution block 82, a confirmation block 83, and the like. Although illustration is omitted, other screen configuration blocks such as a free memo block may be provided.
The command execution screen 80 serves to instruct the operator to issue a failure response command.

  The command confirmation block 81 describes the confirmation items before issuing the command, and the operator who performed the necessary confirmation according to the instruction checks the check box 84 of “execution 1”.

  In the command execution block 82, an “execution” button 85 is generated, and the “execution” button 85 is pre-associated with a command that seems to be effective in solving the failure, and the operator clicks this button. Thus, the corresponding command is automatically issued from the failure handling apparatus 28 to the target monitoring target system 30. However, when the “execution 1” check box 84 of the command confirmation block is not checked, the command is not issued.

In the command execution result image display field 86, an execution result image (sample) of the command issued this time is displayed for each result (success / failure) (not shown).
In response to this, the operator copies the actual command execution result displayed on the display of the failure handling terminal 32 to the command execution result record column 87 by copy and pace, and compares the results to execute the result of the current command execution. Can be determined accurately.

  In the confirmation block 83, “log transfer normal end” and “log transfer abnormal end (including no response)” are listed as options of the command execution result, and the operator can select either one based on the current command execution result. Check the option radio button.

The operator issues necessary commands according to the command execution screen 80 described above, selects the result, and clicks the “Next” button 48.
As a result, the next failure handling screen is displayed on the display of the failure handling terminal 32 in accordance with the command execution result selected and input by the operator.

When creating the command execution screen 80, the designer accesses the screen editing unit 34 from the design terminal 14 and requests a command execution screen creation service.
Upon receiving this, the screen editing unit 34 extracts the design time screen skeleton of the command execution screen from the screen skeleton storage unit 13, generates a design screen, and transmits it to the design terminal 14.

  12 and 13 show a part of the design screen 90 for the command execution screen displayed on the web browser of the design terminal 14. The bibliographic item input field, title input field, and navigation explanation input field have substantially the same configuration as that of the design screen 50 for the procedure manual execution screen shown in FIG. It is omitted.

FIG. 12 shows an editing screen of the command confirmation block 91. First, the designer inputs a block name in the block name setting field 58. “Command confirmation” is displayed by default, but the designer can change it to another name if necessary.
The check box 59 provided on the right side of the block name setting field 58 is grayed out with a check mark, and the designer cannot hide it.

  Next, the designer inputs “please confirm that the fault node name: [test05] has been input as a parameter” in the explanatory note setting field 92 of the command confirmation block 91. At this time, when the designer clicks the “reserved word list” button 61, the screen editing unit 34 transmits the reserved word list screen registered in the reserved word management table 26 and displays it on a separate window. The person can select and input an arbitrary reserved word.

Next, the designer defines the command to be executed. In other words, when the designer checks the “fixed designation” radio button 93 in the command definition column and also checks the “execution command 1” check box 94 and clicks the “designate from list” button 95, the screen editing is performed. The command list screen registered in the command management table 16 is transmitted from the unit 34 and displayed on another window (not shown).
In this command list screen, a number of command names and their functions are listed, and when the designer clicks a specific command selection button to request insertion, the command name is displayed as a command from the screen editor 34. The design screen 90 for the command execution screen inserted in the input field 99 is transmitted and redisplayed on the web browser of the design terminal 14.
Next, the designer inputs a parameter name and parameters necessary for issuing a command in the parameter setting field 96. A plurality of parameters can be set.

  When it is necessary to execute a plurality of commands, the designer checks the check box 94 after the execution command 2 and designates the execution command, sets the parameter name, and the parameter.

As described above, when the designer checks the “fixed designation” radio button 93, the command name cannot be selected in the command confirmation block 81 on the command execution screen 80 as shown in FIG. Displayed with status.
On the other hand, when the designer checks the radio button 97 for “selection designation” and lists specific commands in the command candidate designation column 98, a plurality of commands are displayed in the command confirmation block 81 on the command execution screen 80. Will be listed in a selectable state. In this case, the operator is required to select the most appropriate command according to the situation.

  Next, as shown in FIG. 13, the designer shifts to an editing operation of the command execution block 100. First, a block name is entered in the block name setting field 58 as necessary. By default, “Command Execution” is displayed. Since the check box 59 for selecting / displaying the command execution block is grayed out with a check mark, the designer cannot hide it.

Next, the designer inputs “please press the execution button” in the explanatory note setting field 101 of the block.
In addition, the designer can change the notation of the command execution button from the default “execution” to another notation in the label setting field 102 of the command execution button.
Further, the designer pastes a sample of the execution result of the command (success example and failure example) in the command execution result image setting field 103.

  Next, the designer shifts to an editing operation of the confirmation block 104. First, a block name is entered in the block name setting field 58 as necessary. By default, “Confirm” is displayed. The check box 59 for display / non-display selection of the command execution block is grayed out with a check mark, and the designer cannot hide it.

In the explanatory text setting field 105 of the confirmation block 104, a character string “Select a command execution result and press [Next]” is entered by default, so the designer corrects it if necessary. .
Next, the designer inputs a key such as “log transfer normal end” as a specific option in the option description column 106, and then checks the check box 107 to validate the option. Although two options are set in the figure, the designer can set more options as needed.

  For each option, two items, “for list” and “for report”, are prepared as history definition setting fields, and an arbitrary character string can be set here. The character string set here is not displayed on the command execution screen, but the character string related to the option selected by the operator is separately recorded in the log file of the failure handling apparatus 28.

After inputting the above setting data, the designer clicks the “Preview” button (not shown) to confirm the completed image of the command execution screen 80 and then clicks the “Register” button (not shown). Is input to the screen editing unit 34.
Upon receiving this, the screen editing unit 34 registers necessary data in the component management table 20, the property table 21, and the connector table 22.

FIG. 14 partially shows an example of the failure report screen 110, which includes an investigation block 111, a communication block 112, and the like. Although illustration is omitted, other screen configuration blocks such as a free memo block may be provided.
When a failure message is transmitted from the monitored system 30, the operator follows the failure report screen 110 and reports the fact to the customer.

The investigation block 111 is provided with a detailed information display column 113 for a failure message and an investigation block 114.
The failure message detailed information display column 113 is pre-filled with the content and attribute information of the failure message by the failure handling device 28.
The investigation block 114 includes a node investigation button, a process investigation button, a job investigation button, a log investigation button, and a resource investigation button. When the operator clicks these investigation buttons, the corresponding investigation command responds to a failure. It is issued to the monitoring target system 30 via the device 28, and the result is displayed in the investigation history column 115 of the communication block 112.

The contact block 112 is roughly divided into a contact designation column 116 and a contact item display column 117.
First, the operator clicks an “add from contact block” button 118 and selects a necessary contact block from a contact block list displayed in another window. As a result, a corresponding character string is displayed in each column of the contact block name, contact name, contact affiliation, contact name, and telephone number. When a plurality of contacts are registered in the contact block, each person's name and telephone number are listed according to a preset display priority.
A plurality of contact block is set in the contact block table 33 in advance. The setting of the contact block will be described in detail later.

Next, the operator makes a call to the displayed telephone number and verbally informs the person in charge of the communication to be described later. At this time, clicking the “current” button 119, displaying the date and time when the call was made, and clicking the “contact OK” button 120, the telephone contact was successful in the list log file 401 in the failure response device 28. The date and time are recorded.
On the other hand, when a call is made but no contact is made due to the absence of the other party, the operator displays the date and time of the call and clicks the “Contact NG” button 121. As a result, the date and time when the telephone contact failed is recorded in the list log file 401 in the failure handling apparatus 28.

  In the message display column 117, the greetings and contact comments that the operator should give to the customer's staff, detailed information on the detected failure message, history information on the investigation results, and even the closing comments are carefully written. ing. For this reason, even an inexperienced new operator can make a temporary trouble report to a customer by simply reading the description in the communication item display column 117.

When creating the failure report screen 110, the designer accesses the screen editing unit 34 from the design terminal 14 and requests a failure report screen creation service.
Upon receiving this, the screen editing unit 34 extracts the design time screen skeleton of the failure report screen from the screen skeleton storage unit 13 and transmits it to the design terminal 14.

  FIG. 15 shows a part of the design screen 125 for the failure report screen displayed on the web browser of the design terminal 14, in which a survey block 126 and a contact block 127 are drawn. The bibliographic item input field, title input field, and navigation description input field are the same as the design screen 50 for the procedure manual execution screen shown in FIG.

First, the designer inputs an arbitrary block name in the block name setting field 58 of the investigation block 126. “Survey” is displayed by default, but the designer can change it to another name if necessary.
Since the check box 59 provided on the right side of the block name setting column 58 is activated, the designer can hide the investigation block 111 on the failure report screen 110 by removing the check.

Next, the designer inputs “Please investigate the failure for the following messages” in the explanatory text setting field 128 of the investigation block 126.
When the designer checks the “display investigation block” check box 129, the investigation block 114 is displayed on the failure report screen 110 (see FIG. 14).

  Next, the designer shifts to an editing operation of the communication block 127. First, a block name is entered in the block name setting field 58 as necessary. By default, “Contact” is displayed. Since the check box 59 for selecting display / non-display of the communication block 127 is grayed out with a check mark, the designer cannot hide it.

Next, the designer inputs “Please contact customer” in the explanatory text setting field 130 of the communication block 127.
Next, the designer sets the contact address designation field 131. First, the check box 132 of the contact specification column 131 is checked, and the display of the contact specification column itself is selected.
Next, when the designer wants to fix the contact information, he / she checks the “fixed” radio button 133 and specifically describes the contact name, contact affiliation, name, and telephone number in the input column. At this time, if the "Add from contacts" button 134 is clicked, the contact list screen is sent from the screen editor 34 and displayed on a separate window, so the designer can select and enter any contact information. Can do.

  On the other hand, when the designer checks the radio button 135 for “selection designation” and also checks the radio button 136 for “display list by contact block” under the radio button 135, as shown in FIG. An “add from contact block” button 118 is displayed in the contact designation field 116 of the contact block 112.

  On the other hand, the designer checks the radio button 135 of “selection designation” and also checks the radio button 137 of “display a list by automatic segmentation (judged by message contents and time zone)” under it. In the contact address designation field 116 of the contact block 112, the contact address specified by the failure handling device 28 based on the content and date / time of the failure message is displayed.

  When the designer checks a check box 138 of “input contact confirmation”, as shown in FIG. 14, a “contact NG” button 121 and a “contact OK” button 120 are displayed in the contact designation field 116 of the contact block 112. Will be displayed.

  Next, the designer checks the check box 139 in the contact comment display column, and inputs a greeting and a comment for reporting in the input field 140. At this time, by setting the reserved word “% OPERATORNAME%”, the real name of the operator is automatically filled in by the failure handling apparatus 28 on the failure report screen 110.

When the designer checks the “display detection message” check box 141, as shown in FIG. 14, the attribute information of the fault message is also displayed in the message display column 117. There is no need to read the survey block 111.
In addition, when the designer checks the “Preliminary survey result display” check box 142, the survey history 115 is displayed as shown in FIG. 14, so the operator can communicate the necessary information to the customer in a convenient manner. It becomes.
Further, when the designer checks a check box 143 of “display comment”, and inputs an arbitrary character string in the input field 144, the closing greeting is displayed in the message display column 117 as shown in FIG. Is displayed.

After entering the above setting data, the designer clicks the “Preview” button (not shown) to check the completed image of the failure report screen 110 and then clicks the “Register” button (not shown). Is input to the screen editing unit 34.
Upon receiving this, the screen editing unit 34 registers necessary data in the component management table 20, the property table 21, and the connector table 22.

FIG. 16 partially shows an example of the contact confirmation screen 150, which includes a contact address block 151, a contact content block 152, an answer selection block 153, a confirmation input block 154, and the like. Although illustration is omitted, other screen configuration blocks such as a free memo block may be provided.
The previous trouble report screen 110 was responsible for notifying the customer of the detection of the trouble message, whereas this contact confirmation screen 150 was used to make a request to the customer and listen to the response result. used.

First, the operator clicks the “add from contact block” button 118 in the contact block 151 and selects a necessary contact block from the contact block list displayed in another window.
As a result, a corresponding character string is displayed in each column of the contact block name, contact name, contact affiliation, contact name, and telephone number.

Next, the operator makes a call to the displayed telephone number and verbally informs the displayed person in charge of the contact content and the request content displayed in the contact content block 152.
Next, the operator returns the answer selection button (“log off complete” button 155, “can be forcibly disconnected” button 156, “do not log off” button 157) displayed in the answer selection block 153 from the customer. Select the answer that corresponds to your answer.

Since these options buttons are provided with in-page links to the options for confirmation input set in the confirmation input block 154 in the next stage, for example, when the operator clicks the “log off complete” button 155, the confirmation input block The screen jumps instantly until 154 “Logoff complete”.
On the other hand, the operator checks the radio button 158 for “logoff completion” and clicks the “next” button 48. As a result, the screen transitions to another failure handling screen associated with the option.

When creating the contact confirmation screen 150, the designer accesses the screen editing unit 34 from the design terminal 14 and requests a service for creating a contact confirmation screen.
Upon receiving this, the screen editing unit 34 extracts the design time screen skeleton for the contact confirmation screen from the screen skeleton storage unit 13 and transmits it to the design terminal 14.

  FIGS. 17 and 18 show a part of the design screen 160 for the contact confirmation screen displayed on the web browser of the design terminal 14. The contact content block 161, answer selection block 162 and confirmation input block 163 are shown in FIG. It is drawn. Note that the bibliographic item input field, title input field, and navigation explanation input field are the same as the design screen 50 for the procedure manual execution screen shown in FIG. The contact block is the same as the design screen 125 for the failure report screen shown in FIG.

First, the designer inputs an arbitrary block name in the block name setting field 58 of the communication content block 161. “Contact details” is displayed by default, but the designer can change the name to another name if necessary.
The check box 59 provided on the right side of the block name setting field 58 is grayed out with a check mark, and the designer cannot hide it.

  Next, the designer inputs “Please ask the user to log off” in the explanatory text setting field 162 of the communication content block 161 and at the same time, in the script definition field 163, the content of the communication (report item, customer request, etc.) ).

  Next, the designer shifts to an editing operation of the answer selection block 162. First, a block name is entered in the block name setting field 58 as necessary. By default, “answer selection” is displayed. Since the result block gray / undisplayed check box 59 is also grayed out, the designer cannot hide it.

  Since the character string “Please select user's answer” is input by default in the explanatory note setting field 164 of the answer selection block, the designer corrects it as necessary.

Next, the designer inputs “logoff complete” or the like as a specific option button in the option description field 165, and inputs a comment sentence such as “when the user completes logoff” in the supplemental description field 166, and then selects the option. Check the check box 167 to enable.
Although three options are set in the figure, the designer can set more options as needed.

Next, the designer clicks a pull-down menu in the link destination designation field 168 and sets an in-page link to an option set in the confirmation input block 163 in the next stage. By default, an index code in alphabetical order is assigned to each option button, such as “Index A”, “Index B”, “Index C”, etc., and therefore it is not usually necessary to change it.
The code such as “Index A” corresponds to the code such as “Index A” of each option set in the confirmation input field 163 described below.

  Next, the designer shifts to an editing operation of the confirmation input block 163. First, a block name is entered in the block name setting field 58 as necessary. By default, “confirmation input” is displayed. Since the check box 59 for selecting display / non-display of the result block 163 is also grayed out, the designer cannot hide it.

Next, for each of “Index A”, “Index B”, and “Index C”, the designer inputs “logoff complete” or the like in the option label setting field 169 and provides a supplementary explanation of the option in the option description field 170. input.
Each option has two history definition setting fields, history definition (for list) and history definition (for reporting), and the designer can enter a character string to be recorded in each log file in each field. Set.

After entering the above setting data, the designer clicks the “Preview” button (not shown) to check the completed image on the contact confirmation screen 150 and then clicks the “Register” button (not shown). Is input to the screen editing unit 34.
Upon receiving this, the screen editing unit 34 registers necessary data in the component management table 20, the property table 21, and the connector table 22.

FIG. 19 shows an example of a mail transmission screen 180. The customer name block 181, the address designation block 182, the subject block 183, the person in charge block 184, the mail entry word block 185, the template name block 186, the comment block 187, An attachment file block 188 is provided.
This mail transmission screen 180 is used when a customer is contacted or reported using electronic mail.

The customer name block 181 is pre-filled with the failure handling device 28 with the name of the company (“Tozai Denki Co., Ltd.”, etc.) that owns the system in which the failure has occurred.
Therefore, the operator starts by setting a destination (To), a destination (Cc), and a destination (Bcc) in the destination designation block 182.
At this time, if the "Add from contact block" button 118 is clicked, the contact list screen is transmitted from the failure handling device 28 and displayed on a separate window, so the operator can select and input any contact information. Can do.
Alternatively, enter a specific display name or e-mail address in the display name input field 189 and address input field 190 and click the “<< Add to list” button 191 to individually enter e-mail addresses in the destination list 192. Can also be added.

The subject block 183 is automatically filled with the necessary subject based on a predefined format.
In addition, the mail entry message block 185 corresponding to the mail text reflects the description content of the mail template displayed in the template name block 186 (for example, “Communication at the time of failure occurrence: for first report”).
In the example of FIG. 19, since a mail template of a method for selecting a plurality of canned sentences is specified, “report destination / report time”, “this case will be contacted only by mail”, Options for "I'll send you as soon as possible" and "(Blank)" are listed.
Therefore, for example, the operator checks the radio button of “Report destination / Report time”, enters the name of a specific person in charge as the report destination, and clicks the “Current time” button 194 to display the current time as the report time. Substitute time.
Alternatively, check the “(blank)” radio button and enter an arbitrary character string in parentheses.

The comment block 187 is provided with a list comment input field 195 and a report comment input field 196, and the operator can enter the words (memos) to be recorded in the list log file 401 and the report log file 402. You can enter in the input field.
Since the text entered in the comment block is purely for recording, it is not displayed in the mail sent to the other party.

  When attaching a file to the mail, the operator clicks a “reference” button 197 in the attachment file block 188 and designates a file stored in the failure handling terminal 32 or in another server.

The operator who has completed the necessary input on the mail transmission screen 180 clicks the “mail transmission” button 198 to request transmission of an electronic mail. As a result, a report e-mail is transmitted to the customer's staff via a mail server (not shown).
The operator waits for the message “Mail transmission complete” to be displayed and clicks the “Next” button 48 to transition to the next corresponding screen.

When creating the mail transmission screen 180, the designer accesses the screen editing unit 34 from the design terminal 14 and requests a mail transmission screen creation service.
Upon receiving this, the screen editing unit 34 extracts the design time screen skeleton of the mail transmission screen from the screen skeleton storage unit 13, generates a design screen, and transmits it to the design terminal 14.

FIG. 20 shows a part of the design screen 200 for the mail transmission screen displayed on the web browser of the design terminal 14, and the customer block 201, the destination block 202, the subject block 203, the body block 204, the free memo Block 205 is depicted.
The bibliographic item input field, title input field, and navigation description input field have substantially the same structure as the design screen 50 for the procedure manual execution screen shown in FIG. ing.

  First, the designer inputs a block name in the block name setting field 58 of each block. By default, “customer”, “destination”, “subject”, “text”, and “free memo” are displayed as block names as described above, and the designer modifies them as necessary. For example, by rewriting the block name of “free memo” to “comment”, the block name of “comment” is displayed on the mail transmission screen 180 for the block.

  In the case of the design screen 200 for this mail transmission screen, the check box 59 provided on the right side of the block name setting column is grayed out with the check box except for the free memo block 205, so the designer Only free memo blocks can be hidden.

  Next, the designer defines a method for specifying the customer name in the customer setting field 206 in the customer block 201. By default, [CUST_NAMEEr1] that identifies the company name of the system that sent the failure message is set.

Next, the designer defines a contact setting method in the destination block 202.
First, when the “fixed designation” radio button 207 is checked, the designer needs to individually set the destination (To), the destination (Cc), and the destination (Bcc).
At this time, when the “Add from contacts” button 208 is clicked, the contact list screen is transmitted from the screen editing unit 34 and displayed on a separate window, so the operator can select and input any contact. it can. Alternatively, a specific display name or e-mail address is entered in the display name input field 209 and the address input field 210, and an e-mail address is added to the destination list 212 by clicking the “<< Add to list” button 211. It can also be added individually.
When the designer selects “fixed designation”, only the destination set by the designer is fixedly displayed in the destination column of the mail transmission screen 180, and there is no room for the operator to change it.

  On the other hand, if the radio button 213 of “Selection designation” is checked and the radio button 214 of “Select and display the contact block on the execution screen without displaying the contact” is checked As shown in FIG. 19, destination selection buttons and input fields are displayed in the destination block 182 of the mail transmission screen 180.

  Alternatively, if you check the radio button 213 of “Select and specify”, check the radio button 215 of “List by contact block” under that, and set a specific contact block from the pull-down menu 216, In the address field of the mail transmission screen, a plurality of addresses belonging to the contact block selected by the designer are displayed as options (not shown). In this case, the operator checks a necessary destination check box and selects a specific transmission destination.

  Next, the designer defines a subject format in the subject setting field 217 of the subject block 203. At this time, when the reserved word list button 61 is clicked, the screen editor 34 sends a reserved word list screen and displays it on a separate window, so the designer can set any reserved word (for example, “% SYSTEM_ID%”). Selective input is possible.

Next, when the designer clicks the “select mail template” button 218 in the text block 204, a screen list of mail templates is transmitted from the screen editing unit 34 and displayed on another window.
On the other hand, the designer selects an arbitrary mail template. As a result, the contents of the selected mail template are displayed in the mail template display field.

  Next, the designer sets necessary character strings in the list comment input field 219 and the report comment input field 220 of the free memo block 205. By default, “Enter if there are special notes (for list)” and “Enter if there are special notes (for reporting)” are set.

After entering the above setting data, the designer clicks the “Preview” button (not shown), confirms the completed image of the mail transmission screen 180, and then clicks the “Register” button (not shown). Is input to the screen editing unit 34.
Upon receiving this, the screen editing unit 34 registers necessary data in the component management table 20, the property table 21, and the connector table 22.

FIG. 21 partially shows an example of the general-purpose instruction screen 230, in which an instruction 1 block 231, an instruction 2 block 232, an instruction 3 block 233, and an instruction 4 block 234 are drawn. Although illustration is omitted, other screen configuration blocks such as a free memo block may be provided.
This general-purpose instruction screen 230 includes various procedures that cannot be covered by screens specialized for individual applications, such as the procedure manual execution screen 40, the command execution screen 80, the failure report screen 110, the contact confirmation screen 150, and the mail transmission screen 180 described above. This is used to issue a simple instruction to the operator.

  First, the instruction 1 block 231 includes an item for inputting the elapsed time since the process stop and an option for selecting whether or not the process is automatically recovered (automatic recovery / stopped). Is set. Each option has a radio button.

Therefore, the operator reads the content of the error message, calculates the elapsed time from the process stop, and inputs a numerical value (for example, “5”) in the elapsed time input item 235.
In addition, the radio button 236 of an option corresponding to the current state of the process (for example, “still stopped”) is checked.

The instruction 2 block 232 is provided with two option buttons (“failover target” button 237 / “failover non-target” button 238) for selecting whether or not to be a failover target.
Since each option button has an internal link to the option set in the next instruction 3 block 233, when the operator clicks one of the option buttons, it jumps immediately to the corresponding option in the instruction 3 block 233. To do.

When the jump destination is "when failover is a target", the operator checks the radio button 239 of the option and checks the instruction comment of the option "Execute the failover confirmation procedure for the failure that occurred" Follow.
Specifically, click the “Procedure List” button 240, select the procedure from the list of procedures displayed in another window, display it on the screen, and take action according to the description. Do.

  On the other hand, when the jump destination is "when failover is not applicable", the operator checks the radio button 241 for the option and presses the "Next button" instruction comment for the option. Follow.

In the instruction 4 block 234, there is provided an option as to whether or not the process is automatically recovered as a result of executing the procedure manual in the instruction 3 block 239.
In response to this, the operator clicks the “next” button 48 after checking the radio button of the option that matches the current situation.
As a result, the screen transitions to another failure handling screen associated with each option.

When creating this general-purpose instruction screen 230, the designer accesses the screen editing unit 34 from the design terminal 14 and requests a general-purpose instruction screen creation service.
Upon receiving this, the screen editing unit 34 extracts the design time screen skeleton of the general-purpose instruction screen from the screen skeleton storage unit 13, generates a design screen, and transmits it to the design terminal 14.

Since the design screen for the general-purpose instruction screen has a relatively complicated configuration, the basic structure of the design screen will be described based on FIG. 22 before the details thereof are described.
As shown in the figure, the design screen for the general-purpose instruction screen can use a maximum of five instruction blocks, such as instruction 1 block to instruction 5 block, and each instruction block has a maximum of element 1 to element 5 as shown in FIG. Five elements can be used. Furthermore, for each element, one of the four element types of input, result selection, intra-page link, and external page connection can be selected.
Therefore, by changing the combination of element types set for each element of each instruction block as appropriate, or by adjusting the number of instruction blocks used or the number of elements used in each instruction block, the designer can An extremely versatile general-purpose instruction screen can be easily realized.

  FIG. 23 to FIG. 26 show a part of the design screen 250 for the general-purpose instruction screen displayed on the web browser of the design terminal 14, and an instruction 1 block to an instruction 4 block are drawn. The bibliographic item input field, title input field, and navigation description input field are the same as the design screen 50 for the procedure manual execution screen shown in FIG.

  First, the designer inputs an arbitrary block name in the block name setting field 58 of the instruction 1 block 251. “Instruction 1” is displayed by default, but the designer can change the name to another name (for example, “Survey 1”) as necessary.

This instruction 1 block 251 includes five element blocks, and the designer can add or subtract the number of element blocks actually used by checking or unchecking the checkbox 252 of each element block. .
Each element of this instruction 1 block 251 is assigned an identification code of Index A-1 to Index A-5, and Index A-1 and Index A-2 in this are checked. The use of one element is selected.

The designer then begins editing the Index A-1 block.
First, the designer expands a pull-down menu in the element type selection field 253, and sets one element type from “input”, “result selection”, “in-page link”, and “external page connection”. In the figure, the “input” element type is selected.
In this state, when the designer clicks the page update button of the web browser, the design screen 250 including the setting item for “input” is retransmitted from the screen editing unit 34 and displayed on the display of the design terminal 14.

In response to this, the designer inputs “please check the elapsed time since process stop” in the explanatory note setting field 254.
Next, the designer inputs a character string “From the error message to the current time when the monitoring terminal detects a process stop ...” in the script definition field 255 and “<font color =” red ” > Elapsed time </ font> [TEXT5 I 0] minutes ”is entered, and an elapsed time input field 235 is formed.
Furthermore, the designer sets “elapsed time input” as a wording for recording in the history script input field (for list and report).

The designer then begins editing the Index A-2 block.
First, the designer expands the pull-down menu in the element type selection field 253, sets “result selection” as the element type, and then clicks the page refresh button of the Web browser.
As a result, the design screen 250 including the setting item for “result selection” is retransmitted from the screen editing unit 34 and displayed on the display of the design terminal 14.

In response to this, the designer inputs “Please check whether the process is automatically restored” in the explanatory note setting field 254.
Next, the designer sets “Please check with the monitoring terminal whether the failed process is automatically recovered” in the script definition field 255.
In the case of the element block for selecting the result, since a plurality of option setting fields are provided, the designer inputs a character string as an option in the option description field 256 and defines the history (for list and report). After inputting the character string, the check box 257 is checked to declare the use of the option.

In the figure, two options of “automatic recovery” and “still stopped” are set, but the designer can set more options.
When the option is set in the element block for selecting this result, it will be displayed as an option with a radio button on the general-purpose instruction screen 230, but this is an option for selecting information to be recorded only, which will be described later. This is not for controlling the next screen transition, as in the “External page connection” option.

Next, as shown in FIG. 24, the designer moves to the editing operation of the instruction 2 block 260 and inputs an arbitrary block name in the block name setting field 58. By default, “Instruction 2” is displayed.
This instruction 2 block also has 5 element blocks, and each element is given an identification code of Index B-1 to Index B-5, but here only the element of "Index B-1" Is being used.

First, the designer expands the pull-down menu in the element type selection field 253, sets “in-page link” as the element type, and then clicks the page refresh button of the Web browser.
As a result, the design screen 250 including the setting item for “in-page link” is retransmitted from the screen editing unit 34 and displayed on the display of the design terminal 14.

In response to this, the designer inputs “Please confirm whether or not to fail over” in the explanatory note setting field 254.
Next, the designer inputs “Determine whether the relevant failure is a failover target and press the following link” in the script definition field 255.

In the case of this element block for in-page links, a plurality of option setting fields are provided, so the designer inputs a character string to be an option button in the option description field 261 and a comment text in the comment text setting field 262. And check the check box 263 to declare the use of the option.
In addition, when the pull-down menu of the link destination designation field 264 provided for each option is expanded, the identification codes of all the element blocks included in the design screen 250 for the general-purpose instruction screen are displayed in a list. One element block is set as a link destination.

In the figure, two options, "Failover Target" and "Failover Not Target" are set, and "Index C-1" and "Index C-2" are set as the link destinations respectively. Designers can set more options.
When an option is set in the element block for in-page link, it is displayed as an option button on the general-purpose instruction screen 230.

Next, as shown in FIG. 25, the designer moves to an editing operation of the instruction 3 block 270 and inputs an arbitrary block name in the block name setting field 58. By default, “Instruction 3” is displayed.
This instruction 3 block also includes five element blocks, and each element is given an identification code of Index C-1 to Index C-5. Here, “Index C-1” and “Index C Only the “C-2” element is used.

First, the designer expands the pull-down menu in each element type selection field 253, sets “input” as the element type, and then clicks the page refresh button of the Web browser.
As a result, the design screen 250 including the setting item for “input” is retransmitted from the screen editing unit 34 and displayed on the display of the design terminal 14.

On the other hand, the designer inputs “in case of failover” in the explanatory text setting field 254 of Index C-1.
In addition, the designer inputs “please confirm the failover confirmation procedure manual for the failure that has occurred” in the script definition field 255, and clicks the “reserved word list” button 61 and the “procedure document list” button 240. “[DISP_GUIDE: 0]”, which is a reserved word for displaying “”, is selected and input.
Furthermore, the designer sets “refer to procedure manual” as a recording word in the history script input field (for list and report).

Next, the designer inputs “when failover is not a target” in the explanatory text setting field 254 of Index C-2.
In addition, the designer inputs “Please press the next button” in the script definition field 255 and sets “Next” as the recording text in the history script input field (for list and report). To do.

For this instruction 3 block 270, since the check box 271 of “Add radio button to this block” is checked, each explanatory text set to Index C-1 and Index C-2 has a general purpose A radio button for selection is displayed on the instruction screen 230 (see FIG. 21).
However, this radio button is only an option for selecting information to be recorded, and is not for controlling the next screen transition.

Next, as shown in FIG. 26, the designer moves to the editing operation of the instruction 4 block 280 and inputs an arbitrary block name in the block name setting field 58. By default, “Instruction 4” is displayed.
This instruction 4 block 280 is also provided with five element blocks, and each element is given an identification code of Index D-1 to Index D-5. Only used.

First, the designer expands the pull-down menu in the element type selection field 253, sets “external page connection” as the element type, and then clicks the page refresh button of the Web browser.
As a result, the design screen 250 having the setting item for “external page connection” is retransmitted from the screen editing unit 34 and displayed on the display of the design terminal 14.

In response to this, the designer inputs “Please check whether the process is automatically restored” in the explanatory note setting field 254.
Next, the designer sets “Please check the node status with the thousand node monitor” in the script definition field 255.
In the case of this element block for external page connection, since a plurality of option setting fields are provided, the designer inputs a character string as an option in the option description field 281 and uses it for history definition (for list and report). ) Is entered, then the check box 282 is checked to declare the use of the option.

In the figure, two options “node state UP” and “node state UP” are set, but the designer can set more options.
When an option is set in the element block for external page connection, it is displayed on the general-purpose instruction screen 230 as an option with a radio button.
In addition, since the radio button of the element block for external page connection has a function to control the next screen transition, the operator selects “next” with the radio button of any one option checked. When the “to” button 48 is clicked, a branch transition is made to the screen associated with each option.

After inputting the above setting data, the designer clicks the “Preview” button (not shown) to confirm the completed image of the general-purpose instruction screen 250 and then clicks the “Register” button (not shown). Is input to the screen editing unit 34.
Upon receiving this, the screen editing unit 34 registers necessary data in the component management table 20, the property table 21, and the connector table 22.

As described above, in the case of the support system according to the present invention, the display time setting skeleton, the input item setting field, and the option setting field that should be provided as the failure handling screen are included in the design time screen skeleton of various failure handling screens. The design value is automatically stored in the corresponding table by entering text directly into the design screen generated based on this screen skeleton or checking the radio button. In addition, when the failure handling screen is generated, the above-described setting value is applied to the runtime screen skeleton of the screen to automatically generate an original failure handling screen as intended by the designer. This eliminates the need for design (external design) on how to design each screen, and it can be easily identified even by general operators who do not have expertise in system structure, coding, or business processing. It is possible to design a customized failure response screen for customers.
The designer who has completed the design of the failure handling screen requests the flow editing unit 35 to edit the screen transition flow.
In response to this, the flow editing unit 35 transmits a flow editing screen to the design terminal 14.

FIG. 27 shows an example of the flow editing screen 300, which includes a main screen 301 and a screen component display field 302 provided on the left side thereof.
The screen component display field 302 displays a plurality of screen symbols 303 symbolizing various failure response screens (screen components) designed by the designer.
Each screen symbol 303 is generated by the flow editing unit 35 with reference to the component management table 20, the property table, and the connector table, and the name of the screen component (procedure execution) is displayed on the rectangular component body 304. Screen etc.) and screen part ID (BH001 etc.) are displayed.

  The designer arranges an arbitrary screen symbol 303 from the list of screen symbols 303 by drag and drop at a predetermined position on the main screen 301 using a mouse.

Each screen symbol 303 is provided with a number of connectors 305 corresponding to the number of branches of the screen component.
For example, since the procedure manual execution screen BH001 has three branches, the screen symbol 303 has three connectors 305 formed therein. Since two branches are set in the command execution screen BH002, two connectors 305 are formed. On the other hand, in the case of the failure report screen BH003, no branch is set, but one connector 305 is formed in order to realize connection with other subsequent screens.

The designer drags and stretches the connector 305 of each screen symbol 303 arranged on the main screen 301 with the mouse, and connects it to the top of the screen symbol 303 to be the subsequent screen.
Each connector 305 is associated with a unique option, and when the designer moves the mouse pointer 306 to the side of each connector 305, the option associated with the connector 305 is popped up. For this reason, the designer can connect the screen symbols 303 in a hierarchical order in a necessary order without hesitation, and can very easily design a screen flow having a complicated branch structure.

During editing of this screen flow, a designer who feels that a specific screen component needs to be corrected double-clicks the corresponding screen symbol 303. As a result, an edit screen in which the existing setting value is reflected on the design screen of the screen part is transmitted from the screen editing unit 34 and displayed on the Web browser of the design terminal 14.
On the other hand, if the designer makes necessary corrections and clicks the registration button 76, the correction contents are immediately reflected in the screen symbol.

When the designer who has finished designing the screen flow using the flow editing screen 300 clicks the “Register” button 307, the editing data by the designer (setting data of the link relationship between the screens) is transmitted to the screen editing unit 34. .
Receiving this, the flow editing unit 35 registers the necessary data in the flow management table 23, the flow component table 24, and the transition table 25 with the edited data.

FIG. 28 shows a configuration example of the flow management table 23, which includes data items of flow ID, flow name, start node ID, and status. In the start node ID, the node ID of the screen displayed first in each screen flow is stored.
FIG. 29 shows a configuration example of the flow component table 24, which includes data items of a flow ID, a node ID, and a screen component ID. The node ID item stores a unique ID that identifies the individual screens that make up the screen flow, while the screen component ID item contains the IDs of the specific screen components that make up each node. Stored. Therefore, the same screen component ID may be associated with a plurality of different node IDs.
FIG. 30 shows a configuration example of the transition table 25, which includes data items of screen component ID, connector ID, and transition destination node ID. By referring to this transition table, the failure handling apparatus 28 can specify the branch destination of each screen.

  Next, the designer performs a test in order to confirm whether the designed screen flow functions normally. That is, when the editor presses the “test mode” button in the management menu (not shown) displayed on the screen and requests screen transition in the test mode, the screen transition flow registered from the flow editing unit 35 ( Navi template) list screen is transmitted and displayed on the display of the design terminal 14 (not shown).

  When the designer selects a screen transition flow that has just been registered from the list, a failure selection screen is transmitted from the flow editing unit 35 and displayed on the display of the design terminal 14 (not shown). On this screen, dummy failure messages registered in advance are listed. When the designer selects an arbitrary failure message from these, a screen transition flow in the test mode is started.

  First, the flow editing unit 35 refers to the flow management table 23 and the component management table 20 to identify the first failure handling screen, obtains the corresponding runtime screen skeleton from the screen skeleton storage unit 13, and assigns the property to this property. A failure response screen (HTML file) is generated by applying the setting values stored in the table 21 and transmitted to the design terminal 14.

On the other hand, the designer inputs the result on the screen, assuming that necessary processing has been executed according to the description on the screen.
Receiving this, the flow editing unit 35 refers to the flow component table 24, the transition table 25, the component management table 20, and the connector table 22, and identifies the next failure response screen that matches the above execution result, The corresponding execution screen skeleton is acquired from the screen skeleton storage unit 13, and the setting value stored in the property table 21 is applied to the screen skeleton storage unit 13 to generate the next failure response screen and transmit it to the failure response terminal 32.

Thereafter, by repeating the above-described processing, failure handling screens are successively transmitted from the flow editing unit 35 to the design terminal 14, and the designer performs necessary input and selection.
When the transition destination of the screen branches into a plurality according to the options provided on each screen, the designer repeats the test many times so as to pass all the routes.
In this test, a test coverage screen (not shown) similar to the flow editing screen of FIG. 27 is displayed in a separate window, and each screen symbol 303, the mutual branching relationship, the route passed, etc. are graphically expressed. Yes.

  The designer who discovers that the branch destination is not set on the way, or that the screen changes to a screen different from the intended screen, suspends the test and returns to the flow editing screen 300 in FIG. Try connecting again.

  Then, the designer who has confirmed that there is no problem with all the routes presses the “approval request” button displayed on the test coverage screen and reports the fact to the administrator.

  When the administrator who has received this report accesses the flow editing unit 35 from his design terminal 14, a list screen of registered screen transition flows is transmitted from the flow editing unit 35 and displayed on the display of the design terminal 14. (Not shown).

When the administrator selects a reported screen transition flow from the list, a test coverage screen is transmitted from the flow editing unit 35 and displayed on the display of the design terminal 14 (not shown).
Then, the administrator who confirms that the test has been completed for all routes presses the “approval” button displayed on the test coverage screen.

Upon receiving this, the flow editing unit 35 sets an approved flag in the status of the flow management table 23 (see FIG. 28).
The failure handling device 28 confirms that this approved flag is set, and then applies the screen transition flow at the time of the actual failure. This is the flow implementation condition.

Next, a contact block registration method will be described.
That is, when the designer accesses the carving condition editing unit 403 and requests registration of a contact block, a contact block edit screen (for normal use) is transmitted.
FIG. 31 shows an example of the contact block edit screen (for normal use) 310.

First, the designer inputs the date and time in the start date / time setting field 311 and inputs the name of the contact block in the name input field 312. The contact block ID “514” is automatically assigned by the system.
Next, when the designer clicks the “select / edit” button 313 in the target system setting column, a list screen of monitoring target systems stored in the customer system table 17 is transmitted from the classification condition editing unit 403 (not shown). ). When the designer selects one monitoring target system from the list of monitoring target systems, the monitoring target system is displayed in the confirmation box 314.

  Next, the designer inputs a name of a contact person in charge, a destination type (To / Cc / Bcc), and an e-mail address in the mail destination setting field 315.

Next, the designer inputs the name, name (reading), telephone number, and affiliation of the person in charge of the necessary contact in the telephone contact setting field 316, and sets the display priority of each person.
The display priority means the order in which a plurality of telephone contacts are displayed in a list on the failure handling screen, and the operator makes a call according to this order. The designer can set different display priorities for business days (daytime), business days (nighttime), holidays (daytime), and holidays (nighttime).
The failure handling device 28 arranges the telephone contacts according to the display priority corresponding to the occurrence of the failure, and inserts them into the contact display items of the runtime screen skeleton.

  By clicking the “add” button 317, the designer can add input items for mail address and telephone contact, and add a number of persons in charge to the contact block.

  When the designer who has completed inputting necessary items clicks the “Register” button 318, the input data is transmitted to the segmentation condition editing unit 403 and stored in the contact block table 33.

In the above description, the example in which the designer inputs necessary items from the beginning has been described. However, the setting of a registered contact block can also be used.
That is, when the designer clicks the “copy source search” button 319, a copy source search screen is transmitted from the segmentation condition editing unit 403 and displayed on the display of the design terminal 14 (not shown). When the designer selects one contact block via this search screen, the setting value of the contact block is filled in each input field.
The designer can then complete the editing of the new contact block very easily by modifying the required items.

  In addition to the normal contact block described above, the designer registers multiple temporary contact blocks for the same monitoring target, and is designed to switch contact blocks flexibly according to time conditions can do.

That is, when the designer accesses the carving condition editing unit 403 and requests registration of a temporary contact block, a contact block edit screen (temporary) is transmitted.
FIG. 32 shows an example of this contact block edit screen (temporary) 330.

Since this contact block edit screen (temporary) 330 has many input items that overlap with the above-described contact block edit screen (normal) 310, the difference between the two will be described.
First, in the case of a temporary contact block, not only the start but also the end must be set, so the designer enters the date and time in the start date and time setting field 311 and the end date and time setting field. Enter the date and time in 331.

  The contact block name setting, target system selection, e-mail destination setting, and telephone contact setting are not different from the normal contact block editing screen 310. However, the setting is different from the normal setting.

In the normal contact block name setting field 332, the designer designates a normal contact block that should become the parent of the temporary contact block.
That is, when the designer clicks the “Search” button 333, the normal condition contact block selection screen is transmitted from the segmentation condition editing unit 403 and displayed in another window (not shown).
Here, when the designer selects a target normal time contact block name, the normal time contact block name is transferred to the confirmation box 334.

  When the designer who completes the necessary items clicks the “Register” button 318, the input data is sent to the segmentation condition editing unit 403, and the contact block table 33 is associated with the normal contact block that becomes the parent Stored in

  FIG. 33 is an explanatory diagram illustrating the application relationship between the normal contact block and the temporary contact block, and the first temporary contact block β during the effective period of the normal contact block α. And the state where the 2nd temporary contact block γ is set.

In this case, for the period B that is the effective period of the first temporary contact block β, the contact set in the first temporary contact block β is preferentially applied, and the normal contact block This setting is not applicable.
Similarly, for the period C that is the effective period of the second temporary contact block γ, the contact set in the second temporary contact block γ is preferentially applied, and the normal-time contact block is applied. This setting is not applicable.
In contrast, for the period A and the period D in which the temporary contact block is not set, the contact set in the normal contact block is applied.

  As is clear from the above, when the effective period of the normal contact block and the effective period of the temporary contact block overlap, the setting of the temporary contact block has priority. In addition, it is not allowed that the validity period overlaps between the temporary contact block.

  As described above, by setting multiple temporary contact blocks during the normal period contact block validity period, for example, during summer holidays and the year-end and New Year holidays, contacts different from normal times can be obstructed. It can be displayed on the corresponding screen.

Next, a method for registering the separation condition will be described.
That is, when the designer accesses the cutting condition editing unit 403 and requests registration of the cutting condition, a cutting condition editing screen is transmitted.
FIG. 34 shows an example of the segmentation condition editing screen 340.

  First, the designer inputs a numerical value indicating the priority order of application in the priority order setting column 341. For example, when “1” is set as the priority order, even if a plurality of separation conditions with overlapping valid periods and valid time zones are set, this means that the separation conditions are applied with the highest priority. .

Next, the designer checks the “valid” radio button 342 and inputs an appropriate name in the carving name setting field 343.
Next, the designer opens a pull-down menu in the flow ID selection field 344, and selects and inputs a preset screen transition flow.
Next, the designer clicks the search button 346 in the contact block selection field 345 and selects and inputs a contact block set in advance on a search screen (not shown).

Next, the designer clicks a “select / edit” button 348 in the system ID setting field 347 to select and input a monitoring target system to which the separation condition is applied.
Next, the designer sets the ID of the fault message to be applied in the message ID setting column 349, the identification code of the source process to be applied in the source process setting column 350, and the application target in the message status setting column 351. Each message status specific information is input.
Next, the designer opens a pull-down menu in the failure category selection field 352, selects and inputs the failure category to be applied, and then inputs specific contents of the failure message to be applied in the message body setting field 353. .

Next, in the time zone setting field 354, the designer sets the day of the week (Sunday to Saturday, public holiday) and the time zone to which the separation condition is applied.
For example, if you check the checkbox for Sundays and holidays, enter "0800-1800" as the hour and minute and click the "Add" button 355, "08: 00-18: 00" will be valid for Sundays and holidays Applicable conditions for the time zone are set.

  The designer can also set multiple time zones at the same time. For example, if you check the check box on Wednesday, enter "1000-2000" as the hour and minute and then click the "Add" button 355, apply from 10:00 to 20:00 for the effective time zone for Wednesday A condition is added.

Finally, the designer sets an effective period to which the separation condition is applied in the effective period setting field 356.
For example, if “20100101” is entered as the start date, “0800” is entered as the hour, “20101231” is entered as the end date, and “2000” is entered as the hour, “January 2010 1 day 08:00 to December 31, 2010 20:00 "is the effective period of the carving condition.
However, when the carving condition is used for normal use, the designer is allowed to leave the end of the valid period unset.

  When the designer who has completed the input of necessary items clicks the “Register” button 357, the input data is transmitted to the classification condition editing unit 403 and stored in the classification condition table 19.

The designer can set a plurality of separation conditions with different effective periods and application time zones for the same monitoring target system, and register them in the separation condition table 19.
In the case where valid periods and application time zones overlap among a plurality of separation conditions, the failure handling apparatus 28 determines a separation condition to be applied at the current time according to the priority order set for each.

1 is an overall configuration diagram of a system including a failure handling screen design support system. It is a figure which shows the structural example of a cutting condition table. It is a screen flow figure showing transition of a failure handling screen. It is a figure which shows the structure of an editing apparatus. It is a figure which shows an example of a procedure manual execution screen. It is a figure which shows an example of the design screen for procedure manual execution screens. It is a figure which shows an example of the design screen for procedure manual execution screens. It is a figure which shows the structural example of a components management table. It is a figure which shows the structural example of a property table. It is a figure which shows the structural example of a connector table. It is a figure which shows an example of a command execution screen. It is a figure which shows an example of the design screen of a command execution screen. It is a figure which shows an example of the design screen of a command execution screen. It is a figure which shows an example of a failure report screen. It is a figure which shows an example of the design screen of a failure report screen. It is a figure which shows an example of a contact confirmation screen. It is a figure which shows an example of the design screen of a contact confirmation screen. It is a figure which shows an example of the design screen of a contact confirmation screen. It is a figure which shows an example of a mail transmission screen. It is a figure which shows an example of the design screen of a mail transmission screen. It is a figure which shows an example of a general purpose instruction | indication screen. It is a conceptual diagram which shows the whole structure of the design screen of a general purpose instruction | indication screen. It is a figure which shows an example of the design screen of a general purpose instruction | indication screen. It is a figure which shows an example of the design screen of a general purpose instruction | indication screen. It is a figure which shows an example of the design screen of a general purpose instruction | indication screen. It is a figure which shows an example of the design screen of a general purpose instruction | indication screen. It is a figure which shows an example of a flow edit screen. It is a figure which shows the structural example of a flow management table. It is a figure which shows the structural example of a flow component table. It is a figure which shows the structural example of a transition table. It is a figure which shows an example of a contact block edit screen (for normal use). It is a figure which shows an example of a contact block edit screen (for temporary use). It is explanatory drawing which shows the application relation of the contact block for normal, and the contact block for temporary. It is a figure which shows an example of a cutting condition edit screen. It is a schematic diagram which shows the relationship between the screen skeleton for design time of a procedure manual execution screen, and the screen skeleton for runtime.

10 Screen support system for failure handling screen flow
11 Editing device
12 databases
13 Screen skeleton storage
14 Design terminal
15 Procedure manual management table
16 Command management table
17 Customer system table
18 Contact table
19 Carving condition table
20 Parts management table
21 Property table
22 Connector table
23 Flow management table
24 Flow component table
25 Transition table
26 Reserved word management table
28 Fault response equipment
30 Monitored systems
31 Monitored servers
32 Handset for failure
33 Contact Block Table
34 Screen editor
35 Flow editor
40 Procedure execution screen
50 Design screen for procedure manual execution screen
59 Check box
61 Reserved word list button
67 “Add to List” button
80 Command execution screen
90 Design screen for command execution screen
95 “Select from list” button
110 Trouble report screen
125 Design screen for trouble report screen
150 Contact confirmation screen
160 Design screen for contact confirmation screen
180 E-mail sending screen
200 Design screen for sending email
230 General instruction screen
250 Design screen for general-purpose instruction screen
300 Flow edit screen
303 Screen symbol
305 connector
310 Contact block edit screen (for normal use)
311 Start date and time setting field
312 Name input field
313 Select / Edit button
314 confirmation box
315 Mail address setting field
316 Telephone contact setting field
317 Add button
318 Register button
319 "Copy Source Search" button
330 Contact block edit screen (for temporary use)
331 End time setting field
332 Contact block name setting field for normal use
333 Search button
334 confirmation box
340 Cutting condition edit screen
341 Priority setting field
342 Enabled radio button
343 Carving name setting field
344 Flow ID selection field
345 Contact block selection field
346 Search button
347 System ID setting field
348 Select / Variation button
349 Message ID setting field
350 Source process setting field
351 Message status setting field
352 Failure category selection field
353 Message text setting field
354 Time zone setting field
355 Add button
356 Valid period setting field
357 Register button
400 contact block table
401 Log file for list
402 Log file for reporting
403 Carving condition editor
405 screen skeleton management table

Claims (7)

Multiple types of design screens for generating multiple types of design screens with setting fields for multiple display items that should be included in the failure response screens that are sequentially displayed on the failure response terminal operated by the operator when a failure occurs Screen skeleton storage means for storing a plurality of types of screen skeletons for runtime having display items corresponding to each setting field of each design screen ;
When a design screen display request related to a specific type of failure handling screen is transmitted from the design terminal operated by the designer, the program included in the design time screen skeleton related to the failure handling screen is executed in advance. A design screen generating means for generating a design screen having at least a part of setting fields corresponding to the display request among the setting fields of the plurality of display items ;
Means for sending the design screen to the design terminal and prompting the setting for each setting field;
Fault response screen generation that generates a fault response screen by applying the setting data for each setting field on the design screen transmitted from the design terminal to the corresponding display item of the runtime screen skeleton corresponding to the design screen Means,
Means for transmitting the failure handling screen to the design terminal;
When a registration request is sent from the design terminal for a designed fault handling screen, the setting data for each setting field on the design screen sent from the design terminal is displayed as a screen component unique to the fault handling screen. Means for storing in a predetermined setting data storage means in association with the setting item ID identifying the ID and each setting field;
A screen design support system for failure handling, characterized by comprising: Design screen generated based on the screen skeleton for at the design the display a plurality of blocks are provided with respectively a setting column of the item, and, at least some of the blocks the display / hide Check box to control the
The runtime screen skeleton also includes a plurality of blocks each having display items corresponding to the setting fields included in each block of the design screen.
When the setting data indicating that the check box is unchecked is transmitted from the design terminal, the failure handling screen generation unit generates a failure handling screen that hides the block according to the setting data. The failure handling screen design support system according to claim 1. Screen symbol generation means for referring to the setting data storage means and generating a symbol of a designed failure handling screen associated with the screen part ID,
Means for sending a flow editing screen on which a plurality of screen symbols are displayed to the design terminal, and for prompting the setting of a screen transition flow between each failure handling screen;
Setting data for identifying a plurality of failure handling screens constituting a screen transition flow from the design terminal, setting data for identifying a failure handling screen that is initially displayed in the screen transition flow, and a transition destination of each failure handling screen When setting data for specifying a failure handling screen to be transmitted is transmitted, the setting data is associated with a unique flow ID and stored in a predetermined storage unit.
The flow editing screen includes a screen part display field in which a plurality of screen symbols are displayed in a list, and a main screen. Arbitrary screen symbols are arranged from the screen part display field to the main screen on the design terminal, and In the screen transition flow, setting data for specifying a plurality of failure handling screens constituting the screen transition flow by connecting at least one connector provided for each screen symbol to another screen symbol on the main screen The failure data according to claim 1 or 2, wherein setting data for specifying a failure response screen to be displayed first and setting data for specifying a failure response screen as a transition destination of each failure response screen are generated. Support screen design support system. The design screen generated based on the above design time screen skeleton has an option setting field.
The said screen symbol production | generation means produces | generates the screen symbol provided with the connector according to the number of the said choice, when the setting data of the choice are transmitted from the said design terminal. Fault response screen design support system. It has a procedure manual management table that stores multiple procedure manual names that should be referenced when a failure occurs.
In the design screen generated based on the above design time screen skeleton, the setting field for specifying the procedure manual to be displayed on the failure handling screen and the procedure manual name stored in the procedure manual management table are called. A button is provided,
The design screen generation means, when the button is pressed on the design screen, transmits a list screen describing a plurality of procedure manual names stored in the procedure manual management table to the design terminal, and this list. 5. When a specific procedure manual name is selected on the screen, a design screen in which the procedure manual name is inserted in the setting field is generated and transmitted to the design terminal. Failure support screen design support system. It has a command management table that stores multiple command names that should be executed when a failure occurs.
The design screen generated based on the design time screen skeleton has a setting field for designating a command to be displayed on the failure handling screen and a button for calling a command name stored in the command management table. Provided,
The design screen generation means, when the button is pressed on the design screen, transmits a list screen describing a plurality of command names stored in the command management table to the design terminal, and the list screen 6. When a specific command name is selected in the above, a design screen in which the command name is inserted in the setting field is generated and transmitted to the design terminal. Fault response screen design support system. A reserved word management table for registering a plurality of reserved words with unique meanings defined in advance,
The design screen generated based on the design screen skeleton is provided with a button for calling the reserved word for a specific setting field.
When the button is pressed on the design screen, the design screen generation means transmits a list screen of reserved words stored in the reserved word management table to the design terminal, and a specific screen is displayed on the list screen. The failure handling screen according to claim 1, wherein when a reserved word is selected, a design screen in which the reserved word is inserted in the setting field is generated and transmitted to the design terminal. Design support system.

Images