JP2010061317A - Forecast management system and program thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To shorten the ordering lead time of components by selectively displaying forecast information. <P>SOLUTION: The forecast management system is provided with: a storage means 50 for storing a product code for identifying each complete product and component codes and the information of components; unplaced order information presentation means 10, 14, 20, 30 and 50 for presenting unordered component information including the due dates of the respective components; actual order information presentation means 10, 14, 30, 40 and 50 for presenting the component information including the due dates of the actual order arrangement completion by using the component codes; and publication means 10, 14, 60, 70, 80 and 81 for disclosing the component information of the unplaced order information presentation means and the component information of the actual order information presentation means. The publication means releases information selected from among the first information of the ordered and undelivered components whose ordering is held, the second information of the unordered and ordering scheduled components, the third information of the components obtained by combining the components whose ordering is held with the ordering scheduled components, and the fourth information acquired by arranging the first information and the second information and the third information to the public. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a forecast management system and its program for parts delivery date management in production management.

Conventionally, there are Patent Documents 1, 2, and 3 as methods for procurement of forecasts and parts.
In Patent Document 1, as a method for easily following parts procurement to a production plan changed after an order for necessary parts, a reservation order is issued and a final order is issued thereafter. In addition, a system that sets and issues a pre-order for a quantity that has not been allocated is supported.
In Patent Document 2, the number of procurement is calculated based on forecast information and past arrangement information.
In Patent Document 3, parts necessary for a product are purchased in a batch arrangement in consideration of a production method based on order information and customer specifications related to the product, that is, the parts are collectively purchased in units of models.
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, the procurement order form is more than doubled and complicated, and the parts supplier requires more than twice the labor.
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 batches in consideration of a production method based on order information and customer specifications, and is not suitable for high-mix low-volume production.
In these conventional methods, if the lead time of the parts that make up the product is large compared to the product lead time requested by the customer, an order must be arranged before the time of use of the part becomes clear based on past usage results. Yes.

For this reason, a deviation occurs between the actual required number and the ordered order number, and if the required number is less than the ordered order number, excess inventory occurs. On the other hand, if the required number is greater than the number of orders, the order lead time will be broken due to a shortage of parts.
Therefore, the number of management man-hours such as schedule realignment at parts suppliers and internal related departments is increasing.

As described above, the order lead time from the order of the parts constituting the product to the delivery of the parts is large with respect to the product lead time from the product request to the product shipment requested by the customer, and the customer specifications are generated individually. In such a production system, the lead time required by the customer is generally met by ordering based on parts inventory and past usage records. However, from the management point of view, it is necessary to reduce the inventory of parts, and the order lead time is required to be shortened.
In addition, parts suppliers also have different production backgrounds for handling parts such as different products that use forecasted parts and newly forecasted parts. There is an obstacle to the execution. Therefore, it is necessary to provide forecast information suitable for the production background to the parts supplier and eliminate the waste of the parts procurement period.

For this reason, the parts supplier will have information regarding the order for the part to be traded, information on the order placed, order information (confirmed quantity: confirmed to be ordered) + future part order. If all the situations are required, ordering schedule information (quantity confirmation: that it is decided to place an order) + if only the situation related to future parts ordering is required, etc. Different information according to the timing of information collection There is a need to search for a parts supplier who is a supplier of parts.
SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and it is an object of the present invention to provide a forecast management system and a program therefor that can shorten the ordering time of parts by allowing a business partner to select and display the forecast information of the parts.

  In order to achieve the above object, the forecast management system according to the first aspect of the present invention stores a product code for identifying each finished product, a part code for identifying individual parts constituting each finished product, and part information. Storage means, and unordered information presenting means for presenting unordered part information including a necessary time limit of each part developed for a finished product at a part level using a product code and a part code based on a required delivery date; The actual order information presenting means for presenting the part information including the necessary time limit of the parts developed at the part level already arranged for the actual order using the part code, the part information of the unordered information presenting means, and the part information of the actual order information presenting means Publishing means for publishing, wherein the publishing means includes first information relating to an unordered part that has been ordered and undelivered, second information relating to an unordered part to be ordered, and an unordered part. And any information selected from the third information related to the parts including the parts to be ordered, and the fourth information which is information in which the first information, the second information, and the third information are arranged. Is published.

  The program of the forecast management system according to the second aspect of the invention stores in a storage means a product code for identifying each finished product, a part code for identifying individual parts constituting each finished product, and information on the parts. The first procedure is a second procedure for presenting unordered part information including the necessary deadlines for individual parts developed using the product code and part code on the basis of the required delivery date. A third procedure for presenting part information including the necessary time limit of the part developed to the order-arranged part level by using a part code, first information on an unordered part that has been ordered, and unordered The second information about the parts scheduled to be ordered, the third information about the parts including the remaining parts and the parts scheduled to be ordered, the first information, the second information, and the third information are arranged in parallel. And to execute the published procedure to expose any of the information in a selected one of the fourth information information.

  Note that “expanded to the part level based on the required delivery date of the finished product” in claim 1 corresponds to, for example, FIGS. In addition, “presenting unordered part information including the necessary time limit for each part” in claim 1 is, for example, the display of the “quantity determination” column and the “publication only” column in FIGS. For example, “presenting the necessary time limit of the part developed at the part level where the actual order has been arranged” in claim 1 corresponds to the display of the “order” column in FIGS.

  ADVANTAGE OF THE INVENTION According to this invention, since the business partner can select and display the forecast information of a part, the forecast management system and its program which can shorten the order lead time of a part are realizable.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
<< Overview of Forecast Management System S >>
The forecast management system S of the embodiment according to the present invention discloses a demand release of the planned purchase quantity of IC (Integrated Circuit), capacitor, etc. of parts included in the product based on the advance notice of the expected number of products such as printed circuit boards. Demand forecasting, that is, forecasting, releasing to parts suppliers that are parts suppliers, and using products for orders at parts suppliers who are ordering products and making products even in high-mix low-volume production This makes it possible to properly order and stock the parts to be sold.

<< Overall Configuration of Forecast Management System S >>
The overall configuration of the forecast management system S will be described with reference to the drawings.
FIG. 1 is a block diagram showing an overall configuration including a forecast management apparatus 10 of a forecast management system S according to an embodiment of the present invention.

  As shown in FIG. 1, a forecast management apparatus 10 that performs forecasting of used parts to a parts supplier that is an ordering party of parts constituting a product is performed via a communication network 70 such as a LAN (Local Area Network). A parts development device 20 that develops each product into a used part, an inventory management device 30 that manages the receipt and delivery of stock parts, a purchased product management device 40 that manages parts to be ordered, and an information recording unit that stores various data files described later 50 and an input / output terminal 60 which is placed at the parts ordering source and used for confirming the number of forecasts.

Here, the parts deployment device 20, the inventory management device 30, and the purchased product management device 40 are stored in an auxiliary storage device such as a hard disk of a server (not shown) corresponding to each of the devices 20, 30, and 40. This is realized by each corresponding processing unit executing a corresponding program.
In addition, the parts expansion | deployment apparatus 20, the inventory management apparatus 30, and the purchased goods management apparatus 40 may each be stored in the auxiliary storage device of another server, and may be stored in the auxiliary storage device of the same server. In addition, a plurality of devices may be stored in the auxiliary storage device of the same server, and the form in which each device 20, 30, 40 is stored is not particularly limited.
Further, the forecast management apparatus 10 is connected to the input / output terminal 81 of the parts supplier via a communication network 80 such as the Internet so that data communication with the input / output terminal 81 of the parts supplier is possible.
Here, although the input / output terminal 60 and the input / output terminal 81 are illustrated as one terminal, it is needless to say that there may be any plural number.

<< Forward Management Device 10 >>
Next, the configuration of the forecast management apparatus 10 will be described in detail.
The forecast management apparatus 10 is realized by a CPU executing a forecast management program. As shown in FIG. 1, a master information management unit 11, an arrangement information management unit 12, and a forecast quantity management unit 13 are provided. , And the forecast presentation unit 14 are implemented as corresponding programs.

