# Patent

## Title
System and process for supply management for the assembly of expensive products

## Abstract

A Managing component supply for complex products is achieved by monitoring the delivery performance of component suppliers and optimizing the times at which orders are placed. Supply delivery performance targets are set for each supplier, and component order times are optimized by 1) optimizing safety stock for each component, 2) calculating optimal times to place supply orders in order to maintain the safety stock level, and then 3) iterating safety stock calculations in order to minimize overall inventory costs and maximize supply availability. The process takes into account supply lead times, component costs, and target tolerances for delays in the assembly of components. The effects of changes in supply lead time performance on assembly schedules are projected for planning purposes.

## Background
CROSS REFERENCE TO RELATED APPLICATION
This application is a continuation of parent application Ser. No. 11/434,283 now U.S. Pat. No. 7,418,307 May 16, 2006 which is incorporated herein by reference.


BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention generally relates to supply management, and in particular to techniques for optimizing supply management for the assembly of expensive products.
2. Background Description
There are numerous prior art methods and systems that manage inventory. Since inventory problems can show substantial variations depending on the industry, process, supply network, and product characteristics, there is a proliferation of academic publications as well as patents covering inventory management.
U.S. Pat. No. 7,016,764 to Penkar et al., “Inventory management system for reducing overall warehouse and pipeline inventory” discloses an inventory management system for warehouse and pipeline inventory. The system is designed to provide regular shipments of parts to multiple manufacturing facilities from a hub via an expedited delivery service. The objective of the design is to reduce the amount of safety stock needed to support the operations of the manufacturing facilities.
U.S. Pat. No. 6,983,189 to Lu, “Systems and methods for manufacturing a product in a pull and push manufacturing system and associated methods and computer program products for modeling the same” has a system of manufacturing a product in a pull and push planning environment where products consist of multiple subassemblies which have multiple components. The system includes an order scheduler, a component scheduler, a make-to-order (MTO) portion and an assemble to order (ATO) portion. This is done for multi-plant systems.
U.S. Pat. No. 6,970,756 to Levionnois, “Computer-assisted pull flow production management method” discloses a method to manage component inventory using kanbans.
U.S. Pat. No. 6,594,535 to Costanza, “Material and inventory control system for a demand flow process” discloses a material flow design computer system that designs and monitors material to the production paths of a manufacturing line using a replenishment card pull sequence. Its objective is to monitor the product flow through replenishment pull sequence so as to insure that material arrives as needed at the point-of-usage on the production path and that the quantity of material stored at the manufacturing plant is minimized.
U.S. Pat. No. 6,516,301 to Aykin, “Order-based material management system” has an order based materials management method using forecasts of actual customer orders to determine component stocking levels. Orders are specified by bills of materials. Quantities of the components required in the bill of material have multivariate probability distributions and they can be correlated. The method calculates target number of replenishment orders for components using target order fill rate, replenishment lead times, demand forecasts, forecast error variances and their distributions. The method also calculates order-up-to periodic inventory policies (including safety stocks) for components and subassemblies.
U.S. Pat. No. 5,963,920 to Rose et al., “Inventory control system and method”, discloses a method and system for managing inventory of bulk commodities from a remote location. A rack storage unit at the point of use of the parts has multiple levels each having side by side rows for storing boxes of the parts. The rows are inclined downwardly from back to front to effect gravity feeding of the boxes toward the front. Each row has plural sites which may be occupied by a box, and a sensor senses whether a box is present at or absent from each site. Electrical signals from the sensors are processed and transmitted to the parts supplier at a remote location. The supplier receives a display containing information as to which sites are occupied and which are vacant. The supplier can respond by shipping parts that are indicated to be in short supply.
U.S. Pat. No. 5,946,662 to Ettl et al., “Method for providing inventory optimization”, discloses a method for providing inventory optimization for levels of products in a complex supply chain network for multiple internal suppliers or manufacturer locations and external distributors or retailer locations. The invention constructs a representative supply chain network model to indicate the flow of products between internal and external locations, it determines inventory levels and fill rates to meet the service level requirements, calculates a total inventory cost for all products in the network, and optimizes the fill rates.
U.S. Pat. No. 5,630,070 to Dietrich et al., “Optimization of manufacturing resource planning”, discloses a method for constrained material requirements planning, optimal resource allocation, and production planning provides for an optimization of a manufacturing process by designating the amounts of various manufactured products to be produced, which products include both end products as well as subassemblies to be employed in the manufacture of one or more of the end products. In order to accomplish the optimization, the method employs an objective function such as the maximization of income. In the method, the data describing elemental steps in the manufacturing process for the production of each end product, as well as the quantity or demand for each end product which is to be supplied, are presented as a set of linear mathematical relationships in matrix form to be inserted in a computer which determines the optimum number of each end product in accordance with an LP optimization algorithm. The matrix contains bill of material data, and various constraints.
U.S. Pat. No. 6,415,266 to Do, “Dynamic instruction system for input of parts in vehicle production line”, discloses a dynamic instruction system for the input of parts in a vehicle production line which, based on vehicle type information at each process as well as dynamic production plans, performs computations on a variety of data in order to provide parts input information to both equipment in the production line and to workers such that parts can be provided as they are needed. The system is claimed to prevent the presence of defective parts at processes in the production line and in a parts storage area, and to provide optimum stock levels such that capacity utilization and productivity are enhanced.
U.S. Pat. No. 5,819,232 to Shipman, “Method and apparatus for inventory control of a manufacturing or distribution process”, discloses a method and an apparatus, using a computer model, to control a manufacturing or distribution process, which determines a demand forecast by using an optimized historical weighting factor, determines an upper and a lower bound of a planned inventory by explicitly accounting for the customer order lead time, and computes a production schedule at predetermined intervals to maintain an actual inventory between the upper and lower bounds of the planned inventory.
U.S. Pat. No. 5,611,051 to Pirelli, “Point of supply use distribution process and apparatus”, discloses a method of using a central computer and work station for managing inventory. To dispense inventory to consumers, a system user is issued a card imprinted with a personal user bar code. This user bar code is read into the computer and subsequently verified through the entry of individual user access data to ensure the user is authorized. The issued-item data is communicated to a central computer, where the issued item is decremented from inventory data. The central computer determines when and in what quantity to replenish each item from the inventory data. A replenishment order is processed by the central computer, and the replenishment order is transmitted to a vendor.
U.S. Pat. No. 5,287,267 to Jayaraman et al., “Methods for parts procurement quantity determination where demand is uncertain for the product in which the parts are used”, discloses a method for predicting parts procurement requirements for products over multiple time periods, with parts common to multiple products. The actual demand for the products is uncertain, but the method assures that a specified service level is met for all products and minimizes expected excess part inventories. The method is provided with inputs, which, among others, includes lists of parts for each product, prices for the parts, and demand forecasts for each product in each time period, each forecast in the form of a mean and standard deviation. The description of the problem includes an objective function of minimizing expected excess inventory while satisfying the constraint that a specified service level be achieved. Solution is provided using Lagrange multiplier technique. Additional methods are described for improving the procurement decisions to more closely meet the service requirement.
In all of the above patents (with the exception of U.S. Pat. No. 6,983,189, which is discussed in the next paragraph) the methods disclosed are for managing inventory volumes to support some manufacturing or distribution activity. Managing inventory volumes means using policies such as base-stock levels, lot size or order-up-to levels. Such methods are quantity driven. In other words, they trigger replenishment orders when inventory levels drop to a threshold quantity. They are appropriate methods when usages of components, products or parts are at high volumes. However, quantity-based inventory policies do not perform well for scheduling manufacturing assembly of complex products, simply because they do not allow triggering replenishment orders at any point in time; they trigger orders only if inventory levels drop to a threshold level. For instance, if a component is needed once every 2 months, quantity-based policies will wait an average of 2 months to trigger an order while it might be better to time the order more accurately sometime within the 2 month period. Furthermore, when there are thousands of components that have to come together to perform an assembly, the quantity-based safety stocks can be prohibitively high. For instance, consider a complex product that needs a thousand different types of components for its assembly. If the assembly has to start on time with 99% probability and supply lead times for components are uncertain, then each component has to have a safety factor of at least 4.25. This requires extremely high levels of component inventories and therefore may be too costly. In such cases, there is a need for a fundamentally different method to managing inventory.
U.S. Pat. No. 6,983,189 is an exception to the others mentioned above. It generates order schedules. Generating some kind of supply order schedule is not new. There are procurement systems that suggest order times. For instance, standard MRP (Material Requirements Planning) also schedules component orders but ignores the impact of uncertainty in lead times. Furthermore, MRP is quantity based (i.e. schedules orders of lots), and it does not focus on the best time to trigger an order for an individual part when managing a low volume manufacturing environment.
What is needed is a method for effectively managing supply for products that are expensive to assemble such as aircraft, heavy equipment and machinery. Supply inventory management of such products needs a different approach than those described in the prior art. Known techniques that are implemented in commercially available software are not adequate. Known techniques are designed for high volume products that tend to be less expensive and typically sell in hundreds or thousands in weekly volume.
However, for highly expensive items such as aircraft or heavy machinery, weekly volumes for each model or part number tend to be much smaller. Even the largest manufacturers make just a few items per week. In addition, due to product complexity, there are tens of thousands of components that have to be supplied to do the manufacturing. Furthermore, replenishment lead times for these components are uncertain. Therefore, management of component supply needs a different approach for such products. The challenge is twofold: 1) how to make sure that random variation in supply replenishment lead times does not disrupt the manufacturing activity due to supply shortages, and 2) how to minimize supply safety stock so that supply inventory turns are maximized.
In general, these two objectives are in conflict for any inventory management problem. For expensive items, the problem is particularly challenging. On the one hand, because expensive items tend to have an expensive manufacturing operation, maximizing manufacturing line utilization is an important goal. Therefore, supply must be available at very high levels of confidence. On the other hand, because tens of thousands of components must to be available simultaneously, each component must have extremely high levels of availability to support smooth operations of the manufacturing line. When random variation of supply replenishment lead times is added to this statement of the problem, one is required under conventional safety stock management methods to hold very high levels of component supply. But this is prohibitively expensive for a product which must be assembled from a very large number of component parts. An efficient process needs to be put in place in order to manage supply inventories at reasonable levels and still achieve smooth manufacturing operations for such products.
SUMMARY OF THE INVENTION
It is therefore an object of the present invention to provide a system and process which manages supply inventories at reasonable levels while still achieving smooth manufacturing operations.
Another object of the invention is to maximize manufacturing line utilization for the assembly of expensive products by assuring very high levels of confidence in the availability of component supplies.
A further object of the invention is to minimize safety stock levels so that inventory turns are maximized.
It is also an object of the invention to accommodate uncertainties in supply replenishment lead times for component supplies while at the same time keeping inventories at reasonable levels.
The invention accomplishes these objectives by generating order timing through a fundamentally different and novel process. The method of the present invention takes into account uncertainty in supply lead times and calculates the best time for triggering each order for each component in relation to other components, their inventory carrying costs, and on time assembly start target probability. When followed, the method of the present invention can achieve on time assembly start performance (in a statistical sense) with minimum possible component inventory carrying costs.
The present invention operates by carefully monitoring and managing the on-time delivery performance of component suppliers. Acceptable on-time delivery performance targets are calculated, along with tolerances for delay in shipment. These are communicated to suppliers, and the performance of suppliers against these targets is monitored closely. Based on these monitored supplier performance levels and scheduled manufacturing due dates, the invention triggers supply orders at optimal times so that supply inventory is minimized and supply shortages are avoided.
Furthermore, the invention provides projections of assembly delays and “can-deliver” dates in response to changes in supply lead time performance, and these projections can be used by managers to seek improved delivery times from suppliers.
An aspect of the invention is a system for managing component supply for assembly of complex products. The system comprises a monitoring engine for prompting improved supply lead time performance of suppliers of components of a complex assembly, and an optimization engine for using the improved supply lead time performance to generate supply order times that keep an expected supply delay for a component within a target delay tolerance for the component.
In another aspect of the invention, the monitoring engine further comprises, for each component, means for measuring an historical record of delivery delay by the supplier, means for obtaining from the supplier at periodic intervals an estimated delivery delay for each component item in a delivery pipeline, and means for calculating in a delivery pipeline an improvement factor that compares the estimated delivery delay with the historical delivery delay.
In a further aspect of the invention, the optimization engine further comprises means for selecting for each component an inventory policy for determining a safety factor for the component, means for calculating a safety factor for each component in accordance with the selected inventory policy, means for determining a target delay tolerance for each component, means for calculating an expected supply delay for each component, and means for calculating the supply order time for each component so that the expected supply delay is within said target delay tolerance.
Another aspect of the invention provides means for presenting to a manager projections of an effect of an unexpected supply delay for a component upon an assembly schedule for the complex assembly, and means for the manager to request from a supplier of the component faster delivery of the component in response to the projection.



