JP2006065852A - System, method and program for parts management, and recording medium with the program recorded thereon - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system, method and program for parts management, and a computer-readable recording medium with the program recorded thereon, which can grasp progress from parts order to parts delivery, manage a procurement state of raw materials at parts manufacturers, production progress and a running location, estimate parts delivery, detect bottleneck in parts supply earlier and determine a speedy and suitable process for the bottleneck. <P>SOLUTION: A parts ordering section 1 executes a parts ordering step for placing an order to a part manufacturer 30 for a part necessary for production. A part delivery management section 2 executes a part delivery management step having the steps of tracking a process up to delivery of the part to grasp progress of the delivery, estimating a delivery time of the ordered part, and predicting the bottleneck of part supply based on the estimated delivery time and a production plan. When occurrence of the bottleneck of part supply is predicted, a corresponding support information providing section 3 executes a corresponding support information providing step for providing the corresponding support information. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to parts management, manages the delivery status of parts, predicts the delivery time of parts that have not yet been delivered, and comprehensively includes the cost aspect for handling when a parts bottleneck occurs. The present invention relates to a component management system to be determined, a component management method, a component management program, and a recording medium storing the component management program.

  As an example of a conventional parts management system, a system for checking the assortment of parts in the following manner has been proposed (for example, see Patent Document 1).

  That is, first, parts are ordered based on the production plan, the parts configuration table, and the parts inventory. Regarding the delivery of parts, the scheduled delivery date and the planned number of deliveries are stored in the delivery forecast master. The scheduled delivery date is set several days before the scheduled production date. When the parts are actually delivered and the parts are verified, the parts delivery results are recorded. The production plan and the parts delivery results are collated, the number of parts shortage required for production is determined, and if there is a shortage, the part is highlighted and the part bottleneck can be easily confirmed. Since the parts delivery schedule date is set a few days before the production schedule dates, the availability of production can be immediately determined from the confirmation of the parts pipeline by checking the parts delivery schedule. In addition, for undelivered parts, a delivery reminder is sent to the supplier. In addition, by confirming the part bottleneck by going back to the date before the scheduled part delivery date, it is possible to know that the number of parts is insufficient due to omission of part ordering, so it is possible to order additional parts or adjust the order quantity.

In addition, as an example of a conventional parts management method and parts management apparatus, a means for storing in advance the tact time of the previous process and the time required for the transportation time from the previous process to the subsequent process is used. There is also a thing to carry (for example, refer to patent documents 2).
Japanese Patent Laid-Open No. 2002-312022 (pages 5-6, FIGS. 1 and 2) Japanese Patent Application Laid-Open No. 2002-169606

  However, according to the above prior art, there may be no part bottleneck before the scheduled delivery date, but the ordered part may not be delivered even when the scheduled delivery date is reached. This tendency is observed for parts having a long time, that is, a period from when a part is ordered to when it is delivered. For example, parts with a long L / T include parts imported from overseas and parts with a long manufacturing period such as semiconductors. If a parts bottleneck occurs, the production manager wants to know whether it is possible to respond by simply prompting delivery, or when the parts bottleneck can be resolved and production is possible, but this point cannot be understood There was a problem.

  Also, if a parts bottleneck occurs, it is doubtful if the problem can be solved by simply calling for parts. For example, if the parts manufacturer is urged to make the delivery date earlier, if the urged part is in production, it is necessary to carry out production by express treatment in order to speed up the delivery date, which may generally increase the production cost. . In addition, imported parts from overseas usually use low-cost shipping services, but shipping costs increase if air transportation is used to speed up delivery. Comprehensive judgment is necessary, including costs related to such production or transportation, but the conventional parts management method and parts management apparatus could not provide information for comprehensive judgment. There was a problem.

  The present invention has been made in view of such circumstances, and its purpose is to grasp the progress from part ordering to part delivery, the raw material procurement status of a part manufacturer, the management of production progress and the travel location, Provides a parts management system, parts management method, parts management program, and a storage medium that stores parts management programs that can be used to predict delivery, early detection of parts bottlenecks, and speedy and accurate processing decisions regarding parts bottlenecks There is to do.

  The present invention was devised to solve the above problems, and the component management system according to the present invention, as shown in FIG. 1, is a component ordering unit that orders parts necessary for production based on a production plan from a component manufacturer 30. 1 and the parts ordering department 1 procure raw materials, production and shipment at the parts maker 30, transport parts from the parts maker 30 to the delivery destination (factory 10), and deliver the parts to the delivery destination (factory 10). Track each series of processes from order placement to delivery of parts, grasp delivery progress, predict delivery time of ordered parts, and forecast part bottleneck from predicted delivery date and production plan The parts delivery management unit 2 and the handling support information providing unit 3 that provides handling support information for eliminating the parts bottleneck when the parts delivery management unit 2 predicts the occurrence of the parts bottleneck. Than it is.

  In such a parts management system, according to the present invention, as shown in FIG. 1, the parts ordering unit 1 includes a production plan storage unit (production plan DB) 11 for storing the number of production plans for each model day, and the model type. A component configuration storage unit (component configuration DB) 12 that stores the component parts, a component inventory storage unit (component inventory DB) 13 that stores component inventory, and a supplier storage unit (customer master) that stores the component manufacturer 30 14, a procurement lead time storage unit (procurement L / T master) 15 that stores procurement lead times, a procurement cost storage unit (procurement cost master) 16 that stores procurement costs, and models stored in the production plan DB 11 A part requirement calculation unit 17 that calculates a component requirement from the number of production plans for different days and the model-specific component stored in the component configuration DB 12, and a component requirement calculation unit 17 The net component requirement calculation unit 19 that calculates the net component requirement from the component requirement and the component inventory stored in the component inventory DB 13, and the net component requirement calculated by the net component requirement calculation unit 19 Net component requirement storage unit (net component requirement DB) 20 to be stored, net component requirement stored in net component requirement DB 20, component manufacturer 30 stored in supplier master 14, procurement L / T A part ordering information generation unit 21 that generates part ordering information from the procurement lead time stored in the master 15 and the procurement cost stored in the procurement cost master 16, and the part ordering information generated by the part ordering information generation unit 21 And an ordering part storage unit (ordering part DB) 22 for storing. By configuring the component ordering unit 1 with such a configuration, component ordering information can be created for each component while taking into account inventory, procurement status, procurement cost, and the like.

  In the parts management system as described above, in the present invention, as shown in FIG. 1, the parts delivery management section 2 receives an order information storage section (order information DB) 31 for storing information received by the parts manufacturer 30, and the parts. A product inventory storage unit (product inventory DB) 32 that stores the inventory of products held by the manufacturer 30, a raw material configuration storage unit (raw material configuration DB) 33 that stores information on raw materials constituting the product, and an order information DB 31 The product requirement calculation unit 34 for calculating the raw material requirement from the order information stored in the product inventory DB 32, the product inventory stored in the product inventory DB 32, and the raw material information stored in the raw material configuration DB 33, and the product requirement calculation unit And a raw material procurement information collecting unit 35 that orders raw materials from the raw material manufacturer 60 based on the raw material requirement calculated by 34. . By configuring the parts delivery management unit 2 in such a configuration, a parts manufacturer can place an order for raw materials from a raw material manufacturer while taking into account the inventory of the products and the required amount of raw materials constituting the products.

  In addition, the parts delivery management unit 2 collects raw material delivery information from the raw material maker 60 to the parts maker 30, and the raw material maker 60 obtained by the raw material procuring information collection unit 35 sends the parts maker 30. Collected by a procurement record storage unit (procurement result DB) 36 for storing raw material procurement results, a production record collection unit 37 for collecting production results of each production process in the parts manufacturer 30, and a production record collection unit 37 A production record storage unit (production record DB) 38 for storing production results, a shipment information collection unit 39 for collecting shipment information from the parts manufacturer 30, and a shipment record for storing shipment information collected by the shipment information collection unit 39 A storage unit (shipment result DB) 40 and a travel position collection unit that collects travel positions of transportation means when parts are transported from the parts manufacturer 30 to a delivery destination (here A GPS (Global Positioning System) receiver 70) mounted on a truck for transporting goods, a travel position storage unit (travel position DB) 41 for storing the travel position of the transportation means collected by the travel position collection unit, It has a parts acceptance section 45 that performs parts acceptance processing at the delivery destination and collects parts delivery results, and a parts delivery results storage section (parts delivery results DB) 46 that stores delivered parts collected by the parts acceptance section 45 It may be a thing. By configuring the parts delivery management unit 2 with such a configuration, it is possible to manage the production progress in the parts manufacturer and the travel location during parts transportation.

  Furthermore, as shown in FIG. 1, the parts delivery management unit 2 has a procurement record stored in the procurement record DB 36, a production record stored in the production record DB 38, a shipment record stored in the shipment record DB 40, Travel location stored in the travel location DB 41, location stored in the location master storage unit (location master) 42, travel route stored in the travel route master storage unit (travel route master) 43, process order master storage A part delivery date / time prediction unit 47 that predicts the delivery date / time of a part from the process order stored in the part (process order master) 44 and the procurement L / T stored in the procurement L / T master 15; A part delivery prediction storage unit (part delivery prediction DB) 48 that stores the delivery date and time of parts predicted by the unit 47 may be provided. By configuring the parts delivery management unit 2 as described above, the parts delivery time can be predicted.

  Furthermore, the parts delivery management unit 2 performs the parts delivery forecast date and time stored in the parts delivery forecast DB 48, the parts delivery results stored in the parts delivery results DB 46, and the model-specific dates stored in the production plan DB 11. The part bottleneck determination unit 49 for determining the part bottleneck from the part number of the production plan, the component-specific component stored in the part configuration DB 12, the part inventory stored in the part inventory DB 13, and the part bottleneck determination unit 49 It may also include a component bottleneck storage unit (component bottleneck DB) 50 that stores the component bottleneck. By configuring the parts delivery management unit 2 with such a configuration, the degree of parts bottleneck can be quantitatively predicted.

  In the component management system as described above, in the present invention, the response support information providing unit 3 stores an action master storage unit (action master) 51 that stores possible actions depending on the difference between the delivery date and the production date of the component, Actions stored in master 51, parts bottleneck stored in parts bottle DB 50, parts manufacturer 30 stored in transaction master 14, procurement lead time stored in procurement L / T master 15, and procurement cost master 16 may include an action information providing unit 52 that presents an action for eliminating a part bottleneck from the procurement cost stored in FIG. By configuring the response support information providing unit 3 in such a configuration, the degree of parts bottleneck can be predicted quantitatively, so it is necessary to change the production plan, whether it is a range that requires parts prompting, additional charges, or It is possible to obtain information that can be used as a judgment material for taking action, such as whether or not. Its cost, speedy and accurate decision making are possible.

  In the parts management system as described above, according to the present invention, the parts ordering unit 1 and parts delivery management unit 2 provided on the part ordering side and the raw material manufacturer 60 on the part ordering side are provided. Devices that constitute another part of the provided part delivery management unit may be connected to each other via a communication line. In this case, information exchange between the part ordering side and the part manufacturing side can be easily performed.

  In addition, the parts management method using the parts management system described above is a part ordering step in which parts necessary for production are ordered from the parts manufacturer 30 based on the production plan via the Internet 23, and parts are ordered in the part ordering step. The process of tracking the process from when the parts are delivered to grasping the delivery progress, the step of predicting the delivery time of the ordered parts, and the step of predicting the part bottleneck from the predicted delivery time and production plan The part delivery management step implemented in the parts delivery management unit 2 and the correspondence support information providing unit for providing support support information for eliminating the part bottleneck when the occurrence of the part bottleneck is predicted in the part delivery management step 3 and a support support information providing step provided from 3 (see FIG. 1).

  In the parts management method as described above, according to the present invention, the parts ordering step includes a production plan storage step for storing the production plan number for each model in the production plan DB 11, and a model-specific component in the part configuration DB 12. A component configuration storage step, a component inventory storage step for storing the component inventory in the component inventory DB 13, a supplier storage step for storing the component manufacturer 30 in the supplier master 14, and a procurement lead time in the procurement L / T master 15. The procurement lead time storage step to be stored, the procurement cost storage step to store the procurement cost in 16 in the procurement cost master, and the model stored in the production plan number and parts configuration storage step by type stored in the production plan storage step The component requirement is calculated by the component requirement calculator 17 from another component. The net component requirement calculation unit 19 calculates the net component requirement from the component requirement calculation step to be issued, the component requirement calculated in the component requirement calculation step and the component inventory stored in the component inventory storage step. The component requirement calculation step, the net component requirement storage step for storing the net component requirement calculated in the net component requirement calculation step in the net component requirement DB 20, and the net stored in the net component requirement storage step. The part ordering information generating unit 21 generates part ordering information from the part requirement, the part manufacturer 30 stored in the supplier storing step, the procurement lead time stored in the procurement leadtime storing step, and the procurement cost stored in the procurement cost storing step. Parts ordering information generation step and The part ordering information part order information generated in the generation step may be one and a step of storing the order part DB 22 (see FIG. 1).

  In the component management method as described above, in the present invention, the component delivery management step includes an order information storage step for storing information received by the component manufacturer 30 in the order information DB 31, and an inventory of products held by the component manufacturer 30. The product inventory storage step to be stored in the product inventory DB 32, the raw material configuration storage step to store the information on the raw materials constituting the product in the raw material configuration DB 33, the order information stored in the order information storage step, and the product inventory storage step Based on the raw material information calculated in the raw material requirement calculation step, the raw material requirement calculation step 34 calculates the raw material requirement amount from the raw material information stored in the product inventory and raw material composition storage step. From the raw material procurement information collection unit 35 Charges may be one and a step of ordering the raw materials to the manufacturer 60 (see FIG. 1).

  In addition, the parts delivery management step includes a raw material procurement information collecting step for collecting raw material delivery results from the raw material manufacturer to the parts manufacturer 30 in the raw material procurement information collecting unit 35, and a raw material manufacturer obtained in the raw material procurement information collecting step. A procurement record storage step for storing the raw material procurement record from 60 to the parts manufacturer 30 in the procurement record DB 36, a production record collection step for collecting the production record of each production process in the component manufacturer 30 in the production record collection unit 37, and A production record storing step for storing the production record collected in the production record collecting step in the production record DB 38, a shipment information collecting step for collecting shipment information from the part manufacturer 30 in the shipment information collecting unit 39, and the shipment information collecting step. The shipping information collected in the Collected in the traveling position collecting step, the traveling position collecting step for collecting the traveling position of the transportation step when the parts are conveyed from the parts manufacturer 30 to the delivery destination using the GPS receiver 70, and the traveling position collecting step. In the travel position storage step for storing the travel position of the transport step in the travel position DB 41, the parts acceptance unit 45 performs part acceptance processing at the delivery destination and collects the parts delivery results, and the parts acceptance step. It may have a part delivery result storage step for storing the collected delivered parts in the part delivery result DB 46 (see FIG. 1).

  Furthermore, the parts delivery management step includes the procurement record stored in the procurement record storage step, the production record stored in the production record storage step, the shipment record stored in the shipment record storage step, the travel position stored in the travel position storage step, Parts delivery date / time prediction unit based on location stored in location master storage step, travel route stored in travel route master storage step, process order stored in process order master storage step, and procurement lead time stored in procurement lead time master storage step 47, a part delivery date / time prediction step for predicting the delivery date / time of the part, and a part delivery prediction storage step for storing the delivery date / time of the part predicted in the part delivery date / time prediction step in the part delivery prediction DB 48. Good (see FIG. 1).

  Furthermore, the parts delivery management step includes the parts delivery forecast date and time stored in the parts delivery forecast storage step, the parts delivery results stored in the parts delivery results storage step, and the production plans for each model type stored in the production plan storage step. A part bottleneck judging step for judging a part bottleneck in the part bottleneck judging unit 49 based on the number of components, the model-specific component parts stored in the part constitution storing step, and the part stock memorized in the part inventory storing step, A component bottle path storage step for storing the component bottle path in the component bottle DB 50 (see FIG. 1).

  In the parts management system as described above, in the present invention, the action support information providing step stores an action possible in the action master 51 based on a difference between a delivery date and a production date of the parts, and the action In the action memorized in the master memory step, the part memorized in the part memorized memory step, the action memorized in the action master memorized step, the part manufacturer 30 memorized in the transaction master memorized step, and the procurement lead time master memorized step Based on the stored procurement lead time and the procurement cost stored in the procurement cost master storage step, the response support information providing unit 52 presents an action for eliminating the part bottleneck in the response support information providing unit 52. May be those having a flop (see Fig. 1).

  The computer-readable recording medium of the present invention stores a component management program used in the component management system described above or a component management program for realizing the component management method described above.

  According to the present invention, until now, until the parts are delivered, it is almost impossible to grasp the parts bottleneck, and there is no choice but to prompt parts delivery after the parts bottleneck actually occurs. It is possible to grasp the progress until parts are delivered. In addition, it becomes possible to predict when a part will be delivered at any stage from when the part is ordered to when the part is delivered, so that a part bottleneck can be discovered early.

  In addition, for each component part, it is possible to create part ordering information while taking into account inventory, procurement status, procurement cost, and the like.

  In addition, parts manufacturers can order raw materials from raw materials manufacturers while taking into account the inventory of products and the amount of raw materials that make up products, and can also manage production progress and transportation locations during parts transportation It becomes.

  In addition, since the parts delivery time and the degree of parts bottleneck can be predicted quantitatively, actions such as whether parts are required to be promoted, additional charges will be generated, or production plans need to be changed, etc. It is possible to obtain information that can be used as a judgment material. As a result, speedy and accurate decision making is possible.

  Embodiments of the present invention will be described below with reference to the drawings.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is an explanatory diagram showing a first embodiment of the component management system of the present invention.

  As shown in FIG. 1, the present invention is roughly divided into a part ordering unit 1, a part delivery management unit 2, and a response support information providing unit 3. The part ordering unit 1, a part of the part delivery management unit and a response support information providing unit 3 is installed in the factory 10, and another part of the parts delivery management section is installed in the parts manufacturer 30.

