Open Smart Grid (OpenSG) Technical Committee Plenary November 2010 Agenda
8:00am – Safety & Welcome (Chris)
8:10am – UCA Chairman’s Report (Erich)
8:20am – Logistics / Announcements (Chris)
8:30am – SEP 2.0 Update(Tobin)
8:50am – 2010 Objectives to date (Chris K)
9:00am – WG and TF plan for the week
SG Communications (15min)
SG Conformity (15min)
SG Security (15min)
SG Systems (15min)
Q&A
2 Welcome & Safety
Welcome & Safety
CPR
911
Exits & Meeting Point UCA Chairman’s Report
Erich Gunther
4 UCAIug Corporate Supporters
UCAIug Corporate Supporters By Region
UCAIug Corporate Supporters UCAIug Members
Linear Trend Line
UCAIug 2009 User Accounts By Region UCAIug Membership Composition UCAIug Budget
Historic 2010 Proposed Where the Budget Goes
Projected Expense Professional Fees $9,000 Customer Relations $8,000 Web Presence $103,400 Marketing $31,000 Meetings $270,816 Testing Committee $75,000 Expansion Plan to Establish Utiliy Forum $30,000 Daily Operations $267,930 Bank and Credit Card Fees $15,400
Total Projected Proposed Budget Expenditures $810,546
Projected 2009 Income Less Expenditures -$98,826
Balance brought forward from 2009 operations $150,000 Projected Balance at end of 2010 operations $51,174 Announcements
Internet Information
SSIDs
WestinMeetingRooms
WestinGuestRooms
New OpenSG Simulations WG SEP 2.0 OpenSG Update
Tobin Richardson Director, Smart Energy ZigBee Alliance trichardson@zigbee.org
November 2, 2010
11 11 ZigBee Smart Energy Profile Update
1.0 Implementation & Market Support
1.x evolution
2.0 Development and Status ZigBee Smart Energy Public Application Profile 1.0
More than 70 SE-certified devices now
Market implementation support in Texas – ZigFesTX Go-to- Market
Four ZigFesTX under our belt – May through November
Last ZigFesTX for 2010 in Houston, next week – CenterPoint hosting
1.x Revision Nearly Ratified
First certification event passed; now to Architecture Review and SE WG review – includes features like Multiple ESIs, Over- the-Air Bootloader, CCBs
Continuing demand for increased functionality in 1.x profile evolution
Prepay; multi-fuel; tunneling, etc.; ongoing evaluation of timing/scope and appropriate level of effort. SEP 2.0
Recap development process
Current Status
Ongoing work items
14 ZigBee Process
Market Requirements Document (MRD)
Technical Requirements Document (TRD)
0.7 version of Specification (Interop-Ready)
0.9 version of Specification (Certification- Ready)
1.0 version of Specification (Certified Devices) Current Status – 2.0
SEP 2.0 TRD comment resolution nearing completion and reballot
SEP 2.0 Application Specification (App Spec):
Letter ballot received ~2000 comments
Resolution divided into sections led by champions
Significant progress made on resolving comments
Several meetings (face-to-face this past week in California)
Working closely with various external groups (NAESB and IEC, for example)
The negative: has not been easy – requirements are a moving target with many external factors and internal contentious items, often caught in middle (61968 vs 61850, for example)
Several test events have occurred for IP stack
First interop of SE 2.0 Profile event last week!!
16 Current Status (cont’d)
Ramping up collaboration with multiple MAC/PHYs (HomePlug, Wi-Fi) on developing profile (app support specification)
Continuing work with harmonization efforts with sister organizations (and newly emerging ones)
OpenHAN
NAESB
PAPs
etc. Major Work Items Ongoing
Harmonizing with SAE on plug-in vehicle comms
Harmonizing with DER / inverter / 61850 / SunSpec
Harmonizing with NAESB
Harmonizing with NIST PAPs (3, 4, 9, 10, 11, etc.)
Cleanup and additional detail (transactions, schemas, boot-strap, device discovery, resource discovery, multiple ESIs, etc.)
Certificate Authority selection (downselection, finalizing negotiations – will
announce publicly soon) 18 External Influences - Reminder
OpenSG
US NIST and SGIP
NAESB
IEC
EU (ESMIG, etc.)
AU (WSAA, etc.)
SAE
19 External Outreach
Working with many SDOs
Developing new standards:
IETF ROLL / RPL
IETF CoRE / CoAP
IETF 6LoWPAN (ND, etc.)
Refining existing standards:
IETF PANA
IETF TLS
IEC 61968 (CIM)
IEEE 802.15.4
20 Recent European/Int’l Collaboration
IEC – TC57 – WG 12 – in process
CEN/CENELEC/ETSI – European focus
Liaisons in place and in process
M441 European Mandate
Many others in progress and ongoing collaboration
UK Smart Metering Mandate – Prospectus Key Upcoming Events/Milestones
TRD reissue & public comment (30- day re-ballot when complete)
0.7 AppSpec reissue & public comment (30-day re-ballot when complete)
ZigFesTX – Houston, Nov. 9-11, CenterPoint
ZigBee Alliance member meeting – Nov. 15-19, Dublin, Ireland
More liaisons, ever-expanding tent of participants in SE 2.0 profile Thank You!
www.zigbee.org Reveiw: 2010 OpenSG Strategic Goals
General conformity requirements documents
Complete HAN 2.0 SRS
Expand OpenHAN to be all encompassing around edge devices – evolve from HAN to include C&I
Complete OpenADE SRS 1.0 and associated compliance requirements
Focus on program management 2010 OpenSG WG Specific Objectives
SG Systems OpenADR Build CIM into OpenADR specifications Harmonize OpenADR with other TFs (OpenHAN, OpenADE, Conformance, etc.) OpenADE OpenADE 1.0 SRS: February 2010 OpenADE 2.0: User Requirements Q2 2010 OpenADE 2.0: System Requirements / Service Definitions Q4 2010 OpenHAN OpenHAN 2.0 SRS ratified by OpenSG
SG Communications Continue work on SG-NET System Requirements Specification (interim release 5) Get the Network Interoperability task group work organized for next quarter Meet with NIST on PAP 1 and agree to SG-NET responsibilities
SG Conformance Agree upon (simple) definitions for Conformance and Interoperability and “Abstract Test Cases” and “Concrete Test Cases” Agree upon a language (framework, taxomomy) upon which to build abstract test cases Edge Conformance Complete Certification Process Reference Manual
SG Security Establish coordinated support for other OpenSG working groups & task forces Revise the AMI Security Profile Address additional security profiles as produced by ASAP-SG Shaping 2011 OpenSG Strategic Goals
SG Simulations WG
define how edge devices integrate as a closed-loop system
Impact on distribution system and closed loop design constraints for stability
Communications Strategy for Broad Coverage (Dist Sys level)
-SG comms work with UTC/WCA
Integrated Demand Response/Advanced Load Control
Address edge devices as an integrated systems approach incorporating all edge devices and market interfaces/services
ASAP-SG Security Profiles next round, weave into SG Security/SGIP-CSWG
Enterprise Information Management w.r.t. CIM interoperability projects, Data Reference Architecture
Open Source repository for test cases and lab artifacts 2011 Meeting Dates
March 7-10, San Antonio, TX (SWRI)
Not yet confirmed, looking for alternative
July 18-21, Vancouver, BC (BC Hydro, DeYagher)
November 14-17, Buffalo? Pittsburgh? Baltimore? Charlotte? Atlanta? Jacksonville?
Note: These are tentative dates. Please do not plan travel until you receive a registration notice. SG Communications SG Communications Charter
Identify and articulate Smart Grid communications requirements and work with Standards Development Organizations (SDOs) and vendor consortiums to realize those requirements.
Engage with the NIST Smart Grid Roadmap activities and address communications related OpenSG tasks in the various NIST Priority Action Plans (PAPs).
Slide 29 Don Sturek, PG&E SG Communications Organization
Chair Don Sturek, PG&E
Task Groups: SG-NETWORK: Chair: Matt Gillmore, Consumers Energy Vice Chair: Ron Cunningham, AEP Network Interoperability: Tom Herbst, Silver Spring Networks
Slide 30 Don Sturek, PG&E Progress since Detroit
SG-NETWORK
NIST PAP 2 Tasks: Interim release 4 released 1400 additional requirements created Draft white papers on RF Spectrum Allocation for Smart Grid use cases Database for Communication Requirements modeling has had major improvements. System Requirements Specification document is progressing to align better with the 2800+ requirements identified to date.
Slide 31 Don Sturek, PG&E Objectives for This Meeting
SG Communications
Network Interoperability Task Group deliverables for the next quarter
SG-NETWORK
Continue work on the SG-NETWORK System Requirements and System Requirements Specification (SRS) for Interim Report #5
Support NIST with PAP 1 & 2 for completion by end of year.
Network Interoperability
Agree on deliverables for the next quarter
Plan work to meet deliverables
Slide 32 Don Sturek, PG&E SG-NETWORK Objectives This Week
Joint SG-SEC/SG-NETWORK meeting to review security portions of requirements
System requirements Specification working sessions
Vet SG-Network System requirements for version 4.1
Discuss the use of SG-Network requirements for RF Spectrum allocation white papers.
Review Requirements Database
Plan scope of the next interim release
PAP 2 joint meeting Thursday
Slide 33 Don Sturek, PG&E SG Communications Agenda
Monday, PM1 (SG Communications) Boot Camp Note: Session is an overview for newcomers
Tuesday
10:30-noon SG Communications & SG-Network agenda review
1-3pm SG Security / SG-Network – e.g. CIA vetting
3:30 – 5:30 System Requirements Specification (DA content review)
Slide 34 Don Sturek, PG&E SG Communications Agenda
Wednesday
8-10am Requirements Database Working session – release planning, payload ties to interfaces/dataflows, user feedback
10:30-12noon – SG-Network requirements and Spectrum Requirements
1-3pm System Requirement Specification & payload attribute data review
3:30 -5pm Requirements and SRS working session
6-8pm TBD additional meeting
Slide 35 Don Sturek, PG&E SG Communications Agenda
Thursday
8-10am SG Network / PAP 2
10:30-noon SG Network / PAP 2
Slide 36 Don Sturek, PG&E SG Conformity Bruce Muschlitz July 2010
SG Conformity Charter
Certification requirements for SG systems
Develop Quality Assurance Plan
Explore use of a Product Mark (logo)
Create repository of best practices
Define sustainable conformity programs
Provide coordination between OpenSG and 61850 and CIM testing groups
Explore tester accreditation
Slide 38 Bruce Muschlitz, EnerNex July 2010
SG Conformity Overview
Chair Bruce Muschlitz, EnerNex Vice chair Zahra Makoui, PG&E
Task Groups: Edge Conformity: Phil Beecher, John Lin Security Conformity: Bobby Brown, Sandy Bacik Enterprise Conformity: Mark Ortiz, (co-chair presently vacant)
Slide 39 Bruce Muschlitz, EnerNex July 2010
Progress since Detroit
Paused main conformity meetings to focus on CPRM (Certification Process reference Manual) Identified ITU standard X.291 (IEC 9646-2) as basis for abstract test definitions Progressed CPRM to Rev.9 (now on hold awaiting NIST SGIP TCC IPRM completion) (IPRM=Interoperability Process Reference Manual) CPRM to be restructured as modification to IPRM to avoid duplicative work) Security Conformity Group progress slowed due to lack of participation Mail lists: [email protected] SGCONFORMITY SGCONFORM-EDGE SGCONFORM-SEC SGCONFORM-ENT Working with NIST TCC (Testing and Conformance Committee Ensure no duplication of efforts TCC WG3 Assessment of NIST standards for suitability toward interoperable products TCC WG4 Interoperabilty Process Reference Manual TCC WG5 Laboratory qualification criteria
Slide 40 Bruce Muschlitz, EnerNex July 2010 Objectives for This Meeting
Status update on NIST TCC IPRM completion
Discuss long-term relationship with SGIP
Restructure CPRM as additions/changes to IPRM
Outline Quality Assurance Program for OpenSG
Discuss how Conformity WG can help create ITCA (Interop Testing and Certification Authority) for OpenSG groups
Roundtable – Requests from the OSG Working groups on conformity needs
Slide 41 Bruce Muschlitz, EnerNex July 2010
SG Conformity Agenda
Monday, PM1 (SG Conformity Boot Camp)
Tuesday, AM2 (SG Conformity Main meeting)
Tuesday, PM1 (Edge Conformity)
Tuesday, PM2 (Joint Enterprise / Edge Conformity)
Wednesday, AM1 (Joint Network Interop / Enterprise / Edge Conformity)
Wednesday, AM2 (Joint Enterprise / Edge Conformity)
Wednesday, PM1 (Joint Edge Conformity / Network Interop )
Thursday, AM1 (Security Conformity)
Thursday, AM1 (SGIP TCC WG4, IPRM)
Slide 42 Bruce Muschlitz, EnerNex November 2010
Edge/Enterprise Conformity TG Charter
Develop Certification, Testing and Interoperability Policy and Requirements for ADE, ADR, AMI-Ent and HAN
Slide 43 Phil Beecher November 2010
Edge/Enterprise Conformity TG Overview
Chair
Phil Beecher, (Edge), Mark Ortiz (Ent)
Co-chair
John Lin, (Edge), John Simmins (Ent)
Collaboration:
OpenADE, OpenADR, OpenHAN, AMI-Ent
Slide 44 Phil Beecher November 2010
Edge / Enterprise Conformity Activity
Edge and Enterprise Conformity Task Groups worked on a single combined Certification Process Reference Manual
Content frozen, pending release of SGTCC IPRM
Next step will be ensuring CPRM is complementary to IPRM
Abstract Test Case Documents development in progress
Started work on OpenHAN document
Need to agree scope, then start work on OpenADE and OpenADR
Slide 45 Phil Beecher November 2010
Objectives for November F2F Meeting
Edge/Enterprise Conformity TG work sessions Agree Scope of Abstract Test Case documentation Define Test Methodologies and requirements for OpenADE, OpenADR and Enterprise.
Other Joint Sessions
Network Interop Understand scope of work Overview of Test Methodologies Collaboration on Abstract Test Cases
Slide 46 Phil Beecher November 2010
Edge/Enterprise Conformity TGAgenda
st Monday, Nov 1 PM2, SG Conformity Boot Camp Note: Session is an overview for newcomers nd Tuesday, Nov 2 AM2 SG Conformity Work Session PM1 Edge Conformity, Review OpenHAN Test Cases Document PM2 Edge/Enterprise – Overview of test scenarios / methodologies rd Wednesday, Nov 3 AM1 Edge/Enterprise/Network Interop – Enterprise test scenarios / methodologies
AM2, Edge/Enterprise - Abstract Test Cases PM1, Edge/Network Interop – HAN test scenarios / methodologies
Slide 47 Phil Beecher November 2010 Edge/Enterprise Conformity TG
Email reflector:
GotoMeeting information:
Provided via email to all members of Edge and Enterprise Conformity reflector
Announced on the OpenSG sharepoint in the Edge Conformity calendar
Meeting times:
Meeting Day PST MST CST EST
Edge/Ent Wednesday 10:00 am 11:00 am noon 1pm Conformity
Meeting minutes and documents: http://osgug.ucaiug.org/conformity/edge/Shared%20Documents/Forms/AllItems.aspx
Slide Phil Beecher 48 SG Security Darren Highfill SG Security Charter
Scope: Develop detailed security and assurance requirements and security best practice guidance for organizations throughout the lifecycle of smart grid technology.
Technology-specific, but vendor-agnostic
Feed and accelerate SDO work (IEC, IEEE, etc.)
Mission: Influence development of a higher level of cyber security and governance tied to mission reliability than is required for traditional IT applications.
Slide 50 Darren Highfill, SCE SG Security Overview
Chair Darren Highfill, SCE Vice Chair Bobby Brown, EnerNex
Secretary Nick Gerbino, Dominion
Task Forces: AMI-SEC Security for Advanced Metering Infrastructure systems and components CyberSec-Interop Configuration profiles for security features and functionality
Slide 51 Darren Highfill, SCE Progress since Detroit, MI
CyberSec-Interop Task Force
Published IPSec Configuration Profile document
Developing configuration profiles for Syslog, and LDAP
Usability Analysis Task Force
Completed review of Third Party Data Access Security Profile
Beginning review of Distribution Management Security Profile
AMI Security Profile
Mapped to NISTIR and NERC CIP
SG Network support
Continued collaboration with SG Network, PAP02, and CSWG on C-I-A rankings
Embedded Systems Interest Group
New work being scoped and defined
Slide 52 Darren Highfill, SCE Objectives for November F2F Meeting
Support relationships with other OpenSG working groups and task forces
SG Network
Others?
Review / share information on industry issues
ASAP-SG progress & status
Stuxnet, vulnerability handling / responsible disclosure
Consider needs for new task forces
Embedded Systems
Interfaces with external groups
NIST CSWG
NERC CIP SDT
IEC TC57 WG15
Slide 53 Darren Highfill, SCE SG Security Agenda Day Timeslot Subject Group Monday 1500‐1700 SG Security Boot Camp SG Sec WG Tuesday 1030‐1200 Agenda & Status updates SG Sec WG IEC TC57 WG15 Usability Analysis TF 1300‐1500 SG Sec / SG Net Joint Session Wednesday 0800‐1000 CyberSec‐Interop SG Sec WG ASAP‐SG: Blueprint review NERC CIP SDT Update 1030‐1200 Stuxnet Demo & Discussion SG Sec WG Software Security 1300‐1500 NIST CSWG Update SG Sec WG Embedded Security Interest Group Vulnerability Disclosure & Information Handling 1530‐1730 Planning & Prioritization SG Sec WG
Slide 54 Darren Highfill, SCE SG Systems WG
EIM (new) – Greg Robinson
ADE – Dave Mollerstuen or Steven van Ausdall
ADR – Albert Chiu or Ed Koch
HAN – Erich Gunther Smart Grid Challenges…
Requires Integration – LOTS of integration
Onslaught of new applications and technologies
AMI, MDMS, HAN, DR, ADE, etc.
In a complex IT environment
A plethora of changing technologies with disparate methodologies/philosophies over many years
Many custom systems, legacy technologies
Departmental objectives tend to encourage “silos”
Project funding gives priority to project-focused implementations
Without fitting into an enterprise context
Aging / outsourced systems and IT workforce
Historically, extremely low R&D expenditures It’s More Than Just Technical Matters
Driving Forces Restraining Forces
1. Consistent enterprise-wide data 1. Lack of stable industry standard definitions 2. One version of the truth 2. Vendor’s way = lower project costs 3. Access to data regardless of source 3. Vendors pushing for ‘proprietary lock-in’ 4. Business transformation agility 4. Consultants pushing to be ‘thought leaders’ 5. Reduced project implementation costs 5. Hours-sold revenue driving System Integrators 6. Reduced maintenance costs 6. Internal system experts want to remain experts 7. Reduced IT risks 7. Project managers striving for control
8. Availability of external services Status Quo 8. Inertia – why change? 9. Scalable business process automation 9. Our situation’s unique – standards hinder us 10. Scalable business activity monitoring 11. Accurate reporting – regulatory, KPIs For further information, please refer to the article on page 56 of the January issue of Utility T&D Automation & Engineering: 12. Mergers and acquisitions http://www.uae-digital.com/uae/200801/ Defining EIM (Gartner)
Enterprise Information Management (EIM) is: An organizational commitment to structure, secure and improve the accuracy and integrity of information assets, to solve semantic inconsistencies across all boundaries, and support the technical, operational and business objectives within the organization's enterprise architecture strategy. A commitment to EIM is recognition that information in the enterprise is as important as process (application development) and infrastructure (technology) Overall EIM Framework
Enterprise Business Enterprise Vision & Enterprise Enterprise Business Enterprise & IT Core Strategy Architecture & IT Organizations Infrastructure Processes
EIM Vision & EIM Core EIM Governance EIM Organization EIM Infrastructure Strategy Processes
Data Quality Information Vision Sponsorship CSFs & KPIs Architecture Data Integrity Blueprint Management Data Security & Structure Mission Stewardship Protection (Virtual, Data Lifecycle Hybrid……) Technologies Management (DBMS, Content Policies, Mgmt, ETL, EAI, Roles & Strategy Principles & Data Movement EII, Data Responsibilities Tenets Modeling, BI/DW, Semantics Collaboration…..) Management Goals & Functional Alignment Database Objectives Services Management Knowledgebase Master Data and Repositories Management Value Business Value Structure Information Propositions and Relationship Services Management Standards & Best Services & Support Practices New EIM Task Force Organizational Meeting
Meets during second slot of SG-Systems WG
(3:30 on Tuesday)
Agenda
Overview of EIM
Roundtable to hear about experiences and expectations of members
Form strategy that will help members to mitigate risk and lower costs for their companies
Establish key points for charter
Develop milestones
Subsequent meeting(s) possible on Wednesday if members are available SG Systems – OpenADE Dave Mollerstuen, Chair OpenADE Overview
Charter: The Open Automatic Data Exchange (OpenADE) Task Force within the UCAIug Open Smart Grid Subcommittee is responsible for developing business requirements, use cases, system requirements specifications, and reference definitions that allows a consumer to grant a third party access to their electric data and in accordance with that authorization, the utility to deliver the consumer data to the third party using a standard interoperable machine-to-machine (M2M) interface
Chair: Dave Mollerstuen, Tendril Networks: [email protected]
Co-chair: Steve Van Ausdall, Xtensible Solutions: [email protected]
Participants
Utilities
Vendors
Regulators
Consumer Advocates
Meetings: Weekly (?) webconference working meetings: Thursdays 10a PT / 1p ET
Mailing List: OpenADE list at
Slide 62 OpenADE TF Progress since Detroit (July 2010)
Ongoing contributions (data model, manpower) to PAP10 Energy Usage Information model in NAESB
Helped establish, initiate NAESB Energy Services Provider Interface (ESPI) Task Force: to standardize requirements, services initially developed in OpenADE.
Slide 63 OpenADE TF Objectives for November F2F Meeting
Review updated PAP10 Energy Usage Information Model “Evangelize” NAESB ESPI work Develop plan for next four months (through Spring 2011 OpenSG F2F), twelve months Weekly OpenADE webconference meetings have been “on hiatus” this fall, pending initial traction in ESPI. Is it time to reconvene requirements effort towards OpenADE 2.0? Sample implementation of ESPI standard? Testing and Certification for OpenADE / ESPI? Ongoing discussion of OpenADE 2.0 scope
Slide 64 OpenADE TF OpenADE TF Agenda
Day Date Time Topic Tuesday Nov 2 3:30p to 5:30p • Review SGIP PAP10 and Energy Usage Information Model • “Evangelize” NAESB ESPI Work Wednesday Nov 3 1:00p to 3:00p • OpenADE Roadmap (four month, twelve month) • OpenADE 2.0 Scope
Slide 65 OpenADE TF SG Systems - OpenADR Albert Chiu OpenADR Charter
Identify and articulate DR signals requirements (based on LBNL OpenADR specification) and work with Standards Development Organizations (SDOs) and vendor consortiums to realize those requirements.
Engage with the NIST Smart Grid Roadmap activities and address communications related OpenSG tasks in the various NIST Priority Action Plans (PAP09, etc.).
OpenADR focuses on DR from an application point of view and specifically on the interactions between the Utility and Facility whereas other groups within UCAIug are more focused on platforms or systems that may support DR applications within their specific domains.
Work closely with horizontal OpenSG groups. Some overlap with OpenHAN (facility side) and AMI Ent (Utility head end side).
Develop requirements and harmonize with CIM efforts.
Slide 67 OpenADR Organization
Chair Albert Chiu, PG&E Vice chair Ed Koch, Akuacom
Task Groups: Use Case Team Incrementally build up a set of generic use cases that are expressed in similar format for the scope of AMI-Enterprise. Ralph Martinez ([email protected]), chair Kay Stefferud ([email protected]), co- chair
System Requirement Specification (SRS) Team Generate System Requirements Specification Joe Zhou ([email protected]), chair
Services Definition Team Define integration requirements and service definitions Jerry Gray ([email protected]), chair Shawn Hu ([email protected]),co chair
Slide 68 Progress since Detroit
Completed OpenADR SRS version 1.0
Documents was approved by OpenSG TC on September
Using LBNL OpenADR Specification as basis and utilizing CIM where applicable
Utilized requirements from a number of different efforts – NAESB, EIS alliance, SEP 2.0, EMIX, WS-Calendar
Continue to work with IRC to merge the wholesale and retail data table in NAESB office
Completed OpenADR SD draft version 1.0
Common
Web services implementation Profile
Slide 69 Objectives for This Meeting
NIST PAP09 joint meeting
OpenADR TF updates
NAESB updates
Zigbee/SEP updates
OASIS updates
Discuss OASIS EI TC draft document
Discuss NAESB retail and wholesale data models
Continue Service Definition work
Common
Web services implementation Profile
Finalize comments period and prepare SD for voting
Target date: December
Slide 70 OpenADR Agenda
Monday, PM (SG-System) Boot Camp Note: Session is an overview for newcomers Tuesday, PM (PAP09/OpenADR joint session) Wednesday, AM1 (OpenADR) Continue SD work Wednesday, AM2 (PAP09/OpenADR joint session) Wednesday, PM1 (OpenADR) Continue SD work Wednesday, PM2 (OpenADR) OpenADR 2.0 vision Thursday, AM (OpenADR) Finalize SD work Plan for next F2F
Slide 71 SG Systems – OpenHAN TF Erich Gunther / Mary Zientara OpenHAN TF Overview
Chair Erich W. Gunther, EnerNex – [email protected]
Co-chair Mary Zientara, Reliant Energy - [email protected]
Task Groups: OpenHAN 2.0 Mary Zientara, Reliant Energy, chair Charlie Smith, GE, co-chair Charles Spirakis, Google, co-chair Zahra Makoui, PG&E, co-chair OpenHAN TF
Email reflector:
Web meeting information:
Provided via email to all members of OpenHAN reflector
Announced on the OpenHAN calendar
Web meeting times:
Meeting Day PST MST CST EST OpenHAN 2.0 Tuesday 9:00 am 10:00 am 11:00 am noon
Meetingupdate minutes and documents:
http://osgug.ucaiug.org/sgsystems/openhan/default.aspx Scope of HAN SRS in the NIST conceptual model
75 UCAIug HAN SRS v2.0
Purpose
Define the system requirements for an open standard Home Area Network system
Promote open standards-based HANs that are interoperable
Provide the vendor community with a common set of principles and requirements around which to build products
Ensure reliable and sustainable HAN platforms
Support various energy policies in a variety of states, provinces, and countries
Empower consumers to manage their electricity consumption by giving them the information and control they need to make decisions on their energy use
76 OpenHAN History
2007 2008 2009 2010
OpenHAN TF is August 2008 June 2009 Jan – July 2010 formed to UtilityAMI 2008 Utility AMI 2008 HAN SRS OpenHAN 2.0 collaboration develop system HAN SRS v1.04 selected as a effort requirements v1.04 released customer domain standard for the HAN in the NIST Smart Grid August 30, 2010 Interoperability Standards UCAIug HAN SRS v2.0 Roadmap ratified and released
October 2009 OpenHAN 2.0 formed to develop the next version of the HAN SRS
77 OpenHAN 2.0 Effort Over 130 individuals representing over 80 companies participated in the development of the HAN SRS v 2.0 over a 10 month period Participating Companies
4home DTE Energy I’m in Control Proto6
Aclara Duke Infineon Technologies PSU
AEP Eaton Invaluable Technologies Reliant Energy
APS Ecologic Analytics, LLC Itron RIM
Aridhio Technologies Emerson /White-Rogers Kaapco / ASR Systems Sacramento Municipal Utility District
AT&T emeter KCP&L SCE
BC Hydro Enernex Konnected Universe LLC Schneider Electric
BGE EPRI LG Electronics USA. Inc. Southern Company
BSH FPL LonMark International Subzero
CPUC Ford MicroSoft SunSpec Alliance
Capgemini GE MultiSpeak Tendril
Carrier General Motors NextGEN Consultancy Pvt. Ltd. Trilliant
CenterPoint Georgia Power Co. N-Dimensions Solutions UISOL
Cisco google NV Energy U-SNAP Alliance
Coincident, Inc Granitekey Oncor Electric Delivery Visible Energy
Comverge, Inc. Gridata Inc PA Consulting Xtensible.net
Consumers Energy heyCoop, LLC Panasonic ZigBee Alliance
Certicom Corp Home Automation, Inc Pentair Water Pool & Spa
Deloitte Consulting Honeywell People Power
DotUI HP PG&E
Drummond Group Hypertek Inc Portland General Electric
DS2 IBM Progress Energy
UCAIug HAN SRS v2.0 The audience for the HAN SRS include:
Utilities considering deploying AMI systems that interact with HANs
Vendors that make AMI systems for Utilities that interact with HANs
Vendors that make consumer products (e.g. programmable communicating thermostats, energy management systems, load control switches, in-home displays, smart appliances, Plug-in Electric Vehicles (PEV), distributed energy resources (DER), etc.)
Service Providers developing smart grid enabled programs for consumers (e.g. demand response, energy management, pre-pay, PEV programs, DER programs, etc.)
Policy makers looking to understand how Utility AMI deployments that interact with HANs benefit and impact consumers
Industry alliances and standards organizations
NIST Smart Grid Interoperability Panel (SGIP) activities (e.g. Smart Grid Architectural Committee (SGAC), Cyber Security Working Group (CSWG), Smart Grid Testing and Certification Committee (SGTCC), etc.) 79 UCAIug HAN SRS v2.0 Architectural Considerations
HAN SRS applies from the edge of the AMI System, where the Energy Services Interface (ESI) resides, to all relevant HAN Devices in the premises
Energy Services Interface (ESI)
o An interface which enables communication between authorized parties and HAN devices that are registered to it rd o There may be more than one ESI in the premise (e.g. Utility ESI, 3 party ESI)
o Utility ESI – provides interface between the Utility AMI network and HAN devices, including the AMI meter
o Other ESI – provides interface between other communication media (e.g. internet, cell phone, EMS, etc.) and HAN devices registered to it
80 Enrolled HAN Device (must be Registered)
Registered HAN Device (must be Comissioned)
This figure shows the type Commissioned of communication a HAN HAN Device Device may engage in, which is dependent upon its relationship with the ESI and Energy Services the Service Provider. Interface (ESI)
Service Provider Network (e.g. AMI Network, Internet, etc.)
Communication Types
Service Provider Messages including Control Signals (Two-way communications between Service Provider and Enrolled HAN Devices)
Consumer Specific Information (One-way and Two-way communications between ESI and Registered HAN Devices as well as among Registered HAN Devices)
Public Information (One-way communications to Commissioned HAN Devices)
Service Provider to ESI (Two-way communications to the ESI which may elicit further communication between the ESI and Registered HAN devices and Public Information from 81 the ESI to Commissioned HAN devices) UCAIug HAN SRS v2.0
Commissioned Registered Network admission of HAN Authentication established device on HAN between HAN device and ESI
Pre‐commissioned Enrolled Service Provider granted rights Non‐HAN operation of device to access HAN device
82 UCAIug HAN SRS v2.0 HAN System Requirements . Application Requirements
. Communication Requirements
. Security Requirements . Performance Requirements . Operations, Maintenance, and Logistics Requirements
83 Mapping Requirements to Functional Devices
In order to provide guidance to service providers and vendors, the OpenHAN Task Force mapped each requirement to functional HAN Devices in tables at the end of each requirement section.
The tables indicate which requirements the OpenHAN Task Force considered necessary for the Commissioning Process (CP), for the Registration Process (RP), for Security (S), for application functionality (BF), as Optional (O), or if the requirement was Not Applicable (NA) for the function of the device.
These tables may be used as a template or starting point for Service Providers in their discussions with vendors and in their procurement process.
Vendors may use these tables as guidance for producing devices and software which enables basic HAN functionality and for providing additional functionality in order to provide competitive differentiation.
The tables are for reference only and should not limit the needs of Service Providers nor limit vendor innovation. 84 Mapping Requirements to Functional Devices
Table 3: Control Requirements Mapping
HAN AMI Utility Load Meter Smart ID HAN System Requirements ESI PCT IHD EMS Mete EVSE PEV EUMD ESI Control (non- Appliance r electric)
1 HAN Device shall accept Control Signals from one or more authorized NA NA BF NA BF BF NA NA BF BF BF NA parties (e.g. Utility, Service Provider, EMS, Consumer).
2 HAN Device shall limit or reduce energy consumption in response to NA NA BF NA BF BF NA NA BF BF BF NA Control Signal receipt.
3 HAN Device shall resume previous operational state (as appropriate) following receipt of Control Signal NA NA BF NA BF BF NA NA BF BF BF NA that cancels, expires, or overrides a previous Control Signal in effect
4 HAN Device shall acknowledge receipt of Control Signal, when NA NA BF NA BF BF NA NA BF BF BF NA requested.
5 HAN Device shall acknowledge execution of Control Signal, when NA NA BF NA BF BF NA NA BF BF BF NA requested.
85 Questions????
UCAIug HAN SRS v2.0 is located on the OpenHAN sharepoint: http://osgug.ucaiug.org/sgsystems/openhan/default.aspx
86 Q&A