JP2007249750A - Business consistency verification system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily verify consistency between pieces of treating business based on a business rule even if the treating business or the business rule inside an enterprise is changed. <P>SOLUTION: A verification item extraction means M33 extracts prescribed items including treating business specification information, generation time specification information, and cost information from a treating business storage means M31 as verification item information. A rule information storage means M51 stores and holds rule information wherein the treating business specification information of the treating business and the treating business specification information of the treating business generated just before the treating business are associated. A verification means M57 verifies whether or not the verification item information corresponding to the treating business generated just before the treating business corresponding to the acquired verification item information is present in the verification item information stored and held in the verification item storage means M59 on the basis of the rule information. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a business consistency verification system, and more particularly, to a system for easily verifying consistency between processing tasks generated in a company based on business rules.

In a corporate activity composed of a plurality of processing operations in a plurality of departments, it is necessary to ensure consistency with the business rules of the processing operations executed in each department. For this reason, the consistency of the processing work is ensured by realizing the IT system of the processing work and ensuring the consistency of the data in the system.

  However, a general in-house business system is not intended for the entire company. If anything, it is often a system for a specific processing task. For this reason, a plurality of systems are often used in one company. For example, build and operate a “sales system” for order / customer management, a “purchase system” for purchasing goods from other companies, and a “worktime management system” for employee work management. Yes.

In this way, if there is a change in processing work in an environment with multiple business systems, it is possible to make frequent system modifications to deal with a narrow range of work, such as modifying existing systems or adding new systems. But,
If such limited system modifications are repeated, it becomes difficult to ensure data consistency between different systems.

  It is also possible to employ an ERP or a workflow system for the purpose of optimizing company-wide processing operations and ensuring the consistency of processing operation procedures. However, in the ERP and workflow system, it is necessary to redesign the conventional business procedure and it is necessary to make a complete system modification, so that it is difficult to perform the system modification in a timely manner. For this reason, there is a tendency that the divergence between the current processing task procedure and the processing procedure in the system is widened, and the introduction of ERP and workflow system has not progressed.

  Under such circumstances, conventionally, a workflow support system has been proposed. A conventional workflow support system 100 will be described with reference to FIG. The workflow support system 100 stores a task request reception database 101 that holds a request to execute a task received via a network, stores information on each task that has been performed as a task history, and stores connection information between the task histories. A task history / task connection database 102, a workflow rule base 103 that stores rules defining the relationship between a task and a partial task for executing the task, and a task history stored in the task history / task connection database 102 And a rule compliance determination processing unit 104 that verifies whether the rules stored in the workflow rule base 103 are compliant. Note that at least the rule base 103 is provided in a distributed manner, for example, for each department, and a local rule can be set for each department.

  Next, rules to be set will be described. The rules are written as follows:

Article purchase processing (? Requester, accounting department,? Purchase slip) ← purchase slip creation (? Requester,? Requester,? Purchase slip), approval process (? Requester,? Superior,? Purchase slip), ordering Request (? Requester, purchasing department,? Purchase slip), delivery confirmation report (? Requester, accounting department,? Purchase slip).
Here, the first argument represents the performer, the second argument represents the requester (also a report destination), and the third and subsequent arguments represent information or electronic documents to be exchanged and stored or their storage locations. Also,? Indicates a variable. It is important that the variable names in this rule indicate the relationship that the same name should have the same value, and the name itself may be discarded after the rule is applied. ← indicates an implication (if it is ~). That is, a ← b, c is a if b and c. Procedural interpretation of this proof process by backward reasoning requires that both b and c must be achieved in order for a to be achieved (proven), and therefore the task of a must be activated (which must be achieved) If this occurs, the tasks b and c are started. In addition, b and c are allowed to be executed simultaneously (in parallel).

JP-A-11-259581

  The above-described workflow support system 100 has the following problems. In the workflow support system 100, it is necessary to describe all partial tasks necessary for a certain task as rules. For example, in the article purchase processing, purchase slip creation processing, approval processing, order request processing, and delivery confirmation report processing must be described as rules.

  That is, in order to determine whether or not a certain task is suitable for the rule, there is a problem that it is necessary to determine in advance what partial task is required for the task. When a task (task A) is a partial task of another task (task B), if the rule of task A is changed, the change of the rule affects the rule of task B. That is, there is a problem that a change of a rule for a certain task may result in a review of the rules for all tasks.

  An object of the present invention is to provide a business consistency verification system capable of easily verifying consistency between processing tasks based on the business rules even if there is a change in processing jobs or changes in business rules in the company. .

  Means for solving the problems relating to the present invention and effects of the present invention will be described below.

  In the business consistency verification system, the business consistency verification apparatus, the business consistency verification program, and the business consistency verification method according to the present invention, verification item information indicating a value corresponding to a predetermined registration item is acquired, and one or more And storing the obtained verification item information in a rule information storage means for storing or holding one or more rule information in which one or a plurality of rule information associated with a processing job having a registered item and a processing job occurring immediately before the processing job is associated, Whether the verification item information stored and held in the verification item storage means corresponds to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information is indicated in the rule information. Verify based on.

  Thereby, it is possible to easily verify the consistency between the processing tasks based on the rule information that defines only the context of the processing tasks.

  In the business consistency verification system, the business consistency verification apparatus, the business consistency verification program, and the business consistency verification method according to the present invention, further, the verification item information including the processing business specifying information for specifying the processing business is acquired, The verification item stored in the verification item storage unit by comparing the processing operation identification information of the verification item information stored in the verification item storage unit with the processing operation identification information of the acquired verification item information Whether the information corresponding to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information exists in the information is generated immediately before the processing job specifying information of the processing job and the processing job Verification is performed based on the rule information associated with the processing task specific information of the processing task to be performed.

  This makes it possible to easily verify the consistency of the order in which processing operations occur.

  In the business consistency verification system, the business consistency verification device, the business consistency verification program, and the business consistency verification method according to the present invention, the verification items further include the occurrence identification information for identifying the time when the processing job occurs. The information is acquired, the verification item information corresponding to the processing operation that occurred immediately before the processing operation corresponding to the acquired verification item information is extracted, the specific information when the extracted verification item information occurs and the occurrence of the acquired verification item information By comparing the time specific information, it is verified whether the acquired verification item information and the extracted verification item information have temporal consistency.

  This makes it possible to easily verify the consistency of the order in which processing operations occur.

  In the business consistency verification system, the business consistency verification apparatus, the business consistency verification program, and the business consistency verification method according to the present invention, at least the amount of resources required in the processing business generated after the processing business The verification item information including the resource information that identifies the resource information of the extracted verification item information is compared with the resource information of the extracted verification item information and the resource information of the acquired verification item information. It is verified whether the resource information of the item information has quantitative consistency.

  Thereby, it is possible to easily verify the consistency of the resources generated before and after the processing work.

  In the business consistency verification system, the business consistency verification device, the business consistency verification program, and the business consistency verification method according to the present invention, further, verification items stored in the verification item storage unit based on the rule information In the information, it is determined whether or not the verification item information of the processing job that occurs immediately before the processing job corresponding to the acquired verification item information exists, and the verification item information does not exist in the verification item storage unit When the determination is made, the verification item information of the processing job generated immediately before the processing job corresponding to the acquired verification item information is stored and held in the verification item storage unit.

  Thereby, it is possible to easily verify whether or not a processing operation that should have occurred is occurring.

  In the business consistency verification system, the business consistency verification apparatus, the business consistency verification program, and the business consistency verification method according to the present invention, the verification items further include the occurrence identification information that identifies the time when the processing job occurs. When the information is acquired and the verification item information of the processing job generated immediately before the processing job corresponding to the acquired verification item information is stored in the verification item storage unit, the value of the occurrence information is not set.

  Thereby, it is possible to easily verify whether or not a processing operation that should have occurred is occurring.

  In the business consistency verification system, the business consistency verification apparatus, the business consistency verification program, and the business consistency verification method according to the present invention, at least the amount of resources required in the processing business generated after the processing business When the verification item information including the resource information for specifying the processing item is acquired, and the verification item information of the processing job generated immediately before the processing job corresponding to the acquired verification item information is stored and held in the verification item storage unit, the resource Do not set information values.

  Thereby, it is possible to easily verify the consistency of expenses between the processing operation that should have occurred and the processing operation immediately after that.

  In the business consistency verification system, the business consistency verification device, the business consistency verification program, and the business consistency verification method according to the present invention, the verification item storage control unit further stores the acquired verification item information in the verification item storage. When the control means finishes storing and holding, the verification process is executed.

  Thereby, the consistency verification of the processing work can be easily performed without the user being aware of it.

  In the business consistency verification system, the business consistency verification apparatus, the business consistency verification program, and the business consistency verification method according to the present invention, when the verification request information for requesting execution of the verification process is further acquired, the verification process is performed. Execute.

  Thereby, it is possible to easily verify the consistency of processing tasks according to the user's will.

  Here, the correspondence relationship between the elements described in the claims and the elements in the embodiment is shown. The business consistency verification system corresponds to the business consistency verification system 1, the business consistency verification apparatus corresponds to the business status monitoring server 23, and the business management apparatus corresponds to the sales system server 25 and the purchase system server 27, respectively.

  The processing task storage means is the hard disk 253 and the hard disk 273, the verification item extraction means is the CPU 251, the memory 252, the CPU 271, and the memory 272, and the verification item providing means is the CPU 251, the memory 252, the communication circuit 258, the CPU 271, the memory 272, and the communication. In the circuit 278, the rule information storage means is in the hard disk 233, the verification item acquisition means is in the CPU 231, the memory 232, and the communication circuit 238, the verification item storage means is in the hard disk 233, the verification item storage control means is in the CPU 231 and the memory 232, The verification means corresponds to the CPU 231 and the memory 232, respectively.

  Processing business information is stored in the sales DB or purchase DB, verification item information is business event data, rule information is business regulation information, processing business specific information is processing business identifier and premise processing business identifier, The occurrence specific information corresponds to the date of occurrence, and the resource information corresponds to the cost.

  Examples of the portable terminal in the present invention will be described below.

