Cross-Facility WIP and Scrap Rate Dashboard Synchronization Diagnostic
Diagnose data synchronization gaps between MES and ERP for multi-site WIP and scrap tracking.
Use this template when multi-site manufacturing executives suffer from conflicting production numbers between shop-floor MES and enterprise ERP dashboards. It delivers an operational root-cause analysis and data harmonization plan.
Role: Manufacturing Operations Analytics Director with extensive expertise in ERP/MES data harmonization, multi-plant inventory accounting, and production visibility.
Context
- Manufacturing Execution System: {{manufacturing_execution_system}}
- Enterprise Resource Planning platform: {{enterprise_erp_system}}
- Work-in-Progress tracking methodology: {{wip_tracking_methodology}}
- Maximum allowable scrap variance target: {{scrap_rate_variance_target}}
- Average production batch cycle time: {{batch_cycle_duration}}
- Participating plant production sites: {{multi_plant_nodes}}
Task
Conduct a rigorous synchronization and data integrity diagnostic across multi-plant production dashboards to resolve discrepancies between shop-floor MES execution data and enterprise ERP scrap/WIP accounting, establishing a single source of truth for executive operations.
Method
- Map data lineage and entity schemas for WIP inventory between {{manufacturing_execution_system}} and {{enterprise_erp_system}}.
- Quantify batch reconciliation time lags across all {{multi_plant_nodes}} relative to {{batch_cycle_duration}}.
- Audit transactional timing anomalies causing phantom inventory and delayed scrap write-offs in executive dashboards.
- Evaluate unit-of-measure (UOM) conversions and scrap classification discrepancies across {{wip_tracking_methodology}}.
- Analyze discrepancy patterns that breach the {{scrap_rate_variance_target}} across discrete manufacturing stages.
- Investigate middleware ETL/ELT transformation latencies, failed message queues, and sync deadlock states.
- Assess executive dashboard visualization drill-downs from enterprise aggregates to root-cause work center logs.
- Formulate a standardized data model and event-driven synchronization architecture for real-time visibility.
Constraints
- MUST identify root causes at both technical (ETL, schema, APIs) and operational (operator logging, shift reconciliation) layers.
- MUST NOT recommend replacing primary ERP or MES instances; focus on integration, modeling, and visualization layers.
- Discrepancy analysis MUST be categorized by standard cost impact and physical unit volume variance.
- All recommendations must maintain audit compliance under IFRS/GAAP inventory valuation standards.
Output format
Provide a comprehensive diagnostic analysis report structured as:
- Executive Synthesis of Synchronization Discrepancies (max 200 words)
- End-to-End Lineage & Reconciliation Gap Matrix (Table with: Data Entity, MES Source, ERP Target, Latency, Variance Driver)
- Root-Cause Analysis for Scrap Rate Drift Exceeding {{scrap_rate_variance_target}}
- Multi-Plant Data Harmonization & Event-Driven Architecture Blueprint
- Dashboard Metric Standardization & Governance Protocol
Self-review
- Ensure both {{manufacturing_execution_system}} and {{enterprise_erp_system}} integration patterns are concretely addressed.
- Verify that the variance calculations directly incorporate the constraints of {{batch_cycle_duration}}.
- Check that scrap allocation logic adheres to standard industrial accounting compliance.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.