JP5218068B2 - Information processing apparatus and information processing program - Google Patents

Description

  The present invention relates to an information processing apparatus and an information processing program.

  There is a document management system as a system for managing documents used for business. Various types of information are collected using documents managed by the document management system.

As a technology related to this, for example, Patent Document 1 has an issue of realizing an information collection system capable of effectively utilizing a management system unique to a document management system such as a hierarchical structure and a title structure for information collection. The information collection system displays the collection method selection screen on the client terminal of the administrator user, and the administrator user selects the “select document box from the bookshelf” and “selects the title structure” on the collection method selection screen. When the “select document box from bookcase” method is selected, the client terminal is provided with information for specifying the registration location to be collected according to the hierarchical structure. In addition, when the “select title structure” method is selected, the title structure to be collected is specified from the multiple types of title structures. Information for it has been disclosed that is provided to the client terminal.
JP 2004-086334 A

  An object of the present invention is to provide an information processing apparatus and an information processing program that generate a business procedure in accordance with an already-executed business when generating a business procedure.

The gist of the present invention for achieving the object lies in the inventions of the following items.
The invention of claim 1 is an operation history receiving means for receiving an operation history for a document, a business procedure extracting means for extracting a work procedure based on the operation history received by the operation history receiving means, and the business procedure extraction. An operation was performed as an operation history received by the operation history accepting means, including a presenting means for presenting the work procedure extracted by the means and an operator / role changing means for changing the operator to a role in the work. Operation, a document name that is an operation target, and an operator, and the business procedure extraction unit extracts an activity in the business based on the operation in the operation history and the document name that is the operation target, Based on the role changed by the operator / role changing means and the name of the document that is the operation target, it is determined whether the activity is in a different business or not. Extract the procedure of operations, said presenting means is an information processing apparatus characterized by presenting the steps of the business for each business.

The invention of claim 2, wherein the presentation means is an information processing apparatus according to claim 1, characterized in that an activity in a plurality of operations are presented in common activities and other activities different aspects.

According to a third aspect of the present invention, the operation target document is stored in a storage device having a hierarchical structure, the document name includes a name of the hierarchy, and the operation procedure extracting unit includes the operation procedure extracting unit. 3. The information processing apparatus according to claim 1, wherein an activity in the job is extracted based on the name of the hierarchy in the document name that is the operation target. 4.

In the invention of claim 4, the presenting means presents a business procedure as information relating to a business flow in financial internal control, and a common activity and other activities are subject to risk or control in activities in a plurality of business operations. an information processing apparatus according to any one of claims 1 to 3, wherein the presenting to obtain.

According to a fifth aspect of the present invention, there is provided an operation history receiving means for receiving an operation history for a document, a work procedure extracting means for extracting a work procedure based on the operation history received by the operation history receiving means, An operation history is received as the operation history received by the operation history accepting means, and functions as a presenting means for presenting the work procedure extracted by the work procedure extracting means and an operator / role changing means for changing the operator to a role in the work. When performed, the operation procedure includes the name of the document that is the operation target and the operator, and the business procedure extraction means extracts the activity in the business based on the operation and the document name that is the operation target in the operation history. Whether the activity is in a different job based on the role changed by the operator / role changing means and the name of the document to be operated. Determine, extracts the procedure of the operations for each business, the presentation means is an information processing program characterized by presenting the steps of the business for each business.

According to the information processing apparatus of the first aspect, in the case of generating the business procedure, it is possible to generate the business procedure in accordance with the business already performed. And the load which produces | generates the procedure of work can be reduced. Furthermore, even if there are histories in a plurality of business operations, the business procedure can be generated for each business operation.

According to the information processing apparatus of the second aspect, it is possible to easily find a different job as compared with other jobs.

According to the information processing apparatus of the third aspect , even if the document is stored in the storage device having a hierarchical structure, the business procedure can be generated.

According to the information processing apparatus of the fourth aspect, it is possible to present information suitable for generating a business flow in financial internal control.

According to the information processing program of the fifth aspect, in the case of generating the business procedure, it is possible to generate the business procedure in accordance with the business already performed. And the load which produces | generates the procedure of work can be reduced. Furthermore, even if there are histories in a plurality of business operations, the business procedure can be generated for each business operation.

Hereinafter, examples of various preferred embodiments for realizing the present invention will be described with reference to the drawings.
FIG. 1 is a conceptual module configuration diagram of a configuration example according to the first embodiment.
The module generally refers to components such as software (computer program) and hardware that can be logically separated. Therefore, the module in the present embodiment indicates not only a module in a computer program but also a module in a hardware configuration. Therefore, the present embodiment also serves as an explanation of a computer program, a system, and a method. However, for the sake of explanation, the words “store”, “store”, and equivalents thereof are used. However, when the embodiment is a computer program, these words are stored in a storage device or stored in memory. It is the control to be stored in the device. In addition, the modules correspond almost one-to-one with the functions. However, in mounting, one module may be composed of one program, or a plurality of modules may be composed of one program. A plurality of programs may be used. The plurality of modules may be executed by one computer, or one module may be executed by a plurality of computers in a distributed or parallel environment. Note that one module may include other modules. Hereinafter, “connection” is used not only for physical connection but also for logical connection (data exchange, instruction, reference relationship between data, etc.).
In addition, the system or device is configured by connecting a plurality of computers, hardware, devices, and the like by communication means such as a network (including one-to-one correspondence communication connection), etc., and one computer, hardware, device. The case where it implement | achieves by etc. is also included. “Apparatus” and “system” are used as synonymous terms. “Predetermined” means before the target process, and before the process according to the present embodiment is started, even after the process according to the present embodiment is started, It is used according to the situation / state at that time or with the intention to be decided according to the situation / state up to that point.

  The document handled in this embodiment is electronic data such as images, text data, moving images, audio, or a combination thereof, and is a target of storage, editing, search, etc., and is an individual unit between systems or users. Things that can be exchanged, including similar ones.

  The information processing apparatus according to the present embodiment presents a business procedure (hereinafter also referred to as a business flow) using an operation history for a document managed by the document management system 140. FIG. As shown in the figure, an operation history extraction module 110, a business flow extraction module 120, and a business flow presentation module 130 are included, and are connected to a document management system 140 and a user management system 150.

The document management system 140 is connected to the operation history extraction module 110 and manages and manages documents (document storage, document attribute / access rights assignment / storage, document search, etc.). The document is an operation target, and its editing history is stored. In accordance with a request from the operation history extraction module 110, the stored editing history is passed.
The document management system 140 may store the operation target document as a storage device having a hierarchical structure. For example, a document may be stored in a folder as a hierarchical structure. Further, there may be a folder in the folder.
The user management system 150 is connected to the operation history extraction module 110 and manages users (document management system 140, information processing apparatus and other users as targets, and information about the users (for example, user attributes (role)). Etc.), and in accordance with a request from the operation history extraction module 110, information related to the managed user is passed. For example, a table that associates roles with users is stored, and this table is passed to the operation history extraction module 110.

