Configuring Topology Rules


Topology rules are the rules that need to be followed when building hierarchical relationships between assets, which determine the type of topology tree, the scope of mountable objects, and more. By assigning topology rules to onboarding templates, quick reuse can be achieved across different OUs.

A topology tree needs to be created based on a topology rule, and multiple topology trees can be created under one topology rule.

Procedure

Step 1: Creating a Topology Rule


  1. Select Global Business Rules > Topology Rules in the left navigation pane.
  2. Select New Rule.
  3. Enter the basic information of the topology rule in the pop-up window:
    • Rule Name: The name of the topology rule, which will be used as the display name of the topology rule in Onboarding Tool.
    • Identifier: The unique identifier of the topology rule.
    • Independent Tree: The type of topology tree that can be created under the current topology rule. For more information about independent trees, see Topology.
    • Description: The description of the topology rule.
    • Prompt User to Maintain Topology Relationship: If selected, at least one topology tree must be created under this topology rule.
  4. Select Save.

Step 2: Configuring Constraint Objects


  1. After creating the topology rule, select its corresponding Configuration config from the list.
  2. On the configuration page, enter the following information:
    • Top-level Node Object: Defines the business object category and type that the top-level node of the topology tree can mount. Only one asset that meets the constraint conditions can be mounted on the top-level node.
    • Topology Constraint Object: Defines the constraints on topology node objects. Only assets that meet one of the conditions can be mounted on the topology tree node under the current topology rule.
      • Parent-Child Objects: Enforce constraints on the asset types in the hierarchy of the topology tree. For example, if you choose the Parent Node Object as the PV type of the power site and the Child Node Object as the weather station type of the device, it means that the weather station device must be mounted under the PV power site node. If there is no weather station device under the PV power site node, other types of assets cannot be mounted in the topology structure.
      • Other Objects: Defines other objects that can be mounted in the topology tree. If it overlaps with the items constrained by the Parent-Child Objects, the Parent-Child Objects constraints will be given priority.

Results


After configuring the topology rule, the following operations can be performed:

  • Assign to Onboarding Template: The topology rule needs to be assigned to an onboarding template to take effect in the corresponding OU. For more information, see Managing Onboarding Templates.
  • Edit Topology Rule: Select the corresponding Configure config of the topology rule to enter the configuration page.
    • Edit Basic Information: Select Edit edit button corresponding to the Basic Information, edit in the pop-up window, and select Save.
    • Edit Top-level Node Object: In Top-level Node Object, you can reselect the business object category and type.
    • Edit Topology Constraint Object: In Topology Constraint Object, select Create Parent-Child Objects under the Parent-Child Objects tab, or Create Other Objects under the Other Objects tab. Select Delete delete of the corresponding object to delete it.
  • Delete Topology Rule: Select Delete delete corresponding to the topology rule to delete it.


After the topology rule is assigned to the onboarding template, editing or deleting the rule in Global Business Rules > Topology Rules will directly take effect in the OU without updating the onboarding template.