WO2011052084A1

WO2011052084A1 - Production management apparatus, production management system, production management program, and production management method

Info

Publication number: WO2011052084A1
Application number: PCT/JP2009/068727
Authority: WO
Inventors: 恒裕南里; 実鍋山; 哲二家合; 浩一佐藤; 哲也上原; 太加志内田; 昌浩根岸; 昭治鈴木; 肇長谷川; 悟中野
Original assignee: 富士通フロンテック株式会社
Priority date: 2009-10-30
Filing date: 2009-10-30
Publication date: 2011-05-05
Also published as: JP5355706B2; JPWO2011052084A1

Abstract

Provided is a production management apparatus capable of easily reflecting the progress of a process for manufacturing parts on the manufacturing plan for a product. When a part process management unit (1d) receives the progress information of a manufacturing line (5), which is sent from a terminal device (2) every time when a part passes a predetermined checkpoint, the part process management unit (1d) updates the deadline of the part which is included in part management information stored in an article management information storage unit (1a) on the basis of the received progress information. After the part process management unit (1d) updates the part management information, a reserving unit (1e) reserves the part for the product on the basis of the updated part management information and requirement information indicating the number of required parts for the product which is stored in the article management information storage unit (1a), generates reserve statement information indicating the reserve result, and stores the reserve statement information into a part reserve statement storage unit (1b). After the reserving unit generates the reserve statement information, a production plan management unit (1f) generates production plan information to be used for managing the production schedule for the product on the basis of the reserve statement information stored in the part reserve statement storage unit (1b).

Description

Production management apparatus, production management system, production management program, and production management method

The present invention relates to a production management apparatus, a production management system, a production management program, and a production management method for managing product production.

Conventionally, in the field of manufacturing industry, production management systems for managing production of products are used. By using the production management system, it is possible to efficiently manage the procurement, production, and distribution of parts and materials. There is SCM (Supply Chain Management) as a production management method used in the production management system. The SCM manages a series of processes in product production between companies and departments, and balances the balance between supply and demand. This supports the optimization of production processes from parts procurement to logistics.

Here, in many cases, a system used for business is provided separately between each department in a company or between companies. In that case, each department manages information by a separate business system. For this reason, when information is to be shared between departments or the like, it is necessary to synchronize information by transferring data managed by one system to the other system by batch processing. For example, there is a method in which order information managed in a sales department database is transferred to a factory at night to create a production plan and obtain a delivery date response (see, for example, Patent Document 1). Also, usually, each company often has its own internal network, and it is difficult to directly link information between companies. On the other hand, a method in which the ordering company obtains the progress status of the product processing acquired at the ordering company via a FAX device, etc., and enables the work status at the ordering company to be indirectly confirmed via a person. (See, for example, Patent Document 2).

Japanese Patent Laid-Open No. 2003-044550 Japanese Patent Application Laid-Open No. 09-319795

However, in the method described in Patent Document 1, there is a time lag in sharing information (for example, a time lag of 1 day if data is transferred daily). On the other hand, in order to perform more efficient production management, it is desirable to be able to immediately grasp the results of supply and demand between departments and companies. For this reason, an environment in which information can be shared with less time lag between departments and between companies is required. In particular, the point of delivery of a part from a supplier that supplies the part is important because it is the starting point for a product manufacturing plan. For example, when the supply of parts is stagnant or the supply of parts is accelerated, it is desirable from the viewpoint of improving the use efficiency of production resources that the situation can be quickly grasped and the product manufacturing plan can be reviewed.

Moreover, in the method described in Patent Document 2, it is necessary to input progress information to the system based on documents obtained by the worker of the ordering company via the FAX apparatus. In other words, information managed separately by both companies is shared through people. For this reason, there is a problem that information may not be properly shared due to information shift due to an artificial input error or the like. Further, in this case, the worker of the ordering company needs to make an inquiry to the ordering company to correct the data. For this reason, there is a problem that the burden on the worker is large.

The present invention has been made in view of these points, and a production management device, a production management system, a production management program, and production management capable of easily reflecting the progress of a part manufacturing process in a product manufacturing plan. It aims to provide a method.

In order to solve the above problems, a production management device is provided. This production management apparatus includes a part process management unit, an allocation processing unit, and a production plan management unit. When the part process management unit receives the progress information of the manufacturing process transmitted each time the part passes a predetermined checkpoint from the terminal device that manages the manufacturing process of the part, the part process management unit stores the article management information based on the received progress information. The delivery date of the part included in the part management information stored in the part is updated. When the part process management unit updates the part management information, the allocation processing unit updates the product based on the updated part management information and the requirement information indicating the required number of parts for the product stored in the article management information storage unit. The allocation details information indicating the allocation result is generated and stored in the component allocation details storage unit. When the allocation processing unit generates the allocation detail information, the production plan management unit generates production plan information for managing the product manufacturing schedule based on the allocation detail information stored in the part allocation detail storage unit.

Also, a production management system is provided to solve the above problems. This production management system has a terminal device and a production management device. The terminal device stores the component identification information, communicates with the wireless tag attached to the component, and stores the component identification information and the communication device stored in the communication device provided at a predetermined check point of the component manufacturing line. The progress information acquisition unit generates the progress information including the component identification information, the communication device identification information, and the time stamp indicating the time when the component has passed the checkpoint, and transmits the generated progress information. Is provided. The production management apparatus includes a parts process management unit, an allocation processing unit, and a production plan management unit. When the part process management unit receives the progress information from the terminal device, the part process management unit updates the delivery date of the part included in the part management information stored in the article management information storage unit based on the received progress information. When the part process management unit updates the part management information, the allocation processing unit updates the product based on the updated part management information and the requirement information indicating the required number of parts for the product stored in the article management information storage unit. The allocation details information indicating the allocation result is generated and stored in the component allocation details storage unit. When the allocation processing unit generates the allocation detail information, the production plan management unit generates production plan information for managing the product manufacturing schedule based on the allocation detail information stored in the part allocation detail storage unit.

Also provided is a production management program that causes a computer to execute the same function as the production management device. In addition, a production management method for performing the same processing as that of the production management apparatus is provided.

According to the production management device, the production management system, the production management program, and the production management method, the progress of the part manufacturing process can be easily reflected in the product manufacturing plan.
These and other objects, features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings which illustrate preferred embodiments by way of example of the present invention.

It is a figure which shows the production management apparatus which concerns on 1st Embodiment. It is a figure which shows the whole structure of the production management system which concerns on 2nd Embodiment. It is a figure which shows the structure of a component manufacturing line. It is a figure which shows the hardware constitutions of a management server. It is a 1st figure which shows the function structure of a management server. It is a 2nd figure which shows the function structure of a management server. It is a 3rd figure which shows the function structure of a management server. It is a 4th figure which shows the function structure of a management server. It is a figure which shows the function structure of a line terminal device. It is a figure which shows the structure of a kanban. It is a figure which shows the example of a data structure of an article | item master. It is a figure which shows the example of a data structure of an article | item structure table. It is a figure which shows the data structure example of an order receipt table. It is a figure which shows the example of a data structure of a components requirement table. It is a figure which shows the example of a data structure of a component note remaining table. It is a figure which shows the example of a data structure of a components inventory table. It is a figure which shows the example of a data structure of a product standard process table. It is a figure which shows the example of a data structure of a components standard process table. It is a figure which shows the example of a data structure of a process performance management table. It is a figure which shows the example of a data structure of an update figure number table. It is a figure which shows the example of a data structure of the allocation object figure number table. It is a figure which shows the example of a data structure of an allocation detail table. It is a figure which shows the example of a data structure of an allocation history table. It is a figure which shows the example of a data structure of a surface alignment object management table. It is a figure which shows the example of a data structure of a component surface alignment table. It is a figure which shows the example of a data structure of a manufacturing plan management table. It is a figure which shows the example of a data structure of a delivery date reply table. It is a figure which shows the structure of the work area for allocation processes. It is a figure which shows the example of a data structure of a gate passage history table. It is a flowchart which shows a note remaining delivery date update process. It is a sequence diagram which shows the acquisition process of gate passage information. It is a flowchart which shows a production management process. It is a flowchart which shows an update figure number registration process. It is a flowchart which shows the allocation object figure number generation process. It is a flowchart which shows the allocation process. It is a flowchart which shows a reserve allocation pre-processing. It is a flowchart which shows a reserve allocation process. It is a flowchart which shows a reserve allocation process. It is a flowchart which shows quantity allocation processing. It is a flowchart which shows a surface alignment object extraction process. It is a flowchart which shows a surface alignment process. It is a flowchart which shows a manufacturing management information generation process. It is a flowchart which shows a delivery date reply information generation process. It is a figure which shows a delivery date reply screen. It is a figure which shows reflection from the collection of various data to a production plan. It is a figure which shows the information cooperation between departments and a supplier.

Hereinafter, the present embodiment will be described in detail with reference to the drawings.
[First Embodiment]
FIG. 1 is a diagram illustrating a production management apparatus according to the first embodiment. The production management apparatus 1 performs product production management in a manufacturing company (manufacturer). The production management device 1 can communicate with a terminal device 2 that manages a manufacturing process of components used for production of a product. The parts are manufactured, for example, on a manufacturing line 5 of a factory of a parts supply company (supplier).

The production management apparatus 1 includes an article management information storage unit 1a, a part allocation detail storage unit 1b, a production plan information storage unit 1c, a part process management unit 1d, an allocation processing unit 1e, and a production plan management unit 1f.
The article management information storage unit 1a stores master information (article master) of products and parts and a bill of materials (BOM: Bills Of Materials) that defines the parts configuration of the product. The bill of materials can be used for requirement calculation in material requirements planning (MRP). The required number of each part obtained for the product by the required amount calculation is the required amount information. Further, the article management information storage unit 1a stores part management information including the delivery date of the parts for which the manufacturing order is being placed.

The part allocation detail storage unit 1b stores allocation detail information that is an allocation result of parts necessary for manufacturing a product.
The production plan information storage unit 1c stores production plan information including a product production schedule.

The part process management unit 1 d updates the delivery date of the corresponding part included in the part management information stored in the article management information storage unit 1 a based on the progress information of the part manufacturing process received from the terminal device 2.

The allocation processing unit 1e allocates parts to the product based on the part management information updated by the part process management unit 1d and the requirement information stored in the article management information storage unit 1a, and generates allocation detail information. Stored in the part allocation details storage unit 1b.

The production plan management unit 1f generates production plan information for managing the production schedule of the product based on the allocation details information stored in the parts allocation details storage unit 1b.
The terminal device 2 includes a progress information acquisition unit 2a. The progress information acquisition unit 2 a generates progress information indicating the process progress of a part every time the part passes a predetermined check point in the production line 5, and transmits the progress information to the production management device 1.

The check point in the production line 5 can be provided by a communication device that communicates with a wireless tag, for example. Specifically, first, a wireless tag storing component identification information is preliminarily attached to a component in progress. Then, for example, a communication device is provided at each check point, with each location that passes when the manufacturing process 5a, 5b, 5c, which is a subdivision of the manufacturing line 5 is completed and moves to the next process, as a check point. That is, as the check points, for example, an entrance of the manufacturing process 5a, between the manufacturing processes 5a and 5b, between the manufacturing processes 5b and 5c, and an exit of the manufacturing process 5c can be considered. Then, the communication device transmits the component identification information and the communication device identification information to the terminal device 2 at the timing when the component receives the component identification information from the wireless tag attached to the component after passing through each checkpoint. To do. The progress information acquisition unit 2a can acquire in which process the in-process component is in by receiving the component identification information and the communication device identification information. Further, the progress information acquisition unit 2a can generate progress information based on the information received from the communication device.

According to the production management device 1, the part process management unit 1d receives the progress information of the part manufacturing process from the terminal device 2 every time the part passes a predetermined checkpoint in the manufacturing line 5. Based on the received progress information, the parts process management unit 1d updates the delivery date of the corresponding part included in the part management information stored in the article management information storage unit 1a. Then, the allocation processing unit 1e allocates parts to the product based on the part management information updated by the part process management unit 1d and the required amount information stored in the article management information storage unit 1a, and the allocation details information It is generated and stored in the part allocation details storage unit 1b. Further, the production plan management unit 1f generates production plan information for managing the production schedule of the product based on the allocation detail information stored in the parts allocation detail storage unit 1b.

For example, the production line 5 has three production steps 5a, 5b, and 5c that are sequentially performed to produce parts. Here, it is conceivable that any of the manufacturing processes 5a, 5b, 5c is not completed on the scheduled date or completed earlier than the scheduled date due to material procurement or trouble.

The part process management unit 1d immediately acquires such progress information in the production line 5 via the terminal device 2 and reflects it in the delivery date of the part included in the part management information. The allocation processing unit 1e reallocates parts based on the part management information updated by the part process management unit 1d, and stores the result in the part allocation detail storage unit 1b. Then, the production plan management unit 1f recreates a product production plan based on the re-allocation result.

This makes it possible to easily and immediately reflect changes in the progress of the production line 5 in the product production plan. In addition, by using the production plan reviewed in accordance with the immediate change of the progress status in this way, work instructions to the product manufacturing factory can be accurately given and the utilization efficiency of the company's resources can be improved. It is also possible to provide a highly accurate delivery date response to customers who deliver products.

In the following embodiment, a more specific system for supporting production management between a product manufacturing company and a plurality of suppliers will be described.
[Second Embodiment]
FIG. 2 is a diagram illustrating an overall configuration of a production management system according to the second embodiment. This production management system is constructed between the product manufacturing company 20, the center 30, and the

suppliers

40, 40a, 40b. The sales terminal device 21, the ordering terminal device 22, the warehouse terminal device 26, the management server 100 of the center 30, the terminal devices 41 and 42 of the

suppliers

40, 40 a and 40 b, and the line terminal device 200 are connected to the network 10. Connected through. The network 10 is, for example, the Internet, a VPN (Virtual Private Network), and other dedicated communication networks provided for the production management system.

The product manufacturing company 20 manufactures the product 50 according to the order from the customer and delivers it to the customer. The product manufacturing company 20 manufactures a product 50 by assembling and processing parts supplied from the

suppliers

40, 40a, and 40b. The product manufacturing company 20 stores the parts in the warehouse 25, and orders the parts from the

suppliers

40, 40a, and 40b regularly or as necessary (for example, when there is a shortage). The product manufacturing company 20 can perform these operations using the sales terminal device 21, the ordering terminal device 22, and the warehouse terminal device 26.

The sales terminal device 21 is an information processing device used by employees in the sales department. The sales terminal device 21 is used to input the contents of orders received from customers to the production management system.
The ordering terminal device 22 is an information processing device used by employees in the material department. The ordering terminal device 22 is used for ordering parts from the

suppliers

40, 40a, and 40b.

The warehouse terminal device 26 is a terminal installed in the warehouse 25. The warehouse terminal device 26 manages the inventory of parts stored in the warehouse 25. For example, information such as that a new part has been delivered to the warehouse 25 and that a part has been delivered from the warehouse 25 is collected. In order to obtain information for that purpose, a tag reader that communicates with, for example, a wireless tag attached to a warehousing product or a warehousing product is provided at a key point (a warehousing point or a warehousing point) in the warehouse 25. For example, when the warehouse terminal device 26 receives information related to the goods received from a tag reader installed at the warehouse point, the warehouse terminal apparatus 26 detects that the corresponding goods have been received. The same applies to the goods delivered.

The center 30 provides each function of the production management system to the product manufacturing company 20 and the

suppliers

40, 40a, and 40b by the management server 100.
The management server 100 centrally manages various data necessary for the operation of the production management system. The management server 100 executes various processing functions realized in the production management system. Furthermore, the management server 100 provides a GUI (Graphical User Interface) for making these processing functions available to the employees of the product manufacturing company 20 and the

suppliers

40, 40a, and 40b.

The

suppliers

40, 40 a, and 40 b accept part orders from the product manufacturing company 20 via the management server 100. The

suppliers

40, 40 a, 40 b manufacture parts in accordance with the order contents and deliver them to the warehouse 25 of the product manufacturing company 20. Further, the

suppliers

40, 40 a, 40 b notify the product manufacturing company 20 of the progress of the parts manufacturing process via the management server 100.

The supplier 40 can perform these operations using the terminal devices 41 and 42 and the line terminal device 200.
The terminal devices 41 and 42 are information processing devices used by employees of the supplier 40. The employee of the supplier 40 can receive an order for parts from the product manufacturing company 20 using the terminal devices 41 and 42.

The line terminal device 200 is provided in the component manufacturing line 45. The parts manufacturing line 45 is a manufacturing line for manufacturing parts supplied by the supplier 40 to the product manufacturing company 20. The line terminal device 200 acquires the progress information of the manufacturing process in the component manufacturing line 45 in real time and transmits it to the management server 100.

Here, the

suppliers

40 a and 40 b have the same configuration as the supplier 40.
The management server 100 may be composed of a plurality of server devices in order to improve responsiveness and reliability. For example, a Web server that provides a GUI to the Web browsers of the terminal devices of the product manufacturing company 20 and the

suppliers

40, 40a, and 40b, and functions such as product order / part order / inventory management / manufacturing management / shipment management are provided. It may be configured by an AP (Application) server and a DB (DataBase) server that stores and manages various data used in the production management system. Here, when a Web server is used to provide a GUI, the Internet can be considered as the network 10. In that case, in order to improve the confidentiality of communication between the Web server and each terminal device, it is conceivable to use, for example, HTTPS (Hypertext Transfer Protocol over Secure Socket Layer).

Also, it is conceivable that the above functions can be used on the single system platform provided by the management server 100 in the sales terminal device 21, the ordering terminal device 22, and the warehouse terminal device 26. In other words, even if a dedicated business terminal device is not provided in each department, the management server 100 accepts each employee's password input via each terminal device, so that a business menu corresponding to the department to which the employee belongs can be used. And The management server 100 can also function as an LDAP (Lightweight Directory Access Protocol) server that manages information for that purpose (information that defines the association between an employee ID (Identifier) and a department to which the employee belongs). Moreover, you may provide a LDAP server in the product manufacturing company 20 separately from a security viewpoint. In this regard, the same configuration can be applied to the

suppliers

40, 40a, and 40b.

In this way, if the management server 100 is accessed from a general-purpose computer that can communicate with the management server 100 with the ID or password of each employee, the business menu corresponding to the department to which the employee belongs can be used. Therefore, convenience is good.

FIG. 3 is a diagram showing a configuration of a parts production line. In the component manufacturing line 45, the progress status of the component manufacturing process is managed by the Kanban 60. The kanban 60 has a memory for storing various information for that purpose and a wireless communication function for transmitting the information. The kanban 60 is provided in a parts box 70 for transporting in-process parts between the process lines. Details of the kanban 60 will be described later.

The component manufacturing line 45 includes a line terminal device 200, a communication device 300,

gates

310, 320, 330, 340, a mobile terminal device 350, and a printer 360.
The line terminal device 200 has the same configuration as that described with the same reference numerals in FIG. The line terminal device 200 communicates with the communication device 300 via a wireless or wired network.

The communication device 300 communicates with the line terminal device 200, the

gates

310, 320, 330, and 340 and the mobile terminal device 350 through a wireless or wired network.
The

gates

310, 320, 330, and 340 are gates provided to divide each process line of the component manufacturing line 45.

Gates

310, 320, 330, and 340 correspond to the checkpoints described in the first embodiment.

The gate 310 is provided at the entrance of the A process line which is the first process line.
The gate 320 is provided at the entrance of the B process line which is the second process line (exit of the A process line).

The gate 330 is provided at the inlet of the C process line which is the third process line (the outlet of the B process line).
The gate 340 is provided at the exit of the C process line. At the end of the gate 340, the completed part is packed. The packed part 80 is conveyed toward the warehouse 25.

The

gates

310, 320, 330, and 340 have

communication devices

311, 321, 331, and 341.
The

communication devices

311, 321, 331, 341 communicate wirelessly with the Kanban 60. The

communication devices

311, 321, 331, and 341 transmit the information received from the Kanban 60 and the gate identification information given in advance to the

gates

310, 320, 330, and 340 to the line terminal device 200 via the communication device 300.

The portable terminal device 350 is a small terminal device for notifying the line terminal device 200 of a progress notification point in the middle of each process line or a failure in a part process. The mobile terminal device 350 communicates with the Kanban 60 to acquire information necessary for failure notification and the like, and transmits the information to the line terminal device 200 via the communication device 300. As the mobile terminal device 350, for example, a handy terminal can be used.

The printer 360 rewrites information written in the Kanban 60 and information held in the memory of the Kanban 60. By using the printer 360, the Kanban 60 can be reused for each part to be manufactured.

Although the supplier 40 has been described, the

suppliers

