JP2021096734A - Production management system, production management method, and production management program - Google Patents

Abstract

To efficiently perform production management including physical distribution management and process management for manufacturing products even in a case where necessary member purchase destinations and manufacturing places straddle different companies and countries.SOLUTION: In a distribution system including a plurality of computers connected to one another on the Internet, a plurality of transaction data corresponding to a plurality of unit operations (supply, quality control, a production process 1, and a production process 2) to be subjected to production management for manufacturing a product are sequentially generated according to the execution order of the plurality of unit operations. When corresponding transaction data is generated in response to the start of each unit operation, information relating to execution of the unit operation is recorded thereon, and a start approval and a completion approval for the unit operation are performed. Transaction data that has undergone the start approval and the completion approval is linked by block chain configuration data according to the execution order of the unit operations and stored in a shared storage unit of the distributed system.SELECTED DRAWING: Figure 5

Description

The present invention relates to a production control system, a production control method, and a computer in such a production control system, which performs physical distribution control for arranging parts necessary for production of a product and process control for manufacturing using the parts. Regarding the production control program that should be executed.

When a product is designed by a manufacturer, a material list (hereinafter also referred to as "BOM (Bill Of Material)") is created, and when the product is ordered, an MRP (Material Requirements Planning) system is created based on the BOM. The required parts and their quantities are specified by the required quantity calculation by, and a form for arranging those parts is created. The components are then ordered offline on a paper basis or through an external EDI (Electronic Data Interchange) system. For this reason, conventionally, it has been difficult to efficiently control the progress and quality of production after ordering necessary parts with high accuracy using a computer or the like.

Japanese Unexamined Patent Publication No. 2003-223492 Japanese Unexamined Patent Publication No. 2014-197308 Special Table 2018-506128 JP-A-2018-169798

There are the following problems in the system used in the management of the above series of operations for manufacturing products (ordering / delivery of parts, management of manufacturing process). That is, the system for instructing the calculation and ordering of the required quantity of the parts for manufacturing the product and the system for placing the order are not usually connected so as to be able to exchange data. In addition, there are various different types of these systems, and different companies or departments within the same company often use different types of systems, in which case they. Data compatibility is not obtained between the systems of. In addition, if the necessary parts are purchased from different countries or manufactured in different countries, the data for the above management cannot be exchanged across countries, so the work load for the above management is heavy. It becomes.

Under these circumstances, in the past, when the necessary parts were purchased from different companies or manufactured in different countries, distribution control and process control for manufacturing the product, that is, possession associated with delivery and acceptance inspection. Management of rights transfer, progress of production process in the middle, current position of parts, transit time, quality, etc. became complicated and took a long time.

Therefore, the present invention presents a system and a method capable of efficiently performing production control including the above-mentioned distribution control and process control even when the necessary parts are purchased from different companies or in different countries. Etc. are intended to be provided.

The program according to some embodiments of the present invention is a program for performing production control including distribution control for arranging parts necessary for production of a product and process control for manufacturing using the parts. hand,
A node computer in a distributed system that includes a communication network and a plurality of node computers connected to each other by the communication network to form a blockchain for production control.
An input step that receives information necessary for manufacturing the product as production information,
When a start instruction of any of a plurality of unit works constituting the work subject to the production control is received, transaction data corresponding to the unit work to be started based on the start instruction is generated based on the production information. Steps and
When the transaction data corresponding to the unit work to be started is generated, the construction start approval acquisition step for executing the process for obtaining the approval for the start of the unit work, and the construction start approval acquisition step.
After the approval for the start of the unit work to be started is obtained, the start instruction step for issuing the start instruction for the unit work and the start instruction step.
After the construction start instruction of the unit work to be started is issued, the work result receiving step of receiving the result information of the unit work started based on the construction start instruction, and the work result receiving step.
When the result information of the unit work started is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for the completion of the unit work is executed based on the transaction data. Approval acquisition step and
After the completion approval of the unit work started is obtained, a blockchain update step of adding a new block containing transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain, and
Subsequent execution setting for starting the unit work to be executed next to the unit work based on the predetermined execution order for the plurality of unit works after the completion approval of the started unit work is obtained. To perform steps and
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
In the blockchain update step, when the completion approval of the unit work started is obtained, a new block header containing the hash value of the transaction data corresponding to the unit work for which the completion approval is obtained is described. Added to blockchain configuration data.

The production control terminal device according to some other embodiments of the present invention performs production control including distribution control for arranging members necessary for product production and process control for manufacturing using the members. It is a production control terminal device in a production control system.
The production control system includes a plurality of production control terminal devices including the production control terminal device and a communication network connecting the plurality of production control terminals to each other, and should form a block chain for the production control. It is a distributed system
The production control terminal device is
An input unit that receives information necessary for manufacturing the product as production information,
When a start instruction of any of a plurality of unit works constituting the work subject to the production control is received, transaction data corresponding to the unit work to be started based on the start instruction is generated based on the production information. Department and
When the transaction data corresponding to the unit work to be started is generated, the construction start approval acquisition unit that executes the process for obtaining the approval for the start of the unit work, and the construction start approval acquisition unit.
After obtaining the approval to start the unit work to be started, the construction start instruction unit that issues the start instruction of the unit work, and
After the construction start instruction of the unit work to be started is issued, the work result receiving unit that receives the result information of the unit work started based on the construction start instruction, and
When the result information of the unit work started is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for the completion of the unit work is executed based on the transaction data. Approval acquisition department and
A blockchain update unit that adds a new block containing transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain after the completion approval of the unit work started is obtained.
Subsequent execution setting for starting the unit work to be executed next to the unit work based on the predetermined execution order for the plurality of unit works after the completion approval of the started unit work is obtained. Including part
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
When the approval for the completion of the unit work started is obtained, the blockchain update unit provides a new block header containing a hash value of transaction data corresponding to the unit work for which the approval for completion has been obtained. Add to blockchain configuration data.

The production control method according to still some other embodiments of the present invention performs production control including distribution control for arranging parts necessary for product production and process control for manufacturing using the parts. It ’s a production control method.
Receives the design information of the product, generates the information necessary for manufacturing the product as production information based on the design information, and distributes the communication network and a plurality of production control terminal devices connected to each other by the communication network. A preparatory step to prepare for forming the blockchain for production control in the system, and
A transaction generation step in which a plurality of transaction data corresponding to a plurality of unit works constituting the work subject to the production control are sequentially generated according to a predetermined execution order for the plurality of unit works based on the production information. When,
When any transaction data is generated by the transaction generation step, a construction start approval acquisition step for executing a process for obtaining approval for the start of unit work corresponding to the generated transaction data, and a construction start approval acquisition step.
After the approval for the start of the corresponding unit work is obtained, the construction start instruction step for issuing the construction start instruction for the corresponding unit work, and the construction start instruction step.
After the construction start instruction of the corresponding unit work is issued, the work result receiving step of receiving the result information of the corresponding unit work, and
When the result information of the corresponding unit work is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for completion of the corresponding unit work is executed based on the transaction data. Completion approval acquisition step and
A blockchain update step is provided in which a new block containing transaction data corresponding to the unit work for which the completion approval has been obtained is added to the blockchain after the completion approval of the corresponding unit work is obtained.
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
In the blockchain update step, when the completion approval of the unit work started is obtained, a new block header containing the hash value of the transaction data corresponding to the unit work for which the completion approval is obtained is described. Added to blockchain configuration data
In the transaction generation step, after approval for completion of the corresponding unit work is obtained, the unit work to be executed next to the corresponding unit work is determined based on the predetermined execution order, and the determination is made. Transaction data corresponding to the unit work is generated.

The production control system according to still some other embodiments of the present invention performs production control including distribution control for arranging parts necessary for producing a product and process control for manufacturing using the parts. It is a production control system
Communication network and
A plurality of production control terminal devices connected to each other by the communication network are provided.
The communication network and the plurality of production control terminal devices form a distributed system that forms a blockchain for the production control.
The distributed system
A production information generation unit that receives design information of the product and generates information necessary for manufacturing the product as production information based on the design information.
A transaction generator that sequentially generates a plurality of transaction data corresponding to a plurality of unit works constituting the work subject to the production control according to a predetermined execution order for the plurality of unit works based on the production information. When,
When any transaction data is generated by the transaction generation unit, a construction start approval acquisition unit that executes a process for obtaining approval for the start of unit work corresponding to the generated transaction data, and a construction start approval acquisition unit.
After obtaining the approval to start the construction of the corresponding unit work, the construction start instruction issuing department that issues the construction start instruction of the corresponding unit work, and
After the construction start instruction of the corresponding unit work is issued, the work result receiving unit that receives the result information of the corresponding unit work, and
When the result information of the corresponding unit work is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for completion of the corresponding unit work is executed based on the transaction data. Completion approval acquisition department and
It is provided with a blockchain update unit that adds a new block containing transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain after the completion approval of the corresponding unit work has been obtained.
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
When the approval for the completion of the unit work started is obtained, the blockchain update unit provides a new block header containing a hash value of transaction data corresponding to the unit work for which the approval for completion has been obtained. Add to blockchain configuration data,
After obtaining approval for the completion of the corresponding unit work, the transaction generation unit determines the unit work to be executed next to the corresponding unit work based on the predetermined execution order, and the determination is made. Generate transaction data corresponding to the unit work.

A program according to still some other embodiments of the present invention provides a communication network for production control including distribution control for arranging parts necessary for producing a product and process control for manufacturing using the parts. A program to be performed in a distributed system including server computers and multiple client computers connected to each other by
The server-side production control program to be executed by the server computer and the client-side production control program to be executed by each of the plurality of client computers are included.
The client-side production control program is applied to each of the plurality of client computers.
An input step that receives information necessary for manufacturing the product as production information,
A unit work based on the executable unit work notification is received via the communication network to notify the unit work to be executed next among the plurality of unit works constituting the work subject to the production control. When the start instruction of is received, the transaction generation step of generating the transaction data corresponding to the unit work to be started based on the start instruction based on the production information, and
When the transaction data corresponding to the unit work to be started is generated, the construction start approval acquisition step for executing the process for obtaining the approval for the start of the unit work, and the construction start approval acquisition step.
After the approval for the start of the unit work to be started is obtained, the start instruction step for issuing the start instruction for the unit work and the start instruction step.
After the construction start instruction of the unit work to be started is issued, the work result receiving step of receiving the result information of the unit work started based on the construction start instruction, and the work result receiving step.
When the result information of the unit work started is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for the completion of the unit work is executed based on the transaction data. Approval acquisition step and
After the completion approval of the unit work started is obtained, the block addition notification indicating the addition of a new block containing the transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain is given. The block addition notification step to be transmitted to the server computer via the communication network is executed.
The server-side production control program is a program for causing the server computer to form a blockchain for the production control, and causes the server computer to form a blockchain.
Upon receiving the block addition notification via the communication network, a blockchain update step of adding a new block indicated by the block addition notification to the blockchain, and
Based on a predetermined execution order for the plurality of unit works, the subsequent execution setting step of sending an executable unit work notification to notify the unit work to be executed next among the plurality of unit works is executed. Let me
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
In the blockchain update step, when the completion approval of the unit work started is obtained, a new block header containing the hash value of the transaction data corresponding to the unit work for which the completion approval is obtained is described. Added to blockchain configuration data.

Embodiments other than the above-mentioned some embodiments of the present invention will be clarified from the following description of the embodiments, and thus the description thereof will be omitted.

According to some of the above embodiments of the present invention, it includes construction start information and completion information which are information for managing each unit work (for example, procurement, quality control, production process, etc.) for production control. Transaction data is recorded in the form of a blockchain in the order of execution of unit work as a target of production control as the work for manufacturing the product progresses. Further, as for the transaction data corresponding to each unit work, a block containing the transaction data is added to the blockchain after obtaining the start approval before the start of the unit work and the completion approval after the execution of the unit work. Therefore, highly reliable and appropriate information (each transaction data) is recorded as information for production control in a form that is difficult to falsify. In addition, for example, it is possible to realize a production control system by using a computer such as a personal computer or an information processing device connected to each other via the Internet, and it is possible for companies and countries with different purchase sources and manufacturing locations of parts necessary for manufacturing products. Even when straddling, it is possible to efficiently manage the distribution and process of parts for the manufacturing.

Since the effects of embodiments other than the above-mentioned some embodiments of the present invention are clear from the following description of each embodiment, the description thereof will be omitted.

It is a schematic diagram which shows the distributed system which functions as the production control system which concerns on 1st Embodiment of this invention. This is a block showing a configuration example of a computer (node computer) corresponding to a node constituting the distributed system in the first embodiment. This is a block showing another configuration example of the node computer constituting the distributed system in the first embodiment. It is a block diagram which shows the structure of the network-attached storage device (NAS) which can be used to realize the shared storage part in the distributed system in the 1st Embodiment. It is a figure which shows typically the work flow which concerns on the production control in the said 1st Embodiment. It is a figure which shows the work for obtaining the approval of the start of construction and the work for obtaining the approval of completion for the unit work corresponding to one transaction in the first embodiment. It is a figure for demonstrating the completion approval in the case where the automatic determination processing routine is included as the approver about the transaction in the 1st Embodiment. It is a flowchart which shows the production control pre-processing in the said 1st Embodiment. It is a flowchart which shows the main body processing which is executed for production control in each node computer which constitutes the distributed system in the said 1st Embodiment. It is a figure for demonstrating the structure of the block in the blockchain formed in the said 1st Embodiment. It is a figure for demonstrating the update of own blockchain configuration data held by each node computer in the said 1st Embodiment. It is a figure which shows the production information and construction start information necessary for each unit work in the said 1st Embodiment. It is a figure which shows an example of the production control data structure in the said 1st Embodiment. It is a flowchart which shows the production control preprocessing in the 2nd Embodiment of this invention. It is a flowchart which shows the main body processing which is executed for production control in each node computer which constitutes the distributed system in the 2nd Embodiment. It is a figure which shows an example of the production control data structure in the said 2nd Embodiment. It is a flowchart which shows the server-side main body processing which is executed in the computer as a server for production control in the 3rd Embodiment of this invention. It is a flowchart which shows the client-side main body processing which is executed in the computer as a client for production control in the said 3rd Embodiment. It is a flowchart which shows the server-side main body processing which is executed in the computer as a server for production control in the 4th Embodiment of this invention. FIG. 5 is a flowchart showing a client-side main body process executed by a computer as a client for production control in the fourth embodiment. It is a figure which shows an example of the production control data structure in the modification of the 1st and 3rd embodiments. It is a figure which shows an example of the production control data structure in the modification of the 2nd and 4th embodiments.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
<1. First Embodiment>
<1.1 Overall configuration of production control system>
FIG. 1 is a schematic view showing an overall configuration of a distributed system that functions as a production control system according to the first embodiment of the present invention. This distributed system includes a communication network 100 such as the Internet and a plurality of computers (hereinafter referred to as "node computers") corresponding to nodes connected to each other so as to be able to communicate with each other by the communication network 100. As shown in FIG. 1, the distributed system as the production control system includes, as node computers, a production control computer 10, a procurement control computer 11, a plurality of supplier computers 13a, 13b, ..., A quality control computer 15, and the like. It is equipped with a plurality of manufacturing control computers 17a, 17b, .... In the present embodiment, in such a distributed system, each node computer 10, 11, 13a, 13b, ..., 15, 17a, 17b, ... Operates based on the production control program described later, thereby producing a product. A blockchain is formed for production control that performs distribution control for arranging necessary parts and process control for manufacturing using the parts (hereinafter, this distributed system is also referred to as "blockchain system"). .. Note that FIG. 1 exemplifies the node computers constituting the distributed system in the present embodiment, and the production control system of the present invention includes other computers in place of or together with these node computers. May be good.