The operation history extraction module 110 is connected to the document management system 140, the business flow extraction module 120, and the user management system 150, and receives an operation history for a document from the document management system 140. Then, the operation history (including the operation history changed by the operation history extraction module 110) is passed to the business flow extraction module 120.
For example, the received operation history may include the name of the document that is the operation and operation target when the operation is performed.

Moreover, an operator may be further included as an operation history to be accepted. An operator refers to a person who has performed an operation on the document, and examples of an operator included in the operation history include a user ID and a user name for identifying the operator.
The operation history extraction module 110 may change the accepted operator to a role in business. For example, the user management system 150 may be requested for a table in which users and roles are associated, and the user may be changed to a role from the table.

In addition to the name of the document alone, the document name may include a hierarchical name (so-called path name) in the storage device (document management system 140) in which the document is stored. The document name is assigned (named) so as to include the name of the business. The position where the name of the business is included may be the part of the name of the document alone or the part of the hierarchy. Hereinafter, this document name is also referred to as a file ID or a file path.
Further, as a change process performed by the operation history extraction module 110, in addition to changing from a user to a role, the time when the operation was performed is changed to the order of the operation, and the document name including the name of the hierarchy is changed in advance. You may make it extract the defined hierarchy part.

The business flow extraction module 120 is connected to the operation history extraction module 110 and the business flow presentation module 130, and extracts a business procedure based on the operation history received by the operation history extraction module 110. A business includes activities, and the order of the activities is determined. Furthermore, a role for performing the activity may be determined. Then, the extracted business procedure is passed to the business flow presentation module 130.
Further, the business flow extraction module 120 may extract an activity in the business based on the operation and the document name that is the operation target based on the received operation history.
Also, based on the role changed by the operation history extraction module 110 and the document name that is the operation target, it is determined whether the activity is in a different business, and the procedure of the business is extracted for each business. Good.
Moreover, you may make it extract the activity in work based on the name of the hierarchy in the document name which is operation and operation object.

The business flow presentation module 130 is connected to the business flow extraction module 120 and presents the business procedure extracted by the business flow extraction module 120.
If there are a plurality of tasks, the procedure of the tasks may be presented for each task.
In addition, common activities and other activities may be presented in different manners in a plurality of business activities. “Presenting in a different manner” means, for example, that an icon (small image) corresponding to an activity can be distinguished from other things, and corresponds to changing the color, shape, pattern, sound, or a combination thereof. . Note that changing the sound corresponds to outputting a sound different from the other when the corresponding icon is selected.

FIG. 2 is an explanatory diagram showing a system configuration example for realizing the present embodiment (first to third embodiments).
The document management system 140, the user management system 150, and the business flow extraction system 200 are connected via a communication line. The operation history extraction module 110, the business flow extraction module 120, and the business flow presentation module 130 illustrated in the example of FIG. 1 are built in the business flow extraction system 200. Further, the document management system 140, the user management system 150, and the business flow extraction system 200 are each one in the example of FIG. 2, but may be plural. Mainly, the document management system 140 and the user management system 150 operate as a server, and the business flow extraction system 200 operates as a client for the server. A PC (personal computer) for editing a document managed by the document management system 140 may be connected.

FIG. 3 is an explanatory diagram showing a module configuration example in the operation history extraction module 110, the document management system 140, and the user management system 150.
The document management system 140 has a document DB 141 and an operation history DB 142. The document DB 141 is a database that stores documents, and the documents can be edited by user operations.
For example, a document having a hierarchical structure is stored like the document DB 141 shown in the example of FIG. The example shown in FIG. 6 has an order business folder 610 and an order business folder 630 which are two folders under the business document folder 600 which is a folder, and an estimate which is three folders under the order business folder 610. A request folder 611, an estimate folder 614, and an order folder 617 are provided. Under the estimate request folder 611, two documents, an estimate request form 1 612 and an estimate request form 2 613, are provided. Has two documents, estimate 1 615 and estimate 2 616, and under the order folder 617, there are two documents, order 1 618 and order 2 619.
The operation history DB 142 is a database that stores an operation history for the document. As the operation history, for example, when an operation is performed (any year, month, day, hour, minute, second, etc., any combination of these, and what can be determined before and after two operations) is operated. , The user who performed the operation, the name of the document to be operated (hereinafter also referred to as file ID or file path), and the like.

  The user management system 150 has a user information DB 151. The user information DB 151 is a database that stores information about users. For example, as shown in the example of FIG. 7, a user information table 700 is stored. FIG. 7 is an explanatory diagram showing an example of the data structure of the user information table 700. The user information DB 151 stores a user information table 700, and the user information table 700 has a user column 710 and a role column 720. The user column 710 stores the name as a user, and the role column 720 stores the name as a role corresponding to the user (hereinafter also referred to as a role).

The operation history extraction module 110 includes a target operation history extraction module 111 and an operation history change module 112.
The target operation history extraction module 111 acquires an operation history for a document under a business flow extraction target hierarchy (folder) from the document management system 140. Then, the acquired operation history is passed to the operation history change module 112.
Then, the operation history change module 112 extracts an operation history in a format such as an operation order, a role, hierarchy information of an operation file, and a file ID from the acquired data. In the extraction, in addition to selecting data from the operation history acquired from the document management system 140, the data is converted as necessary. For example, the user management system 150 is inquired to convert a user name included in the operation history into a role name.

  Further, the business flow extraction system 200 receives designation of a processing target (a document to be analyzed as a business procedure (its operation history group)) according to the present embodiment. This designation includes designation according to the user's operation or predetermined designation. For example, it is specified by the setting table 810 shown in the example of FIG. The business flow extraction system 200 stores an operation history table 820 that is a result of business flow extraction by the business flow extraction module 120.

FIG. 4 is an explanatory diagram showing a module configuration example in the business flow extraction module 120. The business flow extraction module 120 extracts a business flow instance (substance) from the operation history from the operation history extraction module 110.
The business flow extraction module 120 includes a subflow extraction module 121, an operation rule application module 122, a role / subflow rule application module 123, and a file ID rule application module 124.
The subflow extraction module 121 extracts a subflow from the file ID extracted by the operation history extraction module 110. Here, the subflow constitutes a business and constitutes an activity name part. The subflow is extracted according to the one specified by the hierarchical subflow correspondence column 812 of the setting table 810 described later. More specifically, for example, the flowchart shown in FIG. 24 is followed. This specific process will be described later.

  The operation rule application module 122 applies a rule to the operation history extracted by the operation history extraction module 110 and extracts a business flow. Here, as a rule, for example, a new registration (operation) of the same document type by the same role is performed only once in one instance of a workflow, and an update activity for a document registered in a certain workflow instance is: It is included in an instance of a registered business flow. Based on this rule, the role / subflow rule application module 123 and the file ID rule application module 124 are controlled to extract a business flow instance from the operation history. More specifically, for example, the flowchart shown in FIG. 19 is followed. This specific process will be described later.