40 a and 40 b have the same configuration as the supplier 40.
FIG. 4 is a diagram illustrating a hardware configuration of the management server. The management server 100 includes a central processing unit (CPU) 101, a read only memory (ROM) 102, a random access memory (RAM) 103, a hard disk drive (HDD) 104, a graphic processing device 105, an input interface 106, and a recording medium reading device. 107 and a communication interface 108.

The CPU 101 controls the entire management server 100.
The ROM 102 stores a BIOS (Basic Input / Output System) program on the management server 100.

The RAM 103 temporarily stores at least a part of an OS (Operating System) program and application software (hereinafter referred to as an application) program to be executed by the CPU 101. The RAM 103 stores various data necessary for processing by the CPU 101.

The HDD 104 stores an OS program and an application program. The HDD 104 stores various data necessary for processing by the CPU 101. Instead of the HDD 104 (or in combination with the HDD 104), other types of storage devices such as SSD (Solid State Drive) may be used.

The graphic processing device 105 is connected to the monitor 11. The graphic processing device 105 displays an image on the screen of the monitor 11 in accordance with a command from the CPU 101.
The input interface 106 is connected to the keyboard 12 and the mouse 13. The input interface 106 transmits a signal sent from the keyboard 12 or the mouse 13 to the CPU 101.

The recording medium reading device 107 is a reading device that reads data stored in the recording medium 14. For example, a function that the management server 100 should have can be realized by causing a computer to execute a program describing the processing content of the function. Such a program can be recorded on a computer-readable recording medium 14 and distributed. The program may be stored from the recording medium 14 in a program distribution server device (not shown) connected to the network 10. In this case, the management server 100 can download the program from the program distribution server device via the network 10.

As the recording medium 14, for example, a magnetic recording device, an optical disk, a magneto-optical recording medium, or a semiconductor memory can be used. Magnetic recording devices include HDDs, flexible disks (FD), magnetic tapes, and the like. Optical discs include CD (Compact Disc), CD-R (Recordable) / RW (ReWritable), DVD (Digital Versatile Disc), DVD-R / RW / RAM, and the like. Magneto-optical recording media include MO (Magneto-Optical disk). Semiconductor memories include flash memories such as USB (Universal （Serial Bus) memories.

The communication interface 108 is connected to the network 10. The communication interface 108 performs data communication with other information processing apparatuses via the network 10.
The sales terminal device 21, the ordering terminal device 22, the warehouse terminal device 26, the terminal devices 41 and 42, and the line terminal device 200 can also be realized by the same hardware configuration as that of the management server 100.

FIG. 5 is a first diagram showing a functional configuration of the management server. The management server 100 includes a management information storage unit 110, an ordered / ordered product management unit 120, a parts allocation processing unit 130, and a production plan management unit 140. These functions are realized by the CPU 101 executing a predetermined program. All or at least a part of these functions may be realized by dedicated hardware.

The management information storage unit 110 centrally stores and manages management information necessary for the operation of the production management system. The management information storage unit 110 includes the article management information storage unit 1a, the parts allocation details storage unit 1b, and the production plan information storage unit 1c described in the first embodiment. Each piece of information stored in the management information storage unit 110 is referred to / updated by the ordered / ordered product management unit 120, the parts allocation processing unit 130, and the production plan management unit 140.

The ordered product management unit 120 accepts an order input for a product from the sales terminal device 21. The order management unit 120 orders parts to the

suppliers

40, 40 a, 40 b based on the order input from the ordering terminal device 22, the product production plan, and the parts inventory status. The order-ordered product management unit 120 receives information related to parts received from the warehouse terminal device 26 into the warehouse 25 and parts delivered from the warehouse 25. The ordered / ordered product management unit 120 accepts the progress information of the manufacturing process in the

suppliers

40, 40a, and 40b for the ordered parts that are being manufactured (ordered parts). The ordered product management unit 120 updates management information (referred to as component management information) related to components stored in the management information storage unit 110 based on the received information.

When the parts management information stored in the management information storage unit 110 is updated by the order management unit 120, the parts allocation processing unit 130 determines whether it is necessary to allocate or reallocate the ordered product. to decide. Then, the part allocation processing unit 130 executes a part allocation process for the ordered product for which it is determined that allocation or re-allocation is necessary. The part allocation processing unit 130 stores the allocation result in the management information storage unit 110.

The production plan management unit 140 refers to the management information storage unit 110 and performs a production plan for a product that has been newly allocated or re-allocated based on the allocation result by the component allocation processing unit 130. Based on the result, the production plan management unit 140 issues a product manufacturing instruction, a delivery date reply, a product shipping instruction, etc. to the product factory of the product manufacturing company 20.

Hereinafter, functional configurations of the ordering / ordering item management unit 120, the parts allocation processing unit 130, and the production plan management unit 140 will be described in detail.
First, the functional configuration of the ordered / ordered product management unit 120 will be described.

FIG. 6 is a second diagram showing the functional configuration of the management server. The management information storage unit 110 includes an article master storage unit 111, a component requirement information storage unit 112, a part order information storage unit 113, a component inventory information storage unit 114, and an article process information storage unit 115.

The article master storage unit 111 stores an article master and a parts table.
The component requirement information storage unit 112 stores component requirement information indicating the required amount of components for the ordered product.

The part ordering information storage unit 113 stores part ordering information indicating the quantity and delivery date of the remaining parts ordered from the

suppliers

40, 40a, and 40b.
The parts inventory information storage unit 114 stores inventory information for managing inventory parts stored in the warehouse 25.

The article process information storage unit 115 stores part process information for managing the progress status of the remaining parts in the

suppliers

40, 40a, and 40b.
The ordered / ordered product management unit 120 includes an order management unit 121, a part order management unit 122, an inventory management unit 123, and a part process management unit 124.

The order management unit 121 generates order information based on an order input from the sales terminal device 21 and stores it in the component requirement information storage unit 112. Then, the order management unit 121 refers to the article master storage unit 111 to calculate the required amount of parts for the ordered product, generates the component requirement information, and stores it in the component requirement information storage unit 112.

The part ordering management unit 122 generates part ordering information based on the ordering input from the ordering terminal device 22. Further, the part order management unit 122 generates part ordering information periodically based on the production plan or according to the inventory status of the parts stock stored in the parts stock information storage unit 114. The part ordering information is information for managing the ordered remaining parts, and is a part of the part management information. The part order management unit 122 stores the generated part order information in the part order information storage unit 113.

The inventory management unit 123 reflects the newly received goods and the information of the delivered goods in the inventory information stored in the parts inventory information storage unit 114 based on the goods storage / reception information received from the warehouse terminal device 26. To do. The inventory information is information for managing parts inventory, and is part of the parts management information. That is, parts ordering information and inventory information correspond to parts management information.

The part process management unit 124 updates the manufacturing process of the remaining parts stored in the article process information storage unit 115 based on the gate passage information received from the line terminal device 200. The gate passage information corresponds to the progress information described in the first embodiment. Further, the part process management unit 124 updates the delivery date of the remaining part included in the part ordering information stored in the part ordering information storage unit 113 in accordance with the progress of the manufacturing process of the remaining part. However, the relational line between the part order information storage unit 113 and the part process management unit 124 is omitted.

Next, the functional configuration of the part allocation processing unit 130 will be described.
FIG. 7 is a third diagram illustrating a functional configuration of the management server. The management information storage unit 110 includes an article master storage unit 111, a component requirement information storage unit 112, a component order information storage unit 113, a component inventory information storage unit 114, an allocation target component information storage unit 116, and a component allocation specification storage unit 117. . The article master storage unit 111, the component requirement information storage unit 112, the component order information storage unit 113, and the component inventory information storage unit 114 are the same as those described with the same reference numerals in FIG.

The allocation target part information storage unit 116 stores a management code (hereinafter referred to as a figure number) of an article to be allocated or re-allocated.
The part allocation detail storage unit 117 stores a part allocation detail that is a result of allocation of parts for a product.

The parts allocation processing unit 130 includes an allocation target figure number acquisition unit 131, an allocation method determination unit 132, a reserve allocation processing unit 133, and a quantity allocation processing unit 134.
The allocation target figure number acquisition unit 131 refers to the component requirement information storage unit 112, the component order information storage unit 113, and the component inventory information storage unit 114, and in the component requirement information, inventory information, and component ordering information, Extract the updated record (update record). The allocation target figure number acquisition unit 131, when acquiring the figure number included in the update record, stores it in the allocation target part information storage unit 116.

The allocation method determination unit 132 refers to the allocation target figure number stored in the allocation target component information storage unit 116 and identifies a component to be allocated. Then, the allocation method determination unit 132 refers to the article master storage unit 111 and determines whether the allocation method for the part is a reserve allocation or a quantity allocation. In the case of reserve allocation, the allocation method determination unit 132 outputs the allocation target figure number to the reserve allocation processing unit 133. In the case of quantity allocation, the allocation method determination unit 132 outputs the allocation target figure number to the quantity allocation processing unit 134.

Here, reserve allocation is an allocation method in which a part once allocated to a product is maintained in a state allocated to the product. That is, when reserving a certain part, if a reserve allocation result already exists for the part, the shortage is additionally allocated in addition to the reserve allocation result. In addition, the reserved parts are not allocated to other products in principle. For this reason, it is suitable for the case where it is possible to reliably secure a component having a large fluctuation in required amount.

On the other hand, quantity allocation is an allocation method for reallocating all necessary parts when a part is re-allocated. If you use quantity reservation, depending on the progress of the manufacturing process of the ordered parts, such as when the delivery date of the remaining parts is advanced or when the delivery date of the remaining parts is delayed, Can be flexibly changed. For this reason, it is suitable when using a component whose delivery date is easy to move around.

The allocation source indicates a holding source such as an inventory or a stock that includes the corresponding part or replacement part in an available manner.
Based on the allocation target figure number acquired from the allocation method determination unit 132, the reserve allocation processing unit 133 is based on the article master storage unit 111, the component requirement information storage unit 112, the component order information storage unit 113, the component inventory information storage unit 114, and Referring to the part allocation detail storage unit 117, reserve allocation processing for the part indicated by the corresponding figure number is performed.

Based on the allocation target figure number acquired from the allocation method determination unit 132, the quantity allocation processing unit 134 includes an article master storage unit 111, a component requirement information storage unit 112, a component order information storage unit 113, a component inventory information storage unit 114, and Referring to the part allocation detail storage unit 117, the quantity allocation process for the part indicated by the corresponding figure number is performed.

The management server 100 has an allocation processing work area 150. The allocation processing work area 150 is a temporary storage area used by the reserve allocation processing unit 133 and the quantity allocation processing unit 134 for allocation processing. Details of the allocation processing work area 150 will be described later.

Next, the functional configuration of the production plan management unit 140 will be described.
FIG. 8 is a fourth diagram illustrating a functional configuration of the management server. The management information storage unit 110 includes a part allocation detail storage unit 117, a part surface alignment information storage unit 118, and a delivery date response information storage unit 119. The parts allocation detail storage unit 117 has the same configuration as that described with the same reference numerals in FIG.

The part surface alignment information storage unit 118 stores component surface alignment information for managing the time when all the parts necessary for manufacturing the product are in the warehouse 25 and the manufacture of the product can be started. The component surface alignment information storage unit 118 stores manufacturing plan management information for managing the manufacturing process of the factory, which is generated based on the component surface alignment information.

The delivery date response information storage unit 119 stores delivery date response information indicating the product delivery date.
The production plan management unit 140 includes a surface alignment information update processing unit 141, a manufacturing management unit 142, a delivery date response information generation unit 143, and a delivery date response processing unit 144.

The surface alignment information update processing unit 141 extracts the update record in the component allocation details stored in the component allocation details storage unit 117, generates the component surface alignment information for the allocation target product, and stores it in the component surface alignment information storage unit 118. Store.

The manufacturing management unit 142 generates manufacturing plan management information based on the component surface alignment information stored in the component surface alignment information storage unit 118 and stores it in the component surface alignment information storage unit 118. Further, the manufacturing management unit 142 transmits a product manufacturing instruction to the factory based on the manufacturing plan management information.

The delivery date response information generation unit 143 generates delivery date response information based on the component surface alignment information and the manufacturing plan management information stored in the component surface alignment information storage unit 118, and stores it in the delivery date response information storage unit 119.

When the delivery date reply processing unit 144 receives a delivery date reply request from the sales terminal device 21 or the like, the delivery date reply processing unit 144 delivers the delivery date to the monitor connected to the request source terminal device based on the delivery date reply information stored in the delivery date reply information storage unit 119. Output the answer screen.

Next, the functional configuration of the line terminal device 200 installed in the component manufacturing line 45 of the supplier 40 will be described.
FIG. 9 is a diagram illustrating a functional configuration of the line terminal device. The line terminal device 200 includes a gate passage information storage unit 210, a passage information reception unit 220, and a passage information transmission unit 230. These functions are realized by the CPU of the line terminal device executing a predetermined program. Note that all or at least a part of these functions may be realized by dedicated hardware.

The gate passage information storage unit 210 stores gate passage information indicating the passage state of the

gates

310, 320, 330, and 340 of the Kanban 60.
The passage information receiving unit 220 receives the component identification information, the gate identification information, and the time stamp when the component has passed through each gate from the

gates

310, 320, 330, and 340 via the communication device 300, and the gate passage information storage unit 210. To store. Note that the passage information receiving unit 220 may set, as the gate passage information, the part identification information and the time stamp when the gate identification information is received from the

gates

310, 320, 330, and 340.

The passage information transmission unit 230 transmits the gate passage information stored in the gate passage information storage unit 210 to the management server 100.
FIG. 10 is a diagram showing the configuration of the kanban. The kanban 60 has a form part 61 and a wireless tag part 62.

The form section 61 is an area where a character string indicating the detailed information of the ordered part is printed. The form section 61 includes, for example, a command ID for managing the order contents on the supplier 40 side, a user name indicating the name of the supplier supplier, an item name indicating the name of the part, and an order name for managing the order contents at the product manufacturing company. Character string indicating information such as order number, figure number of corresponding part and figure number-version number, order number indicating order quantity, issue date indicating the date when Kanban 60 was issued, scheduled delivery date indicating delivery date, etc. Is printed. The operator of the component manufacturing line 45 can confirm the type and delivery date of the components stored in the component box 70 by visually recognizing the character string printed on the form unit 61.

The wireless tag unit 62 is a communication device that wirelessly communicates with the

communication devices

311, 321, 331, and 341. The wireless tag unit 62 includes a memory. The wireless tag unit 62 stores the same information (including at least the command ID) as the information printed on the form unit 61 in this memory. Communication between the wireless tag unit 62 and the

communication devices

311, 321, 331, and 341 can be realized by, for example, RFID (Radio Frequency IDentifier) technology.

FIG. 11 is a diagram showing an example of the data structure of the article master. The article master 111 a is stored in advance in the article master storage unit 111. The item master 111a is provided with items including an item ID, an item name, an item number, a version number item, and an allocation category item. Information arranged in the horizontal direction of each item is associated with each other to indicate information related to one article.

In the item indicating the item ID, identification information for uniquely identifying the item is set. In the item indicating the product name, information indicating the name of the product is set. In the item indicating the figure number, information indicating the figure number of the article is set. In the item indicating the version number, a version number indicating the version of the figure number is set. Different figure numbers (revised editions, etc.) of the same article can be managed depending on the version number. In the item indicating the allocation category, when the article is a part, information indicating whether the part is a reserve allocation target or a quantity allocation target is set.

In the article master 111a, for example, information that the article ID is “PD001”, the article name is “automatic transaction apparatus Z1”, the figure number is “DR001”, the version number is “V01”, and the allocation category is “−” (no setting). Is set. Since the article indicated by the product name “automatic transaction apparatus Z1” is a product manufactured by the product manufacturing company 20 and delivered to the customer, the provision category is not set.

In the article master 111a, for example, information that the article ID is “PD011”, the article name is “part Y11”, the drawing number is “DR011”, the version number is “V01”, and the allocation classification is “reserve allocation” is set. The This indicates that the article indicated by the product name “part Y11” is a part, and reserve allocation is performed when the part is allocated.

In the article master 111a, for example, information that the article ID is “PD012”, the article name is “part Y12”, the drawing number is “DR012”, the version number is “V01”, and the allocation classification is “quantity allocation” is set. The This indicates that the article indicated by the item name “part Y12” is a part, and the quantity is reserved when the part is allocated.

FIG. 12 shows an example of the data structure of the article configuration table. The article configuration table 111 b is stored in advance in the article master storage unit 111. The article configuration table 111b is a parts table that defines a hierarchical structure of parts for a product. The item configuration table 111b includes an item indicating an item ID, an item indicating an upper item ID, and an item indicating a required quantity. Information arranged in the horizontal direction of each item is associated with each other to indicate information regarding one component.

In the item indicating the article ID, an article ID of an article that is a component (part) of the upper article is set. In the item indicating the upper article ID, an article ID of an article (upper article) in a one-stage higher hierarchy constituted by the corresponding article is set. In the item indicating the required quantity, information indicating the quantity of the parts necessary for manufacturing the article indicated by the upper article ID is set.

In the article configuration table 111b, for example, information that the article ID is “PD011”, the upper article ID is “PD001”, and the required quantity is “10” is set. This indicates that the article indicated by the article ID “PD011” is a part of the article indicated by the upper article ID “PD001”, and ten “PD011” are required for manufacturing “PD001”. Yes.

In the article configuration table 111b, for example, a higher article ID “PD001” is set for the article IDs “PD011”, “PD012”, and “PD013”. This indicates that three types of parts “PD011”, “PD012”, and “PD013” are necessary to manufacture the upper article “PD001”.

Note that the part with the article ID “PD022” is the part with the upper article ID “PD002” and the upper article with the article IDs “PD221” and “PD222” as parts. This part is a part manufactured by the product manufacturing company 20 and is called an intermediate product.

FIG. 13 is a diagram showing an example of the data structure of the order reception table. The order table 112 a is generated / updated by the order management unit 121 and stored in the component requirement information storage unit 112. Items including an item indicating an order number, an item indicating an item ID, an item indicating a quantity, an item indicating a delivery date, and an item indicating a priority classification are set in the order table 112a. The information arranged in the horizontal direction of each item is associated with each other to indicate information related to one order content.

In the item indicating the order number, identification information for identifying the contents of the order is set. In the item indicating the product ID, the product ID of the ordered product is set. In the item indicating the quantity, a value indicating the order quantity is set. In the item indicating the delivery date, information indicating the delivery date of the corresponding product is set. In the item indicating the priority classification, a flag indicating whether or not to preferentially secure a part for manufacturing the product (priority target) is set. For example, when the flag “1” is set in the priority classification, it indicates that the product is a priority target. Further, when the flag “0” is set in the priority classification, it indicates that the product is not a priority target.

For example, information indicating that the order number is “OR001”, the item ID is “PD001”, the quantity is “10”, the delivery date is “2009/9/25”, and the priority classification is “1” is set in the order table 112a. . This means that an order for “10” products with the product ID “PD001” is received with the order number “OR001”, the delivery date to the customer is “2009/9/25”, and the product is a priority target. It is shown that.

For example, information indicating that the order number is “OR002”, the item ID is “PD002”, the quantity is “5”, the delivery date is “2009/9/30”, and the priority classification is “0” is set in the order table 112a. . Since the priority classification is “0”, the product with the product ID “PD002” is not subject to priority in this order.

Note that the order management unit 121 acquires information indicating whether or not the order is a priority target when receiving an order input. Then, an item indicating the priority classification of the corresponding record in the order reception table 112a is set according to the received information. For example, for a product whose delivery date is approaching to a customer, the sales terminal device 21 is set to be a priority object in order to prioritize manufacturing over other products.

FIG. 14 is a diagram showing an example of the data structure of the parts requirement table. The component requirement table 112 b is generated / updated by the order management unit 121 and stored in the component requirement information storage unit 112. The component requirement table 112b is requirement information indicating the required number of each component obtained for a product by requirement calculation.

The parts requirement table 112b includes an item indicating a requirement ID, an item indicating an order number, an item indicating a drawing number, an item indicating a version number, an item indicating a required number, an item indicating a required date, and an item indicating a priority classification. It has been. Information arranged in the horizontal direction of each item is associated with each other to indicate required information for one part.

In the item indicating the required ID, identification information for identifying the content of the required information is set. In the item indicating the order number, an order number corresponding to the order associated with the required information is set. In the item indicating the figure number, a figure number of a part necessary for manufacturing the upper product is set. In the item indicating the version number, the version number for the figure number is set. In the item indicating the required number, the quantity of parts necessary for manufacturing the upper product is set. In the item indicating the required date, a date on which the corresponding part is required in order to start production of the upper product is set. In the item indicating the priority classification, a flag indicating whether or not the part is a priority target is set. The order management unit 121 can set the item indicating the priority classification by associating the part requirement record with the order record set in the order table 112a using the order number as a key.

