Protocol Implementation Conformance Statement Template

for NI-Industrial Communications for IEC 61850

Based on IEC 61850-8-1

Conformance

1 Notation

For the following Clause, the following definitions apply:

– m: mandatory support. The item shall be implemented.

– c: conditional support. The item shall be implemented if the stated condition exists.

– o: optional support. The implementation may decide to implement the item.

– x: excluded. The implementation shall not implement this item.

– i: out-of-scope. The implementation of the item is not within the scope of this standard.

– F/S: Functional Standard. Should be applied.

– Base: Shall be applied in any application claiming conformance to this standard.

2 PICS

2.1 Profile conformance

Table 1 – PICS for A-Profile support
A-Profile shortcut	Profile Description	Client		Server		Value/comment
		F/S		F/S
A1	Client/server A-Profile	c1	√	c1	√	Refer to IEC 61850-8-1 6.2
A2	GOOSE/GSE management A-Profile	c2	√	c2	√	Refer to IEC 61850-8-1 6.3
A3	GSSE A-Profile	c3		c3		Refer to IEC 61850-8-1 6.4
A4	TimeSync A-Profile	c4		c4		Refer to IEC 61850-8-1 6.5
c1 Shall be ‘m’ if support for any service specified in 61850-8-1 Table 2 are declared within the ACSI basic conformance statement. c2 Shall be ‘m’ if support for any service specified in 61850-8-1 Table 6 are declared within the ACSI basic conformance statement. c3 Shall be ‘m’ if support for any service specified in 61850-8-1 Table 9 are declared within the ACSI basic conformance statement. c4 Support for at least one other A-Profile shall be declared (e.g. in A1-A3) in order to claim conformance to IEC 61850-8-1.

Table 2 – PICS for T-Profile support
T-Profile	Profile Description	Client		Server		Value/Comment
		F/S		F/S
T1	TCP/IP T-Profile	c1	√	c1	√	Refer to 61850-8-1 6.2
T2	OSI T-Profile	c2	OSI	c2	OSI	Refer to 61850-8-1 6.2
T3	GOOSE/GSE T-Profile	c3	√	c3	√	Refer to 61850-8-1 6.3
T4	GSSE T-Profile	c4		c4		Refer to 61850-8-1 6.4
T5	TimeSync T-Profile	o		o		Refer to 61850-8-1 6.5
c1 Shall be ‘m’ if support for A1 is declared. Otherwise, shall be 'i'. c2 Shall be “o” if support for A1 is declared. Otherwise, shall be 'i'. c3 Shall be ‘m’ if support for A2 is declared. Otherwise, shall be 'i'. c4 Shall be ‘m’ if support for A3 is declared. Otherwise, shall be 'i'.

2.2 MMS conformance

The following conformance statements are conditional upon the support of the client/server A-Profile being declared.

Except where present, MMS conformance shall be in accordance with ISO/ISP 14226-2.

2.2.1 Character sets

2.2.1.1 MMS identifier

The MMS Identifier shall be constrained to BasicIdentifier.

The use of ExtendedIdentifier is deprecated.

2.2.1.2 MMSString

The MMS String shall be constrained to use the ISO646String character set. All other character sets are deprecated.

2.2.1.3 ObjectName

The MMS ObjectName shall be constrained to use BasicIdentifier. All other character sets are deprecated.

2.2.2 Environmental services

2.2.2.1 Initiate conformance

Table 3 and Table 4 specify the conformance of the initiate service.

Table 3 – MMS InitiateRequest general parameters
InitiateRequest	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
InitiateRequest
localDetailCalling	m	m	√ 65000	m	m	√ 65000
proposedMaxServOutstandingCalling	m	m	√ 6	m	m	√ 6
proposedMaxServOustandingCalled	m	m	√ 6	m	m	√ 6
initRequestDetail	m	m	√	m	m	√
InitiateRequestDetail
proposedVersionNumber	m	m	√ 1	m	m	√ 1
proposedParameterCBB	m	m	√ See 2.2.2.1.2	m	m	√ See 2.2.2.1.2
servicesSupportedCalling	m	m	√ See 2.2.2.1.1	m	m	√ See 2.2.2.1.1
additionalSupportedCalling	c1	x		c1	x
additionalCbbSupportedCalling	c1	x		c1	x
privilegeClassIdentityCalling	c1	x		c1	x
c1 Conditional upon Parameter CBB CSPI – see Table 6.

