JP2011227789A - Information processor and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To create an operating procedure manual without the omission of return operations for returning, after executing a predetermined operation, to a state before executing the operation in creating an operating procedure manual.SOLUTION: An operating procedure DB3 stores information which contains definitions of multiple types of operations for which an operation procedure manual is to be generated and definitions of return operations as paired operations for each operation and with which the procedures to be required for properly executing each operation can be generated. An operation execution procedure manual output part 10 and an operation procedure manual output part 30 generate an execution procedure of an operation designated as a target of the procedure generation by an operation ID designation part 2 among the multiple types of operations based on the information in the operating procedure DB3. In parallel, the operation execution procedure manual output part 10, an operation return procedure manual output part 20, and the operation procedure manual output part 30 extract the paired operation of the designated operation based on the information in the operating procedure DB3 and generate an execution procedure of the extracted paired operation. Then, the operation procedure manual output part 30 outputs the operation procedure manual showing the execution procedure of the designated operation and the execution procedure of the paired operation.

Description

  The present invention relates to a work procedure manual creation support system for creating a work procedure manual.

The work procedure manual is a document showing a procedure for changing the system.
When the scale of the system is large, a large number of work procedure manuals are managed, and it takes time to change the work procedure manuals when the system is changed.
The work procedure manual creation support system automates the creation of the work procedure manual.
The contents of the automation were labor savings in creating work procedure manuals by capturing the output screen when the operation was actually performed on the terminal of the system and performing processing such as inserting it into the format (for example, Patent Document 1).

JP 2009-181170 A

As described above, in the conventional work procedure manual creation support system, there is a problem that a work procedure manual leaks when there is work that is not actually performed during operation on the terminal. is there.
The contents of the leak are a return operation for undoing the change after the operation for changing the system is performed, and a confirmation operation for performing the operation after confirming the state of the system at the time of performing the operation.
In order to prevent such work leakage, attention is urged so as to eliminate leakage in education and in the manual of the work procedure manual creation support system, but it is difficult to eliminate the leakage of the procedure.

  One of the main objects of the present invention is to solve the above-mentioned problems, and the main object of the present invention is to provide a mechanism that can create a work procedure manual without leaking back work or the like. .

An information processing apparatus according to the present invention includes:
Information that stores multiple types of work, and for each work, other work that is performed when returning to the state before the work is performed is defined as a counter work, and the work definition information from which the work procedure of each work can be derived is stored A storage unit;
Based on the work definition information, the execution procedure of the designated work designated as the execution procedure derivation target among the plurality of kinds of work is derived, and the work of the designated work is extracted, and the pair of the designated work thus extracted is extracted. And an implementation procedure deriving unit that derives the implementation procedure of the work.

  According to the present invention, a plurality of types of work are defined, and for each work, other work performed when returning to the state before the work is performed is defined as a counter work, and a work procedure from which the work execution procedure of each work can be derived Using the definition information, the execution procedure for the designated work is derived, the work for the designated work is extracted, and the execution procedure for the specified work for the specified work is also derived, so the work procedure is not leaked. You can make a letter.

FIG. 3 is a diagram illustrating a configuration example of a work procedure manual creation apparatus according to the first embodiment. FIG. 3 shows an example of a state transition diagram according to the first embodiment. FIG. 4 shows an example of work according to the first embodiment. FIG. 5 shows an example of steps according to the first embodiment. FIG. 3 is a diagram illustrating an example of a state table according to the first embodiment. FIG. 3 shows an example of a work table according to the first embodiment. FIG. 4 shows an example of a step table according to the first embodiment. FIG. 3 is a diagram showing an example of a state transition table according to the first embodiment. FIG. 6 is a diagram showing an example of a state transition adjacent route table according to the first embodiment. FIG. 6 is a flowchart showing an operation example of a work execution procedure manual output unit according to the first embodiment. FIG. 4 is a flowchart showing an operation example of a work return procedure manual output unit according to the first embodiment. FIG. 6 is a flowchart showing an operation example of a work procedure manual output unit according to the first embodiment. FIG. 4 is a flowchart showing an operation example of a step check unit according to the first embodiment. The figure which shows the example of the step table with an error which concerns on Embodiment 1. FIG. The figure which shows the example of the step table with an error which concerns on Embodiment 1. FIG. The figure which shows the example of the work table with an error which concerns on Embodiment 1. FIG. FIG. 4 is a diagram illustrating a configuration example of a work procedure manual creation apparatus according to a second embodiment. FIG. 6 shows an example of a state transition diagram according to the second embodiment. FIG. 10 shows an example of steps according to the second embodiment. FIG. 10 is a diagram illustrating an example of a state table according to the second embodiment. FIG. 9 shows an example of a work table according to the second embodiment. FIG. 6 shows an example of a step table according to the second embodiment. The figure which shows the example of the state transition table which concerns on Embodiment 2. FIG. The figure which shows the example of the state transition adjacent route table which concerns on Embodiment 2. FIG. The figure which shows the example of the state transition path | route preservation | save table which concerns on Embodiment 2. FIG. FIG. 9 is a flowchart showing an operation example of a timer unit according to the second embodiment. FIG. 9 is a flowchart showing an operation example of a system change monitoring unit according to the second embodiment. FIG. 9 is a flowchart showing an operation example of a work execution procedure manual output unit according to the second embodiment. FIG. 4 is a flowchart showing an operation example of a work return procedure manual output unit according to the first embodiment. FIG. 3 is a diagram illustrating a hardware configuration example of a work procedure manual creation apparatus according to the first and second embodiments.

Embodiment 1 FIG.
FIG. 1 is an overall configuration diagram showing an overview of a work procedure manual creation apparatus according to the present embodiment.

