Management program, management method, and management device

Abstract

To easily add a function of managing a history.SOLUTION: A program causes a computer to execute the steps of: extracting, from instruction log data that record operations to monitoring target data to be monitored, data identification information that specifies the monitoring object data; and storing, in a storage unit, the data identification information and history identification information that specifies history data indicating a history of operations to the monitoring object data in association with each other.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a management program, a management method, and a management device. [Background technology]

[0002] In recent years, traceability systems have become known that have the function of tracking the origins of objects and data and the process history. Specifically, for example, a technology is known that dynamically links data items to be collected in each of multiple processes to product traceability information stored in a database. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-59362 Summary of the Invention [Problem to be solved by the invention]

[0004] In the conventional technology described above, when adding the functionality of a traceability system to another system, it is necessary to add a program to the other system to register the results of monitoring the processing of objects and data in the traceability system, which is a heavy burden.

[0005] In one aspect, the present invention aims to easily add a function for managing history. [Means for solving the problem]

[0006] In one aspect, command log data that records operations performed in a first system is acquired from the first system as monitoring target data to be monitored, data identification information that identifies the monitoring target data is extracted, and the data identification information is associated with history identification information that identifies history data that shows the history of operations on the monitoring target data, extracted from the command log data, and the associated data is stored in a storage unit of a second system that cooperates with the first system. extracting updated values ​​in the monitored data from the command log data, generating history data including the updated values, outputting the history data to an external system, accepting input of environmental data defining data items to be included in the history data, storing the environmental data, and extracting the data identification information and the updated values ​​from the command log data based on the environmental data. , cause a computer to execute a process, cause a computer to execute a process. [Effects of the Invention]

[0007] History management functionality can be easily added. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 2 is a diagram illustrating a management device according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of a management apparatus according to the first embodiment. [Figure 3] FIG. 2 is a diagram illustrating functions of a management apparatus according to the first embodiment. [Figure 4] FIG. 4 is a sequence diagram illustrating an operation of a management device according to the first embodiment. [Figure 5] 10 is a flowchart illustrating a process of a history generation unit according to the first embodiment; [Figure 6] FIG. 10 is a first diagram illustrating an example of a table according to the first embodiment. [Figure 7] FIG. 4 is a diagram illustrating an example of environmental data according to the first embodiment; [Figure 8] FIG. 10 is a first diagram illustrating an example of command log data according to the first embodiment. [Figure 9] FIG. 10 is a second diagram illustrating an example of a table according to the first embodiment. [Figure 10] FIG. 2 is a first diagram illustrating history data stored in a history management table according to the first embodiment. [Figure 11] FIG. 10 is a second diagram illustrating an example of command log data according to the first embodiment. [Figure 12] FIG. 10 is a third diagram illustrating an example of a table according to the first embodiment. [Figure 13] FIG. 10 is a second diagram illustrating history data stored in the history management table of the first embodiment. [Figure 14] FIG. 1 illustrates an example of a system configuration of a management system according to a second embodiment. [Figure 15] FIG. 10 is a diagram illustrating a functional configuration of a management apparatus according to a second embodiment. [Figure 16] FIG. 10 is a sequence diagram illustrating an operation of a management system according to a second embodiment. [Figure 17] FIG. 11 is a first diagram illustrating an example of command log data according to the second embodiment. [Figure 18] FIG. 11 is a first diagram illustrating an example of a table according to the second embodiment. [Figure 19] FIG. 11 is a second diagram illustrating an example of a table according to the second embodiment. [Figure 20] FIG. 11 is a first diagram illustrating history data stored in a history management table according to the second embodiment. [Figure 21] FIG. 10 is a diagram illustrating slip information according to the second embodiment. [Figure 22] FIG. 10 is a third diagram illustrating an example of a table according to the second embodiment. [Figure 23] FIG. 11 is a second diagram illustrating an example of command log data according to the second embodiment. [Figure 24] FIG. 10 is a fourth diagram illustrating an example of a table according to the second embodiment. [Figure 25] FIG. 10 is a fifth diagram illustrating an example of a table according to the second embodiment. [Figure 26] FIG. 10 is a second diagram illustrating history data stored in the history management table according to the second embodiment. [Figure 27] FIG. 13 is a diagram illustrating an example of environmental data according to the third embodiment. [Figure 28]FIG. 13 is a diagram illustrating an example of command log data according to the third embodiment. [Figure 29] FIG. 13 is a diagram illustrating an example of a table according to the third embodiment. [Figure 30] FIG. 13 is a diagram illustrating an example of environmental data according to the fourth embodiment. [Figure 31] FIG. 13 is a diagram illustrating an example of command log data according to the fourth embodiment. [Figure 32] FIG. 13 is a fourth diagram illustrating an example of a table according to the fourth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] (First embodiment) The first embodiment will be described below with reference to the drawings: Fig. 1 is a diagram illustrating a management device according to the first embodiment.

[0010] The customer system 100 shown in FIG. 1 is an example of a system into which the history management system 200 is introduced, and is managed by an organization involved in the distribution of goods and data. The customer system 100 is a system for managing goods, data, etc. that are distributed. In the following description, goods, data, etc. that are distributed may be referred to as tracking objects. Tracking objects may be, for example, packages transported by a delivery company.

[0011] In the following description, data indicating the status of the tracking target may be referred to as management data. The management data is stored and managed in a management table or the like of the customer system 100. In other words, the management data is monitoring target data that is the target of monitoring by the management device 300.

[0012] The customer system 100 also outputs various log data in the customer system 100 to a log database 110 for management. The log database 110 may be owned by the customer system 100. The log data includes, for example, access log data indicating access to the customer system 100, command log data indicating commands to the customer system 100, error log data indicating errors in the customer system 100, etc.