First, the configuration of the part ordering unit 1 will be described with reference to FIGS.
As shown in FIG. 1, the parts ordering unit 1 includes a production plan DB 11, a parts configuration DB 12, a parts inventory DB 13, a supplier master 14, a procurement L / T master 15, a procurement cost master 16, and parts requirements. The quantity calculation unit 17, the component requirement DB 18, the net component requirement calculation unit 19, the net component requirement DB 20, the component order information generation unit 21, and the order component DB 22 are configured.

  In the production plan DB 11, a production plan created by a production plan planning system (not shown) is stored as the number of production plans for each model day as shown in FIG. That is, FIG. 2 includes “model name”, “production date”, and “production planned number” of each model.

  In the component configuration DB 12 shown in FIG. 1, as shown in FIG. 3, the component codes of the components constituting each model and the number of the components are stored in advance. That is, FIG. 3 includes “model name” of each model and “part code” and “number” of parts constituting each model.

  In the parts inventory DB 13 shown in FIG. 1, parts inventory existing in the factory is stored in the form as shown in FIG. 4 by the parts inventory management system. That is, FIG. 4 includes “part code” and “stock quantity” of each part.

  As shown in FIG. 5, the supplier master 14 shown in FIG. 1 stores in advance a “customer code” and a “part manufacturer name” indicated by the supplier code. The name can be searched.

In the procurement L / T master 15 shown in FIG. 1, the supplier code of the part manufacturer 30 that can procure parts and the L / T ( (Hereinafter referred to as “part procurement L / T”), so that “part code”, “partner code”, “raw material procurement L / T”, “processing L / T”, “conveyance L” of each part can be searched. / T "," margin L / T "," processing handling "and" conveying handling "are stored in advance.

  As will be described in detail later, since the present invention also aims to manage the process from ordering parts to delivery, the parts procurement L / T is classified and stored for each process as follows.

Procurement L / T = Raw material procurement L / T + Processing L / T + Transport L / T + Margin L / T Expression (1)
Here, “raw material procurement L / T” indicates “time required for raw material procurement”, and “processing L / T” indicates “time required for processing the raw material and completing the manufacture of the part”. , “Transport L / T” indicates “time required to transport the part to the factory”, “Margin L / T” is “To allow parts acceptance inspection from the completion of parts delivery to the start of production” Or time that can be recovered even if there is a slight delay in delivery due to accidents or production delays.

  The procurement cost master 16 shown in FIG. 1 includes a part manufacturer 30 that can procure parts by using a part code as a key as shown in FIG. 7 and a cost required for procurement by the part manufacturer 30 (hereinafter referred to as “part procurement cost”). ) “Part code”, “partner code”, “raw material procurement cost”, “processing cost”, “conveying cost”, “processing handling” and “conveying handling” for each part Stored in advance.

  Parts procurement costs are also classified and stored by process as described below.

