Minutes Data Exchange Working Group January 16, 2014

Size: px

Start display at page:

Download "Minutes Data Exchange Working Group January 16, 2014"

Mildred Martin
5 years ago
Views:

1 Minutes Data Exchange Working Group January 16, 2014 NERC Atlanta Office 3353 Peachtree Road NE Suite 600, North Tower Atlanta, Georgia The Data Exchange Working Group (DEWG) met on January 16, 2014 in Atlanta, Georgia. The meeting agenda and attendance list are affixed as Exhibits A and B, respectively. DEWG Chair Keith Mitchell presided. Larry Kezele announced that a quorum was present, read the applicable Notice of Public Meeting, and summarized the NERC Antitrust Compliance Guidelines. Data Exchange Working Group Meeting Minutes The working group approved the minutes of the October 17, 2013 meeting. Future Meetings The working group reviewed and revised the list of future meetings. 1. April 10, 2014 (8 a.m. 5 p.m.) in Atlanta, GA, hosted by NERC 2. Locations of future meeting to be determined Data Exchange Working Group Roster and NERC List Servers The working group reviewed and revised the DEWG roster and the dewg@nerc.com, the dewg_plus@nerc.com, and the isnoos@nerc.com list servers. Review of Action Items The working group reviewed the status of action items identified during its last meeting. The updated action item list is attached as Exhibit C. Eastern Interconnect Data Sharing Network (EIDSN) Chair Mitchell briefed the working group on the startup activities being undertaken by the EIDSN. EIDSN has incorporated in Delaware as a non-for-profit corporation. NERC is expected to transition the NERCnet Verizon contract to the EIDSN by the end of March The EIDSN will rewrite NERC s NERCnet request for proposal. Finally Chair Mitchell noted that the EIDSN may encourage NERC to maintain the DEWG and the Telecommunications Working Group until the new NERCnet is installed and functioning. Chair Mitchell introduced Rich Mandes, Southern Company who will be the Treasurer/Secretary of EIDSN. Mr. Mandes identified all of the current members of the EIDSN. The mission of EIDSN is to develop a

2 mechanism by which essential operational data can be shared securely, consistently, and efficiently among the EI reliability coordinators. EIDSN wants to complete the transition of NERCnet by the end of the first quarter of 2014 (i.e., transition the Verizon contract to EIDSN). EIDSN is expected to develop a replacement NERCnet by the end of the first quarter of Mr. Mandes also discussed the details leading to the formation of the EIDSN Corporation. The first board of directors meeting is scheduled to be held in mid-february The EIDSN will also create an Advisory Committee of key operational personnel within each member company. The DEWG and the Telecommunications Working Group will likely report to the Advisory Committee in the near future. Mr. Mandes reviewed the work of the New Network Leadership Team, which is being led by Jim McNierney, NYISO. He reviewed the new network development objectives and outlined the next steps/action items, which includes having a new vendor selection by August/September Review of ISN Data Definition Files Vice Chair Aclin reviewed the status of updates to ISN data definition files and noted that fewer entities are not updating their ISN data definition files as required by the ISN Node Responsibilities and Procedures document. The working group reviewed and revised a listing of those having read/write access to the ISN private files website. ISN Data Point Definition Analog and Status Value Format Vice Chair Aclin reviewed Version 2.5 of the ISN Data Point Definition Analog and Status Value Format document. Robert Kingsmore is investigating the inclusion of automatic watt regulators (AWRs), automatic VAR regulators (AVRs) and sign conventions on flows into and out of busses and transformers and will develop a proposal for discussion at the working group s next meeting. ICCP Association Information Exchange Form Steve Graber reviewed Version 3.2 of the ICCP Association Information Exchange Form, dated January 17, 2013 and proposed a minor modification to the form. Steve Graber moved to approve Version 3.3 of the ICCP Association Information Exchange Form (Exhibit D). The working group approved the motion. Phasor Data Concentrator Information Exchange Form Steve Graber reviewed Version 1.1 of the Phasor Data Concentrator Information Exchange Form, dated January 17, The DEWG did not recommend any revisions to the Phasor Data Concentrator Information Exchange Form as a result of this review. SAFNR, Version 2, Pattern File Data Request Chair Mitchell reported that Sam Chanoski, Associate Director of Bulk Power System Awareness, has requested new SAFNR, Version 2, pattern files from each reliability coordinator representative to the Operating Reliability Subcommittee. Meeting Minutes Data Exchange Working Group January 16,

