Define the signal
Describe the external source, its identifier, meaning, type, timestamp and expected update rate. Determine whether the signal represents current state, a transition or a measured value. Define what an absent or stale value means.
Combine it with video
A scenario can use equipment state or process context to interpret visual observations. Agree identifier mapping, clock synchronisation, allowable age and state lifetime. Test out-of-order updates and source interruptions.
Separate observation and control
Sending a notification and controlling equipment have different engineering consequences. A control interface requires a project-specific design, validation, interlocks and failure-state analysis. The availability of a scenario block does not establish safety certification.
Validate the adapter
Check authentication, data formats, retries, timeouts and recovery. Simulate signal loss and reconnects before enabling the intended operating workflow. Exact protocols and adapters are part of the delivery specification.
Normalized values and reusable bindings
Normalize an incoming signal to a Boolean condition, numeric value or category that the scenario understands. The adapter remains responsible for the original protocol. Bind a signal group to a camera or site so that one graph can be reused with different telemetry sources.
In Sandbox, set a controlled default value and test both branches of the condition. In the live configuration, check signal freshness and behavior after communication loss separately.