In FIG. 1, a work procedure manual creation apparatus 1 manages a work procedure manual in steps.
The work procedure manual creation apparatus 1 has target relationship information between steps and execution and confirmation information between steps in step management, and automatically creates a procedure manual for returning the system when creating the work procedure manual. Create
Further, the work procedure manual creation apparatus 1 detects a work procedure omission when a confirmation work for the work is not defined when creating these work procedure manuals.
The work procedure manual creation device 1 is an example of an information processing device.

The work procedure manual creation device 1 is connected to a work ID designation unit 2.
Further, the work procedure manual creation apparatus 1 includes a work execution procedure manual output unit 10, a work return procedure manual output unit 20, a work procedure manual output unit 30, a step check unit 40, and a work procedure manual DB 3.
Hereinafter, each element will be described.

The work ID designation unit 2 designates a work ID.
The work ID designation unit 2 designates a work ID specified by a user of the work procedure manual creation apparatus 1 or a separate program.
For the work ID specified by the work ID specifying unit 2, the work procedure manual creating apparatus 1 creates a work procedure manual.

  When the work ID is designated from the work ID designation unit 2, the work execution procedure manual output unit 10 calls the step check unit 40, and further refers to the work procedure manual DB 3 to acquire information related to the designated work ID. Then, the work procedure manual output unit 30 is called to obtain a paired work ID that is paired with the designated work ID, and the work return procedure manual output unit 20 is called.

  The work return procedure manual output unit 20 acquires information related to the work ID and calls the work procedure manual output unit 30.

  The work procedure manual output unit 30 refers to the work procedure manual DB 3 and outputs steps.

  The work execution procedure manual output unit 10, the work return procedure manual output unit 20, and the work procedure manual output unit 30 are examples of the execution procedure derivation unit.

The step check unit 40 checks that there is no step leakage.
The step check unit 40 is an example of a step determination unit.

The work procedure manual DB 3 stores a plurality of types of information used for creating the work procedure manual.
The work procedure manual DB3 is an example of an information storage unit.

  Here, the outline | summary of operation | movement of the work procedure manual preparation apparatus 1 which concerns on this Embodiment is demonstrated.

The work procedure manual DB 3 stores work definition information.
In the work definition information, multiple types of work to be created in the work procedure manual are defined, and for each work, other work that is performed when returning to the state before the work is performed is defined as a counter work. This is information from which a procedure (execution procedure) necessary for properly performing the work can be derived.
Specifically, the work definition information includes a work table, a step table, a state transition table, and a state transition adjacent path table which will be described later.
Further, the work execution procedure is composed of a combination of a plurality of procedure steps (also simply referred to as steps). The procedural steps are operations and operations actually performed by the worker.
Based on the work definition information, the work execution procedure manual output unit 10 and the work procedure manual output unit 30 designate a designated work (a work designated by the work ID designation unit 2) as a target for derivation of the implementation procedure among a plurality of types of work. The work procedure of the work represented by the ID is derived.
That is, a plurality of procedural steps necessary for performing the designated work are derived together with the execution order.
In parallel, based on the work definition information, the work execution procedure manual output unit 10, the work return procedure manual output unit 20 and the work procedure manual output unit 30 extract the work for the designated work and perform the extracted work The procedure is also derived.
That is, a plurality of procedural steps necessary for carrying out the counter work are derived together with the execution order.
Finally, the work procedure manual output unit 30 outputs a work procedure manual indicating the execution procedure of the designated work and the execution procedure of the counter work.

Further, the step check unit 40 derives the execution procedure of the designated work by the work execution procedure manual output unit 10 and the work procedure manual output unit 30, the work execution procedure manual output unit 10, the work return procedure manual output unit 20, and the work procedure manual. Prior to the derivation of the execution procedure of the counter work by the output unit 30, it is determined whether or not the content of the step table is appropriate.
Although the details will be described later, the step table shows a plurality of procedural steps that are components of the execution procedure of each work, and if appropriate, the relationship between the procedural steps is defined according to a predetermined rule. Yes.
The step check unit 40 analyzes whether or not the relationship between procedure steps is defined according to the rules in the step table, and determines whether or not the step table is in an appropriate state.
More specifically, the step table is defined as a pair of two procedural steps that are performed before and after each other in an appropriate state, and the step check unit 40 is paired with any procedural step. It is analyzed whether there are any procedural steps that are not present and whether two or more procedural steps are duplicated and paired with the same procedural step.
When the step check unit 40 determines that the step table is in an appropriate state, the work execution procedure manual output unit 10 and the work procedure manual output unit 30 use the step table to derive the execution procedure of the designated work. In addition, the work execution procedure manual output unit 10, the work return procedure manual output unit 20, and the work procedure manual output unit 30 derive the execution procedure for the work.
The step table is an example of procedure step information.

  Next, with reference to FIG. 2 and subsequent figures, details of the work procedure manual creation apparatus 1 according to the present embodiment will be described.

FIG. 2 shows an example of a state transition diagram of a system that is a target for creating a work procedure manual.
The system has states of “stop”, “operation”, and “trace collection operation”.
From the “stop” state, a transition to the “operation” state is indicated by the step “activation of programA”.
A transition from the “active” state to the “stopped” state by the step “stop programA” is shown.
This indicates that the state is changed from the “stop” state to the “trace collection operation” state by the step “trace option designation start of programA”.
A transition from the “trace collection operation” state to the “stop” state by “stop programA” is shown.

