Electronic Flow Measurement Modules for Ignition

Electronic Flow Measurement (EFM) is the cash register for the Oil & Gas industry for measuring hydrocarbons  to calculate production and revenue. Major industry flow computer devices gather the EFM data  but represent it very differently within their  proprietary protocols making the process of extracting this data and sharing its true value throughout the enterprise a challenge.  Cirrus Link has developed a range of EFM module products for the Ignition platform  to extract this EFM data using the efficient open standard MQTT protocol to solve this problem and provide the following benefits. 

Benefits: 

  • Provides faster SCADA data with less bandwidth utilization
  • Supports Alarms, Events, Configs, Minute History, Periodic History and Daily History records
  • Connects EFM data to Flow-Cal transaction queues
  • Store and forward available at the Edge eliminating lost data on comms outage
  • Create tables for Event, Alarm and History data in Ignition supported databases
  • Guaranteed records with hash-based message authentication code
  • Data is time-stamped at source for more accurate leak detection & batch tracking
EFM

EFM Emerson ROC Module:

This module communicates with Emerson ROC and ROC Plus flow computers, formerly Fisher ROC. This includes, but not limited to, FloBoss 100 Series and ROC 800 series. By using the EFM Emerson ROC Module on the Ignition platform the Emerson ROC EFM data is polled and made available as tags within the OPC browser.

EFM Export Module

EFM Export Module:

The EFM Export module receives EFM information via MQTT that includes the Alarms, Events, Configuration and QTR records from flow computers accessed by the Cirrus Link EFM protocol drivers.

MQTT Recorder 173 by 200 Icon

MQTT Recorder Module:

The MQTT Recorder Module receives record objects from the MQTT Engine Module that have arrived via MQTT/Sparkplug. Utilizing a database that is configured within Ignition, the MQTT Recorder Module automatically generates database tables and populates the rows within the tables with records as they are received. Records represent a collection of tags, fields, and key-value pairs. They are especially useful for receiving records from a flow computer for its events, alarms, and history data.

try this

Like all Ignition modules, the IIoT modules can be installed, removed, and upgraded without impacting operations or affecting the rest of the system.

The MQTT Modules by Cirrus Link Solutions are available for download at https://inductiveautomation.com/downloads/ignition 

For tutorials and support, please go here.

EFM Emerson ROC Module

The EFM Emerson ROC module is a protocol driver for the Ignition OPC UA module, by Inductive Automation. It communicates with Emerson ROC and ROC Plus flow computers, formerly Fisher ROC. This includes, but not limited to, FloBoss 100 Series and ROC 800 series. By using the EFM Emerson ROC Module on the Ignition platform the Emerson ROC EFM data is polled and made available as tags within the OPC browser.

EFM Emerson ROC Module uses T,L,P addresses to access data from standard and custom applications running on the flow computer. With the ability to load custom TLP libraries into the protocol module, custom configurations can be created and quickly replicated across entire populations of deployed devices.

The EFM Emerson ROC Module also polls and gathers Alarm, Event and QTR (Quantitative Transaction Records) records for onward transmission to the enterprise or other flow calculation services.

 

Using MQTT with the EFM Emerson ROC Module

By coupling the EFM Emerson Protocol with the power of the MQTT modules by Cirrus Link the real power of this solution can be realized. By installing Ignition or Ignition Edge with the EFM Emerson ROC polling is distributed to the edge and increase bandwidth utilization over radio or other IP networks providing increased response times of SCADA data. Please find below the typical architecture solutions when using the EFM Emerson ROC Module.

 

Using the highly efficient MQTT protocol only event changes are transmitted to the host. The benefit this gives is that the real time SCADA data is transmitted on change, while continuously monitoring for Alarms, Events and QTR records to be sent only when available.

For years complex sets of registers have been used in legacy protocols to send data that is essentially a record of information. These methods are prone to problems with keeping the data together and require a lot of polling from a SCADA host over the network to monitor for new events. With the EFM Emerson Protocol module data such as Alarms, Events and QTR’s are extracted from the flow computer and put into an MQTT Record as an immutable object with a time stamp and checksum then sent straight to a database table at the host.  For delivering MQTT Records, the MQTT Recorder module is required.  Please go here for more information on the MQTT Recorder Module.

