JP2016099640A - Component order placement device and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a component order placement device capable of adjusting the delivery of a component even if the component has already been ordered, in accordance with a change of a production schedule, and improving cashflow.SOLUTION: A component order placement device comprises: a storage section for storing order placement state information including information on an order placement state of a component and contract condition information including information on a contract with a supplier that includes payment conditions of a purchase amount of a component; an input acceptance section for accepting an input of a changed production schedule date that is different from an initial production schedule date of a product; and an adjustment possible component specifying section for specifying the order placement state and the contract conditions with a supplier of a component used for a product whose production schedule date has been changed, from the order placement state information and the contract condition information, respectively, and specifying, as a component whose delivery can be adjusted, a component whose order has not been placed and a component whose order has been placed but whose supplier is not subject to a subcontract law.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a parts ordering apparatus and a program.

  In Patent Document 1, the cost required when a part used in a production process including a plurality of work processes is procured ahead of the delivery date on the standard schedule, and the part is compared with the delivery date on the standard schedule. And a technology for optimizing the delivery date of the parts so that the expected value of the overall cost of the production process is minimized based on the cost of procurement in late. .

JP 2012-181626 A

  In the system described in Patent Document 1, only the initial delivery date that probabilistically minimizes the overall cost is set, and there is no description about the delivery date adjustment when the delivery date is advanced or delayed. Therefore, in the system described in Patent Document 1, delivery and payment based on the delivery are performed at the initial delivery date. In actual procurement operations, there are a number of cases where it is convenient for subcontractors (partners) who deliver parts, especially after the delivery date, so if the delivery dates that match the interests of both parties can be adjusted, Cash flow may improve. However, when the parent company (ordering party) consults with the subcontractor (ordering party) about the delivery date change, it must take into account relevant domestic and foreign laws and regulations such as the Subcontract Act and the Construction Industry Act. In the procurement practice so far, parts that have already been ordered have been dealt with by not adjusting the delivery date change, which has been a factor in the deterioration of cash flow.

  The present invention has been made in view of the above problems, and provides a parts ordering apparatus that can improve the cash flow by adjusting the delivery times of parts even for orders that have already been ordered according to fluctuations in production plans. With the goal.

  In order to solve the above-described problem, a parts ordering apparatus according to the present invention includes order status information including information related to the order status of parts, contract condition information including information related to a contract with a supplier including payment conditions for purchase of parts, and , An input reception unit for receiving an input of a production plan date after a change different from the original production plan date of the product, an order status of parts used for the product whose production plan date has been changed, and the supplier The contract condition is specified from the order status information and the contract condition information, and the supplier is not subject to the subcontract law even if the order status is a part waiting for order and the order status is already ordered. An adjustable part specifying unit that specifies the part as a part whose delivery date can be adjusted.

  According to the parts ordering apparatus according to the present invention, it is possible to improve the cash flow by adjusting the delivery date of parts even for the ordered orders in accordance with the fluctuation of the production plan.

It is a functional block diagram showing an example of functional composition of a parts ordering device concerning a first embodiment of the present invention. It is the figure which showed an example of the production plan information which concerns on 1st embodiment of this invention. It is the figure which showed an example of the component information which concerns on 1st embodiment of this invention. It is the figure which showed an example of the ordering information which concerns on 1st embodiment of this invention. It is the figure which showed an example of the order status information which concerns on 1st embodiment of this invention. It is the figure which showed an example of the contract condition information which concerns on 1st embodiment of this invention. It is the figure which showed an example of the countermeasure component instruction information which concerns on 1st embodiment of this invention. It is the figure which showed an example of the management index evaluation information which concerns on 1st embodiment of this invention. It is the figure which showed an example of the hardware constitutions of the components ordering apparatus which concerns on 1st embodiment of this invention. It is the flowchart which showed the flow of the delivery date adjustment process which concerns on 1st embodiment of this invention. It is the figure which showed an example of the delivery date adjustment instruction | indication screen which concerns on 1st embodiment of this invention. It is the flowchart which showed the flow of the adjustable component specific process which concerns on 1st embodiment of this invention. It is the figure which showed an example of the countermeasure availability determination information which concerns on 1st embodiment of this invention. FIGS. 14A to 14E are diagrams showing, in chronological order, the delivery date, the closing date, and the payment date before and after adjustment of each component according to the first embodiment of the present invention. It is the figure which showed an example of payment date information in 1st embodiment of this invention. It is the figure which showed an example of the display screen on which the countermeasure component and management index which concern on 1st embodiment of this invention were displayed. It is the functional block diagram which showed an example of the function structure of the components ordering apparatus which concerns on 2nd embodiment of this invention. It is the figure which showed an example of the component progress information which concerns on 2nd embodiment of this invention. It is the flowchart which showed the flow of the delivery date adjustment process which concerns on 2nd embodiment of this invention. It is the figure which showed an example of management index evaluation information with which the cash flow improvement expected value which concerns on 2nd embodiment of this invention was matched. It is the figure which showed an example of the display screen on which the countermeasure component and management index which concern on 2nd embodiment of this invention were displayed. It is the functional block diagram which showed an example of the function structure of the components ordering apparatus which concerns on 3rd embodiment of this invention. It is the figure which showed an example of the countermeasure deadline information which concerns on 3rd embodiment of this invention. It is the flowchart which showed the flow of the delivery date adjustment process which concerns on 3rd embodiment of this invention. It is the figure which showed an example of the delivery date adjustment instruction | indication screen which concerns on 3rd embodiment of this invention. It is the figure which showed an example of the display screen on which the countermeasure component and management index which concern on 3rd embodiment of this invention were displayed.

  Hereinafter, a component ordering apparatus according to each embodiment of the present invention will be described with reference to the drawings.

