WO2021059427A1 - Procurement assistance method and procurement assistance system - Google Patents

Abstract

The present invention performs management in which components are delivered neither late nor prematurely on a production start date that is an overall indicator in procurement work including a plurality of procurement steps.　In this procurement assistance method executed by a procurement assistance system S, a production start date determination unit 11 uses a production plan for a product comprising a plurality of components as a basis to determine a production start date for at least one production step for producing the product and divides procurement work for individual components into a plurality of procurement steps, and a step deadline setting unit 12 sets a step completion deadline in each procurement step on the basis of the production start date determined by the production start date determination unit 11.

Description

Procurement support method and procurement support system

The present invention relates to a procurement support method and a procurement support system.

Procurement operations in the manufacturing industry are roughly divided into procurement processes such as ordering requests and orders, and the period (buffer) for performing work in the operations is determined in order from the one for which the procurement instruction for parts is issued in each process. Work between. However, in many cases, it is not possible to prioritize the procurement lead time (hereinafter abbreviated as "LT") and the work start date, so the manufacturing work that actually uses the parts is started. Parts may not be delivered on a daily basis (delayed) or may be delivered early (early).

Patent Document 1 discloses a design development / procurement instruction management system for the purpose of reducing development delays caused by material procurement delays from the design / development progress management stage. This design development / procurement instruction management system is based on the procurement lead time acquired from the parts list that stores the item composition of the product in the work progress information acquired from the work division configuration table that stores the progress status of the work group. Procurement instruction required date addition means to add procurement instruction required date to, and work division configuration recreating means to recreate the work division configuration table based on the work group progress information correction file created by the procurement instruction required date addition means. It has a procurement instruction management means for presenting a member requiring a procurement instruction based on the recreated work division configuration.

Japanese Unexamined Patent Publication No. 2005-346319

However, in the system disclosed in Patent Document 1, only the parts that exceed the procurement instruction required date are highlighted, so that the parts are required all at once on a specific day, and a large amount of work may be displayed at once. There is. Therefore, if it is applied to a manufacturing industry or the like that requires a large amount of parts procurement, there is a problem that the number of tasks to be processed becomes too large, and it is difficult to apply it. In addition, since procurement has at least a plurality of processes of ordering and ordering, delays in each process cannot be reduced unless a deadline is set for each process. In particular, in multiple procurement processes, each department that manages this process operates with its own (individual) index, so even if the individual index of each department is satisfied, the production start date, which is the overall index, may not be satisfied. ..

Furthermore, it is necessary to have all the necessary parts in the work phase at the start of work in the process (full kit), but it was found that the manufacturing work could not be started just before due to the delay of some parts, so it was urgently manufactured. There may be situations where the plan has to be changed, and the impact on the business tends to be large.

The present invention has been made in view of the above problems, and is a procurement support capable of managing parts to be delivered without delay or prematurely on the production start date, which is an overall index in a procurement business having a plurality of procurement processes. The purpose is to provide methods and procurement support systems.

In order to solve the above problems, the procurement support method executed by the procurement support system according to one viewpoint of the present invention is the production of at least one manufacturing process that manufactures the product based on the production plan of the product consisting of a plurality of parts. The start date is determined, the procurement work of each part is divided into a plurality of procurement processes, and the deadline for process completion in each procurement process is set based on the production start date.

According to the present invention, it is possible to realize a procurement support method and a procurement support system capable of displaying a large amount of parts procurement work separately for each procurement process without displaying them all at once.

It is a figure which shows the schematic structure of the procurement support system which concerns on Example. It is a functional block diagram which shows the schematic structure of the procurement support system which concerns on Example. It is a figure for demonstrating an example of the outline of the procurement support system which concerns on Example. It is a figure for demonstrating another example of the outline of the procurement support system which concerns on Example. It is a figure for demonstrating another example of the outline of the procurement support system which concerns on Example. It is a figure which shows an example of the bill of materials (BOM) data which concerns on Example. It is a figure which shows an example of the procurement LT data which concerns on Example. It is a figure which shows an example of the parts inventory data which concerns on Example. It is a figure which shows an example of order request data which concerns on Example. It is a figure which shows an example of ordering data which concerns on Example. It is a figure which shows an example of the work phase list data which concerns on Example. It is a figure which shows an example of the whole index list data which concerns on Example. It is a figure which shows an example of the parts use list data which concerns on Example. It is a figure which shows an example of ordering target list data which concerns on Example. It is a figure which shows an example of the order request target list data which concerns on Example. It is a figure which shows an example of the production planning data which concerns on Example. It is a flowchart which shows an example of each task priority determination process by the procurement support system which concerns on Example. It is a flowchart explaining an example of the delivery waiting task priority determination process by the procurement support system which concerns on Example. It is a flowchart explaining an example of the delivery waiting task priority determination process by the procurement support system which concerns on embodiment, and is the flowchart which shows the continuation process of FIG. 8A. It is a flowchart explaining an example of the follow-up task priority determination process by the procurement support system which concerns on Example. It is a flowchart explaining an example of the follow-up task priority determination process by the procurement support system which concerns on Example, and is the flowchart which shows the continuation process of FIG. 9A. It is a flowchart explaining an example of the state determination process of the follow-up by the procurement support system which concerns on Example. It is a flowchart explaining an example of ordering task priority determination processing by the procurement support system which concerns on Example. It is a flowchart explaining an example of order request task priority determination processing by the procurement support system which concerns on Example. It is a figure which shows the work sequence diagram of the follow-up by the procurement support system which concerns on Example. It is a figure which shows the business sequence diagram of the follow-up by the procurement support system which concerns on Example, and is the figure which shows the continuation sequence of FIG. 13A. It is a figure which shows the outline of the priority determination period in the procurement support system which concerns on Example. It is a figure which shows the outline of the judgment of the risk level in the procurement support system which concerns on Example. It is a figure which shows the outline of the determination of the delivery status in the procurement support system which concerns on Example.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. It should be noted that the embodiments described below do not limit the invention according to the claims, and that all the elements and combinations thereof described in the embodiments are indispensable for the means for solving the invention. Not exclusively.

