JP7844286B2 - Information systems and information management methods - Google Patents

Description

This invention relates to an information system and an information management method.

In various industries, such as manufacturing and service industries, products and services are provided by carrying out numerous tasks as a series of workflows. For example, in manufacturing plants or offices, each task that constitutes a business process generates on-site data upon completion of the task or the occurrence of a predetermined event, and this on-site data is collected. On-site workers and data analysts analyze this collected on-site data to improve the efficiency of each task.

On the other hand, when different departments manage different tasks, information sharing between departments becomes difficult, and problems related to information sharing across departments or tasks remain unresolved.

Each department analyzes collected field data to improve the efficiency of its internal operations. However, collaboration between departments is essential for improving the efficiency of the entire business process. Therefore, it is necessary to manage field data generated not only within departments but also throughout the entire business process, linking them together and using this data analysis to improve the efficiency of the entire process.

Patent Document 1 discloses an information collection and display system in which a data generation device for generating field data and a storage device for storing the field data generated by the data generation device are connected. The information collection and display system includes a relationship data storage unit that stores relationship data defining the relationships between multiple pieces of information included in the field data; a relationship data search unit that searches for second information related to a first piece of information included in the multiple pieces of information based on the relationship data stored in the relationship data storage unit; and a user interface unit that displays the connection relationships of the multiple pieces of information linked by the relationship data. The relationship data search unit searches for second information related to the first piece of information based on the relationship data, according to the selection of the first piece of information in the connection relationships of the multiple pieces of information displayed in the user interface unit, and displays the first and second pieces of information, along with the connection relationships of the multiple pieces of information, in the user interface unit.

Japanese Patent Publication No. 2019-153051

The information collection system disclosed in Patent Document 1 has a relevance data model that shows the relationship between business operations and information related to those operations. This information collection system facilitates the analysis of field data by structuring the information contained in field data based on the structure defined in the relevance data model, and by accumulating and managing it as relevance data.

On the other hand, on-site work processes may change with the aim of improving productivity and operational efficiency. Furthermore, with the diversification of needs, the demand for small-batch, high-mix production is increasing. However, in small-batch, high-mix production, the sequence of operations and the resources used may differ depending on the product or product specifications.

The information gathering system disclosed in Patent Document 1 requires pre-defining all possible combinations of business sequence and the relationship between business and the resources used for those business as a relational data model. Therefore, the effort required to define the relational data model may be significant. Furthermore, as mentioned above, whenever a change occurs in the business process, or when a new product or product specification requires a new business sequence or resources, the relational data model must be updated each time. Consequently, the effort required for managing and operating the data model may be significant. Alternatively, if the relational data model is not updated despite changes in field data resulting from these changes, the accumulation and management of relational data may not be sustainable, potentially requiring identification of the cause and countermeasures.

This invention was made in view of the above-mentioned problems and aims to flexibly respond to changes in business processes.

To achieve the above objective, the present invention provides an information system comprising at least one processor and at least one memory, wherein the processor, by executing a predetermined computer program stored in the memory, receives input data including a plurality of tasks and information relating to at least one of the plurality of tasks, and generates relationship data indicating the relationships between the plurality of tasks and the relationships between the plurality of tasks and the resources relating to at least one of the plurality of tasks based on the received input data; and implements a relationship data storage unit that stores the relationship data generated by the relationship data registration unit.

According to this invention, it becomes possible to flexibly respond to changes in business processes.

System configuration diagram of the information system according to the first embodiment. A block diagram showing a functional configuration example of the information system according to the first embodiment. A diagram showing an example of the data structure of relational data according to the first embodiment. This figure shows an example of field data management information from the model data according to the first embodiment. A diagram showing an example of the business and 4M components of the model data according to the first embodiment. A diagram showing an example of input data according to the first embodiment. A diagram showing an example of the operation procedure for registering input data according to the first embodiment. A diagram showing an example of the procedure for generating and registering relevance data according to the first embodiment. A diagram showing an example of the procedure for generating and registering relevance data according to the first embodiment. A diagram showing a specific example of the procedure for generating and registering relevance data according to the first embodiment. A diagram showing a specific example of relevance data according to the first embodiment. A diagram showing a specific example of the procedure for generating and registering relevance data according to the second embodiment. A diagram showing an example of the procedure for generating and registering relevance data according to the second embodiment. A diagram showing an example of the analysis of the business structure of the related data and process chart in the third embodiment. A diagram showing another example of the analysis of the business structure of the related data and process chart in the third embodiment. A diagram showing a specific example of the procedure for generating and registering relational data according to the fourth embodiment.

The following describes embodiments of the information system and information management method according to the present invention with reference to the drawings. Note that the embodiments described below are not intended to limit the invention as defined in the claims, and not all of the elements and combinations described in the embodiments are necessarily essential to the solution of the invention.

Figure 1 is a system diagram of the information system according to the first embodiment.

In Figure 1, information system 1 is connected to network 2. Network 2 is connected to multiple data generators 6a, 6b, and 6c (hereinafter, when data generators 6a, 6b, and 6c are not specifically distinguished, they will simply be referred to as data generator 6) that collect or generate field data corresponding to records of work execution. Furthermore, network 2 is connected to a model data storage unit 3, a related data storage unit 4, and a field data storage unit 5. These data generators 6, model data storage unit 3, related data storage unit 4, and field data storage unit 5 are all connected to information system 1 via network 2.

The data generation device 6 may be, for example, a barcode reader that acquires worker work logs, a PC (Personal Computer) or server (e.g., data generation device 6a) that collects work logs. Furthermore, the data generation device 6 may be equipment or machinery that processes parts or assembles finished products (e.g., data generation device 6b). Furthermore, the data generation device 6 may be a sensor (e.g., data generation device 6c) that collects RFID (Radio Frequency Identifier) information attached to parts or finished products. The field data collected or generated by these data generation devices 6 is transmitted via the network 2 to the information system 1 or the field data storage unit 5.

The model data storage unit 3 is, for example, a storage device such as a server or memory. The model data storage unit 3 stores information for accessing information related to business operations and resources related to those operations, which are stored in the field data storage unit 5, as well as model data that defines the structure of the data stored in the relevance data storage unit 4.

The relevance data storage unit 4 is, for example, a storage device such as a server or memory, and stores information about business operations, information related to those operations, and information about their relationships. The relevance data storage unit 4 also stores key information for acquiring data about business operations and related information from the field data storage unit 5.

