1285   ICD file must have a communication section for 8-1 implementation

Created: 16 Jul 2014

Status: In Force (green)

Part: Part 8-1 (2011; Edition 2)

Links: #1284 SCSM mapping may require a communication section in an ICD file

Page: 133

Clause: 25


Category: Issue for edition 2 of this part


The OSI address parameters are IED specific and must be provided by the IED tool with the ICD/IID file; the system tool shall import them as is and not modify them.
The list of OSI address parameters is defined in Table 132. Several of those are mandatory (OSI-TSEL, OSI-SSEL, OSI-PSEL).

As a result, the ICD file for a server according to Part 8-1 must have a communication section (it is not optional as in the general case - see the definition of ICD in Part 6).

Note: pure clients do not require a communication section.

(This TISSUE is a result of a discussion held at the WG10 meeting in Québec City. See also TISSUE 1284 for the same issue on Part 6.)


It shall be mentioned that an ICD file for a server according to 8-1 shall contain a communication section with the IED required OSI address parameters.

Discussion Created Status
09 Dec 14 In Force (green)
The OSI P-TYPES will be made conditional based upon the declaration of the server's support for the MMS Initiate Service. If the server declares support for the service, the OSI P-TYPES of the Selectors shall be mandatory in the ICD/IID file. 01 Aug 14 Ballot Period
it makes sense for a server that implements the TPAA model, and therefore implements MMS.
GOOSE only device with or without additional GSE management may not have a communication section at all in their ICD file.

23 Jul 14 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.