TASE.

2 Product Implementation
Conformance Statement (PICS)
The following tables provide a standardized method of conformance and implementation options to the
TASE.2 specification as defined in IEC 870-6-503 TASE.2 Services and Protocol and IEC 870-6-802
TASE.2 Object Models. All products claiming conformance to these standards shall supply a form of this
statement. All codes used within the tables are defined in the attached appendix.

Product Identification
Vendor Name Tamarack Consulting, Inc.
Product Name ICCP
Model
Revision 6.15
Other Identification
Client Supported No
Server Supported Yes

TASE.2 CBBs
PICS Conformance Base C/S
Proforma Building
Reference Block Client-CS Server-CS
I. /1 Basic Services m Yes Yes
I. /2 Extended Conditions o Yes Yes
I. /3 Blocked Transfers o
I. /4 Information Message o
I. /5 SBO Device Control o Yes Yes
I. /6 Programs o
I. /7 Events o
I. /8 Accounts o
I. /9 Time Series o

Association Management
PICS Association Management Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 Supported Features m1 Yes Yes
I. /2 QOS o
I. /3 Associate Operation m1 Yes Yes
I. /4 Conclude Operation m1 Yes Yes
I. /5 Abort Operation m1 Yes Yes

Tamarack Consulting, Inc. Page 1 Last revised 1 February, 2001

Data Value
PICS Data Values Base C/S
Proforma
Reference Client-CS Server-CS
1
I. /1 Data Value Model m Yes Yes
I. /2 VCC-specific scope** m1,o Yes Yes
I. /3 ICC-specific scope** m1,o Yes Yes
I. /4 Get Data Value Operation o, m1 Yes Yes
I. /5 Set Data Value Operation o, m1 Yes Yes
1
I. /6 Get Data Value Names Operation o, m Yes Yes
I. /7 Get Data Value Type Operation o, m1 Yes Yes
**Note: Either VCC-specific or ICC-specific scope must be supported by servers for block 1.

Data Sets
PICS Data Sets Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 Data Set Model m1 Yes Yes
I. /2 VCC-specific scope** m1,o Yes Yes
I. /3 ICC-specific scope** m1,o Yes Yes
I. /4 Create Data Set Operation o Yes Yes
I. /5 Delete Data Set Operation o Yes Yes
I. /6 Get Data Set Element Values Operation o, m1 Yes Yes
I. /7 Set Data Set Element Values Operation o, m1 Yes Yes
I. /8 Get Data Set Names Operation o, m1 Yes Yes
I. /9 Get Data Set Element Names Operation o, m1 Yes Yes
**Note: Either VCC-specific or ICC-specific scope must be supported by servers for block 1.

Accounts
PICS Accounts Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 Account Model m8
I. /2 Query Operation m8

Tamarack Consulting, Inc. Page 2 Last revised 1 February, 2001

DS Transfer Sets
PICS DS Transfer Sets Base C/S
Proforma
Reference Client-CS Server-CS
1
I. /1 Data Set Transfer Set Model m Yes Yes
I. /2 Start Transfer Operation m1 Yes Yes
I. /3 Stop Transfer Operation m1 Yes Yes
I. /4 Get Next DSTransfer Set Operation m1 Yes Yes
I. /5 IntervalTimeOut o, m1 Yes Yes
2
I. /6 ObjectChange o, m Yes Yes
I. /7 OperatorRequest** o, m1 Yes
I. /8 IntegrityTimeout o, m2 Yes Yes
I. /9 OtherExternalEvent** o, m1 Yes
I. /10 EventCodeRequested** o, m1 Yes Yes
I. /11 Start Time m1 Yes Yes
I. /12 Interval m1 Yes Yes
I. /13 TLE o, m2
I. /14 Buffer Time o, m2 Yes Yes
2
I. /15 Integrity Check o, m Yes Yes
I. /16 DSConditions Requested o, m1 Yes Yes
I. /17 Block Data o, m3
I. /18 Critical o, m2
I. /19 RBE o, m2 Yes Yes
**NOTE: Servers must support the processing of these parameters. This does not imply the presence of
the application.

Time Series Transfer Set Objects

PICS Time Series Transfer Set Objects Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 Time Series Transfer Set Model m9
I. /2 Get Next TSTransfer Set Operation m9
I. /3 EndTimeArrived o,m9
I. /4 ReportIntervalTimeOut o,m9
I. /5 OperatorRequest o,m9

Transfer Account Transfer Set Objects

PICS Transfer Account Transfer Set Objects Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 Transfer Account Transfer Set Model m8
I. /2 BeforeTheHour o,m8
I. /3 DispatchUpdate o,m8
I. /4 DuringTheHour o,m8
I. /5 AfterTheHour o,m8
I. /6 ActualDataUpdate o,m8
I. /7 PastHours o,m8
I. /8 ObjectChange o,m8
I. /9 OperatorRequest o,m8