For example, the forecast management apparatus 10 is stored in an auxiliary storage device such as a hard disk of a server (not shown), and the installed forecast management program is executed by the CPU. Each function of the information management unit 12, the forecast quantity management unit 13, the forecast presentation unit 14, and the like is realized.
Here, the forecast management program may be stored in a separate server for each management unit, or a plurality of management units may be stored together in a single server. .
In addition, each program of the component development device 20, the inventory management device 30, and the purchased product management device 40 may be stored in a separate server with each part of the forecast management program, or a plurality or all of the management units 11, 12, 13 and the forecast presentation unit 14 may be stored together in the same server.

<< Information Recording Unit 50 >>
The information recording unit 50 is a storage device such as a memory or a hard disk.
FIG. 2 is a conceptual configuration diagram showing the configuration of the information recording unit 50 shown in FIG.
As shown in FIG. 2, 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 parts information data file 504, a notice parts data file 505, and a product arrangement data file. 506, arranged parts 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, An order lot calculation data file 514, a detailed forecast information data file 515, a forecast information data file 516, and a forecast takeover responsibility data file 517 are stored.
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 provides notice of a required product.
As shown in FIG. 3, 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, and the quantity of the product of the product code that has been noticed by the notice number. A certain product notice quantity and a product notice necessity period which is a required delivery date of the product notice quantity are associated with each other.

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 using a part development technique for products, and indicates what parts each product uses.
As shown in FIG. 4, 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 parts 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.
The product lead time is a period from the start of product production work to completion in the state where parts necessary for producing the product are prepared, and a number representing the number of days is used.
As shown in FIG. 5, the product production information data file 503 is associated with the product code and the production lead time of the product 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 part information data file 504 indicates the following attributes of each part.
As shown in FIG. 6, in the part information data file 504, the part code, the part name of the part code, the order lot which is the minimum unit order quantity to the parts supplier, and the number of days from the order date to the delivery date are displayed. The order lead time that represents the quantity, the quantity confirmation lead time that represents the period in which the responsibility for taking over the part occurs in terms of the number of days from the date when the forecast was released, the period that the part can be postponed, and the part ordering cycle. 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, the quantity confirmation lead time, and the take-off possible period are contracts with parts suppliers in 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 was published and the quantity confirmation lead time, the forecast quantity released within the period will be , Take over responsibility occurs. The responsibility for taking over refers to the responsibility for taking out the parts for which the ordering party has cast. This is because, when the ordering side forecasts a part, the parts supplier side prepares the forecasted part in advance, and therefore defines the responsibility for taking over.
When the responsibility for taking over occurs, the date that the order lead time is subtracted from the required delivery date for the part is defined as the planned order date. Issue a certificate.

Even if the forecast quantity decreases due to the occurrence of takeover responsibility and there is no need to place an order, it is necessary to place an order by the takeover responsibility from the planned order date to the date when the postponement period, which is the grace period for parts, elapses. Don't be.
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. For forecast quantities in the period up to the 11th, responsibility for taking over occurs. If the requested delivery date is 10 January, 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 an interval of parts ordering to a parts supplier, that is, a part ordering cycle to 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 the part orderer until it can be used for production of a product through a process 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 is performed assuming responsibility for taking over. In the case of “Yes”, the takeover responsibility is generated according to the above-mentioned contract, but in the case of “No” Will only disclose a pile of required delivery dates for parts, and will not be responsible for taking over.

  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”, the order lead time from the order date to the delivery date is “30 days”, forecast The quantity confirmation lead time indicating the period in which the responsibility for taking over will be generated after the release is “60 days”, the postponement period that is a postponement period of parts taking is “30 days”, and the ordering cycle that is the ordering cycle is “7 days” The number of production acceptance test days that can be used for production from the arrival of parts to the acceptance inspection, etc. is “0 days”, the parts receipt destination code is “M001”, and the forecast target part flag is “Yes”. This indicates that the part is a cast 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.
As shown in FIG. 7, the notice part data file 505 includes the notice number, the product code of the product included in the notice number, the notice number of the consistent NO allocated for each noticed product code, the product Are associated with the part code of the part, the part notice quantity of the part of the part code, and the part notice period of the part.

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 noticed is assigned the notice technique number “01” since the product code “S001” is first, and the notice number “Y002” has been given a notice. The product code “S001” of the product is assigned the notice branch number “02” because the product code “S001” is second.
The part notice quantity is a part quantity necessary for producing a product having the product code noticed by the notice number. Each of the product notice quantity in the product notice data file 501 in FIG. This is a calculated value obtained by expanding the parts table by the product of the quantity 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 required delivery date of parts necessary for producing a product having a product code notified by a 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. 3, and the part information data file shown 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 arrangement.
As shown in FIG. 8, the product arrangement data file 506 includes an arrangement number for identifying the arrangement data of the product, a product code, a product arrangement quantity indicating the quantity of the product of the product code arranged by the arrangement number, and the arrangement quantity. Is associated with the required product delivery deadline.
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 a 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 expansion of the arranged products described above to the parts level.
As shown in FIG. 9, the arrangement part data file 507 includes the arrangement number (see FIG. 8), the product code of the product arranged by the arrangement number, and the arrangement number of the consistent NO assigned to each arranged product code. , The part code of the part included in the product, the part arrangement quantity of the part, and the part arrangement deadline which is the delivery date when the part is required are associated. 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 in which “S002” appears first, the arrangement branch number “A1” is assigned, and the arrangement number “T003” Since the product code “S002” arranged in (2) is the arrangement number in which “S002” appears second, the arrangement branch number “A2” is assigned.
The part order quantity is a part quantity to be arranged to produce a product having the product code arranged by the order number. The product order quantity in the product order data file 506 in FIG. 8 and the product part table data file 502 in FIG. This 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 further, 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 parts data file 508 is created by combining the notice parts data file 505 in FIG. 7 and the arranged parts 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 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 a product that uses the parts ordered by the ordering party.
The parts that are ordered by the ordering party to the parts supplier are the parts used by the ordering party for the products produced by the ordering party, and when the ordering company outsources the product production and the subcontract manufacturer of the product manufactures the product. Includes parts used.

As shown in FIG. 10, the total necessary parts data file 508 includes an arrangement number or an arrangement number / announcement number of a notice number, the product code, a branch number, a part code of a part included in the branch number, and a part of the part. The quantity and the part period of the part are associated with each other.
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).
In FIG. 10, for the product with the product code “S001”, the part with the part code “B001”, the part with “B002”, and the part with “B003” are shown in the branch number “01” of the product code “S001”, respectively. As shown, it is necessary for the same period of “07/05/25” shown in the part period.

<< 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.
As shown in FIG. 11, 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 storage of parts by a well-known technique.
For example, the inventory quantity of the part code “B001” is 12 pieces.
The ordering party also receives the manufacturer's inventory information through the communication network 80 or the like for the inventory of the part that the manufacturer who requests the parts supplier to produce the product using the part to be forecasted. Assume that it is 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.
As shown in FIG. 12, the ordering information data file 510 has arrived from the ordering number as the unit of ordering, the part code of the part ordered by the ordering number, the order quantity when ordered by the order number, and the order quantity. The remaining order quantity after reducing the quantity, the order date, which is the date of placing an order with the parts supplier, the order lead time of the number of days from the order date to the delivery date, the required delivery date of the deadline requested to the parts supplier, the following key points The order delivery period, which is the difference between the requested weekly delivery date and the order delivery date, and the delivery date of the deliverable date answered by the parts supplier are associated with the order number. Note that parts may be delivered from parts suppliers on the day before the answer delivery date.

Here, the order lead time is the order lead time obtained by referring to the part information data file 504 of FIG. The essential year is defined as a consistent 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, as described above, and is an item for distinguishing between orders with the order lead time secured in the process described below and short delivery orders with no order lead time secured. It is. That is, when the ordering period is shorter than a predetermined ordering lead time that is a period from the ordering date to the delivery date, the order is shortly delivered and is later expressed as a crack in the lead time.
This order information data file 510 (see FIG. 12) is created from the planned order quantity in the part shortage quantity data file 511 in FIG. 13 below, and the ordering person can order the part code, order quantity, and requested delivery date at any timing. May be specified.

