JP2011053962A - Method and system for changing production plan - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To obtain a production plan change method that allows changing of a plan when a delay occurs in a production plan. <P>SOLUTION: Data regarding a manufacturing plan is obtained from a production plan backbone system as a target of production plan change processing, it is determined whether a delay occurs in manufacturing work or delivery of a purchase to be used in the work based on the obtained data, a delay reason for work or delivery where the delay occurs and a changed schedule of the manufacturing plan are collected, delay days for each manufacturing plan is determined based on the collected changed schedule, it is determined whether the delay days can be covered by margin days which are spare days set for each item, which is a management unit, and, when it is determined that the delay days can be covered by the margin days, replanning data where a schedule of the manufacturing plan is changed by appropriating the margin days to the delay days, is created. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a production plan change system that takes into account delays in production planning.

  Conventionally, in producing a production plan in a production management system, it is common to automatically create a production plan (initial plan) based on product information. In addition, various technologies exist for managing the produced production plan. For example, Patent Document 1 below discloses a technique for reducing a delay with respect to a scheduled delivery date at a base that executes a specific process. Further, Patent Document 2 below discloses a technique for enabling timely response by concerned parties by promptly notifying when a delay occurs in production. Further, Patent Document 3 below discloses a technique for collectively managing product quality, cost, and delivery date in a plurality of production factories that perform production in accordance with orders received from customers.

Japanese Patent Laid-Open No. 2006-40039 JP 2003-330519 A JP 2004-246799 A

  However, the above-described conventional technology does not mention a change in the production plan when a delay occurs after the initial plan. Therefore, the production plan is changed by manual processing depending on the judgment and discretion of the department in charge. When making changes, it is necessary to consider the details of the products and the parent-child relationship of products (order of work), organizational and facility-specific capabilities. There was a problem that a heavy load was applied. In addition, if the management of the work itself is entrusted to the manager of the department in charge without implementing the plan change, there will be a delay in delivery time for delivery to other departments. there were.

  This invention is made in view of the above, Comprising: It aims at obtaining the production plan change method and production plan change system which can change a plan when a delay arises in a production plan.

  In order to solve the above-described problems and achieve the object, the present invention is connected to a production plan backbone system that manages a production plan for each construction, and a production plan change system in a production plan change system that changes a production plan. And, as a target of the production plan change process, a data acquisition step for acquiring data relating to a manufacturing plan from the production plan basic system, and a manufacturing operation or work based on the data acquired in the data acquisition step A delay determination step for determining whether or not there is a delay in delivery of the purchased product, a delay information collection step for collecting a reason for the delay in the operation or delivery in which the delay has occurred, and a schedule for changing the production plan, Based on the change schedule collected in the delay information collection step, the delay days determination step for determining the delay days for each production plan. And if it is determined that the delayed days can be covered by the spare days that are spare days set for the sub-items that are the management unit, and if it is determined that the delayed days are covered, the spare days are applied to the delayed days. And a margin days adjustment step of creating rescheduling data in which the schedule of the production plan is changed.

  According to the present invention, it is possible to reduce the load on the person in charge, and there is an effect that it is possible to change the plan quickly and accurately.

FIG. 1 is a diagram showing a configuration example of the present embodiment of a production management system including a production plan change system according to the present invention. FIG. 2 is a block diagram showing an example of the internal configuration of the production management backbone system. FIG. 3A is a diagram illustrating a configuration example of a construction DB. FIG. 3B is a diagram of a configuration example of the manufacturing plan DB. FIG. 3-3 is a diagram illustrating a configuration example of the voucher DB. FIG. 3-4 is a diagram illustrating a configuration example of the construction performance DB. FIG. 4 is a diagram illustrating a configuration example of a production plan change system. FIG. 5A is a diagram illustrating a configuration example of a manufacturing plan delay DB. FIG. 5-2 is a diagram illustrating a configuration example of a ticket delay DB. FIG. 5C is a diagram of a configuration example of the delay reason DB. FIG. 5-4 is a diagram illustrating a configuration example of the review frequency DB. FIG. 5-5 is a diagram illustrating a configuration example of the delay factor DB. FIG. 6 is a flowchart for explaining the production plan change process. FIG. 7 is a flowchart for explaining the delay re-planning process. FIG. 8 is a diagram for explaining an outline of the optimization process. FIG. 9 is a diagram illustrating an example when the delay status by construction is displayed on the screen.

  Hereinafter, an embodiment of a production plan changing system according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Embodiment.