The role / subflow rule application module 123 determines whether to include an operation in the operation history as an activity according to a predetermined rule for the role and the subflow. As a specific example, if the operation in the operation history is registration and the same combination of role and subflow is not already extracted as a business flow, the registered operation is extracted as an activity of the business flow.
The file ID rule application module 124 determines whether or not to include an operation in the operation history as an activity according to a predetermined rule for the file ID. As a specific example, if the operation in the operation history is an update, and the file ID to be updated is included in the file ID of the activity of the registered operation in the business flow that has already been extracted, Extract as business flow activity.

  FIG. 5 is an explanatory diagram showing a module configuration example in the business flow presentation module 130. The business flow presentation module 130 presents the business flow instance data extracted by the business flow extraction module 120 on a screen or file as a business flow diagram or workflow system definition data. In addition, when a plurality of instances of different business flows are extracted by the business flow extraction module 120, a function of presenting the extracted business flows on the screen in descending order of the number of extracted instances and selecting a business flow to be presented is provided. You may make it prepare.

The business flow presentation module 130 includes an activity name generation module 131, a file link generation module 132, a common activity extraction module 133, and a presentation module 134.
The activity name generation module 131 generates an activity name. More specifically, for example, an activity name may be generated by combining a subflow name and an operation name.
The file link generation module 132 generates a link with the document associated with the activity.

When a plurality of business flows are extracted, the common activity extraction module 133 extracts a common activity among the plurality of business flows. In addition, other activities (uncommon activities) may be extracted.
The presentation module 134 presents a business flow diagram on the display of the business flow extraction system 200 and presents data defining the business flow (including a prototype of the definition data of the business flow).

FIG. 8 is an explanatory diagram showing an example of the data structure of the setting / result table group 800. The business flow extraction system 200 includes a setting / result table group 800. The setting / result table group 800 includes a setting table 810 and an operation history table 820.
The setting table 810 has an analysis target column 811 and a hierarchical subflow correspondence column 812. The analysis target column 811 stores a folder that stores a target document in the document management system 140. The hierarchical subflow correspondence column 812 stores objects to be extracted as subflows.
In the example shown in FIG. 8, “/ order receiving work” is designated as an analysis target, which indicates that the document under the order receiving work folder 610 shown in the example of FIG. 6 is targeted. The target to be extracted as a subflow is specified to be a child folder, which is an estimate request folder 611, an estimate folder 614, an order, which are three folders under the order receiving business folder 610 shown in the example of FIG. It shows that the name of the folder 617 is extracted as a subflow.

The operation history table 820 includes an order column 821, an operation column 822, a role column 823, a hierarchy column 824, and a file ID column 825.
The order column 821 stores the order of the activities in the work.
The operation column 822 stores operations in the activity.
The role column 823 stores the role for which the operation was performed.
The hierarchy column 824 stores the hierarchy name portion of the document that is the operation target (which may include the name of the document alone).
The file ID column 825 stores a file ID that is an operation target in the activity.
Note that the state before the processing according to the present embodiment is empty in each column as shown in the example of FIG. In addition, when there are a plurality of tasks included in the analysis target, the operation history table 820 is generated as the number of tasks as a processing result.

  FIG. 9 is a flowchart illustrating a processing example of step (1) according to the first embodiment. This process is performed by the operation history extraction module 110. The operation history extraction module 110 acquires a folder to be analyzed from the analysis target column 811 of the setting table 810, acquires an operation history of a document under the folder to be analyzed from the document management system 140, and obtains a business flow extraction module. Information necessary for the processing in 120 (order, operation (operation type), role, hierarchy, file ID) is extracted. The role is acquired from the user management system 150.

  In step S <b> 902, the target operation history extraction module 111 acquires an operation history for the document under the “/ order received work” folder that is the analysis target from the document management system 140. For example, there is an acquisition operation history table 1000 shown in the example of FIG. FIG. 10 is an explanatory diagram showing an example of the data structure of the acquisition operation history table 1000. The acquisition operation history table 1000 includes a date / time column 1010, an operation column 1020, a user column 1030, a file ID column 1040, and the like. The date / time column 1010 may be any date / time (year, month, day, hour, minute, second, etc.) of the operation, or any combination thereof, and can be determined before and after the two operations. ) Is remembered. The operation column 1020 stores the performed operation. The user column 1030 stores the user ID that performed the operation. The file ID column 1040 stores a file ID that is an operation target. These other information may be stored.

In step S904, the target operation history extraction module 111 extracts only data in the date / time column 1010, the operation column 1020, the user column 1030, and the file ID column 1040 from the acquisition operation history table 1000.
In step S906, the operation history change module 112 replaces the date / time string in the date / time column 1010 with the order of the processing result in step S904. Here, the order may be a code (number or the like) representing the order.
In step S908, the operation history change module 112 inquires of the user management system 150 about the processing result in step S906, and replaces the user with a role. That is, using the user information table 700, a role corresponding to the user is extracted and replaced with that role.
In step S910, the operation history change module 112 removes “/ order received work” from the file path in the file ID column 1040 according to the hierarchical subflow correspondence column 812 of the setting table 810 with respect to the processing result in step S908. Items (intermediate folder name and document single file name (file path part)) are added as a "hierarchy" column (step (1) hierarchy column 1140 of extraction result table 1100).

By the processing example of step (1), the acquisition operation history table 1000 shown in the example of FIG. 10 becomes the step (1) extraction result table 1100 shown in the example of FIG. FIG. 11 is an explanatory diagram showing an example of the data structure of the step (1) extraction result table 1100. Step (1) The extraction result table 1100 has an order column 1110, an operation column 1120, a role column 1130, a hierarchy column 1140, and a file ID column 1150.
The order column 1110 is converted from the date / time column 1010 of the acquisition operation history table 1000 in step S906.
The operation column 1120 is the same as the operation column 1020 of the acquisition operation history table 1000.
The role column 1130 is converted from the user column 1030 of the acquisition operation history table 1000 in step S908.
The hierarchy column 1140 is added by converting from the file ID column 1040 of the acquisition operation history table 1000 in step S910.
The file ID column 1150 is the same as the file ID column 1040 of the acquisition operation history table 1000.

  FIG. 12 is a flowchart illustrating a processing example of step (2) according to the first embodiment. This process is performed by the business flow extraction module 120. The business flow extraction module 120 extracts a business flow from the extraction result obtained in step (1). Based on the correspondence between hierarchical information and subflow names defined in the hierarchical subflow correspondence column 812 of the setting table 810 based on a set of documents for each business flow from the operation history and the order of registration / update Extract.

In step S1202, 1 is substituted into the variable M, and the processing from step S1204 to step S1208 is repeated until all rows of the extraction result (step (1) extraction result table 1100) in step (1) are deleted (step S1202). Loop B). In other words, when the processing in step (2) is completed, the variable M is the number of business flows plus 1, and the extraction result in step (1) is empty. Instead, only the number of business flows is extracted. The result table will be completed.
This will be described with reference to FIGS.
FIG. 13 is an explanatory diagram showing an example of the data structure of the step (1) extraction result table 1300. Step (1) The extraction result table 1300 has an order column 1310, an operation column 1320, a role column 1330, a hierarchy column 1340, and a file ID column 1350. This is because the step (1) extraction result table 1100 is empty. It is in a state.
FIG. 14 is an explanatory diagram showing an example of the data structure of the step (2) extraction result 1 table 1400. Step (2) The extraction result 1 table 1400 has an order column 1410, an operation column 1420, a role column 1430, a subflow column 1440, and a file ID column 1450. The operation line related to 1 is extracted.
FIG. 15 is an explanatory diagram showing an example of the data structure of the step (2) extraction result 2 table 1500. The step (2) extraction result 2 table 1500 includes an order column 1510, an operation column 1520, a role column 1530, a subflow column 1540, and a file ID column 1550. This is an extraction of operation lines related to 2.