FIG. 3 is a diagram illustrating an example of a work management structure described in the work procedure manual.
The work is managed by pairing a work for changing the state of the system in a certain direction and a work for changing the state in the opposite direction, paying attention to the state change of the system.
FIG. 3 shows an example of a work management structure related to the system having the state transition shown in FIG.
This indicates that “system stop” paired with “system start” and “programA trace end” paired with “programA trace start” are defined.
That is, after the operation “system activation” is performed, the operation “system stop” is necessary to return to the state before the “system activation”.
In addition, after the operation of “system stop” is performed, the operation of “system start” is necessary to return to the state before the execution of “system stop”.
Thus, “system stop” is a counter work for “system start”, and “system start” is a counter work for “system stop”.
The same applies to “program A trace start” and “program A trace end”.

FIG. 4 is a diagram illustrating an example of a step management structure.
The step focuses on the state transition of the system, the state transition step for actually transitioning the system state, and the confirmation step for confirming whether or not the step may be performed before the step is performed. Divide and manage.
FIG. 4 shows an example of a step management structure related to the system having the state transition shown in FIG.
FIG. 4 shows that “start programA” is performed after “confirm start condition of programA”.
In addition, after “confirmation of programA stop condition” is performed, “stop of programA” is performed.
Further, it is shown that “program A trace option designation start” is performed after “confirmation of program A start condition at the time of program A trace collection” is performed.

The state transition diagram in FIG. 2 is a management category in the system, and the work in FIG. 3 is a management category for the system user (user).
Further, as described above, the work is composed of steps (a confirmation step and a state transition step).
The confirmation step does not affect the state transition of the system.
For this reason, the confirmation step is not described on the state transition diagram of FIG.
On the other hand, the state transition step affects the state transition of the system.
For this reason, the state transition step is described on the state transition diagram of FIG.

FIG. 5 is a diagram showing a system state management structure when the state in the state transition diagram shown in FIG. 2 is stored in the work procedure manual DB.
The state table 100 includes two columns: a state ID for uniquely managing the state of the system and a state name indicating the name of the system state.

FIG. 6 is a diagram showing a work management structure when the work shown in FIG. 3 is stored in the work procedure manual DB 3.
The work table 110 includes a work ID that uniquely manages a work, a work name that indicates the name of the work, a pair work that indicates a pair relationship between the work by the work ID, and a start point of a state transition of the system that occurs due to the work. The column includes a state transition From indicating the state ID and a state transition To column indicating the end point of the state transition of the system generated by the work by the state ID.

FIG. 7 is a diagram showing a management structure of steps when the steps shown in FIG. 4 are stored in the work procedure manual DB 3.
The step table 120 includes a step ID for uniquely managing a step, a step content indicating the content of the step, and a pre-execution that specifies the step number when there is a step that must be performed before the step is performed. It consists of a column of step ID and a step type column indicating that the type is either C indicating that the step is a confirmation step or A indicating that the step is a state transition step.

FIG. 8 is a diagram showing a management structure for system state transition when the state transition in the state transition diagram shown in FIG. 2 is stored in the work procedure manual DB 3.
The state transition table 130 includes a state transition destination column indicating a system state ID, a step ID, and a state transition destination by the state ID.
The state transition table 130 is managed by a concatenated key of state ID and step ID.

FIG. 9 is a diagram showing a management structure of adjacent paths between system states when the state transition in the state transition diagram shown in FIG. 2 is stored in the work procedure manual DB 3.
The state transition adjacent route table 140 includes columns of an adjacent route ID, a state ID From indicating the state transition start point by the state ID, and a state ID To indicating the end point of the state transition by the state ID.

FIG. 10 is a flowchart showing the processing of the work execution procedure manual output unit 10 in the work procedure manual creation device 1.
Here, the operation will be described using a case in which the work execution procedure manual output unit 10 is called by specifying work ID = 3.

In step S <b> 101, the work execution procedure document output unit 10 receives work ID = 3 from the work ID designation unit 2.
In step S102, the work execution procedure document output unit 10 creates a new stack 1.
In step S <b> 103, the work execution procedure manual output unit 10 calls the step check unit 40.
In step S104, the result of calling the step check unit 40 is determined.
If the response from the step check unit 40 is normal, the process proceeds to step S105, and if abnormal, the process proceeds to step S106.
As will be described later, a normal response is obtained from the step check unit 40 in this case.

In step S105, the work execution procedure manual output unit 10 retrieves the work ID = 3 from the work ID column of the work table 110, and collects the variable A = programA trace for the work name, the work against, the state transition From, and the state transition To. Start, set variable B = 4, variable C = 2, variable D = 3.
In step S <b> 107, the work execution procedure manual output unit 10 performs a route search for the steps from the state transition adjacent route table 140 to the state transition To from the state transition adjacent route table 140 to the variable C = 2, the variable D = 3, and the result. The state transition order (2, 1, 3) is set in the stack 1.
As a route search method, there are methods such as backtracking and width-first search.
In step S108, the work execution procedure manual output unit 10 calls the work procedure manual output unit 30, and passes variable A = programA trace collection start and stack 1 = (2, 1, 3).
In step S109, the work execution procedure manual output unit 10 calls the work return procedure manual output unit 20 with the variable B = 4 as an argument.

FIG. 11 is a flowchart showing the process of the work return procedure manual output unit 20 in the work procedure manual creation apparatus 1.
Here, as described above, the operation will be described using a case where the variable B = 4 is designated and the work return procedure manual output unit 20 is called.

In step S <b> 201, the work return procedure manual output unit 20 creates a new stack 2.
In step S <b> 202, the work return procedure manual output unit 20 searches the work ID column of the work table 110 for work ID = variable B = 4.
In step S203, the work return procedure manual output unit 20 determines whether there is a matching line.
If there is a matching line, the process proceeds to step S204.
If there is no matching line, the process proceeds to step S205.
In this case, since there is a matching line, the process proceeds to step S204.