<First embodiment>
FIG. 1 is a functional block diagram illustrating an example of a functional configuration of a component ordering apparatus 100 according to the present embodiment. The component ordering apparatus 100 includes a storage unit 1 and an arithmetic processing unit 2. Further, the storage unit 1 has production plan information 200, parts information 210, order information 220, order status information 230, contract condition information 240, countermeasure part instruction information 250, and management index evaluation information 260. doing. The production plan information 200, the part information 210, the order information 220, the order status information 230, and the contract condition information 240 are used as input information for a predetermined process executed by the part ordering apparatus 100. The countermeasure component instruction information 250 and the management index evaluation information 260 are output information generated by a predetermined process executed by the component ordering device 100.

  FIG. 2 is a diagram illustrating an example of the production plan information 200. The production plan information 200 is, for example, information for managing a date when parts necessary for product production are input to the manufacturing site. Specifically, the production plan information 200 has a record in which the product ID 201 and the production plan date 202 are associated with each other.

  The product ID 201 is information for identifying a product. The production plan date 202 is information indicating a date on which production of a product is started. For example, in the production plan information 200 of FIG. 2, a product with a product ID “X01” is a plan to start production by putting parts necessary for product production into a production site at “2014/10/15”. It is shown that.

  FIG. 3 is a diagram illustrating an example of the component information 210. The part information 210 is information for managing parts procured from a supplier (for example, a part manufacturer). Specifically, the component information 210 includes a record in which a component ID 211, an ordering unit price (10,000 yen) 212, and a procurement LT (date) 213 are associated with each other.

  The component ID 211 is information for identifying a component. The order price (10,000 yen) 212 is information indicating the unit price per part. Procurement LT (date) 213 is information indicating a period (lead time: Lead Time) required from ordering a part to arrival at the factory. For example, in the part information 210 of FIG. 3, a part with the part ID “P01” costs “10,000 yen” per part, and it takes “10 days” from ordering to arrival at the factory. Is shown.

  FIG. 4 is a diagram illustrating an example of the order information 220. The order information 220 is information for managing the order of each part. Specifically, the order information 220 includes a record in which an order ID 221, a part ID 222, a product ID 223, an order quantity 224, and a delivery date 225 are associated with each other.

  The order ID 221 is information for identifying the order of the part specified by the associated part ID. The component ID 222 is information for identifying the component ordered by the order of the associated order ID. The product ID 223 is information for identifying a target product that uses the component specified by the associated component ID. The order quantity 224 is information indicating the quantity ordered for the part specified by the associated part ID. The delivery date 225 is information indicating the delivery date of the part specified by the associated part ID. For example, in the ordering information 220 of FIG. 4, an order with an order ID “# 01” has a part ID “P01” used for a product ID “X01” with a delivery date “2014/10/15” of “10 points” (Piece) "indicates that an order is placed.

  FIG. 5 is a diagram illustrating an example of the order status information 230. The order status information 230 is information for managing the order status of parts. Specifically, the order status information 230 includes a record in which an order ID 231, a component ID 232, an order status 233, and an order reservation date 234 are associated with each other.

  The order ID 231 is information for identifying an order for a part specified by the associated part ID. The component ID 232 is information for identifying a component ordered by an order specified by the associated order ID. The order state 233 is information indicating the order state of the part specified by the associated part ID, and stores, for example, any one of “waiting for order”, “ordered”, and “arrived”. . The order reservation date 234 is information indicating a date when an order is actually placed for an order that has not been placed. For example, in the order status information 230 of FIG. 5, the order with the order ID “# 01” is in the “waiting order” state where the part with the part ID “P01” has not been ordered from the supplier. / 5 "indicates that an order will be placed.

  FIG. 6 is a diagram showing an example of the contract condition information 240. The contract condition information 240 is information for managing the payment conditions for the purchase money of each part determined by the contract with the supplier. Specifically, the contract condition information 240 includes a record in which a component ID 241, a subcontracting law classification 242, a closing date 243, a payment due date 244, and a payment date 245 are associated with each other.

  The component ID 241 is information for identifying a component. The subcontract law classification 242 is information for identifying whether or not the supplier of the part specified by the associated part ID is a target of the subcontract law. For example, one of “target” and “non-target”. Is stored. The closing date 243 is information indicating the date on which the monthly payment amount of the purchased parts is fixed. The payment due date 244 is information indicating the month in which the payment date falls on the basis of the closing date. The payment date 245 is information indicating the payment date of the confirmed payment amount. For example, in the contract condition information 240 of FIG. 6, the part whose part ID is “P01” is the “subject” of the subcontract law, the closing date on which the monthly payment amount is determined is “20 days”, and the closing date It shows that the contract is to deposit the payment amount to the supplier at the “end of month” after “1 month”. Whether or not it is subject to the Subcontract Act is defined according to the size of the supplier's capital and the nature of the transaction. The following explanation will be given on the assumption that it will be treated as impossible.

  FIG. 7 is a diagram showing an example of countermeasure component instruction information 250. The countermeasure parts instruction information 250 is information for managing whether or not countermeasures for adjusting the delivery date of parts are possible for each order when the production plan is changed. Specifically, the countermeasure component instruction information 250 is a record in which an order ID 251, a component ID 252, a product ID 253, an order status 254, countermeasure availability 255, a pre-adjustment delivery date 256, and an adjusted delivery date 257 are associated with each other. have.

  The order ID 251 is information for identifying the order of the part specified by the associated part ID. The component ID 252 is information for identifying a component ordered by the order of the associated order ID. The product ID 253 is information for identifying a target product that uses the component specified by the associated component ID. The order status 254 is information indicating the order status of the part specified by the associated order ID, and stores, for example, any one of “waiting for order”, “ordered”, and “arrived”. . The countermeasure availability 255 is information indicating whether or not a delivery date adjustment countermeasure is possible, and stores, for example, any one of “permitted (completed)”, “acceptable”, and “impossible”. The pre-adjustment delivery date 256 is information indicating the delivery date of parts scheduled at the beginning of production planning. The post-adjustment delivery date 257 is information indicating the delivery date of the part after adjustment changed by the measure for delivery date adjustment. For example, in the countermeasure component instruction information 250 of FIG. 7, the component with the order ID “# 02” and the component ID “P02” is scheduled to be used for the product ID “X01” and is in the “ordered” state. However, the delivery date adjustment measure is “possible”, and the delivery date adjustment indicates that the delivery date of the part has been changed from “2014/10/15” to “2014/10/30”.

  FIG. 8 is a diagram showing an example of the management index evaluation information 260. The management index evaluation information 260 is information for managing the result of evaluating the degree of influence on management that is improved when delivery date adjustment is performed. Specifically, the management index evaluation information 260 includes an order ID 261, an order amount (10,000 yen) 262, a payment date before adjustment 263, a payment date after adjustment 264, a payment date change period (day) 265, a cash It has a record associated with the flow influence degree 266.

  The order ID 261 is information for identifying each order of the order. The order amount (10,000 yen) 262 is information indicating the order amount of the order specified by the associated order ID. The pre-adjustment payment date 263 is information indicating the payment date before the delivery date adjustment of the parts ordered by the order specified by the associated order ID. The adjusted payment date 264 is information indicating the payment date after the delivery date adjustment of the parts ordered by the order specified by the associated order ID. The payment date change period (day) 265 is information indicating the difference in the number of days between the pre-adjustment payment date and the post-adjustment payment date. The cash flow influence degree 266 is information obtained by quantifying the influence degree of the cash flow improved by the delivery date adjustment. For example, in the management index evaluation information 260 of FIG. 8, when the delivery date is adjusted for the order with the order ID “# 02”, the payment date of the order amount “20 (10,000 yen)” is set to “31 (day)”. This indicates that it can be postponed and the degree of influence on the cash flow is “620”.

  Returning to FIG. The arithmetic processing unit 2 includes an input receiving unit 11, a production plan change determining unit 12, a change target component extracting unit 13, an adjustable component specifying unit 14, a delivery date calculating unit 15, a management index evaluating unit 16, and a display. And a control unit 17.

  The input receiving unit 11 is a functional unit that receives a predetermined process execution instruction and information input from a user via an input device (for example, a mouse or a keyboard) provided in the component ordering apparatus 100.

  The production plan change determination unit 12 is a functional unit that determines whether there is a change in the schedule of the production plan. Specifically, the production plan change determination unit 12 compares the latest production plan date for each product acquired from the user via the input reception unit 11 with the production plan date stored in the production plan information 200. Then, it is determined whether or not the production schedule date has been changed.

  The change target part extraction unit 13 is a functional unit that extracts parts used for a product whose production schedule has been changed. Specifically, the change target part extraction unit 13 extracts, from the part information 210, parts used for a product whose production schedule has been changed using the product ID as a key.

  The adjustable component specifying unit 14 is a functional unit that determines whether or not delivery date adjustment is possible for a component whose production schedule has been changed. Specifically, the adjustable component identification unit 14 determines whether or not delivery date adjustment is possible for the component extracted by the change target component extraction unit 13 using the order status information 230 and the contract condition information 240.

  The delivery date calculation unit 15 is a functional unit that calculates the delivery date of the ordered part. Specifically, the delivery date calculation unit 15 calculates a delivery date according to the changed production schedule date for a part whose delivery date can be adjusted.

  The management index evaluation unit 16 is a functional unit that evaluates the degree of influence on cash flow that is improved by delivery date adjustment. Specifically, the management index evaluation unit 16 calculates the influence on the cash flow indicating the management index based on the purchase price of the parts and the adjusted payment date.

  The display control unit 17 is a functional unit that generates screen information to be displayed on an output device such as a display provided in the component ordering apparatus 100. Specifically, the display control unit 17 generates screen information that constitutes an input screen that accepts input of predetermined information from the user, and screen information that includes output information generated by predetermined processing, and outputs the screen information to the output device. indicate.

  The functional configuration of the part ordering apparatus 100 has been described above.

  FIG. 9 is a diagram illustrating an example of a hardware configuration of the component ordering apparatus 100. The component ordering apparatus 100 is realized by an information processing apparatus such as a personal computer or a tablet terminal, for example.

  As shown in the figure, the part ordering apparatus 100 includes an arithmetic processing unit 301, an external storage unit 305, an input unit 306, an output unit 307, and a bus 308 that electrically interconnects them.

  The arithmetic processing unit 301 includes, for example, a microprocessor such as a CPU (Central Processing Unit) 302 and a main storage device that is a memory device such as a RAM (Random Access Memory) 303 and a ROM (Read Only Memory) 304.

  The external storage device 305 is a non-volatile storage device such as a hard disk (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory that can store digital information.

  The input device 306 is a pointing device such as a keyboard, a mouse, and a touch panel.

  The output device 307 is a display device such as a display.

  In addition, the input reception unit 11, the production plan change determination unit 12, the change target component extraction unit 13, the adjustable component identification unit 14, the delivery date calculation unit 15, and the management index evaluation unit 16 included in the arithmetic processing unit 2 The display control unit 17 is realized by a program that causes the CPU 302 to perform processing. This program is stored in the main storage device or the external storage device 305, loaded on the main storage device when the program is executed, and executed by the CPU 302. The storage unit 1 illustrated in FIG. 1 is realized by, for example, a main storage device and an external storage device 305.

  The parts ordering device 100 is not limited to such a hardware configuration, and may be configured using other hardware. For example, the parts ordering device 100 further includes a communication device, and obtains information corresponding to information stored in the storage unit 1 from another device (for example, a server device) connected via a network. May be.

[Description of operation]
Next, the part delivery date adjustment process executed by the part ordering apparatus 100 will be described. FIG. 10 is a flowchart showing the flow of delivery date adjustment processing. The delivery date adjustment process is a process performed for parts used in a product that has been changed on the production schedule date. Therefore, prior to the start of the delivery date adjustment process, the input receiving unit 11 displays an input table for receiving input of the date after the production plan change on the output device 307 via the display control unit 17 and receives input from the user. Accept.

  FIG. 11 is a diagram showing an example of the delivery date adjustment instruction screen 400. The delivery date adjustment instruction screen 400 includes a product ID 401, a pre-change production plan date 402 indicating the initial production plan date of the product specified by the product ID 401, and a post-change production plan that accepts input of the date after the production plan change. An input table associated with the day 403 and an execution button 404 for receiving an instruction to execute the delivery date adjustment process are displayed. In generating the input table, for example, the display control unit 17 extracts the product ID 201 and the initial production plan date 202 from the production plan information 200 and stores them in the product ID 401 and the pre-change production plan date 402 of the input table. indicate.

  Note that the user of the part ordering apparatus 100 inputs the changed date to the changed production planned date 403 associated with the product ID having a changed production date, and presses the execution button 404. When detecting that the execution button 404 is pressed, the input receiving unit 11 starts the delivery date adjustment process.

  When the delivery date adjustment process is started, the production plan change determination unit 12 determines whether or not there is a change in the production plan date (step S001). Specifically, the production plan change determination unit 12 compares the pre-change production plan date 402 stored in the input table with the post-change production plan date 403 and determines whether there is a change in the production plan date. . For example, in the input table of FIG. 11, the production planned date of product ID “X01” is changed from “2014/10/15” to “2014/10/30”, and the production planned date of product ID “X02” is Since it has been changed from “2014/10/1” to “2014/11/1”, the production plan change determination unit 12 determines that there is a change in the production schedule date for these products. When there is no change in the production plan date (No in step S001), the production plan change determination unit 12 ends the process of this flow.

  When there is a change in the production plan date (Yes in step S001), the change target part extraction unit 13 extracts a target part used for a product having a change in the production plan date (step S002). Specifically, the change target part extraction unit 13 identifies the product ID of the product that has changed on the production schedule date from the input table, and extracts the part ID of the order that includes the product ID from the order information 220. To do. For example, in the ordering information 220 of FIG. 4, the part IDs associated with the ordering orders including the product ID “X01” and the product ID “X02”, that is, the order IDs “# 01” to “# 06”, respectively. “P01” to “P06” are extracted.

  Next, the adjustable component identification unit 14 identifies an adjustable component whose delivery date can be adjusted (step S003). FIG. 12 is a flowchart showing the flow of the adjustable component identification process. When the adjustable component identification process is started, the adjustable component identification unit 14 identifies the order status of the component extracted in step S002 from the order status information 230 (step S011). In the order status information 230 of FIG. 5, the order status of the component IDs “P01” to “P06” is specified.

  Next, the adjustable component identification unit 14 determines whether or not the order status of each identified component is “waiting for order” (step S012). If it is “waiting for ordering” (Yes in step S012), the adjustable component specifying unit 14 temporarily stores the countermeasure availability status of the component as “available (done)” in the storage unit 1 (step S015). ), The process of this flow is terminated. On the other hand, when the ordering state is not “waiting for ordering” (No in step S012), the adjustable component specifying unit 14 proceeds to step S013.

  Further, when the ordering status is “waiting for ordering”, the adjustable component specifying unit 14 also specifies the order reservation date from the ordering status information 230 and stores it in the storage unit 1 in association with the countermeasure availability status. In the order status information 230 of FIG. 5, the countermeasure availability status of the component with the component ID “P01” is set to “OK (Done)”, and this is temporarily associated with “2014/10/5” as the order reservation date. Stored in the storage unit 1.

  The status of “Waiting for order” is set to “Yes (finished)”, and the status of “Waiting for order” is different from the status of “Waiting for order”. This is because the order is not disclosed to the supplier and the delivery date can be adjusted without adjusting the delivery date with the supplier.

  Next, the adjustable component specifying unit 14 determines whether or not the ordering status of each specified component is “arrived” (step S013). If it is “arrived” (Yes in step S013), the adjustable component identification unit 14 temporarily stores the countermeasure availability status of the component as “impossible” in the storage unit 1 (step S016). Finish the flow process. In the order status information 230 of FIG. 5, the countermeasure availability status of the component with the component ID “P06” is temporarily stored in the storage unit 1 as “impossible”. On the other hand, when the ordering state is not “arrived” (No in step S013), the adjustable component specifying unit 14 proceeds to step S014.

  Next, the adjustable part identification unit 14 determines that the parts of the identified parts whose order status is other than “waiting for order” or “arrived”, that is, parts whose order status is “ordered”, are subject to the subcontract law. It is determined whether or not (step S014). Specifically, the adjustable part identifying unit 14 identifies from the contract condition information 240 a record including a part ID of a part whose order status is “ordered”, and whether the subcontract law classification 242 is “target”. Determine whether or not. If it is “non-target” (No in step S014), the adjustable component identification unit 14 temporarily stores the countermeasure availability status of the component as “permitted” in the storage unit 1 (step S017). Finish the flow process.

  In the contract condition information 240 of FIG. 6, the subcontracting law classification of parts other than “P04” among the part IDs “P02” to “P05” of the parts whose order status is “Ordered” is “Non-target”. , “P02”, “P03”, and “P05” are temporarily stored in the storage unit 1 as the countermeasure availability status as “permitted”.

  On the other hand, when the subcontract law classification is “target” (Yes in step S014), the adjustable component identification unit 14 temporarily stores the target availability status of the component as “impossible” in the storage unit 1 (step S016), the process of this flow is terminated. In the contract condition information 240 of FIG. 6, since the subcontracting law classification of the component ID “P04” is “target”, the countermeasure availability status of such a component is temporarily stored in the storage unit 1 as “impossible”.

  Moreover, the adjustable component specific | specification part 14 produces | generates the countermeasure availability determination information 270 based on the determination result of an adjustable component, after complete | finishing the determination process of FIG. FIG. 13 is a diagram showing an example of countermeasure availability determination information 270. The countermeasure availability determination information 270 includes a record in which the order ID 271 of the part that has been changed on the production schedule date, the part ID 272, the order status 273, the countermeasure availability 274, and the order reservation date 275 are associated with each other. Yes. The adjustable part specifying unit 14 uses the part ID of the part to be changed extracted in step S002 as a key, the order ID associated with the part ID and the order state, respectively, the order information 220 and the order state information 230. Identify from. Further, the adjustable component identification unit 14 extracts from the storage unit 1 the countermeasure availability status and the order reservation date of the component ID temporarily stored in the processes of steps S015 to S017. Then, the adjustable component specifying unit 14 generates countermeasure availability determination information 270 that sets these pieces of information as an order ID, a component ID, an order status, countermeasure availability and an order reservation date, respectively.

  Returning to FIG. After specifying the adjustable part, the delivery date calculation unit 15 calculates the delivery date after the adjustment for the part whose delivery date can be adjusted (step S004). Specifically, the delivery date calculation unit 15 uses the countermeasure availability determination information 270 to identify a component ID that is associated with “possibility (completed)” or “possible” as the countermeasure availability. Moreover, the delivery date calculation part 15 specifies the product ID of the product in which the component specified by this component ID is used from the order information 220. For example, in the countermeasure availability determination information 270 of FIG. 13, the component IDs “P01” to “P03” and “P05” in which “possible (completed)” or “possible” is stored in the countermeasure availability are specified. The product IDs “X01” and “X02” for which is used are specified from the order information 220.

  Moreover, the delivery date calculation part 15 extracts the record containing the identified product ID from an input table, and specifies the production schedule date 403 after a change matched with this product ID. In addition, the delivery date calculation unit 15 calculates the identified post-change production plan date as the delivery date after the adjustment of the parts used for the product having the product ID. For example, in the input table of FIG. 11, “2014/10/30” and “2014/11/1” are calculated as the delivery dates after adjustment of the products specified by the product IDs “X01” and “X02”, respectively. .

  The delivery date calculation unit 15 recalculates the order reservation date for a part whose countermeasure availability in the countermeasure availability determination information 270 is “Available”. Specifically, the delivery date calculation unit 15 identifies the part ID of a part whose countermeasure availability is “possible (done)” from the countermeasure availability determination information 270, and the procurement LT of the part information 210 associated with the part ID. Is identified. Moreover, the delivery date calculation part 15 specifies the product ID of the product in which such a part is used from the ordering information 220, and specifies the post-change production plan date associated with the specified product ID from the input table. Further, the delivery date calculation unit 15 calculates a date obtained by subtracting the procurement LT from the specified post-change production plan date as a new order reservation date. For example, in the countermeasure availability determination information 270 of FIG. 13, the component ID “P01” of the component associated with “OK (completed)” is specified, and the procurement LT “10 (day)” of the component is the component information 210. Identified from Further, the product ID “X01” in which the part ID “P01” is used is specified from the order information 220, and the post-change production schedule date “2014/10/30” associated with the product ID is specified from the input table. The Further, “2014/10/20” obtained by subtracting the procurement LT “10 (day)” from “2014/10/30” which is the production planned date after the change is calculated as the order reservation date.

  Further, the delivery date calculation unit 15 associates the calculated delivery date and order reservation date with the part ID, order ID, product ID, order status, availability of countermeasures, and delivery date before adjustment for each part. The countermeasure component instruction information 250 is generated.

  Further, the delivery date calculation unit 15 also has a component ID, an order ID, a product ID, an order status, and the like for parts that cannot be adjusted for delivery, that is, parts for which “impossibility” is stored in the countermeasure availability in the countermeasure availability determination information 270. The countermeasure availability and the pre-adjustment delivery date are stored in the countermeasure component instruction information 250.

  In this embodiment, the production schedule date after the change and the delivery date of the part are treated as the same day, but for example, when a preparation period such as warehousing or delivery of parts is required from the delivery date of the part to the production schedule date. The date after subtracting the preparation period from the production plan date after the change may be used as the adjusted delivery date.

  Next, the management index evaluation unit 16 evaluates the management index (step S005). Specifically, the management index evaluation unit 16 evaluates the management index by calculating the degree of influence on the cash flow by adjusting the delivery date.

  The management index evaluation unit 16 calculates the payment date change period from the payment date before the delivery date adjustment to the payment date after the delivery date adjustment when calculating the influence on the cash flow. Specifically, the management index evaluation unit 16 specifies the pre-adjustment delivery date and the post-adjustment delivery date for each part for each order ID using the countermeasure component instruction information 250. Further, the management index evaluation unit 16 specifies the closing date, the payment due date, and the payment date of the part from the contract condition information 240. Then, the management index evaluation unit 16 calculates a specific payment date for each of the specified pre-adjustment delivery date and post-adjustment delivery date based on the specified closing date, payment due date, and payment date.

  FIGS. 14A to 14E are diagrams showing, in chronological order, delivery times before and after adjustment of each part, closing dates, and payment dates. FIG. 14A shows the delivery date before and after adjustment of the part specified by the order ID “# 01”, the part ID “P01” and the part specified by the order ID “# 02” and the part ID “P02”, and the closing date. And the payment date. The delivery date before adjustment of the parts related to the order IDs “# 01” and “# 02” is “2014/10/15”, and the closing date, payment date, and payment date “20 days”, “ “After one month” and “End of month” are identified from the contract condition information 240. As a result, the deadline for the delivery date is calculated as “10/20” which is the 20th of the same month, and the payment date is calculated as “11/30” which is the end of the month one month after “10/20”. Further, the delivery date after adjustment of the parts related to the order IDs “# 01” and “# 02” is “2014/10/30”, and the closing date, the payment due date, and the payment date of the parts are the same as described above. Therefore, the deadline for the adjusted delivery date is calculated as “11/20”, which is the 20th of the same month, and the payment date is calculated as “12/31”, which is the end of the month one month after “11/20”. .

  FIG. 14B shows the delivery date, the closing date, and the payment date before and after adjustment of the part specified by the order ID “# 03” and the part ID “P03”. The delivery date before adjustment of the part relating to the order ID “# 03” is “2014/10/15”, the closing date of the part, the payment due date, and the payment date “end of month”, “one month later”, “ “End of month” is identified from the contract condition information 240. Accordingly, the closing date for the delivery date is calculated as “10/31” which is the end of the same month, and the payment date is calculated as “11/30” which is the end of the month one month after “10/31”. In addition, the delivery date after adjustment of the part relating to the order ID “# 03” is “2014/10/30”, and the closing date, payment date, and payment date of the part are the same as described above, so The deadline for the delivery date is calculated as “10/31” which is the end of the same month, and the payment date is calculated as “11/30” which is the end of the month one month after “10/31”.

  FIG. 14C shows the delivery date, the closing date, and the payment date of the part specified by the order ID “# 04” and the part ID “P04”. In addition, since the availability of countermeasures is “impossible” and the delivery date cannot be adjusted, the deadline for the delivery date “2014/10/1” is calculated as “2014/10/20”, which is “20 days” of the same month, The payment date is calculated as “11/20”, which is 20 days one month after “10/20”.

  FIG. 14D shows the delivery date before and after adjustment of the part specified by the order ID “# 05” and the part ID “P05”, the closing date, and the payment date. The delivery date before adjustment of the part related to the order ID “# 05” is “2014/10/1”, and the closing date, payment date, and payment date “end of month”, “1 month later”, “ “End of month” is identified from the contract condition information 240. Accordingly, the closing date for the delivery date is calculated as “10/31” which is the end of the same month, and the payment date is calculated as “11/30” which is the end of the month one month after “10/31”. Further, the delivery date after adjustment of the part relating to the order ID “# 03” is “2014/11/1”, and the closing date, the payment date, and the payment date of the part are the same as described above. The deadline for the delivery date is calculated as “11/30” which is the end of the same month, and the payment date is calculated as “12/31” which is the end of the month one month after “11/30”.

  FIG. 14E shows the delivery date, the closing date, and the payment date of the part specified by the order ID “# 06” and the part ID “P06”. In addition, since the availability of countermeasures for these parts is “impossible” and the delivery date cannot be adjusted, the deadline for the delivery date “2014/9/16” is calculated as “2014/9/30”, which is the “end of month” in the same month. The day is calculated as “11/1”, which is the beginning of the month two months after “9/30”.

  When the management index evaluation unit 16 calculates the payment date before and after the adjustment of each part in this way, the management index evaluation unit 16 generates payment date information 280. FIG. 15 is a diagram showing an example of payment date information 280. The payment date information 280 includes a record in which the order ID 281, the component ID 282, the pre-adjustment payment date 283, and the post-adjustment payment date 284 are associated with each other. The management index evaluation unit 16 associates the calculated payment date before and after the adjustment with the order ID and the component ID and stores them in the payment date information 280. The management index evaluation unit 16 does not store the date for the adjusted payment date associated with the part ID that cannot be adjusted for delivery.

  Next, the management index evaluation unit 16 calculates a payment date change period. Specifically, the management index evaluation unit 16 calculates the difference from the payment date before adjustment to the payment date after adjustment in the payment date information 280. For example, in the payment date information 280 of FIG. 15, the payment date of the part specified by the order ID “# 01”, the part ID “P01” and the part specified by the order ID “# 02” and the part ID “P02” is changed. The period is “31 days”. In addition, since the part specified by the order ID “# 03” and the part ID “P03” has no change in the payment date before and after the adjustment, the payment date change period is “0 day”. Further, the payment date change period of the part specified by the order ID “# 05” and the part ID “P05” is “31 days”. Note that the management index evaluation unit 16 does not adjust the delivery date, that is, the part identified by the part ID of the record in which the date is not stored in the payment date after adjustment of the payment date information 280 (for example, the part ID “P04” and “ The payment date change period of the part specified by “P06” is not calculated.

  Next, the management index evaluation unit 16 calculates the degree of influence on the cash flow by adjusting the delivery date based on the payment date change period and the part order amount. Since the degree of influence on the cash flow due to the delivery date adjustment increases (becomes better) as the order amount increases and the payment date is delayed, for example, in this embodiment, the order amount and the payment date change period The product determines the impact on cash flow. Note that the method for calculating the impact on cash flow is not limited to such a method, and any method can be used as long as it is based on a predetermined rule using the order amount or payment date change period. You may ask.

  Specifically, the management index evaluation unit 16 specifies the order unit price of each part from the part information 210 and specifies the order quantity of each part from the order information 220. Then, the management index evaluation unit 16 calculates the order amount by integrating the specified order unit price and the order quantity. Further, the management index evaluation unit 16 calculates the degree of influence on the cash flow by multiplying the calculated order amount by the payment date change period described above. The management index evaluation unit 16 does not calculate the influence on the cash flow for parts that cannot be adjusted for delivery, that is, parts for which the payment date change period has not been calculated.

  For example, in the case of the component ID “P01”, “1 (order unit price−10,000 yen) × 10 (order quantity) = 10 (10,000 yen)” is calculated as the order amount. Further, the degree of influence of such parts on the cash flow is calculated as “10 (order amount−10,000 yen) × 31 (payment date change period−day) = 310”. In the case of the component ID “P02”, “2 (order unit price−10,000 yen) × 10 (order quantity) = 20 (10,000 yen)” is calculated as the order amount. Also, the degree of influence of such components on the cash flow is calculated as “20 (order amount−10,000 yen) × 31 (payment date change period−day) = 620”. In the case of the component ID “P03”, “2 (order unit price−10,000 yen) × 10 (order quantity) = 20 (10,000 yen)” is calculated as the order amount. In addition, the degree of influence of such components on the cash flow is calculated as “20 (order amount−10,000 yen) × 0 (payment date change period−day) = 0”. In the case of the component ID “P05”, “3 (order unit price−10,000 yen) × 10 (order quantity) = 30 (10,000 yen)” is calculated as the order amount. Also, the degree of influence of such components on the cash flow is calculated as “30 (order amount−10,000 yen) × 31 (payment date change period−day) = 930”.

  When the degree of influence on the cash flow is calculated in this way, the management index evaluation unit 16 generates management index evaluation information 260. Specifically, the management index evaluation unit 16 determines the order ID of each part, the order amount (10,000 yen), the pre-adjustment payment date, the post-adjustment payment date, the payment date change period (day), and the cash flow. The management index evaluation information 260 in which the degree of influence is correlated is generated.

  Returning to FIG. When the management index evaluation information 260 is generated, the display control unit 17 outputs the countermeasure component and the management index (step S006). Specifically, the display control unit 17 generates screen information including predetermined items of the countermeasure component instruction information 250 and the management index evaluation information 260 and a graph indicating the accumulated payment amount by date before and after the implementation of the countermeasure for delivery date adjustment, The information is displayed on the output device 307.

  FIG. 16 is a diagram showing an example of a display screen 500 on which countermeasure parts and management indicators are displayed. A graph 501 shown in the upper part of the display screen 500 shows the cumulative payment amount by date before and after the implementation of measures for delivery date adjustment. A display table 510 shown at the bottom of the display screen 500 shows countermeasure parts and management indicators.

  When the display control unit 17 generates the display table, the order ID, the part ID, the product ID, the ordering status, the availability of the countermeasure, the pre-adjustment delivery date, and the adjustment from the countermeasure part instruction information 250 and the management index evaluation information 260 are adjusted. Information associated with the post-delivery date, the order amount (10,000 yen), the payment date change period (day), and the cash flow influence degree is extracted. The display control unit 17 also extracts the extracted information from the order ID 512, the part ID 513, the product ID 514, the order status 515, the countermeasure availability 516, the pre-change delivery date 517, the post-change delivery date 518, and the order amount. A display table 510 in which (ten thousand yen) 519, payment date change period (day) 520, and cash flow influence degree 521 are associated with countermeasure implementation check boxes 511 is generated and displayed. Note that the display control unit 17 displays the countermeasure implementation check box 511 in which “impossible” is stored as the countermeasure availability in a state where the countermeasure cannot be selected. In addition, the display control unit 17 displays the product ID 514, the order status 515, the countermeasure availability 516, the order amount (10,000 yen) 519, the payment date change period (days) 520, and the cash flow influence level 521. In addition, a check button for accepting a sorting instruction for narrowing search or sorting is also displayed.

  Further, the display control unit 17 extracts the payment date of each part for which the countermeasure execution check box 511 of the display table 510 is checked from the management index evaluation information 260 and associates it with the horizontal axis 502. In addition, the display control unit 17 calculates a cumulative amount obtained by adding up the order amount of each part on each payment date from the management index evaluation information 260, and associates this with the vertical axis 503, whereby a graph 501 of the cumulative payment amount by date 501. Is generated.

  When the input reception unit 11 detects an input to the countermeasure execution check box 511, the input reception unit 11 checks or unchecks the countermeasure execution check box 511 via the display control unit 17, and checks the date of the part that is checked. The display is switched to a graph 501 showing the accumulated payment amount. As a result, the user can grasp whether or not measures for each order of parts are available and the degree of influence on the cash flow by implementing the measures.

  When the input receiving unit 11 detects that the product ID 514, the ordering status 515, and the countermeasure availability 516 check button have been pressed, the input receiving unit 11 pulls down a narrowed-down list of each item via the display control unit 17. For example, when the check button of the product ID 514 is pressed, the display control unit 17 displays a list of product IDs (for example, “X01” to “X03”) included in the countermeasure component instruction information 250. In addition, the display control unit 17 displays only information related to the component associated with the product ID selected from the product IDs displayed in the list on the display table 510. When the check button of the order status 515 is pressed, the display control unit 17 displays the order status (for example, “waiting for order”, “order (completed)”, and “arrived” included in the countermeasure component instruction information 250. )). In addition, the display control unit 17 displays only information related to the part associated with the order status selected from the product IDs displayed in the list on the display table 510. When the check button for countermeasure availability 516 is pressed, the display control unit 17 lists countermeasure availability (for example, “possible (completed)”, “possible”, and “impossible”) included in the countermeasure component instruction information 250. indicate. In addition, the display control unit 17 displays only information related to the component associated with the countermeasure availability selected from the countermeasure availability displayed in the list on the display table 510.

  Further, when the input receiving unit 11 detects that the order amount (10,000 yen) 519, the payment date change period (day) 520, and the cash flow influence level 521 check button are pressed, the input receiving unit 11 causes the display control unit 17 to Thus, a sorting list for specifying the arrangement order of the records included in the display table 510 is displayed in a pull-down manner. For example, when the check button of the order amount (10,000 yen) 519 is pressed, the display control unit 17 displays a sorting list that designates the order of the amount from the highest to the lowest. In addition, the display control unit 17 rearranges and displays the records in the display table according to the selected arrangement order. When the check button of the payment date change period (day) 520 is pressed, the display control unit 17 displays a sorting list that specifies the longest order or the shortest order of the payment date change periods. In addition, the display control unit 17 rearranges and displays the records in the display table 510 according to the selected arrangement order. Further, when the check button of the cash flow influence level 521 is pressed, the display control unit 17 displays a sorting list that specifies the order in which the cash flow influence degree is large or small. In addition, the display control unit 17 rearranges and displays the records in the display table 510 according to the selected arrangement order.

  With such a refined search or sort function, the user can narrow down the display to specific products, orders that have already been ordered, or orders that can be dealt with, and records can be ordered in descending order of order amount, payment date change period, and cash flow impact. They can be rearranged, making it easier to prioritize measures.