<< 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 parts shortage quantity data file 511 shows detailed information for each necessary part for each required part of the delivery date, which is a necessary deadline for the part.
As shown in FIG. 13, the part shortage quantity data file 511 includes a part code of an ordered part used for a product, a predetermined order lead time from the ordering date to the delivery date of the part, an ordering cycle, and delivery of the part. Acceptance test days that indicate the period that can be used for product production from the date after inspection, etc., the order lot that is the minimum order quantity, the parts period that is the parts delivery date, the days from today to the parts period, Parts quantity, inventory allocation quantity with inventory parts allocated, inventory remaining quantity after subtracting inventory allocation quantity from part quantity, remaining order allocation quantity below, remaining order quantity after subtracting remaining order allocation quantity from inventory allocation remaining quantity The remaining quantity after allocation, the planned order quantity for the following shortage quantity (before lot calculation), and the forecasted quantity for 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, order period, acceptance test days, and order lot are obtained by referring to the part information data file 504 in FIG.
“Number of days until the required date” is the difference between the required date for the component 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, and calculating 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”, and “Days until the required period” is “Order lead time + If the ordering cycle + the number of acceptance test days is the same or smaller than "order lead time + ordering cycle + 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 the 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 shows the date when the supplier of the parts starts the forecast publication represented by the forecast contract conclusion date.

As shown in FIG. 14, the parts supplier information data file 512 is associated with the parts supplier code for identifying the parts supplier, the parts supplier name of the code, and the forecast contract conclusion date which is the forecast release date. ing.
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 part supplier name of the parts supplier code “M001” is “Company A”, and the forecast contract conclusion date, that is, the date when the forecast release on the premise of taking over responsibility to the parts supplier is started is This indicates that it 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 the forecast, that is, the shortage quantity (before lot calculation) that has the forecasted quantity. is there.

  As shown in FIG. 15, the weekly parts shortage quantity data file 513 includes a part code of a part to be forecasted for use in a product, a part period of the part, and a week including January 1 every year. The forecast release year, the following forecast release week, and the forecast scheduled quantity defined in the consistent NO. For each year until the week preceding January 1 of the following year as a week are associated.

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.
As shown in FIG. 16, in the order lot calculation data file 514, the order lot, the forecasted forecast quantity, and the previously presented quantity shown below are included in each forecast release week and each part code of the forecast published part code. The fixed quantity, the following order quantity considering quantity, the following lot quantity considering quantity, and 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 collecting the forecast scheduled quantity for each forecast release week by referring to the weekly parts shortage quantity data file 513 in FIG.

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. 16) 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 total order quantity after the previous forecast update date in the order of 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, the current (this week), the quantity of parts that do not take into account the number of lots to be cast, The current order quantity considering quantity up to n weeks is defined as ΣB (n), and the quantity before lot number considering up to the nth week is defined as ΣC (n). The quantity C (n) before the lot number consideration in the nth week is a quantity obtained by subtracting ΣC (n−1) from the larger one of ΣA (n) and ΣB (n).
For example, the quantity before considering the number of lots for the current week, that is, the quantity of parts that do not consider the number of lots to be cast this time (this week) This is the quantity obtained by subtracting the quantity before considering the number of lots up to the previous week from the larger quantity. In this way, the cumulative forecast quantity up to the previous week is subtracted from the larger quantity of the cumulative forecast quantity up to the current week and the cumulative quantity of parts for which transaction responsibilities have occurred. By calculating the scheduled cast quantity, it is configured so as not to be duplicated and to purchase extra parts.

In calculating the forecast quantity, if the quantity before considering 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.
In addition, as shown in FIG. 16, the part code and the range of “ordering”, “quantity confirmation” and “publication only” are defined for each subsequent week based on the current 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 the part that is the forecast contract data file when the forecast target flag is “Yes”. It is defined only when the forecast contract conclusion date of the supplier information data file 512 (see FIG. 14) has been set. A part code that does not satisfy the condition that the forecast target flag is “No” (see FIG. 6) and the forecast contract conclusion date (see FIG. 14) is blank is defined as “public only”. The range of “quantity determination” is not defined, but only the ranges of “ordering” and “publication” are defined.

When the conditions of the forecast target flag (see FIG. 6) and the forecast contract conclusion date (see FIG. 14) are satisfied, the “order” first obtains the range of “order” in units of days, The range of “order” in weekly units is obtained from the range of “order”. The range of “ordering” in units of days starts from the forecast release date and extends to the date when the order lead time, which is the period from the ordering date referring to the part information data file in FIG. It is a period.
The weekly “Purchase” range is considered to be the “Purchase Order” range if all dates included in each Forecast Release Week are included in the Daily “Purchase” 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 the “ordering” range on a weekly basis.

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. The range of “ordering” in week units is up to the current week.
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 from the date when the quantity confirmation lead time for the period in which the responsibility for taking over is generated with reference to the part information data file 504 in FIG. It is a period. 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.
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.
As shown in FIG. 17, the forecast detailed information data file 515 includes a previous order for each of the forecast release week and the forecasted part code (ordinary order; indicates that the order lead time can be observed), The last note (lead time break; indicates the short lead time for the order lead time break), the previous order plan, the current order note (normal order), the current order note (lead time break), and the current order plan are associated.

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.
The remaining order (ordinary order) is the total of the remaining order quantity of the data whose order period is equal to or more than the order lead time for each required year and week, referring to the order information data file 510 (see FIG. 12). is there.

The remaining order (breaking lead time) is a quantity obtained by referring to the ordering information data file 510 (see FIG. 12) by a part code and totaling the remaining ordering quantities whose ordering period is less than the ordering lead time for each required period. .
The current ordering schedule is the quantity of the same part code and the same period year, week, referring 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 quantity (normal order) last for the quantity determination are 20 in the current +6 week because one week has passed this time. In addition, 20 pieces of this time +7 weeks are for new orders.
In addition, since the last 20 days of +7 weeks, the remaining amount of the final quantity (lead time split) has been one week this time, it will be 20 of the current +6 weeks. In addition, due to contracts with parts suppliers, it is possible to set 20 items for the current +7 week (indicated in parentheses in FIG. 17) instead of 20 items for the current +6 week. . In this case, this time +6 weeks is blank.

  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 other words, one customer who is inquiring about a product that uses 40 parts is proceeding with the shipment of the product (30 parts are used) as planned. This is the case when the plan (using 10 parts) is delayed by one week.

Further, since 50 weeks of +11 weeks in the period only for the release of the previous ordering schedule has passed one week, 50 pieces of +10 weeks in the period of only the release of the current ordering schedule 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 scheduled for the previous order have passed one week, but +11 weeks of the period of only public release scheduled for the current order. It is good also as 50 pieces. That is, this is the case when the customer's plan for the product that uses these 50 parts is delayed by 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 contents and the previous update contents of the quantity of parts already received 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 that is disclosed to business partners. Information for each part is provided for each business partner, and orders for the current week, next week +1 week, next week +2 week, ..., +15 weeks are placed. It shows the period, the quantity determination period, and the period of only disclosure.

As shown in FIG. 18, the forecast information data file 516 includes an order lead time, a quantity determination lead time during which a responsibility for taking over occurs, and a take-off grace period for each part code for each part supplier code that purchases a part. The postponement possible period is associated, and the remaining (normal order), remaining (lead time split), and order schedules in the forecast detailed information data file 515 (see FIG. 17) are totaled in units of part codes and release weeks. Indicates quantity.
The part supplier code, the order lead time, the quantity confirmation lead time, and the take-off postponement possible period are values obtained by referring to the part information data file 504 (see FIG. 6) with the part code.

<< 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 entered the quantity determination lead time for which takeover responsibility has occurred and is used to see how many parts have to be taken over, the deadline for taking over, etc. Is.
As shown in FIG. 19, a forecast takeover responsibility data file 517 includes a part code for identifying a part, a date of taking responsibility for taking the part of the part code, and a quantity determination lead time at which the responsibility for taking the part of the part code is generated. , The period for which the part code of the part code can be postponed, the quantity of responsibility for taking the part of the part code, and the order deadline for the part of the part code are associated with each other.

The takeover responsibility occurrence date is the date when the takeover responsibility for the parts occurs, 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 in FIG.
With regard to the quantity of responsibility for taking over, refer to the forecast detailed information data file 515 of FIG. 17 by the part code, calculate the total quantity of the planned order (this time) within the range of quantity determination, and calculate the previous forecast from the calculated quantity. It is a quantity obtained by subtracting the total quantity of the responsibility for taking over in the takeover responsibility data file 517.

The order deadline is a date obtained by adding the quantity confirmation lead time and the take-off postponement period to the take-off responsibility occurrence 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 in FIG. 12 under the condition that the order date is larger than the last update date for each part code, the total order quantity is calculated, and the forecast takeover responsibility data file 517 in FIG. Since the order for the amount of occurrence of the responsibility for reference is placed in ascending order of the date of occurrence of the responsibility for take-off, it is offset by the calculated order quantity in ascending order. The amount is canceled until the amount of responsibility for taking over becomes 0, or the total amount of orders placed when the date of occurrence of takeover responsibility is late and the order date can be set later is 0.
Next, various operations of each management unit will be described. Here, first, processing in the master information management unit 11 will be described.

<< Product Production Information Registration Process in Master Information Management Unit 11 >>
Next, 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 registration processing of product production information for registration in the product production information data file 503 (see FIG. 5).
When 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, the product production information registration screen G1 of the input screen shown in FIG. It is displayed on the input / output terminal 60. FIG. 21 is a diagram showing a product production information registration screen G1 as an input screen displayed on the input / output terminal.

The product production information registration screen G1 in FIG. 21 has fields for inputting a product code and production lead time.
First, the registrant uses the input / output terminal 60 (see FIG. 1) to input a product code such as “S001” in the product code field of the product production information registration screen G1 in FIG. click.
Then, the product code data is transmitted (S11 in FIG. 20), and the forecast management apparatus 10 stores the product code in FIG. 5 stored in the information recording unit 50 (see FIG. 1) with the product code input by the registrant. Referring to the information data file 503 (S12 in FIG. 20), the production lead time is acquired (S13 in FIG. 20), transmitted to the input / output terminal 60, and displayed in the input field for the production lead time (S14 in FIG. 20).

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 of the product production information registration screen G1 in FIG. FIG. 21 shows a case where “5” is displayed instead of “blank”.
Next, as shown in FIG. 21, the registrant enters “5” as product production information in the production lead time input field (S15 in FIG. 20), and clicks the registration button.
Then, the production lead time data is transmitted (S16 in FIG. 20), and the forecast management apparatus 10 (see FIG. 1) stores the product production information input by the registrant in the product production information data file 503 of the information recording unit 50. (Refer to FIG. 5) (S17 in FIG. 20).

<< 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 a part information registration process for registration in the part information data file 504.
When the registrant logs in to the master information management unit 11 of the forecast management apparatus 10 (see FIG. 1) using the input / output terminal 60 of FIG. 1, the component information registration screen G2 of the input screen shown in FIG. 60. FIG. 23 is a diagram showing a component information registration screen G2 of the input screen.
The part information registration screen G2 in FIG. 23 includes a part code input field, 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 code. There is an input field for a forecast target part flag.

First, the registrant uses the input / output terminal 60 to input the component code “B001” or the like in the component code field of the component information registration screen G2 in FIG. 23 (S21 in FIG. 22), and then clicks the search button. .
Then, the component code data is transmitted (S22 in FIG. 22), and the forecast management apparatus 10 (see FIG. 1) uses the component code input by the registrant and the component information data file 504 in FIG. (S23 in FIG. 22), search for 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, etc. The result is acquired (S24 in FIG. 22), the search result is transmitted to the input / output terminal 60, and displayed on the component information registration screen G2 in FIG. 23 (S25 in FIG. 22).

If the corresponding product code does not exist as a result of referring to the component information data file 504, the input field of the component information registration screen G2 in FIG. Note that FIG. 23 shows a case where each entry field is displayed.
Next, as shown in FIG. 23, the registrant is required to name the part, order lot, order lead time, quantity confirmation lead time, take-off postponed period, order cycle, acceptance test days, parts supplier code, forecast target part. A flag is input (S26 in FIG. 22), and a registration button is clicked.
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) (see FIG. 22). S28).

<< Part supplier information registration process in master information management unit 11 >>
Next, the parts supplier information registration process in the master information management unit 11 (see FIG. 1) will be described with reference to FIG. FIG. 24 is a diagram showing a procedure related to the parts supplier information registration process for registration in the parts supplier information data file 512 (see FIG. 14).
When the registrant logs in to the forecast management apparatus 10 master information management unit 11 (see FIG. 1) using the input / output terminal 60 (see FIG. 1), the parts supplier information registration screen G3 of the input screen shown in FIG. Is displayed on the input / output terminal 60. FIG. 25 is a diagram showing a parts supplier information registration screen G3 displayed on the input / output terminal 60 of FIG. 1 in the parts supplier information registration process.

The part supplier information registration screen G3 in FIG. 25 includes an input field for a part supplier code, an input field for a part supplier name, and a forecast contract conclusion date.
First, the registrant uses the input / output terminal 60 of FIG. 1 to input “M001” or the like of the parts supplier code in the parts supplier code column of the parts supplier information registration screen G3 of FIG. 25 (FIG. 24). After S31), the search button is clicked.

Then, the parts supplier code data is transmitted (S32 in FIG. 24), and the forecast management apparatus 10 uses the parts supplier code input by the registrant to record the parts shown in FIG. 14 of the information recording unit 50 (see FIG. 1). Referring to the supplier information data file 512 (S33 in FIG. 24), the search result such as the parts supplier name, forecast contract conclusion date, etc. is acquired (S34 in FIG. 24), and transmitted to the input / output terminal 60 and sent to FIG. The information is displayed on the parts supplier information registration screen G3 (S35 in FIG. 24).
As a result of referring to the parts supplier information data file 512 of FIG. 14, if there is no corresponding parts supplier code, the input field of the parts supplier information registration screen G3 of FIG. 25 is left blank. Note that FIG. 25 shows a case where it is displayed in the input field.

Next, as shown in FIG. 25, the registrant inputs the parts supplier name and the forecast contract conclusion date (S36 in FIG. 24), and clicks the registration button.
Then, the input parts supplier information is transmitted (S37 in FIG. 24), and the forecast management apparatus 10 (see FIG. 1) stores the parts supplier information input by the registrant in the information recording unit 50 (FIG. 1, FIG. 1). 2) (see FIG. 2) (see FIG. 24).

<< Notice Arrangement Processing in Arrangement Information Management Unit 12 >>
Next, the notice arrangement process regarding the product notice in the arrangement information management unit 12 (see FIG. 1) will be described with reference to FIG. FIG. 26 is a diagram showing a procedure related to the advance notice arrangement process for registration in the product advance notice data file 501 (see FIG. 3).
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 (see FIG. 1) of the forecast management apparatus 10 using the input / output terminal 60 of FIG. 1, the product notice screen G4 of the input screen shown in FIG. It is displayed on the output terminal 60. FIG. 27 is a diagram showing a product notice screen G4 as an input screen displayed on the input / output terminal 60 of FIG. 1 in the notice arrangement process.
The product notice screen G4 in FIG. 27 includes an entry field for a notice number, and an entry field for a product code, a product notice quantity, and a product notice period.

First, the registrant uses the input / output terminal 60 of FIG. 1 to input the notice number “Y001” or the like in the notice number field of the product notice screen G4 of FIG. 27 (S41 of FIG. 26), and then the search button. Click.
Then, the inputted notice number is transmitted (S42 in FIG. 26), and the forecast management apparatus 10 (see FIG. 1) uses the notice number inputted by the registrant to notify the product notice of the information recording unit 50 (see FIG. 1). Referring to the data file 501 (see FIG. 3) (S43 in FIG. 26), search results such as product code, product notice quantity, product notice period are obtained (S44 in FIG. 26) and transmitted to the input / output terminal 60. It is displayed on the product notice screen G4 of FIG. 27 (S45 of FIG. 26).
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 field of the product notice screen G4 in FIG. 27 is left blank. Note that FIG. 27 shows a case where each entry field is displayed.

Next, as shown in FIG. 27, the noticer inputs the product code, the quantity of product notice, and the product notice period (S46 in FIG. 26), and clicks the registration button.
Then, the input product notice information is transmitted (S47 in FIG. 26), and the forecast management apparatus 10 (see FIG. 1) converts the product notice information inputted by the notice person into the information recording unit 50 (see FIG. 1). Is registered in the product notice data file 501 (see FIG. 3) (S48 in FIG. 26).