In step S204, the work return procedure manual output unit 20 sets a cursor on the corresponding line, and sets the work name, the state transition From, and the state transition To for the variable E = programA trace collection end, the variable F = 3, and the variable G = 2. Set.
In step S206, the work return procedure document output unit 20 searches for a route from the state transition From to the state transition To in the variable F = 3, the variable G = 2, and the state transition adjacent route table 140, and the result is the result. Step order (3, 1, 2) is set in stack 2.
As a route search method, there are methods such as backtracking and width-first search.
In step S207, the work return procedure manual output unit 20 calls the work procedure manual output unit 30, and passes variable E = programA trace collection end and stack 2 = (3, 1, 2).

FIG. 12 is a flowchart showing the process of the work procedure manual output unit 30 in the work procedure manual creation apparatus 1.
Here, as described above, the operation will be described using a case in which the work procedure manual output unit 30 is called by specifying variable = programA trace collection start and stack = (2, 1, 3).

In step S301, the work procedure manual output unit 30 newly creates the stack 3 and the FIFO buffer 1.
In step S302, the work procedure manual output unit 30 sequentially reads two state IDs from the transferred stack = (2, 1, 3), sets the variables to H = 3 and I = 1, and then stacks them. Delete from above.
As a result, the passed stack becomes (2).
In step S303, the work procedure manual output unit 30 searches the state transition table 130 for a row where state ID = variable I = 1, state transition destination = variable H = 3, and reads step ID = 6 from the corresponding row. , Set to stack 3.
As a result, stack 3 = (6).
In step S304, the work procedure manual output unit 30 determines whether or not the passed stack is empty.
If it is empty, the process proceeds to step S305. If it is not empty, the process proceeds to step S306.
Since the passed stack is (2) and is not empty, the process proceeds to step S306.
In step S306, variable I = 1 is set to variable H, and variable H = 1.
Further, the work procedure manual output unit 30 reads one from the transferred stack, sets the variable I = 2, and deletes it from the transferred stack.
As a result, the passed stack becomes (empty).
In step S303, the work procedure manual output unit 30 searches the state transition table 130 for a row where state ID = variable I = 2, state transition destination = variable H = 1, and reads step ID = 2 from the corresponding row. , Set to stack 3.
As a result, stack 3 = (6, 2).
In step S304, since the passed stack is empty, the process proceeds to step S305.

In step S305, the work procedure manual output unit 30 reads one step ID from the stack 3 = (6, 2), sets the variable J = 2, and deletes it from the stack 3.
As a result, stack 3 = (6).
In addition, the work procedure manual output unit 30 searches the step ID column of the step table 120 and advances the cursor to a line that matches the variable J = 2.
In step S307, the work procedure manual output unit 30 determines whether the step type of the row is A.
If it is A, the process proceeds to step S308, and if it is different from A, the process proceeds to step S309.
In this case, since it is A, the process proceeds to step S308.
In step S <b> 308, the work procedure manual output unit 30 sets the pre-execution step ID = 1 of the row in the FIFO buffer 1.
As a result, the FIFO buffer 1 becomes (1).
If the process proceeds to step S309, an abnormal return is performed.
In step S310, the work procedure manual output unit 30 sets the variable J = 2 in the FIFO buffer 1 that has been passed.
As a result, the FIFO buffer 1 becomes (1, 2).
In step S311, the work procedure manual output unit 30 determines whether the stack 3 is empty.
If the stack 3 is empty, the process proceeds to step S312, and if not, the process proceeds to step S305.
Since stack 3 = (6), the process proceeds to step S305.
In step S305, one step ID is read from stack 3 = (6), set to variable J = 6, and then deleted from the stack 3.
As a result, stack 3 = (empty).
In addition, the work procedure manual output unit 30 searches the step ID column of the step table 120 and advances the cursor to a line that matches the variable J = 6.
In step S307, since the step type is A, the process proceeds to step S308.
In step S <b> 308, the work procedure manual output unit 30 sets the pre-execution step ID = 5 of the row in the FIFO buffer 1.
As a result, the FIFO buffer 1 becomes (1, 2, 5).
In step S310, the work procedure manual output unit 30 sets the variable J = 6 in the FIFO buffer 1 that has been passed.
As a result, the FIFO buffer 1 becomes (1, 2, 5, 6).
In step S311, the work procedure manual output unit 30 determines whether the stack 3 is empty.
Since the stack 3 is empty, the process proceeds to step S312.
In step S312, the work procedure manual output unit 30 sequentially reads from the FIFO buffer 1 = (1, 2, 5, 6) as the work procedure manual for the passed variable = programA trace collection start, and on the corresponding step table 120 The contents of the step are output.
In step S313, a normal return is performed.

In FIG. 12, in the case where the variable = programA trace collection end, the stack = (3, 1, 2) is specified and the work procedure manual output unit 30 is called, the same processing as above is performed, and as a result, up to step S312. Then, FIFO buffer 1 = (1, 2, 3, 4) is created.
In step S312, FIFO buffer 1 = (1, 2, 3, 4) is sequentially read out as the work procedure manual for the passed variable = programA trace collection end, and the step contents on the corresponding step table 120 are output.
In step S313, a normal return is performed.

  As described above, the work procedure indicating the execution procedure of the designated work designated by the work ID designation unit 2 (step contents on the step table 120) and the execution procedure of the designated work versus the work (step contents on the step table 120) are shown. Is output.