BRIEF DESCRIPTION OF THE DRAWINGS
The foregoing and other objects, aspects and advantages will be better understood from the following detailed description of a preferred embodiment of the invention with reference to the drawings, in which:
FIG. 1 is a schematic diagram showing a high level architecture for a system implementing the invention.
FIG. 1A is a schematic diagram showing a portion of the architecture providing system information support for managing suppliers.
FIG. 2A is a table (Table 136) illustrating exemplary purchase order data for a system implementing the invention.
FIG. 2B is a table (Table 134) illustrating exemplary supply lead time data for a system implementing the invention.
FIG. 2C is a table (Table 132) illustrating exemplary supply lead time statistics for a system implementing the invention.
FIG. 2D is a table (Table 112) illustrating exemplary supplier performance data for a system implementing the invention.
FIG. 2E is a table (Table 144) illustrating exemplary assembly delay target tolerance data for a system implementing the invention.
FIG. 2F is a table (Table 140) illustrating exemplary component cost data for a system implementing the invention.
FIG. 2G is a table (Table 138) illustrating exemplary supply order status data for a system implementing the invention.
FIG. 2H is a table (Table 142) illustrating exemplary inventory policy type data for a system implementing the invention.
FIG. 2J is a table (Table 122) illustrating exemplary optimal supply order times data for a system implementing the invention.
FIG. 2K is a table (Table 152) illustrating exemplary supply order schedule data for a system implementing the invention.
FIG. 2L is a table (Table 124) illustrating exemplary assembly delay projection data for a system implementing the invention.
FIG. 2M is a table (Table 126) illustrating exemplary “can-deliver” dates data for a system implementing the invention.
FIG. 2N is a table (Table 128) illustrating exemplary what-if analysis data for a system implementing the invention.



DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT OF THE INVENTION
Supply inventory management for the assembly of complex products presents challenges that are not adequately addressed by conventional techniques. These challenges may be understood by reference to the following attributes characteristic of such assemblies. First, these products and their manufacturing operations are expensive. Therefore, there is a premium on efficient utilization of the manufacturing line. Second, while the volume of product produced in the manufacturing line is relatively low, the number of components may be quite large and vary widely in price. Third, supply lead times between order and delivery not only vary widely from component to component but have a degree of uncertainty for any given component. This makes it difficult to assure that component supplies are always available for the manufacturing line and, at the same time, to minimize safety stock levels.
The key to managing supply inventory in an environment as described above is to manage on time delivery performance of the suppliers. In order to do this, the manufacturer needs to calculate acceptable on time delivery performance targets and shipment delay tolerance levels. These targets need to be communicated to the suppliers, and the performance of the suppliers needs to be monitored very closely against these targets. In addition, based on supplier performance levels, and scheduled manufacturing due dates, the manufacturer needs to trigger supply orders at optimal times so that two objectives are met simultaneously: supply inventory is minimized, and supply shortages are avoided.
This invention describes how to both set performance targets and monitor optimal supply timing through a process that manufacturers can use to maintain high supply availability with minimal possible supply inventory. The method consists of the following elements: 1) a process of setting supply delivery performance targets for each supplier; 2) a process of monitoring and managing supply delivery performance for each supplier; 3) a process of optimizing safety stock for each component; and 4) a process of estimating supply shortage probabilities, amount of manufacturing delays due to component shortages and the chances of being able to start/complete manufacturing on a given date.
The invention has two parts to it, as shown in FIG. 1, which is a system implementing the invention. The first part is a supplier performance monitoring engine 110. The second part is a component inventory optimization engine 120. The supplier performance monitoring engine 110 allows setting business rules between suppliers and the manufacturer. These include tolerance levels for supply delays, on time delivery performance targets, etc. Each supplier is monitored closely for their performance to these targets. Their performance is recorded and regular performance statistics are generated. If targets are not met, alerts are created and implications in terms of supply availability and manufacturing delays are reported. The component inventory optimization engine 120 calculates optimal times 122 to place supply orders for each component (which is in turn used by a conventional Material Requirements Planning (MRP) engine 150 to provide a supply ordering schedule 152).
The optimization engine 120 also computes a projection of product assembly delays 124 and “can-deliver” dates 126, as well as performing a “what-if” analysis 128 of scenarios based on alternative assumptions. These calculations are useful for business operations. Although optimal order times are the key to managing performance, operational metrics such as “can-deliver” dates and “assembly-delays” can vary because of uncertainties that cannot be predicted or resolved. These real world uncertainties can be modeled as random variations (as is done with the model shown in FIGS. 2A through 2N), but managers must respond to these uncertainties as they arise. Since these uncertainties have an effect on “can-deliver” dates, “assembly-delays” and other operational metrics, it is helpful to report projections of these metrics to the business decision makers so that they can take actions to make improvements. This is shown in FIG. 1A, where projections 124, 126 and 128 are presented at display 160 so that manager 170 can contact supplier 180 to provide improved delivery, which is then reported back as updated supply order status 138 in component data 100.
For instance, if can-delivery dates are not acceptable due to excessive supply delays, they can call the suppliers to request faster delivery. The system reports projected delays for each component and hence enables managers of operations to identify which supplier to call to shorten or eliminate the assembly delays 138 (see FIG. 2G).
The optimization provided by engine 120 is based on a variety of factors, including supply lead time statistics 132 (computed from supply lead times 134, in turn computed from historical purchase order data 136), supply order status 138 and component costs 140. The type of inventory policy 142 for the component also enters into the optimization calculation, as does an assessment by product managers of target tolerances for assembly delay 144. The engine 120 calculates the optimal times 122 of advance supply orders in order to minimize supply inventory and maximize supply availability, as described below.
The following notations will be used in further describing the workings of the system shown in FIG. 1 for implementing the invention:

    
    
        J[i]: Total number of historical supply orders for component i.
        I[k]: Number of different components needed for assembly process k.
        i: Index representing components (i=1, . . . , I[k])
        j: Index representing orders (j=1, . . . , J[i])
        k: Index representing assembly processes (k=1, . . . , K)
        DSO[i,j]: Date when the supply order is placed for component i and order j.
        DSR[i,j]: Date when the supply is received for component i and order j.
        EDSR[i,j]: Estimated date of supply order arrival for component i and order j.
        COST[i]: Cost per unit of component i.
        There are three groups of statistics based on lead time: historical, current and improvement.
        HSLT[i,j]: Historical supply lead time for component i and order j.
        HASLT[i]: Historical average supply lead time for component i.
        HSSLT[i]: Historical standard deviation of supply lead time for component i.
        HMINSLT[i]: Historical minimum supply lead time for component i.
        HMAXSLT[i]: Historical maximum supply lead time for component i.
        CSLT[i,k]: Supply lead time for component i and assembly k.
        CASLT[i]: Current average supply lead time for component i.
        CSSLT[i]: Current standard deviation of supply lead time for component i.
        CMINSLT[i]: Current minimum supply lead time for component i.
        CMAXSLT[i]: Current maximum supply lead time for component i.
        IASLT[i]: Improvement in supply lead time for component i.
        ISSLT[i]: Improvement in standard deviation of supply lead time for component i.
        IMINSLT[i]: Improvement in minimum supply lead time for component i.
        IMAXSLT[i]: Improvement in supply lead time for component i.
        The following notations apply to inventory policy and the safety factors applicable to each policy.
        POLICY[i]: Inventory policy type for component i.
        OSFACTOR[i]: Optimal safety factor for timing the supply order for component [i].
        FSFACTOR[i]: Fixed safety factor for timing the supply order for component [i].
        ASFACTOR[i]: Availability target based safety factor for timing the supply order for component [i].
        WSFACTOR[i]: Worst case safety factor for timing the supply order for component [i].
        SFACTOR[i]: Safety factor to be used in calculating the safety lead time for component i.
        The following notations apply to lead time calculations.
        SLTIME[i]: Safety lead time for component [i].
        OLTIME[i]: Optimal supply order lead time for component i.
        OOTIME[i,k]: Optimal order time (date) for component i to be used in product k.
        ATARGET[i]: Availability probability target for component i.
        DTARGET[i]: Supply delay target (tolerance) for component i.
        ESDP[i,k]: Expected supply delay for component i and assembly k beyond planned assembly date.
        ESDR[i,k]: Expected supply delay for component i and assembly k beyond requested assembly date.
        SSD[i,k]: Status of supply delay given by the supplier for component i and assembly k.
        JSD[i,k]: Net supply delay of component i for assembly k for joint component availability target of CLEVEL[k].
        TESDP[k]: Total estimated supply delay for assembling process k (in days) beyond planned assembly date.
        TESDR[k]: Total estimated supply delay for assembling process k (in days) beyond requested assembly date.
        PSTART[k]: Date of planned final assembly process k.
        RSTART[k]: Date of requested final assembly for process k.
        CLEVEL[k]: On time assembly confidence level for assembly process k. It is also the target probability of on time start of assembly process k (i.e. joint availability probability of all components for process k so that process k can start at the planned start date).
        CSTART[k]: “Can start” date of assembly process k with confidence level CLEVEL[k].
        ASLTCHANGE[i]: Change (in percentages) in average supply lead time for component i.
        SSLTCHANGE[i]: Change (in percentages) in standard deviation of supply lead time for component i.
        PONTIMEA[k]: Probability of on time start of assembly process k.
        PONTIMEC[k]: Probability of on time arrival of component i for assembly k.
    
    