The field data storage unit 5 is, for example, a storage device such as a server or memory, and stores the field data generated by the data generation device 6.

Information System 1 is a PC or server, etc. Information System 1 comprises a Central Processing Unit (CPU), Read Only Memory (ROM), Random Access Memory (RAM), and a Hard Disk Drive (HDD). The CPU performs overall control of Information System 1. ROM stores control programs that control Information System 1. RAM temporarily stores information processed by the CPU. The following functions are realized when the CPU executes the control programs stored in ROM.

Figure 2 is a block diagram showing a functional configuration example of the information system according to the first embodiment.

The information system 1 comprises at least one processor 10-1 and at least one memory 10-2. The processor 10-1 reads and executes a predetermined computer program stored in the memory 10-2, thereby realizing the functions described later. The storage medium MM for non-temporarily storing the computer program is composed of, for example, flash memory or a hard disk drive. The storage medium MM is connected to the information system 1 and can send and receive computer programs to and from the memory 10-2.

Information System 1 comprises a relationship data registration unit 11, a model creation unit 12, a model management interface 13, a provided data generation unit 14, a data provision interface 15 (as an example of an "interface"), a model data storage unit 3, and a relationship data storage unit 4. In Figure 1, Information System 1, the model data storage unit 3, and the relationship data storage unit 4 are connected via a network 2. However, as shown in Figure 2, these may be different functional blocks within the same device. Furthermore, each of these functions may be configured by a different PC or server, or each may be configured by one or more containers.

The relationship data registration unit 11 receives input data from the data registration device 7. Based on the model data managed by the model data storage unit 3 and the received input data, the relationship data indicates the relationships between business processes and the relationships between business processes and related resources. The relationship data shows the relationships between business processes and related resources and the information stored in the field data storage unit 5. The relationship data registration unit 11 registers the generated relationship data in the relationship data storage unit 4. Here, the relationship data registration unit 11 includes an API (Application Programming Interface) which is an interface for the data registration device 7 to register input data.

The model creation unit 12 creates model data, including components of business operations and related information input from the model management interface 13, and access information to the field data storage unit 5. It then registers the created components and model data in the model data storage unit 3. Furthermore, it provides the model data registered in the model data storage unit 3 to the model management interface 13.

The model management interface 13 displays to the user via the operation terminal 8 the input environment for information stored in the model data storage unit 3 via the model creation unit 12, and the stored model data. Here, the model management interface 13 may be a GUI (Graphical User Interface) that provides information input and display screens to the operation terminal 8, or it may be an API that exchanges information based on a predetermined data structure.

The data generation unit 14 acquires related data regarding associated tasks and related resources from the related data storage unit 4 based on the conditions specified in the data provision interface 15. Based on the acquired related data and access information to the field data stored in the model data storage unit 3, the data generation unit 14 acquires field data from the field data storage unit 5 and transmits the data to the data provision interface 15.

The data provision interface 15 provides an input environment for application 9 to input conditions for the data to be acquired, and transmits the entered data acquisition conditions to the data provision generation unit 14. The data provision interface 15 also transmits the data received from the data provision generation unit 14 to application 9. Here, the data provision interface 15 may be a GUI that provides input and display screens to the user, or it may be an API that exchanges information based on a predetermined data structure.

The data registration device 7 generates input data to be registered in the related data registration unit 11 from the field data stored in the field data storage unit 5, and registers the generated input data in the related data registration unit 11. Here, the data registration device 7 may be one of the functions of the data generation device 6 in Figure 1, or it may be a different device from the data generation device 6.

Figure 3 shows an example of the data structure of the relationship data according to the first embodiment.

The relevance data 100 is structured by business-related data that shows business information and resources related to the business. The relevance data 100 shows how workers, equipment, and parts are related to a given business operation, and in what work procedures, by linking field data generated from various devices (data generation devices 6) in each business process. The relevance data 100 is generated by the information system 1 and stored in the relevance data storage unit 4.

Information concerning workers (huMan), equipment (Machine), work procedures (Method), and materials (Material) is sometimes referred to as 4M information. Alternatively, the terms 4M may be used to abbreviate 4M to refer to workers, machines (or equipment), work procedures, and materials (or parts). In the following explanation, 4M may also refer to at least one of these four elements.

Business information 110 is information that shows records of each operation that makes up a business, such as manufacturing, logistics, or service industries. For example, in the production process of a manufacturing industry, the operations include processing, welding, assembly, and inspection of materials, while in the logistics industry, they include receiving, sorting, packaging, and transporting goods. Operations are sometimes also called processes, tasks, treatments, activities, operations, or processes. Business information 110 consists of information such as which operations were performed, on which target, and when, for operations in these various types of industries.

The relevance data 100 includes, for example, the business information 110, input item information 120, worker information 130, equipment information 140, work procedure information 150, and output item information 160. Input item information 120 is information associated with input items as an example of "input resources" such as parts or materials required when performing a business. Worker information 130 is information associated with the worker performing the business. Equipment information 140 is information associated with the equipment or machinery used to perform the business. Work procedure information 150 is information associated with the work procedure that defines the steps for performing the business. Output item information 160 is information associated with output items or finished products as an example of "output resources" generated as a result of performing a business using parts or materials as input.

The output product or finished product indicated by the output product information 160 becomes the part or material (i.e., input product) used in the subsequent operation, while the input product indicated by the input product information is the output product output from the preceding operation. In other words, the parts or materials associated with the input product information 120 and the output product associated with the output product information 160 have the same attribute meaning, and when neither is specifically distinguished, they are collectively referred to as material information. Here, the parts or materials, input products, and finished products or output products that are the target of input into the operation do not necessarily have to be physical; they may also be information (data). For example, if the operation corresponding to the operation information 110 is assembly in production, the input product will be the parts or materials to be assembled, and the output product will be the physical product as the assembled item. However, if the operation corresponding to the operation information 110 is order acceptance, the order details will be the input product, and after the order is confirmed, the confirmed order details, such as the issued or assigned order number, may become the output product.

