Object-centric data schema for object-based process analysis technique

Abstract

A data structure used for process mining is provided. A method for operating data according to an embodiment of the present invention includes the steps of: assigning an object ID to a generated object and registering the object as a management target when the object which is a work result is generated; acquiring log data for all registered objects; and storing the acquired log data on the basis of the object ID. Accordingly, it is possible to perform analysis without separately obtaining a case ID by loading an object-based log data structure.

Description

Object-centric data schema for object-based process analysis techniques

[0001] The present invention relates to a data structure used in process mining, and more specifically, to a data operation method and system capable of analyzing and managing business processes by analyzing event logs based on objects corresponding to business processes.

[0002] Typically, event log data used in process mining is primarily acquired from log files automatically generated by the system, and case ID, event type information (ACTIVITY), and time information (TIMESTAMP) can be utilized for analysis.

[0003] Here, since the user performs multiple tasks, it is not possible to know which task started and when it ended based on log data alone. Therefore, process analysis usually requires defining a CASE ID to obtain meaningful results.

[0004] Here, the Case ID is a unique number that distinguishes the process and acts as an index that groups and manages a series of processes with a pattern. To configure the Case ID, the defined business process can be recognized or a person can be directly involved and manually record the business process.

[0005] Recently, as ERP systems have become more sophisticated, they have begun to record work logs in detail. However, it is not possible to identify Case IDs with only the raw data of user log files automatically generated by the system. Therefore, business managers and process analysts are maintaining an inefficient method of manually separating processes and deriving patterns to create Case IDs.

[0006] Specifically, as illustrated in FIGS. 1 and 2, in the past, when analyzing user log data, if there is no Case ID, it is not possible to identify it from other business processes, so there is an inconvenience of having to manually separate the process and derive a pattern to create a Case ID.

[0007] The present invention has been devised to solve the above problems, and the purpose of the present invention is to provide a data operation method and system for object-based process analysis technology that enables analysis without separately obtaining a CASE ID for process identification by loading an object-based log data structure instead of existing event-based log data.

[0008] According to one embodiment of the present invention for achieving the above purpose, a data operation method includes: when an object, which is a work result, is created, a step in which the data operation system assigns an object ID to the created object and registers it as a management target; a step in which the data operation system acquires log data for all registered objects; and a step in which the data operation system stores the acquired log data based on the object ID.

[0009] And, when an event occurs for an object, the data operation system can obtain log data of the object and store it based on the object ID along with event type information of the event that occurred for the object, user identification information related to the event that occurred for the object, and information on the time of the event occurrence (Timestamp).

[0010] Additionally, the event type information may be information that can identify whether the event that occurred on the object is among the object's creation (Create), read (Read), update (Update), delete (Delete), and completion (Complete).

[0011] And, according to the present embodiment, the data operation method may further include a step of the data operation system analyzing the business process for each object based on the object ID.

[0012] Additionally, the step of analyzing the business process by object can analyze log data by object based on the object ID to calculate the number of participations by user who participated in creating, viewing, updating, or completing the relevant task.

[0013] And the step of analyzing the business process for each object can be performed by analyzing log data for each object based on the object ID to determine whether a query event for each object occurs repeatedly more than a preset threshold number of times, and selecting an object for which a query event occurs more than the preset threshold number of times as the first object of interest.

[0014] In addition, the step of analyzing the business process for each object can analyze log data for each object based on the object ID to determine whether an update event for each object occurs repeatedly more than a preset threshold number of times, and select an object for which an update event occurs more than the preset threshold number of times as a second object of interest.

[0015] And the step of analyzing the business process by object can analyze the log data by object based on the object ID, and select the object in which no new event occurs for more than the first threshold time set after the most recent event among the objects in which the most recent event is not Delete or Complete as the first process delay object.

[0016] In addition, the step of analyzing the business process for each object can analyze log data for each object based on the object ID, and select objects for which the most recent event is not Delete or Complete, and for which the Delete or Complete event does not occur for a second threshold time or longer from the time of creation, as second process delay objects.

[0017] Meanwhile, according to another embodiment of the present invention, a data operation system includes a processor that, when an object that is a work result is created, assigns an object ID to the created object and registers it as a management target, and acquires log data for all registered objects; and a storage unit that stores the log data acquired based on the object ID.

[0018] And according to another embodiment of the present invention, a data operation method includes a step of a data operation system acquiring log data; and a step of the data operation system storing the acquired log data in a manner identifiable based on an object that is a work result.

[0019] In addition, according to another embodiment of the present invention, the data operation system includes a collection unit that acquires log data; and a processor that stores the acquired log data so that it can be identified based on an object that is a work result.

[0020] As described above, according to embodiments of the present invention, by loading an object-based log data structure instead of existing event-based log data, analysis can be performed without separately obtaining a CASE ID for process identification, thereby reducing manual work time and cost required for process identification.

