5.1 MES rollout method: pilot, line, factory & cutover checklist

Deploying a new MES or ERP module acts as a transplant of the manufacturing facility’s nervous system. A “Big Bang” deployment (switching everything at once) is generally considered a highly risky strategy. Should the system fail under this approach, the factory stops, and revenue drops to zero.

A Phased Rollout Architecture must be adopted to isolate risk and practically validate the solution before scaling.

The three-phase strategy

It is best practice to avoid deploying to the entire floor until the system demonstrates stability on the “Golden Line.”

Phase 1: the pilot (offline / low volume)

Scope: A single NPI (New Product Introduction) line or a dedicated testing cell.
Duration: 2–4 Weeks.
Objective: Validate the Core Model (Integration, Label Printing, Interlocking).
Risk: Low. No impact on mass production revenue.

Phase 2: the golden line (production beta)

Scope: One high-volume production line running real customer orders.
Duration: 2 Weeks.
Objective: Stress test logic under Cycle Time Pressure and Shift Variance.
Risk: Medium. Requires a comprehensive “Rollback Plan” (the ability to revert to the legacy system or paper documentation within 1 hour).

Phase 3: the factory rollout (scale)

Scope: Remaining lines in waves (e.g. 2 lines per week).
Duration: Variable.
Objective: Replication and Stabilization.
Risk: High impact, but Low probability (if Phase 2 was honest).

Entry & exit criteria (the gates)

It is recommended to proceed to the next phase based solely on Metrics, rather than predetermined dates.

Phase	Entry Criteria	Exit Criteria
Pilot	UAT (User Acceptance Test) Sign-off. 100% Master Data loaded.	100 consecutive units produced with 0 critical errors.
Golden Line	Pilot Exit Met. Training 100% complete for Line A crews.	24 Hours continuous uptime. OEE matches or exceeds baseline.
Factory	Golden Line stable for 5 days. Hypercare team assembled.	All lines migrated. Old system Decommissioned.

The cutover checklist (go-live weekend)

The transition from “Old” to “New” requires a surgical cutover.

The “drain” strategy (WIP handling)

Migrating live WIP data is complex and susceptible to corruption. It is generally advisable to avoid it if possible.

Action: Loading new units into the line must be stopped 24 hours prior to cutover.
Action: All existing units must be flushed out to Finished Goods Inventory (FGI).
State: The Line is empty. Physical Work In Progress (WIP) = 0. System Work In Progress (WIP) = 0.

The paper purge

Action: All old paper travelers, log sheets, and cheat sheets must be removed from the floor.
Logic: When paper documentation remains available, operators will likely default to using it. Removing it ensures adoption of the new system.

Account validation

Action: It must be verified that every operator on the roster has a valid Login ID and Badge Scan access.
Test: The Shift Lead must be required to log in at every terminal 2 hours before start.

Connectivity check

Action: All Programmable Logic Controllers (PLCs), printers, and scanners must be ping tested from the VLAN.
Action: One dummy label must be printed at every station.

Training & certification

PowerPoint slides cannot effectively teach muscle memory. Training should emphasize a “Driver’s Ed” hands-on style.

Role-Based Modules:
- Operators: “How to Start,” “How to Handle Errors,” “How to Reprint.”
- Line Leads: “How to Reassign Users,” “How to override Interlocks.”
- Maintenance: “How to swap an Edge PC,” “How to check PLC comms.”
The Certification Gate:
- Rule: A User ID should only be activated in the Production Environment after the user successfully passes a practical exam (Simulator).
- Threshold: 100% Pass rate required for access.

Hypercare (the ICU)

The first 2 weeks of live production are critical and should not be treated as “Business as Usual.”

Visual identification

Action: IT / MES Engineers must wear distinct high-visibility vests (e.g. Orange “MES Support” Vests).
Placement: 1 Support Engineer stationed on the line (not in the office) for every 2 active lines.

The war room

Cadence: Daily Standups at 08:00 (Start of Shift) and 16:00 (End of Shift).
Agenda: Review Incident Log, Prioritize Bug Fixes, Go/No-Go for next wave.

Bug triage SLA

During Hypercare, standard SLAs are suspended. Speed is paramount.

Showstopper (Line Down): Response < 5 mins. Fix < 1 Hour.
Major (Workaround available): Fix < 24 Hours.
Minor (Cosmetic): Backlog.

Final Checkout: MES rollout method (pilot -> line -> factory) + cutover checklist

Category	Metric / Control	Threshold / Rule
Testing	SIT / UAT	100% of Critical Test Cases passed before Pilot.
WIP	Sanitation	Line drained to 0 units before Go-Live (Clean Start).
Access	User Validation	100% of Shift Roster tested for login access 2 hours prior.
Support	Coverage	Support Engineers visibly present on-floor for first 3 shifts.
Fallback	Rollback Plan	Decision point defined (e.g. “If Line Down > 2 hours, revert to Paper”).
Training	Compliance	0% of Operators allowed to login without Exam Pass.
Hardware	Spares	10% spare scanners/printers staged in the War Room.