OpenSG StatusUCAIug Members Meeting

Chris Knudsen – ChairGary Stuebing – Vice-Chair

November 9th, 2009

Agenda

• Organization• SG Conformity• SG Communications• SG Systems• SG Security

SG Conformity• Key accomplishments

– Defined scope and charter with unanimous agreement – Established guiding principles – Agreed on formation and prioritization of 3 TFs:

• Edge Conformity (ADE/ADR/HAN) • SG Security Conformity • AMI ENT Conformity (Not currently prioritized)

• Next steps– kick off task forces and establish weekly calls and

SG Communications• Key accomplishments

– OpenSG PAP #1 and #2 requirements• Identified 21 top level SG applications and 15 potential

actors for each• Worked through 4 of the applications end to end and

created over 100 high level functional requirements

– Organization• Scope/Charter discussion

SG Communications• Next steps

– OpenSG PAP #1 and #2• Complete walkthrough of top level actions• Align requirements by actor interfaces• Distill communications requirements • Face to face at Grid-Interop in Denver (mid November)

– Organization• Task Groups per Knoxville session discussion• Weekly conference calls

• Next encounter data/time (tele./webinar/f2f)

SG Systems• Key accomplishments

– Updated SharePoint– Electronic Balloting Process – Task Forces (next slides)

• Next steps– (Next Slides)

SG-Systems WGChair: Brent Hodges

Co Chair: Greg Robinson

Use Case Team Chair: Ralph Martinez Co-Chair: Kay Stefferud

Interoperability Testing Team Chair: Randy Lowe Co-Chair: Xiaofeng Wang

Service Definitions Team Chair: Jerry Gray Co-Chair: Shawn Hu

SRS Team Chair: Joe Zhou

Security Team Chair: Darren Highfill

AMI-Ent TFChair: Wayne Longcore

Co-Chair: Greg Robinson

OpenADE TFChair: Dave Mollerstuen

Co-Chair: Steve Van Ausdall

OpenADR TFChair: Albert Chiu Co-Chair: Ed Koch

OpenHAN TFChair: Erich Gunther

Co-Chair:

SG-Systems Task Forces & Service Teams

Planning

Underway

Underway

Underway

Underway With NAESB

CollaborationWith SE 2.0

CollaborationWith SE 2.0

& OASISPlanning

Planning

Underway With NAESB

Underway

CollaborationWith SE 2.0

& OASIS

CollaborationWith SE 2.0

& OASIS

CollaborationWith SE 2.0

CollaborationWith SE 2.0

SG Systems – AMI-Enterprise• Key accomplishments

– Industry Best Practice Approved:• Use Cases• System Requirements Specification (SRS)• Methodology• Services• Ready to submit to SDO (IEC TC57 WG14)

• Next steps• Participate in IEC61968-9 interoperability testing• Analyze and incorporate security requirements• Update and ballot next release

Service Definition Team• Key accomplishments

– Approval of the Service Definition Artifacts

• Next steps – Build the roadmap• Open a model for access/collaboration• Baseline the artifacts• Plan new work, e.g. OpenADE, sharing with WG14

SG Systems - OpenADE• Key accomplishments

– Agreement on 1.0 version of Use Case document

• Next steps– Work on SRS, service definitions– Reference / prototype implementations

• Next encounter data/time (tele./webinar/f2f)– Weekly meetings, every Thursday @noon Mtn.

SG-Systems - OpenHAN• Leadership

– Chair and co-chair – lead teleconferences• Chair – Mary Zientara (Reliant)• Co-chair – Steve Van Ausdall (Xtensible)• Co-chair – Charles (Google)• Co-chair – Charlie (GE)

• Define scope and charter• Use cases – common team

– Focused on format and capture• but still need content and selection for our purposes in OpenHAN

• Business level requirements – in OpenHAN?• Provide input to SEP 2.0 (and others as requested)• Analysis – update SRS requirements table• Conformance tasks• Security tasks

Use Case Development Accomplishments

Use Case # Use case description Note

4.2 Notify DR Event SD and Interaction - Completed

4.2.1 Advanced Notification for DR SD and Interaction - Completed

4.2.2 Update a DR Event SD and Interaction - Completed

4.2.3 Cancel a DR Event SD and Interaction - Completed

4.2.4 DR Resource Confirmation SD and Interaction - Completed

4.7 Direct Load Control SD and Interaction - Completed

4.7.1 Monitor DR Event SD and Interaction - Completed

DR Use Case Discussion Topics• 4.4 Broadcast “Pricing” (Retail) for DR Purpose – The

term pricing will change to more generic• Reference Architecture• DR acknowledgement and confirmation• Advanced Notification for DR• Adding testing use case• DR Resource Confirmation (DR Resource, Asset,

PHEV)• Direct Load Control – randomization, monitor

protocol

Next steps and next encounter date/time

• Next steps– Refine use cases developed– Provide draft use cases to sub-group leader (Joe) by Friday, October

21st

– Refine combined retail and wholesale use cases in the next two weeks– Finalized use case and framework document by first week of

November– Continue to work with NAESB, NIST and OASIS on SRS and Service

Definition• Next encounter date/time

– Every Thursday joint conference call with NAESB (12-2:00 central time)

– NAESB SGTF sub-group F2F meeting in New England

UtiliSec• Status:

– Suite of 4 deliverables completed in 2008• AMI Security Risk Assessment• AMI System Security Requirements (incorporates Architectural Description)• AMI Security Component Catalog• AMI Security Implementation Guide

– AMI System Security Requirements document ratified December, 2008 (“1.0”)

• Current Participation:– 200+ Subscribers to Listserv across 8 countries and 4 continents– More than a dozen major North American utilities actively engaged– Broad mix of utilities, vendors, government, and academia

Next Meeting• Host is Florida Power & Light• Juno Beach, FL• January 18-21, 2010

– Boot camps on January 18– Parallel sessions January 19-21