[0013] The history management system 200 of this embodiment is a system for tracking the history or location of a tracking object. In other words, the history management system 200 of this embodiment is a traceability system for tracing (tracking) a tracking object.

[0014] The management device 300 of this embodiment has a history ID management database 310 and a history generation unit 320, and links the customer system 100 with the history management system 200. In this embodiment, the number of customer systems 100 linked to the history management system 200 is one.

[0015] Specifically, in this embodiment, the management device 300 is set in advance with environmental data 10 that defines data items to be included in the history data.

[0016] Next, the management device 300 acquires command log data 11 from the log data output from the customer system 100 using the history generation unit 320, and extracts the values ​​of the data items defined by the environmental data 10 from the command log data 11.

[0017] Here, the command log data is command log data that records operations performed on management data (monitored data). In addition, the command log data 11 in this embodiment is, for example, command information such as SQL that indicates operations on a table for management data managed by the customer system 100. In addition, the values ​​of the data items extracted here include data identification information (data ID) that identifies the management data to be tracked and values ​​that have been updated in the management data (updated values).

[0018] In the following description, the data item name and the value of the data item name extracted from the command log data 11 based on the environment data 10 may be referred to as parameters. That is, the parameters in this embodiment include a data ID and an update value.

[0019] Next, the management device 300 stores the data ID in the history ID management database 310 by the history generation unit 320.

[0020] Furthermore, the management device 300 generates history data in which the extracted update value is associated with the data ID, outputs the history data to the history management system 200, and stores the history data in the history management system 200. The history data in this embodiment is data indicating the history of operations (updates) performed on the management data (monitoring target data). The history management system 200 has a history management table etc. for managing the history data, and the history data is stored and managed in the history management table etc. The history management system 200 assigns history identification information (history ID) to the history data for identifying the history data.

[0021] In this embodiment, the management device 300 associates the management data managed by the customer system 100 with the history data stored in the history management system 200. Therefore, according to this embodiment, the customer system 100 can be linked with the history management system 200 without any modification, and a function for managing history can be easily added to the customer system 100.

[0022] The management device 300 of this embodiment will be described below. Fig. 2 is a diagram illustrating the hardware configuration of the management device of the first embodiment.

[0023] The management device 300 of this embodiment is a computer including an input device 31, an output device 32, a drive device 33, an auxiliary storage device 34, a memory device 35, an arithmetic processing device 36, and an interface device 37, all of which are interconnected by a bus B.

[0024] The input device 31 is a device for inputting various types of information and is realized by, for example, a keyboard, a pointing device, etc. The output device 32 is for outputting various types of information and is realized by, for example, a display, etc. The interface device 37 includes a LAN card, etc., and is used for connecting to a network.

[0025] The management program that realizes the history generation unit 320 of the management device 300 is at least a part of various programs that control the management device 300. The management program is provided, for example, by distributing a recording medium 38 or by downloading it from a network. The recording medium 38 on which the management program is recorded can be of various types, including recording media that record information optically, electrically, or magnetically, such as a CD-ROM, flexible disk, or magneto-optical disk, and semiconductor memory that records information electrically, such as a ROM or flash memory.

[0026] When recording medium 38 on which the management program is recorded is set in drive device 33, the management program recorded on recording medium 38 is installed from recording medium 38 into auxiliary storage device 34 via drive device 33. A management program downloaded from the network is installed into auxiliary storage device 34 via interface device 37.

[0027] The auxiliary storage device 34 that realizes the history ID management database 310 stores the management program installed in the management device 300, as well as various files, data, etc. required by the management device 300. The memory device 35 reads and stores the management program from the auxiliary storage device 34 when the management device 300 is started. The arithmetic processing device 36 then realizes various processes, which will be described later, in accordance with the history management program stored in the memory device 35.

[0028] Next, the functions of the management device 300 of this embodiment will be described with reference to Fig. 3. Fig. 3 is a diagram illustrating the functions of the management device of the first embodiment.

[0029] The management device 300 of this embodiment includes a history ID management database 310 and a history generation unit 320 .

[0030] The history ID management database 310 stores ID management data including data IDs and history IDs associated by the history generating unit 320.

[0031] History generation unit 320 generates ID management data and history data. The ID management data is stored in history ID management database 310. The history data is output to history management system 200 and stored in a history management table or the like of history management system 200.

[0032] The history generation unit 320 includes an environment data holding unit 321 , a command log acquisition unit 322 , a data extraction unit 323 , a data generation unit 324 , an ID information registration unit 325 , and a history data output unit 326 .

[0033] The environmental data storage unit 321 stores environmental data 10 input by an administrator or the like of the customer system 100. The environmental data 10 is information that defines data items whose values ​​are to be extracted from the command log data. In other words, the environmental data 10 is information that defines data items to be included in the history data. Details of the environmental data 10 will be described later.

[0034] The command log acquisition unit 322 acquires command log data output from the customer system 100. The command log data acquired here includes command log data other than the command log data for the management data to be monitored.

[0035] The data extraction unit 323 extracts parameters from the command log data based on the command log data acquired by the command log acquisition unit 322 and the environment data 10.

[0036] The data generation unit 324 generates ID management data and history data. Specifically, the data generation unit 324 acquires the data ID of the management data, associates it with a history ID for identifying the history data, and generates the ID management data. Note that the history ID may be assigned by the history management system 200.

[0037] Furthermore, the data generating unit 324 generates history data in which the update values ​​included in the parameters extracted from the command log data are associated with the history IDs.

[0038] The ID information registration unit 325 stores the ID management data generated by the data generation unit 324 in the historical ID management database 310 .

[0039] The history data output unit 326 outputs the history data generated by the data generation unit 324 to the history management system 200.