In the mathematical formulas that follow, the superscript “2” means the square of the number to which it is applied. Similarly, the superscript “1/2” means the square-root of the number to which it is applied. The brackets “(”, “)” are used in proper mathematical sense and they determine the priority of calculations. Furthermore, the standard convention is adopted to prioritize algebraic operations addition “+” and multiplication “*”. That is, operations “*” and “/” take precedence over operations “+” and “−” when they are not separated by “(”, and “)”.
Some common functions used are also defined as follows:
cdfstdnormal(x) is the cumulative probability distribution function of standard normal random variable evaluated at x.
pdfstdnormal(x) is the probability density function of standard normal random variable evaluated at x.
invcdfnormal(x,y,z) is the inverse cumulative probability distribution function of a normal random variable with mean y and standard deviation z evaluated at x.
product(x1, x2, . . . , xn)=x1*x2* . . . *xn (i.e. the multiplication of x1 through xn).
sqrt(x) gives the square-root of x.
sum(x1, x2, . . . , xn)=x1+x2+ . . . +xn (i.e. the sum of x1 through xn).
min(x1, x2, . . . , xn) gives the minimum of x1, x2, . . . , xn.
max(x1, x2, . . . , xn) gives the maximum of x1, x2, . . . , xn.
Purchase Order (PO) Data 136
Purchase order data consists of historical supply orders and related information. These are DSO[i,j] (date when the supply order is placed for component i and order j) and DSR[i,j] (date when the supply is received for component i and order j).
This data can be accessed from a database or a flat file. The data are used to calculate the lead time statistics.
Table 136 shown in FIG. 2A illustrates exemplary purchase order data.
Supply Lead Times 134
Historical purchase order data of supply orders are used to calculate the historical supply lead times for each component i as follows:

    
    
        HSLT[i,j]=DSR[i,j]−DSO[i,j] for all j=1,2, . . . , J[i]
    
    


