JP5276607B2 - FORECAST MANAGEMENT SYSTEM, ITS CONTROL METHOD, AND ITS PROGRAM - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To shorten a lead time for a component. <P>SOLUTION: This forecast management system S is provided with: unordered component presentation means 13 and 14 which clarify the necessary time limit of each of components by developing components configuring a finished product from order scheduled information by using the requested date of delivery of the finished product as a reference, and presents the necessary time limit of the components to a component transaction destination which purchases the components by display devices 60 and 81; ordered component presentation means 13 and 14 for presenting the necessary time limit of the already ordered components configuring the finished product by the display devices 60 and 81; and a time of delivery observation rate display means 15 which displays the time of delivery observation rate for every accumulating total of normal ordering whose predetermined time of delivery has been observed and short delivery time ordering the delivery of which is shorter than the predetermined time of delivery or the sum of the normal ordering and the short delivery time ordering based on the past component warehousing information stored in a storage part 518 by the display devices 60 and 81. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to a forecast management system for shortening a component lead time from part ordering to delivery in a forecast that discloses part ordering information and ordering schedule information to a part supplier that is a part ordering part, The present invention relates to a control method and a program thereof.

Conventionally, there are Patent Documents 1, 2, and 3 as forecasts for publishing part ordering schedule information and parts procurement methods.
In the method of Patent Document 1, a reservation order is issued and then a firm order is issued as a method for easily following the procurement of parts to a production plan changed after an order of necessary parts. In addition, a system that sets and issues a pre-order for the quantity of parts that have not been allocated is handled.

In Patent Document 2, the number of procurement is calculated based on forecast information and past arrangement information.
In Patent Document 3, necessary parts are purchased together in a batch layout that is conscious of order information of products manufactured using the parts and a production method based on the customer specifications of the products, that is, by purchasing the parts in units of parts. Yes.

Japanese Patent Laid-Open No. 2002-63440 (Claims 1 to 13, FIG. 1 etc.) JP 2002-140110 A (paragraph 0015, FIG. 1 etc.) Japanese Patent Laying-Open No. 2004-178137 (paragraphs 0008 to 0010, FIG. 1, etc.)

By the way, in the above-mentioned patent document 1, there is a problem that the order form of the procurement department is more than doubled and complicated, and the parts supplier is also more than doubled.
Moreover, in patent document 2, in the case of multi-product small-quantity production, there exists a problem that it cannot be determined with the past arrangement information (standard remaining storage system).
Patent Document 3 is a method in which necessary parts are purchased in a unit of form in consideration of a production method based on order information of products manufactured using the parts and customer specifications of the products. There is a problem that it is not suitable for small-lot production of various varieties.

In these conventional methods, the lead time of the parts that make up the product (the period from the order date of the part to the delivery date) is compared to the product lead time required by the customer (the period from the order date of the product to the delivery date). If it is large, orders are arranged before the time of use of the parts becomes clear based on past usage results.
For this reason, a deviation occurs between the actual required number of parts and the number of ordering arrangements, and when the number of ordering arrangements is larger than the necessary number, excessive inventory of parts occurs. Conversely, if the required number of parts is greater than the number of parts ordered, the parts lead time will be broken due to parts shortage (short delivery order shorter than the period from the part order date contracted with the parts supplier to the delivery date) Will occur.

Therefore, the number of management man-hours such as re-adjustment of schedules at internal related departments of parts suppliers and parts ordering sources is increasing.
In this way, in the production system where parts lead time is large compared to the product lead time requested by the customer and customer usage occurs individually, the customer request is generally made by ordering parts according to the inventory of parts or past usage records. Responds to lead time (product lead time). However, from the management point of view, it is necessary to reduce the inventory of parts, and there is a demand for shortening the part lead time (the period from ordering parts to delivery).

  In view of the above circumstances, an object of the present invention is to provide a forecast management system capable of reducing the component lead time, a control method thereof, and a program thereof.

  In order to achieve the above object, a forecast management system according to the first aspect of the present invention is a forecast management system for disclosing information of parts to parts suppliers who purchase or plan to purchase parts. Based on the required delivery date of the product, from the order schedule information, it is expanded to the parts constituting the finished product to clarify the individual deadlines for the parts, and the parts deadline for purchasing the parts is determined based on the deadlines for the parts. An unordered part presenting means for presenting on the display device, an already ordered part presenting means for presenting the necessary time limit of the already ordered parts constituting the finished product on the display device, and a past part arrival stored in the storage unit Based on the information, the delivery date compliance rate is calculated based on the normal order that is an order that meets the predetermined delivery date, the short delivery order that is shorter than the default delivery date, or the sum of the regular order and the short delivery order. Cumulative Separately, and a time delivery display means for displaying on the display device.

  A forecast management system control method according to a second aspect of the present invention is a forecast management system control method for publishing information on a part to a part supplier who purchases or plans to purchase the part, and has not yet been ordered. The part presentation means expands the ordering information from the order schedule information to the parts constituting the finished product on the basis of the required delivery date of the finished product to clarify the individual deadlines for the parts, Is displayed on a display device to a parts supplier who purchases, the already-ordered part presenting means presents the necessary time limit of the already ordered parts constituting the finished product on the display device, and the delivery date compliance rate displaying means is a storage unit. Based on the past parts arrival information stored in the Above Apart from total of the sum of the delivery order, it is displayed on the display device.

  The program of the forecast management system of the third aspect of the present invention is a program of the forecast management system for causing a computer to execute the control method of the forecast management system of the second aspect of the present invention.

  According to the present invention, it is possible to realize a forecast management system capable of reducing the component lead time, a control method thereof, and a program thereof.

1 is a conceptual block diagram illustrating an entire forecast management system according to an embodiment of the present invention. It is a notional block diagram which shows the structure of an information recording part. It is a figure which shows the structure of the product announcement data file stored in an information recording part. It is a figure which shows the structure of the product parts table data file stored in an information recording part. It is a figure which shows the structure of the product manufacture information data file stored in an information recording part. It is a figure which shows the structure of the components information data file stored in an information recording part. It is a figure which shows the structure of the warning component data file stored in an information recording part. It is a figure which shows the structure of the product arrangement data file stored in an information recording part. It is a figure which shows the arrangement parts data file structure stored in an information recording part. It is a figure which shows the structure of the total required component data file stored in an information recording part. It is a figure which shows the structure of the inventory data file stored in an information recording part. It is a figure which shows the structure of the order information data file stored in an information recording part. It is a figure which shows the structure of the part shortage quantity data file stored in an information recording part. It is a figure which shows the structure of the components supplier information data file stored in an information recording part. It is a figure which shows the structure of the weekly parts shortage quantity data file stored in an information recording part. It is a figure which shows the structure of the data file for order lot calculation stored in an information recording part. It is a figure which shows the structure of the forecast detailed information data file stored in an information recording part. It is a figure which shows the structure of the forecast information data file stored in an information recording part. It is a figure which shows the structure of the forecast taking responsibility data file stored in an information recording part. It is a figure which shows the procedure regarding the product manufacture information registration process for registering in the product manufacture information data file by a master information management part. It is a figure which shows the product manufacture information registration screen of a product manufacture information registration process. It is a figure which shows the procedure regarding the component information registration process for registering component information into a component information data file. It is a figure which shows the components information registration screen of a components information registration process. It is a figure which shows the process sequence of the components supplier information registration process in a master information management part. It is a figure which shows the components supplier information registration screen of components supplier information registration processing. It is a figure which shows the process sequence of the advance arrangement process in an arrangement information management part. It is a figure which shows the product notice screen of notice arrangement processing. It is a figure which shows the procedure regarding the product arrangement process in an arrangement information management part. It is a figure which shows the product arrangement screen of a product arrangement process. It is a figure which shows the forecast disclosure screen of the forecast presentation for components suppliers. It is a figure which shows the forecast details public screen of the forecast presentation for components suppliers. It is a figure which shows the forecast publication screen which refers to a forecast. It is a figure which shows a forecast number breakdown screen. It is a figure which shows the components arrival information data file stored in an information recording part. It is a figure which shows the delivery date compliance rate display screen which refers to the delivery date compliance rate of A company. It is a figure which shows the delivery date delay status screen showing the detail of the delivery date delay of A company. (a) is a figure which shows the component lead time distribution display screen of all the parts, (b) is a figure which shows the component lead time distribution display screen of a part with a large use frequency, (c) is a medium use frequency. It is a figure which shows the part lead time distribution display screen of the part of (1), (d) is a figure which shows the part lead time distribution display screen of the part with a small use frequency, (e) is a part of the part with the minimum use frequency It is a figure which shows a lead time distribution display screen. The delivery date compliance line graph showing the change in the delivery date compliance rate by parts supplier, the purchase quantity line graph of the actual number of parts purchased and the number of parts to be purchased in advance, and the number of parts ordered to parts suppliers It is a figure which shows the delivery date compliance rate / purchase quantity / order number transition screen on which the order number bar graph to represent is displayed. Delivery date compliance rate line graph showing the transition of delivery date compliance rate by parts supplier, purchase quantity line graph of actual purchase quantity of parts and previous purchase planned quantity, and purchase price bar chart showing change of purchase price of parts It is a figure which shows the delivery date compliance rate / purchase quantity / purchase amount transition screen on which is displayed.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
<< Overview of Forecast Management System S of Embodiment >>
Conventionally, a part lead time from ordering to delivery of a part used for manufacturing the product is larger than a product lead time from product ordering to delivery required by a customer who orders the product. For this reason, in the product receiver (parts purchaser) that receives orders for products, in a high-mix low-volume production system where customer use occurs individually, products that customers generally request by ordering parts in stock or past usage records Responding to lead time. However, from the viewpoint of management, it is necessary to reduce the inventory of parts, and there is a demand for shortening the lead time of parts.

Therefore, the forecast management system S of the embodiment presents forecast information based on the planned production quantity to a parts supplier who purchases parts.
Specifically, Forecast Management System S discloses the planned purchase quantity of ICs (Integrated Circuits), capacitors, etc. used for manufacturing products based on the advance notice of the expected number of products such as printed circuit boards. Forecasting, that is, forecasting, is made public to parts suppliers who are parts suppliers, and it is possible to properly order and stock parts to be used even in high-mix low-volume production.
Furthermore, the forecast management system S provides parts suppliers who purchase parts to parts suppliers with respect to the due date and the due date, the lead time distribution, the distribution of the parts lead time, the purchase quantity and amount of the parts to be purchased, By presenting the transition of the number of cases and disclosing detailed information on the parts to be delivered to the parts suppliers, we are aiming to improve the delivery date compliance rate and shorten the parts lead time.

Hereinafter, the forecast management system S of the embodiment will be described in detail.
FIG. 1 is a conceptual block diagram showing an entire forecast management system S according to an embodiment of the present invention.
A forecast management apparatus 10 such as a server that operates the forecast management system S uses a product produced by a part orderer (parts purchaser) via a communication network 70 such as a LAN (Local Area Network). Manages information related to parts deployment device 20 deployed in stock, inventory management device 30 that manages the inventory of parts used for product production, ordering of parts from parts suppliers, unsold items remaining after order placement, etc. Purchased goods management apparatus 40, parts arrival information management apparatus 45 for managing the arrival information of ordered parts, information recording unit 50 for recording various information of forecast management system S, and forecast management system S as a part ordering source of parts. The person in charge is connected to an input / output terminal 60 for input / output. The communication network 70 may be a WAN (Wide Area Network), the Internet, or the like, and is not limited.

In addition, the forecast management apparatus 10 is connected to a parts supplier such as a parts manufacturer such as a parts manufacturer via a communication network 80 such as the Internet so that data can be input and output to the forecast management system S and data communication can be performed. An output terminal 81 is connected.
In addition, although the case where each of the input / output terminal 60 of the parts ordering source (part purchasing source) and the input / output terminal 81 of the parts supplier is one is illustrated, it is needless to say that there may be a plurality.

<Forcast management device 10>
The forecast management device 10 is, for example, a computer such as a server, and includes a main storage device such as a CPU (Central Processing Unit), a flash memory, and a RAM (Random Access Memory), an auxiliary storage device such as an HDD (Hard Disk Drive), and the like. Have.
The auxiliary storage device of the forecast management apparatus 10 includes a master information management unit 11, an arrangement information management unit 12, a forecast quantity management unit 13, a forecast presentation unit 14, and a delivery date compliance rate that are processing units of the forecast management system S. A system program for realizing the presentation unit 15 and the lead time presentation unit 16 is stored.

