JP2021105797A - Manual creation device and method thereof - Google Patents

Abstract

To solve the problem in which: according to the conventional art, when it is necessary to correct a manual for business use, it is necessary to completely revise the manual, and it took time and effort to create it.SOLUTION: A manual creation device 10 in accordance with the present invention includes: a manual template generation unit 1021 that creates a blank manual template using a new business flow 1033; a business flow difference analysis unit 1022 that compares an old business flow 1031 and the new business flow 1033 corresponding to each other to identify a correspondence relationship of each of a plurality of tasks constituting the business flows by the comparison, and determines whether or not there is transcription of contents of the tasks included in the old manual 1032 according to a matching status of the correspondence relationship of each task based on the identified result; and a manual transcription unit 1023 that copies the contents of the old manual 1032 to the blank manual template based on the determined result.SELECTED DRAWING: Figure 2

Description

The present invention relates to a technique for generating a manual. Among them, in particular, it relates to a technique for generating a manual for executing a business and a manual template for generating the manual.

Currently, manuals are used to carry out business. For example, when applying for a business trip or reimbursing travel expenses within a company, the application and clearing work flows according to the business flow (business content) in which the business traveler applies and the superior approves. In this example, in order for an employee to apply for a business trip or settle travel expenses, it is necessary to create a manual that records the above contents.

Patent Document 1 and Patent Document 2 have been proposed as techniques for creating such a manual.

In Patent Document 1, in order to automatically generate a business manual having a standard configuration for each user system, parameter information consisting of a skeleton name, a job control language macro name, a screen name, etc. used in each user system is created and registered. At the same time, create and register comments, processing explanations, etc. that you want to describe in the business manual as a document using the word processor function.
Based on the parameter information and documents registered by this parameter information registration means, a business manual with a standard configuration corresponding to each user system is created.

In Patent Document 2, in order to create a business manual that can be provided online from the information created when constructing a business processing system, a term dictionary is searched, a guidance screen is generated from the searched information, and a terminal device is used. By memorizing the operation history in, it is possible to grasp the information requested by the user and provide an easy-to-use business manual for each user.

Japanese Unexamined Patent Publication No. 4-182856 Japanese Unexamined Patent Publication No. 8-212161

Here, the business flow recorded in the manual is not fixed permanently and may be modified for some reason. For example, the version of the business system for business is upgraded, the business flow is changed due to the revision of rules, and the business name and department are revised due to the reorganization of the organization.

Patent Documents 1 and 2 support the creation of business manuals, but do not consider changes in business flow. Therefore, in these Patent Documents 1 and 2, when the business flow is changed, the content cannot be appropriately reflected in the manual. Further, when the manuals are modified according to the change of the business flow by using the techniques of Patent Documents 1 and 2, it is necessary to modify or newly create all the manuals, which is a problem that the labor and burden are enormous. There is also.

In order to solve the above problems, in the present invention, the difference in the business flow due to the business change is processed as follows. A manual template is generated by associating and posting using it according to the relationship of the number of tasks among the completely matched tasks that compose the business flow.

As one aspect of the present invention, in a manual generator that generates a manual template for a manual showing the contents of the business in accordance with the change of the business, the old business flow showing the business flow before the change of the business and having a plurality of tasks. , A blank manual template is created using the new business flow that shows the business flow after the change of the business and has a plurality of tasks, the storage unit that stores the old manual that is the manual before the change of the business, and the new business flow. The manual template generation unit to be created is compared with the old business flow and the new business flow corresponding to each other, and the correspondence of each of the plurality of tasks constituting the business flow is specified by the comparison, and the identified result. Based on the business flow difference analysis unit that determines the matching status of the correspondence of each task and determines whether or not the contents of the tasks included in the old manual have been transcribed according to the matching status, and the determined result. Includes a manual generator having a manual transcription unit that generates a new manual template according to a change in the business by transcribing the contents of the tasks of the old manual to the blank manual template, and a method using the manual. Is done. Further, the present invention also includes a program product (including a medium) that executes the above processing.

According to the present invention, it is possible to efficiently create a manual or a manual template in accordance with a change in a business flow.