The procurement support method and procurement support system of this embodiment have the following configuration as an example.

In the present embodiment, the procurement work is divided into a plurality of procurement processes, a date that is a different individual index is set for each process, and finally the overall index of whether the delivery is in time for the start of the manufacturing work is satisfied. The purpose was to support. Furthermore, based on the date of the individual index, the time required for each procurement process was deducted, and this period was considered as a buffer.

That is, in the procurement support system of this embodiment, individual indexes with priorities are set for each part in each procurement process, and by observing them, the manufacturing work start date, which is the overall index, is not delayed or premature. It is a system that supports the delivery of parts.

With the above configuration, the concept of S-DBR (Simplified Drum Buffer Rope) of TOC (Theory of Constraints) is applied, and not only the deadline is exceeded, but also the priority of work according to the consumption of the buffer is calculated and required. Highlighting is done so that the work can be done sequentially from the work, not too early and not too late.

As a result, a large amount of parts procurement work is not displayed all at once, but is displayed separately for the procurement process, and the highlighting differs depending on the priority, so that the person in charge of each procurement process concentrates on the necessary work. Can carry out procurement operations.

Further, the system disclosed in Patent Document 1 described above is a procurement instruction management system for design and development, but this embodiment is a procurement support system for the manufacturing industry, and is fully prepared for each work phase as an element necessary for the manufacturing industry. We also considered the concept that it should be a kit.

That is, in the procurement support system of this embodiment, the work phase (manufacturing process) of the product is taken into consideration, and the procurement process called follow-up is performed with the aim of arranging the parts with the full kit on the manufacturing work start date of the work phase. Present. By communicating with the supplier before delivery, we will increase the possibility of meeting the delivery deadline, and if a delay is likely to occur, we will provide a system to grasp it in advance and calculate the risk level. As a result, it is possible to support the minimization of the impact on the business by making express delivery or changing the production plan according to the risk level.

In the figure for explaining the embodiment, the same reference numerals are given to the parts having the same function, and the repeated description thereof will be omitted.

Further, in the following description, an expression such as "xxx data" may be used as an example of information, but the data structure of the information may be any. That is, the "xxx data" can be referred to as a "xxx table" to show that the information does not depend on the data structure. Further, "xxx data" may be simply referred to as "xxx". Then, in the following description, the configuration of each information is an example, and the information may be divided and held, or may be combined and held.

Hereinafter, an outline of terms in the present embodiment will be described.
-Procurement work: A series of work to procure parts and materials necessary for manufacturing-Procurement process: A unit that makes it easy to manage the procurement work in the procurement work. Order request, ordering, follow-up, waiting for delivery, etc.
-Manufacturing process: A unit that makes it easy to manage a series of manufacturing operations-Full kit: A state in which the necessary parts for the work phase are delivered without missing the required quantity.
・ Work phase: A unit that collectively represents the manufacturing process and work location of a certain product ・ Procurement LT: The time required for a certain part to be delivered to the specified location after requesting procurement from a supplier (purchase contract). Buffer: The period for performing work in a certain business. The length of the buffer varies depending on the business.
・ Follow-up: The name of the procurement process that confirms the status of the procured items with the supplier in the procurement operation. ・ Risk Level: An index that indicates the degree of influence of the delivery date contracted (contracted) with the supplier on the production plan for a certain part. Delivery Status: An index showing the delivery status of a part from the supplier, the presence or absence of delivery, and the degree of influence on the production plan when the part is not delivered. BOM: Bill of Materials. There are various BOMs such as design BOM, manufacturing BOM, service BOM, etc., and the type of BOM handled may differ depending on the company.
-Express delivery: Procurement items arrive from the supplier, and after acceptance inspection, they are immediately delivered to the work site without being placed in the warehouse.-Overall index: In this embodiment, the work start date (production start date) in each work phase. Since the parts are available in a full kit on the work start date, they are also set to prevent parts from arriving well earlier than the work start date.
-Individual index: In this embodiment, the schedule determined for each procurement process (order request, order, follow-up, waiting for delivery). Specific examples of individual indicators will be described later. It is set to complete the required tasks by each work deadline, and to prevent work from being performed sufficiently earlier than the work deadline.

First, with reference to FIGS. 1 and 2, the hardware configuration and functional block configuration of the procurement support system of the embodiment will be described, and the processing of the procurement support method executed by the procurement support system will be described in FIGS. 3 and later.

FIG. 1 is a diagram showing a schematic configuration of a procurement support system according to an embodiment.

The procurement support system S according to this embodiment has a procurement support device 1 and a core system 2, and these procurement support devices 1 and the core system 2 are communicably connected by a network 3.

The procurement support device 1 is a device capable of various information processing, for example, an information processing device such as a computer. The information processing device has an arithmetic element, a storage medium, and a communication interface, and further has an input device such as a mouse and a keyboard, and a display device such as a display.

The arithmetic element is, for example, a CPU (Central Processing Unit), an FPGA (Field-Programmable Gate Array), or the like. The storage medium includes, for example, a magnetic storage medium such as an HDD (Hard Disk Drive), a semiconductor storage medium such as a RAM (Random Access Memory), a ROM (Read Only Memory), and an SSD (Solid State Drive). Further, a combination of an optical disk such as a DVD (Digital Versatile Disk) and an optical disk drive is also used as a storage medium. In addition, a known storage medium such as a magnetic tape medium is also used as the storage medium.

Programs such as firmware are stored in the storage medium. At the start of operation of the procurement support device 1 (for example, when the power is turned on), a program such as firmware is read from this storage medium and executed to perform overall control of the procurement support device 1. In addition to the program, the storage medium stores data and the like required for each process of the procurement support device 1.

