JP2009151578A - Forecast management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a forecast management system capable of shortening an order lead time by disclosing forecast information to a component customer. <P>SOLUTION: The forecast management system S is equipped with arrangement information management means 12, 20, 50 for managing forenotice information regarding unordered components of components to be used in a product and arrangement information of already ordered components of the components, component information management means 11, 50 for managing contract information regarding component purchase with the component customer to purchase a component for each component, forecast quantity management means 13, 20, 30, 40, 50 for calculating forecast information of components based upon the forenotice information, the arrangement information, and the contract information, and forecast presenting means 14, 50 for presenting the forecast information of the components. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a production management method, and more particularly to a forecast management system that presents a forecast of a necessary part to a parts supplier who purchases the part.

The order lead time, which is the period from the order of the parts used in the product to the delivery of the parts, is larger than the product lead time, which is the period from the order for the product from the customer to the shipment of the product. In a production system in which individual occurrence occurs, that is, high-mix low-volume production, the product lead time required by customers is generally met by parts inventory and intermediate inventory of semi-finished products.
However, from the viewpoint of management, it is necessary to reduce the inventory of parts and the balance of semi-finished products from the viewpoint of interest rate burden and management. From the order of products to the shipment of products by shortening the order lead time from parts ordering to parts delivery Shortening of product lead time is required.

As a means for that, Patent Document 1 discloses a technology that presents part forecast information based on the planned number of products to be produced to parts suppliers and shortens the order lead time from part ordering to part delivery. Yes.
JP 2002-140110 (paragraphs 0032, 0033, FIG. 1, etc.)

  However, in the method disclosed in the above background art, the production of a product or semi-product including procurement of parts used for the product or semi-finished product from the company that receives the order of the product and ships the product is a partner company. When requesting from a manufacturer, the order lead time from ordering a part used for a product or semi-finished product manufactured by a product manufacturer to delivery of the part is a contract between the product manufacturer and the parts supplier who purchases the part. There was a problem of relying on the product manufacturer to reduce the lead time from ordering the product to shipping the product by shortening the order lead time.

  Ideally, it would be desirable for the product manufacturer to build the forecast operation, and it would be desirable for the product manufacturer to shorten the lead time for ordering parts used in the product or semi-finished product. Due to differences in the company scale between the manufacturer of the product and the company that ordered the production of the product from the manufacturer. The contract between the parties may be disadvantageous as compared with the contract between the company that orders the production and the parts supplier.

  In view of the above situation, the present invention provides a forecast management system that shortens the order lead time from ordering of parts used for a product to delivery of the parts, and shortens the product lead time from the order of the product to the product shipment at the order maker. Objective.

  In order to achieve the above purpose, arrangement information management means for managing and processing notice information regarding unordered parts of parts used in products and arrangement information of ordered parts of parts, and purchasing the parts for each part Parts information management means for managing contract information related to parts purchase with parts suppliers, forecast quantity management means for calculating forecast information of parts based on notice information, arrangement information, and contract information, and parts For presenting the forecast information.

  ADVANTAGE OF THE INVENTION According to this invention, the forecast management system which shortens the order lead time from ordering of the parts used for a product to parts delivery, and shortens the product lead time from the product order in the order maker to product shipment is realizable.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
<< Overview of Forecast Management System S >>
In the forecast management system S according to the embodiment of the present invention, a product manufacturing maker (Company A and B, which will be described later) outsources the manufacture of semi-finished products constituting the product from its own order maker that receives product orders. When purchasing parts to be used for a product from a parts supplier of a parts supplier, the order maker (in-house) replaces the product manufacturer (Company A and B below) and purchases the parts. On the other hand, demand disclosure of parts used for semi-finished products, demand prediction, that is, forecasting is performed. It should be noted that the demand maker (in-house) also performs demand disclosure and demand prediction of parts used for products manufactured by the order maker (in-house).

As a result, even if the order maker (in-house) receives an order for a product of high-mix low-volume production, the order maker (in-house) and the product manufacturer (Company A and B below) will be able to The order lead time from part ordering to part delivery can be shortened, and finally the product lead time from the ordering of the ordering manufacturer to the product shipment can be shortened.
In addition, it is possible to properly order parts used for products and semi-finished products from the order maker (in-house) and product manufacturers (Company A and B below). Appropriate inventory of parts used for semi-finished products (company A and company B described later) becomes possible.