<Second embodiment>
Next, a second embodiment of the present invention will be described. The part ordering apparatus 100 according to the present embodiment calculates an expected improvement value of the cash flow in consideration of the production progress of the parts of the supplier.

  FIG. 17 is a functional block diagram illustrating an example of a functional configuration of the component ordering apparatus 100 according to the present embodiment. The basic configuration of the component ordering apparatus 100 is the same as the functional configuration of the first embodiment, but the arithmetic processing unit 2 includes a component progress degree calculating unit 18 and an improved expected value calculating unit 19, and the storage unit 1 This is different from the first embodiment in that the component progress information 600 generated by the predetermined process is stored. In addition, about the structure same as 1st embodiment, the same code | symbol is attached | subjected and description is abbreviate | omitted.

  The part progress degree calculation unit 18 is a functional part that calculates the degree of progress of parts production by the supplier. Specifically, the part progress degree calculation unit 18 generates part progress degree information 600 including the progress degree of part production, and stores this in the storage unit 1.

  The expected improvement value calculation unit 19 is a functional unit that calculates an expected improvement value of cash flow. Specifically, the expected improvement value calculation unit 19 calculates an expected improvement value of cash flow, and stores this in the storage unit 1 in association with the management index evaluation information 260.

  FIG. 18 is a diagram illustrating an example of the component progress information 600 stored in the storage unit 1. The part progress information 600 is information for managing an estimate of the supplier's part production progress for each order. Specifically, the component progress information 600 includes a record in which an order ID 601, a component ID 602, a procurement LT (date) 603, and a component progress (%) 604 are associated with each other.

  The order ID 601 is information for identifying an order for a part specified by the associated part ID. The component ID 602 is information for identifying a component ordered by the order of the associated order ID. The procurement LT 603 is information indicating a period (lead time: Lead Time) required from ordering a part to arrival at the factory. The part progress 604 is information indicating the progress of part production. For example, in the part progress information 600 shown in FIG. 18, an order with an order ID “# 02” and a part ID “P02” has a procurement LT “30 (day)” and the current date (for example, The date of generation of the part progress information 600) indicates that the part production progress is an estimate of “20%”.

  FIG. 19 is a flowchart showing the flow of delivery date adjustment processing according to the present embodiment. In addition, since the process of step S021-step S025 is the same as that of step S001-step S005 in the delivery date adjustment process of 1st embodiment, description is abbreviate | omitted.