When registering in the product notice data file 501, it is checked whether or not the notice number to be registered already exists (S49 in FIG. 26), and if registered (Yes in S49 in FIG. 26), product notice data is registered. After referring to the file 501 (see FIG. 3), the notice component data file 505 (see FIG. 7) and the total necessary parts data file 508 (see FIG. 10) by the notice number and deleting the corresponding record (S49a in FIG. 26) The product notice information input from the product notice screen G4 is registered (S49b in FIG. 26).
On the other hand, if it is determined in S49 in FIG. 26 that the notice number does not already exist in the product notice data file 501 (No in S49 in FIG. 26), the process proceeds to S49b in FIG.

Records registered in the product notice data file 501 (see FIG. 3) are registered in the notice parts data file 505 in FIG. 7 using the parts table development result of the parts development apparatus 20 in FIG.
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. .

<< Product Arrangement Processing in Arrangement Information Management Unit 12 >>
Next, product arrangement processing in the arrangement information management unit 12 (see FIG. 1) for registration in the product arrangement data file 506 (see FIG. 8) will be described with reference to FIG. FIG. 28 is a diagram showing a procedure related to product arrangement processing for registration in the product arrangement data file 506 (see FIG. 8).
For example, when the arranger logs into the arrangement information management unit 12 (see FIG. 1) of the forecast management apparatus 10 using the input / output terminal 60 of FIG. 1, the product arrangement screen G5 of the input screen shown in FIG. 29 is entered. It is displayed on the output terminal 60. FIG. 29 is a diagram showing a product arrangement screen G5 as an input screen displayed on the input / output terminal of FIG. 1 in the product arrangement process.

The product arrangement screen G5 of FIG. 29 includes a notice number input field, an arrangement number input field, and a product code, product arrangement quantity, and product arrangement period input fields.
First, the arranger uses the input / output terminal 60 of FIG. 1 to input the notice number “Y001” or the like previously foretold in the notice number column of the product arrangement screen G5 of FIG. 29 (S51 of FIG. 28). Then click the search button.

Then, the inputted notice number is transmitted (S52 in FIG. 28), and the forecast management apparatus 10 in FIG. 1 shows the information recording unit 50 (see FIGS. 1 and 2) with the notice number inputted by the registrant. 3 is referred to (S53 in FIG. 28), and a search result such as a product code, a product notice quantity, a product notice period is acquired (S54 in FIG. 28), and is transmitted to the input / output terminal 60 to obtain the product. The product code, the product order quantity, and the product order required period column on the order screen G5 are displayed (S55 in FIG. 28).
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 column of the product arrangement screen G5 in FIG. 29 is left blank. Note that FIG. 29 shows a case where each entry field is displayed.

Next, the arranger confirms the displayed product code, product arrangement quantity, and product arrangement period, and if there is a change, corrects each item as shown in FIG. Further, after entering the arrangement number “T001” or the like in the arrangement number field on the product arrangement screen (S56 in FIG. 28), the registration button is clicked.
Then, the input product arrangement information is transmitted (S57 in FIG. 28), and the forecast management apparatus 10 in FIG. 1 stores the product arrangement information input by the arranger in the information recording unit 50 (see FIGS. 1 and 2). The product arrangement data file 506 (see FIG. 8) is registered (S58 in FIG. 28).
Further, the product notice data file 501 in FIG. 3 is referred to by the notice number to check whether it has been registered (S59 in FIG. 28). If the notice number already exists (Yes in S59 in FIG. 28), the product notice The data file 501, the notice component data file 505 (see FIG. 7) and the total necessary parts data file 508 (see FIG. 10) are referred to by the notice number, and the corresponding record is deleted (S59a in FIG. 28).

The records registered in the product arrangement data file 506 in FIG. 8 are registered in the arrangement parts data file 507 in FIG. 9 using the parts table development result of the parts development apparatus 20 (see FIG. 1).
Further, the record registered in the arranged parts data file 507 is combined with the above-described notice parts data file 505 (see FIG. 7) and registered in the total necessary parts data file 508 (see FIG. 10) (S59b in FIG. 28). ).
On the other hand, in S59 of FIG. 28, when the notice number does not already exist (No in S59 of FIG. 28), the process proceeds to S59b of FIG.

<< Order processing in forecast quantity management unit 13 >>
Next, the ordering process in the forecast quantity management unit 13 (see FIG. 1) will be described.
When performing the ordering process, first, the required number of orders is calculated. The following order processing is performed by executing the program of the forecast quantity management unit 13.
For example, the ordering process is performed every day at a time determined by a schedule. The required number of orders can be obtained by creating the part shortage quantity data file 511 of FIG. 13 and extracting the record in which the shortage quantity (before lot calculation) planned order quantity of the part shortage quantity data file 511 is set.

The extracted record is ordered from the parts supplier by a well-known technique based on the order cycle defined in the part information data file 504 in FIG. 6, and the ordered record is registered in the order information data file 510 in FIG.
Further, with reference to the forecast takeover responsibility data file 517 of FIG. 19 for the ordered part code, if there is a record with takeover responsibility, the offset process is performed.

<< Forward Number Calculation Processing in Forecast Quantity Management Unit 13 >>
Next, the forecast quantity is calculated. For example, the forecast quantity calculation process is performed every week at the time of the day of the week determined by the schedule. The forecast number calculation process is performed by executing the corresponding program of the forecast quantity management unit 13.

In the forecast number calculation process, first, the aforementioned component shortage quantity data file 511 (see FIG. 13) is created. Next, the weekly parts shortage quantity data file 513 in FIG. 15, the order lot calculation data file 514 in FIG. 16, the forecast detailed information data file 515 in FIG. 17, and the forecast information data file 516 in FIG. 18 are created.
Also, the above-mentioned forecast takeover responsibility data file 517 of FIG. 19 is registered.

<< Forecast release >>
Next, forecast presentation for parts suppliers in the forecast presentation unit 14 (see FIG. 1) will be described. The following process of presenting a forecast for a parts supplier is performed by executing a program corresponding to the forecast presenting unit 14.

  For example, the parts supplier uses the input / output terminal 81 in FIG. 1 or the parts orderer uses the input / output terminal 60 in FIG. 1 to log in the forecast management system S (not shown). When logging in to the forecast presentation unit 14 (see FIG. 1) of the forecast management apparatus 10 with an ID and a password, each of which is given identification information, a forecast release screen G6 of the input screen shown in FIG. Displayed on the input / output terminal 81 or the input / output terminal 60, respectively. FIG. 30 is a diagram showing a forecast disclosure screen G6 displayed on the input / output terminal 81 of the parts supplier or the input / output terminal 60 of the ordering source shown in FIG. 1 and referring to the forecast.

The forecast release screen G6 in FIG. 30 includes display items of a parts supplier code, a part code, an order lead time, a quantity confirmation lead time, a take-off postponement possible period, and a public week.
The data disclosed to the parts supplier is only the parts supplier code to which the logged-in user belongs in the forecast information data file 516 of FIG.
Here, a user who can log in is preliminarily programmed and provided with a security management means for giving an ID and password of identification information permitting login to the forecast management system S and disclosing information to the ID and password. ing.

That is, the parts supplier, by entering the ID and password given in advance on the login screen of the forecast management system S, by the security management means, so that information about the parts with which it is dealing is displayed. It is configured.
On the other hand, the security management means that the parts ordering party inputs the ID and password given in advance on the login screen of the forecast management system S so that the parts information on all parts supplier codes is displayed. It is constituted by.
The forecast disclosure screen G6 shown in FIG. 30 shows a case where a forecast related to a component supplier with a component supplier code “M002” is released.

Further, by selecting each line displayed on the forecast release screen G6 in FIG. 30 by clicking or the like, the forecast release detail screen G7 in FIG. 31 is displayed. FIG. 31 is a diagram showing a forecast disclosure detail screen G7 displayed on the input / output terminal 81 of the parts supplier or the input / output terminal 60 of the ordering source shown in FIG. 1 and referring to the forecast details.
It is assumed that the data disclosed on the forecast disclosure detail screen G7 refers to the forecast detail information data file 515 of FIG. 17 with the part code of the selected forecast quantity.