Such relationship data 100 can also be represented as a directed graph, with inputs representing what is necessary to perform a task and outputs representing the finished product generated by that task. Therefore, task information 110, input item information 120, worker information 130, equipment information 140, work procedure information 150, output item information 160, and material information are sometimes called nodes, and their relationships are called connecting lines or edges. The relationship data storage unit 4, which stores the relationship data 100, may be configured as a graph database that manages the relationships between data using the structure of a directed graph. However, the relationship data storage unit 4 may be configured as any database other than a graph database, such as a relational database or a Key-Value store type database.

As shown in Figure 3, the related data 100 can manage information across an entire business process by linking and associating multiple business processes through their inputs and outputs.

Here, the business-related data may include information other than that related to the 4Ms. For example, the business-related data may include information related to Measurement, which describes the conditions, methods, and capabilities related to measurement or inspection, based on the 5M+1E concept. Furthermore, the business-related data may also include information related to Environment, which describes the environment during the work, such as temperature, humidity, and location.

Figures 4 and 5 show examples of model data managed by the model data storage unit 3. Figure 4 shows an example of field data management information from the model data according to the first embodiment.

Here, the field data management information refers to information for accessing the field data stored in the field data storage unit 5. The field data management information includes host information indicating which server the field data storage unit 5 is located on, account information such as the username and password for accessing the database where the field data is stored, and database information such as the name of the database where the field data is stored. Furthermore, the database information includes the table names of the tables stored in the database and the names of the columns that make up the tables. The database information may also include other information such as the data type of each column.

In the example in Figure 4, the database named `database1` stores field data related to operational performance (`act_tbl1`) and field data related to equipment performance (`mac_tbl1`). `act_tbl1` includes data items (columns) such as `act_col1_1` and `act_col1_2`.

Figure 5 shows an example of the business and 4M components in the model data according to the first embodiment.

Information System 1 manages the model data, including what elements exist as a business or 4M, and what data items are associated with each business or 4M. For example, Figure 5 shows that there is a business (Business A1) and equipment (Equipment 1 and Equipment 2). Furthermore, it shows that the data items for Business A1 include start date and time, end date and time, number of executions, and business performance.

Each data item is accompanied by information indicating whether or not it is externally referenced data. If a data item is not externally referenced data (hereinafter referred to as directly stored data), it indicates that the corresponding field data is stored directly in the related data storage unit 4. If a data item is externally referenced data, it indicates that the actual field data (real data) is stored in the field data storage unit 5, and the related data storage unit 4 only stores key information for retrieving the real data from the field data storage unit 5. Therefore, in Figure 5, data items of business performance that are externally referenced data store information indicating the referenced table and the key used for the reference. This reference table and reference key correspond to the tables and columns managed in the field data management information in Figure 4.

Thus, in this system, information system 1 manages only the key information for retrieving data from the field data storage unit 5 in the related data storage unit 4, while storing the actual data in the field data storage unit 5. This avoids duplicate data management and reduces the server capacity required for data storage. On the other hand, items that serve as search criteria for business and related information, as well as frequently retrieved items, are directly stored in the related data storage unit 4, thereby speeding up and streamlining data retrieval. For example, in the example shown in Figure 5, the start and end dates of business operations are defined as directly stored data to streamline the retrieval of data related to business operations performed during a certain period. Furthermore, for example, by defining the item number of a part or product and the manufacturing number (also called the lot number or serial number) as directly stored data in material information, data related to specific parts or products can be efficiently searched and retrieved.

Furthermore, as shown in Figure 5, the same data item and referenced table may be associated with multiple tasks or 4Ms, such as the equipment measurement results for data items in Equipment 1 and Equipment 2. Additionally, the reference key for retrieving corresponding field data from the field data storage unit 5 may consist of multiple columns, such as the test record for data items in Equipment 1. In other words, the reference key may be a composite key.

Figures 4 and 5 illustrate the case where the field data stored in the field data storage unit 5 is in a table format. However, the model data only needs to contain information to identify the data stored in the field data storage unit 5; it does not necessarily need to be in a table format.

Figure 6 shows an example of input data according to the first embodiment.

The input data 600 is registered from the data registration device 7 to the related data registration unit 11. The input data 600 consists of business information 610, previous business information 601, input product information 620, output product information 660, worker information 630, equipment information 640, and work procedure information 650, and includes some or all of this information.

The business information 610 indicates which business was performed on which business target and what data was associated with that business. The business information 610 includes business identification information 611 to identify the business, business target identification information 612 to identify the business target, directly stored data 613 for that business, and identification information 614 for the external reference data of that business. The business identification information 611 corresponds to the business identification information in the model data shown in Figure 5. The business target identification information 612 is information that identifies the target on which the business is performed. The business target identification information 612 may be product identification information such as a manufacturing number, work instruction information such as a manufacturing instruction number or manufacturing order number, or an arbitrary serial number. The directly stored data 613 for the business shows the actual values for each data item of the directly stored data defined as a data item for that business in Figure 5. The identification information 614 for the external reference data of the business shows the actual values of the reference keys of the external reference data defined as a data item for that business in Figure 5.

The previous business information 601 includes the previous business identification information 602, which indicates the business identification information of the business preceding the specified business. The previous business information 601 may also include the business target identification information of the previous business, as described in the embodiment below.

The input item information 620 is information indicating what parts or materials were used (input) in that operation and what data was associated with them. The input item information 620 includes input item identification information 621, input item individual identification information 622, and identification information 624 for the material's external reference data. If there is directly stored data defined as a data item for the material, the input item information 620 may also include that directly stored data. Hereafter, unless there is a need to specifically distinguish between directly stored data and external reference data, that data will be treated as material data identification information. The same applies to the output item information 660, worker information 630, equipment information 640, and work procedure information 650.

Output product information 660 is information indicating what the output products and associated data were as a result of the execution of the work. Output product information 660 includes output product identification information 661, output product individual identification information 662, material data identification information 664, etc.

Similar to the business information 610, the input item identification information 621 and output item identification information 661 correspond to the identification information of the material defined as model data, while the material data identification information 624 and 664 indicate the actual value of the reference key of the external reference data defined as the data item of that material, or the actual value of the directly stored data. The input item individual identification information 622 and output item individual identification information 662 are information for uniquely identifying the material that became the input and output to the business. The input item individual identification information 622 and output item individual identification information 662 are, for example, the manufacturing number of the part or material. For materials, information indicating the type of material, i.e., variety or item, becomes the identification information as model data. However, even for the same material, the individual entity used differs for each business target (for example, each product produced). Therefore, the material identification information includes the individual identification information for each.