The figure which shows the outline of making the manual template and the new manual in one Example of this invention. Configuration diagram of the manual generator according to an embodiment of the present invention A flowchart showing the entire processing of the manual generator according to the embodiment of the present invention. The figure which shows the content of the new business flow in one Example of this invention The figure which shows the separate volume information used in one Example of this invention. The figure which shows the processing outline of the business analysis part in one Example of this invention (the 1) The figure which shows the processing outline of the business analysis part in one Example of this invention (the 2) The figure which shows the processing outline of the business analysis part in one Example of this invention (the 3) The figure which shows the processing of the manual transcription part in one Example of this invention. Flow chart showing details of processing of manual template generation unit in one embodiment of the present invention The figure for demonstrating the processing of the business flow difference analysis part in one Example of this invention. Flow chart showing details of processing of business flow difference analysis unit in one embodiment of the present invention Specific Examples for Explaining Step S107-3 in One Example of the Invention Specific Examples for Explaining Step S107-8 in One Example of the Present Invention Specific Example for Explaining Step S107-11 in One Example of the Present Invention (Part 1) Specific Example for Explaining Step S107-11 in One Example of the Present Invention (Part 2) Specific Examples for Explaining Step S107-14 in One Example of the Invention

Hereinafter, examples will be described with reference to the drawings. First, FIG. 1 shows an outline of creating a manual template and a new manual in this embodiment. In this embodiment, the manual generator 10 is used when a manual is created or modified due to a change in business. The manual generation device 10 creates a blank manual template, and generates a new manual template in which the divertable contents of the old manual before the change are transcribed according to the comparison result of the tasks of the old and new business flows. .. Then, the manual generator 10 completes the new manual by performing an operation on the new manual template from the user and making adjustments according to the input.
(Configuration of Manual Generator 10)
Next, the configuration of the manual generator 10 will be described with reference to FIG. The manual generator 10 is realized by a so-called computer and has the following configuration. It has a control unit 101 realized by a CPU or the like, a main storage unit 102 realized by a memory or the like, a sub storage unit 103 in which various information is stored, and a communication unit 104 connected to the network 20. Further, in the manual generator 10 of this embodiment, it is preferable to connect or hold the display device 105 that outputs the processing result of the manual generator 10 and the input device 106 that inputs to the manual generator 10. .. When the manual generator 10 is used as a single unit (so-called stand-alone), the communication unit 104 may be omitted. Further, the sub-storage unit 103 may be configured in a housing separate from the manual generator 10.

Further, it may be connected to the terminal device 30 which is a computer via the network 20. In this case, the manual generator 10 functions as a server, and the result is presented to the terminal device 30. In this case, the display device 105 and the input device 106 can be omitted.

The main storage unit of the manual generation device 10 includes a manual template generation unit 1021 realized as a program, a business flow difference analysis unit 1022, and a manual transcription unit 1023. The control unit 101 performs the processing of this embodiment by executing the calculation according to each of these programs. Details of these processes will be described later with reference to flowcharts (FIGS. 3, 10, and 12). Further, the manual template generation unit 1021, the business flow difference analysis unit 1022, and the manual transcription unit 1023 may be realized as hardware instead of a program, so-called software. Further, the manual template generation unit 1021, the business flow difference analysis unit 1022, and the manual transcription unit 1023 can be realized by an integrated program.

The sub-storage unit 103 contains an old business flow 1031 indicating the business flow before the change, an old manual 1032 corresponding to the old business flow 1031, a new business flow 1033 indicating the changed business, a created manual template 1034, and a business flow. Business flow to store the contents analyzed by the difference analysis unit 1022 Manual template posting result 1036, which is the result of transcribing the contents of the old manual 1032 to the difference 1035 and the manual template 1034, that is, the new manual or the new template is stored. do. The contents of each of these pieces of information will be described later.
(Processing of manual generator 10 (overall))
Next, the entire process of the manual generator 10 of this embodiment will be described with reference to FIG.

When the generation of the business flow is started, in step S101, the manual template generation unit 1021 determines whether the generation target input from the user via the input device 106 is a new business or a reuse of the old manual 1032. This determination may be made based on an instruction via the input device 106, or may be determined by searching for a designated business name and determining whether the corresponding old manual 1032 is stored in the sub-storage unit 103. In the latter case, if it is searched, it is judged as "reuse", and if it is not searched, it is judged as "new".

If the result of step S101 is determined to be new, the process proceeds to step S102. In step S102, the manual template generation unit 1021 generates a blank manual template, which is a kind of manual template 1034, according to the new business flow 1033 stored in the sub storage unit 103. Here, the new business flow 1033 is information specified based on an instruction of the input device 106 or the like, and is searched from the sub-storage unit 103.