[0040] Next, the operation of the management device 300 of this embodiment will be described with reference to Fig. 4. Fig. 4 is a sequence diagram illustrating the operation of the management device of the first embodiment.

[0041] In the management device 300 of this embodiment, the history generating unit 320 acquires command log data from the customer system 100 through the command log acquiring unit 322 (steps S401 and S402).

[0042] Next, the history generation unit 320 causes the data extraction unit 323 to compare the environment data 10 with the command log data, and extract parameters from the command log data acquired by the command log acquisition unit 322 (step S403). In other words, the data extraction unit 323 performs pattern matching between the command log data and the environment data 10, and extracts one record corresponding to the environment data 10 from the command log data group acquired in step S402.

[0043] Next, the history generating unit 320 causes the data generating unit 324 to search the history ID management database 310 using the data ID included in the extracted parameters (step S404), and obtains the search results (step S405).

[0044] Next, the data generating unit 324 generates history data in accordance with the search results (step S406). The processing from step S403 to step S406 will be described in detail later.

[0045] Next, the history generation unit 320 outputs the generated history data to the history management system 200 via the history data output unit 326 (step S407), and receives a history ID from the history management system 200 as a notification indicating that the registration of the history data has been completed (step S408).

[0046] Next, the history generating unit 320 causes the data generating unit 324 to generate ID management data that associates the history ID with the data ID, and the ID information registering unit 325 stores the ID management data in the history ID management database 310 (step S409).

[0047] History generating unit 320 receives a response from history ID management database 310 indicating that registration of ID management data has been completed (step S410), and ends the process.

[0048] Through this operation, the management device 300 of this embodiment associates the data ID of the management data managed by the customer system 100 with the history ID of the history data managed by the history management system 200.

[0049] Next, the processing of the history generation unit 320 of this embodiment will be further described with reference to Fig. 5. Fig. 5 is a flowchart illustrating the processing of the history generation unit of the first embodiment. Fig. 5 shows details of the processing from step S403 to step S406 in Fig. 4.

[0050] In the management device 300 of this embodiment, the history generation unit 320 performs pattern matching between the command log data 11 and the environment data 10 using the data extraction unit 323, and extracts parameters that will become part of the history data (step S501).

[0051] Next, the history generation unit 320 searches the history ID management database 310 using the data ID included in the extracted parameters as a key by the data generation unit 324 (step S502). Next, the data generation unit 324 determines whether or not a record including the data ID (ID management data) exists in the history ID management database 310 as a result of the search (step S503).

[0052] In step S503, if a corresponding record exists, the data generation unit 324 obtains the history ID generated in the previous process from the history ID management database 310, generates history data with the history ID of the previous process as the previous history ID (step S504), and proceeds to step S506, which will be described later.

[0053] If there is no corresponding record in step S503, the data generation unit 324 generates new history data to be registered (step S505), and the process proceeds to step S506, which will be described later.

[0054] When the history data is generated, the history generation unit 320 causes the history data output unit 326 to output the generated history data to the history management system 200, where it is registered (stored) (step S506).

[0055] The following is a specific description of the processing performed by history generating unit 320. Fig. 6 is a first diagram showing an example of a table in the first embodiment.

[0056] 6(A) shows an example of a production management table 120 that stores management data for managing tracking objects in the customer system 100. The production management table 120 is an example of various management tables that the customer system 100 has.

[0057] The production management table 120 includes, for example, the following information items: barcode ID, item ID, item name, quantity, and status. The value of the item "barcode ID" is identification information for specifying the tracking object, and corresponds to the data ID in this embodiment. The value of the item "item ID" is identification information for specifying the item of the tracking object, and the value of the item "item name" indicates the item name of the tracking object. The value of the item "quantity" indicates the quantity of the tracking object, and the value of the item "status" indicates the status of the tracking object.

[0058] The history ID management database 310 includes information items such as a data ID and a history ID. The value of the "data ID" item is identification information for identifying the management data of the tracked object, and is extracted from the management data. The value of the "history ID" item is identification information for identifying the history data, and is assigned to the history data generated by the history generation unit 320.

[0059] The history management table 210 includes information items such as a history ID, a previous history ID, and correspondence management data. The value of the "previous history ID" item indicates the history ID generated before the history ID was generated. The value of the "correspondence management data" item indicates an updated value associated with the history ID.

[0060] The example in Figure 6 shows a state in which no management data has been entered in the customer system 100, and no management data for the tracking object is stored in the production management table 120, and no data is stored in either the history ID management database 310 or the history management table 210.

[0061] Fig. 7 is a diagram showing an example of environment data according to the first embodiment. In the example of Fig. 7, a column name and a table name are set as the environment data 10.

[0062] The column name indicates the name of the data item to be tracked. The table name indicates the name of the table that manages the status of the tracking object in the database of the customer system 100.

[0063] In the example of FIG. 7, the column name is "barcode ID" and the table name is "production management table."

[0064] In this embodiment, the environmental data 10 is set by an administrator of the customer system 100. In this embodiment, by having the administrator of the customer system 100 set the environmental data 10, the administrator of the customer system 100 can impose restrictions on the tables that the management device 300 monitors, thereby preventing data unrelated to tracking from being monitored.

[0065] 8 is a first diagram showing an example of command log data according to the first embodiment. The command log data 11 shown in FIG. 8 is a log recording data operations performed on databases and data stores in the customer system 100.

[0066] The command log data 11 shown in FIG. 8 is an example of command log data when the first data manipulation is performed on the production management table 120.

[0067] 8 shows a case where the database held by the customer system 100 is a relational database, and the command log data 11 is acquired in the form of a query log. Also, the command log data 11-1 and 11-2 shown in FIG. 8 indicate that data manipulation has been performed on the "production management table 120" in the customer system 100.