The worker information 630, equipment information 640, and work procedure information 650 are information indicating what 4M resources were used in the work and what data was associated with them. The worker information 630, equipment information 640, and work procedure information 650 each include identification information 631, 641, and 651 for the worker, equipment, and work procedure, and their respective data identification information 634, 644, and 654. Since the worker, equipment, and work procedure do not necessarily need to be explicitly distinguished, it is sufficient that 4M identification information and 4M data identification information are included. Furthermore, since the worker, equipment, and work procedure are identical in substance if they have the same identification information, unlike input and output items, it is not necessary to include individual identification information.

Next, we will explain the operation procedure in which input data is transmitted from the data registration device 7 and registered in the related data storage unit 4 by the information system 1.

Figure 7 shows an example of the operation procedure for registering input data according to the first embodiment.

The data registration device 7 transmits the input data shown in Figure 6 to the related data registration unit 11 (S701). The related data registration unit 11 searches whether the business and 4M included in the received input data, and the reference keys of the directly stored data and external reference data associated with them, are defined as model data stored in the model data storage unit 3 (S702). The related data registration unit 11 receives a response from the model data storage unit 3 (S703). For example, in the example of the input data in Figure 6, the related data registration unit 11 searches whether there is a business called business A1 as business information, whether there is a data item called start date and time as directly stored data, and whether there is act_col1_1 as a reference key for external reference data. If the items included in the input data do not exist in the model data, the related data registration unit 11 responds to the data registration device 7 that the items included in the input data do not exist in the model data. If the items included in the input data exist in the model data, the related data registration unit 11 creates related data based on the input data (S704) and registers the created related data in the related data storage unit 4 (S705). The related data registration unit 11 then responds to the data registration device 7 with the data registration result (S706).

Next, the operation procedure in which the relationship data registration unit 11 generates and registers relationship data based on the input data, as shown in steps S704 and S705 of Figure 7, will be described.

Figures 8 and 9 show an example of the procedure for generating and registering relevance data according to the first embodiment.

When the relationship data registration unit 11 receives input data (S801), it searches whether relationship data for the same business and business target as the business identification information and business target identification information contained in the input data is already registered in the relationship data storage unit 4 (S802). If the search result in S802 is true (S802: Yes), the relationship data registration unit 11 updates the value of the directly stored data or the value of the data identification information of the externally referenced data for that business data (S803). If the search result in S802 is false (S802: No), the relationship data registration unit 11 generates business data for the business identifier and business target identifier contained in the input data (S804). Here, if the relationship data has the structure of a directed graph as shown in Figure 3, generating data corresponds to generating that node, and updating data corresponds to updating the attribute values of that node.

Next, the relationship data registration unit 11 determines whether the input data contains previous business identification information (S805). If the determination result in S805 is false (S805: No), the process proceeds to step S809. If the determination result in S805 is true (S805: Yes), the system searches whether business data for the previous business targeting the same business is already registered in the relationship data storage unit 4 (S806). Here, business data for the previous business targeting the same business refers to business data (business node) that has the previous business identification information contained in the input data as business identification information, and also has the business target identification information contained in the input data as business target identification information.

If the search result in S806 is true (S806: Yes), the process proceeds to step S808. If the search result in S806 is false (S806: No), the relationship data registration unit 11 generates business data corresponding to the previous business based on the previous business identification information and business target identification information (S807). Then, the relationship data registration unit 11 generates material data as an example of an "intermediate resource" that is both an output product of the previous business and an input product to the current business, and links it with the business data of the previous business and the business data of the current business (S808). Here, if the relationship data has the structure of a directed graph as shown in Figure 3, linking the data corresponds to generating connection lines between nodes.

Thus, in S807, the relationship data registration unit 11 generates business data for the previous business if there is no relationship data for the same business target as the business target identification information in the input data. This allows for the registration of relationship data by linking the preceding and succeeding business processes, even when the input data is registered in an order different from the actual business sequence.

Next, the related data registration unit 11 determines whether the input data contains identification information for the output product (S809). If the determination result in S809 is false (S809: No), the process proceeds to step S901 in Figure 9. If the determination result in S809 is true (S809: Yes), the unit searches whether material data for the same individual output product is already registered in the related data storage unit 4 (S810). Here, material data for the same individual output product refers to material data in which the material identification information of the material data is the same as the output product identification information included in the input data, and the material individual identification information of the material data is the same as the output product individual identification information included in the input data. If the search result in S810 is false (S810: No), the related data registration unit 11 generates material data based on the output product identification information and the output product individual identification information (S811). If the input data contains output product information related to directly stored material data or material data identification information, the related data registration unit 11 registers or updates that information for the material data before step S812. Then, the related data registration unit 11 links the material data of the output product to the business data of its own business as an output product (output resource) (S812). In other words, the related data registration unit 11 generates a connection line from the business data of its own business to that material data. The subsequent steps are shown in Figure 9.

The related data registration unit 11 determines whether the input data contains identification information of the input item (S901). If the determination result in S901 is false (S901: No), the process proceeds to step S905. If the determination result in S901 is true (S901: Yes), the unit searches whether material data for the same individual input item is already registered in the related data storage unit 4 (S902). Here, material data for the same individual input item refers to material data in which the material identification information of the material data is the same as the input item identification information included in the input data, and the material individual identification information of the material data is the same as the input item individual identification information included in the input data. If the search result in S902 is false (S902: No), the related data registration unit 11 generates material data based on the input item identification information and the input item individual identification information (S903). If the input data contains information about directly stored material data or material data identification information, the related data registration unit 11 registers this information with the generated material data before step S904. Then, the related data registration unit 11 links the material data of the input item to the input item of its own business data (S904). In other words, the related data registration unit 11 generates a connection line from that material data to the business data of its own business.

Next, the relevance data registration unit 11 determines whether the input data contains other 4M identification information (i.e., identification information for workers, equipment, or work procedures) (S905). If the result of the determination in S905 is false (S905: No), the process terminates. If the result of the determination in S905 is true (S905: Yes), the relevance data registration unit 11 searches whether 4M data with the same data identification information for that 4M is already registered in the relevance data storage unit 4 (S906). If the search result in S906 is false (S906: No), the relevance data registration unit 11 generates 4M data for that 4M (S907). Then, the relevance data registration unit 11 links that 4M data to the business data of its own business as an input resource for its own business (S908). In other words, the relevance data registration unit 11 generates a connection line from that 4M data to the business data of its own business.