Similar to the procurement support device 1, the core system 2 is also a device capable of various information processing, for example, an information processing device such as a computer.

Note that the procurement support device 1 and the core system 2 of this embodiment may each be configured by a so-called cloud in which the information processing device is configured to be able to communicate via a communication network. Further, although it is shown as a single core system 2 in FIG. 1, there may be a plurality of core systems 2.

The network 3 enables mutual communication between the procurement support device 1 and the core system 2. As the network 3, various well-known networks can be adopted based on the location and environment in which the procurement support device 1 and the core system 2 are installed. As an example of the network 3, the procurement support device 1 and the core system 2 may be connected by a LAN (Local Area Network), or may be connected by a WAN (Wide Area Network) represented by the Internet or a mobile communication network. Good. Further, the network 3 may be either a wired / wireless network, or a wired / wireless network may be partially adopted.

FIG. 2 is a functional block diagram showing a schematic configuration of the procurement support system S according to the embodiment.

The procurement support device 1 has a control unit 10, a storage unit 14, a display unit 15, and a communication unit 16.

The control unit 10 controls the entire procurement support device 1. The control unit 10 has a production start date determination unit 11, a process deadline setting unit 12, and a priority calculation unit 13.

The production start date determination unit 11 determines the production start date of at least one manufacturing process for manufacturing the product, based on the production plan of the product composed of a plurality of parts. As described above, since the production start date is the overall index in this embodiment, it can be said that the production start date determination unit 11 determines the overall index.

More specifically, the production start date determination unit 11 determines the production start date for each part. In particular, the production start date determination unit 11 determines the production start date based on the parts list of parts for each manufacturing process and the procurement lead time of parts. Here, as already described, the procurement process has at least an order request process, an ordering process, and a delivery waiting process, and further has a follow-up process set prior to the delivery waiting process.

The process deadline setting unit 12 divides the procurement work of each part into a plurality of procurement processes, and sets the deadline for process completion in each procurement process based on the production start date, which is an overall index. In this embodiment, as will be described later, since it is the deadline for completing the process in each procurement process, it can be said that the process deadline setting unit 12 sets an individual index.

Further, the process deadline setting unit 12 sets the deadline for process completion of the follow-up process based on the delivery date set in the ordering process. The deadline for completing the follow-up process is also an individual index in this embodiment.

The priority calculation unit 13 calculates the priority of the procurement process related to the process completion deadline based on the process completion deadline and the current date, which are individual indicators. Here, the priority is an index indicating the context of the process completion deadline and the current date, and the magnitude of the period from the process completion deadline to the current date. The details of the priority will be described later.

Further, the priority calculation unit 13 calculates the priority of the manufacturing process related to the production start date based on the production start date and the current date, which are the overall indicators.

The storage unit 14 temporarily or permanently stores programs and data. A program such as firmware and data required for the operation of the procurement support device 1 are stored in the storage unit 14.

The display unit 15 visually displays the control progress and result of the control unit 10, data stored in the storage unit 14, and the like based on instructions from the control unit 10. Further, the display unit 15 displays the priority of the manufacturing process calculated by the priority calculation unit 13 for each part. Preferably, the display unit 15 displays the priorities of different manufacturing processes in different colors.

Based on the control of the control unit 10, the communication unit 16 transmits the data transmitted from the control unit 10 to the core system 2 via the network 3, and also receives the data transmitted from the core system 2 via the network 3. To do.

The core system 2 has a storage unit 20 and a communication unit 21.

The storage unit 20 stores various data necessary for the operation of the entire procurement support system S. Details of the data stored in the storage unit 20 will be described later. The communication unit 21 transmits data to the procurement support device 1 via the network 3 and receives the data transmitted from the procurement support device 1 in the same manner as the communication unit 16 of the procurement support device 1.

Next, the operation of the procurement support system S of this embodiment will be described with reference to FIGS. 3 to 5.

FIG. 3 is a diagram for explaining an example of an outline of the procurement support system according to the embodiment.

The procurement person P is also the operator of the procurement support device 1 that constitutes the procurement support system S. The procurement person P operates the input unit (not shown in FIGS. 1 and 2) of the procurement support device 1 and causes the display unit 15 to display the display screens D1 and D2 as shown in FIG.

On the display screen D1, the products manufactured / produced at the factory (factory A) in charge of the procurement person P are displayed in project units. In the example shown in FIG. 3, X, Y, and Z are products constituting the final product X. Therefore, XY indicates a project for producing the product Y constituting the final product X.

The priority of each project is displayed for each project. In relation to the illustration, the priority is displayed by hatching or the like in the present embodiment, but since the display unit 15 can actually display in color, different priorities are different as shown in the legend of FIG. It is displayed in color.

Procurement person P selects and specifies the project (business) he / she is in charge of from the projects displayed on the display screen D1 by the input unit. In the example shown in FIG. 3, it is assumed that the procurement person P selects the project XX. Upon selection of the project, the procurement support system S displays the display screen D2 for the project XX.

On the display screen D2, a table is displayed in which the manufacturing processes Work1 to Work5 constituting the project XX are arranged in columns and the work place Assembury1 ... Are arranged in rows. Then, in the cells constituting this table, the priority for the work phase specified by the manufacturing process and the work place is displayed.

The procurement person P looks at the display screen D2 and confirms whether the ordered procured items (parts) will be a full kit at the required timing for each work phase in the selected project. This is because if even one part is not prepared (missing) at the required timing in the work phase, work delay or work rework will occur, so the procured items are prepared for each work phase of each product (project). Because it needs to be.

Therefore, the procurement person P confirms the priority for each work phase in each project. Then, the procurement work is managed so that the priority of the work phase preferably stays at High Priority (so that it does not become Past Due Date).

FIG. 4 is a diagram for explaining another example of the outline of the procurement support system according to the embodiment. In addition, in FIG. 4 and FIG. 5, the current date will be described as June 1.

