Accelerating Grid Modernization Open Field Message Bus (OpenFMB) Kickoff Meeting March 5, 2015

Accelerating Grid Modernization

Open Field Message Bus (OpenFMB)Kickoff Meeting

March 5, 2015


Welcome

• Introductions– Around the room

• Meeting Objectives– Kickoff meeting– Understand history and players involved

• Leverage prior work from Duke Energy’s Reference Architecture

– Establish key milestones and regular meeting times– Identify the “big pieces” and begin identifying organizational and

individual responsibilities– Clarify standards development activities– Discuss team collaboration tools– Build team unity and identify roles


AgendaTime Discussion Discussion Lead

0830-0900 Welcome• Introductions• Meeting objectives• Agenda

Stuart McCafferty, SGIP

0900-1045 What is OpenFMB?History• Duke Reference Architecture

• The Big Picture• The Past• The Future• The CPS Test Bed

Stuart Laval, Duke EnergyRaiford Smith, CPS Energy

1045-1100 Break

1100-Noon Team and Tools Stuart McCafferty, SGIP

Noon - 1300 Lunch


AgendaTime Discussion Discussion Lead

1300-1330 Project Plan• Key milestones and events• Key work activities• Leads

Stuart Laval, Duke EnergyStuart McCafferty, SGIP

1330-1415 NAESB Processes and TimelinesOpenFMB Framework/StandardStandards Development Plan and Deliverables

Jonathan Booe, NAESBJoe Zhou, Xtensible Solutions

1415-1430 Break

1430-1515 Open Discussion on Standards Process and OutputThe Demonstration in New Orleans

All

1515-1600 Next Steps Stuart McCafferty, SGIPStuart Laval, Duke Energy

1600-1615 Dinner Plans Stuart McCafferty, SGIP


What is Open Field Message Bus?

• Standard API for Electric Grid interoperability– Secure, peer-to-peer, multi-vendor, outside data center

• Common Semantic models based on existing standards (CIM, 61850)

• Existing IoT pub/sub protocols (DDS, MQTT, AMQP)• Repository of adapters from utility protocols (Modbus,

DNP3, C12, GOOSE/MMS)• Framework and reference architecture for Distributed

Intelligence Apps and systems– Cybersecurity, microgrids, DER, DA, AMI


OpenFMB: Lower Cost & Risk

• Cost Savings

• Risk Mitigation

6

ResiliencyInteroperabilityModularityAsset ManagementLower O&M

Renewable IntegrationSituational AwarenessCybersecuritySustainable InfrastructureSupply Chain


OPENFMB HISTORY

Stuart Laval, Duke EnergyRaiford Smith, CPS Energy


A Short History of the Development of the OpenFMB• (~2007) Initially, we focused on the problem of

connecting to multiple devices to backhaul data.– Node-based solution (high volume) with multiple radios to

connect to MV sensors, AMI, DA, and others.

• (~2012) But use cases evolved and new technologies (battery storage, microgrids, etc.) drove need to get access to data cheaper/better/faster at the edge of the network.– Drove need for node platform hosting 1 or more standards-

based message busses and common semantic models.


Duke Energy Test Areas: Integrated Grid Ecosystems Pilot (2012)Su

bsta

tion • Solar PV

• Energy Storage• Dist. Mgmt System• PMU (6)• Weather stations (7) S

herr

ill’s

Ford

, Ra

nkin

, McA

lpin

e Su

bsta

tions

Cust

omer

Prem

ise

~60

hom

es s

erve

d by

M

cAlp

ine

circ

uits • Solar PV

• Home Energy Manager• PEV • Charging Stations• Smart Appliances• Demand Response • In-home load monitoring

Dis

trib

ution

Ci

rcui

t

6 M

cAlp

ine

circ

uits

• Line Sensors (200+)• Solar PV• CES, HES Energy Storage • Comm. Nodes (3,000)• Intelligent Switches• DERMS/DMS• AMI metering (14,000)

Copyright © 2015 Duke Energy Corporation All rights reserved.


e.g. CIM

e.g. DDS, M

QTT

Key Observations:1. Multi-Purpose Functions2. Modular & Scalable HW&SW3. End-to-End Situational Awareness4. OT/IT/Telecom Convergence5. True Field Interoperability!