Then, in step S103, the display device 105 outputs the generated blank manual template, and ends the process. Here, since the content of S102 overlaps with step S104, it will be described together with step S104.

Further, in step S101, if it is determined to be reused, the process proceeds to step S104. In step S104, the manual template generation unit 1021 uses the new business flow 1033 stored in the sub-storage unit 103 to create a blank manual template (for example, the separate volume information shown in FIG. 5B is merged for each department). To generate. This process has the same contents as in step S102. Details of this process will be described later with reference to FIG.

Next, in step S105, the business flow difference analysis unit 1022 performs shaping processing on each of the new business flow 1033 and the old business flow 1031. This is a pre-processing for the comparison processing in step S107 together with the subsequent step S106.

Here, in the notation such as BPMN used in this embodiment, the business flow information is often character information such as XML. In this case, it is conceivable to take a Diff for the character information to find out the difference in the business flow. However, since character information such as XML is automatically generated by the business flow editing tool, even if the business flow is edited a little, the order may change significantly or information such as the position when drawing may be retained. And it's likely that there will be more Diffs than the essential changes. Therefore, in this embodiment, in order to extract the difference more preferably, a method of comparing the structure of the business flow is adopted. The details of the shaping process (S105) for this purpose will be described below.

First, the business flow difference analysis unit 1022 removes the branch from the object of the new business flow 1033. Specifically, the object "x" is removed from FIG. 6A and converted into the information shown in FIG. 6B.

Next, the business flow difference analysis unit 1022 further adds the corresponding department information to each task, and deletes the swim lane (department information). Specifically, the conversion from FIG. 7A to FIG. 7B is performed.

Further, the processing of step S105 is also applied to the old business flow 1031 (before the change) corresponding to the new business flow 1033 to be processed. However, the old business flow 1031 may be subjected to the same processing when the old business flow 1031 is created or modified, or may be combined with the processing for the new business flow 1033. That is, the timing of the shaping process of the old business flow 1031 and the shaping process of the new business flow 1033 may be different. In this case, the old business flow 1031 that has undergone the shaping process is stored in the sub-storage unit 103, and is used in the process of step S106 or less.

With the above, the process of step S105 is completed, and the process proceeds to step S106.

Next, in step S106, the business flow difference analysis unit 1022 adds a start task and an end task to the result of step S105. This is applied to both the old business flow 1031 and the new business flow 1033. Specifically, the conversion from FIG. 8 (a) to FIG. 8 (b) is performed. The old business flow 1031 may be applied at a timing different from that of the new business flow 1033, such as when the old business flow 1031 is generated (modified). Further, steps S105 and S106 may be executed together with respect to the old business flow 1031 and stored in the sub-storage unit 103. Further, the order of steps S105 and S106 does not matter.

Next, in step S107, the business flow difference analysis unit 1022 compares the result of step S106, that is, the old business flow 1031 and the new business flow 1033. This comparison is made to identify the parts (descriptions) that can be diverted from the old manual to the new manual.

Here, the comparison is performed according to the following procedure. The other task corresponding to each task is specified from the upstream side (start) of the old business flow 1031 to the new business flow 1033. As a result, the correspondence relationship (tasks corresponding to each other) of the tasks in the old business flow 1031 and the new business flow 1033 is specified. Details of this step will be described later with reference to FIG.

Then, in step S108, the manual posting unit 1023 transfers the contents of the old manual 1032 to the blank manual created in step S104 by using the correspondence of the tasks. The details of this process will be described with reference to FIG.

As a premise, the correspondence relationship between the tasks of the old business flow 1031 and the new business flow 1033 is specified. Specifically, as shown in FIG. 9, "business trip information entry", "receipt sending each other," superior approval "of the old business flow 1031 and" superior approval "of the new business flow 1033 correspond to each other. ing.

(1) First, the manual transcription unit 1023 specifies a section of the old manual 1032 (or the old manual template) corresponding to the task of the old business flow 1031. In addition, the manual transcription unit 1023 identifies a section of the blank manual corresponding to the task of the new business flow 1033. As the correspondence between this task and the section, the one specified at the time of creating the separate volume information is used (for example, at the time of processing in step S104).

(2) Next, the manual transcription unit 1023 specifies the correspondence between the sections of the old manual 1032 (or the old manual template) and the blank manual template by using the correspondence of the tasks.

(3) Finally, the manual transcription unit 1023 transfers the description content of the old manual 1032 (or the old manual template) to the corresponding section in the blank manual template by using the correspondence relationship specified in (2).

