Unit 3: Configuring OU Templates


OU templates integrate the business objects (such as site types, custom types, device types, component types, manufacturers, model Nos., and dimensions) and business rules required for OU. Using OU templates, the required data and rules can be safely and quickly accessed for asset onboarding.

Before You Start


The application creator need to ensure the following:

  • The account has been assigned the required permissions. If not, contact the application administrator.

  • Based on the required assets, determine the required business objects and business rules, including site/device/component/custom type assets, manufacturers, model Nos., topology rules, modelling rules.

Task 1: Creating Business Objects


Performed By

Performed In

System Administrator

EnOS Application Portal


Business objects is used to classify assets. Business objects are associated with models and connected to devices, playing a crucial role in the entire application building process.

The business objects in Configuration Center can be shared by multiple OUs in the same environment. This task will teach you to configure business objects in Configuration Center, and the configured business objects can be assigned to specific OUs through the OU template.

Procedure


Follow the steps below to create and configure the required business objects, including dimensions, site types, device types, custom types, component types, manufacturers and model Nos..

Configuring Dimensions


Dimensions are the business semantic dimensions of data defined by Configuration Center. By customizing various dimensions, different business semantics can be assigned to asset data. For example, by function, device types can be divided into different device systems, and by usage domain, templates can be further classified into different categories. This step describes how to configure the DeviceCategory and TemplateCategory dimensions. If other dimensions are required for the target application, contact the system administrator.

  • DeviceCategory: the device systems that can be selected when creating device types in Global Business Objects > Device Types.

  • TemplateCategory: the template categories that can be selected when creating templates in Templates.


  1. Log in to EnOS Application Portal and select Configuration Center in the application list. In the left navigation bar, select Global Business Objects > Dimensions.

  2. In the dimension library, search for the DeviceCategory and TemplateCategory dimensions and select to view whether the required records exist:

    • If they exist, use the corresponding device system and template category when configuring device types and creating templates.

    • If they do not exist, follow the steps below to create a new record in the corresponding dimension.

  3. Hover over the ellipsis icon (…) in the upper-right corner of the dimension and select Configure Records.

  4. On the dimension record page, select New Record. In the pop-up window, enter the Name and Identifier of the record.


After successfully creating the records, select Global Business Objects > Device Types in the left navigation bar, select Create Device Type, and you can see the created dimension record in the Device System dropdown list.

Select Templates in the left navigation bar, select Create Template, and you can see the created dimension record in the Category dropdown list.

Configuring Device/Component/Custom Types


  1. Select Global Business Objects > Device/Component/Custom Types in the left navigation bar.

  2. Select New Device/Component/Custom Type, fill in the information as required in the pop-up window, and select Confirm.

  3. After creation, select the corresponding Associate Asset Model btn_model in the list of device/component/custom types.

  4. In the pop-up window, select the corresponding model and select OK. The models available for selection here are all public models. If you need to complete Task 5: Associate Private Models, make sure to associate the required public models that the required private models are created from with the device/component/custom types.

  5. Follow the steps below to add an icon for the device/component/custom type. The devices/components/custom assets of this type will have the same icon for differentiation with other types when displayed in applications.

    1. Select the hyphen icon (-) in the Icon column of the corresponding device/component/custom type.

    2. In the pop-up window, select Add Image, choose the icon, select the icon style from the dropdown box on the right, and select OK.

Configuring Site Types


  1. Select Global Business Objects > Site Types from the left navigation bar. Follow the steps for creating device/component/custom types to create site types, associate models, and add icons.

  2. Follow these steps to assign device types to site types:

    1. Select the plus icon btn_expand next to the site type name.

    2. On the expanded page, select the plus icon next to Device Types.

    3. In the pop-up window, select the corresponding Device System and Device Types, and then select OK.

After assigning device types, devices and components of that type can be added under the corresponding site.