<< Forecast release >>
Next, forecast publication will be described with reference to FIG.
Note that FIG. 32 is a diagram showing three display functions of the forecast release screen G8 for referring to the forecast, from 8 weeks ahead, 16 weeks ahead, and 24 weeks ahead.
The forecast release screen G8 shown in FIG. 32 is characterized in that it has three display functions of 8 weeks ahead, 16 weeks ahead, and 24 weeks ahead for suppliers who want to conduct transactions on a monthly basis.

When the parts supplier visually checks this forecast disclosure screen G8 (see FIG. 32), first, the login screen (not shown) of the forecast management system S is used using the input / output terminal 81 of the parts supplier shown in FIG. )), Enter the ID and password given to the parts supplier and press the enter key.
Then, a menu screen (not shown) of the forecast management system S is displayed. Select the forecast from the menu and press the enter key. Then, it is selected whether the forecast shown in FIG. 32 is to be viewed in any of the 8th, 16th, and 24th weeks, or whether the forecast is viewed in all of the 8th, 16th, and 24th weeks. A forecast period selection screen (not shown) is displayed.

For example, if the parts supplier “ABCD” selects an option to refer to the forecast in 8 weeks, 16 weeks, and 24 weeks, the security management means will use the ID and password entered on the login screen. 32, the forecast disclosure screen G8 shown in FIG. 32 about the part purchased from itself, that is, “parts supplier ABCD” is displayed on the input / output terminal 81.
In addition, when the forecast 8 weeks ahead is selected, the forecast table G8a up to 8 weeks ahead is displayed. When the forecast 16 weeks is selected, the forecast table up to 16 weeks ahead is displayed. When the cast table G8b is displayed and the forecast 24 weeks ahead is selected, the forecast table G8c up to 24 weeks ahead in units of weeks is displayed. Here, the forecast table G8a up to 8 weeks ahead, the forecast table G8b up to 16 weeks ahead, and the forecast table G8c up to 24 weeks ahead are almost the same structure, so the forecast table G8a up to 8 weeks ahead is Take up and explain.

The part code G8a1 of the forecast table G8a shown in FIG. 32 displays the part code of the part to be cast, and the model G8a2 displays the part type of the part code. For example, the first row of the forecast table G8a indicates that a part whose part code G8a1 is “B003” and whose model G8a2 is “A000003” is an object.
The column of “planned order + actual result” G8a3 is a column for displaying the forecast of the part. The quantity of the part to be ordered and the result, that is, the quantity of the part to be ordered and the part that has been ordered is “delayed”, every week. , “Total”, “Number of remaining notes”, etc.

In the “delay” column in the “scheduled order + actual result” G8a3, the number of undelivered parts that have passed the delivery date among the ordered parts up to the current week including the present is displayed. For example, in the first row of the forecast table G8a, it is displayed that 150 parts with the part code “B003” are undelivered even if the delivery date has passed by the current week.
“Ordering + Actual” G8a3 “Current Week” to “+8 Week” indicates the quantity of the ordered parts and unordered parts for each week from “This Week” to “+8 Weeks”. , “Total” in “Scheduled order + Actual” G8a3 indicates the total quantity of each column from “Delayed” to “+8 weeks”, and (Remaining number of orders) is ordered and received. No part count is shown.

32, the product name of the part code is displayed in the column of the product name G8a4 of the forecast table G8a, and the drawing number G8a5 displays the drawing number of the design drawing in which the part of the part code is illustrated. In the column of product number G8a6, the product number in the design drawing of the component code is displayed.
The part supplier G8a7 column of the forecast table G8a shown in FIG. 32 displays the part supplier name that handles the part of the part code, and the order L / T (lead time) (G8a8) column shows the order. The order lead time is displayed in terms of the number of days from the part ordering date to the part delivery date, which is determined in advance between the original and parts supplier, and the quantity confirmation L / T (lead time) (G8a9) column Displays the lead time for determining the quantity expressed by the number of days from the date when the part is forecasted to the day when the part ordering party is responsible for taking over.

In the forecast table G8a shown in FIG. 32, when the parts supplier “ABCD” logs in with the ID and password given on the login screen, “ABCD” is displayed in the column of the parts supplier G8a7, and the parts supplier Information about parts handled by “ABCD” is displayed.
In the column of the pick-up period G8a10 of the forecast table G8a shown in FIG. 32, a grace period for picking up the parts for which the takeover responsibility has occurred, that is, a grace period for ordering the parts for which the takeover responsibility has occurred is displayed in days, and the minimum lot G8a11 In this column, the minimum purchase number for picking up parts is displayed.
In this way, the parts supplier can visually check the forecasts related to the parts handled by the parts supplier using the input / output terminal 81 (see FIG. 1) for the parts supplier.
Of course, the three display functions up to 8 weeks, 16 weeks, and 24 weeks ahead can be programmed and configured to select and display any number of weeks ahead. The display is not limited to three displays from 16 weeks to 24 weeks ahead.

Further, the parts ordering source displays the login screen of the forecast management system S on the input / output terminal 60 shown in FIG. 1, inputs the ID and password assigned to the ordering source, and the forecasting shown in FIG. When the public screen G8 is displayed, the orderer ID and password input by the security management means are recognized, and the forecast public screen G8 for all parts suppliers is displayed on the input / output terminal 60.
In other words, the names of all parts suppliers are displayed for each row in the column of the parts supplier G8a7 on the forecast disclosure screen G8, and the forecast of the parts related to all the parts suppliers can be visually observed.

<< Forecast release (breakdown display) >>
Next, forecast publication capable of displaying the breakdown will be described with reference to FIG.
There are the following four types of screens for parts suppliers to refer to forecasts.
That is, the sum of the “order left” representing the ordered and undelivered parts shown in FIG. 33 (a) and the “ordered schedule” representing the parts that have not been ordered and are scheduled to be ordered is displayed. A. Searched for a week ahead. There is a screen G9a of “Remaining Note” + “Planned Order”.

Also, the ordered parts shown in FIG. 33B are displayed, and B.B. There is a screen G9b of “notes only”.
In addition, C.1 which is not ordered and which is scheduled to be ordered as shown in FIG. There is a screen G9c of “Ordering schedule only”.
In addition, A. which searched 8 weeks ahead in the week unit shown in FIG. “Remaining order” + “Scheduled order”, B.E. “Notes only”, C.I. There is a three-stage display screen G9d that includes “ordering plan only”.

FIG. 33 is a diagram showing types of screens that are displayed on the input / output terminal 81 (see FIG. 1) of the parts supplier in FIG. FIG. 33B is a diagram showing a screen G9a that displays “note remaining” + “ordering plan”. It is a figure which shows screen G9b which displays "notes only", and FIG. FIG. 33D is a diagram showing a screen “G9c” displaying “Ordering plan only”. “Remaining order” + “Scheduled order”, B.E. “Notes only”, C.I. It is a figure which shows the screen G9d of 3 steps | paragraphs display combining "ordering plan only".
A. shown in FIG. In the part code G9a1 on the screen "Got order" + "Scheduled to order", the part code of the part to be forecasted is displayed, and the part type of the part code is displayed in the model G9a2.

  The display condition G9a3 of the screen G9a is A.1. “A” indicating the display condition of “remaining order” + “scheduled order” is displayed, and the column “scheduled order + actual” G9a4 is a field for displaying the forecast of parts. , That is, the total number of parts scheduled to be ordered and parts already ordered, is indicated by “delay”, “weekly”, “total”, “number of remaining orders”, and the like. In the “delay” column in the “scheduled order + actual result” G9a4, the number of undelivered parts that have passed the delivery date among the ordered parts up to the current week including the present is displayed.

In the column of the product name G9a5 on the screen G9a, the product name of the part of the part code is displayed, the drawing number G9a6 displays the drawing number of the design drawing in which the part of the part code is illustrated, and the field of the product number G9a7 Displays the product number of the part code in the design drawing.
On the screen G9a, the part supplier G9a8 column displays the name of the part supplier that handles the part of the part code, and the order L / T (lead time) (G9a9) column displays between the ordering party and the part supplier. The order lead time expressed in terms of the number of days from the part order date to the part delivery date determined in advance is displayed, and the quantity confirmation L / T (lead time) (G9a10) column shows the part The quantity confirmation lead time represented by the number of days from the date of casting to the date of taking responsibility for taking over of the parts orderer is displayed.

