Is SCADA your enterprise data speed bump?

The steep growth of distributed energy resources has sparked a correspondingly large growth of connected grid systems, devices, assets and Operational Technology (OT) data. Business stakeholders and Information Technology (IT) applications have a vital need for real-time access to this OT data.

Unfortunately, much of this data is not readily accessible to the enterprise IT systems because it is metered out through legacy SCADA systems that were never designed for secure real-time bidirectional publishing and control of data. In fact, SCADA systems are a major speed bump in integrating OT systems into the enterprise information superhighway.

SCADA — Supervisory Control and Data Acquisition technologies — have been around for over 40 years. The basic structure and function as applied in the electric utility industry is largely unchanged. During the same time, the industry has seen the introduction of numerous technological changes in new devices and architectures. For many power companies, this creates constraints in the ability to integrate new OT applications and to integrate OT applications into IT applications.  

Early SCADA ran on back-office centralized mainframes and closed-ended systems, with dedicated point-to-point connectivity between field devices and the back office. As back office systems expanded from these dedicated mainframes to interconnected systems, back-office data interaction improved, resulting in greater optimization of the operation of fielded assets.

Improved situational awareness

The result for the industry has been enormous — quicker information flow resulting in improved situational awareness (within OT systems), with faster restoration times and reduced impact to customers and service personnel. The challenge for these integrations is that they relied on proprietary protocols and implementation was restricted to limited numbers of vendors and are not easy to integrate into IT systems. 

Despite some improvements, the point-to-point connectivity of fielded assets has remained relatively unchanged.  As a result, the interface from the field to the back office has become a complex integration of different protocols, data models, physical interfaces, and of course, different device latencies.

This all makes the back-office processing component more complex. This interface, for established infrastructures, is costly to maintain, upgrade and to incorporate additional field devices and systems. 

Once new infrastructure is built, it becomes established, and inherits all the negative traits of the legacy system.  The result is using the existing architectures to configure fielded assets, receive and process, which imposes higher costs on utilities. 

These costs are often passed to ratepayers and are not properly addressed with the latest technologies, which ultimately, reduce costs and protect them from becoming "legacy" and inflexible.

The traditional SCADA configuration is best described as a hub-and-spoke architecture with field devices and communications converging at a centralized collection point within the utility infrastructure.

Traditional SCADA Configuration (Credit: LiveData Utilities)

Figure 1. Traditional SCADA Configuration

The figure reveals several important observations:

  1. Disparate types of field devices create a large variance in protocols and data models that exist between the device and the SCADA front end. 
  2. There are numerous communication pathways to consider for a traditional SCADA system, each with their own characteristics in terms of throughput (bandwidth) and latency; and
  3. Processing at the front end is highly specific to the types of field devices that are interconnected to the SCADA front end. 

Three developments outside of the traditional utility sphere are having a dramatic impact on operations within the utility and on SCADA: 

  • Renewable integration is accelerating at all levels with respect to residential, commercial and industrial applications;
  • Field devices have greater amounts of relevant information, and are able to communicate the information at higher rates and at increased granularity; and
  • Regulatory changes are driving importance to market participation of aggregated DER.

The above developments are driving greater numbers of integrations as well as cost, maintenance and time. While SCADA is excellent for the purposes of transmitting data between assets and systems, its typical hub-and-spoke architecture creates speed bumps for both integration of OT system and enterprise systems.

An integration platform to clear the speed bumps

To address these challenges, many utilities have deployed an Operational Technology Message Bus (OTMB) to bridge the OT requirements imposed by a rapidly changing electric utility distribution operations environment to a complex IT architecture. 

The OTMB architecture is an example of how to meet the needs of the utility SCADA front end in the presence of high DER penetration without creating enterprise data latency. This bridge solves several traditional challenges and allows seamless interfacing between disparate field equipment and the back-office infrastructure while protecting life, equipment and the environment. 

OTMB implementations address the previous listed requirements as shown in the following table:

Requirement

OTMB

  • Interface to different types of communication methods with different characteristics in terms of throughput (bandwidth) and latency
  • OTMB operationalizes real-time bi-directional control, which includes operating grid automation on lossy and messy radio networks
  • Contain different types of processing capabilities to accommodate different types of field devices and systems
  • OTMB's integrates discrete devices such as RTUs and other grid automation, and manages configurable, complex OT data flow.
  • Typical integrations include: EMS, OMS, DMS, SCADA, DCS, MDMS, DERMS and GMS systems. 
  • Operational and business logic related to OT devices and systems are embedded in the OTMB
  • Scalability as the number of connected DER points, and connections to DER aggregators, continues to grow
  • OTMB is easily scaled to accommodate diverse data types; perform advanced extract, transform, and load functions; accept new protocols and data standards; and simultaneously capture, transform and deliver data across millions of data points
  • Secure, support different vendors' security models
  • The OTMB is designed to meet NERC CIP requirements
  • Seamlessly translate from one protocol to another, while respecting the functionality of the intended data model (e.g. resolve differences between IEC 61850-90-7 and OpenADR)
  • OTMB software patterns must support utility and industry protocols including ICCP, IEC 61850, OPC, DNP3, MultiSpeak, seb services, Modbus, ActiveMQ, and legacy proprietary protocols and include real-time methods for managing software "impedance" mismatches among standards
  • Interface to cloud-based aggregations
  • OTMB is designed for High-Availability and simple cloud integration

As seen here, OTMB is used in place of a SCADA system and acts as the critical bridge, providing data throughout a utility network of Operational Technology systems, devices and Information Technology. The platform approach reduces integration time, cost and maintenance while providing for future integrations.

LiveData Utilities OT-centric middleware platform approach used to reduce integration time, cost, and maintenance while providing for future integrations.

Figure 2. The OT-centric middleware platform approach used to reduce integration time, cost, and maintenance while providing for future integrations.

In addition to robust integration and ETL functions (pre-processing of real-time analytics data), perhaps the greatest advantage OTMB may offer over SCADA is the sheer visibility a utility can have across its enterprise. The OTMB's high-performant, secure bridge between all the OT and IT assets enables every device on the system to be a data generator.  

In the environment where field devices continue to expand along with their data model requirements, traditional SCADA systems become inherently more complex, costly and place legacy constraints on data processing.

An OT-Centric middleware integration platform like OTMB addresses the challenges not meant for traditional SCADA systems. It clears enterprise data speed bumps by enabling scalability while accommodating legacy systems and creates a platform for grid intelligence and optimization.

An OTMB software pattern clears the way for a secure information superhighway extending across the enterprise and into utility OT systems.

 

This guest editorial by Brad Harkavy, President, LiveData Utilities, originally appeared in Utility Dive.

 

 

Optimize

Your Systems

 

LiveData Utilities RTI Server is the basis for our OTMB framework. It is purpose built to deliver exceptionally efficient integrations of data, grid automation devices, OT and IT systems securely across low quality networks, and a range of OT standards ranging from 40-year-old device protocols to state of the art large-scale streaming standards.

LiveData Utilities RTIServer

Click here to schedule a FREE consultation with LiveData Utilities to learn how RTI Server can simplify integration and future-proof your systems.