Next, an operation example of the step check unit 40 will be described.
FIG. 13 is a flowchart showing the process of the step check unit 40 in the work procedure manual creation apparatus 1.

In step S401, the step check unit 40 sets 1 to the variable H.
In step S <b> 402, the step check unit 40 determines whether or not there is a row that matches the variable H = 1 in the step ID column of the step table 120.
If there is a matching line, the process proceeds to step S403.
If there is no matching line, the process proceeds to step S404.
From FIG. 8, since there is a row with step ID = 1, the process proceeds to step S403.
In step S403, the step check unit 40 sets a cursor on the line.
In step S405, the step check unit 40 determines whether the step type of the row is A.
If it is A, the process proceeds to step S406.
If not A, the process proceeds to step S414.
In FIG. 8, since the step type of the row is C, the process proceeds to step S414.
In step S414, the variable H is incremented so that the variable H = 2.
In step S <b> 402, the step check unit 40 determines whether there is a row that matches the variable H = 2 in the step ID column of the step table 120.
Since there is a matching line, in step S403, the cursor is set on the line.
In step S405, since the step type is A, the process proceeds to step S406.
In step S406, it is determined whether the pre-execution step ID of the row is defined.
If so, the process proceeds to step S407. If not, the process proceeds to step S408.
Since the advance execution step ID = 1 is defined, the process proceeds to step S407.
In step S407, the step check unit 40 sets the pre-execution step ID = 1 to the variable I = 1.
In step S409, the step check unit 40 searches the step ID column of the step table 120 for a line that matches the variable I = 1.
In step S410, it is determined whether there is a matching line.
If there is a matching line, the process proceeds to step S411. If there is no matching row, the process proceeds to step S408.
Here, since there is a matching line, the process proceeds to step S411.
In step S411, it is determined whether the step type of the row is C.
If the step type of the row is C, the process proceeds to step S412.
If the step type is not C, the process proceeds to step S408.
Since the step type of the row is C, the process proceeds to step S412.
In step S412, the step check unit 40 searches the pre-execution step ID column of the step table 120 for a line that matches the variable I = 1.
However, the line indicated by the variable H is excluded.
In step S413, the step check unit 40 determines whether there is a matching row.
If there is no matching row, the process proceeds to step S414.
If there is a matching line, the process proceeds to step S408.
Since there is a matching line, the process proceeds to step S414.
In step S414, the variable H is incremented so that the variable H = 3.
Thereafter, the same processing is repeated, and when the variable H = 7, in step S402, since there is no line that matches the variable H = 7 in the step ID column of the step table 120, the process proceeds to S404.
In step S404, a normal return is performed.

FIG. 14 shows a step table 200 (step table with an error) that is different from the step table 120 of FIG.
In the step table 200, the prior execution step ID at step ID = 6 is not designated.
In this case, the step check unit 40 determines in step S406 of FIG. 13 that the pre-execution step ID is not defined, and proceeds to step S408.
In step S408, an abnormal return is performed.
As a result, in step S104 of FIG. 10, it is determined that the normal return has not been performed, and the process proceeds to step S106. In step S106, an abnormality is output.

FIG. 15 shows a step table 210 (step table with an error) that is different from the step table 120 of FIG.
In the step table 210, the pre-execution step ID at step ID = 5 is specified as 3, and the same pre-execution step ID as the step at step ID = 4 is specified.
In this case, the step check unit 40 determines in step S413 in FIG. 13 that there is a matching row, and proceeds to step S408.
In step S408, an abnormal return is performed. As a result, in step S104 of FIG. 10, it is determined that the normal return has not been performed, and the process proceeds to step S106.
In step S106, an abnormality is output.

FIG. 16 shows a work table 220 (work table with errors) that is different from the work table 110 of FIG.
In the work table 220, there are 4 tasks for work ID = 3, but this procedure is not defined.
In this case, the work return procedure manual output unit 20 determines in step S203 of FIG. 11 that there is no matching line, and proceeds to step S205.
In step S205, an abnormality is output.

  As described above, the step check unit 40 checks whether there is any omission of a procedure, and the work return procedure manual output unit 20 creates a work return procedure manual together with the work execution procedure manual.

  As described above, after confirming the status of the system, the work execution procedure document that allows the work to be carried out without omission of the work confirmation procedure, and the return work for returning the system status change caused by the execution of the work to the original state. A work return procedure manual showing the procedure can be automatically created.

As described above, in the present embodiment,
When creating a work procedure manual, it is necessary to check that the conditions for performing the steps that make up the work are satisfied, and check that the different steps do not specify the same confirmation procedure. The work procedure manual creation support system to prevent the problem was explained.

  Further, it has been described that the work procedure manual creation support system according to the present embodiment checks for omissions in the return work procedure when the work procedure manual is created.

Embodiment 2. FIG.
In the present embodiment, an example will be described in which a work procedure manual is automatically created when the system is changed, thereby effectively preventing leakage of the work procedure manual itself.
That is, in the first embodiment, the work ID is specified and the work procedure manual is output, but in this embodiment, the work procedure manual DB is rewritten when the system is changed. , How to re-output only the procedure that is affected by the change.
The same parts as those of the first embodiment shown in FIG. 1 are denoted by the same reference numerals, and detailed description of the overlapping parts is omitted.

