Integrations

Siemens S7 to Snowflake, without a script.

Read the PLC's data blocks with MaestroHub's S7 connector, give every value a name, unit and quality, and land the rows in Snowflake. No OPC server in between, and nothing lost or duplicated when the link drops.

The flow

One value, from the machine to Snowflake. Illustrative.

Siemens S7PLC protocolDB20.DBD0

MaestroHub

Line 2 good parts · 1,240 · Good

named, unit, quality
origin stamped
buffered on disk

Snowflakecloud data warehousePRODUCTION.COUNTS

Why do it with MaestroHub

More than a pipe from Siemens S7 to Snowflake.

Production counts next to ERP

Line counts land in the same warehouse as orders and costs, ready to join.

No double counting after an outage

Replays after a network drop are recognised, so counts in Snowflake stay right.

One tool for every PLC

S7, Allen-Bradley, Modbus and OPC UA sources all arrive in the same shape.

What lands in Snowflake

An example. You choose the fields in the pipeline.

ts	asset	signal	value	unit	quality
2026-10-03 06:00:01	line2	good_parts	1240	count	good

Set it up in three steps

1
Connect Siemens S7
Add the S7 connection with the PLC's address, rack and slot, then create read functions for the data blocks you need.
2
Give the values meaning
Map each value to a topic in the namespace with its name, unit and schema. Quality and origin are stamped on every value.
3
Deliver to Snowflake
Add a Snowflake output to the pipeline and pick the table; with streaming, rows land within seconds.

Before you start

What each side needs, from the connector documentation.

Siemens S7

Network reach to the PLC on port 102 (ISO-on-TCP), entered as host:port.
The CPU rack and slot from the PLC hardware configuration. Common combinations are rack 0 with slot 1 or slot 2.
The session password, only if password protection is enabled in the PLC security settings. Maximum 8 characters.
The DB numbers, byte offsets and data types of the values you need, for example from the TIA Portal project.

Example settings

PLC Address: 192.168.1.100:102
Rack: 0
Slot: 1
Connection Type: Programming Device (PG)
Request Timeout (ms): 10000
Idle Timeout (ms): 30000

Siemens S7 connector documentation

Snowflake

An RSA key pair. The public key is set on the Snowflake user with ALTER USER ... SET RSA_PUBLIC_KEY, and the private key goes into MaestroHub.
A Snowflake user whose default role has USAGE on the database and schema and INSERT (and SELECT) on the target tables. The connector always uses the user's default role.
Extra grants only for the features you use: OPERATE on a custom pipe, CREATE TABLE on the schema, EVOLVE SCHEMA on an existing table.
The account identifier, for example myorg-myaccount or xy12345.us-east-1, plus the database and schema.

Example settings

Account Identifier: <your-org>-<your-account>
Database: FACTORY
Schema: RAW
User: MAESTROHUB_SVC
Table (Stream Rows): TELEMETRY
Rows (Stream Rows): ((data))

Snowflake connector documentation

Things to know

Pitfalls and limits the documentation calls out, so they don't surprise you on site.

Siemens S7

Process Inputs (I) are read-only and writes to them are rejected. CHAR, STRING, WSTRING and the time and counter types can be written to DBs only, not to memory areas.
For STRING and WSTRING, Size must be the declared maximum length plus the 2-byte S7 header. STRING[20] in TIA Portal is 22 bytes.
A passing Test All checks the configuration only. Submit can still fail if the PLC rejects it, for example when the DB does not exist or the address is out of range on that PLC.

Limits

Write functions handle one value each. Only reads group several data points into one function.
TIMER, COUNTER, TIME_OF_DAY and DATE_AND_TIME can be read but not written.

Snowflake

Send epoch timestamps as strings or as ISO-8601 text. Epoch milliseconds sent as a JSON number are read as seconds and stored around the year 57,700 with no error.
A timestamp without a time zone is read in the account time zone (America/Los_Angeles by default) for TIMESTAMP_LTZ and TIMESTAMP_TZ columns. Send the zone, for example 2026-09-23T08:00:00Z.
Snowflake skips rows that do not fit the table. Turn on ERROR_LOGGING on the table to keep them, and turn on Wait for Commit when a rejected row must fail the call.

Limits

Snowflake Streaming only loads rows. To query or run DML and DDL, use the Snowflake SQL connector, which runs through a warehouse.
A single row larger than 4 MB after compression is refused, and each connection writes to one database and schema. Use a second connection for another schema.

What teams use it for

Order and output reconciliation

Planned versus produced, per order and shift.

Scrap and yield reporting

Good and rejected parts per line, with the reason codes from the PLC.

Executive dashboards

Plant KPIs in the BI tool the business already uses on Snowflake.

Ways to connect Siemens S7 to Snowflake

In general terms. Check any specific product for its own details.

Compare a custom script, a flow tool, a cloud vendor's edge service and MaestroHub

Swipe sideways to see every column

	A custom script	A flow tool	A cloud vendor's edge service	MaestroHub
Talks Siemens S7	A library you choose	Community plug-ins	Depends on the vendor	Built in, one of 90+ connectors
Names, units and schema	You write it	You build it	Partly, in the vendor's model	One governed namespace
Quality on every value	You write it	You build it	Depends on the vendor	Built in, carried through calculations
Where each value came from	You write it	You build it	Depends on the vendor	Stamped on every value
Survives a network outage	You build it	You build it	Usually, to that vendor's cloud	On disk, per destination, in order
Several destinations at once	One script each	Yes, flow by flow	Mostly that vendor's cloud	Any mix, each with its own buffer
Permissions and audit	You build it	You build it	Cloud account permissions	Roles, single sign-on, audit trail
AI agents can use the data	You build it	You build it	Depends on the vendor	Through the MCP server

Questions

How do I send Siemens S7 PLC data to Snowflake?

Do I need to write code to connect Siemens S7 to Snowflake?

No. You configure the Siemens S7 connection and the Snowflake output in MaestroHub and join them with a pipeline. Transformations can be added where you need them.

Where does MaestroHub run for this?

On your own infrastructure next to the machines: an edge box, a virtual machine or Kubernetes. Only the rows you choose leave the plant for Snowflake.

Why not just write a script for Siemens S7 to Snowflake?

A script works on day one. The cost comes later: decoding and naming values, handling bad quality, buffering through outages, keeping credentials safe, and doing it again for the next machine and the next destination. MaestroHub does those once, for every connector.

What else can Siemens S7 data go to?

More than 90 connectors are included in every edition, among them historians, databases, cloud warehouses, message brokers and business systems, so the same values can feed several destinations at once.

Other integrations

All integrations