Procurement cost = Raw material procurement cost + Processing cost + Conveyance cost ... Formula (2)
Here, “Raw Material Procurement Cost” indicates “expense required for procurement of raw materials”, and “Processing Cost” indicates “expense required for processing of raw materials to complete the manufacture of parts” and “Transportation” “Cost” indicates “cost required to transport the part to the factory”.

  Next, in the component management method of the present invention, processing performed in the component ordering unit 1 before ordering a component will be described with reference to the drawings.

  FIG. 8 is a flowchart showing a process performed until a part is ordered in the first embodiment of the parts management method of the present invention. In the figure, a solid line arrow indicates the flow of processing, and a broken line arrow indicates the timing of transmission / reception of information in each storage unit.

  First, in step S11, the part requirement calculation unit 17 searches the part code and the number of parts by referring to the information stored in the part configuration DB 2 using the model name stored in the production plan DB 1 as a key. Then, by multiplying the number of parts by the production plan number of the parts stored in the production plan DB 1, the quantity of parts necessary for each model day is calculated. Hereinafter, the “quantity of parts necessary for each model day” is referred to as “part requirement”, and this component requirement is stored in the component requirement storage unit (part requirement DB) 18 as shown in FIG. Remembered. That is, FIG. 9 includes “model name” of each model and “part code”, “production date”, and “required quantity” of parts constituting each model.

  In addition, when a necessary part already exists in the factory as a part inventory, the part can be used for production, and must be removed from the parts to be ordered. In other words, the parts to be ordered are parts whose parts inventory is subtracted from the parts requirement, and this is called the net parts requirement.

  In step S12, the net component requirement calculation unit 19 calculates the net component requirement by subtracting the number of parts inventory stored in the component inventory DB 13 from the component requirement stored in the component requirement DB 18. The net component requirement amount is stored in the net component requirement DB 20 in the form as shown in FIG. That is, FIG. 10 includes “model name” of each model and “part code”, “production date”, and “necessary quantity” of the parts constituting each model.

  In step S <b> 13, the part order information generation unit 21 stores the net part requirement stored in the net part requirement DB 20 and the supplier master 14, the procurement L / T master 15, and the procurement cost master 16. A table 81 as shown in FIG. 11 is created using the information, and the created table 81 is displayed on a screen 80 of a display device (not shown) connected to the component management system. The user (parts in charge of parts purchase) determines an order for the parts while referring to the table 81 on the screen 80.

  In the table 81 shown in FIG. 11, the part code, production date, and required quantity stored in the part requirement DB 20 are displayed. That is, the supplier code is retrieved from the procurement L / T master 15 using the component code stored in the net component requirement DB 20 as a key. If the supplier code (part manufacturer name) is uniquely determined, the procurement L / T is searched using the supplier code and the part code as a key, and the delivery date of the part is calculated from the production date and the procurement L / T. Then, a table 81 as shown in FIG. 11 is created.

  Further, the procurement cost master 16 can be used to search the procurement cost using the part code and the supplier code as search keys, and the table 81 can be created.

  As a result of the search, when there are a plurality of supplier codes, as shown in FIG. 12, a table 82 showing the suppliers stored in the supplier master 14 and the procurement L / T master 15 in the screen 80 is shown. It is necessary to display a list on the screen and select a business partner. Here, “Procurement L / T” as information for selecting a parts manufacturer and “Procurement cost” stored in the procurement cost master 16 are also displayed separately for “partner code” and “part manufacturer name”. ing. Then, when the user (parts in charge of parts purchase) selects a line in which a desired part manufacturer name is displayed and clicks an OK button 82 to select a part manufacturer, the supplier code and the part code are used as search keys. The raw material procurement L / T, processing L / T, conveyance L / T and margin L / T are searched, and further, the procurement L / T is calculated using the equation (1), and the production stored in the production plan DB 11 The delivery date of the part is calculated from the date and the calculated procurement L / T, and a table 81 is created and displayed on the screen 80.

  Next, when the user (parts in charge of parts purchase) selects the row in which the parts to be ordered and the parts manufacturer are displayed from the screen and clicks the order button 83, the order number is assigned, and the order number, part code, The parts manufacturer name, delivery date, and delivery quantity are stored in the order parts DB 22, and the “Status” column of the selected row is displayed as “Ordered” in the table 81 of the screen 80 so that the order status can be confirmed. Become. Here, the order number is a number uniquely added to the order unit for order management, and in this example, a serial number is used.

  In this way, the parts ordering unit 1 determines to which part manufacturer the parts are ordered and when they are delivered, and stores the created table 81 in the ordered parts DB 22 as parts ordering information.

  The part ordering information stored in the ordering part DB 22 shown in FIG. 1 is immediately transmitted from the part ordering unit 1 of the factory 10 to the part manufacturer 30 via the Internet 23. At this time, the part ordering information of the factory 10 is immediately received order information for the parts manufacturer 30.

  Next, the parts delivery management unit 2 shown in FIG. 1 will be described with reference to the drawings.

  The parts delivery management unit 2 is provided for the purpose of tracing a series of processes from when the parts maker 30 receives an order to delivering the parts and predicting the occurrence of a parts bottleneck.

  That is, the parts delivery management unit 2 collects the following information and stores the collected information in order to track a series of processes from when the parts maker 30 receives an order until the parts are delivered. It has. Here, the parts delivery management unit 2 is provided in the factory 10 which is part of the ordering equipment, and is provided in the parts manufacturer 30 which is the ordering side. 23 to each other.

  That is, an order information DB 31 that stores information on received orders and a product inventory DB 32 that stores inventory of products held by the part manufacturer 30 (hereinafter referred to as “product inventory”), which constitutes the parts delivery management unit 2; A raw material composition DB 33 for storing information on raw materials constituting the product, a product requirement calculation unit 34 for calculating a raw material requirement based on information stored in the order information DB 31, the product inventory DB 32, and the raw material composition DB 33; A raw material procurement information collecting unit 35 that collects raw material orders from the raw material manufacturer 60 and delivery results of raw materials from the raw material manufacturer 60 to the parts manufacturer 30 based on the raw material requirements calculated by the product requirement calculating unit 34, and raw material procurement Procurement record storing raw material procurement record from raw material maker 60 to parts maker 30 obtained by information collecting unit 35 B36, a production result collecting unit 37 that collects production results of each production process in the part manufacturer 30, a production result DB 38 that stores the production results collected by the production result collecting unit 37, and shipping information from the part manufacturer 30 The parts manufacturer 30 is provided with a shipment information collection unit 39 for collecting the shipment information and a shipment result DB 40 for storing the shipment information collected by the shipment information collection unit 39.

  Further, the travel position of a truck, a ship, a train, an airplane, etc. (hereinafter referred to as “transportation means”) that is used by the parts delivery management unit 2 to be delivered from the parts manufacturer 30 to the factory 10 after shipment is stored. Travel location DB 41, location master 42 pre-stored with information on locations important for tracking the location of parts, such as factories, parts manufacturer locations, interchanges, harbors and airports, and stored in the location master 42 A travel route master 43 that pre-stores a transport route from the parts manufacturer 30 to the factory 10 based on the information, and a process order master 44 that pre-stores the order of the processes necessary to produce the parts. 10 is provided.

  Furthermore, in the parts delivery management unit 2, a parts acceptance unit 45 that collects the delivery results of delivered parts by performing part acceptance processing at the same time that the ordered parts are delivered to the factory, and parts that are accepted by the parts acceptance part 45 The parts delivery record DB 46, the parts procurement record DB 36, the production record DB 38, the shipment record DB 40, the travel position DB 41, the location master 42, the travel route master 43, the process order master 44, and the procurement L / T master 15 are stored. A parts delivery date / time prediction unit 47 that predicts the delivery date / time of the parts based on the stored information, a parts delivery prediction DB 48 that stores the delivery date / time of the parts predicted by the part delivery date / time prediction unit 47, A part bottleneck judging unit 49 for judging a part bottleneck based on information stored in the parts delivery result DB 46 is provided in the factory 10. It has been.

  Next, in the parts management method of the present invention, processing performed in the parts delivery management unit 2 from when the parts maker 30 receives an order until the parts are delivered will be described with reference to the drawings.

  FIG. 14 is a flowchart showing processing executed in the first embodiment of the component management method according to the present invention from when a component manufacturer receives an order to when a component is delivered. In the figure, a solid line arrow indicates the flow of processing, and a broken line arrow indicates the timing of transmission / reception of information in each storage unit.

  In step S21, the product requirement calculation unit 34 relates to the order information stored in the order information DB 31 as shown in FIG. 15 and the product inventory stored in the product inventory DB 32 as shown in FIG. From the information, the quantity of the product that needs to be manufactured, that is, the product requirement is calculated. If the product inventory is sufficient, the process proceeds to step S25, and if the product inventory is insufficient, the process proceeds to step S22.

  As shown in FIG. 15, the order information stored in the order information DB 31 includes “order number”, “order date”, “model name”, and “model name” assigned to each part when the parts are ordered at the factory 10. It consists of “part code”, “customer code”, “delivery date”, and “delivery quantity”.

  As shown in FIG. 16, the product inventory information stored in the product inventory DB 32 is composed of “part code” and “stock quantity”.

  In step S22, the raw material procurement information collecting unit 35 places an order from the raw material manufacturer 60 based on the raw material configuration information stored in advance in the raw material configuration DB 33 and the product requirement obtained in step S21 in the form shown in FIG. Calculate the raw materials to be ordered.

  As shown in FIG. 17, the raw material configuration information stored in advance in the raw material configuration DB 33 is composed of “part code”, “raw material code”, and “number”.

  In step S23, the raw material procurement information collecting unit 35 collects the raw material delivery results delivered from the raw material manufacturer 60, and stores the raw material delivery results in the procurement result DB 36 as shown in FIG.

  As shown in FIG. 18, the information on the raw material delivery record stored in the procurement record DB 36 includes “order number”, “raw material code” of the ordered raw material, “delivery date”, and “quantity” delivered. ].

  In step S24, the production performance collecting unit 37 collects the production performance in each process in the parts manufacturer 30, and stores the production performance from the start of production to completion in the production performance DB 38 as shown in FIG. .

  As shown in FIG. 19, the information about the production results stored in the production result DB 38 includes “order number”, “part code”, “process code”, and a plurality of processes for finishing one part. "Process order" indicating the number of processes used in the process, "Final process" indicating the number of processes required to finish one part, "Production date", and "Production quantity" And “Production Tact”.