In the parts requirement table 112b, for example, the requirement ID is “SY001”, the order number is “OR001”, the drawing number is “DR011”, the version number is “V01”, the required number is “100”, and the required date is “2009 / Information of “9/1” and priority classification “1” is set. This is because the number of parts indicated by the drawing number “DR011” and the version number “V01” is “100” by “2009/9/1” for the product to be ordered in the order indicated by the order number “OR001”. It is necessary and indicates that this part is a part used in the priority product. It should be noted that the product to be ordered for the order number can be acquired by referring to the order table 112a. Thereby, the required number of a certain part corresponding to a certain product can be specified.

The order reception table 112a also includes various basic information such as the name of the customer who has received the order and the date and time of the order.
FIG. 15 is a diagram illustrating an example of the data structure of the component order remaining table. The component order remaining table 113 a is generated / updated by the component order management unit 122 and stored in the component order information storage unit 113. In the part order remaining table 113a, an item indicating the order ID, an item indicating the supplier ID, an item indicating the ordering command ID, an item indicating the drawing number, an item indicating the version number, an item indicating the order quantity, and an available number The item which shows, the item which shows the warehouse division, and the item which shows the note delivery date is provided. The information arranged in the horizontal direction of each item is associated with each other to indicate information regarding one remaining part.

In the item indicating the remaining part ID, identification information for identifying the remaining part is set. In the item indicating the supplier ID, identification information for identifying the supplier of the ordering party is set. In the item indicating the ordering command ID, identification information for identifying the ordering content is set on the supplier side. In the item indicating the figure number, the figure number of the remaining part is set. In the item indicating the version number, the version number for the figure number is set. In the item indicating the order quantity, the quantity of parts ordered to the supplier is set. In the item indicating the reserveable quantity, a quantity that can be reserved for the order quantity is set. Information for identifying a building or a section in the warehouse 25 in which the corresponding part is to be stored is set in the item indicating the warehouse classification. The scheduled delivery date for the remaining parts is set in the item indicating the remaining delivery date.

In the part order remaining table 113a, for example, the order remaining ID is “FA001”, the supplier ID is “S001”, the ordering command ID is “HT01-001”, the figure number is “DR011”, the version number is “V01”, and the order is placed. Information that the quantity is “50”, the available capacity is “50”, the warehouse classification is “AD01”, and the order delivery date is “2009/8/31” is set. This indicates that the order with the content indicated by the order number “FA001” has been made to the supplier (supplied as supplier 40) identified by the supplier ID “S001”. Further, it is indicated that the supplier 40 is instructed to manufacture the remaining parts to the part manufacturing line 45 by the ordering command ID “HT01-001”. Furthermore, the contents of the order are for the part with the drawing number “DR011” and the version number “V01”, the quantity is “50”, and the quantity that can be allocated to the product is “50”. . Further, when delivered to the warehouse 25, it is received in the building or section indicated by “AD01”, and the delivery date is “2009/8/31”.

It should be noted that the item indicating the note remaining delivery date is set by the parts order management unit 122 at the beginning of ordering the parts. However, the note delivery time can be changed according to the progress of the process in the part manufacturing line 45. For this reason, the part process management unit 124 changes the item indicating the order delivery date in the part order remaining table 113a according to the progress of the process in the part manufacturing line 45.

In addition, when a part set in the part order remaining table 113a is received in the warehouse 25, the corresponding part is set in a part inventory table described later. For this reason, it is no longer managed as a remaining part in the part remaining table 113a. For example, it is conceivable to set the corresponding part order remaining record as received, or to delete it from the part order remaining table 113a.

The part order remaining table 113a is part ordering information for managing the delivery date of parts in this way. The component order remaining table 113a is a part of the component management information.
FIG. 16 is a diagram illustrating an example of a data structure of the parts inventory table. The parts inventory table 114 a is generated / updated by the inventory management unit 123 and stored in the parts inventory information storage unit 114. The parts inventory table 114a is provided with an item indicating an inventory ID, an item indicating a drawing number, an item indicating a version number, an item indicating the number of inventory, and an item indicating a warehouse classification. The information arranged in the horizontal direction of each item is associated with each other to indicate information related to the inventory of one part.

In the item indicating the inventory ID, identification information for identifying the inventory content is set. In the item indicating the figure number, the figure number of the corresponding part is set. In the item indicating the version number, a version number corresponding to the figure number is set. In the item indicating the number of stocks, the quantity of stocks stored is set. The item indicating the number of stocks is also an allocatable number indicating the quantity that can be allocated from the stock. In the item indicating the warehouse division, information indicating a building or a section which is a storage location in the warehouse 25 is set.

In the parts inventory table 114a, for example, information that the inventory ID is “SK001”, the drawing number is “DR011”, the version number is “V01”, the inventory number is “30”, and the warehouse classification is “AD01” is set. This is the part inventory indicated by the inventory ID “SK001”, the part indicated by the drawing number “DR011” and the version number “V01”, and the quantity “30” is stored in the location indicated by the warehouse classification “AD01”. It has been shown.

The parts inventory table 114a is inventory information for managing parts inventory. The parts inventory table 114a is a part of parts management information.
The component order remaining table 113a and the component inventory table 114a correspond to the component management information.

FIG. 17 shows an example of the data structure of the product standard process table. The product standard process table 115a is stored in the article process information storage unit 115 in advance. The product standard process table 115a defines standard process days required for manufacturing products manufactured by the product manufacturing company 20.

The product standard process table 115a is provided with an item indicating the item ID, an item indicating the standard number of days, an item indicating the test process, and an item indicating the total number of days until trial. Information arranged in the horizontal direction of each item is associated with each other to indicate standard process information for one product.

The item ID for identifying the product is set in the item indicating the item ID. In the item indicating the standard number of days, the number of days required for manufacturing a product is set for each process. For example, items indicating standard days are provided with items indicating assembly processes P1, P2, and P3 and a test process, and a required number of days is set for each process. In the item indicating the total number of days until trial is completed, the total number of days required from the start of manufacturing to the completion of the test process is set.

In the product standard process table 115a, for example, the article ID is “PD001”, the assembly process P1 is “2 days”, the assembly process P2 is “3 days”, the assembly process P3 is “5 days”, and the test process is “5 days”. “, The information that the total number of days until trial is“ 15 days ”(= 2 days + 3 days + 5 days + 5 days) is set.

FIG. 18 is a diagram showing an example of the data structure of the part standard process table. The parts standard process tables 115b, 115c, and 115d are stored in advance in the article process information storage unit 115. The part standard process tables 115b, 115c, and 115d are information on standard processes related to parts manufactured by the

suppliers

40, 40a, and 40b. Although only the part standard process table 115b will be described below, the part standard process tables 115c and 115d have the same configuration.

The part standard process table 115b is provided with an item indicating the item ID, an item indicating the standard number of days, an item indicating the number of delivery days, and an item indicating the total number of days. Information arranged in the horizontal direction of each item is associated with each other to indicate information regarding one component.

In the item indicating the item ID, an item ID for identifying the part is set. In the item indicating the standard number of days, the number of days required for manufacturing a product is set for each process. For example, items indicating the standard days are provided with items indicating the A process, the B process, and the C process, and a necessary number of days is set for each process. In the item indicating the number of delivery days, the number of days required for delivery from the supplier 40 to the warehouse 25 is set. In the item indicating the total number of days, the total number of days required for delivery including the start of production to the number of delivery days is set.

In the part standard process table 115b, for example, the item ID is “PD011”, the A process is “1 day”, the B process is “2 days”, the C process is “1 day”, the delivery is “1 day”, and the total number of days. Is set to information “5 days” (= 1 day + 2 days + 1 day + 1 day).

The parts process management unit 124 can appropriately change the setting contents of the parts standard process tables 115b, 115c, and 115d based on information input from the terminal devices 41 and 42 by the employees of the

suppliers

40, 40b, and 40c. You can also. If it does in this way, it will become possible to respond flexibly to the change of the manufacturing process of parts.

Note that the setting of the standard number of days in the product standard process table 115a and the part standard process table 115b may be changed according to the number of products or parts manufactured. Specifically, the number of days required for each lot is determined as a standard process, and the standard process days are changed according to the number of production lots. For example, it is conceivable that 5 × 2 = 10 is set as the standard process days for the production of 2 lots for a product (or part) that requires 5 days for each lot. If it does in this way, the precision of calculation of process days can be raised.

Further, the product standard process table 115a and the part standard process table 115b are not limited to the number of processes described above, and may have a larger number of processes. Moreover, you may have a different number of processes for every product and components. Further, even for the same part, different numbers of processes may be defined for each supplier or factory.

Furthermore, it can be considered that each process is further divided into a plurality of processes.
FIG. 19 is a diagram illustrating an example of the data structure of the process performance management table. The process result management table 115e is generated by the component process management unit 124 and stored in the article process information storage unit 115. The process result management table 115e includes an item indicating an ordering command ID, an item indicating a production start date / time result, an item indicating each process completion scheduled date / time, an item indicating each process completion result date / time, an item indicating the number of delivery days, and a total of all processes And an item indicating a note delivery date are provided. Information arranged in the horizontal direction of each item is associated with each other, and indicates information related to the progress of the manufacturing process of one component.

In the item indicating the order command ID, an order command ID for instructing the manufacture of the part is set. In the item indicating the production start date / time result, the date and time when the manufacture of the part is started is set. In the item indicating each process completion scheduled date and time, the scheduled completion date and time of each process scheduled from the production start date and time results is set. For example, items indicating the process completion schedule date and time include items indicating the A process, the B process, and the C process, and the schedule completion date and time is set for each process. In the item indicating each process completion result date and time, the date and time of the result of completion of each process is set. For example, items indicating the process completion record date and time include items indicating the A process, the A record, the B process, the B record, the C process, and the C record, and the completion record date and the number of record days are set for each process. The In the item indicating the number of delivery days, the number of days required for delivery is set. In the item indicating the total of all processes, the total number of days (scheduled days or actual days) required for manufacturing parts is set. In the item indicating the remaining delivery date, the remaining delivery date of the corresponding part calculated based on the total of all processes is set.

In the process result management table 115e, for example, information that the ordering command ID is “HT01-001” and the production start date / time result is “2009/8/25 9:00: 00” is set. This indicates that production of the part indicated by the ordering command ID “HT01-001” is started at the supplier 40 on the corresponding day.

Further, in the process result management table 115e, for example, for the record of the ordering command ID “HT01-001”, the A process at the scheduled completion date and time of each process is “2009/8/26 9:00: 00”, and the B process is “2009”. / 8/27, 9:00: 0, and C process is set to “2009/8/28, 9:00: 00”. This indicates that each process for manufacturing the corresponding part is scheduled to be completed (or scheduled to be completed) at each set date and time. The component process management unit 124 can obtain the scheduled completion date and time of each process at the scheduled completion date and time by referring to the component standard process tables 115b, 115c, and 115d and the production start date and time results.

Further, in the process result management table 115e, for example, the A process of the process completion record date and time is “2009/8/26 15:00:00” and the A record is “1” for the record of the ordering command ID “HT01-001”. .25 days ", B process is" 2009/8/28 21:00: 00 ", B performance is" 2.25 days ", C process is" 2009/8/30 9:00:00 ", C performance is Information of “1.5 days” is set. This indicates that the completion date and time of the results of each process is the set date and time, and the actual number of days actually required for each process is the number of days set as the A, B, and C results.

Here, the A process result is the number of days in the period from the production start date and time to the completion result date and time of the A process. The B process performance is the number of days in the period from the completion performance date / time of the A process to the completion performance date / time of the B process. The C process performance is the number of days in the period from the completion performance date / time of the B process to the completion performance date / time of the C process.

Further, in the process result management table 115e, for example, the delivery date is “1 day”, the total of all processes is “6 days”, and the remaining delivery date is “2009/8/31” for the record of the ordering command ID “HT01-001”. "Is set. This takes “one day” from the completion of parts manufacture to delivery to the warehouse 25, and “6 days” in total for all processes (= 1.25 days + 2.25 days + 1.5 days + 1) Day). Note that the remaining delivery date can be obtained, for example, as a date and time obtained by adding the number of delivery days to the completion result date and time of the C process as the final process. Moreover, it can also obtain | require as a date which added the sum total of all the processes to the production start date / time result.

Further, in the process result management table 115e, for example, the process completion record date and time of the C process is “-” (no setting) for the record of the ordering command ID “HT01-002”. This indicates that at the present time, the manufacturing process of the ordering instruction ID “HT01-002” has been completed up to the B process, but has not been completed up to the C process. In that case, the part process management unit 124 calculates the total of all processes with reference to the part standard process tables 115b, 115c, and 115d for the C process. Here, the ordering command ID “HT01-002” indicates a manufacturing process in the part manufacturing line 45 of the part indicated by the article ID “PD012”. For this reason, the part process management unit 124 refers to the part standard process table 115b and acquires the standard number of days “2 days” required for the C process of the article ID “PD012”. Then, all process totals “9 days” (= 2 days + 4 days + 2 days (standard number of days in process C) +1 day) are acquired. As a result, it is possible to calculate the remaining delivery date for parts that are still in the process.

The part process management unit 124 reflects the order delivery date obtained in this way in the item indicating the order delivery date in the part delivery table. Thereby, in the parts order remaining table 113a, it is possible to manage an accurate order remaining time according to the progress of the manufacturing process in the

suppliers

40, 40a, and 40b.

It should be noted that when the parts production line 45 is stopped at night, it is conceivable to manage the scheduled date and time and the actual results excluding the stopped time. Thereby, the process management according to the working time of the line can be performed.

FIG. 20 is a diagram showing an example of the data structure of the update figure number table. The updated figure number table 116 a is generated by the allocation target figure number acquisition unit 131 and stored in the allocation target part information storage unit 116. The updated figure number table 116a is provided with an item showing the figure number and an item showing the version number. The information arranged in the horizontal direction of each item is associated with each other, and constitutes information related to a part for which one update has been performed.

In the item indicating the figure number, among the pieces of information managed by the part requirement information storage unit 112, the part order information storage unit 113, and the part inventory information storage unit 114, the figure number of the updated part is set. . In the item indicating the version number, the version number for the figure number is set.

For example, it is assumed that the order management unit 121 receives a change in the order quantity of a product and updates the record of the requirement ID “SY001” in the component requirement table 112b stored in the component requirement information storage unit 112. Then, the allocation target figure number obtaining unit 131 refers to the record of the requirement ID “SY001” in the part requirement table 112b, extracts the figure number and version number of the target part, and sets them in the updated figure number table 116a. The same applies to the update of each record of the component order remaining table 113a stored in the component order information storage unit 113 and the component inventory table 114a stored in the component inventory information storage unit 114.

The allocation target figure number acquisition unit 131 sets the figure number and the version number included in the updated record of each table in the updated figure number table 116a at any time when an update is detected.
FIG. 21 is a diagram showing an example of the data structure of the allocation target figure number table. The allocation target figure number table 116 b is generated based on the updated figure number table 116 a by the allocation target figure number acquisition unit 131 and stored in the allocation target part information storage unit 116. The allocation target figure number table 116b is provided with an item indicating the figure number and an item indicating the version number. Information arranged in the horizontal direction of each item is associated with each other, and indicates information of a part to be allocated.

In the item indicating the figure number, the figure number of the part to be allocated is set. In the item indicating the version number, the version number for the figure number is set.
The allocation target figure number table 116b is a collection of records with duplicate figure numbers and version numbers from the updated figure number table 116a.

FIG. 22 is a diagram showing an example of the data structure of the allocation details table. The allocation detail table 117a is generated / updated by the reserve allocation processing unit 133 or the quantity allocation processing unit 134, and is stored in the part allocation detail storage unit 117. In the allocation detail table 117a, an item indicating an order number, an item indicating a required ID, an item indicating a drawing number, an item indicating a version number, an item indicating a required date, an item indicating a required number, and a required remaining number before allocation are shown. There are provided an item, an item indicating the number of allocations, an item indicating the allocation category, an item indicating the number of stocks / the number of orders, an item indicating inventory ID / the remaining order ID, and an item indicating the remaining delivery date. Information arranged in the horizontal direction of each item is associated with each other to indicate information related to one allocation result.

In the item indicating the order number, an order number related to the provision contents is set. In the item indicating the required ID, a required ID related to the provision contents is set. In the item indicating the figure number, the figure number of the allocation target part is set. In the item indicating the version number, the version number for the figure number is set. The required date of the part is set in the item indicating the required date. In the item indicating the required number, the required number of parts is set. In the item indicating the required remaining number before allocation, the remaining number excluding the allocated number that has already been allocated in the allocation process until immediately before the required number is set. In the item indicating the number of allocations, the quantity allocated in the current allocation process (indicated by the corresponding record) is set. In the item indicating the allocation category, a category indicating whether the allocation is from the inventory or the allocation from the backlog is set. In the item indicating the number of stocks / the number of orders, the quantity of stocks / remaining parts that are the source of allocation is set. In the item indicating inventory ID / remaining note ID, an inventory ID or a remaining note ID serving as a reservation source is set. In the item indicating the remaining delivery date, the remaining delivery date is set for a part allocated from the remaining purchase date.

In the allocation details table 117a, for example, the order number is “OR001”, the required ID is “SY001”, the figure number is “DR011”, the version number is “V01”, the required date is “2009/9/1”, the required number Is “100”, the required remaining number before allocation is “100”, the allocation number is “30”, the allocation category is “inventory”, the inventory number / order number is “30”, the inventory ID / remaining ID is “SK001”, Note The information that the remaining delivery date is "-" (no setting) is set. This is because the required record of the required ID “SY001” of the part specified by the figure number “DR011” and the version number “V01” is linked to the received order of the order number “OR001”, and before the allocation of the part It shows that “30” is allocated from the stock indicated by the stock ID “SK001” to the required remaining number “100”. In addition, since the allocation process shown by this allocation detail record allocates from stock, there is no setting of the order delivery date.

Further, in the allocation details table 117a, for example, the order number is “OR001”, the required ID is “SY001”, the figure number is “DR011”, the version number is “V01”, the required date is “2009/9/1”, The required number is “100”, the required remaining number before allocation is “70”, the allocated number is “10”, the allocation type is “inventory”, the inventory number / order number is “10”, and the inventory ID / remaining ID is “SK002”. ", The information that the note delivery date is"-"(no setting) is set. The required remaining number before allocation “70” is “100−30 = 70” because “30” has already been allocated from the inventory with the inventory ID “SK001” with respect to the required remaining number “100” by the previous allocation process. "

Further, in the allocation details table 117a, for example, the order number is “OR001”, the required ID is “SY001”, the figure number is “DR011”, the version number is “V01”, the required date is “2009/9/1”, The required number is “100”, the required remaining number before allocation is “50”, the allocated number is “50”, the allocation category is “remaining order”, the inventory quantity / order quantity is “50”, and the inventory ID / remaining ID is “50”. The information is set to FA001 ”and the note delivery date“ 2009/8/31 ”. This is because the required record of the required ID “SY001” of the part specified by the figure number “DR011” and the version number “V01” is linked to the received order of the order number “OR001”, and the required remaining of the part The number “50” indicates that “50” is allocated from the remaining stock indicated by the inventory ID “FA001”. Furthermore, it shows that the remaining delivery date for the remaining parts is “2009/8/31”.

Further, in the allocation details table 117a, for example, the order number is “OR001”, the required ID is “SY003”, the drawing number is “DR013”, the version number is “V01”, the required date is “2009/9/1”, The required number is “50”, the required remaining number before allocation is “10”, the allocated number is “0”, the allocation category is “out of stock”, the inventory number / order number is “0”, and the inventory ID / remaining ID is “ -"(No setting) and note remaining delivery date is set as"-"(no setting). This is because the required record of the required ID “SY003” of the part specified by the figure number “DR013” and the version number “V01” is linked to the received order of the order number “OR001”, and before the allocation of the part For the required remaining number “10”, there is no allocation source (the number of inventory and the number of remaining orders does not exist), indicating that the item is “out of stock” that could not be allocated.

FIG. 23 is a diagram showing an example of the data structure of the allocation history table. The allocation history table 117b is generated in the reserve allocation processing unit 133 or the quantity allocation processing unit 134 and is stored in the part allocation detail storage unit 117. The allocation history table 117b is a log that records the figure number and version number of a part that has been allocated and the corresponding order number. Each time the reserve allocation processing unit 133 or the quantity allocation processing unit 134 generates an allocation detail record of the allocation detail table 117a, it generates an allocation history record and registers it in the allocation history table 117b. The allocation history table 117b includes an item indicating an order number, an item indicating a drawing number, and an item indicating a version number. Information about the parts that have been allocated is shown by associating pieces of information arranged in the horizontal direction of each item with each other.

