Planning coordination device and planning coordination method
By designing planning collaboration devices in the manufacturing industry, using database management to manage ordering and order acceptance relationships among operators, calculate reliability and automatically adjust production plans, the problem of difficult to respond quickly to production planning collaboration in multiple management organizations is achieved, and even Reliable production plans can also be formulated without coordination to ensure the rapid response and stability of production plans.
Patent Information
- Application Number
- CN202110392085.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-05-25
- Filing Date
- 2021-04-13
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2041-04-13
Smart Images

Figure CN113723736B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a planning coordination device and a planning coordination method for rapidly executing the drafting and modification of production plans involving a plurality of operators. Background Art
[0002] In the manufacturing industry, the manufacturing process of a product often involves multiple management organizations. If the plan of one management organization is changed, its impact will affect the plans of other organizations.
[0003] For example, when a sales company requests an increase in the number of product deliveries due to an increase in demand, the assembler must not only adjust its own assembly schedule, but also make adjustments with the parts manufacturers of the parts delivered from other companies before responding to the delivery. The parts manufacturer will then respond whether the plan change is possible based on the adjustments with other parts manufacturers that deliver sub-parts to the company, so the adjustments take time and it is difficult to give a quick response on the delivery date.
[0004] In order to solve the above-mentioned problem, Patent Document 1 states that "a plan coordination system is proposed, which can effectively and quickly perform integration processing between plans while appropriately maintaining the confidentiality of information about plans between organizations that manage mutually coordinated plans separately. Its structure includes a computing device that performs: generating public data based on definition data of each plan, accepting user definition of information for coordination between plans in the process sequence represented by the public data, applying the user definition to the definition data of the corresponding plan to create a plan coordination model; in the event of a change event regarding the definition data, notifying the corresponding data to the management device of other plans that are coordination destinations in the corresponding coordination relationship, changing the plan coordination model based on the production results of other plans that reflect the change event, notifying the management device of other plans that have a coordination relationship with the corresponding plan that has been changed by the change of the corresponding data; and outputting the production results of each plan when all plans become plan completion."
[0005] Patent Document 1: International Publication No. 2015 / 068231
[0006] Patent Document 1 described above describes a model of a plan of a business operator directly related to a plan, but does not consider the coordination of a plurality of business operators or the coordination between unrelated business operators.
[0007] In addition, the premise is that real-time data can be obtained during planning collaboration. If the data quality or the frequency / cycle of data acquisition does not meet expectations, it may deviate from the current situation.
[0008] Furthermore, there is no description of the processing to be performed when an event that cannot be coordinated (there is no solution that satisfies the plan) occurs. Summary of the invention
[0009] Therefore, the present invention provides a means of plan coordination: when a certain operator makes a request for a production plan change, it is quickly determined whether a supplier with a good performance in ordering and receiving orders from the operator can cope with the plan change. In addition, for a supplier with a good performance in ordering and receiving orders from the operator that does not have a product ordering and receiving order relationship with the operator, the reliability of the performance in ordering and receiving orders with other operators is used as a judgment indicator to determine a replacement operator.
[0010] In a preferred example of the planning coordination device of the present invention, it is composed of the following parts: the first database, which registers each operator of the management object as a node with operator type and product information, and stores value chain data, which connects the above nodes through edges that are assigned index values of the reliability of the ordering and ordering relationship according to the performance of the ordering and ordering relationship between the operators; the second database, which stores the parts and quantities of the product reported by the above-mentioned operators before the production plan of the new product as product data in the form of a bill of materials, i.e., BOM; the third database, which stores scheduling data, which discloses the operator's report at the time of drafting the plan for the production and delivery of the product. The product delivery plan and automatically adjustable amount between operators, the automatically adjustable amount indicating how much the operator can increase the production volume in addition to the scheduled production volume of the product; a value chain management unit that produces value chain data, and recalculates the reliability of the ordering and ordering relationship between operators whenever the performance of the ordering and ordering relationship of products is newly collected between operators, and updates it by assigning it to the corresponding edge; and a scheduling formulation unit that accepts a plan change request from an operator of the management object, refers to the automatically adjustable amount of the corresponding product data, value chain data, and scheduling data from each database, determines whether it can cope with the plan change of the relevant operator, determines a replacement operator, and notifies the corresponding operator of the plan change to change the scheduling data of the third database.
[0011] In addition, as another feature of the present invention, in the above-mentioned planning coordination device, the above-mentioned value chain management unit will register each operator as a management object together with its final product ID in the node information table of the first database; the above-mentioned value chain management unit is started at a performance information collection cycle, and when the performance of the ordering and ordering relationship of a new product is collected between operators, a new edge connecting the nodes of the two operators is defined in the edge information table of the first database, and when the performance of the ordering and ordering relationship between existing operators is newly collected, the reliability of the ordering and ordering relationship between operators is recalculated based on the performance data, and assigned to the corresponding edge for update.
[0012] Effects of the Invention
[0013] The planning coordination device of the present invention has the effect of being able to formulate a plan with less calculation and high reliability even when a plan cannot be reached between related business operators with good performance. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1 This is a diagram showing a configuration example of a system in which a planning coordination device according to an embodiment of the present invention is connected to a planning preparation device of each business operator who is a target of planning coordination.
[0015] Figure 2 It is a functional structure diagram of the planning coordination device.
[0016] Figure 3 It is a functional block diagram of the planning coordination device.
[0017] Figure 4 This is a diagram showing an example of the hardware configuration of the planning coordination device.
[0018] Figure 5A This is a diagram showing an example of a node information table stored in the value chain data DB.
[0019] Figure 5B This is a diagram showing an example of a side information table stored in the value chain data DB.
[0020] Figure 6 This is a diagram showing an example of a performance data table stored in the performance data DB.
[0021] Fig. 7A This is a table showing the schedule data stored in the schedule data DB.
[0022] Figure 7B This is a diagram showing an example of an automatically adjustable data table stored in the schedule data DB.
[0023] Figure 8 It is an action flow chart of the value chain management unit of the planning coordination device.
[0024] Fig. 9 This is an operation flow chart of the schedule creation unit of the planning coordination part of the planning coordination device.
[0025] Fig. 10A This is an example of a screen showing a user inputting a plan change request to the plan coordination device.
[0026] Fig. 10B This is a diagram showing an example of a screen in which the plan coordination device reports to a user the results of adjustment of plan coordination.
[0027] Description of symbols
[0028] 10 Planning Collaboration Device
[0029] 20 User-facing display device
[0030] 30 Display device for managers
[0031] 40 Planning device for each operator
[0032] 70 Network
[0033] 101 Operator Management Department
[0034] 1011 Value Chain Management Unit
[0035] 1012 Performance Collection Unit
[0036] 1013 Planning Data Acceptance Unit
[0037] 1014 Product Data Acceptance Unit
[0038] 102 Planning and Coordination Department
[0039] 1021 Scheduling Unit
[0040] 111 Value Chain Data DB
[0041] 1111 Node Information Table
[0042] 1112 Edge Information Table
[0043] 112 Performance Data DB
[0044] 1121 Performance Data Table
[0045] 113 Scheduling Data DB
[0046] 1131 Scheduling Data Table
[0047] 1132 Automatically adjust data table
[0048] 114 Product Data DB
[0049] 1141 Product Data Sheet
[0050] 201 Main control unit
[0051] 202 Processor (CPU)
[0052] 203 RAM
[0053] 204 Auxiliary storage unit
[0054] 205 Input
[0055] 206 Output
[0056] 207 Ministry of Communications
[0057] 301 Plan Change Request Screen
[0058] 302 Report adjustment results screen
[0059] 303 Plan Adjustment Button DETAILED DESCRIPTION
[0060] Hereinafter, a plan coordination device and a plan coordination method for realizing the present invention will be described using the accompanying drawings.
[0061] [Example 1]
[0062] Figure 1 This is a system configuration diagram in which the plan coordination device 10 of this embodiment and the plan preparation device 40 of each target business operator are connected via a network 70. The display device 20 for each user and the display device 30 for the manager are also connected via the network.
[0063] Figure 2 The functional structure diagram of the planning coordination device of this embodiment is shown. The functional part is roughly divided into two parts, namely, the business operator management part 101 and the planning coordination part 102. The business operator management part 101 has: a value chain management unit 1011, which creates a directed graph of business operators based on product transactions between each business operator as a management object and information on the association of business operators representing the delivery relationship, and saves it in the value chain data DB111; a performance collection unit 1012, which collects product transactions and delivery performance information between each business operator as a management object in a specified period and records it in the performance data DB112; a plan data acceptance unit 1013, which accepts the plan data created by each business operator as a management object from each business operator when each business operator creates or updates the plan data and saves it in the schedule data DB113; and a product data acceptance unit 1014, which accepts product data related to the number of parts constituting the products shipped and delivered by each business operator as a management object, and saves it in the product data DB114. The planning coordination unit 102 includes a schedule preparation unit 1021 that prepares changes to the production plans of related managers in response to changes to the production plan of a certain manager.
[0064] Figure 3 A functional block diagram of the planning coordination device 10 is shown.
[0065] The value chain management unit 1011 of the planning coordination device of this embodiment registers each operator as a management object together with its final product ID in the node information table 1111 of the value chain data DB 111. When a production plan for a new product is generated from each operator, the product data receiving unit 1014 receives the quantity of parts constituting the product as product data in the form of BOM (Bill of Material) and registers it in the product data DB 114.
[0066] The plan data receiving unit 1013 receives a report on plan data from each operator at the time when each operator drafts a schedule for production and delivery (transportation, etc.) of products (or parts, etc.), and records it in the schedule data table 1131 and the automatically adjustable data table 1132 of the schedule data DB113.
[0067] The performance collection unit 1012 collects performance data of ordering and ordering relationships between operators according to a specified period and records it in the performance data DB 112. The value chain management unit 1011 refers to the performance data in the performance data DB 112, and when the performance of ordering and ordering relationships of new products between operators is collected, it defines an edge connecting the nodes of two operators in the edge information table 1112 of the value chain data DB 111. For each edge in the edge information table 1112, the reliability of the ordering and ordering relationship between operators is calculated and assigned. The reliability is recalculated and updated every time new performance data is collected.
[0068] The scheduling unit 1021 accepts a plan change request from a certain operator of the management object, refers to the object's product data, value chain data, and automatically adjustable amount of the scheduling data, determines whether the plan change can be coped with, determines the replacement operator, and notifies each operator of the plan change to change the scheduling data.
[0069] Figure 4 This is a diagram showing the hardware structure of the planning coordination device 10. The planning coordination device 10 can be constructed on a general-purpose computer, and includes: a main control unit 201, which is composed of a processor (CPU) 202, a RAM (Random Access Memory) 203, etc.; an auxiliary storage unit 204, which is composed of a ROM (Read Only Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive) using a flash memory, etc.; an input unit 205, which is composed of an input device such as a keyboard or a mouse; and an output unit 206, which is composed of a display device such as an LCD (Liquid Crystal Display) or an organic EL display, various output devices, etc.; and a communication unit 207, which is composed of a NIC (Network Interface Card), etc.
[0070] The communication unit 207 is connected to the plan preparation device 40 and the display device 20 of each business operator to be managed, the display device 30 of the manager, and the like via the network 70 of a wired network or a wireless network.
[0071] The main control unit 201 loads the plan coordination program stored in the auxiliary storage unit 204 into the RAM 203 and executes it through the processor (CPU) 202 to realize Figure 2 The functional parts shown.
[0072] exist Figure 5A , Figure 5B An example of value chain data stored in the value chain data DB 111 is shown in FIG. 111. For example, multiple operators related to a certain product a constitute a group including a factory (operator a) that assembles the product a, a distribution operator (operator c) that transports the product a to a sales company (operator b), suppliers d and e (operators d and e) that deliver parts b and c assembled in product a to the factory, and supplier f (operator f) that delivers sub-parts to supplier d. Operators belonging to the group are called related operators, and each operator is assigned to a node to form a directed graph, i.e., value chain data, in which the flow of objects between operators is represented by arrows (edges).
[0073] Figure 5A An example of a node information table 1111 representing value chain data. The node information table 1111 has data items of node ID (1111a), business name 1111b, business type ID (1111c), and product ID (1111d). The data record 1111e in the third row is the node information of a supplier with a node ID of "N3", a business name of "Business 3", a business type ID of "T3", and a product (or part, etc.) with a product ID of "D3".
[0074] Figure 5B An example of an edge information table 1112 of value chain data is shown in FIG. The edge information table 1112 has data items of edge ID (1112a), call source node ID (1112b), call destination node ID (1112c), and reliability 1112d.
[0075] The call source node represents the node of the connection source of the directed graph connected by arrows (edges), and corresponds to the business operator on the side that delivers (transports, etc.) the product (or parts, etc.). The call destination node represents the node of the connection destination of the directed graph connected by arrows (edges), and corresponds to the business operator on the side that the product (or parts, etc.) is delivered (transported, etc.).
[0076] Reliability is calculated based on past performance data of delivering (transporting, etc.) products (or parts, etc.) from the operator of the call source node to the operator of the call destination node as an indicator for evaluating the degree to which the needs of the operator of the call destination node are met. The calculation formula of reliability is defined by the following formula (1).
[0077] (Equation 1)
[0078] Reliability = c1×(delivery date compliance)+c2×(defective product occurrence rate)+c3×(data update rate)
[0079] Here, the delivery date compliance degree indicates the ratio of the business operator of the call source node to comply with the delivery date when delivering (transporting, etc.) products (or parts, etc.) in the past (for example, a value standardized with a maximum of 1 and a minimum of 0).
[0080] The occurrence rate of defective products indicates the ratio of defective products mixed in after quality inspection after receiving products (or parts, etc.) delivered (transported, etc.) by the operator of the destination node. The occurrence rate can also be increased according to the number of defective products (for example, set to a value standardized in a way that the maximum is 1 and the minimum is 0).
[0081] The calculation of data update degree depends on the value of the number of times the business operator of the call source node has delivered (transported, etc.) products (or parts, etc.) to the business operator of the call destination node in the past (for example, a value standardized with a maximum of 1 and a minimum of 0).
[0082] c1, c2, and c3 are coefficients corresponding to weights of the respective elements in the reliability calculation process.
[0083] The reliability is calculated for each product (or part, etc.), and an amount equivalent to the number of combinations of the operator of the call source node and the operator of the call destination node is calculated and allocated to each edge. The data record 1112e of the first row of the edge information table 1112 is edge information with an edge ID of "E1", an operator with a call source node ID of "N1", an operator with a call destination node ID of "N2", and a reliability of "10".
[0084] Figure 61 shows an example of performance data stored in the performance data DB 112. The performance data table 1121 includes, as data items: a source node ID (1121a) indicating a business operator that delivers (transports, etc.) a product (or part, etc.), a destination node ID (1121b) indicating a business operator that receives delivery (transports, etc.) of the product (or part, etc.), a product ID (1121c) that identifies the product (or part, etc.), an average lead time 1121d based on past delivery performance information, etc., the latest number of delivery performance 1121e, a data update cycle 1121f that specifies the cycle for updating the performance data (if there is no change, no update), and a defective rate (quality) 1121g based on information obtained by inspecting products (or parts, etc.) of past delivery performance.
[0085] The performance collection unit 1012 collects the performance data of the ordering and order-taking relationships between operators according to the specified update cycle, and records it in the performance data DB112. In order to calculate the reliability of the ordering and order-taking relationships between operators, the performance data such as the delivery period compliance information, the occurrence information of defective products, the ordering and order-taking relationship performance frequency, etc. are collected and recorded together with the past history.
[0086] Fig. 7A , Figure 7B 1 shows an example of the schedule data stored in the schedule data DB 113. For example, each business operator reports to the planning coordination device 10 at the time of drafting the schedule for production and delivery (transportation, etc.) of products (or parts, etc.). The planning data receiving unit 1013 of the planning coordination device 10 reports to the planning coordination device 10 based on the plan data reported by each business operator. Fig. 7A Schedule data table 1131, Figure 7B The data table 1132 records may be automatically adjusted or updated.
[0087] Fig. 7A1 shows an example of the schedule data stored in the schedule data table 1131 of the schedule data DB 113. The schedule data table 1131 has, as data items: a schedule ID (1131a) for identifying the schedule; a product ID (1131b) for identifying the product (or part, etc.); a source business operator ID (1131c) for identifying the business operator who produces and delivers (transports, etc.) the product (or part, etc.); a destination business operator ID (1131d) for identifying the business operator who receives the delivery (transport, etc.) of the product (or part, etc.); a delivery quantity 1131e; a reliability 1131f for recording the reliability value stored in the column of the reliability 1112d of the corresponding data record stored in the side information table 1112 of the value chain data DB 111 if there have been several performances of delivering (transporting, etc.) the product (or part, etc.) corresponding to the schedule in the past, and setting it to a blank column in the case of a completely new plan; and a delivery period 1131g for recording the delivery period of the corresponding schedule.
[0088] Figure 7B 1 shows an example of the scheduling data stored in the automatically adjustable data table 1132 of the scheduling data DB 113. The automatically adjustable data table 1132 includes as data items: the name of the operator 1132a of the operator who delivers (transports, etc.) the product (or parts, etc.); the product name 1132b of the product (or parts, etc.); the delivery date 1132c; the scheduled production quantity 1132d; and the automatically adjustable quantity 1132e, which indicates the maximum extent to which the corresponding operator can produce additionally compared to the scheduled production quantity.
[0089] Regarding the automatically adjustable quantity 1132e, when each operator drafts a schedule for the production and delivery (transportation, etc.) of products (or parts, etc.), he / she shall disclose through self-declaration in the planning data reported to the planning coordination device 10 the maximum extent to which additional production (or transportation) can be performed compared to the planned production quantity (or planned transportation quantity).
[0090] The data record 1132f in the second row of the automatically adjustable data table 1132 is the scheduling data that registers the operator name "A", the product name "Part D", the delivery period "1 / 5", the scheduled production quantity "20", and the automatically adjustable quantity of up to "5" that can be produced.
[0091] When a production plan for a new product is generated from each business operator, the product data receiving unit 1014 of the planning coordination device 10 receives a report of the number of parts constituting the product as product data in a BOM (Bill of Material) format and registers it in the product data DB 114 .
[0092] Although not shown in the figure, the product data stored in the product data DB 114 is in the form of a list showing the total quantity of each part constituting the product shipped as a final product by each operator. The data record of each part includes data items such as product name (product name, product ID), model, manufacturer name (operator name, operator ID), and quantity.
[0093] For example, since the supplier of the parts is the final product of the supplier, the supplier (business operator) reports the product data of the parts (products), and the product data receiving unit 1014 registers the product data in the product data table 1141 of the product data DB 114. For example, the product data is in the form of BOM composed of sub-parts and the like.
[0094] exist Figure 8 1 shows the operation flow of the value chain management unit 1011 of the planning coordination device 10. The value chain management unit 1011 is activated at a predetermined cycle to perform a series of processes. The predetermined cycle is a cycle for collecting performance data according to each data record of the performance data table 1121 according to the pre-specified data update cycle 1121f.
[0095] In step S101, the performance collection unit 1012 is started, and the performance collection unit 1012 inquires about performance data from the operator who provides the source node ID and the operator who provides the destination node ID in the corresponding data update period to collect performance information.
[0096] In step S102, if the performance data collected in S101 is a new performance data of the combination of the source node ID, the destination node ID and the product ID, it is determined that there is a new node collaboration and the process moves to S103. If it is performance data of a previously existing node collaboration, the process moves to S104.
[0097] In step S103, based on the performance data determined as new node collaboration in S102, a new edge information data record is created in the edge information table 1112 of the value chain data DB 111. A new edge ID is created in the edge ID (1112a) column of the new data record, the value of the source node ID is input in the call source node ID (1112b) column, and the value of the destination node ID is input in the call destination node ID (1112c) column.
[0098] In step S104, based on the performance data collected in S101, the newly collected performance data is compared with the performance data required for calculating the (delivery date compliance), (defective product occurrence rate), and (data update rate) of formula (1) used in the previous calculation of reliability, and it is determined whether different new performance data has been added. If there is no different new performance data, the reliability does not change, so no calculation is performed. If there is different new performance data, the reliability is calculated by including the past performance data.
[0099] In addition, when it is determined in S102 that there is new node cooperation, since there is no previous reliability calculation, the reliability is calculated based on the newly received performance data.
[0100] In step S105 , when the reliability is calculated in S104 , the calculated reliability value is written and updated in the reliability 1112 d column of the data record corresponding to the edge ID in the edge information table 1112 of the value chain data DB 111 .
[0101] Fig. 9 2 shows the operation flow of the schedule creation unit 1021 of the plan coordination part 102 of the plan coordination apparatus 10. The schedule creation unit 1021 is activated when, for example, a plan change request is received from a certain business operator to be managed.
[0102] In step S201 , the content of the plan change request from the business operator who requested the plan change is compared with the schedule data stored in the schedule data DB 113 and received.
[0103] In step S202 , the node ID ( 1111 a ) of the business operator who has requested the plan change is identified in the node information table 1111 of the value chain data DB 111 .
[0104] In step S203, for example, if product assembler A requests a plan change and makes a plan change to produce 5 more product B, then referring to the product data of product B of operator A registered in product data DB114, it can be known that 5 additional parts of each component of product B need to be ordered.
[0105] Since the various operators (suppliers) who delivered the various parts constituting product B to operator A can be known by searching the performance data 1121, the plans of the various operators (suppliers) to produce the various parts constituting product B are searched in the automatically adjustable data table 1132 of the scheduling data DB 113, and the delivery period and automatically adjustable quantity of the data records corresponding to the operator name and the corresponding product name are confirmed. If the search result of the automatically adjustable data of operator D (supplier D) who delivered a certain part C constituting product B to operator A shows that the delivery period and the automatically adjustable quantity meet the result of the plan change of operator A in terms of both the delivery period and the additional order quantity, that is, the additional order quantity of part C is 5, then it is determined that the plan change can be coped with.
[0106] Alternatively, in the case where the operator (supplier) who delivers part C constituting product B to operator A is not only operator D (supplier D) but multiple operators (suppliers), as long as the total amount of automatically adjustable quantities of each operator (supplier) satisfies the result of operator A's plan change, i.e., an additional order quantity of 5 parts C, and meets the delivery period, it is determined that the plan change can be coped with.
[0107] As described above, according to the various parts that constitute product B, it is determined whether the total amount of automatically adjustable quantities of each operator (supplier) who delivers each part to operator A satisfies the result of operator A's plan change, that is, the additional order quantity of part C of 5 pieces, and meets the delivery period (can cope with plan changes) or does not satisfy it (cannot cope with plan changes).
[0108] In step S204, if the results of determining whether the planned changes can be accommodated according to the components constituting product B in S203 show that even one component cannot accommodate the planned changes, the process proceeds to S205; if all components can accommodate the planned changes, the process proceeds to S209.
[0109] In step S205, the following processing is performed on the parts E (usually there are multiple types) that are determined to be incompatible with the plan change as a result of determining whether the plan change can be accommodated for each part constituting the product B in S203.
[0110] From the node information table 1111 of the value chain data, the business operators that can manufacture the part E are listed. Among these business operators, a business operator F (a related node) whose recent delivery performance cannot be found from the performance data 1121 but whose past delivery performance to business operator A is confirmed from the edge information table 1112 of the value chain data (a case where multiple business operators are confirmed) is determined. If more than one business operator F is determined, they are set as candidates for the replacement node for ordering the additional order quantity of the part E by 5 in descending order of reliability in the edge information table 1112.
[0111] As described above, for all the parts E, it is determined whether there is a business operator F that can be a candidate for a replacement node, and one or more determined business operators F are set as candidates for a replacement node.
[0112] In step S206, if the business operator F that can serve as a candidate for the replacement node is determined for all the parts E in S205, the process proceeds to S208. If there is a part G for which the business operator F that can serve as a candidate for the replacement node is not determined, the process proceeds to S207.
[0113] In step S207, the following processing is performed on the parts G (usually there are multiple types) of the business operator F that have not been identified as candidates for replacement nodes in S205.
[0114] From the node information table 1111 of the value chain data, the business operators that can manufacture the part G are listed. Among the above business operators, a business operator H is identified that has no past delivery record to business operator A (unrelated node), but has a delivery record of the part G to other business operators from the edge information table 1112 of the value chain data (in some cases, multiple business operators are identified). If more than one business operator H is identified, they are set as candidates for the replacement node for ordering the additional order quantity of the part G by 5 in descending order of reliability in the edge information table 1112.
[0115] As described above, for all the parts G, it is determined whether there is a business operator H that can be a candidate for a replacement node, and one or more determined business operators H are set as candidates for a replacement node.
[0116] In step S208, based on the plan change of operator A, operator D who was judged in S203 to be able to cope with the plan change within the range of the automatically adjustable amount for the additional order of part C, operator F who was set as a candidate for the alternative node for the additional order of part E in S205, and operator H who was set as a candidate for the alternative node for the additional order of part G in S207 are determined as the destinations of the plan change.
[0117] In step S209, the operator A who requested the plan change is notified of the ability to cope with the plan change and the request to send the data after the plan change, and for the operator determined to be able to cope with the plan change in S203, the plan making device 40 of the operator is notified of the request to change the plan for additional orders within the range of the automatically adjustable amount.
[0118] Furthermore, with respect to the business operator set as a candidate of the replacement node to which the additional order is requested in S205 and S207, a request to create and transmit new plan data is notified to the plan making device 40 of the business operator.
[0119] In step S210, the plan making device 40 of each operator who was notified of the sending commission of the changed plan data or the newly made plan data in S209 accepts the plan data, and changes or newly records the data records of the schedule data table 1131 and the automatically adjustable data table 1132 of the schedule data DB113 to reflect the plan changes.
[0120] In step S211, according to the plan data received from each business operator in S210, the latest automatically adjustable amount reported by each business operator is written into the automatically adjustable amount 1132e column of the automatically adjustable data table 1132, and the processing of the schedule creation unit 1021 ends.
[0121] [Example 2]
[0122] Fig. 10A , Fig. 10B 2 shows an example of a screen in which a user of each business operator inputs a plan change request from the display device 20 to the plan coordination device 10 , and an example of a screen in which the plan coordination device 10 reports to the user the adjustment result after plan coordination.
[0123] Fig. 10A The user-assembly factory (business operator N5) confirms the planned change of business operator N4 regarding the manufacture of product B and does not deliver the planned quantity, so the user (business operator N5) presses the plan adjustment button 303 to entrust the plan coordination device 10 with the plan coordination, showing an example of a plan change request screen 301. In the screen, a directed graph representing the relationship between business operators centered on the user is displayed, and the impact of the plan change is displayed near the edge of the directed graph (-10 in the figure). In this way, the user can easily confirm the relationship between the business operators and the impact of the plan change. In addition, only the nodes of the business operators who have a direct relationship with the user are displayed in the directed graph, but the nodes of the business operators who are further related to the displayed business operators (N2, N3) can also be displayed. In addition, the display method of the edge can be changed in a way that makes it easy to know the business operators with plan changes, such as using a dotted line to represent the edge connecting the nodes of N4 and N5.
[0124] Fig. 10B The example screen 302 shows that the schedule preparation unit 1021 of the plan coordination device 10 receives a plan change request, confirms that the business operator N3 can make up for the shortfall of the business operator N4, coordinates the plan, and reports the adjustment result. Since it is a new business operator, it can be identified by a thick frame, etc. Once the delivery performance is obtained, the reliability is assigned.
Claims
1. A planning coordination device, characterized in that: The system comprises: a first database for registering each operator of the management object as a node with operator type and product information, and storing value chain data, wherein the value chain data connects the above nodes through edges that are assigned with index values of reliability of ordering and ordering relationships according to the performance of ordering and ordering relationships between operators; a second database for storing product data in the form of a bill of materials (BOM) including the parts and quantities constituting the product reported by each operator before the production plan of the new product; and a third database for storing scheduling data, wherein the scheduling data discloses the product delivery plan between operators reported by each operator at the time point of drafting the schedule for production and delivery of the product and the automatically adjustable amount, wherein the automatically adjustable amount indicates how many units the operator can increase the production volume by at most in addition to the planned production volume of the product; A value chain management unit that generates value chain data, and whenever the performance of the ordering and order-taking relationship of a product is newly collected between operators, recalculates the reliability of the ordering and order-taking relationship between operators, and updates it by assigning it to the corresponding edge; and a scheduling unit that performs the following processing: accepts a plan change request to increase the production volume of a product from an operator of the management object, determines from the product data a plurality of parts constituting the product, and delivers the parts to the operator for all of the plurality of parts, and the delivery period and automatically adjustable amount disclosed by the operator in the scheduling data satisfy the plan change of the operator. In the case of an additional order quantity and delivery period of the part as a result of the plan change of the operator, it is determined that the plan change can be coped with. In the case that the delivery period and the automatically adjustable amount disclosed in the above scheduling data by the delivery operator who delivers one of the above-mentioned multiple parts to the operator do not meet the additional order quantity and delivery period of the part as a result of the plan change of the operator, the operators who are associated with the operator through an edge and can supply the part will be determined as substitute operators in descending order of reliability. In the case that no substitute operator can be determined among the delivery operators associated with the operator through an edge, the substitute operator who is not associated with the operator through an edge and can The operators who can supply the parts are determined as substitute operators in order of reliability from high to low, and the corresponding operators are notified of the plan change and the scheduling data of the third database is changed. The above-mentioned plan coordination device also has a performance collection unit, which automatically starts the collection of performance data at an update cycle separately specified for each of a plurality of performances, and collects the performance of the ordering and order-taking relationship between operators, and at the same time collects the delivery period compliance information, defective product occurrence information, and ordering and order-taking relationship performance frequency data used in calculating the reliability of the ordering and order-taking relationship between operators, and records them together with the past history in the first 4 database, the above-mentioned value chain management unit automatically registers each operator as a management object together with its final product ID in the node information table of the first database. When the above-mentioned value chain management unit collects the performance of the ordering and ordering relationship of new products between operators, the above-mentioned value chain management unit automatically defines a new edge connecting the nodes of two operators in the edge information table of the first database. Whenever the above-mentioned value chain management unit collects new performance of the ordering and ordering relationship between existing operators, it recalculates the reliability of the ordering and ordering relationship between operators based on the above-mentioned performance data, updates the above-mentioned reliability, and assigns the above-mentioned reliability to the corresponding edge.
2. A planning collaboration method, characterized in that: The computer executes the following processes: a process of registering each operator of the management object as a node with operator type and product information, storing value chain data in a first database, the above value chain data connecting the above nodes through edges assigned with index values of reliability of ordering and ordering relationships according to the performance of ordering and ordering relationships between operators; a process of storing the parts and quantities constituting the product and reported by each operator before the production plan of a new product as product data in the form of a bill of materials, i.e., BOM, in a second database; a process of storing scheduling data in a third database, the above scheduling data disclosing the product delivery plan between operators reported by each operator at the time of drafting the schedule for production and delivery of the product and the automatically adjustable amount, the above automatically adjustable amount indicating how many units the operator can increase the production volume by at most in addition to the planned production volume of the product; a process of recalculating the reliability of the ordering and ordering relationship between operators and assigning it to the corresponding edge of the first database whenever the performance of the ordering and ordering relationship of the product is newly collected between operators by the value chain management unit and updating it;The scheduling unit receives a plan change request for increasing the production volume of a product from a business operator of a management target, determines a plurality of parts constituting the product from product data, and determines that the plan change can be coped with when the delivery period and the automatically adjustable amount disclosed in the above-mentioned scheduling data by the delivery business operator that delivers the parts to the business operator meet the additional order quantity and delivery period of the parts as a result of the plan change of the business operator for all of the above-mentioned plurality of parts, and when the delivery period and the automatically adjustable amount disclosed in the above-mentioned scheduling data by the delivery business operator that delivers one of the above-mentioned plurality of parts to the business operator do not meet the additional order quantity and delivery period of the parts as a result of the plan change of the business operator, determines the business operators who are associated with the business operator through an edge and can supply the parts in descending order of reliability as substitute businesses, and when no substitute business operator can be determined among the delivery business operators associated with the business operator through an edge, determines the business operators who are not associated with the business operator through an edge and can supply the parts in descending order of reliability as substitute businesses, notifies the corresponding business operator of the plan change and makes the In the step of changing the schedule data of the third database, the computer further executes the following steps: the performance collection unit automatically starts the collection of performance data at an update cycle individually specified for each of the plurality of performances, collects the performance of the ordering and ordering relationship between the operators, and collects the delivery period compliance information, defective product occurrence information, and the data of the number of performance of the ordering and ordering relationship used in calculating the reliability of the ordering and ordering relationship between the operators, and records them in the fourth database together with the past history; the value chain management unit automatically registers each operator as a management object together with its final product ID in the node information table of the first database; the value chain management unit automatically defines a new edge connecting the nodes of the two operators in the edge information table of the first database when the performance of the ordering and ordering relationship of a new product is collected between the operators; the value chain management unit recalculates the reliability of the ordering and ordering relationship between the operators based on the performance data every time the performance of the ordering and ordering relationship between the existing operators is newly collected, updates the reliability, and assigns the reliability to the corresponding edge.;
