Show the equipment values recorded while this batch step was running.
I’ll use the current-value readings that were collected, with their timestamps. Readings between collections aren’t recorded, so gaps stay visible.
Collected current values
Equipment status note
- Readings with source timestamps
- Gaps between collected values
- Questions for the process owner
1What’s connected.
Collect current values from OPC UA servers where your approved Seal IoT installer includes OPC UA collection. It is not part of the released file workflow, and current-value collection does not provide subscriptions, history access or continuous offline sampling. Equipment that exports files can use the released file collection instead.
Connection setup and permissions
Connect through Seal’s IoT app or a scoped integration. The equipment model, software version and available interfaces determine the connection method.
Related blueprints
2Start with the job.
Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.
3Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.