The procurement person P selects a specific work phase (in the example shown in FIG. 4, the manufacturing process is Work4 and the work place is Assembury1) by the input unit on the display screen D2 shown in FIG. By selecting the work phase, the procurement support system S causes the display unit 15 to display the display screen D3 as shown in FIG.

On the display screen D3, the delivery date, follow-up status, new delivery date, production start date, and Risk Level are displayed for each part (procured item) that constitutes the selected work phase. In addition, the priority of each part is also displayed. Details of follow-up and Risk Level will be described later.

Procurement person P first looks at the display screen D2 in FIG. 3 and identifies the work phase that should be prioritized. In the illustrated example, the priority of the work phase in which the manufacturing process is Work4 and the work place is Assembury1 is Past Due Date (see FIG. 3). Therefore, it is determined that this work phase should be prioritized and selected by the input unit. The details are displayed on the display screen D3.

The procurement person P looks at the display screen D3 and confirms the priority of the parts that are not complete (not yet delivered). In the example shown in FIG. 4, the procurement product Part 1 has not yet been delivered even after the production start date, and since the supplier has already been requested to change the delivery date, the procurement person P does not take any action at this time. The procured product Part 2 has a high priority, and the new delivery date exceeds the production start date. In this way, if the delivery date of the procured item is delayed, the influence of the work plan in the work phase is confirmed as Risk Level, and if the influence is large (for example, Risk Level is Critical), the supplier SP and delivery (mainly delivery date). Can negotiate (about the day) (follow-up).

Therefore, the procurement person P can follow the supplier SP to see if the delivery is performed as scheduled for the high-priority procurement work by checking the display screen D3. Then, the procurement department including the procurement person P can grasp whether the delivery is possible or delayed from the supplier SP as scheduled before the delivery schedule.

From the above, the procurement person P can grasp whether each part can be delivered as scheduled before the delivery date by checking the display screen D3, and thereby the parts are scheduled for each work phase. It is possible to check for each part whether or not they are aligned.

FIG. 5 is a diagram for explaining another example of the outline of the procurement support system according to the embodiment.

It is assumed that the supplier has requested and negotiated a change in the delivery date, and as a result, there are parts whose delivery date has been changed (procured items Part2 and Part3 on the display screen D4 in FIG. 5). The procurement person P confirms the Risk Level after the delivery date is changed, and confirms whether or not the work plan of the work phase is affected.

Regarding the procured product Part3, since the new delivery date is before the production start date, it can be judged that the work plan will not be affected. Therefore, the procurement manager P notifies the material manager M that the delivery of the procured product Part 3 is delayed, and in some cases, the procured product Part 3 is delivered to the workplace as soon as it arrives.

On the other hand, regarding the procured product Part2, although we are following up with the suppliers, it can be judged that the work plan will be affected because the new delivery date is after the production start date. Therefore, the person in charge of procurement P tells the person in charge of production planning that it is necessary to change the work in the corresponding work phase, the work start date, and the person in charge of production planning delivers the procured product Part 2 to the work place as soon as it is delivered to the material manager M. Notify PP and field manager FM.

From the above, the procurement person P can grasp that the delivery delay occurs for each part before the delivery date by checking the display screen D4, and notifies the persons concerned according to the influence on the work plan for each work phase. can do.

Next, the details of the data stored in the storage unit 20 of the core system 2 of the procurement support system S will be described with reference to FIGS. 6A to 6K.

FIG. 6A is a diagram showing an example of the bill of materials (BOM) data 100 according to the embodiment.

The bill of materials data 100 has a factory ID 101, a BOM ID 102, a work phase 103, a parts ID 104, and a required quantity 105.

Factory ID 101 is the ID of the factory where the parts are used. BOM ID 102 is an ID for each bill of materials. The work phase 103 is the ID of the work phase 103 in which the component is used. The part ID 104 is the ID of the part. The required quantity 105 is the required quantity of the parts specified by the part ID 104 in the work phase specified by the work phase 103.

Next, FIG. 6B is a diagram showing an example of the procurement LT data 110 according to the embodiment.

The procurement LT data 110 has a factory ID 111, a BOM ID 112, a part ID 113, a supplier ID 114, and a procurement LT 115. In the following description, the description of the items already described will be omitted.

Supplier ID 114 is the supplier's ID. The procurement LT 115 is the number of days of the procurement LT of the parts specified by the part ID 113 and the supplier ID 114.

Next, FIG. 6C is a diagram showing an example of the parts inventory data 120 according to the embodiment.

The parts inventory data 120 has a factory ID 121, a project ID 122, a BOM ID 123, a parts ID 124, and an inventory quantity 125.

Project ID 122 is the project ID. The inventory quantity 125 is a numerical value indicating the inventory quantity of parts for each project, which is specified by the BOM ID123 and the part ID124.

Next, FIG. 6D is a diagram showing an example of the order request data 130 according to the embodiment.

The order request data 130 has a factory ID 131, a project ID 132, an order request ID 133, a part ID 134, a supplier ID 135, an order request quantity 136, a delivery request date 137, and an order request completion flag 138.

The order request ID 133 is the ID of the order request made by the order requester. The order request quantity 136 is a value indicating the quantity of the parts for which the order request is made in the order request specified by the order request ID 133. The delivery request date 137 is a date indicating the delivery request date instructed to the supplier specified by the supplier ID 135 in the order request specified by the order request ID 133. The order request completion flag 138 is a flag indicating whether or not the order requester has completed the work of the order request specified by the order request ID 133, and if it is a true value (TRUE), it indicates the completion of the order request.

Next, FIG. 6E is a diagram showing an example of order data 140 according to the embodiment.

The order data 140 has a factory ID 141, a project ID 142, an order ID 143, a part ID 144, a supplier ID 145, a delivery date 146, an order quantity 147, a delivered quantity 148, and an order completion flag 149.