FIG. 2 is a block diagram showing a hardware configuration of the procurement management computer 11 as a node computer constituting the distributed system of FIG. 1. The computer 11 includes a main body 110, an auxiliary storage device 120, an optical disk drive 130, a display unit 140, a keyboard 150, a mouse 160, and the like. The main body 110 includes a CPU 111, a memory 112, a first disk interface unit 113, a second disk interface unit 114, a display control unit 115, an input interface unit 116, and a network interface unit 117. The CPU 111, the memory 112, the first disk interface unit 113, the second disk interface unit 114, the display control unit 115, the input interface unit 116, and the network interface unit 117 are connected to each other via a system bus. An auxiliary storage device 120 is connected to the first disk interface unit 113. An optical disk drive 130 is connected to the second disk interface unit 114. A display unit (display device) 140 is connected to the display control unit 115. A keyboard 150 and a mouse 160 are connected to the input interface unit 116. The above communication network 100 is connected to the network interface unit 117. The auxiliary storage device 120 is a magnetic disk device or the like. An optical disk 170 as a computer-readable recording medium such as a DVD (Digital Versatile Disc) or a CD-ROM (Compact Disc Read Only Memory) is inserted into the optical disk drive 130. The display unit 140 is a liquid crystal display or the like. The display unit 140 is used to display information desired by the operator. The keyboard 150 and the mouse 160 are used for the operator to input instructions to the distributed system as the production control system, that is, the blockchain system (FIG. 1).

The other node computers in the distributed system of FIG. 1 can also have the same configuration as the above configuration shown in FIG. However, in the present embodiment, a storage unit (hereinafter referred to as "shared memory" or "shared storage unit") that can be accessed from any node computer constituting the distributed system is provided. FIG. 3 is a diagram for explaining a first implementation example of the shared storage unit, and shows another configuration example slightly different from the configuration example of FIG. 2 for the node computer. In the first implementation example, the shared area 123 provided in the auxiliary storage device 120 in the production control computer 10 functions as the shared storage unit. That is, as shown in FIG. 3, the production control computer 10 is basically the same as the configuration of FIG. 2 in terms of hardware, but the auxiliary storage device 120 has other nodes in the distributed system of FIG. A shared area 123 that can be accessed from a computer via the communication network 100 is provided. Since other parts of the hardware configuration of the production control computer 10 are the same as the above configuration shown in FIG. 2, the same elements are designated by the same reference numerals and the description thereof will be omitted.

FIG. 4 is a diagram for explaining a second implementation example of the shared storage unit, and is a network attached storage device (hereinafter referred to as “NAS”) 19 that can be used in the distributed system of FIG. 1. Shows the hardware configuration of. The NAS 19 includes a control unit 210 including a CPU 111, a memory 112, a disk interface unit 113, and a network interface unit 117 connected to each other by a system bus, and a shared auxiliary storage device 220 connected to the disk interface unit 113. , The shared auxiliary storage device 220 is made accessible from another node computer in the distributed system of FIG. 1 via the communication network 100. Therefore, the auxiliary storage measure 220 functions as the shared storage unit.

Note that each node computer in the distributed system of FIG. 1 may have a configuration different from the configuration shown in FIGS. 2 or 3 as long as it has a normal function as a computer that can be connected to the communication network 100. .. However, the distributed system needs to include the shared storage unit. Hereinafter, for convenience of explanation, each node computer other than the production control computer 10 has the same configuration as that shown in FIG. 2, and the same parts are designated by the same reference numerals. The production control computer 10 is configured as shown in FIG. 3, and the shared area 123 in the auxiliary storage device 120 functions as the shared storage unit.

The auxiliary storage device 120 of the procurement management computer 11 stores a production control program 121 for causing the procurement management computer 11 to function as a node in the blockchain system. In the other node computer in the distributed system of FIG. 1, a similar production control program 121 is stored in the auxiliary storage device 120. In each node computer constituting the distributed system of FIG. 1, the CPU 111 reads the production control program 121 from the auxiliary storage device 120 into the memory 112 and executes it to form a blockchain for production control in the distributed system. Then, using this blockchain, distribution control for arranging members necessary for product production and process control for manufacturing using the members are performed.

FIG. 5 is a diagram schematically showing a work subject to production control and a work flow for production control in the present embodiment. Hereinafter, the flow of these work related to production control in the present embodiment will be described with reference to FIG.

As shown in FIG. 5, when the ordered product is designed by the manufacturer (P1, P2), data indicating the design result (hereinafter referred to as "design information") is stored in the drawing database (drawing DB) (drawing DB). P3). Here, the data stored in the drawing database includes a member list (hereinafter referred to as "design parts list") B1 showing the parts configuration at the design stage of the product, that is, the parts configuration from the functional aspect. After that, a quality process procedure manual and a process procedure manual are created based on the above design information (P8, P11, P13). That is, based on the above product design (P2), information indicating the design specifications and quality indicators of each member is stored in the quality / specification / control database (P7), and the quality process procedure manual is used using this quality / specification / control database. Is created (P8). Further, a process design for manufacturing the product is performed based on the above product design (P2) (P10), and a necessary production process (production process 1 and production process 2 in the example of FIG. 5) is performed based on the process design. ) Is created (P11, P13). In addition, it is necessary by performing the required quantity calculation (hereinafter also referred to as "MRP calculation") by the method of MRP (Material Requirements Planning) based on the above design bill of materials B1 created in the design of the product (P2). The members are specified (P4), and a bill of materials for procuring those members (hereinafter referred to as "procurement bill of materials", sometimes abbreviated as "BOM") is created (P5). The "process procedure manual" is a procedure manual that describes the procedure of each process, and also describes the specifications to be achieved in the process and the members that are the target of the process. The "quality process procedure manual" is a procedure manual that describes the specifications of the target members and parts and the standards to be achieved. In addition, the quality process procedure manual may describe the specifications of each part or a member composed of the member, if necessary.

When the procurement parts list is created as described above, the procurement department of the manufacturer procures the necessary parts according to the procurement parts list (P6). That is, each necessary member is ordered from the supplier who provides the member. Specifically, a worker (person in charge) in the procurement department can specify the necessary parts and parts and their quantity and place an order manually, or the manufacturer can use it to procure the parts and parts. If an EDI (Electronic Data Interchange) system is provided, an order is placed using that system. For convenience of explanation, in the example shown in FIG. 5, 10 members (1) to (10) are ordered. Further, in the procurement department, the procurement management computer 11 in the distributed system shown in FIG. 1 is installed. As will be described later, before the start of the procurement work, the worker in the procurement department sends an input operation instructing the start of procurement as a unit work subject to production control in the present embodiment to the procurement management computer 11. Do. As a result, transaction data TD1 corresponding to the procurement is generated. However, this embodiment is configured so that the start of procurement can be instructed by an input operation to a node computer other than the procurement management computer 11 in the distributed system of FIG. 1 (details will be described later).

When the parts (1) to (10) ordered by the procurement department as described above are delivered from the supplier, the worker inspects the parts. After that, the accepted member is passed to the next process, the quality control process. That is, the inspected parts are delivered to the quality control department of the manufacturer (delivery in the next process).

In the quality control department, quality control work is performed for each of the delivered parts based on the above-mentioned quality process procedure manual (P9). Specifically, each of the above-mentioned members (1) to (10) handed over to the quality control department is inspected based on the quality process procedure manual. Further, in the quality control department, the quality control computer 15 in the distributed system of FIG. 1 is installed. As will be described later, before the start of the quality control work, the worker of the quality control department performs an input operation instructing the start of the quality control as the unit work subject to the production control in the present embodiment of the quality control computer 15. To do. As a result, transaction data TD2 corresponding to the quality control is generated. However, this embodiment is configured so that the start of the quality control can be instructed by an input operation to a node computer other than the quality control computer 15 in the distributed system of FIG. 1 (details will be described later).

Such a quality control process is completed by inspecting and inspecting the members (1) to (10) for which the quality control work has been completed, and the members that have passed the inspection and acceptance are the next process, the production process 1. Passed to. That is, the product is delivered to the manufacturing department of the manufacturer (in-house) or another company (including affiliated companies; the same applies hereinafter) having the production process 1 (delivery in the next process).

In the manufacturing department including the production process 1 (hereinafter referred to as the "first manufacturing department"), the above-mentioned process procedure manual for the production process 1 (hereinafter referred to as "the first manufacturing department") is performed using the delivered members (1) to (10). Manufacture is performed based on "1 process procedure manual"). In the example shown in FIG. 5, in the production process 1, the part 1 is manufactured from the member (1), the part 2 is manufactured from the members (2) and (3), and the part 3 is manufactured from the members (4) to (6). It is manufactured, the component 4 is manufactured from the members (7) to (9), and the component 5 is manufactured from the member (10). Further, in the first manufacturing department, the first manufacturing management computer 17a in the distributed system of FIG. 1 is installed. As will be described later, the worker of the first manufacturing department performs an input operation for instructing the start of the first production process as the unit work subject to the production control in the present embodiment before the start of the production by the first production process. This is performed on the first manufacturing control computer 17a. As a result, transaction data TD3 corresponding to the first production process is generated. However, this embodiment is configured so that the start of the first production process can be instructed by an input operation to a node computer other than the first production control computer 17a in the distributed system of FIG. See below).

The first production process is completed by inspecting and inspecting the parts 1 to 5 manufactured there, and the parts 1 to 5 that have passed the inspection and acceptance are passed to the production process 2 which is the next process. That is, the product is delivered to the manufacturer having the production process 2 or the manufacturing department of another company (delivery in the next process).

In the manufacturing department including the production process 2 (hereinafter referred to as "second manufacturing department"), the above-mentioned process procedure manual for the production process 2 (hereinafter referred to as "second process procedure manual") using the delivered parts 1 to 5 is used. ”). In the example shown in FIG. 5, in the production process 2, component I is manufactured from parts 1 and 2, component II is manufactured from component 3, and component III is manufactured from parts 4 and 5. .. Further, in the second manufacturing department, the second manufacturing control computer 17b in the distributed system of FIG. 1 is installed. As will be described later, the worker in the second manufacturing department performs an input operation instructing the start of the second production process as the unit work subject to the production control in the present embodiment before the start of the production by the second production process. This is performed for the second manufacturing control computer 17b. As a result, the transaction data TD4 corresponding to the second production process is generated. However, this embodiment is configured so that the start of the second production process can be instructed by an input operation to a node computer other than the second production control computer 17b in the distributed system of FIG. See below).

In the example shown in FIG. 5, the components I to III manufactured as described above are shipped as one set of products, but instead of this, the production step 3 is further performed as the next step of the production step 2. They may be provided and their components I to III may be assembled into one product in this production step 3.

<1.2 Transactions and their approval in the production control system>
As shown in FIG. 5, in the production control system according to the present embodiment, each of procurement, quality control, production process 1 and production process 2 is treated as a unit work as a management unit, and transaction data corresponding to each unit work. TD1 to TD4 are sequentially generated. That is, in the present embodiment, a plurality of transaction data TD1 to TD4 (four in the example shown in FIG. 5) having different types depending on the type of unit work subject to production control are generated in a predetermined order. .. When any transaction data TDk (k = 1 to 4) is generated, the transaction data TDk is verified by the approval described later, and then the transaction data TDk alone or another verified 1 Together with one or more transaction data TDkb (kb ≠ k), it is added as one block to the blockchain to be formed by the distributed system of FIG. 1 (details will be described later). In the present embodiment, the unit work such as procurement, quality control, production process 1 or production process 2, which is the unit of control in the production control system, is a transaction in the blockchain to be formed in the distributed system of FIG. A record relating to the execution of a unit work corresponding to a transaction is referred to as transaction data (the same applies to other embodiments). As will be described later, a template consisting of items determined in advance for each transaction type is prepared, and when any unit work is started, the transaction template corresponding to the unit work is used for the unit work. Transaction data is generated by incorporating data related to execution.

FIG. 6 is a diagram showing a work for obtaining approval for starting construction and a work for obtaining approval for completion of a unit work corresponding to one transaction in the present embodiment. In the present embodiment, for each transaction, one or a plurality of approvers (hereinafter, also referred to as “construction approvers”) who approve the start of the corresponding unit work, and the unit work is properly performed after the completion of the unit work. One or more approvers (hereinafter also referred to as "completion approvers") who approve the execution are predetermined. In the example shown in FIG. 6, the construction start approver (main body of construction start approval) is composed of three approvers 1s, 2s, 3s, and the completion approver (main body of completion approval) is three approvers 1c, 2c, It is composed of 3c.

If the unit work to be started is, for example, procurement, the person in charge of ordering and / or the person in charge of the procurement department is the person who approves the start of construction, and the person in charge of receiving the delivery in the procurement department and / or the person in charge is the person who approves the completion. .. A node computer is also installed in the supplier as a supplier (Fig. 1), and the supplier may be included in the construction start approver. Further, when the unit work to be started is, for example, quality control, the worker and / or the person in charge of the quality control department becomes the construction start approver and the completion approver. In this case, construction start approval and completion approval are performed by confirming that the parts delivered to the quality control department conform to the specifications in the above-mentioned quality process procedure manual (P8). The construction start approval is given to confirm that the product conforms to the production plan, and the completion approval is given to confirm that the parts and parts are appropriate in terms of inspection and quality control. Will be done.