The master information management unit 11, the arrangement information management unit 12, the forecast quantity management unit 13, the forecast presentation unit 14, the due date compliance rate presentation unit 15, and the lead time presentation unit 16 are system programs in which the CPU is stored in the auxiliary storage device Is loaded into the main storage device and executed, and the following functions of the forecast management system S are realized.
The system program that embodies the master information management unit 11, the arrangement information management unit 12, the forecast quantity management unit 13, the forecast presentation unit 14, the due date compliance rate presentation unit 15, and the lead time presentation unit 16 is a single server. Or may be stored in another server. Further, the file may be transferred from another server or read from a magnetic recording medium, and the form is not limited.

  The master information management unit 11, the arrangement information management unit 12, the forecast quantity management unit 13, the forecast presenting unit 14, the delivery date compliance rate presenting unit 15, and the lead time presenting unit 16 can perform these functions as long as each function can be exhibited. As a matter of course, one or any number of management units can be configured.

The master information management unit 11 is stored in an information recording unit 50 described later that stores master information such as inventory information of parts used for production of products, product information of products to be produced, and part information of parts used for products. Manage files.
The master information includes, for example, the order lead time from part ordering to delivery (part lead time), and the quantity confirmation lead time that represents the period in which the responsibility for picking up the part occurs from the date the forecast is released. The information includes information such as a possible period for postponement representing a grace period for taking parts, an order lot which is a minimum ordering part for parts, a usage frequency of parts, and a unit unit price.
In the master information management unit 11, information that is not recorded in the information recording unit 50 is stored in a storage unit such as a table.

As shown in FIG. 1, the arrangement information management unit 12 manages the arrangement information of parts by using a parts development device 20, an inventory management device 30, a purchased product management device 40, a parts arrival information management device 45, and the like.
The forecast quantity management unit 13 performs an ordering process for calculating the required number of parts to be described later, and a forecast number calculating process for calculating the forecast quantity of parts scheduled to be purchased with respect to a parts supplier.
The forecast presentation unit 14 is a processing unit that forecasts information on parts to be purchased based on the information in the information recording unit 50 to parts suppliers, parts purchasers, and the like. And the security management of the forecast management system S is performed.

