231 likes | 455 Vues
Operational Technology + Information Technology. Applying Message Oriented Middleware to Operational Systems. Arlen Nipper - Cirrus Link. Instrumented. Interconnected. Intelligent. How can we apply technology to:. Mitigate environmental risk? Detect leaks earlier?
E N D
Operational Technology + Information Technology Applying Message Oriented Middleware to Operational Systems Arlen Nipper - Cirrus Link
Instrumented Interconnected Intelligent How can we apply technology to: • Mitigate environmental risk? • Detect leaks earlier? • Resolve problems faster? • Manage audit and regulation more effectively? • Run operations more efficiently?
Message Oriented Middleware Message Oriented Middleware (MOM) is a well proven and an integral component in modern Service Oriented Architecture (SOA) and Enterprise Service Bus (ESB) solutions. How can we best apply this mature and well proven technology to Operational systems as well? • What problems does Message Oriented Middleware solve? • How can Message Oriented Middleware be applied to operational systems today?
Using the SCADA Host as Message Oriented Middleware To a large extent, we as an industry have already been trying to make our Operational Applications “look” like Message Oriented Middleware….. Future Apps & Integration Historian Analytics & BIG DATA SCADA Host Electronic Flow Measurement ? 1 3 ERP Protocol X Mobile Apps 2 Asset Management & Optimization “Enterprise (IT)” “Operations (OT)”
Using the SCADA Host as Message Oriented Middleware Future Apps & Integration Analytics & BIG DATA 1 PLC 3 Flow Computer SCADA Host Electronic Flow Measurement ? ERP Protocol X Mobile Apps 2 Asset Management & Optimization “Enterprise (IT)” “Operations (OT)”
Using the SCADA Host as Message Oriented Middleware 1 PLC 3 Flow Computer SCADA Host Protocol X “New” Application Electronic Flow Measurement 2 “Enterprise (IT)” “Operations (OT)” Create a “New” application that can provide the interface between the EFM application and the SCADA Host Application. Define the interface/data schema between the New application and the EFM application. 2 3 2 4 3 4 1 1 Modify/change/test any required Access Control List (ACL) and define the security for connecting to the SCADA Host application. Modify the SCADA Host poll tables so that additional polls to the Flow Computer are added to acquire desired information.
Using the SCADA Host as Message Oriented Middleware “What is invariably happening is that more and more access to SCADA data from the lines of business is putting the SCADA Host application in the position of being a MOM system, which they were never intended to be in the first place. As more and more applications and modifications are made to the SCADA Host application to satisfy the needs of lines of business, the systems invariably become harder and harder to manage, and ultimately become so brittle that no one will touch them to add additional capabilities. At this point innovation within the business, as it applies to the vast amount of additional information in field devices, comes to a grinding halt!”
Decoupling Devices from Applications using Message Oriented Middleware Future Apps & Integration Historian Analytics & BIG DATA SCADA Host Electronic Flow Measurement ? 1 3 ERP Protocol X Mobile Apps 2 Asset Management & Optimization “Enterprise (IT)” “Operations (OT)” Starting from here…… we can keep all of the same components by just re-architecting the topology a bit.
Decoupling Devices from Applications using Message Oriented Middleware SCADA Host Future Apps & Integration Historian Analytics & BIG DATA 1 Electronic Flow Measurement Message Oriented Middleware 2 ERP Mobile Apps 3 Asset Management & Optimization “Enterprise (IT)” “Operations (OT)” Nice topology picture, but how can you actually implement this architecture?
Use Message Queuing Telemetry Transport (MQTT) A Transport Designed for SCADA “MQTT is a bi-directional lightweight event and message oriented transport allowing devices to communicate efficiently across constrained networks to backend systems” MQTT was originally designed for use in real time pipeline SCADA systems! • Natively built on top of TCP/IP. • Stateful with continuous session awareness. • Extremely bandwidth efficient. • Three levels of Quality of Service for data delivery. • Data agnostic. • Client side session establishment. • No defined security model. Since MQTT is natively build on top of TCP/IP, best practice TCP/IP security scheme can be used.* *The OASIS MQTT Security Subcommittee is working in conjunction with NIST for recommended best practices using MQTT in critical infrastructure.
Add an MQTT Data Broker The Message Oriented Middleware Component MQTT Enabled Device MQTT Enabled Application MQTT Enabled Message Oriented Middleware MQTT Enabled Device JMS Enabled Application MQTT Enabled Device SOAP Enabled Application
MQTT - Publish Subscribe Messaging A Publish Subscribe messaging protocol allowing a message to be published once and multiple consumers (applications / devices) to receive the message providing decoupling between the producer and consumer(s) A producer publishes a message (publication) on a topic (subject) A consumer subscribes (makes a subscription) for messages on a topic (subject) A Message Oriented Middleware server / broker matches publications to subscriptions • If no matches the message is discarded • If one or more matches the message is delivered to each matching subscriber/consumer
The Resulting 100% MQTT MOM SCADA Implementation SCADA Host Future Apps & Integration Protocol X Edge of Network Controller 1 Historian Analytics & BIG DATA DMZ Protocol Y Edge of Network Controller Electronic Flow Measurement 2 MQTT Enabled Message Oriented Middleware ERP Mobile Apps 3 -Native MQTT device Asset Management & Optimization “Enterprise (IT)” “Operations (OT)” 1 2 1 2 3 4 4 3 MQTT message transport. MQTT, JMS, REST, SOAP, and “other” ESB message transports Single point DMZ for access control, permissions, and security settings. SCADA is a VERY important data consumer, but not the ONLY consumer.
With MQTT and Message Oriented Middleware we can move from “Current State” …..
… to “Future State” SCADA Host SCADA Host SCADA Host SCADA Host SCADA Host SCADA Host Future Apps & Integration Historian MQTT Enabled Message Oriented Middleware DMZ Analytics & BIG DATA Electronic Flow Measurement ERP Mobile Apps Asset Management & Optimization
The Vision - Tie All Operations Together Cathodic Protection Upstream Terminal Automation MQTT Transport Data Center Message Oriented Middleware Enterprise SCADA Tank Farm / Storage Midstream/Downstream Pipeline Control 16
Summary Poll-Response SCADA systems were perfectly viable solutions when first developed 35 years ago. They have served the industry well, and continue to do so. But we are entering 2014. SCADA solutions need to leverage the very same Message Oriented Middleware technologies that IT solutions use to: • Decouple device protocols from applications. • Dramatically improve critical data update times. • Reduce network bandwidth consumption. • Enable “one to many” information exchange. • “UnlockOperational Intelligence” stranded in field devices!
Additional Topics Not Yet Covered • Message flows, data transformation, message transformation. • Migration strategy maintaining Operational Integrity and 100% legacy backwards capability. • Redundancy (native architecture capability) • High availability (native architecture capability) • Scalability (native architecture capability)
Instrumented Interconnected Intelligent We can apply technology to: • Mitigate environmental risk • Detect leaks earlier • Resolve problems faster • Manage audit and regulation more effectively • Run operations more efficiently
Message Queuing Telemetry Transport (MQTT) Resources All things MQTT http://mqtt.org Eclipse Paho http://www.eclipse.org/paho/ OASIS MQTT Technical Committee https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=mqtt Eclipse M2M http://wiki.eclipse.org/Machine-to-Machine MQTT Specification http://www.ibm.com/developerworks/webservices/library/ws-mqtt/index.html