Benefits of EFM Emerson Protocol Module when used with MQTT Modules

  • Supports ROC and ROC Plus protocols for SCADA TLPs and all EFM data
  • Runs on Ignition and Ignition Edge Platform
  • Can access any TLP including from User Programs (e.g. Vinson Engineering)
  • Supports Alarms, Events, Configs, Minute History, Periodic History and Daily History records

To find support and tutorials for the EFM Emerson ROC module, please go here.

EFM Export Module

The EFM Export Module provides EFM data connectivity to Flow-Cal.  The EFM Export module receives EFM information via MQTT that includes the Alarms, Events, Configuration and QTR records from flow computers accessed by the Cirrus Link EFM protocol drivers.  This data is passed and put in the proper formation and placed into transaction queues for automatic ingest and analysis by Flow-Cal, the industry leader in gas and liquid measurement software application.  The process can be seen by the diagram below.

End-to-End Solution

The EFM Export is just one part for of the solution. For years data has been created in flow computers that represent a record of information with the limitations of register-based communication protocols.  This information has always been clumsily handled as consecutive blocks of registers. This method runs the risk of not keeping all the data together as a record event, when a partial subset of the registers get overwritten with a newer set of information. Today with the power of MQTT and the Cirrus Link EFM modules these records of data are published, on event, as an immutable record and fed directly into database tables for flow measurement applications. In addition, this record is time stamped and carry a cryptographic hash key that will guarantee that the entire contents of the record are unedited from source.

When using Cirrus Link EFM modules the following benefits are offered:

  • Connects EFM data to Flow-Cal transaction queues
  • Supports Alarms, Events, Configs, Minute History, Periodic History and Daily History records
  • Supports store and forward at the Edge eliminating lost data on comms outage

Faster Scada data

Traditionally EFM data is polled from the SCADA host at the center of the network, with the need to at least gather hourly ticket data along with events, alarms and any config changes many networks are stretched to breaking point.  Any interruptions in the network soon put all the scheduled polling being and sometimes they can never catch up.  By using the EFM Modules by Cirrus Link the polling is pushed out to the Edge of the network allowing data to be monitored faster and only sent on change using MQTT/Sparkplug reducing the network utilization by up to 80%.  This allows real time data for SCADA, such as Pressure, Temperature and flow to be sent in near real time as they change.

Store and forward

In the event there is a network outage, the MQTT Transmission module will buffer all the data limited only by local storage and then once the network is restored, pace the backfill of the historic data while keeping the live data fresh and top priority.  This eliminates manual local downloads and drive time for employees increasing profitability and lower safety risks.

The find support and tutorials for the EFM Modules, please go here!

MQTT Recorder Module

For years data has been created in PLC’s and RTU’s that represent a record of information such as a quantitative transaction record (QTR) from a flow computer. With the limitations of register based communication protocols this information has always been clumsily handled as consecutive blocks of registers. This method runs the risk of not keeping all the data together as a record event, when a partial subset of the registers get overwritten with a newer set of information. Today with the power of MQTT these records of data can be published, on event, as an immutable record which automatically builds and populates a table within a database. In addition this record can be time stamped and carry a SHA-256 Hash key that will guarantee that the entire contents of the record are unedited from source. The MQTT Recorder module receives these records and first automatically builds the database table, and then populates each record into the table as it is received.

Examples of the records are:

  • Oil & Gas –  EFM Quantitative Transaction Records (QTR’s), EFM Alarms, EFM Events, P’cards for Pump of Controllers
  • Pharmaceutical –  Batch records for drug manufacture
  • Transportation Industry-  Locomotive engine events

The diagram below shows an example of the record flow of data for the MQTT Recorder with the EFM Emerson ROC Module.  The EFM Emerson ROC module polls locally on Ignition or Ignition Edge Platform for the  events, alarms and history records on the flow computer.  MQTT transmission publishes the record to the MQTT Server. MQTT Engine on the Primary Ignition Gateway subscribes to the MQTT Server to receive the record.  The MQTT Recorder Module works in unison with the MQTT Engine module to receive the record and puts the record data into table within the SQL database.

Benefits

The MQTT Recorder offer the following benefits:

  • Creates tables for any record formatted data in Ignition supported databases
  • Guaranteed records with hash-based message authentication code
  • Supports store and forward at the Edge eliminating lost data on coms outage

The find support and tutorials for the MQTT Modules, please go here!