[0068] Figure 9 is a second diagram showing an example of a table in the first embodiment. Management table 120-1 in Figure 9(A) stores two pieces of management data. History ID management database 310-1 in Figure 9(B) stores two pieces of management data and corresponding ID management data. History management table 210-1 in Figure 9(C) stores two pieces of management data and corresponding history data.

[0069] In the history generating unit 320 of this embodiment, when the command log acquiring unit 322 acquires the command log data 11 shown in FIG. 8, the data extracting unit 323 performs pattern matching between the environment data 10 and the command log data 11.

[0070] The data extraction unit 323 of this embodiment sets the following matching conditions based on the environmental data 10, for example.

[0071] [Data update command clause][TABLE name]([COLUMN name],...)][Connection clause]([Data ID],[Update value]) Here, the parameters extracted from the command log data 11 are two points, "data ID" and "update value" in the command log data 11-1 and 11-2 for data operations on the production management table 120-1.

[0072] "Data ID" is the value of the data item specified by the COLUMN name. "Updated value" is the value of a data item other than the COLUMN name, and is a character string of the value set for that data ID. Also, "Updated value" indicates the updated value in the management data in the production management table 120.

[0073] In the example of Figure 9, the value "A1" of the barcode ID in production management table 120-1 is extracted as the data ID, and the data items "item ID," "item name," "quantity," and "status" and the values ​​of each data item, "X1," "product X1," "200," and "production," are extracted as update values.

[0074] Next, the data generation unit 324 searches the history ID management database 310 in the state shown in Fig. 6 using the acquired data ID "A1." Here, since the data ID "A1" does not exist in the history ID management database 310, the result is returned as no corresponding ID, and it is determined to be a newly registered history with no previous history ID.

[0075] Then, the data generation unit 324 generates history data that associates the parameters extracted as update values ​​by the data extraction unit 323. Specifically, the data generation unit 324 generates history data 211 that associates the history ID "T1" with the data items "item ID," "item name," "quantity," and "status," and the values ​​of each data item: "X1," "product X1," "200," and "production."

[0076] The history data output unit 326 registers the history data 211 in the history management system 200. The history management system 200 generates a new history ID "T1", associates it with the history data 211, and stores it in the history management table 210-1. The data generation unit 324 receives the history ID "T1" from the history management system 200 as a notification indicating that the registration of the history data has been completed, and stores ID management data that associates the data ID "A1" with the history ID "T1" in the history ID management database 310-1.

[0077] Similarly, the history generation unit 320 associates the history data 212, which is obtained by extracting parameters from the command log data 11-2, with the history ID "T2" and stores the associated data in the history management table 210-1 of the history management system 200. The history generation unit 320 also stores ID management data, which associates the data ID "A2" with the history ID "T2," in the history ID management database 310-1.

[0078] FIG. 10 is a first diagram illustrating history data stored in the history management table of the first embodiment.

[0079] History data 211 is history data of a tracking object identified by a data ID "A1", and history data 212 is history data of a tracking object identified by a data ID "A2".

[0080] The history data 211 and 212 indicate that management data including the data ID "A1" and management data including the data ID "A2" have been registered in the production management table 120. Therefore, the history data 211 and 212 are not associated with history data indicating the history of data operations prior to these.

[0081] Next, a case will be described in which the status of management data including the data ID "A1" and the status of management data including the data ID "A2" in the production management table 120 are updated from "production" to "shipment."

[0082] 11 is a second diagram showing an example of command log data according to the first embodiment. Command log data 11A shown in FIG. 11 is an example of command log data when a second data operation is performed on the production management table 120.

[0083] Command log data 11-3 shown in FIG. 11 indicates that new management data has been stored, and in command log data 11-1a, the value of the item "status" has been updated from "production" to "shipment."

[0084] The history generating unit 320 extracts parameters from the command log data 11-3 and 11-1a included in the command log data 11A using the data extracting unit 323.

[0085] Figure 12 is a third diagram showing an example of a table in the first embodiment. New management data is stored in management table 120-2 in Figure 12(A). Specifically, in production management table 120-2, the value of the item "status" of management data including barcode ID "A1" has been updated from "production" to "shipment," and new management data including barcode ID "A3" has been stored.

[0086] The historical ID management database 310-2 in FIG. 12(B) stores the new management data and the corresponding ID management data.

[0087] The history management table 210-2 in FIG. 12(C) stores history data corresponding to updates to the production management table 120.

[0088] When the barcode ID "A3" is extracted from the command log data 11-3, the history generation unit 320 searches the history ID management database 310-1 for the barcode ID "A3." Here, there is no ID management data containing the barcode ID "A3" (see FIG. 9).

[0089] Therefore, the history generation unit 320 stores the history data 213 in which the history ID “T3” is associated with the parameter in the history management table 210-1 of the history management system 200.

[0090] Furthermore, the history generating unit 320 extracts parameters from the command log data 11-3, and stores ID management data in which the data ID "A3" and the history ID "T3" are associated with each other in the history ID management database 310-1.

[0091] Furthermore, when the barcode ID "A1" is extracted from the command log data 11-1a, the history generation unit 320 searches the history ID management database 310-1 for the barcode ID "A1." Here, ID management data including the barcode ID "A1" exists.

[0092] Therefore, the history generation unit 320 acquires the history ID "T1" associated with the barcode ID "A1" in the history ID management database 310-1 as the "previous history ID." The history generation unit 320 then generates history data 214 that associates the parameters extracted from the command log data 11-1a, the "previous history ID," and the new history ID "T4," and stores the data in the history management table 210-1.

[0093] Furthermore, the history generating unit 320 updates the history ID from "T1" to "T4" in the ID management data that includes the barcode ID "A1" and is stored in the history ID management database 310-1.

[0094] The history ID management database 310-2 and history management table 210-2 show the state after these processes have been performed.

