1

Connectivity Week 2010

How Can Standards Be Regulated?

Thursday May 27

10:30AM-Noon

Zahra Makoui

2

Session Abstract

NIST’s Smart Grid Interoperability Panel attempts to bring together the outputs of two dozen standards organizations and many advanced beta projects, and weave them into a unified path forward, for multiple stakeholders in the North American power grid. Can it be done? Can you regulate standards? How will competing systems be reconciled? Is anyone going to use all this stuff?

3

Technology Development Process

Business Case

($)

Use Cases Market Requirements

Document(MRD)

Technical Requirements

Document(TRD) Technical

Specification

Certification &Interoperability Testing

Are only use cases

regulated?Or is it

certification? Or is it just

the Business Case?

4

Key Principles of Standards Strategy

Adoption

Open Governance

Participation

Acquisition

Certification

Process forces compliance with standards

1. Openness2. Separation of Duties

3. Generational Compliance 4. Loose Coupling

1st

Generation2nd

GenerationCertification

Process forces compliance with standards

Process forces compliance with standards

Certification

User Groups

Industry AlliancesSDOs

Are these high level principles

regulated?

5

Technology as the Enabler, Not the Gate

Highlights the importance of:

Open standards Consensus based process Good technical design Most importantly: A broad spectrum of use

cases

6

Example 1: OpenHAN Major Changes Because of Additional Use Cases

OpenHAN 1.0 to OpenHAN 2.0 2007: OpenHAN formed. Outreach but not enough interest.

Main participation from Utilities, AMI Vendors, Device Vendors. 2008: OpenHAN 1.04 release 2009: NIST Smart Grid Activities Launched Q3 2009: Additional stakeholders and use cases identified

through the NIST process OpenHAN 2.0 launched to capture additional requirements

Additional participation from : EMS vendors, Texas Retail Energy Providers, Google, Other Service Providers.

77

Example 2: SE 2.0 Dedication to Capturing All Use Cases

May 2008: First SE 1.0 Certified Device Announced – flexibility in use key;DLRC, Simple metering, EI use cases as basis (also OpenHAN)

August 2009PAP 3,4,9,10 Harmonization meeting Conclusion: SE 2.0 consistent with group identified direction.

2010

October 2008Add’l stakeholders identified: HomePlug, SAE, IPSO, etc. New Use Cases indentified. SE 2.0 Launched

April 2010Draft SE 2.0 Released for Public comment

20092008

May 18 2009 : DOE press release announces SE2.0 as one of the initial 16 low hanging fruit standards identified through the NIST process

March 2009 : SE 2.0 MRD andUse cases release

March 2010 WiFi + ZigBee collaborations announced

8

Standards Development Takes TimeRequirements Technology Certification

UCAIUG

OpenSG

Other WorkingGroups

SG Systems Working Group

SG enterprise OpenADE Open HANTechnology agnostic HAN requirements

Third party access to

customer data

Back office integrations

requirements

IEC Harmonization

HAN StandardsZigBee®

HomePlug®

ZB + HP Joint Working Group

Joint SC

Technical WG Marketing WGMarket

requirements and alignment

Answer the technical questions

Compliance WG

Define certification process

Joint steering committee

chaired by PG&E

ZigBee IPTG

Smart Energy Profile WG

ZigBee Security WG

ZB QualificationGroup

HomePlug SE HomePlug AVIEEE P1901

IEEE

IETF

Other Standards

802.15.4 HAN2.4 GHz

ROLL

IPSO

Wireless M-Bus

802.11

Bluetooth

ZARC

Any standards activity that touches the HAN in any way.

ZigBee Architecture Review committee

Acts as the technical oversight committee and

authority

Defining ZigBee’s IP

gateway functionality

Goal of integrating to a common application layer independent of the underlying physical platform

Low bandwidth PLC communications std

Higher bandwidth PLC communication

std

Low power wireless mesh technology

HAN standard getting traction in

Europe

Oversee ZigBee certification

Routing over low

power and lossy

networks

ZigBee Labs

HomePlug Labs

802.15 Labs

OpenSG SG Conformity

Comprehensive Certification

Requirements

1. NTS

2. TUV

No specified labs. NTS and TUV

execute their own conformance testing

Marketing Working Group

6lWPAN

Skinny IP (UDP) over

802.15.4

Which piece of the

process is regulated?

9

Who Should Set Standards? SDO vs. Consortium

Application Standards Development Tasking (e.g., IEC)Define Environmental ConstraintsProduce Architectural ContextDefine Architectural Objects (Definition, Object Decomposition and Inheritance)Define Data AttributesDefine Standards SyntaxDefine Minimal Object Behavior (Encapsulate Functionality)

Networking Standards Development Tasking (e.g., IETF)SponsorshipDefine RoutingDefine Discovery Define Management

Platform and Technology Development (802.15.4, 802.11, 802.15)Define Physical Layer and MediaDefine Data Link Layer (e.g., MAC and LLC)

Commercial Entity Tasking (Wi-Fi, ZigBee, HomePlug)Define Common Network Standards SetDefine Minimal Network Standards SetDefine Interface and Service InteroperabilityDefine Certification and Testing Standards Define Upgrade PathsIdentify and Sponsor Additional Standards

SE

2.0(Z

igB

ee Allian

ce)

10

System and Standards

PSTN

ApplicationPresentation

SessionTransportNetworkData LinkPhysical

HANMeter

Specific Networks

Wide Area

Networks

Data Collection Systems

MDM Systems

Utility Systems

Web Presentation

CIS

Powerline Data Collection

Wireless Data Collection

Paging Data Collection

Telephone Data Collection

OMSGIS

AMI Management

Usage Data

Private Wireless

Public Wireless

Point -to-Point

Mesh RF

CSR

Third Parties

Customer

Regulator

Retailer

$

Internet

DataExchange

00000

00000

00000

00000

72°

BPL

BPL/PLC

At which layers are standards

regulated?

11

Questions Needs To Be Addressed

Standards Are Complicated And Take Time What Happens If You Accelerate The Timeline? Can You Regulate Standards? Technology? Use

Cases?