Supplier Lead Time Variance

A buyer expects a part ten days after releasing a purchase order, but the material becomes available after fourteen days, and the four-day difference matters because the production plan depended on that promise. Set the endpoints first, since supplier manufacturing, shipping, receiving and inspection are different stages; IFS describes total purchase lead time as the period from order to availability in inventory, with several components.

Oracle reports supplier lead-time variances by item, supplier and site, with fields for a planned lead time, historical lead time and variance days, but the calculation used in a business should state its own event definitions. Choose one start event and one end event, because a line creation date, PO release date or supplier confirmation date can produce different elapsed times and should not be mixed within a trend.

A supplier ship date measures a different promise from approved receipt, so state whether the metric ends at dock arrival, receipt or usable stock. Match the promise too, since a requested date and a supplier-promised date are not identical, and record both if teams need to distinguish internal planning from supplier performance.

Calculate the variance in comparable days: if promised lead time is ten calendar days and observed lead time fourteen, variance is four calendar days, and if working days are used, the same calendar should apply to both. Keep the sign clear, since positive may mean later than planned and negative earlier, but the convention must be documented because a reversed sign can make a dashboard dangerous.

Group by supplier-item-site, because one supplier can deliver a standard component reliably and a custom part slowly, and a company-wide average hides the difference. Check partial deliveries, since the first carton arriving does not mean an entire order line is available, and decide whether to measure first receipt, complete receipt or quantities separately.

Exclude internal delays carefully, because a lot can sit at receiving for inspection and a supplier-shipment measure and an end-to-end measure answer different questions. Review revisions as well: if the promise changes after acceptance, preserve the original commitment and the approved amendment, otherwise a late delivery can vanish from the metric.

Use a suitable sample, because three orders may not establish a reliable pattern, and show count, dates and unusually large orders alongside averages. Consider variability, not just the average, since an average of ten days can include repeated twenty-day delays and the range and percentiles may better inform safety stock.

Investigate causes, because manufacturing capacity, customs, transport and incorrect order details need different fixes and the number itself does not assign blame. Link the result to planning: if a repeatable delay persists, adjust the planning lead time while working on its cause, because keeping an unrealistic ten-day value can create recurring shortages, but do not quietly pad every record, since excessively long lead times raise inventory and working capital.

Separate expedited orders, as air freight may make a shipment look fast at unusual cost, measure forecast impact, because a four-day slip may be harmless for surplus stock but severe for a constrained assembly, and validate data for missing confirmation dates, backdated receipts and inconsistent time zones. Share disputed lines with suppliers before concluding their process caused all variance, track improvements by comparing similar periods and item mixes, and escalate critical parts to a risk owner, remembering that the measure turns delivery experience into a planning input only when the clock is defined and like is compared with like.