Table 134 shown in FIG. 2B illustrates exemplary supply lead time data.
Supply Lead Time Statistics 132
Historical supply lead time performance for each component can be summarized in terms of mean, standard deviation, minimum and maximum of historical observations. These statistics are calculated as follows:

    
    
        HASLT[i]=(1/J[i])*sum(HSLT[i,j] for all j=1,2, . . . , J[i])
        HSSLT[i]=sqrt((sum(HSLT[i,j]2 for all j=1,2, . . . , J[i])−J[i]*sum(HSLT[i,j] for all j=1,2, . . . , J[i])/(J[i]−1))
        HMINSLT[i]=min(HSLT[i,j] for all j=1,2, . . . , J[i])
        HMAXSLT[i]=max(HSLT[i,j] for all j=1,2, . . . , J[i])
    
    


Table 132 shown in FIG. 2C illustrates exemplary supply lead time statistics.
Supplier Performance 112
The current projections of supply lead time performance are based on the pipeline orders. The process allows each supplier to update the supply order status of each order (i.e. the delay or early delivery of each outstanding order against the original request date). The order status for component i to be used in assembly k is an input and its value in the system is updated by the supplier. This input is represented by ESDP[i,k]. Based on this, we calculate the current supply lead time projection for component i in the pipeline to be used for scheduled assembly process k as follows:

    
    
        CSLT[i,k]=HASLT[i]+ESDP[i,k]
    
    


Based on this, we calculate the projected supply lead time performance statistics as follows:

    
    
        CASLT[i]=(1/K[i])*sum(CSLT[i,k] for all k=1,2, . . . , K[i])
        CSSLT[i]=sqrt((sum(CSLT[i,k]2 for all k=1,2, . . . , K[i])−K[i]*sum(CSLT[i,k] for all k=1,2, . . . , K[i]))/(K[i]−1))
        CMINSLT[i]=min(CSLT[i,k] for all k=1,2, . . . , K[i])
        CMAXSLT[i]=max(CSLT[i,k] for all k=1,2, . . . , K[i])
    
    


Based on historical supply lead time performance and projected supply lead time performance, we calculate the improvement in supply lead time performance as follows:

    
    
        IASLT[i]=(HASLT[i]−CASLT[i])/HASLT[i]
        ISSLT[i]=(HSSLT[i]−CSSLT[i])/HSSLT[i]
        IMINSLT[i]=(HMINSLT[i]−CMINSLT[i])/HMINSLT[i]
        IMAXSLT[i]=(HMAXSLT[i]−CMINSLT[i])/HMAXSLT[i]
    
    


Table 112 shown in FIG. 2D illustrates exemplary supplier performance data. This data provides guidance to operations managers for ensuring that suppliers perform in accordance with the agreements. If a supplier's delivery performance is poorer than the agreements, this report allows detection so that operations managers can contact the supplier requesting better performance. Since the most recent supplier lead time statistics data 132 will also reflect this recent poor performance, when the component inventory optimization engine 120 calculates updated optimal times for supply orders 122, it takes into account this poor performance and hence recommends earlier placement or orders with this particular supplier. Similarly, it recommends later placement of orders if the supplier performance has improved.
Assembly Delay Target Tolerance 144
Optimal supply order times depend on how much delay in supply arrival can be tolerated. For each component, a target delay is specified. This target delay is an input to the calculations. If the user chooses to optimize the supply order times, then optimal safety lead times are calculated so as to bring expected supply delay for each component below the target delay specified for that component. For component i, we denote target delay by DTARGET[i].
Table 144 shown in FIG. 2E illustrates exemplary assembly delay target tolerance data.
Component Costs 140
Component costs are essential to the minimization of inventory costs. These costs are user inputs to the system. We will denote the cost per unit for component i by COST[i].
Table 140 shown in FIG. 2F illustrates exemplary component cost data.
Supply Order Status 138
Supply order status is used to calculate the assembly delay projections and “can-delivery” projections. The status information of each supply order is given by the supplier of that order. The status information needs to have the expected delay (or early delivery) of the order along with other useful information such as reason for delay, or any other changes in the order. We denote the supply status by SSD[i,k] for component i and assembly k. This is the current anticipated delay in delivery against the original planned assembly date. If early delivery is anticipated, then it takes a negative value. It is expressed in days.
Table 138 shown in FIG. 2G illustrates exemplary supply order status data.
Inventory Policy Type 142
Calculation of the safety factor and of the times of supply orders depends on the inventory policy. There can be many different policies. We will focus on five of them here.

    
    
        1. Optimize safety factor. In this case, the safety factor is optimized. This means, supply inventory is minimized so as not to exceed an average supply delay target set by the user. Since each component has different costs and their supply lead times show different characteristics (i.e. mean, and standard deviation), at optimality each component has a different safety factor. For instance, more expensive items with shorter lead times, and smaller lead time variability, will tend to have smaller safety factors (leading to lower inventory levels) and others will tend to have higher safety factors (leading to higher inventory levels). Safety factors are optimized through an optimization algorithm that we will give in detail later.
        2. Fixed safety factor. In this case, the user specifies what safety factor is to be used for the component. There may be special reasons for the user to choose this option, such as contractual obligations or manufacturing policy.
        3. Availability based safety factor. In this case, the user specifies a target availability level for the component, and the safety factor that provides that availability level is calculated by the system. The availability level is defined by the probability of on time delivery of the supply, and on time delivery means the supply arrives before the planned assembly date.
        4. Worst case supply lead time. This is a conservative policy that uses a safety factor that will guarantee no supply delay if the supply lead time is not longer than the historical maximum.
        5. Best case supply lead time. This is an optimistic policy that uses a safety factor that assumes supply lead time can be as short as the historical minimum.
    
    


Inventory policy type is stored in parameter POLICY[i] for component i and takes a value indexed to the policy options. In the above example list of five policy options, the value for the POLICY[i] index would be one of the values 1, 2, 3, 4, or 5.
Table 142 shown in FIG. 2H illustrates exemplary inventory policy type data.
Optimal Times for Supply Order 122
Here the term “optimal” means that the supply order times are calculated based on policy types desired by the user. That is, one of the five alternative policies mentioned above is applied for each component.
In order to calculate the optimal time for supply order for a component, the safety factor is calculated first. Then, safety lead times are calculated. Safety lead times indicate how early the supply orders should be placed above and beyond the average supply lead times in order to control the chance of supply delays that would cause delays in assembly process.
Safety lead time is always calculated as follows:

    
    
        SLTIME[i]=SFACTOR[i]*HSSLT[i]
    
    


Optimal supply order lead time is how far in advance of the planned assembly date a component should be ordered. It is calculated as follows:

    
    
        OLTIME[i]=HASLT[i]+SLTIME[i]
    
    


Once the optimal supply order lead time is calculated, the optimal time for placing the supply order can easily be calculated by subtracting the optimal supply order lead time from the planned assembly start date. That is,

    
    
        OOTIME[i,k]=PSTART[k]−OLTIME[i]
    
    


Table 122 shown in FIG. 2J illustrates exemplary optimal supply order times data.
MRP (Materials Requirements Planning) Engine 150
MRP is a well established method and widely used in practice. The general principal of MRP is to calculate the supply timing based on the lead times at several stages of manufacturing/supply/distribution operations. However, MRP has some restrictions. An important restriction of MRP in the context of this method is that its plans are done assuming known lead times. If lead times are uncertain, MRP does not calculate the appropriate levels of “safety factors” to calculate optimal order lead times. The method described here should feed the safety factors to MRP in order to update the order schedules generated by MRP. In this way, delays in supply can be controlled at desired levels.
Supply Order Schedule 152
This is the output of the MRP engine described in method element 150. More specifically, let us assume that MRP sets the supply order date for component i to be used in assembly process k at MRPOTIME[i,k]. Then the modified date for this particular supply order is
MRPOTIME[i,k]+SLTIME[i].
The second term in this expression is the safety lead time that the method calculates (as described in the method element 122), which takes into account the uncertainty in the lead times.
Table 152 shown in FIG. 2K illustrates exemplary supply order schedule data.
Assembly Delay Projections 124
Expected supply delay for component i is calculated by assuming that the supply lead times have normal distribution with mean HASLT[i] and standard deviation HSSLT[i]. Other probability distributions can also be used. The calculation of expected supply delay for component i to assembly process k is done against the planned assembly date. It is done as follows:

    
    
        ZVALUE[i,k]=(OLTIME[i]+SSD[i,k]−HASLT[i])/HSSLT[i]
        ESDP[i,k]=HSSLT[i]*(pdfstdnormal(ZVALUE[i,k])+ZVALUE[i,k]*(1−cdfstdnormal(ZVALUE[i,k])))
    
    


The total estimated supply delay for assembly process k against the planned start date of the assembly is given by the following:

    
    
        TESDP[k]=max(ESDP[i,k] for all i=1,2, . . . , I[k])
    
    


Table 124 shown in FIG. 2L illustrates exemplary assembly delay projection data.
Projections of “Can-Deliver” Dates 126
Being able to start assembly process at a given date PSTART[k] with a given level of confidence means we have all the components available for assembly with a certain probability. The probability here gives us the confidence level. The date we can start the assembly process is called the “can start” date and it can be estimated as follows:

    
    
        CSTART[k]=PSTART[k]+max(JSD[i,k] for all i=1,2, . . . , I[k])
        
            where
        
        
        JSD[i,k]=max(0,min(HMAXSLT[i], invcdfnormal(CLEVEL[k](1/I[k]),0,1)*HSSLT[i]+HASLT[i])−(OLTIME[i]−ESDP[i,k]))
    
    


Sometimes, a different date for assembly may be requested due to changes in customer requirements, etc. In this case, it may be desirable to calculate the estimated delay beyond the requested date, RSTART[k]. This delay can be calculated as follows:

    
    
        TESDR[k]=max(ESDR[i,k] for all i=1,2, . . . , I[k])
        
            where
        
        
        ESDR[i,k]=HSSLT[i]*(pdfstdnormal(ZVALUE[i,k])−ZVALUE[i,k]*(1−cdfstdnormal(ZVALUE[i,k]))
        ZVALUE[i,k]=(OLTIME[i]+SSD[i,k]+RSTART[k]−PSTART[k]−HASLT[i])/HSSLT[i]
    
    


If it is desired to calculate the chance of being able to start the assembly at the requested date, this can be calculated as follows:

    
    
        PONTIMEA[k]=product(PONTIMEC[i,k] for all i=1,2, . . . , I[k])
        
            where
        
        
        PONTIMEC[i,k]=cdfstdnormal(ZVALUE[i,k])
        ZVALUE[i,k]=(OLTIME[i]+SSD[i,k]+RSTART[k]−PSTART[k]−HASLT[i])/HSSLT[i]
    
    


Table 126 shown in FIG. 2M illustrates exemplary “can-deliver” dates data.
What-if Analysis 128
When the supply timing planning is done, there may be a number of questions useful to answer in the planning and execution process. We will show some of them and others can be handled similar to the illustrations here.
We will list three “what-if” questions here and show how answers can be generated.

    
    
        1. If average supply lead time performance of a component (or a group of components) changes, what happens to the “can start” date for assembly and the projected assembly delay?
        2. If supply lead time performance (as measured by coefficient of variation) of a component (or a group of components) changes, what happens to the “can start” date for assembly and the projected assembly delay?
        3. If a component (or a group of components) is (are) delayed for some time, what happens to the “can start” date for assembly and the projected assembly delay?
    
    


Case 1: In order to answer this question, the user enters the value of change for the average lead time in percent terms. Then, the average supply lead time is updated as follows:

    
    
        HASLTNEW[i]=HASLT[i]*(1+ASLTCHANGE[i]).
    
    


Then calculations described in method elements 124 and 126 are performed after replacing HASLT[i] by HASLTNEW[i].
Case 2: In order to answer this question, the user enters the value of change for the variability of lead time in percent terms. Then, the average supply lead time is updated as follows:

    
    
        HSSLTNEW[i]=HSSLT[i]*(1+SSLTCHANGE[i]).
    
    


Then calculations described in method elements 124 and 126 are performed after replacing HSSLT[i] by HSSLTNEW[i].
If both average lead time and variability of lead time change, then the new standard deviation is calculated as follows:

    
    
        HSSLTNEW[i]=(HASLTNEW[i]/HASLT[i])*HSSLT[i]*(1+SSLTCHANGE[i]).
    
    


Case 3: In order to answer this question, the user enters the value of anticipated delay in supply order delivery (in days). Then, this new delay (denote it by SSDNEW[i,k]) replaces the old one (i.e. SSD[i,k]). Then calculations described in method elements 124 and 126 are performed to answer the questions.
Table 128 shown in FIG. 2N illustrates exemplary what-if analysis data. These “what-if” questions are important for the operations managers to simultaneously control i) the assembly delays and on time delivery of completed products to customers and ii) component inventory. Accurate answers to these “what-if” questions require the above described method of this invention, and in particular the way the method of the invention links component supply delays to assembly delay, and the way it calculates the probabilities of on time starts of assemblies. Many planning systems particularly MRP does not incorporate uncertainties in the planning and hence is not able to generate probabilities of on time starts or does not able to estimate the amounts of delays. Inventory optimization techniques that are common on the other hand calculate “safety stocks” rather than “safety lead times”. Safety stocks require monitoring the inventory position and they tend to work well for products with high demand volume. For complex and expensive products that do not have high volumes safety stocks do not accurately show the optimal times of placing supply orders to feed scheduled assemblies of such products.
Supplier's Performance Monitoring Engine 110
This engine is used to keep track of supply performance statistics calculated in method element 132, and allows users to update current projected delays in supply delivery for each component and each assembly process (described in method element 138). Based on these data, it calculates estimates of lead time delivery performance statistics for the future assembly processes (described in method element 112).
The engine reports all historical and current lead time performance statistics and the improvements. This helps the operations managers keep the supply arrivals in check. If any supplier's performance falls short of the targets, suppliers can be notified and requests for improvements can be made or negotiations can be triggered.
Component Inventory Optimization Engine 120
This engine calculates the safety factors according to the desired specifications by the user. That is, the user can specify the policy type desired for each component. There are five policy types described in method element 142. The engine calculates the safety factors for all components. The safety factor for each component depends on the policy type selected for that component:
Safety factor for each policy type is calculated as follows:

    
    
        If POLICY[i]=1 (Optimize safety factor)
        
            then calculate SFACTOR[i] using the optimization algorithm.
        
        
        If POLICY[i]=2 (Use fixed safety factor)
        
            then get SFACTOR[i] as an input from the user.
        
        
        If POLICY[i]=3 (Use availability target based safety factor)
        
            then SFACTOR[i]=invcdfnormal(ATARGET[i], HASLT[i], HSSLT[i])
        
        
        If POLICY[i]=4 (Use worst case supply lead time safety factor)
        
            then SFACTOR[i]=(HMAXSLT[i]−HASLT[i])/HSSLT[i]
        
        
        If POLICY[i]=5 (Use best case supply lead time safety factor)
        
            then SFACTOR[i]=(HMINSLT[i]−HASLT[i])/HSSLT[i]
        
        
    
    