In the item indicating the order number, an order number related to the part for which the allocation process has been performed is set. In the item indicating the figure number, the figure number of the part subjected to the allocation process is set. In the item indicating the version number, the version number for the figure number is set.

In the allocation history table 117b, for example, information that the order number is “OR001”, the figure number is “DR011”, and the version number is “V01” is set. This indicates that an allocation process has been performed for an order with the order number “OR001” of the part indicated by the figure number “DR011” and the version number “V01”.

FIG. 24 is a diagram showing an example of the data structure of the surface alignment target management table. The surface alignment target management table 118 a is generated by the surface alignment information update processing unit 141 and stored in the component surface alignment information storage unit 118. Information indicating the order number is set in the surface alignment target management table 118a.

In the item indicating the order number, an order number indicating the order contents to be subjected to the surface alignment processing is set.
For example, information indicating that the order number is “OR001” is set in the surface alignment target management table 118a. This indicates that the arrangement processing is necessary for this order because the provision for the parts related to the order product indicated by the order number “OR001” has been updated. That is, by referring to the surface alignment target management table 118a, it is possible to identify orders that require surface alignment processing.

FIG. 25 is a diagram showing an example of the data structure of the component surface alignment table. The component surface alignment table 118b is generated / updated by the surface alignment information update processing unit 141 based on the allocation detail table 117a, and is stored in the component surface alignment information storage unit 118. The parts surface alignment table 118b includes an item indicating an order number, an item indicating a drawing number, an item indicating a version number, an item indicating a required number, an item indicating the number of inventory reservations, an item indicating an inventory part surface alignment date, Item indicating the number of remaining reserves (within delivery date), item showing the number of remaining reserves (delayed), item showing the remaining order delivery date, item showing the date of the remaining parts, and unarranged (within delivery date) There are provided an item, an item indicating unarranged (delayed), an item indicating an unarranged part delivery date, and an item indicating an unarranged part surface alignment date. The information arranged in the horizontal direction of each item is associated with each other, and indicates information for managing the surface alignment date of the parts.

In the item indicating the order number, the order number related to the current assortment record is set. In the item indicating the figure number, the figure number of the target part is set. In the item indicating the version number, the version number for the figure number is set. In the item indicating the required number, the required number necessary for allocation is set.

The number allocated from stock is set in the item indicating the number of stocks reserved. In the item indicating the inventory part surface alignment date, the surface alignment date of the part allocated from the inventory is set. In addition, since the date of inventory part alignment is provision from inventory, the required date of each part is set as it is.

In the item indicating the number of remaining reserves (within the delivery date), the quantity of the parts allocated from the remaining stock with the remaining delivery date within the initial delivery date is set. Here, the initial delivery date is the delivery date of the parts initially desired by the product manufacturing company 20 to the

suppliers

40, 40a, and 40b based on the delivery date of the product to the customer. In the item indicating the number of remaining allowances (delayed), the quantity of the parts allocated from the remaining remnants that are not yet delivered in the initial delivery date (the delivery date is delayed) is set. In the item indicating the remaining delivery date, the remaining delivery date is set according to the progress of the parts manufacturing process at the

suppliers

40, 40a, and 40b. In the item indicating the remaining part surface alignment date, the date when the remaining part group which is a component part of the upper article is aligned in the warehouse 25 is set.

In the item indicating unarranged (within delivery date), provision is not made in a shortage state, but the quantity that can be ordered from the current time to the

suppliers

40, 40a, 40b and received into the warehouse 25 within the initial delivery date is set. The In the item indicating unarranged (delayed), a quantity that is not reserved in the shortage state and cannot be received in the warehouse 25 within the initial delivery date even if an order is made to the

suppliers

40, 40a, 40b from the present time is set. . In the item indicating the unarranged part delivery date, an assumed delivery date when an unallocated product is ordered at the present time is set. In the item indicating the unarranged part surface alignment date, an expected date when an unarranged part group as a component part of the upper article is aligned in the warehouse 25 is set.

Hereinafter, specific setting contents of the part surface alignment table 118b assuming the time of 9:00 am on August 30, 2009 will be exemplified.
In the component surface alignment table 118b, for example, the order number is “OR001”, the drawing number is “DR011”, the version number is “V01”, the required number is “100”, the inventory allocation number is “50”, the inventory component surface alignment The date is “2009/9/1”, the remaining reserve number (within delivery date) is “50”, the remaining reserve number (delayed) is “0”, the remaining order delivery date is “2009/8/31”, The remaining part alignment date is "2009/9/2", unarranged (within delivery date) is "0", unarranged (delayed) is "0", unarranged component delivery date is "-" (no setting), The information that the unarranged part surface alignment date is “2009/9/3” is set.

This indicates that the part designated by the figure number “DR011” and the version number “V01” has been allocated from the stock by the quantity “50”. For the amount allocated from the stock, the required date in the allocation detail table 117a is set as it is as the date of the arrangement. In addition, the quantity of “50” is allocated for the part from the remaining order within the due date (referred to as the remaining part within the due date), and the remaining order due date is referred to as the delayed due date (referred to as the delayed due date part). Indicates that it has not been allocated.

Also, as the remaining order delivery date, the later delivery date “2009/8/31”, which is the later of the remaining delivery date within the due date and the late delivery date, is set. That is, in this record, the necessary quantity “100” is prepared as the required number by “2009/8/31”. In this record, since no provision is made from the late delivery due date, the remaining delivery date for the remaining parts within the delivery date is set. In addition, if it is allocated from the delayed delivery date, the delivery date of the late delivery date component is usually later, so the delivery date of the late delivery date component is set.

Note: “2009/9/2” set for the date of the remaining parts to be ordered is the latest date of the remaining delivery date for the parts in order to manufacture the upper article. Here, for the product “PD001” specified by the order number “OR001”, the parts group “DR011”, “DR012”, “DR013” (all of the version numbers “V01”) are required. For this reason, the order remaining delivery date “2009/9/2” of the part “DR012” with the latest order remaining delivery date is set.

Furthermore, since all the required numbers can be allocated using the stock and the backlog as the allocation source, both unarranged (within the delivery date) and unarranged (delayed) will be “0”, and the undelivered part delivery date will be “-” ( No setting). In addition, in the unarranged part surface alignment date, the latest estimated delivery date is set for the parts group of unarranged products by the same determination as the remaining component surface alignment date.

Also, in the parts alignment table 118b, for example, the order number is “OR001”, the figure number is “DR012”, the version number is “V01”, the required number is “50”, the inventory allocation number is “30”, and the inventory parts The date of arrangement is “2009/9/1”, the number of remaining provisions (within delivery date) is “10”, the number of remaining provisions (delay) is “10”, and the remaining order delivery date is “2009/9/2” , The remaining part surface alignment date is "2009/9/2", unarranged (within delivery date) is "0", unarranged (delayed) is "0", unarranged component delivery date is "-" (no setting) ), The information that the unarranged part surface alignment date is “2009/9/3” is set. The meaning of each setting included in this record is the same as the setting of the part surface alignment record of the figure number “DR011” described above. However, the setting of the number of remaining orders (delay) is “10”. In other words, provisions are made based on the late delivery deadline. Therefore, in the note remaining payment date, the note remaining date related to this delivery date delayed remaining is set.

Also, in the parts alignment table 118b, for example, the order number is “OR001”, the figure number is “DR013”, the version number is “V01”, the required number is “50”, the inventory allocation number is “20”, and the inventory part The date of arrangement is “2009/9/1”, the number of remaining reserves (within delivery date) is “20”, the number of remaining reserves (delayed) is “0”, and the remaining order delivery date is “2009/8/30” , The remaining part surface alignment date is "2009/9/2", unarranged (within delivery date) is "0", unarranged (delayed) is "10", unarranged component delivery date is "2009/9/3" ", The information that the unarranged part surface alignment date is" 2009/9/3 "is set. The meaning of each setting included in this record is the same as the setting of the part surface alignment record of the figure number “DR011” described above.

However, in this record, it is not possible to allocate all the required numbers using the stock and the backlog as a reserve source. Specifically, with respect to the required number “50”, the number of inventory reserves is “20” and the number of remaining reserves (within delivery date) is “20”, which is insufficient by “50-20-20 = 10”. For this reason, the quantity “10” is set as unarranged (within delivery date) or unarranged (delayed) as an unarranged product.

Here, whether the quantity of unarranged parts is set as unarranged (within delivery date) or unarranged (delayed) is based on the fact that the relevant part has been ordered from the supplier at the present time (in this case, “2009/8/30”) The expected delivery date can be determined according to whether it is within the initial delivery date or delayed from the initial delivery date. As the initial delivery date, for example, the required date set in the component required table 112b can be used. Whether or not there is a delay can be determined based on the current date and the initial delivery date by referring to the part standard process table 115b and using the total number of days required for the standard process of each part as the lead time from part ordering to part delivery. . In this case, even if an order is placed on “2009/8/30”, the standard lead time of the corresponding part is “4 days”, so that it is not in time for the initial delivery date “2009/9/1”. For this reason, “10” corresponding to the current shortage is set in the item indicating unarranged (delayed). In addition, the expected delivery date “2009/9/3” is set as an item indicating the unallocated parts delivery date.

FIG. 26 shows an example of the data structure of the manufacturing plan management table. The production plan management table 118 c is generated / updated by the production management unit 142 based on the component surface alignment table 118 b and stored in the component surface alignment information storage unit 118. The production plan management table 118c includes an item indicating an order number, an item indicating a product drawing number, an item indicating a version number (product), an item indicating a part drawing number, an item indicating a version number (part), and the number of uses (inventory). ), Items indicating available dates (inventory), items indicating trial dates (inventory), items indicating the number of used items (within the remaining delivery date), indicating the number of used items (delayed delay) Items, items that indicate the date when the product can be started (notes remaining), items that indicate the date of trial (notes remaining), items that indicate the number of uses (within the unallocated delivery date), items that indicate the number of uses (unallocated delay) In addition, an item indicating an available date (unarranged) and an item indicating a date of trial (unarranged) are provided. Information arranged in the horizontal direction of each item is associated with each other to indicate information related to one product.

The order number of the product is set in the item indicating the order number. In the item indicating the product drawing number, the drawing number of the product is set. In the item indicating the version number (product), the version number for the product drawing number is set. In the item indicating the part diagram number, the diagram number of the component part is set. In the item indicating the version number (part), the version number for the part diagram number is set.

The number of parts that should be used to start manufacturing the product is set in the item indicating the number used (inventory). The parts here are parts indicated by the part drawing number and the version number included in the record (the same applies hereinafter). In the item indicating the start date (inventory), a date on which manufacture can be started using a stock part is set. In the item indicating the date of trial (inventory), a date on which a product manufactured from stock parts is trialed (the test process is completed) is set.

In the item indicating the number of use (within the remaining delivery date), the number of the remaining parts within the delivery date that should be used in order to start manufacturing the product is set. In the item indicating the number of uses (remaining delay), the number of delivery date delayed remaining parts to be used for starting the manufacture of the product is set. In the item indicating the date of commencement (the remaining order), a date on which the manufacturing can be started including the remaining part is set. The date indicating the date of trial of the product manufactured with the remaining part is set in the item indicating the date of trial (the remaining part).

In the item indicating the number of uses (within the unarranged delivery date), the number of unarranged parts within the due date that should be used in order to start manufacturing the product is set. Here, the unarranged part within the delivery date refers to a part (a part corresponding to an item indicating an unarranged (within delivery date) in the part alignment table 118b) that is expected to be received within the initial delivery date if an order is placed at the present time. . In the item indicating the number of uses (unarranged delay), the number of undelivered parts that are to be used for starting the manufacture of the product is set. Here, the delivery date unarranged parts are parts that are not expected to be received within the initial delivery date even if an order is placed at the present time (parts corresponding to items indicating unarranged (delayed) in the parts alignment table 118b). Say. In the item indicating the start date (unarranged), a date when the manufacture can be started using the unarranged part is set even if the unarranged part is ordered. In the item indicating the date of trial (unarranged), a date on which a product manufactured from the unarranged parts will be retriald is set.

