| Phase | What it covers | Status |
|---|---|---|
| Business Context & Problem Scope | Analytics Project Charter, NCG Order Lifecycle | Complete |
| KPI Framework | Tier 1 KPIs, Tier 2 KPIs, KPI Catalog Register, KPI definitions, data sources and fields | Complete |
| Data Architecture | Operational data model, KPI fact table design, Dimension tables | Complete |
| Data Generation | Mock data design, SQL table creation | Complete |
| KPI SQL Logic | Spine builds, OTIF derivation, cost and lead time | In Progress |
| Diagnostic Analysis | Python, variance analysis | Upcoming |
| Executive Reporting | KPI views, Power BI dashboard | Upcoming |
Business Context, Operating Model, Scope Boundaries, and my Analytical Mandate
Order Created → ATP → Order Confirmed → Order Released → Order Shipped → Order Delivered
Measures the percentage of customer orders delivered on time and in full against the committed promise date - (customer centric)
Answers → Whether downstream execution is failing customers and where service is breaking down
| Component | Included | Reason |
|---|---|---|
| Released On Time | No | Internal warehouse SLA. Late release that still delivers on time does not impact the customer. Diagnostic value captured in Release spine separately. |
| Released In Full | Yes | release_qty = 0 means the line never ships. Customer cannot receive full quantity. Root cause of downstream In Full failures. |
| Shipped On Time | No | Internal execution risk. If shipment arrives on time despite late ship date, customer is not impacted. Diagnostic value captured in Shipment spine separately. |
| Shipped In Full | Yes | Pick/pack shortfall flows directly to customer. Delivered In Full captures loss and damage but not quantity shortfalls from picking. |
| Delivered On Time | Yes | Core customer-facing OTIF component. |
| Delivered In Full | Yes | Core customer-facing OTIF component. |