Next, we will explain a specific example of the procedure for generating and registering related data based on input data, as shown in Figures 8 and 9.

Figure 10 shows a specific example of the procedure for generating and registering related data according to the first embodiment.

Assume that no related data is stored in the related data storage unit 4, and that input data 1001 is input from the data registration device 7 to the related data registration unit 11. In this case, the related data registration unit 11 generates business data (node) 1002 with business identification information of business A1 and business target identification information of a01, based on the business identification information and business target identification information contained in the input data 1001. Then, the related data registration unit 11 generates material data (node) 1003 with input product identification information of material 1 and input product individual identification information of mat1_01, based on the input product identification information and input product individual identification information contained in the input data 1001. The related data registration unit 11 generates linking information (connection line) 1004 from the material data 1003 to the business data 1002. Furthermore, the related data registration unit 11 generates equipment data 1005 based on the 4M identification information and 4M data identification information contained in the input data 1001, where the 4M identification information is equipment 1 and the value of the 4M data identification information mac_col1_1 is mac_rec01. The related data registration unit 11 then generates linking information 1006 from the equipment data 1005 to the business data 1002. As a result, when business A1 of business target a01 is performed, information for acquiring the 4M resources used and related field data is associated and registered in the related data storage unit 4.

Next, let's assume that input data 1007 has been entered from the data registration device 7 into the related data registration unit 11. For example, in a normal business process, the next task after task A1 would have been to perform task A2 using equipment 2. However, due to changes in on-site work, the next task after task A1 would be to perform task A3 using equipment 1. This is an example of input data for that case.

In this case, the related data registration unit 11 generates business data 1008 with business identification information of business A3 and business target identification information of a01, based on the business identification information and business target identification information contained in the input data 1007. Then, based on the previous business identification information, the related data registration unit 11 generates material data 1009 for an intermediate product, which is the output product of the previous business's business data 1002 and the input product of the current business's business data 1008, for business data with business identification information of business A1 and business target identification information of a01. The related data registration unit 11 links the generated material data 1009 with the previous business's business data 1002 and the current business's business data 1008. That is, the related data registration unit 11 generates connection lines 1010 and 1011. In addition, the related data registration unit 11 generates equipment data 1014 and linking information 1015 with business data 1008, based on the 4M identification information and 4M data identification information. Furthermore, the related data registration unit 11 generates material data 1012 based on the output product identification information and output product individual identification information, and also generates linking information 1013 with the business data 1008.

Thus, the information system 1 according to the present invention generates, associates, and manages the relationships between preceding and succeeding tasks, the relationships between tasks and the 4M resources used in those tasks, and the relationships between tasks and field data associated with those tasks and 4M resources, based on the input data. As a result, data traceability can be guaranteed even without predetermined information on business processes and 4M resources. Furthermore, even when business processes change, new task sequences emerge, or 4M resource usage patterns occur, data management can continue without updating the model data.

Next, let's assume that input data 1016 is input from the data registration device 7. In this case, the related data registration unit 11 generates business data 1017 with business identification information of business B1 and business target identification information of b01, based on the business identification information and business target identification information contained in the input data 1016. At this time, since material data 1012 with input product identification information of part A and input product individual identification information of matA_01 has already been generated, that material data is not generated, and only linking information 1018 between business data 1017 and material data 1012 is generated. As a result, business A3 (business data 1008) with business target a01 and business B1 (business data 1017) with business target b01 are related as preceding and succeeding business via material data 1012 with material identification information of part A and material individual identification information of matA_01. On the other hand, since there is no material data with input item identification information of material 2 and input item individual identification information of mat2_01, material data 1019 is generated, and the business data 1017 and material data 1019 are linked by the linking information 1020.

Through the procedures described above, it becomes possible to record, manage, and link information about a series of business processes, their associated 4M resources, and field data. As a result, data analysis across the entire business process can be easily performed.

Here, the input data 1007 does not contain identification information for the input product, but it does contain identification information for the previous process. As a result, based on the previous process identification information, the process data 1008 and the process data 1002 of that process are linked via the material data 1009. In processes performed within the same stage, explicit identifiers are not always assigned to the input and output products of a process. However, since the information system 1 of the present invention is configured to include previous process identification information in the input data 1007, even if explicit identifiers are not assigned to the input and output products of a process, the relationship between preceding and succeeding processes can be managed based on the previous process identification information.

On the other hand, input data 1016 does not include information identifying the previous task, but it does include input item identification information and input item individual identification information. Similarly, input data 1007 includes output item identification information and output item individual identification information, but does not include information identifying the subsequent task. In other words, tasks A3 and B1 are related by the fact that part A (i.e., material data 1012) with individual identification information matA_01 is both an output item of task A3 and an input item to task B1, without explicitly including information that they are preceding and succeeding tasks. For example, if tasks A3 and B1 are different processes or different locations, the departments or management systems for tasks A3 and B1 may be different. In this case, information on output items and input items in each task is managed. However, the relationship between preceding and succeeding tasks between processes or locations may not be managed. Therefore, the task target identification information is a01 for task A3 and b01 for task B1, and they are different in each case. Even in such cases, the information system 1 of the present invention can record and manage the relationship between preceding and succeeding operations via material data 1012, based on the identification information of the input and output products.

Furthermore, as described above, the information system 1 of the present invention links operations using intermediate material data 1009, even when there is no explicit identification information for output and input products, such as between operations A1 and A3. Therefore, whether operations are linked based on prior operation identification information or based on identification information and individual identification information for output and input products, all business processes can be linked, recorded, and managed using the same data structure. This reduces the complexity of data tracing across the entire business process and speeds up the tracing process.

Figure 11 shows a specific example of the relevance data according to the first embodiment.

As shown in Figure 3, relevance data can be represented by a directed graph containing business processes and 4M resources that serve as inputs and outputs to those processes. In this case, relevance data can be represented by node information indicating the relationship between business processes, 4M resources, and related field data, connection lines connecting the nodes, and attribute information possessed by the nodes and connection lines. For example, the attribute value 1101 of business data or business node includes the node type, business identification information, business target identification information, actual values of directly stored data such as the start or end date and time of the business, and actual values of the reference key of externally referenced data.