In step S1204, process B using the variable M as an argument is performed. Process B will be described later using the flowchart shown in the example of FIG.
In step S1206, the variable M is incremented by one. In other words, this is because the next business flow is to be extracted.
In step S1208, the process returns to step S1202, and if all rows extracted as a result of step (1) are deleted, the process of step (2) is terminated (step S1299).

  FIG. 16 is a flowchart illustrating a processing example of the processing B according to the first embodiment. This process is performed by the business flow extraction module 120. This is processing in step S1204 of the flowchart shown in the example of FIG. A variable M-th business flow is extracted.

  In step S1602, an empty table for storing the extraction result of the business flow M is created. As a specific example, an extraction result 1 table 1700 as shown in FIG. 17 is created. FIG. 17 is an explanatory diagram of an example of the data structure of the extraction result 1 table 1700. The extraction result 1 table 1700 has an order column 1710, an operation column 1720, a roll column 1730, a subflow column 1740, and a file ID column 1750. The difference from the step (1) extraction result table 1100 that is the extraction result of step (1) is that it is not the hierarchy column 1140 but the subflow column 1740.

In step S1604, the processing (processing from step S1606 to step S1608) for each row of the extraction result (step (1) extraction result table 1100) in step (1) is repeated (loop A). That is, at the time when the processing B is completed, a table of the extraction result of the business flow M is completed.
This will be described with reference to FIG. FIG. 18 is an explanatory diagram showing an example of the data structure of the business flow extraction result 1 table 1800 when M is 1. The extraction result 1 table 1800 has an order column 1810, an operation column 1820, a roll column 1830, a subflow column 1840, and a file ID column 1850. That is, the extraction result is inserted into the extraction result 1 table 1700.

In step S1606, process A using the variable M and the current target row as arguments is performed. The process A will be described later using the flowchart shown in the example of FIG.
In step S1608, the process returns to step S1604, and if the processing for each row of the extraction result in step (1) has been completed, the process B ends (step S1699).

FIG. 19 is a flowchart illustrating a processing example of the processing A according to the first embodiment. This process is performed by the business flow extraction module 120. This is the processing of step S1606 in the flowchart shown in the example of FIG. The target row of the extraction result of step (1) (step (1) extraction result table 1100) is an operation in the variable Mth business flow by determining whether or not the operation is in the variable Mth business flow. Extract that case operation.
As a specific example, FIG. 20 shows a case where M = 1 in the first row of the step (1) extraction result table 1100 that is the extraction result of step (1). FIG. 20 is an explanatory diagram showing an example of the data structure of argument line = step (1) extraction result first line 2000. Argument line = step (1) The extraction result first line 2000 has an order field 2010, an operation field 2020, a role field 2030, a hierarchy field 2040, and a file ID field 2050. That is, the argument line = step (1) extraction result first line 2000 is the target of copying the first line of the step (1) extraction result table 1100.

  In step S1902, process C is performed. Process C will be described later using the flowchart shown in the example of FIG. FIG. 21 shows the state of the argument line at the time when the process C is finished = step (1) replacement of the sub-folder (child folder) 2100 of the first acquisition line for the extraction result first line 2000 as an object. FIG. 21 is an explanatory diagram showing an example of the data structure of the hierarchy subflow replacement (child folder) 2100 of the first acquisition line. The hierarchy subflow replacement (child folder) 2100 of the first acquisition line has an order column 2110, an operation column 2120, a role column 2130, a subflow column 2140, and a file ID column 2150. That is, the “hierarchy” is converted to “subflow” by the process C.

In step S1904, the operation rule application module 122 determines whether or not the operation column 2120 of the argument row (replacement (child folder) 2100 of the hierarchy subflow of the first acquisition row) is “registered”. If it is “registration”, the process proceeds to step S1906; otherwise, the process proceeds to step S1908.
In step S1906, the role / subflow rule application module 123 determines that the combination of the values in the role column 2130 and the subflow column 2140 of the argument row (replacement (child folder) 2100 of the hierarchical subflow of the first acquisition row) is step (2). If it does not exist in the extraction result M, the argument line is included in the extraction result M. That is, it is determined whether or not an operation (registration) of the same subflow has already been extracted by a person having the same role, and if it is not extracted, it is extracted as an extraction result M. FIG. 22 shows the state of the step (2) extraction result 1 table 2200 for the hierarchical subflow replacement (child folder) 2100 of the first acquired line at the time when step S1906 is completed. FIG. 22 is an explanatory diagram showing an example of the data structure of the step (2) extraction result 1 table 2200. Step (2) The extraction result 1 table 2200 has an order column 2210, an operation column 2220, a roll column 2230, a subflow column 2240, and a file ID column 2250. That is, since nothing is extracted in the extraction result 1 (extraction result 1 table 1700), the row of the hierarchy subflow replacement (child folder) 2100 of the first acquisition row is changed to step (2) extraction result 1 It is included in the table 2200.

In step S1908, the operation rule application module 122 determines whether or not the operation column 2120 of the argument row (replacement (child folder) 2100 of the hierarchy subflow of the first acquisition row) is “update”. If it is “update”, the process proceeds to step S1910; otherwise, the process proceeds to step S1999 (ends process A and returns to step S1606 in the flowchart shown in the example of FIG. 16).
In step S1910, the file ID rule application module 124 includes the file path in the file ID (file path) column of the argument row in the row where the operation column of the extraction result M table in step (2) is “registered”. If so, an argument row is included in the table of extraction results M in step (2). In other words, if the operation has been performed, the registration should have already been performed, and if the same file path is included (update to an already registered document), the workflow M Therefore, the argument row is included in the table of the extraction result M.

In step S1912, the argument line is deleted from the extraction result of step (1) (step (1) extraction result table 1100). However, the argument line to be deleted here refers to a line included in the extraction result M in the process of step S1906 or step S1910. Therefore, the lines that are not included in the extraction result M remain as they are without being deleted.
FIG. 23 shows an example of the state of the step (1) extraction result table 1100 at the time when the process of step S1912 ends. FIG. 23 is an explanatory diagram showing an example of the data structure of the step (1) extraction result table 2300. Step (1) The extraction result table 2300 has an order column 2310, an operation column 2320, a roll column 2330, a hierarchy column 2340, and a file ID column 2350. That is, step (1) is obtained by deleting the order 1 row from the extraction result table 1100.

FIG. 24 is a flowchart illustrating a processing example of the processing C according to the first embodiment. This process is performed by the business flow extraction module 120. This is the processing of step S1902 in the flowchart shown in the example of FIG. Convert hierarchies into subflows.
In step S2402, the name of the highest folder in the file path in the hierarchy column of the argument row is replaced with the subflow column as a value. This processing is performed according to the hierarchical subflow correspondence column 812 of the setting table 810. As a specific example, the folder names of the quotation request folder 611, the quotation folder 614, and the order folder 617 shown in the example of FIG.

