Skip to content

Glossary

Key terms used throughout Redline and this documentation, in alphabetical order.

TermDefinition
Action listThe department-specific set of instructions generated by Redline after a phase-in date is calculated. Each action includes an ERP reference, quantity, due date, and a justification sentence.
BOMBill of Materials. The structured list of components that make up an assembly. Redline reads BOM structure from your ERP to detect where-used impacts of a component change.
Buffer daysA safety margin added to the calculated phase-in date. Default: 5 days. Configurable per tenant in Settings → Process.
CCBChange Control Board. The cross-functional group that reviews and approves, defers, or rejects ECRs. Members typically include Engineering, Procurement, Production, and Quality.
ConflictAn ERP situation — an open PO or production order — that conflicts with the calculated phase-in date and requires an action to resolve before the switch date can be honoured.
ECOEngineering Change Order. The operational document that defines the change plan, phase-in dates, and action list. Created from a CCB-approved ECR.
ECREngineering Change Request. The formal record that captures what needs to change and why. The starting point of every engineering change.
ERPEnterprise Resource Planning. Your company’s operational system — Business Central, Exact, SAP, etc. Redline reads inventory, PO, and production data from your ERP to calculate phase-in dates.
FCOField Change Order. A change instruction for machines already deployed at customer sites. Phase 2 feature — not yet available.
FFFForm, Fit, Function. The three dimensions used to classify whether a change is Minor (no FFF impact on the customer interface) or Major (changes form, fit, or function).
Governing dateIn a multi-item ECO, the latest phase-in date across all affected items. Recommended as the ECO implementation date so all items switch simultaneously.
Lead timeThe number of days between ordering a new part and receiving it. Used in the phase-in calculation to ensure the new part arrives before the switch date.
N1 / N2 / N3Redline’s three automated notification triggers. N1 = ECO published (action assigned to owner). N2 = 48-hour reminder if action is still Open. N3 = overdue escalation to owner and engineering manager.
Phase-in dateThe date at which the new part officially replaces the old part in production. Calculated by Redline from ERP data using the selected strategy.
Phase-in strategyThe approach used to manage the transition from old to new part. Redline supports four strategies: Run-down, New-only, Stop, Proactive.
ProactiveA phase-in strategy where the switch date is set to align with a specific production milestone rather than being driven by stock depletion.
Run-downThe default phase-in strategy. Continue using existing old-part stock and honour all open POs before switching to the new part. Minimises write-offs.
Staleness thresholdThe maximum age of ERP data before Redline blocks phase-in calculations. Default: 24 hours. Configurable per tenant in Settings → Process.
StopA phase-in strategy that switches to the new part at the earliest possible date — today plus new part lead time. Used for safety or compliance-driven changes. May result in inventory write-offs.
TenantYour company’s isolated workspace in Redline. All data, settings, and users are scoped to your tenant. No other company using Redline can see your data.
Where-usedThe set of assemblies and products that contain a given component. Redline uses BOM structure data to identify where-used impacts when a component changes.