Table 4 – MMS InitiateResponse general parameters
InitiateResponse	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
InitiateResponse
localDetailCalled	m	m	√ 65000	m	m	√ 65000
negotiatedMaxServOutstandingCalling	m	m	√ 6	m	m	√ 6
negotiatedMaxServOustandingCalled	m	m	√ 6	m	m	√ 6
initResponseDetail	m	m	√	m	m	√
InitiateResponseDetail
negotiatedVersionNumber	m	m	√ 1	m	m	√ 1
negotiatedParameterCBB	m	m	√ See 2.2.2.1.2	m	m	√ See 2.2.2.1.1
servicesSupportedCalled	m	m	√ See 2.2.2.1.1	m	m	√ See 2.2.2.1.1
additionalSupportedCalled	c1	x		c1	x
additionalCbbSupportedCalled	c1	x		c1	x
privilegeClassIdentityCalled	c1	x		c1	x
c1 Conditional upon Parameter CBB CSPI – see Table 6.

2.2.2.1.1 Services supported

Table 5 defines the service support requirement, and restrictions, for this standard. Relationship to ACSI services can be found in 61850-8-1 Table 1.

Table 5 – MMS service supported conformance table
MMS service supported CBB	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
status	o	o		o	m
getNameList	o	o	√	o	c1	√
identify	o	o	√	m	m	√
rename	o	o		o	o
read	o	o	√	o	c2	√
write	o	o	√	o	c3	√
getVariableAccessAttributes	o	o	√	o	c4	√
defineNamedVariable	o	o		o	o
defineScatteredAccess	o	i		o	i
getScatteredAccessAttributes	o	i		o	i
deleteVariableAccess	o	o		o	o
defineNamedVariableList	o	o	√	o	o
getNamedVariableListAttributes	o	o	√	o	c5	√
deleteNamedVariableList	o	o	√	o	c6
defineNamedType	o	i		o	i
getNamedTypeAttributes	o	i		o	i
deleteNamedType	o	i		o	i
input	o	i		o	i
output	o	i		o	i
takeControl	o	i		o	i
relinquishControl	o	i		o	i
defineSemaphore	o	i		o	i
deleteSemaphore	o	i		o	i
reportPoolSemaphoreStatus	o	i		o	i
reportSemaphoreStatus	o	i		o	i
initiateDownloadSequence	o	i		o	i
downloadSegment	o	i		o	i
terminateDownloadSequence	o	i		o	i
initiateUploadSequence	o	i		o	i
uploadSegment	o	i		o	i
terminateUploadSequence	o	i		o	i
requestDomainDownload	o	i		o	i
requestDomainUpload	o	i		o	i
loadDomainContent	o	i		o	i
storeDomainContent	o	i		o	i
deleteDomain	o	i		o	i
getDomainAttributes	o	o		o	c14
createProgramInvocation	o	i		o	i
deleteProgramInvocation	o	i		o	i
start	o	i		o	i
stop	o	i		o	i
resume	o	i		o	i
reset	o	i		o	i
kill	o	i		o	i
getProgramInvocationAttributes	o	i		o	i
obtainFile	o	c9		o	c9
defineEventCondition	o	i		o	i
deleteEventCondition	o	i		o	i
getEventConditionAttributes	o	i		o	i
reportEventConditionStatus	o	i		o	i
alterEventConditionMonitoring	o	i		o	i
triggerEvent	o	i		o	i
defineEventAction	o	i		o	i
deleteEventAction	o	i		o	i
alterEventEnrollment	o	i		o	i
reportEventEnrollmentStatus	o	i		o	i
getEventEnrollmentAttributes	o	i		o	i
acknowledgeEventNotification	o	i		o	i
getAlarmSummary	o	i		o	i
getAlarmEnrollmentSummary	o	i		o	i
readJournal	o	c13		o	c13
writeJournal	o	o		o	o
initializeJournal	o	o		o	c12
reportJournalStatus	o	i		o	i
createJournal	o	i		o	i
deleteJournal	o	i		o	i
fileOpen	o	c8	√	o	c8	√
fileRead	o	c8	√	o	c8	√
fileClose	o	c8	√	o	c8	√
fileRename	o	i		o	i
fileDelete	o	c9	√	o	c9	√
fileDirectory	o	c11	√	o	c11	√
unsolicitedStatus	o	i		o	i
informationReport	o	c7	√	o	c7	√
eventNotification	o	i		o	i
attachToEventCondition	o	i		o	i
attachToSemaphore	o	i		o	i
conclude	m	m	√	m	m	√
cancel	o	o		o	m
getDataExchangeAttributes	o	c10		o	c10
exchangeData	o	c10		o	c10
defineAccessControlList	o	c10		o	c10
getAccessControlListAttributes	o	c10		o	c10
reportAccessControlledObjects	o	c10		o	c10
deleteAccessControlList	o	c10		o	c10
alterAccessControl	o	c10		o	c10
reconfigureProgramInvocation	o	c10		o	c10
c1 Shall be ‘m’ if logical device or logical node model support is declared in ACSI basic conformance statement. c2 Shall be ‘m’ if logical node model support is declared in ACSI basic conformance statement or if support for the MMS write service is declared. c3 Shall be ‘m’ if ACSI support for SetDataValues service is declared or implied. c4 Shall be ‘m’ if logical node model support is declared in ACSI basic conformance statement. c5 Shall be ‘m’ if data set support is declared in the ACSI basic conformance statement. c6 Shall be ‘m’ if support for defineNamedVariableList is declared. c7 Shall be 'm' if support for ACSI Report or ACSI command termination is declared. c8 Shall be 'm' if support for ACSI GetFile is declared. c9 Shall be 'm' if support for ACSI SetFile is declared. c10 Shall not be present since MMS minor version is declared to be 1. c11 Shall be 'm' if support for ACSI GetFileAttributeValues is declared. c12 Shall be 'm' if support for the ACSI log model is declared. c13 Shall be 'm' if support for the ACSI QueryLogByTime or QueryLogAfter is declared. c14 Shall be 'm' if support for the ACSI logical device model is declared.