Key Observations:1. Single-Purpose Functions2. Proprietary & Silo’ed systems3. Latent , Error-prone Data4. OT/IT/Telecom Disconnected5. No Field Interoperability!

Lessons Learned from 2012 Smart Grid Pilot

Copyright © 2015 Duke Energy Corporation. All rights reserved.


Enabling of the Integrated GridDrivers

• Distributed Energy Resources• Demand Response• Electric Vehicles• In-Premise Automation• Cybersecurity Threats• Aging Infrastructure• “Big Data” Complexity• Stranded Assets

New Requirements• Proactive Operations• Situational Awareness• Fast Edge Decisions• Seamless Interoperability• Modularity / Scalability• Hybrid Central/Distributed• Zero Touch Deployments• Refined Utility Skillsets

Technology Approach1. Internet Protocol2. Translation3. Common Dictionary4. Security5. Analytics

Distributed Intelligence

Platform(DIP)

Copyright © 2015 Duke Energy and 2014 Electrical Power Research Institute. All rights reserved.

Source: EPRI


InternetProtocol (IP)

Network

Smart Meter

Capacitor Bank

LineSensor

XStreet Light

SmartAssets

DistributedEnergy Resources

Transformer

Intelligent Switch

DEM

AND

ELEC

TRIC

GRI

D

Smart Generation

Continuous Emission Monitoring

Weather SensorSUPP

LY

Other Nodes

Open StandardNode

CPU

Radio InternetConnectivity

Distributed Computing

HeadEnd A

HeadEnd B

HeadEnd N

Data Center M

essage Bus

Network Router

UTILITYDATA CENTER

Technology Approach1. Internet Protocol2. Translation3. Contextualization4. Security5. Analytics


DIP: Internet of Things (IoT) Platform for the Utility

OpenFMB


InternetProtocol (IP)

Network

Smart Meter

Capacitor Bank

LineSensor

XStreet Light

SmartAssets


Transformer

Intelligent Switch

DEM

AND

ELEC

TRIC

GRI

D

Smart Generation

Continuous Emission Monitoring

Weather SensorSUPP

LY

Other Nodes

Open StandardNode

Virtual OS

Core OS InternetConnectivity

Distributed Computing

HeadEnd A

HeadEnd B

HeadEnd N

Data Center M

essage Bus

Network Router

UTILITYDATA CENTER

Technology Approach1. Internet Protocol2. Translation3. Contextualization4. Security5. Analytics

DIP: Internet of Things (IoT) Platform for the Utility


OpenFMB


Flexible Hardware & Software Platform Using Legacy Equipment

14

RetrofitInside Cabinet

Pole MountedEnclosure

PadmountEnclosure

SubstationRackmount Server(s)

Integrated in End Device(as Software)

Copyright © 2014 Duke Energy All rights reserved.


AMISmart Meters

Protection& Control


IP Router

Virtual Software

Corporate Private

Network

MDM

SCADA

Headend

Higher Tier Central Office

(Utility Datacenter)

Application OSCore OS

Legend

Middle TierNodes

(e.g. substation)

Lower Tier Nodes

(e.g. grid)

End PointsDevices

IP Router

Virtual Software

IP Router

Virtual Software

Field Area Network

(FAN)

Wide Area Network(WAN)

Local Area Network

(LAN)

Local Area Network

(LAN) Physical TransportVirtual Telemetry

Tier 5 DIP Node

Field Message Bus

Field M

essage Bus

Fie

ld M

essa

ge B

us

Field M

essage B

us

Enterprise Bus

Enterprise B

us

Enterprise B

us

Enterprise Bus

Firewall

Virtual Firewall

DMS

Enterprise B

us

>15 min

~1min

<5 min

<50 ms

No model

No model

No model

model

model

model

model

Polling

model

IoT Reference Architecture: Hybrid Multi-level Hierarchy


