Key concepts
This page explains the core concepts you will encounter in Redline. For formal definitions of all terms, see the Glossary.
ECR vs EC vs ECO
Section titled “ECR vs EC vs ECO”These three document types form the change lifecycle:
| Document | Full name | Purpose | Created by |
|---|---|---|---|
| ECR | Engineering Change Request | Captures what needs to change and why. A proposal — not yet approved. | Any user |
| EC | Engineering Change | The approved change scope. Holds the BOM, affected items, and coordinator assignment. | Auto-created on ECR approval, or created manually |
| ECO | Engineering Change Order | The execution order. Contains phase-in dates, the action list, and notification history. | Created from an approved EC |
An ECR becomes an EC when approved. An EC becomes an ECO when the coordinator is ready to execute.
The four phase-in strategies
Section titled “The four phase-in strategies”When creating an ECO, you choose a strategy that determines when the switch happens:
| Strategy | Phase-in date logic | Use when |
|---|---|---|
| Run down | Latest open commitment date + buffer | You want to use up existing stock and open orders before switching |
| New only | Today + new part lead time | You want to stop ordering the old part immediately |
| Stop | Today | Production cannot continue with the old part (safety, regulatory) |
| Proactive | Coordinator-selected target date | You want to implement on a specific date, regardless of stock |
See The four strategies for detailed guidance.
Conflict flags
Section titled “Conflict flags”Redline warns you when the calculated phase-in date creates operational problems:
| Flag | Meaning |
|---|---|
| PO after phase-in | A purchase order for the old part arrives after the switch date |
| Production order after phase-in | A production run using the old part ends after the switch date |
| Missing lead time | Redline cannot resolve the lead time for the new part |
| Concurrent EC | Another open EC affects the same item |
| FCO required | A field change order is needed (proactive/stop strategy) |
| Immediate action | Item is actively in use and requires urgent intervention |
Every conflict flag generates a corresponding action item in the action list.
Action items and departments
Section titled “Action items and departments”When an ECO is released, Redline generates an action list — a set of department-specific instructions derived from the affected items and ERP data. Each action contains:
- What to do (cancel PO, update BOM, hold production order)
- The specific ERP reference (PO number, production order ID)
- The quantity and date
- A plain-language justification
- A due date and priority
Actions are grouped by department. Each department receives only their actions by email.
Notification tiers
Section titled “Notification tiers”Redline uses a three-tier notification system to ensure actions get done:
| Tier | When | Who |
|---|---|---|
| N1 — Release | ECO is released | Department assignees |
| N2 — Reminder | Action still open after delay (default: 48 hours) | Same assignees |
| N3 — Escalation | Action still open after escalation threshold | Coordinator, then director |
Recipients can update their action status directly from the email — no login required.
| Role | Access level |
|---|---|
| Coordinator | Full access — create, edit, approve, configure |
| Department user | View tasks, update action status |
| Viewer | Read-only |
| CCB member | Additional flag — sees ECRs in CCB review status |
BOM structure
Section titled “BOM structure”Redline works with hierarchical Bills of Materials. Each BOM line has:
- Item type — MAKE (manufactured), BUY (purchased), PHANTOM (virtual assembly), DUMMY (placeholder)
- BOM level — 0 for top-level assembly, 1+ for sub-components
- Quantity per — how many of this item go into the parent
- Revision — current item revision level