Skip to main content

Integration guideHistorian gateway

Siemens S7

Bring S7 controller data into Seal through OPC UA or exported files.

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

Siemens S7 to SealHistorian gateway

Seal reads
Scoped S7 tag data
Writes back
No
Source of truth
The S7 controller
Set up
Scoped with your team
Neil › Batch comparison
draft

Compare the controller values recorded for these two batches.

Neil

  • Once the scoped connection supplies the tags, I’ll compare them with their timestamps and units, and list any values it doesn’t provide.
Reads
Scoped S7 tag data
Returns
  • Tag values with timestamps and units
  • Differences between the batches
  • Missing or unmatched values
Illustrative work with Siemens S7: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Bring process data from Siemens S7 controllers into Seal through a scoped integration, for example through an OPC UA server or exported files collected with Seal Edge. The released Seal Edge workflow collects files; it does not read controllers directly. Confirm the controller, network route and tags with your automation team.

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

2Reach S7-1500 data through its OPC UA server or its DataLogs.

Route

Siemens’ manual for the CPU 1513-1 PN says the CPU can act as an OPC UA server, with data access (read, write and subscribe), method calls and a custom address space.⁠¹ The December 2014 edition of the S7-1500 web server manual says its file browser shows the SIMATIC memory card and gives read-only access to DataLogs.⁠²

Record identity

Siemens describes the S7-1500 OPC UA server as giving symbolic read access to PLC data, and its example Read response returns a value with a timestamp and Status Good.⁠³

Limits

On the CPU 1513-1 PN, OPC UA needs a runtime licence, the Small licence, and the server allows at most 32 sessions and 50,000 accessible variables. These figures are for that CPU.⁠¹

When it fails

The server refuses another client
The CPU 1513-1 PN allows at most 32 OPC UA sessions.⁠¹ Count the clients already connected with the automation team before adding one.
OPC UA is not available on the CPU
OPC UA on the CPU needs a runtime licence.⁠¹ Confirm the licence before scoping the connection.

Check one record

Read one tag through the CPU’s OPC UA server, or collect one DataLog from the memory card, and attach it in Seal. Check the tag’s symbolic name, value, timestamp and status against what the automation team reads on the controller at the same time.

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. 1Siemens: CPU 1513-1 PN equipment manual.
  2. 2Siemens: S7-1500 web server function manual, 12/2014.
  3. 3Siemens: OPC UA webinar, August 2020.