Here, the "supervisor approval" task has been changed to the "supervisor approval" task. This change can be specified in the comparison result at the time of the posting process or in step S107 described later. Therefore, the term "supervisor approval" described in the old manual 1032 (or old manual template) is changed to "supervisor approval" and transcribed.

In addition, when the manual posting unit 1023 has a task with a similar task name in the old business flow 1031 for the newly added task, the content added to the section of the task in the old manual is added to the blank manual template. You may post it in the task section. The conditions for performing such posting will be described later with reference to FIGS. 12 and 15.

Furthermore, for a task in which a plurality of tasks existing in the old business flow 1031 are merged, the manual posting unit 1023 merges the contents described in the section of the plurality of tasks and posts them to the section of the corresponding task. do. The conditions for performing such posting will be described later with reference to FIGS. 12 and 16.

By the above processing, a new manual template is created from the blank manual template. The new manual template created in this way is stored in the sub-storage unit 103 as the manual template transcription result 1036 or the manual template 1034. Then, the new manual is completed by operating the input device 106 from the user. This new manual is stored in the sub-storage unit 103.

In creating a new manual template, the following processing may be performed. The above-mentioned corrected part (approved by the superior) may be displayed on the display device 105 in a format distinct from other parts (color, font, etc.). Further, as information, a flag that distinguishes the corrected part from other parts may be recorded.
(Details of step S104 in the manual template generation unit 1021)
Next, the details of step S104 executed by the manual template generation unit 1021 will be described. Here, the contents of the new business flow 1033 shown in FIG. 4 will be referred to, and the description will be given with reference to the flowchart of FIG. First, the new business flow 1033 can be described by BPMN (Business Process Management Notation). In this embodiment, the "business flow" can also be expressed as a "business process". Further, in this embodiment, BPMN is taken as an example as a notation of business flow, but the present invention is not limited to this. However, those that can read objects such as tasks and connectors that make up the business flow are targeted. In this embodiment, as shown in FIG. 4, the new business flow 1033 is information in which each object is concatenated for each department according to the business flow. Here, each of the objects (x, X, Y, Z, Q in the figure) indicates a task or a branch that constitutes a business. The old business flow 1031 is also represented in the same format.

Next, the details of step S104 (similar S102) will be described with reference to FIG. 10A. In step S104-1, the manual template generation unit 1021 controls each of the following steps so as to loop in each department. Then, in step S104-2, the manual template generation unit 1021 creates separate volume information for each department. Here, when the department information (BPMN swim lane) is described in the new business flow 1033, the separate volume information for each department is generated by using this.

Then, in step S104-3, the manual template generation unit 1021 adds an "overview" chapter (item name) and a "procedure" chapter (item name) to each separate volume information.

Further, in steps S104-4 and S104-5, the manual template generation unit 1021 controls to loop the subsequent steps. That is, the following processing is looped from the start object in the new business flow 1033 to the succeeding object in the order in which the objects to be processed by breadth-first search or the like are specified.

Then, in step S104-6, the manual template generation unit 1021 determines whether each object is a task or a branch according to the specified order. Here, the judgment is made according to the information shown in the new business flow 1033. Here, the object determined to be a task is processed in step S104-7. In addition, the object determined to be a branch is terminated without any particular processing.

Next, in step S104-7, the manual template generation unit 1021 adds a section to the separate volume information with the task name of the target task as the title. A separate volume for department B, which is an example of the separate volume information created as a result, is shown in FIG. 5 (b) (an example of separate volume information for department B). As shown in FIG. 5 (b), the chapters "1. Overview" and "2. Procedure" and "2.1 Q" indicating the sections of "2. Procedure" are recorded as separate volume information of department B. Has been done. With respect to the separate volume information shown in FIG. 5B, the guide sentence is added in step S104 to complete the separate volume information.

Next, in step S104-8, the manual template generation unit 1021 adds a guide sentence to the added section. The details of this process will be described with reference to FIG. 10 (b).

First, in step S104-80, the manual template generation unit 1021 determines whether the task corresponding to the target section is a merging task. This is determined by whether the number of upstream tasks is 2 or more in the new business flow 1033. In the case of two or more tasks, that is, a merging task, the process proceeds to step S104-81. If it is not a merging task, the process proceeds to step S104-84.

