OpenADE Problem Statement Existing Solutions Standardization Process

Columbus, OH, July 14, 2009, Hosted by AEP

AMI-EnterpriseAMI-Enterprise

OpenADE Overview

Dave Mollerstuen

[email protected]



OpenADE Problem Statement

Existing Solutions

Standardization Process

Business & User Requirements Overview

Request for Participation

Q & A


OpenADE Problem Statement

What• Standardized Machine-to-Machine (M2M) interface that permits

utilities to share, at the consumer’s request and under the consumer’s direction, a broad set of that consumer’s utility data with specific 3rd Parties.

Who• Consumers!

• Utilities (T&D, REPs)

• 3rd Parties (Residential Energy Management, Demand Response Aggregators, Distributed Generation, etc.)

Why• Increased efficiencies, increased reliability, … (i.e “Why SmartGrid?”)

• Standardizes interface: reduces implementation costs, time to market

Where• Universal!


Open ADE Problem Statement

Existing Solutions




Q & A


Existing Solutions

Currently looking at each of these to elicit business and user requirements; subsequent efforts (i.e. SRS) will measure each of these against the derived functional requirements, and consider each as a potential technology source.

• Proprietary – Existing Utility 3rd Party

• Regional– PUCT Implementation Project relating to Advanced Metering

• EDI-867



Existing Solutions




Q & A



Historical(through April 2009 OpenSG Meeting)

• OpenHAN, others demonstrated successful methodology• NIST and DOE focus on SG interoperable standards• Jurisdictional (e.g. CA, TX) focus on SG interoperable

standards• January 2009: OpenSG leadership considers ADE• March 2009: OpenSG leadership request collaboration

from leading vendors• April 2009: OpenADE kicked off at OpenSG quarterly

meeting



Present Day(April 2009 to July 2009)

• Ad Hoc group formed to collect business, user, and functional requirements (roughly equivalent to Use Case Team role)

• Meeting weekly via teleconference

• Participants (sampling)Utilities 3rd Parties Consumer

Consumers Energy Tendril Networks Citizens Utility Board

Florida Power and Light Google UCAN

Oncor Greenbox

Pacific Gas and Electric Comverge

Reliant Juice Technologies

Southern California Edison

San Deigo Gas & Electric

Xtensible Solutions (consultants)

• Work Product: “OpenADE Business & User Requirements Document”



Futures(July 2009 and forward)

• Existing ad hoc team completes gathering business and user requirements, functional requirements

• Ad hoc team’s work reviewed by AMI-Ent Use Case team

• SRS, Services team (expect some calendar and personnel overlap with requirements team)

• Selection of Standards Development Organization (SDO)

• Handoff to SDO; expect to continue to work with SDO throughout standardization process



Existing Solutions




Q & A


Requirements Overview

OpenADE Business Requirements

Business Requirements represent the high-level objectives of the organization in defining the system. Additionally, business requirements help define the domain for the subsequent vision and scope.



OpenADE Business Requirements

• Opportunity• Objectives and Success Criteria• Market Needs• Risks• Specific Business Requirements

ID Requirement

OADE BR-001 Allow a Consumer to authorize release of data to registered 3rd Party

OADE BR-002 Allow a Consumer to authorize multiple registered 3rd Parties to have limited, time based, read-only access to their data



OpenADE Vision

The Project Vision summarizes the project’s long-term purpose and intent. The vision should include all reasonable, eventual goals of the project, not just those targeted for the initial release.



OpenADE Vision

• Project Vision Statement: For utility consumers who want greater access to, and derived value from, their utility data …

• Major Features– Standardized interface– Data types: consumption, pricing, demand response, HAN

• Assumptions– 3rd Parties must be authorized by the appropriate regulator …



OpenADE Scope

The Project Scope defines a specific release of the project. For a project with anticipated multiple releases, not all features within the project vision might be included in the initial project scope.



OpenADE Scope

• OpenADE 1.0– Full implementation of security, authorization requirements– Limited to near-realtime and historical consumption data

