OTIF performance for co-manufacturing partners
OTIF performance for co-manufacturing partners
OTIF measures service failures after the delivery attempt; the consequence (retailer penalty, lost sale) is already locked in before the score is calculated.
(Conforming co-man delivery lines / Total delivery lines) x 100One row per outbound delivery line — plant × product × customer × date
A preview of what's actually built for this KPI — extracted from the real Implementation Pack, not a mockup.
This is the primary ratio the pack's other measures build on — trend, rank, and period-comparison variants, all on Fact_Outbound_Delivery_Line. It guards against missing dates and values with NOT ISBLANK checks.
Fact_Outbound_Delivery_Line — 10 mandatory columns — actual arrival date key, qty ordered, ...Dim_Batch — batch_key + batch_nbrDim_Carrier — key + nameDim_Customer — key + nameDim_Plant — key + nameDim_Product — key + nameDim_Route — key + nameDim_Date — Auto-generated calendar table — no customer data requiredFull field-by-field data contract, in 4 SQL dialects (SQL Server, Snowflake, Databricks, BigQuery), ships in the pack.
| Target | 0.97 — performance considered compliant at or above this line |
| Warning | 0.92 — amber alert — triggers a review |
Both live in one Excel tab — change them, refresh the report, done. No DAX editing needed.
Everything you need to build Co-Packing OTIF in Power BI — dimensional model, DAX measures, SQL views, and a food-industry demo dataset.