3 Eastern Interconnection Time Monitor Chair Mitchell reported that on February 1, 2014 the Eastern Interconnection Time Monitor will transition from the VACAR-S reliability coordinator to the SPP reliability coordinator. Vice Chair Aclin questioned how SPP would transmit via ICCP the required time error correction information to NERC for display in the Reliability Coordination Information System. PMU Registry Validator Test Files Subsequent to the April 19, 2012 working group meeting, Steve Graber sent the PMU registry validator to Chair Mitchell and Larry Kezele. Steve Graber informed the working group that he has begun development of PMU registry validator test files and reviewed his current progress. Status of DEWG Documents The working group reviewed and revised a spreadsheet which identifies documents posted on the working group s website (Exhibit E). ISN Node Status Reports This agenda item provided working group members the opportunity to provide a status report related to implementation of EMS projects, NERCnet connectivity projects, and other items of general interest. Next Meeting The next DEWG meeting will be on April 10, 2014 in Atlanta, Georgia. Adjournment The working group meeting adjourned at 3:38 p.m. EST on January 16, Larry Kezele Larry J. Kezele Secretary Meeting Minutes Data Exchange Working Group January 16,

4 Agenda Data Exchange Working Group January 16, :00 a.m. 5:00 p.m. EST NERC Atlanta Office 3353 Peachtree Road NE Suite 600, North Tower Atlanta, Georgia Dial-in Number: Access Code: Security Code: Introductions and Chair s Remarks NERC Antitrust Compliance Guidelines and Public Announcement Agenda Items 1. Administrative Matters a. Arrangements Larry Kezele b. Announcement of Quorum Larry Kezele c. Parliamentary Procedures* - Larry Kezele d. Approve Agenda Chair Mitchell 2. Approve Minutes of October 17, 2013 Meeting* Chair Mitchell 3. Future Meetings a. April 10, 2014 (8:00 a.m. 5:00 p.m.) Atlanta, GA, hosted by NERC b. Location of Future Meetings c. Schedule Future Meetings 4. Review of Data Exchange Working Group (DEWG) Roster and List Servers* Chair Mitchell a. DEWG Roster b. DEWG List Server c. DEWG Plus List Server d. ISNOOS List Server 5. Review Action Items* - Larry Kezele 6. Eastern Interconnection Data Sharing Network Status Report Chair Mitchell

5 7. ISN and PMU Data Definition Files a. Review of ISN and PMU Data Definition File Submission Vice Chair Aclin b. Review of Access Rights to ISN and PMU Data Definition Files* Larry Kezele 8. ISN Data Point Definition Analog and Status Value Format* Vice Chair Aclin 9. ICCP AIE Form Version 3.2* Steve Graber 10. PDC Association Information Exchange Form* Steve Graber 11. SAFNR, Version 2, Pattern File Data Request Chair Mitchell 12. Review PMU Registry Validator Test Files Steve Graber 13. Information Status of DEWG Documents* All 14. Discussion ISN Node Status Reports Chair Mitchell *Background materials included. DEWG Meeting Agenda January 16,

6 Exhibit B Data Exchange Working Group Meeting Attendance January 16, 2014 Atlanta, Georgia Name Chair (MISO) Vice Chair (SPP) SPP IESO ERCOT Southern ISO-NE NYISO PJM VACAR-S HQT FPL (FRCC) TVA Southern Company NERC NERC NERC NERC NERC Keith Mitchell Scott Aclin Matt Beck Anca Fatu Steve White Ramya Subramanian (speakerphone) Brock Nubile Steve Graber Jim Ortlieb Robert Kingsmore Maxime Nadeau Deepal Rodrigo (speakerphone) Joey Burke (speakerphone) Rich Mandes Marvin Santerfeit David Kruke Jeff Hicks Sam Chanoski Larry Kezele - 1 -

7 Exhibit C Data Exchange Working Group Open Action Items List Assigned Subject Action Item/Assignment Due Date NERC Larry Kezele Steve Graber MPLS Plan NERC s Roles and Responsibilities document Request NERC to develop a timeline and plan for implementing MPLS on NERCnet Chair Mitchell reported that NERC is still working with Verizon to complete this project. TWG and Verizon scheduled a conference call on 4/19/12 to review current status. Chair Mitchell will discuss this with TWG Chair Clifton Johnson Chair Mitchell reported that MPLS will only be used on Option 2. Option 1 will remain on frame. About 60% of the Option 2 sites have been converted to MPLS Roman Carter reported that MPLS is in service on 14 of 20 ICCP nodes on Option 2. No Option 1 sites have been converted to MPLS Option 1 started from perspective of ordering circuits, but is now placed on hold. NERC staff is having weekly meetings with Verizon to resolve operational concerns and previous Verizon commitments Option 1 remains on hold Option 1 remains on hold Option 1 remains on hold. Waiting on EIDSN for final resolution Waiting on EIDSN for final resolution Mr. Graber will summarize responses received from his request for comments and the working group s discussion of the NERC s Roles and Responsibilities document for discussion at the working group s next meeting Chair Mitchell will arrange a conference call with NERC staff to discuss recent NERCnet outages and NERC response to those outages. In addition, he will engage NERC staff on the development of NERCnet Operational Procedures document Completion Date 1