In the present embodiment, when any unit work should be started, that is, when any transaction should be started, the construction start approval shown in FIG. 6 is performed for the transaction. That is, first, a construction start application is made to each approver 1s, 2s, 3s who is a construction start approver. Specifically, the construction start application is made by sending an e-mail to each approver 1s, 2s, 3s using the communication network 100.

When the construction start permission is obtained from all the approvers 1s, 2s, 3s by e-mail or the like using the communication network 100 in response to the above construction start application, the unit work is started. After that, when the unit work is completed, the completion approval shown in FIG. 6 is performed for the transaction. That is, first, a completion application is made to each approver 1c, 2c, 3c who is a completion approver. Specifically, a completion application is made by sending an e-mail to each approver 1c, 2c, 3c using the communication network 100.

When the completion permission was obtained from all the approvers 1c, 2c, 3c by e-mail or the like using the communication network 100 in response to the above completion application, the contents of the transaction data TDk corresponding to the transaction were verified. become. As a result, the block containing the transaction data TDk is added to the blockchain according to the procedure described later, and the production control system can start the next transaction, that is, the next unit work. It becomes a state (see FIG. 5).

In the above, the construction start application, construction permission, completion application, and completion permission (hereinafter collectively referred to as "application approval work") are assumed to be performed by e-mail or the like using the communication network 100. The application approval work may be performed by other methods instead of or in combination with this. For example, the application approval work may be performed by telephone, handing over a document, direct dialogue, or the like. An electronic signature may be used to certify the construction start permit and the completion permit by the approver.

In addition, the construction start approver or the completion approver may include a point manager who confirms that the construction has been completed (start and end of the unit work) at a predetermined point. The point manager does not have to be a human being, and may be a predetermined program (or processing routine) that operates an information processing device such as a computer in conjunction with GPS (Global Positioning System). By including such a point manager as a construction start approver or a completion approver, it is possible to prevent erroneous delivery of parts necessary for manufacturing a product. Further, the position data used for approval by the point manager preferably includes detailed data such as an area and a shelf position when the part or product is stored in the warehouse.

In addition, the construction start approver or the completion approver may include a time manager who confirms that the construction has been completed (start and end of the unit work) within a predetermined time or time zone. The time manager does not have to be a human being, and may be a predetermined program (or processing routine) that operates an information processing device such as a computer in conjunction with a clock. By including such a time manager in the construction start approver and the completion approver, it is possible to prevent, for example, early introduction or delay of members and parts in the production process.

FIG. 7 is a diagram for explaining the completion approval when the automatic determination processing routine is included as the completion approver for the transaction in the present embodiment. FIG. 7 schematically shows the procedure of construction start approval and completion approval when the unit work to be started is quality control. That is, in the example shown in FIG. 7, when quality control should be started as a unit work subject to production control, first, transaction data corresponding to the quality control as the unit work (hereinafter referred to as "corresponding transaction data"). When TD2 is created (see Fig. 5), then the construction start application is made to the corresponding construction start approvers 1s to Ns, and the construction start permission is obtained from all the construction start approvers 1s to Ns in response to this, the unit work is concerned. Is started. After that, when the unit work is completed, the result information of the unit work is incorporated into the transaction data TD2, and subsequently, a completion application is made to each approver 1c, 2c, ..., Mc which is a completion approver. As shown in FIG. 7, among the approvers 1c, 2c, ..., Mc as the completion approver, the second approver 2c is not a human being but an automatic judgment processing routine, and the completion application to the second approver 2c is This corresponds to the activation of this automatic determination processing routine. This automatic determination processing routine is executed by, for example, the quality control computer 15. At this time, the quality control computer 15 operates as follows.

First, the quality process procedure manual (P8) described above is collated with the corresponding transaction data TD2 (step S202), and it is determined whether or not the corresponding transaction data TD2 conforms to the quality process procedure manual (step S204). As a result of the determination, when the corresponding transaction data TD2 conforms to the quality process procedure manual (that is, when each member subject to quality control conforms to the specifications), the automatic determination processing routine ends. As a result, the automatic judgment processing routine as the approver 2c gives the completion permission to the routine of the construction start approval acquisition processing on the computer (usually the quality control computer) that started the transaction corresponding to the quality control (FIG. 9 described later). See step S42).

As a result of the determination in step S204, if the transaction data TD2 corresponding to the quality process procedure manual is not conforming, troubleshooting is performed to eliminate the nonconforming portion (step S206). However, if the nonconforming portion cannot be resolved in this automatic determination processing routine, the nonconforming portion is notified (for example, displayed on the display unit of the quality control computer 15) in this step S206, and the nonconforming portion is processed by another device or an operator. You will have to wait until the part is resolved. If an input operation or data indicating that the nonconforming portion is resolved is received during this standby, the process returns to step S202. After that, steps S202 to S206 are repeatedly executed until the corresponding transaction data TD2 conforms to the quality process procedure manual, and when it is determined that the corresponding transaction data TD2 conforms to the quality process procedure manual, the automatic determination processing routine is performed. Is completed, and completion permission is given to the completion approval acquisition processing routine in the computer that started the corresponding transaction data TD2 (see step S54 in FIG. 9 described later).

<1.3 Programs and processes for production control>
As described above, in the present embodiment, each node computer 10, 11, 13a, 13b, ..., 15, 17a, 17b, ... In the distributed system of FIG. 1 executes the production control program to obtain the ordered product. A blockchain is formed in the distributed system for production control for manufacturing, that is, distribution control for arranging parts necessary for the production of the product and process control for manufacturing using the parts. The distributed system functions as a production control system for manufacturing products using this blockchain. That is, the node computers 10, 11, 13a, 13b, ..., 15, 17a, 17b, ... Connected to each other by the communication network 100 are the production control terminals constituting the production control system by executing the production control programs, respectively. It functions as devices 10, 11, 13a, 13b, ..., 15, 17a, 17b, .... However, in order for the above-mentioned manufacturer to perform production control for manufacturing the ordered product, it is necessary to give each node computer information necessary for manufacturing the product as production information based on the design information of the product. is there. In the present embodiment, the processing for this purpose (hereinafter referred to as "production control preprocessing") is realized by the production control computer 10 executing a predetermined program (hereinafter referred to as "production control preprocessing program").

From the above, in the distributed system of FIG. 1, each node computer 10, 11, 13a, 13b, ..., 15, 17a, 17b, ... Executes the production control program, and the production control computer 10 executes the production control preprocessing program. By doing so, the production control system according to the present embodiment is realized. These production control programs and production control preprocessing programs are provided stored in an optical disk 170 as a computer-readable recording medium (non-transient recording medium). That is, the users of the node computers 10, 11, 13a, 13b, ..., 15, 17a, 17b, ... For example, purchase the optical disk 170 as the recording medium of the production control program 121 and insert it into the optical disk drive 130. The production control program 121 is read from the optical disk 170 and installed in the auxiliary storage device 120 (see FIG. 2). Alternatively, the network interface unit 117 may receive the production control program 121 transmitted via the communication network 100 and install it in the auxiliary storage device 120. Similarly, the user of the production control computer 10 purchases the optical disk 170 as a recording medium in which the production control preprocessing program is stored, or receives the production control preprocessing program via the communication network 100. It is installed in the auxiliary storage device 120.

Hereinafter, the production control preprocessing based on these production control preprocessing programs and the production control main body processing based on the production control program will be described with reference to FIGS. 8 and 9.

<1.3.1 Production control pretreatment>
FIG. 8 is a flowchart showing the procedure of production control preprocessing in the present embodiment. This production control preprocessing is a process performed by the production control computer 10 based on the production control preprocessing program in the distributed system shown in FIG. 1, and corresponds to preparation for forming a blockchain for production control in the distributed system. To do. The production control computer 10 operates as follows based on this production control preprocessing program.

As described above, based on the design information of the ordered product, the procurement bill of materials (BOM) (P5), the quality process procedure manual (P8), and the process procedure manual for production processes 1 and 2 (P11, P13) are prepared. When created (see FIG. 5), the production control computer 10 receives these procurement bills of materials, quality process procedure manuals, and process procedure manuals, and creates production information for manufacturing the product from these (see FIG. 5). Step S12).

Next, the production control computer 10 sends the production information created in step S12 to the communication network 100 so that each node computer in the distributed system of FIG. 1 can acquire it (broadcast). As will be described later, this production information is received by each node computer and stored in the memory 112 or the auxiliary storage device 120. When the shared memory accessible to each node computer is provided in the distributed system (for example, in the memory 112 in any node computer), the production information is stored in the memory 112 or the like in each node computer. Alternatively, it may be stored in the shared memory. In the present embodiment, as described above, since the shared area 123 provided in the auxiliary storage device 120 of the production control computer 10 functions as the shared memory (shared storage unit) (see FIG. 3), this shared area The production information may be stored in 123. This point is the same in other embodiments.

After the production information is sent to the communication network 100, the following data (d1) to (d3) are created based on the production information, and the following data (d1) to (d3) are communicated so that each node computer can acquire the following data (d1) to (d3). Send to network 100. That is, the following data (d1) to (d3) are broadcast. Hereinafter, these data (d1) to (d3) are collectively referred to as "production control preparation data".
(D1) Templates TP1 to TP4 for each transaction data (FIG. 13)
(D2) Preparation data required for blockchain formation (see FIG. 11)
(D3) Order data indicating the transaction activation order (TBL in FIG. 13)

Here, regarding the template (d1), in the example shown in FIG. 5, four types of transaction data TD1 to TD4 correspond to each of the four unit operations of procurement, quality control, production process 1, and production process 2. Four templates TP1 to TP4 are created and sent to the communication network 100.
The preparation data of (d2) is data necessary for forming a blockchain as shown in FIG. 11 described later and is data other than transaction data. For example, in order to define a hash function for calculating a hash value. Data, data for defining the structure of each block, and constraints imposed on the hash value required when adding a new block to the blockchain (this corresponds to the difficulty of the hash puzzle in the blockchain). It is the data which shows. The hash function used in this embodiment is a cryptographic hash function which is a one-way function.
The order data of (d3) is based on the fact that the order of activation is predetermined for a plurality of transactions in the present embodiment, and is data for specifying the order of activation. In the example shown in FIG. 5, four transactions corresponding to each of these four unit operations are started in the order of execution of the unit operations of procurement → quality control → production process 1 → production process 2. In this case, the order data indicates the execution order of the unit work of procurement → quality control → production process 1 → production process 2. In the present embodiment, the information indicated by such order data is held in the form of a table as shown in FIG. 13 during the execution of the production control program described later.

When the production control preparation data (d1) to (d3) are sent to the communication network 100, the production control pre-processing ends. As will be described later, the production control preparation data (d1) to (d3) are stored in the memory 112 or the like of each node computer and are held in each node computer. When the shared memory accessible to each node computer is provided in the distributed system (for example, in the memory 112 in any node computer), a part of the production control preparation data (d1) to (d3). Alternatively, instead of storing all of them in the memory 112 or the like in each node computer, they may be stored in the shared memory. In the present embodiment, a part or all of the production control preparation data (d1) to (d3) is stored in the shared area 123 that functions as a shared memory (shared storage unit) in the auxiliary storage device 120 of the production control computer 10. You may (see FIG. 3).

<1.3.2 Production control main unit processing>
FIG. 9 is a flowchart showing a process (hereinafter, referred to as “production control main body process” or simply “main body process”) performed for production control in each node computer constituting the distributed system (FIG. 1) in the present embodiment. .. This main body processing is realized by each of the node computers (including the production control computer 10) in the distributed system shown in FIG. 1 executing the production control program 121. By this main body processing, the own blockchain configuration data to be held in each node computer and the transaction data to be stored in the shared storage unit 123 are generated and updated, so that the blockchain for production control is shown in FIG. Formed and updated in a distributed system. Specifically, each node computer operates as follows based on the production control program 121. Hereinafter, focusing on one node computer, the main body processing based on the production control program will be described with reference to FIG.

First, the node computer receives the production information and the production control preparation data sent from the production control computer 10 to the communication network 100 (see steps S14 and S16 in FIG. 8 and step S22 in FIG. 9), and based on the production information. The unit work to be executed first among the unit works constituting the work subject to production control is set as the executable unit work (step S24). In the example shown in FIG. 5, since the unit work to be executed first is procurement, this is set as an executable unit work. Further, based on the production control preparation data, FIG. 13 is shown as a data structure (hereinafter referred to as “production control data structure”) for specifying the execution order of the unit work in the present embodiment and holding the template of each transaction data. Create a data structure.

Next, it is determined whether or not the block addition notification has been received from another node computer (step S26), and if the block addition notification has not been received, the process proceeds to step S28 to display the executable unit work (step S28). .. As a result, the operator of the node computer can recognize the unit work that can be executed at the present time, and when it is determined that the unit work that can be executed should be started, the unit is referred to the node computer. Perform an input operation to instruct the start of work.

After that, the node computer determines whether or not the input operation instructing the start of the unit work has been performed on the node computer (step S30). As a result, if the input operation for instructing the start of the unit work has not been performed, the process returns to step S26. After that, as long as the block addition notification is not received and the input operation for instructing the start of the unit work is not performed, step S26 → step S28 → step S30 is repeatedly executed.

The block addition notification here means that the block including the transaction data for which the construction start permission and the completion permission have been obtained by the main body processing in the other node computer in the distributed system of FIG. 1, that is, the verified transaction data is put into the block chain. When added, in order to ensure the consistency of the blockchain configuration data held in each node computer, it means to send information about block addition to each node computer to notify the blockchain update (step described later). See S60).

If a block addition notification is received while repeatedly executing step S26 → step S28 → step S30 as described above (if it is determined to be Yes in step S26), the process proceeds to step S32 and the own blockchain configuration data is input. Update. Hereinafter, the update of the own blockchain configuration data will be described with reference to FIGS. 10 and 11. Although each block constituting the blockchain can include a plurality of transaction data, it is assumed that each block contains only one transaction data for convenience of explanation below.

The blockchain in the present embodiment is obtained by concatenating blocks including transaction data generated for production control for one product in the production control system in the order of generation, and a block header among the data constituting the blockchain. The own blockchain configuration data configured by concatenating is held in each node computer in the distributed system of FIG. However, as described below, the transaction data in each block constituting the block chain is stored in the shared area 123 (hereinafter referred to as "shared storage unit 123") in the auxiliary storage device 120 of the production control computer 10, and this shared storage is performed. The transaction data stored in the unit 123 is shared by each node computer in the distributed system of FIG. In this respect, it can be said that the production control computer 10 functions as a server.