Next, in step S104-81, the manual template generation unit 1021 adds information stored in advance in the sub-storage unit 103 or the like to the target section, stating that "the following tasks are premised". Then, in step S104-82, the manual template generation unit 1021 controls to repeat steps S104-83 for each task before merging. That is, in steps S104-83, the manual template generation unit 1021 adds the task name before each merging to the section.

Next, in steps S104-84, the manual template generation unit 1021 determines whether the object following the task corresponding to the target section is a task or a branch. This is done by using the result of step S104-6. If it is a branch, the process proceeds to step S104-85, and if it is a task, the process proceeds to step S108-87. Then, in step S104-85, the manual template generation unit 1021 controls so that step S104-86 is repeated. That is, in step S104-86, the manual template generation unit 1021 adds the information stored in advance in the sub-storage unit 103 or the like to the target section as "in the case of [branch condition]". Here, the content of the subsequent branch condition is inserted in [branch condition].

Next, in step S104-87, the manual template generation unit 1021 determines the department in charge of the task corresponding to the target section or the task following the branch determined in step S104-84. This is determined using the information shown in the new business flow 1033. As a result, if the task is in the same department as the task corresponding to the target section, the process proceeds to step S104-88, and if the task is in another department, the process proceeds to step S104-89.

Then, in step S104-88, the manual template generation unit 1021 adds the information stored in advance in the sub-storage unit 103 or the like to the target section, saying, "Next, do [next task name]." .. Here, a specific task name of the succeeding task determined in step S104-88 is inserted into the [next task name]. Further, in step S104-89, the manual template generation unit 1021 stores in advance in the sub-storage unit 103 or the like, "Next, enter the [next task name] in the [department name]" in the target section. Add information. Here, the other department name determined in step S104-87 is inserted in [department name], and the specific task name of the succeeding task determined in step S104-88 is inserted in [next task name]. Is inserted.

An example of the separate volume information completed in this way is shown in FIG. 5 (a) (an example of the separate volume information of department A). Here, the chapters "1. Overview", "2. Procedure", and "2.1 X", "2.2 Y", and "2.3 Z" indicating the sections of "2. Procedure" are recorded. .. And explanations are added to each of the sections "2.1 X" and "2.3 Z".

In addition, in FIGS. 5A and 5B, the separate volume information of the department A composed of the objects of ×, X, Y, and Z of the department A generated from the new business flow 1033 shown in FIG. 4 and the separate volume information of the department B An example of separate volume information of department B including an object with Q is shown.

As described above, the separate volume information for each department created is merged and stored in the sub-storage unit 103 as a blank manual template.
(Details of step S107 in the business flow difference analysis unit 1022)
Next, the details of step S107 executed by the business flow difference analysis unit 1022 will be described with reference to FIGS. 11 and 12.

First, the business flow difference analysis unit 1022 first identifies the tasks corresponding to each other in the old business flow 1031 and the new business flow 1033. Here, it is determined whether the task names match. The result is shown in FIG. Here, the "start", "X: A", "Y: A", "Q: A", and "end" tasks are the same. On the other hand, the old business flow "Z: A" and the new business flow "Z': A" "P: B" do not match (underlined task). Here, it is specified that the tasks having the same task name correspond to each other.

However, the new business flow "Z': A" indicates that the old business flow "Z: A" in FIG. 11 has been partially modified. Here, these "Z: A" and "Z': A" originally have a corresponding relationship, and there is a possibility that they can be diverted. For example, it is possible that the task name is simply changed (change from superior approval to superior approval) and the content is not changed. In addition to this, a plurality of tasks may be merged into one task, and the manual can be diverted in this case as well. In this case as well, there is a possibility that it can be diverted. Therefore, in these cases as well, the following processing shown in FIG. 12 is performed in order to specify the correspondence between the tasks.

First, in step S107-1, the business flow difference analysis unit 1022 identifies a plurality of tasks having the same task name and a task sandwiched between them. In the example of FIG. 11, "X: A" and "Q: A" having the same task name and "Z: A" and "Z': A" sandwiched between them are specified. Then, the matching status is identified by comparing the sandwiched tasks. The match status specifies the relationship between the number of tasks sandwiched between the old business flow 1031 and the new business flow 1033. That is, the relationship between the number of tasks of the old business flow 1031 and the new business flow 1033 is "1: 1", "N: 0" or "1: 0", "0: N" or "0: 1", "N: Specify either "1", "N: M" or "1: N" (N and M are 2 or more each).