In FIG. 17, when the work procedure manual DB 3 is rewritten by the system change input unit 4, the work procedure manual creation apparatus 1 a outputs a work that is affected by the rewriting.
The state transition path storage DB 5 stores system state transition information when the same procedure as the work ID is executed.
After calling the step check unit 40, the work execution procedure manual output unit 10a refers to the work procedure manual DB 3, obtains information related to the designated work ID, stores it in the state transition path storage DB 5, and stores the work procedure manual. The output unit 30 is called, a work ID that is paired with the specified work ID is acquired, and the work return procedure manual output unit 20a is called.
The work return procedure manual output unit 20a acquires information related to the work ID, stores it in the state transition path storage DB 5, and calls the work procedure manual output unit 30.
The work procedure manual output unit 30 refers to the work procedure manual DB 3 and outputs steps.
The step check unit 40 checks that there is no step leakage.

The system change monitoring unit 50 is periodically activated by the timer unit 60.
The timer unit 60 activates the system change monitoring unit 50 at regular intervals.
The system change monitoring unit 50 compares the state transition information in the state transition path storage DB 5 with the state transition created by referring to the work procedure manual DB 3, and if there is a difference, calls the work execution procedure manual output unit 10 a. .
That is, the system change monitoring unit 50 analyzes the work definition information (work table, step table, state transition table, state transition adjacent route table), and the execution procedure may have changed as a result of the work definition information being changed. A certain work is extracted, and the extracted work is designated as a designated work.
Then, the work execution procedure manual output unit 10a, the work return procedure manual output unit 20a, and the work procedure manual output unit 30 are similar to those in the first embodiment, and the execution procedure of the designated work specified by the system change monitoring unit 50, Derive the execution procedure for the designated work.
The system change monitoring unit 50 is an example of an information analysis unit.

FIG. 18 shows an example of a state transition diagram of a system in which a state adding change is applied to the system shown in FIG.
The system has the statuses “stopped”, “running”, “trace collection running”, and “intermediate running”.
From the “stop” state, the transition to the “intermediate operation” state is indicated by the step “activation of programA”.
A transition from the “intermediate operation” state to the “stop” state by the step “stop programA” is shown.
This indicates that the state is changed from the “stop” state to the “trace collection operation” state by the step “trace option designation start of programA”.
A transition from the “trace collection operation” state to the “stop” state by “stop programA” is shown.
A transition from the “intermediate operation” state to the “operation” state is indicated by the step “activation of programB”.
A transition from the “operating” state to the “intermediate operating” state is indicated by the step “stop program B”.

FIG. 19 is a diagram illustrating an example of a step management structure.
FIG. 19 shows an example of a step management structure related to the system having the state transition shown in FIG.
It shows that "stop of programA" can be performed after "confirmation of stop condition of programA" is performed. This indicates that “program A start” can be performed after “confirm start condition of program A”.
It shows that “programA trace option designation start” can be performed after “confirmation of programA start condition when collecting programA trace”.
It shows that “stop of program B” can be performed after “confirmation of stop condition of program B”. This indicates that “program B can be started” after “program B start condition is confirmed”.

  FIG. 20 is a diagram showing a system state management structure when the state in the state transition diagram shown in FIG. 18 is stored in the work procedure manual DB 3.

  FIG. 21 is a diagram showing a work management structure when the work shown in FIG. 3 is stored in the work procedure manual DB 3, and the system work, the state transition From, and the state transition represented by the state transition diagram of FIG. 18. Contains the value of To.

  FIG. 22 is a diagram showing a management structure of steps when the steps shown in FIG. 19 are stored in the work procedure manual DB 3.

  FIG. 23 is a diagram showing a system state transition management structure when the state transitions in the state transition diagram shown in FIG. 18 are stored in the work procedure manual DB 3.

  FIG. 24 is a diagram showing a management structure of adjacent paths between system states when the state transitions in the state transition diagram shown in FIG. 18 are stored in the work procedure manual DB 3.

FIG. 25 is a diagram showing a state transition path management structure when the procedure shown in FIG. 3 is stored in the state transition path storage DB 5.
It consists of a work ID string and a state transition path string formed by listing a series of state IDs.
In the following, the work procedure manual creating apparatus 1a that created the work procedure manual for the system shown in FIG. 2 will be described in the case where the target system has been changed and changed as shown in FIG.

FIG. 26 is a flowchart showing the process of the timer unit 60 in the work procedure manual creating apparatus 1a.
In step S801, the system change monitoring unit execution interval n [minutes] is set in the variable M.
Here, n = 5 is designated. In step S802, sleep is performed for 5 minutes. In step S803, the system change monitoring unit 50 is activated.

FIG. 27 is a flowchart showing the process of the system change monitoring unit 50 in the work procedure manual creating apparatus 1a.
In S701, the system change monitoring unit 50 sets 1 to the variable J.
In step S <b> 702, the system change monitoring unit 50 searches the work ID column of the state transition path storage table 350 for a line that matches the variable J = 1.
In step S703, the system change monitoring unit 50 determines whether there is a matching row.
If there is a matching line, the process proceeds to step S704.
If there is no matching row, the process proceeds to step S705.
In step S704, the system change monitoring unit 50 reads the value of the state transition path column of the matching row and sets the variable K = (1, 2).
In step S706, the system change monitoring unit 50 searches the work ID column of the work table 310 for the variable J = 1.
In step S707, the system change monitoring unit 50 sets the value of the state transition From column and the value of the state transition To column of the row to variable L = 1 and variable M = 4.
In step S708, the system change monitoring unit 50 performs a route search for the variable L = 1, the variable M = 4, and the state transition sequence from the state transition adjacent route table 340 to the state transition To, and the result is the result. The state transition order (1, 2, 4) is set to the variable N.
In step S709, the system change monitoring unit 50 determines whether the values of the variable K = (1,2) and the variable N = (1,2,4) match.
If they match, the process proceeds to step S710, and if they do not match, the process proceeds to step S711.
Since this case does not match, the process proceeds to step S711.
In step S711, the system change monitoring unit 50 calls the work execution procedure document output unit 10a and passes the variable J = 1.
In step S710, the system change monitoring unit 50 increments the variable J to become the variable J = 2, and proceeds to step S702.
Thereafter, when the variable J = 5 in step S710, it is determined in step S703 that there is no matching row, and the process proceeds to step S705.
In step S705, the process of the system change monitoring unit 50 ends.

