IDX 8 Data Exchange and Alarms and Events

-
Data Exchange has been the core of the IDX suite since its first inception in 1995. Data Exchange allows real-time tag data to be shared between various, usually incompatible, systems with IDX being the intermediary that converts the data between the systems.  Up to IDX 7, IDX was exclusively a Data Exchange engine with a reliable industry track record. IDX 7 still exists today, and provides the bulk to the Data Exchange requirements to service our clients’ needs. This includes special connectors such as the Gensym G2 Expert Sytem bridge, as well as more common OPC DA, MODBUS, and OPC DA tunnelling via TCP.
IDX 8 introduces its own implementation of the Data Exchange engine. The intention is to mirror the functionality of common IDX 7 connectors, such as the OPC DA client, in native IDX 8 connectors to provide general data exchange ability to service functionality such as Alerting (more below). However, in the near future, the IDX 7 runtime will become a “proxy” data exchange engine of the IDX 8 framework, so that all the existing IDX 7 connectors can be configured and used from within IDX 8 without the need for the separate IDX 7 configuration tool and database. 

One of the more exciting new aspects of IDX 8 Data Exchange is that it couples to the IDX 8 Alarms and Events modules, which allows users to setup SMS and/or Email notifications based on configurable, hierarchical alarm logic. The standard alarm types are available, such as value, limit and heartbeat alarms. Two alarms types in particular provide additional useful functionality. The Logic alarm is used to aggregate alarms up the logic tree and this allows one to setup alarm configurations that do not send emails and SMS unnecessarily. Customised logic can be setup so that the logic alarm only enters the alarm state if its child alarm states match those specified.


Configuring a Logic alarm that analyses the state of a Heartbeat and Value/Condition alarm.

The Snapshot alarm allows you to generate a value snapshot of one or more Alarm Event items, such as Data Exchange tags, at the time the alarm is triggered in the alarm tree.  You can format the snapshot message to your requirements with custom text so that the data snapshot is presented as required in an Email or SMS message. At the time an alarm occurs, there is also the option to perform an action, which includes running a program, controlling a Windows service or writing a value into an Alarm Element such as a Data Exchange tag. We have used the service control action in a number of projects where alarms are set to monitor the health of other real-time data interfaces that happen to stop working once in a while. The Alarm action allows us to restart the interface services to get the data moving again without any user intervention.

Alarms can also be setup with acknowledgement escalation where, if an alarm is not acknowleged by any contacts in a group, the alarm is escalated to the next group. All alarms and alarm notifications and acknowledgements are logged, providing a useful event audit trail.

Popular posts from this blog

Common pitfalls when installing a Modbus RS485 network on site

-
Image
Last week IDX were called to site at  a large commercial residence building in Pretoria, South Africa. Where our  client was implementing an IoT solution for remote monitoring and control of various HVAC and power systems in the building.  The control system the SI chose in this case was a Modbus enabled Industrial Micro PC called the Revolution PI. The client had Modbus sensors connected to boilers, air conditioning systems, ventilation systems and power meters. The Modbus  communications between the controller and the sensors were intermittently failing due to various installation and implementation faults: 1. Earthing and Shielding Within any fieldbus communication installation, one of the requirements to ensure uninterrupted operation is to implement adequate grounding and shielding techniques. Effective grounding and Shielding help to prevent electrostatic and electromagnetic pickup, which can lead to failed communications. Some of the shielding and grounding req
Read more

IEC61850 to Modbus TCP/IP, EtherNet/IP, M-bus, PROFINET or PROFIBUS

-
Image
The SG-gateway family is a current leading Smart Grid application solution, acting as a remote terminal unit for the energy market. The SG-gateway enables the remote control and management of electrical equipment in power grids, controlling and monitoring assets, processes and installations in the field. Networking and interfacing between various fieldbuses and Industrial Ethernet protocols is where this gateway shines, allowing cross interfacing between: IEC61850 (Client/Server) IEC60870-5-104 (Client/Server) Modbus TCP (Client/Server) Modbus RTU (Master/Slave) Various Serial RS232, RS485 and RS232 PROFIBUS PROFINET EtherNet/IP Here are some application examples: Transmission can also be made available via Ethernet or 3G VPN connection into your server. The SG-Gateways sports an easy web based configuration tool using a standard browser, configuring with a simple drag and drop method. Choose the right SG-gateway to suit your requ
Read more

IDX 8 Tag Manager - Managing the unmanagable?

-
Image
Tag management of real-time data systems can prove challenging. As an industrial IT company we frequently come across the problem where tags need to be migrated from one system to another or where tags need to be synchronised and maintained between systems including historians. Generally, this ends up being a manual process, often involving Excel and much diligence and patience of the maintainer’s behalf. IDX Unifig was the first incarnation of a tool we designed with the aim to simplify the migration and management of tags between systems. The tool worked, but with as with most first editions of software tools, we could see the need for improvement and refinement of the approach used. Thus Tag Manager was born, and has become the key stone in the IDX 8 software suite. All other IDX 8 modules, such as Data Exchange, Alarms and Events and the Historian use Tag Manager to store and reference tags. The comparison result we like to see - no changes.   Tag Manager employs a plug
Read more