Engineering Change Order Cut-Over Verification Spec

Role: Lead Production Integration Engineer with expertise in plant floor operations and configuration management.

Context

• Engineering Change Number: {{eco_number}}
• Plant / Station ID: {{assembly_station_id}}
• Responsible Facility / Sub-Contractor: {{subcontractor_facility}}
• Obsolete Inventory Scrap Exposure: {{scrapped_inventory_risk}}
• Line Downtime Rate: {{downtime_hourly_cost}}
• Start of Production (SOP) Date: {{target_line_sop_date}}

Task

Generate a comprehensive Engineering Change Order (ECO) follow-up specification and operational email sequence to enforce tooling cut-over verification and eliminate scrap production.

Method

1. Review the scope of {{eco_number}} against tooling requirements at {{assembly_station_id}}.
2. Calculate the financial burn exposure combining {{downtime_hourly_cost}} and {{scrapped_inventory_risk}}.
3. Identify mandatory cut-over physical artifacts (e.g., serial break points, revised work instructions, scrap bin locks).
4. Establish a mandatory physical sign-off checklist for the shift manager at {{subcontractor_facility}}.
5. Draft an urgent, unambiguous operational follow-up email demanding immediate confirmation of First Piece Inspection (FPI).
6. Set clear quarantine procedures for legacy parts produced past the effective revision date.

Constraints

• MUST require positive verification of First Piece Inspection before serial production restart.
• MUST NOT authorize verbal or undocumented acknowledgments of {{eco_number}}.
• Financial metrics must clearly highlight {{downtime_hourly_cost}} to underscore urgency.
• Language must be actionable for plant floor managers and quality inspectors alike.

Output format

• Section 1: ECO Operational Cut-Over Parameter Table
• Section 2: First Article & Legacy Purge Requirements
• Section 3: Action-Oriented Operations Follow-Up Email (Under 250 words)
• Section 4: Non-Compliance Containment & Line Stop Trigger Spec

Self-review

• Does the follow-up draft provide clear instructions on how to handle legacy inventory?
• Is the timeline strictly bounded by {{target_line_sop_date}}?
• Are physical proof artifacts (e.g., red tags, traveler sign-offs) explicitly mandated?