Skip to main content

Integration guideHistorian gateway

OPC UA

Collect current OPC UA values where an approved Seal Edge installer includes it.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

OPC UA to SealHistorian gateway

Seal reads
Collected current values
Writes back
No
Source of truth
The OPC UA server
Set up
Scoped with your team
Neil › Equipment status note
draft

Show the equipment values recorded while this batch step was running.

Neil

  • I’ll use the current-value readings that were collected, with their timestamps. Readings between collections aren’t recorded, so gaps stay visible.
Reads
Collected current values
Returns
  • Readings with source timestamps
  • Gaps between collected values
  • Questions for the process owner
Illustrative work with OPC UA: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Collect current values from OPC UA servers where your approved Seal Edge 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 Edge or a scoped integration. The equipment model, software version and available interfaces determine the connection method.

Related blueprints

2Read an OPC UA node’s current value, status and time.

Route

The Read service reads one or more attributes of one or more nodes. If the server cannot meet the maximum age requested, it returns its best-effort value rather than refusing.⁠¹ A variable’s AccessLevel says whether it can be read or written and whether it holds current or historical data. Seal’s collection reads current values only.⁠²

Record identity

A NodeId identifies a node within a server, so keep the server with every NodeId.⁠³ Each value carries a sourceTimestamp, the time the data source applied, and a serverTimestamp, when the server received it or knew it to be accurate.⁠⁴

Units and status

The EngineeringUnits property gives an analog item’s units, but it is optional, so a server may not expose them.⁠⁵ A Bad StatusCode means the value is not usable and Uncertain that its quality is uncertain. A client must check at least the severity before using a value.⁠⁴

When it fails

Every value reports Good
A server that does not support status information must still return Good.⁠⁴ Ask the equipment owner whether the server reports status before relying on Good.
The value is older than expected
A server that cannot meet the maximum age returns its best effort.⁠¹ Compare the sourceTimestamp with the time of the read before attaching the value.
No units arrive
EngineeringUnits is optional.⁠⁵ Agree each node’s unit with the automation team and keep it in the mapping.

Check one record

Read one node, such as a bioreactor temperature, and attach the value in Seal. It should keep the NodeId and its server, both timestamps, the StatusCode and the unit. Compare it with the equipment’s own display at the same moment.

3Start 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.

Discuss this connection →

4Before 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.

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.

Read the assurance detail →

References

  1. 1OPC UA Part 4: Read.
  2. 2OPC UA Part 3: Variable attributes.
  3. 3OPC UA Part 3: NodeId.
  4. 4OPC UA Part 4: DataValue.
  5. 5OPC UA Part 8: EngineeringUnits.