Priority Action Plans
PAGE CONTENTS
Priority Action Plans (PAPs) Described The Current Priority Action Plans Completed Priority Action Plans Standard Setting Organizations (SSOs) and Expected Outputs Cross PAP Issues PAP Email Lists List server etiquette Individual PAP Lists PAP Phone Conferences and Webinars Proposed Priority Action Plans Template for starting a new PAP proposal Template for starting new PAP Please Enter Any Comments Here Draft NIST Framework and Roadmap for Smart Grid Interoperability Standards, Release 2.0 : PAPs Description Please Enter Any Comments Here	Standard PAP Timeline & Milestones Cross PAP Issues Discussion Page Archived: Priority Action Plan PAP 3/4/9/10 Meeting Page Recognizing Outstanding Members: Seeking Nominations Project Management Office -- Oversees PAPs

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.

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.

The Current Priority Action Plans

The priority action plans page provides a guide to the function and operation of these plans.

#	Priority Action Plan
2	Wireless Communications for the Smart Grid
5	Standard Meter Data Profiles
7	Electric Storage Interconnection Guidelines
8	CIM for Distribution Grid Management
9	Standard DR and DER Signals
12	Mapping IEEE 1815 (DNP3) to IEC 61850 Objects
14	Transmission and Distribution Power Systems Model Mapping
15	Harmonize Power Line Carrier Standards for Appliance Communications in the Home
17	Facility Smart Grid Information Standard
16	Wind Plant Communications
19	Wholesale Demand Response (DR) Communicatiion Protocol
20	Green Button ESPI Evolution
21	Weather Information

Completed Priority Action Plans

The priority action plans page provides a guide to the function and operation of these plans.

#	Priority Action Plan
00	Meter Upgradeability Standard
01	Role of IP in the Smart Grid
03	Common Price Communication Model
04	Common Schedule Communication Mechanism
6	Common Semantic Model for Meter Data Tables
10	Standard Energy Usage Information
11	Common Object Models for Electric Transportation
13	Harmonization of IEEE C37.118 with IEC 61850 and Precision Time Synchronization
18	SEP 1.x to SEP 2 Transition and Coexistence

Standard Setting Organizations (SSOs) and Expected Outputs

This table shows SSO leads and outputs for each PAP.