[0095] FIG. 13 is a second diagram illustrating the history data stored in the history management table of the first embodiment.

[0096] The history data 214 is history data of the tracked object identified by the data ID "A1." This history data 214 includes, as a previous history ID, the history ID "T1" of the history data 211 generated immediately before the history data 214 was generated.

[0097] That is, the history data 214 is associated with history data of operations performed in the past on management data including the data ID "A1." Therefore, in the example of Fig. 13, it is possible to trace past history data with history ID "T1" from the latest history data corresponding to the data ID "A1."

[0098] Furthermore, the history data 213 indicates that management data including the data ID "A3" has been registered in the production management table 120-2. Therefore, the history data 213 is not associated with history data indicating the history of data operations prior to this.

[0099] In this embodiment, a data ID that identifies the tracking target and a parameter that indicates the content of the data operation on the management data that includes this data ID are extracted from the command log data output from the customer system 100. Also, in this embodiment, a history ID that is associated with the parameter is generated and associated with the data ID.

[0100] In this embodiment, history data in which the parameters and the history IDs are associated with each other is generated and output to the history management system 200.

[0101] Furthermore, in this embodiment, when generating history data, a search is performed on the history management table 210 to determine whether history data corresponding to the same data ID has been generated in the past. If history data corresponding to the same data ID has been generated in the past, the history ID of the previously generated history data is included as a previous history ID in the history data to be generated.

[0102] Therefore, in this embodiment, it is possible to trace (track) past history data from the latest history data of the tracking object.

[0103] Therefore, according to this embodiment, it is possible to associate the management data managed by the customer system 100 with the history data managed by the history management system 200 without making any changes to the customer system 100. In other words, according to this embodiment, it is possible to manage the history of tracked objects without changing the existing customer system 100.

[0104] (Second embodiment) The second embodiment will be described below with reference to the drawings. The second embodiment differs from the first embodiment in that the history management system 200 is linked to multiple customer systems 100. In the following description of the second embodiment, differences from the first embodiment will be described, and components having the same functional configuration as those in the first embodiment will be assigned the same reference numerals as those used in the description of the first embodiment, and their description will be omitted.

[0105] 14 is a diagram illustrating an example of the system configuration of a management system according to the second embodiment. The management system 400 of this embodiment includes management devices 300A-1 and 300A-2. The management system 400 of this embodiment also links the customer system 100A and the customer system 100B with the history management system 200.

[0106] In this embodiment, we will explain a case where, for example, a tracked item (package) is stored in an organization where customer system 100A has been introduced (e.g., a package collection point), and then moved to an organization where customer system 100B has been introduced (e.g., a package delivery point), and managed by customer system 100B.

[0107] In the management system 400, the management device 300A-1 links the customer system 100A with the history management system 200, and the management device 300A-2 links the customer system 100B with the history management system 200. In the following description, when there is no need to distinguish between the management devices 300A-1 and 300A-2, they will simply be referred to as the management device 300A.

[0108] The management device 300A of this embodiment includes a history ID management database 310, a history generation unit 320, and an ID linking unit 330.

[0109] The ID linking unit 330 of this embodiment associates the data ID of the management data acquired in the other management device 300A with the data ID of the management data acquired in its own device.

[0110] Specifically, for example, the ID association unit 330 of the management device 300A-2 associates the data ID extracted from the command log data acquired by the management device 300A-1 from the customer system 100A with the data ID extracted from the command log data acquired by the management device 300A-1 from the customer system 100B.

[0111] 15 is a diagram illustrating the functional configuration of a management device according to the second embodiment. The management device 300A according to this embodiment includes a history ID management database 310, a history generation unit 320, and an ID linking unit 330.

[0112] The ID linking unit 330 of this embodiment includes a history ID search unit 331 and an ID information registration unit 332.

[0113] The history ID search unit 331 searches the history management table 210 of the history management system 200 using the data ID acquired in the other management device 300A.

[0114] The ID information registration unit 332 associates the history ID acquired as a search result of the history ID search unit 331 with the data ID acquired by its own device, and stores the result in the history ID management database 310.

[0115] Next, the operation of the management system 400 of this embodiment will be described with reference to Fig. 16. Fig. 16 is a sequence diagram illustrating the operation of the management system of the second embodiment.

[0116] 16 shows the operation after management data for tracking a tracking target is stored in the management device 300A-1 through processing similar to that shown in FIG. 6 of the first embodiment.

[0117] 16 is executed, the history ID management database 310-1 stores ID management data in which a data ID that identifies the management data to be tracked is associated with a history ID. The history management table 210 of the history management system 200 also stores history data including a history ID associated with a data ID that identifies the management data to be tracked.

[0118] 16, the tracking target is assumed to be a package, the organization that has implemented customer system 100A is assumed to be a collection point, and the organization that has implemented customer system 100B is assumed to be a delivery point. Also, in FIG. 16, the barcode ID read from the barcode shown on the slip attached to the package is assumed to be the data ID that identifies the management data to be tracked.

[0119] In this embodiment, when a package is moved from a collection point to a delivery point (steps S1601 and S1602), the barcode ID is transferred from customer system 100A to customer system 100B.

[0120] Specifically, for example, when a barcode printed on a slip attached to a package is read at a delivery station where the customer system 100B is installed, the barcode ID is transmitted to the customer system 100B.

[0121] At this time, customer system 100B may obtain slip information from customer system 100A, which includes a barcode ID and a data ID assigned by customer system 100A. The slip information may be information indicating that the barcode ID in customer system 100A and the barcode ID in customer system 100B have the same value. Details of the slip information will be described later.