FIG. 28 is a flowchart showing the process of the work execution procedure manual output unit 10a in the work procedure manual creation device 1a.
Here, the operation will be described using a case where work ID = 1 is designated and the work execution procedure document output unit 10a is called.

In step S101, the work execution procedure manual output unit 10a receives work ID = 1.
In step S102, the work execution procedure document output unit 10a creates a new stack 1.
In step S103, the work execution procedure manual output unit 10a calls the step check unit 40.
In step S104, the work execution procedure document output unit 10a determines the result of calling the step check unit 40.
If the response from the step check unit 40 is normal, the process proceeds to step S105, and if abnormal, the process proceeds to step S106.
In this case, a normal response is obtained from the step check unit 40.
In step S105, the work execution procedure document output unit 10a retrieves the work ID = 3 from the work ID column of the work table 310, and sets the work name, the counter work, the state transition From, and the state transition To, respectively, by variable A = system activation, Variable B = 2, variable C = 1, and variable D = 4 are set.
In step S107, the work execution procedure document output unit 10a performs route search for the steps from the state transition From to the state transition To in the variable C = 1, the variable D = 4, and the state transition adjacent route table 340, and the result is the result. The state transition order (1, 2, 4) is set in the stack 1.
As a route search method, there are methods such as backtracking and width-first search.
In step S108, the work execution procedure manual output unit 10a calls the work procedure manual output unit 30, and passes variable A = system activation and stack 1 = (1, 2, 4).
In step S109a, the work return procedure manual output unit 20a is called with the variable B = 2 as an argument.
In step S501, the work execution procedure document output unit 10a overwrites the existing work ID line data in the state transition path storage table 350 with work ID = 1 and stack 1 = (1, 2, 4).

FIG. 29 is a flowchart showing the process of the work return procedure manual output unit 20a in the work procedure manual creation apparatus 1a.
Here, the operation will be described using a case in which the variable B = 2 is designated and the work return procedure manual output unit 20a is called.

In step S201, the work return procedure manual output unit 20a creates a new stack 2.
In step S202, the work return procedure manual output unit 20a searches the work ID column of the work table 310 for work ID = variable B = 2.
In step S203, the work return procedure manual output unit 20a determines whether there is a matching line.
If there is a matching line, the process proceeds to step S204.
If there is no matching line, the process proceeds to step S205.
In this case, since there is a matching line, the process proceeds to step S204.
In step S204, the cursor is set on the corresponding line, and the work name, state transition From and state transition To are set to variable E = system stop, variable F = 4, and variable G = 1, respectively.
In step S206, a route search is performed for the step from the state transition From to the state transition To in the variable F = 4, the variable G = 1, and the state transition adjacent route table 340, and the resulting step order (4, 2, 1). Is set on stack 2.
As a route search method, there are methods such as backtracking and width-first search.
In step S207, the work return procedure manual output unit 20a calls the work procedure manual output unit 30, and passes variable E = system stop and stack 2 = (4, 2, 1).
In step S601, the work return procedure manual output unit 20a overwrites the existing work ID line data in the state transition path storage table 350 with the work ID = 2 and the stack 2 = (4, 2, 1).

As shown in FIG. 12, the work procedure manual output unit 30 receives variable = 1 and stack 1 = (1, 2, 4) and variable = 2 and stack 2 = (4, 2, 1), and receives them. Outputs the corresponding work procedure manual.
Similarly, variables = 3 and stack 1 = (4, 2, 1, 3) and variables = 4 and stack 2 = (3, 1, 2, 4) are received, and work procedures corresponding to them are received. Output the document.

  The operation of the step check unit 40 according to the present embodiment is the same as that of the first embodiment, but the table that is the target of the step check is the step table 320 in FIG.

  In the present embodiment, as described above, the timer unit 60 and the system change monitoring unit 50 create a work procedure manual in a range where the system has been changed based on the system change information input from the system change input unit 4. To do.

  As described above, after performing the work to change the system, undo the change, and when performing the work, after confirming the system status, the work confirmation procedure is leaked. No work procedure manual can be created automatically.

  As described above, the present embodiment has described the work procedure manual creation support system that creates a work procedure manual that is affected by the input of system change information.

Finally, a hardware configuration example of the work procedure manual creation apparatus 1 shown in the first and second embodiments will be described.
FIG. 30 is a diagram showing an example of hardware resources of the work procedure manual creation apparatus 1 shown in the first and second embodiments.
30 is merely an example of the hardware configuration of the work procedure manual creation device 1, and the hardware configuration of the work procedure manual creation device 1 is not limited to the configuration described in FIG. It may be a configuration.

In FIG. 30, the work procedure manual creation apparatus 1 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, a processing unit, a microprocessor, a microcomputer, and a processor) that executes a program.
The CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
Further, the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907. Further, instead of the magnetic disk device 920, a storage device such as an SSD (Solid State Drive), an optical disk device, or a memory card (registered trademark) read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
The “work procedure manual DB 3” and “state transition path storage DB 5” described in the first and second embodiments are realized by the RAM 914, the magnetic disk device 920, and the like.
A communication board 915, a keyboard 902, a mouse 903, a scanner device 907, an FDD 904, and the like are examples of input devices.
The communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.

  The communication board 915 is connected to a LAN (Local Area Network), the Internet, a WAN (Wide Area Network), a SAN (Storage Area Network), etc., for example.

