Create an ECO
An ECO is created from an approved Engineering Change (EC). The coordinator prepares the BOM, reviews the delta, and runs the phase-in calculation before releasing.
Engineering Change Details
Section titled “Engineering Change Details”The EC detail page opens on the Engineering Change Details tab, which contains the BOM upload section and any attachments. Redline supports two push modes for BOM data:
Change Package mode
Section titled “Change Package mode”Upload only the changed items. Each line includes the item reference, revision, quantity, and change type (added / removed / revised / qty_changed). Use this when your PLM system exports a change package.
Full BOM mode
Section titled “Full BOM mode”Upload the complete assembly BOM. Redline automatically calculates the delta by comparing the uploaded BOM against the current ERP BOM. Items are classified as added, removed, revised, or quantity changed. Unchanged items are shown for reference but not stored as affected items.
Upload methods
Section titled “Upload methods”- CSV upload — drag and drop a CSV file. Redline auto-detects column names (supports English, Dutch, and German headers) and delimiter format
- Manual entry — add individual BOM lines using the inline form with item reference, revision, quantity, and change type fields
- Edit inline — after upload, edit any BOM line directly in the table
BOM validation
Section titled “BOM validation”After upload, Redline runs three structural validation rules:
| Rule | What it checks | Fix |
|---|---|---|
| BOM_RULE_01 | BUY item under a BUY parent | Change child item type to DUMMY |
| BOM_RULE_02 | MAKE or BUY under a DUMMY parent | Change child item type to DUMMY |
| BOM_RULE_03 | MAKE under a BUY parent | Change child item type to DUMMY |
Violations are displayed in separate containers per rule. Use the inline item type dropdown to fix each violation, then click Re-validate. When validation passes, the BOM can be pushed to ERP (automatically if bom_auto_push_on_clean is enabled).
BOM comparison view
Section titled “BOM comparison view”For Full BOM mode, the comparison view shows a side-by-side layout:
- Left — current ERP BOM
- Right — new uploaded BOM
- Delta highlighting — green border for added, red for removed, blue for revised, orange for quantity changed
- Summary bar — counts of each change type
- Toggle — show all items or affected only
Affected items
Section titled “Affected items”After delta calculation, the affected items table shows every item that changed:
| Column | Description |
|---|---|
| Item ref | Part number (monospace) |
| Change type | Added, removed, revised, or qty_changed (colour-coded badge) |
| Old → new revision | Revision comparison |
| Old → new quantity | Quantity comparison |
| Phase-in date | Calculated or manually set |
| Conflict status | Flags from conflict detection |
Items are enriched with live ERP data: current stock on hand, open purchase orders, active production orders, and lead times.
Implementation strategy
Section titled “Implementation strategy”Select one of the four phase-in strategies for the ECO:
| Strategy | When to use |
|---|---|
| Run down | Default. Use existing stock before switching. Phase-in = latest commitment date + buffer. |
| New only | Stop ordering old part immediately. Cancel outstanding POs. |
| Stop | Halt everything now. Immediate phase-in. Risk of write-off. |
| Proactive | Coordinator selects a target date. Triggers field change orders. |
See The four strategies for detailed guidance.
Multiple top-level assemblies
Section titled “Multiple top-level assemblies”An EC can have multiple top-level assemblies, each with its own BOM. Upload BOMs separately for each assembly. Phase-in dates are calculated per item across all assemblies.