WO2009104276A1 - 業務フロー処理プログラム、方法及び装置 - Google Patents
業務フロー処理プログラム、方法及び装置 Download PDFInfo
- Publication number
- WO2009104276A1 WO2009104276A1 PCT/JP2008/053086 JP2008053086W WO2009104276A1 WO 2009104276 A1 WO2009104276 A1 WO 2009104276A1 JP 2008053086 W JP2008053086 W JP 2008053086W WO 2009104276 A1 WO2009104276 A1 WO 2009104276A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- event
- process instance
- field
- data
- business
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45508—Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
- G06F9/45512—Command shells
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H70/00—ICT specially adapted for the handling or processing of medical references
- G16H70/20—ICT specially adapted for the handling or processing of medical references relating to practices or guidelines
Definitions
- the present invention relates to information processing technology for business process analysis.
- Event data which is information indicating the execution state of each application arranged in different business systems, is collected by a method corresponding to each application and queued in an event queue.
- an event indicates that a certain business has been executed in the business system, and is data including the start and end times of business and related attributes.
- the event data is extracted by an event data extraction application for each business system according to the event extraction definition arranged in each business system.
- the extracted event information is converted into a common XML (eXtensible Markup Language) format and queued in an event queue of an event management apparatus that manages event data.
- JMS Java (registered trademark) Message Service
- event information queued in the event queue is collected for each business data, and the business data is associated and stored in the event management database (DB).
- the business data means data shared between a certain unit of business.
- the business data is narrowed down based on the input search conditions (for example, event occurrence period, related attributes, etc.).
- Data related to the narrowed down business data is expanded and displayed in a tree, and processing from arbitrary data is traced.
- An event related to the business data expanded in the tree is searched, the business related to this event is illustrated in the tracking view, and the current execution status of the business flow is displayed.
- tracking refers to a method of confirming which business is being executed and which business is not being executed among the business processes that are the flow of the entire business across the business systems defined in advance.
- an object of the present invention is to provide a technique for making it easy for the user to grasp the characteristics of the entire business flow that is performed so that the business flow can be appropriately classified.
- the business flow processing method extracts a series of business data performed for each case from a database storing business processing results, and arranges the business names of the business performed for each case in time series.
- the step of storing in the instance data storage unit, the step of counting the process instances stored in the simplified process instance data storage unit for each type, and the appearance frequency is equal to or greater than a predetermined reference based on the counting result;
- the output step described above may include a step of superimposing the specified process instances. This is to make it easier to grasp the main business flow.
- the output step described above may include a step of outputting a process instance other than the specified process instance as an exception flow. This is to grasp the occurrence status of the exception flow and use it for business improvement.
- a step of determining whether or not a repetition of returning from the third task of the process instance to the third task has occurred For the process instance that has occurred, delete the repeated repetition of each repetition pattern type (that is, the repetition that makes it difficult to grasp the overall picture of the business), and the process instance after deleting the repeated repetition is replaced with process instance data And a step of storing in the storage unit. In this way, even if the same iteration occurs many times, it can be integrated into one iteration, and it becomes easy to identify the main business flow that is important in understanding the characteristics of the entire business flow. .
- a step of determining whether or not a repetition of returning from the third task of the process instance to the third task has occurred For process instances where repetition has occurred, delete the repeated repetition of each repetition pattern type (that is, the repetition that makes it difficult to grasp the overall picture of the business), and process instances after deleting the repeated repetition, And storing the simplified process instance data in the simplified process instance data storage unit.
- the deletion of repeated repetitions may be performed after the duplicate rework or first. In addition, deletion of duplicate rework or deletion of repeated repetitions may be performed independently.
- a program for causing a computer to execute the method according to the present invention can be created, and the program is a storage medium or storage device such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, and a hard disk.
- the program is a storage medium or storage device such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, and a hard disk.
- digital signals are distributed over a network.
- data being processed is temporarily stored in a storage device such as a computer memory.
- FIG. 1 is a functional block diagram according to the embodiment of the present invention.
- 2A to 2D are diagrams for explaining the outline of the embodiment of the present invention.
- FIG. 3 is a diagram showing a main processing flow in the embodiment of the present invention.
- FIG. 4A is a diagram showing schema information of an order DB as an example of extracted data
- FIG. 4B is a diagram showing a record group of the order DB.
- FIG. 5A shows the schema information of the production DB as an example of extracted data
- FIG. 5B shows the record group of the production DB.
- FIG. 6A is a diagram showing arrangement DB schema information as an example of extracted data
- FIG. 6B is a diagram showing a record group of the arrangement DB.
- FIG. 7A is a diagram showing schema information of a delivery DB as an example of extracted data
- FIG. 7B is a diagram showing a record group of the delivery DB
- FIG. 8A shows schema information of a product number DB as an example of extracted data
- FIG. 8B shows a record group of the product number DB.
- FIG. 9A shows an example of data in the order DB in the CSV format
- FIG. 9B shows an example in which the data in the order DB is tabulated.
- FIG. 10A shows an example of data in the production DB in CSV format
- FIG. 10B shows an example in which the data in the production DB is tabulated.
- FIG. 11A illustrates an example of data in the arrangement DB in the CSV format
- FIG. 11B illustrates an example in which the data in the arrangement DB is tabulated.
- FIG. 12A shows an example of data in the delivery DB in the CSV format
- FIG. 12B shows an example in which the data in the delivery DB is tabulated.
- FIG. 13A shows an example of data in the product number DB in the CSV format
- FIG. 13B shows an example in which the data in the product number DB is tabulated.
- FIG. 14 is a diagram illustrating a process flow of the time stamp determination process.
- FIG. 15 is a diagram illustrating an example of a time stamp accuracy score table.
- FIG. 16 is a diagram illustrating a processing flow of event ID / related ID candidate determination processing.
- FIG. 17 is a diagram illustrating an example of an event ID / related ID candidate accuracy score table.
- FIG. 18 is a diagram illustrating a process flow of the event name determination process.
- FIG. 19 is a diagram illustrating an example of a table including a plurality of time stamps.
- 20A to 20E are diagrams illustrating an example in which the table of FIG. 19 is divided into a plurality of tables for each event.
- FIG. 21 is a diagram illustrating an example of determination display for each element of event candidate data in the order DB when schema information exists.
- FIG. 22 is a diagram illustrating an example of a determination display for each element of an event candidate in the order DB in the case of CSV format data.
- FIG. 23 is a diagram illustrating an example of a determination display for each element of event candidate data in the production DB when schema information exists.
- FIG. 24 is a diagram illustrating an example of a determination display for each element of the production DB event candidate in the case of CSV format data.
- FIG. 25 is a diagram illustrating an example of a determination display for each element of event candidate data in the arrangement DB when schema information exists.
- FIG. 26 is a diagram illustrating an example of a determination display for each element of event candidates in the arrangement DB in the case of CSV format data.
- FIG. 27 is a diagram illustrating an example of a determination display for each element of event candidate data in the delivery DB when schema information exists.
- FIG. 24 is a diagram illustrating an example of a determination display for each element of the production DB event candidate in the case of CSV format data.
- FIG. 25 is a diagram illustrating an example of a determination display for each element of event candidate data in the arrangement DB when schema information exists.
- FIG. 28 is a diagram illustrating an example of a determination display for each element of a delivery DB event candidate in the case of CSV format data.
- FIG. 29 is a diagram illustrating an example of a determination display for each element of event candidate data in the product number DB when schema information exists.
- FIG. 30 is a diagram illustrating an example of a determination display for each element of event candidates in the product number DB in the case of CSV format data.
- FIG. 31 is a diagram illustrating an example of a selection result for each element of event candidate data.
- FIG. 32 is a diagram illustrating an example of event candidate data generated from data in the order DB when schema information exists.
- FIG. 33 is a diagram showing an example of event candidate data generated from data in the order DB in the case of CSV format data.
- FIG. 29 is a diagram illustrating an example of a determination display for each element of event candidate data in the product number DB when schema information exists.
- FIG. 30 is a diagram illustrating an example of a determination display
- FIG. 34 is a diagram illustrating an example of event candidate data generated from data in the production DB when schema information exists.
- FIG. 35 is a diagram illustrating an example of event candidate data generated from production DB data in the case of CSV format data.
- FIG. 36 is a diagram illustrating an example of event candidate data generated from the data in the arrangement DB when schema information exists.
- FIG. 37 is a diagram showing an example of event candidate data generated from data in the arrangement DB in the case of CSV format data.
- FIG. 38 is a diagram illustrating an example of event candidate data generated from data in the delivery DB when schema information exists.
- FIG. 39 is a diagram illustrating an example of event candidate data generated from data in the delivery DB in the case of CSV format data.
- FIG. 35 is a diagram illustrating an example of event candidate data generated from production DB data in the case of CSV format data.
- FIG. 36 is a diagram illustrating an example of event candidate data generated from the data in the arrangement DB when schema information exists.
- FIG. 40 is a diagram showing an example of event candidate data related to the draft in FIG. 41 is a diagram showing an example of event candidate data related to the approval of FIG.
- FIG. 42 is a diagram showing an example of event candidate data related to the order shown in FIG.
- FIG. 43 is a diagram showing an example of event candidate data related to delivery in FIG.
- FIG. 44 is a diagram illustrating an example of event candidate data relating to the inspection in FIG.
- FIG. 45 is a diagram illustrating an example of event data and an inter-event relationship tree.
- FIG. 46 is a diagram for explaining process instance generation from event data.
- FIG. 47 is a diagram illustrating an example of a process instance.
- FIG. 48 is a diagram for explaining main and exceptional flow extraction processing.
- FIG. 49 is a diagram showing a display example when the process instances shown in FIG. 48 are overlaid.
- 50A to 50C are diagrams showing display examples when the process instances shown in FIG. 48 are classified into main flows and exception flows.
- FIG. 51 is a diagram illustrating an example of a process instance for explaining the deduplication processing.
- FIG. 52 is a diagram showing an example in which the process instances shown in FIG. 51 are simply classified.
- FIG. 53 is a diagram illustrating a processing flow of the deduplication processing.
- FIG. 54A is a diagram illustrating an example of a process instance having overlapping repetitions.
- FIG. 54B is a diagram illustrating an example of process instances when overlapping repetitions are deleted.
- FIG. 55 is a diagram showing a process flow of the return overlap elimination process.
- FIG. 56 is a diagram showing an example of a process instance for explaining the return overlap elimination processing.
- FIG. 57 is a diagram for explaining extraction of the return part.
- FIG. 58A is a diagram for explaining classification of the return portion.
- FIG. 58B is a diagram for describing processing for deleting duplication of a return part.
- FIG. 59 is a diagram illustrating an example of reconstructing a process instance.
- FIG. 60 is a diagram showing an example of superimposed display of process instances in FIG.
- FIG. 61 is a diagram showing an example of superimposed display of process instances in FIG.
- FIG. 62 is a diagram showing a process instance as a result of performing the deduplication processing on the process instance example shown in FIG. FIG.
- FIG. 63 is a diagram illustrating an example of data stored in the model data storage unit.
- FIG. 64 is a diagram showing a processing flow of flow display processing.
- FIG. 65 is a diagram showing a display example when all the process instances registered in FIG. 63 are overlaid.
- FIG. 66 is a diagram showing a display example when the process instances registered in FIG. 63 are divided into main flows and exception flows.
- FIG. 67 is a functional block diagram of the computer apparatus.
- FIG. 1 shows a functional block diagram of a business system analysis apparatus according to an embodiment of the present invention.
- the business system analysis apparatus according to the present embodiment includes data collected from one or a plurality of analysis target systems (database record group, log data, network DB (NDB) record group, journal, etc. generated in a predetermined period).
- database record group data collected from one or a plurality of analysis target systems
- NDB network DB
- Analysis target data storage unit 1 that stores event candidate data generation unit 3 that generates event candidate data from the analysis target data storage unit 1, and an event that stores event candidate data generated by the event candidate data generation unit 3
- Candidate data storage unit 5 input / output unit 11 serving as an interface with the user
- event data generation unit 7 that receives user instructions via the input / output unit 11 and generates event data
- event data generation unit 7 An event data storage unit 9 for storing the event data that has been received
- a process instance generation unit 13 that generates a process instance from event data stored in the event data storage unit 9, a process instance data storage unit 15 that stores data of a process instance generated by the process instance generation unit 13, and a process
- a duplication resolving unit 17 that performs processing for deleting rework and repetition that makes it difficult to grasp the overall picture of the business
- a duplication resolving unit 17 A simplified process instance data storage unit 19 that stores data of processed process instances, and a process instance that classifies the process instances stored in the
- the input / output unit 11 also operates as an interface with the user for the event candidate data generation unit 3, the process instance generation unit 13, and the process display processing unit 25.
- each processing unit may perform processing such as reading a processing result and presenting it to the user via the input / output unit 11.
- the event candidate data generation unit 3 includes a time stamp processing unit 31, an event ID / related ID candidate processing unit 32, an event name processing unit 34, and a score table storage unit 35. Furthermore, the duplication elimination unit 17 includes a repetition processing unit 171 and a rework processing unit 173.
- the event candidate data generation unit 3 generates event candidate data from data on the business system stored in the analysis target data storage unit 1.
- An example of event candidate data is shown in FIG. In the example of FIG. 2A, for example, from one table (for example, a database), the event name, time (time stamp that is the date and time when the event occurred), other first value (value 1), A record group including a value of 2 (value 2) and the like is extracted.
- event names and time stamps, and other data fields that are candidates for event IDs and related IDs are specified.
- the event data generation unit 7 generates event data from the event candidate data stored in the event candidate data storage unit 5.
- An example of event data is shown in FIG. In the example of FIG. 2B, from a plurality of tables (for example, databases), a record group including an event name, time (time stamp which is the date and time of occurrence of the event), event ID (here ID1), and other values, A record group including an event name, time (time stamp), ID1 and ID2 is extracted, and a field value of ID2 which is a related ID of a record of the second event class (that is, event type) is the first, By taking any value of the field value of ID1 which is the event ID of the record of the event class (ie, event type), each record (ie, event instance) of the second event class becomes the first event.
- the process instance generation unit 13 generates process instance data from the event data stored in the event data storage unit 9.
- An example of the process instance is shown in FIG. In the example of FIG. 2C, four process instances are illustrated, and each process instance includes a series of event instances (specific events). That is, for example, a process instance is composed of consecutive event instances (specific events that correspond to specific records) belonging to event classes such as “order received”, “draft”, “delivery”, and “inspection”. However, the event instances included in the process instances do not have to be derived from all event classes, and a plurality of event instances belonging to one event class may be included.
- the process instance generation process itself is not a main part in the present embodiment, and for example, a business process tracking method such as US Patent Publication No. 2005 / 076059A1 can be used. This publication is incorporated in the present application.
- the process instance data is processed by the deduplication unit 17 and the process instance classification processing unit 21, and the process display processing unit 25 determines the process flow (also referred to as a business flow) from the data stored in the model data storage unit 23. Data) is generated and displayed on the display device via the input / output unit 11.
- a business flow in which process instances are identified and specified is shown.
- the user designates the analysis target table in the business system, copies the data, and stores it in the analysis target data storage unit 1 (FIG. 3: step S1). For example, an order DB, a production DB, an arrangement DB, a delivery DB, and a product number DB are designated, and a record group generated and accumulated in a predetermined period is copied and stored in the analysis target data storage unit 1. If these DBs are relational databases, the schema information is also copied and stored in the analysis target data storage unit 1. Since this step is a process performed in advance by the user operating the computer, it is indicated by a dotted line block in FIG.
- schema information as shown in FIG. 4A and a record group as shown in FIG. 4B are stored in the analysis target data storage unit 1.
- the field name, key setting data, data type, record length, and comment are registered for each of the fields 1 to 4.
- the date and time is registered in field 1
- the order number as the primary key is registered in field 2
- the region is registered in field 3
- the order details are registered in field 4. I understand.
- the record group is as shown in FIG. 4B, but if the schema information as shown in FIG. 4A is obtained, the contents of the record group as shown in FIG. 4B are easily interpreted. be able to.
- schema information as shown in FIG. 5A and a record group as shown in FIG. 5B are stored in the analysis target data storage unit 1.
- the field name, key setting data, data type, record length, and comment are registered for each of the fields 1 to 5.
- the date and time is registered in field 1
- the production number as the primary key is registered in field 2
- the order number as the secondary key is registered in field 3
- the secondary key is registered in field 4. It can be seen that the product number is registered and the delivery date is registered in the field 5.
- the record group is as shown in FIG. 5B, but if the schema information as shown in FIG. 5A is obtained, the contents of the record group as shown in FIG. 5B are easily interpreted. be able to.
- schema information as shown in FIG. 6A and a record group as shown in FIG. 6B are stored in the analysis target data storage unit 1.
- the field name, key setting data, data type, record length, and comment are registered for each of the fields 1 to 5.
- the date and time is registered in field 1
- the order number as the primary key is registered in field 2
- the order number as the secondary key is registered in field 3
- the secondary key is registered in field 4. It can be seen that the product number is registered and the delivery destination is registered in the field 5.
- the record group is as shown in FIG. 6B, but if the schema information as shown in FIG. 6A is obtained, the contents of the record group as shown in FIG. 6B are easily interpreted. be able to.
- schema information as shown in FIG. 7A and a record group as shown in FIG. 7B are stored in the analysis target data storage unit 1.
- the field name, key setting data, data type, record length, and comment are registered for each of the fields 1 to 4.
- date and time are registered in field 1
- an arrangement number as a primary key is registered in field 2
- a delivery flight as a secondary key is registered in field 3
- a delivery destination is stored in field 4. You can see that it is registered.
- the record group is as shown in FIG. 7B, but if the schema information as shown in FIG. 7A is obtained, the contents of the record group as shown in FIG. 7B can be easily interpreted. be able to.
- schema information as shown in FIG. 8A and a record group as shown in FIG. 8B are stored in the analysis target data storage unit 1.
- schema information shown in FIG. 8A field names, key setting data, data types, record lengths, and comments are registered for fields 1 and 2, respectively. From FIG. 8A, it can be seen that the product number which is the primary key is registered in the field 1, and the product name is registered in the field 2.
- the record group is as shown in FIG. 8B, but if the schema information as shown in FIG. 8A is obtained, the contents of the record group as shown in FIG. 8B are easily interpreted. be able to.
- the data of the order DB is acquired in the CSV format
- the data as shown in FIG. 9A is stored in the analysis target data storage unit 1.
- label data such as date / time, order number, region, and order contents are included at the top, and thereafter, the data is listed in the order of the labels, and the data is separated by commas.
- the table format is used to make FIG. 9 (a) easier to understand, it will be as shown in FIG. 9 (b). That is, the table includes a date / time column, an order number column, a region column, and an order content column. Since there is no schema information, all data is stored as character strings. There is no key setting data.
- FIG. 10A when the data of the production DB is acquired in the CSV format, data as shown in FIG. 10A is stored in the analysis target data storage unit 1.
- label data such as date / time, production number, order number, product number, and delivery date is included at the head, and then the data is listed in the order of the labels, and the data is separated by commas. Yes.
- FIG. 10B a table format is shown in FIG. 10B. That is, the table includes a date / time column, a production number column, an order number column, a product number column, and a delivery date column.
- FIG. 11A when the data of the arrangement DB is acquired in the CSV format, data as shown in FIG. 11A is stored in the analysis target data storage unit 1.
- label data such as date / time, arrangement number, order number, product number, and delivery destination is included at the top, and then the data is listed in the order of the labels, and the data is separated by commas. ing.
- FIG. 11 (b) a table format is shown in FIG. 11 (b). That is, the table includes a date / time column, an arrangement number column, an order number column, a product number column, and a delivery destination column.
- data as shown in FIG. 12A is stored in the analysis target data storage unit 1.
- label data such as date / time, arrangement number, delivery flight, and delivery destination is included at the top, and thereafter, the data is listed in the order of the labels, and the data is separated by commas.
- FIG. 12A a table format is shown in FIG. That is, the table includes a date / time column, an arrangement number column, a delivery flight column, and a delivery destination column.
- FIG. 13A when the data of the product number DB is acquired in the CSV format, data as shown in FIG. 13A is stored in the analysis target data storage unit 1.
- label data of a product number and a product name is included at the head, and thereafter, the data is arranged in the order of the labels, and the data is separated by commas.
- FIG. 13 (b) If the table format is used to make FIG. 13 (a) easier to understand, it will be as shown in FIG. 13 (b). That is, the table includes a product number column and a product name column.
- the event candidate data generation unit 3 of the business system analysis apparatus determines whether all the analysis target tables have been processed (step S3). If there is an unprocessed analysis target table, one unprocessed analysis target table is specified (step S5). Then, a time stamp determination process is performed (step S7). This time stamp determination process will be described with reference to FIGS.
- the time stamp processing unit 31 of the event candidate data generating unit 3 refers to the analysis target data storage unit 1 and identifies one unprocessed field in the analysis target table (FIG. 14: step S31). Then, it is determined whether the schema information of the analysis target table is usable in the analysis target data storage unit 1 (step S33).
- step S35 If the schema information is usable, the data portion of the processing target field is specified in the schema information, and it is determined whether the data type of the processing target field is a time stamp type (step S35). If the data type of the processing target field is not the time stamp type, the process proceeds to step S39. For example, in the case of processing data as shown in FIGS. 9A to 13A, there is no schema information, so the process proceeds to step S39.
- step S37 when it is determined that the data type of the processing target field is a time stamp type, the time stamp determination of the processing target field is set to “confirmed” and stored in a storage device such as a main memory (step S37). ). Then, the process proceeds to step S43.
- step S33 If it is determined in step S33 that the schema information is unusable or the data type of the processing target field is not a time stamp type, the time stamp accuracy score table stored in the score table storage unit 35 is referred to, and the schema information The accuracy is specified from the corresponding data portion of the processing target field, the label data indicating the field name of the processing target field, and the field value of the processing target field (step S39).
- the accuracy score is set to 1 (%) if the field data type is a variable-length character string, and the accuracy score is 5 (%) if the field data type is a real number. If the field name ends with "Time”, “Time”, etc., the accuracy score is set to 90 (%), and the field name ends with "Monday”, “Day”, etc. If not, the accuracy score is set to 70 (%). If a future time such as “plan” or “delivery date” is specified as the field name, the accuracy score is set to 10 (%).
- the accuracy score is 5 ( %)
- the field value string is “YYYY / MM / If the format is Dhh: mm: ss, the accuracy score is set to 90 (%), and if the field value string is "YYYY / MM / DD", the accuracy score is set to 70 (%). If the same field value is included, the accuracy score is set to 30 (%), and if there is no corresponding item, the accuracy score is set to 50 (%).
- the probability score is assumed that the field value includes characters other than characters related to time. 5 (%) is specified. Similarly, the probability score 5 (%) is specified for the field 3 on the assumption that the field value includes characters other than the characters related to time. Furthermore, since the data type of the field 4 is a variable length character string, the accuracy score is specified as 1 (%). For field 4, since the field value includes characters other than time-related characters, it corresponds to a plurality of items in the time stamp accuracy score table, but in this embodiment, it is 50 (%). The value that deviates from the median is adopted. That is, 1 (%) is adopted rather than the accuracy score of 5 (%) when the field value includes characters other than characters related to time.
- the field values include characters other than characters related to time.
- the accuracy score is 5 (%).
- the accuracy score is specified as 10 (%).
- the field value character string in the format of “YYYY / MM / DD” corresponds to a plurality of items in the time stamp accuracy score table, but in the present embodiment, 50 (% ), Which is more deviated from the median. That is, 10 (%) is adopted rather than the accuracy score 70 (%) when the character string of the field value is in the format of “YYYY / MM / DD”.
- the field value includes characters other than characters related to time. Specificity is specified as an accuracy score of 5 (%).
- the accuracy score is 90 (%). Identified.
- the fields 2 and 4 since the data type is not related, the same result as in the case where the schema information exists is obtained.
- the field value includes characters other than characters related to time. Specificity is specified as an accuracy score of 5 (%).
- the data type is not related, so that the same result as in the case where the schema information exists can be obtained.
- the time stamp determination of the processing target field is set to the specified accuracy score (step S41).
- the numerical values mentioned above are identified.
- step S43 it is determined whether all fields in the processing target table have been processed. If there is an unprocessed field, the process returns to step S31. On the other hand, when all fields are processed, the process returns to the original process.
- a high accuracy score is set in a highly probable field as an event time stamp. If the time stamp is clear from the data type, data indicating the probability of “determined” is set.
- step S9 the event ID / related ID candidate processing unit 32 of the event candidate data generating unit 3 performs an event ID and related ID candidate determination process.
- the event ID and related ID candidate determination processing will be described with reference to FIGS.
- the event ID / related ID candidate processing unit 32 identifies one unprocessed field in the analysis target table stored in the analysis target data storage unit 1 (step S51). Then, it is determined whether the field value of the processing target field stored in the analysis target data storage unit 1 is unique among all records (step S53). If the field value of the processing target field is not unique among all records, that is, there is a record with a duplicate value, the process proceeds to step S62.
- the event ID is an event identifier storage field
- the field values do not overlap each other. Therefore, if there is a duplicate value in the event ID field, it can be determined that it is not an event ID.
- step S55 it is determined whether NULL is included in the field value of the processing target field stored in the analysis target data storage unit 1 (step S55). ). If NULL is included in the field value of the processing target field, the process proceeds to step S62. This is because the event ID is a storage field for an event identifier, and the field value cannot be NULL.
- the field value of the processing target field stored in the analysis target data storage unit 1 is It is determined whether there are two or more except NULL (step S62).
- step S63 If there are not two or more field values of the processing target field except NULL, “No” is set in the event ID / related ID candidate determination, and the result is stored in a storage device such as a main memory (step S63). Then, the process proceeds to step S61. This is because the related ID is a value indicating which of the other events corresponds to the event, and if the field value does not have two or more values except NULL, a meaningful result cannot be obtained. .
- field 1 and field 2 do not have duplicate field values, and fields 3 to 5 have duplicates, but other than NULL. Therefore, “No” is not set in the event ID / related ID candidate determination.
- field 1 and field 2 have no duplicate field values, and fields 3 and 4 have duplicates, but other than NULL. Therefore, “No” is not set in the event ID / related ID candidate determination.
- step S55 When it is determined in step S55 that the field value of the processing target field does not include NULL, or when it is determined in step S62 that the field value of the processing target field has two or more types of values excluding NULL.
- the event ID / related ID candidate probability score table stored in the score table storage unit 35, the corresponding data portion of the processing target field in the schema information, the label data indicating the field name of the processing target field, and the processing The accuracy is specified from the field value of the target field (step S57). However, when there is no corresponding item in the event ID / related ID candidate accuracy score table, the accuracy score 50 (%) is specified.
- FIG. 17 An example of the event ID / related ID candidate accuracy score table is shown in FIG. In the example of FIG. 17, if the field data type is a variable-length character string, the accuracy score is set to 1 (%), and if the field data type is a real number, the accuracy score is set to 5 (%). If the data type of is an integer, the accuracy score is set to 80 (%). If the data type of the field is a fixed-length character string, the accuracy score is set to 70 (%). If it is a date, the accuracy score is set to 10 (%), and if the field name is designated as a primary key, the accuracy score is set to 80 (%).
- An item for a field value or field name string is not defined here, but may be defined. If an item for the field value is defined, it is referred to in step S57.
- the data type for field 1 is a time stamp, so the accuracy score is 10 (%), and the data type for field 2 is a fixed-length character string. And since the primary key is specified, an accuracy score of 80 (%) with a large deviation from 50% is adopted, and since the data type of field 3 is a fixed-length character string, it is specified as an accuracy score of 70 (%).
- the data type is a variable length character string, so the accuracy score is 1 (%).
- the accuracy score 50 (%) is specified for the field 1 to the field 4 because the corresponding item does not exist in the event ID / related ID candidate accuracy score table.
- the data type for field 1 is a time stamp, so the accuracy score is 10 (%), and the data type for field 2 is a fixed-length character string.
- the primary key is specified, an accuracy score of 80 (%) with a large deviation from 50% is adopted, and the accuracy score of 70 (%) is specified because the data type is a fixed-length character string for fields 3 to 4
- the accuracy score 10 (%) is specified.
- the accuracy score 50 (%) is specified for the field 1 to the field 5 because the corresponding item does not exist in the event ID / related ID candidate accuracy score table.
- the accuracy score is specified as 10 (%), and for field 2, the data type is a fixed-length character string. And since the primary key is specified, an accuracy score of 80 (%) with a large discrepancy from 50% is adopted, and for field 3 to field 5, the data type is a fixed-length character string, so an accuracy score of 70 (%) is specified. Is done.
- the accuracy score 50 (%) is specified for the fields 1 and 5 because the corresponding item does not exist in the event ID / related ID candidate accuracy score table. Is done.
- the accuracy score is specified as 10 (%), and the data type for field 2 is a fixed-length character string. And since the primary key is specified, an accuracy score of 80 (%) with a large deviation from 50% is adopted, and the accuracy score of 70 (%) is specified because the data type is a fixed-length character string for fields 3 to 4 Is done.
- the accuracy score 50 (%) is specified for the field 1 to the field 4 because the corresponding item does not exist in the event ID / related ID candidate accuracy score table.
- the event ID / related ID candidate processing unit 32 sets the accuracy score specified in step S57 for the event ID / related ID candidate determination, and stores it in a storage device such as a main memory (step S59).
- step S61 it is determined whether all fields in the processing target table have been processed (step S61), and if there is an unprocessed field, the process returns to step S51. On the other hand, if all fields are processed, the process returns to the original process.
- step S13 the event name processing unit 34 of the event candidate data generation unit 3 performs an event name determination process (step S13). This event name determination process will be described with reference to FIGS.
- the event name processing unit 34 counts the number of fields that can be regarded as time stamp fields with a predetermined accuracy score or higher as the processing result of the time stamp determination processing (step S91). For example, a threshold value such as an accuracy score of 70 (%) or higher is set.
- a threshold value such as an accuracy score of 70 (%) or higher is set.
- the field identified as “determined” is a time stamp field.
- the field whose field name is date / time is determined to be a time stamp field, and the number of fields is “1”. In the product number DB, since there is no field that can be regarded as a time stamp, the number of fields is “0”.
- step S93 it is determined whether the number of time stamp fields is 0 (step S93). If the number of fields is 0, the analysis target table is set to be excluded from the following processing (step S95). A table without a time stamp (for example, a product number DB) is determined not to be a table corresponding to an event that occurs during a business process. Then, the process returns to the original process.
- a time stamp for example, a product number DB
- step S97 it is determined whether the number of fields is 1 (step S97). If the number of fields in the time stamp is 1, a table name is set as the event name and stored in a storage device such as a main memory (step S99).
- the event name is specified as “order received” in the case of the order DB
- the event name is specified as “production” in the case of the production DB
- the event name is “arrangement” in the case of the arrangement DB.
- the event name is specified as “delivery”. Then, the process returns to the original process.
- the field name of the field regarded as the time stamp is set as the event name and stored in a storage device such as a main memory (step S101). Then, the process returns to the original process.
- step S101 is executed.
- the draft date / time, approval date / time, order date / time, delivery date / time, and inspection date / time are fields that are regarded as event time stamps, and a plurality of events are recorded in one record.
- Such a table can be handled as a plurality of tables such as a drafting table, an approval table, an ordering table, a delivery table, and an inspection table as shown in FIGS. Therefore, in such a case, “draft”, “approval”, “ordering”, “delivery”, and “acceptance” are specified as event names.
- the event candidate data generation unit 3 presents the determination result to the user via the input / output unit 11 (step S15).
- the determination results of steps S7 to S13 are presented for each of the date / time field, the order number field, the region field, and the order detail field.
- the event name the table name is used as the event name, so that all of the event names are set to “deny”. From this, it can be seen that the date / time field is “fixed” in the time stamp field, and the order number field and the region field are highly likely to be event IDs or related IDs.
- the order DB in the CSV format shown in FIG. 9A data as shown in FIG. 22 is presented to the user.
- the determination results of steps S7 to S13 are presented for each of the date / time field, the order number field, the region field, and the order detail field.
- the event name the table name is used as the event name, so that all of the event names are set to “deny”. From this, it can be seen that the date / time field is likely to be a time stamp, and the possibility of being an event ID or a related ID is the same for any field.
- data as shown in FIG. 23 is presented to the user.
- the determination results of steps S7 to S13 are presented for each of the date / time field, production number field, order number field, product number field, and delivery date field.
- the event name the table name is used as the event name, so that all of the event names are set to “deny”. From this, it can be seen that the date / time field is “fixed” in the time stamp field, and the production number field, the order number field, and the product number field are highly likely to be event IDs or related IDs.
- data as shown in FIG. 24 is presented to the user.
- the determination results of steps S7 to S13 are presented for each of the date / time field, production number field, order number field, product number field, and delivery date field.
- the event name the table name is used as the event name, so that all of the event names are set to “deny”. From this, it can be seen that the date / time field is likely to be a time stamp, and the possibility of being an event ID or a related ID is the same for any field.
- data as shown in FIG. 25 is presented to the user.
- the determination results of steps S7 to S13 are presented for each of the date / time field, the arrangement number field, the order number field, the product number field, and the delivery destination field.
- the event name the table name is used as the event name, so that all of the event names are set to “deny”. From this, it can be seen that the date / time field is “fixed” in the time stamp field, and the arrangement number field, the order number field, the product number field, and the delivery destination field are highly likely to be event IDs or related IDs.
- the determination results of steps S7 to S13 are presented for each of the date / time field, the arrangement number field, the order number field, the product number field, and the delivery destination field.
- the event name the table name is used as the event name, so that all of the event names are set to “deny”. From this, it can be seen that the date / time field is likely to be a time stamp, and the possibility of being an event ID or a related ID is the same for any field.
- data as shown in FIG. 27 is presented to the user.
- the determination results of steps S7 to S13 are presented for each of the date / time field, the arrangement number field, the delivery flight field, and the delivery destination field.
- the event name the table name is used as the event name, so that all of the event names are set to “deny”. From this, it can be seen that the date / time field is “fixed” in the time stamp field, and the arrangement number field, the delivery flight field, and the delivery destination field are highly likely to be event IDs or related IDs.
- data as shown in FIG. 28 is presented to the user.
- the determination results of steps S7 to S13 are presented for each of the date / time field, the arrangement number field, the delivery flight field, and the delivery destination field.
- the event name the table name is used as the event name, so that all of the event names are set to “deny”. From this, it can be seen that the date / time field is likely to be a time stamp, and the possibility of being an event ID or a related ID is the same for any field.
- step S ⁇ b> 15 when step S ⁇ b> 15 is completed, the user performs correction input or confirmation input for the event name, time stamp, event ID / related ID candidate, and the like via the input / output unit 11, and copies the record.
- the event candidate data is generated by performing or commanding, and the like, and is stored in the event candidate data storage unit 5 in the event candidate data generation unit 3 (step S16). Since this operation is mainly or partly performed by the user, it is drawn as a dotted block in FIG. Then, the process returns to step S3.
- the table name “order received” is confirmed for the event name
- the date / time field is confirmed for the time stamp
- the order number field for the event ID / related ID candidate is stored in the event candidate data storage unit 5.
- the event name “order received” is added to all records, all records of the field value in the date / time field are copied to the time stamp field, and the order number field and the region field are the event ID / related ID. As a candidate, all records of field name and field value are copied.
- “order received” which is a table name is confirmed for the event name, the date / time field is confirmed for the time stamp, the order number field, the region field, and the order contents for the event ID / related ID candidate.
- the field is determined, for example, data as shown in FIG. 33 is stored in the event candidate data storage unit 5.
- “arrangement” which is a table name is determined for the event name, the date / time field is determined for the time stamp, the arrangement number field and the order number field for the event ID / related ID candidate,
- the product number field and the delivery destination field are determined, for example, data as shown in FIG. 36 is stored in the event candidate data storage unit 5.
- “delivery” which is a table name is confirmed for the event name, the date / time field is confirmed for the time stamp, the arrangement number field and the delivery flight field for the event ID / related ID candidate,
- the delivery destination field is determined, for example, data as shown in FIG. 38 is stored in the event candidate data storage unit 5.
- “delivery” which is a table name for the event name is confirmed, the date / time field is confirmed for the time stamp, the arrangement number field, the delivery flight field and the event ID / related ID candidate
- the event candidate data storage unit 5 When finalizing the delivery destination field, for example, data as shown in FIG. 39 is stored in the event candidate data storage unit 5.
- data as shown in FIGS. 40 to 44 is the event candidate data storage unit 5.
- the event name is set to “start” for each field based on the draft date / time, the approval date / time, the order date / time, the delivery date / time, and the inspection date / time, which are determined as time stamps. Create event candidate data that is confirmed as “voting”, “approval”, “ordering”, “delivery”, and “acceptance”.
- all records of the field values of the draft date / time field, the approval date / time field, the order date / time field, the delivery date / time field, and the inspection date / time field are copied to the time stamp field of each event candidate data.
- fields other than the draft date / time field, approval date / time field, order date / time field, delivery date / time field, and inspection date / time field are all field names and field values as event ID / related ID candidates. The record is copied.
- event candidate data used in the following processing is stored in the event candidate data storage unit 5.
- step S3 If it is determined in step S3 that all the analysis target tables have been processed, the event data generation unit 7 uses the event candidate data stored in the event candidate data storage unit 5 to perform event data generation processing. Then, the processing result is stored in the event data storage unit 9 (step S17).
- FIG. 32, FIG. 34, FIG. 36, and FIG. 38, respectively, or FIG. 33, FIG. FIG. 45 shows an example of event data generated using the set of event candidate data shown in FIG. 37 and FIG.
- the generation method the above-described automatic extraction method of event data related information as described in Japanese Patent Application No. 2006-197294 described above may be used, or the event ID / relation of each event candidate data manually.
- the relationship between the events may be determined by investigating and analyzing the correspondence relationship between the field values of the ID candidates.
- the event ID of the order event is the order number
- the event ID of the production event is the production number
- the related ID is the order number
- the event ID of the order event is the order number
- the related ID is the order number
- the delivery It is confirmed that the event ID of the event is an arrangement number and the related ID is a delivery flight.
- each record of the production event that is, the event instance
- each record of the production event is changed to which record ( That is, the relevance between events is determined so that it is specified whether it is related to the event instance). Similar relevance is determined between the event ID of the arrangement event and the event ID of the order event, and between the event ID of the delivery event and the event ID of the arrangement event.
- the process instance generation unit 13 performs a process instance generation process using the event data stored in the event data storage unit 9, and stores the processing result in the process instance data storage unit 15 (step S19).
- a business process tracking method such as US Patent Publication No. 2005 / 076059A1 can be used.
- FIG. 46 shows a schematic explanation of the process for generating a process instance starting from the order event instance of the order number JT01 using the event data of FIG.
- a record that is, an event instance
- JT01 order ID field value
- two event instances from the production event and three event instances from the arrangement event are determined. Is done.
- the arrangement number: TH01, TH02, TH03 which is the event ID of the confirmed arrangement event, is recorded as a record (that is, an event instance) having the field number of the related ID as three fields from the delivery event.
- the event instance is finalized.
- the process is performed by connecting the event instances that are directly or indirectly related to each other in the order of time based on the value of the time stamp, starting from the confirmed order number instance of JT01.
- An instance is created. That is, as the first process instance, a process instance is generated in which event instances such as orders, production, arrangement, arrangement, arrangement, delivery, production, delivery, and delivery are arranged in time series.
- the second process instance is a process instance in which event instances of order receipt, arrangement, and delivery are arranged in time series.
- the third process instance is a process instance in which event instances of order receipt, production, production, arrangement, and delivery are arranged in time series.
- the fourth process instance is a process instance in which event instances such as orders, arrangements, and deliveries are arranged in time series.
- the deduplication unit 17 performs deduplication processing using the process instance data stored in the process instance data storage unit 15 (step S ⁇ b> 21). This process will be described in detail with reference to FIGS.
- a process instance is created to return to the billing through continuation and perform collection (return) to transition to contract expiration and final state.
- C is configured.
- one process instance is created in which collection is performed (repeated) again and the contract expires and the state transitions to final state.
- FIG. A flow in which process instances of group B are superimposed is generated and presented to the user.
- the exception flow is a process instance of group C shown in FIG. 50B (however, for the sake of explanation, the routed event instance and the transition of the return part are indicated by dotted lines), FIG.
- the process instance of the group D shown in 50 (c) (however, for the sake of easy explanation, the transition representing the repetition is shown by a dotted line) is presented to the user.
- the process of initial state, contract, voucher creation, billing, collection, contract expiration, and final phase is basically the same as creating a voucher, billing and collection once via a contract update event instance.
- One process instance is generated that performs rework for repeating billing and collection three times.
- one process instance is also generated that performs rework that repeats billing and collection once via a continuation event instance. Has been.
- the deduplication unit 17 identifies one unprocessed process instance in the process instance data storage unit 15 (FIG. 52: step S111). Then, the specified process instance is inspected for repetition and rework (step S113). Identifies a transition that returns to or from another event instance that was executed before a specific event instance as a reversal, and a transition that returns to the same event instance as a repetition .
- One process instance may include repetition and rework, and may include multiple locations, repetitive or rework.
- the iterative processing unit 171 of the duplication eliminating unit 17 determines whether or not all repetitive portions have been processed for the identified process instance (step S115). If there is an unprocessed repeat location, the repeat processing unit 171 identifies an unprocessed repeat location (step S117), leaves only one iteration at the identified repeat location, and deletes the rest (step S119). . Then, the process returns to step S115.
- the return processing unit 173 determines whether all the returned portions have been processed (step S121). If there is an unprocessed return part, the return processing unit 173 identifies one unprocessed return part (step S123). Then, a return overlap elimination process is performed (step S125). The return overlap elimination process will be described with reference to FIGS. 55 to 58B.
- the return processing unit 173 cuts out the return portion at the specified return location (step S131).
- a process instance as shown in FIG. 56 is processed is assumed. Specifically, in this process instance, Initial State, contract, slip creation, billing, contract renewal, proceed to billing start, return to billing, contract renewal, proceed to billing start, then return to slip creation, After proceeding to billing, contract renewal, and billing start, return to billing, proceed to contract renewal, billing start, billing end, and proceed to Final State.
- step S131 as shown in FIG. 57, a first return part to return to billing, a second return part to return to bill creation, and a third return part to return to billing are cut out.
- the return processing unit 173 classifies the patterns of the return portion (step S133). As shown in FIG. 58A, the three reworked parts cut out as shown in FIG. 58 are identified as pattern 1 in the two reworked parts until billing, contract renewal, and billing start. One return part is identified as pattern 2.
- the rework processing unit 173 eliminates duplication for each pattern, that is, leaves one rework for each pattern and deletes the remaining rework (step S135).
- the rework processing unit 173 eliminates duplication for each pattern, that is, leaves one rework for each pattern and deletes the remaining rework (step S135).
- the return processing unit 173 reconstructs the process instance and stores it in the simplified process instance data storage unit 19 (step S137).
- the reworked portions of patterns 1 and 2 are connected as event instances that occur in succession, and Initial State, contract, slip creation, billing, contract update, Process instances are generated in which event instances are generated in the order of billing start, billing, contract update, billing start, slip creation, billing, contract update, billing start, billing end, FinalFState.
- step S121 If it is determined in step S121 that all reworked parts have been processed or if there are no reworked parts, the duplication eliminating unit 17 determines whether all process instances have been processed (step S127). If there is an unprocessed process instance, the process returns to step S111. On the other hand, if there is no unprocessed process instance, the process returns to the original process.
- the process instance classification processing unit 21 classifies the process instances stored in the simplified process instance data storage unit 19, counts for each type based on the classification result, and calculates for each type.
- the numerical value is stored in the model data storage unit 23 (step S23).
- the process display processing unit 25 performs a flow display process using the data stored in the model data storage unit 23 (step S25). The flow display process will be described with reference to FIGS.
- the flow display processing unit 25 arranges the process instance groups stored in the model data storage unit 23 in descending order based on the count value (step S141).
- a threshold value for the ratio of the total number of process instances in the group which is a criterion for handling each process group as a main flow
- it is determined by a preset value (step S143). For example, when a group having a threshold of 20% or more of the total ratio is classified as a main flow, 20% is input. However, a preset value (for example, 30%) may be used as it is.
- the flow display processing unit 25 selects one unselected process instance from the higher count value (step S147).
- the selected process instance is designated as a main flow (also called a typical flow) (step S149).
- the main flow flag in the table of the model data storage unit 23 is set to ON.
- the ratio to the whole is 60%, and if the threshold is 20%, the process returns to step S147.
- the ratio to the entire record is 30%, and the process returns to step S147. In this way, the main flow flag is set on for the first record and the second record.
- the ratio to the whole is 10%, and the condition that the ratio to the whole is equal to or greater than the threshold value is not satisfied, so the flow display processing unit 25 returns to the original process.
- process instances other than the group of process instances selected in step S147 are identified as exceptional flows because the main flow flag is not set on.
- the flow display processing unit 25 outputs the processing result via the input / output unit 11 using the data stored in the model data storage unit 23 (step S27). For example, when all process instances are displayed in a superimposed manner, a business flow as shown in FIG. 65 is displayed. As shown in FIG. 65, the display is such that there is only one rework through continuation, rework through contract renewal, and collection.
- the display as shown in FIG. 66 is made. For example, if the classification ratio is 90%, the process instances of the first and second records are overlapped in the table shown in FIG. 63, and the business flow as shown in the upper part of FIG. 66 is displayed as the main flow. Also, the third process instance is displayed as an exception flow in the table shown in FIG.
- the business flow is presented in a very organized form as compared to the classification and display as shown in FIG. 52, so the user can give an overview of the business flow actually being performed. It becomes easier to grasp. That is, since rework and repetition that make it difficult to grasp the overall picture of the work in grasping the characteristics are omitted, it becomes easy to grasp the presence and manner of repetition and the presence and manner of rework.
- the functional block diagram shown in FIG. 1 is an example and does not necessarily correspond to an actual program module.
- Each score table is also an example, and the method of setting the accuracy score value may be determined more finely empirically. Furthermore, as for the items in the score table, there may be a case where fewer items are set or a case where more items are set.
- steps S7 to S13 can be changed, and may be performed in parallel.
- a field that has a “determined” determination or an accuracy score equal to or greater than a predetermined threshold is automatically selected and presented to the user for each determination item, and a determination item that cannot be automatically selected is selected by the user Or you may make it prompt an input.
- loop for the processing target field is configured in each of steps S7 to S13, a loop for the processing target field may be provided outside steps S7 to S13.
- the business system analyzer is a computer device, and as shown in FIG. 67, a memory 2501, a CPU 2503, a hard disk drive (HDD) 2505, a display controller 2507 connected to the display device 2509, and a removable disk 2511.
- Drive device 2513, input device 2515, and communication control unit 2517 for connecting to a network are connected by a bus 2519.
- An operating system (OS: Operating System) and an application program for executing the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. If necessary, the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 to perform necessary operations.
- OS Operating System
- data in the middle of processing is stored in the memory 2501 and stored in the HDD 2505 if necessary.
- an application program for executing the processing described above is stored in the removable disk 2511 and distributed, and installed from the drive device 2513 to the HDD 2505.
- the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517.
- Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above, the OS, and necessary application programs.
Abstract
Description
Claims (7)
- 業務処理の結果を格納するデータベースから案件毎に実施された一連の業務のデータを抽出して、前記案件毎に実施された業務の業務名を時系列に並べたプロセスインスタンスを生成し、プロセスインスタンスデータ格納部に格納するステップと、
前記プロセスインスタンスデータ格納部に格納されている各前記プロセスインスタンスについて、当該プロセスインスタンスの第1の業務から、先に実施された第2の業務に戻る手戻りが発生しているか判断するステップと、
前記手戻りが発生している前記プロセスインスタンスについて、前記手戻りのパターン種別毎に当該手戻りの重複手戻りを削除し、前記重複手戻り削除後の前記プロセスインスタンスを、簡略化プロセスインスタンスデータ格納部に格納するステップと、
前記簡略化プロセスインスタンスデータ格納部に格納されている前記プロセスインスタンスを、種別毎に計数するステップと、
前記計数結果に基づき、出現頻度が所定基準以上となっており且つ前記簡略化プロセスインスタンスデータ格納部に格納されている前記プロセスインスタンスを特定し、主要な業務フローとして出力する出力ステップと、
を、コンピュータに実行させるための業務フロー処理プログラム。 - 前記プロセスインスタンスデータ格納部に格納されている各前記プロセスインスタンスについて、当該プロセスインスタンスの第3の業務から当該第3の業務に戻る繰り返しが発生しているか判断するステップと、
前記繰り返しが発生している前記プロセスインスタンスについて、前記繰り返しのパターン種別毎に当該繰り返しの重複繰り返しを削除し、前記重複繰り返し削除後のプロセスインスタンスを、前記プロセスインスタンスデータ格納部に格納するステップと、
をさらに前記コンピュータに実行させるための請求項1記載の業務フロー処理プログラム。 - 前記簡略化プロセスインスタンスデータ格納部に格納されている各前記プロセスインスタンスについて、当該プロセスインスタンスの第3の業務から当該第3の業務に戻る繰り返しが発生しているか判断するステップと、
前記繰り返しが発生している前記プロセスインスタンスについて、前記繰り返しのパターン種別毎に当該繰り返しの重複繰り返しを削除し、前記重複繰り返し削除後のプロセスインスタンスを、前記簡略化プロセスインスタンスデータ格納部に格納するステップと、
をさらに前記コンピュータに実行させるための請求項1記載の業務フロー処理プログラム。 - 前記出力ステップが、
特定された前記プロセスインスタンスを重ね合わせるステップ
を含む請求項1記載の業務フロー処理プログラム。 - 前記出力ステップが、
特定された前記プロセスインスタンス以外のプロセスインスタンスを、例外フローとして出力するステップ
を含む請求項1記載の業務フロー処理プログラム。 - 業務処理の結果を格納するデータベースから案件毎に実施された一連の業務のデータを抽出して、前記案件毎に実施された業務の業務名を時系列に並べたプロセスインスタンスを生成し、プロセスインスタンスデータ格納部に格納するステップと、
前記プロセスインスタンスデータ格納部に格納されている各前記プロセスインスタンスについて、当該プロセスインスタンスの第1の業務から、先に実施された第2の業務に戻る手戻りが発生しているか判断するステップと、
前記手戻りが発生している前記プロセスインスタンスについて、前記手戻りのパターン種別毎に当該手戻りの重複手戻りを削除し、前記重複手戻り削除後の前記プロセスインスタンスを、簡略化プロセスインスタンスデータ格納部に格納するステップと、
前記簡略化プロセスインスタンスデータ格納部に格納されている前記プロセスインスタンスを、種別毎に計数するステップと、
前記計数結果に基づき、出現頻度が所定基準以上となっており且つ前記簡略化プロセスインスタンスデータ格納部に格納されている前記プロセスインスタンスを特定し、主要な業務フローとして出力する出力ステップと、
を含み、コンピュータに実行される業務フロー処理方法。 - 業務処理の結果を格納するデータベースから案件毎に実施された一連の業務のデータを抽出して、前記案件毎に実施された業務の業務名を時系列に並べたプロセスインスタンスを生成し、プロセスインスタンスデータ格納部に格納する手段と、
前記プロセスインスタンスデータ格納部に格納されている各前記プロセスインスタンスについて、当該プロセスインスタンスの第1の業務から、先に実施された第2の業務に戻る手戻りが発生しているか判断する手段と、
前記手戻りが発生している前記プロセスインスタンスについて、前記手戻りのパターン種別毎に当該手戻りの重複手戻りを削除し、前記重複手戻り削除後の前記プロセスインスタンスを、簡略化プロセスインスタンスデータ格納部に格納する手段と、
前記簡略化プロセスインスタンスデータ格納部に格納されている前記プロセスインスタンスを、種別毎に計数する手段と、
前記計数結果に基づき、出現頻度が所定基準以上となっており且つ前記簡略化プロセスインスタンスデータ格納部に格納されている前記プロセスインスタンスを特定し、主要な業務フローとして出力する出力手段と、
を有する業務フロー処理装置。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2008/053086 WO2009104276A1 (ja) | 2008-02-22 | 2008-02-22 | 業務フロー処理プログラム、方法及び装置 |
KR1020107016492A KR101175475B1 (ko) | 2008-02-22 | 2008-02-22 | 업무 흐름 처리 방법 및 장치 |
JP2009554181A JP5012911B2 (ja) | 2008-02-22 | 2008-02-22 | 業務フロー処理プログラム、方法及び装置 |
EP08711854A EP2256677A4 (en) | 2008-02-22 | 2008-02-22 | PROGRAM, METHOD AND DEVICE FOR PROCESSING WORKFLOW |
CN2008801269662A CN101952843A (zh) | 2008-02-22 | 2008-02-22 | 业务流程处理程序、方法和装置 |
US12/849,163 US20100318389A1 (en) | 2008-02-22 | 2010-08-03 | Business flow processing method and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2008/053086 WO2009104276A1 (ja) | 2008-02-22 | 2008-02-22 | 業務フロー処理プログラム、方法及び装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/849,163 Continuation US20100318389A1 (en) | 2008-02-22 | 2010-08-03 | Business flow processing method and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009104276A1 true WO2009104276A1 (ja) | 2009-08-27 |
Family
ID=40985171
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2008/053086 WO2009104276A1 (ja) | 2008-02-22 | 2008-02-22 | 業務フロー処理プログラム、方法及び装置 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20100318389A1 (ja) |
EP (1) | EP2256677A4 (ja) |
JP (1) | JP5012911B2 (ja) |
KR (1) | KR101175475B1 (ja) |
CN (1) | CN101952843A (ja) |
WO (1) | WO2009104276A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110795171A (zh) * | 2019-09-18 | 2020-02-14 | 平安银行股份有限公司 | 业务数据处理方法、装置、计算机设备及存储介质 |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103247007A (zh) * | 2012-07-09 | 2013-08-14 | 中国科学院沈阳自动化研究所 | 一种基于生产事件的生产过程跟踪方法 |
US20140343982A1 (en) * | 2013-05-14 | 2014-11-20 | Landmark Graphics Corporation | Methods and systems related to workflow mentoring |
US20160071043A1 (en) * | 2014-09-04 | 2016-03-10 | International Business Machines Corporation | Enterprise system with interactive visualization |
US11042506B2 (en) * | 2016-07-20 | 2021-06-22 | Microsoft Technology Licensing, Llc | Compliance violation detection |
US11972296B1 (en) * | 2023-05-03 | 2024-04-30 | The Strategic Coach Inc. | Methods and apparatuses for intelligently determining and implementing distinct routines for entities |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050076059A1 (en) | 2003-10-03 | 2005-04-07 | Fujitsu Limited | Apparatus and method for business process tracking and business process tracking program, and recording medium thereof |
JP2006197294A (ja) | 2005-01-14 | 2006-07-27 | Epson Toyocom Corp | 対称インバーター対圧電発振器 |
WO2007132547A1 (ja) * | 2006-05-16 | 2007-11-22 | Fujitsu Limited | 業務モデル生成プログラム、業務モデル生成方法および業務モデル生成装置 |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE69811790T2 (de) * | 1997-08-01 | 2003-11-20 | Ibm | Ableitung von Prozessmodellen aus Rechnungsprüfvorgängen für Systeme zur Verwaltung von Arbeitsflüssen |
US6038538A (en) * | 1997-09-15 | 2000-03-14 | International Business Machines Corporation | Generating process models from workflow logs |
DE19954268B4 (de) * | 1998-12-01 | 2005-07-21 | Ibm Corp. | Verfahren und System zur Verbesserung des Workflow in Workflow-Management-Systemen |
JP3609333B2 (ja) * | 2000-09-29 | 2005-01-12 | 株式会社リコー | 営業管理方法、営業管理システム及び記録媒体 |
US20030065702A1 (en) * | 2001-09-24 | 2003-04-03 | Ravinder Singh | Cache conscious load balancing |
US7562339B2 (en) * | 2002-01-15 | 2009-07-14 | Bea Systems, Inc. | System architecture for business process development and execution with introspection and generic components |
US7398525B2 (en) * | 2002-10-21 | 2008-07-08 | International Business Machines Corporation | Resource scheduling in workflow management systems |
EP1639458A4 (en) * | 2003-06-12 | 2010-05-05 | Reuters America | BUSINESS PROCESS AUTOMATION |
US20070203589A1 (en) * | 2005-04-08 | 2007-08-30 | Manyworlds, Inc. | Adaptive Recombinant Process Methods |
US7712102B2 (en) * | 2004-07-30 | 2010-05-04 | Hewlett-Packard Development Company, L.P. | System and method for dynamically configuring a plurality of load balancers in response to the analyzed performance data |
US8010337B2 (en) * | 2004-09-22 | 2011-08-30 | Microsoft Corporation | Predicting database system performance |
JP4549231B2 (ja) * | 2005-05-17 | 2010-09-22 | 富士通株式会社 | サービス処理状況分析プログラム、サービス処理状況分析方法、およびサービス処理状況分析装置 |
US7739099B2 (en) * | 2005-12-22 | 2010-06-15 | International Business Machines Corporation | Method and system for on-line performance modeling using inference for real production IT systems |
JP5095629B2 (ja) * | 2005-12-28 | 2012-12-12 | テレコム・イタリア・エッセ・ピー・アー | 特に通信ネットワーク介入用としてのワークフローモデルの自動作成方法 |
JP4904878B2 (ja) * | 2006-03-27 | 2012-03-28 | 富士通株式会社 | システム開発支援プログラム、システム開発支援装置およびシステム開発支援方法 |
US20090094074A1 (en) * | 2007-10-04 | 2009-04-09 | Nikovski Daniel N | Method for Constructing Business Process Models from Task Execution Traces |
US7912946B2 (en) * | 2008-01-25 | 2011-03-22 | International Business Machines Corporation | Method using footprints in system log files for monitoring transaction instances in real-time network |
-
2008
- 2008-02-22 EP EP08711854A patent/EP2256677A4/en not_active Withdrawn
- 2008-02-22 JP JP2009554181A patent/JP5012911B2/ja not_active Expired - Fee Related
- 2008-02-22 CN CN2008801269662A patent/CN101952843A/zh active Pending
- 2008-02-22 WO PCT/JP2008/053086 patent/WO2009104276A1/ja active Application Filing
- 2008-02-22 KR KR1020107016492A patent/KR101175475B1/ko not_active IP Right Cessation
-
2010
- 2010-08-03 US US12/849,163 patent/US20100318389A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050076059A1 (en) | 2003-10-03 | 2005-04-07 | Fujitsu Limited | Apparatus and method for business process tracking and business process tracking program, and recording medium thereof |
JP2005115494A (ja) | 2003-10-03 | 2005-04-28 | Fujitsu Ltd | 業務プロセストラッキング装置,業務プロセストラッキング方法,業務プロセストラッキングプログラム,業務プロセストラッキングプログラムを記録した記録媒体 |
JP2006197294A (ja) | 2005-01-14 | 2006-07-27 | Epson Toyocom Corp | 対称インバーター対圧電発振器 |
WO2007132547A1 (ja) * | 2006-05-16 | 2007-11-22 | Fujitsu Limited | 業務モデル生成プログラム、業務モデル生成方法および業務モデル生成装置 |
Non-Patent Citations (4)
Title |
---|
HAVEY MICHAEL: "Shosetsu Business Process Modeling", 2 June 2006, O'REILLY JAPAN, INC., pages: 50 - 58 * |
KATO K.: "Gyomu no Kashika o Okonau BPM Kiban no Shisaku", INFORMATION PROCESSING SOCIETY OF JAPAN KENKYU HOKOKU, vol. 2004, no. 87, 20 August 2004 (2004-08-20), pages 37 - 44, XP008140457 * |
See also references of EP2256677A4 * |
YUMOTO T.: "Scenario Test no Test Sekkei", SOFTWARE ? TEST PRESS, vol. 1, 15 April 2006 (2006-04-15), pages 50 - 54 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110795171A (zh) * | 2019-09-18 | 2020-02-14 | 平安银行股份有限公司 | 业务数据处理方法、装置、计算机设备及存储介质 |
CN110795171B (zh) * | 2019-09-18 | 2023-08-04 | 平安银行股份有限公司 | 业务数据处理方法、装置、计算机设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
KR101175475B1 (ko) | 2012-08-20 |
EP2256677A1 (en) | 2010-12-01 |
JP5012911B2 (ja) | 2012-08-29 |
EP2256677A4 (en) | 2012-12-05 |
US20100318389A1 (en) | 2010-12-16 |
CN101952843A (zh) | 2011-01-19 |
JPWO2009104276A1 (ja) | 2011-06-16 |
KR20100092981A (ko) | 2010-08-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4832523B2 (ja) | 業務プロセス分析のための情報処理方法及び装置 | |
JP3302522B2 (ja) | データベースシステムおよびその情報活用支援装置 | |
US10853387B2 (en) | Data retrieval apparatus, program and recording medium | |
JP4704461B2 (ja) | 業務モデル生成プログラム、業務モデル生成方法および業務モデル生成装置 | |
US20100042745A1 (en) | Workflow diagram generation program, apparatus and method | |
JP5012911B2 (ja) | 業務フロー処理プログラム、方法及び装置 | |
JP2017091329A (ja) | データベース分析装置およびデータベース分析方法 | |
JP5169560B2 (ja) | 業務フロー処理プログラム、方法及び装置 | |
JP4953834B2 (ja) | データ解析方法及びデータ解析システム | |
JP4529861B2 (ja) | 階層データの検索装置および検索方法および検索プログラム | |
JP5246031B2 (ja) | 業務フロー処理プログラム、方法及び装置 | |
JP2003016226A (ja) | 製品市場品質情報解析支援装置、製品市場品質情報解析支援システム及び製品市場品質情報解析支援用プログラム | |
JP2016143106A (ja) | 業務バリエーションに基づく業務影響箇所抽出方法および業務影響箇所抽出装置 | |
JP7411489B2 (ja) | 生産知識管理システム、生産知識管理方法及び生産知識管理プログラム | |
JP2023141268A (ja) | プロセスモデル作成システムおよび方法 | |
EP4068028A1 (en) | Screen generation assisting program, screen generation assisting apparatus, and generation assisting method | |
JP2007334393A (ja) | 部品表データ管理方法およびシステム | |
JP4663526B2 (ja) | 帳票作成支援装置、帳票作成支援方法、および帳票作成支援プログラム | |
JP4181330B2 (ja) | 要約作成プログラム及びシステム並びにコンピュータによる要約作成方法 | |
Dara et al. | A Robust Approach for Data Cleaning used by Decision Tree Induction Method in the Enterprise Data Warehouse‖ | |
JP2006133883A (ja) | プロジェクト管理方法、プロジェクト管理プログラム及びプロジェクト管理装置 | |
JP2004086352A (ja) | テキスト情報分析システム、分析結果の格納方法および提示方法 | |
AU2012202032A1 (en) | A web server, client computing device, computer implemented method and computer readable storage medium for processing intellectual property data | |
JP2007140891A (ja) | データ項目辞書作成方法 | |
JPH0830676A (ja) | 開発実績の自動収集管理装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200880126966.2 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08711854 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2009554181 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20107016492 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008711854 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |