Transcript OpenSG Closing Plenary Oct 22nd, 2009 Agenda • • • • • • SG Conformity SG Communications SG Systems SG Security Feedback Next Meeting.

OpenSG Closing Plenary
Oct 22nd, 2009
Agenda
•
•
•
•
•
•
SG Conformity
SG Communications
SG Systems
SG Security
Feedback
Next Meeting
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
• Next encounter data/time (tele./webinar/f2f)
– To be announced via the general listserve
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
SG Communications
• Next encounter data/time (tele./webinar/f2f)
– Plan for next week to continue PAP #1 and #2
requirements generation
SG Systems
• Key accomplishments
– Updated SharePoint
– Electronic Balloting Process
– Task Forces (next slides)
• Next steps
– (Next Slides)
SG-Systems Task Forces & Service Teams
SG-Systems WG
Chair: Brent Hodges
Co Chair: Greg Robinson
AMI-Ent TF
OpenADE TF
OpenADR TF
OpenHAN TF
Chair: Wayne Longcore
Co-Chair: Greg Robinson
Chair: Dave Mollerstuen
Co-Chair: Steve Van Ausdall
Chair: Albert Chiu
Co-Chair: Ed Koch
Chair: Erich Gunther
Co-Chair:
Underway
Underway
With NAESB
Underway
Underway
With NAESB
Use Case Team
Chair: Ralph Martinez
Co-Chair: Kay Stefferud
SRS Team
Chair: Joe Zhou
Planning
Collaboration
With SE 2.0
& OASIS
Collaboration
With SE 2.0
Planning
Planning
Collaboration
With SE 2.0
& OASIS
Collaboration
With SE 2.0
Underway
Underway
Collaboration
With SE 2.0
& OASIS
Collaboration
With SE 2.0
Service Definitions Team
Chair: Jerry Gray
Co-Chair: Shawn Hu
Interoperability Testing Team
Chair: Randy Lowe
Co-Chair: Xiaofeng Wang
Security Team
Chair: Darren Highfill
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
• Next encounter data/time (tele./webinar/f2f)
– Service Definition con call: 10/28 2PM
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
SG-Systems - OpenADR
Suggest DR Use Case Matrix
uc Use Case Matrix
DR Signals Use Cases Diagram - (NAESB Smart Grid Task Force)
The purpose of this diagram is to show all relevant use cases under the scope of
NIST PAP09 (Standard DR Signals) and shall cover DR programs at both the
wholesale and retial market level. The focus of the use cases are interactions
between the Smart Grid Domains defined by the NIST Smart Grid Interoperability
Standards Roadmap.
4.5.1 Monitor DR
Ev ent (Bulk)
4.9 Operational Coordination
betw een Transmission and
Distribution and DR
Resources
«include»
4.7.1 Monitor DR
Ev ent (Distribution)
«include»
Verison 0.1
Date: October 14, 2009
«extend»
«extend»
4.6 Dispatch DR
Instructions
(Distribution)
«include»
«extend»
«invokes»
4.5 Dispatch DR
Instructions (Bulk
Pow er)
2.0 Administrate
Customer Entity for DR
1.0 Administrate DR
Program
«include»
3.0 Administrate DR
Resource
«precedes»
4.8 DR Resource
Ev ent Execution
«invokes»
4.7 DR Direct Load
Control (Distribution)
«invokes»
4.0 Execute DR
Ev ent
«precedes»
5.0 Post DR Ev ent
Management
«precedes»
«include»
«include»
1.1 Create DR
Program
«include»
1.3 Remov e DR
Program
3.2 Administrate
Distribution DR
Resource
3.1 Administrate Bulk
Pow er DR Resource
4.1 Notify DR Ev ent
(Bulk Pow er)
4.3 Broadcast
Pricing (Wholesale)
for DR Purpose
5.1 Post DR Ev ent
M&V (Wholesale)
«include»
«include»
«include»
«include»
«include»
«include»
«include»
1.2 Udpate DR
Program
3.1.1 Registor DR
Resource
3.1.2 Declare DR
Resource Status
3.1.3 Remov e DR
Resource
4.1.1 Adv anced
Notification for DR
(Bulk Pow er)
«include»«include»
«include»
4.1.2 Update a DR
Ev ent (Bulk Pow er)
«include»
«include»
«include»
«include»
«include»
4.1.3 Cancel a DR
Ev ent (Bulk Pow er)
«include»
«include»
4.2.1 Adv anced
Notifiation for DR
(Distribution)
«include» «include»
«include»
«include»
4.2.2 Update a DR
Ev ent (Distribution)
«include»
«include»
3.1.4 Administrate DR
Asset (Direct)
Administrate DER for
DR Purpose
4.1.4 DR Resource
Confirmation (Bulk
Pow er)
4.2.4 DR Resource
Confirmation
(Distribution)
5.2 Post DR Ev ent
M&V (Retail Regulated)
5.3 Post DR Ev ent &V
(Retail - Deregulated)
«include»
4.2.3 Cancel a DR
Ev ent (Distribution)
«include»
«include»
3.1.5 DR Bidding
«include»
«include»
4.2 Notify DR Ev ent
(Distribution)
4.4 Broadcast Pricing
(Retail) for DR Purpose
«precedes» «precedes»
«precedes»
5.4 DR Ev ent
Financial Settlement
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
If you have comments and/or wish to join and
contribute to the OpenADR Task Force effort, please
contact
Albert Chiu or Ed Koch
at [email protected] or [email protected]
Attendee Feedback
•
•
•
•
•
•
•
•
•
•
•
Names, specific group and meeting
Consistent dashboards across WGs for reporting
More detailed agenda, better, earlier planning for F2F
Realtime schedule time change mechanism at F2F
Capture on phone attendance
Real full- duplex polycomm type phones for conf calls
New people better comms, glossary, terms, promote don’t be shy attitude. Online
library ref
Boot camps were a positive
WGs need to tighten up scopes, ie. OpenHAN and Net, more groups means need
for tighter coordination
More formal joint sessions
Web based agenda with links to open meeting etc.
Next Meeting
• Host is Florida Power & Light
• Juno Beach, FL
• January 18-21, 2010
– Boot camps on January 18
– Parallel sessions January 19-21
Hosting Opportunity
• April 2010 Meeting…somewhere warmer?
– Looking at DC or Raleigh
• July 2010 Meeting…somewhere cooler?
– Looking at San Francisco Area
• Send email to Chris Knudsen: [email protected]
Thank you!
Safe return!