FIG. 10A is a diagram showing a configuration example of one block constituting the blockchain in the present embodiment. As shown in FIG. 10A, the one block includes a block header BLKk and transaction data TDk associated with the block header BLKk. The block header BLKk is held in each node computer as a component of its own blockchain configuration data, and the transaction data TDk is stored in the shared storage unit 123 (see FIG. 3). In the configuration example of FIG. 10A, each block header BLKk (k = 1, 2, ...) has a hash value THSk of transaction data TDk to be associated with the block header BLKk and a storage location of the transaction data TDk (in the shared storage unit 123). The address value TADk indicating the storage position), the immediately preceding reference PRFk as address information for referring to the immediately preceding block header BLKk-1, the hash value PHSk of the immediately preceding block header BLKk-1, and the hash value of the block header BLKk. It includes the nonce value NSk used when obtaining it (see FIG. 11 (A) described later).

In the present embodiment, when transaction data TDk is newly generated based on the start instruction of any unit work, the block corresponding to the transaction data TDk is subjected to the work of approval of start and completion of the unit work. Is created and added to the blockchain (see steps S58, S60, etc. in FIG. 9). At this time, as shown in FIG. 10A, only one transaction data TDk corresponds to one block header BLKk, but a plurality of transaction data correspond to one block header, that is, a plurality of one block. It may be configured to include the transaction data of. In a block having such a configuration, a plurality of transaction data contained therein are concatenated in the form of a Merkle Tree, so that the hash value of the plurality of transaction data is the hash of the root node of the Merkle tree. It is aggregated into values (hereinafter referred to as "root hash value"), and the root hash value is held as the transaction hash value THSk in the block header BLKk of the block, and the storage location (that is, root) of the root node of the Merkle tree. The address information indicating the storage location of the hash reference data described later that constitutes the node) is held as the transaction address value TADk.

For example, when one block contains two transaction data TDk1 and TDk2 (for example, transaction data TD1 corresponding to procurement and transaction data TD2 corresponding to quality control), the block is configured as shown in FIG. 10B. Will be done. That is, the block includes a block header BLKk having the same configuration as the block header BLKk in the configuration example of FIG. 10A, and a Merkle tree configured by concatenating the two transaction data TDk1 and TDk2. As shown in FIG. 10B, this Merkle tree includes two transaction data TDk1 and TDk2 as leaf nodes, respectively, and has a hash reference data THRk1 of one transaction data TDk1 and a hash reference of the other transaction data TDk2. Includes a root node TNk1 consisting of data THRk2. Here, the hash reference data is data to be used for reading data, and is data including an address value indicating a storage location of the data to be read and a hash value of the data to be read (hereinafter, transaction). Hash reference data that should be used to read data is called "transaction hash reference data"). Therefore, in the configuration example of FIG. 10B, of the two transaction hash reference data constituting the root node TNk1, one hash reference data THRk1 has an address value indicating a storage location of the one transaction data TDk1 and the above. It is composed of a hash value of one transaction data TDk1, and the other hash reference data THRk2 is composed of an address value indicating a storage location of the other transaction data TDk2 and a hash value of the other transaction data TDk2. Further, the hash reference data THRk of the root node TNk1 is held in the block header BLKk corresponding to the two transaction data TDk1 and TDk2. That is, as shown in FIG. 10B, in the block header BLKk, the address value indicating the storage location of the root node TNk1 is held as the transaction address value TADk, and the hash value of the root node TNk1 is the transaction hash value THSk. Is held as. In the Merkle tree in the configuration example of FIG. 10B, by providing (two) intermediate nodes between the root node TNk1 and the transaction data TDk1 and TDk2 as leaf nodes, one block is formed. More transaction data can be included. In this case, each intermediate node is composed of the hash reference data of the leaf node as its child node, and the root node TNk1 is composed of the hash reference data of the intermediate node as its child node.

By using the Merkle tree as described above, it is possible to include a plurality of transaction data in one block without changing the structure of the block header. However, in the following, as described above, for convenience of explanation, only one transaction data is included in each block.

FIG. 11 is a diagram for explaining the update of the blockchain configuration data (own blockchain configuration data) held by each node computer in the present embodiment. Now, when the block addition notification is received, when the own blockchain configuration data in the node computer is in a state in which the block headers BLK1 to BLKn are connected in order as shown in FIG. 11 (A), the transaction data TDn + It is assumed that the block addition notification including the hash reference data (transaction hash value THSn + 1 and transaction address value TADn + 1) of 1 and the immediately preceding hash value PHSn + 1 and the nonce value NSn + 1 is received (step S26). The following own blockchain configuration data is updated in response to this block addition notification.

First, the block header BLKn + 1 of the block to be added to the blockchain is generated and incorporated into the own blockchain configuration data. Specifically, the latest reference RRF in the own blockchain, that is, includes the immediately preceding hash value PHSn + 1, the nonce value NSn + 1, the transaction hash value THSn + 1, and the transaction address value TADn + 1 included in this block addition notification. A block header containing the address information indicating the position of the nth block header BLKn as the immediately preceding reference PRFn + 1 is generated as the n + 1th block header BLKn + 1. After that, the latest reference RRF is updated with the address information indicating the position of the n + 1th block header BLKn + 1. In this way, the own blockchain configuration data is updated from the configuration shown in FIG. 11A to the configuration shown in FIG. 11B.

When the block addition notification is received, the output value of the hash function whose input value is the transaction data TDn + 1 stored in the shared storage unit 123 as the transaction data included in the block to be added and the block addition notification Confirm that the included transaction hash value THSn + 1 matches, and use the combination of the transaction hash value THSn + 1 included in the block addition notification, the immediately preceding hash value PHSn + 1, and the nonce value NSn + 1 as the input value. It is preferable to obtain the output value of the hash function to be used and confirm that this output value is equal to or less than a predetermined value. If these cannot be confirmed, at least one of the transaction data TDn + 1, the immediately preceding hash value PHSn + 1, and the nonce value NSn + 1 is not appropriate, so the update of the own blockchain configuration data based on the block addition notification is performed. This is because it should be avoided.

After the own blockchain configuration data is updated as described above, it is determined whether or not there is a feasible unit work by referring to the data shown in FIG. 12 or FIG. 13 based on the production information input in step S22. (Step S34). As a result of this determination, if there is no feasible unit work, all transactions corresponding to all the unit work subject to production control in the present embodiment have been started. That is, the main body processing in the node computer for the production control of one product is completed. Therefore, the process returns to step S22, and the process waits in step S22 until the production information regarding the next product to be manufactured is received.

As a result of the determination in step S34, if there is an executable unit work, the latest block header BLKn + in the own blockchain configuration data is based on the execution order specified in the table TBL in the production control data structure shown in FIG. The unit work to be executed next to the unit work corresponding to the latest transaction data corresponding to 1 is determined, the determined unit work is set as an executable unit work, and this is set on the display unit 140 of the node computer. Display (step S36). Then, the process returns to step S26.

On the other hand, if the node computer accepts an input operation instructing the start of the unit work while repeatedly executing step S26 → step S28 → step S30 (if it is determined to be Yes in step S30), the current execution is performed. It is considered that the start of the possible unit work is instructed, and the process proceeds to step S38 with the executable unit work as the target unit work.

In step S38, the transaction data TDn included in the latest block header in the production information and own blockchain configuration data input in step S22 (hereinafter, this latest block header is indicated by the code “BLKn”) is referred to. Target unit Acquire construction start information for work. This construction start information is data necessary for starting the target unit work. FIG. 12 shows production information and construction start information required for each unit work. As shown in FIG. 12, the construction start information is a parts order number obtained from the bill of materials (BOM) in the production information when the target unit work is procurement, and when the target unit work is quality control. Is information indicating the quality process procedure in the production information and information indicating the next process delivery obtained from the transaction data TDn corresponding to the immediately preceding unit operation (procurement). When the target unit operation is the production process 1, Information indicating the process procedure 1 in the production information and information indicating the next process delivery 1 obtained from the transaction data TDn corresponding to the immediately preceding unit operation (quality control). When the target unit operation is the production process 2, Information indicating the process procedure 2 in the production information and information indicating the next process delivery 2 obtained from the transaction data TDn corresponding to the immediately preceding unit operation (production process 1) (see FIG. 5).

Next, based on the production control data structure shown in FIG. 13, the acquired transaction start information is incorporated into the template TPn + 1 corresponding to the target unit work (see FIG. 12), so that the transaction data corresponding to the target unit work (hereinafter referred to as Generate TDn + 1 (referred to as “corresponding transaction data”) (step S40).

Next, the process of obtaining the start approval of the target unit work is executed (step S42). As shown in FIG. 13, the template TPk (k = 1 to 4) corresponding to each unit work contains information (hereinafter referred to as “approver information”) AS that identifies the start approver or the completion approver of the unit work. include. Therefore, the work for obtaining the construction start permission from each construction start approver Ssj specified by the approver information AS included in the corresponding transaction data TDn + 1 is performed as described above (see FIGS. 6 and 7). Based on the work, the node computer is notified or input operation indicating the construction start permission by each construction start approver Ssj. This process of obtaining the construction start approval is repeated until the construction start permission is obtained from all the construction start approvers Ssj specified in the approver information AS (steps S42 and S44). When the construction start permission is obtained from all the construction start approvers Ssj specified in the approver information AS, it is considered that the start of the target unit work has been approved, and the process proceeds to step S46.

In step S46, a construction start instruction for the target unit work is issued. By issuing this construction start instruction, the target unit work is started. That is, depending on whether the target unit work is procurement, quality control, production process 1, or production process 2, the person in charge of the corresponding department, a computer, or the like performs the above-mentioned work or processing (see FIG. 5). ..

When the above-mentioned work or process corresponding to the target unit work is completed, the node computer receives the completion notification of the target unit work (step S48), and then acquires the result information of the target unit work (step S50). The acquired result information is incorporated into the corresponding transaction data TDn + 1 as completion information (step S52). Here, the result information of the target unit work is information indicating the ordering date, the acceptance date, etc. when the target unit work is procurement, and the inspection of parts when the target unit work is quality control. Information indicating the result, etc., and when the target unit work is the production process 1, the information indicates the inspection result, acceptance date, etc. of the parts obtained by the production process 1, and the target unit work is the production process 2. In the case, it is information indicating an inspection result, an acceptance date, or the like of a part or product obtained in the production process 2.

Next, the process of obtaining the completion approval of the target unit work is executed (step S54). In this acquisition process, as described above from each completed approver Scj (see FIG. 13) specified by the approver information AS included in the corresponding transaction data TDn + 1, the target unit is based on the corresponding transaction data TDn + 1. The work for obtaining the completion permission is performed for the work (see FIGS. 6 and 7), and based on the work, the node computer is notified or input operation indicating the completion permission by each completion approver Scj. This completion approval acquisition process is repeated until completion permission is obtained from all completion approvers Scj specified in the approver information AS (steps S54 and S56). When the completion permission is obtained from all the completion approvers Scj specified in the approver information AS, it is considered that the completion of the target unit work has been approved, and the process proceeds to step S57.

In step S57, the nonce value for adding the block including the corresponding transaction data TDn + 1 to the blockchain in the present embodiment is obtained. That is, the nonce value is obtained so that the hash value when the hash function specified in the above-mentioned production control preparation data (see step S22) satisfies the following condition HP (the problem of obtaining such a nonce value is Called a "hash puzzle").
(Condition HP): The hash value, which is the output value of the hash function when the combination of the transaction hash value THSn + 1 and the immediately preceding hash value and the nonce value is used as the input value, is equal to or less than the predetermined value (for example, the predetermined upper level of the output value). The bit is "0"). The immediately preceding hash value here is the output value of the hash function when the combination of the transaction hash value THAn, the immediately preceding hash value PHSn, and the nonce value NSn in the nth block header BLKn, which is the latest block header at the present time, is used as the input value. Is.

When a nonce value satisfying the above condition HP is obtained, the own blockchain configuration data is updated by the corresponding transaction data TDn + 1 (step S58). That is, the following processing is performed on the own blockchain configuration data of the node computer.

Immediately before the update of the own blockchain configuration data in step S58, it is assumed that the own blockchain configuration data is in a state in which the block headers BLK1 to BLKn are sequentially connected as shown in FIG. 11A. At this time, in step S58, first, the corresponding transaction data TDn + 1 is stored in the shared storage unit 123 (shared area 123 (see FIG. 3) in the auxiliary storage device 120 of the production management computer 10 functioning as a server), and the corresponding transaction data is stored. The block header BLKn + 1 corresponding to TDn + 1 is generated and incorporated into the own blockchain configuration data. Here, the block header BLKn + 1 is generated as a block header containing the following data. That is, the block header BLKn + 1 includes the address information indicating the position of the latest block header immediately before the update of the own blockchain configuration data, that is, the nth block header BLKn, as the immediately preceding reference PRFn + 1, and the nth block header BLKn + 1. The output value of the hash function when the combination of the transaction hash value THSn, the immediately preceding hash value PHSn, and the nonce value NSn included in is used as the input value is included as the immediately preceding hash value PHSn + 1, and the corresponding transaction data TDn + 1 is shared and stored. The address information indicating the storage location in the unit 123 is included as the transaction address value TADn + 1, and the output value of the hash function when the corresponding transaction data TDn + 1 is used as the input value is included as the transaction address value TADn + 1. After that, as the latest reference RRF, the address information indicating the position of the n + 1th block header BLKn + 1 is set. In this way, the own blockchain configuration data is updated from the configuration shown in FIG. 11A to the configuration shown in FIG. 11B.

After updating the own blockchain configuration data as described above, the node computer immediately before corresponding to the block header BLKn + 1 added in step S58 as the blockchain update authority for the corresponding transaction data TDn + 1. Communication network so that other node computers in the distributed system of FIG. 1 can obtain block addition notifications including hash value PHSn + 1, nonce value NSn + 1, transaction hash value THSn + 1, and transaction address value TADn + 1. Send to 100 (step S60).

After that, the process returns to step S34, and the processes after step S34 are executed in the same manner as when the own blockchain configuration data is updated based on the receipt of the block addition notification (step S26 → S32).

