Run a calculation

The phase-in calculation runs on the ECO Phase-In tab. It analyses all affected items against live ERP data and produces a synchronised phase-in date, financial exposure summary, and per-item breakdown.

When calculation runs

At the EC level (preview) — on the Affected Items tab, select a strategy and click Suggest Phase-in Dates. These are suggestions you can accept or reject before creating the ECO.
At the ECO level (final) — open the ECO and go to the Phase-In tab. Click Calculate phase-in to run the full v2 calculation with financial exposure, conflict detection, and MOQ analysis.
Recalculate — after ERP data changes, click Recalculate on the decision header to refresh everything.

The Phase-In result view

The Phase-In tab is divided into five zones, top to bottom.

Zone 1 — Decision header

The top banner shows three key outputs at a glance:

Element	What it shows
Synchronised date	The governing phase-in date across all items (the latest individual date). Labelled “(synchronised)” when it differs from any item’s individual date.
Driver item	The specific item whose calculation produced the synchronised date, with its revision change (e.g. rev A → B).
Data confidence	A 0–100 score indicating how complete the ERP data is. Green (80+), amber (60–79), red (below 60). Shows the data snapshot age.

Three action buttons are always available: Recalculate (runs fresh calculation), Run what-if (opens the simulator), and Override date (manual override).

If no calculation has been run yet, only a single Calculate phase-in button is shown.

Zone 2 — Financial exposure strip

Four metric cards summarising the financial impact across all affected items:

Card	What it measures
Stock at risk	Old-revision inventory that cannot be consumed before phase-in. Shows unit count and EUR value.
PO exposure	Open purchase orders arriving after the phase-in date. Shows EUR value and PO count.
Total risk	Combined financial exposure (stock + POs). Red left-border when above zero.
MOQ saving opportunity	Potential savings from reducing PO quantities to minimum order quantities. Green left-border when suggestions exist.

All monetary values are formatted in EUR.

Zone 3 — Item result cards

Each affected item appears as a collapsible card. The collapsed row shows: item reference, type, strategy, revision change, phase-in date, confidence score, and badges for conflicts and MOQ suggestions. The sync driver item is tagged with a “driver item” label and expanded by default.

Expanding a card reveals two panels side by side:

Left panel — Timeline visualisation. A horizontal SVG timeline showing:

Open PO bars (amber if before phase-in, red if after)
Production order bars (blue if in scope, muted if not)
A vertical red line at the phase-in date
A dotted vertical line for today
Stock level indicator

Right panel — Reasoning. Under the heading “WHY THIS DATE”:

Bullet points explaining the calculation logic (e.g. “Last PO delivery on 28 May, +5 buffer days”)
A collapsible “Show AI reasoning” section with the full prose explanation

Below the panels: conflict flags (amber for standard, red for IMMEDIATE_ACTION) and MOQ suggestions (green, showing PO number, current vs suggested quantity, and potential saving).

Zone 4 — What-if simulator

A collapsible panel for testing alternative dates. Enter a target date or use the quick-shift buttons (±4 weeks) and click Run simulation. The result shows:

Feasibility — green (feasible), amber (warning), or red (infeasible)
Financial delta — the cost difference compared to the calculated date. Green for savings, red for additional cost.
Stranded items — count of POs and production orders that would be stranded

Click Save as scenario to preserve the simulation for later comparison. Click Commit this date to promote it to the actual phase-in date — a confirmation dialog asks whether to notify affected assignees.

Previously saved scenarios are listed below the simulator, with a “Committed” badge on the active one.

Zone 5 — Sales order impact

A collapsible table showing customer delivery commitments affected by the change. Each row shows the customer name, order number, item, quantity, delivery date, and whether the commitment falls before or after the phase-in date (amber “After phase-in” badge for at-risk deliveries).

Only appears when sales order data exists for affected items.

Drift detection

If ERP data changes after a calculation, Redline detects the drift automatically. An amber banner appears at the top of the Phase-In tab:

⚠ Phase-in drift detected — AGX-MOT-024 shifted from 15 May to 1 June (+17 days).

Click Recalculate all to update all dates. Dismiss the banner with ✕ (it reappears on page reload if drift persists).

Manual override

To override the calculated date, use the What-if simulator: enter your target date, run the simulation to see the impact, save as a scenario, then commit. The override is recorded in the audit trail with the original calculated date preserved.

EC-level phase-in suggestions

Before an ECO exists, engineers can preview phase-in dates directly on the EC:

Open the EC and go to the Affected Items tab
Select a strategy from the dropdown (RunDown, NewOnly, Stop, or Proactive)
Click Suggest Phase-in Dates
Review each item’s suggested date, conflict flags, and action preview
Click Accept on individual items, or Accept All to accept every complete suggestion

Lead time resolution

Redline resolves lead times using one of three priority modes (configurable in Settings):

Mode	Resolution order
Item master first (default)	Item master lead time → preferred supplier lead time → any supplier lead time
Supplier preferred first	Preferred supplier lead time → item master lead time → any supplier
Supplier shortest	Shortest supplier lead time across all suppliers

If no lead time can be resolved, Redline raises a MISSING_LEAD_TIME conflict flag.

Buffer days

A configurable safety margin (default: 5 days) is added to every calculated phase-in date. Change the buffer in Settings.