BMW-targeted concept demonstration. Operational entities, suppliers, parts, inventory, production, financial values and incident conditions are synthetic and do not represent BMW systems, performance or current exposure.
Pilot Readiness Brief
Generated from AutoResilience demonstration dataset (Meridian Stamping). Every figure below is recalculated from the loaded data — nothing on this page is written by hand.
From an SAP or EDI interruption to a production event
Read from the imported dependency model.
The supplier's 830 Planning Schedule interruption prevents confirmation of the next scheduled shipment. Synthetic SC Assembly has 22.4 hours of verified usable inventory for 98R-1225. Without confirmation, inventory transfer, or alternate supply, Line SC-2 (final assembly) is projected to stop 22.4 hours from the analysis clock.
3 affected systems · 10 affected interfaces · 3 of them with no manual fallback on record. This is why the interruption is a measurable production event and not only an IT outage.
Data received
Built-in demonstration dataset — no customer import in this session.
| Suppliers / sites | 25 / 51 |
| Parts | 250 |
| Plants / lines / programs | 3 / 8 / 4 |
| Systems / interfaces | 20 / 30 |
| Inventory pairs / customer commitments | 297 / 40 |
| Dependency relationships | 717 |
Data rejected
Rows that could not be accepted, by file.
No import in this session, so nothing was rejected.
Material data gaps
Categories that limit the conclusion, with the named records behind them.
- ▲ 27A-1000: count is 120h old (No inventory record found)
- ▲ 14Z-1025: count is 168h old (Contract schedule A)
- ▲ 14Z-1025: count is 72h old (Supplier questionnaire 2026-02-02)
- ▲ 40Y-1050: count is 72h old (SAP S/4HANA MM extract 2026-03-14)
- ▲ 99X-1075: count is 96h old (Contract schedule A)
- ▲ 99X-1075: count is 96h old (MES routing master 2026-03-01)
- ▲ 27A-1000: 1283 units in transit with no confirmed ETA
- ▲ 65I-1008: 1397 units in transit with no confirmed ETA
- ▲ 23L-1011: 786 units in transit with no confirmed ETA
- ▲ 39O-1014: 803 units in transit with no confirmed ETA
- ▲ 39O-1014: 1078 units in transit with no confirmed ETA
- ▲ 14Z-1025: 1174 units in transit with no confirmed ETA
- ▲ 14Z-1025 via Belmont Die Casting: partial
- ▲ 40Y-1050 via Weyland Forge: unqualified, capacity never validated
- ▲ 99X-1075: single source with no alternate on record
- ▲ 50S-1200: single source with no alternate on record
- ▲ DEP-0006 (SUP-002 → SITE-006): stale, confidence 64%
- ▲ DEP-0012 (SUP-004 → SITE-012): unvalidated, confidence 63%
- ▲ DEP-0016 (SUP-006 → SITE-016): unvalidated, confidence 56%
- ▲ DEP-0017 (SUP-006 → SITE-017): stale, confidence 54%
- ▲ DEP-0018 (SUP-006 → SITE-018): unvalidated, confidence 71%
- ▲ DEP-0025 (SUP-009 → SITE-025): stale, confidence 67%
Validated dependency coverage
| Relationships in the model | 717 |
| Validated | 459 |
| Unvalidated or stale | 258 |
| Entities reached from the incident | 94 |
| Part–line pairs not calculable | 1 |
Initial concentration risks
| Supplier | Parts | Single source | Lines touched |
|---|---|---|---|
| Quantum Harness Co | 10 | 6 | 8 |
| Belmont Die Casting | 10 | 6 | 8 |
| Ironwood Fasteners | 10 | 5 | 8 |
| Frontier Axle | 10 | 5 | 8 |
| Meridian Stamping | 10 | 4 | 8 |
Shared technology providers: Meridian Stamping (Meridian ERP (SAP ECC), 4 downstream links); Meridian Stamping (Meridian EDI Gateway, 8 downstream links); Meridian Stamping (Meridian Shipping WMS, 3 downstream links); Silverline Logistics (Global TMS, 3 downstream links); Silverline Logistics (Milk-run Scheduler, 1 downstream links); Halbrecht Drivetrain (Halbrecht ERP, 1 downstream links); Kessler Wire Systems (Kessler EDI Gateway, 1 downstream links).
Scenario analysed
INC-2026-0113 · Meridian Stamping ransomware — ERP and EDI unavailable
Highest-value intervention
Reduce the production rate to 70%
Stretch existing stock by building slower across the exposed lines.
Approvals required: Plant Manager · Customer Programs Lead
Decisions requiring customer validation
- ▲ Calculate time to shutdown — Rates are present but some counts are older than one production day, so hours of cover are reported as estimates.
- ▲ Count confirmed inbound supply as relief — Inbound shipments lack confirmation or ETAs, so none of them can extend the countdown.
- ▲ Decide whether an alternate source closes the shortage — Alternate capacity claims are unqualified or never validated, so they cannot be relied on to close a shortage.
- ▲ Defend the conclusion in a customer or audit review — Dependency ownership or evidence currency is incomplete, so parts of the conclusion rest on unattributed data.
- ▲ Confirm the 72h supplier recovery estimate against evidence, not a verbal statement.
- ▲ Confirm the transfer and expedite lead times used in the intervention analysis.
- ▲ Confirm who holds authority to release safety stock and to reprioritise a program.
Additional data needed for a production pilot
- • 27A-1000: count is 120h old (No inventory record found)
- • 14Z-1025: count is 168h old (Contract schedule A)
- • 14Z-1025: count is 72h old (Supplier questionnaire 2026-02-02)
- • 27A-1000: 1283 units in transit with no confirmed ETA
- • 65I-1008: 1397 units in transit with no confirmed ETA
- • 23L-1011: 786 units in transit with no confirmed ETA
- • 14Z-1025 via Belmont Die Casting: partial
- • 40Y-1050 via Weyland Forge: unqualified, capacity never validated
- • 99X-1075: single source with no alternate on record
- • DEP-0006 (SUP-002 → SITE-006): stale, confidence 64%
- • DEP-0012 (SUP-004 → SITE-012): unvalidated, confidence 63%
- • DEP-0016 (SUP-006 → SITE-016): unvalidated, confidence 56%
- • A daily inventory and consumption extract rather than a point-in-time file.
- • Shipment confirmation status from the transport or EDI platform.
- • Named owners for each dependency relationship not yet attributed.
Recommended pilot scope
- Two plants (Synthetic SC Assembly and Synthetic Saltillo Assembly) and the Synthetic X-Program SX-1 / Synthetic Pickup Program programs.
- The 40 parts on the exposed lines, with their supplier sites and single-source flags.
- The transaction chain already modelled: OEM SAP S/4HANA → Supplier scheduling → 830 Planning Schedule → Inbound logistics — enough to prove an SAP or EDI interruption as a production event.
- A daily data feed for inventory, consumption and inbound shipment confirmation.
- Two rehearsed scenarios: this supplier ransomware case and one shared technology-provider outage (Meridian Stamping).
- Six weeks, ending in an operator-run walkthrough and a signed set of validated assumptions.