As described above, each node computer in the distributed system of FIG. 1 performs the main body processing of FIG. 9 based on the production control program 121, so that the transaction generation unit (see step S40) and the construction start approval acquisition unit are performed in the distributed system. (See steps S42 to S44), construction start instruction issuing section (see steps S46), work result receiving section (see steps S48 to S50), completion approval acquisition section (see steps S52 to S56), blockchain updating section (steps S26, S32, S57 to S60) and the subsequent execution setting unit (see S34, S36) are realized, and the distributed system functions as a production control system using a blockchain. The blockchain update unit includes a block generation update unit (steps S57 to S58) that updates its own blockchain configuration data based on the generation of a new block, and a block addition notification unit (step S60) that sends a block addition notification. It includes a block reception update unit (steps S26 and S32) that updates the own blockchain configuration data based on the reception of the block addition notification sent from another node computer.

<1.4 Effect>
As described above, according to the present embodiment, it is information for managing each unit work (in the example shown in FIG. 5, each of procurement, quality control, production process 1 and production process 2) for production control. Transaction data TDk (k = 1, 2, ...) Containing construction start information and completion information is in the order of execution of unit work as a target of production control according to the progress of work for manufacturing the ordered product (see FIG. 13). , Recorded in the form of a blockchain (see FIG. 11). Further, the transaction data TDk corresponding to each unit work is blocked by the block including the transaction data TDk after obtaining the construction start permission by the construction start approver and the completion permission by the completion approver determined in advance according to the unit work. Added to the chain. Therefore, highly reliable and appropriate information (each transaction data TDk) is recorded as information for production control in a form that is difficult to falsify. That is, in the block chain including each transaction data in the form shown in FIG. 11, since the hash value of the block header BLKk is included in the immediately following block header BLKk + 1 as the immediately preceding hash value PHSk + 1, the block header When the transaction data TDk corresponding to BLKk is falsified, the falsification can be easily detected. On the other hand, when the transaction data TDk of the block header BLKk (k <n) in the middle preceding the latest block header BLKn is tampered with, if the nonce value or the immediately preceding hash value is changed so that the tampering is not detected, the block concerned. Since it is necessary not only to solve the hash puzzle described above for the header BLKk, but also to solve the hash puzzle for all the block headers BLKk + 1, BLKk + 2, ..., BLKn following the block header BLKk, the blockchain It is difficult to falsify the transaction data in.

Further, among the data constituting the blockchain for recording the above information for production management, the transaction data TD1, TD2, ... Are stored in the shared storage unit (shared area) 123 in the production management computer 10 functioning as a server. However, the own blockchain configuration data configured by concatenating the block headers is held in each node computer (see FIG. 1) constituting the distributed system, and each node computer. The own blockchain configuration data in is updated while maintaining consistency (see FIG. 9). Therefore, the production control system according to the present embodiment does not require a part that controls or adjusts the entire system, and is particularly reliable except for a computer as a server that stores transaction data as a component of the system. It can operate continuously at a high operating rate while maintaining high reliability without using a high-performance computer or communication network. Therefore, for example, it is possible to realize a production control system by using a computer such as a personal computer or an information processing device connected to each other via the Internet, and a company or a company having a different purchase source or manufacturing place of parts necessary for manufacturing a product. Even if it spans countries, it is possible to efficiently manage the distribution and process of parts for the manufacturing while maintaining high reliability. In addition, there is no highly controlled system or adjustment part, and it is possible to build a robust production information database without using a highly reliable computer or network other than the computer as the above server, and those who have authority You can manage data and check the progress of the process. It may also be used as an EDI system between organizations that do not have a capital relationship.

Further, according to the present embodiment, since the transaction data TDk included in each block constituting the blockchain is stored only in the shared storage unit 123, the storage capacity required in the production control system using the blockchain can be obtained. Can be reduced.

<2. Second embodiment>
In the first embodiment described above, the start instruction of each unit work subject to production control and the generation of the corresponding transaction data based on the instruction can be performed on any node computer in the distributed system as the production control system (Fig.). 9). In the examples shown in FIGS. 1 and 5, the unit work (procurement, quality control, production process 1, production process 2) constituting the work subject to production control and the node computers 11, 15, 17a, 17b in the distributed system Can be associated with each other, so that a computer that generates transaction data corresponding to each unit work may be determined in advance. Therefore, in the following, a production control system in which a computer for generating transaction data corresponding to each unit work is predetermined will be described as a second embodiment of the present invention.

Also in the present embodiment, as in the first embodiment, in the distributed system shown in FIGS. 1 and 2, each node computer constituting the distributed system executes a predetermined program to have the same function as described above. A production control system with Further, the work and processing for obtaining the construction start permission and the completion permission based on the transaction data corresponding to each unit work are the same as those in the first embodiment (see FIGS. 6 and 7). However, among the computers constituting the distributed system (FIG. 1) in the present embodiment, the production control preprocessing program executed by the production control computer 10 and each node computer 10, 11, 13a, 13b, ..., 15, 17a, The production control program 121 executed by 17b, ... is different from the corresponding program (see FIGS. 8 and 9) in the first embodiment, and the unit work execution order (transaction activation order) is set accordingly. The data structure for specifying and holding the template of each transaction data, that is, the production control data structure is also different from the data structure (FIG. 13) in the first embodiment. Since the configurations other than these in the present embodiment are the same as those in the first embodiment, the same reference numerals are given to the same or corresponding parts, and detailed description thereof will be omitted. In the following, among the configurations and operations in the present embodiment, a program for production control, production control preprocessing based on the program, and production control main body processing will be mainly described.

<2.1 Programs and processes for production control>
Also in this embodiment, in order to generate production information necessary for production control based on the design information of the ordered product and give it to each node computer, the production control computer 10 in the distributed system of FIG. 1 provides a production control preprocessing program. Execute. Further, also in the present embodiment, each node computer 10, 11, 13a, 13b, ..., 15, 17a, 17b, ... In the distributed system of FIG. 1 executes a production control program to be a member necessary for manufacturing a product. A blockchain for production control that performs distribution control for arranging goods and process control for manufacturing using the parts is formed in the distributed system, and the distributed system manufactures products using the blockchain. It functions as a production control system for this purpose.

FIG. 14 is a flowchart showing a procedure of production control preprocessing in the present embodiment. This production control preprocessing is a process performed by the production control computer 10 based on the production control preprocessing program in the distributed system shown in FIG. 1, and corresponds to preparation for forming a blockchain for production control in the distributed system. To do. The production control computer 10 operates as follows based on this production control preprocessing program.

First, as in the first embodiment (see FIG. 8), the procurement parts list (BOM) (P5), the quality process procedure manual (P8), the production processes 1 and 2 created based on the design information of the ordered product. Production information for the product is created from the process procedure manuals (P11, P13) for the above (step S12), and the production information is transferred to the communication network 100 so that each node computer in the distributed system of FIG. 1 can acquire the production information. Send (step S14).

After that, the following data (e1) to (e3) are created based on the above production information, and the following data (e1) to (e3) are transmitted to the communication network 100 so that each node computer can acquire the following data (e1) to (e3). That is, the following data (e1) to (e3) are broadcast (hereinafter, these data (e1) to (e3) are collectively referred to as "production control preparation data").
(E1) Templates TP1 to TP4 for each transaction data (FIG. 16)
(E2) Preparation data required for blockchain formation (Fig. 11)
(E3) Order data indicating the transaction activation order

These production control preparation data (e1) to (e3) correspond to the production control preparation data (d1) to (d3) in the first embodiment, respectively. However, in the present embodiment, the computer that generates the transaction data corresponding to each unit work is predetermined and is specified in the table TBL in the production control data structure shown in FIG. The procurement management computer (Node1), quality control computer (Node2), manufacturing control computer (Node3), and manufacturing control computer (Node4) specified in this table TBL are the procurement management computer 11 and quality control shown in FIG. It corresponds to the computer 15, the first manufacturing control computer 17a, and the second manufacturing control computer 17b, respectively.

After the production control preparation data (e1) to (e3) are sent to the communication network 100, the unit work to be executed first is performed based on the order data of the production control preparation data (e1) to (e3). A start instruction for the unit work is transmitted to the node computer for which the corresponding transaction data should be generated (step S18). In the example shown in FIG. 16, a procurement start instruction as a unit work is transmitted to the procurement management computer 11. After the transmission of the instruction to start the unit work to be executed first, the production control preprocessing is terminated.

FIG. 15 is a flowchart showing a production control main body process (hereinafter abbreviated as “main body process”) performed for production control in each node computer constituting the distributed system (FIG. 1) in the present embodiment. Similar to the first embodiment, this main body processing is realized by each of the node computers (including the production control computer 10) in the distributed system shown in FIG. 1 executing the production control program 121, and this main body processing , The blockchain for production control is formed in the distributed system of FIG. 1 by generating and updating the own blockchain configuration data to be held in each node computer and the transaction data to be stored in the shared storage unit 123. Will be updated. However, in the present embodiment, since the computer that generates the transaction data corresponding to each unit work is predetermined, the production control program 121 is different from the production control program 121 in the first embodiment. Each node computer operates as follows based on the production control program in this embodiment. Hereinafter, focusing on one node computer, the main body processing based on the production control program in the present embodiment will be described with reference to FIG.

First, the node computer receives the production information (see step S14 in FIG. 14) and the production control preparation data (see step S16 in FIG. 14) sent from the production control computer 10 to the communication network 100 (step S62).

Next, it is determined whether or not the block addition notification has been received (step S64), and if the block addition notification has not been received, the process proceeds to step S66 to determine whether or not the unit work start instruction has been given. As a result of the determination, if the unit work start instruction has not been given, the process returns to step S64. After that, step S64 → step S66 is repeatedly executed while the block addition notification is not received and the unit work start instruction is not given.

If a block addition notification is received while the steps S64 → S66 are repeatedly executed as described above (if it is determined to be Yes in step S64), the process proceeds to step S68 and the own blockchain configuration data is updated. The specific processing in updating the own blockchain configuration data is the same as that in the first embodiment (see FIG. 11).

After updating the own blockchain configuration data, it is determined whether or not there is a feasible unit work by referring to the data shown in FIG. 12 or FIG. 16 based on the production information input in step S62 (step S70). As a result of this determination, if there is a unit work that can be executed, the process returns to step S64. On the other hand, as a result of this determination, if there is no feasible unit work, all transactions corresponding to all the unit work subject to production control in the present embodiment have been started. That is, the main body processing in the node computer for the production control of one product is completed. Therefore, the process returns to step S62, and the process waits in step S62 until the production information regarding the next product to be manufactured is received.

If a unit work start instruction is received from another node computer in step S66 while the steps S64 → step S66 are being repeatedly executed as described above, the process proceeds to step S72 (hereinafter, the start instruction is received here). Unit work is called "target unit work"). As will be described later, a unit work start instruction from each node computer is issued to a node computer predetermined for the unit work (step S102). Therefore, as can be seen from the table TBL shown in FIG. 16, when the node computer is the procurement management computer 11 (Node 1), the procurement start instruction is received, and when the node computer is the quality control computer 15 (Node 2), the quality control is received. In the case of the first manufacturing control computer 17a (Node 3), the start instruction of the production process 1 is received, and in the case of the second manufacturing control computer 17b (Node 4), the start instruction of the production process 2 is received. receive.

In step S72, the transaction data TDn included in the latest block header in the production information and own blockchain configuration data input in step S62 (hereinafter, this latest block header is also referred to by the reference numeral “BLKn”) is referred to. Target unit Acquire construction start information for work. Since this construction start information is the same as the construction start information in the first embodiment, the description thereof will be omitted (see FIG. 12).

Next, based on the production control data structure shown in FIG. 16, by incorporating the acquired construction start information into the template TPn + 1 corresponding to the target unit work (see FIG. 12), the transaction data corresponding to the target unit work (hereinafter referred to as Generate TDn + 1 (referred to as “corresponding transaction data”) (step S74).

Next, the process of obtaining the start approval of the target unit work is executed (step S76). Since the process of obtaining the construction start approval is the same as that of the first embodiment, the description thereof will be omitted (see FIGS. 6 and 7). This process of obtaining the construction start approval is repeated until the construction start permission is obtained from all the construction start approvers Ssj specified by the approver information AS in the template TPi (see FIG. 16) corresponding to the target unit work (steps S76 and S78). .. When the construction start permission is obtained from all the construction start approvers Ssj specified in the approver information AS, it is considered that the start of the target unit work has been approved, and the process proceeds to step S80.

In step S80, a construction start instruction for the target unit work is issued. By issuing this construction start instruction, the target unit work is started. That is, as in the first embodiment, depending on whether the target unit work is procurement, quality control, production process 1, or production process 2, the person in charge of the corresponding department, the computer, or the like has already described the work. Alternatively, processing is performed (see FIG. 5).

When the above-mentioned work or process corresponding to the target unit work is completed, the node computer receives the completion notification of the target unit work (step S82), and then acquires the result information of the target unit work (step S84). The acquired result information is incorporated into the corresponding transaction data TDn + 1 as completion information (step S86). Since the specific processing of these steps S82 to 86 is the same as that of the first embodiment (see steps S48 to S52 of FIG. 9), the description thereof will be omitted.

Next, the process of obtaining the completion approval of the target unit work is executed (step S88). Since the process of obtaining the completion approval is the same as that of the first embodiment, the description thereof will be omitted (see FIGS. 6 and 7). This completion approval acquisition process is repeated until completion permission is obtained from all completion approvers Scj specified in the approver information AS in the template TPi (see FIG. 16) corresponding to the target unit work (steps S88 and S90). .. When the completion permission is obtained from all the completion approvers Scj specified in the approver information AS, it is considered that the completion of the target unit work has been approved, and the process proceeds to step S92.

In step S92, a nonce value for adding a block containing the corresponding transaction data TDn + 1 to the block chain in the present embodiment is obtained (step S92), and the nonce value is used to obtain the own block chain based on the corresponding transaction data TDn + 1. Update the configuration data (add a block containing the corresponding transaction data TDn + 1) (step S94). At this time, the corresponding transaction data TDn + 1 is stored in the shared storage unit 123 and is not included in the own blockchain configuration data. Since the specific processing of these steps S92 and S94 is the same as that of the first embodiment (see steps S57 and S58 of FIG. 9 and FIG. 11), the description thereof will be omitted.

After updating the own blockchain configuration data as described above, the node computer immediately before corresponding to the block header TBLKn + 1 added in step S94 as the blockchain update authority for the corresponding transaction data TDn + 1. Communication network so that other node computers in the distributed system of FIG. 1 can obtain block addition notifications including hash value PHSn + 1, nonce value NSn + 1, transaction hash value THSn + 1, and transaction address value TADn + 1. Send to 100 (step S96).

After that, based on the execution order (order data) specified in the table TBL shown in FIG. 16, it is determined whether or not the target unit work is the last unit work (step S98). As a result of this determination, when the target unit work is the last unit work, it means that all the transactions corresponding to all the unit work subject to the production control in the present embodiment have been started. That is, the main body processing in the node computer for the production control of one product is completed. Therefore, the process returns to step S62, and the process waits in step S62 until the production information regarding the next product to be manufactured is received.

As a result of the determination in step S98, if the target unit work is not the last unit work, the unit work to be executed next to the target unit work is determined based on the execution order specified in the table TBL shown in FIG. Step S100), the determined unit work start instruction is transmitted to the node computer to execute the unit work (issue of the next unit work start instruction) (step S102). After that, the process returns to step S64, and the subsequent processes are executed again.

