Managing and Filtering Wire-Break Alarms on Analog Channels in SIMATIC PCS 7 - Routing to Maintenance

To prevent hardware wire-break, under-range, and over-range diagnostic alarms on analog channels from flooding the operator summary banner in SIMATIC PCS 7—without hiding, shelving, or disabling safety-critical detection—engineers should route hardware diagnostic messages to dedicated maintenance views using WinCC Message Classes and AlarmControl filtering. In PCS 7 (APL and Basis Library), hardware faults generated by channel drivers (Pcs7AnIn, Bad = 1) and diagnostic blocks (MOD_D1) are categorized under the Control System Fault (CSF) message class, separate from process limit alarms. By filtering out CSF messages from the main operator summary display (@AlarmNew.PDL) and creating a dedicated Maintenance Alarm View (or deploying the PCS 7 Maintenance Station), wire-break alarms are directed exclusively to instrumentation technicians while keeping the operator banner focused purely on process alarms.

Alarm Flooding Challenges: Process Alarms vs Hardware Diagnostics

In continuous chemical, refining, and manufacturing facilities, alarm flooding during unit startup or field instrument maintenance is a primary contributor to operator fatigue and process safety incidents. When an instrument technician disconnects a 4-20mA sensor cable for routine calibration, the ET 200 analog card detects an open circuit (< 3.6 mA), the module driver asserts a diagnostic interrupt (OB82), and the channel driver (Pcs7AnIn) trips Bad = 1.

If hardware diagnostics and process alarms share a single, unfiltered alarm list, dozens of 'Wire Break' and 'Underflow' messages clutter the top-level operator banner. Operators who are responsible for process throughput and burner management are distracted by low-level electrical faults that can only be resolved by electrical and instrumentation (E&I) technicians. The ISA-18.2 and EEMUA 191 alarm management standards mandate segregating instrumentation maintenance alerts from process operator alarms.

Message Classes in PCS 7: Segregating Process Limits from Control System Faults

SIMATIC PCS 7 implements native message classification across all technological and driver blocks:

Message TypeOriginating BlockDefault Message ClassTarget AudienceRecommended Display LocationProcess Limit AlarmsMonAnL, PIDConLAlarm - High / Warning - HighProcess OperatorsTop Banner (@AlarmNew.PDL), Overview AreaProcess InterlocksInterlock, PermitProcess Message / InterlockProcess OperatorsFaceplate, Process Alarm ListWire Break / Out of RangePcs7AnIn (Bad = 1)Control System Fault (CSF)E&I MaintenanceMaintenance Dashboard, Asset ManagementRack / Module FailureMOD_D1, RACKSystem Message (AS / Diagnostics)Automation TechniciansMaintenance Station (MS), Diagnostic View

Because channel drivers explicitly classify wire breaks as Control System Faults (CSF) rather than process limit alarms, filtering by Message Class achieves complete segregation without suppressing the diagnostic event.

Configuring WinCC AlarmControl Filters and Maintenance Dashboards

To implement structured alarm routing in WinCC OS Runtime, execute the following configuration steps:

1. Configure Operator Summary Filter (Exclude CSF):
- Open WinCC Explorer -> Graphics Designer. Open @AlarmNew.PDL (or the operational alarm banner).
- Double-click the WinCC AlarmControl object. Navigate to the Message Selection or Filter tab.
- Under Message Classes, check all process classes: Alarm - High, Alarm - Low, Warning - High, Warning - Low.
- Uncheck: Control System Fault (CSF) and System Message (AS).
- Save @AlarmNew.PDL.

2. Create Dedicated Maintenance Alarm View:
- Create a new graphic picture (e.g., Maintenance_Alarms.PDL) or add a tab to the alarm window.
- Insert a WinCC AlarmControl object.
- In its Filter configuration, invert the selection: Check only Control System Fault and System Message.
- Link this picture to a navigation button accessible to maintenance personnel.

3. Configure Channel Driver Flutter Suppression (FlutEn):
- In CFC, open the properties of the Pcs7AnIn channel drivers.
- Enable flutter suppression (FlutEn = 1) and parameterize FlutTm (e.g., 3.0s) and BadDelay (e.g., 2.0s) to prevent loose wire connections or electrical noise from generating dozens of rapid chatter alarms.

Verification

Verify alarm routing and filtering behavior using these testing steps:

Wire Break Simulation: Disconnect the signal wire on a test analog channel in an ET 200 station. Verify that the module LED indicates a channel fault (SF).
Operator Banner Audit: Inspect the main operator single-line alarm banner. Confirm that the 'Wire Break' message does not appear in the operator's primary alarm summary.
Maintenance View Audit: Open Maintenance_Alarms.PDL (or the Maintenance Station). Confirm that the 'Wire Break' / Control System Fault alarm appears immediately with precise timestamp, card slot, and channel tag ID.
Process Alarm Integrity: Inject a valid 4-20mA signal exceeding the high-high threshold. Confirm that the process alarm renders instantly in the operator summary banner.

Limitations and Operational Precautions

When filtering hardware alarms, observe these critical operational safeguards:

Never Disable Wire-Break Detection: Do not disable wire-break monitoring in HW Config to eliminate alarms; doing so causes severed wires to read raw zero, which could be misinterpreted as a legitimate process zero, causing catastrophic control loop over-drive.
Technological Block Indication: Even when filtered from the top alarm banner, technological faceplates (MonAnL, PIDConL) will still display the yellow Control System Fault (CSF) icon, informing the operator that the sensor is faulted.
Maintenance Station Integration: For large facilities with thousands of I/O points, deploying the dedicated SIMATIC PCS 7 Maintenance Station (MS) is the Siemens recommended standard for centralized asset health tracking.

Engineer FAQ

Does filtering out CSF hide alarms permanently?

No. Filtering simply changes which WinCC AlarmControl window displays the message. The wire-break alarm is still fully recorded in the historical SQL Alarm Logging database and displayed on maintenance screens.

Can I delay the wire-break alarm to avoid brief sensor bounces?

Yes. The APL channel driver Pcs7AnIn features the BadDelay parameter. Setting BadDelay = 3.0 ensures that wire breaks persisting for less than 3 seconds are suppressed from generating alarms.

What is the difference between shelving an alarm and filtering it?

Shelving temporarily suppresses an alarm for a fixed period (e.g., 2 hours during transmitter maintenance). Filtering permanently routes specific alarm classes to different user groups (operators vs maintenance) based on plant responsibility.