815   CID derived from SCD File

Created: 16 Jan 2012

Status: In Force (green)

Part: Part 6 (2009-12; Edition 2)

Links:

Page: 26

Clause: 7 SCL description file types

Paragraph: 4th (2nd buttet at page)

Category: No impact on this part

Issue

The standard IEC 61850-6 Ed2 defines: A CID File (Configured IED Description) is a SCD file, possibly stripped down to what the concerned IED shall know (restricted view of source IEDs).

Part 6 defines also in 8.3.6: "The private data is owned by a tool respective by a tool category (for example, a picture generator).
The owner is allowed to modify its contents, and normally is the only one able to interpret the data. All other tools, which read private data, have to preserve (store) its contents on SCL import, and
regenerate it at the same place if an SCL file containing this part is produced/exported."

Assume a SCD File that contains an IED Sections for a server or publisher. The data model may have a binding of the model to the internal application program specified by Private elements ... maybe for each leaf of the model.

Now we want configure a client or subscriber that communicates with the above IED, i.e., we want to get a CID file for the client or subscriber. The client is not interested in the binding of the model to the server application (specified in the SCD file). For the client we need to re-specify the binding of the model - now bind the model to the application of the client or subscriber! So, for the CID file (which is a "stripped down" SCD file) we need to "overwrite" the Private Elements.

Proposal

The minimum revision of the paragraph on page 26 should be as follows:

1. Add some text to the following sentence:

It is an SCD file, possibly stripped down to what the concerned IED shall know (restricted view of source IEDs).

Extended text:
It is an SCD file, possibly stripped down to what the concerned IED shall know (restricted view of source IEDs and with a specific binding of model to application for the IED to be configured).

2. Add some normative text at the end of the paragraph after the following text:

The file extension for the SCL part (if any) shall be .CID for Configured IED Description.

Text to be added: The optional binding of the model to the application (in the CID file for the IED to be configured) may overwrite the binding defined in the SCD file.

Example: A XCBR.Pos.stVal may be bound in the SCD file for the bay controller to a Private Element with the value x/y/z. The position may be bound in the CID file for an HMI in a Private Element with the value 198-12-IN.

Discussion Created Status
20 Mar 12 In Force (green)
Rejected.
In my opinion the part 'stripped down to what an IED shall know' is sufficient to allow removal also of Private parts from other applications, i.e. it overrides 8.3.6 in that sense, that here the application is 'configuring an IED', everything not needed for this purpose can be removed, and private stuff needed for this purpose can be added. Further the only purpose of a CID is to configure an IED. Usage for other purpose, e.g. feed back to other applications, is outside the standard.
16 Jan 12 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 21.10.16.1