<2.2 effect>
As described above, in the present embodiment, the computer that generates transaction data corresponding to each unit work subject to production control (in the example shown in FIG. 5, each of procurement, quality control, production process 1 and production process 2). Is predetermined (see table TBL shown in FIG. 16), but as in the first embodiment, transaction data TDk (k =) including construction start information and completion information which are information for managing each unit work. 1, 2, ...) Are recorded in the form of a blockchain in the order of execution of unit work as the target of production control (see FIGS. 5 and 16) according to the progress of the work for manufacturing the ordered product. (See FIG. 11). Further, as in the first embodiment, the transaction data TDk corresponding to each unit work is obtained after obtaining the construction start permission by the construction start approver and the completion permission by the completion approver determined in advance according to the unit work. A block containing the transaction data TDk is added to the blockchain. Therefore, this embodiment also has the same effect as that of the first embodiment. That is, even in this embodiment, even if the supplier or manufacturing place of the parts required for manufacturing the product spans different companies or countries, the distribution control and process control of the parts for the manufacturing are high. It can be done efficiently while maintaining reliability. In addition, there is no highly controlled system or parts to be adjusted, and it is possible to construct a robust production information database without using a highly reliable computer or network other than the computer as the server. It may also be used as an EDI system between organizations that do not have a capital relationship. Furthermore, since the transaction data TDk included in each block constituting the blockchain is stored only in the shared storage unit 123, the storage capacity required in the production control system using the blockchain can be reduced. ..

<3. Third Embodiment>
In the first and second embodiments, the transaction data TD1, TD2, ... Of the data constituting the blockchain are stored only in the shared storage unit 123, but the block headers BLK1, BLK2, ... Are concatenated. The configured own blockchain configuration data is stored in each node computer (see FIGS. 10 and 11). However, all the data constituting the blockchain may be stored in the shared storage unit 123. In the following, in the first embodiment, the own blockchain configuration data stored in each node computer is used as the shared blockchain configuration data in the shared storage unit 123 (shared area 123 in the auxiliary storage device 120 of the production control computer 10). ) Will be described as the third embodiment. In the third embodiment, a shared storage unit (first shared storage unit) in which transaction data TD1, TD2, ... Is stored and a shared storage unit (second shared storage unit) in which shared blockchain configuration data is stored. Is the same shared storage unit 123, but the transaction data TD1, TD2, ... And the shared blockchain configuration data may be stored in different first and second shared storage units, respectively (this point). The same applies to the fourth embodiment described later).

Also in the present embodiment, as in the first embodiment, in the distributed system shown in FIGS. 1 and 2, each node computer constituting the distributed system executes a predetermined program to have the same function as described above. A production control system with Further, the work and processing for obtaining the construction start permission and the completion permission based on the transaction data corresponding to each unit work are the same as those in the first embodiment (see FIGS. 6 and 7). However, among the node computers constituting the distributed system (FIG. 1) in the present embodiment, the production management computer 10 executes the production control preprocessing program according to the first embodiment, and also executes the production control preprocessing program according to the first embodiment. By executing the server-side production control program described later in place of the production control program in the above, the computer functions as a server computer (hereinafter, also simply referred to as a "server"), and the other node computers are produced in the first embodiment. It executes a program corresponding to the management program (hereinafter referred to as "client-side production control program") and functions as a client computer (hereinafter, also simply referred to as "client"). Since the configurations other than these in the present embodiment are the same as those in the first embodiment, the same reference numerals are given to the same or corresponding parts, and detailed description thereof will be omitted. In the following, among the configurations and operations in the present embodiment, the server-side main body processing based on the server-side production management program executed by the production management computer 10 as a server, and the client-side production management program executed by each client computer. The explanation will focus on the client-side main body processing based on.

<3.1 Production control pretreatment>
In this embodiment as well, as in the first embodiment, the production control computer 10 as a server executes the production control preprocessing shown in FIG. 8 based on the production control preprocessing program. As a result, the production information for manufacturing the target product is sent to each node computer or stored in the shared storage unit 123. After that, the production control preparation data (d1) to (d3) described above are generated based on this production information and sent to each node computer or stored in the shared storage unit 123.

<3.2 Server-side main unit processing>
After the completion of the above production control pre-processing, the production control computer 10 as a server executes the server-side production control main body processing (hereinafter referred to as "server-side main body processing") based on the server-side production management program. FIG. 17 is a flowchart showing the server-side main body processing. In the distributed system of FIG. 1, the production control computer 10 executes the server-side production control program, and each client computer, that is, each of the node computers other than the production control computer 10 as a server executes the client-side production control program described later. As a result, a blockchain for production control is formed and updated in the distributed system of FIG.

Hereinafter, the server-side main body processing will be described with reference to FIG. In the server-side main body processing, the production control computer 10 operates as follows based on the server-side production control program.

First, the production information and the production control preparation data are read from the shared storage unit 123 (shared area 123 in the auxiliary storage device 120 of the production control computer 10) (step S22).
Next, it waits until the block addition notification is received from another node computer, that is, the client computer (step S26), and when the block addition notification is received, the process proceeds to step S27.

The block addition notification here is a block that includes transaction data (verified transaction data) for which construction start permission and completion permission have been obtained by main body processing (client side main body processing) on another node computer as a client. When it should be added to the chain, it means that the block chain should be updated by transmitting the information about the block addition to the production management computer 10 as a server (details will be described later (see step S60 in FIG. 18)). ). As will be described later, the block addition notification includes a transaction hash value THSn + 1 and a transaction address value TADn + 1 to be set in the block header BLKn + 1 of the block to be added.

In step S27, the hash function of the hash function when the combination of the transaction hash value THAn, the immediately preceding hash value PHSn, and the nonce value NSn in the nth block header BLKn, which is the latest block header at the present time in the shared blockchain configuration data, is used as the input value. The immediately preceding hash value PHSn + 1, which is the output value, is obtained, and the nonce value is used so as to satisfy the above-mentioned condition HP by using the immediately preceding hash value PHSn + 1 and the transaction hash value THSn + 1 included in the block addition notification. Find NSn + 1.

Next, the shared blockchain configuration data is updated by using the obtained nonce value NSn + 1 together with the immediately preceding hash value PHSn + 1 and the transaction hash value THSn + 1 (step S32). In the present embodiment, the transaction data TD1, TD2, ... Included in each block of the block chain is not only stored in the shared storage unit 123 (shared area 123 in the auxiliary storage device 120 of the production management computer 10), but also in the above-mentioned first. The own blockchain configuration data stored in each node computer in the first embodiment is also stored only in the shared storage unit 123 as shared blockchain configuration data. Except for such a difference, the update of the shared blockchain configuration data in the present embodiment (step S32) is the same as the update of the own blockchain configuration data in the first embodiment (step S32 in FIG. 9). (Fig. 11). Therefore, detailed description of updating the shared blockchain configuration data will be omitted.

After the shared blockchain configuration data is updated as described above, it is determined whether or not there is a feasible unit work by referring to the data shown in FIG. 12 or FIG. 13 based on the production information input in step S22. (Step S34). As a result of this determination, if there is no feasible unit work, all transactions corresponding to all the unit work subject to production control in the present embodiment have been started. Therefore, the process returns to step S22, and the process waits in step S22 until the production information regarding the next product to be manufactured is received.

As a result of the determination in step S34, if there is an executable unit work, the latest block header BLKn + in the shared blockchain configuration data is based on the execution order specified in the table TBL in the production control data structure shown in FIG. A notification (hereinafter referred to as "executable unit work notification") for determining the unit work to be executed next to the unit work corresponding to the latest transaction data corresponding to 1 and notifying the determined unit work is shown in FIG. It is sent to the communication network 100 so that it can be acquired by another node computer as a client in the distributed system (step S36).

After that, the process returns to step S26, and the processes after step S26 are executed.

<3.3 Client-side processing>
FIG. 18 shows a process performed for production control at each node computer other than the production control computer 10 as a server among the node computers constituting the distributed system (FIG. 1) in the present embodiment, that is, a client computer (hereinafter, “client side”). It is a flowchart which shows "main body processing"). This client-side main body processing is realized by each client computer in the distributed system of FIG. 1 executing a client-side production control program. Each client computer operates as follows based on this production control program. Hereinafter, focusing on one client computer, the client-side main body processing based on this production control program will be described with reference to FIG.

First, the client computer receives the production information and the production control preparation data sent from the production control computer 10 to the communication network 100 (see steps S14 and S16 in FIG. 8 and step S22 in FIG. 18). Next, the production control computer 10 attempts to receive the executable unit work notification sent to the communication network 100. As a result, when the executable unit work notification is received, the (executable) unit work indicated by the notification is displayed, and when the executable unit work notification is not received, the immediately received executable unit work is displayed. The unit work indicated by the notification is displayed (step S28). However, if there is no executable unit work received by this point, it is displayed that the executable unit work is unknown.

After that, it is determined whether or not the input operation instructing the start of the displayed executable unit work has been performed on the node computer (step S30). As a result, if the input operation for instructing the start of the unit work has not been performed, the process returns to step S25. After that, step S25 → step S28 → step S30 is repeatedly executed while the input operation for instructing the start of the unit work is not performed.

If an input operation instructing the start of the unit work is performed in step S30 while repeatedly executing step S25 → step S28 → step S30 as described above, the process proceeds to step S38. In the following, the unit work for which the start instruction is received (executable) is referred to as "target unit work").

After that, transaction data (corresponding transaction data) TDn + 1 corresponding to the target unit work is generated by the same process as the first embodiment (steps S38 to S56 in FIG. 9), and the start approval is obtained for the target unit work. When the processing, the completion approval acquisition process, and the like are performed (steps S38 to S56 in FIG. 18) and the completion permission is obtained from all the completion approvers, it is considered that the completion of the target unit work has been approved, and the process proceeds to step S60.

In step S60, the client computer stores the corresponding transaction data TDn + 1 in the shared storage unit 123 as a blockchain update authority for the corresponding transaction data TDn + 1, and blocks that should include the corresponding transaction data TDn + 1. The block addition notification for adding the data to the blockchain is transmitted to the production management computer 10 as a server via the communication network 100. This block addition notification includes a transaction address value TADn + 1 indicating the storage location of the corresponding transaction data TDn + 1, and a transaction hash value THSn + 1 which is an output value of a hash function having the corresponding transaction data TDn + 1 as an input value. Includes.

After sending the block addition notification, it is determined whether or not there is a unit work that can be performed by referring to the data shown in FIG. 12 or 13 based on the production information input in step S22 (step S61). As a result of this determination, if there is a unit work that can be executed, the process returns to step S25 and the subsequent processing is executed. On the other hand, as a result of this determination, if there is no feasible unit work, all transactions corresponding to all the unit work subject to production control in the present embodiment have been started. Therefore, the process returns to step S22, and the process waits in step S22 until the production information regarding the next product to be manufactured is received.

<3.4 effect>
As described above, in the distributed system (FIG. 1) of the present embodiment, the production control computer 10 executes the server-side production control program, and each client computer executes the client-side production control program for production control. Blockchain is formed and updated in the distributed system of FIG. In this embodiment as well, as in the first embodiment, the transaction data TDk (k = 1, 2, ...) Containing the construction start information and the completion information, which are information for managing each unit work, can be obtained. As the work for manufacturing the ordered product progresses, the unit work as the target of production control is recorded in the form of a blockchain in the order of execution (see FIGS. 5 and 16) (see FIG. 11). Further, as in the first embodiment, the transaction data TDk corresponding to each unit work is obtained after obtaining the construction start permission by the construction start approver and the completion permission by the completion approver determined in advance according to the unit work. A block containing the transaction data TDk is added to the blockchain. Therefore, this embodiment also has the same effect as that of the first embodiment. In the present embodiment, not only the transaction data TD1, TD2, ..., But also the shared blockchain configuration data configured by concatenating the block headers is stored only in the shared storage unit 123. In comparison, the required storage capacity can be further reduced.

<4. Fourth Embodiment>
Next, in the second embodiment, the own blockchain configuration data stored in each node computer is used as the shared blockchain configuration data, and the shared area 123 in the shared storage unit 123, that is, the auxiliary storage device 120 of the production control computer 10. The configuration modified to be stored in the fourth embodiment will be described.

Also in the present embodiment, as in the second embodiment, in the distributed system shown in FIGS. 1 and 2, each node computer constituting the distributed system executes a predetermined program to have the same function as described above. A production control system with Further, the work and processing for obtaining the construction start permission and the completion permission based on the transaction data corresponding to each unit work are the same as those in the second embodiment (see FIGS. 6 and 7). However, among the node computers constituting the distributed system (FIG. 1) in the present embodiment, the production management computer 10 executes the production control preprocessing program in the second embodiment and also executes the production control preprocessing program in the second embodiment. By executing the server-side production control program described later in place of the production control program in the above, the computer functions as a server computer (hereinafter, also simply referred to as a "server"), and the other node computers are produced in the second embodiment. It executes a program corresponding to the management program (hereinafter referred to as "client-side production control program") and functions as a client computer (hereinafter, also simply referred to as "client"). Since the configurations other than these in the present embodiment are the same as those in the second embodiment, the same reference numerals are given to the same or corresponding parts, and detailed description thereof will be omitted. In the following, among the configurations and operations in the present embodiment, the server-side main body processing based on the server-side production management program executed by the production management computer 10 as a server, and the client-side production management program executed by each client computer. The explanation will focus on the client-side main body processing based on.

<4.1 Production control pretreatment>
In this embodiment as well, as in the second embodiment, the production control computer 10 as a server executes the production control preprocessing shown in FIG. 14 based on the production control preprocessing program. As a result, the production information for manufacturing the target product is sent to each node computer or stored in the shared storage unit 123. After that, the production control preparation data (e1) to (e3) described above are generated based on this production information and sent to each node computer or stored in the shared storage unit 123.