http://www.google.com/imgres?imgurl=http://www.smartenergy-jobs.com/furniture/cms/images/thumbnails/sector_icon_smart_meter.gif&imgrefurl=http://www.smartenergy-jobs.com/&usg=__GsvewpASnN9XC6FoMxyHMisCyCI=&h=80&w=80&sz=1&hl=ko&start=5&sig2=qQuHU1C15MX1IiHIGdm8Wg&zoom=1&itbs=1&tbnid=u6Irlz20fT3RvM:&tbnh=74&tbnw=74&prev=/images?q=smartmeter+icon&hl=ko&tbm=isch&ei=TNPSTZ_4Hsuq-Aa5vLjXCg




Smart Meter

Capacitor Bank

Line Sensor

BatteryInverter

DMS

Head Ends SCADA

Higher Tier NodeCentral Office

(Utility Datacenter)

Common Semantic ModelLegacy Protocol TranslationLegend

Middle Tier Nodes(e.g. substation)

Lower Tiers Nodes(e.g. grid)

End PointsDevices

Legacy Protocol Adapter

Common Data Model

Field Message

Bus (FMB)

Client/Server PollingPub/Sub Messaging

Open Field Message Bus (OpenFMB) Framework Firewall

Virtual Firewall

MDMM

- +

Open API FMB protocol


Common Data Model

Open APIFMB protocol


Common Data Model

Open APIFMB protocol

BreakerRelay

Solar PVInverter

C12

DNP

DNP

Modbus

GO

OSE

Modbus

Open FMB IoT Protocol


Common Data Model

Open API FMB protocol

OMSGIS

DNP

Oth

er

DDS, MQTTDDS

MQTT, DDS

AMQP, DDS

MQTT



Background on Publish-Subscribe IoT Protocols

• Leverage existing IoT pub/sub – Data Distribution Service (DDS): OMG standard– Message Queue Telemetry Transport (MQTT): OASIS standard– Advanced Message Queue Protocol (AMQP): OASIS standard

• Abstraction of physical, network, & logic layers

• Standardized APIs for Multi-Vendor Interoperability– E.g. OMG’s DDS-i RTPS or DCPS API– IoT translators allow interoperability between DDS/MQTT/AMQP

• Performance– Scalability: >10000 msg/sec for DDS; >1000 msg/sec for AMQP/MQTT – Latency: ~1 ms– Multi-cast & Fault-Tolerance: DDS & AMQP

• Security: Encryption, Quality of Service, Dynamic Discovery



Information Modeling

Use-case Requirements(Power Systems SME)

Common Semantic Models(CIM, IEC 61850)

Contextual Profiles(UML)

Schema(IDL / XSD)

