Scenarios
Deliberate cross-system lags, duplicate source records and event-ordering conditions built into the frozen Day-0 reference estate. They are verified when the reference estate is built and are part of the Day-0 state, not defects.
Loading…
Loading…
12 scenarios
| Key | Name | Details |
|---|---|---|
| SCN-X01 | HR hire → ERP employee lag | HR → ERPStanding at Day-0An employee has been hired in HR, but ERP does not yet hold an employee reference for them. ERP catches up when that reference is synchronised. |
| SCN-X02 | Termination access lag | HR → ERP/POS/MESStanding at Day-0An employee is terminated in HR while their ERP login remains active and an open role grant still applies — operational access has outlived employment. |
| SCN-X03 | CRM duplicate account | CRM → ERPStanding at Day-0Two CRM accounts describe the same customer and both point to the same ERP customer. Entity resolution treats all three source records as one canonical Organization while preserving the source records. |
| SCN-X04 | Won deal order lag | CRM → ERPStanding at Day-0A CRM opportunity reached Closed Won after the last CRM-to-ERP hand-off, so the corresponding ERP sales order has not yet been created. |
| SCN-X05 | Retail stock mismatch | POS → ERPStanding at Day-0A franchise store has produced its daily POS inventory summary, but the summary has not been sent to ERP, leaving POS and ERP out of sync for that store day. |
| SCN-X06 | Franchise offline sync | POS → ERPStanding at Day-0A franchise store sent a prior-day sync batch, but the centre has not yet fully acknowledged the records it received. |
| SCN-X07 | Production dispatch lag | ERP → MESStanding at Day-0ERP has released a production order, but it has not yet been handed off to MES, so no MES work order exists for it. |
| SCN-X08 | Quality release lag | MES → ERPStanding at Day-0MES released a quality hold, but the release was not sent to ERP, so ERP has not caught up and the corresponding inventory remains blocked. |
| SCN-X09 | IoT/MES event ordering | IoT → MESStanding at Day-0An operator recorded a manual machine stop in MES before an IoT alert for the same machine arrived, so Day-0 preserves the two system events in that order. |
| SCN-X10 | Warranty fulfillment lag | Support → ERPStanding at Day-0Approved warranty claims have remedies sent from Support, but ERP has not produced the corresponding replacement order or credit note for the lagging claims. |
| SCN-X11 | POD acknowledgement lag | Logistics → ERPStanding at Day-0A proof of delivery has been recorded in Logistics, but ERP has not yet confirmed the corresponding delivery. |
| SCN-X12 | Delivery/receipt lag | Logistics → POSStanding at Day-0A shipment has been delivered to a store, but POS has not yet booked the corresponding goods receipt. |