The inventory optimization algorithm that calculates the safety factors SFACTOR[i] for all components is given below.
Inventory Optimization Algorithm
If policy type is 1 then an optimization of the safety factor is performed by using an optimization algorithm.
This optimization algorithm solves the following problem:
Minimize over S[i], i=1, . . . , N:

    
    
        sum{h[i]E[max{T[i]+S[i]−L[i],0}], i=1, . . . , N]}
    
    


Subject to:

    
    
        E[max{L[i]−T[i]−S[i],0}]<= for all i=1, . . . , N.
    
    


Here E[X] means the expected value of random variable X.
What is to be minimized here is the inventory holding cost of all components.
The constraint states that we want the expected value of the component delay for each component to be no more than a target value alpha.
The definitions of the parameters used in the formulation are below:

    
    
        i: Index for components to be optimized.
        N: Total number of components to be optimized.
        h[i]: Inventory cost of holding component I for a day in inventory.
        T[i]: Mean supply lead time for component i. It is equal to HASLT[i].
        L[i]: Actual supply lead time for component and it is an unknown normally distributed random variable with mean HASLT[i] and standard deviation HSSLT[i].
        S[i]: Safety lead time for component i. It is equal to SLTIME[i].
        : Target supply delay to final assembly (in days). It is also called DELAYTOLERANCE (see below). This is the amount of delay we can tolerate for the assembly to start on time at the planned date. It is an input by the user.
    
    