PAP	SSO Lead(s)	Output
00	NEMA	NEMA SG-AMI1 Standard, published in 2009.
01	IETF	IETF Requests For Comment (RFC’s) Approximately 80 are referenced in the “core “ document for this PAP. Well defined networking “stacks” will use a subset of these core standards
02	IEEE, EIA, WIMAX Forum, TIA, 3GPP2, ATIS, 3GPP, ETSI	IEEE 802 series: IEEE 802.11, 802.15.4, 802.16, IPOS DVB S2, CDMA 2000 series, TIA HRPD and MPS series, 1X-EV-DO, EDGE, UMTS, HSPA+, LTE
03	OASIS, ZigBee, NAESB	OASIS Energy Market Information Exchange, SEP2
04	CalConnect, IETF, OASIS, NAESB	OASIS WS-Calendar
05	AEIC, ANSI, IEEE, MC	AEIC v2.0 Guidelines for implementing ANSI/IEEE/MC metering protocol standards; Improved/clarified ANSI/IEEE/MC metering protocol standards; Tutorial/education materials on metering protocol standards
06	PAP06	Technical mappings between key standards (ANSI/IEC, ANSI/MultiSpeak), integration roadmap, White Paper for IKB
07	IEEE SCC21, IEC TC57 WG17	IEEE 1547.8, IEC 61850-7-420
08	IEC TC 57 WGs 13, 14, 17	IEC 61968, IEC 61970, IEC 61850
09	OASIS, LBL OpenADR, ZigBee, NAESB, ASHRAE, LonMark	OASIS Energy Interoperation, SEP2
10	UCAIug, EIS Alliance, ANSI, NAESB, OASIS, IEC, IEEE, Open ADR, IEC, ASHRAE, ISA, OVDA	IEC 61968, IEC 61850, SEP 2, ASHRAE 135/189, ANSI C12.19/22, EIA 721, EIA 709, OASIS Open ADR, Open ADE
11	IEC TC 57, IEC TC 69, UL, NEC, NEMA, IEEE 1547, SAE	IEC 61850-7-420, IEC 61968, IEC 61970, IEEE 1547, SEP 2, SAE, NEMA, UL, NEC Codes
12	IEC, DNP User’s Group, IEEE, UCA-IUG	IEC 61850-80-2, DNP3 Application Note, Potential (not confirmed) Changes to: DNP3, IEEE P1815, IEC 61850
13	IEEE, IEC, NASPI	IEEE C37.118.2 (updated version), IEC 61850-90-5, IEEE C37.238, Potential (not confirmed) Changes to: IEC 61850, IEEE 1588, NASPI Guidelines and Specifications, IEEE 1815, DNP3 documents
14	IEC TC 57 Working Groups 10, 13,14,16, 17,19 IEEE PSRC H5, H16, Multispeak	IEC 61850, IEC 61970, IEC 61968, IEEE C37.239, IEEE C37.237 MultiSpeak v1-v4
15	IEEE, ITU-T	IEEE 1901, IEEE 1901.2, ITU-T G.hn (G.9960, G.9961), G.cx (G.9972), ITU-T G.hnem, ISO/IEC 14908-3 (LonWorks ), ISO/IEC 14543 (ST/KNX), EN 50065-1
16	IEC	61400-25, Wind Plant Communications, based on 61850
17	ASHRAE	Facility Smart Grid Information Model standard.
18	ZigBee Alliance, H2G DEWG	SGIP White Paper, detailing specific requirements that must be met to allow for the coexistence of SEP 1.x and 2.0 and to support the migration of 1.x implementations to 2.0.
19	ISO/RTO Council (IRC)	A common wholesale market (ISO/RTO) to market participant Demand Response interface profile(s) to support pricing or grid condition communications with minimal translation of semantics as information flows from market participants to consumers in cascade.
20	NAESB, UCAIug, OpenESPI	Deliverables in a modest timeframe to support the growing support for a critical standard of the Smart Grid - the ubiquitous availability of Energy Usage Information, and, a marketplace of sources and uses of that data.
21	TBD	...

Cross PAP Issues

Goto: Cross PAP Issues Discussion Page

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.

List server etiquette

• Include a signature tag on all messages. Include your name, affiliation, location, and e-mail address.
• State concisely and clearly the specific topic of the comments in the subject line. This allows members to respond more appropriately to your posting and makes it easier for members to search the archives by subject.
• Include only the relevant portions of the original message in your reply, delete any header information, and put your response before the original posting.
• Only send a message to the entire list when it contains information that everyone can benefit from.
• Send messages such as “thanks for the information” or “me, too” to individuals—not to the entire list. Do this by using your e-mail application's forwarding option and typing in or cutting and pasting in the e-mail address of the individual to whom you want to respond.
• Do not send administrative messages, such as remove me from the list, through the list server. Instead, use the web interface to change your settings or to remove yourself from a list. If you are changing e-mail addresses, you do not need to remove yourself from the list and rejoin under your new e-mail address. Simply change your settings.
• Warn other list subscribers of lengthy messages either in the subject line or at the beginning of the message body with a line that says “Long Message.”

Additionally

• The listserv is principally for technical discussion related to the PAPs.
• Files should NOT be distributed on the listserv list, rather they should be attached to the relevant TWiki topic page and a link shared via the listserv list.
• Issues with the listserv operation should be sent to ListservHelp@enernex.com and NOT to the listserv list itself.
• The listserv software maintains an archive of ALL messages and attachments sent through the listserv list. This archive is available to all listserv list members.

Individual PAP Lists

Email lists have been establish for each PAP. Use the entries in the table below to send an email to one of the lists, to register your email to be part of the list, or, to review the list archives. These lists support self registration.

