doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 1 +1 (321) Marvell Lane, Santa Clara, CA, Name Company Address Phone Bruce Kraemer Marvell Smart Grid ad hoc Meeting Information - March 2010 Date: Authors: Abstract: Information on Smart Grid of interest to WG11 – March 2010

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 2 Introduction Ad Hoc Committee rules –No call for essential patents –AHC, is a "committee of the whole" of the WG - i.e. any WG member can contribute; in practice, anybody who turns up can speak –During f2f meetings, you can hold formal votes of only the voting members of ; on a telecon you can take straw polls, but not formal votes Required notices –Affiliation FAQ - –Anti-Trust FAQ - –Ethics - –IEEE Working Group Policies and Procedures - policies-and-procedures.doc policies-and-procedures.doc

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 3 Introduction Request for recording secretary Request for ad hoc chair

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 4 Agenda Topics - Tuesday Planned topics: 1.National Broadband plan – first pass 2.An update on the sub 1GHz project plan (Dave Halasz) commentsonsub1ghz.ppthttps://mentor.ieee.org/802.11/dcn/10/ wng- commentsonsub1ghz.ppt 3. Results and action items for NIST PAP#2 modeling sggrid/pub/SmartGrid/PAP02Wireless/PAP2modeling.ppthttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/PAP2modeling.ppt 4. Thursday meeting and call topics

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 5 Agenda Topics - Thursday Planned topics: 1.National Broadband plan – second pass 2.Update on SGIP – Mark Klerer 3. Results and action items for NIST PAP#2 modeling sggrid/pub/SmartGrid/PAP02Wireless/PAP2modeling.ppthttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/PAP2modeling.ppt 4. Subsequent conference calls and plans for May meeting

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 6 New Broadband Plan Recommendations Integrate broadband into the Smart Grid ➤ As outlined in Chapter 16, the Federal Communications Commission (FCC) should start a proceeding to explore the reliability and resiliency of commercial broadband communications networks. ➤ States should reduce impediments and financial disincentives to using commercial service providers for Smart Grid communications. ➤ The North American Electric Reliability Corporation (NERC) should clarify its Critical Infrastructure Protection (CIP) security requirements. ➤ Congress should consider amending the Communications Act to enable utilities to use the proposed public safety 700 MHz wireless broadband network. ➤ The National Telecommunications and Information Administration (NTIA) and the FCC should continue their joint efforts to identify new uses for federal spectrum and should consider the requirements of the Smart Grid. ➤ The U.S. Department of Energy (DOE), in collaboration with the FCC, should study the communications requirements of electric utilities to inform federal Smart Grid policy.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 7 Broadband Plan Recommendation 12.4 Recommendation 12.4: Congress should consider amending the Communications Act to enable utilities to use the proposed public safety 700MHz wireless broadband network. The wide-area network requirements of utilities are very similar to those of public safety agencies. Both require near universal coverage and a resilient and redundant network, especially during emergencies. In a natural disaster or terrorist attack, clearing downed power lines, fixing natural gas leaks and getting power back to hospitals, transportation hubs, water treatment plants and homes are fundamental to protecting lives and property. Once deployed, a smarter grid and broadband-connected utility crews will greatly enhance the effectiveness of these activities. Congress should consider amending the Communications Act to enable utilities to use the public safety wireless broadband network in the 700MHz band, subordinated to the communications of Section 337-defined public safety services. Jurisdictions that are licensees or lessees of the public safety 700MHz broadband spectrum should be allowed to enter into agreements with utilities on uses and priorities. At the sole discretion of the public safety licensee, utilities should also be able to purchase services on a public safety network, contribute capital funds and infrastructure or even be the operator of a joint network. These statutory changes should create more options for the construction and operation of a public safety wireless broadband network. Although the network will take years to build, carrying critical traffic from multiple users can help lower costs for all.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 8 Broadband Plan Recommendation 12.6 Recommendation 12.6: The U.S. Department of Energy (DOE ), in collaboration with the FCC, should study the communications requirements of electric utilities to inform Federal Smart Grid policy. Understanding the evolving communications requirements of electric utilities will help DOE develop informed Smart Grid policies for the nation. As an input to this plan, the FCC solicited public comment on Smart Grid technologies, and a number of utilities filed detailed responses. However, many utilities declined to comment, and others understandably declined to reveal confidential or sensitive information in public filings. DOE, in collaboration with the FCC, should conduct a thorough study of the communications requirements of electric utilities, including, but not limited to, the requirements of the Smart Grid. Building upon the FCC’s recent efforts, DOE should collect data about utilities’ current and projected communications requirements, as well as the types of networks and communications services they use.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 9

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 10 SGIP Event Schedule Plenary Officers Chair: Steve Widergren Vice Chair: Mark Klerer Secretary: Paul Molitor Upcoming Meeting Details April 23: SGIP Virtual MeetingSGIP May 24-27: 2nd SGIP Face-to-Face in Santa Clara, CA. Held in conjunction with ConnectivityWeek.SGIPConnectivityWeek July 23: SGIP Virtual MeetingSGIP Sept. 17: SGIP Virtual MeetingSGIP Oct. 29: SGIP Virtual MeetingSGIP Nov. 30-Dec. 3: 3rd SGIP Face-to-Face in Chicago, IL. Held in conjunction with Grid-InteropSGIPGrid-Interop

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 11 Tough Questions What are the consequences of not responding to the request? How much effort, from whom, how quickly needs to be contributed to meet the request? Could the June deadline for task completion be extended? How will the data provided to NIST be used by other entities in influencing deployment decisions? “Entities” range from FERC to consumer appliances Can simulation models be useful enough without selecting and constructing channel models?

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 12 Working Assumptions The ongoing interchange of information between power engineering and communications industry is essential. Computer modeling communications against PE supplied uses cases is far more useful than hand waving. Although not fully understood or quantified, there will be business incentives to being recognized as a qualified Smart Grid technology. Although not fully understood, industry would prefer to be “actively influencing” the technology selection process rather than have it dictated to them.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 13 Status Checklist 1.Is there a public simulator available to run? –Yes, NS – Yes, NIST Matlab 2.Has the simulator been recently executed to demonstrate it can produce useful results? –Yes, NIST Matlab for attendees. 3.Have any of the OpenSG uses cases been modeled? –No 4.Has anyone volunteered to run the model and report results? 5.In time for the March 31 status meeting?

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 14 Status Checklist 4.Has anyone volunteered to run the model on the use cases and report results? 4.In time for the March 31 NIST status meeting? 5.In time for May 802 Interim meeting? 6.In time for June NIST deadline? 5.Has any 802 participant validated the model results against other simulators or lab test? –No 6.Are there any known corrections or extensions to the models needed to model uses cases? – model is missing mesh – model uses only 1 Mbps, BPSK in 2.4 GHz

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 15 Status Checklist 7.Is there a better way to promote uptake of model execution? –through advertising/cooperation with universities? –through outreach/cooperation with support organizations such as Zigbee, Wi-Fi, WiMAX

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 16 Status Checklist (Additional Q & A) 7.????? –xxx 8.???? –yyy

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 17 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 develop response and action plan for June

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 18 NIST PAP#2 Goals/Events February 4 at SFO Hilton – Joint with UCAIug OpenSG Next meeting: March 31 at NIST Gaithersburg At least partial analytic results based upon execution of models against high priority Use Cases by June Neded: Clarification of how these results will be used. How are they coupled into SmartGrid Policy or Law/ What is the role of FERC?

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 19 Outline 1.Overview of NIST PAPs 2.PAP#2 goals and sub tasks 3.PAP#2 Task 6 plan 4.IEEE approach to Task 6

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 20 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 sggrid/bin/view/_SmartGridInterimRoadmap/InterimRoadmapWorks hop1 –May 2009 workshop sggrid/bin/view/_SmartGridInterimRoadmap/InterimRoadmapWorks hop2 –EPRI report to NIST, June e.pdf NIST convenes an SDO workshop in August 2009 in order to develop plans to address priority issues sggrid/bin/view/_SmartGridInterimRoadmap/PriorityActionPlans

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 21 The Current Priority Action Plans 0 Meter Upgradeability StandardMeter Upgradeability Standard 1 Role of IP in the Smart GridRole of IP in the Smart Grid 2 Wireless Communications for the Smart GridWireless Communications for the Smart Grid 3 Common Price Communication ModelCommon Price Communication Model 4 Common Scheduling MechanismCommon Scheduling Mechanism 5 Standard Meter Data ProfilesStandard Meter Data Profiles 6 Common Semantic Model for Meter Data TablesCommon Semantic Model for Meter Data Tables 7 Electric Storage Interconnection GuidelinesElectric Storage Interconnection Guidelines 8 CIM for Distribution Grid ManagementCIM for Distribution Grid Management 9 Standard DR and DER SignalsStandard DR and DER Signals 10 Standard Energy Usage InformationStandard Energy Usage Information 11 Common Object Models for Electric TransportationCommon Object Models for Electric Transportation 12 IEC Objects/DNP3 MappingIEC Objects/DNP3 Mapping 13 Time Synchronization, IEC Objects/IEEE C HarmonizationTime Synchronization, IEC Objects/IEEE C Harmonization 14 Transmission and Distribution Power Systems Model MappingTransmission and Distribution Power Systems Model Mapping 15 Harmonize Power Line Carrier Standards for Appliance Communications in the HomeHarmonize Power Line Carrier Standards for Appliance Communications in the Home 16 Wind Plant CommunicationsWind Plant Communications

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 22 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?

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide Review of PAP#2 tasks 1.Develop Smart Grid application communication requirements and devise a taxonomy for applications with similar network requirements –Draft under development and available for review sggrid/pub/SmartGrid/PAP02Wireless/app_matrix_pap.xlshttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/app_matrix_pap.xls 2.Develop terminology and definitions 3.Compile and communicate use cases and develop requirements –is part of Task 1 4.Create an attribute list and performance metrics for wireless standards –Draft developed and available for reviewhttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/NIST_PAP2-_Wireless_Characteristics-IEEE802- v_02.xlshttp://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, 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. 23

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 24 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:OpenSG Indication of interest by February 19, 2010 to assist in conducting the evaluation. Contribution of wireless technologies modeling tools by February 19, 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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 25 NIST Modeling Presentation Detailed description of the modeling approach can be found at: sggrid/pub/SmartGrid/PAP02Wireless/PAP2m odeling.ppthttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP02Wireless/PAP2m odeling.ppt

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 26 OpenSG Information Input from Open SG SG-NET received on February 22, 2010: The reference architecture models locations are: ease_2/SG-NET-diagram-r0.4e-with-Xflows.pdfhttp://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Rel ease_2/SG-NET-diagram-r0.4e-with-Xflows.pdf ease_2/SG-NET-diagram-r0.4e.pdfhttp://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Rel ease_2/SG-NET-diagram-r0.4e.pdf The SG-Network functional requirements spreadsheet location is: ease_2/SG-Net_TF_%20funct-volumteric-reqs_v2.xlshttp://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Rel ease_2/SG-Net_TF_%20funct-volumteric-reqs_v2.xls The SG-Network system requirements specification locations is: ease_2/SG%20Network%20System%20Requirements%20Specification %20v2.dochttp://osgug.ucaiug.org/UtiliComm/Shared%20Documents/Interium_Rel ease_2/SG%20Network%20System%20Requirements%20Specification %20v2.doc

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 27 NIST mailing list General access portal sggrid/bin/view/SmartGrid/PriorityActionPlanshttp://collaborate.nist.gov/twiki- sggrid/bin/view/SmartGrid/PriorityActionPlans PAP Lists 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.SGIP

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 28 NIST Modeling Tools provided by NIST and used in presentation PAP2modeling.ppt PAP2modeling.ppt nist_80211_mac.m: Matlab code for 80211_MAC_Modelnist_80211_mac.m nist_80211_MAC_readme.pdf: Readme file for using the model Matlab codenist_80211_MAC_readme.pdf SNRcdf.m: Matlab code for computing SNR probability at wireless receiverSNRcdf.m SNRcdfCell.m: Matlab code for coverage analysisSNRcdfCell.m nist_phy_model_readme.pdf: Readme file for using Matlab code for SNRcdf and SNRcdfCellnist_phy_model_readme.pdfSNRcdfCell nist_channel_propagation_models.pdf: Channel propagation modelsnist_channel_propagation_models.pdf

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide Meter Reporting Application: Mean Delay versus Offered Load

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 30 Future Smart Grid ad hoc calls Schedule plan so far has been Wednesdays at 2pm EST Feb 10 Feb 17 March 3 March 24 Future call plans will be to continue this pattern – 1 per week – to July

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 31

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 32 EPRI Whitepaper Whitepaper I_ ConceptsAdvancementDER.pdfhttp:// I_ ConceptsAdvancementDER.pdf

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 33 Initial Questions from Ted Booth As part of the PHY model, it’s not clear how NIST derived interference (I 0 ) first introduced on slide 16. In 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 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 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?

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 34 OpenSG

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 35 NIST Next PAP#2 meetings IEEE 802 centric: During 802 Plenary in Orlando either Tuesday or Thursday 1 day at NIST HQ either March 30 or 31

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 36 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 needs to take to fit into the Smart Grid plan

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 37 High Level Questions What is happening in Smart Grid arena? Is 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 more useful in SG domains?

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 38 Observation/Assumption/Conclusion #1 Dozens of organizations are involved but our focus is primarily on: NIST SGIP sggrid/bin/view/SmartGrid/PriorityActionPlanshttp://collaborate.nist.gov/twiki- sggrid/bin/view/SmartGrid/PriorityActionPlans IEEE P2030 Discussion: Other 802 groups such as , , , 802.1, 802.3

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 39 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 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:

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 40 AMI Use Case Report to NIST on Smart Grid Interoperability Roadmap Source: Report to NIST on Smart Grid Interoperability Roadmap

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 41 Source: Report to NIST on Smart Grid Interoperability Roadmap NIST Roadmap Description of a Domain

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 42 Other examples of Requirements Example #1 - description of need for Home Area Network ements/OpenHAN%20Specification%20Dec.ppthttp://osgug.ucaiug.org/sgsystems/openhan/HAN%20Requir ements/OpenHAN%20Specification%20Dec.ppt

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 43 Observation #3 The NIST PAP#2 Tasks deserve considerable attention Discussion:

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 44 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.SGIP

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 45 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:SGIP 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.SGIP

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 46 NIST PAP2 Wireless Communications for the Smart Grid (6.1.5) sggrid/bin/view/SmartGrid/PAP02Wirelesshttp://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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 47 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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 48 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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 49 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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 50 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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 51 NIST PAP#2 – Next Meeting PAP 2 session at OpenSG Users Group, San Fransisco, February 4, 2010:OpenSG 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, Information about registration and the hotel venue can be found at:OpenSG

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 52 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

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 53 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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 54 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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 55 NIST PAP#2 Functional Requirements sggrid/pub/SmartGrid/PAP01InternetProfile/SG_Com munications_funct-reqs_v1-draft.xlshttp://collaborate.nist.gov/twiki- sggrid/pub/SmartGrid/PAP01InternetProfile/SG_Com munications_funct-reqs_v1-draft.xls

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 56 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.NIST_PAP2- _Wireless_Characteristics-IEEE802-v_02.xls 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.

doc.: IEEE /0373r1 Submission March 2010 Bruce Kraemer, MarvellSlide 57 NIST PAP#2 – Task 5 so far