In the manufacturing plan management table 118c, for example, the order number is “OR001”, the product drawing number is “DR001”, the version number (product) is “V01”, the part drawing number is “DR011”, and the version number (part) is “ V01 ”, the number of uses (inventory) is“ 40 ”, the start date (inventory) is“ 2009/9/1 ”, the date of trial (inventory) is“ 2009/9/15 ”, the number of uses ( “Inside delivery deadline” is “40”, the number of uses (outside delay) is “0”, the available date (outside) is “2009/9/1”, and the date of trial (outside) is “2009/9/15”, the number of uses (within the unarranged delivery date) is “0”, the number of uses (unarranged delay) is “20”, and the start date (unarranged) is “2009/9/3” The information that the date of trial (unarranged) is “2009/9/17” is set.

This is because the product indicated by the product drawing number “DR001” and the version number “V01” is used by using the part indicated by the part drawing number “DR011” and the version number “V01” from the stock “40”, and “2009 / 9/1 ″ indicates that manufacturing can be started. In addition, in this case, the date of the scheduled trial is “2009/9/15”. According to the item indicating the number of inventory allocations in the part surface alignment table 118b, the allocation quantity from the inventory is “50”. Here, according to the article configuration table 111b, the parts “PD011”, “PD012”, and “PD013” of the parts group necessary for manufacturing the product “PD001” are required in a quantity ratio of 2: 1: 1. . By the way, from the stock only, the number of parts allocated (usable number) indicated by the part diagram number “DR013” and the version number “V01” is “20”. That is, the quantity of products that can be manufactured is determined by the usable number “20” of the parts with the part diagram number “DR013”. For this reason, at the time of “2009/9/1” when only stock items can be used, the quantity “40” from the stock for the part (corresponding to “PD011”) indicated by the part diagram number “DR011” and the version number “V01”. You just have to use it.

In addition, “20” is set as the quantity that can be used for manufacturing together with the inventory, including those that are scheduled to be received as the remaining parts within the delivery date, in the number of uses (within the remaining delivery date). This means that parts with part numbers “DR011” and “DR013” (the version numbers are the same and will be omitted below) are newly available for “50” and “20”, respectively. It is a result. In other words, the quantity that can be used from the stock items and the remaining parts within the delivery date is respectively for each part number “DR011”, “DR012”, “DR013” (considering already used parts). Since 10 + 50 = 60, 10 + 10 = 20, and 0 + 20 = 20, the upper limit of the number of products that can be manufactured is determined by the usable quantities of “DR012” and “DR013”, and the number of parts used is determined. Here, since “20” can be used for “DR012” and “DR013”, the item indicating the number of uses of this record (parts of “DR011”) (within the remaining delivery date) from the required quantity ratio of each part. , “40” is set.

Similarly, regarding the number of used parts (remaining delay), the usable numbers of the respective parts number “DR011”, “DR012”, and “DR013” are 20 + 0 = 20, 0 + 10 = 10, and 0 + 0 = 0. At this time, the usable quantity of “DR013” is “0”. Accordingly, the manufacture of the product cannot be started, and “0” is set in the item indicating the number of uses (remaining delay).

In addition, “2009/9/1” including the remaining parts within the delivery date and the remaining parts due to the delivery date indicates that it is possible to start manufacturing including the remaining parts. In addition, in this case, the date of the scheduled trial is “2009/9/15”. In addition, if it is possible to start manufacturing products using late delivery deadline parts, the latest delivery date of the late delivery deadline parts must be set as the available date It becomes. In this example, even if “DR012” is received as a delayed delivery due part, production cannot be started due to a shortage of the part “DR013”. Set to year, month, day (remaining note).

Furthermore, “0” is set as the quantity that can be used together with stocks and unordered items as unarranged parts within the delivery date, in the number of uses (within the unarranged delivery date). Similarly, “0” is set for the records “DR012” and “DR013”. This is because, according to the item indicating unarranged (within the delivery date) of the component surface alignment table 118b, all the parts available as unarranged items within the period are “0”, which is enough to manufacture a new product. This is because the parts cannot be used.

In addition, regarding the number of use (unarranged delay), the usable numbers of the parts of the part diagram numbers “DR011”, “DR012”, and “DR013” are 20 + 0 = 20, 10 + 0 = 10, and 0 + 10 = 10, respectively. The production can be started using all available parts. As a result, “20” is set in the item indicating the number of uses of this record (unarranged delay).

In addition, “2009/9/3” including parts not yet arranged within the delivery date and parts not arranged late in the delivery date indicates that it is possible to start production including all the parts that are not yet arranged. In addition, in this case, the date of the scheduled trial is “2009/9/17”.

In this way, by using the production plan management table 118c, it is possible to manage the date when the product can be started and the date of the scheduled trial. That is, the production plan management table 118c can be used as information for managing the production schedule of products. In addition, the manufacturing management unit 142 can issue a product manufacturing instruction to the product factory of the product manufacturing company 20 with reference to the manufacturing plan management table 118c.

FIG. 27 is a diagram showing an example of the data structure of the delivery date reply table. The delivery date response table 119a is generated / updated by the delivery date response information generation unit 143 based on the manufacturing plan management table 118c, and is stored in the delivery date response information storage unit 119. The delivery date reply table 119a includes an item indicating an order number, an item indicating a drawing number, an item indicating a version number, an item indicating the number of manufacturable items, an item indicating a final surface alignment (start) scheduled date, and a final scheduled date of trial. Items to be shown are provided. The information arranged in the horizontal direction of each item is associated with each other, and indicates information for delivery date management for one order.

The order number is set in the item indicating the order number. In the item indicating the figure number, the figure number of the product to be delivered is set. In the item indicating the version number, the version number for the figure number is set. The number of products that can be manufactured is the quantity of products that can be manufactured at each point when stock items, unordered items (within delivery date / each delivery date delay), and unarranged products (within delivery date / each delivery date delay) are available. Is set. In the item indicating the final surface alignment (start) scheduled date, a date indicating the final surface alignment scheduled date is set. In the item indicating the final scheduled date, the final scheduled date when production starts from the final scheduled date is set.

In the delivery date reply table 119a, the order number is “OR001”, the figure number is “DR001”, the version number is “V01”, the stock is “4” for the number of manufacturable items, “4” is in the remaining delivery date, and the remaining delay is Is “0”, within the non-arranged delivery date is “0”, the unarranged delay is “2”, the final surface alignment (starting) scheduled date is “2009/9/3”, and the final scheduled date for testing is “2009/9 / Information "17" is set. This means that the product indicated by the figure number “DR001” and the version number “V01”, which is an order item in the order number “OR001”, is “4” for the stock parts only, and “4” including the remaining parts within the delivery date. ”,“ 0 ”including parts with late delivery deadlines,“ 0 ”including parts not yet arranged within the delivery date, and“ 2 ”including parts not yet arranged within the delivery date. . In addition, it is indicated that the date when all the parts necessary for manufacturing the product for the number of orders are prepared (the final surface alignment date) is “2009/9/3”. Further, it is shown that the date of completion of the trial is “2009/9/17” on the assumption that the production is started on the final surface alignment scheduled date.

When the delivery date reply processing unit 144 receives a delivery date reply request from the sales terminal device 21, for example, the delivery date reply processing unit 144 makes a delivery date reply based on the delivery date reply table 119a stored in the delivery date reply information storage unit 119. The delivery date reply table 119a reflects the progress of the parts manufacturing process at the

suppliers

40, 40a, 40b. For this reason, the employee of the sales department who operates the sales terminal device 21 can obtain an accurate delivery date answer.

FIG. 28 is a diagram showing the configuration of the work area for allocation processing. The work area for allocation process 150 is used as a work area for the allocation process of the reserve allocation processing unit 133. The reserve allocation processing unit 133 refers to the allocation target figure number table 116b stored in the allocation target component information storage unit 116, extracts various data used for allocation processing from the management information storage unit 110, and allocates the allocation processing work Store in area 150.

The allocation processing work area 150 includes a free requirement storage unit 151, a free order remaining storage unit 152, a free stock storage unit 153, an allocation detail reserve storage unit 154, and an allocation work information storage unit 155.

In the free requirement storage unit 151, a record updated in the component requirement information storage unit 112 (a record for a newly ordered product) is temporarily stored.
The free order storage unit 152 temporarily stores a remnant record that has been updated and is not yet assigned to any order in the part order table 113a stored in the part order information storage unit 113. Stored.

Here, the updated part can be obtained by referring to the figure number and the version number registered in the allocation target figure number table 116b stored in the allocation target part information storage unit 116. In addition, whether or not allocation is performed for the remaining order record of the part is determined by checking whether the item indicating “stock ID / remaining ID” in the allocation detail table 117a stored in the part allocation detail storage unit 117 is appropriate. It can be distinguished by whether or not the note remaining ID of the remaining record is set. Specifically, if it is set, provision is made from the remainder of the part. Moreover, when it is not set, the allocation is not performed from the remainder of the part.

The free inventory storage unit 153 temporarily stores an inventory record that has been updated and is not yet assigned to any order in the component inventory table 114a stored in the component inventory information storage unit 114. .

Here, the updated part can be acquired by referring to the figure number and the version number registered in the allocation target figure number table 116b stored in the allocation target part information storage unit 116 as described above. Whether or not the inventory record of the part has been allocated is determined based on the item corresponding to “stock ID / remaining ID” in the allocation detail table 117a stored in the part allocation detail storage unit 117. Can be distinguished by whether or not a stock ID is set. Specifically, if set, provision is made from the inventory of the part. If not set, provision is not made from the inventory of the part.

In the allocation detail reserve storage unit 154, either the inventory ID or the remaining inventory ID is set in the item indicating “inventory ID / remaining inventory ID” in the allocation detail table 117 a stored in the parts allocation detail storage section 117. The provision detail record is temporarily stored. That is, the allocation detail reserve storage unit 154 stores an allocation detail record that has already been allocated to any allocation source.

The allocation work information storage unit 155 is an area for temporarily storing an allocation detail record newly generated by the reserve allocation processing unit 133. The reserve allocation processing unit 133 stores the allocation detail record stored in the allocation work information storage unit 155 in the part allocation detail storage unit 117.

Here, each data stored in the component requirement information storage unit 112, the part order information storage unit 113, and the component inventory information storage unit 114 can be updated in real time. For this reason, simply allocating a reserve allocation target part based on the information in the part requirement information storage unit 112, the part order information storage unit 113, and the part inventory information storage unit 114, the information stored in these storage units is used. However, there may be a case where processing cannot be performed properly.

Specifically, extraction of parts that are reserved for reserve requires a certain amount of time for checking the parts that are reserved for reserve (checking the status of previous allocations, the unallocated inventory, and the status of unallocated reserves). There are cases. This is because the determination process needs to be performed with reference to a large number of records. Then, during the checking process, for example, a part that was a remaining part may be changed to a stock part when it is received in the warehouse 25. In this case, if allocation is performed at different timings from the information stored in the component requirement information storage unit 112, the part order information storage unit 113, the component inventory information storage unit 114, and the component allocation detail storage unit 117, for example, A problem arises when the same part is allocated twice to product b as an allocated financial resource for inventory parts, even though it has been allocated to product a as an allocated financial resource.

On the other hand, the reserve allocation processing unit 133 extracts a snapshot obtained by extracting information at a certain timing in the component requirement information storage unit 112, the part order information storage unit 113, the component inventory information storage unit 114, and the component allocation detail storage unit 117. And reserve reserve processing. Thereby, the above-mentioned problem of double allocation can be avoided.

As described above, the reserve allocation processing unit 133 uses the allocation processing work area 150 for allocation processing, so that the component requirement information storage unit 112, the part order information storage unit 113, the component inventory information storage unit 114, and the component allocation allocation unit The reserve allocation process can be appropriately performed while maintaining the consistency of the data managed by each of the detail storage units 117.

The work area 150 for allocation processing can also be used as a work area for allocation processing of the quantity allocation processing unit 134.
FIG. 29 is a diagram illustrating a data structure example of the gate passage history table. The gate passage history tables 211, 212, and 213 are history of progress of parts production lines (logs of gate passage times) in the

suppliers

40, 40a, and 40b. Hereinafter, only the gate passage history table 211 will be described, but the gate passage history tables 212 and 213 have the same configuration.

The gate passage history table 211 is generated / updated by the passage information receiving unit 220 and stored in the gate passage information storage unit 210. In the gate passage history table 211, an item indicating an ordering command ID, an item indicating a gate ID, and an item indicating a passage date and time are provided. Information arranged in the horizontal direction of each item is associated with each other to indicate one gate passage information.

In the item indicating the order command ID, the order command ID stored in the kanban 60 is set. In the item indicating the gate ID, the gate ID of each of the

gates

310, 320, 330, and 340 is set. In the item indicating the passage date and time, the date and time of passing through the gate is set.

Here, it is assumed that gate IDs “Gate01”, “Gate02”, “Gate03”, and “Gate04” are set in the

gates

310, 320, 330, and 340.
In the gate passage table 211, for example, information that the ordering command ID is “HT01-002”, the gate ID is “Gate01”, and the passage date and time is “2009/8/24 9:00:00” is set.

The passage information receiving unit 220 receives gate passage information from the

gates

310, 320, 330, and 340 via the communication device 300. The timing is the timing immediately after each gate and the Kanban 60 communicate. The passage information transmission unit 230 sequentially notifies the component process management unit 124 of the contents of the gate passage history record newly added to the gate passage information storage unit 210.

As information to be set in the item indicating the date and time of passing through the gate, the passage information receiving unit 220 uses the ordering instruction ID and the gate as the time stamp of the passage time obtained at each gate from the

gates

310, 320, 330, and 340. It can be considered to be received together with the ID. Alternatively, a time stamp when the passage information receiving unit 220 receives information including the ordering command ID and the gate ID from the

gates

310, 320, 330, and 340 may be set.

Next, the processing procedure of the management server 100 realized by the above configuration will be described. First, the procedure of the remnant delivery date update process when the management server 100 receives the gate passage information will be described.

FIG. 30 is a flowchart showing the note remaining delivery date update process. In the following, the process illustrated in FIG. 30 will be described in order of step number.
[Step ST1] The part process management unit 124 receives gate passage information from the line terminal device 200.

[Step ST2] The part process management unit 124 refers to the ordering command ID included in the received gate passage information.
[Step ST3] The part process management unit 124 updates the record of the corresponding order command ID in the process result management table 115e stored in the article process information storage unit 115. The item to be updated can be specified by the gate ID included in the gate passage information. For example, if the gate ID is “Gate01”, the passage date / time is set in the item indicating the production start date / time result in the process performance management table 115e. If the gate ID is “Gate02”, the passage date and time is set in the item indicating each process completion record date and time (A process) in the table.

Also, the part process management unit 124 calculates the actual number of days of each process every time the passage date and time is set in the item indicating each process of each process completion actual date and time. For example, in the case of an item indicating the A record, the number of days required from the production start date / time record to the A process completion record date / time is calculated and set. If it is an item indicating the B performance, the number of days required from the process completion performance date / time of the A process to the process completion performance date / time of the B process is calculated and set.

[Step ST4] The part process management unit 124 indicates an item indicating the production start date / time result of the process result management table 115e, an item indicating each process result (A, B, C result) of each process completion result date and time, and the number of delivery days. Based on the number of days set in the item, the total of all processes and the order delivery date are calculated. In addition, when the completion performance date / time is not set in the item indicating each process performance, the standard days are acquired with reference to the part standard process tables 115b, 115c, and 115d stored in the article process information storage unit 115, Calculate the total of all processes and the remaining delivery date.

[Step ST5] The part process management unit 124 sets the calculated order delivery date as an item indicating the order delivery date in the record of the corresponding order command ID in the part order remaining table 113a stored in the part order information storage unit 113. .

As described above, when the part process management unit 124 receives the gate passage information from the line terminal device 200, the part process management unit 124 acquires the progress of the part manufacturing process based on the gate ID and the passage time included in the gate passage information. Change the remaining delivery date.

In step ST3, if there is no process result management record for the corresponding order command ID, the part process management unit 124 receives the order command ID that is not registered in the process result management table 115e and receives the order command. It is conceivable to generate a process result management record for ID. Alternatively, it may be generated in advance at the timing when parts are ordered from the

suppliers

40, 40a, and 40b (timing when the ordering command ID is newly generated).

In step ST5, the part process management unit 124 delays the parts delivery date with respect to the sales terminal device 21, the ordering terminal device 22, and the terminal devices 41 and 42 when the order delivery date is changed after the initial delivery date. It is conceivable to send an alarm indicating that this is to be done. By notifying the delay of parts delivery in this way, the employees of the product manufacturing company 20 and

suppliers

40, 40a, 40b are notified of the delivery delay earlier, reviewing the production plan, expanding the allocation of parts production resources, etc. Can be encouraged.

Hereinafter, a specific example of the process of acquiring the manufacturing process progress information from the supplier 40 will be described. In the following description, it is assumed that the component box 70 to which the Kanban 60 is attached in FIG. 3 is manufactured through steps A, B, and C in order.

FIG. 31 is a sequence diagram illustrating a process of acquiring gate passage information. In the following, the process illustrated in FIG. 31 will be described in order of step number.
[Step ST11] When the gate 310 communicates with the Kanban 60 and obtains the ordering instruction ID, the gate 310 transmits to the line terminal device 200 gate passage information including the obtained ordering instruction ID, the gate ID of the gate 310, and the passage date and time. The line terminal device 200 receives the gate passage information.

[Step ST12] The line terminal device 200 transmits the gate passage information received in step ST11 to the management server 100. The management server 100 receives the gate passage information, and for the record of the corresponding order command ID in the process result management table 115e stored in the article process information storage unit 115, the item indicating the production start date / time record includes the pass date / time of the gate 310. Set. By setting the passage date / time to the item indicating the production start date / time record, it is possible to set information on the scheduled process completion date and delivery date of the corresponding part with reference to the part standard process table 115b. In addition, it is possible to set information on the total process and order delivery date from the standard process.

[Step ST13] When the gate 320 communicates with the Kanban 60 and obtains the ordering instruction ID, the gate 320 transmits gate ordering information including the acquired ordering instruction ID, the gate ID of the gate 320, and the passage date and time to the line terminal device 200. The line terminal device 200 receives the gate passage information.

[Step ST14] The line terminal device 200 transmits the gate passage information received in step ST13 to the management server 100. The management server 100 receives the gate passage information, and sets the passage date and time of the gate 320 in the item indicating each process completion record date (A process) for the record of the corresponding order command ID in the process record management table 115e. Then, the actual number of days required for the process A is calculated and set in an item indicating each process completion result date (A result). The actual number of days of the A process can be calculated by the number of days required from the production start date and time to the completion actual result date and time of the A process. As a result, the total of all processes and the remaining delivery date are updated based on the completion results up to process A.

[Step ST15] When the gate 330 communicates with the Kanban 60 and obtains the ordering instruction ID, the gate 330 transmits gate passage information including the obtained ordering instruction ID, the gate ID of the gate 330, and the passage date and time to the line terminal device 200. The line terminal device 200 receives the gate passage information.

[Step ST16] The line terminal device 200 transmits the gate passage information received in step ST15 to the management server 100. The management server 100 receives the gate passage information, and sets the passage date and time of the gate 330 in the item indicating each process completion result date and time (B process) for the record of the corresponding ordering command ID in the process result management table 115e. Then, the actual number of days required for the process B is calculated, and set in an item indicating each process completion record date (B record). The actual number of days of the B process can be calculated from the number of days required from the completion actual result date / time of the A process to the completion actual result date / time of the B process. As a result, the total of all processes and the remaining delivery date are updated according to the completion results up to the B process.

[Step ST17] When the gate 340 communicates with the Kanban 60 and obtains the ordering command ID, the gate 340 transmits gate passage information including the obtained ordering command ID, the gate ID of the gate 340, and the passage date and time to the line terminal device 200. The line terminal device 200 receives the gate passage information.

[Step ST18] The line terminal device 200 transmits the gate passage information received in step ST17 to the management server 100. The management server 100 receives the gate passage information, and sets the passage date and time of the gate 340 in an item indicating each process completion record date and time (C process) for the record of the corresponding order command ID in the process result management table 115e. Then, the actual number of days required for the C process is calculated, and set in an item indicating each process completion actual date and time (C actual result). The actual number of days of the C process can be calculated from the number of days required from the completion actual result date / time of the B process to the completion actual result date / time of the C process. As a result, the total of all processes and the remaining delivery date are updated based on the completion results up to the C process.

Thus, the line terminal apparatus 200 receives gate passage information from the

gates

310, 320, 330, and 340. Then, the line terminal device 200 stores the received gate passage information in the gate passage information storage unit 210 and transmits it to the management server 100.

Thereby, the management server 100 can acquire the progress status of the manufacturing process in the supplier 40 in real time.
Next, a production management process procedure in the management server 100 will be described.

FIG. 32 is a flowchart showing the production management process. In the following, the process illustrated in FIG. 32 will be described in order of step number.
[Step S1] Upon receiving an input of a new order from the sales terminal device 21, the management server 100 generates a new order record and stores it in the order table 112a stored in the component requirement information storage unit 112. In addition, the management server 100 generates a part requirement record based on the article master, the article configuration table, and the new order record stored in the article master storage unit 111, and the component requirement table stored in the part requirement information storage unit 112. 112b.

In addition, when receiving an input of a new order from the ordering terminal device 22, the management server 100 generates a part order record for the newly ordered part and stores it in the part order table 113 a stored in the part order information storage unit 113. Store. Also, the management server 100 updates the order delivery date of each part set in the part order remaining table 113a based on the gate passage information received from the line terminal device 200.

Furthermore, when the management server 100 receives an input of a new warehousing from the warehouse terminal device 26, the management server 100 generates a parts inventory record and stores it in the parts inventory table 114a stored in the parts inventory information storage unit 114.

[Step S2] When any of the records in the component requirement table 112b, the component order remaining table 113a, and the component inventory table 114a is updated, the management server 100 acquires the figure number and version number of the component included in the record. To generate an update figure number record. The management server 100 registers the generated update figure number record in the update figure number table 116 a stored in the allocation target part information storage unit 116.

[Step S3] The management server 100 generates an allocation target figure number table 116b based on the updated figure number table 116a and stores it in the allocation target part information storage unit 116.
[Step S4] The management server 100 performs an allocation process for the part of the figure number and version number registered in the allocation target figure number table 116b, and generates an allocation detail record. The management server 100 registers the generated allocation detail record in the allocation detail table 117 a stored in the part allocation detail storage unit 117. The management server 100 registers the order number, the figure number, and the version number of the product to be allocated in the allocation history table 117b stored in the component allocation details storage unit 117.

[Step S5] The management server 100 identifies the order number for which the allocation process has been performed based on the allocation history table 117b, generates a surface alignment target management table 118a, and stores it in the component surface alignment information storage unit 118.

[Step S6] The management server 100 performs a surface alignment process on the order number registered in the surface alignment target management table 118a, and generates a component surface alignment record. The management server 100 registers the generated component surface alignment record in the component surface alignment table 118b stored in the component surface alignment information storage unit 118.

[Step S7] The management server 100 performs a manufacturing management process for the product based on the component surface alignment table 118b, and generates a manufacturing plan management record. The management server 100 registers the generated manufacturing plan management record in the manufacturing plan management table 118 c stored in the part surface alignment information storage unit 118.

[Step S8] The management server 100 generates a delivery date reply table 119a based on the manufacturing plan management table 118c and stores it in the delivery date reply information storage unit 119.
[Step S9] When the management server 100 receives a delivery date reply request from the sales terminal device 21, the management server 100 responds with delivery date reply information based on the delivery date reply table 119a. The business terminal device 21 generates a delivery date reply screen based on the delivery date reply information and displays it on the monitor.

Thus, when the record is updated in the component requirement table 112b, the component order remaining table 113a, and the component inventory table 114a, the management server 100 performs an allocation process for the corresponding component. The management server 100 executes surface alignment processing based on the result, and updates manufacturing management information and delivery date reply information.

Hereinafter, each process shown in steps S2 to S8 will be described in detail.
First, the update figure number registration process in step S2 will be described.
FIG. 33 is a flowchart showing an update diagram number registration process. In the following, the process illustrated in FIG. 33 will be described in order of step number.

[Step S11] The allocation target figure number acquisition unit 131 refers to the component requirement table 112b stored in the component requirement information storage unit 112 and determines whether or not the component requirement record has been updated. If there is an update in the component requirement record, the process proceeds to step S12. If there is no update in the component requirement record, the process proceeds to step S13.

[Step S12] The allocation target figure number acquisition unit 131 acquires the figure number and version number from the updated part requirement record. Then, the process proceeds to step S17.
[Step S13] The allocation target figure number acquisition unit 131 refers to the component order remaining table 113a stored in the part ordering information storage unit 113, and determines whether or not the part order remaining record has been updated. If there is an update in the part order remaining record, the process proceeds to step S14. If there is no update in the part order remaining record, the process proceeds to step S15.

[Step S14] The allocation target figure number obtaining unit 131 obtains the figure number and version number from the updated part order record. Then, the process proceeds to step S17.
[Step S15] The allocation target figure number acquisition unit 131 refers to the component inventory table 114a stored in the component inventory information storage unit 114, and determines whether or not the component inventory record has been updated. If there is an update in the parts inventory record, the process proceeds to step S16. If there is no update in the parts inventory record, the process is completed.

[Step S16] The allocation target figure number acquisition unit 131 acquires the figure number and version number from the updated parts inventory record. Then, the process proceeds to step S17.
[Step S17] The allocation target figure number acquisition unit 131 registers the acquired figure number and version number in the updated figure number table 116a stored in the allocation target part information storage unit 116.

In this way, the allocation target figure number acquisition unit 131 updates the parts to the updated figure number table 116a at the timing when any update of the parts requirement table 112b, the parts order remaining table 113a, and the parts inventory table 114a is detected. Register the figure number and version number. Alternatively, the allocation target figure number acquisition unit 131 periodically refers to the component requirement table 112b, the component order remaining table 113a, and the component inventory table 114a to identify an updated record.

Here, the figure number / version number of the updated part is registered in the updated figure number table 116a. For this reason, the drawing number / version number of the same part can be registered in the updated drawing number table 116a as a target to be allocated. For this reason, the allocation target figure number generation process shown below collects duplicate figure numbers and version numbers, and generates information for identifying the parts that are the targets of the allocation process.

Hereinafter, the allocation object figure number generation process of step S3 is demonstrated.
FIG. 34 is a flowchart showing allocation target figure number generation processing. In the following, the process illustrated in FIG. 34 will be described in order of step number.

[Step S21] The allocation target figure number acquisition unit 131 acquires the updated figure number table 116a stored in the allocation target part information storage unit 116.
[Step S22] The allocation target figure number acquisition unit 131 arranges the records in the updated figure number table 116a by the figure number and the version number. For example, the records are sorted in ascending order of figure number / version number.

[Step S23] The allocation target figure number acquisition unit 131 extracts one record from each of the arranged records in a predetermined order (for example, ascending order of stored array numbers).
[Step S 24] Whether the allocation target figure number acquisition unit 131 is not registered in the allocation target figure number table 116 b stored in the allocation target part information storage unit 116 with the figure number / version number included in the extracted record. Determine whether or not. If it is unregistered, the process proceeds to step S25. If it is not unregistered, that is, if it is registered, the process proceeds to step S26.

[Step S25] The allocation target figure number acquisition unit 131 registers the figure number / version number included in the extracted record in the allocation target figure number table 116b.
[Step S26] The allocation target figure number acquisition unit 131 deletes the record extracted in step S23 from the updated figure number table 116a. For example, the same figure number / version number stored in the array continuously by sorting can be deleted at once in this step.

[Step S27] The allocation target figure number acquisition unit 131 has performed registration determination processing (processing of steps S23 to S26) in the allocation target figure number table 116b for all the records that have been aligned in the updated figure number table 116a. Determine. If all records have been processed, the process is completed. If there is an unprocessed record, the process proceeds to step S23.

As described above, the allocation target figure number acquisition unit 131 aggregates the duplicated figure number / version number records included in the updated figure number table 116a to generate the allocation target figure number table 116b.
It is conceivable that the allocation target figure number acquisition unit 131 executes the above allocation figure number generation process at predetermined time intervals. Further, it is conceivable to execute at a timing when a predetermined number of records are registered in the updated figure number table 116a.

In addition, when one record is registered in the updated figure number table 116a, the allocation target figure number acquisition unit 131 may identify it with the allocation target figure number table 116b. In this case, since the updated figure number table 116a is the same as the allocation target figure number table 116b, the above allocation figure number generation process need not be performed. In this case, every time an update record is generated in any of the component requirement table 112b, the component order remaining table 113a, and the component inventory table 114a, the subsequent allocation process is performed on the record, so that immediacy is improved.

On the other hand, assuming that the allocation target figure number table 116b is generated after a certain amount of records are accumulated in the update figure number table 116a as described above, the immediacy required when operating the system (the update frequency of the manufacturing plan, delivery date reply information, etc.) ) Can be adjusted. For example, by changing the interval for executing the allocation diagram number generation process to 10 seconds, 1 minute, 10 minutes, etc., it is possible to construct an environment in consideration of the influence on the entire business department.

Next, the allocation process in step S4 will be described.
FIG. 35 is a flowchart showing the allocation process. In the following, the process illustrated in FIG. 35 will be described in order of step number.