Programming Languages(Java, C/C++/C#, XML)

Pub/Sub Protocols(DDS, MQTT, AMQP)

Semantic Context

Message Syntax

Message Oriented

Middleware

Map Relevant ContextDiagram Business Process

Model Driven Transformation

Code Generation

Interoperable Topics

OpenFMB Data Modeling Process



Meter

Transformer

Meter

480/277V

12 kV

Point of Common Couplingfor Microgrid

Power Grid

Solar PV Inverter

BatteryInverter

Example Use-case: Microgrid Solar Smoothing

MicrogridController

(MGC)

Solar Smoothing App

Recloser







Node 1

MQTTBroker

Opengridstandards.org

Cloud Hosted Field Message Bus (FMB) Demo Website

Meter

BatteryInverter

PV Inverter

Meter

MGC Solar Smoothing

App

DDSDataSpace

2 IDL’s JavaD

DS

1 IDL

3 IDL’s JavaD

DS

1 IDL

JavaD

DS

Sub to Data

Pub Controls

Pub Data

Sub to Controls

Pub Data

JavaD

DS

7 XSD’s

XML

MQ

TT

Sub to Data Pub XML

User Interface

Node 2

Node 3

Input Datasets M2M Devices DDS Field Message Bus Topics

Node 4

Text-based Message Interfaces

page 20Copyright © 2015 Duke Energy Corporation All rights reserved.



http://www.opengridstandards.org/


XML/MQTT Translatorto Cloud Website

CIM/DDS Solar Smoothing App

CIM/DDS Solar PV &Meter data

CIM/DDS Battery Inverter& Meter data

Open Field Message Bus (OpenFMB) Demo Setup



Strategies to Gain Adoption

• Patent strategy (2013-2014): patent the architecture (so no one can lock utilities or vendors out) and give away the IP (so everyone can adopt it)

• Getting vendors on board (2013-today)– Duke Energy Coalition of the Willing (pt 1) – Distributech 2014 demo (6 vendors)– Duke Energy Coalition of the Willing (pt 2) – Distributech 2016 demo (25 vendors)

• Getting utilities on board (2013-today)– CPS Energy

• Standards strategy (2015)– SGIP– NAESB– Others


Duke Energy Test Lab: Mount Holly, NC

PV Installations

Islanding Switch, Transformer, and Battery

Behind the meter and low voltage power electronic equipment

23

Grid Equipment


Duke Energy Mount Holly Microgrid: Electrical One-line

Copyright © 2014 Duke Energy All rights reserved.

Point of Common Coupling


How CPS Energy Will Utilize the OpenFMB

• NREL INTEGRATE Microgrid at JBSA Ft. Sam Houston

• Grid-of-the-Future deployment• CPSE Coalition of the Willing • Augment existing AMI/DA deployment


JBSA Ft. Sam Houston Microgrid Location• NREL Integrate project to build an open-source, interoperable microgrid.• Collaboration between CPS Energy, Duke Energy, and Omnetric Corp.• 75kW/48kWh SciB battery from Toshiba, Princeton Power Inverter, Viper

Recloser, Schneider Ion meters, Microgrid Management System from Siemens, and ~25kWAC PV.

• Operational date Q3 2015.

26

Ft. Sam Houston Library

Transformer / Meter Rack Location

Potential Battery & PV

Locations


CPS Energy Grid of the Future

27

Walzem Substation (NE San Antonio, off of I-35). This site includes:

• 15 circuits (13 and 35 kV).

• About 30k customers (including HQ of large technology firm and logistics site for major retail firm).

• Includes clustered (~70) solar DG and utility-scale solar at 5.5MW Alamo 3 site off O313 circuit.

• AMI and DA deployment scheduled for deployment in this area.

• Implementation work will be done over a three year period in conjunction with microgrid, smart inverter, and battery storage initiatives.

San Antonio, TX


Demand-Side Benefits• One primary purpose of GoF is to avoid divergence of customer and utility services (e.g. 3rd

party disaggregation w/o deregulation)

• Additional revenues can also be derived from new technologies: – Electric vehicles and charging – Premium power – battery/CHP/PV– Premium reliability – microgrid– Asset control (inverter/battery) and advanced DR

• Brand & customer satisfaction improvement though enabling new services– If customers purchase an additional product or service (beyond gas or electricity) they are 3X more likely to

favorably rate their service provider.

page 28


Utility-Side Benefits• Operational metrics (SAIDI, SAIFI, asset utilization, MTBF, etc.,.)

• Financial metrics (O&M spend, revenue generation, better asset utilization, and reduced total ownership costs)

• Environmental benefits – predominantly extrapolated intangibles through planned work in analytics combined with modeling and simulation of demand and supply

• Training and development of professional and wage-scale staff.

• Safety and standards updated to reflect new capabilities.

• Risk modeling should improve prediction of revenue, expense and customer satisfaction from new products and services.

page 29


Morning Break: 10:45 – 11:00


TEAM AND TOOLSStuart McCafferty


OpenFMB Project Objectives

1. Engage with multiple utilities and vendors2. Leverage prior work3. Identify one business problem to solve4. Identify or develop use case(s)5. Develop logical architecture6. Establish standards framework at NAESB7. Demonstrate working prototype at SGIP Nov 3-58. Create OpenFMB repository9. Incorporate SGIP T&C and Cybersecurity processes10. Test Bed coordination11. Governance policy for OpenFMB implementation and validation12. Roadmap for future distributed applications13. Regular outside communication and information exchange


OpenFMB Team

Utility Partners

User Groups

SDOVendors

Research Labs, Gov’t, Test Facilities


OpenFMB Leads

• SGIP Co-Chairs– Stuart Laval, Duke Energy / Stuart McCafferty, SGIP

• SGIP OpenFMB Vice Chair– TBD

• SGIP OpenFMB Secretary– TBD

• Demonstration planning for November– Aaron Snyder, EnerNex

• NAESB Task Force– Co-Chairs: Joe Zhou, Xtensible Solutions / Stuart Laval, Duke Energy– Raiford Smith, CPS / Matt Wakefield, EPRI / Craig Miller, NRECA

• Test Bed Coordination– TBD

• Business and Use Cases– TBD

• Regulatory awareness– TBD


Current Interested Parties

• AEP• Ameren• BC Hydro• Cisco• Coergon• CPS Energy• DOE• Duke Energy• EnerNex• EPRI• GE Energy• Green Energy Corp• Itron• Leidos Engineering

• LocalGrid Technologies• Missouri University of Science

and Technology• NIST• OpenADR Alliance• PNNL• Real-Time Innovations (RTI)• Saviva Research• Schneider Electric• SGIP• UCAIUG• ViaSat• Xtensible Solutions


Tools

• Kavi Collaboration environment– Document repository with version control– Action items– Calendar and Schedule– Ballots– Comment manager– Auditing and reporting tools– Listserver

• [email protected]

– Full privileges to SGIP members– Free access to approved non-SGIP members

mailto:[email protected]


Tools - Kavi

Project Environment Group Environment


Questions and Closing Thoughts

• For Kavi account access:– Email: [email protected] or [email protected]

• Need to recruit more utilities, vendors, and others– Everybody’s job

• Interested in volunteering to lead an area?– Contact Stuart or Stuart

• Got things to post to Kavi?– SGIP members can post– Non-members can send materials to Billie or Stuart M




Lunch: Noon – 13:00


PROJECT PLANStuart McCafferty, SGIP


OpenFMB Program Timelines

Organization ProjectDevelopment Schedule

2015 2016

NAESB(North America

Energy Standards Board)

• Standardization of Open Field Message Bus (OpenFMB)

SGIP(Smart Grid

Interoperability Panel)

• OpenFMB Project

• Test Beds

UCAIug • OpenFMB Repository

OpenFMB Wholesale Energy Quadrant

OpenFMB Planning

OpenFMB Interoperability Testing & Certification

Duke COW Phase II Demo

LegendPlanning / OtherDuke CPS TBD

OpenFMB Retail Market Quadrant

OpenFMB Phase 2OpenFMB Phase I

CPS Grid of the Future Demo

Utility TBD Demo

Duke Tech Transfer

OpenFMB Data Models/Adapters/Specifications Development


Milestones

2015 2 9 16 23 30 6 13 20 27 6 13 20 27 3 10 17 24 1 8 15 22 29 5 12 19 26 3 10 17 24 31 7 14 21 28 4 11 18 25 2 9 16 23 30 6 13 20 27 4 11 18 25

TaskMilestones

Proposal Accepted

Distributech

Kickoff Meeting (March 5) 5

Use Case F2F (April 2) 1

Use Case/UML Deliverable 1

Requirements Deliverable 22

Regulatory Issues and Plan Deliverable 5

Demonstration Plan Deliverable 22

Annual Meeting Breakout Session Delierable 21

Test Bed Plan Deliverable 19

Final Report and Case Study Deliverable 11

Press Article 24 31 16 15

Complete Idiot's Guide to OpenFMB 31

J uneJanuary February March April May July August September October November December


NAESB PROCESSES AND TIMELINES

Jonathan Booe, NAESB


Background on NAESB

• The North American Energy Standards Board (NAESB), originally the Gas Industry Standards Board (GISB), serves as an industry forum for the development and promotion of standards which will lead to a seamless marketplace for wholesale and retail natural gas and electricity, as recognized by its customers, business community, participants, and regulatory entities.

• GISB est. 1994 / NAESB est. 2001

• Roughly 2,700 Wholesale Standards / 1,200 Retail Standards

• Strong relationship with the Federal Energy Regulatory Commission (FERC), National Association of Regulatory Utility Commissioners (NARUC), Department of Energy (DoE), Department of Commerce (DoC), National Institute of Standards and Technology (NIST), National Petroleum Council (NPC), the American National Standards Institute (ANSI) and various state regulators


NAESB Quadrant & Segments

• Wholesale Gas – 5 Segments1. End Users2. Local Distribution3. Pipelines4. Producers5. Services

• Retail Markets – 4 Segments1. Electric Utilities2. Gas Market Interests3. Electric End Users/Public Agencies4. Electric Service Providers/Suppliers

• Wholesale Gas – 5 Segments1. End Users2. Distribution/LSE3. Transmission4. Generation5. Marketers/Brokers6. Independent Grid Operators/Planners7. Technology and Services

• Membership1. Retail Market Quadrant - 432. Wholesale Gas Quadrant - 1213. Wholesale Electric Quadrant - 139


NAESB Organizational Structure


NAESB Standards Development Process


NAESB Final Products

• Ratified recommendations = NAESB Final Actions• Copyright protection• Access provided to members, non-member

purchasers and through copyright waivers for evaluation

• Wholesale standards provided to Federal Energy Regulatory Commission and other agencies as appropriate

• Retail standards provided to NARUC and requesting state commissions


OPENFMB FRAMEWORK/STANDARDSTANDARDS DEVELOPMENT PLAN AND DELIVERABLES

Joe Zhou, Xtensible Solutions


Agenda

• Introduction and Background

• Industry Drivers and Guiding Principles

• OpenFMB Specification Key Components:– Business Requirements (Use Cases)– Reference Architecture and Systems Requirements– Platform Independent Model (Semantic Model, Messages and Services)– Platform Specific Model (DDS, MQTT, etc.)– Implementation Guidelines

• Development Plan Timelines, Processes and Roadmap

• Open Discussion

NAESB OpenFMB TF


Notable IoT Standards Initiatives

March 5, 2015 NAESB OpenFMB TF


Introduction and Background

• NAESB has been involved in the smart grid standards development – PAP09 – Demand response use cases that led to OpenADR specification– ESPI – Energy Service Provider Interface that led to Green Button.

• NAESB, as an ANSI accredited SDO, typically files their standards with FERC and informs NARUC. This increases the exposure and possibilities of utility regulators adopting said standards.

• OpenFMB task force will be a special purpose task force under the NAESB Retail Market Quadrant (RMQ).

• OpenFMB TF will work closely with SGIP and UCAiug to facilitate the development, implementation, and future enhancements to the standard.



Industry Drivers for OpenFMB

• Rapid maturing and adoption of IoT Technologies in many industries

• Renewable energy resources integration into the Grid – especially at the distribution and end consumer levels

• The advent of Distribution Service Platform Provider (DSPP) role and the potential need to support Transactive Energy implementation.

• Transition from top down power grid architecture into networked, two way power flow, and distributed supply and demand power network.

• An open standard is needed to unlock the value of field devices and networks, and to enable distributed intelligence for more reliable and resilient grid of the future.



Guiding Principles

• Leverage what has been done before, no reinventing the wheels• Focus on business value and objectives in solving real world problems• Collaborate and coordinate with other relevant smart grid standards

bodies, no duplication of effort and scope• Time to market is important to provide real solution and standard to the

industry in order to enable field interoperability for on-going deployments• Flexibility, scalability and backwards compatibility (where feasible) are

critical• Security should be built into the standard, not an afterthought.



OpenFMB Specification – The Key Components

Reference Architecture

Use Cases

Platform Independent Model (Semantic Model, Messages & Services)

Platform Specific Model (DDS, MQTT and Hybrid, etc.)

Implementation Guidelines



OpenFMB – Reference Architecture

• Duke Energy’s Distributed Intelligence Platform Reference Architecture Volume I: Vision Overview provides a great foundation for the standard development.

• Task Force will need to review the work contributed by Duke, and discuss/decide how to leverage it, and what potential areas may require more work, such as:

– Security Architecture– Node Classification and Interaction Patterns

(EPRI REC-VEN Concept adopted by OpenADR)

– Reference Architecture components – what is informative vs. what is normative for the standard

– Reference Model relative to other standards

• Leverage similar work done from other IoT standards initiatives.



OpenFMB – Use Cases

March 4, 2015

NAESB OpenFMB TF

• Use Cases will drive the content of OpenFMB 1.0 Specification in terms of model, messages and services. We must decide a subset of use cases in the following categories to have a manageable scope.

• Use Cases will fall into the following two categories: – Functional:

• DER Integration• MicroGrid• Distribution Management • DSPP Enablement• Transactive Energy Enablement• ……

– Technical: • Device Management• Network Management• Security Management• ……


OpenFMB – Platform Independent Model

class Duke

Agreement

Customers::CustomerAgreement

+ loadMgmt :String [0..1]

Document

Customers::CustomerAccount

+ billingCycle :String [0..1]+ budgetBill :String [0..1]

OrganisationRole

Customers::Customer

+ kind :CustomerKind [0..1]+ pucNumber :String [0..1]+ specialNeed :String [0..1]+ status :Status [0..1]+ vip :Boolean [0..1]

Location

Customers::ServiceLocation

+ accessMethod :String [0..1]+ needsInspection :Boolean [0..1]+ siteAccessProblem :String [0..1]::Location+ direction :String [0..1]+ electronicAddress :ElectronicAddress [0..1]+ geoInfoReference :String [0..1]+ mainAddress :StreetAddress [0..1]+ phone1 :TelephoneNumber [0..1]+ phone2 :TelephoneNumber [0..1]+ secondaryAddress :StreetAddress [0..1]+ status :Status [0..1]+ type :String [0..1]::IdentifiedObject+ aliasName :String [0..1]+ mRID :String [0..1]+ name :String [0..1]

AssetContainer

Metering::EndDevice

+ amrSystem :String [0..1]+ installCode :String [0..1]+ isPan :Boolean [0..1]+ isVirtual :Boolean [0..1]+ timeZoneOffset :Minutes [0..1]

Metering::Meter

+ formNumber :String [0..1]

IdentifiedObject

Metering::UsagePoint

+ amiBillingReady :AmiBillingReadyKind [0..1]+ checkBilling :Boolean [0..1]+ connectionState :UsagePointConnectedKind [0..1]+ estimatedLoad :CurrentFlow [0..1]+ grounded :Boolean [0..1]+ isSdp :Boolean [0..1]+ isVirtual :Boolean [0..1]+ minimalUsageExpected :Boolean [0..1]+ nominalServiceVoltage :Voltage [0..1]+ outageRegion :String [0..1]+ phaseCode :PhaseCode [0..1]+ ratedCurrent :CurrentFlow [0..1]+ ratedPower :ActivePower [0..1]+ readCycle :String [0..1]+ readRoute :String [0..1]+ serviceDeliveryRemark :String [0..1]+ servicePriority :String [0..1]

+ServiceLocation

0..1+UsagePoints

0..*

+CustomerAgreement

0..1

+UsagePoints

0..*

+UsagePoint

0..1

+EndDevices

0..*

+Customer

1

+CustomerAccounts

0..*

+CustomerAccount 1

+CustomerAgreements 0..*

OpenFMB Semantic Model

IEC CIM

IEC 61850

IEEEC37 IEEE

1588

DNP3

……



OpenFMB – Platform Specific Model

March 4, 2015

NAESB OpenFMB TFOpenFMB

Protocol Specific Message/Services

DDS

CoAP

MQTTREST

XMPP

......

AMQP


OpenFMB – Implementation and Compliance Guidelines• NAESB OpenFMB TF will develop implementation guidelines

• NAESB will look to SGIP to provide framework and guidance on how this should be accomplished.

• NAESB will look to UCAiug to setup an OPenFMB Users Group to help promote, implement, and provide testing and certification services.



TimelineRequirements

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

(TBD)

OpenFMB TF F2F Meeting #2

(TBD)



OpenFMB Roadmap

New Use Cases

2015 – OpenFMB 1.0 2016 – 2017 OpenFMB 2.0

Expanded Models, Messages and Services

Expanded Models/Services and New Protocols

Enhancements

EnhancementsReference Architecture

Use Cases

Platform Independent Model (Semantic Model, Messages & Services)

Platform Specific Model (DDS, MQTT and Hybrid, etc.)

Implementation Guidelines



Next Steps

• We need broad participation in NAESB OpenFMB Task Force– Bi-weekly calls– F2F meetings (TBD)– Contribution to specification– Review and feedback

• We want to manage this to accomplish the goals by the end of this year, with a defined scope and project plan.



Afternoon Break: 14:15-14:30


Open Discussions

• Standards Development Process and Deliverable

• SGIP Annual Meeting November 3-5

Documents

Accelerating Grid Modernization Open Field Message Bus (OpenFMB) Kickoff Meeting March 5, 2015