Configuring Manufacturers and Model Nos.


  1. Select Global Business Objects > Manufacturers from the left navigation bar.

  2. Select New Manufacturer, and then fill in the manufacturer information as needed in the pop-up window. Select OK.

  3. Select View Details btn_details for the manufacturer in the list.

  4. On the model No. page, select New Model No.. Fill in the model No. information as needed in the pop-up window, and then select OK.

  5. Select Associate Asset Model btn_model for the model in the list.

  6. In the pop-up window, select the corresponding model, and then select OK. If the public model associated with the model No. is the same as the one associated with the device/component type, the model No. can be used as an onboarding model No. for that type of device/component.

Results


After all business objects are created and associated with the corresponding models, they can be used for asset onboarding, and the characteristics defined in the public models, including attributes, measurement points, events, and services, will be assigned to the assets.

Task 2: Configuring Topology Rules


Performed By

Performed In

System Administrator

EnOS Application Portal


Topology rules define the rules for the topology structure between assets, control the types of topologies that can be created, the business objects that can be mounted, and the hierarchical relationships between business objects.

Procedure


  1. Log in to EnOS Application Portal and select Configuration Center in the application list.

  2. Refer to Configuring Topology Rules to create and configure topology rules as needed.

Results


After the topology rules are configured, you can use them to build the topologies according to the rules during asset onboarding.

Task 3: Creating a Template


Performed By

Performed In

System Administrator

EnOS Application Portal


Templates integrate business objects and business rules used by the application to form a standardized solution for asset onboarding. Note the following:

  • Only one template can be bound to an OU.

  • Multiple site types can be added to a template, and a template can be used to onboard assets in multiple sites.

Procedure


  1. Log in to EnOS Application Portal and select Configuration Center from the application list.

  2. Refer to Configuring OU Templates to create and configure an OU template.

Results


After the template is created, the system administrator can click on the template in the template list to see that the previously created business objects and topology rules have been successfully assigned to the template.

Task 4: Binding the Template


Performed By

Performed In

System Administrator

EnOS Application Portal


EnOS supports fast OU initialization by binding templates. OU must be successfully initialized in Configuration Center before using the Onboarding Tool to onboard assets.

Procedure


  1. Log in to EnOS Application Portal and select Configuration Center from the application list.

  2. Refer to Binding OU Templates to bind the template to the OU.

Results


After the binding is completed, the system will prompt “Initialization Successful”. Wait for about 10 minutes for the template to take effect. Please do not perform any operations during this period.

(Optional) Task 5: Associating Private Models


Performed By

Performed In

System Administrator

EnOS Application Portal


If the assets need to be onboarded through private models, the system administrator needs to configure corresponding modelling rules, assign modelling rules to the OU template, and associate business objects with private models at the OU level after the template update takes effect, so that the corresponding private models can be used when onboarding assets of this type.

Procedure


  1. To associate a private model with a device/component type, ensure that the public model associated with the device/component type in the Configure Device/Component/Custom Types step is consistent with the public model associated with the required manufacturer and model No. in the Configuring Manufacturers and Model Nos. step.

  2. Refer to Configuring Modelling Rules to create modelling rules for the required site/device/component/custom type.

  3. Refer to Editing OU Templates to add the modelling rules to the OU template created in Task 3: Creating a Template.

  4. After the template update takes effect at the OU level, refer to Associating Models for Business Objects to associate the private models with business objects at the OU level.

Results


  • For site types and custom types: the associated private models will be used as the onboarding model for the assets of the corresponding site/custom type of the current OU. At the same time, the attributes of the private model will determine the selectable attributes and measurement points displayed on the visualization page for the asset. For more information, refer to Configuring Display Fields.

  • For device types and component types: the associated private models will determine the selectable attributes and measurement points displayed on the visualization page for the asset. For more information, refer to Configuring Display Fields.

  • For manufacturers and model Nos.: the private model associated with the model No. created from the public model associated with the device/component type at the global level will be used as the onboarding model for the assets under the corresponding device/component type of the current OU.