Making the. LiveData Utilities manages OT integration (OTMB)

Transcription

1 Making the Grid complexity, so Smarter you don t have to. LiveData Utilities manages OT integration Managing Title Slide OT System or Section Integration Complexity Slide Title with an Goes OT Message Here Bus (OTMB)

2 Smart Grid Challenge more systems, more integrations Storage, Microgrids, Smart Devices, Demand Response, Cloud Analytics Distribution Substations Field Devices Gas Coal Energy Storage Wind Micro Grids Operational Technology Message Bus SCADA Data Lake Real Time Database DERMS EMS Analytics Engine AMI Network Historian OMS 2

3 OT Real-Time Middleware Operational Data-bus Control Room Grade Real-time middleware Control-bus Headless SCADA High performance OT centric dataflow engine Integration Bus OTMB OT Message Bus 3

4 OT and IT are Different OT Architectural Imperatives Protect: Life, Equipment, Environment Maintain service reliability Operationalize real-time bi-directional control Support lossy and messy radio networks Support legacy equipment and protocols Respond to regulatory quality requirements 4

5 OT and IT are Different 5

6 Operational Technology Message Bus (OTMB) Distribution Substations Field Devices Gas Coal Energy Storage Wind Micro Grids Operational Technology Message Bus SCADA Data Lake Real Time Database DERMS EMS Analytics Engine AMI Network Historian OMS OTMB: software architectural pattern OT-centric bidirectional real-time middleware Efficient integration of OT Systems and DA devices ETL functions for real-time Analytics Native protocol support 6

7 OTMB Attributes SCADA-class in-memory processing Configurable dataflows: mappings, statistical functions, filtering, coalescing, translations Dataflows configured from templates Populated at runtime Source of configuration: CIM, GIS Network scalable high availability (HA) solution Seamless integration with IT Enterprise Service Bus Native protocol support including ICCP, DNP3, Modbus, OPC, ActiveMQ and web services Embedded Data Manipulation (Python, Java ) 7

8 OTMB helps to manage disparate naming conventions/models Device name sometimes tied to location When a device moves, its name should not change Device names sometimes represent locational and functional information Very hard to manage device names across department and systems Typically, SCADA naming conventions are different from OMS naming conventions 8

9 OTMB Alternatives Custom point-to-point integrations (N to 1 vs. N^2) Point-to-point integrations Same general problems again and again Overriding commonality of meta-data issues Naming, Types, Network port sharing Expensive, time intensive, unpredictable development schedules Enterprise Service Bus (ESB) Focuses on "SOA", but web services weren't designed for the finegrained real-time requirements of Operations Lack native protocol support 9

10 Kansas City Power and Light Future DA Devices (FCIs, Reclosures, Cap Closures) Single point of control OT Middleware NO Distribution SCADA ADMS functionality using Oracle NMS RTP/TCP/IP DNP/TCP DNP3/MODBUS (Future Connection) RTI OT M essage Bus ICCP (Future Connection) Oracle Network Manager System NM S Ser vices & DB 10

11 Another view of KCPL 90,000 data points reduced to 30 templates Significant cost/time savings relative to custom interface Data flow 138 feet by 8 feet at full scale 11

12 CMPAS OTMB integration to member Web Management System Wind Farm 1 RTU 2 RTU Member Utilities 3 RTU 4 RTU 5 RTU 6 RTU 1 RTU 8 RTU 9 RTU 10 RTU 11 RTU 12 RTU MODBUS DNP3/MODBUS OT M essage Bus ICCP Future Connections MISO SQL Server RTI GAM Historian HMIs 12

13 New customer Member Communities RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU RTU DNP3 DNP3 DNP3 OT Message Bus ICCP ICCP HTTPS Distribution Control Center Region 1 Distribution Control Center Region 2 Energy Management Control Center 13

14 MRES Energy Management architecture using OTMB Natural Gas Power Plant Marshall Wind Farm Oil Fired Power Plant SOAP/ DNP3 DNP3 DNP3 XML OT M essage Bus DNP3 SOAP/ XML DNP3 SOAP/ XML ICCP ICCP MISO SPP SQL Server 14

15 NYPA -- OTMB and IT Middleware (WebSphere) NYPA Trading System OTMB Integration NYPA s Trading System, EMS and GMS Synchrophasor/SCADA integration ICCP IBM WebSphere WebSphere MQ OT Message Bus ICCP MODBUS SQL GMS Hydro EMS State Estimator 15

16 OT Message Bus Real-time OT centric dataflow engine and middleware platform Ensure the protection of : Life, equipment, environment Supports virtually all utility protocols including: ICCP, DNP3, Modbus, OPC, Web Services Faster OT system integrations Less risk, less cost, less one-off custom point-to-point solutions Lower operating costs Future-proof system integration Operational logic and IP remains in place as systems, devices and apps are upgraded 16