In the column of the collection period G9a11 on the screen G9a, a grace period for taking parts for which takeover responsibility has occurred, that is, a grace period for ordering parts for which takeover responsibility has occurred is displayed in days.
In addition, B. shown in FIG. A screen G9b that displays "only note remaining", C.I shown in FIG. A screen G9c displaying "Ordering plan only", and A.B shown in FIG. “Remaining order” + “Scheduled order”, B.E. “Notes only”, C.I. The items displayed on the screen G9d of the three-stage display including “ordering plan only” are A. shown in FIG. Since it is an item displayed on the screen G9a displaying “note remaining” + “planned order”, a detailed description is omitted.

A. shown in FIG. The same quantity as the quantity shown in the forecast information data file 516 (refer to FIG. 18) is displayed on the screen “G9a” of “note remaining” + “planned order”.
The reference method of the data file stored in the information recording unit 50 shown in FIG. 2 is the same as the forecast information data file 516 described above, and the remaining order of the forecast detailed information data file 515 (see FIG. 17) (normal order) In addition, the remaining quantity (breaking lead time) and the order quantity are displayed in total by the part code and release week unit.

B. shown in FIG. As for the screen G9b displaying “only the remaining order”, the remaining order (ordinary order) and the remaining order (breaking lead time) in the forecast detailed information data file 515 (see FIG. 17) are totaled by the part code and the release week unit. The quantity is displayed.
C. shown in FIG. On the screen G9c displaying “Ordering Order Only”, the quantity obtained by summing up the ordering schedule in the forecast detailed information data file 515 (see FIG. 17) in units of part code and release week is displayed.

  Furthermore, the parts supplier code, order L / T (lead time) G9d9, and quantity confirmation L / T shown in the parts supplier G9d8, which are common items displayed on the three-stage display screen G9d shown in FIG. (Lead time) G9d10 and the take-off period G9d11, which is a postponed postponement period, display values obtained by referring to the part information data file 504 (see FIG. 6) with the part code.

Note that the difference (deviation) from the previous update content in each of the forecast information data file 516 shown in FIG. 18 and the forecast detailed information data file 515 shown in FIG.
A difference field between the current update content and the previous update content is calculated, the difference (deviation) is recorded, and A. shown in FIG. A screen “G9a” of “note remaining” + “scheduled order”, B.B shown in FIG. A screen G9b that displays "only note remaining", C.I shown in FIG. The difference (deviation) from the previous update content may be displayed on the screen G9c displaying only the “ordering plan” display and the screen G9d displaying three steps shown in FIG.
In addition, in FIG. 33, the case where the search is performed 8 weeks ahead in the week unit is described as an example. However, the search may be performed in 16 weeks, 4 weeks unit, and 24 weeks ahead. Of course, it can be configured as follows.

<< Summary >>
The forecast management system collects in real time information on order information for products that use parts to be ordered and specification determination information for design advance notices based on budget information, and publishes them in real time. The parts to be forecasted within are always sent information to each parts supplier using the quantity confirmation lead time to order.
As a method for presenting information to parts suppliers, a. B. C. From this week to 4 weeks, 24 weeks ahead, d. There are all these patterns (I, B, C) and four types, and the parts supplier can select freely according to the business mode and output the data. As a result, management operations can be facilitated.

  Further, the parts supplier and the part ordering party are A. shown in FIG. In addition to being able to see the forecast information on the screen “G9a” of “Remaining Note” + “Scheduled to Order”, A. B. As shown in FIG. A screen G9b that displays "notes only" and C.I. A screen G9c displaying “ordering plan only” can be selected and viewed, and the forecast information of parts is displayed in a batch as shown in FIG. “Remaining order” + “Scheduled order”, B.E. “Notes only”, C.I. It is possible to freely select and visually check the screen G9d of the three-stage display of “ordering only”.

Therefore, when a part that was scheduled to be ordered is changed to an ordered part, when parts are suddenly ordered and the number of forecast parts suddenly increases, or when the delivery date of the ordered part is accelerated, etc. In response to the change in the number of parts, the parts supplier and the ordering party change A. shown in FIG. From the screen “G9a” of “Notes remaining” + “Scheduled to order”, A. B. As shown in FIG. A screen G9b that displays "notes only" and C.I. shown in FIG. Since the screen “G9c” indicating “ordering only” is visible, the parts supplier and the part ordering source can search according to the timing of information collection.
In addition, since the forecast information of the parts can be viewed at a time on the three-stage display screen G9d shown in FIG. 33 (d), it is easy to use and it is possible to realize schedule management with higher accuracy.

In addition, a function for hiding only numerical items of the forecast search results for only 0 (zero) is provided, management data is carefully selected, and only necessary data is searched.
Then, the numerical change from the previous update date is “identified and displayed”, the alarm management is visualized, and more detailed contents can be searched on another screen, thereby improving information accuracy.
In addition, all displayed numerical values are displayed as contracted minimum lots with parts suppliers, that is, multiples of the minimum number of purchases, and the management man-hours are reduced by displaying the numerical values that each parts supplier can capture without problems. .

  Further, the background of the search screen is the forecast information shown in FIGS. 17, 18, and 31, “delay with respect to required time (delivery date) = pink” (not shown), “order = yellow”, “quantity confirmation = light blue” ”,“ Only open = white ”, and visualized by color, making it easy to manage visually. In this way, by displaying the color-coded display in the forecast, the order form is simplified because the order is placed once with the order lead time (order issue) in accordance with the order cycle.

According to this configuration, ordered information + planned order information (quantity confirmed: confirmed to be ordered) + when all the situations related to future parts ordering are required, planned order information + future parts Desired information can be appropriately viewed in accordance with the timing of information collection in the case where only the situation related to the order is required, the case where only the ordered information is required, and the case where all these pieces of information are required.
Therefore, even if the production background of parts handled varies widely, such as different products that use forecasted parts or newly forecasted parts, it is suitable for the production background for parts suppliers. Provides forecast information on parts and eliminates waste of parts procurement period.

Also, before arranging the formal order, set a period of quantity confirmation lead time that defines the period during which the takeover responsibility will occur and set it as an introductory rule. The information can be obtained via the communication network 80.
Therefore, based on the deadline of the quantity determination lead time during the period in which the responsibility for taking over occurs, the part ordering party can start production of only the required number of products, ensuring the part order lead time and It is possible to avoid the risk of overproduction of the products used.

Further, since the parts ordering source indicates the deadline of the quantity determination lead time for which responsibility for taking over occurs, the official order can be placed with the shortest order lead time. That is, the substantial procurement lead time can be shortened, and the parts inventory can be reduced.
Thereby, the delivery time can be determined as close as possible to the date of production.
Therefore, an increase in management man-hours such as re-adjustment of schedules with parts suppliers and internal related departments caused by cracks in the order lead time due to parts shortage can be greatly reduced, and the delivery date compliance rate is improved.

In addition, a product code is used for each finished product, and a part code of a part constituting the product is identified.
For this reason, the parts supplier can narrow down the product code and provide the parts information to the parts supplier, and the parts supplier can view the forecast information of the parts. A part supplier can use the input / output terminal 81 (see FIG. 1) to search for the part related to the part used in the product for which attention has been paid, and visually check the part.
Therefore, it is ensured that the parts delivered by the parts supplier are delivered on time.
From the above, it is possible to promote shortening of the part order lead time and reduction of parts inventory.
It should be noted that the parts described in the claims include semi-finished products constituting the product.

In a production system in which customer specifications are generated individually, if the order 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 order lead time. It is necessary to present forecasts to parts suppliers.
However, shortening the lead time for ordering the parts and shortening the lead time for manufacturing the product including the parts purchase has a problem that it becomes a part supplier's request. In order to solve this problem, the business model according to the present invention may be applied.