[0122] Here, the data ID systems are different between the customer system 100A and the customer system 100B. Therefore, the management device 300A-2 of this embodiment uses the ID linking unit 330-2 to replace the data ID associated with the barcode ID in the customer system 100A with the data ID used in the customer system 100B.

[0123] Specifically, the ID linking unit 330-2 of the management device 300A-2 acquires slip information from the customer system 100B (steps S1603 and S1604). Next, the ID linking unit 330-2 acquires the barcode ID included in the slip information via the history ID search unit 331 (step S1605).

[0124] In this embodiment, the barcode ID is the data ID in the customer system 100A. Therefore, the ID linking unit 330-2 causes the history ID search unit 331 to search the history management table 210 of the history management system 200 using this data ID (barcode ID) (step S1606).

[0125] At this time, the management device 300A has stored history data corresponding to the data ID in the history management table 210. Therefore, the history ID search unit 331 acquires the history ID associated with the data ID as the search result (step S1607).

[0126] Next, the ID association unit 330-2 stores ID management data that associates the acquired history ID with the data ID assigned in the customer system 100B in the history ID management database 310-2 using the ID information registration unit 332 (step S1608), and completes the registration (step S1609).

[0127] Subsequently, management device 300A-2 generates history data using history generation unit 320-2. The processes from step S1610 to step S1619 in Fig. 16 are the same as the processes from step S401 to step S410 in Fig. 4, and therefore description thereof will be omitted.

[0128] The operation of the management system 400 of this embodiment will be further described below. Fig. 17 is a first diagram showing an example of command log data of the second embodiment.

[0129] The command log data 11A shown in FIG. 17 is an example of command log data output from the customer system 100A when management data for tracking a tracking object is stored in the production management table 120A of the customer system 100A.

[0130] In the management device 300A-1 of this embodiment, the command log acquisition unit 322 of the history generation unit 320-1 acquires this command log data 11A, and the data extraction unit 323 extracts the data ID and parameters.

[0131] FIG. 18 is a first diagram showing an example of a table in the second embodiment, and FIG. 19 is a second diagram showing an example of a table in the second embodiment.

[0132] The production management table 120A-1 shown in Fig. 18(A), the history ID management database 310-1A shown in Fig. 18(B), and the history management table 210A shown in Fig. 19 show the state of each table before the process shown in Fig. 16 is started. In other words, the tables shown in Fig. 18 and Fig. 19 show the state of each table before the barcode ID is transferred to the customer system 100B.

[0133] The production management table 120A-1 shown in Fig. 18(A) stores management data for tracking a tracking object. The barcode ID included in this management data is "A1" and the status is "production." When this management data is stored in the production management table 120A, the customer system 100A outputs the command log data 11A shown in Fig. 17.

[0134] The history generation unit 320 of the management device 300A-1 acquires the command log data 11A output from the customer system 100A. Then, the history generation unit 320 extracts the barcode ID "A1" as a data ID from the command log data 11A, and stores the ID management data associated with the history ID "T1" in the history ID management database 310-1.

[0135] In the history ID management database 310-1A shown in FIG. 18(B), the barcode ID "A1" is used as the data ID and ID management data associated with the history ID "T1" is stored.

[0136] Furthermore, the management device 300A-1 stores in the history management table 210 history data 215 that associates the parameters extracted from the command log data 11A with the history ID "T1."

[0137] 19 stores history data 215. Note that the history data 215 in this embodiment includes a barcode ID.

[0138] FIG. 20 is a first diagram illustrating history data stored in the history management table of the second embodiment.

[0139] The history data 215 generated by the management device 300A-1 is history data indicating that new management data identified by the data ID "A1" has been stored in the production management table 120A, and therefore does not include a previous history ID.

[0140] Here, the slip information will be described with reference to Fig. 21. Fig. 21 is a diagram illustrating the slip information of the second embodiment.

[0141] The slip information 201 shown in FIG. 21 indicates the association between the data ID in the customer system 100A and the data ID in the customer system 100B.

[0142] Specifically, in this embodiment, the barcode ID in the customer system 100A is set as a data ID "A1", and the barcode ID after receipt in the customer system 100B is set as a data ID "B1".

[0143] Here, the barcode ID is an unchanging value indicated by the barcode printed on the slip attached to the package. Therefore, slip information 201 indicates that data ID "A1" in customer system 100A and data ID "B1" in customer system 100B are the same barcode ID.

[0144] Fig. 22 is a third diagram showing an example of a table in the second embodiment. Fig. 22 shows the state of the production management table 120B and the history ID management database 310-2 after the ID linking unit 330-2 replaces the data IDs. In other words, Fig. 22 shows the state of the production management table 120B and the history ID management database 310-2 when the processing from step S1601 to step S1609 in Fig. 16 is completed.

[0145] The production management table 120B-1 shown in FIG. 22(A) is empty because no management data has yet been stored in the customer system 100B.

[0146] The historical ID management database 310-2A shown in FIG. 22(B) stores ID management data in which the data ID associated with the historical ID "T1" in the customer system 100B has been replaced with "B1."

[0147] This command log data 11B is acquired by the command log acquisition unit 322 of the history generation unit 320-2 in steps S1610 and S1611 of FIG.

[0148] FIG. 24 is a fourth diagram showing an example of a table in the second embodiment, and FIG. 25 is a fifth diagram showing an example of a table in the second embodiment.

[0149] 24 and 25 show the state after the management device 300A-2 stores history data in the history management system 200. In other words, the tables shown in Fig. 24 and 25 show the state after the processing from step S1612 to step S1619 in Fig. 16 has been completed.

[0150] 24(A) stores management data for barcode ID "B1" and management data for barcode ID "B2." The status of the management data containing barcode ID "B1" has been updated from "production" to "arrival."

[0151] The management device 300A-2 first obtains the barcode ID "B1" and the updated value from the command log data 11B-1 using the data extraction unit 323 of the history generation unit 320-2.