FIG. 25 is an explanatory diagram illustrating a processing result example of step (2) according to the first embodiment.
The step (1) extraction result table 2500 shown in the example of FIG. 25A shows the processing result of step (1) (equivalent to the step (1) extraction result table 1100 shown in the example of FIG. 11). Step (1) The extraction result table 2500 includes an order column 2510, an operation column 2520, a roll column 2530, a hierarchy column 2540, and a file ID column 2550.

The step (2) extraction result 1 table 2500A shown in the example of FIG. 25B is an operation extracted as the business flow 1.
Step (2) The extraction result 1 table 2500A has an order column 2510A, an operation column 2520A, a roll column 2530A, a subflow column 2540A, and a file ID column 2550A. That is, in step (1), the hierarchy column 2540 of the extraction result table 2500 is converted into the subflow column 2540A (processing C), and the operation column 2520 is “registered” and the combination of the role and the subflow appears first. Then, in the operation column 2520, “update” in which the file path already exists in the step (2) extraction result 1 table 2500A is extracted.

Step (2) extraction result 2 table 2500B shown in the example of FIG. 25C is an operation extracted as the business flow 2.
Step (2) The extraction result 2 table 2500B has an order column 2510B, an operation column 2520B, a roll column 2530B, a subflow column 2540B, and a file ID column 2550B. That is, the step (1) in which the hierarchy column 2540 of the extraction result table 2500 is converted into the subflow column 2540B (process C), and the combination of the role and the subflow appears second in the operation column 2520 “registration”. Of the extracted “update” in the operation column 2520, the file path already extracted in the step (2) extraction result 2 table 2500B is extracted.

FIG. 26 is an explanatory diagram illustrating a presentation example of a processing result by the business flow presentation module 130 according to the first embodiment.
The extraction result 1 2600A shown in the example of FIG. 26A illustrates the step (2) extraction result 1 table 2500A shown in the example of FIG. 25B.
The reception staff 2610A, the estimate / order staff 2620A, and the management staff 2630A are generated from the role column 2530A of the step (2) extraction result 1 table 2500A.
For each activity (quotation request_registration 2611A, quotation request_update 2631A, quotation_registration 2621A, quotation_update 2633A, order_registration 2623A), a link icon (quotation request document 1 2612A) to the document used to extract the business flow , Quotation Request Form 1 2632A, Quotation Form 1 2622A, Quotation Form 1 2634A, Order Form 1 2624A).
And each activity is connected with the arrow according to the order column 2510A.
Each activity of extraction result 1 2600A corresponds to each row of the extraction result of step (2) (step (2) extraction result 1 table 2500A), and the activity name is a character string in operation column 2520A and subflow column 2540A. It is assumed to be consolidated. For example, the activity name of the quotation request_registration 2611A on the first line is “quotation request_registration” by connecting the subflow “quotation request” and the operation “registration”.

Similarly, the extraction result 2 2600B shown in the example of FIG. 26B illustrates the step (2) extraction result 2 table 2500B shown in the example of FIG. 25C.
The business flow presentation module 130 presents a plurality of extraction results (extraction result 1 2600A and extraction result 2 2600B). For example, the common part is shown in blue, and the non-common part is shown in red (in FIG. 26, the estimate_update 2633A is indicated by hatching).

Next, a second embodiment will be described.
The module configuration example of the second embodiment is the same as that of the first embodiment (FIGS. 1 to 5).
The second embodiment corresponds to the case where the document management system 140 stores a document having a hierarchical structure as shown in the example of FIG. FIG. 27 is an explanatory diagram illustrating a configuration example of a document in the document DB 141. In other words, unlike the hierarchical structure targeted by the first embodiment, the order receiving work folder 2710 is not divided into folders, and the documents (quotation request form 1 2711 to order form 2 2716) are directly stored. It corresponds to the case. The name of the activity is included as a file name according to a predetermined rule.

  In order to support such a hierarchical structure, the setting table 2810 in the setting / result table group 2800 of the business flow extraction system 200 (corresponding to the setting table 810 shown in the example of FIG. 8 in the first embodiment). ) Has an analysis target column 2811 and a hierarchical subflow correspondence column 2812 as shown in the example of FIG. FIG. 28 is an explanatory diagram showing an example of the data structure of the setting / result table group 2800. The analysis target column 2811 is equivalent to the analysis target column 811 of the setting table 810. The hierarchical subflow correspondence column 2812 corresponds to the hierarchical subflow correspondence column 812 of the setting table 810, and its content is a regular expression for extracting a subflow from a character string that is a file path. The regular expression shown in the example of FIG. 28 extracts, for example, the character string “order” from the order form 27716 as a subflow.

FIG. 29 is a flowchart illustrating a processing example of step (1) according to the second embodiment. This process is performed by the operation history extraction module 110. The operation history extraction module 110 acquires the folder to be analyzed from the analysis target column 2811 of the setting table 2810, acquires the operation history of the document under the folder to be analyzed from the document management system 140, and the business flow extraction module Information necessary for the processing in 120 (order, operation (operation type), role, hierarchy, file ID) is extracted. The role is acquired from the user management system 150.
The processing from step S2902 to step S2908 is equivalent to the processing from step S902 to step S908 of the flowchart shown in the example of FIG. 9 according to the first embodiment.
In step S2910, the operation history change module 112 determines, based on the processing result in step S2908, from the file path in the file ID column 3040, the hierarchical subflow correspondence column 2812 of the setting table 2810 (in this case, the target of the regular expression) Is added to the “hierarchy” column (step (1) hierarchy column 3140 in the extraction result table 3100). .

As an operation history to be processed according to the second embodiment, there is an acquisition operation history table 3000 shown in the example of FIG. FIG. 30 is an explanatory diagram of an exemplary data structure of the acquisition operation history table 3000. The acquisition operation history table 3000 includes a date / time column 3010, an operation column 3020, a user 3030, a file ID column 3040, and the like, and corresponds to the acquisition operation history table 1000 illustrated in the example of FIG.
Further, by the processing shown in the example of FIG. 29, the acquisition operation history table 3000 becomes like the step (1) extraction result table 3100 shown in the example of FIG. FIG. 31 is an explanatory diagram showing an example of the data structure of the step (1) extraction result table 3100. Step (1) The extraction result table 3100 has an order column 3110, an operation column 3120, a role column 3130, a hierarchy column 3140, and a file ID column 3150. The step (1) extraction result table shown in the example of FIG. This corresponds to 1100.

The processing of step (2) performed by the second embodiment is equivalent to the processing examples according to the flowcharts shown in the examples of FIGS. 12, 16, and 19 in the first embodiment. However, the process C follows the flowchart shown in the example of FIG.
FIG. 32 is a flowchart illustrating a processing example of the processing C according to the second embodiment. This process is performed by the business flow extraction module 120. This is the processing of step S1902 in the flowchart shown in the example of FIG. Convert hierarchies into subflows.
In step S3202, the regular expression in the hierarchical subflow correspondence column 2812 of the setting table 2810 is used to extract the subflow name from the character string in the hierarchical column of the acquired argument line, and the hierarchical column is replaced with the subflow column.

A processing example of the flowchart shown in the example of FIG. 32 will be described with reference to FIGS.
An example of an argument line in process C is shown in FIG. FIG. 33 is an explanatory diagram of an example of the data structure of the first row 3300 of the extraction result in step (1). Step (1) The extraction result first line 3300 has an order column 3310, an operation column 3320, a roll column 3330, a hierarchy column 3340, and a file ID column 3350. That is, step (1) extraction result first row 3300 is the target of copying the first row of step (1) extraction result table 3100.
An example of FIG. 34 shows the state of the step (1) hierarchical subflow replacement (regular expression) 3400 of the first acquisition line for the first (3) extraction result first line 3300 at the time when the process C ends. FIG. 34 is an explanatory diagram of an example of the data structure of the hierarchical subflow replacement (regular expression) 3400 of the first acquisition line. The hierarchical subflow replacement (regular expression) 3400 of the first acquisition line has an order column 3410, an operation column 3420, a role column 3430, a subflow column 3440, and a file ID column 3450. That is, the “hierarchy” is converted to “subflow” by the process C.

FIG. 35 is an explanatory diagram illustrating an example of a processing result according to the second embodiment.
The step (1) extraction result table 3500 shown in the example of FIG. 35A shows the processing result of step (1) (corresponding to the step (1) extraction result table 3100 shown in the example of FIG. 31). Step (1) The extraction result table 3500 includes an order column 3510, an operation column 3520, a roll column 3530, a hierarchy column 3540, and a file ID column 3550.

The step (2) extraction result 1 table 3500A shown in the example of FIG. 35B is a table extracted as the business flow 1.
Step (2) The extraction result 1 table 3500A has an order column 3510A, an operation column 3520A, a roll column 3530A, a subflow column 3540A, and a file ID column 3550A. This corresponds to the step (2) extraction result 1 table 2500A shown in the example of FIG. 25B in the processing example of the first embodiment.

The step (2) extraction result 2 table 3500B shown in the example of FIG. 35C is a table extracted as the business flow 2.
Step (2) The extraction result 2 table 3500B has an order column 3510B, an operation column 3520B, a roll column 3530B, a subflow column 3540B, and a file ID column 3550B. This corresponds to the step (2) extraction result 2 table 2500B shown in the example of FIG. 25C in the processing example of the first embodiment.

Next, a third embodiment will be described.
The module configuration example of the third embodiment is the same as that of the first embodiment (FIGS. 1 to 5).
The third embodiment corresponds to the case where the document management system 140 stores a document having a hierarchical structure as shown in the example of FIG. FIG. 36 is an explanatory diagram illustrating a configuration example of a document in the document DB 141. That is, unlike the hierarchical structure targeted by the first embodiment or the second embodiment, the order receiving work folder 3610 is divided into folders for each fiscal year (2008 year folder 3620), and each folder for each case. This is divided (case 101 folder 3630, case 102 folder 3640), and below that is equivalent to the hierarchical structure of folders and documents shown in the example of FIG. This corresponds to the case where a plurality of hierarchies are used. The name of the activity is included in a predetermined rule as a folder name of any hierarchy.

  In order to support such a hierarchical structure, a setting table 3710 in the setting / result table group 3700 of the business flow extraction system 200 (corresponding to the setting table 810 shown in the example of FIG. 8 in the first embodiment). ) Has an analysis target column 3711 and a hierarchical subflow correspondence column 3712 as shown in the example of FIG. FIG. 37 is an explanatory diagram showing an example of the data structure of the setting / result table group 3700. The analysis target column 3711 is equivalent to the analysis target column 811 of the setting table 810. The hierarchical subflow correspondence column 3712 corresponds to the hierarchical subflow correspondence column 812 of the setting table 810, and the content thereof is a regular expression for extracting a subflow from a character string that is a file path. The regular expression shown in the example of FIG. 37 extracts, for example, a character string “request for quotation” from the character string of the file path of the request for quotation 3632 as a subflow.

FIG. 38 is a flowchart illustrating a processing example of step (1) according to the third embodiment. This process is performed by the operation history extraction module 110. The operation history extraction module 110 acquires the folder to be analyzed from the analysis target column 3711 of the setting table 3710, acquires the operation history of the document under the folder to be analyzed from the document management system 140, and the business flow extraction module Information necessary for the processing in 120 (order, operation (operation type), role, hierarchy, file ID) is extracted. The role is acquired from the user management system 150.
The processing from step S3802 to step S3808 is equivalent to the processing from step S902 to step S908 of the flowchart shown in the example of FIG. 9 according to the first embodiment.
In step S3810, the operation history change module 112 determines, based on the processing result in step S3808, from the file path in the file ID column 3940, the hierarchical subflow correspondence column 3712 of the setting table 3710 (in this case, the target of the regular expression) In the “hierarchy” column (step (1) hierarchy of the extraction result table 4000). Column 4040).

As an operation history to be processed according to the third embodiment, there is an acquisition operation history table 3900 shown in the example of FIG. FIG. 39 is an explanatory diagram of an exemplary data structure of the acquisition operation history table 3900. The acquisition operation history table 3900 includes a date / time column 3910, an operation column 3920, a user 3930, a file ID column 3940, and the like, and corresponds to the acquisition operation history table 1000 illustrated in the example of FIG.
Also, the acquisition operation history table 3900 becomes like the step (1) extraction result table 4000 shown in the example of FIG. 40 by the processing shown in the example of FIG. FIG. 40 is an explanatory diagram showing an example of the data structure of the step (1) extraction result table 4000. Step (1) The extraction result table 4000 has an order column 4010, an operation column 4020, a role column 4030, a hierarchy column 4040, and a file ID column 4050. The step (1) extraction result table shown in the example of FIG. This corresponds to 1100.

The processing of step (2) performed by the third embodiment is equivalent to the processing examples according to the flowcharts shown in the examples of FIGS. 12, 16, and 19 in the first embodiment. However, the process C follows the flowchart shown in the example of FIG.
FIG. 41 is a flowchart illustrating a processing example of the processing C according to the third embodiment. This process is performed by the business flow extraction module 120. This is the processing of step S1902 in the flowchart shown in the example of FIG. Convert hierarchies into subflows.
In step S4102, the subflow name is extracted from the character string in the hierarchy column of the acquired argument row using the regular expression in the hierarchy subflow correspondence column 3712 of the setting table 3710, and the hierarchy column is replaced with the subflow column.