Then, in step S107-2, the business flow difference analysis unit 1022 branches the process according to the result of step S107-1. That is, if it is "1: 1", it goes to step S107-3, if it is "N: 0" or "1: 0", it goes to step S107-8, and if it is "0: N" or "0: 1", it goes to step S107-8. The process transitions to step S107-11, to step S107-14 if "N: 1", and to step S107-16 if "N: M" or "1: N".

Next, in step S107-3, the business flow difference analysis unit 1022 compares the task names of the tasks corresponding to 1: 1. Then, it is determined whether the task names are similar or dissimilar depending on whether the similarity of the task names is equal to or higher than a certain threshold value. As a result, if it is determined to be dissimilar, the process proceeds to step S107-4, and if it is determined to be similar, the process proceeds to step S107-6.

Then, in step S107-4, the business flow difference analysis unit 1022 determines that there is no correspondence between the tasks. In response to this, in step S107-5, the business flow difference analysis unit 1022 determines that the posting of S108 is unnecessary, and stores the result as the business flow difference 1035 in the sub storage unit 103.

Further, in step S107-6, the business flow difference analysis unit 1022 determines that each task has a correspondence relationship. In response to this, in step S107-7, the business flow difference analysis unit 1022 determines that the S108 is to be posted, and stores the result as the business flow difference 1035 in the sub storage unit 103. S108 is executed using the determination results of steps S107-5 and S107-7. It should be noted that the results of judgments that do not require posting in other steps shown in FIG. 12 and are required are also used in the same manner.

Here, if it is determined in step S107-7 that posting is necessary, the posting in S108 is performed as follows. If there is a task with a similar task name in the old business flow 1031 for the newly added task, the manual posting unit 1023 will add the content added to the section of the task in the old manual to the task in the blank manual template. Post to section.

Specific examples of the processes from step S107-3 to step S107-7 will be described with reference to FIG. In FIG. 13 (a), the task name of the task between (2) for (1) matching tasks "entering business trip information" and "sending receipt" is changed from "supervisor approval" to "supervisor approval". There is. These "superior approval" and "superior approval" are judged to be similar because the degree of similarity is above a certain value. Therefore, "superior approval" and "superior approval" are associated with each other.

On the other hand, in FIG. 13 (b), the task name of the task between (2) for (1) matching tasks "entering business trip information" and "sending receipt" is changed from "supervisor approval" to "print". .. These "superior approval" and "printing" are judged to be dissimilar because the degree of similarity is less than a certain value. In this case, the "print" task is also determined to be a new addition, and these tasks are not associated.

The determination in step S107-3 may be made by specifying the tasks corresponding to each other in the old business flow 1031 and the new business flow 1033. That is, it is determined whether or not the task names match, including similar judgments, and if they are similar, it is specified that they correspond. In this case, it is possible to omit the determination of "1: 1" in step S107-2 and the processing of steps S107-3 to S107-7.

Next, a case where it is determined as “N: 0” or “1: 0” in step S107-2 will be described. In step S107-8, the business flow difference analysis unit 1022 determines that the task of the old business flow 1031 has been deleted. Then, the business flow difference analysis unit 1022 executes the same processing as in steps S107-4 and S107-5 in steps S107-9 and S107-10, respectively. In other words, it is judged that there is no correspondence and that posting is unnecessary.

However, the manual transcription unit 1023 may add the content described in the section of the task of the old manual 1032 (or the old manual template) to the end of the blank manual template for the task determined to be deleted. This allows the user to reuse this description in the new manual.

Specific examples of the processes from step S107-8 to step S107-10 will be described with reference to FIG. In FIG. 14A, the task “supervisor approval” between (2) for the matching tasks “entering business trip information” and “sending receipt” is no longer in the new business flow 1033. Further, in FIG. 14 (b), the tasks "supervisor approval" and "printing" between (2) for the matching tasks "entering business trip information" and "sending receipt" are no longer in the new business flow 1033. There is. Therefore, it is judged that these "supervisor approval" and "printing" have been deleted.

Next, a case where it is determined as “0: N” or “0: 1” in step S107-2 will be described. In step S107-11, the business flow difference analysis unit 1022 determines that the task has been added to the new business flow 1033. Then, the business flow difference analysis unit 1022 executes the same processing as in steps S107-4 and S107-5 in steps S107-12 and S107-19, respectively. In other words, it is judged that there is no correspondence and that posting is unnecessary.