It is a block diagram which shows the whole structure containing the forecast management apparatus of the forecast management system of embodiment concerning this invention. It is a notional block diagram which shows the structure of the information recording part of embodiment. It is a figure which shows the structure of the product announcement data file of embodiment. It is a figure which shows the structure of the product parts table data file of embodiment. It is a figure which shows the structure of the product manufacture information data file of embodiment. It is a figure which shows the structure of the components information data file of embodiment. It is a figure which shows the structure of the notification component data file of embodiment. It is a figure which shows the structure of the product arrangement data file of embodiment. It is a figure which shows the structure of the arrangement parts data file of embodiment. It is a figure which shows the structure of the total required component data file of embodiment. It is a figure which shows the structure of the inventory data file of embodiment. It is a figure which shows the structure of the order information data file of embodiment. It is a figure which shows the structure of the component shortage quantity data file of embodiment. It is a figure which shows the structure of the components supplier information data file of embodiment. It is a figure which shows the structure of the weekly parts shortage quantity data file of embodiment. It is a figure which shows the structure of the data file for order lot calculation of embodiment. It is a figure which shows the structure of the forecast detailed information data file shown in FIG. 2 of embodiment. It is a figure which shows the structure of the forecast information data file of embodiment. It is a figure which shows the structure of the forecast taking responsibility data file of embodiment. It is a figure which shows the procedure regarding the registration process of the product manufacture information for registering in a product manufacture information data file. It is a figure which shows the product manufacture information registration screen of the input screen displayed on an input / output terminal in the registration process of product manufacture information. It is a figure which shows the process sequence regarding the registration process of the components information for registering in a components information data file. It is a figure which shows the components information registration screen of the input screen displayed on an input / output terminal in the registration process of components information. It is a figure which shows the procedure regarding the components supplier information registration process for registering in a components supplier information data file. It is a figure which shows the components supplier information registration screen displayed on the input / output terminal shown in FIG. 1 in components supplier information registration processing. It is a figure which shows the procedure regarding the notice arrangement process for registering in a product notice data file. It is a figure which shows the product notice screen displayed on an input / output terminal in notice arrangement processing. It is a figure which shows the procedure regarding the product arrangement process for registering in a product arrangement data file. It is a figure which shows the product arrangement screen of the input screen displayed on an input / output terminal in a product arrangement process. It is a figure which shows the forecast publication screen which refers to a forecast. It is a figure which shows the forecast disclosure detail screen which refers to a forecast detail. It is a figure which shows the three types of display functions of 8 weeks ahead, 16 weeks ahead, and 24 weeks ahead of the forecast publication screen which refers to a forecast. (a) It is a figure which shows the screen which displays "note remainder" + "order plan", (b) It is a figure which shows the screen which displays "note only", (c) is C.I. It is a figure which shows the screen of a "order plan only" display, (d). “Remaining order” + “Scheduled order”, B.E. “Notes only”, C.I. It is a figure which shows the screen of 3 steps | paragraphs display combining "ordering plan only".

Explanation of symbols

10 Forecast management device (unordered information presentation means, actual order information presentation means, disclosure means, computer),
14 Forecast presentation section (unordered information presentation means, actual order information presentation means, disclosure means),
20 parts deployment device (unordered information presentation means),
30 inventory management device (unordered information presenting means, actual order information presenting means),
40 Purchased goods management device (actual order information presentation means),
50 information recording unit (unordered information presenting means, actual order information presenting means, storage means),
60 Input / output terminal (public means) of the parts orderer,
70 communication network (public means),
80 communication network (public means),
81 Input / output terminal of parts supplier (public means)
S Forecast management system

Claims (16)

Storage means for storing a product code for identifying each finished product, a part code for identifying an individual part constituting each finished product, and information on the part;
Unordered information presenting means for presenting unfinished part information including the necessary time limit of each of the parts developed to the part level using the product code and the part code based on the required delivery date of the completed product;
Actual order information presenting means for presenting part information including the necessary time limit of the part developed to the part level already arranged for actual order using the part code;
Publishing means for publishing the part information of the unordered information presenting means and the part information of the actual order information presenting means,
The publishing means combines the first information relating to the unordered parts that have been ordered and the undelivered parts, the second information relating to the unordered parts that are scheduled to be ordered, and the remaining parts and the parts that are scheduled to be ordered. Disclosing third information on the selected component and any information selected from the first information, the second information, and the fourth information, which is information in which the third information is arranged. A forecast management system characterized by When there are a plurality of the finished products and there are common parts among the parts constituting the plurality of finished products,
The unordered information presenting means and the actual order information presenting means respectively sum the quantity for each of the common parts,
The publication means publishes any of the selected information based on the information on the common parts totaled by the unordered information presentation means and the actual order information presentation means, respectively. The forecast management system according to 1. 2. The forecast management system according to claim 1, wherein, when the disclosure unit is accessed using identification information given to a user in advance, any of the selected information is disclosed. The forecast management system according to claim 1, wherein the publishing unit publishes any of the selected information for each component supplier that handles the component. The storage means has an order lead time indicating a period from the order of the part to delivery of the part, and a quantity determination indicating a period during which the responsibility for taking the part occurs from the date when the forecast of the part is released A lead time and a take-off postponement possible period indicating a take-off period for the part are stored,
The forecast management system according to claim 1, wherein the publication unit publishes the order lead time, the quantity determination lead time, and the take-off possible period. The unordered information presenting means and the actual order information presenting means are searched up to 8 weeks ahead, up to 16 weeks ahead, up to 24 weeks ahead every 4 weeks, or all three systems simultaneously,
The publishing means publishes any of the selected information until the 8th week, the 16th week, the 24th week after every 4 weeks, or all three systems simultaneously. The forecast management system according to claim 1, wherein: If the quantity information of the part disclosed by the publishing means has changed from the previous update,
The unordered information presenting means and the actual order information presenting means determine each week,
2. The forecast management system according to claim 1, wherein the publishing unit publishes any of the selected information based on determination results of the unordered information presentation unit and the actual order information presentation unit. . The forecast management system according to claim 1, wherein the publishing unit publishes the difference from the previous update content in any of the selected information. On the computer,
A first procedure for storing in a storage means a product code for identifying each finished product, a part code for identifying individual parts constituting each finished product, and information on the part;
A second procedure for presenting unordered part information including a necessary deadline for each of the parts, wherein the finished product is developed at the part level using the product code and the part code based on the required delivery date;
A third procedure for presenting part information including a necessary time limit of the part developed to the part level that has been actually ordered, using the part code; and first information relating to an unordered part that has been ordered and Second information relating to unordered parts to be ordered, third information relating to the remaining parts and parts scheduled to be ordered, the first information and the second information, A program of a forecast management system for executing a publishing procedure for disclosing any selected information of the fourth information, which is information in which the third information is arranged. When there are a plurality of the finished products and there are common parts among the parts constituting the plurality of finished products,
In the second procedure and the third procedure, the quantities are summed for each of the common parts,
10. The disclosure procedure includes releasing any of the selected information based on the information on the common parts summed up by the second procedure and the third procedure, respectively. The program of the described forecast management system. The program of the forecast management system according to claim 9, wherein, in the case of access using the identification information given to the user in advance, the release procedure releases any of the selected information. . The program of the forecast management system according to claim 9, wherein the publishing procedure publishes any of the selected information for each component supplier handling the component. The first procedure includes an order lead time indicating a period from ordering the part to delivery of the part, and a quantity indicating a period during which responsibility for taking out the part occurs from the date when the forecast of the part is released. Memorize the confirmed lead time and the possible period for postponement indicating the grace period for the part,
The program of the forecast management system according to claim 9, wherein in the release procedure, the order lead time, the quantity confirmation lead time, and the take-off postponement possible period are disclosed. The second procedure and the third procedure are searched up to 8 weeks ahead, 16 weeks ahead, or every 4 weeks up to 24 weeks ahead, or all three systems simultaneously,
The publishing procedure publishes any of the selected information until the 8th week, the 16th week, the 4th week, the 24th week, or all three systems simultaneously. The program of the forecast management system according to claim 9. If the quantity information of the parts released by the release procedure has changed from the previous update,
The second procedure and the third procedure are determined weekly,
10. The forecast management system according to claim 9, wherein the publishing procedure publishes any of the selected information based on a determination result of the second procedure and the third procedure. program. The program of the forecast management system according to claim 9, wherein the publishing procedure publishes the difference from the previous update content in any of the selected information.

Images