ICCP IMPLEMENTATION STANDARDS
REVISION STATUS
ITEMS / ACCEPTED / BY / REVISION COMMENTS1-10 / 2/11/98 / DEWG
5 / 5/21/98 / DEWG / Show “STATE” Examples in Comments Section
7 / 5/21/98 / DEWG / Modify Transfer Interval, Add Assumption
8 / 5/21/98 / DEWG / Remove Transfer Interval
5 / 7/16/99 / DEWG / Clarify Integrity Scan, Add Buffer Time
6 / 7/16/99 / DEWG / Clarify Integrity Scan, Add Buffer Time
7 / 7/16/99 / DEWG / Remove reference to Information Update Interval
8 / 7/16/99 / DEWG / Clarify Integrity Scan, Add Buffer Time, Remove reference to Information Update Interval, Clarify Assumption
11 / 7/16/99 / DEWG / Added
9 / 4/19/00 / DEWG / Changed ‘Version 1.1, Dated 12/23/97’ to ‘latest version as posted at
ITEM# / STANDARD / COMMENTS / ASSUMPTION
1 / Data Values Objects / VMD (Global) / DEWG agreed upon standard for un-restricted access of information pertaining to NERC security requirements. / NERC ISN Node participants have signed the "NERC Confidentiality Agreement". DEWG agreed upon standard.
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” / 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).
3 / Data Set(s) / The loss of Association(s), for whatever reason, shall cause the Data Transfer Set(s) to be re-created by the CLIENT. / This will ensure that Data Sets are maintained accurately on the Server System during system failures, Client data base maintenance and / or communication failures. / Vendors are able to support this option.
4 / ICCPObjectID's / 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. / 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. / ICCP Vendors provide a cross mapping option to allow for transposition to legacy system preferred object naming convention.
5 / Status Point Object Block 2 / Type - STATE Quality - YES
TimeStamp - NO
Report–by-Exception
Integrity Scan – Mutually Agreed (not to exceed 30 minutes)
Buffer Time – Mutually Agreed
(typically 5 seconds) / 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-6-802 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., -- / Type - State will be used to model up to three (3) states and all ICCP vendors have implemented "Type - State". DEWG agreed upon standard.
1
04/19/00Version 2.0
{iccp_implement_standards.doc}
ICCP IMPLEMENTATION STANDARDS
6 / Status Point Object Block 2 / Type - DISCRETE Quality - YESTimeStamp - NO
Report-By-Exception Integrity Scan – Mutually Agreed (not
to exceed 30 minutes)
Buffer Time – Mutually Agreed (typically 5 seconds) / Type - DISCRETE will be used to Model status points with more than three (3) states. The integer value, 32bits, would need to be interpreted uniformly for accurate interpretation. This is not an option for 2 state devices. / The implementation has been coordinated between the Data Provider and the Data Requester. To recognize Type - DISCRETE expanded definition as being an accepted Standard they need to be approved through the appropriate Standards Committee.
7 / Analog Point Object Block 1 / Type - REAL
Quality - YES
TimeStamp - NO
Transfer Interval – 30sec. / Point Type Real is defined as a Single Precision IEEE Floating Point value.
Quality definitions "Validity", 5.1.1 / 30sec. Transfer interval is considered to be a Node to Node transfer rate and not a Provider node to Requester node transfer rate.
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 / Point Type Real is defined as a Single Precision IEEE Floating Point value.
Quality definitions "Validity", 5.1.1. / This is an option however not suggested for Transfer of Analog information. Vendors required to have implemented Dead-Band Logic. Deadband should be at source on SCADA. Resolution of Data would have been agreed upon as a standard.
9 / ISN Data Definitions / NERC ISN Data Point Definitions, Analog and Status Value Format – latest version as posted at “ / The NERC ISN Data Server Site at " 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. / ISN Node Administrators, Security Coordinators and Control Areas are familiar with the use of update procedures.
10 / ICCP Association Exchange Form / A Standard Form for the exchange of configuration information required by the Client and Server Nodes. / 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. / Most current version will be posted on the NERC Web Site, "
11 / DataSet Deletion / Data sets that are no longer needed shall be deleted as soon as practical.
1
04/19/00Version 2.0
{iccp_implement_standards.doc}