OpenSG - SG Communications May 2010 Slide 1 SG Communications DC Meeting AM2 Session Tuesday...

OpenSG - SG Communications

May 2010

Slide 1

SG Communications DC MeetingAM2 Session Tuesday 5/4/2010

Network Interoperability


SG COMMUNICATIONS TUESDAY AM2 AGENDA

Review SG Communications structure within UCAiugOverview of this weeks meeting scheduleOverview of Network Interop Task Force


UCAIUG ORGANIZATION OVERVIEW


February 2010

Slide 4

THIS WEEKS SG COMMUNICATIONS AGENDA

Monday, PM2 (SG Communications)Boot CampNote: Session is an overview for newcomers

Tuesday, AM2 (SG Communications)Network Interop OverviewSG-Network Overview

Tuesday, PM1 (SG-NET)Work submitted overview

Pre-pay use casesDA use casesMeter Event use casesOutage Manangement

Tuesday, PM2 (SG-NET)Break into teams to review submitted work


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 overviewFAQ review

Wednesday, PM2 (SG-NET)AOB Shortened time due to Smithsonian Tour

Wednesday, PM2 (Net-Interop)Network Interop meeting


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


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

Don Sturek, PG&E

February 2010

Slide 8


• 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).

Don Sturek, PG&E

February 2010

Slide 9


• 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..

Don Sturek, PG&E

February 2010

Slide 10


• System Requirements Specification:– Requirements for certification of single interface platforms

• MAC/PHY requirements (IEEE 802.2 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)

Don Sturek, PG&E

February 2010

Slide 11


• Call for participation:– Please e-mail: Don Sturek, [email protected]

• 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

mailto:[email protected]


QUESTIONS?


SG-NETWORK OVERVIEW

Scope and Charter for SG-Network within UCAiugNIST PAP 2 (Wireless standards for the Smart Grid)

Supply functional requirements for Smart Grid Networks from a utility perspectiveDefine functional domains within the Smart Grid

Create a System Requirements SpecificationProvide information to SDO’s (e.g., IEEE P2030)

ParticipationUtilitiesAcademiaVendors


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)


EXAMPLES OF WORK ACCOMPLISHED TO DATE

Sample Actors

Smart Meter

Load Management System (LMS)

Sample Requirement for a Smart Meter

Use 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

e.g

. DN

P

AMI Network (j)

Home / Building

Mgr

Aggregator

Energy Market Clearinghouse

RTO / ISO

Utility EMS Utility DMS MDMS

AMI Head End (j)

Energy Services Interface (ESI)

Sub-MeterMajor device loads –

non PHEV PHEV

Phone (y) – voice / email /

Txt / web

Email /TXT /web

ESI – in meter

PTC

IHD

Load Cntl Device

DERs

Smart Appliances

Customer

Customer EMS

METERjn – 2way

HVAC

Substation Controllers

Transmission Field Sensors

Data Collector

DistributionTransmission

Distributed Generation

Distributed Storage

Market Services Interface

Plant Control Systems

Bulk Generation

Aggregator

Retailer / Wholesaler

EMS

RTO SCADA

Asset Mgmt

Event /OMS

GIS

DSM

CIS / Billing

Service Providers

Utility 3rd Party (s)

Retail Energy Providers (REPs)

Markets

RTO / ISO Ops

Transmission Ops

Distribution Ops

Operations

Smart Grid Conceptual Data Flow Diagram – Cross Domain Network Focused – OpenSG / SG-Network TF

DRAFT 22Jan10 Base à SG-NET-diagram-r0.3b.vsd

Web Portal

Common Web

Portal – ISO/RTOs

8

1B

1Aa

1Ab

2AaCIS / Billing

Web Portal

PSN (x) / CELLULAR (x)

HAN

Cust. LAN

Regional Trans. SCADA

Trans. SCADA

FEP

Distr. SCADA FEP

15

13

4A

SG 4Bi1Cj

1Dn3By

Regional Distr. SCADA (r)

Su

bst

atio

n N

etw

ork

Fie

ld A

rea

Ne

twor

k

Substation Controllers (k)

Distr. Field Devices (l)

Data Collector

Su

bst

atio

n N

etw

ork

(s)

4Brs

4Br

Substation Devices

RTU

Generators

Generators

Generators

1Cam

Substation Devices (l)

RTU

Wide Area NetworksInternet / ExtranetsInternet / Extranets

1Ca

1D

Common Web

Portal I/O

2B

2C

2Fa

2Ea

2Fb

2Eb

2Da

Smart Meter

3Aa

2Ab

2Dc

Field Area Network (j)

Field Crews Tools

DAP (jm)

4Ba4Djl

4Dskj

NMS

Work Force Mgmt

Field force

11

7

14

LMS

DSDR

9

12

10

6

Common Web

Portal I/O

Bill Payment Orgs / Banks

GL / Accts Payable /

Receivable

3Abx

2G

5Bb

2Db

4Bb

3Acx

3Aax

3Ab

3Ac

5Ba

5Bc

16Ab

16Bb

16Ba

16Aa

1

23

4

56

7

8 1Cbm

1Cb


SG-NETWORKS REFERENCE ARCHITECTURE


DELIVERABLES

Interim Release 1.0 was published in December 2009Requirements and some volumetric and latency requirements

Interim Release 2.0 was published in February 2010Requirements, volumetric, latency requirements, security, implications and more use casesReference Architecture Diagram first publishedSystem requirements specification published

Interim Release 3.0 will be published in mid MayAddition of the following use cases: Pre-Payment, Meter Events, DA and Outage ManagementSystem requirements specification updatesReference Architecture Diagram updates

Interim Release 4.0 JuneScope to be determined this week


WORK PLAN FOR THE WEEKReview 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


QUESTIONS

OpenSG - SG Communications May 2010 Slide 1 SG Communications DC Meeting AM2 Session Tuesday...

Documents

Transcript of OpenSG - SG Communications May 2010 Slide 1 SG Communications DC Meeting AM2 Session Tuesday...