Supplier OTIF and the lead-time stack
From supplier orders calculates the share on time, in full and both (OTIF), perfect orders, the worst supplier, average lead time planned and actual and by stage, and which stage used up the time buffer.
At a glance
- What question does it answer?
- What share of orders arrives on time and in full and which stage uses up the time buffer.
- What data is needed?
- Orders by supplier: all, on time, in full, both, optionally perfect.
- How to read the result?
- On the default data (three suppliers, 125 orders) OTIF is 82.4%, on time 87.2%, in full 92.8%, perfect 76.8%. The worst supplier is Factory B with 64%. The average lead time is 34.9 days planned, 40.6 actual. The stage stack: plan 82 days, actual 96, overrun 14 days; with a 7-day buffer 7 days are not covered. Example on the default values: OTIF: 82.4%; Share on time: 87.2%; Share in full: 92.8%; Perfect orders: 76.8%. The figures are illustrative: enter your own to see your result.
Why and how to reason
A lead time of “two weeks” says nothing until you know what it consists of and how often it is met. OTIF (on time in full) counts the share of orders that arrived both on time and complete. This is stricter than the separate shares: an order a day late, or one carton short, counts as bad. For three suppliers: on time 109 of 125, in full 116 of 125, both 103, so OTIF is 82.4%. The worst supplier (Factory B) gives 16 ÷ 25 = 64%. The second part of the calculation is the lead-time stack: planned stages give 82 days, actual 96, an overrun of 14 days. The lead-time buffer is 7 days, so another 7 are not covered. Alongside, “perfect orders” are counted (76.8% in the example): orders that arrived on time and in full and also undamaged and with correct documents, so they are stricter than OTIF and cannot exceed it.
When to use it
It comes in handy to assess suppliers, discuss penalties and set a lead-time safety margin. Do not use it on a small sample: for a supplier with five orders OTIF jumps by 20 points. Assumptions: the single basis is orders (not lines and not units), “both” is not above “on time” and “in full”, you have actual stage durations.
How to read the result
Compare overall OTIF (82.4%) with your target and look at the worst supplier: an average hides a weak one. Then open the stack: the “Materials” stage (+5 days) and “Production” (+4) give the most overrun, so those are what you must negotiate. If the overrun exceeds the buffer, the plan formula no longer works: either increase the buffer or shorten the stages. Cross-check the result against the reasons for lateness. Agree terms by stage and not by the overall lead time: the culprit is then visible, and a penalty or bonus is tied to the real cause. Also check the receiving time: it is often forgotten, yet it adds days.
Common mistakes
Computing OTIF by lines but comparing with a figure by orders, taking “delivered” instead of “accepted”, not entering partial deliveries, averaging lead times without weighting by volume. Do not compare OTIF of companies counting on different bases. Do not enter “perfect” orders above “both”: that is mathematically impossible, and the calculation will refuse to run and point at the supplier.
What data is needed?
- Orders by supplier: all, on time, in full, both, optionally perfect.
- Planned and actual lead times by supplier and by stage.
- The time buffer built in.
Inputs
| Field | Unit | Value in the example | Meaning |
|---|---|---|---|
| Time buffer built in | days | 7 | How many days of buffer the plan holds between the arrival and the date the goods are needed. The example value is illustrative. |
| Your OTIF target | % | — | A target from the supplier contract or your past results; empty: no color is assigned. There is no single standard in Russia: enter your own figure. |
How it is calculated
| Step | Formula |
|---|---|
| OTIF | sum of “both” orders ÷ sum of orders |
| Average lead time | sum (orders × lead) ÷ sum of orders |
| Lead-time overrun | sum of actual stage durations − planned |
| Not covered | overrun − buffer (if above zero) |
Worked numbers
Default values from the app; in the interactive version you enter your own.
- OTIF
- 82.4 %The single basis in Lab: orders (not order lines and not units). Orders on time and in full at once ÷ all orders. If you count by lines or deliveries, label the basis and do not compare with this figure.
- Share on time
- 87.2 %
- Share in full
- 92.8 %
- Perfect orders
- 76.8 %
- Worst supplier by OTIF
- 64 % · Factory B
- Planned lead time, on average
- 35 days
- Actual lead time, on average
- 41 days
- Stage stack: lead-time overrun
- 14 days · plan 82, actual 96
- Not covered by the time buffer
- 7 daysLead-time overrun less the buffer built in.
Data as a table
| Measure | Share of orders |
|---|---|
| OTIF | 82.4 |
| On time | 87.2 |
| In full | 92.8 |
| Perfect orders | 76.8 |
| Worst supplier | 64 |
Suppliers: OTIF and lead times
| Supplier | Orders | OTIF | Plan lead | Actual lead |
|---|---|---|---|---|
| Factory A | 40 | 77.5 % | 60 | 68 |
| Factory B | 25 | 64 % | 45 | 58 |
| Carrier | 60 | 93.3 % | 14 | 15 |
The lead-time overrun of 14 days exceeds the 7-day buffer: goods will arrive later than needed on the shelf. The biggest overrun is the stage “Materials” (+5 days).
“On time” and “in full” must be defined jointly with the supplier: fix the tolerance in the contract. There is no single OTIF standard in Russia: the target is yours. The method is the perfect order (the share of orders with no error at all); the formulas are our own.
Nuances and limits
- Agree the definition of on time and in full with the supplier.
- “Both” is entered as a fact: it cannot be derived from two shares.
- There is no single OTIF standard in Russia: the target is yours.
- The average lead time hides the worst supplier.