8 Assigned Subject Action Item/Assignment Due Date Steve Graber PMU Validator Test File Chair Mitchell Requiring Option 2 on NERCnet Chair Mitchell will arrange a conference call with NERC IT, given Brian Nolan s having left NERC Chair Mitchell will invite Marvin Santerfeit to the January 2013 DEWG meeting to discuss this open action item Marvin Santerfeit will send NERC s internal procedure to the TWG and the DEWG. In addition, NERC will discuss with Verizon the possibility of providing NERCnet users access to Verizon s trouble ticket system Should roll this requirement into a procedures document with the RFP This should be a deliverable from the selected vendor for the new NERCnet This should be a deliverable from the selected vendor for the new NERCnet, possibly provided under the ownership of the EIDSN No change in status Chair Mitchell will develop a PMU validator test file based upon the draft PMU data definition file structure Chair Mitchell reported no progress Chair Mitchell reported no progress Chair Mitchell reported no progress Chair Mitchell reported no progress Chair Mitchell reported no progress. Task assigned to Steve Graber Steve Graber reported no progress In progress Chair Mitchell to discuss with the ORS requiring the installation of Option 2 at those NERCnet nodes that have not yet added it Chair Mitchell summarized his presentation to the ORS at its November 2012 meeting. VACAR-S is considering moving to Option VACAR-S working on installing Option 1 (MPLS), before moving to install Option In limbo given possible Verizon upgrade and release of new NERCnet Request for Proposal Completion Date

9 Assigned Subject Action Item/Assignment Due Date Vice Chair Aclin Working Group Larry Kezele Enhance DDF Report to include PMU DDFs Contact ISN Nodes to assure adherence to Version 2.5 of the ISN DDF Document NERC Link to SAFNR Defer to the EIDSN. Should this be a new requirement of the new NERCnet? Defer to the EIDSN. Close this action item Vice Chair Aclin to modify the DDF Report database to include PMU DDFs Vice Chair Aclin reported that this is still in progress Vice Chair Aclin reported that this is still in progress Vice Chair Aclin reported that this is still in progress Vice Chair Aclin reported that this is still in progress. In addition, there are no PMU DDFs posted No change in status Contact all ISN Nodes to assure adherence to Version 2.5 of the ISN DDF Document In progress In progress In progress In progress In progress Can data going to the existing NERC link be moved to the SAFNR link? ? There is a legal issue around the Chain of Custody of the data. The reason that we had to have Node was that someone stated that the data has to be provided directly to NERC via a NERC managed Node we can t get it from a secondary source as we wouldn t be able to verify the data was not altered by the third party. Let s say we can get around the legal issue and use SmartCloud s Node. This won t be able to occur anytime soon as we would have to re-write all the data feeds to RCIS, CIPIS, CRC, and Resource Adequacy, Tag Dump Process and several other application / functions. We have extensive custom code that was developed many years ago to feed data to the systems above. If this is something that is necessary then the PMO needs to be engaged to manage the project as this will be a very large task Ongoing Completion Date

10 Assigned Subject Action Item/Assignment Due Date Larry Kezele Status of NERC s NERCnet Backup Node Larry Kezele will discuss with NERC IT initiation of a project to resolve identified ICCP shortcomings This action item will be discussed at the working group s 1/16/14 meeting in Atlanta. NERC IT will be invited to the January NERC IT will further investigate Where is NERC s backup node located? What are its current parameters? Will NERC be testing its backup node? NERC does not have a backup node and we never have had a backup node. Since NERC use the node for reporting there was never a reason from NERC to have a backup node DEWG questioned the statement that NERC does not have a back-up NERCnet node. However, David Kruke confirmed that NERC does not have a backup NERCnet node NERC will confirm which IP addresses are used to reach NERC. NERC may request/approve removal of one of those associations? In other words, NERC should send out its AIEF form to all other ISN nodes NERC s Primary node only has one Network Interface Card. NERC has never operated a secondary node. Larry Kezele NERCnet Metrics Robert Jackson and Jeff Hicks will review the development of NERCnet metrics NERC will escalate its request for NERCnet metrics with Verizon DEWG still not receiving NERCnet metrics DEWG still not receiving NERCnet metrics. Defer this action item to the EIDSN, since it is required in the RFP Close this action item, transition to the EIDSN. Completion Date