Information Message Objects

Tamarack Consulting, Inc. Page 3 Last revised 1 February, 2001

PICS Information Message Objects Base C/S
Proforma
Reference Client-CS Server-CS
4
I. /1 Information Message Transfer Set Model m

Special Transfer Set Objects

PICS Special Transfer Set Objects Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 Transfer Set Name o,m1 Yes Yes
I. /2 Next DSTransfer Set o Yes Yes
I. /3 Next TSTransfer Set o Yes
I. /4 Event Code o,m1 Yes
I. /5 DSConditionsDetected o,m1 Yes Yes
I. /6 TSConditionsDetected o,m1
I. /7 TAConditionsDetected o,m1
I. /8 Transfer Set Time Stamp o,m1 Yes Yes

SBO Devices
PICS Devices Base C/S
Proforma
Reference Client-CS Server-CS
5
I. /1 Device Model m Yes Yes
I. /2 Select Operation m5 Yes Yes
I. /3 Operate Operation m5 Yes Yes
I. /4 Get Tag o Yes
I. /5 Set Tag o Yes
I. /6 Timeout Action o,m7
I. /7 Local Reset Action o
I. /8 Success Action o,m7
I. /9 Failure Action o,m7

Programs
PICS Programs Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 Program Model m6
I. /2 Start Operation m6
I. /3 Stop Operation m6
I. /4 Resume Operation m6
I. /5 Reset Operation m6
I. /6 Reset Operation m6
I. /7 Kill Operation m6
I. /8 Get Program Attributes Operation o,m6

Tamarack Consulting, Inc. Page 4 Last revised 1 February, 2001

Event Enrollments
PICS Event Enrollments Base C/S
Proforma
Reference Client-CS Server-CS
7
I. /1 Event Enrollment Model m
I. /2 Create Event Enrollment Operation m7
I. /3 Delete Event Enrollment Operation o,m7
I. /5 Get Event Enrollment Attrib. Operation o,m7

Event Conditions
PICS Event Conditions Base C/S
Proforma
Reference Client-CS Server-CS
7
I. /1 Event Condition Model m
I. /2 Event Notification Action m7

Tamarack Consulting, Inc. Page 5 Last revised 1 February, 2001

 Object Model Conformance
The following tables define the specific object models implemented.

Supervisory Control and Data Acquisition

PICS Supervisory Control and Base C/S
Proforma Data Acquisition
Reference Client-CS Server-CS
1
I. /1 IndicationPoint Object m Yes Yes
I. /2 ControlPoint Object m5 Yes Yes
I. /3 ProtectionEquipmentEvent Object o Yes Yes

Transfer Accounts
PICS Transfer Accounts Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 TransferAccount Object m8
I. /2 TransmissionSegment Object m8
I. /3 ProfileValue Object m8
I. /4 AccountRequest Object o

Device Outage
PICS Device Outage Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 Device Outage Object o

Information Message
PICS Information Message Base C/S
Proforma
Reference Client-CS Server-CS
4
I. /1 Information Message Object m

Power Plant
PICS Power Plant Base C/S
Proforma
Reference Client-CS Server-CS
I. /1 AvailabilityReport Object o
I. /2 RealTimeStatus Object o
I. /3 ForecastSchedule Object o
I. /4 Curve Object o
I. /5 Power System Dynamic Objects o

Tamarack Consulting, Inc. Page 6 Last revised 1 February, 2001

 Appendix - Code Definitions
Base column
The "Base" column reflects the definitions and specifications in the appropriate base standard. Each entry
in this column is chosen from the following list:

mandatory; m: This feature shall be supported, i.e. its syntax and procedures shall be
implemented as specified in the base standard. However, it is not a requirement that the
feature shall be used in all instances of communication, unless mandated by the base
standard. The entry mn denotes that the item is mandatory for conformance to block n.

optional; o: Any feature denoted by "o" is left to the implementation as to whether that feature is
implemented or not. If a parameter is optionally supported, then the syntax shall be
implemented, but it is left to each implementation whether the procedures are implemented or
not.

Where the base entry contains two classifications separated by a comma, these reference the client and
server capabilities, respectively.

C/S column
The "C/S" column reflects the conformance statement of the product. Where appropriate, the colunm is
further divided into Client-CS: Client Conformance Statement, and Server-CS: Server Conformance
Statement. Each entry in this column is chosen from the following terminology:

supported; Yes: Any feature denoted by "Yes" is supported, i.e. its syntax and procedures are
implemented as specified in the base standard or in the profile. It is not a requirement that the
feature shall be used in all instances of communication, unless mandated by the base standard
or stated otherwise in this profile.

unsupported; (blank): Any feature denoted by a blank is not claimed to be supported. Proper
procedures must be implemented to signal appropriate error responses in the event that an
attempt is made to inadvertantly make use of the feature.

Tamarack Consulting, Inc. Page 7 Last revised 1 February, 2001