[RSR-621] - COMPAS - Evolution on services which create DataSets and CB about the checking of the ability of an IED to create new DataSet or CB

[DamienPERNET]

Context:

Our COMPAS Services which create DataSets and Control Blocks check the ability of an IED to create a DataSet or new Control Block before allowing the creation of such objects into it.

But in the previous US:

• the XPath to check this ability has to be fixed
• the checking of the ability to create a new DataSet has to be done with the associated CB type

 

Purpose:

The US purpose is to fix these abilities for services described in US RSR-20, RSR-245, RSR-253 and RSR-255

 

Prerequisites:

US RSR-20, RSR-245, RSR-253 and RSR-255 are already developed.

 

Description:

• Fix the XPath of the checking:
  • /SCL/IED@name = IED.name as defined in input/AccessPoint/Services/ instead of /SCL/IED@name = IED.name as defined in input/Services/
• The CB creation is allowed when XXXSettings/@cbName attribute is set to "Conf" OR "Dyn"
• For the DataSet creation, the checking has to be done according to the CB type associated:
  • For that a new input parameter for the CB type has to be added. See Details part to have the right XPath  to verify the property
  • If this parameter is left empty and if for all CB types, the settings allow the creation of DataSet for all CB type then create the DataSet

 

Details:

This ability is provided by checking the following attributes attached to the IED for each type of Control Block and associated DataSet:

• For DataSet:
  • /SCL/IED@name = IED.name as defined in input/AccessPoint@name="XXXXXX"/Services/GSESettings/@datSet = Conf OR Dyn for a DataSet associated to a GOOSE CB
  • /SCL/IED@name = IED.name as defined in input/AccessPoint@name="XXXXXX"/Services/SMVSettings/@datSet = Conf OR Dyn for a DataSet associated to a SMV CB
  • /SCL/IED@name = IED.name as defined in input/AccessPoint@name="XXXXXX"/Services/ReportSettings/@datSet = Conf OR Dyn for a DataSet associated to a Report CB
  • /SCL/IED@name = IED.name as defined in input/AccessPoint@name="XXXXXX"/Services/LogSettings/@datSet = Conf OR Dyn or a DataSet associated to a Log CB
• For Control Blocks:
  • /SCL/IED/AccessPoint@name="XXXXXX"/Services/GSESettings/@cbName has to be equal to 'Conf' or 'Dyn' for a GOOSE CB
  • /SCL/IED/AccessPoint@name="XXXXXX"/Services/SMVSettings/@cbName has to be equal to 'Conf' or 'Dyn' for a SMV CB
  • /SCL/IED/AccessPoint@name="XXXXXX"/Services/ReportSettings/@cbName has to be equal to 'Conf' or 'Dyn' for a Report CB
• To find the right AccessPoint use the property that couple (IED.name, LDevice.inst) is unique within the whole SCD.
• If a setting parameter is missing then it means that the creation action not allowed

 

Output:

• The same as current COMPAS services

 

Error messages:

• For US RSR-20 service, the error message "The capability of IED is not allowing DataSet creation" becomes "The capability of IED ied_name is not allowing DataSet creation for the CB_type_associated CB type"
• For US RSR-245, RSR-253 and RSR-255, the error messages "The IED capabilities don't support ControlBlock name modification or creation" become "The IED ied_name capabilities don't support ControlBlock_type CB modification or creation"

 

Acceptance criteria:

• Check that the XPath of the checking is now /SCL/IED@name = IED.name as defined in input/AccessPoint@name/Services/ instead of /SCL/IED@name = IED.name as defined in input/Services/
• Check that the CB creation is allowed when XXXSettings attribute is set to "Conf" OR "Dyn".
• For the DataSet creation, check that the checking is done according to the CB type associated too
• For the DataSet creation, check that if the settings of the IED allow the creation of DataSet for all CB types then create the DataSet even when the CB type is not known and not given as input parameter
• If a setting parameter is missing check that it means that the creation action is not allowed