1. Overview FIG. 1 shows a functional block diagram according to Embodiment 1 of a business consistency verification system according to the present invention. The business consistency verification system M1 includes a business management apparatus M3 and a business consistency verification apparatus M5. The business management apparatus M3 includes a processing business storage unit M31, a verification item extraction unit M33, and a verification item provision unit M35. The business consistency verification device M5 includes a rule information storage unit M51, a verification item acquisition unit M53, a verification item storage control unit M55, and a verification unit M57.

  The processing work storage means M31 stores and holds one or a plurality of the processing work information.

  The verification item extraction unit M33 extracts, as verification item information, predetermined items including the processing task specifying information, the occurrence specifying information, and the resource information from the processing task storing unit M31.

  The verification item providing means M35 provides verification item information to the business consistency verification device M5.

  The rule information storage means M51 stores and holds one or a plurality of pieces of rule information in which the processing task specifying information of the processing task is associated with the processing task specifying information of the processing task that occurs immediately before the processing task.

  The verification item acquisition unit M53 acquires verification item information.

  The verification item storage control unit M55 stores and holds the acquired verification item information in the verification item storage unit M59. Further, the verification item storage control means M55 is based on the rule information in which the processing work specifying information of the processing work and the processing work specifying information of the processing work generated immediately before the processing work are associated with each other. It is determined whether or not the verification item information stored in the processing item verification item information generated immediately before the processing operation corresponding to the acquired verification item information exists, and the verification item information is the verification item If it is determined that the item does not exist in the item storage unit M59, the verification item storage unit M59 stores the verification item information of the processing job that occurs immediately before the processing job corresponding to the acquired verification item information. Further, the verification item storage control unit M55 stores the verification item information of the processing job generated immediately before the processing job corresponding to the acquired verification item information in the verification item storage unit M59, and stores the information on the occurrence time information. Do not set a value. Further, the verification item storage control unit M55 stores the value of the resource information when the verification item storage unit M59 stores and holds the verification item information of the processing job that occurs immediately before the processing job corresponding to the acquired verification item information. Is not set.

  The verification unit M57 determines whether the verification item information stored in the verification item storage unit M59 includes one corresponding to the processing job generated immediately before the processing job corresponding to the acquired verification item information. Is verified based on the rule information. Further, the verification unit M57 compares the processing task identification information of the verification item information stored and held in the verification item storage unit M59 with the processing task identification information of the acquired verification item information, thereby the verification item storage unit M59. Based on the rule information, whether the verification item information stored and held in the database corresponds to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information exists. . Further, the verification unit M57 extracts the verification item information corresponding to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information, and the identification information at the time of occurrence of the extracted verification item information and the acquired verification item information By comparing the occurrence specific information, it is verified whether or not the acquired verification item information and the extracted verification item information have temporal consistency. Further, the verification unit M57 extracts the verification item information corresponding to the processing job generated immediately before the processing job corresponding to the acquired verification item information, and the resource information of the extracted verification item information and the resource information of the acquired verification item information Are compared to verify whether or not the resource information of the extracted verification item information and the resource information of the acquired verification item information have quantitative consistency. Further, the verification unit M57 executes a verification process when the verification item storage control unit M55 finishes storing and holding the acquired verification item information in the verification item storage control unit.

2. Hardware configuration
2.1. Business Consistency Verification System 1
A hardware configuration of the business consistency verification system 1 will be described with reference to FIG. The business consistency verification system 1 includes a business consistency monitoring system 3, a sales system 5, and a purchasing system 7. The business consistency monitoring system 3 includes a business status monitoring server 23 and a business monitoring department operation terminal 33. The sales system 5 includes a sales system server 25 and a sales department operation terminal 35. The purchase system 7 includes a purchase system server 27 and a purchase department operation terminal 37.

  The business status monitoring server 23 verifies the consistency between business operations occurring in the company. The sales system server 25 manages the order status from customers. The purchase system server 27 manages the procurement of commodities requested for purchase. The operation monitoring department operation terminal 33, the sales department operation terminal 35, and the purchase department operation terminal 37 remotely operate the operation status monitoring server 23, the sales system server 25, and the purchase system server 27, respectively.

  Here, it is assumed that the sales system 5 and the purchasing system 7 are individually developed and operated. That is, it is assumed that there is no data linkage function between the sales system server 25 and the purchase system server 27. In the sales department, the order contents from the customer are input to the sales system server 25 via the sales department operation terminal 35, and at the same time, the request items to the purchasing department are determined from the order contents, and the purchase system server 27 is informed. It is assumed that it is necessary to input via the purchase department operation terminal 37.

2.2. Business condition monitoring server 23
The hardware configuration of the business monitoring server 23 will be described with reference to FIG. The business monitoring server 23 includes a CPU 231, a memory 232, a hard disk 233, and a communication circuit 238. In addition, a keyboard 234, a mouse 235, a display 236, and a CD-ROM drive 237 are connected to the business monitoring server 23.

  The CPU 231 performs processing based on other applications such as an operating system (OS) and a work monitoring server program recorded on the hard disk 233. The memory 232 provides a work area for the CPU 231. The hard disk 233 records and holds other applications such as an operating system (OS) and a business monitoring server program. The business regulation table and the business situation table recorded on the hard disk 233 will be described later.

  The CD-ROM drive 237 reads data from the CD-ROM 239 such as reading a business monitoring server program from the CD-ROM 230 in which the business monitoring server program is recorded, and reading other application programs from other CD-ROMs. Read.

  The keyboard 234 and the mouse 235 accept external commands. The display 236 displays an image such as a user interface.

2.3. Sales System Server 25
The hardware configuration of the sales system server 25 will be described with reference to FIG. The sales system server 25 includes a CPU 251, a memory 252, a hard disk 253, and a communication circuit 258. In addition, a keyboard 254, a mouse 255, a display 256, and a CD-ROM drive 257 are connected to the sales system server 25.

  The CPU 251 performs processing based on other applications such as an operating system (OS) and a sales system server program recorded on the hard disk 253. The memory 252 provides a work area for the CPU 251. The hard disk 253 records and holds other applications such as an operating system (OS) and a sales system server program. The sales database (sales DB) recorded on the hard disk 253 will be described later.

  The CD-ROM drive 257 reads five data from the CD-ROM 239 such as reading the sales system server program from the CD-ROM 250 in which the sales system server program is recorded, and reading other application programs from other CD-ROMs. Read.

  The keyboard 254 and the mouse 255 accept external commands. The display 256 displays an image such as a user interface.

2.4. Purchasing system server 27
The hardware configuration of the purchase system server 27 will be described with reference to FIG. The purchase system server 27 includes a CPU 271, a memory 272, a hard disk 273, and a communication circuit 278. In addition, a keyboard 274, a mouse 275, a display 276, and a CD-ROM drive 277 are connected to the sales system server 27.

  The CPU 271 performs processing based on other applications such as an operating system (OS) and a purchasing system server program recorded in the hard disk 273. The memory 272 provides a work area for the CPU 271. The hard disk 273 records and holds other applications such as an operating system (OS) and a purchasing system server program. The purchase database (purchase DB) recorded on the hard disk 273 will be described later.

  The CD-ROM drive 277 reads five data from the CD-ROM 279, such as reading a purchasing system server program from a CD-ROM 270 in which a sales system server program is recorded, and a program of another application from another CD-ROM. Read.

  The keyboard 274 and the mouse 275 accept external commands. The display 276 displays an image such as a user interface.