In step S25, the shipping information collection unit 39 collects shipping information within the parts manufacturer 30, and stores the shipping record in the shipment record DB 40 in the form as shown in FIG. That is, at the time of shipment, a part code and an order number of a part are recorded in a delivery form in a format standardized as an industry, such as an EIAJ (Electronic Industries Association of Japan) format. In addition, in order to manage the location of parts after shipment, a GPS receiver is mounted on the transportation means as shown in FIG. 1 so that the traveling position of the transportation means can be detected. Further, in order to associate the parts with the transportation means loaded with the parts, the ID of the GPS receiver mounted on the transportation means (hereinafter referred to as “running ID (Identification)”) is also read together with the reading of the invoice. In order to read the traveling ID, for example, the ID of the GPS receiver mounted on the transportation means is recorded in advance as a barcode label, and the barcode label is attached to the GPS receiver. At the stage where the delivery note and the traveling ID are read, the shipment results are stored in the shipment result DB 40 in the form shown in FIG.

  As shown in FIG. 20, the information related to the shipment record stored in the shipment record DB 40 includes “order number”, “part code”, “shipment date”, “shipment quantity”, and “travel ID”. .

  The procurement record stored in the procurement record DB 36 in step S23, the production record stored in the production record DB 38 in step S24, and the shipment record stored in the shipment record DB in step S25 are shown in FIG. As shown, data search in the factory 10 is possible via the Internet.

  In step S26, information on the travel position of the transport means indicated by the GPS receiver mounted on the transport means is transmitted to the factory 10 via wireless communication, and further, along with the travel ID after shipment, as shown in FIG. Is stored in the travel position DB 41 in a form.

  As shown in FIG. 21, the information stored in the travel position DB 41 includes “travel ID”, “date and time” indicating when information relating to the travel position of the transport means is received, and “longitude” indicating the travel position of the transport means. ”And“ latitude ”.

  In step S27, the parts inspection unit 45 performs an inspection process on the delivered parts, and stores information on the parts delivery results in the parts delivery results DB 46 in the form as shown in FIG.

  As shown in FIG. 24, the information stored in the parts delivery record DB 46 is composed of “order number”, “part code”, “customer code”, and “delivery date”.

  Next, referring to the drawings, the process for predicting the delivery date of the ordered part based on the information obtained by executing the steps from step S23 to step S27 and determining the part bottleneck is described. I will explain.

  FIG. 25 is a flowchart showing a process performed until the delivery date and time of the ordered part is predicted and the part bottleneck is determined in the first example of the parts management method of the present invention. In the figure, a solid line arrow indicates the flow of processing, and a broken line arrow indicates the timing of transmission / reception of information in each storage unit.

  In step S31, the parts delivery date prediction unit 47 determines whether the ordered part has been delivered. That is, the order number of the part stored in the order part DB 22 and the order number of the part stored in the part delivery result DB 46 are collated, and a part that is not in the part delivery result DB 46 in the order part DB 22 is determined as an undelivered part. judge. Here, when all the ordered parts have been delivered (when the determination result in step S31 is Y), the process proceeds to step S45, and when there are unordered parts among the ordered parts (determination in step S31). If the result is N), the process proceeds to step S32.

  FIG. 13 shows an example of part ordering information stored in the ordering part DB 22. That is, as shown in FIG. 13, the part ordering information stored in the ordering part DB 22 includes “order number”, “order date”, “model name”, “part code”, “customer code”, and “delivery”. It consists of “day” and “delivery quantity”.

  In step S <b> 32, the parts delivery date prediction unit 47 determines whether undelivered parts are shipped from the parts manufacturer 30. That is, with respect to the part determined not to be delivered in step S31, the shipping record DB 40 is searched for information on this part using the order number as a key, and if the information related to this part is in the shipment record DB 40, it has been shipped. Is determined. If it has been shipped (if the determination result in step S32 is Y), the process proceeds to step S33, and if it has not been shipped (if the determination result in step S32 is N). Advances to step S35.

  In step S33, the parts delivery date prediction unit 47 searches the travel ID for the parts determined to have been shipped in step S32 by referring to the information stored in the shipment record DB 40 using the order number as a key. The travel position of the transportation means is searched with reference to the information stored in the travel position DB 40 using the searched travel ID as a key.

  The location master 42 includes a “location code”, “location name”, “location name”, “location code” for locations important for tracking the location of parts, such as the location of the factory 10, the parts manufacturer 30, interchanges, ports, and airports. In addition, information indicating “longitude” and “latitude” with respect to the place code is stored in advance in the form as shown in FIG. On the other hand, as shown in FIG. 23, the travel route master 43 divides the travel route from the parts manufacturer 30 to the factory 10 into a plurality of sections, expresses the start position of the section as “FROM”, and indicates the end position of the section. Expressed by “TO”, these “FROM” and “TO”, “traveling means” by section, “required time”, “traveling distance”, normal “traveling speed”, and “traveling order” Are stored in advance for each “travel ID”. Here, a location code is stored in the FROM and TO fields, and this location code matches one of a plurality of location codes stored in the location master 42 shown in FIG. Therefore, the FROM and TO are searched using the driving ID stored in the driving route master 43 as a key, and the longitude and latitude of the FROM and TO stored in the location master 42 are searched using the FROM and TO as a key. If the traveling position of the transportation means obtained from the information stored in the traveling position DB 41 is sequentially plotted on a map, the traveling position of the transportation means can be visually confirmed.

  In step S34, the parts delivery date and time prediction unit 47 calculates the date and time when the transportation means arrives at the factory based on the travel position of the transportation means retrieved in step S33 and the information stored in the travel route master 43. Is stored in the parts delivery prediction DB 48 in the form as shown in FIG. The arrival date and time is calculated based on the travel position obtained in step S33 and the information stored in the travel route master 43. That is, the latest travel position (longitude and latitude) and travel speed are searched for each ID by referring to the information stored in the travel position DB 41, and the information stored in the travel route master 43 using the travel ID as a key. By referring to which section (FROM and TO) the latest travel position is in, the travel distance in the remaining section is calculated, and the travel time is calculated from the travel speed and the travel distance. Then, when searching for the section from the travel route master 43, the travel order is also searched. For a section that is larger than the travel order and matches the travel ID, the travel time is determined by the travel distance and travel speed of the section. calculate. Finally, the time when the transportation means arrives at the factory can be predicted from the travel time described above, and this time is stored in the parts delivery prediction DB 48.

  As shown in FIG. 27, the information stored in the parts delivery prediction DB 48 includes “order number”, “part code”, “customer code”, “current status” indicating that the product is being transported, being produced, or being adjusted. ”,“ Scheduled delivery date ”and“ delivery quantity ”.

  In step S35, the part delivery date prediction unit 47 determines whether or not the part determined to be unshipped in step S32 is in production. That is, for the parts determined not to be shipped in step S32, the production record stored in the production record DB 38 is searched using the order number as a key, and if there is a production record, it is determined that the part is in production.

  In step S36, the parts delivery date prediction unit 47 searches to which process the production of the parts in production is progressing. In the process order master shown in FIG. 19, the process order and the final process are stored in advance for each part code so that it can be tracked to what process a certain part has been produced. That is, the order number of the part determined not to be shipped in step S35 is collated with the information (see FIG. 19) stored in the production result DB 38, and the data in the process order is the largest among the data matching the order number. Search for process, production quantity and final process. Referring to the information on the production results shown in FIG. 19, for example, the fourth row from the top shows the production results when the production status is seen on January 24, and the part with the order number “401601” It can be seen that the process has progressed to “HI”, which is the final process, and production of up to 400 of the 500 units to be produced (the number calculated in step S21) has been completed.

  As shown in FIG. 26, the information stored in the process order master 44 includes “part code”, “number of Nissan units”, “process code”, “process order”, and “final process”.

  In step S37, the parts delivery date prediction unit 47 calculates the production completion scheduled date of the part in production in step S36. That is, the remaining production is calculated based on the process order and the production quantity obtained in step S36. At this time, as shown in FIG. 19, the production result DB 38 also stores a production-based production tact, so that the production tact can be searched. By multiplying the production residue by the production tact, the time required to complete the production can be calculated, and the production completion date can be calculated. If the process order determined to be currently performed in step S36 is smaller than the final process, the machining time from the process larger than the process order to the final process is calculated. That is, by using the information stored in the process order master 44 shown in FIG. 26, using the part code as a key, the number of Nissans in the process order that is larger than the process order determined to be currently being executed in step S36. The number of days required for production can be calculated by searching and dividing the product requirement calculated in step S21 by the number of Nissans already searched. As a result, the production completion date can be calculated. Note that the process order master 44 shown in FIG. 26 stores in advance the process order of each part code and the process order of the final process so that it can be tracked to what process a certain part has been produced.

  In step S38, the parts delivery date / time prediction unit 47 uses the information stored in the procurement L / T master 15 to search for a part conveyance L / T in the middle of production, and the production completion date calculated in step S37. The delivery date of the part is calculated by the transfer L / T, and the delivery date of the part is stored in the parts delivery prediction DB 48. That is, referring to the information stored in the order information DB 31 (see FIG. 15), the part code and the supplier code are searched using the order number as a key, and the procurement L / The delivery date is calculated by searching the conveyance L / T with reference to the information stored in the T master 15 (see FIG. 6) and adding the conveyance L / T to the production completion date calculated in step S37. it can.

  In step S39, the part delivery date prediction unit 47 determines whether or not the raw material of the part has been procured for the part determined not to be in production in step S35. That is, whether or not the ordering number of the part determined not to be produced in step S35 and information indicating the raw material that matches the raw material code of the raw material ordered in step S22 shown in FIG. 14 is stored in the procurement record DB 36. It searches and the information which shows the applicable raw material is memorize | stored in procurement history DB36, and it determines with it being procurement. If the raw materials are being procured (if the determination result in step S39 is Y), the process proceeds to step S40, and if all the raw materials are determined to be undelivered procurement (determination in step S39). If the result is N), the process proceeds to step S44.

  In step S40, the parts delivery date prediction unit 47 compares the raw material determined to be procured in step S39 with the raw material requirement calculated in step S22, that is, the raw material ordered from the parts manufacturer 30 to the raw material manufacturer 60. To calculate how much raw materials are procured. For example, for a part whose part code is DUNTK9000DE01, referring to the information stored in the order information DB 31 shown in FIG. 15, the delivery quantity is 1000 pieces and is stored in the product inventory DB 32 shown in FIG. If the information stored in the raw material configuration DB 33 shown in FIG. 17 is referred to, it is necessary to produce 500 pieces. Therefore, referring to the information stored in the raw material configuration DB 33 shown in FIG. The number of raw materials is 20 for MAT00XX and 10 for MAT00YY. Therefore, in order to produce 500 of these parts, 10000 for MAT00XX and 5000 for MAT00YY must be procured. However, referring to the information stored in the procurement record DB 36 shown in FIG. 18, 10,000 MAT00XX have been delivered, but only 2000 MAT00YY have been procured and 3000 have not been procured. Yes. In this case, (10000 + 2000) / (10000 + 5000) = 80% is procured as the raw material.

  In step S41, the part delivery date prediction unit 47 calculates a scheduled date for completing the procurement from the raw material procurement status calculated in step S40. This calculation procedure will be described in more detail with reference to FIG.

  FIG. 28 is a graph showing an example of the relationship among the procured raw materials, the raw material requirements, and the procurement results L / T that are referred to when the scheduled procurement completion date is calculated in the part delivery date prediction unit 47 shown in FIG.

  The raw material requirement amount has been calculated in step S22, and the procured raw material is obtained by referring to the information stored in the procurement performance DB 36 and summing the quantities of the procured raw materials. Further, the procurement record L / T refers to the information stored in the procurement record DB 36 to search for the date with the maximum delivery date and the date with the minimum order date among the procured raw materials. It can be calculated by taking the difference between The procurement pace and L / T required for procurement are calculated by the following formula.

