CS-OT-004 · OT Industrial telemetry and equipment acquisition · 28 of 192
Receive machine alarms and condition changes
Operations Data Engineer · Trigger: A control system reports alarm or condition transitions.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
2 of 4 steps satisfiedRaise, acknowledge and clear test events will remain separately traceable and correctly ordered within scope.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
Equipment telemetry is acquired by a deployed flow on a healthy runtime, with the run ledger inspected.
Step 1. Validate the flow definition including its recovery contract.
not yet satisfiedOperates onFLOW-020SHF Partner SaaS B20 → canonical flowFlow definition· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
definitionreviewdeploymentblockedruntimeHealthhealthy
Moves the record and writes evidence. Permission: test.
Acceptance for this step: definition = approved
Step 2. Confirm the runtime that will execute it is reachable.
not yet satisfiedconnectivityunreachabletrustreviewdriftcurrent
Moves the record and writes evidence. Permission: test.
Acceptance for this step: connectivity = healthy
Step 3. Deploy the flow to its placement.
satisfieddefinitiondraftdeploymentreleasedruntimeHealthhealthy
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: deployment = released
Step 4. Inspect the run: admitted, published and receipts compared.
satisfiedOperates onRUN-033RGH Relational database E5 → canonical flow · run 20260932Flow run· OPTIMON-IND / Raigarh Melt Shop
executionsucceededadmissioncompletedeliveryaccepted
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: evidence entry written
Exception path
Missing lifecycle transitions will be surfaced as incomplete alarm history.
Alternate path. Acquisition stalls: raise and assign the incident against the failing stage.
not yet satisfiedtriageresolvedimpactdegradedremediationcomplete
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: triage = in review
Workflow as specified
CoreSync will preserve alarm identity, active/cleared state, severity, occurrence time and source acknowledgement status without converting an alarm acknowledgement into physical resolution.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.
Journeys that include it
Not part of a composite journey; exercised through its family views.