2.5. Each Operation Terminal The hardware configuration of the operation monitoring department operation terminal 33 will be described with reference to FIG. The business monitoring department operation terminal 33 includes a CPU 331, a memory 332, a hard disk 333, and a communication circuit 338. In addition, a keyboard 334, a mouse 335, a display 336, and a CD-ROM drive 337 are connected to the operation monitoring / monitoring department operation terminal 33.

  The CPU 331 performs processing based on other applications such as an operating system (OS) and a work monitoring department operation terminal program recorded on the hard disk 333. The memory 332 provides a work area for the CPU 331. The hard disk 333 records and holds other applications such as an operating system (OS) and a business monitoring department operation terminal program.

  The CD-ROM drive 337 reads the operation monitoring department operation terminal program from the CD-ROM 330 in which the operation monitoring department operation terminal program is recorded, and reads other application programs from other CD-ROMs. -Reading data from the ROM 339.

  The keyboard 334 and the mouse 335 accept external commands. The display 336 displays an image such as a user interface.

  The hardware configurations of the sales department operating terminal 35 and the purchasing department operating terminal 37 are the same as the hardware configuration of the business monitoring department operating terminal 33 (see FIG. 6).

3. Data Recorded in the business regulation table and business situation table recorded in the hard disk 233 of the business monitoring server 23, the business DB recorded in the hard disk 253 of the sales system server 25, and the hard disk 273 of the purchasing system server 27. A purchase DB is described.

3.1. Business specification table The business specification table is a table in which business specification information serving as a reference for verifying the consistency of business operations generated between departments is described.

  The business regulation table will be described with reference to FIG. The business regulation table has a [business type classification identifier] column C701, a [business name] column C703, and a [prerequisite business type identifier] column C705. In the [business type identifier] column C701, an identifier for uniquely identifying a business in the business consistency verification system 1 is described. In the [business name] column C703, a name for identifying a business in the company is described. In the [Prerequisite business type identifier] column C705, a business type identifier of a business that is assumed to be implemented in order to perform the business is described.

  For example, when executing a business name “purchase request (business type identifier: B)”, in the case of a business rule that assumes that the business name “order reception (business type identifier: A)” has ended, In the [Prerequisite business] column C705 corresponding to the “purchase request” described in the “business name” column C703, the value “A” of the business type identifier of the business name “order received” is described. The business name “order reception (business type identifier: A)” corresponds to “order reception” described in the [business name] column C703 when there is no business to be premised in the internal business [ Prerequisite job] column C705 describes the value “null (means that no value exists)”.

3.2. Sales DB
The sales DB is a database in which information related to processing operations occurring in the sales department is described. The data structure of the records constituting the sales DB is uniquely customized in the sales department. The sales DB data is input to the sales system server 25 from the sales department operation terminal 35 (see FIG. 2). The sales representative inputs the data to the sales system server 25 using the sales department operation terminal 35 while viewing the contents sent from the orderer on paper.

  The data structure of the sales DB is shown in FIG. The sales DB includes a [business type identifier] column C900, an [order processing number] column C901, an [order date] column C903, an [order amount] column C905, an [orderer] column C907, and an [order content] column C909. is doing. In the [Business Type Identifier] column C900, a business type identification number “A” corresponding to order reception is described (see FIG. 7). [Order processing number] column C901 describes a number for uniquely specifying the order processing performed based on the order reception. [Order Date] column C903 describes the date on which order processing occurred. [Order Amount] column C905 describes the order amount. [Orderer] column C907 describes the orderer who placed the order. [Order Contents] column C909 describes specific contents of the order processing.

  In FIG. 9, an order process for delivering “a set of personal computers” from “Company X” for “1 million yen” occurs as a business on “April 1, 2005”, and the order process number “A100” is assigned to the order process. “A100” is stored in the [Order Processing Number] column C901, “April 1, 2005” is stored in the [Order Date] column C903, and “1 million yen” is stored in the [Order Amount] column C905. , “Company X” is described in the “Orderer” column C907, and “Computer set” is described in the [Order details] column C909.

3.3. Purchasing DB
The purchase DB is a database that describes information related to processing operations occurring in the purchasing department. The data structure of the records constituting the purchase DB is uniquely customized in the purchasing department as in the sales department. Data in the purchase DB is input from the purchase department operation terminal 37 to the purchase system server 27. The person in charge of purchase inputs data to the purchase system server 27 using the operation terminal 37 for purchase department based on the purchase contents made in accordance with the purchase request from the sales department.

  The data structure of the purchase DB is shown in FIG. The purchase DB includes a [business type identifier] column C1000, a [purchase process number] column C1001, a [purchased product content] column C1003, a [purchase destination] column C1005, a [purchase request date] column C1007, a [purchase price] column C1009, [Orderer] column C1011 and [Order processing number] column C1013 are included. In the [business type identifier] column C1000, a business type identification number “B” corresponding to the purchase request is described (see FIG. 7). [Purchase Processing Number] column C1001 describes a number that uniquely identifies a purchase processing job performed based on a purchase request. [Purchased product content] column C1003 describes the content of products purchased in the purchase processing operation. [Purchase] column C1005 describes the purchase source of the purchased product. [Purchase Request Date] column C1007 describes the date of ordering from the purchaser. [Purchase Amount] column C1009 describes the amount of money required for the purchase. [Orderer] column C1011 describes the orderer who requested the purchase operation. [Order processing number] column C1013 describes the order processing number of the order processing that is the premise of purchase.

  In FIG. 9, for the order processing work of order processing number “A100” which is an order from “Company X”, “Company A” with “700,000 yen” from “A Manufacturing” is “2005 4”. When the purchase processing business to be purchased occurs on “Monday 2” and the order number “B100” is given to the purchase processing business, “B100” is displayed in the [Purchase processing number] column C1001 and the “purchased product content” column C1003. “Company A”, “Purchased” column C1005 “A Manufacturing”, “Purchase Request Date” column C1007 “April 2, 2005”, and “Purchase Amount” column C1009 "700,000 yen" is described in the "Orderer" column C1011 with "Company X" and "Order processing number" column C1013 with "A100".

3.4. Business Status Table The business status table is a table that records business event data composed of predetermined data acquired from the sales DB or purchase DB in order to monitor the business status. The business event data includes “business type identifier”, “occurrence date”, “processing business identifier”, “prerequisite business type identifier”, “prerequisite processing business identifier”, and “cost”.

  The sales system server 25 acquires each value of the [business type identifier] column C900, the [order processing number] column C901, the [order date] column C903, and the [order amount] column C905 from the sales DB, and stores them as business event data. Are transmitted to the status monitoring server 23 in association with the “business type identifier”, “processing business identifier”, “occurrence date”, and “cost”. Since values corresponding to the “prerequisite business type identifier” and the “prerequisite processing business identifier” of the business event data are not set in the sales DB, the sales system server 25 selects “prerequisite business type identifier” and “prerequisite processing business identifier”. No value is set for "."

  In addition, the purchase system server 27 stores, from the purchase DB, a [business type identifier] column C1000, a [purchase process number] column C1001, a [purchase request date] column C1007, a [purchase price] column C1009, and an [order process number] column C1013. The status monitoring server 23 obtains each of the values and associates each value with the “business type identifier”, “processing business identifier”, “occurrence date”, “cost”, and “prerequisite processing business identifier” of the business event data. Send to. Since no value corresponding to the “prerequisite business type identifier” of the business event data is set in the purchase DB, the purchasing system server 27 sets no value for the “prerequisite business type identifier”.

  The business event data constituting each record of the business status table is transmitted from the sales system server 25 and the purchase system server 27 to the business status monitoring server 23. The business situation monitoring server 23 updates the contents of the business situation table each time data is transmitted from the sales system server 25 or the purchase system server 27.

  The data structure of the business situation table in the present embodiment is shown in FIG. The business status table includes a [business type identifier] column C801, an [occurrence date] column C803, a [processing business identifier] column C805, a [prerequisite business type identifier] column C806, a [prerequisite processing business identifier] column C807, and [cost]. Column C809 is included.

  The business monitoring server 23 describes the value of the business type identifier in the business event data in the [business type identifier] column C801 of the business status table, and sets the value of the processing business identifier in the business event data in the [processing business identifier] of the business status table. Described in the column C805, the value of the occurrence date in the business event data is described in the [occurrence date] column C803 of the business status table, and the value of the precondition processing business identifier in the business event data is set in the [Precondition processing business identifier] It is described in column C807, and the cost value of the business event data is described in [Cost] column C809 of the business status table.

  Regarding the “prerequisite business type identifier”, the status monitoring server 23 sets the value of the “predetermined business type identifier” column C705 in the business rule table, and the value of the “business type identifier” of the acquired business event data. What is included in the [business type identifier] column C701 of the regulation table is set.

  Further, for a column in which no value is set in the record of the business situation table, the business monitoring server 23 describes “Null”.