The delivery date compliance rate presenting unit 15 calculates the delivery date compliance rate, which is the ratio of keeping the delivery date, from the delivery results of the parts of the parts supplier. It is a processing unit that presents information such as quantity to a parts supplier, a parts purchaser, and the like.
The lead time presentation unit 16 is a processing unit that presents various information related to the component lead time to a component supplier, a component purchaser, and the like, using information managed by the master information management unit 11.

  In the forecast management system S, an access right to the forecast management system S is set, and an ID and a password stored in a security data file (not shown) are supplied to the user via the input / output terminals 60 and 81. Is assigned or set in advance. The forecast presentation unit 14, the delivery date compliance rate presentation unit 15, and the lead time presentation unit 16 provide the ID and password input via the input / output terminals 60 and 81 in the security data file (see FIG. For those whose access authority is set, information corresponding to the set access authority is disclosed, and the input ID and password are stored in the security data file. If the access authority is not set, access is disabled.

<< Information Recording Unit 50 >>
The information recording unit 50 is a storage device such as a memory or a hard disk, but is not limited as long as it is a storage unit.
FIG. 2 is a conceptual configuration diagram showing the configuration of the information recording unit 50 shown in FIG.
The information recording unit 50 includes a product notice data file 501, a product parts table data file 502, a product production information data file 503, a part information data file 504, a notice part data file 505, a product arrangement data file 506, and an arrangement part data file 507. , Total necessary parts data file 508, inventory data file 509, order information data file 510, parts shortage quantity data file 511, parts supplier information data file 512, weekly parts shortage quantity data file 513, order lot calculation data file 514 , Forecast detailed information data file 515, Forecast information data file 516, Forecast takeover responsibility data file 517 for recording a record with takeover responsibility, and storage of the information on the ordered parts received Parts stock information data file 518 is stored that.

Hereinafter, these data files 501 to 517 will be described in order.
<< Product Notice Data File 501 >>
FIG. 3 is a diagram showing the configuration of the product notice data file 501 stored in the information recording unit 50 of FIG.
The product notice data file 501 is used to make a notice of a product to be ordered from a customer.
The product notice data file 501 includes a notice number for identifying the notice data of the product, a product code for identifying the product, a product notice quantity that is the product quantity of the product code for which the notice number is given, and the The product notice period, which is the required delivery date for the product notice quantity, is associated.

Here, codes such as “Y001”, “Y002”,... Are used as the notice numbers, and codes such as “S001”, “S002”,... Are used as the product codes.
For example, for the notice number “Y001”, 10 products with the product code “S001” are requested on June 1, 2007, and 20 products with the product code “S002” are requested on June 1, 2007. I foresee that.

<< Product Parts List Data File 502 >>
FIG. 4 is a diagram showing the configuration of the product parts table data file 502 stored in the information recording unit 50 of FIG.
The product parts table data file 502 is created by using a part development technique for products, and indicates what parts each product uses.
The product parts table data file 502 is associated with a product code, a part code for identifying a part necessary for producing a product of the product code, and the quantity of the part of the part code. Here, codes such as “B001”, “B002”,... Are used as the component codes.

For example, the product with the product code “S001” needs one part with the part code “B001”, one part with the part code “B002”, and two parts with the part code “B003”. Yes.
However, the relationship illustrated here is a simple case where the relationship between the product code and the part code is one layer, and the general expansion of n layers (n is a positive integer) is a data file defined by a well-known technique. By providing the above, the development from the product code to the part code can be realized.

<< Product Production Information Data File 503 >>
FIG. 5 is a diagram showing the configuration of the product production information data file 503 stored in the information recording unit 50 of FIG.
The product production information data file 503 indicates how many days each product can be produced when parts are available. This number of production days is referred to as production lead time. That is, the production lead time is a period required from the start of production of a product to completion in a state where parts necessary for producing the product are prepared, and a number representing the number of days is used.
The product production information data file 503 is associated with a product code and a product production lead time of the product code.

<< Part information data file 504 >>
FIG. 6 is a diagram showing a configuration of the component information data file 504 stored in the information recording unit 50 of FIG.
The component information data file 504 manages component information and contract information purchased from a component supplier, and indicates the following attributes of each component.
The part information data file 504 includes a part code, a part name of the part code, an order lot which is the minimum unit of the part order quantity to the part supplier, and an order lead time (number of parts from the order date to the delivery date). (Part lead time), the quantity confirmation lead time that represents the period in which the responsibility for taking over the part occurs from the date when the forecast is released, expressed in days, the postponement possible period that represents the grace period for taking parts, and the cycle of the part order date The ordering cycle to be displayed, the number of days of acceptance testing that represents the number of days required for inspection of the part from the date of delivery of the part, the part supplier code that identifies the supplier of the part, and the forecast that contains “Yes” in the case of a forecasted part The target part flag is associated.

The order lead time (part lead time), the quantity confirmation lead time, and the take-off postponement possible period are determined by the contract with the parts supplier in the forecast operation, and are expressed in days.
Depending on the required delivery date, if the demand forecast quantity of each part by day, that is, the forecast quantity piled up, is between the date when the forecast is published and the quantity confirmation lead time, it will be released within the quantity confirmation lead time period For the forecast quantity, the parts purchaser is responsible for taking over. The responsibility for picking up means the responsibility for picking up the parts that have been forecasted by the ordering side (parts purchaser). This is because, when the ordering side (parts purchaser) forecasts the parts, the parts supplier side prepares the forecasted parts in advance, and therefore defines the responsibility for taking over.
When the responsibility for taking over occurs, the date when the order lead time (part lead time) is subtracted from the required delivery date of the part is defined as the planned order date, and if there are no fluctuations in the forecast quantity and the required delivery date, the parts supplier An order is issued to the customer.

Even if the required number of parts of the forecast quantity has decreased due to the occurrence of takeover responsibility and the need for ordering is no longer required, the parts purchaser can take over the postponement period, which is the grace period for taking parts from the planned order date, due to takeover responsibility. An order must be placed by the day that passes.
For example, if a part with an order lead time “5 days”, a quantity confirmation lead time “10 days”, and a postponement postponement possible period “15 days” is published on January 1, the required delivery date of the parts is January. With regard to forecast quantities in the period up to 11 days, takeover responsibility arises. If the required delivery date is January 10, the forecast quantity for which the takeover responsibility has occurred is the order lead time “5 days”. Orders must be placed by January 20th.

The ordering cycle represents the interval at which a part purchaser places an order for a part from a parts supplier, that is, the part ordering cycle from the parts supplier in days. For example, when placing an order once a week, the order interval is “7 days”.
The purpose of using the ordering cycle is to determine how many days before the planned order date to place an order. In the case of daily ordering, it is an unnecessary item because it can be ordered according to the planned order date. However, if “7 days” is the order cycle, orders with a planned order date within 6 days from the order date are ordered. There is a need to. Otherwise, the order after 7 days will not be placed until the next 7 days, so it will be the worst, plus 7 days later, and the planned order date will be over. .

The acceptance test days are the number of days from when a part arrives at a product maker (parts purchaser) to when the parts maker (parts purchaser) can use it for production of products through processes such as acceptance inspection. The parts supplier code is a parts supplier defined for each part code, indicates a supplier of each part, and is a parts supplier that performs forecast disclosure.
The forecast target part flag is a flag indicating whether or not the forecast operation determined in the contract assuming the responsibility for taking over is performed. In the case of “Yes”, the takeover responsibility is generated according to the above-mentioned contract. In the case of “,” since the contract concerning the forecast with the parts supplier is not concluded, only the piles of the requested delivery date of the parts are disclosed, and the responsibility for taking over the parts purchaser does not occur.

  For example, the part code “B001” is the part name “AAA”, the order lot which is the minimum unit quantity of the order is “10”, and the order lead time (part lead time) from the order date to the delivery date is “ “30 days”, the quantity confirmation lead time indicating the period in which the responsibility for taking over occurs after the publication of “Forecast” is “60 days”, the postponement period that is the postponement period for taking parts can be “30 days”, and the order is an order cycle The cycle is “7 days”, the production acceptance test days that can be used for production from the arrival of parts to the acceptance inspection are “0 days”, the parts receipt destination code is “M001”, and the forecast target part flag is “Yes” Is. Therefore, a contract concerning the forecast is made with the parts take-up destination of the take-away destination code “M001”, and the part “AAA” indicates that the part is a forecast target part.

<< Notice Part Data File 505 >>
FIG. 7 is a diagram showing the configuration of the notice component data file 505 stored in the information recording unit 50 of FIG.
The notice part data file 505 represents the result of developing the product for each notice number shown in the product notice data file 501 of FIG. 3 into parts.
The notice part data file 505 includes the notice number, the product code of the product included in the notice number, the consistent NO. The part notice quantity of the part of the part code and the part notice period of the part are associated with each other.

For the notice branch number, codes such as “01”, “02”,... Are used. For example, the product code “S001” for which the notice number “Y001” has been notified is assigned the notice technique number “01” because the product code “S001” is the first, and the notice number “Y002” has been given a notice. Since the product code “S001” is second, the notice branch number “02” is assigned to the product code “S001” of the product.
The part notice quantity is a part quantity necessary for producing a product with the product code noticed by the notice number. Each of the product notice quantity in the product notice data file 501 in FIG. 3 and each of the product parts table data file 502 in FIG. It is a calculated value when it is expanded in the parts table by the product of the number of parts used in the product.

As described above in the description of the product parts table data file 502 (see FIG. 4), the development of a product into a general n-layer part is performed by developing the parts using a well-known technique, and the notice part data file 505 shown in FIG. Shall be created.
The parts notice required period is a requested delivery date of parts necessary for producing a product having the product code notified by the notice number. In this part notice period, the production lead time of the product production information data file 503 in FIG. 5 is traced back to the factory operating date from the product notice period in the product notice data file 501 in FIG. This is a date retroactive to 504 acceptance test days.

Here, the relationship between the data files is determined by referring to the product code in the product production information data file 503 (see FIG. 5) with the product code in the product notice data file 501 (see FIG. 3), and obtaining the production lead time. The acceptance test days are obtained by referring to the part code of the part information data file 504 (see FIG. 6) with the part code of the file 505 (see FIG. 7).
For example, as shown in FIG. 7, in order to produce the product code “S001” of the notice number “Y001”, 10 part codes “B001” are required on May 25, 2007.

<< Product arrangement data file 506 >>
FIG. 8 is a diagram showing the configuration of the product arrangement data file 506 stored in the information recording unit 50 of FIG.
The product arrangement data file 506 shows details such as the quantity and delivery date of products arranged with an arrangement number representing one arrangement.
The product arrangement data file 506 includes an arrangement number for identifying the arrangement data of the product, a product code of the product to be arranged, a product arrangement quantity indicating the quantity of the product arranged by the arrangement number, and a product having a requested delivery date for the arrangement quantity. The arrangement period is associated.
As the arrangement number, codes such as “T001”, “T002”,... Are used. For example, the arrangement number “T001” in FIG. 8 indicates that 10 products having the product code “S001” need to be arranged on May 21, 2007, which is the product arrangement period.

<< Ordered part data file 507 >>
FIG. 9 is a diagram showing the configuration of the arrangement part data file 507 stored in the information recording unit 50 of FIG.
The arranged parts data file 507 is an expanded product arranged at the parts level.
The arrangement part data file 507 includes the arrangement number (see FIG. 8), the product code of the product arranged by the arrangement number, the arrangement number of the consistent NO allocated for each arranged product code, and the parts included in the product. Are associated with a part code, a part arrangement quantity of the part, and a part arrangement necessity period, which is a delivery date when the part is required. As the arrangement branch number, codes such as “A1”, “A2”,... Are used.

  For example, since the product code “S002” arranged with the arrangement number “T002” is the arrangement number where “S002” appears first, the arrangement branch number “A1” is assigned, and the arrangement number “T003” The product branch order “S002” is assigned the order branch number “A2” because “S002” is the order number that appears second.

  The part arrangement quantity is the part quantity to be arranged necessary for producing the product of the product code arranged by the arrangement number. The product arrangement quantity in the product arrangement data file 506 in FIG. 8 and the product parts table data file 502 in FIG. It is a calculated value obtained by integrating the quantity of parts used for each product and expanding the parts table.

  The part arrangement deadline is a required delivery date of parts necessary to produce a product having the product code arranged by the arrangement number. In this part arrangement period, the production lead time of the product production information data file 503 in FIG. 5 is traced back to the factory operation date from the product arrangement period in the product arrangement data file 506 in FIG. 8, and the part information data file 504 in FIG. This is the date that goes back the number of days of acceptance testing.

Here, the relationship between the data files is determined by referring to the product code in the product production information data file 503 in FIG. 5 with the product code in the product arrangement data file 506 in FIG. It is assumed that the acceptance test days are obtained by referring to the part code of the part information data file 504 in FIG.
For example, as shown in FIG. 9, in order to produce the product code “S001” with the arrangement number “T001”, 10 parts with the part code “B001” are required on May 14, 2007, which is the part arrangement period. Indicates that it is necessary.

<< Total Necessary Parts Data File 508 >>
FIG. 10 is a diagram showing the configuration of the total necessary component data file 508 stored in the information recording unit 50 of FIG.
The total necessary part data file 508 is created by combining the notice part data file 505 in FIG. 7 and the arranged part data file 507 in FIG.
The total necessary parts data file 508 is managed for each arrangement number or notice number in part code and part period.

The total necessary parts data file 508 includes an arrangement number or a notice number, a notice number, a product code of a product that has been arranged / predicted, a branch number, a part code of a part included in the branch number, a part quantity of the part, The part deadline (delivery date of the necessary deadline for parts) is associated.
The arrangement / notice number is the notice number of the notice part data file 505 (see FIG. 7) or the order number of the arrange part data file 507 (see FIG. 9). The branch number is the notice branch number of the notice component data file 505 (see FIG. 7) or the arrange branch number of the arrange part data file 507 (see FIG. 9). The parts quantity is the parts notice quantity in the notice parts data file 505 (see FIG. 7) or the parts arrangement quantity in the arranged parts data file 507 (see FIG. 9). The parts essential period is the parts preliminary notice period in the notice part data file 505 (see FIG. 7) or the parts arrangement essential period in the arranged part data file 507 (see FIG. 9).
Note that the data of the arranged parts data file 507 (see FIG. 9) is registered in the total necessary parts data file 508 as data for producing the product in-house.

<< Inventory data file 509 >>
FIG. 11 is a diagram showing the configuration of the inventory data file 509 stored in the information recording unit 50 of FIG.
The inventory data file 509 indicates how many parts of the part code are in the warehouse.
The inventory data file 509 is associated with a part code representing a part and the inventory quantity of the part of the part code. Note that the stock quantity is registered by the stock management apparatus 30 (see FIG. 1), and the latest stock quantity is registered by managing the loading and unloading of parts by a well-known technique.
For example, the inventory quantity of the part code “B001” is 12 pieces.
When subcontracting the production of a product, the inventory information of the manufacturer of the manufacturer that is the subcontractor is also received via the communication network 80 and registered in the inventory data file 509.

<< Order Information Data File 510 >>
FIG. 12 is a diagram showing the configuration of the order information data file 510 stored in the information recording unit 50 of FIG.
The order information data file 510 shows detailed information of the ordered parts for each order number.
The order information data file 510 includes an order number, which is a unit of an already ordered order, a part code of a part ordered with the order number, an order quantity when ordered with the order number, and an order remaining after subtracting the received quantity from the ordered quantity. The quantity, the date of ordering from the parts supplier to the parts supplier, the order lead time (part lead time) from the order date to the delivery date, and the delivery deadline for the parts requested from the parts supplier The required delivery date, the following required date / week, the order delivery period that is the difference between the requested delivery date and the order date, the response delivery date of the deliverable date answered by the parts supplier to the order number, and the takeover responsibility number are associated with each other. Yes. In some cases, parts are delivered from parts suppliers on the day before the answer delivery date.

Here, the order lead time (part lead time) is the order lead time obtained by referring to the part information data file 504 in FIG. The term year / week is defined as the consistent weekly NO for each year up to the week before January 1 of the following year, where the week including January 1 is the first week. For example, January 1, 2007 is the first week of 2007, and January 8, 2007 is the second week of 2007.
The order period is the difference between the requested delivery date and the order date, and is used to distinguish between orders that secure the order lead time (part lead time) or short-term orders that do not secure the order lead time in the processing described below. It is an item. That is, when the ordering period is shorter than a predetermined ordering lead time (part lead time) that is a period from the ordering date to the delivery date, the order is shortly delivered and expressed as a crack in the lead time later.

The takeover responsibility number is a number that is taken when the takeover responsibility number is registered in the forecast takeover responsibility data file 517 on the occurrence date of the takeover responsibility. The date of occurrence of the responsibility for taking over will be described later.
The order information data file 510 (see FIG. 12) is created from the planned order quantity in the part shortage quantity data file 511 of FIG. There is a case to create by specifying the delivery date.
In addition, as for ordering information of a manufacturing maker that is a subcontractor in the case of subcontracting the production of a product, information on the manufacturing maker is received via the communication network 80 or the like and registered in the ordering information data file 510.

<< Part shortage quantity data file 511 >>
FIG. 13 is a diagram showing a configuration of the component shortage quantity data file 511 stored in the information recording unit 50 of FIG.
The part shortage quantity data file 511 shows detailed information for each required part, which is the required delivery date of the part.

  The part shortage quantity data file 511 can be used after being inspected from the part code of the part, the predetermined order lead time (part lead time) from the order date of the part to the delivery date, the order cycle, the delivery date of the part, etc. The number of days of acceptance testing that represents the period of time, the order lot that is the minimum order quantity, the part time that is the part delivery date, the number of days from today to the part time, the part quantity for the part time period, the inventory reserve quantity that reserves the inventory parts , Remaining inventory quantity after deducting inventory allocation quantity from parts quantity, remaining inventory quantity after order reservation, remaining inventory quantity after remaining inventory order by subtracting remaining inventory quantity after order allocation, shortage quantity below (lot calculation The previous planned order quantity and the forecast quantity of the following shortage quantity (before lot calculation) are associated.

The part code, the part period, and the part quantity are obtained by referring to the total necessary part data file 508 in FIG. The order lead time (part lead time), order period, acceptance test days, and order lot are obtained by referring to the part information data file 504 in FIG.
“Days until the required period” is the difference between the component required period and the creation date of the component shortage quantity data file 511 (see FIG. 13), that is, the forecast data creation date.
The inventory allocation quantity is obtained as a result of the allocation to the part quantity in the order of the parts essential period in the parts shortage quantity data file 511 in FIG. 13 until the inventory quantity referring to the inventory data file 509 in FIG. It is a quantity.

The remaining order quantity is calculated by referring to the order information data file 510 in FIG. 12 with the part code to calculate the total value of the remaining order quantity. This is the quantity resulting from the allocation to the remaining quantity.
The planned order quantity for the shortage quantity (before lot calculation) is compared with “Days until the required period” and “Order lead time + Order cycle + Acceptance test days”. When the ordering cycle + the number of acceptance test days is the same or smaller than the "order lead time + ordering cycle + the number of acceptance test days", the "remaining quantity after remaining order placement" is set.
The forecasted quantity of shortage (before lot calculation) is calculated by comparing “number of days until the required time” with “order lead time + ordering cycle + acceptance test days”. If it is greater than “+ order cycle + acceptance test days”, “remaining quantity after remaining order placement” is set.

<< Parts supplier information data file 512 >>
FIG. 14 is a diagram showing a configuration of the parts supplier information data file 512 stored in the information recording unit 50 of FIG.
The parts supplier information data file 512 indicates the date when the parts supplier who has concluded a contract relating to the forecast with the parts purchaser has started the forecast publication represented by the date of conclusion of the forecast contract.
In the parts supplier information data file 512, the parts supplier code for identifying the parts supplier who has signed a contract related to the forecast with the parts purchaser, the parts supplier name of the code, and the date when the forecast release is started. Associated with the date of the conclusion of the forecast contract.

The forecast contract conclusion date is the date on which forecast publication is started on the premise of taking over responsibility for parts suppliers.
For example, the parts supplier name of the parts supplier code “M001” is “Company A”, and the forecast contract is concluded, that is, the forecast disclosure that assumes the responsibility of taking over the parts purchaser to the parts supplier is made public. The start date is February 22, 2007.

<< Weekly parts shortage quantity data file 513 >>
FIG. 15 is a diagram showing the configuration of the weekly parts shortage quantity data file 513 stored in the information recording unit 50 of FIG.
The weekly parts shortage quantity data file 513 is extracted only from the parts shortage quantity data file 511 shown in FIG. 13 that have a forecast, that is, a shortage quantity (before lot calculation) that has a forecasted quantity. is there.

In the weekly parts shortage quantity data file 513, the part code of the part to be forecasted, the part period of the part, the week including January 1 of every year is the first week of the week including January 1 of the following year. It is related to the forecast release year, the following forecast release week, and the forecasted forecast quantity.
The forecast release period is divided into weekly release periods. In the example shown in Fig. 15, the forecast release date is divided into weeks starting with Sunday and ending with Saturday. It is a thing.
In this way, the weekly parts shortage quantity data file 513 in FIG. 15 extracts data in which the forecast quantity of the shortage quantity (before lot calculation) is 1 or more from the data in the parts shortage quantity data file 511 in FIG. Shows what you did.

<< Order Lot Calculation Data File 514 >>
FIG. 16 is a diagram showing the configuration of the order lot calculation data file 514 stored in the information recording unit 50 of FIG.
In the order lot calculation data file 514, the order lot, the forecasted forecast quantity, the previously announced quantity determined quantity below, and the current order quantity consideration below are taken into account for each forecast release week and forecasted part code. The quantity, the quantity before considering the number of lots below, and the forecast quantity are associated.

The order lot is obtained by referring to the part information data file 504 in FIG. 6 with a part code, and is the minimum unit quantity of the parts to be ordered as described above.
The forecast scheduled quantity is a total quantity obtained by summarizing the forecast scheduled quantity every forecast release week by referring to the weekly parts shortage quantity data file 514 of FIG. 15 by the part code.

The previously presented quantity fixed quantity is the quantity for which the quantity has been confirmed among the forecast quantities in the order lot calculation data file 514 (see FIG. 15) created at the time of the previous update, that is, the quantity for which takeover responsibility has occurred.
The current order quantity considering quantity is a quantity obtained by subtracting the previously presented quantity determined quantity by the order quantity total quantity after the previous forecast update date in order from the oldest date. This order quantity total quantity is the total value of the order quantity referred to the order information data file 510 of FIG. 12 by the part code and the order date after the previous forecast update date.

  To calculate the quantity before considering the number of lots, that is, this time (this week), the quantity of parts that do not take into account the number of lots to be cast is calculated by first calculating the cumulative number of forecasted quantities up to the nth week by ΣA (n), nth The current order quantity considering quantity up to a week is defined as ΣB (n), and the quantity before considering the number of lots up to the nth week is defined as ΣC (n). The quantity C (n) before the lot number in the n-th week is a quantity obtained by subtracting ΣC (n−1) from the larger quantity of ΣA (n) and ΣB (n).

  For example, the quantity before considering the number of lots this week, that is, the number of parts that do not take into account the number of lots that will be cast this time (this week) is larger than the cumulative number of forecasts up to this week and the quantity before considering the number of lots up to this week. This is the quantity obtained by subtracting the quantity before the number of lots up to the previous week. In this way, the forecast forecast for this week is calculated by subtracting the forecast forecast quantity up to the previous week from the larger quantity of the forecast forecast quantity up to this week and the cumulative quantity of parts for which transaction responsibility has occurred. By calculating the quantity, it is configured so as not to be duplicated and to purchase extra parts.

In calculating the forecast quantity, if the quantity before the number of lots up to the nth week is ΣC (n), the forecast quantity D (n) in the nth week is a multiple of the order lot, and ΣC (n ) -ΣC (n-1) or more and the smallest number.
Further, as shown in FIG. 16, a range of “ordering”, “quantity determination”, and “publication only” is defined for each subsequent week based on the part code and this week. For example, next week is +1 week, next week is +2 week, and so on.

  For the range of “ordering” and “confirm quantity”, the part information data file 504 (see FIG. 6) is referred to by the part code, and when the forecast target part flag is “Yes”, the forecast contract data file 512 ( This is defined only when the forecast contract conclusion date in FIG. 14 has been set. On the other hand, for parts codes that do not satisfy the condition that the forecast target part flag is “No” (see FIG. 6) and the forecast contract conclusion date (see FIG. 14) is blank, all disclosure ranges are defined as “public only”. The In this case, the range of “quantity determination” is not defined, but only the range of “ordering” and “publication” is defined.

  When the conditions of the forecast target parts flag (see FIG. 6) and the forecast contract conclusion date (see FIG. 14) are satisfied, the “order” first obtains the range of “order” on a daily basis. The range of the “order” for each week is obtained from the range of the “order”. The range of “ordering” in units of days is the order lead time (part lead time) that is the period from the order date to the delivery date that refers to the part information data file in FIG. This is the period up to the date of addition.

  Weekly “Purchase” range is considered as “Purchase Order” range if all dates included in each Forecast Release Week are included in the daily “Purchase Order” range. . For example, if the weekly schedule starts on Sunday and ends on Saturday, and if Wednesday is the daily "order" range, all dates included in the forecast release week are included in the daily "order" range. Therefore, the range up to the previous week is “ordering” in units of weeks.

Also, for example, if the weekly schedule starts on Sunday and ends on Saturday, and if Saturday is the daily ordering range, all the dates included in the forecast release week are included in the daily ordering range. This week is the range of weekly “ordering”.
In the “quantity determination”, first, the range of “quantity determination” is obtained on a daily basis, and the range of “quantity determination” on a weekly basis is obtained from the range of “quantity determination” on a daily basis. The range of “quantity confirmation” on a daily basis is the period up to the date when the quantity confirmation lead time for the period in which the responsibility for taking over occurs when the part information data file in FIG. It is. Note that the weekly “quantity determination” range is that if all dates included in each forecast release week are included in the daily “quantity determination” range, the forecast release week will be “quantity determination”. As a range.

“Public only” corresponds to a period other than the ranges of “ordering” and “confirm quantity”.
Finally, for part codes that have a quantity confirmation range, add the total of forecast quantities in the “order” range to the weekly forecast quantity at the left end of the quantity confirmation area, Set the forecast quantity of the range to 0.
This indicates that the postponement of the order due to the period in which the takeover responsibility occurred can be displayed in the range of “confirm quantity”, not in the range of “order”.

<< Forcast Detailed Information Data File 515 >>
FIG. 17 is a diagram showing a configuration of the forecast detailed information data file 515 stored in the information recording unit 50 of FIG.
The forecast detailed information data file 515 shows detailed information on the previous forecast and the current forecast, that is, the forecast for the current week (this week).
The forecast detailed information data file 515 indicates, for each part code, the quantity that has been received (ordered and delivered), the order that has been ordered but not yet delivered, the order that has not been ordered, and that is scheduled to be ordered.

  The forecast detailed information data file 515 includes the last note (normal order; indicates that the order lead time (part lead time) can be observed) for the forecast release week and each forecasted part code. Remaining (breaking lead time; indicates lead time for order lead time (part lead time) cracking), previous order planned, current order remaining (normal order), current order remaining (lead time cracked), current order planned Yes.

The last order (normal order) sets the current order (normal order) of the same essential year and week of the forecast detailed information data file 515 at the time of the previous update.
The last note (lead time break) sets the current note (lead time break) of the same essential year / week of the forecast detailed information data file 515 at the time of the previous update.
As the previous ordering schedule, the current ordering schedule of the same essential year and week of the forecast detailed information data file 515 at the time of the previous update is set.
For this order (normal order), refer to the order information data file 510 (see FIG. 12) with the part code, and the remaining order quantity for the data whose order period is equal to or greater than the order lead time (part lead time) for each required year / week. Is the total quantity.

For the remaining order (breaking lead time), refer to the ordering information data file 510 (see FIG. 12) with the part code, and the remaining order quantity for which the ordering period is less than the order lead time (part lead time) for each required year and week. This is the total quantity.
The current ordering schedule is the quantity of the same part code and the same period year and week with reference to the forecast quantity in the order lot calculation data file 514 (see FIG. 16).
As shown in FIG. 17, for example, 20 items in the last +7 week of the remaining amount (normal order) for finalizing the quantity will be 20 in the current +6 week since one week has passed this time. In addition, 20 pieces of this time +7 weeks are for new orders.
In addition, 20 items in the last +7 weeks of the remaining quantity (lead time split) in the final quantity determination will be 20 in the current +6 weeks since the current one week has passed. In addition, from the relationship of product inquiries, it is possible to set 20 pieces for the current +7 week instead of 20 pieces for the current +6 week by contract with a parts supplier. In this case, this time +6 weeks is blank. FIG. 17 shows this case.

  Further, since 40 weeks of +9 weeks in the period only for the release of the previous ordering schedule has been passed for one week, it becomes 40 pieces of +8 weeks of the quantity order scheduled to be ordered this time. In addition, due to contracts with parts suppliers due to product inquiries, 40 items of +9 weeks in the period of only release of the previous ordering plan are 30 pieces of +8 week of quantity confirmation scheduled to be ordered this time, only release It may be divided into 10 pieces of +9 weeks of the period. In this case, for example, one customer of a product inquiry destination (part purchase source) that uses 40 parts is proceeding with the shipment of the product (uses 30 parts) as planned. Another customer (parts purchaser) is when the plan for a product (using 10 parts) is delayed by one week.

In addition, since 50 pieces of +11 weeks in the period only for the release of the previous ordering schedule have passed one week, 50 pieces of +10 weeks in the period of only the release of the current ordering plan are provided. In addition, due to product inquiries, due to contracts with parts suppliers, 50 weeks of +11 weeks in the period of only public release of the previous ordering have passed one week, but +11 weeks of the period of only public release of the current ordering scheduled It may be 50 (shown in parentheses in FIG. 17). That is, this is the case when the customer's plan for the product that uses these 50 parts (part purchase source) can be sent for one week. In this case, this time +10 weeks is blank.
In addition, in the forecast detailed information data file 515 of FIG. 17, the difference between the current update content and the previous update content of the received parts quantity may be searched.

<< Forward Information Data File 516 >>
FIG. 18 is a diagram showing the structure of the forecast information data file 516 stored in the information recording unit 50 of FIG.
The forecast information data file 516 is a main screen to be disclosed to suppliers, and information for each component for each component supplier, and this week (this week), +1 week of next week, +2 week of next week, ..., +15 weeks Indicates the ordering period, quantity confirmation period, and period of disclosure only.

The forecast information data file 516 associates the order lead time (part lead time), the quantity determination lead time during the period in which the responsibility for taking over occurs, and the period in which the take-off period can be postponed for each part code for each part supplier code. In addition, the total quantity of the remaining portion of the forecast detailed information data file 515 (see FIG. 17) (ordinary order), the remaining order (breaking lead time), and the order schedule is shown for each part code and release week. .
The parts supplier code, order lead time (part lead time), quantity confirmation lead time and take-off postponement possible period of the forecast information data file 516 were obtained by referring to the part information data file 504 (see FIG. 6) with the part code. Value.

<< Forward receipt responsibility data file 517 >>
FIG. 19 is a diagram showing the structure of a forecast takeover responsibility data file 517 stored in the information recording unit 50 of FIG.
The forecast takeover responsibility data file 517 manages the parts that have reached the quantity confirmation lead time for which the takeover responsibility has occurred, and is used to see how many parts must be bought, the deadline for taking over, etc. Is.
The forecast takeover responsibility data file 517 includes a part code for identifying a part for which the takeover responsibility has occurred at the part purchaser, a date of takeover responsibility for the part of the part code, and a number of days in which the takeover responsibility for the part of the part code occurs. Quantity confirmation lead time, possible period for taking off parts of the part code, quantity of responsibility for taking parts of the part code, ordering deadline for parts of the part code, takeover responsibility number indicating the unit of takeover responsibility, the takeover responsibility number The estimated arrival date of the part is associated.

The takeover responsibility occurrence date is the date when the takeover responsibility for the parts is generated, and is the registration date in the forecast takeover responsibility data file 517.
The quantity determination lead time is a value obtained by referring to the part information data file 504 in FIG. The take-off possible period is a value obtained by referring to the part information data file 504 of FIG.
Refer to the forecast detailed information data file 515 of FIG. 17 by the part code, and calculate the total number of orders to be placed (this time) within the quantity fixed range. This is a quantity obtained by subtracting the total quantity of responsible responsibility occurrence quantity in the data file 517.

The order deadline is a date obtained by adding the quantity confirmation lead time and the take-off postponement period on the take-off responsibility occurrence date. The takeover responsibility number is a number that is taken when the forecast takeover responsibility data file 517 is registered on the occurrence date of the takeover responsibility. The scheduled arrival date is a date clearly showing the arrival schedule by presenting it to the parts supplier and confirming the delivery date.
The take-off responsibility generation quantity is calculated for each part code, and if it is larger than 0, it is registered in the forecast take-off responsibility data file 517.
Further, referring to the order information data file 510 of FIG. 12 under the condition that the order date is larger than the previous update date for each part code, the order quantity total is calculated. Then, since the take-off responsibility occurrence quantity that refers to the forecast take-off responsibility data file 517 of FIG. 19 by the part code is ordered first from the one with the smallest take-off responsibility occurrence date, the calculated order in ascending order of the take-off responsibility occurrence date. Offset by total quantity. The amount is canceled until the amount of occurrence responsibility becomes 0, or the total order amount generated when the occurrence date of receipt responsibility is late and the order date can be a later date becomes 0.

Next, various operations of the management units 11, 12, 13 and the presentation units 14, 15, 16 of the forecast management apparatus 10 shown in FIG. 1 will be described. First, the master information management unit 11 is described here. Will be described.
<< Product Production Information Registration Process in Master Information Management Unit 11 >>
The product production information registration process in the master information management unit 11 will be described with reference to FIG. FIG. 20 is a diagram showing a procedure related to product production information registration processing for registration in the product production information data file 503 (see FIG. 5) by the master information management unit 11.
The registrant logs in to the master information management unit 11 (see FIG. 1) of the forecast management apparatus 10 using the input / output terminal 60 shown in FIG. 1, and selects product production information registration from the menu screen. 21 is displayed on the input / output terminal 60.

The product production information registration screen G1 shown in FIG. 21 has input fields G1a and G1b for product code and production lead time. After inputting data into the search button G1c and the input fields G1a and G1b to be searched when searching for information. It has a registration button G1d to be pressed when registering data.
When searching for product production information of a desired product code, the registrant first enters the product code in the product code input field G1a of the product production information registration screen G1 displayed on the input / output terminal 60 (see FIG. 1). For example, after inputting “S001” or the like, the search button G1c is pressed.
Then, the input product code data is transmitted (S11 in FIG. 20), and the forecast management apparatus 10 stores the product code input by the registrant in the information recording unit 50 (see FIG. 1) in FIG. The product production information data file 503 is referred to S12), the production lead time is acquired, transmitted to the input / output terminal 60 (S13, S14), and displayed in the production lead time input field G1b.

As a result of referring to the product production information data file 503 (see FIG. 5), if the corresponding product code does not exist, the production lead time input field G1b of the product production information registration screen G1 in FIG. 21 remains “blank”. And FIG. 21 shows a case where “5” is displayed instead of “blank”.
When the production lead time input field G1b is “blank”, as shown in FIG. 21, the registrant inputs “5” in the production lead time input field G1b (S15 in FIG. 20), and the registration button G1d. Press.
Then, the input production lead time data is transmitted (S16), and the forecast management apparatus 10 (see FIG. 1) uses the production lead time inputted by the registrant as the product production information data file 503 (see FIG. 5). (S17).

<< Part Information Registration Processing in Master Information Management Unit 11 >>
Next, the component information registration process in the master information management unit 11 will be described with reference to FIG. FIG. 22 is a diagram showing a procedure related to the component information registration process for registering the component information in the component information data file 504 (see FIG. 6).
When the registrant logs in to the master information management unit 11 of the forecast management apparatus 10 using the input / output terminal 60 (see FIG. 1) and selects part information registration from the menu screen, the input screen shown in FIG. A part information registration screen G 2 is displayed on the input / output terminal 60.
The part information registration screen G2 in FIG. 23 includes a part code input field G2a, a part name, an order lot, an order lead time, a quantity confirmation lead time, a postponement possible period, an order cycle, an acceptance test day, and a part supplier. Each input field of code and forecast target part flag, search button G2b to be pressed when searching for part information of the part code input in the part code input field, part name, order lot, order lead time, quantity There is a registration button G2c which is pressed when registering input part information such as a confirmed lead time, a period for which a postponement is possible, an ordering cycle, an acceptance test day, a parts supplier code, and a forecast target part flag.

When searching for the component information of the desired component code, the registrant first uses the input / output terminal 60 to enter the component code “B001” or the like in the component code input field G2a of the component information registration screen of FIG. After inputting (S21 in FIG. 22), the search button G2b is clicked.
Then, the component code data is transmitted (S22), and the forecast management apparatus 10 (see FIG. 1) refers to the component information data file 504 in FIG. 6 of the information recording unit 50 with the component code input by the registrant. (S23), part name, order lot, order lead time, quantity confirmation lead time, take-off postponed period, order cycle, acceptance test days, parts supplier code, forecast target part flag (S24), input / output The data is transmitted to the terminal 60 (S25) and displayed.

If there is no corresponding part code as a result of referring to the part information data file 504 in FIG. 6, the part name, order lot, order lead time, quantity confirmation lead time, take-off postponement on the forecast information registration screen G2 in FIG. The input fields of possible period, ordering cycle, acceptance test days, parts supplier code, and forecast target parts flag are “blank”. FIG. 23 shows the case where the part code “B001” exists and data is displayed in each input field.
When registering the part information, as shown in FIG. 23, the registrant, as shown in FIG. 23, the part name, order lot, order lead time, quantity confirmation lead time, take-off postponed period, order cycle, acceptance test days, parts supplier code Then, part information such as a forecast target part flag is input (S26 in FIG. 22), and the registration button G2l is pressed. Note that in S26 of FIG. 22, information on any of the part name, order lot, order lead time, quantity confirmation lead time, take-off postponed period, order cycle, acceptance test days, parts supplier code, forecast target part flag And the registration button G2l may be pressed. In this case, the corrected component information is registered in the component information data file 504 in FIG.
Then, the input component information is transmitted (S27 in FIG. 22), and the forecast management apparatus 10 registers the component information input by the registrant in the component information data file 504 (see FIG. 6) (S28).

<< Part supplier information registration process in the master information management unit 11 >>
Next, parts supplier information registration processing in the master information management unit 11 for registering parts supplier information using the input / output terminal 60, the forecast management apparatus 10, and the information management unit 50 will be described.
FIG. 24 is a diagram illustrating a processing procedure of parts supplier information registration processing in the master information management unit 11.

  The registrant logs in to the master information management unit 11 of the forecast management apparatus 10 using the input / output terminal 60 and selects parts supplier information registration from the menu screen, so that the parts supplier information registration screen shown in FIG. G3 is displayed on the input / output terminal 60. In the parts supplier information registration screen G3 in FIG. 25, the parts supplier code input field G3a, the parts supplier name, each input field of the forecast contract conclusion date, and the parts supplier code entered in the input field G3a are displayed. A search button G3b that is pressed when searching for the parts supplier information, and a registration button G3c that is pressed when registering the parts supplier information entered in the input fields of the parts supplier name and the forecast contract conclusion date are displayed. is there.

When searching for the parts supplier information of the desired parts supplier code, the registrant first uses the input / output terminal 60 to input the parts supplier code input field G3a on the parts supplier information registration screen G3 in FIG. After inputting a desired parts supplier code (such as “M001”), the search button G3b is pressed (S31 in FIG. 24).
Then, the input parts supplier code is transmitted to the forecast management apparatus 10 (S32), and the forecast management apparatus 10 uses the parts supplier code input by the registrant to check the parts supplier shown in FIG. The information data file 512 is referred to (S33), the parts supplier name and the forecast contract conclusion date are acquired (S34), transmitted to the input / output terminal 60 (S35), and displayed.

As a result of referring to the parts supplier information data file 512 of FIG. 14, when there is no corresponding parts supplier code, the parts supplier name and forecast contract conclusion date of the parts supplier information registration screen G3 of FIG. The input field is blank.
When registering the parts supplier information, the registrant inputs the parts supplier name and the forecast contract conclusion date into the input fields of the parts supplier name and the forecast contract conclusion date, and presses the registration button G3c ( S36 in FIG. Note that in S36 of FIG. 24, the information on either the parts supplier name or the forecast contract conclusion date displayed in the parts supplier code may be corrected and the registration button G3c may be pressed. In this case, the corrected parts supplier information is registered in the parts supplier information data file 512 of FIG.

  Then, the entered parts supplier name and the parts supplier information on the contract conclusion date are transmitted to the forecast management apparatus 10 (S37 in FIG. 24), and the forecast management apparatus 10 receives the parts transaction input by the registrant. The destination information is registered in the parts supplier information data file 512 of FIG. 14 of the information recording unit 50 (S38).

<< Notice Arrangement Processing in Arrangement Information Management Unit 12 >>
Next, the advancement arrangement processing in the arrangement information management unit 12 for making advance arrangements for products will be described with reference to FIG. FIG. 26 is a diagram illustrating a processing procedure of the advance notice arrangement process in the arrangement information management unit 12.
Here, the description will be made on the assumption that the advance notice has calculated the advance notice information of the product based on the future production plan.

For example, when the noticer logs in to the arrangement information management unit 12 of the forecast management apparatus 10 using the input / output terminal 60 of FIG. 1 and selects the notice arrangement of the product from the menu screen, the product shown in FIG. A notice screen G4 is displayed on the input / output terminal 60.
In the product notice screen G4 in FIG. 27, a search number input field G4a, a product code, a product notice quantity, a product notice period input field, and a notice information of the product of the notice number entered in the input field G4a are searched. There is a search button G4b that is pressed when the user presses, and a registration button G4c that is pressed when registering the product advance information entered in the input fields of the product code, the product advance quantity, and the product advance notice period.

When the registrant searches for the notice information of the product having the desired notice number, first, using the input / output terminal 60, the desired notice number, for example, in the notice number input field G4a of the product notice screen G4 of FIG. , “Y001” is input, and then the search button G4b is pressed (S41 in FIG. 26).
Then, the input notice number is transmitted to the forecast management apparatus 10 (S42), and the forecast management apparatus 10 refers to the product notice data file 501 of FIG. 3 of the information recording unit 50 with the notice number input by the registrant. (S43), the product code, the product notice quantity, and information on the product notice period are acquired (S44), transmitted to the input / output terminal 60 (S45), and displayed.

If the product code of the corresponding notice number does not exist as a result of referring to the product notice data file 501 of FIG. 3, the product code, product notice quantity, and product notice period input fields of the product notice screen G4 of FIG. Leave blank.
When registering the product advance notice information, the advance person inputs the product code, the product advance quantity and the product advance notice period on the product advance screen G4, and presses the registration button G4c (S46 in FIG. 26). Note that, in S46 of FIG. 26, any information on the displayed product code, product notice quantity, or product notice period may be corrected and the registration button G4c may be pressed. In this case, the corrected product notice information is registered in the product notice data file 501 of FIG.

Then, the entered product code, product notice quantity, and product notice information for the product notice period are transmitted to the forecast management apparatus 10 (S47 in FIG. 26), and the forecast management apparatus 10 receives the product notice input by the notice person. Information is registered in the product notice data file 501 of FIG. 3 of the information recording unit 50 (S48).
Specifically, registration in the product notice data file 501 is performed by checking whether or not the notice number to be registered already exists (S48A in FIG. 26), and when registered (Yes in S48A), FIG. The product notice data file 501 in FIG. 3, the notice part data file 505 in FIG. 7 and the total necessary parts data file 508 in FIG. 10 are referred to by the notice number, and the corresponding record is deleted (S48B). The product notice information input from G4 is registered in the product notice data file 501 of FIG. The record registered in the product notice data file 501 is registered in the notice part data file 505 of FIG. 7 using the parts table development result of the parts development device 20. Further, the record registered in the notice component data file 505 is combined with the arrangement component data file 507 of FIG. 9 created at the time of product arrangement in the process described later, and is registered in the total necessary component data file 508 of FIG. .
On the other hand, if it is determined in S48A of FIG. 26 that registration has not been completed (No in S48A), the process proceeds to S48C.

<< Product Arrangement Processing in Arrangement Information Management Unit 12 >>
Next, the product arrangement process in the arrangement information management unit 12 for the product purchaser to arrange products will be described with reference to FIG. FIG. 28 is a diagram illustrating a procedure related to product arrangement processing in the arrangement information management unit 12.
For example, when the arranger logs in to the arrangement information management unit 12 of the forecast management apparatus 10 using the input / output terminal 60 of FIG. 1 and selects the product arrangement from the menu screen, the product arrangement screen shown in FIG. G5 is displayed on the input / output terminal 60.
In the product arrangement screen G5 of FIG. 29, input is made in the input field G5a for the advance notice number, the input field G5b for the arrangement number, the input fields for the product code, the quantity of the product arrangement, the product arrangement period, and the input fields G5a and G5b. Search button G5c that is pressed when searching for the product notice / arrangement information of the given notice number or arrangement number, and the product arrangement information entered in the input fields of the product code, product arrangement quantity, and product arrangement period There is a registration button G5d that is pressed when registering.

The arranger first uses the input / output terminal 60 to input the advance notice number, for example, “Y001”, which has been previously notified in the advance number input field G5a of the product arrangement screen G5 in FIG. G5c is pressed (S51 in FIG. 28).
Then, the information of the inputted notice number is transmitted to the forecast management apparatus 10 (S52), and the forecast management apparatus 10 uses the notice number inputted by the arranger and the product notice data file 501 of FIG. (S53), the product code, the product notice quantity, and the product notice period are acquired (S54) and sent to the input / output terminal 60 (S55). The product code, the product arrangement quantity, and the product arrangement on the product arrangement screen G5 are obtained. Display each time. On the other hand, if the corresponding product code does not exist as a result of referring to the product notice data file 501 in FIG. 3, the input fields for the product code, product arrangement quantity, and product arrangement period in the product arrangement screen G5 in FIG. 29 are blank. And

Next, the arranger confirms the product code displayed on the product arrangement screen G5, the product arrangement quantity, and the product arrangement period, and corrects each item if there is a change. Further, after inputting a predetermined item, for example, the arrangement number “T001”, in the arrangement number input field G5b, the registration button G5d is pressed (S56).
Then, the input product arrangement information is transmitted to the forecast management apparatus 10 (S57), and the forecast management apparatus 10 registers the product arrangement information input by the arranger in the information recording unit 50 (S58).
Specifically, the product arrangement data file 506 in FIG. 8 is referred to by the arrangement number to check whether it has been registered (S58A in FIG. 28). If the arrangement number already exists (Yes in S58A), the product in FIG. The arrangement data file 506, the arrangement part data file 507 in FIG. 9 and the total necessary part data file 508 in FIG. 10 are referred to by the arrangement number, and the corresponding record is deleted (S58B).

Then, the product arrangement information input by the arranger is registered in the product arrangement data file 506 of FIG. 8 of the information recording unit 50, and the record registered in the product arrangement data file 506 is the result of the parts table expansion of the parts expansion device 20. Is registered in the arranged parts data file 507 of FIG. Further, the record registered in the arranged parts data file 507 is combined with the above-mentioned notice part data file 505 in FIG. 7 and updated with correction information, and is registered in the total necessary parts data file 508 in FIG. .
On the other hand, if it is determined in S58A of FIG. 28 that the input arrangement number has not been registered (No in S58A), the process proceeds to S58C.

<< Order processing in forecast quantity management unit 13 >>
Next, the ordering process in the forecast quantity management unit 13 that calculates the required number of orders will be described.
For example, the ordering process is performed every day at a time determined by a schedule.
The required order quantity is obtained by creating the part shortage quantity data file 511 shown in FIG. 13 and extracting a record in which the shortage quantity (before lot calculation) in the parts shortage quantity data file 511 is set. Can do.
The extracted record is ordered from the parts supplier by a well-known technique based on the ordering cycle defined in the part information data file 504 of FIG. 6, and the ordered record is registered in the ordering information data file 510 of FIG.
In addition, referring to the forecast takeover responsibility data file 517 of FIG. 19 with the ordered part code, if there is a record with takeover responsibility, an offset process is performed.

<< Forward Number Calculation Processing in Forecast Quantity Management Unit 13 >>
Next, the forecast number calculation process in the forecast quantity management unit 13 that calculates the forecast quantity will be described.
For example, the forecast number calculation processing for calculating the forecast quantity is performed every week at the time of the day of the week determined by the schedule.
In the forecast number calculation process, first, the part shortage quantity data file 511 shown in FIG. 13 is created. Next, the weekly parts shortage quantity data file 513 shown in FIG. 15, the order lot calculation data file 514 shown in FIG. 16, the forecast detailed information data file 515 shown in FIG. 17, and the forecast shown in FIG. An information data file 516 is created.
Also, the forecast takeover responsibility data file 517 shown in FIG. 19 is registered.

<< Forward presentation for parts suppliers in forecast presentation section 14 >>
Next, description will be given of forecast presentation for parts suppliers in the forecast presentation unit 14 that presents forecasts to parts suppliers.
For example, the parts supplier inputs the ID and password of authentication identification information given or set in advance from the forecast management system S to the initial screen of the forecast management system S using the input / output terminal 81 shown in FIG. When logging in, the menu screen (not shown) will be displayed if the entered ID and password are authorized and registered in the security data file (not shown). Then, it logs in to the forecast presentation part 14, and the forecast disclosure screen G6 shown in FIG.

The forecast release screen G6 shown in FIG. 30 includes display items of a parts supplier code, a part code, an order lead time (part lead time), a quantity confirmation lead time, a take-off postponement possible period, and a public week.
The data to be disclosed is only the parts supplier code to which the logged-in logged-in user belongs in the forecast information data file 516 of FIG.
That is, the forecast presentation unit 14 is configured to display only the public information on the forecast related to the logged-in component supplier. For example, the forecast disclosure screen G6 of FIG. 30 is displayed only for the parts supplier having the parts supplier code “M002”. On the other hand, with regard to a parts purchaser who forwards parts to all parts suppliers, the public information on the forecasts concerning all parts suppliers is displayed.

Further, by selecting the forecast quantity displayed on the forecast release screen G6 with a mouse or the like, a forecast detail release screen G7 shown in FIG. 31 is displayed.
It is assumed that the data to be disclosed is a part code of the selected forecast quantity and refers to the forecast detailed information data file 515 in FIG.
Further, as shown in FIG. 32, there are three types of forecast release screens: a forecast release screen G8 after 8 weeks, a forecast release screen G9 after 16 weeks, and a forecast release screen G10 after 24 weeks. It has a display function. Note that the published public screen is not limited to the forward public screens G8, G9, and G10 shown in FIG. 32, and it is a matter of course that an arbitrary period can be set as appropriate.

Furthermore, by selecting the forecast quantity displayed on the forecast details disclosure screen G7 in FIG. 31, a forecast number breakdown screen G11 shown in FIG. 33 is displayed.
Here, on the forecast number breakdown screen G11, the breakdown of the quantity is displayed in association with the takeover responsibility number and the ordering number, and the part supplier who is accessing can enter and set the reply period that is the expected arrival date. It is said.

<< Presentation of the due date compliance rate in the due date compliance rate presentation unit 15 >>
Next, the delivery date compliance rate display processing in the delivery date compliance rate display unit 15 for displaying the delivery date compliance rate of the purchased parts to the parts supplier will be described.
FIG. 35 is a diagram showing a delivery date compliance rate display screen H1 for referencing the delivery date compliance rate of company A.
In the parts receipt information data file 518 shown in FIG. 34, whether or not the ordered parts have been received on the requested delivery date in the parts receipt information management apparatus 45 of FIG. 1 that manages the arrival of parts from the parts supplier. Comparing the "Delivery date" with the "Received date" and dividing the number of requested delivery times in the symmetric period (required delivery date> = arrival date) by the total number of the order numbers in the symmetric period, and clarifying the delivery date compliance rate by month To do.

  The delivery date compliance rate on the delivery date compliance rate display screen H1 shown in FIG. 35 is based on normal ordering (ordering parts according to the part lead time for each part determined by the parts purchaser as the parts supplier) and short delivery ordering (part purchaser) Can be displayed separately for H1a and cumulative (normal order + quick delivery order) H1b, and the search period can also be set in units of months (yyy / mm, for example, December 2010) Have

The delivery date compliance rate display process for displaying the delivery date compliance rate display screen H1 is performed as follows.
When a part of order data in the order information data file 510 in FIG. 12 is received, it is managed by the part arrival information management device 45 and recorded as a record in the part arrival information data file 518 shown in FIG.
In the parts arrival information data file 518, “○” indicates that the arrival date matches the requested delivery date of the delivery request deadline (delivery within the requested delivery date), and “x” indicates that the delivery date is unmatched (when delayed). Classified and recorded. In addition, in the order information data file 510 of FIG. 12, what is ordered with the order lead time (part lead time) secured is “normal order”, and the short delivery time when the order lead time (part lead time) is not secured. Are classified as “short delivery orders”. For example, the record in the first line of the order information data file 510 in FIG. 12 is “normal order”, and the record in the third line is “short delivery order”.

  Then, the number of orders received in units of years (** year ** months) designated for each part supplier is extracted from the record of the parts arrival information data file 518 in FIG. Display on graph. In the “Delivery date compliance rate”, a value obtained by dividing the number of orders in which the required delivery date and the arrival date in the target period match “O” by the population of all the order numbers in the target period is displayed as a percentage (**%).

  When the parts supplier displays the delivery date compliance rate display screen H1, the initial screen of the forecast management system S is given or set in advance from the forecast management system S using the input / output terminal 81 of FIG. Enter the ID and password of the authentication identification information. Then, if the input ID and password are authorized ones registered in advance in a security data file (not shown), the user is logged in to the due date compliance rate presenting unit 15 of the forecast management apparatus 10. Note that if the entered ID and password are not registered and authorized in advance in a security data file (not shown), the forecast management system S cannot be accessed.

The parts supplier selects the display of the due date compliance rate on the displayed menu screen (not shown), and (yyy / mm) of the search period of the above conditions, and the normal order and the short delivery order which are the usage selections. When either H1a or cumulative H1b or both are selected and entered, a delivery date compliance rate display screen H1 shown in FIG. In FIG. 35, a case where a company A which is a parts supplier permitted to log in in advance sets the search period for the delivery date compliance rate to ** year ** month and selects both the delivery date compliance rates H1a and H1b. Show.
Similarly, the ID and password of authentication identification information given or set in advance from the forecast management system S are input and input from the parts purchaser as the ordering source using the input / output terminal 60 of FIG. If the ID and password are allowed, the delivery date compliance rate display screen shown in FIG. 35 is similarly displayed by logging into the delivery date compliance rate presentation unit 15 of the forecast management apparatus 10 and selecting the company A. H1 is displayed on the input / output terminal 60.

<< Delivery date display screen for parts supplier in delivery date compliance rate presentation unit 15 >>
The forecast management system S also has a function of displaying a delivery date delay status screen (distribution of delivery date delay days) H2 showing details of delivery date delay for each component supplier shown in FIG.
The delivery delay status screen H2 shows delivery delay days (+1 day (1 day delay), +2 days (2 days delay), +3 days (3 days delay), ..., +6 days or more (6 days or more delay)) The distribution can be selected and displayed as a normal order, a short delivery order, or a cumulative (normal order + short delivery order).

  The delivery date delay status screen H2 in FIG. 36 is displayed on the part arrival information management device 45 as described above, and the arrival date is unmatched from the record of the part arrival information data file 518 in FIG. Calculate the difference between the arrival date and the requested delivery date for “×”, and “+1 day” for the one day delay and “+2 day” for the two day delay,…, Those that are more than 6 days late are divided into “+6 days or more”, and the number and ratio (percentage: **%) are displayed in a bar graph. The display method can be displayed as “Normal Order”, “Short Delivery Order”, or “Regular Order + Accumulated Short Delivery Order” in the year / month (** Year ** Month) specified for each part supplier. is there.

  When the parts supplier displays the delivery delay status screen H2, the authentication identification information given or set in advance by the forecast management system S is displayed on the initial screen of the forecast management system S using the input / output terminal 81. Enter your ID and password. Then, when the input ID and password are registered and authorized in advance in a security data file (not shown), the user is logged in to the due date compliance rate presenting unit 15 of the forecast management apparatus 10. Note that if the entered ID and password are not registered and authorized in advance in a security data file (not shown), the forecast management system S cannot be accessed.

The parts supplier selects the display of the delivery delay status on the displayed menu screen (not shown), enters the search period (yyy / mm), and either regular orders or short delivery orders or cumulative or both 36 is displayed on the input / output terminal 81 as shown in FIG.
In FIG. 36, company A, a parts supplier, sets the search period to ** year ** month, selects “regular order + cumulative short delivery order”, and displays the delivery delay status screen H2. Shows the case.
Similarly, the ID and password of authentication identification information given or set in advance from the forecast management system S are input and input from the parts purchaser as the ordering source using the input / output terminal 60 of FIG. If the ID and the password are permitted, the delivery date compliance rate presentation unit 15 of the forecast management apparatus 10 is logged in and the company A is selected. Displayed on the input / output terminal 60.

<< Lead time presentation for parts suppliers in the lead time presentation unit 16 >>
Next, the lead time presentation process for the parts supplier in the lead time presentation unit 16 that presents the parts lead time of the parts to be purchased to the parts supplier will be described.
With regard to the lead time distribution of parts suppliers, as shown in FIG. 37, the distribution of part lead times can be displayed for every part unit or for each part unit of which usage frequency is large, medium, small, and extremely small. It has a function that can display the average lead time for each component unit.

  FIG. 37 (a) is a diagram showing a component lead time distribution display screen H3 for all components, and FIG. 37 (b) is a diagram showing a component lead time distribution display screen H3A for components that are frequently used. FIG. 37 (c) is a diagram showing a component lead time distribution display screen H3B for a component with a medium usage frequency, and FIG. 37 (d) shows a component lead time distribution display screen H3C for a component with a low usage frequency. FIG. 37 (e) is a diagram showing a component lead time distribution display screen H3D of a component having a minimum use frequency.

  The processing for displaying the component lead time distribution display screens H3, H3A, H3B, H3C, and H3D in FIG. 37 is executed by the contracted order lead time (stored in the component information data file 504 in FIG. (Component lead time) and the usage frequency (usage frequency: large, medium, small, extremely small) of each component stored in a storage unit (not shown) such as a table of the master information management unit 11 for each usage frequency. The order lead time (part lead time) is “1-5 days” (frequency of use: high), “-10 days” (frequency of use: medium), “˜30 days” (frequency of use: small), “31 days- The number of parts is totaled for each (usage frequency: local minimum), drawn on a pie chart, and displayed on the input / output terminal 60 and the input / output terminal 81 of FIG. The average lead time shown in FIG. 37 is calculated from the order lead time (part lead time) of the target number of parts for every part or for every part usage frequency (large, medium, small, extremely small).

  When the parts supplier displays the parts lead time distribution display screens H3, H3A, H3B, H3C, and H3D of FIG. 37, the forecast management system S uses the input / output terminal 81 to display the forecast management system S on the initial screen. The ID and password of authentication identification information given or set in advance from the system S are input. Then, if the input ID and password are authorized ones registered in advance in a security data file (not shown), the login is made to the lead time presentation unit 16 of the forecast management apparatus 10. Note that if the entered ID and password are not registered and authorized in advance in a security data file (not shown), the forecast management system S cannot be accessed.

The component supplier selects the display of the component lead time distribution on the displayed menu screen, and also uses the above-described component usage frequency conditions (the usage frequency for the entire component or each component unit: large, medium, small, minimal) 37), any one of the lead time distribution display screens H3, H3A, H3B, H3C, and H3D shown in FIG.
Similarly, the ID and password of authentication identification information given or set in advance from the forecast management system S are also input from the parts purchaser of the ordering party using the input / output terminal 60. Then, when the input ID and password are authorized ones registered in advance in a security data file (not shown), they are logged in to the lead time presentation unit 15 of the forecast management apparatus 10 in the same manner. One of the lead time distribution display screens H3, H3A, H3B, H3C, and H3D shown in FIG. 37 is displayed on the input / output terminal 60.

<< Presentation of changes in the delivery date compliance rate for parts suppliers in the delivery date compliance rate presentation unit 15 >>
Next, the delivery date compliance rate transition presenting process for the parts supplier in the delivery date compliance rate presentation unit 15 that presents the transition of the delivery date compliance rate of the parts to the parts supplier will be described.
FIG. 38 is a delivery date compliance rate line graph (change in delivery date compliance rate) H4 showing the change in the delivery date compliance rate by parts supplier, the actual purchase quantity (number) of parts, and the previous purchase quantity (number). FIG. 11 is a diagram showing a delivery date compliance rate / purchase quantity / order quantity transition screen G12 in which a purchase quantity line graph H5 and an order quantity bar graph H6 representing a transition in the number of orders (orders) of parts to parts suppliers are displayed. .

  As shown by the delivery date compliance rate line graph H4 of FIG. 38, the transition of the delivery date compliance rate by parts supplier is displayed by month with the search period set (yyy / mm / dd to yyyy / mm / dd). it can. "Normal order (blue) (represented by a solid line in FIG. 38)", quick delivery order (red) (represented by a broken line in FIG. 38), cumulative (normal order + short delivery order) (black) (by color) , Which is indicated by a one-dot chain line) ”, and has a function to understand the trend at a glance.

The delivery date compliance rate line graph H4 showing the transition of the delivery date compliance rate in FIG. 38 is displayed on the line graph using the “delivery date compliance rate” described above with reference to FIG.
When the parts supplier displays the delivery date compliance rate line graph H4 representing the delivery date compliance rate transition of FIG. 38, the forecast management system S displays the initial screen of the forecast management system S using the input / output terminal 81. The ID and password of authentication identification information given or set in advance are input. Then, if the input ID and password are authorized ones registered in advance in a security data file (not shown), the user is logged in to the due date compliance rate presenting unit 15 of the forecast management apparatus 10. Note that if the entered ID and password are not registered and authorized in advance in a security data file (not shown), the forecast management system S cannot be accessed.

  The parts supplier selects the display of the due date compliance rate on the displayed menu screen, and inputs the search period (yyyy / mm / dd to yyyy / mm / dd) of the above conditions to select the normal order for the application selection, short By selecting and inputting any of delivery date order, or cumulative, or normal / short delivery order / cumulative, the delivery date compliance rate line graph H4 of the delivery date compliance rate / purchase quantity / order number transition screen G12 shown in FIG. It is displayed on the input / output terminal 81. Note that the delivery date compliance rate line graph H4 shown in FIG. 38 shows a case where the parts supplier A accesses with the input / output terminal 81 and selects and displays all of normal / short delivery order / cumulative total.

  Similarly, an ID and password of authentication identification information previously assigned or set from the forecast management system S are input to the initial screen of the forecast management system S using the input / output terminal 60 from the parts purchaser. . Then, if the entered ID and password are authorized and registered in advance in a security data file (not shown), the user logs in to the due date compliance rate presentation unit 15 of the forecast management apparatus 10 and selects Company A. Accordingly, the delivery date compliance rate line graph H4 of the delivery date compliance rate / purchase quantity / order number transition screen G12 shown in FIG. 38 is displayed on the input / output terminal 60.

<< Presentation of purchase quantity for parts supplier in delivery date compliance rate presentation unit 15 >>
Next, the purchase quantity presentation processing for parts suppliers in the delivery date compliance rate presenting unit 15 that presents the transition of the actual number of parts purchased and the planned number of purchases of the preceding (future) parts to the parts supplier will be described.
The actual purchase quantity (number) of parts and the planned purchase quantity (number) of preceding (future) parts can be displayed in units of months, weeks, and days as shown in the purchase quantity line graph H5 shown in FIG. Therefore, the search period can be selected by setting the range (yyyy / mm / dd to yyyy / mm / dd).
For the purchase number line graph H5 of the purchase quantity, the actual results are displayed by accumulating the actual purchase quantity (number of parts received) in the part arrival information data file 518 of FIG. 34 managed by the part arrival information management device 45. In FIG. 5, the above-mentioned forecast quantity management unit 13 accumulates and displays the results every month.

  When the parts supplier displays the purchase quantity line graph H5 of FIG. 38 showing the transition of the number of parts purchased, the forecast management system S uses the input / output terminal 81 of FIG. The ID and password of authentication identification information given or set in advance from the management system S are input. Then, if the input ID and password are authorized ones registered in advance in a security data file (not shown), the user is logged in to the due date compliance rate presenting unit 15 of the forecast management apparatus 10. Note that if the entered ID and password are not registered and authorized in advance in a security data file (not shown), the forecast management system S cannot be accessed.

The parts supplier selects the display of the purchase quantity on the displayed menu screen, selects the condition (display unit (month / week / day), and the search period (yyyy / mm / dd to yyyy / mm /). dd)) is input, the purchase quantity line graph H5 of the delivery date compliance rate / purchase quantity / order quantity transition screen G12 shown in FIG.
Note that the purchase quantity line graph H5 shown in FIG.

Similarly, an ID and password of authentication identification information previously assigned or set from the forecast management system S are input to the initial screen of the forecast management system S using the input / output terminal 60 from the parts purchaser. . Then, if the entered ID and password are authorized and registered in advance in a security data file (not shown), the user logs in to the due date compliance rate presentation unit 15 of the forecast management apparatus 10 and selects Company A. Thus, the purchase quantity line graph H5 shown in FIG.
The purchase number line graph H5 shown in FIG. 38 exemplifies the cumulative total of the normal order and the short delivery order. You may comprise so that either the total of the sum of normal order and short delivery order, and all of normal / short delivery order / cumulative can be selected and displayed.

<< Presenting the number of orders for parts suppliers in the delivery date compliance rate presentation unit 15 >>
Next, the order quantity presentation process for parts suppliers in the delivery date compliance rate presenting unit 15 that presents the transition of the number of parts ordered to the parts suppliers will be described.
As for the number of orders from the parts purchaser to the parts supplier, the past order record (solid line) and the preceding (future) planned order (dotted line) are shown as the number of orders as shown in the order number bar graph H6 shown in FIG. It can be displayed as a bar graph in units of months, weeks, and days.
As shown in FIG. 38, the order number bar graph H6 shown in FIG. 38 sets the search period as a range (yyy / mm / dd to yyyy / mm / dd). Monthly display is possible, and the cumulative display (the total number of orders (orders) including regular orders and short delivery orders) and the ability to display in two ways: distinction between normal orders and short delivery orders have.

  The order number bar graph H6 in FIG. 38 showing the actual number or order of parts ordered is divided into “normal order” and “short delivery order” based on the order number described in FIG. Also, the planned order number is displayed by accumulating the number of parts scheduled to be ordered monthly from the forecast quantity management unit 13 described above.

  38. When the parts supplier displays the order number bar graph H6 shown in FIG. 38, the authentication given or set in advance from the forecast management system S to the initial screen of the forecast management system S using the input / output terminal 81. Enter the ID and password of the identification information. Then, if the input ID and password are authorized ones registered in advance in a security data file (not shown), the user is logged in to the due date compliance rate presenting unit 15 of the forecast management apparatus 10. Note that if the entered ID and password are not registered and authorized in advance in a security data file (not shown), the forecast management system S cannot be accessed.

The parts supplier selects the display of the number of orders on the displayed menu screen (not shown), selects the display unit (month / week / day), and the search period (yyyy / mm / dd.about. yyyy / mm / dd), and select and enter the cumulative display (no distinction between normal order and short delivery order), normal order, and short delivery order distinction. The order quantity bar graph H6 of the purchase quantity / order quantity transition screen G12 is displayed on the input / output terminal 81.
FIG. 38 shows a case where the company A accesses and selects and displays normal order and short delivery order distinction.
Similarly, the ID and password of the authentication identification information given or set in advance from the forecast management system S on the initial screen of the forecast management system S using the input / output terminal 60 from the parts purchaser of the supplier. Enter. Then, if the entered ID and password are authorized and registered in advance in a security data file (not shown), the user logs in to the due date compliance rate presentation unit 15 of the forecast management apparatus 10 and selects Company A. Thus, the order number bar graph H6 shown in FIG. 38 is displayed on the input / output terminal 60 in the same manner.
Note that the order number bar graph H6 shown in FIG. 38 can be configured so that the number of orders for normal orders and the number of orders for quick delivery orders can be displayed individually.

<< Presentation of purchase amount for parts supplier in delivery date compliance rate presentation unit 15 >>
Next, the purchase price presentation process for parts suppliers in the delivery date compliance rate presentation unit 15 that presents the purchase price of parts to the parts supplier will be described.
FIG. 39 is a delivery date compliance rate line graph H4 showing the transition of the delivery date compliance rate for each part supplier, the actual purchase quantity (number) of parts, and the purchase quantity line graph H5 of the preceding purchase planned quantity (number), It is a figure which shows the due date adherence rate / purchase quantity / purchase amount transition screen G13 on which a purchase amount bar graph H7 showing the transition of the purchase amount of parts is displayed.
The actual purchase price and the expected purchase price of the parts can be displayed as a bar graph in units of months, weeks, and days, as in the purchase price bar graph H7 shown in FIG. 39, and the range setting (yyyy / mm / dd.about. yyyy / mm / dd), a search period can be selected.

  The purchase price bar graph H7 representing the actual purchase price and the schedule of the part purchase source parts is shown in FIG. 34 for the part unit price of each part recorded in the storage unit such as a table managed by the master information management unit 11 in FIG. The total of the purchase amount determined by the product of the number of arrivals in the parts arrival information data file 518 is displayed as a bar graph. Further, the planned purchase price is calculated from the information on the unit unit price of the master information management unit 11 and the planned purchase quantity of the forecast quantity management unit 13, and is accumulated every month and displayed as a bar graph.

  When the parts supplier displays the purchase price of the parts, the ID and password of authentication identification information given or set in advance from the forecast management system S are input using the input / output terminal 81. Then, if the input ID and password are authorized ones registered in advance in a security data file (not shown), the user is logged in to the due date compliance rate presenting unit 15 of the forecast management apparatus 10. Note that if the entered ID and password are not registered and authorized in advance in a security data file (not shown), the forecast management system S cannot be accessed.

The parts supplier selects the display of the purchase price on the menu screen (not shown) to be displayed, selects the display unit (month / week / day) of the above conditions, and the search period (yyyy / mm / dd to yyyy / mm / dd)), the purchase amount bar graph H7 of the delivery date compliance rate / purchase quantity / purchase amount transition screen G13 shown in FIG. 39 is displayed on the input / output terminal 81.
The purchase price bar graph H7 shown in FIG. 39 shows a case where the company A accesses and selects and displays “month” as a display unit.
Similarly, the ID and password of the authentication identification information given or set in advance from the forecast management system S on the initial screen of the forecast management system S using the input / output terminal 60 from the parts purchaser of the supplier. Enter. Then, if the entered ID and password are authorized and registered in advance in a security data file (not shown), the user logs in to the due date compliance rate presentation unit 15 of the forecast management apparatus 10 and selects Company A. Thus, the purchase amount bar graph H7 shown in FIG. 39 is displayed on the input / output terminal 60 in the same manner.

