How to display safety critical information without overwhelming the operators?

At the age of digitalization, software automation engineers have a stronger responsibility to NOT implement front-ends that are overwhelming for the operators. "An alarm message can be seen as a short telegram sent to the operator to inform him of a fault".

Such a message should be - as compact - as visual - as clear - as intelligent - as possible. RIVOPS is an alarm page for the control room. It shall grasp the attention of the operator for just a few seconds (<3s) and send its telegram message across the HMI displays of the control room. RIVOPS is nothing else than a smart OPC Alarm Client, it renders a dynamic representation for each fault scenario. That image is computed in real-time for any given alarm list. It contains an alarm banner compliant with the #OPCUA, #EMUA191, ISA 18.2 specifications. For those who believe that showing an image tells more than a hundred words, follow that link.

RIVOPS OPC 3D SCADA.jpg

EATOPS builds control rooms equipped with an Alarm Summary overlaying Alarm Banners on the top of a 3D representation of the plant. The RIVOPS technology is able to display an OPC Alarm Message from an automatic-fault-scenario function running on the PLC. (compatible with #Siemens 400, 1200 and 1500 series).

Smart use of scripting languages

AutoGen-PLC-Logic.png

Whereas the Industry is facing a digitalisation of its plants, EATOPS makes use of scripting languages to produce a robust PLC logic and build virtual piplines that control physical parts.

The code is consistent across multiple installations and highly reliable thus produce by a script rather than a human hand which could make mistakes.

AutoGen serves an even broader ambition at embedding articifical intelligence ruling into the PLC code and publishing industrial OPC UA data over the internet (IIOT).

#3DSCADA for #AutomationStudio

The power of standardization. The acquisition of B&R Automation by ABB did not come as a surprise. B&R Automation Studio suite is following the OPC UA standard. This decision to implement the OPC communication protocol at the very lowest level of their PLC & HMI compenents surely played a part in their recent buy-out by the ABB Group. EATOPS has been following the same approach and complies with OPC Unified Architecture for the same practical reasons. An open-standard between the PLC and the HMI leads to a stronger architecture leaving the PLC is its role of 'process logic controller' taking care of the logic, and the HMI in its role of 'human machine interface'. The HMI remains a slave of the PLC which means that several HMI modules can inherit the alarm & sensor values directly from the PLC.

The #RIVOPS overview panels are fully compatible with the #AutomationStudio Suite. Some more #3DSCADA overview panels will come-out from EATOPS production line during the year following that same OPC implementation.

PLC-OPCUA-RIVOPS.png

AutoGenforOPC

Automatic generation of your OPC communication tables is just one click away. AutoGenforOPC is a script written in Python which parses your IO-list and automatically generates your OPC sever configuration files. It saves you of a day of work, without mistakes! 

AutoGen is compatible with Siemens Step7, Automation Studio 4.2, CodeSys, & RIVOPS. OPC EATOPS products are compliant with OPC stacks v1.3.1340.

Milestone -- Unified Architecture - OPC UA

RIVOPS supports OPC UA (unified architecture, OPC Stack 1.3.340) for both DataAccess (DA) and AlarmEvent (AE). The new standard is compliant with the ISA 18.2 requirements on dynamic alarm arouping, alarm acknowledgment, display of advisory messages and alarm shelving mecanisms. EATOPS develops its expertise in using the standard to anticipate the growing demand related to Industry 4.0 and Industrial Internet of Things.

AlarmGroupCode.jpg