The attribute value 1102 of material data or a material node, which indicates a part or finished product, material, etc., includes the node type, material identification information, and individual material identification information. The attribute value 1102 may also include the actual value of the reference key of the external reference data related to that material, or the actual value of the directly stored data (not shown). The information indicated by the attribute value of the material data is the same whether the material is used only as an input, only as an output, or as both an input and output for preceding and succeeding processes. For material data (intermediate products) generated to link preceding and succeeding processes based on preceding process identification information, the basic attribute values are the same as for other material data. However, since it does not have explicit material identification information, as shown in the material data 1106 in Figure 11, the material identification information and individual material identification information may be composed of a combination of the process identification information and process target identification information of the preceding and succeeding processes to indicate that it is an intermediate product between preceding and succeeding processes.

Other 4M data, such as workers, equipment, and work procedures, or attribute values of 4M nodes 1103, 1104, and 1105, include the 4M type and 4M identification information. Attribute values 1103, 1104, and 1105 may also include actual values of the reference key for externally referenced data and actual values of directly stored data (not shown) related to that 4M resource.

The connection lines include connection line 1111, which links materials and tasks as input items; connection line 1112, which links tasks and materials as output items; connection line 1113, which links workers and tasks; connection line 1114, which links equipment and tasks; and connection line 1115, which links work procedures and tasks. The attribute values of these connection lines 1111 to 1115 include information indicating the type of connection line, and information indicating the start and end points of the connection line (From, To).

A second embodiment of the present invention will be described with reference to Figures 12 and 13. In this embodiment, only the differences from the first embodiment will be described.

Figure 12 shows a specific example of the procedure for generating and registering related data according to the second embodiment.

Unlike material data that becomes input or output, the workers, equipment, and work procedures are identical to those actually used in the work, as indicated by the 4M identification information. Therefore, it is not always necessary to generate data (i.e., nodes) related to the workers, equipment, and work procedures each time field data is generated during the execution of work. However, since this 4M-related field data differs for each execution of work, it is necessary to associate and record the field data corresponding to these 4Ms with the work data for each individual work target. Therefore, in the information system 1 according to the second embodiment, data related to workers, equipment, and work procedures is registered in both the model data storage unit 3 and the related data storage unit 4 when it is set as model data. Then, if the input data entered for each execution of work includes the identification information of these 4Ms and related field data information, a connection line is generated between the work data and the 4M data corresponding to that input data. At this time, the field data information corresponding to the 4Ms is included in the connection line, not the 4M data (i.e., nodes).

Figure 12 shows an example where, as shown in Figure 5, the relationship data storage unit 4 stores equipment data for equipment 1 through 5, at the point when the elements of the business and 4M resources are defined as model data. Each piece of equipment data recorded here includes attribute values such as equipment data 1201, indicating the type of business or 4M category, and 4M identification information.

Here, we will explain the case where input data 1202, similar to input data 1001 in Figure 10, is input. The information system 1 according to the second embodiment generates linking information between the equipment data 1204 corresponding to the pre-registered equipment 1 and the business data 1205 generated from this input data, based on the 4M identification information and 4M data identification information contained in the input data 1202. That is, the information system 1 generates a connection line 1203 from the equipment data 1204 to the business data 1205. At this time, the connection line 1203 records information about the type of connection line, its start point, and its end point, as well as information about the external reference data indicated by the 4M data identification information.

Next, even when input data 1206 is entered, linking information (connection line 1207) between equipment data 1204 corresponding to equipment 1 and business data 1208 is generated based on the 4M identification information and 4M data identification information contained in input data 1206. At this time, the external reference data information indicated by the 4M data identification information is recorded as the attribute value of the connection line 1207.

Thus, in the information system 1 according to the second embodiment, data or nodes related to workers, equipment, and work procedures are pre-registered, and only connection lines are generated each time input data is received. This simplifies the generation process of related data and reduces the total amount of data to be recorded compared to generating these 4M nodes each time input data is received.

Figure 13 shows an example of the procedure for generating and registering related data according to the second embodiment.

The basic operating procedure is the same as that shown in Figures 8 and 9, with the only differences being the case where step S901 is No and the subsequent processing after step S904; therefore, a similar description is omitted. The relationship data registration unit 11 determines whether the input data contains other 4M identification information, i.e., 4M identification information corresponding to the worker, equipment, and work procedure (S1301). If the determination result of S1301 is false (S1301: No), the process ends. If the determination result of S1301 is true (S1301: Yes), the relationship data registration unit 11 searches for linking information between the business data corresponding to the business identification information and business target identification information contained in the input data (i.e., business data of the current business) and the 4M data corresponding to the 4M identification information. That is, the relationship data registration unit 11 searches whether the connection line has already been registered in the relationship data storage unit 4 (S1302). If the search result in S1302 is true (S1302: Yes), the relationship data registration unit 11 updates the attribute information of the connection line based on the 4M data identification information (S1304). If the search result in S1302 is false (S1302: No), the relationship data registration unit 11 generates connection lines between the business data and the 4M data based on the 4M data identification information, and links the business data and the 4M data (S1303).

As described above, the information system 1 according to the present invention generates relationships between business processes, relationships between business processes and 4M resources, and relationships between related data, based on input data. This allows for the recording and management of data related to a series of business processes in a related manner, even when changes occur in on-site business processes or differences arise in business processes or resources used for each product or product specification, without modifying the model data. As a result, the relationship data storage unit 4 can record and manage, for example, in a production business process, the actual results of how individual business objects, such as products, were created, and what resources and related data were used in each business process. This accumulated relationship data enables diverse analyses.

A third embodiment of the present invention will be described with reference to Figures 14 and 15. In this embodiment, only the differences from the first embodiment will be described.

This section describes an example of comparing and analyzing the business structure of the relevance data and process chart in this embodiment.

Figure 14 shows an example of the analysis of the business structure of the related data and process chart in the third embodiment.

The user interface for analysis shown in Figure 14 may be provided by the data provision interface 15, or it may be realized by the application 9 acquiring relevant data information from the data provision interface 15.

The user interface (or screen) 1401 in Figure 14 includes a planning process display area 1402, a search condition input area 1403 for related data, and a display area 1404 for the actual process.

