Accelerating Grid Modernization Open Field Message (OpenFMB) Bus Project SGIP OpenFMB Working Group OpenFMB Priority Action Plan

Accelerating Grid Modernization

Open Field Message (OpenFMB) Bus Project

SGIP OpenFMB Working GroupOpenFMB Priority Action Plan


What is Open Field Message Bus?

• Framework for distributed intelligent nodes interacting with each other• Economical industrial internet technologies applied to Smart Grid• Distributed resources communicating via common semantic definitions• Grid-edge nodes processing data locally for control and reporting

• OpenFMB supports field-based applications that enable:– Scalable peer-to-peer publish/subscribe architecture– Data-centric rather than device-centric communication including

support for harmonized system and device data– Distributed logic as well as centralized logic


Industry Drivers for OpenFMB

• Leverage lessons learned across many industries from the rapid maturation and adoption of Internet of Things (IoT) technologies

• Optimize legacy and future assets• Promote self-healing, resiliency, and improved power quality• Integrate renewable and distributed energy resources into the Grid and

flexibly manage two way power flow• Support a Transactive Energy marketplace • Facilitate new solutions and capabilities and reduce time-to-market


Guiding Principles

Based on operational and functional requirements

Use cases drive functional and operational requirements.

Requirements determine and limit scope and success parameters

Features added only when requirements demand it.


What’s Different About OpenFMB?

• Led by utilities (largest IOU, Muni, and Co-op) based on their priorities and interoperability demonstration experience

• OpenFMB reduces latency and creates distributed intelligence opportunities to manage local grids in the most efficient way based on local resources and conditions

• The data-centric bus secures information, data topic via data topic (analogous to securing data in a database, table by table) instead (or in addition to) of traditional method of applying security at the transport layer

• OpenFMB enables grid devices to speak to each other, e.g. meters, relays, inverters, cap bank controllers, etc.

• Enables legacy equipment to be retrofitted for new capabilities, features, and extended life

• Facilitates data integration across previously silo-ed domains within the utility


OpenFMB Expected Benefits

• Fostering innovative products and services• Local intelligence with coordinated self-optimization where the

volume of local data overwhelms the capability to transfer the data elsewhere

• Fast response when centralized sites are too far away to respond promptly

• Resiliency when portions of the grid are segmented• Open, observable, and auditable interfaces at multiple scales for

interoperability• Interoperability with existing assets with no rip-and-replace• Potential unified backhaul for reduced OPEX, simplified

management, and enhanced security • Unlocking stranded assets by building adapters and applications


Origin of Open Field Message Bus

• 2014 Duke Energy Coalition of the Willing (COW)– 6 vendor partners

• Distributed Intelligence Platform (DIP)– Peer-to-peer communications– Internet technologies– Goals

• Foster innovative products and services and COTS tools

– Distributech 2014• 2015

– COWII– Testing and interoperability demonstration at Dtech 2015


Participants• Utilities

– Ameren Services– American Electric Power (AEP)– CPS Energy– Detroit Edison (DTE)– Duke Energy– Oklahoma Gas & Electric– Pedernales Electricity Cooperative– Southern California Edison (SCE)– Southern Company

• Test Beds– CPS Energy– Duke Energy– National Renewable Energy Laboratory (NREL)

• Academia, R&D, and Standards Setting Organizations– EPRI– IEEE – NAESB– NEMA– OpenADR Alliance– FREEDM Systems Center

• Vendors– ABB– Aclara– Ericcson– General Electric– Green Energy– ITOCHU– Itron– Kitu Systems– LocalGrid– Omnetric– Real Time Innovations– ViaSat

• Consultants– Coergon– EnerNex– GridIntellect– Xanthus– Xtensible Solutions

• Government– DOE– FERC– NIST– ORNL– PNNL


Demos NAESB Standard

EPRI SGIPDtechNRELDuke EnergyCPS Energy

SpecificationReference

Architecture

Test Beds

SGIP OpenFMB Project Process