FIG. 1 is a diagram showing a configuration example of the present embodiment of a production management system including a production plan change system according to the present invention. The production management system in FIG. 1 includes, as an example, a production management backbone system 1, a production plan change system 2, a terminal 3 for accessing these systems, and a network 4 such as a LAN (Local Area Network). . The production management backbone system 1 is an existing backbone system, and performs production management of products. The production plan change system 2 changes the production plan managed by the production management backbone system 1.

  FIG. 2 is a block diagram illustrating an internal configuration example of the production management backbone system 1. The production management backbone system 1 in FIG. 2 includes, as an example, a construction DB 11, a manufacturing plan DB 12, a voucher DB 13, a construction performance DB 14, a communication I / F unit 15, and a DB processing unit 16. The construction DB 11 is a database for managing construction unit information. The production plan DB 12 is a database for managing a production schedule plan for each construction. The voucher DB 13 is a database for managing the delivery schedule of purchased items used for construction. The construction result DB 14 is a database for managing the results of the production schedule. Note that the construction in the present embodiment refers to producing a product. The data held in the construction DB 11, the production plan DB 12, the purchase ticket DB 13, and the construction result DB 14 are referred to as construction data, production plan data, purchase ticket data, and construction result data, respectively.

  FIG. 3A is a diagram illustrating a configuration example of the construction DB 11. In the example of FIG. 3A, the construction DB 11 includes “construction number”, “construction subject”, “order source”, “model”, “construction order date”, “construction completion date”, “contract delivery date”, “construction”. Items such as “Scale”, “Design document type”, “Number of drawings”, “Number of sub-items”, “Number of original products”, “Number of work processes”, “Delay point”, “Delay days”, “Plan change point” are provided. . That is, the construction DB 11 manages basic information of construction and various information necessary for managing the construction schedule. The key item of the construction DB 11 is “construction number”.

  As described for each item in FIG. 3A, the “construction number” is a number for uniquely managing the construction. “Construction subject” is the name of the construction. “Order source” is the customer who ordered the construction. “Model” is the model of the product to be produced. “Construction order date” is the start date of construction (production). “Construction completion date” is the deadline date for completion of construction (production). The “contract delivery date” is a delivery date contracted with the “order source”. “Construction scale” is the order amount. “Design document type” is the quantity of design documents created for a product to be produced. “Number of drawings” is the number of drawings of the product to be produced. “Number of details” is the number of details which is a management unit of production. The “number of elementary products” is the number of parts belonging to the “details” in the product to be produced. The “number of work processes” is the total number of processes for manufacturing a product to be produced. The “delay point” is a delay frequency when a delay occurs, and as an example, here, a value is held in process units such as “design / processing / assembly / test / shipment”. “Delay days” is the number of days of delay that occurred in the production plan, and holds a value for each process unit, for example. The “plan change point” is the number of cases where the production plan is changed, and holds a value for each process unit, for example.

  FIG. 3B is a diagram illustrating a configuration example of the manufacturing plan DB 12. In the example of FIG. 3B, the production plan DB 12 includes “construction number”, “detail code”, “element code”, “work process code”, “department code”, “work start date (initial plan)”, Items such as “work completion date (initial plan)”, “work start date (current plan)”, “work completion date (current plan)”, “parent detail code”, and “detail margin days” are provided. That is, in the manufacturing plan DB 12, the work schedule is managed in units of details belonging to each construction. The key items of the production plan DB 12 are “construction number”, “detail code”, “element code”, and “work process code”.

  As described for each item in FIG. 3-2, the “construction number” is a number for uniquely managing the construction. “Fine code” is a fine code. The “element code” is a code of a part belonging to the details. The “work process code” is a code of a work process to be performed for each elementary product. The “department code” is a code of a department that performs the work process. The “work start date (initial plan)” is a scheduled start date for each work process at the time of initial planning, that is, when construction is issued. The “work completion date (initial plan)” is a scheduled completion date of each work process at the time the work is issued. “Work start date (latest plan)” is a scheduled start date of the work process after the plan change. The “work completion date (current plan)” is the scheduled completion date of the work process after the plan change. The “parent-detail code” is a fine-detail code that is a parent when viewed from the details indicated by the detail code. The “detail margin days” is the number of spare days for the production schedule (start date to completion date) in detail units.

  In the production plan in the present embodiment, a production plan is formulated for each detailed unit. The sub-items have a hierarchical structure, and there are child sub-items that are subordinate subordinates and parent sub-items that are upper subordinates in terms of management. The parent item is managed by linking a plurality of child items. Each of the parent details and the child details has its own item margin days. In addition, it is assumed that the production schedule in the present embodiment is formulated in parallel between works.

  FIG. 3-3 is a diagram illustrating a configuration example of the voucher DB 13. In the example of FIG. 3C, the voucher DB 13 includes “purchase code”, “construction number”, “detail code”, “element code”, “order delivery date”, “answer delivery date”, “arrival date”, “Purchase” is provided. “Purchase code” is the order number of the purchased item. “Construction number” is the number of the construction that uses the purchased product. The “detail code” is a detail code that uses the purchased product. The “element code” is a code of a part that uses the purchased item among the details. “Order delivery date” is the scheduled delivery date of the purchased product at the time of initial planning. “Reply delivery date” is a scheduled delivery date that is returned from the purchaser as a result of presenting the order delivery date to the purchaser. The “arrival date” is the date when the purchased item is actually delivered from the purchaser. “Purchase” is the purchaser of the purchased item.

  FIG. 3-4 is a diagram illustrating a configuration example of the construction performance DB 14. In the example of FIG. 3-4, the construction result DB 14 stores “construction number”, “detail code”, “element code”, “department code”, “work start date (actual)”, and “work completion date (actual)”. And the like. As described for each item in FIG. 3-4, the “construction number” is a number for uniquely managing the construction. The “construction number”, “detail code”, “element code”, and “department code” are the same as the items in the manufacturing plan DB 12 described above. “Work start date (actual result)” is the actual date when each work process was actually started. “Work completion date (actual)” is the actual date when each work process was actually completed. The key items of the construction result DB 14 are “construction number”, “detail code”, and “element code”.

  FIG. 4 is a diagram illustrating a configuration example of the production plan change system 2. The production plan change system 2 of FIG. 4 includes a control unit 20, a storage unit 30, and a communication I / F unit 50 as an example. The control unit 20 includes a data acquisition unit 21, a delay determination unit 22, a delay information processing unit 23, a replanning unit 24, a replanning confirmation unit 25, a replanning confirmation unit 26, and a mail function unit 27. Prepare. In addition, the storage unit 30 includes a construction DB 31, a production plan DB 32, a purchase ticket DB 33, a construction performance DB 34, a production plan delay DB 35, a ticket delay DB 36, a delay reason DB 37, a review frequency DB 38, and a delay factor. DB39 and replan DB40 are provided.

  The data acquisition unit 21 acquires data from the production management backbone system 1 (construction DB 11, production plan DB 12, purchase ticket DB 13, construction result DB 14) as an object of the production plan change process. The delay determination unit 22 determines whether there is a delay in the construction based on the data acquired by the data acquisition unit 21. The delayed information processing unit 23 uses the mail function unit 27 to collect information from related parties regarding the construction in which the delay has occurred. The re-planning unit 24 executes re-planning processing for the construction in which the delay has occurred based on the information collected from the parties concerned, and creates re-planning data. The replan confirmation unit 25 notifies the related department of the replan data using the mail function unit 27 and obtains approval. When the re-planning data is authenticated, the re-planning determination unit 26 transmits data related to the re-planning using the mail function unit 27 and performs various processes for accumulating the contents. The mail function unit 27 has a function for sending and receiving electronic mail. Here, e-mail is used for notification to the parties concerned, but other means may be used.

  The construction DB 31 is a database for holding construction data of the construction DB 11. The production plan DB 32 is a database for holding the production plan data of the production plan DB 12. The voucher DB 33 is a database for holding the voucher data of the voucher DB 13. The construction performance DB 34 is a database for holding construction performance data of the construction performance DB 14. The manufacturing plan delay DB 35 is a database for registering delay information for manufacturing plan data in which a delay has occurred in the manufacturing plan. The ticket delay DB 36 is a database for registering delay information for purchased items that have been delayed in delivery. The delay reason DB 37 is a database for managing the delay frequency (weighting) corresponding to the reason for delay. The review frequency DB 38 is a database for accumulating the frequency at which a plan change has occurred. The delay factor DB 39 is a database for accumulating reasons for delay and the like in order to be useful for analysis of delay factors. The replan DB 40 is a database for holding temporary replan data by replan processing.

  As described above, the construction DB 31, the production plan DB 32, the purchase ticket DB 33, and the construction performance DB 34 are copies of the construction DB 11, the production plan DB 12, the purchase ticket DB 13, or the construction performance DB 14 (construction data, production plan data, purchase ticket data, Holds construction results data). Further, the data held in the manufacturing plan delay DB 35, the purchase ticket delay DB 36, the delay reason DB 37, the review frequency DB 38, the delay factor DB 39, and the replan DB 40 are respectively updated in the manufacture plan delay data, the ticket delay data, the delay reason data, and the review. It is called frequency data, delay factor data, and replan data.

  The construction DB 31, the production plan DB 32, the purchase ticket DB 33, and the construction performance DB 34 have the same configurations as the construction DB 11, the production plan DB 12, the purchase ticket DB 13, and the construction performance DB 14, respectively.

  FIG. 5A is a diagram illustrating a configuration example of the manufacturing plan delay DB 35. In the example of FIG. 5A, the production plan delay DB 35 includes “construction number”, “detail code”, “component code”, “work process code”, “department code”, “work start date (initial plan)”. , “Work completion date (initial plan)”, “reason for delay”, “startable date (current plan)”, “completion date (current plan)”. “Construction number” is the number of the construction in which the production schedule was delayed. The “detail code” is a detail code in which the production schedule is delayed in the above construction. The “element code” is an element code for which a delay has occurred in the manufacturing schedule plan in the above construction. The “work process code” is a code of a work process in which a delay has occurred in the production schedule plan in the above construction. The “department code” is a code of a department that performs the work process. The “work start date (initial plan)” is a scheduled start date for each work process at the time the work is issued. The “work completion date (initial plan)” is a scheduled completion date of each work process at the time the work is issued. “Available date (current plan)” is a date when the work process can be initiated after the plan is changed. “Completion date (current plan)” is a completion date of the work process after the plan change. The key items of the production plan delay DB 35 are “construction number”, “detail code”, “element code”, and “work process code”. Further, the replanning DB 40 has the same configuration as the manufacturing plan delay DB 35.

  FIG. 5-2 is a diagram illustrating a configuration example of the ticket delay DB 36. In the example of FIG. 5B, the ticket delay DB 36 includes “purchase code”, “construction number”, “detail code”, “element code”, “department code”, “order delivery date”, “answer delivery date”, Items such as “reason for delay” and “response delivery date (latest plan)” are provided. “Purchase code” is the order number of the purchased item that has been delayed in delivery. “Construction number” is the number of the construction that uses the purchased product. The “detail code” is a detail code that uses the purchased product. The “element code” is a code of a part that uses the purchased item among the details. “Department code” is a code of the order department. “Order delivery date” is the scheduled delivery date of the purchased product at the time of initial planning. “Reply delivery date” is a scheduled delivery date that is returned from the purchaser as a result of presenting the order delivery date to the purchaser. The “reason for delay” is the reason for delay in delivery of purchased products. The “response delivery date (latest plan)” is the latest response delivery date from the purchaser.

  FIG. 5C is a diagram illustrating a configuration example of the delay reason DB 37. In the example of FIG. 5C, the delay reason DB 37 includes items such as “work process code”, “delay reason code”, “delay reason name”, and “delay point”. In this database, the reason for work delay is managed. The “work process code” is a work process code. The “delay reason code” is a code indicating the reason for the delay. The “reason for delay” is a name that classifies the reason for delay. For example, it is classified as “work delay due to design error”, “work delay due to inadequate equipment”, or “ordering mistake of purchased product”. The “delay point” is a degree of delay corresponding to a combination of “work process code” and “delay reason code”. The key items of the delay reason DB 37 are “work process code” and “delay reason code”.

  FIG. 5-4 is a diagram illustrating a configuration example of the review frequency DB 38. In the example of FIG. 5-4, the review frequency DB 38 includes items such as “work process code”, “department code”, and “review frequency”. The “work process code” is a work process code. The “department code” is a code of a department that performs the work process. The “review frequency” is a frequency at which a plan change is made for a combination of “work process code” and “department code”. The frequency is, for example, a value obtained by accumulating the number of plan changes every month, but may be another definition.

  FIG. 5-5 is a diagram illustrating a configuration example of the delay factor DB 39. In the example of FIG. 5-5, the delay factor DB 39 includes items such as “record ID”, “date”, “work process code”, “delay reason name”, “department code”, and “remarks”. “Record ID” is an identifier of each record. “Date” is the system date when the reason for delay is input. The “work process code” and “delay reason name” are the same as the items in the delay reason DB 37. The “department code” is a code of a department that performs the work process. “Remarks” is information for supplementing the delay situation.

  Next, the operation of the production plan change system configured as described above will be described. FIG. 6 is a flowchart for explaining the production plan change process. The production plan change process is started daily, for example.

  The data acquisition unit 21 of the control unit 20 requests the production management backbone system 1 to collect data via the communication I / F unit 50. When the DB processing unit 16 of the production management backbone system 1 receives the request via the communication I / F unit 50, the DB processing unit 16 reads all data from the construction DB 11, the manufacturing plan DB 12, the voucher DB 13, and the construction performance DB 14, and transmits the communication I. The data is transmitted to the production plan change system 2 via the / F unit 50. When the communication I / F unit 50 of the production plan changing system 2 receives the data, the communication I / F unit 50 outputs the data to the control unit 20, and the data acquisition unit 21 of the control unit 20 converts the received data into the construction DB 31, the production plan DB 32, Registration is made in the voucher DB 33 or the construction result DB 34 (step S1). Then, the delay determination unit 22 is notified that the data has been collected.

  The delay determination unit 22 of the control unit 20 reads data from the construction DB 31, the production plan DB 32, the purchase ticket DB 33, and the construction performance DB 34, and determines whether or not there is a delay in the construction based on the data (step S2). ). Construction delays occur due to work delays or delivery delays. Specifically, the following processing is performed to determine work delay. The delay determination unit 22 compares the production plan data and the construction result data with those having the same “construction number”, “detail code”, “component code”, and “work process code”. First, the “work start date (actual)” in the construction result data is the latest work start date (that is, “work start date (current plan)” in the production plan data, or if the value is not set, “ Check whether it is before the value of “work start date (initial plan)”. If the “work start date (actual)” is before the latest work start date in the production plan data, it is determined that the start date is not delayed due to work delay. On the other hand, if the “work start date (actual)” is after the latest work start date of the production plan data, it is determined that the start date is delayed due to work delay. In addition, the “work completion date (actual)” of the construction performance data is the latest work completion date (that is, “work completion date (current plan)”) of the manufacturing plan data, or if the value is not set, “ Check whether it is before the value of “work completion date (initial plan)”. If the “work completion date (actual)” is before the latest work completion date in the production plan data, it is determined that the completion date is not delayed due to work delay. On the other hand, when the “work completion date (actual result)” is after the latest work completion date of the production plan data, it is determined that the completion date is delayed due to the work delay.

  In addition, the following processing is performed to determine the construction delay based on the delivery delay. First, the delay determination unit 22 compares “order delivery date”, “answer delivery date”, and “arrival date” of the voucher data. When there is data only for “response delivery date” and no data for “arrival date”, it is checked whether “response delivery date” is before “order delivery date”. On the other hand, if there is data in both “answer delivery date” and “arrival date”, it is checked whether “arrival date” is before “answer delivery date”. As a result, if the “response delivery date” is later than the “order delivery date”, or if the “arrival date” is later than the “response delivery date”, it is determined that there is a delay in delivery. To do.

  When it is determined that a delay has occurred as described above, the delay determination unit 22 registers the manufacturing plan data for the construction in which the delay has occurred in the manufacturing plan delay DB 35. Further, the voucher data determined to have a delivery delay is registered in the voucher delay DB 36. Then, the manufacturing plan data or the voucher data and work delay or delivery delay are designated, and the delay information processing unit 23 is notified that a delay has occurred.

  The delay information processing unit 23 outputs the manufacturing plan data or the voucher data and a message indicating that work delay or delivery delay has occurred to the mail function unit 27 and instructs the person in charge to send an e-mail. To do.

  When receiving the data, the mail function unit 27 of the control unit 20 refers to the “department code” in any data, for example, and obtains the mail address corresponding to the department code from the address book held by itself. get. Then, for each received data, a delay reason collection mail that is a mail for collecting a delay situation is transmitted via the communication I / F unit 50 with the mail address as a destination including the contents of the data. (Step S3).

  The person in charge (related person) of each department who has received the delay reason collection mail at the terminal 3 or the like in FIG. 1 recognizes that work delay or delivery delay has occurred according to the content of the email. When the work delay occurs, the person in charge determines whether or not the plan is changed depending on the situation at the site, and if so, summarizes the schedule after the change. If there is a delivery delay, summarize the circumstances. Then, for example, the person in charge adds these report contents to the e-mail and transfers them to the manager of the production plan. In the terminal 3 of FIG. 1 and the like, the administrator (related person) who has received the forwarded delay reason collection mail recognizes that work delay or delivery delay has occurred due to the message included in the mail. The manager makes an inquiry to the person in charge or the purchaser as necessary, and the delay factor in the construction DB 11, manufacturing plan DB 12, voucher DB 13, construction result DB 14, and production plan change system 2 in the production management backbone system 1. Refer to DB39. Then, the manager considers countermeasures for the delay, and determines the plan change in consideration of the necessary number of days expected for the reason of the delay. Then, the schedule change schedule (work start date and / or work completion date) of the production plan data changed due to work delay or delivery delay is determined. Here, the production plan data for which the production plan is changed due to the delay is referred to as production plan delay occurrence data. The voucher data for which delivery delay has occurred is referred to as voucher delay occurrence data. In the case of delivery delay, the latest answer delivery date is obtained from the supplier. Even if delivery is delayed, the latest response delivery date is not necessary if the purchased item has already arrived (if the arrival date has been confirmed). Here, the person in charge and the administrator share the work. However, for example, the administrator may perform all the work.

  The administrator must add a delay reason code based on a predetermined code system and a schedule change schedule associated with the production plan delay occurrence data to the delay reason response mail, which is a response to the above delay reason collection mail. The latest answer delivery date associated with the data is input, and “remarks” useful for grasping the cause of the delay are input and returned to the production plan change system 2. The delay reason reply mail has a predetermined format. For example, in the case of work delay, only the work completion date is changed. When only one of the work start date and the work completion date is changed, the original schedule is input to the plan change schedule for those who are not changed. In addition, the specification which makes the direction which is not changed blank. Therefore, the delay reason response email includes the delay reason code set above, the schedule change schedule associated with the production plan delay occurrence data, and if necessary, the latest response delivery date associated with the ticket delay occurrence data. It is.

  When the mail function unit 27 of the control unit 20 in the production plan change system 2 receives the delay reason reply mail (step S4), the mail function unit 27 outputs it to the delay information processing unit 23. When the delay information processing unit 23 receives the delay reason reply mail, if the latest reply delivery date is included, the items [“purchase code”, “construction number”, “detail code”, “ Set "Fundament code", "Department code", "Order delivery date", "Response delivery date"], set the delay reason code included in the delay reason response email to "Delay reason code", and include it in the delay reason response email Data in which the latest answer delivery date is set to “answer delivery date (latest plan)” is registered in the ticket delay DB 36.

  The delay information processing unit 23 calculates a delay point indicating the degree of delay for each construction and the number of days for each construction based on the delay reason reply mail (step S5). In the example of FIG. 3-1, the delay point, the number of days of delay, and the plan change point are respectively for each work process ((1) design / (2) processing / (3) assembly / (4) test / (5). (Shipment) and aggregated.

  The delay point will be described. Specifically, the delay information processing unit 23 acquires the “work process code” of the production plan delay occurrence data included in the delay reason reply mail and the answered “delay reason code”, and uses these as keys to delay. The “delay point” in the reason DB 37 is read. Then, the corresponding construction data is read from the construction DB 31 using the “construction number” of the production plan delay occurrence data as a key. Then, in the construction data, the delay point read out above is added to the “delay point” of the process corresponding to the work process code.

  In addition, the delay information processing unit 23 delays the data in which the “delay reason code” and “remarks” included in the delay reason reply mail and the “work process code” and “department code” of the production plan delay occurrence data are set. Register in the factor DB 39. At this time, “record ID” and “date” (system date) are automatically given by the delay factor DB 39.

  The delay days will be described. The delay information processing unit 23 reads from the manufacturing plan DB 32 data that has the same key item as the answered manufacturing plan delay occurrence data. In the production plan data of the production plan DB 32, “work completion date (latest plan)” is set if a value is set in “work completion date (latest plan)”, and “work completion date (initial plan) is not set. ) ”Is the latest work completion date. The late information processing unit 23 compares the latest work completion date with the work completion date in the schedule change schedule designated by the delay reason reply mail, and obtains the number of late days as the difference. If there is no change in the work completion date, the number of days delayed is zero.

  The delay information processing unit 23 reads the corresponding construction data from the construction DB 31 using the “construction number” of the production plan delay occurrence data as a key. Then, in the construction data, the delay days calculated as described above are added to the “delay days” of the process corresponding to the work process code of the production plan delay occurrence data.

  Then, the delayed information processing unit 23 associates the calculated number of days of delay with the production plan delay occurrence data and outputs it to the replanning unit 24.

  When receiving the production plan delay occurrence data, the replanning unit 24 performs a delay replanning process (step S6). FIG. 7 is a flowchart for explaining the delay re-planning process. The re-planning unit 24 compares the “detail margin days” of the production plan delay occurrence data with the delay days associated with the production plan delay occurrence data (step S21).

  When the detailed margin days are equal to or greater than the delay days (step S21: Yes), since the delay can be covered within the corresponding detail, the re-planning unit 24 changes the production schedule of the element within the same detail (step S22). Specifically, first, manufacturing plan data having the same values as the “construction number”, “detailed code”, and “element code” of the above-mentioned manufacturing plan delay occurrence data, The manufacturing plan data holding the work process code that follows the process is read from the manufacturing plan DB 32 rather than the “code”.

  Next, shift the schedule back by the number of days delayed. When only the “work completion date (initial plan)” is input in the read production plan data, the re-planning unit 24 adds the number of days delayed to the “work completion date (initial plan)” Completed date (current plan) ". On the other hand, if the “work completion date (latest plan)” has already been input, the new work completion date (latest plan) is obtained by adding the number of days late. Further, the work start date designated by the change plan date is defined as “work start date (current plan)”. When there is no change in the work start date on the change plan date, the original “work start date (initial plan)” or “work start date (current plan)” is left as it is. Also, a value obtained by subtracting the number of days delayed (number of days shifted) from the number of days of fine margin is set as a new number of days of fine margin.

  Then, the re-planning unit 24 selects “construction number”, “detail code”, “product code”, “work process code”, “department code”, “work start date (from the data items read from the production plan DB 32). "Initial plan)", "Work completion date (initial plan)", and the reason for delay included in the reply email for reason for delay, "Work start date (current plan)", "Work completion date (latest plan) obtained above" Plan) ”and“ detail margin days ”are created, and the replan data is registered in the replan DB 40.

  On the other hand, when the detailed margin days are less than the delay days (step S21: No), since the delay cannot be covered within the corresponding details, the re-planning unit 24 includes the parent details of the production plan delay occurrence data. The “detail margin days” are compared with the delay days (step S23). Specifically, the re-planning unit 24 reads from the production plan DB 32 the production plan data (parent code) whose “construction number” and “detail code” match the “construction number” and “parent detail code” of the production plan delay occurrence data. Read out detailed manufacturing plan data). The replanning unit 24 compares the value obtained by adding the “fine margin days” of the production plan delay occurrence data and the “fine margin days” of the parent detailed production plan data with the delay days.

  As a result, when the added value, that is, the extra days including the sub-items is equal to or greater than the number of days of delay (step S23: Yes), the sub-item (child sub-item) in which the delay has occurred and the sub-item of the sub-item In particular, since the delay can be covered, the re-planning unit 24 changes the production schedule of the element within the parent item and the element within the child item where the delay has occurred (step S24). First, shift the schedule from the child details. The re-planning unit 24 is the production plan data having the same values as the “construction number”, “detail code”, and “product code” of the production plan delay occurrence data of the sub-items, The manufacturing plan data holding the work process code that follows the process is read from the manufacturing plan DB 32 rather than the “process code”. Then, for example, the “work start date (latest plan)” and “work completion date (latest plan)” are set in the same manner as in the process of step S21 described above, and the new fine margin days are set to zero here. .

  Next, the re-planning unit 24 shifts the schedule of the parent details. For example, the re-planning unit 24 subtracts the number of days delayed by the child details (number of days of child details) from the number of days delayed to obtain the remaining days of delay. Then, in the parent detailed manufacturing plan data, the "work start date (current plan)" and "work completion date (current plan)" are set differently by the number of days that are left behind. The value obtained by subtracting the number of days of remaining lag from "" is set as the new fine margin days.

  For each of the production plan data corresponding to the production plan delay occurrence data and the parent detailed production plan data, “construction number”, “detail code”, “element code”, “work process code”, “department code”, Set “work start date (initial plan)” and “work completion date (initial plan)”, and the reason for delay included in the reply email for reason for delay, “work start date (current plan)”, “ Re-plan data in which the “work completion date (current plan)” and “detail margin days” are set is created, and the re-plan data is registered in the re-plan DB 40.

  In addition, when changing the production plan data within the range up to the sub-items, for example, it is possible to design freely, such as leaving specifications for the sub-items to be shifted further backwards by leaving the number of days in the sub-items. You can do it.

  On the other hand, when the detailed margin days including the sub-details are less than the delay days (step S23: No), the delay cannot be covered in the details (child sub-items) where the delay occurred and the parent details. Next, the re-planning unit 24 compares the “days of fine items” including other child details (other details) having the same parent details as the production plan delay occurrence data with the days of delay (step S25). . Specifically, the re-planning unit 24 produces from the production plan DB 32 the production plan data (others) in which “construction number” and “parent detail code” match the “construction number” and “detail code” of the parent detail production plan data. Read out detailed manufacturing plan data). The re-planning unit 24 compares the value obtained by adding the “fine margin days” of the production plan delay occurrence data and the “fine margin days” of the other fine production plan data with the delay days. When the added value is smaller than the number of days late, the “detail margin days” of the parent detailed manufacturing plan data are further added and compared with the days late.

  As a result, when the number of days of detail including other details is equal to or greater than the number of days of delay (step S25: Yes), the details (child details) and other details that have been delayed, and the parent details Since the delay can be covered, the re-planning unit 24 changes the production schedules of the other sub-item and the parent sub-item and the sub-item in which the delay has occurred (step S26). For example, the re-planning unit 24 allocates the extra margin days to the delayed days in the order of child details, other details, and parent details in which the delay has occurred. Then, processing is performed in the same manner as described above to create replan data and register it in the replan DB 40.

  On the other hand, when the fine margin days including up to other details are less than the number of delay days (step S25: No), since the delay cannot be covered within the other details, the re-planning unit 24 has a low delay frequency. It is decided to change the plan for another construction project, and the process related to the production plan delay occurrence data is terminated (step S27). The production plan delay occurrence data is processed manually separately.

  Next, the re-planning unit 24 performs an optimization process for optimizing the manufacturing plan. First, the replanning unit 24 reads all the production plan data from the production plan DB 32 and reads all the replan data from the replan DB 40. The replanning unit 24 associates the replanning data with the matching key items with the production plan data. Then, based on the production plan data, “work start date (initial plan)”, “work start date (current plan)”, “work completion date (initial plan)”, “work completion date (current plan) for key items. ) ”, The latest start date and the latest completion date, which are the latest schedule, are extracted. At that time, if the replan data is associated, similarly, the latest start date and the latest completion date, which are the latest schedule based on the replan data, are extracted and replaced with the latest start date and completion date of the production plan data. Therefore, the data is to be optimized. Then, the optimization target data is arranged in time series for each “department code” to create a department unit work schedule. Specifically, the latest start date and the latest completion date are set in the order of the latest start date, and the “detail margin days” are added to form a work schedule for one process. This is performed for each optimization target data. Here, a work schedule is created for each construction number.

  Further, the re-planning unit 24 reads the “construction number” and the “delay point” for each work process from the construction DB 31, and adds the delay point for each construction number. Then, the construction numbers are arranged in descending order of the delay points, and priorities are assigned.

  Then, the re-planning unit 24 performs a process of changing the production schedule in the work schedule in units of construction numbers for each department code. First, the re-planning unit 24 determines whether or not other work can be performed by checking whether or not there is a free day in the department unit work schedule for each work number (step S28). For example, it may be determined that other work can be performed if one day is available, or a predetermined number of days may be set. If it is determined that no other work can be performed for any department code (step S28: No), the delay re-planning process in FIG. 7 is terminated without performing optimization. On the other hand, when it is determined that other work can be performed (step S28: Yes), the following processing is performed.

  FIG. 8 is a diagram for explaining an outline of the optimization process. As already described, since the construction is performed in parallel, in FIG. 8, as an example, there is a work schedule of construction #A, construction #B, construction #C, construction #D for a certain department code. Show the case. Here, it is assumed that a work schedule from 8/1 to 8/30 is formulated for the construction #A, and 8/1 to 8/5 are vacant due to a delay. An empty schedule is called an empty schedule. For example, construction #B has a production plan # B01, a production plan # B02, and a production plan # B03 as shown in FIG. 8 as work schedules after 8/1, and the delay point is “10”. To do. Further, it is assumed that the construction #C has a production plan # C01, a production plan # C02, and a production plan # C03 as work schedules after 8/1, and the delay point is “20”. Also, it is assumed that the construction #D has a production plan # D01, a production plan # D02, and a production plan # D03 as work schedules after 8/1, and the delay point is “15”. Further, it is assumed that the delay point of construction #A is “15”.

  Since the replanning unit 24 has 8/1 to 8/5 (5 days) of work #A as an empty schedule, it implements other work ahead of schedule. Here, among the works #A to #D, the work with the highest delay point is the work #C. Therefore, the production schedule is changed by moving the work schedule of the work #C forward (step S29). Since the work that starts earliest after 8/1, which is the start date of the vacant schedule, is the production plan # C01, the replanning unit 24 advances the schedule for the production plan # C01. Here, in FIG. 8, since the production plan # C01 is a schedule of 8/1 to 8/5 (5 days), if it is moved forward, it falls within the vacant schedule ((1) of FIG. 8).

  If the production plan # C01 is moved forward, an empty schedule is generated before the production plan # C02. Therefore, the replanning unit 24 moves the production plan # C02 forward to the subsequent stage of the production plan # C01 ((2) in FIG. 8). Here, since the schedule of manufacturing plan # C02 is 8/10 to 8/20 (11 days), it does not fall within the schedule of manufacturing plan # C01 (5 days). Therefore, the replanning unit 24 instead puts back the construction with the lowest delay point. Here, among the construction #A to the construction #D, the construction with the lowest delay point is the construction #B. Therefore, the re-planning unit 24 changes the production schedule by putting back the work schedule of the construction #B. (Step S30). Since the schedule of the production plan # B01 starts on 8/5 and is 8/5 to 8/12 (8 days), the schedule of the production plan # B01 is newly added to the schedule of the production plan # C02 after the advance. Duplicate. Therefore, the re-planning unit 24 pushes back the schedule of the production plan # B01 by the number of overlapping days ((3) in FIG. 8). In this example, the schedule of the production plan # B01 with a low delay point overlaps with the schedule of the production plan # C02 after the advance, but in general, the most delayed point among the production plans with overlapping schedules. The manufacturing plan belonging to the low construction is pushed back.

  If manufacturing plan # B01 is pushed back, it will overlap with the schedule of manufacturing plan # B04. Therefore, the re-planning unit 24 puts back the subsequent production plans by the number of overlapping days in the production plans belonging to the construction. In the example of FIG. 8, the production plan # B02 is postponed by the number of overlapping days ((4) of FIG. 8), and the production plan # B03 is postponed by the same number of days ((5) of FIG. 8). If a vacant schedule has occurred in the construction (construction #B), the vacant schedule is digested in the process of carrying back.

  The re-planning unit 24 repeatedly executes the above processing for all vacant dates. Then, when the work is completed, the optimized start date and completion date are respectively set to “startable date (current plan)” or “completed date ( The latest plan) ”is set, and the replan DB 40 is updated. Thus, the process of FIG. 7 ends. In the above case, in order to cope with the advancement of a certain construction, the other construction is postponed, so that the consistency of the manufacturing plan for each construction can be maintained.

  Returning to the processing of FIG. 6, the replanning unit 24 notifies the replanning confirmation unit 25 that the replanning is completed. Upon receiving this, the replan confirmation unit 25 reads all replan data from the replan DB 40. Then, the re-planning confirmation unit 25 instructs the mail function unit 27 to send an approval request mail for requesting approval of the re-planning data to related parties. The mail function unit 27 transmits, for example, a message requesting approval of the re-planning data and a mail including the re-planning data to related parties such as the person in charge of each department and the overall manager (step S7). The re-planning confirmation unit 25 receives an approval response mail that is a response to the approval request mail via the communication I / F unit 50 and the mail function unit 27 from a predetermined party required for approval. When the approval response email indicates that the approval is accepted, the replan confirmation unit 25 notifies the replan determination unit 26 that the replan has been approved.

  Upon receiving this, the replan determination unit 26 determines that the replan indicated by the replan data has been determined (step S8). For example, the replan determination unit 26 reads all the replan data in the replan DB 40 and creates, for example, a process chart for each construction as the production schedule data after the change based on the replan data. Then, the re-planning determination unit 26 notifies the mail function unit 27 to distribute the new production schedule data with the production schedule data after the change. The mail function unit 27 distributes the received production schedule data to necessary parties (for example, all managers and workers) by mail (step S9). In addition, the replan determination unit 26 controls the mail function unit 27 to transmit a mail notifying that the replan has been approved to the parties who have transmitted the approval response mail (step S10).

  Further, the replan determination unit 26 compares the production plan data in the production plan DB 32 with the replan data in the replan DB 40 and calculates a plan change point for each work number. Here, in the construction DB 31 in FIG. 3A, the plan change point is the number of work changed in plan, that is, the number of delays for each process of the original product. Therefore, the replan determination unit 26 counts the production plan delay data existing in the production plan delay DB 35 using the “construction number” and “work process code” as keys, and totals the plan change points (step S11). Then, the plan change points are made to correspond to the “construction number”, and the total plan change points are added to the “plan change point” of the “construction number” in the construction DB 31 (step S11).

  In addition, the re-planning determination unit 26 performs various evaluation processes for the construction (step S12). For example, the replan determination unit 26 refers to the manufacturing plan delay data in the manufacturing plan delay DB 35 and counts the number of data using “work process code” and “department code” as keys. Then, the counted value is added to “review frequency” for “work process code” and “department code” in the review frequency DB 38.

  In addition, the replan determination unit 26 outputs the construction-specific delay status to, for example, an administrator terminal (not shown), a management screen (not shown) provided in the production plan change system 2, and the like. Display. FIG. 9 is a diagram illustrating an example when the delay status by construction is displayed on the screen. In FIG. 9, information such as “construction number”, “(construction) subject”, “number of design documents”, “number of sub-items”, and “number of elementary products” is displayed as basic data regarding the construction. "Overall", "Delayed point", "Delayed days", and "Plan change point" are displayed. “Overall” is the number of processes managed for the construction. The “delay point” is a “delay point” in the construction DB 11 and is the number of cases where a delay has occurred in each process. Similarly, “delayed days” is the number of days in which a delay has occurred in each process. Similarly, the “plan change point” is the number of cases where the plan has been changed in each process. By outputting such a form, an administrator or the like can grasp the delay status by construction in real time.

  Thus, the production plan change process in FIG. 6 ends. The re-planning determination unit 26 transmits the “delay point”, “delay days”, and “plan change point” of the construction DB 31 to the construction DB 11 of the production management backbone system 1, the communication I / F unit 50, the production management backbone system 1. The communication I / F unit 15 and the DB processing unit 16 are interfaced and reflected. In addition, the replan determination unit 26 sets the “work start date (latest plan)” and “completion possible date (latest plan)”, “work start date (latest plan)” and “work completion date (latest plan) in the replan DB 40 In the same manner as described above, it is interfaced with the manufacturing plan DB 12 of the production management backbone system 1 and reflected.

  Note that the production plan change process in FIG. 6 is started on a daily basis, for example, but the process after the reception of the delay reason reply mail (FIG. 6: after step S4) is a process at any time. Therefore, if the production plan change process of FIG. 6 is not completed by the next start timing, for example, the process is terminated. The case where the production plan change process is not completed means that the delayed information processing unit does not receive all reply emails for reason for delay, and the replan confirmation unit 25 does not receive all approvals for the replan. This is a case where the process of is not completed. In this case, processing is performed again using the data of the production management backbone system 1 at the next activation timing. At the end of the process, data held in a database other than the delay reason DB 37, the review frequency DB 38, and the delay factor DB 39 are deleted.

  As explained above, the production plan change system according to the present embodiment collects the reason for the delay and the schedule after the change by determining whether or not there is a delay in the production plan and notifying relevant parties to that effect. It was set as the structure to do. At that time, it was decided to manage the delay situation by construction unit. In addition, the delay in the production plan is adjusted in detail units based on the updated schedule that is answered. Furthermore, when it is detected that an empty schedule has occurred due to the adjustment, the production plan is changed between constructions in consideration of the degree of delay, and the production plan is optimized.

  As a result, it is possible to automatically determine that a delay has occurred in the production plan, and in the event of a delay, the plan can be automatically changed. The load can be reduced, and the plan can be changed quickly and accurately. Further, by automatically determining the delay and calculating the degree of delay, it can be used for construction evaluation, and more efficient management becomes possible.

  In the above embodiment, as described in the configuration of the manufacturing plan DB in FIG. 3-2, a plurality of products are managed in detail, which is a management unit of manufacturing, and a manufacturing plan is managed in detail units. However, the manufacturing plan may be managed by another method. For example, the manufacturing plan may be managed in units of elementary products, and in the production plan data, the parent products may be managed based only on the parent-child relationship of work. Also, here, a case has been described in which the parent item has a hierarchical structure in which a plurality of child items are managed, but another hierarchical structure may be employed. In other words, the process can be performed in the same manner as described above even when the production parts are managed in any hierarchy using the production plan data.

  As described above, the production plan change system according to the present invention is useful when performing a production plan, and is particularly suitable for a system that cooperates with an existing production plan backbone system.