In the delivery date adjustment process of FIG. 19, when the management index is evaluated (step S025), the part progress degree calculation unit 18 calculates the progress degree of production of adjustable parts (step S026). Specifically, the part progress degree calculation unit 18 specifies the delivery date of each part specified by the order ID of the management index evaluation information 260 from the order information 220, and calculates a period T _i from the present time to the delivery date. Further, the component progress degree calculation unit specifies the procurement lead time LT _i of the component from the component information 210. Then, the part progress degree calculation unit calculates each of the order orders i based on the period T _i from the current time to the delivery date and the procurement lead time LT _{i of the} parts related to the order order by the following formula (1). It calculates the progress degree P _i of parts production according to the order order.

In the above formula (1), with respect to procurement lead time LT _i of each order order i, if the period T _i from the present time until the delivery is short, the supplier starts the arrangements and parts production of materials used in the production of parts As the difference between the procurement lead time LT _i and the period T _i is larger, it is expected that the production of parts is more advanced. On the other hand, with respect to procurement lead time LT _i of each ordering the order i, if the period T _i from the present time until the delivery time is long, likely parts production has not yet started, and the procurement lead time LT _i and period T _i The smaller the difference is, the more likely it is that the production of parts is closer to the start. Note that the value indicating the degree of component progression approaches 0 as the state is closer to unstarted.