[0021] Figure 1 is a diagram illustrating how log data is organized by business processor based on Case ID.

[0022] Figure 2 is a drawing illustrating an example of not being able to identify log data by business processor in actual user log data without a Case ID.

[0023] FIG. 3 is a drawing provided for the description of a data operating system according to one embodiment of the present invention;

[0024] FIG. 4 is a drawing provided to explain a data operation method according to one embodiment of the present invention;

[0025] FIG. 5 is a diagram provided for explaining an object-centric data schema according to one embodiment of the present invention;

[0026] FIG. 6 is a diagram provided to explain the configuration of object-based log data according to one embodiment of the present invention;

[0027] FIG. 7 is a diagram provided for the description of object-based log data according to one embodiment of the present invention;

[0028] FIG. 8 is a diagram provided for the description of object-based log data according to one embodiment of the present invention;

[0029] FIG. 9 is a diagram illustrating object-based log data according to one embodiment of the present invention; and

[0030] FIG. 10 is a diagram illustrating an example of object-based log data classified by object according to one embodiment of the present invention.

[0031] Hereinafter, the present invention will be described in more detail with reference to the drawings.

[0032] FIG. 3 is a diagram provided for explaining a data operating system according to one embodiment of the present invention.

[0033] The data operation system according to this embodiment can load an object-based log data structure instead of the existing event-based log data, thereby enabling analysis without separately obtaining a CASE ID for process identification.

[0034] To this end, the data operation system may include a collection unit (110), a processor (120), and a storage unit (130).

[0035] The collection unit (110) is equipped with a communication means and can collect data necessary for the processor (120) to operate.

[0036] For example, the collection unit (110) can obtain log data.

[0037] The storage unit (130) is a storage medium that stores data and programs necessary for the processor (120) to operate.

[0038] The processor (120) is provided to process all matters of the data operation system.

[0039] Specifically, when an object, which is a work result, is created, the processor (120) can register the created object as a management target by assigning an object ID to the data operation system, acquire log data for all registered objects, and store the acquired log data in the storage unit (130) based on the object ID.

[0040] At this time, the processor (120) can obtain and store log data of the object whenever an event occurs for the object.

[0041] Here, the event for the object can be any one of the following: Create, Read, Update, Delete, and Complete.

[0042] And the processor (120) can analyze the business process for each object based on the object ID. Here, the business process may refer to a set of events that occur from the time a certain object is created until it is deleted or completed.

[0043] FIG. 4 is a drawing provided for explaining a data operation method according to one embodiment of the present invention, FIG. 5 is a drawing provided for explaining an object-centric data schema according to one embodiment of the present invention, and FIGS. 6 to 10 are drawings provided for explaining object-based log data according to one embodiment of the present invention.

[0044] The data operation method according to the present embodiment can be executed by the data operation system described above with reference to FIG. 3.

[0045] Specifically, when an object, which is a work product, is created, the data operation system assigns an object ID to the created object and registers it as a management target (S410), and can acquire log data for all registered objects (S420). Here, an object may refer to a work product such as a document or file.

[0046] And the data operation system can store log data acquired based on object ID (S430) and analyze business processes for each object based on object ID (S440).

[0047] Specifically, when an event occurs for an object, the data operation system can obtain log data of the object and store it based on the object ID along with event type information of the event that occurred for the object, user identification information (ID) associated with the event that occurred for the object, and information about the time the event occurred (Timestamp).

[0048] Event type information may be information that can identify whether the event that occurred on an object is among the following: object creation (Create), object search (Read), object update (Update), object deletion (Delete), and object completion (Complete). Here, FIG. 5 is a diagram provided for explaining an object-centric data schema according to one embodiment of the present invention, and FIG. 6 is a diagram illustrating object-based log data.

[0049] Meanwhile, the data operation system can use the object ID instead of the case ID by classifying the business process using the index (object ID) of the log data.

[0050] Specifically, when analyzing the business process of each object based on the object ID, the data operation system can analyze log data of each object based on the object ID to determine which users are actively participating in the work, whether the object is frequently searched, or whether updates occur frequently, and thereby understand the business flow of the object.

[0051] For example, when analyzing a business process for each object, the data operation system can analyze log data for each object based on the object ID, determine whether a query event for each object occurs repeatedly more than a preset threshold number of times, and select an object for which a query event occurs more than the preset threshold number of times as a first object of interest.

[0052] As another example, when analyzing a business process for each object, the data operation system can analyze log data for each object based on the object ID to determine whether an update event for each object occurs repeatedly more than a preset threshold number of times, and select an object for which an update event occurs more than the preset threshold number of times as a second object of interest.