4. Operation of business monitoring system 1
4.1. Business Event Data Extraction Processing Business event data extraction processing in the sales system server 25 will be described with reference to the flowchart shown in FIG. When the CPU 251 of the sales system server 25 determines that data related to new business processing has been registered in the sales DB (S1001), it acquires business event data definition information stored in the hard disk 253 (S1003). The CPU 251 acquires corresponding data from the sales DB based on the acquired business event data definition information (S1005). The CPU 251 transmits the acquired data as business event data to the business monitoring server 23 (S1007).

  If the purchasing system server 27 determines that data has been registered in the purchasing DB, the purchasing system server 27 similarly executes the processing from step S1001 to step S1007 in the sales system server 23.

4.2. Business Status Table Update Processing Business status table update processing performed by the CPU 231 of the business monitoring server 23 will be described with reference to the flowchart shown in FIG.

  The CPU 231 of the business situation monitoring server 23 determines whether business event data has been transmitted from the sales system server 25 or the purchase system server 27 (S1101). When the CPU 231 determines that the business event data has been received from the sales system server 25 or the purchasing system server 27, the CPU 231 determines whether or not the processing business corresponding to the received business event data has a prerequisite processing business. It is determined whether or not a prerequisite processing job is set in the job specification table for the processing job corresponding to the business event data.

  The CPU 231 sets the value of “Processing business identifier” of the received business event data to “Xa”, the value of “Prerequisite processing business identifier” to “Xb”, and the value of “Business type identifier” to “Xc”, respectively. Substitute (S1103). Next, the CPU 231 acquires the value of the [Prerequisite business identifier] column C705 of the record whose value in the [business type identifier] column C701 of the business regulation table is “Xc”, and substitutes it into “Yc” (S1105). The CPU 231 determines whether the value of “Yc” is “Null” (S1107).

  If the CPU 231 determines in step S1107 that the value of “Yc” is not “Null”, that is, the processing job corresponding to the received business event data requires a pre-requisite processing job, Determine whether the business event data corresponding to the pre-requisite processing business has already been registered in the business status table. The CPU 231 determines whether or not business event data having a value of “Yc” in the “business type identifier” column C801 and a value of “Xb” in the “processing business identifier” column C805 is already registered in the business situation table. Is determined (S1109).

  In step S <b> 1109, the CPU 231 still registers business event data having a value of “Yc” in the [business type identifier] column C <b> 801 and a value of “Xb” in the [processing business identifier] column C <b> 805 in the business situation table. If it is determined that it has not been performed, the business type identifier value “Yc”, the occurrence date value “Null”, the processing business identifier value “Xb”, The business event data having the value “Null” of the prerequisite business type identifier, the value “Null” of the prerequisite processing business identifier, and the value “Null” of the expense is added to the business situation table (S1111).

  In step S1107, the CPU 231 determines that the value “Yc” is “Null”, that is, the processing job corresponding to the received business event data does not require a pre-requisite processing job, or in step S1109, the job status. It is determined that business event data having a value of “Yc” in the “business type identifier” column C801 and a value of “Xb” in the “prerequisite processing business identifier” column C807 is already registered in the table, or If it is determined that the processing in step S1111 is completed, it is determined whether or not a new record needs to be added when the received business event data is registered in the business status table. The CPU 231 determines whether or not business event data having a value of “Xc” in the “business type identifier” column C801 and a value of “Xa” in the “processing business identifier” column C805 is already registered in the business situation table. Is determined (S1113).

  In step S <b> 1113, the CPU 231 has already registered business event data whose value in the [business type identifier] column C <b> 801 is “Xc” and whose value in the [processing business identifier] column C <b> 805 is “Xa” in the business status table. If it is determined that the business event data previously registered in the process of step S1111 already exists, the [occurrence date] column C803 and the [expense] column C809 corresponding to the business event data are determined. The date value and cost value of the received business event data are registered (S1115).

  In step S <b> 1113, the CPU 231 still registers business event data whose value in the [business type identifier] column C <b> 801 is “Xc” and whose value in the [processing business identifier] column C <b> 805 is “Xa” in the business situation table. If it is determined that it is not, the contents of the received business event data are registered in the business status table (S1117). When registering the business event data, the CPU 231 registers the value of the [Prerequisite business type identifier] column C705 of the business rule table acquired in step S1105 in the “Prerequisite business type identifier” column C806 of the business situation table. To do.

  CPU231 repeats the process from step S1101 to step S1117.

4.3. Business Status Monitoring Processing Business status monitoring processing performed by the CPU 231 of the business status monitoring server 23 will be described with reference to the flowcharts shown in FIGS. The CPU 231 executes a business situation monitoring process every time the business situation table update process is completed.

  The CPU 231 extracts the first processing task in a series of processing tasks from the task definition table. The CPU 231 determines whether or not there is business regulation information whose value in the [Prerequisite business type identifier] column C705 is “Null” in the business regulation table (S1301). When the CPU 231 determines that the corresponding business regulation information exists, the CPU 231 acquires the value of the [business type identifier] column C701 of the business regulation information and substitutes it for “S” (S1303). It is determined whether or not there is business event data whose value in the “business type identifier” column C801 is “S” (S1305).

  If the CPU 231 determines that the corresponding business event data exists, the value of the [processing business identifier] column C805 of the business event data is set to “Xa”, the value of the [occurrence date] column C803 is set to “Xb”, and [expense] ] The value of column C809 is assigned to “Xc”, respectively (S1307). Next, when displaying the list of monitoring results, the CPU 231 prepares data Y for displaying one business event data. The data Y has items of [Processing business identifier], “Occurrence date”, “Cost”, “Work compliance verification”, and “Price verification”. The CPU 231 sets “Xa” to “Processing business identifier” of data Y, “Xb” to “Date of occurrence”, “Xc” to “Cost”, “OK” to “Work order verification”, “Cost verification” "OK" is set to "" (S1309).

  Subsequently, the CPU 231 determines whether or not the processing work corresponding to the business event data to be verified is actually performed. The CPU 231 determines whether the value of the “occurrence date” of the data Y is “Null” (S1311). If the CPU 231 determines that the value of the “occurrence date” of the data Y is “Null” in step S1311, that is, the corresponding processing task has not yet been performed, the value “ "Warning" is set (S1313).

  Next, the CPU 231 determines whether or not there is business event data having a value of “Xa” in the [Prerequisite processing business identifier] column C807 of the business situation table (S1315). If the CPU 231 determines that the corresponding business event data exists, the CPU 231 acquires the business event data, and determines whether or not the value (date) in the [occurrence date] column C803 is earlier than “Xc”. It is determined whether the “date of occurrence of previous business” is a date prior to the date of occurrence of subsequent business (S1317).

  The CPU 231 has a value (date) in the [occurrence date] column C803 in the acquired business event data that is earlier than “Xc”, that is, the “occurrence date of the previous task” is higher than the “occurrence date of the subsequent task”. If it is determined that the date is a later date, it is determined that the order of occurrence of the processing work is invalid, and “Warning” is set as the “work order verification” value of the data Y (S1319).

  Next, the CPU 231 determines whether there is other business event data having a value of “Xa” in the [Prerequisite processing business identifier] column C807 of the business situation table (S1321). When CPU 231 determines that there is other business event data, CPU 231 executes processing from step S1317 to step S1321 on the business event data.

  If the CPU 231 determines that there is no other corresponding business event data in step S1321, the [expense] of the business event data whose value in the [prerequisite processing business identifier] column C807 extracted from the business situation table is “Xa” is displayed. ] Sum the values in column C809. The CPU 231 determines whether or not the total value in the [cost] column C809 matches “Xc”, that is, the total cost required for the “post-work” matches the cost set in advance in the “pre-work”. It is determined whether or not (S1323). In step S <b> 1323, the CPU 231 does not match the value of the total [cost] column C 809 with “Xb”, that is, the total cost required for the “post-work” does not match the cost set in advance in the “pre-work”. If it is determined, the cost relationship is determined to be inconsistent, and “Warning” is set as the “cost verification” value of the data Y (S1325).

  Based on the data Y, the CPU 231 displays a list of business situation monitoring results on the display 236 (S1327).

  The CPU 231 repeats the processing from step S1305 to step S1327 also for other business event data in the business situation table. If the CPU 231 determines in step S1305 that the corresponding business event data does not exist, or in step S1315, the business event whose value in the [prerequisite processing business identifier] column C807 of the business status table is “Xa”. If it is determined that there is no data, it is determined whether there is other business rule information in the business rule table (S1331). If CPU 231 determines in step S1331 that there is other business regulation information, it repeats the processing from steps S1303 to S1331. If CPU 231 determines in step S1331 that there is no other business regulation information, it ends the process.