Ordering ID 143 is an ordering ID placed by the ordering party. The delivery date 146 is a date indicating the delivery date indicated to the supplier in the order specified by the order ID 143. The order quantity 147 is a value indicating the quantity of parts to be ordered from the supplier in the order specified by the order ID 143. The delivered quantity 148 is a value indicating the quantity of the delivered parts among the parts related to the order specified by the order ID 143 on the current date. The order completion flag 149 is a flag indicating whether or not the orderer has completed the ordering work specified by the order ID 143, and if it is a true value (TRUE), it indicates the order completion.

Next, FIG. 6F is a diagram showing an example of work phase list data 150 according to the embodiment.

The work phase list data 150 has a factory ID 151, a project ID 152, a BOM ID 153, an organization 154, and a work phase 155.

Knitting 154 is a numerical value for specifying each product when manufacturing a plurality of the same products. The work phase 155 is an ID indicating the work phase.

Next, FIG. 6G is a diagram showing an example of the overall index list data 160 according to the embodiment.

The overall index list data 160 has a factory ID 161, a project ID 162, a BOM ID 163, an organization 164, a work phase 165, a work phase production start date 166, a part ID 167, a required quantity 168, and a procurement LT169.

The work phase production start date 166 is a date indicating the production start date of the work phase specified by the work phase 165.

Next, FIG. 6H is a diagram showing an example of the component availability list data 170 according to the embodiment.

The parts available list data 170 has a factory ID 171, a project ID 172, a BOM ID 173, a parts ID 174, an inventory quantity 175, an order ID 176, a delivery date 177, an order quantity 178, a delivered quantity 179, and an available quantity 180.

The available quantity 180 is the sum of the inventory quantity 175 and the delivered quantity 179.

Next, FIG. 6I is a diagram showing an example of the order target list data 190 according to the embodiment.

The order target list data 190 includes factory ID 191 and project ID 192, BOM ID 193, organization 194, work phase 195, work phase production start date 196, order request ID 197, order ID 198, part ID 199, supplier ID 200, procurement LT201, and order request quantity 202. , Delivery request date 203, delivery date 204, order quantity 205, delivered quantity 206, and order completion flag 207.

Next, FIG. 6J is a diagram showing an example of the order request target list data 210 according to the embodiment.

The order request target list data 210 includes factory ID 211, project ID 212, BOM ID 213, organization 214, work phase 215, work phase production start date 216, part ID 217, procurement LT218, inventory quantity 219, required quantity 220, order required quantity 221 and. It has an order request completion flag 222.

The required order quantity 221 is a numerical value obtained by subtracting the inventory quantity 219 from the required quantity 220.

Then, FIG. 6K is a diagram showing an example of the production planning data 220 according to the embodiment.

The production plan data 220 has a factory ID 221 and a project ID 222, a BOM ID 223, an organization 224, a work phase 225, and a work phase production start date 226.

Next, the operation of the procurement support system S of this embodiment will be described with reference to FIGS. 7 to 13B.

FIG. 7 is a flowchart showing an example of each task priority determination process by the procurement support system S according to the embodiment. The flow of the entire procurement support method by the procurement support system S of this embodiment will be described with reference to the flowchart of FIG. 7.

First, the procurement support device 1 obtains the production start date of the work phase as an overall index mainly based on the production plan data 220, the bill of materials data 100, and the procurement LT data 110 by the production start date determination unit 11 (step S300). ).

Next, the procurement support device 1 mainly uses the process deadline setting unit 12 to obtain the delivery waiting deadline date as an individual index based on the production start date of the work phase, which is an overall index. Next, the procurement support device 1 mainly calculates the priority of each task by the priority calculation unit 13 based on the delivery waiting deadline date obtained by the process deadline setting unit 12 (step S301).

Further, the procurement support device 1 mainly uses the process deadline setting unit 12 to obtain the follow-up deadline date as an individual index based on the production start date of the work phase, which is an overall index. Next, the procurement support device 1 mainly calculates the priority of each task by the priority calculation unit 13 based on the follow-up deadline date obtained by the process deadline setting unit 12 (step S302).

Further, the procurement support device 1 mainly uses the process deadline setting unit 12 to obtain the order deadline date as an individual index based on the production start date of the work phase, which is an overall index. Next, the procurement support device 1 mainly calculates the priority of each task by the priority calculation unit 13 based on the order deadline date obtained by the process deadline setting unit 12 (step S303).

Then, the procurement support device 1 mainly uses the process deadline setting unit 12 to obtain the order request deadline date as an individual index based on the production start date of the work phase, which is an overall index. Next, the procurement support device 1 mainly calculates the priority of each task by the priority calculation unit 13 based on the order request deadline date obtained by the process deadline setting unit 12 (step S304).

Next, FIGS. 8A and 8B are flowcharts for explaining an example of the delivery waiting task priority determination process by the procurement support system according to the embodiment, and are flowcharts corresponding to steps S300 and S301 of FIG.

First, the procurement support device 1 mainly creates work phase list data 150 based on the production plan data 220 and the bill of materials data 100 by the production start date determination unit 11 (step S400). Next, the procurement support device 1 mainly has the production start date determination unit 11, and the overall index list data 160 having the production start date of the work phase for each part based on the production plan, the parts list data 100, and the procurement LT data 110. Is created (step S401).

Next, the procurement support device 1 mainly acquires the parts inventory data 120 and the order request data 130 by the production start date determination unit 11, and the parts availability list based on the inventory quantity, the delivered quantity, and the order quantity of each part. Data 170 is created (step S402).

Next, the procurement support device 1 repeatedly assigns the work phase of the parts described below and determines the priority for 160 minutes of the overall index list data (step S403).

That is, the procurement support device 1 mainly allocates the available quantity 180 of the same parts of the parts available list data 170 to the required quantity 168 of the parts of the overall index list data 160 by the process deadline setting unit 12 (step). S404).