[0152] Here, the barcode ID "B1" is acquired as the data ID "B1." Note that the data ID "B1" indicates the same barcode ID as the data ID "A1" in the customer system 100A. In other words, the data ID "B1" and the data ID "A1" have the same value.

[0153] Next, the history generation unit 320 searches the history ID management database 310-2A for the data ID "B1." Here, since the data ID "B1" has the same value as the data ID "A1," the history generation unit 320 obtains the history ID "T1" as the search result (see FIG. 22).

[0154] Next, history generation unit 320-2 sets history ID "T1" as the previous history ID, associates it with the update value extracted from command log data 11B-1, and generates history data with a new history ID "T2." History generation unit 320-2 then stores history data 216 with history ID "T2" in history management table 210.

[0155] Furthermore, the history generation unit 320 of the management device 300A-2 first obtains the barcode ID "B2" and the updated value from the command log data 11B-2 using the data extraction unit 323 of the history generation unit 320-2.

[0156] Here, the management data with the data ID "B2" is management data that has been newly added to the customer system 100B, and does not exist in the historical ID management database 310-2.

[0157] Therefore, the history generation unit 320-2 generates a new history ID "T3" and generates history data 217 that is associated with the updated value extracted from the command log data 11B-2, and stores the history data 217 in the history management table 210.

[0158] In the history management table 210B shown in FIG. 25(B), history data 216 and history data 217 generated by the management device 300A-2 are stored.

[0159] FIG. 26 is a second diagram illustrating the history data stored in the history management table according to the second embodiment.

[0160] In the history management table 210B, the history data "T1" that identifies the history data 215 is included in the history data 216 as the previous history data of the history data 216. Therefore, in this embodiment, the history data 215 and the history data 216 can be associated with each other.

[0161] Moreover, since the history data 217 is history data indicating that new management data has been stored, it does not include a previous history ID.

[0162] In this way, in this embodiment, even if a tracking object is managed by multiple customer systems 100 with different data ID systems, the data IDs used in each customer system 100 can be linked together.

[0163] In addition, in this embodiment, the tracking object is managed by two customer systems 100, but this is not limiting. The tracking object may be managed by three or more customer systems 100. In this case, data exchange between the two customer systems 100 occurs at multiple locations.

[0164] In this embodiment, the history generation unit 320 and the ID linking unit 330 are configured as separate functional components, but this is not limiting. The history generation unit 320 and the ID linking unit 330 may be realized as a single functional unit. In other words, the history generation unit 320 and the ID linking unit 330 may be integrated as a program.

[0165] (Third embodiment) A third embodiment will be described below with reference to the drawings. The third embodiment differs from the first and second embodiments in that the format of the update value to be included in the history data is set. Therefore, in the following description of the third embodiment, differences from the first embodiment will be described, and components having the same functional configuration as those in the first embodiment will be assigned the same reference numerals as those used in the description of the first embodiment, and their description will be omitted.

[0166] Fig. 27 is a diagram showing an example of environment data according to the third embodiment. In the environment data 30 shown in Fig. 27, in addition to the data ID and table name, the correspondence between the update value and the history data item and the format of the history data are defined.

[0167] Fig. 28 is a diagram showing an example of command log data according to the third embodiment. Command log data 11C shown in Fig. 28 indicates command log data output from the customer system 100A when management data with data ID "A1" and management data with data ID "A2" are stored in the production management table 120A of the customer system 100A.

[0168] In this embodiment, history data is generated that indicates the updated values ​​output from this command log data 11C in a format defined by the environment data 30.

[0169] Fig. 29 is a diagram showing an example of a table in the third embodiment. The production management table 120A-2 shown in Fig. 29(A) shows a state in which management data of data ID "A1" and management data of data ID "A2" are stored.

[0170] The history ID management database 310-1B shown in Figure 29(B) shows a state in which ID management data is stored in which history ID "T1" and history ID "T2" are associated with data ID "A1" and data ID "A2" extracted from command log data 11C, respectively.

[0171] A history management table 210C shown in FIG. 29(C) shows a state in which history data including update values ​​extracted from the command log data 11C is stored.

[0172] In the example of FIG. 29(C), the updated value is stored in a format defined by the environment data 30. Specifically, for example, in the history data including the history ID "T1", the updated value is stored as a natural language sentence such as "200 units of product X1 have been produced."

[0173] In this way, in this embodiment, it is possible to generate history data in a format specified by the administrator of the customer system 100. Therefore, in this embodiment, it is possible to register history data in any format in the history management system 200 without modifying the customer system 100.

[0174] (Fourth embodiment) A fourth embodiment will be described below with reference to the drawings. The fourth embodiment differs from the first embodiment in that a table format is set for the environmental data. Therefore, in the following description of the fourth embodiment, differences from the first embodiment will be described, and components having the same functional configuration as those in the first embodiment will be assigned the same reference numerals as those used in the description of the first embodiment, and their description will be omitted.

[0175] Fig. 30 is a diagram showing an example of environmental data according to the fourth embodiment. In the environmental data 10A shown in Fig. 30, in addition to a data ID and a table name, the data structure of the table identified by the table name is defined. Specifically, the data structure of the table is the data item names included in the table and the order in which the data item names are arranged.

[0176] In the example of Figure 30, since the "barcode ID" which will be the data ID is the first in "TABLE_FORMAT", the first value of the table identified by the table name is extracted as the data ID, and the values ​​thereafter are treated as update values ​​(counting from the left).

[0177] Fig. 31 is a diagram showing an example of command log data according to the fourth embodiment. The command log data 11D shown in Fig. 31 indicates command log data output from the customer system 100A when management data with data ID "A1" and management data with data ID "A2" are stored in the production management table 120A of the customer system 100A.