Send an email to PAP Email List	Join a PAP Email List	Review Achive of Email List
Closed. PAP is complete.	Not possible. PAP is complete.	PAP00 listserv archive file in .txt format
Closed. PAP is complete.	Not possible. PAP is complete.	PAP01 listserv archive file in .txt format
SGIP-PAP02WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP02	SGIP-PAP02WG
Closed. PAP is complete.	Not possible. PAP is complete.	PAP03 listserv archive file in .txt format
Closed. PAP is complete.	Not possible. PAP is complete.	PAP04 listserv archive file in .txt format
SGIP-PAP05WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP05	SGIP-PAP05WG
SGIP-PAP06WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP06	SGIP-PAP06WG
SGIP-PAP07WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP07	SGIP-PAP07WG
SGIP-PAP08WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP08	SGIP-PAP08WG
SGIP-PAP09WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP09	SGIP-PAP09WG
Closed. PAP is complete.	Not possible. PAP is complete.	PAP10 listserv archive file in .zip format-NOTE 16.3MB!
Closed. PAP is complete.	Not possible. PAP is complete.	PAP11 listserv archive file in .txt format-NOTE 15.9MB!
SGIP-PAP12WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP12	SGIP-PAP12WG
SGIP-PAP13WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP13	SGIP-PAP13WG
SGIP-PAP14WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP14	SGIP-PAP14WG
SGIP-PAP15WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP15	SGIP-PAP15WG
SGIP-PAP16WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP16	SGIP-PAP16WG
SGIP-PAP17WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP17	SGIP-PAP17WG
Closed. PAP is complete.	Not possible. PAP is complete.	PAP18 listserv archive file in .txt format
SGIP-PAP19WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP19	SGIP-PAP19WG
SGIP-PAP20WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP20	SGIP-PAP20WG
SGIP-PAP21WG@SMARTGRIDLISTSERV.ORG	Join SGIP-PAP21	SGIP-PAP21WG

PAP Phone Conferences and Webinars

Please find all working group phone conferences and webinars on the SGIP Calendar topic page

Proposed Priority Action Plans

Pages that contain proposed Priority Action Plans are listed here:

• PAPXXCommonSemanticModel: A Common Semantic Model for the SGIP
• PAPYYBottomUpCIM61850: Possible Next Effort: Bottom-Up CIM-61850 Cross-Modeling
• PAPZZAMISecurityRequirements: Standardized security requirements for advanced metering infrastructure
• PAPMS: Joining together MultiSpeak® and IEC 61968 through modeling.
• PAP19 PEV Fast Charge Requirements: The existing gaps in configurations of fast charge equipment and impact on interoperability are the purpose of this Priority Action Plan.
• PAP21WeatherInformation : A Common Weather Information Model

Template for starting a new PAP proposal

Use this template page to construct/propose a new PAP.

1. Create your new page using the Create New Topic” menu choice on the left of the page under “General Links”.
2. When it creates the page, just save and go to the next step.
3. Go to this link: Priority Action Plan Template
4. Select on the bottom menu "raw view"
5. Click cursor inside this view of page in "TWiki text"
6. Copy
7. Go to your new page
8. Select Edit it in raw mode
9. Paste the sample template from the clipboard
10. Edit as appropriate
11. Add a comment to the PriorityActionPlans topic page to describe your proposed PAP and put the name of the page in the comment so that the link is available to folks to navigate to it.

Template for starting new PAP

Use this page (copy and edit contents) to establish a new PAP workspace after PAP approval

1. Make copy of page NEW PAP PAGE CONTENTS using the page titel PAPxxDescriptionCamelCase
2. Add entry to main TWiki page table of PAP links
3. Add entry to PriortyActionPlans TWiki page
4. Edit PAP page replacing "xx" where appropriate and adding content

Please Enter Any Comments Here

Note comments actually on this topic page: PriorityActionPlansCommentPage