5. Specific examples
5.1. Business Flow An example of the business flow, which is the business flow in the company, will be described with reference to FIG. It is assumed that the sales department and the purchasing department share the following tasks.

  The sales department is in charge of order reception work from the customer (S110). The order reception operation includes registering the order contents in the “sales system” when an order from a customer is received.

  Subsequently, the sales department is in charge of a purchase requesting operation for requesting the purchasing department for products that need to be purchased according to the order contents (S111). The purchase requesting business includes inputting necessary items into the “purchasing system”. If multiple purchase requests are required, such as when multiple products are required for a single order receipt from a customer or there are multiple suppliers, Repeat input to "Purchasing System".

Based on the data entered in the “purchasing system” in the sales department,
Responsible for ordering / purchasing various products and delivering deliverables (S120).

  The following processing will be described on the assumption that the business DB shown in FIG. 8 and the purchase DB shown in FIG. 9 are constructed according to this business flow. It is assumed that the business rule table shown in FIG. 7 is set.

  Further, in the DB and tables described in FIGS. 7 to 10, numbers are assigned to the respective rows for convenience. Thereafter, data corresponding to each DB and table row is specified using this number. For example, “business rule information # 1” indicates the data in the first row of the business rule table in FIG. Similarly, “business event data # 3” indicates the data in the third row of the business situation table in FIG.

5.2. Business Event Data Extraction Processing A specific example of business event data extraction processing in the sales system server 25 will be described with reference to the flowchart shown in FIG. Here, consider a case where sales information # 2 which is data related to new business processing is registered in the sales DB.

  When the CPU 251 of the sales system server 25 determines that the sales information # 2 is registered in the sales DB and the sales DB is updated (S1001), the business event data definition information (business type identifier, The date of occurrence, processing business identifier, precondition business type identifier, precondition processing business identifier, cost) is acquired (S1003). The CPU 251 acquires data (A, 2005/5/2, A200, Null, Null, 1 million yen) corresponding to the business event data definition information from the sales database sales information # 2 (S1005). The CPU 251 transmits the acquired data as business event data to the business monitoring server 23 (S1007).

5.3. Business Status Table Update Processing A specific example of business status table update processing will be described with reference to the flowchart shown in FIG.

5.3.1 In case of business status table / business event data # 4 (Refer to Fig. 10, 4th line)
In the following, the update process of the business situation table performed when the CPU 231 of the business monitoring server 23 registers the business event data # 4 in the business situation table will be described. It should be noted that at the stage where business event data # 4 is to be registered in the business situation table, the data after business event data # 4 in the business situation table in FIG. 10 is not yet registered.

  The CPU 231 of the business status monitoring server 23 determines whether or not business event data has been received from the sales system server 25 (S1101).

  The CPU 231 receives the “processing job identifier” value “A200” of the received business event data as “Xa”, the “prerequisite processing job identifier” value “Null” as “Xb”, and the “business type identifier” value “ A ”is substituted for“ Xc ”, respectively (S1103). Next, the CPU 231 determines the value of the [Prerequisite business type identifier] column C705 of the business rule information # 1 whose value in the [Business type identifier] column C701 of the business rule table (see FIG. 7) is “Xc (= A)”. “Null” is acquired and substituted for “Yc” (S1105).

  If the CPU 231 determines that the value of “Yc” is “Null”, that is, the processing job corresponding to the received business event data does not require a pre-requisite processing job (S1107), When registering in the status table, it is determined whether or not a new record needs to be added. The CPU 231 includes business event data whose value in the [business type identifier] column C801 is “Xc (= A)” and whose value in the [processing business identifier] column C805 is “Xa (= A200)” in the business status table. Is already registered (S1113).

  In step S <b> 1113, the CPU 231 indicates that the value in the [business type identifier] column C <b> 801 is “Xc (= A)” and the value in the [processing business identifier] column C <b> 805 is “Xa (= A200)”. If it is determined that the business event data is not yet registered, the contents of the received business event data are registered in the business status table (S1117). When registering the business event data, the CPU 231 uses the value “Null” in the [Prerequisite business type identifier] column C705 of the business rule table acquired in step S1105 and the “Prerequisite business type” column C806 of the business situation table. Set to.

5.3.2 Business situation table / business event data # 7 (Refer to Fig. 10, line 7)
In the following, an update process of the business situation table performed when the CPU 231 of the business monitoring server 23 registers the business event data # 7 in the business situation table will be described. At the stage where business event data # 7 is to be registered in the business status table, business event data # 6 to # 10 in the business status table in FIG. 10 are not yet registered. Since the business event data # 6 is newly generated and registered in the process of the business event data # 7, it is registered in the business situation table when the business event data # 7 is to be registered. Not. Business event data # 8 to # 10 are not registered in the business situation table at the stage of registering business event data # 7 because the occurrence time is later than business event data # 7. .

  The CPU 231 of the business status monitoring server 23 determines whether or not business event data has been received from the sales system server 25 (S1101).

  The CPU 231 sets the “processing job identifier” value “B300” of the received business event data # 7 to “Xa”, the “prerequisite processing job identifier” value “A300” to “Xb”, and the “job type identifier”. The value “B” is assigned to “Xc”, respectively (S1103). Next, the CPU 231 determines the value of the [Prerequisite business type identifier] column C705 of the business rule information # 2 whose value in the [Business type identifier] column C701 of the business rule table (see FIG. 7) is “Xc (= B)”. “A” is acquired and assigned to “Yc” (S1105).

  When the CPU 231 determines that the value of “Yc (= A)” is not “Null”, that is, the processing job corresponding to the received business event data # 7 requires a pre-requisite processing job, It is determined whether or not the business event data corresponding to the processing business that is the premise of data # 7 has already been registered in the business status table. The CPU 231 includes business event data whose value in the “business type identifier” column C801 is “Yc (= A)” and whose value in the “processing business identifier” column C805 is “Xb (= A300)” in the business situation table. Is already registered (S1109).

  In step S1109, the CPU 231 indicates that the value in the [business type identifier] column C801 is “Yc (= A300)” and the value in the [processing business identifier] column C805 is “Xb (= A300)”. If it is determined that the business event data is not yet registered, the business type identifier value “Yc (= A300)” and the occurrence date value “ “Null”, processing task identifier value “Xb (= A)”, prerequisite task type identifier value “Null”, prerequisite processing task identifier value “Null”, and cost value “Null”. It adds to a situation table (S1111).

  Then, when registering the received business event data # 7 in the business situation table, the CPU 231 determines whether or not a new record needs to be added. The CPU 231 includes business event data whose value in the [business type identifier] column C801 is “Xc (= B)” and whose value in the [processing business identifier] column C805 is “Xa (= B400)” in the business situation table. Is already registered (S1113).

  In step S <b> 1113, the CPU 231 indicates that the value in the [business type identifier] column C <b> 801 is “Xc (= B)” and the value in the [processing business identifier] column C <b> 805 is “Xa (= B400)”. If it is determined that the business event data is not yet registered, the contents of the received business event data are registered in the business status table (S1117). When registering the business event data, the CPU 231 uses the value “A” in the [Prerequisite business type identifier] column C705 of the business rule table acquired in step S1105 and the “Prerequisite business type identifier” column of the business status table. Set to C806.

5.4. Business Status Monitoring Processing A specific example of business status monitoring processing performed by the CPU 231 of the business status monitoring server 23 will be described with reference to flowcharts shown in FIGS. The business monitoring server 23 executes a business status monitoring process each time business event data is registered in the business status table.

  Hereinafter, a business situation monitoring process performed after the CPU 231 of the business monitoring server 23 registers business event data # 10 in the business situation table will be described. The business situation table at the stage where business event data # 10 is registered in the business situation table is as shown in FIG.

  The CPU 231 extracts the first processing task in a series of processing tasks from the task definition table. The CPU 231 determines whether or not there is business regulation information whose value in the [Prerequisite business type identifier] column C705 of the business regulation table is “Null” (S1301). If the CPU 231 determines that the corresponding business rule information # 1 exists, the CPU 231 acquires the value “A” in the [business type identifier] column C701 of the business rule information # 1, and substitutes it for “S” (S1303). Then, it is determined whether or not there is business event data whose value in the [business type identifier] column C801 is “S (= A)” from the business situation table (S1305).