[Step S31] The allocation method determination unit 132 refers to the allocation target figure number table 116b stored in the allocation target part information storage unit 116 and acquires one allocation target figure number record.
[Step S32] The allocation method determination unit 132 refers to the article master 111a stored in the article master storage unit 111 based on the figure number / version number included in the acquired allocation target figure number record. Then, the allocation method determination unit 132 determines whether or not the corresponding component is a reserve allocation target component. If it is a reserve allocation target, the figure number / version number is output to the reserve allocation processing unit 133, and the process proceeds to step S33. If it is not a reserve allocation target, the figure number / version number is output to the quantity allocation processing unit 134, and the process proceeds to step S35.

[Step S33] The reserve allocation processing unit 133 executes reserve allocation pre-processing based on the figure number / version number acquired from the allocation method determination unit 132. Specifically, the reserve allocation processing unit 133 is stored in the allocation processing work area 150 in the component requirement information storage unit 112, the component order information storage unit 113, the component inventory information storage unit 114, and the component allocation detail storage unit 117. A part of each information is extracted as a snapshot and stored in the work area 150 for allocation processing.

[Step S34] The reserve allocation processing unit 133 executes reserve allocation processing using information such as free requirements, free inventory, and free stock provided in the allocation processing work area 150 in the reserve allocation pre-processing, Generate an allocation detail record for parts. The reserve allocation processing unit 133 registers the generated allocation details record in the allocation details table 117 a stored in the parts allocation details storage unit 117. Then, the process proceeds to step S36.

[Step S35] The quantity allocation processing unit 134 executes the quantity allocation process based on the figure number / version number acquired from the allocation method determination unit 132, and generates an allocation detail record for the allocation target part. The quantity allocation processing unit 134 registers the generated allocation details record in the allocation details table 117a. Then, the process proceeds to step S36.

[Step S36] The allocation method determination unit 132 determines whether allocation processing has been performed for all allocation target figure number records in the allocation target figure number table 116b. If all records have been allocated, the process is completed. If there is a record for which the allocation process has not been executed, the process proceeds to step S31.

In this way, the allocation method determination unit 132 determines whether to reserve for each part or to allocate a quantity with reference to the allocation target figure number record stored in the allocation target figure number table 116b and the article master 111a. To do. Then, according to the determined allocation processing method, the reserve allocation processing unit 133 and the quantity allocation processing unit 134 perform allocation processing for each component.

Below, the procedure of a reserve allocation process and a quantity allocation process is demonstrated in detail.
First, the reserve pre-allocation process in step S33 will be described.
FIG. 36 is a flowchart showing reserve allocation pre-processing. In the following, the process illustrated in FIG. 36 will be described in order of step number.

[Step S41] The reserve allocation processing unit 133 extracts the component requirement record stored in the component requirement information storage unit 112 using the figure number and version number acquired from the allocation method determination unit 132 as a key. Thereafter, each process is executed using the figure number / version number acquired from the allocation method determination unit 132 as a key.

[Step S42] The reserve allocation processing unit 133 stores the extracted component requirement record in the free requirement storage unit 151.
[Step S43] The reserve allocation processing unit 133 uses the figure number / version number as a key, the component order remaining table 113a stored in the component order information storage unit 113, and the allocation detail table stored in the component allocation detail storage unit 117. With reference to 117a, a part order record that is not allocated to any higher order article is extracted. Specifically, first, the reserve allocation processing unit 133 refers to the part order remaining table 113a, and identifies the part order remaining record of the corresponding figure number / version number. Then, it is the order ID set in the part order record, and is not set as the allocation source in each record of the corresponding figure number and version number in the allocation details table 117a (ie, inventory ID / note) The note remaining ID (not set in the item indicating the remaining ID) is specified. Thus, the extracted part order record can be identified as a part order record that has not been assigned to any higher-level item.

Further, the reserve allocation processing unit 133 refers to the component inventory table 114a and the allocation details table 117a stored in the component inventory information storage unit 114 using the figure number and the version number as a key, and for any higher-level article. Extract parts inventory records that have not been allocated. Specifically, first, the reserve allocation processing unit 133 refers to the parts inventory table 114a and identifies the parts inventory record of the corresponding figure number / version number. Then, an inventory ID that is set in the part inventory record and that is not set as an allocation source in each record of the corresponding figure number / version number in the allocation detail table 117a is specified. As a result, the extracted parts inventory record can be identified as a parts inventory record that has not been assigned to any higher-level item. Then, the reserve allocation processing unit 133 stores the extracted parts inventory record in the free inventory storage unit 153.

[Step S44] The reserve allocation processing unit 133 stores the extracted part order remaining record in the free order remaining storage unit 152. Also, the reserve allocation processing unit 133 stores the extracted parts inventory record in the free inventory storage unit 153.

[Step S45] The reserve allocation processing unit 133 uses the figure number / version number as a key, and the allocation details record that has already been associated (allocated) with the remaining parts or the inventory components from the allocation details table 117a. To extract. The reserve allocation processing unit 133 can specify a record that is set in the item indicating the inventory ID / remaining ID among the allocation detail records of the corresponding figure number / version number in the allocation detail table 117a as the allocated record.

[Step S46] The reserve allocation processing unit 133 stores the allocated allocation detail record in the allocation detail reserve storage unit 154.
[Step S 47] The reserve allocation processing unit 133 obtains the total S 1 of the required number of records whose priority classification is “1” among the component required records stored in the free requirement storage unit 151. And the reserve allocation process part 133 was set to the item which shows the allocation number of the record by which the required ID corresponding to priority classification "1" was set among the allocation detailed records stored in the allocation detailed reserve memory | storage part 154 The sum S2 of values is obtained. Then, a difference S3 (S3 = S1-S2) from the sum S1, S2 is obtained.

[Step S48] The reserve allocation processing unit 133 determines whether the difference S3 can be allocated from the free stock. If allocation is not possible, an allocation detail record having a priority classification of “0” in the component requirement record corresponding to the requirement ID is specified among the allocation detail records stored in the allocation detail reserve storage unit 154. Then, among the specified provision detail records, the provision date record set in the item indicating the required date is the latest provision detail record, and the parts inventory record is used as the provision source. Allocation is made to the allocation detail record corresponding to the priority category “1” by the amount obtained by subtracting the amount that can be allocated from the free stock from the difference S3. That is, the order number and the required ID set in the allocation detail record having the priority order “0” and the different order number are changed to the order number and the required ID of the corresponding record in the priority order “1”.

As described above, the reserve allocation processing unit 133 stores information on free requirements, free inventory, free stock, and reserved details in the allocation processing work area 150 as pre-processing for reserve allocation processing.

Thereby, it is possible to maintain consistency between the data stored in the part requirement information storage unit 112, the part order information storage unit 113, and the part inventory information storage unit 114, which can be updated in real time, and the allocation result.

In addition, the reserve allocation processing unit 133, when it is not possible to secure the necessary number of allocations from the free stock for the allocation detail record that is the target of the priority allocation, Reserve from the detail record. At this time, the allocation is performed from the latest allocation schedule record that is not subject to priority allocation, from the latest allocation date. In this way, the influence on the production plan and delivery date of each product can be minimized.

If the difference S3 = 0 in step S47, step S48 need not be executed.
Next, the reserve allocation process in step S34 will be described.

37 and 38 are flowcharts showing reserve allocation processing. In the following, the process illustrated in FIGS. 37 and 38 will be described in order of step number.
[Step S51] The reserve allocation processing unit 133 uses the figure number / version number acquired from the allocation method determination unit 132 as a key, and the allocation details record registered in the allocation details table 117a stored in the parts allocation details storage unit 117 Is deleted. This is because the allocation detail record of the corresponding figure number / version number is duplicated in the allocation detail reserve storage unit 154, and the allocation processing is performed again by the following processing. Thereafter, each process is executed using the figure number / version number acquired from the allocation method determination unit 132 as a key.

[Step S52] The reserve allocation processing unit 133 acquires one part requirement record stored in the free requirement storage unit 151 using the figure number and the version number as a key.
[Step S53] The reserve allocation processing unit 133 acquires the required ID set in the component required record.

[Step S54] The reserve allocation processing unit 133 searches the allocation details record stored in the allocation details reserve storage unit 154 using the acquired required ID as a key.
[Step S55] The reserve allocation processing unit 133 determines whether there is an allocation detail record in which the corresponding required ID is set. If it exists, the process proceeds to step S56. If not, the process proceeds to step S58.

[Step S56] The reserve allocation processing unit 133 stores all allocation detail records extracted as a result of the search in the allocation work information storage unit 155.
[Step S57] The reserve allocation processing unit 133 refers to the allocation detail record stored in the allocation work information storage unit 155 and determines whether there is a required remaining number for the corresponding component required record. If there is no required remaining number, the process proceeds to step S70. If there is a required remaining number, the process proceeds to step S58. The presence / absence of the required remaining number can be determined from the difference between the required remaining number before allocation set in the allocation detail record and the allocated number. For example, when the required remaining number before allocation of the allocation detail record is “60” and the allocation number is “10”, the difference between these is “50”. This indicates that the number of parts is insufficient by “50”. Therefore, in this case, it can be determined that there is a required remaining number. On the other hand, when the required remaining number before allocation is “50” and the allocated number is “50”, these differences are “0”, so that it can be determined that there is no required remaining number. In the same manner, it is possible to determine whether there is a required remaining number for each component in the same manner.

[Step S58] The reserve allocation processing unit 133 searches the parts inventory record stored in the free inventory storage unit 153 using the figure number and version number as a key.
[Step S59] The reserve allocation processing unit 133 determines whether there is a parts inventory record in which the corresponding figure number / version number is set. If it exists, the process proceeds to step S60. If not, the process proceeds to step S63.

[Step S60] The reserve allocation processing unit 133 generates an allocation detail record for the corresponding order number, required ID, component diagram number / version number based on the component inventory record acquired as a result of the search. The allocation detail record is generated in association with the parts inventory record. That is, when a plurality of parts inventory records can be acquired, the reserve allocation processing unit 133 generates a plurality of allocation detail records whose allocation category is “inventory” for each inventory ID of each parts inventory record. In addition, in the item indicating the required remaining number before allocation of each allocation detail record, a value obtained by subtracting the total number of allocations from the required number is set in the order in which the allocation detail records are generated.

[Step S61] The reserve allocation processing unit 133 stores the generated allocation detail record in the allocation work information storage unit 155.
[Step S62] The reserve allocation processing unit 133 refers to the allocation detail record stored in the allocation work information storage unit 155 and determines whether there is a required remaining number for the corresponding component required record. If there is no required remaining number, the process proceeds to step S70. If there is a required remaining number, the process proceeds to step S63.

[Step S 63] The reserve allocation processing unit 133 searches the part order remaining record stored in the free order remaining storage unit 152 using the figure number / version number as a key.
[Step S64] The reserve allocation processing unit 133 determines whether there is a part order remaining record in which the corresponding figure number / version number is set. If it exists, the process proceeds to step S65. If not, the process proceeds to step S67.

[Step S65] The reserve allocation processing unit 133 generates an allocation detail record for the corresponding order number, required ID, part diagram number / version number, based on the part order record acquired as a result of the search. The allocation detail record is generated in association with the part order record. In other words, the reserve allocation processing unit 133 generates a plurality of allocation detail records whose allocation category is “Notes” for each item ID of each component note record. In addition, in the item indicating the required remaining number before allocation of each allocation detail record, a value obtained by subtracting the sum of the allocation numbers so far from the required number in the order in which the allocation detail records are generated is set.

[Step S66] The reserve allocation processing unit 133 stores the generated allocation detail record in the allocation work information storage unit 155.
[Step S67] The reserve allocation processing unit 133 refers to the allocation detail record stored in the allocation work information storage unit 155 to determine whether there is a required remaining number for the corresponding component required record. If there is a required remaining number, the process proceeds to step S68. If there is no required remaining number, the process proceeds to step S69.

[Step S68] The reserve allocation processing unit 133 generates an allocation detail record for the allocation category “shortage” in which the required remaining number and the allocation number “0” are set, and stores the allocation detail record in the allocation work information storage unit 155.

[Step S69] The reserve allocation processing unit 133 registers the order number and figure number / version number of the newly generated allocation detail record in the allocation history table 117b stored in the part allocation detail storage unit 117.

[Step S70] The reserve allocation processing unit 133 determines whether or not reserve allocation processing has been executed for all the component requirement records stored in the free requirement storage unit 151. If all the component requirement records have been processed, the process proceeds to step S71. If there is an unprocessed part requirement record, the process proceeds to step S52. Note that the part requirement record for which the reserve allocation process is performed this time is treated as being processed, and is excluded from the record acquisition process in step S52.

[Step S71] The reserve allocation processing unit 133 registers all allocation details records stored in the allocation work information storage unit 155 in the allocation details table 117a stored in the part allocation details storage unit 117.

[Step S72] The reserve allocation processing unit 133 clears information stored in the allocation processing work area 150.
In this way, the reserve allocation processing unit 133 can perform allocation in consideration of the allocated products that have already been allocated from inventory or inventory.

That is, by making a reserve allocation, a part once allocated to a certain product is maintained in a state allocated to that product thereafter. For this reason, when a part is re-allocated, if a reserve allocation result already exists for the part, in addition to the reserve allocation result, a shortage can be additionally allocated. In addition, the reserved parts are not allocated to other products in principle. For this reason, the reserve allocation process is suitable for ensuring the allocation source for the parts with large fluctuations in the required amount.

Note that the reserve allocation processing unit 133 performs the reserve allocation processing with priority from the closest to the required date. At that time, the reserve allocation processing unit 133 allocates from the free order remaining from the order with the short remaining order. As a result, it is possible to prevent a situation in which the order delivery date is not in time even though the required date for parts is approaching.

Next, the quantity allocation process in step S35 will be described.
FIG. 39 is a flowchart showing the quantity allocation process. In the following, the process illustrated in FIG. 39 will be described in order of step number.

[Step S81] The quantity allocation processing unit 134 uses the figure number / version number acquired from the allocation method determination unit 132 as a key, and the allocation details record registered in the allocation details table 117a stored in the part allocation details storage unit 117 Is deleted. This is because the allocation detail record of the corresponding figure number / version number is recreated by the following processing. Thereafter, each process is executed using the figure number / version number acquired from the allocation method determination unit 132 as a key.

[Step S82] The quantity allocation processing unit 134 acquires one component requirement record from the component requirement table 112b stored in the component requirement information storage unit 112 using the figure number / version number as a key.

[Step S83] The quantity allocation processing unit 134 acquires the required number set in the component required record.
[Step S84] The quantity allocation processing unit 134 searches for a component inventory record from the component inventory table 114a stored in the component inventory information storage unit 114 using the figure number and the version number as a key.

[Step S85] The quantity allocation processing unit 134 determines whether there is a parts inventory record in which the corresponding figure number / version number is set. If it exists, the process proceeds to step S86. If not, the process proceeds to step S89.

[Step S86] The quantity allocation processing unit 134 generates an allocation detail record for the order number, required ID, part diagram number / version number of the corresponding part requirement record, based on the part inventory record acquired as a result of the search. The allocation detail record is generated in association with the parts inventory record as described in step S60 of FIG.

[Step S87] The quantity allocation processing unit 134 stores the generated allocation detail record in the allocation work information storage unit 155.
[Step S88] The quantity allocation processing unit 134 refers to the allocation detail record stored in the allocation work information storage unit 155 to determine whether there is a required remaining number for the corresponding component required record. If there is no required remaining number, the process proceeds to step S95. If there is a required remaining number, the process proceeds to step S89.

[Step S89] The quantity allocation processing unit 134 searches for a part order record from the part order table 113a stored in the part order information storage unit 113 using the figure number and the version number as a key.
[Step S90] The quantity allocation processing unit 134 determines whether there is a part order remaining record in which the corresponding figure number / version number is set. If it exists, the process proceeds to step S91. If not, the process proceeds to step S93.

[Step S91] The quantity allocation processing unit 134 generates an allocation detail record for the order number, the required ID, and the part diagram number / version number of the corresponding part requirement record based on the part order remaining record acquired as a result of the search. The allocation detail record is generated in association with the component order remaining record as described in step S65 of FIG.

[Step S92] The quantity allocation processing unit 134 stores the generated allocation detail record in the allocation work information storage unit 155.
[Step S93] The quantity allocation processing unit 134 refers to the allocation detail record stored in the allocation work information storage unit 155 to determine whether there is a required remaining number for the corresponding component required record. If there is a required remaining number, the process proceeds to step S94. If there is no required remaining number, the process proceeds to step S95.

[Step S94] The quantity allocation processing unit 134 generates an allocation detail record for the allocation category “shortage” in which the required remaining number and the allocation number “0” are set, and stores the allocation detail record in the allocation work information storage unit 155.

[Step S95] The quantity allocation processing unit 134 registers the order number and figure number / version number of the newly generated allocation detail record in the allocation history table 117b stored in the part allocation detail storage unit 117.

[Step S96] The quantity allocation processing unit 134 determines whether or not the quantity allocation process has been executed for all the part requirement records for the same drawing number / version number in the component requirement table 112b. If all parts required records for the same drawing number / version number have been processed, the process proceeds to step S97. If there is an unprocessed part requirement record, the process proceeds to step S82. It should be noted that the part requirement records for the same drawing number / version number that have undergone the current quantity allocation process are treated as processed and are excluded from the record acquisition process in step S82.

[Step S97] The quantity allocation processing unit 134 registers all the allocation details records stored in the allocation work information storage unit 155 in the allocation details table 117a stored in the parts allocation details storage unit 117. Then, the quantity allocation processing unit 134 clears the information stored in the allocation work information storage unit 155.

In this way, the quantity allocation processing unit 134 performs the quantity allocation process by reallocating all necessary parts for a certain part. At this time, the quantity allocation processing unit 134 performs the quantity allocation process with priority from the closest date. At that time, the reserve allocation processing unit 133 allocates from the component order remaining table 113a in the order of the remaining order delivery date. As a result, as in the case of the reserve allocation process, it is possible to suppress a situation in which the due date is not in time even though the required date for the parts is approaching.

Depending on the progress of the manufacturing process of the ordered parts, such as when the delivery date of the remaining parts is advanced or when the delivery date of the remaining parts is delayed, It is possible to flexibly change the provision from the source. For this reason, quantity allocation is suitable when using parts that are likely to be delivered quickly.

As described above, the allocation process is sequentially executed for the parts of each figure number / version number registered in the allocation target figure number table 116b.
Next, the surface alignment target extraction process in step S5 will be described.

FIG. 40 is a flowchart showing surface alignment target extraction processing. In the following, the process illustrated in FIG. 40 will be described in order of step number.
[Step S101] The surface alignment information update processing unit 141 refers to the allocation history table 117b stored in the part allocation detail storage unit 117, and acquires the order number of the allocation detail record updated in the allocation detail table 117a. If there are a plurality of allocation history records with the same order number in the allocation history table 117b, they are aggregated into one record. The process for that can be performed by the same method as the allocation object figure number generation process shown, for example in FIG.

[Step S 102] The surface alignment information update processing unit 141 registers the acquired order number in the surface alignment target management table 118 a stored in the component surface alignment information storage unit 118.
[Step S103] The surface alignment information update processing unit 141 deletes the allocation history record for the acquired order number from the allocation history table 117b.

As described above, the surface alignment information update processing unit 141 aggregates the records of the duplicate order numbers included in the allocation history table 117b to generate the surface alignment target management table 118a. The surface alignment information update processing unit 141 can identify an order number to be subjected to surface alignment processing by referring to the surface alignment object management table 118a.

Next, the surface alignment process in step S6 will be described.
FIG. 41 is a flowchart showing the surface alignment process. In the following, the process illustrated in FIG. 41 will be described in order of step number.

[Step S 111] The surface alignment information update processing unit 141 acquires one surface alignment target record from the surface alignment target management table 118 a stored in the component surface alignment information storage unit 118.
[Step S112] The surface alignment information update processing unit 141 acquires an order number included in the surface alignment target record.

[Step S113] The surface alignment information update processing unit 141 deletes the component surface alignment record registered in the component surface alignment table 118b stored in the component surface alignment information storage unit 118 using the acquired order number as a key. This is because the part surface alignment record of the corresponding order number is re-created by the following processing.

[Step S114] The surface alignment information update processing unit 141 acquires an allocation detail record from the allocation detail table 117a stored in the part allocation detail storage unit 117 using the order number as a key. The surface alignment information update processing unit 141 generates one component surface alignment record in which the same order number, figure number / version number, and required number are set from the acquired allocation detail record. That is, when the plane order information update processing unit 141 acquires a plurality of allocation detail records having the same order number from the allocation detail table 117a but having different figure numbers / version numbers, one part is assigned to each figure number / version number. Generate a flush record. For example, the allocation detail record having the order number “OR001” in the allocation detail table 117a has three types of figure numbers “DR011”, “DR012”, and “DR013” (all version numbers are “V01”). Accordingly, the surface alignment information update processing unit 141 generates three component surface alignment records corresponding to the three types of figure numbers for the order number “OR001”.