We will use the following parameters in the optimization algorithm:

    
    
        LAMBDA: Lagrange multiplier (needed for constrained optimization).
        DELAYTOLERANCE: Target assembly process delay (in days) due to delays in component supply.
        COST[i]: Unit cost of component i (purchase cost if supplied, manufacturing cost if manufactured).
        LTMEAN[i]: Sample mean of lead time observations for component i. This is the average supply lead time for component i. Historical lead times are used to calculate this if there is not a better estimate for it. Therefore, it is equal to HASLT[i].
        LTSTDEV[i]: Sample standard deviation of lead time observations for component i. This is the standard deviation of supply lead time for component i. Historical lead times are used to calculate this if there is not a better estimate for it. Therefore, it is equal to HSSLT[i].
        LTMAX[i]: Sample maximum of lead time observations for component i. Historical lead times are used to calculate this if there is not a better estimate for it. Therefore, it is equal to HMAXSLT[i].
        LTMIN[i]: Sample minimum of lead time observations for component i. Historical lead times are used to calculate this if there is not a better estimate for it. Therefore, it is equal to HMINSLT[i].
        ATARGET[i]: Availability probability target for component i. It is a user input to the calculations.
        POLICY[i]: Inventory policy type for component i. It takes values from 1 to 5. see 142.
        SFACTOR[i]: Safety factor for timing the supply order for component i.
        SUMDELAY: Total projected delay in final assembly due to component supply shortages (in days).
        DELAY[i]: Projected delay in the supply of component i (in days).
        INVENTORY[i]: Projected amount of inventory (in units) at final assembly for component i.
        INVENTORY$[i]: Projected amount of inventory (in dollars) at final assembly for component i.
        NORMINV(x,y,z): This is the inverse of normal distribution function evaluated at x. The normal random variable has a mean of y and standard deviation of Z.
        Z[i]: This is the z-value of standard normal distribution. It is equal to the ratio: (S[i]−LTMEAN[i])/LTSTDEV[i].
        PDF[i]=NORMDIST(Z[i],0,1,FALSE): This is the Probability Density Function of standard normal random variable (i.e. mean=0, standard deviation=1) evaluated at Z[i].
        CDF[i]=NORMDIST(Z[i],0,1,TRUE): This is the Probability Distribution Function of standard normal random variable (i.e. mean=0, standard deviation=1) evaluated at Z[i].
        G[i]=PDF[i]−Z[i]*(1−CDF[i]): This is the G-function used in inventory control theory. It measures the expected amount of random supply lead time above and beyond the level S[i].
    
    












Algorithm 1: Calculating optimal order times

















1. Get Inputs: DELAYTOLERANCE, COST[i],









LTMEAN[i], LTSTDEV[i], LTMAX[i], LTMIN[i],



ATARGET[i], POLICY[i].









2. Calculate MAXLAMBDA (see Algorithm 2).



3. Let LAMBDA = MAXLAMBDA.



4. Let SUMDELAY = 0.



5. Let INCREMENT = MAXLAMBDA.



6. Let ITERATION = 1.



7. Do while ITERATION < 60:









1. Calculate SUMDELAY (see Algorithm 3).



2. Let INCREMENT = 0.5*INCREMENT



3. IF SUMDELAY > DELAYTOLERANCE









THEN Let LAMBDA = LAMBDA +









INCREMENT









ELSE Let LAMBDA = LAMBDA −









INCREMENT









4. Let ITERATION = ITERATION + 1.



5. Continue









8. Stop.



9. Report SUMDELAY, DELAY[i], INVENTORY[i],









INVENTORY$[i], SFACTOR[i].




















Algorithm 2: Calculation of MAXLAMBDA

















1. Let SUMDELAY = 0



2. Let LAMBDA = 1,000,000.



3. Do While SUMDELAY > DELAYTOLERANCE









1. Calculate SUMDELAY



2. Let LAMBDA = 2*LAMBDA



3. continue









4. Stop.



5. Let MAXLAMBDA = LAMBDA



6. Report MAXLAMBDA.




















Algorithm 3: Calculation of SUMDELAY















1. Let SUMDELAY = 0. Let i=1.


2. Do While i < N+1










 1.
If POLICY [i]=1 then









Let SFACTOR[i] =