-Regarding business event data # 1 If the CPU 231 determines that there is business event data # 1 whose value in the [business type identifier] column C801 is "S (= A)" from the business status table, the business event data # 1 And the value “A100” in the [Processing business identifier] column C805 of the business event data # 1 is set to “Xa”, the value “2005/4/1” in the [Occurrence date] column C803 is set to “Xb”, [ Cost] The value “1 million yen” in column C809 is assigned to “Xc”, respectively (S1307). Next, when displaying the list of monitoring results, the CPU 231 prepares data Y for displaying one business event data. The data Y includes items of “business type identifier”, “occurrence date”, “cost”, “work order verification”, and “amount verification”. The CPU 231 sets “Xa (= A100)” as the “business type identifier” of the data Y, “Xb (= 2005/4/1)” as the “occurrence date”, and “Xc (= 1,000,000 yen) as the“ expense ”. ) ”,“ OK ”is set in“ Work Order Verification ”, and“ OK ”is set in“ Cost Verification ”(S1309).

  Subsequently, when the CPU 231 determines that the value of the “occurrence date” of the data Y is not “Null”, that is, that the corresponding processing job has already been performed (S1311), [Prerequisite processing job identifier] in the job status table. It is determined whether or not there is business event data whose value in the column C807 is “Xa (= A100)” (S1315). When the CPU 231 determines that the corresponding business event data # 2 exists, the value (date) “2005/4/2” in the [occurrence date] column C803 in the business event data # 2 is “Xb” (= 2005/4). / 1) ”, that is,“ the date of occurrence of the previous job ”is determined to be a date before the“ date of occurrence of the subsequent job ”(S1317), [prerequisite processing job identifier] in the job status table It is determined whether or not there is other business event data whose value in the column C807 is “Xa (= A100)” (S1321). The CPU 231 determines that other business event data # 3 exists, and executes the processing from step S1317 to step S1321 for the business event data # 3.

  If the CPU 231 determines in step S1321 that there is no other corresponding business event data, the business event whose value in the [prerequisite processing business identifier] column C807 extracted from the business situation table is “Xa (= A100)”. The values “700,000 yen” and “300,000 yen” in the “Expense” column C809 of data # 2 and # 3 are totaled. The CPU 231 determines whether or not the value “1 million yen” in the total [cost] column C809 matches “Xc (= 1 million yen)”, that is, the total cost required for the “post-work” is “front If it is determined that it matches the cost set in advance in “business” (that is, the total cost required for “post-work” matches the cost set in “previous business”) (S 1323), Judge that they are consistent. In the processing so far, the values of “work order verification” and “cost verification” of data Y are both values “OK” set in step S1309.

  Based on the data Y, the CPU 231 displays a list of business situation monitoring results on the display 236 (S1327).

-Regarding business event data # 4 Next, the CPU 231 determines from the business status table that there is another business event data # 4 whose value in the [business type identifier] column C801 is “S (= A)” (S1305). ), The business event data # 4 is acquired, the value “A200” in the [processing business identifier] column C805 of the business event data # 4 is set to “Xa”, and the value “2005/5/2” in the [occurrence date] column C803. "Xb" and the value "1 million yen" in the [Cost] column C809 are substituted into "Xc" (S1307). Next, when displaying the list of monitoring results, the CPU 231 prepares data Y for displaying one business event data. The data Y includes items of “business type identifier”, “occurrence date”, “cost”, “work order verification”, and “amount verification”. The CPU 231 sets “Xa (= A200)” as the “business type identifier” of the data Y, “Xb (= 2005/5/2)” as the “occurrence date”, and “Xc (= 1,000,000 yen) as the“ cost ”. ) ”,“ OK ”is set in“ Work Order Verification ”, and“ OK ”is set in“ Cost Verification ”(S1309).

  Subsequently, when the CPU 231 determines that the value of the “occurrence date” of the data Y is not “Null”, that is, that the corresponding processing job has already been performed, the CPU 231 stores the “precondition processing job identifier” column C807 in the job status table. It is determined whether or not there is business event data whose value is “Xa (= A200)” (S1315). When the CPU 231 determines that the corresponding business event data # 5 exists, the value (date) “2005/5/1” in the [occurrence date] column C803 in the business event data # 5 is “Xb” (= 2005/5). / 2) ", that is, it is determined whether or not the" date of occurrence of the previous work "is a date after the date of occurrence of the subsequent work (S1317). When the CPU 231 determines that the value (date) “2005/5/1” in the [occurrence date] column C803 in the business event data # 5 is before “Xb (= 2005/5/2)”, It is determined that the order of occurrence of the processing work is invalid, and “Warning” is set as the “work order verification” value of the data Y (S1319).

  If the CPU 231 determines that there is no other business event data whose value in the [Prerequisite processing business identifier] column C807 of the business status table is “Xa (= A200)”, the [Prerequisite processing business identifier extracted from the business status table] ] Whether the value “1 million yen” in the [expense] column C809 of the business event data # 5 whose value in the column C807 is “Xa (= A200)” matches “Xc (= 1 million yen)”, That is, it is determined whether or not the total cost required for the “post-work” is equal to the cost set in advance in the “pre-work” (S 1323). If the CPU 231 determines that the two are the same, that is, if the total cost required for the “post-work” matches the cost set in advance in the “pre-work”, the CPU 231 determines that the cost relationship is consistent. In the processing so far, the “work order verification” values of the data Y are “Warning” and the “cost verification” values “OK”.

  Based on the data Y, the CPU 231 displays a list of business situation monitoring results on the display 236 (S1327).

