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.
BOM upload wizard
Section titled “BOM upload wizard”BOM upload uses a guided 3-step wizard on a dedicated page. Open it from the EC detail page by clicking Upload BOM → (or Open BOM Comparison → if a BOM was already uploaded).
Step 1 — Upload
Section titled “Step 1 — Upload”Drag and drop a CSV file or click to browse. Redline parses the file instantly in your browser — no server round-trip needed. You see:
- Column mapping preview — which CSV headers mapped to which Redline fields, with a sample value from the first row
- First 10 rows — a quick sanity check that the data looks right
- Detected delimiter, encoding, and total row count
If client-side parsing fails (encoding issues, unusual format), Redline automatically falls back to server-side parsing.
Step 2 — Review & Fix
Section titled “Step 2 — Review & Fix”Redline validates the parsed BOM against three structural 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 as expandable cards — each card shows the rule, affected item count, and a list of specific items with suggested fixes. Warnings (duplicate lines, missing fields) are shown separately.
The full BOM is displayed in a paginated table (20 rows per page) with rows containing issues highlighted.
Step 3 — Confirm
Section titled “Step 3 — Confirm”A summary screen showing total line count, violation count, and the active push mode. Click Confirm & Import to persist the BOM to the database. This is the only step that writes data — Steps 1 and 2 are entirely preview.
After confirmation, Redline:
- Inserts all BOM lines
- Creates a BOM snapshot record
- Runs delta calculation (Full BOM mode)
- Updates the EC status to
bom_uploaded
Other upload methods
Section titled “Other upload methods”- Manual entry — add individual BOM lines using the inline form (available on the EC detail page)
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.