In the above-described embodiment, the parts supplier accesses the parts supplier as shown by the case where the parts supplier A accesses with the ID and password assigned or set in advance from the forecast management system S. In such a case, it is configured so that only information relating to the parts traded by Company A can be referred to. That is, the parts supplier has the authority to refer only to the information on the parts related to the company in the security data file (not shown) in the ID and password to be given.
On the other hand, a part purchaser who purchases a part from a parts supplier is purchased with a security data file (not shown) with an ID and password assigned or set in advance from the forecast management system S. The authority to refer to all information related to the part is set.
Of course, the authority of the ID and password to be given can be set as appropriate and is not limited to those exemplified. For example, when the parts supplier forms a group company, the authority to refer to the information in the group may be set with an ID and a password.

<Effect>
According to the above configuration, the component lead time can be shortened by disclosing the forecast information to the component supplier.
In addition, by disclosing the delivery date compliance rate of the actually purchased parts, the breakdown of regular order and short delivery order, already purchased quantity / amount, planned purchase quantity, and planned purchase price, the delivery date compliance rate to parts suppliers The accuracy of forecast information can be further improved at the parts purchaser.
Moreover, as shown in FIG. 38, by disclosing the past purchase results by the transition of the delivery date compliance rate, it is possible to further improve the delivery date compliance rate of the parts supplier.

