Upload
mimir
View
71
Download
0
Tags:
Embed Size (px)
DESCRIPTION
Submission Title: [ OpenSG San Francisco TC Report ] Date Submitted: [ February 1st, 2010 ] Source: [ Don Sturek ] Company [ PG&E ] Address [ 77 Beale Street, San Francisco, CA 94105 ] Voice [+ 1 619 504 3615 ], E-Mail:[ [email protected] ] Re: [ OpenSG Communications TC Report ] - PowerPoint PPT Presentation
Citation preview
Submission
Don Sturek, PG&E
February 2010
Slide 1
Submission Title: [OpenSG San Francisco TC Report]Date Submitted: [February 1st, 2010]Source: [Don Sturek] Company [PG&E]Address [77 Beale Street, San Francisco, CA 94105]Voice [+1 619 504 3615], E-Mail:[[email protected]]Re: [OpenSG Communications TC Report]
Abstract: [Technical Committee Report for OpenSG Communications]
Purpose: [OpenSG TC report]
Submission
Don Sturek, PG&E
February 2010
Slide 2
Notable SG Communications Activities
• NIST PAP related– PAP 1
• Tasks for OpenSG: – Task 1: Develop a set of requirements for different
Smart Grid applications (end 2009) – DONE (sort of, see App Matrix)
– Task 3: Develop application specific protocol requirements (mid 2010)
– Task 4: Perform gap analysis (mid 2010)
Submission
Don Sturek, PG&E
February 2010
Slide 3
Notable SG Communications Activities
• NIST PAP related– PAP 2
• Tasks for OpenSG:– Task 1: Segment the smart grid and wireless environments into a
minimal set of categories for which individual wireless requirements can be identified. (end of 2009) – DONE (sort of, see App Matrix)
– Task 3: Compile & communicate use cases and develop requirements for all smart grid domains in terms that all parties can understand (end of 2009) – DONE (sort of, see App Matrix)
– Task 4: Compile and communicate a list of capabilities, performance metrics, etc. in a way that all parties can understand. - Not quantifying any standard, just defining the set of metrics. (DONE by IEEE 802)
– Task 6:Perform the mapping and conduct an evaluation of the wireless technologies based on the criteria and metrics developed in task 4. (mid 2010)
Submission
Service Provider Operations
Customer
Distribution
Electric Vehicle
Utility EMS DA Field
Devices
Sub-Meter
CIS
SCADA
MDMSBilling
Aggregator / Retail Energy
Provider
Markets
Energy Market Clearinghouse
RTO/ISOCustomer
Appliances
Third Party
Customer
AMI3
AMI1
AMI2
AMI5AMI4
AMI9
AMI7
AMI6
AMI10 AMI11
AMI12
AMI13
AMI14
AMI16
AMI18
AMI19
AMI20
AMI23
AMI22
AMI24
AMI26
AMI31 AMI32
AMI33 AMI34AMI35 AMI36 AMI37
AMI38
AMI41
AMI Systems Use Cases: Actors, Logical Interfaces, and Networks
AMI: Advanced Metering InfrastructureCIS: Customer Information SystemDMS: Distribution Management SystemDRMS: Demand Response Management SystemEMS: Energy Management SystemGIS: Geographic Information System
HAN: Home Area NetworkISO: Independent System OperatorLMS: Load Management SystemOMS: Outage Management SystemRTO: Regional Transmission Operator
Customer DER
AMI43
AMI Network
Local Connection
ESI Network
AMI40
Network
DMSApplications
GIS
OMS
LMS / DRMS
AMI15AMI Headend
Energy Services Interface/ HAN
Gateway
Field crew Tool
MeteringCustomer EMS
AMI17
AMI8
AMI28
AMI39
AMI27
AMI21
AMI42
AMI29 AMI30
From the NIST IR ……..
Submission
Distilled the intra-subsystem interfaces to……..
Submission
Don Sturek, PG&E
Notable SG Communications Activities
• Application Matrix: http://osgug.ucaiug.org/UtiliComm/Shared%20Documents/SG-NET%20PAP%20work-in-progress/SG%20Communications%20funct-reqs%20v1-draft-29Jan10-r03c.xls (addresses both PAP 1 and PAP 2)
• To be done (PAP 1 and PAP 2)– Update and ballot Application Matrix (April 2010)– PAP 1:
• Collaborate on Task 4 with IETF on gap analysis (mid 2010)
– PAP 2:• Collaborate on Task 6 with IEEE 802 on mapping of
application requirements to wireless standards
October 2009
Slide 6
Submission
Don Sturek, PG&E
February 2010
Slide 7
Notable SG Communications Activities
• Non NIST PAP related– Network Interoperability
• Proposed Scope/Charter document to be discussed at SF face to face
• Document outline available from ZigBee/HomePlug Platform work
• Since we are using IP, document should only address:– Collection of RFCs used (from SE 2.0 TRD)– Security protocols and cipher suites (from SE 2.0
TRD)– Application support protocols (from SE 2.0)
Submission
Don Sturek, PG&E
February 2010
Slide 8
Notable SG Communications Activities
• Non NIST PAP related– AMI-NET
• Matt: could you fill in any non PAP 2 tasks AMI-NET will be working on?
Submission
Don Sturek, PG&E
February 2010
Slide 9
Notable SG Communications Activities• Non NIST PAP related
– IETF• 6LowPAN Neighbour Discovery (link local address
assignment)– Issues resolution team headed by Ralph Droms of
Cisco (IETF Internet Area Director for 6LowPAN)• ROLL
– JP Vasseur (Cisco and co-chair of ROLL) is the ZigBee Alliance-IETF liaison representative
– David Culler (CTO of Archrock and co-chair of ROLL) is here this week.
• 6LowAPP– Problem Statement:
http://www.ietf.org/id/draft-shelby-6lowapp-coap-00.txt