A processing example of the flowchart shown in the example of FIG. 41 will be described with reference to FIGS.
An example of argument lines in process C is shown in FIG. FIG. 42 is an explanatory diagram showing an example of the data structure of the step (1) extraction result first row 4200. Step (1) The extraction result first line 4200 has an order column 4210, an operation column 4220, a roll column 4230, a hierarchy column 4240, and a file ID column 4250. That is, step (1) extraction result first line 4200 is the target of copying the first line of acquisition operation history table 3900.
The example of FIG. 43 shows the state of the step (1) hierarchical subflow replacement (regular expression) 4300 of the first acquisition line targeted for the extraction result first line 4200 at the time when the process C is completed. FIG. 43 is an explanatory diagram of an example of the data structure of the hierarchical subflow replacement (regular expression) 4300 in the first acquisition line. The hierarchical subflow replacement (regular expression) 4300 of the first acquisition line has an order column 4310, an operation column 4320, a role column 4330, a subflow column 4340, and a file ID column 4350. That is, the “hierarchy” is converted to “subflow” by the process C.

FIG. 44 is an explanatory diagram of a processing result example according to the third embodiment.
The step (1) extraction result table 4400 shown in the example of FIG. 44A shows the processing result of step (1) (corresponding to the step (1) extraction result table 4000 shown in the example of FIG. 40). Step (1) The extraction result table 4400 has an order column 4410, an operation column 4420, a roll column 4430, a hierarchy column 4440, and a file ID column 4450.

The step (2) extraction result 1 table 4400A shown in the example of FIG. 44B is a table extracted as the business flow 1.
Step (2) The extraction result 1 table 4400A has an order column 4410A, an operation column 4420A, a roll column 4430A, a subflow column 4440A, and a file ID column 4450A. This corresponds to the step (2) extraction result 1 table 2500A shown in the example of FIG. 25B in the processing example of the first embodiment.

The step (2) extraction result 2 table 4400B shown in the example of FIG. 44C is a table extracted as the business flow 2.
Step (2) The extraction result 2 table 4400B has an order column 4410B, an operation column 4420B, a roll column 4430B, a subflow column 4440B, and a file ID column 4450B. This corresponds to the step (2) extraction result 2 table 2500B shown in the example of FIG. 25C in the processing example of the first embodiment.

Next, the case where this embodiment is used for financial internal control will be described.
In recent years, financial internal control has been required. With regard to the financial internal control, “Internal Control – Integrated Framework” announced by COSO (Treadway Committee Organizing Committee) in 1992 has become the de facto standard.・ Board of Directors, Management and other organizations intended to provide reasonable assurance to achieve three objectives: efficiency, (2) reliability of financial statements, and (3) compliance with relevant laws and regulations. It is defined as a single process carried out by staff.
This embodiment is preferably used for financial internal control (hereinafter also referred to as internal control).
In order to carry out financial internal control, the relationship between activities / systems / resources / knowledge information is organized and business processes (hereinafter simply referred to as processes) are documented, and the documents are utilized and evaluated (maintenance evaluation, operational evaluation). It is necessary to construct a system for
First, “Basic 4 Documents” of internal control to be documented will be described.
Basic 4 documents are basic documents created for each business process subject to internal control. Specifically, business description, business flow diagram, RCM (risk control matrix), separation of duties There is a table.
The business description is also called narrative. This is a documented flow of a series of operations from the start of the transaction to the final entry to the general ledger and reporting. Regulatory documents such as personnel regulations and accounting business regulations are higher-level documents of the business description, and the revision affects the business description. The business manual is a sub-document of the business description and is affected by the revision.
The business flow diagram is a visual flowchart of a series of business flows from the start of a transaction to the final entry to the general ledger and reporting. Risk and control are also placed in this workflow.
The RCM is a summary table of internal control activities related to business processes, the key control points (assertions) to be achieved, the assumed risks, and the corresponding internal control activities.
The segregation of duties table is used to check whether there is a duplication of processing by the same person in charge that causes a financial control problem in the flow of business processes.
Assertion is a precondition for financial information to be considered as reliable information. Specifically, it includes reality, completeness, evaluation, rights and obligations, period / allocation, and display. Items are commonly used. However, it may be partially changed, that is, customized by each company or audit corporation, and is not necessarily limited to the above-mentioned six items.
Risk refers to an impediment to assertions assumed in business processes.
Control (control) refers to internal control activities against risks. Control types include preventive and detective.
In addition, it is necessary to conduct an evaluation that uses the trail to test whether the system is operating as documented. Therefore, this trail must be preserved.

The above-described embodiment is suitable for creating a business flow diagram in internal control. In particular, the business procedure presented by the business flow presentation module 130 (for example, the one shown in the example of FIG. 26) may be information relating to the business flow in internal control (for example, the business flow diagram or its prototype). Therefore, it can be used to introduce an internal control system.
In addition, when the business flow presentation module 130 of the above-described embodiment presents a common activity and other activities in different modes in activities in a plurality of business operations, the activities other than the common activities can be risks. Judgment may be made and the message may be presented. Further, it may be determined that an activity other than the common activity can be controlled, and the message may be presented.

  The hardware configuration of a computer (business flow extraction system 200, document management system 140, user management system 150) on which the program according to the above-described embodiment is executed is a general computer as illustrated in FIG. Specifically, it is a personal computer, a computer that can be a server, or the like. That is, as a specific example, a CPU 4501 is used as a processing unit (calculation unit), and a RAM 4502, a ROM 4503, and an HD 4504 (for example, a hard disk can be used) are used as storage devices. A CPU 4501 for executing programs such as the operation history extraction module 110, the business flow extraction module 120, and the business flow presentation module 130, a RAM 4502 for storing the programs and data, a program for starting the computer, and the like are stored. ROM 4503, auxiliary storage device HD4504, input device 4506 for inputting data such as a keyboard and a mouse, presentation device 4505 such as a CRT or a liquid crystal display, and a communication line interface 4507 for connecting to a communication network (for example, a network) An interface card can be used), and a bus 4508 is used for connecting and exchanging data. A plurality of these computers may be connected to each other via a network.

Among the above-described embodiments, the computer program is a computer program that reads the computer program, which is software, in the hardware configuration system, and the software and hardware resources cooperate with each other. Is realized.
The hardware configuration shown in FIG. 45 shows one configuration example, and the above-described embodiment is not limited to the configuration shown in FIG. 45, and the modules described in the above-described embodiment can be executed. Any configuration may be used. For example, some modules may be configured by dedicated hardware (for example, ASIC), and some modules may be in an external system and connected via a communication line. A plurality of systems shown in FIG. 5 may be connected to each other via communication lines so as to cooperate with each other. In particular, in addition to personal computers, information appliances, copiers, fax machines, scanners, printers, and multifunction machines (image processing apparatuses having two or more functions of scanners, printers, copiers, fax machines, etc.) Etc. may be incorporated.

  In the above embodiment, examples of “registration” and “update” are shown as operations, but other operations may be targeted. For example, if “reference” is included in the operation and there is a “reference” operation in the operation history, processing may be performed so as not to be extracted as a business flow.