Determine Semantic Model Needs

Develop Adapters and Applications

IEC 61968/70

IEC 61850MultiSpeak

Microgrid Unscheduled DisconnectMicrogrid ReconnectMicrogrid Operational Optimization

SchemasIndustrial Protocols

Pub/SubDistributed Intelligence

Develop Use Cases and Requirements


OpenFMB Project Timeline

Use Case

UML Modeli

ng

Application and Adapter Develop

ment

Demonstrations

Feb - May July - AugustMay - July September - February

2015

DistribuTECH 2016Feb. 9-11 (Orlando, FL)

SGIP Annual MeetingNov. 3-5 (New Orleans)

Use Case MeetingMay 14-15 (NREL)

Modeling MeetingJuly 8-9 (EPRI Charlotte)


NAESB Standard Development Timeline

Requirements

Design

Draft

Task Force Voting

30 Day Public Comment

30 Day Membership Ratification

NAESB Executive Committee Meeting on

Feb. 2016

March - May June - August Sept.-Nov.

DistribuTECH 2016Feb. 9-11 (Orlando, FL)

Dec. Jan. – March

2015 2016

SGIP Engage 2015(March 4, 2015)

OpenFMB Use Case Prioritization

(April 2, 2015)

OpenFMB TF F2F Meeting #1 (May 15, 2015)

OpenFMB TF F2F Meeting #2 (July 8-9, 2015)

OpenFMB TF F2F Meeting #3

(TBD)


How does OpenFMB relate to the GWAC* Stack? *Gridwise Architecture

Council


Data-Centric (OpenFMB) vs. Message-Centric Bus

Message Centric Data Centric (DDS)

Message Centric Middleware

Application

Application Logic

Message Parsing and Filtering

Message Caching

Send/Receive Packets

Addressing, Marshaling

Data Centric Middleware (RTI)

Send/Receive Packets

Discovery, Presence Marshaling, 32/64

Message Caching & State

Management

Message Parsing and Filtering

Application

Application Logic

Savi

ngs

• Message centric middleware addresses network interoperability, syntactic interoperability, and semantic understanding (GWAC Layers 2, 3, & 4).

• Data-centric middleware (DDS) supports GWAC layers 2, 3 & 4 as well as Layer 5 (Business Context), allowing for simpler application code development, scalability, and fine-grain security on the data itself rather than the transport layer.


Overall OpenFMB Design Process

OpenFMB XSD

Pub/Sub Syntax

OpenFMB node

Adapter

Device

OpenFMB node

Adapter

App

OpenFMB DataFlow Configuration

Build Use-Case

Export Profiles

Convert XSD

Configure Middleware

Topics, QoS, Readers/ Writers

OpenFMB UML

Requirements

IEC CIM UML


Open Field Message Bus

Pub/Sub

OpenFMB Conceptual Architecture

A

C

D

EB

A C

F

B

Use Case

1

Use Case 2

Use Case 3

Grid Resource Group B

AppAdapter

D

Data Device & App

Use Case

LEGEND

A

CB E

F

D

Grid Resource Group A

AppAdapter

Grid Resource Group C

Adapter

AppAdapter

App

AppAdapterAp

pAd

apte

r


• System Boundary• Network Transport

– Media access (layer 2)– Network (layer 3) security– Session/Endpoint (layer 4/5) security

• Host– Machine/OS/Applications/Files

• Data & Information flows

At least one, but not all need to be implemented

This is addressed by DDS Security

How will OpenFMB be secured?


Questions?

Stuart McCaffertySGIP, VP OperationsOpenFMB [email protected]

Dr. Stuart LavalDuke Energy, SG Technology ManagerOpenFMB [email protected]

For more information, visit the SGIP website

mailto:[email protected]



http://sgip.org/Open-Field-Message-Bus-OpenFMB-Project

Documents

Accelerating Grid Modernization Open Field Message (OpenFMB) Bus Project SGIP OpenFMB Working Group OpenFMB Priority Action Plan