[0178] In this embodiment, history data is generated from this command log data 11D, with the first value "A1" of the values ​​of the items defined in the environment data 10A as the data ID and the other values ​​as update values.

[0179] Fig. 32 is a fourth diagram showing an example of a table in the fourth embodiment. The production management table 120A-3 shown in Fig. 32(A) shows a state in which management data of data ID "A1" and management data of data ID "A2" are stored.

[0180] The history ID management database 310-1B shown in Figure 32(B) shows a state in which ID management data is stored in which history ID "T1" and history ID "T2" are associated with data ID "A1" and data ID "A2" extracted from command log data 11D, respectively.

[0181] A history management table 210D shown in FIG. 32(C) shows a state in which history data including update values ​​extracted from the command log data 11D is stored.

[0182] 32(C), the updated values ​​of the history data include items and item values ​​other than the barcode ID among the values ​​of the identified items defined in the environment data 10A. Specifically, for example, in the history data including the history ID "T1", the updated values ​​are "Item ID: X1," Item ID: Product X1, Quantity: 200, Status: Production."

[0183] In this way, in this embodiment, it is possible to generate history data by simply setting the items included in the table to be monitored, without having to specify the names of the items to be updated in the environmental data. Therefore, in this embodiment, environmental data can be easily set.

[0184] The disclosed technology may take the following forms as described below. (Appendix 1) extracting data identification information for identifying the monitoring target data from command log data that records operations on the monitoring target data; the data identification information and history identification information for identifying history data indicating a history of operations on the monitoring target data are stored in a storage unit in association with each other; A management program that causes a computer to execute a process. (Appendix 2) extracting an updated value in the monitoring target data from the command log data; generating historical data including the updated values; 2. The management program according to claim 1, which causes the computer to execute a process of outputting the history data to an external system. (Appendix 3) The storage unit is searched using the data identification information, and when history identification information corresponding to the data identification information is obtained, the history data is stored in the storage unit as history data in which the acquired history identification information and the updated value are associated with each other. (Appendix 4) Accepting input of environmental data that defines data items to be included in the history data, and storing the environmental data; 4. The management program according to claim 2, further comprising: extracting the data identification information and the updated value from the command log data based on the environmental data. (Appendix 5) In the environmental data, 5. The management program according to claim 4, wherein a correspondence between the updated value and a data item included in the history data, and a format of the history data are defined. (Appendix 6) In the environmental data, 5. The management program according to claim 4, wherein the data structure of a table in which the monitoring target data is stored is defined. (Appendix 7) A management method by a computer, the computer comprising: extracting data identification information for identifying the monitoring target data from command log data that records operations on the monitoring target data; The management method includes storing the data identification information and history identification information that identifies history data indicating a history of operations on the monitoring target data in a storage unit in association with each other. (Appendix 8) a data extraction unit that extracts data identification information that identifies the monitoring target data from command log data that records operations on the monitoring target data; a registration unit that associates the data identification information with history identification information that identifies history data that indicates a history of operations on the monitoring target data and stores the data identification information in a storage unit. The invention is not limited to the specifically disclosed embodiments, but various modifications and variations are possible without departing from the scope of the appended claims. [Explanation of symbols]

[0185] 100 Customer System 200 History Management System 300, 300A management device 310 Historical ID Management Database 320 History Generation Unit 321 Environmental Data Storage Unit 322 Command Log Acquisition Unit 323 Data Extraction Unit 324 Data Generation Unit 325, 332 ID Information Registration Department 326 History data output unit 330 ID Linkage Department 331 History ID Search Unit

Claims

1. Obtaining command log data from the first system, the command log data being the monitoring target data and recording operations performed in the first system; extracting data identification information that identifies the monitoring target data; the data identification information and history identification information that identifies history data indicating a history of operations on the monitoring target data, extracted from the command log data, are associated with each other and stored in a storage unit of a second system that is linked to the first system; extracting an updated value in the monitoring target data from the command log data; generating historical data including the updated values; outputting the history data to an external system; Accepting input of environmental data that defines data items to be included in the history data, and storing the environmental data; A management program that causes a computer to execute a process of extracting the data identification information and the update value from the command log data based on the environmental data.

2. The storage unit is searched using the data identification information, and when history identification information corresponding to the data identification information is obtained, 2. The management program according to claim 1, wherein the history data is stored in the storage unit as history data in which the acquired history identification information and the updated value are associated with each other.

3. A management method by a computer, the computer comprising: Obtaining command log data from the first system that records operations performed in the first system on the monitoring target data to be monitored; extracting data identification information that identifies the monitoring target data; the data identification information and history identification information that identifies history data indicating a history of operations on the monitoring target data, extracted from the command log data, are associated with each other and stored in a storage unit of a second system that is linked to the first system; extracting an updated value in the monitoring target data from the command log data; generating historical data including the updated values; outputting the history data to an external system; Accepting input of environmental data that defines data items to be included in the history data, and storing the environmental data; A management method comprising: extracting the data identification information and the update value from the command log data based on the environment data.

4. an acquisition unit that acquires, from the first system, command log data that records operations performed in the first system with respect to the monitoring target data that is a monitoring target; a data extraction unit that extracts data identification information that identifies the monitoring target data; a registration unit that associates the data identification information with history identification information that identifies history data that indicates a history of operations on the monitoring target data, extracted from the command log data, and stores the associated data in a storage unit included in a second system that is linked to the first system; a data generating unit that extracts updated values ​​in the monitoring target data from the command log data and generates history data including the updated values; a history data output unit that outputs the history data to an external system; A management device having a history generation unit that accepts input of environmental data that defines data items to be included in the history data, stores the environmental data, and extracts the data identification information and the update value from the command log data based on the environmental data.

Images