The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
The programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.

The RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
The RAM 914 stores various data necessary for processing by the CPU 911.

The ROM 913 stores a BIOS (Basic Input Output System) program, and the magnetic disk device 920 stores a boot program.
When the work procedure manual creating apparatus 1 is activated, the BIOS program in the ROM 913 and the boot program in the magnetic disk device 920 are executed, and the operating system 921 is activated by the BIOS program and the boot program.

  The program group 923 stores programs that execute the functions described as “˜units” in the description of the first and second embodiments. The program is read and executed by the CPU 911.

In the file group 924, in the description of the first and second embodiments, “search for”, “set of”, “comparison of”, “evaluation of”, “update of”, “setting of” ”,“ Registration of ”,“ Selection of ”, etc. Information, data, signal values, variable values, and parameters indicating the results of the processing are indicated as“ ˜file ”and“ ˜database ”items. It is remembered.
The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory.
Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit.
The read information, data, signal value, variable value, and parameter are used for CPU operations such as extraction, search, reference, comparison, calculation, calculation, processing, editing, output, printing, and display.
Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
In addition, the arrows in the flowcharts described in the first and second embodiments mainly indicate input / output of data and signals.
Data and signal values are recorded on a recording medium such as a memory of the RAM 914, a flexible disk of the FDD 904, a compact disk of the CDD 905, a magnetic disk of the magnetic disk device 920, other optical disks, a mini disk, and a DVD.
Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

In addition, what is described as “˜unit” in the description of the first and second embodiments may be “˜circuit”, “˜device”, “˜device”, and “˜step”, It may be “˜procedure” or “˜processing”.
That is, the work procedure manual creation apparatus 1 can be grasped as a method by the steps, procedures, and processes shown in the flowcharts described in the first and second embodiments.
Further, what is described as “˜unit” may be realized by firmware stored in the ROM 913.
Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware.
Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD.
The program is read by the CPU 911 and executed by the CPU 911.
That is, the program causes the computer to function as “to part” in the first and second embodiments. Alternatively, the computer executes the procedure and method of “to unit” in the first and second embodiments.

As described above, the work procedure manual creation device 1 shown in the first and second embodiments includes a CPU that is a processing device, a memory that is a storage device, a magnetic disk, a keyboard that is an input device, a mouse, a communication board, and a display device that is an output device. A computer including a communication board and the like.
Then, as described above, the functions indicated as “˜units” are realized using these processing devices, storage devices, input devices, and output devices.

  DESCRIPTION OF SYMBOLS 1 Work procedure manual preparation apparatus, 2 Work ID designation | designated part, 3 Work procedure manual DB, 4 System change input part, 5 State transition path preservation | save DB, 10 Work execution procedure manual output part, 20 Work return procedure manual output part, 30 Work Procedure manual output unit, 40 step check unit, 50 system change monitoring unit, 60 timer unit.

Claims (6)

Information that stores multiple types of work, and for each work, other work that is performed when returning to the state before the work is performed is defined as a counter work, and the work definition information from which the work procedure of each work can be derived is stored A storage unit;
Based on the work definition information, the execution procedure of the designated work designated as the execution procedure derivation target among the plurality of kinds of work is derived, and the work of the designated work is extracted, and the pair of the designated work thus extracted is extracted. An information processing apparatus comprising: an execution procedure deriving unit that derives a work execution procedure. The information processing apparatus further includes:
Analyzing the work definition information, as a result of the work definition information being changed, extracting work that may have changed the implementation procedure, and having an information analysis unit that designates the extracted work as the designated work,
The implementation procedure deriving unit
The information processing apparatus according to claim 1, wherein an execution procedure of a designated work designated by the information analysis unit and an execution procedure of a paired procedure of the designated procedure are derived. The information storage unit
As a part of the work definition information, a plurality of procedural steps that are components of the execution procedure of each work are shown. If they are in an appropriate state, the relationship between the procedural steps is defined according to a predetermined rule. Remembers step information,
The information processing apparatus further includes:
Prior to derivation of the implementation procedure by the implementation procedure derivation unit, the procedure step information is analyzed to determine whether the relationship between the procedure steps is defined according to the rules, and whether the procedure step information is in an appropriate state. A step determining unit for determining,
The implementation procedure deriving unit
When the step determination unit determines that the procedure step information is in an appropriate state, based on the procedure definition information including the procedure step information, the specified procedure execution procedure and the specified procedure execution procedure are performed. The information processing apparatus according to claim 1, wherein a procedure is derived. The information storage unit
If it is in an appropriate state, it stores procedure step information defined by a pair of two procedure steps executed before and after,
The step determination unit
4. The analysis according to claim 3, wherein there is no procedural step that is not paired with any procedural step, and whether or not two or more procedural steps are duplicated and paired with the same procedural step. Information processing device. The information processing apparatus further includes:
2. A work procedure manual output unit that outputs a work procedure manual including an execution procedure of the designated work derived by the execution procedure deriving unit and an execution procedure of a paired procedure of the designated procedure. Information processing apparatus in any one of -4. A computer that stores work definition information in which multiple types of work are defined, and for each work, other work performed when returning to the state before the work is performed is defined as a counter work, and the execution procedure of each work can be derived In addition,
Based on the work definition information, a process for deriving an implementation procedure of a designated task designated as an implementation procedure derivation target among the plurality of types of tasks;
A program that extracts a work for the designated work based on the work definition information, and executes a process for deriving an execution procedure of the extracted work for the designated work.

Images