For example, if the current time is “2014/9/21”, the delivery date of the part specified by the order ID “# 02” of the ordering information 220 in FIG. 4 is “2014/10/15”, so the period T _i = 24 days. Further, in the part information 210 of FIG. 3, since the procurement LT of the part (part ID “P02”) related to the order is 30 days, LT _i = 30 days is calculated. Therefore, by substituting these values into the above equation (1), the progress P _i of parts production is calculated as 0.2 (20%). In this way, the part production progress P _i is calculated for all parts related to each order included in the management index evaluation information 260.

  When the part progress degree calculation unit 18 calculates the progress degree of production of each part in this manner, the part progress degree information 600 is generated by associating the order ID, the procurement LT, and the part progress degree with the part ID. This is stored in the storage unit 1.

Next, the improvement expected value calculation unit 19 calculates an improvement expected value of cash flow (step S027). Specifically, the expected improvement value calculation unit 19 uses the cash flow influence level CF _i and the part production progress level P _i to calculate the expected improvement value E _i of the cash flow by the following equation (2). calculate.

In the above formula (2), as the part production progress P _i is smaller, the part production at the supplier is not progressing and the delivery time is likely to be adjusted. Further, the larger the cash flow influence level CF _i is, the greater the efficiency of improving the cash flow when the delivery date adjustment is successful. Therefore, the improvement expected value calculation unit calculates the improvement expected value of cash flow by accumulating these values.