Next, the procurement support device 1 mainly determines the magnitude relationship between the required quantity 168 of the parts of the overall index list data 160 and the available quantity 180 of the parts available list data 170 by the process deadline setting unit 12 (step S405). ). Then, when it is determined that the required quantity of parts of the overall index list data 160 is 168 or more than the available quantity of 180 of the parts available list data 170, the flow proceeds to step S406, and the required quantity of parts of the overall index list data 160 is determined. If it is determined that 168 is less than the available quantity 180 of the component available list data 170, the flow proceeds to step S407.

In step S406, the procurement support device 1 mainly substitutes the values as shown in the figure for the required quantity 168 of the parts of the overall index list data 160 and the available quantity 180 of the parts available list data 170 by the process deadline setting unit 12. To do. Then, the satisfaction flag is set to True.

On the other hand, in step S407, the procurement support device 1 mainly uses the process deadline setting unit 12 to set the required quantity 168 of the parts of the overall index list data 160 and the available quantity 180 of the parts available list data 170 as shown in the figure. Substitute. Then, the satisfaction flag is set to False.

Next, the procurement support device 1 mainly uses the priority calculation unit 13 to calculate the delivery waiting start date, the delivery waiting deadline date, the red determination date, and the yellow determination date of each part (step S408). Further, the procurement support device 1 mainly obtains the Delivery Status of each component by the priority calculation unit 13 (step S409).

In step S410, the repetition from step S403 is completed.

Next, the procurement support device 1 mainly uses the priority calculation unit 13 to repeatedly determine the priority for each work phase for the organization within the work phase and the work phase (step S411).

That is, the procurement support device 1 mainly determines the presence / absence of the corresponding work phase component in the overall index list data 160 for which the priority has been calculated by the priority calculation unit 13 (step S412). Then, if it is determined that there is no corresponding work phase component in the overall index list data 160, the flow shifts to step S417, and if it is determined that there is a corresponding work phase component in the overall index list data 160, the flow changes. The process proceeds to step S413.

Next, the procurement support device 1 mainly determines whether or not the satisfaction flag is True for all the parts by the priority calculation unit 13 (step S413). Then, when it is determined that the sufficiency flag is True for all the parts, the flow proceeds to step S418, and when it is determined that the sufficiency flag is False for at least one component, the flow shifts to step S414.

Next, the procurement support device 1 determines the presence or absence of expired parts mainly by the priority calculation unit 13 (step S414). Then, if it is determined that there are expired parts, the flow proceeds to step S419, and if it is determined that there are no expired parts, the flow proceeds to step S415.

Further, the procurement support device 1 mainly determines the presence / absence of a part having a red priority by the priority calculation unit 13 (step S415). Then, if it is determined that there is a component having a red priority, the flow shifts to step S420, and if it is determined that there is no component having a red priority, the flow shifts to step S416.

Then, the procurement support device 1 mainly determines the presence / absence of a part having a yellow priority by the priority calculation unit 13 (step S416). Then, if it is determined that there is a component having a yellow priority, the flow shifts to step S421, and if it is determined that there is no component having a yellow priority, the flow shifts to step S422.

In step S417, the priority of the corresponding work phase is set to none (white). In step S418, the priority of the corresponding work phase is set to complete (light blue). In step S419, the priority of the corresponding work phase is set to expired (black). In step S420, the priority of the corresponding work phase is set to red. In step S421, the priority of the corresponding work phase is set to yellow. Then, in step S422, the priority of the corresponding work phase is set to green.

In step S423, the repetition from step S411 is completed.

Next, FIGS. 9A and 9B are flowcharts for explaining an example of the follow-up task priority determination process by the procurement support system according to the embodiment, and are flowcharts corresponding to step S302 in FIG.

Since steps S500 to S507 in FIG. 9A are the same processes as steps S400 to S407 in FIG. 8A, description thereof will be omitted.

Next, the procurement support device 1 mainly calculates the follow-up start date, follow-up deadline date, red determination date, and yellow determination date of each part by the priority calculation unit 13 (step S508). Further, the procurement support device 1 obtains the Risk Level of each component mainly by the priority calculation unit 13 (step S509).

Since steps S510 to S523 of FIGS. 9A and 9B are the same processes as steps S410 to S423 of FIGS. 8A and 8B, the description thereof will be omitted.

Next, FIG. 10 is a flowchart illustrating an example of the follow-up state determination process by the procurement support system according to the embodiment, and is a flowchart corresponding to step S302 of FIG. 7.

First, the procurement support device 1 acquires parts ordering information mainly by the priority calculation unit 13 based on the information input by the procurement person P or the like via the input unit (step S600).

Next, the procurement support device 1 confirms and determines the state of the follow-up status input to the procurement support system S by the supplier mainly by the priority calculation unit 13 (step S601). Here, it is assumed that the "follow-up status" is one of "confirmation without change of delivery date, no follow-up required, confirmation with change of delivery date, confirmation with request for change of delivery date, confirmation without request for change of delivery date". Then, if it is determined that the follow-up status is confirmed without changing the delivery date or follow-up is unnecessary, the flow shifts to step S602, and if it is determined that the follow-up status is confirmed with changing delivery date, the flow shifts to step S603 and follows. If it is determined that the up status is confirming that there is a delivery date change request, the flow proceeds to step S604, and if it is determined that the follow-up status is confirming that there is no delivery date change, the flow proceeds to step S605.

In step S602, the follow-up completion flag is set to True. After that, the flow shifts to step S608. In step S603, the follow-up completion flag is set to True, and the new delivery date is acquired. After that, the flow shifts to step S606. In step S603, the follow-up completion flag is set to False, and the new delivery date is acquired. After that, the flow shifts to step S606. In step S606, the follow-up completion flag is set to False. After that, the flow shifts to step S608.

Next, the procurement support device 1 mainly updates the Risk Level of each part by the priority calculation unit 13 (step S606), updates the changed delivery date and the Risk Level of the parts order information (step S607), and updates the risk level of the parts. The completion flag in the order information is updated (step S608).

