CS-OT-002 · OT Industrial telemetry and equipment acquisition · 26 of 192
Poll register-based or legacy equipment
OT Integration Engineer · Trigger: A device requires scheduled reads rather than subscriptions.
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 satisfiedKnown test registers will produce expected canonical values and invalid reads will retain a failure disposition.
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-018NGD Vision system F18 → canonical flowFlow definition· OPTIMON-IND / Nagda Warehouse
definitiondraftdeploymentreleasedruntimeHealthhealthy
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.
satisfiedconnectivityhealthytrusttrusteddriftcurrent
Moves the record and writes evidence. Permission: test.
Acceptance for this step: connectivity = healthy
Step 3. Deploy the flow to its placement.
not yet satisfiedOperates onFLOW-004SHF Event stream D4 → canonical flowFlow definition· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
definitionreviewdeploymentplannedruntimeHealthfailed
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-023HAL Application API E23 → canonical flow · run 20260922Flow run· OPTIMON-IND / Halol Packaging Line
executionfailedadmissionpartialdeliveryaccepted
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: evidence entry written
Exception path
Missing engineering definitions or failed reads will not produce guessed measurements or zero values.
Alternate path. Acquisition stalls: raise and assign the incident against the failing stage.
satisfiedtriagein reviewimpactblockedremediationproposed
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: triage = in review
Workflow as specified
CoreSync will apply an approved register or address map with type, endianness, scale, unit and read cadence, recording the acquisition method.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.