8000 RSR-367 : Automated ICD import and then IED renaming and Communication section creation into SCD file - Part 2 of 4 · Issue #66 · com-pas/compas-sct · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
RSR-367 : Automated ICD import and then IED renaming and Communication section creation into SCD file - Part 2 of 4 #66
Closed
@jeanetiennelemaire

Description

@jeanetiennelemaire

As a COMPAS service user, this US purpose is to create a COMPAS service that generate a new SCD file and complete it with Substation section from SSD file, IED section from STD files and Private elements.

 

As service user, I would like to have a service in order to create a new SCD file and complete it with:

  • IED sections with its DataTypeTemplate by copying STD files content and renaming IED name (cf US RSR-367)
  • Communication nodes from STD files (cf US RSR-367)
  • Private elements (cf US RSR-367)

  

Prerequisites: 

  • The following COMPAS services have already been developed:
    • RSR-352  to import a SSD file and a set of STD files from an ExportSite
    • RSR-6      to import DataTypeTemplate from an STD file into an SCD file
    • RSR-60    to import an IED from an STD file into an SCD file
    • RSR-64    to associate a list of Connected Access Point (ConnectedAP) to a SubNetwork
    • RSR-259  to create a Private element
  • US RSR-358 has been developed

 

The inputs of this service are:

  • A SCD file (required) defined by Header.id, Header.version and Header.revision.
    • This SCD file
  • A set of STD files associated with the /substation XML section already imported into SCD file

 

US process description:

 

  •  Step 1)
    • List all Private /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader from SCD file and remove duplicate LNode/Private/compas:ICDHeader with same IED name attribute and same value.
      • Technical purpose: List all private from SCD /Substation /VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader and remove duplicate private with the help of uniqueness of IED name into a given Site
    • From this Private list, for each Private /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @ICDSystemVersionUUID @iedName:
      • Find the unique corresponding STD file among the set of STD files where LNode/Private/compas:ICDHeader @ICDSystemVersionUUID from Private list = SCL/IED/Private/compas:ICDHeader @ICDSystemVersionUUID of one STD file and do:
        • Return an error message and abort the whole processing if the corresponding STD file is not found or if it is not unique 
        • Import DataTypeTemplate section from this STD file into current SCD file by calling the COMPAS service described in US RSR-6
        • Import /IED section from this STD file into /IED section of the current SCD file and then rename the newly imported /IED @name with current /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @iedName by calling the COMPAS service described in US RSR-60
        • Into this newly created /IED section into SCD file:
          • Check that current Private /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader attributes values matches with the current Private /IED/Private/compas:ICDHeader attributes values except for @BayLabel @iedName @IEDinstance attributes which don't exist in the /IED/Private/compas:ICDHeader, else an error message is returned and the whole processing is aborted
          • As there are 3 missing attributes in current Private /IED/Private/compas:ICDHeader, copy them with their values from current Private  /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader@BayLabel and @iedName and @IEDinstance into current Private /IED/Private/compas:ICDHeader by calling service described in US RSR-259
        • Import SCL/Communication/Subnetwork/ConnectedAP section from this STD file:
          • A settings file gives the link between Communication/Subnetwork/ConnectedAP/@apname from a STD and the SCD Communication/Subnetwork/@name and @type which is the Subnetwork where to copy the ConnectedAP section. This settings file is in attachement: Link_ConnectedAP.apName_Subnetwork.type.name.xlsx
          • Copy Communication/Subnetwork/ConnectedAP section from STD file into the right SCD Communication/Subnetwork/@name and @type and rename the SCD Communication/Subnetwork/ConnectedAP/@iedName with current /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @iedName by calling the COMPAS service described in US RSR-64

 

Output:

The SCD file has been completed with these elements:

  • All STD files referenced in Substation LNode Private section are imported into /DataTypeTemplate node, /IED node and /Communication node
  • In SCD file, all Private /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader attributes and their values matches with one and only one Private IED/Private/compas:ICDHeader   

 

Error messages:

  • All error messages from COMPAS services are returned
  • If a SCD file is not provided as input then an error message is returned: "A SCD file is mandatory as input of this service"
  • If at least one Private /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader doesn't have one and only one corresponding STD file then the processing is aborted and an error message is returned: "There is no STD file found or there are several STD files corresponding to HeaderId= '/Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @headerId',    HeaderVersion= '@headerVersion', HeaderRevision= '@headerRevision' and ICDSystemVersionUUID='value'"

 

 

Acceptance criteria:

  • Check that if a SCD file is not provided as input then an error message is returned and the whole processing is aborted
  • Check that all duplicate Private  /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader with same attributes with same values are removed to generate a list of unique Private  /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader
  • Check that if at least one Private  /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @ICDSystemVersionUUID from SSD file doesn't have one and only one corresponding /IED/Private/compas:ICDHeader @ICDSystemVersionUUID from one and only one STD file then an error message is returned and the whole processing is aborted
  • Check that all STD files having their Private /IED/Private/compas:ICDHeader @ICDSystemVersionUUID which matches with at least one Private  /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @ICDSystemVersionUUID from SSD file, have:
    • their DataTypeTemplate section imported into current SCD file by calling the COMPAS service described in US RSR-6
    • their /IED section imported into current SCD file with their /IED @name renamed with current /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @iedNameby by calling the COMPAS service described in US RSR-60
  • Check that for each newly imported /IED section into SCD file that:
    • A verification is done about current Private /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader attributes values which shall match with the current Private /IED/Private/compas:ICDHea 686A der attributes values except for @BayLabel @iedName @IEDinstance attributes which don't exist in the /IED/Private/compas:ICDHeader.
    • If an attribute value doesn't match then an error message is returned and the whole processing is aborted
    • The 3 missing attributes in current Private /IED/Private/compas:ICDHeader, are recovered with their values from current Private  /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader@BayLabel and @iedName and @IEDinstance by calling service described in US RSR-259
  • To import SCL/Communication/Subnetwork/ConnectedAP section from STD file into current SCD file, check that a settings file gives the link between Communication/Subnetwork/ConnectedAP/@apname from a STD and the SCD Communication/Subnetwork/@name and @type which is the Subnetwork where to copy the ConnectedAP section.
  • Check that all STD files having their Private /IED/Private/compas:ICDHeader @ICDSystemVersionUUID which matches with at least one Private  /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @ICDSystemVersionUUID from SSD file, have their Communication/Subnetwork/ConnectedAP section copied into the right SCD Communication/Subnetwork/@name and @type and then check that the SCD Communication/Subnetwork/ConnectedAP/@iedName is renamed with current /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @iedName by calling the COMPAS service described in US RSR-64

OUTPUT

  • Check that the SCD file has been completed with these elements:
    • All STD files referenced in Substation LNode Private section are imported into /DataTypeTemplate node, /IED node and /Communication node
    • In SCD file, all Private /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader attributes and their values matches with one and only one Private IED/Private/compas:ICDHeader   

ERROR MESSAGES

  • Check that all error messages from COMPAS services are returned
  • Check that if a SCD file is not provided as input then an error message is returned: "A SCD file is mandatory as input of this service"
  • Check that if at least one Private /Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader doesn't have one and only one corresponding STD file then the processing is aborted and an error message is returned: "There is no STD file found or there are several STD files corresponding to HeaderId= '/Substation/VoltageLevel/Bay/Function/LNode/Private/compas:ICDHeader @headerId',    HeaderVersion= '@headerVersion', HeaderRevision= '@headerRevision' and ICDSystemVersionUUID='value'"

 

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0