In addition, regarding the order contents of the parts purchaser, it is possible to further improve the accuracy of forecast information by clearly disclosing whether the order is a normal order or a short delivery date.
In addition, as shown in FIG. 37, in the component lead time, since the distribution of the past and the current component lead time can be disclosed according to the usage frequency, it is possible to further reduce the component lead time.
In addition, since the purchase quantity and purchase price can be selected within the search period from the purchase record to the current situation, and further to the preceding schedule, it is possible to improve the accuracy of budgeting.

In the above-described embodiment, ID and password are exemplified as authentication-identifiable information. However, identification information for biometric authentication such as vein and iris may be used, and authentication-identifiable information that can determine whether access to the forecast management system S is possible. If so, it goes without saying that other than the ID and password may be applied.
In the above-described embodiment, the month, week, and day are exemplified as the unit of period. Of course, a half year other than the month, week, and day, a full year, a plurality of years, and the like can be appropriately selected and set. is there.

In a production system where customer specifications are generated individually, if the component lead time of the parts that make up the product is larger than the product lead time required by the customer, it is essential to shorten the component lead time. It is necessary to present forecasts to parts suppliers.
However, shortening the component lead time of the component and shortening the product lead time including the purchase of the component has a problem that it becomes a part supplier's request. In order to solve this problem, there is a possibility of applying the business model according to this patent.