• Subsequent Releases– Pricing data, utility network events, HAN-related data

• Limitations and Exclusions

Feature In Out

Criteria for Consumer data availability at Utility portal X

Consumer HAN data X



OpenADE Business Context

Business Context summarizes various business issues, including profiles of major stakeholders and the desired relationship between the major project dimensions of scope, quality, schedule, cost and staff.



OpenADE Business Context• Stakeholder Profiles

– Consumers– Utilities– 3rd Parties

• Residential Energy Management

• C&I Energy Management

• Demand Response Aggregators

• REPs (deregulated environments)

• Project Dimensions– Drivers: scope, quality

– Constraints: schedule

– Degree of freedom: cost, staff



OpenADE Use Cases

Use Cases can have multiple roles throughout the project life cycle: requirements elicitation, functional requirements, documentation of system design, etc.

Use cases employed to elicit user requirements can be less rigorous (i.e. formal) than for other purposes.

The following are more properly termed activity diagrams, and are each a high-level graphical representations of the use case scenario.



“Overview” Use Caseact ADE Ov erv iew - Prov ide Utility Data to Consumers

Re

gu

lato

r3

rd P

art

yC

on

su

me

rU

tili

ty /

AD

E

Register withUtility

Process 3rdParty

Applications

Start

Screen 3rd PartyApplicant

Approved?

Configure 3rdParty in ADE

End

Register for 3rdParty Serv ice

Prov ide RegisteredUsers Usage Data

to 3rd Parties

Receiv e UsageData

Use 3rd PartyServ ice

Track and SettleCosts and Usage

Process UserRegistration

Process UserRegistration

Periodically

Prov ide 3rd PartyServ ice

yes

no



“Manage Customer Authorization” Use Caseact ADE Registration - Consumer Grants Permission

3rd

Pa

rty

«O

Au

th C

on

su

me

r»

Uti

lity

«O

Au

th S

erv

ice

Pro

vid

er»

Co

ns

um

er

«O

Au

th U

se

r» Beginregistration forsepecific 3rdparty serv ice

Start

Redirect toutility to startregistration

process

Receiv eunauthorized

request token,authenticateutility user

identity

Requestconsent to

share specificinformation

Authentic? Granted?

Redirect to 3rdparty withauthorized

request token

Request accesstoken usingauthorized

request token

Validaterequest, returnaccess token

and token secret

Subscribe toprotected

userresourcesfrom utility

Prov eidentity to

utility

Grant access request(click "yes")

Prov e identity to3rd party

Receiv eauthorized

request token,authenticate

3rd party useridentity

Authentic?

choice

Validateaccess

request, addsubscription

to ADE

yes yes

yes



“Provide Consumer Data” Use Caseact ADE Publication - Utility Prov ides Consumer Data to 3rd Party

3rd

Pa

rtie

sA

DE

Uti

lity

Compile data forregistered 3rd

party consumerusersStart

Periodically (daily)

Transferconsumer

usage data toADE system

Storeconsumerusage data

ConsumerUsage

Notify each 3rd partythat new data is

av ailable

Receiv enotification

Notification

Requestusage data

Verify requestand prov ideusage data

UsageRequest

Receiv e consumeruser usage data

ConsumerUsage



Existing Solutions




Q & A



• “Business and User Requirements Document”– AMI-Ent TF > Shared Documents > OpenADE

• Breakout Sessions this Afternoon (proposed)– 2:00 to 3:30 – “OpenADE Business and User Requirements”

review– 3:45 to 5:00 – “Manage Customer Authorization” Use Case

• Weekly Calls– Thursdays 12p to 2p Mountain Time (conflicts with AMI-SEC

calls, might have to reschedule)

• Email Reflector– Email Dave Mollerstuen ([email protected]) to join

• Particular need for:– Security-savvy participants– MDMS participants



Existing Solutions




Q & A


Q & A


Thanks!

OpenADE Problem Statement Existing Solutions Standardization Process

Documents

Transcript of OpenADE Problem Statement Existing Solutions Standardization Process