CS-OT-006 · OT Industrial telemetry and equipment acquisition · 30 of 192
Acquire burst and waveform evidence
Reliability Data Engineer · Trigger: A trigger requests high-frequency samples around an event.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
3 of 4 steps satisfiedA test capture will account for expected blocks and preserve sample timing without flattening the waveform into one scalar.
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 satisfieddefinitiondraftdeploymentcanaryruntimeHealthdegraded
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.
satisfiedOperates onFLOW-008SHF Vision system B8 → canonical flowFlow definition· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
definitionreviewdeploymentreleasedruntimeHealthhealthy
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-035HAL Document library A7 → canonical flow · run 20260934Flow run· OPTIMON-IND / Halol Packaging Line
executionsucceededadmissionpartialdeliverypartial
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: evidence entry written
Exception path
Missing blocks or incompatible sample metadata will mark the capture incomplete.
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 ingest bounded sample blocks with rate, channel, scale, trigger, sequence and evidence-object references, using appropriate bulk transport and integrity checks.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.