Procurement pace = Procured raw materials (A) / Raw material requirements (B) Formula (3)
L / T required for procurement = (1-procurement pace) x procurement record L / T (C) Equation (4)
By referring to the information stored in the procurement record DB 36, the procurement completion date can be calculated by adding L / T necessary for procurement on the day of the maximum delivery date among the procured raw materials.

  In step S42, the parts delivery date prediction unit 47 searches the processing L / T with reference to the information stored in the procurement L / T master 15, and obtains the procurement completion date calculated in step S41 and the processing L / T. Thus, the production completion date is calculated.

  In step S43, the parts delivery date prediction unit 47 refers to the information stored in the procurement L / T master 15, searches for the conveyance L / T, and determines the production completion date calculated in step S42 and the conveyance L / T. Based on T, the scheduled delivery date is calculated and stored in the parts delivery forecast DB 48.

  In step S44, when it is determined in step S39 that all raw materials are not delivered, the part delivery date is searched with reference to the information stored in the ordered part DB 22, and stored in the part delivery prediction DB 48.

  In step S45, the parts bottleneck determination unit 49 refers to the information stored in the parts delivery record DB 46, the parts delivery forecast DB 48, the production plan DB 11, the parts configuration DB 12, and the parts inventory DB 13 to determine the production plan and the delivery date. The part bottleneck is determined by collation. That is, the number of units produced is searched by model and date of production with reference to information stored in the production plan DB 11. Further, the parts constituting the model are searched with reference to the information stored in the parts configuration DB 12, the necessary quantity is calculated, and the net requirement is calculated from the parts inventory with reference to the information stored in the parts inventory DB 13. Calculate the amount. Then, using the searched part code as a key, the delivery date and quantity of the part are searched with reference to the information stored in the part delivery record DB 46, and the information stored in the part delivery record DB 46 indicates If there is no corresponding part in the part, the delivery date and quantity of the part are searched with reference to the information stored in the part delivery forecast DB 48, a table as shown in FIG. 29 is created, and the production plan and delivery date are created. And match.

  FIG. 29 is a table relating to one model, and above the “code”, “required quantity”, “net requirement”, “current situation”, and “scheduled production number” of this model are shown. Below, the “code”, “required quantity”, “net requirement”, “current situation” and “planned number of production” of each ordered part among the parts necessary for producing this model are shown. Yes.

  Then, if the parts that are missing by the day of production planning are Kushiro and FIG. 29 is displayed on the screen of the display device, the missing parts, the date of occurrence of the shortage, and the delivery quantity are highlighted. In addition, here, it is also displayed which process the ordered part is in, such as delivered, transported, in production, or arranged for raw materials. The information on the parts bottleneck is stored in the parts bottleneck DB 50 in the form as shown in FIG.

  As shown in FIG. 30, the information stored in the parts bottleneck DB 50 is composed of “model”, “order number”, “part code”, “customer code”, “production date”, and “insufficient quantity”. Has been.

  Next, in the parts management system according to the present invention, when a parts bottleneck has occurred or is predicted to occur, consider whether to prompt parts or change the production plan, and make a decision. The support support information providing unit 3 provided for providing necessary information will be described with reference to the drawings.

  As shown in FIG. 1, the correspondence support information providing unit 3 includes a parts bottleneck DB 50, an action master 51, and an action information providing unit 52, which are stored in the supplier master 14, the procurement L / T master 15, and the procurement cost master 16. Information is referred to as auxiliary data.

  The action master 51 stores in advance actions that can be taken according to the difference between the delivery date of the part and the production date, as shown in FIG.

  As shown in FIG. 31, the information stored in the action master 51 is composed of “difference between delivery date and production date” and “possible action”. As an example, there are “less than 1 day”, “1 day to less than 3 days” and “3 days or more”, and “possible action” when “difference between delivery date and production date” is “less than 1 day” As an example of “possible action” when there is “parts prompting” and “difference between delivery date and production date” is “1 day or more and less than 3 days”, As an example of “possible actions” when there is “Parts manufacturer replacement” and “Difference between delivery date and production date” is “3 days or more”, “Production plan change” or “Transportation express handling” is there.

  Hereinafter, data processing performed in the support information providing unit 3 will be described with reference to the drawings.

  FIG. 32 is a flowchart showing a process performed when determining possible actions in the first embodiment of the component management method of the present invention. In the figure, a solid line arrow indicates the flow of processing, and a broken line arrow indicates the timing of transmission / reception of information in each storage unit.

  In step S51, the action information providing unit 52 refers to the information (see FIG. 30) stored in the part bottleneck DB 50 to calculate the difference between the production date and the delivery date of the bottle part, and this difference and the action master The possible actions are determined by collating the information stored in 51. For example, referring to FIG. 29 and FIG. 30, the difference between the production date and the delivery date of the part with the part code DUNTK9000EE01 is one day, and when compared with FIG. Is obtained.

  In step S52, the action information providing unit 52 searches for an additional fee generated according to the action. For example, an additional charge is not incurred when only part prompting is required, but an additional charge is incurred when handling an express flight or replacing a part manufacturer. This additional incurred amount is obtained as follows. First, the procurement cost is searched using the part code and the transaction code as a key with reference to the information stored in the part bottleneck DB 50. In the ordering stage, it is desirable to select a supplier with a low procurement cost and a treatment, and here, the treatment is normal and is added to the search key. This provides the current procurement cost. Next, referring to information stored in the parts bottleneck DB 50, the procurement cost master 16 searches the procurement cost master 16 for each supplier and for each part code. The difference between the current procurement cost and the procurement cost for each business partner and each handling is an additional cost.

  In step S53, the additional fee obtained in step S52 for the action obtained in step S51 is output on the screen of the display device as a candidate for action in the form shown in FIG. 33, or as shown in FIG. Action candidates are output to paper by a printer. Here, as an example of the action, the part manufacturer replacement to Company B with a lower additional charge is determined from the action candidates shown in FIG.

  As shown in FIG. 33, the output table is composed of “model”, “part code”, “possible action”, “part manufacturer”, and “additional charge” of parts related to this model.

  FIG. 34 is an explanatory diagram showing a second embodiment of the parts management system of the present invention.

  The difference between the first embodiment shown in FIG. 1 and the second embodiment is that a plurality of types of transportation means (a truck and a ship in this figure) equipped with a GPS receiver 70 are managed via the relay station 54, In addition, in order to transship parts between transportation means, a transshipment result DB 53 that stores a history of parts transshipment due to changes in transportation means from the parts manufacturer 30 to the factory 10 is provided. The same as in the first embodiment.

  Further, in the component management method by the component management system according to the second embodiment, the processing (FIG. 8 of the first embodiment) performed until the part is ordered and the data processing performed by the response support information providing unit 3 Of these, the processing performed when determining possible actions (FIG. 32 of the first embodiment) is the same as the processing in the first embodiment, and a description thereof will be omitted here. On the other hand, the processing (from FIG. 14 of the first embodiment) that is performed after the parts maker receives an order to deliver the parts, and the delivery date and time of the ordered parts are predicted, and the parts bottleneck is determined. Since the processing (FIG. 25 of the first embodiment) is different from the first embodiment in part of the processing, only these different processing will be described here. 2 to 33 can also be used in common in the second embodiment, and will be described with reference to FIGS. 2 to 33 as necessary.

  FIG. 35 is a flowchart illustrating a process performed from when a part manufacturer receives an order to when a part is delivered, in the part management method using the part management system according to the second embodiment. In the flowchart shown in FIG. 35, the same step numbers are assigned to the same processing steps as those in the flowchart shown in FIG.

  In step S21, the product requirement calculation unit 34 relates to the order information stored in the order information DB 31 as shown in FIG. 15 and the product inventory stored in the product inventory DB 32 as shown in FIG. From the information, the quantity of the product that needs to be manufactured, that is, the product requirement is calculated. If the product inventory is sufficient, the process proceeds to step S25, and if the product inventory is insufficient, the process proceeds to step S22.

  In step S22, the raw material procurement information collecting unit 35 places an order from the raw material manufacturer 60 based on the raw material configuration information stored in advance in the raw material configuration DB 33 and the product requirement obtained in step S21 in the form shown in FIG. Calculate the raw materials to be ordered.

  In step S23, the raw material procurement information collecting unit 35 collects the raw material delivery results delivered from the raw material manufacturer 60, and stores the raw material delivery results in the procurement result DB 36 as shown in FIG.

  In step S24, the production performance collecting unit 37 collects the production performance in each process in the parts manufacturer 30, and stores the production performance from the start of production to completion in the production performance DB 38 as shown in FIG. .

  In step S25, the shipping information collection unit 39 collects shipping information within the parts manufacturer 30, and stores the shipping record in the shipment record DB 40 in the form as shown in FIG. That is, at the time of shipment, a part code and an order number of a part are recorded in a delivery form in a format standardized as an industry, such as an EIAJ (Electronic Industries Association of Japan) format. Further, in order to manage the location of the parts after shipment, a GPS receiver 70 is mounted on the transportation means as shown in FIG. 34 so that the traveling position of the transportation means can be detected. Further, in order to associate the parts with the transportation means loaded with the parts, the ID of the GPS receiver 70 mounted on the transportation means (hereinafter referred to as “running ID (Identification)”) is also read together with the reading of the invoice. . In order to read the traveling ID, for example, the ID of the GPS receiver 70 mounted on the transportation means is recorded in advance as a barcode label, and the barcode label is attached to the GPS receiver 70. At the stage where the delivery note and the traveling ID are read, the shipment results are stored in the shipment result DB 40 in the form shown in FIG.

  The procurement record stored in the procurement record DB 36 in step S23, the production record stored in the production record DB 38 in step S24, and the shipment record stored in the shipment record DB in step S25 are as shown in FIG. In addition, data search in the factory 10 is possible via the Internet.

  In step S26, information relating to the travel position of the transport means indicated by the GPS receiver 70 mounted on the transport means is transmitted to the factory 10 via wireless communication, and further shown in FIG. 21 together with the travel ID after shipment. It memorize | stores in driving | running | working position DB41 in such a form. Since the radio wave does not reach when the transportation means and the factory are separated, a relay station 54 for amplifying the radio wave is provided.

  In step S26a, at the part transshipment point 55 shown in FIG. 34, the barcode label attached to the GPS receiver 70 in step S25 is read before the part is transshipped, and the running ID and the reading date and time before the part transshipment are obtained. After the parts are reloaded, the barcode label affixed to the GPS receiver 70 mounted on the traveling means after the parts are reloaded is read, the running ID and the reading date and time after the parts are reloaded are obtained, and the running before and after the parts are reloaded. The ID and the reading date / time are stored in the transshipment record DB 53 in the form as shown in FIG. Here, since it is anticipated that the transshipment point 55 of parts is separated from the factory, the transshipment result is transmitted to the factory by wireless communication.

  As shown in FIG. 36, the information on the transshipment record stored in the transshipment record DB 53 is composed of “travel ID” and “date and time” before transshipment, and “travel ID” and “date and time” after transshipment. ing.

  In step S27, the parts inspection unit 45 performs an inspection process on the delivered parts, and stores information on the parts delivery results in the parts delivery results DB 46 in the form as shown in FIG.

  Next, FIG. 25 shows a process for predicting the delivery date of the ordered part based on the information obtained by executing the steps S23 to S27 described above and determining the part bottleneck. This will be described with reference to a flowchart. In the flowchart shown in FIG. 25, the difference between the processing in the second embodiment and the processing in the first embodiment is mainly the processing in step S33 and step S34. In the following, description will be given in order.

  In step S31, the parts delivery date prediction unit 47 determines whether the ordered part has been delivered. That is, the order number of the part stored in the order part DB 22 and the order number of the part stored in the part delivery result DB 46 are collated, and a part that is not in the part delivery result DB 46 in the order part DB 22 is determined as an undelivered part. judge. Here, when all the ordered parts have been delivered (when the determination result in step S31 is Y), the process proceeds to step S45, and when there are unordered parts among the ordered parts (determination in step S31). If the result is N), the process proceeds to step S32.

  In step S <b> 32, the parts delivery date prediction unit 47 determines whether undelivered parts are shipped from the parts manufacturer 30. That is, with respect to the part determined not to be delivered in step S31, the shipping record DB 40 is searched for information on this part using the order number as a key, and if the information related to this part is in the shipment record DB 40, it has been shipped. Is determined. If it has been shipped (if the determination result in step S32 is Y), the process proceeds to step S33, and if it has not been shipped (if the determination result in step S32 is N). Advances to step S35.

  In step S33, the parts delivery date prediction unit 47 searches the travel ID for the parts determined to have been shipped in step S32 by referring to the information stored in the shipment record DB 40 using the order number as a key. The travel position of the transportation means is searched with reference to the information stored in the travel position DB 40 using the searched travel ID as a key.

  The location master 42 includes a “location code”, “location name”, “location name”, “location code” for locations important for tracking the location of parts, such as the location of the factory 10, the parts manufacturer 30, interchanges, ports, and airports. In addition, information indicating “longitude” and “latitude” with respect to the place code is stored in advance in the form as shown in FIG. On the other hand, as shown in FIG. 23, the travel route master 43 divides the travel route from the parts manufacturer 30 to the factory 10 into a plurality of sections, expresses the start position of the section as “FROM”, and indicates the end position of the section. Expressed by “TO”, these “FROM” and “TO”, “traveling means” for each section, “travel distance”, normal “travel speed”, and “travel order” are “travel ID”. Each is stored in advance. Here, a location code is stored in the FROM and TO fields, and this location code matches one of a plurality of location codes stored in the location master 42 shown in FIG. Further, in FIG. 23, when the transportation of parts is stopped due to parts transshipment or customs clearance, the same place code and transportation stop time are entered in the “FROM” and “TO” fields. It is remembered. Therefore, the FROM and TO are searched using the driving ID stored in the driving route master 43 as a key, and the longitude and latitude of the FROM and TO stored in the location master 42 are searched using the FROM and TO as a key. If the traveling position of the transportation means obtained from the information stored in the traveling position DB 41 is sequentially plotted on the map, the traveling position of the transportation means can be visually confirmed.

  36. Using the travel ID of the transportation means transported first after shipment by the above-described method as a key, the travel ID before transshipment in the transshipment record DB 53 shown in FIG. 36 is collated, and the travel ID after transshipment is the transshipment record. If it exists in the DB 53, the travel position can be searched using the travel ID after transshipment as a key. Thereafter, by using the travel ID after transshipment as a key and collating with the ID before transshipment, the travel ID after transshipment can be obtained and the travel position is known. By the time, even if there is a change in the transportation means of parts, the current traveling position and traveling means of the shipped parts can be known.

  In step S34, the date and time when the transport means arrives at the factory is calculated from the travel position of the transport means searched in step S33 and the travel route master 43, and the arrival date and time is stored in the parts delivery prediction DB 48 as shown in FIG. The arrival date and time is calculated based on the current travel position, travel means, and information in the travel route master 43 obtained in step S33. That is, the latest post-transmission travel ID is obtained from the transshipment record DB 53. A travel position (longitude and latitude) and travel speed are retrieved from the latest travel UD after transshipment from the travel position DB 41. Using the latest travel ID after transshipment as a key, search the travel route master 43 in which section (FROM, TO) the latest travel position is, and calculate the travel distance in the remaining sections. The required time is calculated from the traveling speed of the previous period and the traveling distance. When searching for the section from the travel route master 43, the travel order is also searched. For a section that is larger than the travel order and matches the travel ID, the time required for the section is searched. The time when the transportation means arrives at the factory can be predicted from the above required time. The time is stored in the parts delivery prediction DB 48.

  In step S34, the parts delivery date and time prediction unit 47 calculates the date and time when the transportation means arrives at the factory based on the travel position of the transportation means retrieved in step S33 and the information stored in the travel route master 43. Is stored in the parts delivery prediction DB 48 in the form as shown in FIG. The arrival date and time is calculated based on the travel position and travel means obtained in step S33 and the information stored in the travel route master 43. That is, the latest post-transmission travel ID is obtained from the transshipment record DB 53. A travel position (longitude and latitude) and a travel speed are retrieved from the travel position DB 41 based on the latest post-transshipment travel ID. Using the latest travel ID after transshipment as a key, search the travel route master 43 in which section (FROM, TO) the latest travel position is, and calculate the travel distance in the remaining sections. The required time is calculated from the traveling speed of the previous period and the traveling distance. When searching for the section from the travel route master 43, the travel order is also searched. For a section that is larger than the travel order and matches the travel ID, the time required for the section is searched. The time when the transportation means arrives at the factory can be predicted from the above required time. The time is stored in the parts delivery prediction DB 48.

  In step S35, the part delivery date prediction unit 47 determines whether or not the part determined to be unshipped in step S32 is in production. That is, for the parts determined not to be shipped in step S32, the production record stored in the production record DB 38 is searched using the order number as a key, and if there is a production record, it is determined that the part is in production.

  In step S36, the parts delivery date prediction unit 47 searches to which process the production of the parts in production is progressing. In the process order master shown in FIG. 19, the process order and the final process are stored in advance for each part code so that it can be tracked to what process a certain part has been produced. That is, the order number of the part determined not to be shipped in step S35 is collated with the information (see FIG. 19) stored in the production result DB 38, and the data in the process order is the largest among the data matching the order number. Search for process, production quantity and final process. Referring to the information on the production results shown in FIG. 19, for example, the fourth row from the top shows the production results when the production status is seen on January 24, and the part with the order number “401601” It can be seen that the process has progressed to “HI”, which is the final process, and production of up to 400 of the 500 units to be produced (the number calculated in step S21) has been completed.

  In step S37, the parts delivery date prediction unit 47 calculates the production completion scheduled date of the part in production in step S36. That is, the remaining production is calculated based on the process order and the production quantity obtained in step S36. At this time, as shown in FIG. 19, the production result DB 38 also stores a production-based production tact, so that the production tact can be searched. By multiplying the production residue by the production tact, the time required to complete the production can be calculated, and the production completion date can be calculated. If the process order determined to be currently performed in step S36 is smaller than the final process, the machining time from the process larger than the process order to the final process is calculated. That is, by using the information stored in the process order master 44 shown in FIG. 26, using the part code as a key, the number of Nissans in the process order that is larger than the process order determined to be currently being executed in step S36. The number of days required for production can be calculated by searching and dividing the product requirement calculated in step S21 by the number of Nissans already searched. As a result, the production completion date can be calculated. Note that the process order master 44 shown in FIG. 26 stores in advance the process order of each part code and the process order of the final process so that it can be tracked to what process a certain part has been produced.

  In step S38, the parts delivery date / time prediction unit 47 uses the information stored in the procurement L / T master 15 to search for a part conveyance L / T in the middle of production, and the production completion date calculated in step S37. The delivery date of the part is calculated by the transfer L / T, and the delivery date of the part is stored in the parts delivery prediction DB 48. That is, referring to the information stored in the order information DB 31 (see FIG. 15), the part code and the supplier code are searched using the order number as a key, and the procurement L / The delivery date is calculated by searching the conveyance L / T with reference to the information stored in the T master 15 (see FIG. 6) and adding the conveyance L / T to the production completion date calculated in step S37. it can.

  In step S39, the part delivery date prediction unit 47 determines whether or not the raw material of the part has been procured for the part determined not to be in production in step S35. That is, whether or not the ordering number of the part determined not to be produced in step S35 and information indicating the raw material that matches the raw material code of the raw material ordered in step S22 shown in FIG. 14 is stored in the procurement record DB 36. It searches and the information which shows the applicable raw material is memorize | stored in procurement history DB36, and it determines with it being procurement. If the raw materials are being procured (if the determination result in step S39 is Y), the process proceeds to step S40, and if all the raw materials are determined to be undelivered procurement (determination in step S39). If the result is N), the process proceeds to step S44.