2.2.2.1.2 Parameter CBB

The specific settings for the MMS parameter CBB is specified in Table 6.

Table 6 – MMS Parameter CBB
MMS parameter CBB	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
STR1	o	o	√	o	c1	√
STR2	o	o	√	o	o	√
NEST	1	1 or greater	√ 10	1	c2	√ 10
VNAM	o	o	√	o	c1	√
VADR	o	o		o	o
VALT	o	o	√	o	c1	√
bit 5	x	x		x	x
TPY	o	o		o	o
VLIS	o	c1	√	o	c3	√
bit 8	x	x		x	x
bit 9	x	x		x	x
CEI	o	i		o	i
ACO	o	c4		o	c4
SEM	o	c4		o	c4
CSR	o	c4		o	c4
CSNC	o	c4		o	c4
CSPLC	o	c4		o	c4
CSPI	o	c4		o	c4
c1 Shall be ‘m’ if ACSI logical node model support declared. c2 Shall be five(5) or greater if ACSI logical node model support is declared. c3 Shall be ‘m’ if ACSI data set, reporting, GOOSE, or logging model support is declared. c4 Shall not be present. Receiving implementations shall assume not supported.

2.2.2.2 GetNameList conformance

Table 7 defines the conformance of the GetNameList service.

Table 7 – GetNameList conformance statement
GetNameList	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
ObjectClass	m	m	√	m	m	√
ObjectScope	m	m	√	m	m	√
DomainName	o	o	√	m	m	√
ContinueAfter	o	m	√	m	m	√
Response+
List Of Identifier	m	m	√	m	m	√
MoreFollows	m	m	√	m	m	√
Response–
Error Type	m	m	√	m	m	√
NOTE Object class ‘vmd' (formerly VMDSpecific in MMS V1.0) shall not appear. If a request contains this ObjectClass, an MMS Reject shall be issued.

2.2.3 Variable access conformance

2.2.3.1 Supporting productions

2.2.3.1.1 AlternateAccessSelection

Table 8 defines the conformance of the alternate access selection.

Table 8 – AlternateAccessSelection conformance statement
AlternateAccessSelection	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
accessSelection	o	o	√	o	m	√
component	o	o	√	o	m	√
index	o	i	√	o	i	√
indexRange	o	i		o	i	√
allElements	o	i		o	x	√
alternateAccess	o	o	√	o	m	√
selectAccess	o	o	√	o	m	√
component	o	o	√	o	m	√
index	o	i	√	o	i	√
indexRange	o	i		o	i	√
allElements	o	i		o	x	√