<4.2 Server-side main unit processing>
After the completion of the above production control pre-processing, the production control computer 10 as a server executes the server-side production control main body processing (hereinafter referred to as "server-side main body processing") based on the server-side production management program. FIG. 19 is a flowchart showing the server-side main body processing. In the distributed system of FIG. 1, the production control computer 10 executes the server-side production control program, and each client computer, that is, each of the node computers other than the production control computer 10 as a server executes the client-side production control program described later. As a result, a blockchain for production control is formed and updated in the distributed system of FIG.

Hereinafter, the server-side main body processing will be described with reference to FIG. In the server-side main body processing, the production control computer 10 operates as follows based on the server-side production control program.

First, the production information and the production control preparation data are read from the shared storage unit 123 by executing steps S62 to S68 corresponding to steps S22 to S32 in the server-side main body processing (FIG. 17) in the third embodiment. Next, when the block addition notification is received from any of the client computers, the nonce value required for adding the block to the blockchain is obtained based on the block addition notification, and the shared blockchain configuration data is updated.

After that, with reference to the data shown in FIG. 12 or 13 based on the production information input in step S62, it is determined whether or not there is a feasible unit work (step S70). As a result of this determination, if there is no feasible unit work, all transactions corresponding to all the unit work subject to production control in the present embodiment have been started. Therefore, the production control end notification is sent to the communication network 100 so that each client computer in the distributed system of FIG. 1 can acquire it (step S104). After that, the process returns to step S62, and the process waits in step S62 until the production information regarding the next product to be manufactured is received.

As a result of the determination in step S70, if there is an executable unit work, the latest block header BLKn + in the shared blockchain configuration data is based on the execution order specified in the table TBL in the production control data structure shown in FIG. The unit work to be executed next to the unit work corresponding to the latest transaction data corresponding to 1 is determined (step S100), and the start instruction of the determined unit work is transmitted to the client computer to execute the unit work (step S100). Issuing an instruction to start the next unit work) (step S102). After that, the process returns to step S65, and the subsequent processes are executed again.

<4.3 Client-side processing>
FIG. 20 is a flowchart showing a process (hereinafter referred to as “client-side main body process”) performed for production control in each client computer among the node computers constituting the distributed system (FIG. 1) in the present embodiment. This client-side main body processing is realized by each client computer in the distributed system of FIG. 1 executing a client-side production control program. Each client computer operates as follows based on this client-side production control program. Hereinafter, focusing on one client computer, the client-side main body processing based on this production control program will be described with reference to FIG. 20.

First, the client computer receives production information (see step S14 in FIG. 14) and production control preparation data (see step S16 in FIG. 14) sent from the production control computer 10 to the communication network 100 (step S62).

Next, it is determined whether or not the unit work start instruction has been received (step S67), and if the unit work start instruction has not been received, the process proceeds to step S69, and the production control end sent from the production control computer 10 as a server. Determine if you have received the notification. As a result of the determination, if the production control end notification has not been received, the process returns to step S67. After that, step S67 → step S69 is repeatedly executed while neither the start instruction of the unit work nor the production control end notification is received.

When the production control end notification is received while the steps S67 → S69 are being repeatedly executed, the process returns to step S62, and the process waits in step S62 until the production information regarding the next product to be manufactured is received.

If a start instruction for unit work is received while the steps S67 → S69 are being repeatedly executed, the process proceeds to step S72 (hereinafter, the unit work for which the start instruction is received is referred to as “target unit work”).

Proceeding to step S72, transaction data (corresponding transaction data) TDn + 1 corresponding to the target unit work is generated by the same process as the second embodiment (steps S72 to S90 in FIG. 15), and the target unit work is performed. When the construction start approval acquisition process, the completion approval acquisition process, etc. are performed (steps S72 to S90 in FIG. 20) and the completion permission is obtained from all the completion approvers, it is considered that the completion of the target unit work has been approved and the completion of the target unit work is approved in step S96. Proceed to.

In step S96, the client computer stores the corresponding transaction data TDn + 1 in the shared storage unit 123 as a blockchain update authority for the corresponding transaction data TDn + 1, and should include the corresponding transaction data TDn + 1. The block addition notification for adding the data to the blockchain is transmitted to the production management computer 10 as a server via the communication network 100. This block addition notification includes a transaction address value TADn + 1 indicating the storage location of the corresponding transaction data TDn + 1, and a transaction hash value THSn + 1 which is an output value of a hash function having the corresponding transaction data TDn + 1 as an input value. Includes.

After sending the block addition notification, it is determined whether or not the target unit work is the last unit work based on the execution order (order data) specified in the table TBL shown in FIG. 16 (step S98). As a result of this determination, when the target unit work is the last unit work, it means that all the transactions corresponding to all the unit work subject to the production control in the present embodiment have been started. Therefore, the process returns to step S62, and the process waits in step S62 until the production information regarding the next product to be manufactured is received.

As a result of the determination in step S98, if the target unit work is not the last unit work, the process returns to step S67, and the subsequent processes are executed again.

<4.4 effect>
As described above, in the distributed system (FIG. 1) of the present embodiment, the production control computer 10 executes the server-side production control program, and each client computer executes the client-side production control program for production control. Blockchain is formed and updated in the distributed system of FIG. In the present embodiment, as in the second embodiment, the transaction corresponding to each unit work subject to production control (in the example shown in FIG. 5, each of procurement, quality control, production process 1 and production process 2). Although the computer that generates the data is predetermined (see the table TBL shown in FIG. 16), as in the first embodiment, the transaction including the construction start information and the completion information which are the information for managing each unit work. Data TDk (k = 1, 2, ...) Is in the order of execution of unit work as the target of production control according to the progress of work for manufacturing the ordered product (see FIGS. 5 and 16), and the form of the blockchain. It is recorded in (see FIG. 11). Further, as in the first and second embodiments, the transaction data TDk corresponding to each unit work obtains a construction start permit and a completion permit by a completion approver determined in advance according to the unit work. After that, the block containing the transaction data TDk is added to the blockchain. Therefore, this embodiment also has the same effect as the first and second embodiments. In the present embodiment, not only the transaction data TD1, TD2, ..., But also the shared blockchain configuration data configured by concatenating the block headers is stored only in the shared storage unit 123. The required storage capacity can be further reduced as compared with the embodiment.

<5. Modification example>
The present invention is not limited to the above-described embodiment, and the above-described embodiment can be variously modified and implemented without departing from the spirit of the present invention. Hereinafter, a modified example of the above embodiment will be described.

In the first to fourth embodiments, the execution order of the unit work is specified and the template of each transaction data is held based on the production control preparation data generated in the production control preprocessing (FIGS. 8 and 14). The data structure for the purpose, that is, the production control data structure is configured by using the table TBL as shown in FIG. 13 or FIG. 16, but uses a data structure having a structure different from the data structure shown in FIG. 13 or FIG. You may. For example, a linked list in which templates are concatenated in an order according to the execution order of unit work may be used. In this case, in the first and third embodiments, the linked list shown in FIG. 21 can be used instead of the data structure shown in FIG. 13, and in the second and fourth embodiments, FIG. The linked list shown in FIG. 22 can be used instead of the data structure shown. These linked lists are converted into templates TP1, TP2, TP3, TP4, ... Of transaction data TD1, TD2, TD3, TD4, ... Corresponding to unit operations such as procurement, quality control, production process 1, production process 2, ... The corresponding entries E1, E2, E3, E4, ... Are concatenated as a unidirectional list. That is, in the linked list shown in FIGS. 21 and 22, a header HDR for storing a pointer SPtr pointing to the first entry E1 corresponding to the procurement template TP1 is provided, and each entry Ek has a data structure of the corresponding template TPk. In addition, a pointer NPtr pointing to the next entry Ek + 1 is included. In the second and fourth embodiments, since the computer that generates the transaction data corresponding to each unit work subject to production control is predetermined, each entry Ek in the linked list shown in FIG. 22 is included. Contains the identification information Nodek of the node computer from which the corresponding transaction data should be generated. Each of the linked lists shown in FIGS. 21 and 22 specifies the execution order of the unit work, and includes the same data structure as in FIGS. 13 and 16 as the data structure of the template corresponding to each unit work. Therefore, even when the linked list shown in FIGS. 21 and 22 is used instead of the data structures shown in FIGS. 13 and 16, the same effects as those in the first and second embodiments can be obtained, respectively. ..

In the first or second embodiment, the node computer that generated the new transaction data sends a block addition notification to the other node computer to the communication network 100 as the update authority (step S60 in FIG. 9, FIG. 14). Step S96), and in the third or fourth embodiment, the node computer (client computer) that generated the new transaction data acts as the update authority and sends a block addition notification to the production management computer 10 as a server in the communication network. It is sent to 100 (step S60 in FIG. 18, step S96 in FIG. 20). However, the configuration may be such that the update authority for new transaction data is not limited to the node computer or client computer that generated the transaction data.

In the first or second embodiment, among the data constituting the blockchain, the own blockchain configuration data formed by concatenating the block headers is held in each node computer (see FIG. 1) and is transaction data. The TD1, TD2, ... Are stored in the shared storage unit 123 (shared area 123 in the production management computer 10 that functions as a server) (see FIGS. 3 and 10). However, instead of this, not only the own blockchain configuration data but also transaction data TD1, TD2, ... May be stored in each node computer. According to such a configuration, the storage capacity required in the production control system is larger than that of the first and second embodiments, but the same effect as that of the first or second embodiment is obtained. In addition, since all the data that makes up the blockchain is stored in each node computer and updated while maintaining consistency, there is no highly controlled system or coordination part, and a highly reliable computer or network can be created. It is possible to build a robust production information database without using it.

In each of the above embodiments, the hash value is obtained as the output value of the hash function having the combination of the transaction hash value THSn, the immediately preceding hash value PHSn, and the nonce value NSn as input values in order to solve the hash puzzle (described above). (Refer to "(Condition HP)"), if a change (tampering) of transaction data can be detected, another value or a combination of data may be used as an input value of the hash function instead. For example, a combination of the transaction data TDn, the immediately preceding hash value PHSn, and the nonce value NSn may be used as the input value of the hash function, or the hash reference data THRn (transaction hash value THSn and the transaction address value TADn) and the immediately preceding hash value PHSn. The combination of and the nonce value NSn may be used as the input value of the hash function.

In each of the above embodiments, the block header of each block in the block chain holds the hash reference data THRk of the transaction data TDk included in the block, and the hash reference data THRk is the storage location of the transaction data TDk. It is composed of a transaction address value TADk indicating the above and a transaction hash value THSk which is a hash value of the transaction data TDk (see FIG. 10A). According to the configuration using such hash reference data THRk, the transaction data is read out based on the transaction address value TADk, the hash value is obtained, and the hash value is collated with the transaction hash value THSk in the hash reference data. It is possible to easily confirm whether or not the transaction data TDk has been changed (whether or not it has been tampered with). However, instead of holding such hash reference data THRk in the block header, only the transaction hash value THSk may be held in the block header. In this case, for example, the transaction data TDk corresponding to the block header includes the address value indicating the storage location of the block header or the transaction hash value THSk included in the block header, so that the transaction can be performed in the same manner as described above. It is possible to confirm whether or not the data TDk has been changed (whether or not the data has been tampered with). Normally, in a system application, the contents of the transaction data TDk are accessed by the user inputting specific information such as "ordering part A on the MY year MM month DD date" corresponding to the transaction data TDk. be able to.

In each of the above embodiments, the unit work subject to production control is not limited to the one shown in FIG. 5, and different unit work may be executed depending on the product to be manufactured. In this case, the transaction data corresponding to the different unit work is recorded in the form of a blockchain according to the execution order of the different unit work.

10 ... Production control computer (node computer, production control terminal equipment)
11 ... Procurement management computer (node computer, production control terminal equipment)
13a ... Supplier computer (node computer, production control terminal equipment)
13b ... Supplier computer (node computer, production control terminal equipment)
15 ... Quality control computer (node computer, production control terminal equipment)
17a ... 1st manufacturing control product computer (node computer, production control terminal device)
17b ... Second manufacturing control product computer (node computer, production control terminal device)
18 ... Production control program 100 ... Communication network 111 ... CPU
112 ... Memory 117 ... Network interface memory 120 ... Auxiliary storage 121 ... Production control program 123 ... Shared area (shared storage)
TAk ... Transaction (k = 1, 2, ...)
TDk ... Transaction data (k = 1, 2, ...)
RRF ... Latest reference TPk ... Template (k = 1, 2, ...)
BLKk ... Block header (k = 1, 2, ...)
TBL ... Table 1s-Ns ... Start of construction approver (main body of approval of start of construction)
1c ~ Mc ... Completion approver (completion approver body)

Claims (23)