[Step S115] The surface alignment information update processing unit 141 determines whether there is an allocation detail record whose allocation category is “inventory” among the acquired allocation detail records. If it exists, the process proceeds to step S116. If not, the process proceeds to step S118.

[Step S116] The surface alignment information update processing unit 141 calculates the total number of allocations included in the allocation detail record whose allocation category is “inventory” for each figure number / version number, and generates the calculated values. Set in the item indicating the number of inventory reserves in the side-by-side record. For example, in the allocation detail table 117a, there are 3 records for the part with the drawing number “DR011” whose allocation classification is “inventory”. Then, from the total number of allocations set in each allocation detail record, the inventory allocation number can be calculated as “30 + 10 + 10 = 50”.

[Step S117] The surface alignment information update processing unit 141 sets the date of the required date set in the allocation detail record in the item indicating the inventory component surface alignment date of the component surface alignment record of each figure number / version number. . For example, in the allocation details table 117a, the required date of the part with the drawing number “DR011” is “2009/9/1”. Therefore, “2009/9/1” is set as the inventory part surface alignment date.

[Step S118] The surface alignment information update processing unit 141 determines whether there is an allocation detail record whose allocation classification is “remaining” among the acquired allocation detail records. If it exists, the process proceeds to step S119. If not, the process proceeds to step S121.

[Step S119] The surface alignment information update processing unit 141 executes the following processing for the allocation detail record whose allocation classification is “remaining order”.
(A1) The surface alignment information update processing unit 141 calculates the total number of allocations for each drawing number / version number even though the remaining delivery date is within the initial delivery date. Set in the item indicating the number of remaining reserves (within delivery date). For example, in the allocation detail table 117a, there is one record in which the allocation classification is “Note” for the part of the drawing number “DR011”. The order delivery date set in the allocation detail record is “2009/8/31”, which is in time for the initial delivery date (required date) “2009/9/1”. Therefore, the allocation number “50” is set to the remaining allocation number (within the delivery date) of the part surface alignment record of the figure number “DR011”. Here, the required date of the allocation details table 117a is treated as the initial delivery date (the same applies hereinafter).

(A2) The surface alignment information update processing unit 141 calculates the total number of allocations for each drawing number / version number, although the remaining order delivery date is delayed from the initial delivery date, and generates the calculated value for each component surface alignment record. Set in the item indicating the number of remaining reserves (delay). For example, in the allocation detail table 117a, there are two records whose allocation classification is “Note” for the part of the figure number “DR012”. Then, there are “2009/9/1” and “2009/9/2” in the remaining order delivery date set in the allocation detail record. Since the record “2009/9/1” is in time for the initial delivery date (required date) “2009/9/1”, it corresponds to the case of (A1) above. On the other hand, the record “2009/9/2” is not in time for the initial delivery date (required date) “2009/9/1” (in the case of A2). Accordingly, the allocation number “10” is set as the remaining allocation number (delay) of the part surface alignment record of the figure number “DR012”.

For each part number and version number, set the date with the latest order delivery date in the item indicating the order delivery date in each part alignment record. For example, in the allocation details table 117a, there are those with a part number “DR012” of the drawing number “2009/9/1” and “2009/9/2” for the order remaining delivery date. In this case, “2009/9/2”, which is the latest date for the part surface alignment record of the drawing number “DR012”, is set as the order delivery date.

[Step S120] The surface alignment information update processing unit 141 acquires a date with the latest order delivery date among the component surface alignment records having the same order number. The surface alignment information update processing unit 141 sets the acquired date as an item indicating the remaining part surface alignment date of the component surface alignment record of each drawing number / version number. For example, in the part surface alignment table 118b, the latest date of the order delivery date is “2009/9/2” among the three records having the order number “OR001”. Therefore, “2009/9/2” is set for the remaining part surface alignment date of these three records.

[Step S121] The surface arrangement information update processing unit 141 determines whether or not there is an unallocated item among the acquired allocation details records, that is, an allocation details record whose allocation category is “out of stock”. If it exists, the process proceeds to step S122. If not, the process proceeds to step S124.

[Step S122] The surface alignment information update processing unit 141 executes the following processing for an allocation detail record whose allocation classification is “unallocated”.
(B1) The surface alignment information update processing unit 141 calculates the total of the estimated delivery date within the initial delivery date for each figure number and version number, and has not arranged each component surface alignment record that generated the calculated value (within the delivery date) ). Here, the assumed delivery date is an expected delivery date when an order is placed with the

suppliers

40, 40a and 40b from the present time. For example, it is assumed that the total number of days required for manufacturing and delivery of each part set in the part standard process tables 115b, 115c, and 115d stored in the article process information storage unit 115 is regarded as a standard lead time until the part is received. The delivery date can be calculated.

(B2) The surface alignment information update processing unit 141 calculates, for each drawing number / version number, the total of the estimated delivery date delayed from the initial delivery date, and has not arranged each component surface alignment record that generated the calculated value (delay ). For example, in the allocation details table 117a, there is a “out of stock” part for the part number “DR013”. Here, it can be seen that the standard lead time for the part number “DR013” takes “4 days” from the part standard process table 115b. Therefore, assuming that the current date is August 30, 2009, if an order is placed with the supplier 40 for the part “DR013” from the present time, the estimated delivery date can be calculated as “2009/9/3”. However, this estimated delivery date is not in time for the initial delivery date “2009/9/1”. For this reason, the quantity “10” for the shortage is set in the unallocated (delayed) part surface alignment record of the drawing number “DR013”.

In addition, the date with the latest expected delivery date for each part number / version number is set in the item indicating the undelivered part delivery date of each part alignment record. In the example of the component surface alignment table 118b, only the component “DR013” includes those in the “out of stock” state. For this reason, “2009/9/3”, which is an assumed delivery date for “DR013” not yet arranged (delayed), is set as the unallocated parts delivery date. For other records, "-" (no setting) is displayed.

[Step S123] The surface alignment information update processing unit 141 acquires a date with the latest estimated delivery date (unarranged component delivery date) among the component surface alignment records having the same order number. The surface alignment information update processing unit 141 sets the acquired date as an item indicating the unarranged component surface alignment date of the component surface alignment record of each drawing number / version number. In the example of the part surface alignment table 118b, of the three records of the order number “OR001”, only the part “DR013” has the unarranged part delivery date set. For this reason, the date “2009/9/3” is set as the unarranged parts alignment date of each record.

[Step S124] The surface alignment information update processing unit 141 determines whether or not the surface alignment processing has been completed for all the surface alignment target records registered in the surface alignment object management table 118a. If it has been processed, the process is completed. If not, the process proceeds to step S111. Note that the surface alignment target record that has been subjected to the surface alignment processing this time is treated as processed. That is, the corresponding record is excluded from the record acquisition process in step S111. When the process is completed, the surface alignment information update processing unit 141 clears information registered in the surface alignment target management table 118a.

In this way, the surface alignment information update processing unit 141 performs surface alignment processing for the allocation detail record of the order number that has been updated in the allocation detail table 117a.
It should be noted that it is conceivable that the date of surface preparation of unreserved parts / unarranged parts will be ahead of the original delivery date for all parts corresponding to a certain order number. In that case, it is conceivable that the surface finish date of the remaining parts / unarranged parts is the later one for the stock parts. If it does in this way, it will become possible to set up the manufacture start of a product ahead of time by the below-mentioned processing. For this reason, adjustment with the manufacturing schedule of other products becomes possible from an earlier date, and manufacturing resources can be utilized more efficiently.

The manufacturing management unit 142 can generate a product manufacturing plan based on the component surface alignment table 118b generated as described above.
Next, the manufacturing management information generation process in step S7 will be described.

FIG. 42 is a flowchart showing manufacturing management information generation processing. In the following, the process illustrated in FIG. 42 will be described in order of step number.
[Step S 131] The manufacturing management unit 142 acquires a component surface alignment record of the updated order number from the component surface alignment table 118 b stored in the component surface alignment information storage unit 118. At this time, the manufacturing management unit 142 acquires all the component surface alignment records having the same order number.

[Step S132] The manufacturing management unit 142 deletes the manufacturing plan management record registered in the manufacturing plan management table 118c stored in the part surface alignment information storage unit 118 using the order number as a key. This is because the production plan management record of the corresponding order number is recreated by the following processing.

[Step S133] The manufacturing management unit 142 generates a manufacturing plan management record for each order number and each drawing number / version number of the part surface alignment record acquired in step S131. Then, the manufacturing management unit 142 calculates the quantity of each part that can be used for manufacturing the product based on the inventory allocation number set for each part in the acquired part surface alignment record. The manufacturing management unit 142 sets the calculated quantity of each part to an item indicating the number of used (inventory) of each newly generated manufacturing plan management record.

For example, there are three records of the order number “OR001” in the part surface alignment table 118b. The inventory allocation numbers of the parts “DR011”, “DR012”, and “DR013” are “50”, “30”, and “20”. The manufacturing management unit 142 refers to the article master 111a and the article configuration table 111b stored in the article master storage unit 111, and in order to generate the product “PD001”, each of these parts is in a 2: 1: 1 ratio. Detect that it is necessary. As a result, the manufacturing management unit 142 can recognize that the usable number “20” of “DR013” determines the upper limit number of products manufactured by inventory parts. The number of parts used can be specified as “40”, “20”, and “20”. Accordingly, “40”, “20”, and “20” are set in the items indicating the number of used (inventory) of the manufacturing plan management records of the parts “DR011”, “DR012”, and “DR013” of the order number “OR001”. Set.

Hereinafter, the manufacturing management unit 142 performs setting for each item of the newly generated manufacturing plan management record.
[Step S134] The production management unit 142 sets the date set in the item indicating the inventory part surface alignment date of the component surface alignment record in the item indicating the date of commencement (stock). In addition, the manufacturing management unit 142 calculates the date until the trial has been completed and sets it as an item indicating the date of trial (inventory), assuming that the production has started on the date of commencement date (inventory). The production management unit 142 refers to the product standard process table 115a stored in the article process information storage unit 115, and adds the total number of days until the trial to the date of the start date (stock). Calculations can be made.

In the example of the manufacturing plan management table 118c, the start date (inventory) for the manufacturing plan management record with the order number “OR001” is “2009/9/1”. Further, the corresponding product “PD001” requires “15 days” until trial is completed according to the product standard process table 115a. Therefore, “2009/9/15” is set as the date of trial (inventory).

[Step S135] The manufacturing management unit 142 calculates the quantity of each part that can be used for manufacturing the product including the remaining parts in the delivery date. The production management unit 142 sets the calculated quantity of each part as an item indicating the number of use of each production plan management record (within the order delivery date).

In the example of the production plan management table 118c, for the production plan management record of the order number “OR001”, the total number of provisions for each part of “DR011”, “DR012”, “DR013” from the inventory parts and the remaining parts within the due date The values excluding the used number (usable number) are “50 + 50−40 = 60”, “30 + 10−20 = 20”, and “20 + 20−20 = 20”. In order to manufacture the product “PD001”, each part is required in a quantity ratio of 2: 1: 1. Therefore, the number of parts used, including parts within the remaining delivery date, is “40”, “20”, “20”. " Therefore, “40”, “20”, and “20” are set in the items indicating the number of used parts (within the order delivery date).

[Step S136] The production management unit 142 calculates the quantity of each part that can be used in the production of the product, including the delivery delay delayed parts. The production management unit 142 sets the calculated quantity of each part as an item indicating the number of uses (remaining delay) of each production plan management record.

In the example of the production plan management table 118c, each of the “DR011”, “DR012”, and “DR013” from the inventory part, the in-delivery-ordered remaining part, and the delivery-date-delayed-ordered part for the production plan management record of the order number “OR001” The total number of parts allocated and excluding the number of used parts (usable number) is “60−40 = 20”, “20−20 + 10 = 10”, and “20−20 = 0”. For this reason, it is not possible to secure enough parts to manufacture the product “PD001”. Therefore, “0”, “0”, and “0” are set in the item indicating the number of parts used (note remaining delay).

[Step S137] The manufacturing management unit 142 sets an item indicating the date (starting) that can be started as follows.
(C1) The manufacturing management unit 142, when the product can be manufactured including the undelivered parts with late delivery date, includes the item with the delivery date delayed with the remaining delivery date in the item indicating the start date. Set a later date.

(C2) If the manufacturing management unit 142 cannot manufacture the product including the undelivered parts due to the delivery date and can manufacture the product including the unordered parts within the due date, the manufacturing management unit 142 will indicate the date when the product can start. The latest date is set in the item to be indicated.

(C3) In cases other than C1 and C2, the item indicating the start date (note remaining) is “-” (no setting).
In the example of the production plan management table 118c, the production plan management record of the order number “OR001” cannot be manufactured including the late delivery due part and the product can be produced including the remaining part within the delivery date. This is the case (case C2). For this reason, the manufacturing management unit 142 obtains “2009/9/1” with the latest order delivery date out of the remaining parts within the delivery date from the allocation details table 117a, and sets it as the start date (out of order). To do.

Also, the manufacturing management unit 142 calculates the date until the trial has been completed and sets the item indicating the date of trial (the remainder), assuming that the production has started on the date of the commencement date (the remainder). The manufacturing management unit 142 can perform this calculation by referring to the product standard process table 115a and adding the total number of days until the trial is completed to the date of the start date (note remaining).

In the example of the manufacturing plan management table 118c, the start date (note) is “2009/9/1” for the manufacturing plan management record of the order number “OR001”. Further, the corresponding product “PD001” requires “15 days” until trial is completed according to the product standard process table 115a. Therefore, “2009/9/15” is set as the date of trial (note remaining).

[Step S138] The manufacturing management unit 142 calculates the quantity of each part that can be used for manufacturing the product, including unarranged parts within the delivery date. The production management unit 142 sets the calculated quantity of each part as an item indicating the number of use of each production plan record (within an unallocated delivery date).

In the example of the manufacturing plan management table 118c, “DR011” and “DR012” from the inventory parts, the remaining parts within the due date, the remaining due parts within the due date, and the unarranged parts within the due date for the manufacturing plan management record of the order number “OR001”. , “DR013” is the total number of parts allocated, and the value excluding the used number (usable number) is “20-0 = 20”, “10-0 = 10”, “0-0 = 0 ". However, allocation from unallocated parts to products is also referred to herein as “reserve” (the same applies hereinafter). For this reason, it is not possible to secure enough parts to manufacture the product “PD001”. Accordingly, “0”, “0”, and “0” are set in the item indicating the number of parts used (within the unordered delivery date).

[Step S139] The manufacturing management unit 142 calculates the quantity of each part that can be used in the manufacture of the product, including parts that have not yet been delivered. The production management unit 142 sets the calculated quantity of each part as an item indicating the number of uses (unarranged delay) of each production plan record.

In the example of the manufacturing plan management table 118c, “DR011” and “DR012” from the inventory parts, the remaining parts within the due date, the remaining parts due to the due date, and the unarranged parts within the due date for the manufacturing plan management record of the order number “OR001”. , “DR013” is the total number of parts allocated, and the values excluding the used number (usable number) are “20 + 0 = 20”, “10 + 0 = 10”, and “0 + 10 = 10”. In order to manufacture the product “PD001”, each part is required in a quantity ratio of 2: 1: 1. Therefore, the number of parts used, including parts within the remaining delivery date, is “20”, “10”, “10”. " Therefore, “20”, “10”, and “10” are set in the item indicating the number of parts used (unarranged delay).

[Step S140] The manufacturing management unit 142 sets an item indicating the date (unarranged) that can be started as follows.
(D1) When the manufacture management unit 142 can manufacture a product including undelivered parts, the latest delivery date of the undelivered parts in the item indicating the start date (unarranged) is the latest. Set the date.

(D2) The manufacturing management unit 142 does not manufacture the product including the parts that are not yet delivered due to delivery, and if the product can be manufactured including the parts that are not yet delivered within the delivery date, The latest date of the assumed delivery date of the parts not yet arranged within the delivery date is set in the item shown.

(D4) In the case other than D1 and D2, the item indicating the date (unarranged) that can be started is “-” (no setting).
In the example of the production plan management table 118c, the production plan management record of the order number “OR001” can be manufactured including the parts that have not been delivered due to the delivery date (in the case of D1). For this reason, the manufacturing management unit 142 obtains “2009/9/3” having the latest estimated delivery date from the parts surface alignment record among the undelivered parts that have not been delivered, and sets them as possible start dates (unarranged).

Also, the manufacturing management unit 142 calculates the date until the trial has been completed and sets it as an item indicating the date of trial (unarranged), assuming that the manufacturing has started on the date of commencement (unarranged). The production management unit 142 can perform this calculation by referring to the product standard process table 115a and adding the total number of days until the trial is completed to the date of commencement date (unarranged).

In the example of the manufacturing plan management table 118c, the start date (unarranged) for the manufacturing plan management record of the order number “OR001” is “2009/9/3”. Further, the corresponding product “PD001” requires “15 days” until trial is completed according to the product standard process table 115a. Therefore, “2009/9/17” is set as the date of trial (unarranged).

[Step S141] The manufacturing management unit 142 determines whether or not the production plan information has been generated for the part surface alignment records of all the order numbers for which the component surface alignment table 118b has been updated. If there is an unprocessed part surface alignment record, the process proceeds to step S131. If all the component surface alignment records have been processed, the processing is completed. Note that the part surface alignment record for which the production plan information generation process is performed this time is handled as processed. That is, the corresponding record is excluded from the record acquisition process in step S131.

In this way, the manufacturing management unit 142 can generate the manufacturing plan management table 118c based on the component surface alignment table 118b. Here, the manufacturing plan management table 118c reflects the process progress of parts in the

suppliers

40, 40a, and 40b immediately. Therefore, the production management unit 142 can accurately manage the date when the production of each product can be started by the production plan management table 118c.

Also, the manufacturing management unit 142 can manage the competition status of manufacturing schedules with other products based on the manufacturing plan management table 118c. In addition, it is possible to perform manufacturing management such as assigning to each product on the factory line, changing the schedule for starting the manufacturing, and giving a product manufacturing instruction. In addition, the manufacturing management unit 142 can manage the process of the factory line and issue a shipping instruction for a product that has been manufactured. This makes it possible to efficiently manage from product manufacture to shipment.

Further, the manufacturing plan management table 118c is used for generating delivery date reply information.
Next, the delivery date reply information generation process in step S8 will be described.
FIG. 43 is a flowchart showing delivery date reply information generation processing.

[Step S151] The delivery date reply information generation unit 143 obtains a production plan management record of the updated order number in the production plan management table 118c stored in the part surface alignment information storage unit 118. At this time, the delivery date response information generation unit 143 acquires all the production plan management records of the same order number.

[Step S152] The delivery date reply information generation unit 143 deletes the delivery date reply record registered in the delivery date reply table 119a stored in the delivery date reply information storage unit 119 using the order number as a key. This is because the delivery date response record of the corresponding order number is recreated by the following processing.

[Step S153] The delivery date response information generation unit 143 generates one delivery date response record with the order number of the manufacturing plan management record acquired in step S151. The delivery date response information generation unit 143 sets one product drawing number / version number set in each manufacturing plan management record acquired in this delivery date response record. Then, the delivery date response information generation unit 143 calculates the quantity of products that can be manufactured based on the number of uses (inventory) set for each part of the acquired manufacturing plan management record. The delivery date response information generation unit 143 sets the calculated quantity as an item indicating the production possible number (inventory) of each newly created delivery date response record.

In the example of the delivery date reply table 119a, there are three records “OR001” in the production plan management table 118c for the record of the order number “OR001”. The number of parts used (inventory) of “DR011”, “DR012”, and “DR013” in each production plan management record is “40”, “20”, and “20”. The delivery date response information generation unit 143 refers to the article master 111a and the article configuration table 111b stored in the article master storage unit 111, and each of these parts has a quantity “10” in order to generate the product “PD001”. It detects that only “5” and “5” are necessary. Thereby, the delivery date reply information generation part 143 can specify that the quantity of the product which can be manufactured with stock parts is "4". Therefore, “4” is set in the item indicating the production possible number (inventory).

Hereinafter, the delivery date response information generation unit 143 performs setting for each item of the newly generated delivery date response record.
[Step S154] The delivery date reply information generating unit 143 calculates the quantity of products that can be manufactured including the remaining parts within the delivery date. The delivery date reply information generation unit 143 sets the calculated quantity as an item indicating the number that can be manufactured (within the remaining delivery date).

In the example of the delivery date reply table 119a, the number of parts used in “DR011”, “DR012”, and “DR013” of each production plan management record corresponding to the record of the order number “OR001” is “40”. "20" and "20". Thereby, the delivery date reply information generation unit 143 can specify that the quantity of products that can be manufactured including the remaining parts in the delivery date is “4”. Therefore, “4” is set in the item indicating the number of products that can be manufactured (within the order delivery date).