In step S40, the parts delivery date prediction unit 47 compares the raw material determined to be procured in step S39 with the raw material requirement calculated in step S22, that is, the raw material ordered from the parts manufacturer 30 to the raw material manufacturer 60. To calculate how much raw materials are procured. For example, for a part whose part code is DUNTK9000DE01, referring to the information stored in the order information DB 31 shown in FIG. 15, the delivered quantity is 1000 pieces, and is stored in the product inventory DB 32 shown in FIG. If the information stored in the raw material configuration DB 33 shown in FIG. 17 is referred to, it is necessary to produce 500 pieces. Therefore, referring to the information stored in the raw material configuration DB 33 shown in FIG. The number of raw materials is 20 for MAT00XX and 10 for MAT00YY. Therefore, in order to produce 500 of these parts, 10000 for MAT00XX and 5000 for MAT00YY must be procured. However, referring to the information stored in the procurement record DB 36 shown in FIG. 18, 10,000 MAT00XX have been delivered, but only 2000 MAT00YY have been procured and 3000 have not been procured. Yes. In this case, (10000 + 2000) / (10000 + 5000) = 80% is procured as the raw material.

  In step S41, the part delivery date prediction unit 47 calculates a scheduled date for completing the procurement from the raw material procurement status calculated in step S40. This calculation procedure will be described in more detail with reference to FIG.

  FIG. 28 is a graph showing an example of the relationship among the procured raw materials, the raw material requirements, and the procurement results L / T that are referred to when the scheduled procurement completion date is calculated in the part delivery date prediction unit 47 shown in FIG.

  The raw material requirement amount has been calculated in step S22, and the procured raw material is obtained by referring to the information stored in the procurement performance DB 36 and summing the quantities of the procured raw materials. Further, the procurement record L / T refers to the information stored in the procurement record DB 36 to search for the date with the maximum delivery date and the date with the minimum order date among the procured raw materials. It can be calculated by taking the difference between The procurement pace and L / T required for procurement are calculated by the following formula.