Next, FIG. 11 is a flowchart illustrating an example of the ordering task priority determination process by the procurement support system according to the embodiment, and is a flowchart corresponding to step S303 of FIG. 7.

Since step S700 in FIG. 11 is the same process as step S400 in FIG. 8A, the description thereof will be omitted.

Next, the procurement support device 1 mainly uses the priority calculation unit 13 to collate the order request data 130, the order data 140, and the overall index list data 160 to create the order target list data 190 for the parts that need to be ordered. (Step S701).

Next, the procurement support device 1 mainly uses the priority calculation unit 13 to repeatedly determine the priority of the task for 190 minutes of the order target list data (step S702).

First, the procurement support device 1 mainly uses the priority calculation unit 13 to obtain the order deadline date, the red determination date, and the yellow determination date of each part (step S703).

Next, the procurement support device 1 mainly determines the state of the order completion flag 207 of the order target list data 190 by the priority calculation unit 13 (step S704). Then, if it is determined that the order completion flag 207 is True, the flow proceeds to step S708, and if it is determined that the order completion flag 207 is False or Null (undecided), the flow proceeds to step S705.

Next, the procurement support device 1 mainly determines whether or not the order deadline date obtained in step S703 is today by the priority calculation unit 13 (step S705). Then, if it is determined that the order deadline date is today, the flow shifts to step S709, and if it is determined that the order deadline date is not today, the flow shifts to step S706.

Next, the procurement support device 1 mainly determines whether or not the red determination date obtained in step S703 is today by the priority calculation unit 13 (step S706). Then, if it is determined that the red determination date is today, the flow proceeds to step S710, and if it is determined that the red determination date is not today, the flow proceeds to step S706.

Next, the procurement support device 1 mainly determines whether or not the yellow determination date obtained in step S703 is today by the priority calculation unit 13 (step S706). Then, if it is determined that the yellow determination date is today, the flow proceeds to step S711, and if it is determined that the yellow determination date is not today, the flow proceeds to step S712.

In step S708, it is determined that the color code is light blue, in step S709 it is determined that the color code is black, in step S710 it is determined that the color code is red, and in step S711 it is determined that the color code is yellow. Then, in step S712, it is determined that the color code is green.

In step S713, the repetition from step S702 is completed.

Then, FIG. 12 is a flowchart illustrating an example of the order request task priority determination process by the procurement support system according to the embodiment, and is a flowchart corresponding to step S304 of FIG. 7.

Since step S800 in FIG. 12 is the same process as step S400 in FIG. 8A, the description thereof will be omitted.

Next, the procurement support device 1 mainly acquires the parts inventory data 120 and the order request data 130 by the priority calculation unit 13, collates these with the overall index list data 160, and orders the parts for which the order request is required. Request target list data 210 is created (step S801).

Next, the procurement support device 1 mainly uses the priority calculation unit 13 to repeatedly determine the priority of the task for 210 minutes of the order request target list data (step S802).

First, the procurement support device 1 mainly uses the priority calculation unit 13 to obtain an order request deadline date, a red determination date, and a yellow determination date for each part (step S803).

Next, the procurement support device 1 mainly determines the state of the order request completion flag 222 of the order request target list data 210 by the priority calculation unit 13 (step S804). Then, if it is determined that the order request completion flag 222 is True, the flow proceeds to step S808, and if it is determined that the order request completion flag 222 is False or Null (undecided), the flow proceeds to step S805.

Next, the procurement support device 1 mainly determines whether or not the order request deadline date obtained in step S803 is today by the priority calculation unit 13 (step S805). Then, if it is determined that the order request deadline date is today, the flow shifts to step S809, and if it is determined that the order request deadline date is not today, the flow shifts to step S806.

From this point onward, steps S806 to S813 in FIG. 12 are the same processes as steps S706 to S713 in FIG. 11, and thus description thereof will be omitted.

13A and 13B are diagrams showing a follow-up work sequence diagram by the procurement support system according to the embodiment. The follow-up sequence shown in FIGS. 13A and 13B includes contents that overlap with the contents already described, but is intended to show a sequence that includes not only the procurement support system S but also operations such as operators of the procurement support system S. I will explain here.

First, the procurement support device 1 performs follow-up priority determination processing (step S900). The follow-up priority determination process performed by the procurement support device 1 has already been described with reference to FIGS. 9A and 9B, and thus the description thereof will be omitted here.

Next, the procurement person P instructs the procurement support device 1 to confirm the priority of the follow-up task (step S902), and the procurement support device 1 displays the follow-up in units of work phases accordingly (step S902). Step S903). The procurement person P visually recognizes the display unit 15 of the procurement support device 1 and selects a work phase to be preferentially processed via the input unit (step S904).

Next, the procurement person P instructs the procurement support device 1 to confirm the follow-up priority of the parts unit (step S905), and the procurement support device 1 displays the follow-up priority of the parts unit accordingly. (Step S906).

Next, the procurement person P selects a task to be processed via the input unit while looking at the display unit 15 of the procurement support device 1 (step S907). After that, the procurement person P confirms with the supplier whether or not the delivery date has been changed (step S908), and the supplier replies whether or not the delivery date has been changed (step S909).

Based on the response result from the supplier, the procurement person P registers the follow-up status in the core system 2 (step S910). The procurement support device 1 appropriately accesses the core system 2, refers to the follow-up status (step S911), and captures the follow-up status information (step S912).

Then, the procurement support device 1 performs a follow-up state determination process (step S913). Since the follow-up state determination process performed by the procurement support device 1 has already been described with reference to FIG. 10, the description here will be omitted.

Here, if the Risk Level of the follow-up task is Critical, the procurement manager P requests the production control department to reschedule the production plan (step S914), and the production control department notifies the new production plan accordingly. Then (step S915), the new production plan is registered in the core system 2.