11 Critical Energy Infrastructure Information Association Information Exchange Form The attached ICCP Association Information Exchange Form has been created to facilitate ICCP associations between ICCP nodes. All fields are required to create an association. ICCP node administrators should fill out this form using their own setup information. Thus the form will contain information supplied by company-a to company-b detailing the parameters needed during company-b s ICCP association configuration. Note that similar information needs to be supplied by company-b to company-a. Date: Company-A: Contact for Company-A: Company-B: Contact for Company-B: General Notes: January 16, 2014 Version 3.3 1

12 Critical Energy Infrastructure Information ICCP Association Information Exchange Form Table 1: Company-wide / Server independent information 1. ICCP vendor and platform The name of the Company-A s ICCP vendor, vendor software version, as well what operating system and hardware platform used for the ICCP servers. 2. Number of possible ICCP servers: This is the total number of ICCP servers that may be available to a remote client to associate with. Include backup servers if they have unique addresses. This number should equal the number of copies of Table 2 included in this form. Typically Company A s domain name: The domain name of company A. Recommended to be the 4 character ISN node name of Company-A. 4. Company B s domain name: The domain name of company B. Recommended to be the 4 character node name of company-b. 5. Association type Single direction Client-Server : Enter this if Company A s and Company B s ICCP nodes act as either Client or Server over one association. Information can be sent in only one direction per association. The client must initiate the association. Dual direction Client-Server : Enter this if Company A s and Company B s ICCP nodes act as Client and Server over one association. Information can be sent in either direction per association. The association type is determined by prior agreement between the two users. Typically Dual direction Client-Server. 6. Association Initiation: This field is only used if the association type is Dual direction Client-Server and indicates which ICCPnode shall initiate the association (e.g. company-a). The initiator of the association is determined by prior agreement between the two users. 7. Bilateral table ID: Company A s bilateral table name used when Company B is accessing Company A s data (e.g. 1.1 ). 8. Supported ICCP services: A list of the conformance blocks supported by the server (e.g. Blocks 1, 2). 9. ICCP version: The version of ICCP running on the server (e.g. TASE.2 Version ). January 16, 2014 Version 3.3 2

13 Critical Energy Infrastructure Information ICCP Association Information Exchange Form 10. Shortest periodic interval: Frequency in seconds at which Company B can request data from Company A. 11. Maximum MMS PDU size. Size in bytes of the maximum MMS protocol data unit. January 16, 2014 Version 3.3 3

14 Critical Energy Infrastructure Information ICCP Association Information Exchange Form Table 2: ICCP Server specific information 1. Server names and descriptions: The names by which company-a refers to these servers. (Note: The following information boxes must remain in same server order!) 2. IP network addresses: If you are using TCP/IP, this optional field is the IP address for this ICCP server if TCP/IP can be used as the network transport. 3. AP Titles: Object identifier representing the Application Process Title given to this application. The standardized format of the AP Title is found in Appendix A. 4. AE Qualifiers A long integer (32 bit signed) is used to qualify the application entity. 5. Presentation Selectors (PSEL) 2 or 4 byte number used to select the correct instance of the presentation layer (e.g or ). 6. Session Selectors (SSEL) 2 or 4 byte number used to select the correct instance of the session layer (e.g or ). 7. Transport Selectors (TSEL) 2 or 4 byte number used to select the correct instance of the session layer (e.g or ). 8. X.509 Certificate filename Subject CN, and expiration date. The current in use certificate information for this server identified by the filename and the CN contained in the subject field of the certificate. (Note: Only required if running Secure ICCP) January 16, 2014 Version 3.3 4