Procurement pace = Procured raw materials (A) / Raw material requirements (B) Formula (5)
L / T required for procurement = (1-procurement pace) x procurement record L / T (C) Equation (6)
By referring to the information stored in the procurement record DB 36, the procurement completion date can be calculated by adding L / T necessary for procurement on the day of the maximum delivery date among the procured raw materials.

  In step S42, the parts delivery date prediction unit 47 searches the processing L / T with reference to the information stored in the procurement L / T master 15, and obtains the procurement completion date calculated in step S41 and the processing L / T. Thus, the production completion date is calculated.

  In step S43, the parts delivery date prediction unit 47 refers to the information stored in the procurement L / T master 15, searches for the conveyance L / T, and determines the production completion date calculated in step S42 and the conveyance L / T. Based on T, the scheduled delivery date is calculated and stored in the parts delivery forecast DB 48.

  In step S44, when it is determined in step S39 that all raw materials are not delivered, the part delivery date is searched with reference to the information stored in the ordered part DB 22, and stored in the part delivery prediction DB 48.

  In step S45, the parts bottleneck determination unit 49 refers to the information stored in the parts delivery record DB 46, the parts delivery forecast DB 48, the production plan DB 11, the parts configuration DB 12, and the parts inventory DB 13 to determine the production plan and the delivery date. The part bottleneck is determined by collation. That is, the number of units produced is searched by model and date of production with reference to information stored in the production plan DB 11. Further, the parts constituting the model are searched with reference to the information stored in the parts configuration DB 12, the necessary quantity is calculated, and the net requirement is calculated from the parts inventory with reference to the information stored in the parts inventory DB 13. Calculate the amount. Then, using the searched part code as a key, the delivery date and quantity of the part are searched with reference to the information stored in the part delivery record DB 46, and the information stored in the part delivery record DB 46 indicates If there is no corresponding part in the part, the delivery date and quantity of the part are searched with reference to the information stored in the part delivery forecast DB 48, a table as shown in FIG. 29 is created, and the production plan and delivery date are created. And match.

  Then, if the parts that are missing by the day of production planning are Kushiro and FIG. 29 is displayed on the screen of the display device, the missing parts, the date of occurrence of the shortage, and the delivery quantity are highlighted. In addition, here, it is also displayed which process the ordered part is in, such as delivered, transported, in production, or arranged for raw materials. The information on the parts bottleneck is stored in the parts bottleneck DB 50 in the form as shown in FIG.

  Next, in the parts management system according to the present invention, when a parts bottleneck has occurred or is predicted to occur, consider whether to prompt parts or change the production plan, and make a decision. The support support information providing unit 3 provided for providing necessary information will be described with reference to the drawings.

  As shown in FIG. 34, the correspondence support information providing unit 3 includes a parts bottleneck DB 50, an action master 51, and an action information providing unit 52, which are stored in the supplier master 14, the procurement L / T master 15, and the procurement cost master 16. Information is referred to as auxiliary data.

  The action master 51 stores in advance actions that can be taken according to the difference between the delivery date of the part and the production date, as shown in FIG.

  The parts management system and parts management method of the first embodiment and the second embodiment described above are used to grasp the progress from part ordering to part delivery, the raw material procurement status of parts manufacturers, the management of production progress and travel location, and order parts. This is realized by a program that allows a series of processing such as prediction from parts to parts to be delivered and early detection of parts bottlenecks.

  The subject of the invention may be the program itself, or the program stored in a computer-readable recording medium.

  In the present invention, as the recording medium, for example, a ROM itself may be a program medium, or a program reading device is provided as an external storage device (not shown), and the recording medium is inserted therein. It may be a readable program medium. In any case, the stored program may be configured to be accessed and executed by the microcomputer, or in any case, the program is read and the read program is a program (not shown) of the microcomputer. It may be a method in which the program is executed after being loaded into the storage area. It is assumed that this loading program is stored in the main device in advance.

  Here, the program medium is a recording medium configured to be separable from the main body, such as a tape system such as a magnetic tape or a cassette tape, a magnetic disk such as an FD (flexible disk) or HD (hard disk), or a CD-ROM / Supports fixed programs including optical disks such as MO / MD / DVD, card systems such as IC cards (including memory cards) / optical cards, and semiconductor memories such as mask ROM, EPROM, EEPROM, flash ROM, etc. It may be a medium.

  Further, in the present invention, since the system configuration is connectable to a communication network including the Internet, the medium may be a medium that dynamically carries the program so as to download the program from the communication network. When the program is downloaded from the communication network in this way, the download program may be stored in the apparatus main body in advance or may be installed from another recording medium. The content stored in the recording medium is not limited to a program, and may be data.

  The component management system, the component management method, the component management program, and the computer-readable recording medium on which the component management program of the present invention is recorded are devices that are produced by using a plurality of raw materials and are configured by a plurality of components. It can be used for production.

It is explanatory drawing which shows Example 1 of the components management system of this invention. It is explanatory drawing which shows the example of the production plan number according to model day. It is explanatory drawing which shows the structural example of a components structure database. It is explanatory drawing which shows the structural example of a parts inventory database. It is explanatory drawing which shows the structural example of a supplier master. It is explanatory drawing which shows the structural example of the procurement L / T master. It is explanatory drawing which shows the structural example of a procurement cost master. It is a flowchart which shows the process implemented before ordering components in Example 1 of the components management method of this invention. It is explanatory drawing which shows an example of the memory content of a components requirement memory | storage part. It is explanatory drawing which shows the structural example of a net components requirement database. It is explanatory drawing which shows an example of the chart which shows the delivery date of components displayed on the screen of the display apparatus connected to the components management system shown in FIG. It is explanatory drawing which shows an example of the chart which shows a business partner displayed on the screen of the display apparatus connected to the components management system shown in FIG. It is explanatory drawing which shows an example of the information memorize | stored in the ordering parts database. It is a flowchart which shows the process implemented after the parts maker receives an order from the Example 1 of the parts management method of this invention until it delivers a part. It is explanatory drawing which shows an example of the information memorize | stored in the order information database. It is explanatory drawing which shows an example of the information memorize | stored in the product stock database. It is explanatory drawing which shows an example of the information memorize | stored in the raw material structure database. It is explanatory drawing which shows an example of the information memorize | stored in a procurement performance database. It is explanatory drawing which shows an example of the information memorize | stored in a production performance database. It is explanatory drawing which shows an example of the information memorize | stored in a shipment performance database. It is explanatory drawing which shows an example of the information memorize | stored in a driving | running | working position database. It is explanatory drawing which shows an example of the information previously memorize | stored in the place master. It is explanatory drawing which shows an example of the information previously memorize | stored in the travel route master. It is explanatory drawing which shows an example of the information memorize | stored in a components delivery track record database. It is a flowchart which shows the process implemented before it predicts the delivery date of the ordered part among Examples 1 of the components management method of this invention, and determines a components bottleneck. It is explanatory drawing which shows an example of the information previously memorize | stored in the process order master. It is explanatory drawing which shows an example of the information memorize | stored in a components delivery prediction database. 3 is a graph showing an example of a relationship between a procured raw material, a raw material requirement amount, and a procurement record L / T that are referred to when calculating a scheduled procurement completion date in the part delivery date prediction unit shown in FIG. 1. It is explanatory drawing which shows an example of the result of having searched the delivery date and quantity of components about one model. It is explanatory drawing which shows an example of the information memorize | stored in a parts Kushiro database. It is explanatory drawing which shows an example of the information memorize | stored in the action master. It is a flowchart which shows the process implemented when determining possible action among Example 1 of the components management method of this invention. It is explanatory drawing which shows the example of the action candidate displayed on the screen of a display apparatus. It is explanatory drawing which shows Example 2 of the components management system of this invention. It is a flowchart which shows the process implemented until it delivers parts after a parts maker receives an order among Example 2 of the components management method of this invention. It is explanatory drawing which shows an example of the information memorize | stored in the transshipment performance database.

