1 / 59

Smart Grid ad hoc Meeting Information - March 2010

Smart Grid ad hoc Meeting Information - March 2010. Authors:. Date: 2010-2-10. Name. Company. Address. Phone. email. 5488 Marvell Lane, Santa Clara, CA, 95054. +1 (321) 427-4098. bkraemer@. marvell. .com. Bruce Kraemer. Marvell.

nora
Download Presentation

Smart Grid ad hoc Meeting Information - March 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Smart Grid ad hoc Meeting Information - March 2010 Authors: Date: 2010-2-10 Name Company Address Phone email 5488 Marvell Lane, Santa Clara, CA, 95054 +1 (321)427-4098 bkraemer@ marvell .com Bruce Kraemer Marvell Abstract: Information on Smart Grid of interest to WG11 – March 2010 Bruce Kraemer, Marvell

  2. Meeting Agenda & Context - NIST PAP#2 • NIST is going to use (require) a model to demonstrate performance when operating in typical Smart Grid domains • Details are to be found at the URL on Slide 2 • Goal today is to: • Promote awareness of Model • Collect Model questions or change suggestions • Plan for subsequent discussion on future calls and in March plenary Bruce Kraemer, Marvell

  3. Outline Overview of NIST PAPs PAP#2 goals and sub tasks PAP#2 Task 6 plan IEEE approach to Task 6 Bruce Kraemer, Marvell

  4. Background • The NIST interoperability process identifies a number of high priority issues including the role of IP and the use of wireless communications: • April 2009 workshop http://collaborate.nist.gov/twiki-sggrid/bin/view/_SmartGridInterimRoadmap/InterimRoadmapWorkshop1 • May 2009 workshop http://collaborate.nist.gov/twiki-sggrid/bin/view/_SmartGridInterimRoadmap/InterimRoadmapWorkshop2 • EPRI report to NIST, June 2009 http://nist.gov/smartgrid/InterimSmartGridRoadmapNISTRestructure.pdf • NIST convenes an SDO workshop in August 2009 in order to develop plans to address priority issues http://collaborate.nist.gov/twiki-sggrid/bin/view/_SmartGridInterimRoadmap/PriorityActionPlans Bruce Kraemer, Marvell

  5. The Current Priority Action Plans 0 Meter Upgradeability Standard 1 Role of IP in the Smart Grid 2 Wireless Communications for the Smart Grid 3 Common Price Communication Model 4 Common Scheduling Mechanism 5 Standard Meter Data Profiles 6 Common Semantic Model for Meter Data Tables 7 Electric Storage Interconnection Guidelines 8 CIM for Distribution Grid Management 9 Standard DR and DER Signals 10 Standard Energy Usage Information 11 Common Object Models for Electric Transportation 12 IEC 61850 Objects/DNP3 Mapping 13 Time Synchronization, IEC 61850 Objects/IEEE C37.118 Harmonization 14 Transmission and Distribution Power Systems Model Mapping 15 Harmonize Power Line Carrier Standards for Appliance Communications in the Home 16 Wind Plant Communications Bruce Kraemer, Marvell

  6. Issue: Use of Wireless Communications in the Smart Grid • There are a number of advantages for using wireless communications including: • Untethered access to information • Mobility • Interoperability • Reduced cost and complexity • Availability of technologies with different characteristics to choose from • A number of challenges remain to be addressed: • How to choose among technologies with different characteristics? • How do we know which technology to use for what Smart Grid application? • Are there any implications for using a certain wireless technology in a certain environment? • Are there any deployment? Interference issues? Bruce Kraemer, Marvell

  7. Review of PAP#2 tasks • Develop Smart Grid application communication requirements and devise a taxonomy for applications with similar network requirements • Draft under development and available for review http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP02Wireless/app_matrix_pap.xls • Develop terminology and definitions • Compile and communicate use cases and develop requirements • is part of Task 1 • Create an attribute list and performance metrics for wireless standards • Draft developed and available for review http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP02Wireless/NIST_PAP2-_Wireless_Characteristics-IEEE802-v_02.xls 5. Create an inventory of wireless technologies and standards that are identified by each SDO • Feedback is expected by December 6, 2009. • Conduct an evaluation of the wireless technologies based on the application requirements • Perform a gap analysis and developing guidelines for the use of wireless technologies. 7 7 Bruce Kraemer, Marvell

  8. NIST PAP#2 Goals/Events • Modeling introduced February 4 at SFO Hilton – Joint with UCAIug OpenSG • Next meeting to review progress and address questions: March 31 at NIST Gaithersburg • At least partial analytic results based upon execution of models against high priority Use Cases by June 2010. • Neded: Clarification of how these results will be used. How are they coupled into SmartGrid Policy or Law/ What is the role of FERC? Bruce Kraemer, Marvell

  9. Approach to PAP#2 Task #6 Task 6 is to perform the mapping and conduct an evaluation of the wireless technologies based on the application communication requirements developed in Task 1 and the inventory of wireless technologies and their associated characteristics collected in Task 5. • During the February 4, 2010 PAP2 meeting that was held in San Francisco in conjunction with the OpenSG meetings, it was agreed that an evaluation methodology similar to the one presented by NIST and discussed by the group be used to perform Task 6. The group has also decided to issue a call for contribution of modeling tools and resources to assist in conducting the evaluation: • Indication of interest by February 19, 2010 to assist in conducting the evaluation. • Contribution of wireless technologies modeling tools by February 19, 2010. The tools contributed must be made available on the NIST twiki and available for use by all parties. • Contribution of measurement and experimental data for validating the performance evaluation results. Bruce Kraemer, Marvell

  10. Homework NIST Modeling Presentation • Detailed description of the modeling approach can be found at: • http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP02Wireless/PAP2modeling.ppt Bruce Kraemer, Marvell

  11. Homework OpenSG Information Input from Open SG SG-NET received on February 22, 2010: • http://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Release_2/ The reference architecture models locations are: • http://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Release_2/SG-NET-diagram-r0.4e-with-Xflows.pdf • http://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Release_2/SG-NET-diagram-r0.4e.pdf The SG-Network functional requirements spreadsheet location is: • http://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Release_2/SG-Net_TF_%20funct-volumteric-reqs_v2.xls The SG-Network system requirements specification locations is: • http://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Release_2/SG%20Network%20System%20Requirements%20Specification%20v2.doc Bruce Kraemer, Marvell

  12. Homework NIST Modeling • Tools provided by NIST and used in presentation PAP2modeling.ppt • nist_80211_mac.m: Matlab code for 80211_MAC_Model • nist_80211_MAC_readme.pdf: Readme file for using the 802.11 model Matlab code • SNRcdf.m: Matlab code for computing SNR probability at wireless receiver • SNRcdfCell.m: Matlab code for coverage analysis • nist_phy_model_readme.pdf: Readme file for using Matlab code for SNRcdf and SNRcdfCell • nist_channel_propagation_models.pdf: Channel propagation models Bruce Kraemer, Marvell

  13. Meter Reporting Application: Mean Delay versus Offered Load 13 Bruce Kraemer, Marvell

  14. Initial Questions from Ted Booth • As part of the PHY model, it’s not clear how NIST derived interference (I0 ) first introduced on slide 16.  In 802.11 access methods, usually, interference means signals from other BSS or other device's signal emission on the operating channel. However, it’s not clear what NIST assumes here.  Comments? • Regarding Transmit Power Control (TPC) (slide 17), Sony believes most of the current 802.11 devices do not apply dynamic transmit power control.  What’s your assessment here?  The NIST Models allow for either approach. Comments? • Looking again at TPC in the MAC Model, traditionally most 802.11 implementations try to use the best MCS to achieve higher throughput;  this will significantly impact results out of the Model.  How should the Model properly takes this into account? Bruce Kraemer, Marvell

  15. Future Smart Grid ad hoc calls • Schedule plan was for Wednesdays at 2pm EST • Feb 10 • Feb 17 • March 3 • March 10 • Plenary meeting March 15-19 • Joint WG discussion during 802 Plenary in Orlando on Thursday • March 24 • Future call plans will be discussed during March Plenary Bruce Kraemer, Marvell

  16. EPRI Whitepaper New • Whitepaper • http://www.smartgridnews.com/artman/uploads/1/EPRI_1020432ConceptsAdvancementDER.pdf Bruce Kraemer, Marvell

  17. Information Source Links Bruce Kraemer, Marvell

  18. NIST • http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/WebHome • http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PAP02Wireless • Next PAP#2 meetings • 1 day at NIST HQ on March 31 Bruce Kraemer, Marvell

  19. NIST mailing list • General access portal http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PriorityActionPlans • PAP Email Lists • Email lists have been establish for each PAP. These lists support self registration using the links below. They will replace the current set. Where possible, the SGIP Administrator will autoregister those presently on the list. If you have any question, please self register and this will ensure that you are on the desired list. Bruce Kraemer, Marvell

  20. OpenSG • http://osgug.ucaiug.org/default.aspx Bruce Kraemer, Marvell

  21. Prior meeting material Bruce Kraemer, Marvell

  22. Background information • High Level Questions • National Smart Grid Perspective • EPRI View • What has previously transpired? • NIST PAP#2 • What is happening over the next two months • Longer term goals, events, project plans. • Observations/Assumptions/Conclusions/Discussion • Steps 802.11 needs to take to fit into the Smart Grid plan Bruce Kraemer, Marvell

  23. High Level Questions • What is happening in Smart Grid arena? • Is 802.11 properly positioning its existing and pending standards and amendments for acceptance in SG? • Participation in key Smart Grid activities • Are there any identifiable additions or changes that should be considered to make 802.11 more useful in SG domains? Bruce Kraemer, Marvell

  24. Observation/Assumption/Conclusion #1 • Dozens of organizations are involved but our focus is primarily on: • NIST SGIP • http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PriorityActionPlans • IEEE P2030 • Discussion: • Other 802 groups such as 802.15, 802.20, 802.16, 802.1, 802.3 Bruce Kraemer, Marvell

  25. Observation #2 • There is a substantial amount of material already created by NIST and other long term SmartGrid participants that describe Application Domains and Use Cases. • There is no need for 802.11 to duplicate this work. • There is a need to make these data flow models more complete/quantitative . • Task 1 of NIST PAP#2 intends to supply this information. • Discussion: Bruce Kraemer, Marvell

  26. AMI Use Case Report to NIST on Smart Grid Interoperability Roadmap Bruce Kraemer, Marvell Source: Report to NIST on Smart Grid Interoperability Roadmap http://www.nist.gov/smartgrid/Report%20to%20NISTlAugust10%20(2).pdf

  27. Source: Report to NIST on Smart Grid Interoperability Roadmap http://www.nist.gov/smartgrid/Report%20to%20NISTlAugust10%20(2).pdf NIST Roadmap Description of a Domain Bruce Kraemer, Marvell

  28. Other examples of Requirements • Example #1 - description of need for Home Area Network • http://osgug.ucaiug.org/sgsystems/openhan/HAN%20Requirements/OpenHAN%20Specification%20Dec.ppt Bruce Kraemer, Marvell

  29. Observation #3 • The NIST PAP#2 Tasks deserve considerable attention • Discussion: Bruce Kraemer, Marvell

  30. NIST PAP Overview (1) Priority Action Plans (PAPs) Described • PAPs arise from the analysis of the applicability of Standards to the Use Cases of the Smart Grid. PAPs include identified experts in relative SDOs, known as the PAP Working Group Management Team. • Specifically, a PAP addresses either: • A gap where a standard or standard extension is needed: • The need for meter image-download requirements is an example of a non-existing standard needed to fill an identified gap. • An overlap where two complementary standards address some information that is in common but different for the same scope of an Application: • An example of this is metering information where CIM, 61850, ANSI C12.19, SEP 1&2 all have non-equivalent methods of representing revenue meter readings. • PAPs should only be created when the SGIP determines there is a need for interoperability coordination on some urgent issue. The PAPs themselves are executed within the scope of the SDOs and Users Groups that sign up for tasks that implement the plans. The duty of the SGIP is to facilitate this process, ensure that all PAP materials are publicly available in real time on the TWiki (that is, not entirely within the domain of the SDOs which prevents all but membership access), and provides guidance when the participants in the PAP are at odds or unsure of its goals. Bruce Kraemer, Marvell

  31. NIST PAP Overview (2) • It will often be the case that the SDOs that are executing the PAP tasks (as part of the PAP Working Group Execution Team) diverge from the original intent of the PAP. This is due to their natural, and correct, orientation towards their own specific goals and needs. The PAPs arise from the broader stakeholder involvement in the Smart Grid problem space and such has identified goals that come from this broader scope. In these cases, the parties are brought together under the auspices of the SGIP and an attempt to resolve the differences is pursued. The possibility could arise where this is not sufficient to move the PAP forward. In this case the PAP WG or the SGIP can: • Revise the PAP to accommodate the concerns of the implementers, or, • Can redistribute the tasks of the PAP to organizations more in line with the needs of the scope of the PAP. • Rescind the PAP judging that it is no longer in the interest of the SGIP to pursue. Bruce Kraemer, Marvell

  32. NIST PAP2Wireless Communications for the Smart Grid (6.1.5) • http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PAP02Wireless • Abstract: • This work area investigates the strengths, weaknesses, capabilities, and constraints of existing and emerging standards-based physical media for wireless communications. The approach is to work with the appropriate standard development organizations (SDOs) to determine the characteristics of each technology for Smart Grid application areas and types. Results are used to assess the appropriateness of wireless communications technologies for meeting Smart Grid applications. Bruce Kraemer, Marvell

  33. NIST PAP#2 • Description: • Review existing documentation and ongoing work to assess the capabilities and weaknesses of wireless technologies operating in both licensed and unlicensed bands and to develop guidelines on their use for different Smart Grid application requirements. Bruce Kraemer, Marvell

  34. NIST PAP#2 • Objectives: • Identify requirements for use of wireless technologies for the Smart Grid. • Identify guidelines for effectively, safely, and securely employing wireless technologies for the Smart Grid. • Identify approaches to define the strengths and weaknesses of candidate wireless technologies to assist Smart Grid design decisions. • Analyze co-channel interference issues and develop coexistence guidelines for operation in unlicensed bands. • Identify key issues to be addressed in wireless assessments and development for the Smart Grid. Bruce Kraemer, Marvell

  35. NIST PAP#2 • Why: • Wireless technologies are one of many types of media that could meet many Smart Grid requirements by enabling access where other media are too costly or otherwise not workable. • However, different types of wireless technologies also have different availability, time-sensitivity, and security characteristics that may constrain what applications they are suitable for. • Therefore, different wireless technologies must be used with knowledge of their varying capabilities and weaknesses in all plausible conditions of operation. This work provides objective information on the appropriateness of use. Bruce Kraemer, Marvell

  36. NIST PAP#2 • Where: • Wireless can be used in field environments across the Smart Grid including generation plants, transmission systems, substations, distribution systems, and customer premises communications. • The choice of wireless or non-wireless, as well as type of wireless must be made with knowledge of the appropriate use of the technology. Bruce Kraemer, Marvell

  37. NIST PAP#2 – Next Meeting • PAP 2 session at OpenSG Users Group, San Fransisco, February 4, 2010: • A face-to-face meeting will take place on February 4th, 2010, starting at 8am until 3:00pm. This meeting is collocated with the OpenSG User Group meetings in San Fransisco during the week of February 1, 2010. Information about registration and the hotel venue can be found at: • http://osgug.ucaiug.org/sf2010/default.aspx Bruce Kraemer, Marvell

  38. NIST PAP#2 Tasks • Task 1: Segment the smart grid and wireless environments into a minimal set of categories for which individual wireless requirements can be identified. • Task 2: Develop Terminology and definitions. • Task 3: Compile & communicate use cases and develop requirements for all smart grid domains in terms that all parties can understand Bruce Kraemer, Marvell

  39. NIST PAP#2 Tasks • 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. • Task 5: Create an inventory of wireless standards and their associated characteristics (defined in previous task) for the environments identified in task 1. • Task 6:Perform the mapping and conduct an evaluation of the wireless technologies based on the criteria and metrics developed in task 4. Bruce Kraemer, Marvell

  40. NIST PAP#2 -Network Information • Both IP and wireless communications priority action plans include as a first task the development of network requirements for Smart Grid applications. • Identifying these requirements is key in order to develop guidelines for the use of IP and wireless communications in the context of the Smart Grid. Bruce Kraemer, Marvell

  41. NIST PAP#2 Functional Requirements • http://collaborate.nist.gov/twiki-sggrid/pub/SmartGrid/PAP01InternetProfile/SG_Communications_funct-reqs_v1-draft.xls Bruce Kraemer, Marvell

  42. NIST PAP#2 – Task 5 Guidance • Task 5 calls for the collection of an inventory of wireless technologies, based on the parameters and metrics developed in Task 4, to be filled by each SDO. • The purpose of the row entries in the wireless capability matrix NIST_PAP2-_Wireless_Characteristics-IEEE802-v_02.xls developed in Task 4 is to allow high level assessment of the suitability of particular wireless standard based technologies for use in various applications and domains of the Smart Grid. • Since many of the parameters in the matrix have dependencies on each other, e.g. data throughput, range and mobility, the matrix should be filled out by providing a consistent set of parameter values, rather then best case values for each parameter. • By a “consistent set” we mean that one picks some “operating point” for the technology and provides parameter values (for those that depend on operating point) that are consistent. For example, maximum data rate will not be delivered at maximum range. A column entry is expected to provide values for the error rate, range, throughput, mobility and other interrelated parameters consistent with the chosen operating point. It would be appropriate to complete more than one column for an individual technology to display the results for more than one operating point. Bruce Kraemer, Marvell

  43. NIST PAP#2 – Task 5 so far Bruce Kraemer, Marvell

  44. Observation #4 • The Matrix rows were adequate for collecting information from SDOs. • Discussion: • The rows do/do not require further modification. Bruce Kraemer, Marvell

  45. Observation #5 • The operating points used were chosen by the SDOs. • This was adequate for collecting first response information. • Discussion: • The operating point should be “standardized” to allow useful comparisons. Bruce Kraemer, Marvell

  46. Observation #6 • Within WG11, reporting on Smart Grid activities in an ad hoc forum once time block per session is adequate. • Discussion: Bruce Kraemer, Marvell

  47. Plans for Thursday • One more session Thursday am1 • Topics to be addressed: • 1. Review the operating options /selections needed for Task 5. Process or completion. • Process for moving on thru Task 6 • 2. OpenSG/PAP2 activity planning • 3. 900 Mhz ISM reband for 802.11 (Halasz presentation) • 4. Coordination mechanism with 15.4g? • 5. Link to Emergency Services? • 6. Plan for March…. Plan for ad hoc: • Avoid overlap with 15.4g – coordinate with 15.4g • Suggestion: Tuesday pm1 and Thursday am1 • Cybersecurity • EC SG Bruce Kraemer, Marvell

  48. NIST PAP#2 – Next Meeting • PAP 2 session at OpenSG Users Group, San Fransisco, February 4, 2010: • A face-to-face meeting will take place on February 4th, 2010, starting at 8am until 3:00pm. This meeting is collocated with the OpenSG User Group meetings in San Fransisco during the week of February 1, 2010. Information about registration and the hotel venue can be found at: • http://osgug.ucaiug.org/sf2010/default.aspx Bruce Kraemer, Marvell

  49. Planning for OpenSG venue • PAP#2 face to face meeting February 4 at SFO Hilton • How much data traffic flow characterization information will be available? • Will there be any matrix row changes? • How do we establish a common set of “operating points”? Bruce Kraemer, Marvell

  50. Operating Point • How should operating points be described to ensure common understanding. • How to choose “operating points” with some degree of commonality across a diverse set of radio technologies and operating scenarios to allow comparison without requiring full channel models and simulations? Bruce Kraemer, Marvell

More Related