<< Overall configuration of forecast management system S >>
The forecast management apparatus 10 in the forecast management system S will be described in detail 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 in a forecast management system S is provided in an in-house order manufacturer that receives product orders, and 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 loading and unloading 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 the input / output terminal 60 used by an order maker in order to confirm the number of forecasts. Note that the parts deployment device 20, inventory management device 30, purchased product management device 40, information recording unit 50, and input / output terminal 60 are installed at an order maker in-house.

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 device 20, 30, 40, and CPU (Central Each processing unit is implemented by executing a corresponding program.
The parts unpacking device 20, the inventory management device 30, and the purchased product management device 40 may be stored in auxiliary storage devices of different servers, or 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.

In addition, the forecast management apparatus 10 has an input / output terminal 82 of a product manufacturer that outsources the manufacture of semi-finished products constituting the product by an order receiving manufacturer that receives the order of the product via a communication network 80 such as the Internet. Are connected to an input / output terminal 81 of a part manufacturer of a parts supplier from which a product manufacturer purchases a part to be used for a semi-finished product. Data communication with the manufacturer's input / output terminal 82 is possible.
Here, the input / output terminal 60 of the order manufacturer, the input / output terminal 81 of the parts manufacturer, and the input / output terminal 82 of the product manufacturer are shown as one terminal, but any number may be provided. Of course.

<< Forward Management Device 10 >>
Next, the configuration of the forecast management apparatus 10 will be described in detail.
The forecast management apparatus 10 is a server, for example, and is realized by a CPU (not shown) executing a forecast management program stored in an auxiliary storage device such as a hard disk. As shown in FIG. 1, a master information management unit 11, an arrangement information management unit 12, a forecast quantity management unit 13, and a forecast presentation unit 14 are implemented as corresponding programs.

In other words, the forecast management apparatus 10 has a master information management unit 11, an arrangement information management unit 12, a forecast quantity management unit 13, and a forecast presentation unit 14 when the installed forecast management program is executed by the CPU. Each function 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 collectively stored in one server. .
In addition, each program of the component deployment 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 forecast detailed information data file 515, a forecast information data file 516, and a takeover responsibility data file 517 are stored.
Hereinafter, these data files 501 to 517 will be described in order. In the data files 501 to 517, semi-finished products manufactured by company A and company B, which are product manufacturers, are also handled as products.

<< 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 for which the notice number is given. A certain product notice quantity and a product notice necessity period which is a requested 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 by 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 a product code of a product including a semi-finished product, a product production lead time of the product code, and a production company that produces the product.
Here, it is assumed that a product including a semi-finished product is requested to A, B, etc., a product manufacturer of the partner company, and the product code “S003” in the product manufacturing information data file 503 of FIG. ”Indicates that the product manufacturer is“ Company A ”, and the product manufacturer of the product code“ S004 ”is“ Company B ”. The production company in the case of production by the order maker sets “own”.

<< Part information data file 504 >>
FIG. 6 is a diagram showing a configuration of the component information data file 504 stored in the information recording unit 50 of FIG.
The component information data file 504 shows the following attributes of each component.
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 of the part 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 starting 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 postponement possible period are contracts with parts suppliers in forecast operation, and are expressed in days.
Depending on the requested 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 , Responsibility for taking over 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. If there is no change in the forecast quantity and the required delivery date, an order is placed to the parts supplier on the planned order date, that is, the order is placed. Issue a certificate.

Even if the forecast quantity is reduced 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 taking 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. With regard to forecast quantities in the period up to 11 days, takeover responsibility arises. If the required delivery date is January 10, the forecast quantity for which the takeover responsibility has occurred is the order lead time “5 days”. Orders must be placed by January 20th.

The ordering cycle represents 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 order maker until it can be used for production 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 that indicates whether or not the forecast operation is performed on the assumption of takeover responsibility. If “Yes”, the takeover responsibility is generated according to the above-mentioned contract, but “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 expanding the product for each notice number shown in the product notice data file 501 of FIG. 3 into parts, and records the production company that produces the product indicated by the product code. .
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 assigned for each noticed product code, the product Are associated with a part code of a part, a part notice quantity of a part of the part code, a part notice period of the part, and a production company that manufactures a product including a semi-finished product.

For the notice branch number, codes such as “01”, “02”,... Are used. For example, the product code “S001” for which the notice number “Y001” has been notified is assigned the notice technique number “01” because the product code “S001” is the first, and the notice number “Y002” has been given a notice. Since the product code “S001” is second, the notice branch number “02” is assigned to the product code “S001” of the product.
The part notice quantity is a part quantity necessary for producing a product with the product code noticed by the notice number. Each of the product notice quantity in the product notice data file 501 in FIG. 3 and each of the product parts table data file 502 in FIG. 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 requested delivery date of parts necessary for producing a product having the product code notified by the notice number. In this part notice period, the production lead time of the product production information data file 503 in FIG. 5 is traced back to the factory operating date from the product notice period in the product notice data file 501 in FIG. 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 date.
As the arrangement number, codes such as “T001”, “T002”,... Are used. For example, the arrangement number “T001” in FIG. 8 indicates that 10 products having the product code “S001” need to be arranged on May 21, 2007, which is the product arrangement period.

<< Ordered part data file 507 >>
FIG. 9 is a diagram showing the configuration of the arrangement part data file 507 stored in the information recording unit 50 of FIG.
The arranged parts data file 507 is an 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 allocated 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 with each other. As the arrangement branch number, codes such as “AI”, “A2”,... Are used.

For example, since the product code “S002” arranged with the arrangement number “T002” is the arrangement number where “S002” appears first, the arrangement branch number “A1” is assigned, and the arrangement number “T003” The product branch order “S002” is assigned the order branch number “A2” because “S002” is the order number that appears second.
The part arrangement quantity is the part quantity to be arranged necessary for producing the product of the product code arranged by the arrangement number. The product arrangement quantity in the product arrangement data file 506 in FIG. 8 and the product parts table data file 502 in FIG. It is a calculated value obtained by integrating the quantity of parts used for each product and expanding the parts table.
The part arrangement deadline is a required delivery date of parts necessary to produce a product having the product code arranged by the arrangement number. In this part arrangement period, the production lead time of the product production information data file 503 in FIG. 5 is traced back to the factory operation date from the product arrangement period in the product arrangement data file 506 in FIG. 8, and the part information data file 504 in FIG. This is the date that goes back the number of days of acceptance testing.

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

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

As shown in FIG. 10, the total necessary parts data file 508 includes a manufacturing company that manufactures a product including a semi-finished product, an arrangement number or an arrangement number / announcing number of an announcement number, the product code, a branch number, and the branch number. The part code of the included part, the part quantity of the part, and the part period of the part are associated with each other.
When the original file is the notice part data file 505 (see FIG. 7), the arrangement / notice number, branch number, part quantity, and part period of the total necessary parts data file 508 (see FIG. 10) are the notice part data file. This corresponds to the notice number 505 (see FIG. 7), notice branch number, parts notice quantity, and parts notice essential period.

When the original file is the arranged part data file 507 (see FIG. 9), the arrangement / notice number, branch number, part quantity, and part period of the total necessary parts data file 508 (see FIG. 10) are respectively arranged parts data file. This corresponds to the order number 507 (see FIG. 9), the order number, the part order quantity, and the part order period.
The total necessary parts data file 508 is managed for each arrangement / notice number in part code and part period. Further, the data of the arranged parts data file 507 (see FIG. 9) is registered in the total necessary parts data file 508 as data produced by the company.

<< 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 of each production company. In FIG. 11, the data of Company A and Company B are omitted.
As shown in FIG. 11, the inventory data file 509 is associated with the manufacturing company, the part code representing the part, and the inventory quantity of the part of the part code. Note that the stock quantity is registered by the stock management apparatus 30 (see FIG. 1), and the latest stock quantity is registered by managing the loading and unloading of parts by a well-known technique.
For example, the inventory quantity of the part code “B001” is 12 pieces.
Further, as shown in FIG. 11, the inventory information of product manufacturers such as Company A and Company B is also received via the communication network 80 (see FIG. 1) and registered in the inventory data file 509. It shall be.

<< 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 parts ordered for each production company for each order number.
As shown in FIG. 12, the order information data file 510 includes a production company, an order number as a unit of ordering, a part code of a part ordered with the order number, an order quantity when ordered with the order number, and an order quantity. The remaining order quantity after reducing the quantity received from, 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 requested delivery date for the deadline requested to the parts supplier, The order delivery period, which is the difference between the required delivery date and the order delivery date, and the delivery date of the delivery date that the parts supplier answered to the order number are associated with each other. In some cases, parts are 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 in FIG. The term year / week is defined as a consistent weekly NO for each year up to the week preceding January 1 of the following year, where the week including January 1 is the first week. For example, January 1, 2007 is the first week of 2007, and January 8, 2007 is the second week of 2007.
The order period is the difference between the requested delivery date and the order date, and is an item for distinguishing between an order for which an order lead time is secured and a short delivery order for which an order lead time is not secured in the processing described later. 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 expressed as a crack in the lead time later.
This ordering information data file 510 (see FIG. 12) is created from the planned order quantity in the part shortage quantity data file 511 of FIG. 13 below, and the ordering person at any timing has the part code, order quantity, and requested delivery date. May be specified.
Further, as shown in FIG. 12, the order information of the product manufacturer is also received through the communication network 80 (see FIG. 1) and registered in the order information data file 510.

<< Part shortage quantity data file 511 >>
FIG. 13 is a diagram showing a configuration of the component shortage quantity data file 511 stored in the information recording unit 50 of FIG.
The parts shortage quantity data file 511 shows detailed information for each part required period, which is a required delivery date of the part, for each part required for each manufacturing company.
As shown in FIG. 13, the parts shortage quantity data file 511 includes the production company, the part code of the ordered part, the default order lead time from the ordering date to the delivery date of the part, the ordering cycle, and the part delivery date. Acceptance test days that indicate the period that can be used after inspection, etc., order lots that are the minimum order quantity, parts deadlines that are parts delivery dates, the number of days from today (today) to the parts deadlines, and the quantity of parts in the parts deadlines , Inventory allocation quantity with inventory parts allocated, inventory remaining quantity after subtracting inventory allocation quantity from parts quantity, remaining order allocation provision quantity below, after order allocation reserve after subtracting inventory reserve quantity from inventory allocation remaining quantity The remaining quantity, 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 cycle, acceptance test days, and order lot are obtained by referring to the part information data file 504 in FIG.
“Days until the required period” is the difference between the component required period and the creation date of the component shortage quantity data file 511 (see FIG. 13), that is, the forecast data creation date.
The inventory allocation quantity is allocated to the part quantity in the order of the parts essential period of the part shortage quantity data file 511 of FIG. 13 until the inventory quantity referring to the inventory data file 509 of FIG. Result quantity.

The remaining order quantity is calculated by referring to the order information data file 510 in FIG. 12 with the part code to calculate the total value of the remaining order quantity, and after the inventory is allocated in order of the parts essential period in the parts shortage quantity data file 511 in FIG. This is the quantity resulting from the allocation to the remaining quantity.
The planned order quantity for the shortage quantity (before lot calculation) is calculated by comparing “Days until the required period” and “Order lead time + Order cycle + Acceptance test days”. “Remaining quantity after remaining order reservation” is set when it is equal to or less than “ordering lead time plus 10 acceptance period testing days”.
The forecasted quantity of the shortage (before lot calculation) is calculated by comparing “number of days until the required period” and “order lead time + order cycle + acceptance test days”. If it is larger than “10 ordering cycles and 10 acceptance test days”, “remaining quantity after remaining order placement” is set.

<< Parts supplier information data file 512 >>
FIG. 14 is a diagram showing a configuration of the parts supplier information data file 512 stored in the information recording unit 50 of FIG.
The parts supplier information data file 512 indicates the date on which the supplier of the parts has started the forecast publication expressed 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 a forecast, that is, a shortage quantity (before lot calculation) that has a forecasted quantity. is there.

  As shown in FIG. 15, the weekly parts shortage quantity data file 513 includes a production company that produces a product using the part indicated by the part code to be published, the part code of the part to be forecasted, The part release period, the week of January 1 every year, the first week of the week, and the week of January 1 of the following year, the week before January 1 of the following year, the forecast release year of the week, which is defined in the consistent NO. Associated with the cast release week, forecasted quantity.

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

<< Order Lot Calculation Data File 514 >>
FIG. 16 is a diagram showing the configuration of the order lot calculation data file 514 stored in the information recording unit 50 of FIG.
As shown in FIG. 16, in the order lot calculation data file 514, the production company, the order lot, the forecasted quantity, and the following previous presentation are shown for each forecast release week and each part code released for forecast. The quantity 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 tabulating the forecast scheduled quantity every forecast release week with reference to the weekly parts shortage quantity data file 514 of FIG. 15 by the production company and the part code.

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

To calculate the quantity before considering the number of lots, that is, this time (this week), the quantity of parts that do not take into account the number of lots to be cast is calculated by first calculating the cumulative number of forecasted quantities up to the nth week by ΣA (n), nth The current order quantity considering quantity up to a week is defined as ΣB (n), and the quantity before considering the number of lots up to the nth week is defined as ΣC (n). The quantity C (n) before the lot number in the n-th week is a quantity obtained by subtracting ΣC (n−1) from the larger quantity of ΣA (n) and ΣB (n).
For example, the quantity before considering the number of lots this week, that is, the number of parts that do not take into account the number of lots that will be cast this time (this week) is larger than the cumulative number of forecasts up to this week and the quantity before considering the number of lots up to this week. This is the quantity obtained by subtracting the quantity before the number of lots up to the previous week. In this way, the forecast forecast for this week is calculated by subtracting the forecast forecast quantity up to the previous week from the larger quantity of the forecast forecast quantity up to this week and the cumulative quantity of parts for which transaction responsibility has occurred. By calculating the quantity, it is configured not to purchase extra parts twice.

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.
Further, as shown in FIG. 16, a range of “ordering”, “quantity determination”, and “publication only” is defined for each subsequent week based on the part code and this week. For example, next week is +1 week, next week is +2 week, and so on.
For the range of “quantity determination”, the part information data file 504 (see FIG. 6) is referred to by the part code, and when the forecast target flag is “Yes” and the forecast contract data file 512 (see FIG. 14) Defined only when the forecast contract conclusion date has been set. For part codes that do 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, the “quantity determination” range is not defined, and “order” And only “open” scope is defined. In other words, the items other than “ordering” are “public only”.

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” on a daily basis, The range of “order” in weekly units is obtained from the range of “order”. The range of “ordering” in daily units 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.
Weekly “Purchase” range is considered as “Purchase Order” range if all dates included in each Forecast Release Week are included in the daily “Purchase Order” range. . For example, if the weekly schedule starts on Sunday and ends on Saturday, and if Wednesday is the daily "order" range, all dates included in the forecast release week are included in the daily "order" range. Therefore, the range up to the previous week is “ordering” in units of weeks.

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

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

<< Forcast Detailed Information Data File 515 >>
FIG. 17 is a diagram showing a configuration of the forecast detailed information data file 515 stored in the information recording unit 50 of FIG.
The forecast detailed information data file 515 shows detailed information on the previous forecast and the current forecast for each production company for each part code.
The forecast detailed information data file 515 is received (ordered and delivered) for each part code of a part used for a product produced by each production company, and has been ordered but not delivered. Indicates the quantity scheduled to be ordered.
As shown in FIG. 17, the forecast detailed information data file 515 includes the last order (normal order; order lead time can be observed) for each production company for each forecast release week and each forecasted part code. ), Last order remaining (lead time break; indicates short delivery time of order lead time break), previous order planned, current order remaining (normal order), current order remaining (lead time crack), current order planned ing.

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) this time is a quantity obtained by referring to the ordering information data file 510 (see FIG. 12) with a part code and totaling the remaining ordering quantities whose ordering period is less than the ordering lead time for each required year and week. .
The current ordering schedule is the quantity of the same part code and the same period year and week with reference to the forecast quantity in the order lot calculation data file 514 (see FIG. 16).
As shown in FIG. 17, for example, 20 items in the last +7 week of the remaining amount (normal order) for finalizing the quantity will be 20 in the current +6 week since one week has passed this time. In addition, 20 pieces of this time +7 weeks are for new orders.
In addition, 20 items in the last +7 weeks of the remaining quantity (lead time split) in the final quantity determination will be 20 in the current +6 weeks since the current one week has passed. In addition, due to contracts with parts suppliers, it is possible to set 20 items for this +7 week (shown in parentheses in FIG. 17) instead of 20 items for this +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 for +9 weeks in the period only for the release of the previous ordering plan are 30 pieces for +8 weeks for the quantity order to be ordered this time (in Fig. 17 It may be divided into 10 items (shown in parentheses in FIG. 17) of +9 weeks in the period of only disclosure. 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 of only release of the previous ordering schedule have passed one week, they are 50 pieces of +10 weeks of the period of only release of the scheduled ordering this time. In addition, due to product inquiries, due to contracts with parts suppliers, 50 weeks of +11 weeks in the period of only public release of the previous ordering have passed one week, but +11 weeks of the period of only public release of the current ordering scheduled It may be 50 (shown in parentheses in FIG. 17). In other words, this is the case when the customer's plan for inquiring about a product that uses these 50 parts can be sent for one week. In this case, this time +10 weeks is blank.
In addition, in the forecast detailed information data file 515 of FIG. 17, the difference between the current update content and the previous update content of the received parts quantity may be searched.

<< Forward Information Data File 516 >>
FIG. 18 is a diagram showing the structure of the forecast information data file 516 stored in the information recording unit 50 of FIG.
The forecast information data file 516 is a main screen that is disclosed to suppliers or production companies by production company, information for each part having parts suppliers by production company, and this week, next week +1 week, and next week. +2 weeks, ..., +15 weeks of ordering period, quantity determination period, and period of disclosure only.
As shown in FIG. 18, the forecast information data file 516 includes a production company, a parts supplier code, a part code, an order lead time, a quantity determination lead time in a period in which the takeover responsibility occurs, and a take-off postponement period during the take-off grace period. In addition, it shows the quantity that is the total of the remaining order (normal order), remaining order (breaking lead time), and planned order in the forecast detailed information data file 515 (see FIG. 17) in units of part code and release week. Yes.
The parts supplier code, the order lead time, the quantity confirmation lead time, and the take-off possible period are values obtained by referring to the part information data file 504 (see FIG. 6) with the part code.

<< collection responsibility data file 517 >>
FIG. 19 is a diagram showing a configuration of the takeover responsibility data file 517 stored in the information recording unit 50 of FIG.
The takeover responsibility data file 517 manages the parts that have entered the quantity lead time for which the takeover responsibility has occurred for each production company. In order to see how many parts have to be taken over, the deadline for taking over, etc. belongs to.
As shown in FIG. 19, in the takeover responsibility data file 517, the production company that produces the part, the part code for identifying the part, the takeover responsibility date for the part of the part code, and the takeover responsibility for the part of the part code are generated. The quantity determination lead time to be performed, the period for which the part code with respect to the part code can be postponed, the quantity of responsibility for taking over the part with the part code, and the order deadline for the part with the part code are associated.

The takeover responsibility occurrence date is the date when the takeover responsibility for the parts has occurred, and is the registration date in the takeover responsibility data file 517.
The quantity determination lead time is a value obtained by referring to the part information data file 504 in FIG. The take-off possible period is a value obtained by referring to the part information data file 504 of FIG.
With regard to the amount of responsibility for taking over, refer to the forecast detailed information data file 515 in FIG. This is the quantity obtained by subtracting, from the calculated quantity, the total quantity that has been accumulated up to the previous time of the take-off responsibility occurrence quantity in the previous take-off responsibility data file 517.

The order deadline is a date obtained by adding the quantity confirmation lead time and the take-off postponement period on the take-off responsibility occurrence date. The take-off responsibility generation quantity is calculated for each production company and part code, and when it is larger than 0, it is registered in the take-off responsibility data file 517.
Further, the ordering information data file 510 in FIG. 12 is referred to under the condition that the ordering date is larger than the last update date for each production company and part code, the total order quantity is calculated, and the takeover responsibility data file 517 in FIG. Orders for taking responsibility for delivery referenced in the code are ordered starting from those with the smallest occurrence date of take-off responsibility, and are therefore offset by the calculated order quantity in ascending order. The amount is canceled until the amount of occurrence responsibility becomes 0, or the total order amount generated when the occurrence date of receipt responsibility is late and the order date can be a later date becomes 0.
Next, various operations of 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 (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 includes fields for entering a product code, production lead time, and production company.
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 and the production company are acquired and transmitted (S13 in FIG. 20), and sent to the input / output terminal 60 to the production lead time and production company input fields. This is displayed (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 and production company input fields of the product production information registration screen G1 in FIG. Remains and nothing is displayed. FIG. 21 shows a case where “5” is displayed in the input field for the production lead time, and “in-house” is displayed in the input field for the production company, instead of “blank”.
Next, as shown in FIG. 21, the registrant inputs “5” in the input field of the production lead time in the “blank” state, and “own” in the input column of the production company in the “blank” state. (S15 in FIG. 20) and the registration button is clicked.
Then, the production lead time and the production company data are transmitted (S16 in FIG. 20), and the forecast management apparatus 10 (see FIG. 1) uses the product advance information entered by the registrant as the product production information in the information recording unit 50. Registration is made in the data file 503 (see FIG. 5) (S17 in FIG. 20).

<< Part Information Registration Processing in Master Information Management Unit 11 >>
Next, component information registration processing 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.
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, a part supplier code. There is an input field for a forecast target part flag.

First, the registrant uses the input / output terminal 60 shown in FIG. 1 to input “B001” or the like of the part code in the part code field of the part information registration screen in FIG. 23 (S21 in FIG. 22), and then search. Click the 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) to obtain the part name, order lot, order lead time, quantity confirmation lead time, take-off postponed period, order cycle, acceptance test days, parts supplier code, and forecast target part flag The data is transmitted (S24 in FIG. 22), and transmitted to the input / output terminal 60 (see FIG. 1) and displayed (S25 in FIG. 22).

If the corresponding product code does not exist as a result of referring to the component information data file 504 in FIG. 6, the input field of the forecast information registration screen G2 in FIG. Note that FIG. 23 shows a case where each entry field is displayed.
Next, the registrant, as shown in FIG. 23, the part name, order lot, order lead time, quantity confirmation lead time, take-off postponed period, order cycle, acceptance test days, parts supplier code, and forecast target The component flag is input (S26 in FIG. 22), and the 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, parts supplier information registration processing 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 (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 parts supplier information registration screen G3 in FIG. 25 includes an entry field for a parts supplier code, an entry field for a parts supplier name, and a forecast contract conclusion date.
First, the registrant uses the input / output terminal 60 of FIG. 1 to input “M001” 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). The supplier information data file 512 is referred to (S33 in FIG. 24), the parts supplier name and the forecast contract conclusion date are acquired and transmitted (S34 in FIG. 24), and transmitted to the input / output terminal 60 and displayed (FIG. 24). S35).
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 (see FIG. 1). ) In the parts supplier information data file 512 (see FIG. 14) (S38 in 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 a 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 a search button. Click.
Then, the input notice number is transmitted (S42 in FIG. 26), and the forecast management apparatus 10 (see FIG. 1) uses the notice number input by the registrant to notify the product recording notice of the information recording unit 50 (see FIG. 1). Referring to the data file 501 (see FIG. 3) (S43 in FIG. 26), the product code, the product notice quantity, and the product notice period are acquired and transmitted (S44 in FIG. 26), and transmitted to the input / output terminal 60 and displayed. (S45 in 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 advance notice inputs the product code, the quantity of advance notice of the product, and the product notice advance 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).

Registration in the product notice data file 501 checks whether or not the notice number to be registered has already been registered (S49 in FIG. 26). If registered (Yes in S49 in FIG. 26), the product notice data file is registered. 501 (see FIG. 3), 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 (S49a in FIG. 26). 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 of FIG. 26 that the notice number has not been registered in the product notice data file 501 (No in S49 of FIG. 26), the process proceeds to S49b of 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 the advance arrangement process for registration in the product arrangement data file 506 (see FIG. 8).
For example, when the arranger 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 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 advance 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.
In performing the product arrangement process, the arranger first uses the input / output terminal 60 of FIG. 1 to display the notice number “Y001” or the like that has been previously noticed in the notice number column of the product arrangement screen G5 of FIG. After inputting (S51 in FIG. 28), the search button is clicked.

Then, the input notice number is transmitted (S52 in FIG. 28), and the forecast management apparatus 10 in FIG. 1 displays the information recording unit 50 (see FIGS. 1 and 2) with the notice number input by the registrant. 3 is obtained (S53 in FIG. 28), the product code, the product notice quantity, and the product notice period are acquired (S54 in FIG. 28), and transmitted to the input / output terminal 60 and sent to the product arrangement screen G5 ( The product code (see FIG. 29), the product arrangement quantity, and the product arrangement period column are displayed (S55 in FIG. 28).
If there is no corresponding product code as a result of referring to the product notice data file 501 in FIG. 3, the input field of the product arrangement screen G5 in FIG. 29 is 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. Furthermore, after entering the arrangement number “T001” or the like in the arrangement number field on the product arrangement screen (S56 in FIG. 28), the search 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 has already been registered (Yes in S59 in FIG. 28), the product notice is displayed. The data 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) 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, if the notice number has not been registered in S59 of FIG. 28 (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, referring to the take-off responsibility data file 17 of FIG. 19 of the cast with the ordered part code, if there is a record with take-off responsibility, an 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 part 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.
Further, the above-mentioned takeover responsibility file 517 of FIG. 19 is registered.

<< Forward presentation for parts suppliers in forecast presentation section 14 >>
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, when company A, a parts supplier or product manufacturer, logs in to the forecast presentation unit 14 (see FIG. 1) of the forecast management apparatus 10 using the input / output terminal 81 or the input / output terminal 82 of FIG. A forecast release screen G6 of the input screen shown in FIG. 30 is displayed on the input / output terminals 81 and 82. Note that FIG. 30 is a diagram showing a forecast release screen G6 displayed when referring to the forecast.
The forecast release screen G6 of FIG. 30 includes display items of a production company, a parts supplier code, a parts code, an order lead time, a quantity confirmation lead time, a postponement possible period, and a public week.

The data published on the forecast publication screen G6 in FIG. 30 is only the data of the product manufacturer to which the logged-in login user belongs to the product manufacturer in the forecast information data file 516 in FIG. For the parts supplier, only the data of the parts supplier code to which the logged-in logged-in user belongs is used (see FIG. 30). Here, it is assumed that the ordering company can refer to all data in the forecast information data file 516 in FIG.
A user who can log in is provided with a security management means in order to give an ID and a pass and to disclose information on the ID and the pass.

30 is selected by clicking each column of the consistent NO (not shown) attached to each part code displayed on the forecast release screen G6 in FIG. 30, and the forecast detail release screen G7 in FIG. Is displayed. FIG. 31 is a diagram showing a forecast detail disclosure screen G7 displayed on the input / output terminals 60, 81, and 82 (see FIG. 1) when referring to the forecast details.
It is assumed that the data disclosed on the forecast details disclosure screen G7 refers to the forecast details information data file 515 of FIG. 17 with the production company and part code of the selected forecast quantity.

<< Forward presentation for product manufacturers in forecast presentation section 14 >>
The above-mentioned forecast release screen G6 (see FIG. 30) and forecast detail release screen G7 (see FIG. 31) are basically for each product manufacturer of the manufacturing company, for example, company A, company B only The public screen is configured to be visible, and the component supplier of the component supplier is configured to be able to visually recognize the screen that has been publicly released for its own component supplier code.
On the other hand, the company that receives orders for products and requests the manufacture of semi-finished products for product shipments from company A, company B, etc., is a subject that is publicly available. 30 is configured so that the forecast release screen G6 shown in FIG. 30 and the entire forecast detail release screen G7 shown in FIG. 31 can be visually recognized.

That is, company A, which is the production company, displays a forecast release screen G6 (see FIG. 30) whose production company column is company A on the screen of the input / output terminal 82 shown in FIG. The cast details disclosure screen G7 (see FIG. 31) is displayed.
Further, company B, which is the production company, displays a forecast release screen G6 (see FIG. 30) in which the column of production company is company B on the screen of the input / output terminal 82 shown in FIG. The cast details disclosure screen G7 (see FIG. 31) is displayed. As described above, the data to be disclosed on the forecast disclosure screen G6 in FIG. 30 is limited to the component supplier code to which the logged-in user who logged in belongs in the forecast information data file 516 (see FIG. 18).

Further, the parts maker who is the parts supplier displays the forecast disclosure screen G6 (in which the parts supplier code is its own in the forecast release screen G6 shown in FIG. 30 on the screen of the input / output terminal 81 shown in FIG. 30) is displayed, and the forecast details disclosure screen G7 (see FIG. 31), which is the details of this screen, is displayed. As described above, the data to be disclosed on the forecast disclosure screen G6 in FIG. 30 is limited to the component supplier code to which the logged-in user who logged in belongs in the forecast information data file 516 (see FIG. 18).
On the other hand, an order maker's own company that receives an order for a product, ships the product, and releases the parts used in the product for forecast release, displays the foreword shown in FIG. 30 on the screen of the input / output terminal 60 shown in FIG. The entire cast disclosure screen G6 and the forecast details disclosure screen G7 shown in FIG. 31, which is the details of the forecast disclosure screen G6, are displayed.

The data published on the forecast release screen G6 (see FIG. 30) and the forecast details release screen G7 (see FIG. 31) is the fork data file 515 (see FIG. 17) with the production company and part code of the selected forecast quantity. Is the lead.
According to the above configuration, the order maker provides forecast information according to the forecast contract information to parts suppliers and subcontracted product manufacturers based on advance notice information including outsourced products and arrangement information after the specification is finalized. A forecast management device is provided. The notice information includes the production company, and the parts supplier can refer to the forecast from the manufacturer and the forecast from the production company, respectively.

<< Summary >>
Based on the advance notice information including outsourced products such as Company A and Company B, and the arrangement information after the specification is confirmed, the order receiving manufacturer, which is the company that receives the product orders, will receive the forecast information according to the forecast contract information as a part. Is provided with a forecast management apparatus 10 for providing the parts to suppliers who purchase The notice information includes company A, company B, etc., who are product manufacturers, and the parts suppliers have forecast and production from the manufacturer of the order (displayed in the column of “production company” for each file). It is possible to refer to forecasts from company A, company B, etc., which are product manufacturers of the company.

Therefore, it is possible to provide parts forecasts to parts suppliers for products manufactured by companies A and B, which are product manufacturers, as well as the companies A and B, which are order manufacturers, By shortening the order lead time from part ordering to part delivery, it is possible to ultimately shorten the product lead time from the order of the product of the company that is the ordering manufacturer to the product shipment.
In other words, regardless of the products that the company manufactures, it is possible to provide part forecasts to parts suppliers for products manufactured by product manufacturers of contract manufacturing companies. By shortening the lead time, the product lead time from product order to product shipment can be shortened.

  In the present embodiment, the case where the order maker (in-house) performs forecasting of parts used in the product manufactured by the order maker (in-house) is exemplified. You may perform only the forecast of the parts which product manufacture manufacturers, such as A company and B company, do not perform forecast of parts.

In a production system in which customer specifications are generated individually, from the order of the parts that make up the product compared to the product lead time from the product order of the ordered manufacturer requested by the customer who orders the product to the ordered manufacturer to the product shipment of the ordered manufacturer When the lead time for ordering parts is large, it is indispensable to shorten the lead time for ordering parts, and as a means for this, it is necessary to present forecasts to parts suppliers.
However, when subcontracting production to a product manufacturer that is a partner company of another company (corresponding to Company A and Company B in this embodiment), parts are purchased from the supplier (Parts A and B). Is equivalent).

Therefore, the contract lead time from ordering of parts used for products to parts delivery is shortened, and the product lead time from the final product order of the company including parts purchase to product shipment is shortened by the partner company. There is a problem that product manufacturers (equivalent to Company A and Company B) are relied upon.
In order to solve this problem, there is a possibility of applying the business model according to this patent, which is a proxy forecast of a manufacturer of orders received from a customer (in this embodiment, equivalent to the company).

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 of 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 takeover 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 of 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 notice arrangement process for registering in a product notice data file. It is a figure which shows the product arrangement screen of the input screen displayed on an input / output terminal in prior notice arrangement processing. It is a figure which shows the forecast public screen displayed when referring a forecast. It is a figure which shows the forecast details public screen displayed when referring to forecast details.

Explanation of symbols

11 ... Master information management unit (part information management means),
12 ... Arrangement information management department (arrangement information management means),
13 ... Forecast quantity management department (forecast quantity management means),
14 ... Forecast presentation section (forecast presentation means),
20 ... Parts deployment device (arrangement information management means, forecast quantity management means),
30 ... Inventory management device (forecast quantity management means),
40 ... Purchased goods management device (forecast quantity management means),
50. Information recording part (arrangement information management means, parts information management means, forecast quantity management means, forecast presentation means),
60: Input / output terminal (input / output means),
70: Communication network (input / output means),
80: Communication network (input / output means for parts suppliers, input / output means for production consignment companies),
81 ... Input / output terminal of parts manufacturer (input / output means for parts suppliers)
82 ... Product manufacturer's input / output terminal (input / output means for contract manufacturing company)
Company A, Company B ... Product manufacturer (Manufacturing consignment company)
S ... Forecast management system

Claims (7)

Arrangement information management means for managing and processing notice information on unordered parts of parts used for products and arrangement information on ordered parts of the parts;
Parts information management means for managing contract information related to parts purchase with parts suppliers who purchase the parts for each part;
Forecast quantity management means for calculating forecast information of parts based on the advance notice information, the arrangement information, and the contract information;
A forecast management system comprising: forecast presenting means for presenting forecast information of the part. In the forecast management system according to claim 1,
Input / output means for input / output;
A forecast management system comprising: a component supplier input / output unit for displaying forecast information of a component presented by the forecast presenting unit. In the forecast management system according to claim 2,
When the production of the product is outsourced to a production consignment company including the purchase of parts used for the product,
The arrangement information management means manages and processes notice information on unordered parts of parts used for products produced by the production consignment company and arrangement information on ordered parts of the parts,
The part information management means manages and processes contract information related to part purchase with a part supplier who purchases the part for each part used in a product produced by the production consignment company,
The forecast quantity management means calculates forecast information of parts related to the production consignment company based on the advance notice information, the arrangement information, and the contract information,
The forecast presenting means presents forecast information of parts related to the production consignment company. In the forecast management system according to claim 3,
A forecast management system comprising input / output means for a production consignment company for displaying forecast information of the part presented by the forecast presentation means. In the forecast management system according to claim 2,
The forecast presenting means displays the forecast information of parts for the parts supplier on the input / output means for parts suppliers, and hides the forecast information for other parts suppliers. A featured forecast management system. In the forecast management system according to claim 4,
The forecast presenting means displays the forecast information of the parts from the production consignment company to the parts supplier on the input / output means for the production consignment company, and also displays the parts information from other production consignment companies to the parts supplier. A forecast management system characterized by hiding forecast information. In the forecast management system according to claim 3,
The forecast quantity management means calculates the forecast information of the part by subtracting the quantity of the part in the inventory when the production consignment company has the inventory of the part.

Images