ICCP IMPLEMENTATION STANDARDS REVISION STATUS ITEMS 1-10 5 7 8 5 6 7 8 ACCEPTED 2/11/98 5/21/98 5/21/98 5/21/98 7/16/99 7/16/99 7/16/99 7/16/99 BY DEWG DEWG DEWG DEWG DEWG DEWG DEWG DEWG 11 9 7/16/99 4/19/00 DEWG DEWG 7-9 12-13 3 and 5-8 10/21/10 10/21/10 7/12/12 DEWG DEWG DEWG July 12, 2012 REVISION COMMENTS Show “STATE” Examples in Comments Section Modify Transfer Interval, Add Assumption Remove Transfer Interval Clarify Integrity Scan, Add Buffer Time Clarify Integrity Scan, Add Buffer Time Remove reference to Information Update Interval Clarify Integrity Scan, Add Buffer Time, Remove reference to Information Update Interval, Clarify Assumption Added Changed ‘Version 1.1, Dated 12/23/97’ to ‘latest version as posted at http://www.nerc.com’ Modified data transfer interval and updated to current Functional Model terminology. Added reference to TASE.2 documents Version 4.0 clarified that DISCRETE should not be used, provided industry standard configuration parameters, and partial data set support, 1 Version 4.0 ICCP IMPLEMENTATION STANDARDS ITEM# 1 Data Values Objects STANDARD VMD (Global) COMMENTS DEWG agreed upon standard for un-restricted access of information pertaining to NERC security requirements. Associations between ISN Nodes and ISN Nodes to Control Areas have not been standardized within the ICCP TASE.2 Services and Protocol Object Models. Establishment of Associations (Single and/or Dual) are at the discretion of the Node Administrator(s). This will ensure that Data Sets are maintained accurately on the Server System during system failures, Client data base maintenance and / or communication failures. 2 ICCP Associations Association types will be negotiated between each ISN node and between an ISN Node and their participating Control Areas. The Association Type will be identified within the “ICCP Association Exchange Form” 3 Data Set(s) The loss of Association(s), for whatever reason, shall cause the Data Transfer Set(s) to be recreated by the CLIENT. 4 ICCPObjectID's 5 Status Point Object Block 2 July 12, 2012 The loss of one data object should not prevent the exchange of remaining data objects in the same data set (supporting partial data sets). NERC Site ID + Valid Legal Characters ('A' through 'Z', 'a' through 'z', '0' through '9', '$' and '_'). Total number of Characters not to exceed 32. The first character of the ICCPObject must start with an “Alpha” character. Type - STATE Quality - YES TimeStamp - NO Report–by-Exception Integrity Scan – Mutually Agreed (not to exceed 30 minutes) Buffer Time – Mutually Agreed (typically 1 seconds) 2 The Valid Characters are defined in "Inter-Control Center Communications Protocol, TASE.2 Services and Protocol Object Models, Version 6.1", section 8.1.2 MMS ObjectName. Upper Case characters are the suggested naming convention. The "Data_State" is represented as 8bits (0-7) of which the first two bits (0-1) have pre-defined definitions and identified in "IEC 870-6802 TASE.2 Object Models, Version 1996-08, Section 8.1. Quality definitions are defined as "Validity", Section 5.1.1 Example: Bits (0-1) 00(0) – Between 01(1) – Tripped, Off, Auto, -10 (2) –Closed, On, Man., -- ASSUMPTION NERC ISN Node participants have signed the "NERC Confidentiality Agreement". DEWG agreed upon standard. Vendors are able to support this option. ICCP Vendors provide a cross mapping option to allow for transposition to legacy system preferred object naming convention. Type - State is used to model up to three (3) states and all ICCP vendors have implemented "Type State". DEWG agreed upon standard. Version 4.0 ICCP IMPLEMENTATION STANDARDS 6 Status Point Object Block 2 Type - DISCRETE 7 Analog Point Object Block 1 Type - REAL Quality - YES TimeStamp - NO Transfer Interval – Mutually agreed (not to exceed 30 seconds). 8 Analog Point Object Block 2 Type – REAL Quality - YES TimeStamp - NO Report-By-Exception Integrity Scan – Mutually Agreed, not to exceed 30 minutes Buffer Time – Mutually Agreed 9 ISN Data Definitions NERC ISN Data Point Definitions, Analog and Status Value Format – latest version as posted at “http://www.nerc.com” 10 ICCP Association Exchange Form A Standard Form for the exchange of configuration information required by the Client and Server Nodes. 11 DataSet Deletion Data sets that are no longer needed shall be deleted as soon as practical. 12 Quality Code Attributes 13 ICCP Specifications IEC Technical Report #60870-6-505, Amendment 1 (Telecontrol equipment and systems) Part 6-505 (Telecontrol protocols compatible with ISO standards and ITU-T recommendations – TASE.2 User Guide). ICCP specifications are defined in the document IEC 870-6-503 (TASE.2 Services and Protocols, version 199608). July 12, 2012 This is not an endorsed practice by the Data Exchange Working Group. 3 Point Type Real is defined as a Single Precision IEEE Floating Point value. Quality definitions "Validity", Section 5.1.1 in IEC 870-6802 TASE.2. Point Type Real is defined as a Single Precision IEEE Floating Point value. Quality definitions "Validity", Section 5.1.1, IEC 870-6-802 TASE.2. The NERC ISN Data Server Site at "http://www.nerc.com" has been established as a central information site for ISN Information. The NERC ISN Data Point Definition Document along with the "NERC ISN Point Definition File Instructions" allows user access. This Form is required to be exchanged by each of the ISN Node Administrator who desire to establish an Association (Connection). ISN Node Administrator(s) wishing to exchange information with their respective Control Area(s) should exchange Forms. Transfer rates must be agreed upon between the Provider and the Requester. This is an option however not suggested for Transfer of Analog information. Vendors required to have implemented DeadBand Logic. Deadband should be at source on SCADA. Resolution of Data would have been agreed upon as a standard. ISN Node Administrators, Reliability Coordinators and Balancing Authorities are familiar with the use of update procedures. Most current version will be posted on the NERC Web Site, "http://www.nerc.com". Version 4.0