OpenSG Closing Plenary Oct 22 nd, 2009. Agenda SG Conformity SG Communications SG Systems SG...
22
OpenSG Closing Plenary Oct 22 nd , 2009
-
Upload
dinah-holly-todd -
Category
Documents
-
view
243 -
download
5
Transcript of OpenSG Closing Plenary Oct 22 nd, 2009. Agenda SG Conformity SG Communications SG Systems SG...
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
• Next encounter data/time (tele./webinar/f2f)
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 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
• 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
Suggest DR Use Case Matrixuc Use Case Matrix
3.0 Administrate DR Resource
3.1 Administrate Bulk Power DR Resource
3.2 Administrate Distribution DR
Resource
1.0 Administrate DR Program
3.1.1 Registor DR Resource
3.1.4 Administrate DR Asset (Direct)
3.1.2 Declare DR Resource Status
4.0 Execute DR Ev ent
3.1.3 Remov e DR Resource
1.1 Create DR Program
1.2 Udpate DR Program
1.3 Remov e DR Program
2.0 Administrate Customer Entity for DR
4.1.1 Adv anced Notification for DR
(Bulk Power)
4.1.2 Update a DR Ev ent (Bulk Power)
4.1.3 Cancel a DR Ev ent (Bulk Power)
4.1.4 DR Resource Confirmation (Bulk
Power)
4.2.1 Adv anced Notifiation for DR
(Distribution)
4.3 Broadcast Pricing (Wholesale)
for DR Purpose
4.2.2 Update a DR Ev ent (Distribution)
4.2.3 Cancel a DR Ev ent (Distribution)
4.2.4 DR Resource Confirmation (Distribution)
4.4 Broadcast Pricing (Retail) for DR Purpose
4.5 Dispatch DR Instructions (Bulk
Power)
4.7 DR Direct Load Control (Distribution)
4.5.1 Monitor DR Ev ent (Bulk)
Administrate DER for DR Purpose
4.9 Operational Coordination between Transmission and
Distribution and DR Resources
4.7.1 Monitor DR Ev ent (Distribution)
5.0 Post DR Ev ent Management
4.8 DR Resource Ev ent Execution
5.1 Post DR Ev ent M&V (Wholesale)
5.2 Post DR Ev ent M&V (Retail -
Regulated)
5.3 Post DR Ev ent &V (Retail - Deregulated)
5.4 DR Ev ent Financial Settlement
4.1 Notify DR Ev ent (Bulk Power)
4.2 Notify DR Ev ent (Distribution)
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.
Verison 0.1Date: October 14, 2009
3.1.5 DR Bidding
4.6 Dispatch DR Instructions (Distribution)
«include»
«include»«include»
«include»
«include» «include»
«invokes»
«include»«include»
«include»«include»
«invokes»
«precedes»
«include»
«include»
«include»
«include»
«include»
«include»«include»«include»
«precedes»«precedes»
«extend»
«include»«include»«include»
«include»«include»«include»
«include»«extend» «extend»
«include»
«precedes»
«invokes»
«include»«include»«include» «include»«include»«include»
«include»
«precedes»«precedes»
«include»
«include»
SG-Systems - OpenADR
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!