NORMINV(LAMBDA/(LAMBDA+COST[i]),LTMEAN



[i],LTSTDEV[i])/LTSTDEV[i]−



LTMEAN[i]/LTSTDEV[i]










 2.
If POLICY[i]=2 then









Set SFACTOR[i] to the input value



given by the user










 3.
If POLICY[i]=3 then









Set SFACTOR[i] =



invcdfnormal(ATARGET[i], LTMEAN[i],



LTSTDEV[i])










 4.
If POLICY[i]=4 then









Set SFACTOR[i] = (LTMAX[i] −



LTMEAN[i])/LTSTDEV[i]










 5.
If POLICY[i]=5









then SFACTOR[i] = (LTMIN[i] −



LTMEAN[i])/LTSTDEV[i]










 6.
Let S[i] =









LTMEAN[i]+SFACTOR[i]*LTSTDEV[i]










 7.
Let Z[i] = (S[i] − LTMEAN[i]) /









LTSTDEV[i]










 8.
Let PDF[i] = NORMDIST(Z[i],0,1,FALSE)



 9.
Let CDF[i] = NORMDIST(Z[i],0,1,TRUE)










10.
 Let G[i] = PDF[i] − Z[i]*(1−









CDF[i])










11.
 Let DELAY[i] = LTSTDEV[i]*G[i]



12.
 Let INVENTORY[i]=S[i]−









LTMEAN[i]+DELAY[i]










13.
 Let









INVENTORY$[i]=COST[i]*INVENTORY[i]










14.
 Let SUMDELAY = SUMDELAY +









DELAY[i]










15.
 Let i=i+1



16.
 Continue.







3. Stop.


4. Report SUMDELAY, DELAY[i], INVENTORY[i],









INVENTORY$[i], SFACTOR[i].










Note that the safety factors this algorithm calculates are conservative. In other words, the total supply delays would be shorter than targets when the solution of this algorithm is implemented. Other algorithms can be used to calculate safety factors that are not conservative. Simulation can be used as a technique when analytical calculations are not possible. Note also that the optimization algorithm takes into account the cost of all components simultaneously and calculates the best lead time safety factors that minimize the component inventory costs. Components are not optimized independently of each other.
While the invention has been described in terms of a single preferred embodiment, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the appended claims.

## Claims

1. A computer system for managing component supply for assembly of complex products, comprising:
a monitoring engine implemented in software and operating on said computer system for prompting improved supply lead time performance of one or more suppliers of respective one or more components of a complex assembly; and
an optimization engine implemented in software and operating on said computer system for using said improved supply lead time performance to generate supply order times, for each respective component, that keep an expected supply delay for the respective component within a target delay tolerance for the component,
the optimization engine having means for using supply lead time uncertainty and component costs relative to other components in performing optimization.

2. The system of claim 1, wherein the monitoring engine further comprises, for each component:
means for measuring an historical record of delivery delay by the supplier of the respective component;
means for obtaining from the supplier at periodic intervals an estimated delivery delay for each component item in a delivery pipeline of the supplier;
means for calculating in said delivery pipeline an improvement factor that compares the estimated delivery delay with the historical delivery delay.

3. The system of claim 2, wherein the optimization engine further comprises:
means for selecting for each component an inventory policy for determining a safety factor for the component;
means for calculating a safety factor for each component in accordance with the selected inventory policy;
means for determining a target delay tolerance for each component;
means for calculating an expected supply delay for each component; and
means for calculating the supply order time for each component so that the expected supply delay is within said target delay tolerance.

4. The system of claim 3, wherein the historical record of delivery delay is described by a standard probability density.

5. The system of claim 4, wherein the improvement factor is calculated for a mean value, a standard deviation from the mean, a maximum value, and a minimum value.

6. The system of claim 3, wherein the calculated supply order time and calculated safety factor are provided to a materials requirements planning (MRP) engine.

7. The system of claim 3, wherein one of said respective policies uses an optimization algorithm to calculate the respective safety factor.

8. The system of claim 7, wherein the optimization engine uses a cost for each component to optimize a total cost of inventory.

9. The system of claim 1, further comprising
means for presenting to a manager projections of an effect of an unexpected supply delay for a component upon an assembly schedule for said complex assembly; and
means for said manager to request from a supplier of said component faster delivery of said component in response to said projection.

10. The system of claim 1, wherein the generated supply order times are provided to a materials requirements planning (MRP) engine.

11. A computer implemented method for managing component supply for assembly of complex products, the computer performing the steps of:
monitoring, so as to prompt improvement in, supply lead time performance of one or more suppliers of components of a complex assembly;
generating, from a measure of said prompted improvement in supply lead time performance, supply order times for each component that keep an expected supply delay for a component within a target delay tolerance for the component, and
generating said measure using supply lead time uncertainty and component costs relative to other components.

12. The method of claim 11, wherein the monitoring further comprises, for each component:
measuring an historical record of delivery delay by the supplier of the respective component;
obtaining from the supplier at periodic intervals an estimated delivery delay for each component item in a delivery pipeline of the supplier;
calculating in a delivery pipeline an improvement factor that compares the estimated delivery delay with the historical delivery delay.

13. The method of claim 11, further comprising presenting to a manager projection of an effect of an unexpected supply delay for a component upon an assembly schedule for said complex assembly; and
requesting by said manager from a supplier of said component faster delivery of said component in response to said projection.

14. The method of claim 13, wherein said projected effects include delay in completion of said assembly schedule or change in “can-deliver”dates for said assembly.

15. The method of claim 11, wherein the generated supply order times are provided to a materials requirements planning (MRP) engine.

16. A computer implemented system for managing component supply for assembly of complex products, comprising:
first computer code on said computer implemented system for monitoring, so as to prompt improvement in, supply lead time performance of one or more suppliers of respective one or more components of a complex assembly; and
second computer code on said computer implemented system for generating, from a measure of said prompted improvement in supply lead time performance, supply order times for each respective component that keep an expected supply delay for the respective component within a target delay tolerance for the component,
wherein supply lead time uncertainty and component costs relative to other components are used by means for generating said measure.

17. The computer implemented system of claim 16, wherein said first computer code for monitoring further comprises:
third computer code for measuring, for each component, an historical record of delivery delay by the supplier of the respective component;
fourth computer code for obtaining from the supplier of each component at periodic intervals an estimated delivery delay for each component item in a delivery pipeline of the supplier;
fifth computer code for calculating, for each component in a delivery pipeline, an improvement factor that compares the estimated delivery delay with the historical delivery delay.