[0053] That is, the data operation system selects a first object of interest or a second object of interest at a preset interval and transmits information about the object to a user participating in the relevant business process or an administrator managing the relevant business process, thereby enabling the system to determine which users are actively participating in the relevant business process, whether the object is frequently searched, or whether updates occur frequently.

[0054] In addition, as another example, when analyzing a business process by object, the data operation system can analyze log data by object based on the object ID, and select an object in which no new event occurs for a preset first threshold time or longer after the most recent event among objects in which the most recent event is not Delete or Complete as a first process delay object.

[0055] And as another example, when analyzing a business process by object, the data operation system can analyze log data by object based on the object ID, and select objects for which the most recent event is not Delete or Complete, and for which a Delete or Complete event does not occur for a second threshold time or longer from the time of creation, as second process delay objects.

[0056] That is, the data operation system selects the first process delay object or the second process delay object at preset intervals, and transmits information about the object to a user participating in the relevant business process or an administrator managing the relevant business process, thereby enabling special management of the object whose process is delayed, or by selecting and analyzing only the objects whose processes are delayed, the data can be used as analysis data when performing other processes.

[0057] In addition, the data operation system can separately select users who manage delayed objects and provide them with the ability to analyze their work status.

[0058] This allows analysis to be performed without having to separately obtain a CASE ID for process identification by loading an object-based log data structure instead of the existing event-based log data, thereby reducing the manual time and cost required for process identification.

[0059] Additionally, by loading log data centered on objects (files, documents) that are actual work results, it can contribute to recognizing the start and end of work, bottlenecks, etc.

[0060] Meanwhile, it goes without saying that the technical idea of ​​the present invention can also be applied to a computer-readable recording medium containing a computer program that performs the functions of the device and method according to the present embodiment. In addition, the technical idea according to various embodiments of the present invention can be implemented in the form of computer-readable code recorded on a computer-readable recording medium. The computer-readable recording medium can be any data storage device that can be read by a computer and store data. For example, the computer-readable recording medium can be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a hard disk drive, etc. In addition, the computer-readable code or program stored on the computer-readable recording medium can be transmitted through a network connected between computers.

[0061] In addition, although the preferred embodiments of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments described above, and various modifications can be made by a person having ordinary skill in the art to which the present invention pertains without departing from the gist of the present invention as claimed in the claims, and such modifications should not be understood individually from the technical idea or prospect of the present invention.

Claims

1. When an object, which is a work result, is created, the data operation system assigns an object ID to the created object and registers it as a management target; The data operation system acquires log data for all registered objects; and A data operation method, comprising: a step of storing log data acquired based on an object ID by a data operation system; 2. In claim 1, The data operating system is, A data operation method characterized in that when an event occurs for an object, log data of the object is acquired and stored based on the object ID along with event type information of the event that occurred for the object, identification information of a user associated with the event that occurred for the object, and information about the time the event occurred (Timestamp).

3. In claim 2, Event type information is: A data operation method characterized by having information that can identify whether an event that occurred in an object is creation, read, update, delete, or completion of the object.

4. In claim 3, A data operation method, characterized in that the data operation system further includes a step of analyzing a business process for each object based on an object ID.

5. In claim 4, The steps to analyze the business process by object are: A data operation method characterized by analyzing log data by object based on object ID and calculating the number of participations by user who participated in creating, searching, updating, or completing the corresponding task.

6. In claim 4, The steps to analyze the business process by object are: A data operation method characterized by analyzing log data for each object based on an object ID, determining whether a query event occurs repeatedly for each object more than a preset threshold number of times, and selecting an object for which a query event occurs more than the preset threshold number of times as a first object of interest.

7. In claim 4, The steps to analyze the business process by object are: A data operation method characterized by analyzing log data for each object based on an object ID, determining whether an update event occurs repeatedly for each object more than a preset threshold number of times, and selecting an object for which an update event occurs more than the preset threshold number of times as a second object of interest.

8. In claim 4, The steps to analyze the business process by object are: A data operation method that analyzes log data by object based on object ID, and selects an object as a first process delay object among objects in which no new events occur for a preset first threshold time after the occurrence of the most recent event, among objects in which the most recent event is not Delete or Complete.

9. In claim 4, The steps to analyze the business process by object are: A data operation method that analyzes log data by object based on object ID, and selects objects for which a Delete or Complete event has not occurred for a preset second threshold time from the time of creation among objects for which the most recent event is not Delete or Complete, as second process delay objects.

10. When an object that is a work result is created, a processor that assigns an object ID to the created object and registers it as a management target, and obtains log data for all registered objects; and A data operation system including a storage unit in which log data acquired based on an object ID is stored.

11. The data operation system acquires log data; and A data operation method, comprising: a step of storing acquired log data in a manner in which the data operation system can identify the obtained log data based on an object that is a work result; 12. A collection unit that obtains log data; and A data operating system including a processor that stores acquired log data in a manner identifiable based on an object that is a work result.

Images