Comment	User	Date
Enter comments here for Priority Action Plans in general. Put comments on the specific PAP pages for those PAPs.	MartyBurns	2009-12-27 - 12:55
After reading the road map, these action plans, and several other documents, there appear to be a number of gaps in both documentation and planning that are important to achieve effective interoperability in the smart grid. It is possible I have missed some information. If that is the case, I would appreciate pointers to the information. The comments that follow are general, I will write suggestions for the creation of additional PAPs on the appropriate pages with additional details. ;Many different Protocol and Data Definition/Modeling Activities: ;Interoperability is, in part, a function of complexity. The more standards we have for protocols, data models, data definition languages, along with the translation software needed to convert one to the other, the more complex and costly it will be to develop software applications. In this context, software applications are integrated service applications that are more sophisticated than the stove pipes that would spring up around each standard such as those centered around smart meters, or distribution systems, etc. I will propose a PAP to look at this issue. ; ;Scope: ;Transmission, Distribution, Smart Meters, and many other elements have been detailed in these pages, yet there is no one place that I can find that clearly outlines the the full scope of what is intended to be in the smart grid domain. The roadmap does have pictures that hint at this a bit, but significant expansion is needed so that everyone is clear. For example, the Internet is mentioned, but to what degree and how it is envisioned to play in this environment is not clear. Understanding this and other issues is fundamental to understanding work ahead. ; ;Requirements: ;What are the requirements of the interoperable system? How much information must flow and in what units of time? What elements must be understood across the boundaries described other documents. If there are interfaces to be developed at boundaries of the generation, transmission, distribution, customer and business environments, what are the requirements for them. There are two issues here. The first involves details of what and how, the second is concerned with understanding the larger system and how it impacts each of these interfaces. There are probably two different PAP activities possible. The first would be an effort to take an ‘end-to-end view of all the systems involved and identify the issues across all these boundaries (looking at security from this perspective is also helpful). The second would be requirements, these requirements can have an important impact on the protocols, data models etc. currently under discussion. ; ;Internet Role: ;The Internet is more than a collection of protocols. The role it might play in the smart grid should be fleshed out more fully since it too will have a significant impact on boundaries and the standards that flow across them. It seems this work, like the other items listed above should come before, or at least be concurrent with the PAPs currently underway.	JonSaperia	2009-12-28 - 15:00
	JonSaperia	2010-01-30 - 09:29
I have created drafts for: InternetIntegration, PAPDataModeIing , and PAPRequirementsAndScope to act as a starting place for discussions on my points about data modeling, scope, requirements and Internet role.	JonSaperia	2010-01-30 - 09:30
I think there is an issue of the nature of the interface between the PAPs/DEWGs/SGAC and the SDO's. I have had an extended email discussion today regarding the interface between the SGIP activities and IEEE P2030. The PAPs/DEWGs/SGAC are doing architecture and use cases, presumably to define requirements for standards. For that purpose they are identifying tools. P2030 is also doing architecture and use cases that overlap those being developed by SGIP activities and are choosing tools for that effort. If the tools, use case structures/formats, and use cases themselves are not compatible and coordinated, there will likely be extensive duplicate work in possibly incompatible structures. The duplication will mean that resources will not be available to fill gaps, so both sets of work will be less complete and increasingly difficult to harmonize. <br /><br />Based on aspects of the discussion, the problem appears to be that the interface between the SGIP efforts (PAPs/DEWGs/SGAC, etc.) and the SDOs is not clearly defined, and the need for compatible/interoperable tools across that interface has not been addressed.<br /><br />The definition of this interface needs to be addressed on a priority basis, especially as it applies to P2030, or the harmonization of the incompatible efforts will become increasingly difficult to solve and efforts will be wasted. Stan, I completely agree with you about being concerned about duplication of effort. I'm also quite aware of the need for better definition of the relationships within the SGIP and between the SDOs. What you are probably not aware of is that we have been working feverishly for nearly 2 months to help define that handoff and those relationships. I have personally worked with the Governing Board, the Administrator team, NIST, AND IEEE, in particular, to get that relationship defined. I actually just got our first version of the PAP Project Lifecycle approved yesterday. That lifecycle shows the business process we plan to use as well as the specific artifacts that fall out of each organization. We will be posting that in the coming days and it is public information - I'll send it to you offline until we can get it posted. I want a very clear hand off between the SGIP and the SDOs. The SGIP does NOT write standards. Period. However, we do provide requirements for standards to SDOs, and that is what the lifecycle BPM explains. We will also talk about this in depth at the F2F in March - our "taking care of business" meeting which will help define not only that relationship, but also the relationships between all the other organizational entities you discussed above. This is one of my many #1 priorities and you are spot on in identifying it as something needing attention. - Stuart McCafferty	StanKlein	2010-02-18 - 21:30

• 15sept2010IEEE-ITU-T_PAP15.pptx: IEEE-ITU-T-Joint-work-update

Draft NIST Framework and Roadmap for Smart Grid Interoperability Standards, Release 2.0 : PAPs Description

• PAPs.docx: Draft Release 2.0 PAPs Description

Please Enter Any Comments Here