10 Forecast management device (unordered part presentation means, already ordered parts presentation means, delivery date compliance rate presentation means, parts arrival / plan information display means, purchase price display means, order number display means, authentication availability judgment means)
13 Forecast Quantity Management Department (unordered part presentation means, already ordered parts presentation means)
14 Forecast presenting section (unordered part presenting means, already ordered parts presenting means recognition, proof approval determination means)
15 Delivery date compliance rate presentation part (parts arrival / plan information display means, purchase price display means, proof approval / disapproval judgment means)
16 Lead time presentation unit (component lead time display means, proof approval / disapproval judgment means)
45 Parts arrival information management device 50 Information recording part (unordered parts presentation means, already ordered parts presentation means, delivery date compliance means, parts arrival / schedule information display means, purchase price display means, order quantity display means)
60 I / O terminal (display device)
81 Input / output terminal (display device) of parts supplier
518 Parts arrival information data file (storage unit)
H1 Delivery date compliance rate display screen (Display of delivery date compliance rate)
H2 delivery delay details screen (distribution of delivery delay days)
H3, H3A, H3B, H3C, H3D Lead time distribution display screen (part lead time distribution, part lead time average)
H4 Delivery date compliance rate line graph (Changes in delivery date compliance rate)
H5 Purchase number line graph (Parts purchased and actual purchases)
H6 Order number bar graph (Normal order and short delivery order are distinguished)
H7 Purchase amount bar graph (Actual purchase amount and planned purchase amount of parts)
S Forecast management system