For example, in the management index evaluation information 260 of FIG. 8, the cash flow influence level CF _{i of} the order ID “# 02” is “620”, and the production progress of the part specified by the order ID is “0.2”. (20%) ”, the expected cash flow improvement value E _i is calculated as E _i = (1−0.2) × 620 = 496”. In this way, the cash flow improvement expected value E _i is calculated for all the parts related to each order in which the delivery date can be adjusted included in the management index evaluation information 260.

  When the expected cash flow improvement value of the part related to each order is thus calculated, the expected improvement value calculation unit 19 calculates the calculated cash flow in the record of the management index evaluation information 260 including the corresponding order ID. The improvement expectation value is associated and stored in the storage unit 1. FIG. 20 is a diagram illustrating an example of the management index evaluation information 260 associated with the cash flow improvement expected value 267.

  Next, the display control unit 17 outputs the countermeasure component and the management index (step S028). Specifically, the display control unit 17 generates screen information including predetermined items of the countermeasure component instruction information 250 and the management index evaluation information 260 and a graph indicating the accumulated payment amount by date before and after the implementation of the countermeasure for delivery date adjustment, The information is displayed on the output device 307.

  FIG. 21 is a diagram showing an example of a display screen 700 on which countermeasure parts and management indicators are displayed. A graph 701 shown at the top of the display screen 700 shows the cumulative payment amount by date before and after the implementation of the measure for delivery date adjustment. A display table 710 at the bottom of the display screen shows countermeasure parts and management indicators. The content displayed on the display screen is basically the same as the display screen of the first embodiment, except that the display table 710 includes the component progress 722 and the expected cash flow improvement value 723. It ’s different. Therefore, items of the component progress 722 and the cash flow improvement expected value 723 will be described below.

  As shown in the figure, the display control unit 17 also displays a check button for accepting a sorting instruction for rearrangement from the user for the component progress (%) 722 and the expected cash flow improvement value 723. Further, when the input receiving unit 11 detects that the check button of the component progress (%) 722 and the expected cash flow improvement value 723 is pressed, the input receiving unit 11 stores the records included in the display table 710 via the display control unit 17. Pull down a sorting list that specifies the sort order.

  For example, when the check button of the component progress (%) 722 is pressed, the display control unit 17 displays a sorting list that specifies the order of the progress (%) in descending order or small order. In addition, the display control unit 17 rearranges and displays the records in the display table 710 according to the selected arrangement order. When the check button of the expected cash flow improvement value 723 is pressed, the display control unit 17 displays a sorting list that specifies the order of increasing or decreasing expected cash flow improvement value. In addition, the display control unit 17 rearranges and displays the records in the display table 710 according to the selected arrangement order.

  With this sort function, the user can prioritize adjustable parts based on the expected value of cash flow improvement that takes into account the feasibility of delivery date adjustment based on part progress and the feasibility of delivery time adjustment. This makes it possible to more efficiently carry out parts delivery adjustment work.