Explanation of symbols

1 Parts ordering department 2 Parts delivery management department 3 Response support information provision department 10 Factory 11 Production plan DB
12 Parts configuration DB
13 Parts inventory DB
14 Supplier Master 15 Procurement L / T Master 16 Procurement Cost Master 17 Parts Requirement Calculation Unit 18 Parts Requirement DB
19 Net Parts Requirement Calculation Unit 20 Net Parts Requirement DB
21 parts ordering information generator 22 ordering parts DB
23 Internet 30 Parts manufacturer 31 Order information DB
32 Product Inventory DB
33 Raw material composition DB
34 Product Requirements Calculation Department 35 Raw Material Procurement Information Collection Department 36 Procurement Results DB
37 Production Results Collection Department 38 Production Results DB
39 Shipping Information Collection Department 40 Shipping Results DB
41 Travel position DB
42 Location Master 43 Travel Route Master 44 Process Order Master 45 Parts Inspection Department 46 Parts Delivery Results DB
47 Parts delivery date and time prediction section 48 Parts delivery forecast DB
49 Parts Kushiro Judgment Unit 50 Parts Kushiro DB
51 Action Master 52 Action Information Providing Department 53 Transshipment Achievement DB
54 Relay station 55 Transshipment point 60 Raw material manufacturer 70 GPS receiver

Claims (17)

Parts ordering means for ordering parts required for production to parts manufacturers based on the production plan,
The process from ordering a part by the part ordering means to tracking the process from delivery of the part to grasping the delivery progress, predicting the delivery time of the ordered part, and predicting the delivery time from the predicted part delivery time and production plan Parts delivery management means for predicting Kushiro,
A parts management system comprising: correspondence support information providing means for providing support support information for eliminating a part bottleneck when the parts delivery management means predicts occurrence of a part bottleneck. The parts ordering means is
A production plan storage unit that stores the number of production plans for each model day,
A component configuration storage unit for storing the model-specific component,
A parts inventory storage unit for storing parts inventory;
A supplier storage unit for storing parts manufacturers;
A procurement lead time storage unit for storing the procurement lead time;
A procurement cost storage unit for storing procurement costs;
A part requirement calculation unit that calculates a part requirement from the number of production plans for each model type stored in the production plan storage unit and the component by type stored in the part configuration storage unit;
A net component requirement calculation unit for calculating a net component requirement from the component requirement calculated by the component requirement calculation unit and the component inventory stored in the component inventory storage unit;
A net part requirement storage unit for storing the net part requirement calculated by the net part requirement calculation unit;
Net component requirement stored in the net component requirement storage unit, component manufacturer stored in the supplier storage unit, procurement lead time stored in the procurement lead time storage unit, and procurement cost storage unit A parts ordering information generator that generates parts ordering information from the procurement cost
The part management system according to claim 1, further comprising: an ordering part storage unit that stores part ordering information generated by the part ordering information generation unit. The parts delivery management means is:
An order information storage unit for storing information received by a parts manufacturer;
A product inventory storage unit that stores the inventory of products owned by parts manufacturers,
A raw material configuration storage unit storing information on the raw materials constituting the product;
A raw material requirement calculation unit for calculating a raw material requirement from the order information stored in the order information storage unit, the product inventory stored in the product inventory storage unit, and the raw material information stored in the raw material configuration storage unit; ,
The parts management system according to claim 1, further comprising: a raw material ordering unit that orders a raw material from a raw material manufacturer based on the raw material requirement calculated by the raw material requirement calculation unit. The parts delivery management means is:
A raw materials procurement information collection department that collects the delivery results of raw materials from raw material manufacturers to parts manufacturers;
A procurement record storage unit for storing the raw material procurement record from the raw material manufacturer to the component manufacturer obtained by the raw material procurement information collecting unit;
A production results collection unit that collects production results for each production process within a parts manufacturer;
A production result storage unit for storing production results collected by the production result collection unit;
A shipping information collection unit that collects shipping information from parts manufacturers;
The parts delivery management system according to claim 1, further comprising a shipment record storage unit that stores shipment information collected by the shipment information collection unit. The parts delivery management means is:
A travel position collection unit that collects travel positions of parts transportation means by changing transportation means from the parts manufacturer to the delivery destination;
A travel position storage unit for storing the travel position of the transportation means collected by the travel position collection unit;
A transshipment collection unit that collects transshipments of parts associated with changes in means of transport;
A transshipment record storage unit for storing the transshipment of parts collected by the transshipment collection unit;
A parts acceptance department that performs parts acceptance processing at the supplier and collects parts delivery results;
The component management system according to claim 1, further comprising: a component delivery result storage unit that stores delivered components collected by the component inspection unit. The parts delivery management means is:
Parts delivery forecast date and time stored in the parts delivery forecast storage unit, parts delivery results stored in the part delivery result storage unit, number of production plans for each model date and parts configuration stored in the production plan storage unit A component-specific component stored in the storage unit, a component bottleneck determination unit that determines a component bottleneck from the component inventory stored in the component inventory storage unit,
The component management system according to claim 1, further comprising: a component bottleneck storage unit that stores a component bottleneck discovered by the component bottleneck determination unit. The correspondence support information providing means includes:
An action master storage unit for storing possible actions depending on the difference between the delivery date of the part and the production date;
Actions stored in the action master storage unit, parts bottles stored in the parts bottle storage unit, parts manufacturers stored in the transaction master storage unit, procurement lead times stored in the procurement lead time master storage unit The component management system according to claim 1, further comprising: an action information providing unit that presents an action for eliminating the component bottleneck based on the procurement cost stored in the procurement cost master storage unit.   Communication between the equipment constituting part of the part ordering means and part delivery management means provided on the part ordering side and the equipment constituting the other part of part delivery management means provided on the part ordering side The parts management system according to claim 1, which are connected to each other via a cable. A part ordering step to order parts required for production from a parts manufacturer based on a production plan;
Tracing the process from ordering a part to delivering the part in the part ordering step to grasp the delivery progress;
Predicting the delivery date of the ordered part;
A parts bottleneck prediction step for predicting a part bottleneck based on the predicted delivery date and production plan,
A component support information providing step of providing response support information for eliminating a component bottleneck when occurrence of a component bottleneck is predicted in the component bottleneck prediction step. The parts ordering step includes
A production plan storage step for storing the number of production plans for each model day;
A component configuration storage step for storing the model-specific component,
A parts inventory storage step for storing parts inventory;
A supplier storage step for storing the parts manufacturer;
A procurement lead time storage step for storing the procurement lead time;
A procurement cost storage step for storing the procurement cost;
A part requirement calculation step for calculating a part requirement from the production plan number by type stored in the production plan storage step and the component by type stored in the part configuration storage step;
A net component requirement calculation step for calculating a net component requirement from the component requirement calculated in the component requirement calculation step and the component inventory stored in the component inventory storage step;
A net component requirement storage step for storing the net component requirement calculated in the net component requirement calculation step;
Part ordering information based on the net part requirement stored in the net part requirement storage step, the parts manufacturer stored in the supplier storage step, the procurement lead time stored in the procurement lead time storage step, and the procurement cost stored in the procurement cost storage step Parts ordering information generation step for generating
The component management method according to claim 9, further comprising: storing the component order information generated in the component order information generation step. The parts delivery management step includes:
Order information storage step for storing information received by the parts manufacturer,
A product inventory storage step for storing the inventory of products owned by the parts manufacturer;
A raw material composition storing step for storing information of raw materials constituting the product;
The raw material requirement calculation step for calculating the raw material requirement from the order information stored in the order information storage step, the product inventory stored in the product inventory storage step, and the raw material information stored in the raw material configuration storage step;
The part management method according to claim 9, further comprising: ordering a raw material from a raw material manufacturer based on the raw material requirement calculated in the raw material requirement calculation step. The parts delivery management step includes:
A raw material procurement information collection step to collect raw material delivery results from raw material manufacturers to parts manufacturers;
A procurement record storage step for storing a raw material procurement record from a raw material manufacturer to a parts manufacturer obtained in the raw material procurement information collecting step;
Production results collection step to collect production results of each production process within the parts manufacturer,
A production performance storage step for storing the production performance collected in the production performance collection step;
A shipping information collection step for collecting shipping information from the parts manufacturer;
A shipping record storing step for storing the shipping information collected in the shipping information collecting step;
A travel position collection step for collecting the travel position of the transport step when parts are transported from the parts manufacturer to the delivery destination;
A travel position storage step for storing the travel position of the transportation step collected in the travel position collection step;
A parts acceptance step that performs parts acceptance processing at the supplier and collects parts delivery results;
The part management method according to claim 9, further comprising a part delivery result storage step for storing the delivered parts collected in the part inspection step. The parts delivery management step includes:
A raw material procurement information collection step to collect raw material delivery results from raw material manufacturers to parts manufacturers;
A procurement record storage step for storing a raw material procurement record from a raw material manufacturer to a parts manufacturer obtained by the raw material procurement information collecting step;
Production results collection step to collect production results of each production process within the parts manufacturer,
A production performance storage step for storing the production performance collected in the production performance collection step;
A shipping information collection step for collecting shipping information from the parts manufacturer;
The parts management method according to claim 10, further comprising a shipment record storage step for storing the shipment information collected in the shipment information collection step. The parts delivery management step includes:
A travel position collection step for collecting the travel position of the transportation step from the parts manufacturer to the delivery destination;
A travel position storage step for storing the travel position of the transportation step collected in the travel position collection step;
Transshipment collection step for collecting transshipment of parts due to change of means of transport;
Transshipment record storage step for storing the transshipment of parts collected in the transshipment collection step;
A parts acceptance step that performs parts acceptance processing at the supplier and collects parts delivery results;
The part management method according to claim 10, further comprising a part delivery result storage step for storing the delivered parts collected in the part inspection step. The correspondence support information providing step includes:
An action master storage step for storing possible actions according to the difference between the delivery date of the part and the production date;
The action stored in the action master storage step, the part bottleneck stored in the part bottleneck storage step, the part manufacturer stored in the transaction master storage step, the procurement lead time stored in the procurement lead time master storage step, and stored in the procurement cost master storage step The component management method according to claim 9, further comprising: a response support information providing step of presenting an action for eliminating the component bottleneck based on the procurement cost.   A computer-readable component management program for executing the component management method according to any one of claims 9 to 15.   A computer-readable recording medium on which the component management program according to claim 16 is recorded.

Images