2.2.3.1.2 VariableAccessSpecification

Table 9 defines the conformance of the variable access.

Table 9 – VariableAccessSpecification conformance statement
VariableAccessSpecification	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
listOfVariable	o	o	√	o	c1	√
variableSpecification	o	o	√	o	c1	√
alternateAccess	o	o	√	o	c1	√
variableListName	o	o	√	o	c2	√
c1 Shall be ‘m’ if ACSI support for Logical Node Model is declared. c2 Shall be ‘m’ if ACSI support for ACSI DataSets, reporting, or logging is declared.

2.2.3.1.3 VariableSpecification

Table 10 defines the conformance of the variable specification.

Table 10 – VariableSpecification conformance statement
VariableSpecification	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
name	o	o	√	o	m	√
address	o	o		o	i
variableDescription	o	o	√	o	i	√
scatteredAccessDescription	o	x		o	x
invalidated	o	x		o	x

2.2.3.2 Read

Table 11 defines the conformance of the read service.

Table 11 – Read conformance statement
Read	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
specificationWithResult	o	o	√	o	m	√
variableAccessSpecification	m	m	√ See 2.2.3.1.2	m	m	√ See 2.2.3.1.2
Response
variableAccessSpecification	o	o	√	o	m	√
listOfAccessResult	m	m	√	m	m	√

2.2.3.3 Write

Table 12 defines the conformance of the write service.

Table 12 – Write conformance statement
Write	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
variableAccessSpecification	m	m	√ See 2.2.3.1.2	m	m	√ See 2.2.3.1.2
listOfData	m	m	√	m	m	√
Response
failure	m	m	√	m	m	√
success	m	m	√	m	m	√

2.2.3.4 InformationReport

Table 13 defines the conformance of the InformationReport service.

Table 13 – InformationReport conformance statement
InformationReport	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
variableAccessSpecification	m	m	√ See 2.2.3.1.2	m	m	√ See 2.2.3.1.2
listOfAccessResult	m	m	√	m	m	√

2.2.3.5 GetVariableAccessAttributes

Table 14 defines the conformance of the GetVariableAccessAttributes service.

Table 14 – GetVariableAccessAttributes conformance statement
GetVariableAccessAttributes	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
name	o	o	√	m	m	√
address	o	o		m	x
Response
mmsDeletable	m	m	√	m	m	√
address	o	x		o	x
typeSpecification	m	m	√	m	m	√

2.2.3.6 DefineNamedVariableList

Table 15 defines the conformance of the DefineNamedVariableList service.

Table 15 – DefineNamedVariableList conformance statement
DefineNamedVariableList	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
variableListName	m	m	√	m	m
listOfVariable	m	m	√	m	m
variableSpecification	m	m	√	m	m
alternateAccess	o	i		o	m
Response	m	m		m	m

2.2.3.6.1 GetNamedVariableListAttributes

Table 16 defines the conformance of the GetNamedVariableListAttributes service.

Table 16 –GetNamedVariableListAttributes conformance statement
GetNamedVariableListAttributes	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
ObjectName	m	m	√	m	m	√
Response
mmsDeletable	m	m	√	m	m	√
listOfVariable	m	m	√	m	m	√
variableSpecification	m	m	√	m	m	√
alternateAccess	o	m		o	i

2.2.3.7 DeleteNamedVariableList

Table 17 defines the conformance of the DeleteNamedVariableList service.

Table 17 – DeleteNamedVariableList conformance statement
DeleteNamedVariableList	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
Scope	m	m	√	m	m
listOFVariableListName	m	m	√	m	m
domainName	o	m	√	o	m
Response
numberMatched	m	m	√	m	m
numberDeleted	m	m	√	m	m
DeleteNamedVariableList-Error	m	m	√	m	m

2.2.4 Journal management services

2.2.4.1 ReadJournal

Table 124 and Table 125 define the conformance of the ReadJournal service.

