← All vendors

Tier 1 · Full-solution provider · France

Schneider Electric

Strong where time is most regulated — process industries, energy management, building automation. Schneider's audit footprint is unusually wide because it spans three layers at once: the Modicon field estate, the Aveva/Wonderware supervision above it, and the Modbus protocol that carries timestamps across all of them.

  • PLC · Modicon M580 / M340
  • SCADA · Aveva System Platform
  • DCS · Process Expert (Foxboro)
  • Ecosystem · EcoStruxure
S1

Controller families

Modicon M580 / M340
The flagship ePAC and the mid-range PAC — Ethernet-native control for process and hybrid industries. Current platforms with vendor support: audit is revision, runtime, and the time services compiled into the application.
MachineStruxure (M221–M262)
The machine-builder ladder from entry-level M221 to motion-capable M241/M251 to the IIoT-native M262 with MQTT built in. MQTT on the controller means the cloud backend inherits its clock — which means the backend gets audited too.
Quantum
Legacy high-end, still widely used in critical process applications — Schneider's most exact parallel to the PLC-5 situation: a large estate of dependable machines with no forward path. Replacement or defended workarounds, chosen early.
Premium & TSX Micro
Older platforms still running lines worldwide. Where they touch Modbus time fields or local event logs, they surface in the register as silent-failure candidates: they will keep running after 2038 — with wrong history.
S2

SCADA, DCS & the software-defined layer

Aveva / Wonderware
Schneider's acquisition of Aveva made InTouch and System Platform its premier SCADA/DCS stack — and it remains the most widely deployed third-party supervision on earth. The historian write path, ODBC layers, and report timestamps all carry the overflow question into multi-vendor estates that never chose Schneider at all.
Citect & Vijeo Designer
Legacy SCADA/HMI platforms still supervising real assets. Their versions, hot-fix levels, and time zones rulesets are recorded per site; the rollover test runs on the replica, not the alarm screen.
Process Expert / Foxboro
The large-scale process DCS lineage. Batch records, electronic signatures, and audit trails here are regulated data — the timekeeping proof goes into the FDA 21 CFR Part 11 evidence pack, not just the engineering file.
EcoStruxure Automation Expert
The software-defined, IEC 61499 platform — containerized control on industrial PCs. A 64-bit-era foundation with one catch: portability means one vendor's timing semantics now drive another's equipment. We test the pair, not the parts.
S3

Modbus, buildings & the long tail

Modbus belongs to the open specification that Schneider's PLC lineage grew up with, and it is one of the SCADA protocols whose older implementations carry time fields. On a Schneider estate the protocol audit and the controller audit are the same conversation — which is convenient. Where Modbus/TCP is the plant's lingua franca, every device that answers a timestamped request rides the same register.

Building automation is the long tail nobody budgets for: HVAC units, access panels, energy meters — thousands of embedded devices per campus, deployed with a fifteen-year outlook and no vendor portal. They behave like the water pumps and traffic signals in our embedded chapter, because they are the same thing wearing a different badge.

Field note The most common Schneider finding: an InTouch HMI faithfully displaying 1901 timestamps from a perfectly healthy PLC — because the ODBC driver between them was compiled when Windows XP was new. The controller was never the problem. The conversion layer was.

Audit the whole Schneider stack — Modicon to Aveva.

Field, supervision, protocol, and the building estate below the plant fence line: one register, one time-warp test plan, one evidence pack.