OpenSG - SG Communications May 2010 Slide 1 SG Communications DC Meeting AM2 Session Tuesday 5/4/2010 Network Interoperability

OpenSG - SG Communications SG Communications Tuesday AM2 Agenda Review SG Communications structure within UCAiug Overview of this weeks meeting schedule Overview of Network Interop Task Force

OpenSG - SG Communications UCAiug Organization Overview

OpenSG - SG Communications February 2010 Slide 4 This Weeks SG Communications Agenda Monday, PM2 (SG Communications) –Boot Camp –Note: Session is an overview for newcomers Tuesday, AM2 (SG Communications) –Network Interop Overview –SG-Network Overview Tuesday, PM1 (SG-NET) –Work submitted overview Pre-pay use cases DA use cases Meter Event use cases Outage Manangement Tuesday, PM2 (SG-NET) –Break into teams to review submitted work

OpenSG - SG Communications SG Communications Agenda Cont. Wednesday, AM1 (SG-NET) –Interim Release 3 scoping Wednesday, AM2 (SG-NET) –Assignments for Interim Release 3 Wednesday, PM1 (SG-NET) –Requirements Database overview –FAQ review Wednesday, PM2 (SG-NET) –AOB Shortened time due to Smithsonian Tour Wednesday, PM2 (Net-Interop) –Network Interop meeting

OpenSG - SG Communications SG Communications Agenda Cont. Thursday AM1 (Joint SG-NET / PAP 2) –SG Network work product review Thursday AM2 (Joint SG-NET / PAP 2) –Interim Release 3 scope overview Thursday PM2 (Joint SG-NET / PAP 2) –Section 6 working session for PAP 2’s Jun Deliverable

OpenSG - SG Communications February 2010 Slide 7 Network Interoperability Volunteer for Network Interoperability chair: Tom Herbst, Silver Spring Networks Call for approval in SG-Communications to approve Tom Draft Scope/Charter document Draft requirements document outline (need to revise) Since we are using IP, draft requirements document needs to address the following types of issues as they apply across platforms: –Collection of RFCs used, Security protocols and cipher suites, Application support protocols –Policies, procedures and other considerations (eg firewalls, etc.) that are needed for cross platform deployments –What else? Co-existence for PLC

February 2010 Don Sturek, PG&ESlide 8 Network Interoperability From the draft Scope/Charter: –Identify and articulate premise Network Interoperability requirements. Engage with Standards Development Organizations (SDOs) and vendor consortiums to realize realize implementation specifications and conformance programs based on the requirements. –Premise networks cover commercial, industrial and home area networks employing OpenSG requirements specifications. Ensure that the Network Interoperability requirements cover all market segments. –Align all premise Network Interoperability requirements with the NIST Smart Grid Interoperability Guidelines (Version 1.0 and any subsequent updates).

February 2010 Don Sturek, PG&ESlide 9 Network Interoperability Proposed deliverables: –Creation of a Network Interoperability System Requirements Specification for premise platforms employing multiple physical network interfaces; –Outreach and engagement with SDO’s and vendor consortiums embracing and deploying the Network Interoperability System Requirements to realize standards and conformance programs based on the requirements; –The Network Interoperability Task Force will create, distribute and maintain a schedule and roadmap detailing the tasks and milestones that comprise the group's work; –The Task Force shall assist the Conformity Task Group in their job in defining the test plans and protocol interchange conformance statements (PICs) to apply certification to the components in its charter..

February 2010 Don Sturek, PG&ESlide 10 Network Interoperability System Requirements Specification: –Requirements for certification of single interface platforms MAC/PHY requirements (IEEE compliant, IETF RFC 1042) Network requirements (RFCs for: IPv6, ICMP, UDP, TCP) Platform requirements (eg RFCs for HTTP 1.1, REST architectural description, W3C EXI) –Internetworking requirements Edge routing requirements (RFCs for: OSPF, RIP, etc.) Avoid pairwise interface internetworking requirements –Policies, Best Common Practices, etc. Commissioning, Configuration and Maintenance Edge firewalling (aligned with SG-Security) Design for conformance test (aligned with SG-Conformity) Software/firmware update (aligned with OpenHAN) Security provisioning and revocation (aligned with SG-Security)

February 2010 Don Sturek, PG&ESlide 11 Network Interoperability Call for participation: –Please Don Sturek, Process: –Update/approve the draft Scope/Charter –Review the Requirements Specification Outline, update/approve and begin work –Complete Requirements Specification and approve –Outreach to SDO’s, vendor consortiums: IETF, IEEE, IEC ZigBee Alliance, HomePlug Alliance, HomeGrid Alliance, WiFi Alliance, others embracing our work

OpenSG - SG Communications Questions?

OpenSG - SG Communications SG-Network Overview Scope and Charter for SG-Network within UCAiug –NIST PAP 2 (Wireless standards for the Smart Grid) Supply functional requirements for Smart Grid Networks from a utility perspective Define functional domains within the Smart Grid –Create a System Requirements Specification Provide information to SDO’s (e.g., IEEE P2030) Participation –Utilities –Academia –Vendors

OpenSG - SG Communications SG-Network Work underway –Selected 30+ SG use cases for requirements –Defined 75 total actors from the use cases –Alignment with NIST and other sources to create an architecture diagram for reference –Functional Requirements Definition (300+ identified to date) –Define latency requirements (How long) –Define volumetric information (How often)

OpenSG - SG Communications Examples of work accomplished to date Sample Actors –Smart Meter –Load Management System (LMS) Sample Requirement for a Smart Meter Use Case RequirementHow OftenReliabilityLatency Meter reading Smart Meter shall be able send on demand read information 1 transaction per meter on demand > 98%< 5s Meter reading Smart Meter shall be able to report on demand read communication failure 1 transaction per meter on demand > 98%< 5s Meter reading Residential Electric Smart Meter shall be able to report when scheduled All meters report 4-6 times per day > 98%< 4hr

OpenSG - SG Communications

NIST Conceptual Model

OpenSG - SG Communications Reference Architecture from NISTIR

OpenSG - SG Communications P2030 Smart Grid Comms Reference Architecture

OpenSG - SG Communications SG-Networks Reference Architecture

OpenSG - SG Communications SG-Networks Reference Architecture

OpenSG - SG Communications Deliverables Interim Release 1.0 was published in December 2009 –Requirements and some volumetric and latency requirements Interim Release 2.0 was published in February 2010 –Requirements, volumetric, latency requirements, security, implications and more use cases –Reference Architecture Diagram first published –System requirements specification published Interim Release 3.0 will be published in mid May –Addition of the following use cases: Pre-Payment, Meter Events, DA and Outage Management –System requirements specification updates –Reference Architecture Diagram updates Interim Release 4.0 June –Scope to be determined this week

OpenSG - SG Communications Work Plan for the week Review work submitted for Interim Release 3 Review SG-NETWORK’s Reference Architecture Model Review Requirements Database Plan scope of the next interim release PAP 2 joint meeting Thursday

OpenSG - SG Communications Questions