Specific examples of the processes from step S107-11 to step S107-13 will be described with reference to FIG. In FIG. 15A, the task “supervisor approval” between (2) for the matching tasks (1) “entering business trip information” and “sending receipt” is added to the new business flow 1033. Also, in FIG. 15 (b), the tasks "supervisor approval" and "printing" between (2) for the matching tasks "entering business trip information" and "sending receipt" have been added to the new business flow 1033. ing. Therefore, it is judged that these "supervisor approval" and "printing" have been deleted.

The following alternative processes also exist for steps S107-11 to S107-13.

If it is determined to be added in step S107-11, the business flow difference analysis unit 1022 determines whether a task name similar to the task name of the task added in the new business flow 1033 exists in the old business flow. .. This determination is made in the same manner as in step S10703. As a result, when a task with a similar task name cannot be specified, the processes of S107-12 and S107-13 are executed. When a task with a similar task name can be specified, the business flow difference analysis unit 1022 associates the tasks with similar task names in the old business flow 1031 and the new business flow 1033. A specific example of this is shown in FIG. FIG. 16A shows an example in which one task is added (0: 1), and FIG. 16B shows an example in which a plurality of tasks are added (0: N). In each of these cases, it is determined that the "receipt printing" added in the new business flow 1033 is similar to the "receipt sending" in the old business flow 1031. Then, each of these is associated. That is, the correspondence relationship (3) is specified. Using this result, if there is a task with a similar task name in the old business flow 1031 for the newly added task, the manual posting unit 1023 will add the content added to the relevant task section of the old manual to a blank manual. Post to the relevant task section of the template. It is more desirable that the similar judgment here is limited to the comparison of the tasks existing in the meantime including the matching task of (1).

Next, a case where it is determined to be “N: 1” in step S107-2 will be described. In step S107-14, the business flow difference analysis unit 1022 determines that the plurality of tasks in the old business flow 1031 have been merged into one task in the new business flow 1033. In response to this, the business flow difference analysis unit 1022 performs the same processing as in steps S107-6 and S107-7 in steps S107-15 and S107-16.

When the process of step S107-16 is performed, the manual posting unit 1023 may post the contents of each task of the merged old business flow 1031 or may post the contents of a similar task. .. In the latter case, other tasks may be described at the end of the blank manual template. It is more desirable that the similar judgment here is also limited to the comparison of the tasks existing in the meantime including the matching task of (1).

Specific examples of the processes from step S107-14 to step S107-16 will be described with reference to FIG. In FIG. 17, for (1) matching tasks “business trip information entry” and “receipt sending”, (2) task between the old business flow 1031 “superior approval” and (3) task between the old business flow 1031. It is determined that "printing" has been merged into "superior approval" in the new business flow 1033. Then, in the posting of the manual posting unit 1023, the contents of both "supervisor approval" and "printing" may be transcribed to "supervisor approval", and similar contents of "supervisor approval" may be transferred to "above". It may be posted to "long approval".

Next, a case where it is determined as “N: M” or “1: M” in step S107-2 will be described. In step S107-17, the business flow difference analysis unit 1022 determines that the tasks of the old business flow 1031 and the new business flow 1033 are mixed. Then, the business flow difference analysis unit 1022 executes the same processing as in steps S107-4 and S107-5 in steps S107-18 and S107-19, respectively. In other words, it is judged that there is no correspondence and that posting is unnecessary. In these cases, the processing may be performed as in steps S107-11 to S107-13 and steps S107-14 to S107-16. That is, when a similar task exists among the tasks existing in the meantime including the matching task, it may be determined to post the contents of the similar task.

The process shown in FIG. 12 above is executed for each task sandwiched between matching tasks. Then, using each result, the manual posting unit 1023 generates a new manual template by posting to the corresponding section of the blank manual template.

According to the above embodiment, when the business flow is changed, the manual template is regenerated, but the man-hours can be reduced by automatically transferring the contents added to the old manual template to the newly generated new manual template. It can be suppressed.

In addition, since the feature that the majority of tasks are not changed when the business flow is changed, the task name change, new addition, deletion, and merge are determined more reliably.

10 ... Manual generator, 101 ... Control unit, 102 ... Main storage unit, 1021 ... Manual template generation unit, 1022 ... Business flow difference analysis unit, 1023 ... Manual transcription unit, 103 ... Sub storage unit, 1031 ... Old business flow, 1032 ... Old manual, 1033 ... New business flow, 1034 ... Manual template, 1035 ... Business flow difference, 1036 ... Manual template transcription result, 104 ... Communication unit, 105 ... Display device, 106 ... Input device, 20 ... Network, 30 ... Terminal device