Table 18 – ReadJournal conformance statement
ReadJournal	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
invokeID	m	m		m	m
journalName	m	m		m	m
rangeStartSpecification	o	m		o	m
startingTime	o	c1		o	m
EntrytoStartAfter	o	o		o	m
rangeStopSpecification	o	m		o	m
endingTime	o	c2		o	m
numberOfEntries	o	o		o	m
EntryToStartAfter	o	c2		o	m
TimeSpecification	m	m		m	m
EntrySpecification	m	m		m	m
Response						`
invokeID	m	m		m	m
listOfJournalEntry	m	m		m	m
entryIdentifier	o	m		m	m
originatingApplication	m	m		m	m
entryContent	m	m		m	m
moreFollows	m	m		o	m
c1 At least one shall be present. c2 At least one shall be present.

Table 19 – JournalEntry conformance statement
Ref	Parameter	Client-CR			Server-CR
		Base	F/S	Value/range	Base	F/S	Value/range
1	occurrenceTime	m	m		m	m
2	additionalDetail	x	x		x	x
3	entryForm	m	m		m	m
4	data	o	m		o	c1
5	event	o	m		o	o
6	currentState	o	m		o	c2
7	listofVariable	o	m		o	c3
8	variableTag	o	m		o	c4
9	valueSpecification	o	m		o	c4
10	annotation	o	m		o	c1
c1 Either data or annotation shall be present. c2 If event is present, then m. c3 If data is present, then m. c4 If listofVariable present, then m.

2.2.4.2 InitializeJournal

Table 126 defines the conformance of the InitializeJournal service.

Table 20 – InitializeJournal conformance statement
InitializeJournal	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
journalName	m	m		m	m
limitSpecification	m	m		m	m
limitingTime	m	m		m	m
limitingEntry	o	o		o	m
Response+
entriesDeleted	m	m		m	m

2.2.5 File management services

2.2.5.1 FileDirectory

Table 21 defines the conformance of the FileDirectory service.

Table 21 – FileDirectory conformance statement
FileDirectory	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
filespecification	o	o	√	m	m	√
continueAfter	o	o	√	m	m	√
Response+
listOfDirectoryEntry	m	m	√	m	m	√
MoreFollows	m	m	√	m	m	√

2.2.5.2 FileOpen

Table 22 defines the conformance of the FileOpen service.

Table 22 – FileOpen conformance statement
FileOpen	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
filename	m	m	√	m	m	√
initialPosition	o	o	√	m	m	√
Response+
frsmID	m	m	√	m	m	√
fileAttributes	m	m	√	m	m	√

2.2.5.3 FileRead

Table 23 defines the conformance of the file read service.

Table 23 – FileRead conformance statement
FileRead	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
frsmID	m	m	√	m	m	√
Response+
fileData	m	m	√	m	m	√
moreFollows	m	m	√	m	m	√

2.2.5.4 FileClose

Table 24 defines the conformance of the FileClose service.

Table 24 – FileClose conformance statement
FileClose	Client-CR			Server-CR
	Base	F/S	Value/range	Base	F/S	Value/range
Request
frsmID	m	m	√	m	m	√
Response+	m	m	√	m	m	√

3 PICS Statement

This Subclause describes the Protocol Implementation Conformation Statement Proforma (PICS). Every implementor shall complete the entire PICS. Refer to IEC 61850-7-2 ACSI basic conformance statement.

The PICS, in the following Subclauses, shall also be completed.

3.1 Logical device

The following PICs represent the conformance requirements if support for the logical device model is declared within the ACSI basic conformance statement.

3.2 GOOSE Services

Table 25 shall define the conformance of the GOOSE service.

Table 25 – GOOSE conformance statement
	Subscriber	Publisher	Value/comment
GOOSE Services	c1	c1
SendGOOSEMessage	M	m	√
GetGoReference	O	c3	√
GetGOOSEElementNumber	O	c4	√
GetGoCBValues	O	o	√
SetGoCBValues	O	o	√
GSENotSupported	c2	c5
GOOSE Control Block (GoCB)	O	o	√
c1 Shall be ‘m’ if support is declared within ACSI basic conformance statement. c2 Shall be ‘m’ if ACSI basic conformance support for either GetGoReference or GetGOOSEElementNumber is declared. c3 Shall be ‘m’ if support for ACSI basic conformance of GetGoReference is declared. c4 Shall be ‘m’ if support for ACSI basic conformance of GetGOOSEElementNumber. c5 Shall be ‘m’ if no support for ACSI basic conformance of GetGOOSEElementNumber is declared.

3.3 Substation configuration language

Conforming implementations shall support the substation configuration language as defined in IEC 61850-6 for exchange between engineering tools. Implementors that wish to provide online access and management for SCL configuration should refer to informative Annex D for guidance.