Architecture and Licensing of High-Precision Sequence of Events in SIMATIC PCS 7 and WinCC

A high-precision Sequence of Events (SOE) station with 1-millisecond time stamping in SIMATIC PCS 7 does not require a specialized standalone software package; it is fully integrated into standard SIMATIC PCS 7 OS / WinCC software. SOE event recording operates across three integrated layers: time-stamping digital input modules (e.g. ET 200M IM 153-2 with 6ES7321-7BH01-0AB0 or ET 200SP HA) stamp contact transitions directly in hardware, AS system blocks (IMDRV_TS and EventTs) transmit buffered events via Alarm_8P, and a standard WinCC OS Single Station or Server logs the chronological sequence into the standard WinCC Alarm Logging database.

Functional Overview of Sequence of Events (SOE) Architecture

In power generation stations, electrical substations, and chemical plants, major process trips involve dozens of binary contacts triggering within milliseconds (e.g., turbine trip, boiler flameout, generator breaker open, emergency stop). Standard SCADA polling cycles (100 ms to 1 s) cannot determine the root cause initiating event.

A Sequence of Events (SOE) system records binary state transitions with 1-millisecond resolution directly at the field input terminal, maintaining an audit-proof chronological log to pinpoint the exact sequence of trips.

Hardware-Level Time Stamping (1 ms Resolution) in Distributed I/O

High-precision time stamping is executed at the distributed I/O hardware level:

Time-Stamping Interface Module: The distributed station interface (e.g. ET 200M IM 153-2 High Feature 6ES7153-2BA10-0XB0 or ET 200SP HA IM 155-6 PN HA) receives high-precision clock synchronization frames from the plant master clock over Industrial Ethernet.
Specialized Digital Input Modules: Fast digital input modules (such as 6ES7321-7BH01-0AB0 / SM 321, 16 DI x 24 VDC with process interrupt) capture contact transitions and immediately stamp the event with an internal 1 ms hardware clock.
Buffer Memory: The module buffers up to several hundred timestamped events in local non-volatile memory, preventing loss of trip records during communication network bursts.

Controller Driver Blocks: IMDRV_TS and EventTs

The controller layer processes buffered hardware events without CPU jitter:

The driver block IMDRV_TS (FB 1215) continuously reads timestamped event buffers from the IM 153-2 interface module.
Technological blocks or the message generator EventTs (FB 1216) receive the timestamped bits.
EventTs forwards the messages to WinCC using standard Alarm_8P system calls, carrying the original hardware timestamp rather than the controller execution time.

WinCC OS Alarm Logging and Historical Archiving Integration

On the Operator Station (OS):

SOE events arrive in the standard WinCC AlarmControl incoming list and archive list.
The message list sorts events by millisecond timestamps, highlighting the 'first-up' trip contact.
Long-term retention is managed by standard WinCC Process Historian or Information Server without requiring proprietary third-party SOE software packages.

Procurement and Software Package Schedule for SOE Stations

The table below details software and hardware requirements for a PCS 7 SOE station:

| System Component | Siemens Order Number (MLFB) | Role in SOE System | Mandatory / Optional |
|---|---|---|---|---|
| IM 153-2 High Feature | 6ES7153-2BA10-0XB0 | Distributed I/O Time Sync master | Mandatory (for ET 200M) |
| SM 321 DI 16x24VDC (TS)| 6ES7321-7BH01-0AB0 | Hardware 1 ms contact time stamping | Mandatory (for 1 ms SOE) |
| S7-400 / CPU 410-5H | 6ES7410-5HX08-0AB0 | AS Controller running IMDRV_TS & EventTs| Mandatory |
| OS Software Single Station| 6ES7658-2AA08-0YA0 | WinCC Runtime & Alarm Logging engine | Mandatory for standalone SOE |
| PCS 7 Process Historian| 6ES7652-7AX58-2YA0 | Long-term multi-year SOE event archiving| Optional (for utility archives) |

Verification

Verify 1-millisecond SOE time stamping in runtime:

Connect two physical contacts to channels 0 and 1 on the 6ES7321-7BH01-0AB0 module.
Trigger both contacts with a known 5-millisecond delay using a test pulse generator.
In WinCC OS Runtime, open the Alarm Logging Archive List.
Confirm that both events appear as distinct alarm entries with identical date and time up to seconds, but with differing millisecond fields (e.g. .102 vs .107).
Verify that event descriptions report 'Came' and 'Went' states accurately.

Limitations and Operational Precautions

Observe the following safeguards when engineering SOE systems:

Plant-Wide Clock Synchronization: A central GPS/NTP grandmaster clock (such as SICLOCK TC 400 2XV9450-1AR23) must synchronize controllers and distributed I/O stations to guarantee sub-millisecond accuracy across separate racks.
Module Filter Delay: Sizing input filter delay times (e.g. 3 ms vs 0.5 ms) must account for field switch contact chatter without masking fast trip transitions.
Commercial Procurement Guardrail: Do not purchase proprietary third-party SOE loggers without evaluating PCS 7 native capabilities; standard WinCC OS licenses fully support high-precision time stamping.

Engineer FAQ

Do I need to buy a special WinCC SOE option package to record events?

No. High-precision time stamping is built into standard SIMATIC PCS 7 WinCC OS software. Events stamped by distributed I/O hardware are processed natively by WinCC Alarm Logging without optional packages.

Can an SOE station be configured standalone without PCS 7?

While standalone data loggers exist, in a Siemens environment SOE requires STEP 7 HW Config to parameterize the time-stamping modules and an S7 CPU to execute IMDRV_TS driver blocks.