1 Production management backbone system 2 Production plan change system 3 Terminal 4 Network 11 Construction DB
12 Production plan DB
13 Purchase DB
14 construction results DB
DESCRIPTION OF SYMBOLS 15 Communication I / F part 16 DB processing part 20 Control part 21 Data acquisition part 22 Delay judgment part 23 Delay information processing part 24 Replanning part 25 Replanning confirmation part 26 Replanning confirmation part 27 Mail function part 30 Storage part 31 Construction DB
32 Manufacturing plan DB
33 voucher DB
34 construction results DB
35 Production plan delay DB
36 Ticket delay DB
37 Reason DB
38 Review frequency DB
39 Delay factor DB
40 Replan DB
50 Communication I / F part

Claims (14)

A production plan change method in a production plan change system that connects to a production plan backbone system that manages a production plan for each construction and changes the production plan,
As a target of the production plan change process, a data acquisition step of acquiring data related to a manufacturing plan from the production plan basic system;
Based on the data acquired in the data acquisition step, a delay determination step of determining whether there is a delay in manufacturing work or delivery of purchases used in the work,
A delay information collection step that collects the reason for the delay in the work or delivery in which the delay is occurring, and the schedule for the change in the manufacturing plan
Based on the change schedule collected in the delay information collection step, a delay days determination step for determining the delay days for each production plan;
It is determined whether or not the delayed days can be covered by the spare days that are spare days set for the details that are the management unit, and if it is determined that they can be covered, the spare days are applied to the delayed days. An extra days adjustment step to create re-planning data with a modified schedule,
A production plan change method characterized by comprising: further,
A construction evaluation calculation step for calculating one or more of delay points that are the number of delays or days of delay that are the number of days in which delays have occurred, as a delay index for a construction unit;
In the re-planning data created in the margin days adjustment step, a first vacancy schedule determination step for determining whether there is a vacancy schedule that can be performed due to a delay,
If it is determined in the first vacancy schedule determination step that there is a vacancy schedule, the vacancy schedule is a manufacturing plan that starts after the vacancy schedule, and the degree of delay is high due to the delay index. For the production plan belonging to the indicated construction, schedule advance step to change schedule by advance,
As a result of the schedule advancement step, if it is necessary to postpone, new replanning data by changing the schedule due to postponement for the production plan belonging to the construction indicated by the delay indicator that the degree of delay is low To create a schedule step backwards,
A second free schedule determination step for determining whether there is a free schedule in which other work can be performed on the re-planning data created in the schedule postponement step;
Including
When it is determined that there is an empty schedule in the second empty schedule determination step, the schedule advance step, the schedule backward step, and the second empty schedule determination step are repeated.
The production plan changing method according to claim 1, wherein: A delay reason storing step for storing the delay reason collected in the delay information collecting step;
The production plan changing method according to claim 1, further comprising: A change point calculation step for calculating, as one of the delay indicators, a plan change point, which is the number of cases where the plan has been changed by the re-planning process for each construction unit,
The production plan changing method according to claim 1, 2 or 3, further comprising: An approval acquisition step for controlling to send an email for obtaining approval for the re-planning data;
When re-planning data is approved in the approval acquisition step, schedule data showing the schedule of the manufacturing plan for each construction, and schedule data distribution step for distributing the schedule data;
The production plan changing method according to any one of claims 1 to 4, further comprising: Delay status output step for outputting the delay status for each construction including one or more delay indicators,
The production plan changing method according to claim 1, further comprising: An interface step for reflecting the schedule of the production plan after the change based on the created re-planning data in the production planning core system;
The production plan changing method according to any one of claims 1 to 6, further comprising: A production plan change system that connects to a production plan core system that manages a production plan for each construction and changes the production plan.
Construction storage means for holding construction data;
Manufacturing plan storage means for holding manufacturing plan data;
Voucher storage means for holding voucher data which is the delivery schedule of purchased items used in the construction;
Construction results storage means for holding construction results data;
Data acquisition means for acquiring production plan data from the production plan backbone system as a target for production plan change processing and storing it in the construction storage means, the manufacturing plan storage means, the voucher storage means, and the construction result storage means When,
Based on the production plan data, the voucher data, and the construction performance data, a delay determination means for determining whether there is a delay in manufacturing work or delivery of purchases used in the work,
Performs control to collect the reason for the delay in the work or delivery in which the delay has occurred and the schedule for changing the production plan, and determines the number of days to be delayed for each of the production plan data based on the collected change schedule. Delayed information processing means;
It is determined whether or not the delayed days can be covered by the spare days that are spare days set for the details that are the management unit, and if it is determined that they can be covered, the spare days are applied to the delayed days. A re-planning means for creating re-planning data with a modified plan schedule;
Re-plan storage means for holding the re-plan data;
A production plan change system characterized by comprising: further,
The delay information processing means calculates one or more of a delay point, which is the number of cases where a delay has occurred, or a delay day, which is the number of days that a delay has occurred, as a delay indicator for a construction unit, and reflects it in the construction storage means. ,
The re-planning means includes
In the re-planning data that you create, determine if there is a vacant schedule that can be performed due to delay, and if it is determined that there is a vacant schedule, start after the vacant schedule for the vacant schedule For the manufacturing plan data belonging to the construction that is shown to be a high degree of delay by the delay index, the schedule is changed in advance,
As a result of the advance, if it is necessary to postpone, the production plan data belonging to the construction indicated by the delay index to indicate a low degree of delay will be updated to create new replanned data. To
The production plan change system according to claim 8, wherein: further,
Delay factor storage means for accumulating delay reasons,
With
The delay information collecting means stores the collected delay reasons in the delay factor storage means.
10. The production plan change system according to claim 8 or 9, wherein further,
The re-plan decision means for calculating a plan change point, which is the number of cases changed by the re-planning process, as one of the delay indexes for the construction unit, and reflecting it in the construction storage means,
The production plan change system according to claim 8, wherein the production plan change system is provided. Replan confirmation means to control to obtain approval for replan data,
Further comprising
When the replan confirmation means approves the replan data, it is determined that the replan data in the replan storage means is confirmed, and schedule data indicating the schedule of the manufacturing plan for each construction is created, and the schedule data is Re-planning confirmation means for controlling distribution,
The production plan change system according to any one of claims 8 to 11, further comprising: The re-planning confirmation means further reads out a delay index for each construction from the construction storage means and outputs a form including one or more delay indices.
The production plan change system according to any one of claims 8 to 12, wherein The replan determination unit further reads out the replan data from the replan storage unit, and performs control for reflecting the replan data in the production plan backbone system.
The production plan change system according to any one of claims 8 to 13, wherein the system changes.

Images