Claims (25)

A forecast management system that publishes information on parts to parts suppliers who purchase or plan to purchase parts,
Based on the requested delivery date of the finished product, the order schedule information is expanded to the parts constituting the finished product to clarify the individual deadlines for the parts, and the parts deadline for purchasing the parts is determined based on the deadlines for the parts. An unordered part presenting means for first presenting on the display device;
An already-ordered part presenting means for presenting a necessary time limit of an already ordered part constituting the finished product on a display device;
Based on the past parts arrival information stored in the storage unit, the delivery date compliance rate is set to a normal order that is an order that keeps a predetermined delivery date, or a short delivery order that is an order that is shorter than the default delivery date, or the normal delivery A forecast management system comprising: a delivery date compliance rate display means for displaying on a display device according to a cumulative total of an order and the short delivery date order. The forecast management system according to claim 1,
The said delivery date compliance rate display means displays the transition of the said delivery date compliance rate on the said display apparatus for every predetermined period unit. The forecast management system characterized by the above-mentioned. In the forecast management system according to claim 1 or 2,
The delivery date compliance rate display means displays, on the display device, the distribution of the delivery delay days of the received parts according to the normal order, the short delivery order, or the cumulative total of the normal order and the short delivery order. A forecast management system characterized by this. The forecast management system according to claim 1,
A component lead time display that displays a distribution of component lead times, which is a period from part ordering to delivery, and an average of the component lead times on a display device, according to the entire parts constituting the finished product or the frequency of use of each part. A forecast management system comprising means. The forecast management system according to claim 1,
Based on the past part arrival information and the order schedule information, a part arrival / schedule information display means for displaying the actual purchase quantity of the part and the expected purchase quantity of the part in a predetermined period unit is provided. A forecast management system characterized by The forecast management system according to claim 1,
Based on the past part arrival information and the order schedule information, the actual order quantity and the order schedule number of parts, in which the regular order and the quick delivery order are distinguished in a predetermined period unit, and the normal order And an order number display means for displaying on a display device as one of the sums of the sums of the short delivery date and the short delivery date order. The forecast management system according to claim 1,
Based on the past part arrival information and the order schedule information, a purchase price display for displaying a purchase price result of the part received in the past and a planned purchase price of the part scheduled to be ordered on a display unit in a predetermined period unit A forecast management system comprising means. The forecast management system according to claim 1,
There is a plurality of the finished products, and when there is a common part for each required part, the quantity of each part is totaled and released to the parts supplier for each part. The forecast management system according to claim 1,
When authenticable identification information that enables access to the forecast management system previously assigned or set to a user is input to the display device, the authority information defined by the authenticable identification information is A forward management system, comprising: an authentication enable / disable determining unit that does not disclose information when the authentication enable identification information is not input to the display device while being displayed on a display device. The forecast management system according to claim 1,
The unordered part presentation means, the already ordered parts presentation means, and the delivery date compliance rate display means publish information on the parts to be purchased to the parts supplier who purchases each of the parts. Management system. The forecast management system according to claim 1,
The unordered part presentation means and the already ordered parts presentation means are:
Part lead time, which is the period from part ordering to delivery, quantity confirmation lead time, which is the number of days for which the publication of the forecasted parts takes place, and the period in which the part can be postponed A forecast management system that publishes information using postponement possible periods. The forecast management system according to claim 1,
The already ordered parts presenting means and the unordered parts presenting means are:
A forecast management system that presents all three systems simultaneously, up to 8 weeks ahead, 16 weeks ahead, every 4 weeks up to 24 weeks ahead, and so on. A control method of a forecast management system that publishes information on the parts to parts suppliers who purchase or plan to purchase parts,
The unordered part presentation means develops from the order schedule information to the parts constituting the finished product based on the required delivery date of the finished product to clarify the individual deadlines for the parts, Present the parts on the display to the parts supplier who purchases the parts,
The already-ordered part presentation means presents the necessary time limit of the already ordered parts constituting the finished product on the display device,
The delivery date compliance rate display means is a normal order that is an order that keeps the delivery date compliance rate based on the past parts arrival information stored in the storage unit, or an order that is shorter than the delivery date. A control method for a forecast management system, characterized in that a short delivery date order or a cumulative total of the normal order and the short delivery date order is displayed on a display device. In the control method of the forecast management system according to claim 13,
The said delivery date compliance rate display means displays the transition of the said delivery date compliance rate by the said display apparatus per predetermined period unit. The control method of the forecast management system characterized by the above-mentioned. In the control method of the forecast management system according to claim 13 or 14,
The delivery date compliance rate display means displays, on the display device, the distribution of the delivery delay days of the received parts according to the normal order, the short delivery order, or the cumulative total of the normal order and the short delivery order. A control method for a forecast management system. In the control method of the forecast management system according to claim 13,
The component lead time display means displays the distribution of the component lead time, which is the period from ordering of the component to delivery, and the average of the component lead times according to the entire components constituting the finished product or the frequency of use of each component. A control method of a forecast management system, characterized by being displayed on the screen. In the control method of the forecast management system according to claim 13,
The parts arrival / schedule information display means displays the purchase quantity actual result of the part and the scheduled purchase quantity of the part on a display unit in a predetermined period based on the past part arrival information and the order schedule information. A control method of a forecast management system characterized by the above. In the control method of the forecast management system according to claim 13,
The order quantity display means distinguishes between the normal order and the short delivery order in a predetermined period unit, based on the past part arrival information and the order schedule information, in order of the number of parts ordered and the planned order quantity. A control method for a forecast management system, which is displayed on a display device in any one of a total of a sum of the normal order and the quick delivery order. In the control method of the forecast management system according to claim 13,
The purchase price display means displays the purchase price record of the parts received in the past and the planned purchase price of the parts scheduled to be ordered in a predetermined period based on the past parts arrival information and the order schedule information. A control method of a forecast management system, characterized by being displayed on the screen. In the control method of the forecast management system according to claim 13,
A method for controlling a forecast management system, wherein when there are a plurality of the finished products and there is a common part for each required part, the quantity of each part is totaled and the part is disclosed to the parts supplier. In the control method of the forecast management system according to claim 13,
The authentication availability determination means
When authenticable identification information that enables access to the forecast management system previously assigned or set to a user is input to the display device, the authority information defined by the authenticable identification information is A control method for a forecast management system, wherein the information is not disclosed when the authentication enable identification information is not input to the display device while the information is disclosed on the display device. In the control method of the forecast management system according to claim 13,
The unordered part presentation means, the already ordered parts presentation means, and the delivery date compliance rate display means publish information on the parts to be purchased to the parts supplier who purchases each of the parts. Management system control method. In the control method of the forecast management system according to claim 13,
The unordered part presentation means and the already ordered parts presentation means are:
Part lead time, which is the period from part ordering to delivery, quantity fixed lead time, which is the number of days for which the forecast is released, and the period in which the part can be postponed. A control method for a forecast management system, wherein information is disclosed using a postponement possible period. In the control method of the forecast management system according to claim 13,
The already ordered parts presenting means and the unordered parts presenting means are:
A control method for a forecast management system characterized by presenting all three systems simultaneously, up to 8 weeks ahead, 16 weeks ahead, every 4 weeks up to 24 weeks ahead, and so on.   25. A forecast management system program for causing a computer to execute the forecast management system control method according to any one of claims 13 to 24.

Images