For example, in production operations, there is information such as the flow of design-related tasks and processes, the relationships between parts, and equipment structure, which are called process charts or Bill of Process (BOP), bill of materials or Bill of Materials (BOM), and equipment list or Bill of Equipment (BOE). The relationship between the business processes generated based on this information and the 4M resources represents the design or planning business process structure. Therefore, the business process structure generated from such design or planning data is called the planning process. The planning process can be configured, for example, as shown in the planning process display area 1402 in Figure 14. On the other hand, the actual business processes and the resources used in each task may not necessarily match the planning process.

For example, in Figure 14, the user enters a search condition (matB_01 of part B) in the search condition input area 1403 to identify material data containing material identification information and individual material identification information, and searches for related data. In this case, the information system 1 extracts related data for a series of business processes associated with that part (matB_01 of part B) and displays the structure of the related data, which shows the relationship between the actual business processes and the resources used in each process, in the display area 1404. This is referred to as the actual process. In the example in Figure 14, it is easy to understand that, compared to the planned process model, in the actual process, task A3 was performed instead of task A2, and furthermore, in task A3, equipment 1 was used instead of equipment 3. In this way, by comparing the related data recorded by the present invention as the actual process with the planned process generated from planning or design data such as BOP, it becomes easy to analyze the difference between the planned and actual BOP structure.

Figure 15 shows another example of the analysis of the business structure of the related data and process chart in the third embodiment.

In Figure 15, as shown in area 1503, the search criteria for related data are the starting task (task A1) and the duration of the task, and related data is searched. In this case, information system 1 extracts related data for multiple tasks A1 during that period, and related data for a series of associated business processes. If multiple records of related data exist under these conditions, the number of extracted nodes and connection lines may be displayed in areas 1505, 1506, 1507, 1508, and 1509. Furthermore, areas 1506 and 1509, which show relationships different from the planned process model, may be displayed separately from other areas.

In the example in Figure 15, there are 10 records (i.e., 10 business targets) of related data for task A1 that meet the conditions. Of these, 2 records show that task A3 was performed after task A1, not task A2. Furthermore, in task A3, 1 of the 10 records shows that equipment 1 was used instead of equipment 3. Also, 1 record shows that part B was output as a result of task B1, not task B2. By comparing the planned process with the actual process shown by the related data in this way, it is easy to understand the extent of unplanned task sequences and the use of 4M resources. Additionally, by selecting each node, connection line, and number, the attribute values of each node and connection line, as shown in Figure 11, can be further displayed.

In addition, by defining the planned process as the sequence of tasks and processes (the normal route) when the work is carried out without problems, and comparing the actual process against this plan, it is possible to analyze the occurrence of deviations, such as the extent to which tasks followed a different procedure than the normal route.

As a result of presenting the difference between the planned process and the actual process in this way, the system may be configured to reflect the structure of the actual process in the planned process and BOP data through user action (pressing button 1510). Furthermore, the system may also include a configuration that allows for selection, such as not reflecting differences between the planned process and the actual process that have a low probability of occurring relative to the number of records in the related data constituting the actual process. This allows, for example, that even if related data is incorrectly registered due to an input data generation error, only the necessary differences between the planned and actual processes can be reflected in the planned process and BOP data.

In addition to comparing the difference between plan and actual results, showing the structure of the actual process over a certain period allows for comparison and analysis of how the relationships between business processes, operations, and 4M resources have changed. Furthermore, by analyzing the actual process that changes over a certain period together with the field data within that process, it becomes possible to analyze, for example, the structure of business processes with low defect rates, or the structure of business processes with short lead times.

A fourth embodiment of the present invention will be described with reference to Figure 16. In this embodiment, only the differences from the first embodiment will be described.

In this embodiment, a specific example of a procedure for generating and registering relevant data based on input data will be described.

Figure 16 shows a specific example of the procedure for generating and registering relational data according to the fourth embodiment.

When performing various tasks, there are cases where the same task is repeated due to malfunctions during the task, or where the process is rolled back to and repeated from an already completed upstream process. In the information system 1 according to the fourth embodiment of the present invention, the record of such repeatedly performed tasks includes, in addition to the previous task identification information, further identification information of the target of the previous task.

As shown in area 1601 of Figure 16, in a situation where tasks A1 and A2 have been performed on task a01, let's assume that task A2 is performed repeatedly due to a malfunction or other issue. In this case, for example, input data 1602 is entered. Input data 1602, as a record of the second execution of task A2, includes task identification information (a01_2) that is different from the first execution. Furthermore, as information regarding the previous task, it includes information that the previous task identification information is task A2 of the same task, and the task identification information of the previous task is a01, which corresponds to the record of the first execution.

In this case, information system 1 first generates business data 1605, which is the second execution record, with business identification information of business A2 and business target identification information of a01_2. Then, information system 1 generates material data 1604, which is an intermediate product between business data 1603, the first execution record, with business identification information of business A2 and business target identification information of a01, and business data 1605, the second execution record, with business identification information of business A2 and business target identification information of a01_2. Finally, information system 1 associates business data 1603 and business data 1605 via material data 1604.

This allows for the recording and management of recurring tasks using the same relevance data structure as other cases. As a result, the complexity of data tracing can be reduced. Furthermore, in this case, the task identification information may be composed of information indicating the individual task, information such as instructions, and the number of times the task has been performed. Figure 16 shows an example of performing the same task multiple times consecutively. However, even when the task identification information and the previous task identification information differ, task data may be generated based on the task identification information and task identification information, and intermediate material data may be generated between the task data corresponding to the previous task identification information and the previous task target identification information. In this case, the processing procedure for associating these task data is the same.

Furthermore, as shown in area 1611 of Figure 16, repeatedly performed business data can also be associated with material nodes that have explicit identifiers. This corresponds, for example, to cases where, after performing a business up to a downstream process, the output product of the downstream process is used again as the input product of the upstream process for a second or subsequent business execution. In this case, data such as input data 1612 is input. Similar to input data 1602, input data 1612 includes information that the business identification information is business A1, and the business target identification information as a record of the second execution is a different business target (a01_2) from the first execution. It also includes information regarding the input product for the business, such as the input product identification information being part A and the input product individual identification information being matA_01. The material data 1614 indicated by matA_01 of part A is output as a result of performing the first business A1, A2, and A3. In this case, the information system 1, similar to the first embodiment, links material data 1614 and business data 1613 as input items for business data 1613, which serves as a record of the second execution. As a result, after outputting part A in business A3, related data indicating that business A1 was performed a second time is recorded.