On the other hand, if the Risk Level of the follow-up task is High, the procurement manager P informs the material management department that the parts need to be shipped immediately after they are received (step S916).

FIG. 14 is a diagram showing an outline of a priority determination period in the procurement support system S according to the embodiment. Each procurement process of order request, ordering, follow-up, and waiting for delivery has a priority determination period as shown in the figure. It should be noted that the detailed period and the time at which the priority is changed are design matters, and the example shown in FIG. 14 is merely an example.

FIG. 15 is a diagram showing an outline of the determination of the risk level (Risk Level) in the procurement support system S according to the embodiment, and FIG. 16 is an outline of the determination of the delivery status (Delivery Status) in the procurement support system S according to the embodiment. It is a figure which shows. It should be noted that the detailed period and the time at which the priority is changed are design matters, and the examples shown in FIGS. 15 and 16 are merely examples.

According to the present embodiment configured as described above, the production start date determination unit 11 determines the production start date of at least one manufacturing process in which the product is manufactured, based on the production plan of the product composed of a plurality of parts. Procurement support that divides the procurement work of each part into a plurality of procurement processes, and the process deadline setting unit 12 sets the deadline for process completion in each procurement process based on the production start date determined by the production start date determination unit 11. Realize the method.

Therefore, according to this embodiment, it is possible to manage the delivery of parts without delay or prematurely on the production start date, which is an overall index, in the procurement business having a plurality of procurement processes.

It should be noted that the above-described embodiment describes the configuration in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the described configurations. In addition, a part of the configuration of each embodiment can be added, deleted, or replaced with another configuration.

As an example, on the display screens D3 and D4 shown in FIGS. 4 and 5 in the above-described embodiment, it is possible to perform (filtering) display in which the display contents are narrowed down for each priority (color coding). It is also possible to perform a filtering display (for example, a filter at a supplier) according to a classification suitable for the procurement process.

Further, in the above-described embodiment, the data shown in FIGS. 6A to 6K are stored in the storage unit 20 of the core system 2, but each of these data is the procurement support device 1 and the core system constituting the procurement support system S. It may be stored in any of the storage units 14 and 20 of 2.

Further, each of the above configurations, functions, processing units, processing means, etc. may be realized by hardware by designing a part or all of them by, for example, an integrated circuit. The present invention can also be realized by a program code of software that realizes the functions of the examples. In this case, a storage medium in which the program code is recorded is provided to the computer, and the processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the program code itself and the storage medium storing the program code itself constitute the present invention. Examples of the storage medium for supplying such a program code include a flexible disk, a CD-ROM, a DVD-ROM, a hard disk, an SSD (Solid State Drive), an optical disk, a magneto-optical disk, a CD-R, and a magnetic tape. Non-volatile memory cards, ROMs, etc. are used.

Further, the program code that realizes the functions described in this embodiment can be implemented in a wide range of programs or script languages such as assembler, C / C ++, perl, Shell, PHP, and Java (registered trademark).

Further, by distributing the program code of the software that realizes the functions of the examples via the network, it is stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or a CD-R. , The processor provided in the computer may read and execute the program code stored in the storage means or the storage medium.

In the above-described embodiment, the control lines and information lines indicate those that are considered necessary for explanation, and do not necessarily indicate all the control lines and information lines in the product. All configurations may be interconnected.

S ... Procurement support system 1 ... Procurement support device 2 ... Core system 3 ... Network 10 ... Control unit 11 ... Production start date determination unit 12 ... Process deadline setting unit 13 ... Priority calculation unit 14 ... Storage unit 15 ... Display unit 16 ... Communication unit 20 ... Storage unit 21 ... Communication unit

Claims (14)

1. It is a procurement support method executed by the procurement support system.
   Based on the production plan of the product consisting of a plurality of parts, the production start date of at least one manufacturing process for manufacturing the product is determined.
   A procurement support method characterized in that the procurement operation of each of the parts is divided into a plurality of procurement processes, and the deadline for process completion in each of the procurement processes is set based on the production start date.
2. A production start date determination unit that determines a production start date of at least one manufacturing process that manufactures the product based on a production plan of a product composed of a plurality of parts.
   Procurement support characterized by having a process deadline setting unit that divides the procurement work of each of the parts into a plurality of procurement processes and sets a deadline for process completion in each of the procurement processes based on the production start date. system.
3. The procurement support system according to claim 2, wherein the production start date determination unit determines a production start date for each of the parts.
4. The procurement support according to claim 2, wherein the production start date determination unit determines the production start date based on the parts list of the parts for each manufacturing process and the procurement lead time of the parts. system.
5. The procurement support system according to claim 2, wherein the procurement process includes at least an order request process, an ordering process, and a delivery waiting process.
6. The procurement support system according to claim 2, further comprising a priority calculation unit that calculates the priority of the procurement process related to the process completion deadline based on the process completion deadline and the current date. ..
7. The procurement support system according to claim 6, wherein the priority calculation unit calculates the priority of the manufacturing process related to the production start date based on the production start date and the current date.
8. The procurement according to claim 6, wherein the priority is an index indicating the context of the process completion deadline and the current date, and the magnitude of the period from the process completion deadline to the current date. Support system.
9. The procurement support system according to claim 5, wherein the procurement process includes a follow-up process that is set prior to the delivery waiting process.
10. The procurement support system according to claim 9, wherein the process deadline setting unit sets a deadline for process completion of the follow-up process based on a delivery date set in the ordering process.
11. The procurement support system according to claim 7, further comprising a display unit that displays the priority of the manufacturing process for each of the parts.
12. The procurement support system according to claim 11, wherein the display unit displays different priorities of the manufacturing processes in different colors.
13. The procurement support system according to claim 11, wherein the display unit displays the parts having a specific priority of the manufacturing process.
14. The procurement support system according to claim 11, wherein the display unit displays the parts related to the specific procurement process.
    

Images