<Third embodiment>
Next, a third embodiment of the present invention will be described. The component ordering apparatus 100 according to the present embodiment calculates a countermeasure deadline that allows adjustment of the delivery date of a component.

  FIG. 22 is a functional block diagram illustrating an example of a functional configuration of the component ordering apparatus 100 according to the present embodiment. The basic configuration of the part ordering apparatus 100 is the same as the functional configuration of the second embodiment, but the arithmetic processing unit 2 has a countermeasure deadline calculation unit 20 and the storage unit 1 is generated by a predetermined process. It differs from the second embodiment in that the countermeasure deadline information 800 is stored. In addition, about the structure same as 2nd embodiment, the same code | symbol is attached | subjected and description is abbreviate | omitted.

  The countermeasure deadline calculating unit 20 is a functional unit that calculates the countermeasure deadline for the delivery date adjustment of parts. Specifically, the countermeasure deadline calculation unit 20 calculates the countermeasure deadline for delivery date adjustment for each part so as not to exceed the upper limit of the production progress level at which the delivery date of the part can be adjusted. Further, the countermeasure deadline calculation unit 20 generates countermeasure deadline information 800 and stores it in the storage unit 1.

  FIG. 23 is a diagram showing an example of countermeasure deadline information 800 stored in the storage unit 1. The countermeasure deadline information 800 is information for managing the deadline of delivery date adjustment for the parts related to each order. Specifically, the countermeasure deadline information 800 includes a record in which an order ID 801, a component ID 802, an upper limit (%) 803 of progress, and a countermeasure deadline 804 are associated with each other.

  The order ID 801 is information for identifying the order of the part specified by the associated part ID. The component ID 802 is information for identifying a component ordered by the order of the associated order ID. The upper limit of progress (%) 803 is information indicating the upper limit of the production progress of parts that cannot be adjusted for delivery. The countermeasure deadline 804 is information indicating a deadline date on which the delivery date of the part can be adjusted. For example, the ordering order of a part identified by the order ID “# 02” and the part ID “P02” is “2014/9” when the upper limit of the degree of progress that can adjust the delivery date is “50 (%)”. / 30 "indicates that it is necessary to take measures to adjust the delivery date.

  FIG. 24 is a flowchart showing the flow of delivery date adjustment processing according to the present embodiment. Prior to the start of the delivery date adjustment process, the input receiving unit 11 outputs an input table for receiving the upper limit value (%) of the production progress of parts together with the input of the date after the change of the production plan via the display control unit 17. 307 to accept input from the user.

  FIG. 25 is a diagram showing an example of a delivery date adjustment instruction screen 400 according to the present embodiment. Although the basic configuration of the delivery date adjustment instruction screen 400 is the same as that of the first embodiment, an input table 411 for receiving an input of the upper limit value (%) of the degree of progress is further displayed. Note that, in the delivery date adjustment instruction screen 400, the same components as those in the delivery date adjustment instruction screen of the first embodiment are denoted by the same reference numerals and description thereof is omitted.

  The user of the parts ordering apparatus 100 inputs an after-change production plan date 404 associated with a product ID 401 having a change in the production plan date and an upper limit value 411 of the degree of progress, respectively, to the input table, and then executes the button. Press 404. When detecting that the execution button 404 is pressed, the input receiving unit 11 starts the delivery date adjustment process. Hereinafter, as shown in FIG. 25, the case where the upper limit value of the degree of progress is accepted as 50 (%) will be described as an example.

  In addition, since the process of step S031-step S037 is the same as that of step S021-step S027 in the delivery date adjustment process of 2nd embodiment, description is abbreviate | omitted.

In the delivery date adjustment process of FIG. 24, when the expected improvement value of cash flow is calculated (step S037), the countermeasure deadline calculation unit 20 calculates the countermeasure deadline (step S038). Specifically, the countermeasure deadline calculation unit 20 identifies the delivery date D _{i of} each part identified by the order ID of the record in which “possible” is stored in the countermeasure part instruction information 250 as “possibility of countermeasure” from the order information 220. . Further, the countermeasure deadline calculation unit 20 specifies the procurement lead time LT _i of the part for which the delivery date D _i is specified from the part information 210. Then, parts progress degree calculation unit 20, based on the P _max is the upper limit of progression of the input of which is accepted from the user, and delivery D _i of each component, and the procurement lead time LT _i of each part, by the following equation (3), to calculate the measures expiration date X _i of ordering the order of each component.

