May 2010
Slide 1
SG Communications Boot Camp
Matt Gillmore11/1/2010
SG Boot Camp Agenda
• Review SG Communications structure within UCAiug• Overview of this weeks meeting schedule• Overview of Network Interop Task Force• Overview of SG-Network• Walkthrough of SG-Networks work
– Requirements– Architecture reference diagram– System Requirements Specification overview
UCAiug Organization Overview
February 2010
SG Communications Agenda Tuesday– 10:30-noon SG Communications & SG-
Network agenda review– 1-3pm SG Security / SG-Network – e.g. CIA
vetting– 3:30 – 5:30 Vetting of 4.1 Sg-Network
requirements
SG-Communications Agenda Cont.• 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
SG-Communications Agenda Cont.
• Thursday –8-10am SG Network / PAP 2–10:30-noon SG Network / PAP 2
Slide 7
Network Interoperability• Tom Herbst from Silver Spring Networks is the chair• Internet Protocol (IP) use is assumed• 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 (from SE 2.0 TRD)– Security protocols and cipher suites (from SE 2.0 TRD)– Application support protocols (from SE 2.0)– Policies, procedures and other considerations (eg firewalls,
etc.) that are needed for cross platform deployments– What else?
• Co-existance for PLC
February 2010
Slide 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
Slide 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
Slide 10
Network Interoperability• Call for participation:
– Please e-mail: Don Sturek, [email protected]– Email reflector - www.smartgridlistserv.org
• OPENSG-SGCOMM-NETINTEROP
• Process:– Update/approve the draft Scope/Charter– Submit to OpenSG TC for approval– Review the Requirements Specification Outline,
update/approve and begin work– Outreach to SDO’s, vendor consortiums:
• IETF, IEEE• ZigBee Alliance, HomePlug Alliance• Other SDO’s and vendor consortiums working on SE 2.0
Questions?
SG-Network Overview• Previously started as AMI-Network with a focus on
network management.• 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
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 (2400+ identified to
date, was 1400+ before the Detroit meeting)– Define latency requirements (How long)– Define volumetric information (How often)
Examples of work accomplished to date• Sample Actors– Smart Meter– Load Management System (LMS)
• Sample Requirement for a Smart MeterUse Case Requirement How Often Reliability Latency
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
NIST Conceptual Model
Reference Architecture from NISTIR
P2030 Smart Grid Comms Reference Architecture
SG-Networks Reference Architecture
SG-Networks Reference Architecture
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 was published in May 2010– Addition of the following use cases: Pre-Payment, Meter Events, DA and
Outage Management– System requirements specification updates
• Interim Release 4.0 was published in June 2010– Addition of the following use cases: DRLC, DA fault isolation and
reconfiguration– System requirements specification re-write
Work Plan for the week• Joint SG-SEC/SG-NET meeting to review
security portions of requirements (C I A)• System requirements Specification working
sessions• Review Requirements Database• Plan scope of the next interim release• PAP 2 joint meeting Thursday
Questions