MPS Template & BOM Synchronization Checklist

Why this checklist matters

Keep the Master Production Schedule (MPS) reliable by making sure confirmed demand, current bills of materials (BOMs), and realistic capacity match each week. Unsynced BOMs and unmanaged engineering changes are common root causes of expediting, wrong kits, excess inventory, and missed deliveries. Use this item as a working routine: it helps planners, engineering, procurement, and production operate from one accurate plan instead of firefighting.

How to use this checklist

1. Run through the weekly template fields and collect data before the weekly MPS review meeting.
2. Perform the reconciliation checklist between BOM/ERP/MES and resolve or escalate mismatches immediately.
3. Apply the engineering-change rules for items inside the planning horizon—either freeze, queue, or approve as an exception.
4. Follow the escalation guide when mismatches threaten delivery dates or create capacity conflicts.

MPS Weekly Template (fields to complete)

1. Planning horizon dates: (Start date — End date)
2. Revision / Version: (MPS v. YYYY-MM-DD)
3. Confirmed customer orders: (Order#, Part#, Qty, Due Date, Customer)
4. Forecasted demand flagged for commitment: (Part#, Qty, Rationale)
5. Available-to-promise (ATP) inventory: (Part#, Qty)
6. Key constrained resources: (Line/Machine, Available capacity hours, Changeover impact)
7. Top schedule risk items: (Parts with BOM mismatches, long lead-time components, quality holds)
8. Planned production orders / builds: (MO#, Part#, Qty, Start Date, End Date)
9. Planned kit requirements: (Kit#, Components, Qty)
10. Open engineering changes: (ECN#, Part affected, Status, Impact on schedule)
11. Known supplier issues: (Supplier, Part, ETA change, Mitigation)
12. Escalations issued this week: (Yes/No — if yes, link to escalation record)

BOM / ERP / MES Reconciliation Checklist

• Confirm BOM revision in engineering system matches BOM revision in ERP for each production part scheduled this week.
• For each production order, verify the ERP BOM exploded component list equals the MES kit list (part number, quantity, UOM).
• Check component lead times in ERP against supplier confirmations; flag any lead-time growth that impacts the schedule.
• Validate current on-hand and on-order inventory in ERP against MES consumption history for high-usage components.
• Confirm phantom and kit items are resolved: phantom nodes have a clear assembly/consumption rule and are not accidentally scheduled as stocked items.
• Ensure substitutions or approved alternate parts are documented and reflected across BOM and ERP pick lists.
• For configurable products, validate variant rules (options matrix) so kits and pick lists generate correctly.
• Run a components-impact scan: for any change to a parent BOM, list all affected children and where they are scheduled in the current horizon.
• Document any mismatch as: 1) Data error (correct and close), 2) Engineering change (follow ECN rules), or 3) Supply issue (procurement action required).

Engineering Change (ECN) Handling Rules for the Planning Horizon

1. Stabilization window: Define a firm freeze window inside the short-term horizon (example: 0–2 weeks = frozen, 2–6 weeks = controlled, beyond 6 weeks = open). Avoid applying non-essential ECNs inside the frozen window.
2. Minor documentation changes: If change does not affect part numbers, quantities, or routings, allow as administrative update with planner notification.
3. Material or kit changes: Require approval from Planning, Production, and Procurement before applying to MPS if inside the controlled window; include mitigation plan (e.g., re-kitting, rework steps).
4. Emergency ECN process: For safety, compliance, or customer-required changes that must be applied inside the frozen window, require: ECN tag, impact statement, rework/replace plan, and explicit sign-off from Plant Manager and Supply Chain within X business hours.
5. Backwards compatibility: For phased rollouts, specify which serials or batches use old vs new BOM and update ERP/MES with clear effective dates and lot controls.

Stabilization & Release Rules (practical examples)

• Short-term freeze (execution window): Do not change parent part numbers or kit components inside 0–10 production days unless emergency ECN.
• Controlled change window: Between execution window and full planning horizon, allow changes with multi-team approval and a mitigation plan.
• Release cadence: Publish a single weekly MPS revision after reconciliation; calls for expedites should be tracked as exceptions with root-cause logged.

Escalation guide for mismatches that jeopardize delivery

1. Raise a schedule exception ticket (record: Part#, MO#, mismatch type, proposed mitigation).
2. Immediate owner: Planner resolves data/ERP mismatch within 4 business hours or escalates to Engineering for BOM correction.
3. If procurement lead time causes the issue, Procurement must confirm supplier ETA and propose alternatives within 24 hours.
4. If production capacity or tooling causes the issue, Production Supervisor proposes re-sequencing, overtime, or subcontracting within 24–48 hours.
5. If delivery is still at risk, escalate to Operations Manager who issues customer communication and recovery plan (SLA: initial plan within 48 hours).

Roles & Responsibilities (quick)

• Planner: Run reconciliations, update MPS, issue exception tickets.
• Engineering: Maintain authoritative BOMs, own ECNs and impact analysis.
• Procurement: Confirm lead times, source alternates, update ERP PO info.
• Production: Validate kits in MES, report assembly shortages, propose mitigations.
• Operations Manager / Plant Manager: Approve emergency ECNs and execute escalations that affect delivery.

KPIs to monitor

• Schedule adherence (percent of MOs completed on-time to planned finish).
• MPS drift rate (number of schedule revisions affecting same MO/part per horizon).
• Percentage of production orders with BOM mismatches at release.
• Number of emergency ECNs applied inside frozen window per month.
• Expedite events and expediting cost (labor, freight, rework).

Quick wins and next steps

• Start each weekly MPS meeting with the top five high-risk parts from the reconciliation checklist.
• Make the planner responsible for closing data-error tickets within the same shift.
• Document and enforce a simple freeze window and emergency ECN template so exceptions are consistent and auditable.
• Turn common reconciliation checks into automated reports (ERP vs BOM vs MES) where possible.

Tailor this checklist: Adjust freeze windows, SLA times, and KPI thresholds to your plant cadence, lead times, and customer commitments. This checklist is intended as a practical starting point; keep it alive by recording each week's exceptions and lessons learned.

Note: This static checklist can be converted into an interactive weekly form (collect the MPS template fields, record reconciliation outcomes, and store exceptions). Using the platform's Interactive Form and data-submission capabilities would let your team track trends, produce dashboard metrics, and build a searchable history of ECNs and escalations.