What it measures
% of finished products meeting all specification limits
Business impact
- Increased 'chaos tax' from unplanned rework, lab re-testing, and management time spent negotiating concessions for out-of-spec but safe-to-consume product.
- Batches on QA hold erode finished goods inventory position, creating phantom stock-outs that cause short shipments and customer service commitment failures.
- Sustained non-compliance on a retailer's own-label product triggers a formal audit and potential delisting, putting the entire account relationship at risk.
Formula
(Spec-compliant batches / Total batches) x 100Grain
One row per production order batch — plant × product × recipe × shift × date
Inside the Implementation Pack
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_Production_Order_Batch. It guards against missing dates and values with NOT ISBLANK checks.
Fact_Production_Order_Batch— 9 mandatory columns — batch key, production line key, ...Dim_Batch— batch_key + batch_nbrDim_Plant— key + nameDim_Product— key + nameDim_Production_Line— key + nameDim_Recipe— key + nameDim_Shift— key + nameDim_Date— Auto-generated calendar table — no customer data required
Full field-by-field data contract, in 4 SQL dialects (SQL Server, Snowflake, Databricks, BigQuery), ships in the pack.
| Target | 0.99 — performance considered compliant at or above this line |
| Warning | 0.96 — 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 Product Specification Compliance in Power BI — dimensional model, DAX measures, SQL views, and a food-industry demo dataset.