The program described above may be provided by being stored in a recording medium, or the program may be provided by communication means. In that case, for example, the above-described program may be regarded as an invention of a “computer-readable recording medium recording the program”.
The “computer-readable recording medium on which a program is recorded” refers to a computer-readable recording medium on which a program is recorded, which is used for program installation, execution, program distribution, and the like.
The recording medium is, for example, a digital versatile disc (DVD), which is a standard established by the DVD Forum, such as “DVD-R, DVD-RW, DVD-RAM,” and DVD + RW. Standard “DVD + R, DVD + RW, etc.”, compact disc (CD), read-only memory (CD-ROM), CD recordable (CD-R), CD rewritable (CD-RW), Blu-ray disc ( Blu-ray Disc (registered trademark), magneto-optical disk (MO), flexible disk (FD), magnetic tape, hard disk, read-only memory (ROM), electrically erasable and rewritable read-only memory (EEPROM), flash Includes memory, random access memory (RAM), etc. .
The program or a part of the program may be recorded on the recording medium for storage or distribution. Also, by communication, for example, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wired network used for the Internet, an intranet, an extranet, etc., or wireless communication It may be transmitted using a transmission medium such as a network or a combination of these, or may be carried on a carrier wave.
Furthermore, the program may be a part of another program, or may be recorded on a recording medium together with a separate program. Moreover, it may be divided and recorded on a plurality of recording media. Further, it may be recorded in any manner as long as it can be restored, such as compression or encryption.

It is a conceptual module block diagram about the structural example of 1st Embodiment. It is explanatory drawing which shows the system configuration example for implement | achieving 1st to 3rd embodiment. It is explanatory drawing which shows the example of a module structure in an operation history extraction module, a document management system, and a user management system. It is explanatory drawing which shows the module structural example in a business flow extraction module. It is explanatory drawing which shows the module structural example in a business flow presentation module. It is explanatory drawing which shows the structural example of the document in document DB. It is explanatory drawing which shows the example of a data structure of a user information table. It is explanatory drawing which shows the example of a data structure of a setting and a result table group. It is a flowchart which shows the process example of step (1) by 1st Embodiment. It is explanatory drawing which shows the example of a data structure of an acquisition operation log | history table. It is explanatory drawing which shows the example of a data structure of step (1) extraction result table. It is a flowchart which shows the process example of step (2) by 1st Embodiment. It is explanatory drawing which shows the example of a data structure of step (1) extraction result table. It is explanatory drawing which shows the example of a data structure of step (2) extraction result 1 table. It is explanatory drawing which shows the example of a data structure of step (2) extraction result 2 table. It is a flowchart which shows the process example of the process B by 1st Embodiment. It is explanatory drawing which shows the example of a data structure of extraction result 1 table. It is explanatory drawing which shows the example of a data structure of extraction result 1 table. It is a flowchart which shows the process example of the process A by 1st Embodiment. It is explanatory drawing which shows the data structure example of argument line = step (1) extraction result 1st line. It is explanatory drawing which shows the example of a data structure of substitution (child folder) of the hierarchy subflow of the 1st acquisition line. It is explanatory drawing which shows the example of a data structure of step (2) extraction result 1 table. It is explanatory drawing which shows the example of a data structure of step (1) extraction result table. It is a flowchart which shows the process example of the process C by 1st Embodiment. It is explanatory drawing which shows the example of a process result by 1st Embodiment. It is explanatory drawing which shows the example of a presentation of the process result by 1st Embodiment. It is explanatory drawing which shows the structural example of the document in document DB. It is explanatory drawing which shows the example of a data structure of a setting and a result table group. It is a flowchart which shows the process example of step (1) by 2nd Embodiment. It is explanatory drawing which shows the data structure example of an acquisition operation log | history table. It is explanatory drawing which shows the example of a data structure of step (1) extraction result table. It is a flowchart which shows the process example of the process C by 2nd Embodiment. It is explanatory drawing which shows the example of a data structure of step (1) extraction result 1st line. It is explanatory drawing which shows the example of a data structure of substitution (regular expression) of the hierarchy subflow of the 1st acquisition line. It is explanatory drawing which shows the example of a process result by 2nd Embodiment. It is explanatory drawing which shows the structural example of the document in document DB. It is explanatory drawing which shows the example of a data structure of a setting and a result table group. It is a flowchart which shows the process example of step (1) by 3rd Embodiment. It is explanatory drawing which shows the data structure example of an acquisition operation log | history table. It is explanatory drawing which shows the example of a data structure of step (1) extraction result table. It is a flowchart which shows the process example of the process C by 3rd Embodiment. It is explanatory drawing which shows the example of a data structure of step (1) extraction result 1st line. It is explanatory drawing which shows the example of a data structure of substitution (regular expression) of the hierarchy subflow of the 1st acquisition line. It is explanatory drawing which shows the example of a process result by 3rd Embodiment. It is a block diagram which shows the hardware structural example of the computer which implement | achieves 1st to 3rd embodiment.

110 ... Operation history extraction module 111 ... Target operation history extraction module 112 ... Operation history change module 120 ... Business flow extraction module 121 ... Subflow extraction module 122 ... Operation rule application module 123 ... Role / subflow rule application module 124 ... File ID rule application Module 130 ... Business flow presentation module 131 ... Activity name generation module 132 ... File link generation module 133 ... Common activity extraction module 134 ... Presentation module 140 ... Document management system 141 ... Document DB
142 ... operation history DB
150 ... User management system 151 ... User information DB
200 ... Business flow extraction system

Claims (5)

An operation history receiving means for receiving an operation history for a document;
Business procedure extraction means for extracting a business procedure based on the operation history received by the operation history reception means;
Presenting means for presenting the work procedure extracted by the work procedure extracting means ;
Operator / role change means to change operator to role in business
Comprising
The operation history received by the operation history receiving means includes an operation, a document name that is an operation target, and an operator when the operation is performed,
The business procedure extracting unit extracts an activity in a business based on the operation in the operation history and a document name that is the operation target, and the role changed by the operator / role change unit and the operation target are extracted. Based on a document name, determine whether the activity is in a different business, extract the procedure of the business for each business,
The information processing apparatus , wherein the presenting means presents a procedure of the business for each business . The information processing apparatus according to claim 1 , wherein the presenting unit presents a common activity and other activities differently in activities in a plurality of tasks. The operation target document is stored in a storage device having a hierarchical structure, and includes the name of the hierarchy as the document name,
3. The activity according to claim 1, wherein the business procedure extraction unit extracts an activity in the business based on the operation and the name of the hierarchy in the document name that is the operation target. Information processing device. The presenting means presents a business procedure as information related to a business flow in financial internal control, and presents that a common activity and other activities can be subject to risk or control in activities in a plurality of business operations. The information processing apparatus according to any one of claims 1 to 3 , wherein the information processing apparatus is characterized. Computer
An operation history receiving means for receiving an operation history for a document;
Business procedure extraction means for extracting a business procedure based on the operation history received by the operation history reception means;
Presenting means for presenting the work procedure extracted by the work procedure extracting means ;
Operator / role change means to change operator to role in business
Function as
The operation history received by the operation history receiving means includes an operation, a document name that is an operation target, and an operator when the operation is performed,
The business procedure extracting unit extracts an activity in a business based on the operation in the operation history and a document name that is the operation target, and the role changed by the operator / role change unit and the operation target are extracted. Based on a document name, determine whether the activity is in a different business, extract the procedure of the business for each business,
An information processing program characterized in that the presenting means presents a procedure of the business for each business .

Images