[Step S155] The delivery date response information generation unit 143 calculates the quantity of products that can be manufactured including the delivery date delayed remaining parts. The delivery date reply information generating unit 143 sets the calculated quantity as an item indicating the number of manufacturable products (remaining delay).

In the example of the delivery date reply table 119a, the number of parts used (“remaining delay”) of “DR011”, “DR012”, “DR013” in each manufacturing plan management record corresponding to the record of the order number “OR001” is “0”. , “0”, “0”. Therefore, “0” is set in the item indicating the number of manufacturable products (remaining delay).

[Step S156] The delivery date reply information generating unit 143 calculates the quantity of products that can be manufactured including unarranged parts within the delivery date. The delivery date reply information generation unit 143 sets the calculated quantity as an item indicating the number that can be manufactured (within the unallocated delivery date).

In the example of the delivery date reply table 119a, the number of parts used in “DR011”, “DR012”, and “DR013” of each production plan management record corresponding to the record of the order number “OR001” is “0”. "," 0 "," 0 ". Therefore, “0” is set in the item indicating the number of manufacturable products (within the unallocated delivery date).

[Step S157] The delivery date reply information generation unit 143 calculates the quantity of products that can be manufactured including parts that have not been delivered yet. The delivery date reply information generating unit 143 sets the calculated quantity as an item indicating the number that can be manufactured (unarranged delay).

In the example of the delivery date reply table 119a, the number of used parts (unarranged delay) of “DR011”, “DR012”, and “DR013” in each production plan management record corresponding to the record of the order number “OR001” is “20”. , “10”, “10”. Therefore, “2” is set in the item indicating the number of manufacturable products (unarranged delay).

[Step S158] The delivery date response information generation unit 143 acquires the latest date of the start date of the start of the acquired production plan management record, and sets it as an item indicating the final surface alignment (start) scheduled date.

In the example of the delivery date reply table 119a, the available dates of stock, remnant, and unarranged corresponding to the record of the order number “OR001” are “2009/9/1”, “2009/9/1”, “2009/9/3”. Therefore, “2009/9/3” is set in the item indicating the final surface alignment (start) scheduled date.

[Step S159] The delivery date reply information generating unit 143 acquires the latest date of the date of trial from the acquired production plan management record, and sets it as an item indicating the scheduled date of final trial.
In the example of the delivery date reply table 119a, the respective dates of inventory, remnant, and unarranged corresponding to the record of the order number “OR001” are “2009/9/15”, “2009/9/15”, “2009/9/17”. Therefore, “2009/9/17” is set in the item indicating the scheduled final trial date.

Note that the delivery date reply information generation unit 143 can also obtain the scheduled final date by adding the standard process days of the product to the final surface alignment (start) scheduled date acquired in step S158.
[Step S160] The delivery date response information generation unit 143 determines whether delivery date response information has been generated for the production plan management records of all the order numbers for which the production plan management table 118c has been updated. If there is an unprocessed manufacturing plan management record, the process proceeds to step S151. If all the production plan management records that have been updated have been processed, the processing is completed. Note that the manufacturing plan management record for which the delivery date reply information is generated this time is treated as processed. That is, the corresponding record is excluded from the record acquisition process in step S151.

In this way, the delivery date response information generation unit 143 generates the delivery date response table 119a. The delivery date reply table 119a immediately reflects the progress of the parts manufacturing process in the

suppliers

40, 40a, and 40b. For this reason, the delivery date reply processing unit 144 makes a delivery date reply based on the delivery date reply table 119a, thereby enabling a highly accurate delivery date reply in accordance with the current situation.

Furthermore, the delivery date response information generation unit 143 manages the number of products that can be manufactured according to the purchase status of parts (stocked items, unordered items, unordered items). As a result, when a delay in the delivery date of the product to the customer occurs, it is possible to grasp whether it is due to a delivery delay delayed remaining part or due to an undelivered part. As a result, it is possible to identify an unreserved part or an unarranged part that is a bottleneck by referring to the part surface alignment table 118b or the manufacturing plan management table 118c, and to follow procurement of the part at an early stage. For example, it may be possible to take measures such as requesting new orders from other suppliers, expanding parts manufacturing resources, or considering application of alternative parts.

It should be noted that the product manufactured by the product manufacturing company 20 may be an intermediate product. Here, as described with reference to FIG. 12, the intermediate product is an article manufactured by the product manufacturing company 20, but is an article that is a part of another higher-level article. Since the intermediate product is also an article manufactured by the product manufacturing company 20, it can be managed by the article master storage unit 111 and the like as with other products.

In this case, the intermediate product can be managed by the parts order remaining table 113a (for example, the ordering party is managed as its own factory). For this reason, a change in the scheduled date of trial of an intermediate product is a change in delivery date as a part of the intermediate product. Therefore, in such a case, the change in the scheduled delivery date of the part purchase remaining table 113a is changed by changing the scheduled date of trial as the change in the delivery date of the intermediate product. As a result, even when the scheduled date for trial of the intermediate product is changed, the influence can be immediately reflected in the manufacturing process of the upper article.

FIG. 44 is a diagram showing a delivery date reply screen. The delivery date reply screen 400 is generated based on the delivery date reply table 119a stored in the delivery date reply information storage unit 119 by the delivery date reply processing unit 144 in response to a delivery date reply request from the sales terminal device 21 or the like. The delivery date reply screen 400 is displayed on the monitor of the sales terminal device 21 or the like. The delivery date response request includes an order number indicating an order for which the delivery date response is to be confirmed. The delivery date response processing unit 144 can extract a corresponding delivery date response record from the delivery date response table 119a based on the order number.

The delivery date reply screen 400 includes information such as an order number, customer name, product name, product number, quantity, reply delivery date, and update date / time. Information such as the order number, customer name, product name, product number, and quantity can be acquired from the order master table 111 a stored in the article master storage unit 111 and the order table 112 a stored in the component requirement information storage unit 112. . The answer delivery date can be acquired by adding the standard number of days necessary for delivery based on the scheduled final date of the delivery date reply table 119a.

In the example of the delivery date reply screen 400, the scheduled final date “2009/9/17” can be acquired from the delivery date reply record for the order number “OR001”. The standard delivery number “1 day” necessary for delivery is added to this, and the answer delivery date “2009/9/18” is displayed. Note that various information such as the standard number of days necessary for delivery is stored in advance in the delivery date reply information storage unit 119.

Also, as the update date and time, a time stamp indicating the generation date and time of the delivery date response record based on the delivery date response screen 400 is displayed. It is conceivable that the time stamp response information generation unit 143 assigns the time stamp to the due date response record at the timing when each due date response record is generated. For example, the employee of the product manufacturing company 20 can grasp whether or not the delivery date has changed since the previous delivery date response confirmation by confirming this time stamp.

FIG. 45 is a diagram showing the reflection from the collection of various data to the production plan. The management server 100 collects new order information, parts inventory information, and update information of progress information in the manufacturing process of ordered parts from the sales terminal device 21, the warehouse terminal device 26, and the line terminal device 200.

For example, upon receiving a new order input or an update input of the order contents, the order receiving / order management unit 120 updates the component requirement table 112b stored in the component requirement information storage unit 112 in real time based on the input. When the ordered / ordered product management unit 120 places an order for a missing part, a part to be regularly ordered, or the like from the supplier 40, it updates the part order remaining table 113 a stored in the part ordering information storage unit 113 in real time.

In addition, when receiving / receiving item information indicating that a part has been received from the warehouse terminal device 26 to the warehouse 25, the order-order-item management unit 120 receives the part inventory stored in the parts inventory information storage unit 114 based on the contents. The table 114a is updated in real time.

Further, when receiving / receiving the progress information (corresponding to the gate passing information) of the manufacturing process of the parts ordered from the line terminal apparatus 200 to the supplier 40, the order receiving / order management unit 120 stores the article process information based on the contents. The process performance management table 115e stored in the unit 115 is updated in real time. As a result, when a change occurs in the remaining order delivery date, the changed delivery date is reflected in the parts order remaining table 113a in real time.

When the data stored in the part requirement information storage unit 112, the part order information storage unit 113, and the part inventory information storage unit 114 are updated, the part allocation processing unit 130 manufactures a product based on the updated data. Provision of parts for Based on the allocation result, the production plan management unit 140 can generate a production plan management table 118c for managing the product production plan and a delivery date reply table 119a for making a delivery date reply.

Here, it is conceivable that the allocation timing by the parts allocation processing unit 130 is changed according to the operation. For example, it may be executed at a predetermined time interval, executed at a timing when a predetermined number of update data is accumulated, or executed at a timing when an update is detected with any data. By adjusting the timing of the allocation process in this way, it is possible to adjust the immediacy (update frequency of manufacturing plan, delivery date reply information, etc.) required when operating the system. For example, by changing the interval for executing the allocation diagram number generation process to 10 seconds, 1 minute, 10 minutes, etc., it is possible to construct an environment in consideration of the influence on the entire business department. It is also conceivable to adjust the allocation processing load of the management server 100 by changing the number of update records to “100”, “200”, “300”, etc.

Such a timing setting change can be performed, for example, by an operation input that designates any timing on the management server 100 by a person who has an operation authority to the management server 100. Alternatively, the management server 100 may provide a terminal device via the network 10 with a GUI that can be operated only by a person who has authority to perform such an environment setting.

FIG. 46 is a diagram showing information linkage between departments and with suppliers. The management server 100 centrally manages various types of information in the management information storage unit 110.
Employees of the product manufacturing company 20 and the

suppliers

40, 40a, and 40b manage the management information storage unit 110 via the sales terminal device 21, the ordering terminal device 22, the warehouse terminal device 26, the terminal devices 41 and 42, the line terminal device 200, and the like. Can be accessed. The operations that can be performed on the management information storage unit 110 are restricted depending on, for example, the company, department, or position to which the employee belongs. The management server 100 can manage such access restrictions in association with the identification information of the employee.

In addition, it is considered that electronic commerce is conducted between the product manufacturing company 20 and the

suppliers

40, 40a, 40b in accordance with BtoB (Business-to-Business) cooperation in response to an order from the product manufacturing company 20 to the

suppliers

40, 40a, 40b. It is done. In this way, settlement according to the order contents can be automated.

Here, heretofore, for example, if the department is different from the sales department / business department / manufacturing department / purchasing department in the same company, for example, each department often operates different systems. This was especially true if the companies were different, such as between a product manufacturer and a supplier. In this case, it is necessary to synchronize data managed between departments and between companies. For example, data is shared by batch processing such as daily or data input through a person. In that case, if data inconsistency occurred, the accuracy of the manufacturing plan and the delivery date response was reduced.

On the other hand, as described above, each department of the product manufacturing company 20 and the

suppliers

40, 40a, and 40b can access the management information storage unit 110 that centrally manages information. For this reason, it is not necessary to manage data individually in each department / company. This makes it possible to share production management information on products and parts in real time between the departments of the product manufacturing company 20 and the

suppliers

40, 40a, 40b. In other words, it is possible to realize comprehensive production management from order receipt to delivery to customers in each department / company. In addition, since it is not necessary to consider the consistency of data in each department / company, data management is facilitated, and accuracy of various information such as manufacturing plans and delivery date responses can be improved.

The production management apparatus, production management system, production management program, and production management method of the present invention have been described based on the illustrated embodiments. However, the present invention is not limited thereto, and the configuration of each unit has the same function. It can be replaced with one having any structure. Moreover, other arbitrary structures and processes may be added. Further, any two or more configurations (features) of the above-described embodiments may be combined.

The above merely shows the principle of the present invention. In addition, many modifications and changes can be made by those skilled in the art, and the present invention is not limited to the precise configuration and application shown and described above, and all corresponding modifications and equivalents may be And the equivalents thereof are considered to be within the scope of the invention.

DESCRIPTION OF SYMBOLS 1 Production management apparatus 1a Article management information storage part 1b Parts allocation detail storage part 1c Production plan information storage part 1d Parts process management part 1e Allocation processing part 1f Production plan management part 2 Terminal apparatus 2a Progress information acquisition part 5 Manufacturing line 5a, 5b , 5c Manufacturing process

Claims

When the progress information of the manufacturing process transmitted every time the part passes a predetermined checkpoint is received from the terminal device that manages the manufacturing process of the part, it is stored in the article management information storage unit based on the received progress information. A part process management unit for updating the delivery date of the part included in the parts management information
When the part process management unit updates the part management information, the product is based on the updated part management information and requirement information indicating the required number of parts for the product stored in the article management information storage unit. An allocation processing unit for allocating the part to generate allocation detail information indicating the allocation result and storing the allocation detail information in the component allocation detail storage unit;
When the allocation processing unit generates the allocation details information, production plan management generates production plan information for managing the production schedule of the product based on the allocation details information stored in the parts allocation details storage unit And
A production management device comprising:
The article management information storage unit maintains the provisioned state of the part for the product and reserves the part after the part management information is updated when the part is provisioned for any product. Information indicating whether or not reserve allocation, which is an allocation method to be performed, is stored in the article master associated with the part;
The allocation processing unit refers to the article master stored in the article management information storage unit at the time of the allocation, and when the part is a target of the reserve allocation, the allocation processing unit is stored in the article management information storage unit The reserve allocation is performed based on the requirement information, the component management information, and the allocation detail information of the component stored in the component allocation detail storage unit, and the allocation detail information is updated based on the reserve allocation result ,
The production management device according to claim 1, wherein:
The allocation processing unit includes the required number of parts included in the required amount information stored in the article management information storage unit, an allocation possible number indicating the number of parts that can be allocated included in the part management information, The allocation details information of the parts stored in the delivery date and the allocation details information storage unit is extracted and stored in the temporary storage unit, the required number of the parts stored in the temporary storage unit, the allocation possible number, and the 3. The production management apparatus according to claim 2, wherein the reserve allocation is performed based on the allocation details information of parts.
The article management information storage unit includes, as the part management information, inventory information including the inventory quantity of the parts not allocated to any product and the manufacturing process not allocated to any product. Memorizing information including the memorized number of the parts in the memory,
The allocation processing unit refers to the inventory information and the remaining inventory information stored in the article management information storage unit, extracts the possible allocation number based on the inventory quantity and the remaining inventory number, and the temporary storage unit 4. The production management device according to claim 3, wherein the production management device is stored in a storage area.
The allocation detail storage unit is in an unallocated state in which no allocation is made from the first allocation detail information indicating the parts in the allocated state and any of the inventory information and the remaining information. Storing second allocation details information indicating a part;
The allocation processing unit stores the first allocation details information stored in the parts allocation details storage unit in the temporary storage unit, and the first allocation details information stored in the parts allocation details storage unit Deleting the second allocation detail information, referring to the temporary storage unit, performing the reserve allocation, and storing the allocation detail information generated as a result of the reserve allocation in the allocation detail information storage unit,
The production management apparatus according to claim 4, wherein:
The allocation processing unit is configured to calculate the required number of parts, the possible allocation number, the delivery date, and the allocation details information from the requirement information, the parts management information and the allocation details information stored in the article management information storage unit. 6. The production management apparatus according to any one of claims 3 to 5, wherein information including the same is extracted at the same timing.
The article management information storage unit is a priority object that gives the reserve allocation of the parts for the product as priority information over the reserve allocation for other products that is the reserve allocation of the parts for other products. Including information indicating whether or not
The allocation processing unit refers to the requirement information at the time of reserve allocation, and when the reserve allocation is the priority target, the reserve allocation unit is based on a result of the reserve allocation for other products that is not the priority target. I do,
The production management apparatus according to any one of claims 2 to 6, wherein the production management apparatus is any one of claims 2 to 6.
When the reserve allocation is the priority target, the allocation processing unit gives priority to the product with the latest product delivery date for delivering the other product to the order receiving party among the plurality of other products that are not the priority target. 8. The production management apparatus according to claim 7, wherein the reserve allocation is performed based on a result of the reserve allocation for the other product specified and specified for the specified other product.
2. The provision processing unit according to claim 1, wherein the provision processing unit changes the provision processing timing to a timing specified by the setting input when receiving a setting input for prompting a change in the provision processing timing for performing the provision. The production management device according to any one of Items 8 to 8.
The allocation processing unit includes, as a result of the allocation, if there is a shortage of the part with respect to the required number, that the part has a shortage, and includes information indicating the shortage quantity in the provision detail information. The production management device according to any one of claims 1 to 9, wherein:
The component process management unit is stored in the component identification information, the checkpoint identification information, a time stamp indicating when the component has passed the checkpoint, and a component standard process storage unit included in the progress information. The delivery date of the part is calculated based on a standard number of days required for manufacturing the part, and the part management information stored in the article management information storage unit based on the calculated delivery date is included in the part management information. The production management apparatus according to any one of claims 1 to 10, wherein the delivery date of a part is updated.
The article management information storage unit stores the required amount information including a required date predetermined for the part,
The production management according to any one of claims 1 to 11, wherein the part process management unit issues an alarm that the receipt of the part is delayed when the delivery date is later than the required date. apparatus.
The production plan management unit identifies a startable time point at which the manufacture of the product can be started based on a delivery date of the part included in the allocation details information, and the specified startable time point is used as the production plan information. The production management apparatus according to any one of claims 1 to 12, wherein the production management apparatus is included.
The provision detail information storage unit stores the provision detail information in association with the delivery date of each part and the product manufactured from each part,
The production plan management unit sets the latest delivery time among the delivery times of the parts for manufacturing the product as the startable time point.
The production management apparatus according to claim 13, wherein
When the allocation detail information includes information indicating that any one of the parts is insufficient with respect to the required number of the products, the production plan management unit stores the information in the part standard process storage unit. The stored standard lead time from ordering to receipt of the missing part is acquired, and the delivery date with the latest delivery date calculated from the current standard lead time for the missing part is determined as the possible start time. The production management apparatus according to claim 14, wherein:
The production plan management unit includes a first startable point in time at which the manufacture of the product can be started using the parts being manufactured in the manufacturing process and the parts in stock, and the first start The production plan information includes an unused part at a possible time point and a second possible time point at which the production of the product can be started using the missing part. The production management apparatus according to item 15.
The production plan management unit generates the production plan information including a third possible start time that is predetermined as the scheduled start time of the product using the parts in stock, and stores the production plan information in the production plan information storage unit. And when the first startable time point and the second startable time point are earlier than the third startable time point, the production plan information storage unit stores the 16. The range according to claim 16, wherein the third startable time point included in the production plan information is changed to the later one of the first startable time point and the second startable time point. The production management device described.
The identification information of the component and the communication stored in the communication device are stored from a communication device that stores identification information of the component, communicates with a wireless tag attached to the component, and is provided at a predetermined check point of the production line Upon receipt of device identification information, it generates progress information including the component identification information, the communication device identification information, and a time stamp indicating when the component has passed the checkpoint, and transmits the generated progress information. Progress information acquisition unit,
A terminal device comprising:
When the progress information is received from the terminal device, a part process management unit that updates the delivery date of the part included in the part management information stored in the article management information storage unit based on the received progress information;
When the part process management unit updates the part management information, the product is based on the updated part management information and requirement information indicating the required number of parts for the product stored in the article management information storage unit. An allocation processing unit for allocating the part to generate allocation detail information indicating the allocation result and storing the allocation detail information in the component allocation detail storage unit;
When the allocation processing unit generates the allocation detail information, the production plan management generates production plan information for managing the production schedule of the product based on the allocation detail information stored in the parts allocation detail storage unit And
A production management device comprising:
A production management system comprising:
Computer
When the progress information of the manufacturing process transmitted every time the part passes a predetermined check point is received from the terminal device that manages the manufacturing process of the part, it is stored in the article management information storage unit based on the received progress information. Parts process management means for updating the delivery date of the parts included in the parts management information
When the part process management means updates the part management information, the product is based on the updated part management information and requirement information indicating the required number of parts for the product stored in the article management information storage means. An allocation processing means for allocating the parts to generate allocation details information indicating the allocation result and store the allocation details information in the parts allocation details storage means,
When the allocation processing unit generates the allocation detail information, production plan management generates production plan information for managing the production schedule of the product based on the allocation detail information stored in the part allocation detail storage unit means,
Production management program characterized by functioning as
A production management method for a production management device, comprising:
The production management device is
When the progress information of the manufacturing process transmitted every time the part passes a predetermined checkpoint is received from the terminal device that manages the manufacturing process of the part, it is stored in the article management information storage unit based on the received progress information. Update the delivery date of the part included in the received parts management information,
Allocation specification information for allocating the part for the product and indicating the allocation result based on the updated part management information and the requirement information indicating the required number of parts for the product stored in the article management information storage unit Is generated and stored in the part allocation details storage unit,
Generate production plan information for managing the production schedule of the product based on the generated provision details information,
A production management method characterized by that.