15 Critical Energy Infrastructure Information ICCP Association Information Exchange Form Appendix A: AP Title Standard The AP Title is used by some ISO applications to determine what application is calling since NSAP s, TSEL s, SSEL s and PSEL s of the caller may not passed to applications upon association. The AP Title consists of 9 16 bit decimal numbers: Field Name Field format One single 16 bit One 16 bit Seven 16 bit decimal integers decimal integer) decimal integer Required value in decimal 2 (joint-iso-ccitt) 16 (country based naming hierarchy) For example, an ICCP application at MAIN1 would have an AP Title of: XXXX XXXX XXXX XXXX YYYY 0073 (3826 is the abbreviated NERC org ID used to specify ISN applications), XXXX XXXX XXXX XXXX is for the registered ISN node ID in decimal (one 16 bit decimal number for each ASCII character in the site ID including padding underscores), YYYY is the for the node number (one 16 bit decimal number), the last 16 bit number is an application specification where decimal 0073 indicates ICCP.) Note: Some ICCP vendors do not provide a user interface for setting AP Titles. In this case the user may be required to manually edit a Directory Information Base ASCII file. ASCII to Hex and Decimal Conversion Table: ASCII Dec ASCII Dec ASCII Dec ASCII Dec _ I 73 R A 65 J 74 S B 66 K 75 T C 67 L 76 U D 68 M 77 V E 69 N 78 W F 70 O 79 X G 71 P 80 Y H 72 Q 81 Z 90 Note: Only use this ASCII conversion table to calculate the AP Title. January 16, 2014 Version 3.3 5

16 Critical Energy Infrastructure Information ICCP Association Information Exchange Form Revision history: Version Date Comments 1/16/98 Added transport layer parameters Added AP Title and NSAP appendices 1/23/98 Fixed IP addressing and association parameter errors Changed AP Title standard 2/24/98 Added ICCP vendor information 5/20/98 Added more instructions to help user fill out forms. 5/26/98 Added cover page Added M,R,O column 9/25/98 Moved rows (formerly labeled now labeled ). Deleted row (formerly labeled 1.5) 12/1/98 In table 2, changed fields 4, 8, 9, and 10 from Recommended to Mandatory 1/19/99 Fixed typographical errors 5/13/99 Moved Association type and initiator from Table 2 to Table 1. Updated version number and date in header/ footer. [kbp] 7/15/1999 Made AP Titles mandatory per Version 2.0 Appendix B. Removed John Gillerman as document owner. Upgraded document to Version /9/2009 Made extensive revisions due to initial Version 3.0 yearly document review. 1/12/2012 Minor syntax fix. Annual approval at Version 3.1 1/17/2013 Version 3.2 1/16/2014 Version 3.3 NERC DEWG meeting. Added the phrase Critical Energy Infrastructure Information to the document Header. Moved date, contacts, general notes to cover page. Reviewed and approved at NERC DEWG meeting. January 16, 2014 Version 3.3 6

17 Exhibit E Document DEWG Validator files DEWG Scope Media DEWG Site Public / Private Location Various Private a/ Acrobat/ Word Status of DEWG Documents January 16, 2014 Lead Reviewer Scott Actin and Keith Mitchell Comments Will review all validator files and make any required changes Public DEWG Scope Steve Graber Scope approved by ORS on May 7, Update Status Ongoing Review Scope at the July 2014 meeting. ISN Node Responsibilities and Procedures - Version 2.5 ICCP Association Information Exchange Form - Version 3.2 Acrobat/ Word Acrobat/ Word Public ISN Node Responsibilities and Procedures - Version 2.5 Robert Kingsmore Approved Version 2.5 at April 2013 DEWG meeting. Public ICCP AIE Form - Version 3.2 Steve Graber Approved Version 3.3 at January 2014 DEWG meeting. ISN Data Point Definition - Analog and Status Value Format Acrobat/ Word Public ISN Data Point Definition - Analog and Status Value Format Scott Aclin Approved Version 2.5 at October 18, 2012 meeting. Continue review Version 2.5 at January 2014 meeting.

18 Document ICCP Implementation Standards Version 4.1 PMU Data Definition File Media Acrobat/ Word DEWG Site Public / Private Public Location ICCP Implementation Standards Version 4.0 Excel Public PMU Data Definition File Information - Version 1.0 Lead Reviewer Robert Kingsmore Comments Version 4.1 approved at July 2013 DEWG meeting. Update Status Review Version 4.1 at July 2014 meeting. Steve Graber Review Version 1.0 at the April 2014 meeting. PMU DDF Background Information Acrobat/ Word Public PMU DDF Background Information Steve Graber Review Version 1.0 at the April 2014 meeting. PDC Association Information Exchange Form PDC Association Information Exchange Form Steve Graber No changes required as a result of January 2014 review. Review at January 2015 meeting.

Association Information Exchange Form

Association Information Exchange Form The attached ICCP Association Information Exchange Form has been created to facilitate ICCP associations between ICCP nodes. All fields are required to create an association.