DSLCore

Urgent oil result

An engine-oil result comes back urgent: Condition Monitoring raises an alert, Work is asked for a draft order, and closing the order resolves the alert.

Recorded simulation replay — generated from an actual DSLCore network run (capture-a2-20261022). Pacing is normalised for viewing; the Technical view shows the recorded timings. Nothing on this page is live.

OrchestratorWork ManagementInventoryAsset RegisterAsset LifecycleWarrantyAssuranceClassificationCondition MonitoringMaintenance ScheduleWorkforceCatalogueSupplierSAP APPurchasingOrchestratorWork ManagementWarrantyCondition MonitoringMaintenance ScheduleSAP AP

Step by step

Key moment The urgent result, the order it asks for, and the alert resolving once the order is closed. The other steps are the background every story shares.

    This step in detail

    Checked against the reference flow

    A2 — Urgent oil result to work — the alert asks Work for a draft order from the template; closing the order resolves it. The network's specification declares the messages this flow involves. Every one of them appears in this recording. It also contains messages outside the reference flow: work.create_work_order.

    1. ✓ condition.urgent_reading
    2. ✓ work.work_order_created
    3. ✓ work.work_closed
    4. ✓ condition.alert_resolved