Claims (8)

In a manual generator that generates a manual template for a manual that shows the contents of the business due to a change in the business.
The old business flow that shows the business flow before the change of the business and has multiple tasks, the new business flow that shows the business flow after the change of the business and has multiple tasks, and the old manual that is the manual before the change of the business. A memory unit to memorize and
A manual template generator that creates a blank manual template using the new business flow,
The old business flow and the new business flow corresponding to each other are compared, and the correspondence relationship of each of the plurality of tasks constituting the business flow is specified by the comparison, and the correspondence relationship of each task is matched based on the identified result. A business flow difference analysis unit that judges the situation and determines whether or not the contents of the tasks included in the old manual have been posted according to the matching situation.
Based on the result of the determination, the blank manual template is characterized by having a manual transcription unit that generates a new manual template according to the change of the business by transcribing the contents of the tasks of the old manual. Manual generator. In the manual generator according to claim 1,
The business flow difference analysis department
As the matching situation, the manual generation device is characterized in that the corresponding number of tasks for each of the new business flow and the old business flow is specified while the task names match. In the manual generator according to claim 2.
The business flow difference analysis department
As the corresponding number,
(1) When the number of tasks of either the old business flow or the new business flow is 0, or (2) when the number of tasks of both the old business flow and the new business flow is different.
(3) When the new business flow is 1 for a plurality of tasks in the old business flow, it is determined that the plurality of tasks in the old business flow are merged and posted as a task in the new business flow.
(4) When the number of tasks of both the new business flow and the old business flow correspond on a one-to-one basis,
(4-1) If the task names of the corresponding tasks are similar or match, it is determined that the task of the old business flow of the corresponding tasks is posted as the task of the corresponding new business flow.
(4-2) A manual generation device characterized in that if the task names of the corresponding tasks are not similar or match, it is determined that there is no posting. In the manual generator according to claim 3,
The business flow difference analysis department
If the number of tasks in the new business flow is 0, it is determined that the tasks in the old business flow will be deleted.
A manual generation device characterized in that when the number of tasks in the old business flow is 0, it is determined that a task in the new business flow is to be added. In the manual generation method using a manual generator that generates a manual template for a manual showing the contents of the business due to a change in the business.
The storage unit of the manual generator indicates the business flow before the change of the business and has a plurality of tasks, the old business flow which shows the business flow after the change of the business and has a plurality of tasks, and the new business flow of the business. Memorize the old manual, which is the manual before the change,
The manual template generation unit of the manual generation device creates a blank manual template using the new business flow.
The business flow difference analysis unit of the manual generator compares the old business flow and the new business flow that correspond to each other, and by the comparison, the correspondence relationship of each of the plurality of tasks constituting the business flow is specified. Based on the identified result, the matching status of the correspondence of each task is determined, and according to the matching status, whether or not the content of the task included in the old manual is transcribed is determined.
Based on the result of the determination, the manual transcription unit of the manual generator transfers the contents of the tasks of the old manual to the blank manual template to generate a new manual template according to the change of the business. A manual generation method characterized by that. In the manual generation method according to claim 5,
By the business flow difference analysis department
A manual generation method, characterized in that, as the matching status, the number of corresponding tasks for each of the new business flow and the old business flow while the task names match is specified. In the manual generation method according to claim 6,
By the business flow difference analysis department
As the corresponding number,
(1) When the number of tasks of either the old business flow or the new business flow is 0, or (2) when the number of tasks of both the old business flow and the new business flow is different.
(3) When the new business flow is 1 for a plurality of tasks in the old business flow, it is determined that the plurality of tasks in the old business flow are merged and posted as a task in the new business flow.
(4) When the number of tasks of both the new business flow and the old business flow correspond on a one-to-one basis,
(4-1) If the task names of the corresponding tasks are similar or match, it is determined that the task of the old business flow of the corresponding tasks is posted as the task of the corresponding new business flow.
(4-2) A manual generation method characterized in that if the task names of the corresponding tasks are not similar or match, it is determined that there is no posting. In the manual generation method according to claim 7,
By the business flow difference analysis department
If the number of tasks in the new business flow is 0, it is determined that the tasks in the old business flow will be deleted.
A manual generation method characterized in that when the number of tasks in the old business flow is 0, it is determined that a task in the new business flow is to be added.

Images