It is a program for performing production control including distribution control for arranging parts necessary for product production and process control for manufacturing using the parts.
A node computer in a distributed system that includes a communication network and a plurality of node computers connected to each other by the communication network to form a blockchain for production control.
An input step that receives information necessary for manufacturing the product as production information,
When a start instruction of any of a plurality of unit works constituting the work subject to the production control is received, transaction data corresponding to the unit work to be started based on the start instruction is generated based on the production information. Steps and
When the transaction data corresponding to the unit work to be started is generated, the construction start approval acquisition step for executing the process for obtaining the approval for the start of the unit work, and the construction start approval acquisition step.
After the approval for the start of the unit work to be started is obtained, the start instruction step for issuing the start instruction for the unit work and the start instruction step.
After the construction start instruction of the unit work to be started is issued, the work result receiving step of receiving the result information of the unit work started based on the construction start instruction, and the work result receiving step.
When the result information of the unit work started is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for the completion of the unit work is executed based on the transaction data. Approval acquisition step and
After the completion approval of the unit work started is obtained, a blockchain update step of adding a new block containing transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain, and
Subsequent execution setting for starting the unit work to be executed next to the unit work based on the predetermined execution order for the plurality of unit works after the completion approval of the started unit work is obtained. To perform steps and
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
In the blockchain update step, when the completion approval of the unit work started is obtained, a new block header containing the hash value of the transaction data corresponding to the unit work for which the completion approval is obtained is described. A program that is added to the blockchain configuration data. The distributed system includes a first shared storage unit that holds transaction data corresponding to the unit work for which the completion approval has been obtained, which is accessible to all of the plurality of node computers. Described program. The program according to claim 1, wherein the distributed system further includes a second shared storage unit that is accessible to all of the plurality of node computers and holds the blockchain configuration data. Each of the plurality of node computers holds the blockchain configuration data, and
The blockchain update step
When a new block containing transaction data corresponding to the unit work for which completion approval has been obtained should be added to the blockchain, data writing for storing the corresponding transaction data in the first shared storage unit. Steps and
When the new block should be added to the blockchain, a block generation update that adds a block header containing a hash value of the corresponding transaction data to the blockchain configuration data in the node computer in which the corresponding transaction data was generated. Steps and
When the corresponding transaction data is stored in the first shared storage unit and a block header containing a hash value of the corresponding transaction data is added to the blockchain configuration data, the new block is added. A block addition notification step of sending the indicated block addition notification to the communication network so that other node computers in the distributed system can receive it, and
When a block addition notification indicating the addition of a new block is received via the communication network, the block header containing the hash value of the transaction data in the new block in the blockchain configuration data in the node computer that received the block addition notification. The program according to claim 2, comprising a block reception update step to add. It also has an operation reception step that accepts input operations for unit work start instructions.
In the subsequent execution setting step, when the block addition notification is sent in the block addition notification step, the unit work to be executed next based on the predetermined execution order is displayed as a unit work that can be executed. The block reception update step includes a display step of displaying the unit work to be executed next based on the predetermined execution order as a unit work that can be executed when the block addition notification is received.
In the transaction generation step, when the input operation is accepted while the executable unit work is displayed by the display step, the executable unit work is regarded as a unit work to be started and should be started. The program according to claim 4, wherein transaction data corresponding to unit work is generated. Further provided with a start instruction receiving step of receiving a unit work start instruction via the communication network.
The plurality of node computers are associated with the plurality of unit operations, respectively.
The subsequent execution setting step is
When the block addition notification is sent in the block addition notification step, a subsequent determination step of determining the unit work to be executed next based on the predetermined execution order, and a subsequent determination step.
Including a subsequent transmission step of transmitting the determined unit work start instruction to the node computer associated with the unit work.
The program according to claim 4, wherein in the transaction generation step, when a start instruction of a unit work is received by the start instruction receiving step, transaction data corresponding to the unit work is generated. The distributed system is a storage unit accessible to all of the plurality of node computers, stores order information indicating the predetermined execution order, and corresponds to each of the plurality of unit operations. Contains a storage unit that stores the identification information of the node computer from which transaction data should be generated.
In the subsequent determination step, the unit work to be executed next is determined by referring to the order information stored in the storage unit.
The program according to claim 6, wherein in the subsequent transmission step, an instruction to start the unit work to be executed next is transmitted to the node computer indicated by the identification information stored in the storage unit. The distributed system includes a storage unit that is accessible to all of the plurality of node computers and stores a plurality of transaction data templates corresponding to the plurality of unit operations.
Each transaction data template contains identification information of the approver of the start and the approver of the completion for the corresponding unit work.
In the transaction data generation step, transaction data corresponding to the unit work to be started is generated based on the transaction data template and the production information.
In the construction start approval acquisition step, a process for obtaining approval for the start of the unit work is executed based on the identification information of the approval entity of the construction start included in the transaction data corresponding to the unit work to be started.
In the completion approval acquisition step, a process for obtaining approval for completion of the unit work is executed based on the identification information of the completion approval entity included in the transaction data corresponding to the unit work started. The program described in 1. In the construction start approval acquisition step, when a plurality of approval entities are determined for the start of the unit work to be started, when it is found that the construction has been approved by all of the plurality of approval entities. It is considered that the approval of the start of construction has been obtained,
In the completion approval acquisition step, when a plurality of approval entities are determined for the completion of the unit work started, when it is found that the completion is approved by all of the plurality of approval entities. The program of claim 8, which is deemed to have been approved for completion. Each transaction data template further includes identification information for the unit work to be performed next to the corresponding unit work and identification information for the node computer that generates the transaction data corresponding to the unit work to be performed next.
In the subsequent execution setting step, the unit work start instruction indicated by the unit work identification information stored in the corresponding transaction data template is sent to the node computer indicated by the node computer identification information stored in the template. The program according to claim 8, which is transmitted. The plurality of unit operations according to any one of claims 1 to 10, which include procurement of parts necessary for the production of the product, quality control of the parts, and each production process for manufacturing the product. program. The program according to any one of claims 1 to 10, wherein the communication network is the Internet. It is a production control terminal device in a production control system that performs production control including distribution control for arranging parts necessary for product production and process control for manufacturing using the parts.
The production control system includes a plurality of production control terminal devices including the production control terminal device and a communication network connecting the plurality of production control terminals to each other, and should form a block chain for the production control. It is a distributed system
The production control terminal device is
An input unit that receives information necessary for manufacturing the product as production information,
When a start instruction of any of a plurality of unit works constituting the work subject to the production control is received, transaction data corresponding to the unit work to be started based on the start instruction is generated based on the production information. Department and
When the transaction data corresponding to the unit work to be started is generated, the construction start approval acquisition unit that executes the process for obtaining the approval for the start of the unit work, and the construction start approval acquisition unit.
After obtaining the approval to start the unit work to be started, the construction start instruction unit that issues the start instruction of the unit work, and
After the construction start instruction of the unit work to be started is issued, the work result receiving unit that receives the result information of the unit work started based on the construction start instruction, and
When the result information of the unit work started is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for the completion of the unit work is executed based on the transaction data. Approval acquisition department and
A blockchain update unit that adds a new block containing transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain after the completion approval of the unit work started is obtained.
Subsequent execution setting for starting the unit work to be executed next to the unit work based on the predetermined execution order for the plurality of unit works after the completion approval of the started unit work is obtained. Including part
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
When the approval for the completion of the unit work started is obtained, the blockchain update unit provides a new block header containing a hash value of transaction data corresponding to the unit work for which the approval for completion has been obtained. Production control terminal equipment to be added to blockchain configuration data. 13. The distributed system includes a first shared storage unit that holds transaction data corresponding to the unit work for which the completion approval has been obtained, which is accessible to all of the plurality of node computers. The production control terminal equipment described. The production control according to claim 14, wherein the distributed system further includes a second shared storage unit that is accessible to all of the plurality of node computers and holds blockchain configuration data corresponding to the blockchain. Terminal device. Each of the plurality of production control terminal devices holds the blockchain configuration data.
The blockchain update unit
When a new block containing transaction data corresponding to the unit work for which completion approval has been obtained should be added to the blockchain, data writing for storing the corresponding transaction data in the first shared storage unit. Department and
A block generation update unit that adds a block header containing a hash value of the corresponding transaction data to the blockchain configuration data when the new block should be added to the blockchain.
When the corresponding transaction data is stored in the first shared storage and a block header containing a hash value of the corresponding transaction data is added to the blockchain configuration data, the new block is added. A block addition notification unit that sends the block addition notification shown to the communication network so that other production management terminal devices in the distributed system can receive it, and
When a block addition notification indicating the addition of a new block is received via the communication network, a block reception update unit that adds a block header containing a hash value of transaction data in the new block to the blockchain configuration data is included. The production control terminal device according to claim 14. It also has an operation reception unit that accepts input operations for unit work start instructions.
When the block addition notification is sent by the block addition notification unit, the subsequent execution setting unit displays the unit work to be executed next based on the predetermined execution order as a unit work that can be executed. The block reception update unit includes a display unit that displays the unit work to be executed next based on the predetermined execution order as a unit work that can be executed when the block addition notification is received.
When the input operation is received while the feasible unit work is displayed by the display unit, the transaction generation unit sets the feasible unit work as a unit work to be started and corresponds to the unit work. The production control terminal device according to claim 16, wherein the transaction data to be generated is generated. A start instruction receiving unit for receiving a unit work start instruction via the communication network is further provided.
The plurality of production control terminal devices are associated with the plurality of unit operations, respectively.
The subsequent execution setting unit is
When the block addition notification is sent in the block addition notification unit, a subsequent determination unit that determines the unit work to be executed next based on the predetermined execution order, and the subsequent determination unit.
Including a subsequent transmission unit that transmits a start instruction of the determined unit work to the production control terminal device associated with the unit work.
The production control terminal device according to claim 16, wherein the transaction generation unit generates transaction data corresponding to the unit work when the start instruction of the unit work is received by the start instruction receiving unit. It is a production control method that performs production control including distribution control for arranging parts necessary for product production and process control for manufacturing using the parts.
Receives the design information of the product, generates the information necessary for manufacturing the product as production information based on the design information, and distributes the communication network and a plurality of production control terminal devices connected to each other by the communication network. A preparatory step to prepare for forming the blockchain for production control in the system, and
A transaction generation step that sequentially generates a plurality of transaction data corresponding to each of a plurality of unit works constituting the work subject to the production control based on the production information, and a transaction generation step.
When any transaction data is generated by the transaction generation step, a construction start approval acquisition step for executing a process for obtaining approval for the start of unit work corresponding to the generated transaction data, and a construction start approval acquisition step.
After the approval for the start of the corresponding unit work is obtained, the construction start instruction step for issuing the construction start instruction for the corresponding unit work, and the construction start instruction step.
After the construction start instruction of the corresponding unit work is issued, the work result receiving step of receiving the result information of the corresponding unit work, and
When the result information of the corresponding unit work is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for completion of the corresponding unit work is executed based on the transaction data. Completion approval acquisition step and
After the completion approval of the corresponding unit work is obtained, a blockchain update step of adding a new block containing transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain, and
After obtaining approval for the completion of the unit work that has started, the subsequent execution setting step that determines the unit work to be executed next to the unit work based on the predetermined execution order for the plurality of unit work. With
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
In the blockchain update step, when the completion approval of the unit work started is obtained, a new block header containing the hash value of the transaction data corresponding to the unit work for which the completion approval is obtained is described. Added to blockchain configuration data
In the transaction generation step, when the unit work to be executed next is determined by the subsequent execution step, transaction data corresponding to the determined unit work is generated, which is a production control method. The plurality of production control terminal devices are associated with the plurality of unit operations, respectively.
The production control method according to claim 19, wherein in the transaction generation step, any transaction data is generated in the production control terminal device associated with the unit work corresponding to the transaction data. The approval body for starting construction and the approval body for completion are predetermined for each of the plurality of unit works.
In the construction start approval acquisition step, when a plurality of approval bodies are determined for the start of the unit work corresponding to the generated transaction data, the construction start is approved by all of the plurality of approval bodies. When it is found, it is considered that the approval of the start of construction has been obtained,
In the completion approval acquisition step, when a plurality of approval entities are determined for the completion of the unit work corresponding to the generated transaction data, the completion is approved by all of the plurality of approval entities. The production control method according to claim 19, wherein when it is found, the approval of the completion is considered to be obtained. It is a production control system that performs production control including distribution control for arranging parts necessary for product production and process control for manufacturing using the parts.
Communication network and
A plurality of production control terminal devices connected to each other by the communication network are provided.
The communication network and the plurality of production control terminal devices form a distributed system that forms a blockchain for the production control.
The distributed system
A production information generation unit that receives design information of the product and generates information necessary for manufacturing the product as production information based on the design information.
A transaction generation unit that sequentially generates a plurality of transaction data corresponding to each of a plurality of unit works constituting the work subject to the production control based on the production information.
When any transaction data is generated by the transaction generation unit, a construction start approval acquisition unit that executes a process for obtaining approval for the start of unit work corresponding to the generated transaction data, and a construction start approval acquisition unit.
After obtaining the approval to start the construction of the corresponding unit work, the construction start instruction issuing department that issues the construction start instruction of the corresponding unit work, and
After the construction start instruction of the corresponding unit work is issued, the work result receiving unit that receives the result information of the corresponding unit work, and
When the result information of the corresponding unit work is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for completion of the corresponding unit work is executed based on the transaction data. Completion approval acquisition department and
A blockchain update unit that adds a new block containing transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain after the completion approval of the corresponding unit work has been obtained.
After obtaining approval for the completion of the unit work that has started, the subsequent execution setting unit that determines the unit work to be executed next to the unit work based on the execution order predetermined for the plurality of unit work. With
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
When the approval for the completion of the unit work started is obtained, the blockchain update unit provides a new block header containing a hash value of transaction data corresponding to the unit work for which the approval for completion has been obtained. Add to blockchain configuration data,
The transaction generation unit is a production control system that generates transaction data corresponding to the determined unit work when the subsequent execution setting unit determines the unit work to be executed next. A distributed system that includes a server computer and a plurality of client computers connected to each other by a communication network for production control including distribution control for arranging parts necessary for product production and process control for manufacturing using the parts. It is a program to do in
The server-side production control program to be executed by the server computer and the client-side production control program to be executed by each of the plurality of client computers are included.
The client-side production control program is applied to each of the plurality of client computers.
An input step that receives information necessary for manufacturing the product as production information,
A unit work based on the executable unit work notification is received via the communication network to notify the unit work to be executed next among the plurality of unit works constituting the work subject to the production control. When the start instruction of is received, the transaction generation step of generating the transaction data corresponding to the unit work to be started based on the start instruction based on the production information, and
When the transaction data corresponding to the unit work to be started is generated, the construction start approval acquisition step for executing the process for obtaining the approval for the start of the unit work, and the construction start approval acquisition step.
After the approval for the start of the unit work to be started is obtained, the start instruction step for issuing the start instruction for the unit work and the start instruction step.
After the construction start instruction of the unit work to be started is issued, the work result receiving step of receiving the result information of the unit work started based on the construction start instruction, and the work result receiving step.
When the result information of the unit work started is obtained, the result information is incorporated into the generated transaction data, and then a process for obtaining approval for the completion of the unit work is executed based on the transaction data. Approval acquisition step and
After the completion approval of the unit work started is obtained, the block addition notification indicating the addition of a new block containing the transaction data corresponding to the unit work for which the completion approval has been obtained to the blockchain is given. The block addition notification step to be transmitted to the server computer via the communication network is executed.
The server-side production control program is a program for causing the server computer to form a blockchain for the production control, and causes the server computer to form a blockchain.
Upon receiving the block addition notification via the communication network, a blockchain update step of adding a new block indicated by the block addition notification to the blockchain, and
Based on a predetermined execution order for the plurality of unit works, the subsequent execution setting step of sending an executable unit work notification to notify the unit work to be executed next among the plurality of unit works is executed. Let me
The blockchain is a blockchain formed by concatenating transaction data corresponding to a unit work for which completion approval has been obtained and a block header containing a hash value of the transaction data in the order in which completion approval has been obtained. Including configuration data
In the blockchain update step, when the completion approval of the unit work started is obtained, a new block header containing the hash value of the transaction data corresponding to the unit work for which the completion approval is obtained is described. A program that is added to the blockchain configuration data.

Images