In the above formula (3), when even if i.e. the production of the upper limit P _{max = 1} production progress of parts _(100%) is complete capable delivery adjustment measures time limit set for delivery D _i and day Is done. Further, the production progress of the component upper P _{max = 0} If If That part of production _(0%) can not be simultaneously delivery adjustment to that undertaken is procurement lead time LT orders order i from delivery D _{i The} countermeasure deadline is set on the date after subtracting _i . For example, the order information 220 of FIG. 4, order ID "# 02", the case of calculating the measure time limit targeting component ID "P02", delivery _{D i} of the part is "2014/10/15", FIG. 3, the procurement lead time LT _{i of the part} is “30 (days)”. Moreover, since the upper limit P _max of progress is “0.5 (50%)”, the countermeasure deadline X _{i of the part} is “2014/9/30” obtained by subtracting 15 days from 2014/10/15. Calculated. In this way, the countermeasure deadline calculation unit calculates the countermeasure deadline for all the parts for which “possible” is stored as the countermeasure availability in the countermeasure part instruction information 250. It should be noted that the reason for not calculating the countermeasure deadline for the ordering order of the part in which “possible (completed)” is stored in the countermeasure part instruction information 250 is because the part is not ordered from the supplier. This is because production is not progressing and there is no need to request a countermeasure deadline. In addition, since it is not possible to adjust the delivery date of a part in which “impossible” is stored in the propriety of countermeasures, it is meaningless to request a countermeasure deadline.

  When the countermeasure deadline calculation unit 20 calculates the countermeasure deadline for each target part, the countermeasure deadline calculation unit 20 generates countermeasure deadline information 800 that associates the order ID of the part, the upper limit of progress (%), and the calculated countermeasure deadline. And stored in the storage unit 1.

  Next, the display control unit 17 outputs the countermeasure component and the management index (step S039). Specifically, the display control unit 17 generates screen information including predetermined items of the countermeasure component instruction information 250 and the management index evaluation information 260 and a graph indicating the accumulated payment amount by date before and after the implementation of the countermeasure for delivery date adjustment, The information is displayed on the output device 307.

  FIG. 26 is a diagram showing an example of a display screen 900 on which countermeasure parts and management indicators are displayed. A graph 901 shown at the top of the display screen 900 shows the cumulative payment amount by date before and after the implementation of the measure for delivery date adjustment. A display table 910 at the bottom of the display screen 900 shows countermeasure parts and management indicators. The contents displayed on the display screen 900 are basically the same as those of the display screen of the second embodiment, but differ in that the countermeasure table is included in the display table 910. Therefore, in the following, the countermeasure deadline item will be described.

  As shown in the figure, the display control unit 17 also displays a check button for accepting a sorting instruction for sorting from the user for the countermeasure deadline. In addition, when the input receiving unit 11 detects that the check button of the countermeasure deadline 924 is pressed, the input receiving unit 11 pulls down a sorting list that specifies the arrangement order of the records included in the display table 910 via the display control unit 17. .

  For example, when the check button for the countermeasure deadline is pressed, the display control unit 17 displays a sorting list that specifies a date order that is close to the current time (the time when the processing is performed) or a date order that is far from the current time. In addition, the display control unit 17 rearranges and displays the records in the display table 910 according to the selected arrangement order.

  Further, the display control unit 17 specifies the date of the countermeasure deadline using the countermeasure deadline information 800 and calculates the number of countermeasure deadline orders for each date. Then, the display control unit 17 displays a mark 903 indicating that it is a countermeasure deadline date and a countermeasure deadline order number 904 on a graph 901 that indicates the accumulated payment amount by date.

  With such a rearrangement function, the user can prioritize adjustable parts in the order of close countermeasure deadlines, and can more efficiently carry out parts delivery adjustment work. Further, since the date of the countermeasure deadline and the number of countermeasure deadline orders are displayed on the display screen, the user can easily grasp when and how many order orders need to be adjusted.

  The functional blocks of the parts ordering apparatus 100 are classified according to the main processing contents in order to facilitate understanding of the functions of the parts ordering apparatus 100 realized in the present embodiment. The present invention is not limited by the way or the name. Further, each component of the part ordering apparatus 100 can be classified into more components according to the processing content. Moreover, it can also classify | categorize so that one component may perform more processes.

  The present invention is not limited to the above-described embodiments, and includes various modifications. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.

  In the above description, control lines and information lines indicate what is considered necessary for the description, and not all control lines and information lines on the product are necessarily shown. In practice, it can be considered that almost all the components are connected to each other.

100: parts ordering device, 1 ... storage unit, 2 ... arithmetic processing unit,
11 ... input receiving unit, 12 ... production plan change judging unit,
13 ... change target component extraction unit, 14 ... adjustable component identification unit,
15 ... delivery date calculation unit, 16 ... management index evaluation unit, 17 ... display control unit 200 ... production plan information, 210 ... parts information, 220 ... ordering information,
230 ... Order status information, 240 ... Contract condition information, 250 ... Countermeasure component instruction information, 260 ... Management index evaluation information

Claims (9)

A storage unit storing order status information including information related to the order status of parts, and contract condition information including information related to a contract with a supplier including payment conditions for purchase of parts;
An input reception unit for receiving an input of a production plan date after a change different from the original production plan date of the product;
Specify the order status of parts used for products whose production plan date has been changed and the contract conditions with the supplier, respectively, from the order status information and the contract condition information,
An adjustable part identifying unit that identifies a part whose order status is waiting to be ordered and a part when the supplier is not subject to the subcontracting law even if the order status is already ordered, as a part capable of adjusting delivery date; A part ordering apparatus characterized by comprising: The part ordering apparatus according to claim 1,
A parts ordering apparatus, further comprising: a delivery date calculation unit that calculates a delivery date after adjustment of a delivery-adjustable part specified by the adjustable part identification unit based on the production schedule date after the change. The parts ordering device according to claim 2,
The storage unit
Stores parts information including information on parts procurement lead time,
The delivery date calculation unit
A part that calculates an order reservation date for a part after delivery date adjustment by subtracting the procurement lead time of the part from the delivery date after adjustment for a preset order reservation date for a part awaiting ordering Ordering equipment. The parts ordering apparatus according to claim 3, wherein
The parts information further includes the order price of the parts,
The storage unit
Further storing ordering information including information on the order quantity of the part and the delivery date before adjustment;
Using the delivery date before the adjustment of the part, the delivery date after the adjustment, and the closing date, payment date and payment date of the part included in the contract condition information, the payment date and payment date before and after the adjustment Calculate the change period,
Calculate the order amount from the order price and order quantity of the parts,
A component ordering apparatus, further comprising a management index evaluation unit that calculates a cash flow influence degree indicating a management index by integrating the payment date change period and the order amount. The parts ordering device according to claim 4,
A part ordering apparatus, further comprising: a part progress degree calculating unit that calculates a progress degree of part production using a period from a current time to a delivery date of a part before adjustment and the procurement lead time of the part. The parts ordering device according to claim 5,
A component ordering apparatus, further comprising: an expected improvement value calculation unit that calculates an expected improvement value of cash flow by integrating the cash flow influence level and the progress level of the part production. The parts ordering device according to claim 6,
It further includes a countermeasure deadline calculation unit that calculates a countermeasure deadline that allows the delivery of parts to be adjusted,
The input receiving unit receives an input of a value of the upper limit of the degree of progress of parts production,
The countermeasure deadline calculation unit
A part ordering apparatus that calculates a deadline for adjusting a delivery date of a part using the delivery date of the part before the adjustment, the procurement lead time of the part, and the value of the upper limit of progress. The parts ordering device according to claim 7,
Using the information regarding the payment date before and after the adjustment and the order amount, a graph showing the accumulated payment amount by date before and after the implementation of measures for adjusting the delivery date of parts,
Generating a display table including at least one of the cash flow influence degree, the component progress degree, the cash flow improvement expected value, and the countermeasure deadline;
A component ordering apparatus, further comprising: a display control unit configured to display the generated graph and the display table on a display device. A program for causing a computer to function as a parts ordering device,
The computer,
A storage unit storing order status information including information related to the order status of parts, and contract condition information including information related to a contract with a supplier including payment conditions for purchase of parts;
An input reception unit for receiving an input of a production plan date after a change different from the original production plan date of the product;
Specify the order status of parts used for products whose production plan date has been changed and the contract conditions with the supplier, respectively, from the order status information and the contract condition information,
Functions as an adjustable part identifying unit that identifies parts whose order status is awaiting order and parts whose order status is already ordered even if the supplier is not subject to subcontracting as a part whose delivery date can be adjusted A program characterized by letting

Images