As described above, the information system 1 according to the fourth embodiment of the present invention can manage data in a structure that allows for easy tracing of the order of tasks, the tasks themselves, and the relationships between 4M resources, even when the same tasks are performed repeatedly.

As described above, according to the embodiment described, the information system 1 according to the present invention generates relationships between business processes, relationships between business processes and 4M resources, and relationships between related data, in accordance with the input data. This allows for the recording and management of data related to a series of business processes in association with each other, even when changes occur in on-site business processes or differences in business processes or resources used for each product or product specification, without modifying the model data. As a result, the information system 1 according to the present invention enables flexible responses to changes in business processes, reduces data model management and operational man-hours, and facilitates data analysis aimed at improving the overall efficiency of business processes.

Furthermore, the information system 1 according to the present invention can record and manage the actual process by which individual business objects, such as products, were created, and the resources and related data used in each process. Therefore, by comparing planned processes, such as process charts, with actual processes, which represent the relationship between actual business operations and related resources, it becomes easy to analyze the difference between planned and actual business processes.

Furthermore, even when the output or input of a business process lacks explicit identification information, all business processes can be linked, recorded, and managed using the same data structure. This reduces the complexity of data tracing across the entire business process and speeds up the tracing process.

Furthermore, even when the same task is performed repeatedly, the data can be managed in a structure that allows for easy tracing of the task sequence and the relationship between the task and the 4M resources.

1...Information system, 3...Model data storage unit, 4...Relationship data storage unit, 5...Field data storage unit, 10-1...Processor, 10-2...Memory, 11...Relationship data registration unit, 14...Provided data generation unit, 15...Data provision interface, 110...Business data or business node, 120...Parts data or parts node, 130...Worker data or worker node, 140...Equipment data or equipment node, 150...Work procedure data or work procedure node, 160...Finished product data or finished product node, MM...Storage medium

Claims (10)

At least one processor,
A memory device for storing a predetermined computer program ,
The storage device has a relational data storage unit that stores relational data including, for the preceding task, which is the first of two consecutive tasks, task data including identification information of the preceding task and identification information of the target of the preceding task, material data which is information that identifies the input resources to be input to the preceding task, equipment data which is information that identifies the equipment related to the preceding task, and relational data which includes linking information that links the material data and the equipment data to the task data.
The processor executes the predetermined computer program,
Regarding the subsequent task, which is performed after the preceding task, input data is received that includes identification information for the subsequent task, identification information for the preceding task, identification information for the target of the preceding task, and information that identifies the output resources to be output from the subsequent task. If the input data includes identification information for the preceding task, an intermediate resource is generated between the preceding task and the subsequent task, which will be the output resource for the preceding task and the input resource for the subsequent task.
The generated intermediate resources are registered in the related data storage unit.
Information systems. The aforementioned processor ,
Based on the identification information of the said business and the identification information of the target of the said business, the said business data including the identification information of the said business and the identification information of the target of the said business is generated.
If the input data includes information that identifies the input resource, input resource data relating to the input resource is generated based on the information that identifies the input resource.
As input resources for the aforementioned business, data is generated that associates the input resource data with the business data, and the generated data is registered in the relationship data storage unit.
The information system according to claim 1 . The aforementioned processor ,
Based on the identification information of the said business and the identification information of the target of the said business, the said business data including the identification information of the said business and the identification information of the target of the said business is generated.
If the input data includes information that identifies the output resource, output resource data relating to the output resource is generated based on the information that identifies the output resource.
As an output resource for the aforementioned business, data is generated that associates the output resource data with the business data, and the generated data is registered in the relationship data storage unit.
The information system according to claim 1 . The aforementioned processor ,
Based on the identification information of the said business and the identification information of the target of the said business, the said business data including the identification information of the said business and the identification information of the target of the said business is generated.
If the input data includes resource identification information for the input resource or the output resource and data identification information related to the resource, business-related data related to the business is generated based on the resource identification information and the data identification information related to the resource, and the generated business-related data is registered in the related data storage unit.
The information system according to claim 1 . The aforementioned relationship data has the structure of a directed graph.
The information system according to claim 1. The aforementioned input data includes information identifying the subject of the preceding business,
The aforementioned processor ,
If the input data includes identification information for the previous task and identification information for the task target of the previous task, an intermediate resource is generated between the previous task and the subsequent task, which contains the identification information for the previous task and the identification information for the task target of the previous task. This intermediate resource becomes an output resource for the previous task and an input resource for the subsequent task. The generated intermediate resource is then registered in the related data storage unit.
The information system according to claim 1 . The aforementioned storage device is
A field data storage unit that stores the field data that will be used as input data,
It has a model data storage unit that stores access information for accessing the aforementioned field data storage unit,
The processor executes the predetermined computer program ,
Based on the aforementioned related data and the aforementioned access information, the system retrieves field data from the field data storage unit and provides the retrieved data to the interface.
The information system according to claim 4 . The aforementioned processor ,
The relationship data corresponding to the identification information of the resource is registered in the model data storage unit and the relationship data storage unit.
Based on the input data, the relationship data corresponding to the identification information of the resource is associated with the business data corresponding to the identification information of the business and the identification information of the target of the business.
The information system according to claim 7 . The system includes an interface for displaying relationship data generated based on a schedule showing the planned relationships between multiple tasks, including the two tasks mentioned above, and the relationships between the multiple tasks and resources related to at least one of those tasks, and the relationship data stored in the relationship data storage unit.
The information system according to claim 1. A method of information management that is performed by a computer,
Of two consecutive tasks, the preceding task, which is the first task performed, is stored in a storage device as follows: task data including identification information of the preceding task and identification information of the target of the preceding task; material data, which is information identifying the input resources to be input into the preceding task; equipment data, which is information identifying the equipment related to the preceding task; and relationship data, which includes linking information that links the material data and equipment data to the task data.
Regarding the subsequent task, which is performed after the preceding task, input data is received that includes identification information for the subsequent task, identification information for the preceding task, identification information for the target of the preceding task, and information that identifies the output resources to be output from the subsequent task. If the input data includes identification information for the preceding task, an intermediate resource is generated between the preceding task and the subsequent task, which will be the output resource for the preceding task and the input resource for the subsequent task.
The generated intermediate resources are registered in the storage device.
Information management methods.