-Regarding business event data # 6 Next, the CPU 231 determines from the business status table that there is another business event data # 6 whose value in the [business type identifier] column C801 is “S (= A)” (S1305). ), The business event data # 6 is acquired, the value “A300” of the “processing business identifier” column C805 of the business event data # 6 is set to “Xa”, and the value “Null” of the “occurrence date” column C803 is set to “Xb”. The value “Null” in the [Cost] column C809 is assigned to “Xc”, respectively (S1307). Next, when displaying the list of monitoring results, the CPU 231 prepares data Y for displaying one business event data. The data Y includes items of “business type identifier”, “occurrence date”, “cost”, “work order verification”, and “amount verification”. The CPU 231 sets “Xa (= A300)” as the “business type identifier” of the data Y, “Xb (= Null)” as the “occurrence date”, “Xc (= Null)” as the “cost”, and “work” “OK” is set in “Order verification”, and “OK” is set in “Cost verification” (S1309).

  Subsequently, when the CPU 231 determines that the value of the “occurrence date” of the data Y is “Null”, that is, the corresponding processing operation has not yet been performed, the value “Warning” is set in the “work order verification” of the data Y. Is set (S1313).

  Then, the CPU 231 determines whether or not there is business event data having a value of “Xa (= A300)” in the [Prerequisite processing business identifier] column C807 of the business situation table (S1315). When the CPU 231 determines that the corresponding business event data # 7 exists, the value (date) “2005/6/1” in the [occurrence date] column C803 in the business event data # 7 is “Xb (= Null)”. It is determined whether the date is earlier, that is, the “date of occurrence of the previous job” is later than the date of occurrence of the subsequent job (S1317). In this case, the CPU 231 determines whether or not the value (date) “2005/6/1” in the [occurrence date] column C803 in the business event data # 7 is before “Xb (= Null)”. Therefore, “Warning” is set as the “work order verification” value of the data Y (S1319).

  Next, when the CPU 231 determines that there is no other business event data having a value of “Xa (= A300)” in the [Prerequisite Processing Business Identifier] column C807 of the business status table, the CPU 231 extracts the [Premise Whether or not the value “1 million yen” in the [expense] column C809 of the business event data # 7 in which the value of the processing business identifier column C807 is “Xa (= A200)” matches “Xc (= Null)” That is, it is determined whether or not the total cost required for the “post-work” matches the cost set in advance in the “pre-work” (S 1323). In this case, the CPU 231 cannot verify the cost relationship, and thus sets “Warning” as the value of “cost verification”. In the processing so far, the values of “work order verification” and “cost verification” of data Y are both “Warning”.

  Based on the data Y, the CPU 231 displays a list of business situation monitoring results on the display 236 (S1327).

-Regarding business event data # 8 If the CPU 231 determines that there is business event data # 8 whose value in the [business type identifier] column C801 is "S (= A)" from the business status table, the business event data # 8 In the business event data # 8, the value “A400” of the “processing business identifier” column C805 is set to “Xa”, the value “2005/7/1” of the “occurrence date” column C803 is set to “Xb”, [ Cost] The value “2 million yen” in column C809 is assigned to “Xc”, respectively (S1307). Next, when displaying the list of monitoring results, the CPU 231 prepares data Y for displaying one business event data. The data Y includes items of “business type identifier”, “occurrence date”, “cost”, “work order verification”, and “amount verification”. The CPU 231 sets “Xa (= A400)” as the “business type identifier” of the data Y, “Xb (= 2005/7/1)” as the “occurrence date”, and “Xc (= 2 million yen) as the“ cost ”. ) ”,“ OK ”is set in“ Work Order Verification ”, and“ OK ”is set in“ Cost Verification ”(S1309).

  Subsequently, when the CPU 231 determines that the value of the “occurrence date” of the data Y is not “Null”, that is, that the corresponding processing task has already been performed, the CPU 231 stores the “precondition processing task identifier” column C807 in the task status table. It is determined whether or not there is business event data whose value is “Xa (= A400)” (S1315). When the CPU 231 determines that the corresponding business event data # 9 exists, the value (date) “2005/7/2” in the [occurrence date] column C803 in the business event data # 9 is “Xb” (= 2005/7). / 1) ”, that is, whether“ date of occurrence of previous business ”is a date before“ date of occurrence of subsequent business ”(S1317). The CPU 231 determines that the value (date) “2005/7/2” in the [occurrence date] column C803 in the business event data # 9 is after “Xb (= 2005/7/1)”. Then, it is determined whether there is other business event data whose value in the [Prerequisite processing business identifier] column C807 of the business status table is “Xa (= A400)” (S1321). The CPU 231 determines that other business event data # 10 exists, and executes the processing from step S1317 to step S1321 for the business event data # 3.

  If the CPU 231 determines in step S1321 that there is no corresponding other business event data, the business event whose value in the [prerequisite processing business identifier] column C807 extracted from the business situation table is “Xa (= A400)”. The values “1.5 million yen” and “1 million yen” in the “expense” column C809 of data # 9 and # 10 are totaled. The CPU 231 determines whether or not the total “cost” column C809 value “2.5 million yen” matches “Xc (= 2 million yen)”, that is, the total cost required for the “post-work” It is determined whether or not it matches the cost set in advance in the “business” (S1323). The CPU 231 does not match the value “2.5 million yen” in the total [cost] column C809 with “Xc (= 2 million yen)”, that is, the total cost required for the “post-work” is “pre-work”. If it is determined that the cost does not match the preset cost, it is determined that the cost relationship is inconsistent, and “Warning” is set as the value of “cost verification”. In the processing so far, the value of “work order verification” of data Y is “OK” and the value of “cost verification” is the value “Warning”.

  Based on the data Y, the CPU 231 displays a list of business situation monitoring results on the display 236 (S1327).

-Regarding business event data # 2, 3, 5, 7, 9, 10 Next, the CPU 231 determines that business event data whose value in the [business type identifier] column C801 is "S (= A)" from the business status table. If it is determined that it no longer exists (S1305), it is determined whether or not other business rule information exists in the business rule table (S1331). If the CPU 231 determines that the business regulation information # 2 exists, the CPU 231 obtains the business event data # 2, obtains the value “B” in the [business type identifier] column C701 of the business regulation information # 1, and “S”. (S1303) The CPU 231 determines whether there is business event data whose value in the [business type identifier] column C801 is “S (= B)” from the business situation table (S1305).
If the CPU 231 determines that there is business event data # 2 whose value in the [business type identifier] column C801 is “S (= B)” from the business status table, the CPU 231 acquires the business event data # 2, and the business event data The value “B100” in the “Processing business identifier” column C805 of # 2 is “Xa”, the value “2005/4/2” in the “occurrence date” column C803 is “Xb”, and the value “ “700,000 yen” is substituted for “Xc” (S1307). Next, when displaying the list of monitoring results, the CPU 231 prepares data Y for displaying one business event data. The data Y includes items of “business type identifier”, “occurrence date”, “cost”, “work order verification”, and “amount verification”. The CPU 231 sets “Xa (= B100)” as the “business type identifier” of the data Y, “Xb (= 2005/4/2)” as the “occurrence date”, and “Xc (= 700,000 yen) as the“ cost ”. ) ”,“ OK ”is set in“ Work Order Verification ”, and“ OK ”is set in“ Cost Verification ”(S1309).

  Subsequently, when the CPU 231 determines that the value of the “occurrence date” of the data Y is not “Null”, that is, that the corresponding processing job has already been performed (S1311), [Prerequisite processing job identifier] in the job status table. It is determined whether or not there is business event data whose value in the column C807 is “Xa (= B100)” (S1315). If the CPU 231 determines that the corresponding business event data does not exist, the CPU 231 executes steps S1307 to S3307 for the next business event data # 3 whose value in the [business type identifier] column C801 is “S (= B)” from the business status table. The process of step S1315 is executed. The same applies to the business event data 5, 7, 9, and 10.

  From the above processing, the business event data 2, 3, 5, 7, 9, 10 is not displayed as the verification result.

  If the CPU 231 determines that there is no other business regulation information (S1331), the process is terminated.

FIG. 15 shows the verification results so far. Moreover, the verification result in FIG. 15 can also be shown with a flowchart. FIG. 17 shows a flow display of the verification result. FIG. 17A shows a verification result flow relating to the [processing work identifier] column = “A200” of the verification result in FIG. 15. The wavy arrow in the figure indicates that the verification result of “work order verification” is “Warning”. FIG. 17B shows a verification result flow related to the [processing work identifier] column = “A300” of the verification result in FIG. 15. FIG. 17C shows a verification result flow relating to the [processing work identifier] column = “A400” of the verification result in FIG. 15. The cost value highlighted in the figure indicates that the verification result of “Cost Verification” is “Warning”.

[Other Examples]
(1) Extraction of business event data from sales DB / purchasing DB In the first embodiment, the business system data 25 is extracted from the sales DB / purchasing DB by the sales system server 25 and the purchasing system server 27. did. However, as long as business event data can be extracted, it is not limited to the example. For example, the business consistency verification server 23 may perform this.

(2) Timing of Verification In the first embodiment, the CPU 231 of the business situation monitoring server 23 executes the business situation monitoring process every time the business situation table update process is completed. However, the timing of the business situation monitoring process is not limited to the example. For example, the business consistency verification process may be executed according to an instruction from a user of the business situation monitoring server 23, a user of the business monitoring department operation terminal 33, or the like.

(3) Business event data to be verified In the first embodiment, the business status monitoring process is executed for all business event data registered in the business status table. However, the business situation monitoring process may be executed for specific business event data. In this case, what business event data is to be subjected to the business status monitoring process may be acquired from the user who is trying to verify.

(4) Business Flow In the first embodiment, the business flow shown in FIG. 16 is taken as an example. However, as long as business processing is performed, the business flow is not limited to the illustrated business flow.

(5) Verification Items In the above-described first embodiment, work order verification and cost verification are set as verification items. However, the items are not limited to the examples as long as they are necessary for the verification of the processing work. For example, it may be a lead time for performing business or an input amount of resources.

(6) Resource information In the first embodiment, cost information is exemplified as resource information. However, the present invention is not limited to this as long as it specifies at least the amount of resources required for processing operations occurring after the processing operation. For example, it may be the number of personnel or the amount of materials required after a certain business process.

  Further, in the first embodiment, the case where there is a quantitative consistency in the cost information when the total cost set in each processing business generated after a certain processing business matches the cost set in the processing business. It was. However, not only the case where they match, but the case where the former cost does not exceed the cost of the latter, and the following cases may be considered as cases where there is quantitative consistency. Moreover, when the latter exceeds the former, it is good also as a case where there exists quantitative consistency.

(7) Processing Order In the first embodiment, the business event data extraction process, the business situation table update process, and the business situation monitoring process are executed according to the respective flowcharts. However, the present invention is not limited to the processing according to the illustrated flowchart as long as the functions in the functional block diagram of each embodiment can be realized. In particular, the order of processing is not limited.

It is the figure which showed the functional block diagram in Example 1 of the business consistency verification system in this invention. It is the figure which showed the hardware constitutions of the business consistency verification system. 2 is a diagram illustrating a hardware configuration of a business situation monitoring server 23. FIG. 2 is a diagram illustrating a hardware configuration of a sales system server 25. FIG. It is the figure which showed the hardware constitutions of the purchase system server. It is the figure which showed the hardware constitutions of each operation terminal 33,35,37. It is the figure which showed the data structure of the business regulation table. It is the figure which showed the data structure of sales DB. It is the figure which showed the data structure of purchase DB. It is the figure which showed the data structure of the work condition table. It is the flowchart which showed the business event data extraction process. It is the flowchart which showed the business condition table update process. It is the flowchart which showed the business condition monitoring process. It is the flowchart which showed the business condition monitoring process. It is the figure which showed the list display screen of business condition. It is the figure which showed an example of the business flow. It is the figure which visualized the business situation. 1 is a diagram illustrating a conventional workflow support system 100. FIG.

Explanation of symbols

M1: Business consistency verification system M3: Business management device M5: Business consistency verification device M31: Processing business storage means M33: Verification item extraction Means M35... Verification item providing means M51... Rule information storage means M53... Verification item acquisition means M55... Verification item storage control means M57. 1 ... Business Consistency Verification System 23 ... Business Status Monitoring Server 25 ... Sales System Server 27 ... Purchasing System Server 33 ... Operation for Business Monitoring Department Terminal 35 ... Sales Department Operation Terminal 37 ... Purchasing Department Operation Terminal

Claims (19)

A business consistency verification system comprising a business management device for managing processing business information indicating a processing business having one or more registered items, and a business consistency verification device for verifying consistency between the processing business,
The business management device is
Processing work storage means for storing and holding one or more of the processing work information;
Verification item extraction means for extracting, as verification item information, a value corresponding to a predetermined registration item from the processing work storage means;
Verification item providing means for providing the verification item information to the business consistency verification device;
Have
The business consistency verification device includes:
A rule information storage means for storing and holding one or a plurality of rule information in which the processing work and the processing work occurring immediately before the processing work are associated;
Verification item acquisition means for acquiring the verification item information;
Verification item storage control means for storing and holding the acquired verification item information in the verification item storage means,
Whether the verification item information stored in the verification item storage means corresponds to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information is determined by the rule information. Verification means to verify based on
Having
Business consistency verification system characterized by A rule information storage means for storing and holding one or a plurality of rule information in which a processing job having one or a plurality of registration items and a processing job generated immediately before the processing job are associated;
Verification item acquisition means for acquiring verification item information indicating a value corresponding to a predetermined registration item;
Verification item storage control means for storing and holding the acquired verification item information in the verification item storage means,
Whether the verification item information stored in the verification item storage means corresponds to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information is determined by the rule information. Verification means to verify based on
A business consistency verification device. In either the business consistency verification system according to claim 1 or the business consistency verification apparatus according to claim 2,
The verification item information is:
Contains processing work identification information that identifies the processing work,
The rule information is
The processing business identification information of the processing business is associated with the processing business identification information of the processing business that occurs immediately before the processing business,
The verification means includes
The verification item stored in the verification item storage unit by comparing the processing operation identification information of the verification item information stored in the verification item storage unit with the processing operation identification information of the acquired verification item information Verifying, based on the rule information, whether or not there is information corresponding to the processing operation that occurred immediately before the processing operation corresponding to the acquired verification item information,
It is characterized by. In either the business consistency verification system or the business consistency verification device according to claim 3,
The verification item information further includes:
Including on-occurrence identification information that identifies when the processing operation occurred,
The verification means further includes:
Extract the verification item information corresponding to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information, and specify when the extracted verification item information is generated and when the acquired verification item information is generated Verifying whether the obtained verification item information and the extracted verification item information have temporal consistency by comparing,
It is characterized by. In either the business consistency verification system or the business consistency verification apparatus according to claim 4,
The verification item information further includes:
At least resource information that identifies the amount of resources required for processing operations occurring after the processing operation,
The verification means further includes:
Verifying whether the resource information of the extracted verification item information and the resource information of the acquired verification item information have quantitative consistency;
It is characterized by. In either the business consistency verification system according to claim 1 or the business consistency verification apparatus according to claim 2,
The verification item storage control means further includes:
Among the verification item information stored in the verification item storage unit, based on the rule information that associates the processing task specifying information of the processing task with the processing task specifying information of the processing task that occurs immediately before the processing task. Determining whether or not the verification item information of the processing job that occurs immediately before the processing job corresponding to the acquired verification item information exists, and determining that the verification item information does not exist in the verification item storage unit, Storing and storing in the verification item storage means verification item information of a processing job that occurs immediately before the processing job corresponding to the acquired verification item information;
It is characterized by. In either the business consistency verification system or the business consistency verification apparatus according to claim 6,
The verification item information further includes:
Including occurrence specific information for identifying the occurrence of the processing work,
The verification item storage control means further includes:
When storing and holding in the verification item storage means the verification item information of the processing job that occurs immediately before the processing job corresponding to the acquired verification item information, the value of the occurrence time information is not set,
It is characterized by. In either the business consistency verification system or the business consistency verification apparatus according to claim 6,
The verification item information further includes:
At least resource information that identifies the amount of resources required for processing operations occurring after the processing operation,
The verification item storage control means further includes:
When storing and holding in the verification item storage means the verification item information of the processing job generated immediately before the processing job corresponding to the acquired verification item information, the value of the resource information is not set,
It is characterized by. In either the business consistency verification system or the business consistency verification apparatus according to claim 1 to claim 8,
The verification means further includes:
When the verification item storage control unit finishes storing and holding the acquired verification item information in the verification item storage control unit, executing verification processing;
It is characterized by. In either the business consistency verification system or the business consistency verification apparatus according to claim 1 to claim 8,
The verification means further includes:
When the verification request information for requesting execution of the verification process is acquired, the verification process is executed.
It is characterized by. A business consistency verification program for generating hierarchical structure information for associating input information with items forming a hierarchical structure,
The business consistency verification program includes:
On the computer,
The verification item information indicating the value corresponding to the predetermined registration item is acquired,
Store the acquired verification item information in the verification item storage means,
Obtaining the rule information from a rule information storage means that stores one or more rule information in which one or a plurality of rule information associated with a processing job having one or more registered items and a processing job generated immediately before the processing job is associated;
Whether the verification item information stored in the verification item storage means corresponds to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information is determined by the rule information. To be verified based on
Business consistency verification program characterized by In the business consistency verification program according to claim 11,
The business consistency verification program includes:
To the computer,
Extract the verification item information corresponding to the processing job that occurred immediately before the processing job corresponding to the acquired verification item information, and specify when the extracted verification item information is generated and when the acquired verification item information is generated Verifying whether the acquired verification item information and the extracted verification item information have temporal consistency by comparing,
Business consistency verification program characterized by In the business consistency verification program according to claim 12,
The business consistency verification program includes:
To the computer,
At least obtain verification item information including resource information that identifies the amount of resources required in the processing operations occurring after the processing operation,
Whether the resource information of the extracted verification item information and the resource information of the acquired verification item information have quantitative consistency by comparing the resource information of the extracted verification item information with the resource information of the acquired verification item information To verify whether or not
Business consistency verification program characterized by In the business consistency verification program according to claim 11,
The business consistency verification program includes:
To the computer,
Among the verification item information stored in the verification item storage unit, based on the rule information that associates the processing task specifying information of the processing task with the processing task specifying information of the processing task that occurs immediately before the processing task. Determining whether or not the verification item information of the processing job that occurs immediately before the processing job corresponding to the acquired verification item information exists, and determining that the verification item information does not exist in the verification item storage unit, Storing the verification item information of the processing job generated immediately before the processing job corresponding to the acquired verification item information in the verification item storage unit;
Business consistency verification program characterized by In the business consistency verification program according to claim 14,
The business consistency verification program includes:
To the computer,
Obtaining verification item information including occurrence specific information for specifying the time when the processing operation occurs;
When the verification item information of the processing job generated immediately before the processing job corresponding to the acquired verification item information is stored in the verification item storage unit, the value of the occurrence information is not set,
Business consistency verification program characterized by In the business consistency verification program according to claim 14,
The business consistency verification program includes:
To the computer,
At least obtain verification item information including resource information that identifies the amount of resources required in the processing operations occurring after the processing operation,
Not having to set the value of the resource information when storing and holding in the verification item storage means verification item information of a processing job that occurs immediately before the processing job corresponding to the acquired verification item information;
Business consistency verification program characterized by In any one of the business consistency verification programs according to claims 11 to 16,
The business consistency verification program includes:
To the computer,
When the acquired verification item information is stored and held in the verification item storage control unit, a verification process is executed.
Business consistency verification program characterized by In any one of the business consistency verification programs according to claims 11 to 16,
The business consistency verification program includes:
To the computer,
When the verification request information for requesting execution of the verification process is acquired, the verification process is executed.
Business consistency verification program characterized by A business consistency verification method for verifying consistency between processing tasks having one or more registered items using a computer,
The business consistency verification method includes:
A computer extracts, as verification item information, a value corresponding to a predetermined registration item from a processing task storage unit that stores and holds one or more of the processing task information;
A computer provides the verification item information;
The computer acquires the verification item information,
The computer stores and holds the acquired verification item information in a rule information storage unit that stores and holds one or more rule information associated with the processing work and the processing work that occurs immediately before the processing work,
Whether the computer has a processing item corresponding to the processing operation that occurred immediately before the processing item corresponding to the acquired verification item information, among the verification item information stored and held in the verification item storage unit, Verifying based on the rule information;
Business consistency verification method characterized by

Images