Configure Property Rules¶
Property rules define the logical relationships between different model features (attributes and measurement points) through feature expressions, mapping the feature values of a single model or multiple models. Using property rules can reduce the repetitive mapping of measurement point data during secondary integration and simplify data processing in scenarios without a model, thereby improving data management efficiency.
For example, you can define property rules in the following scenarios:
Data mapping across model features. For instance, the “total power generation” measurement point in a “wind farm” model is the sum of the “current power generation” data from all wind turbine devices within the wind farm. You can set this in the property rule as
Wind Farm. Total Power Generation = sum(Wind Turbines. Current Power Generation).Mismatch between raw device data and model feature definitions. For example, the raw data format or units provided by a device may not match the model’s requirements, necessitating transformation and mapping through property rules.
Dynamic calculation of model features based on multiple raw data measurement points. For example, the “range efficiency” measurement point in a car model may need to be calculated using the “maximum range” and “battery capacity” data. You can set this property rule as
Range Efficiency = Max Range / Battery Capacity.
This file explains how to configure property rules for models. Property rules mainly include the following two types:
Default Rules: If only the features of the current model are referenced as parameters in the expression, configure single-model feature expressions in default rules.
Custom Rules: If features of other models need to be referenced as parameters in the expression, a new rule must be created to configure cross-model feature expressions.
Prerequisites¶
You need permission to edit models. If you don’t have the permissions, contact your OU administrator for access. For more information, refer to Model Management Permission Allocation.
Create Rules¶
If elements of other models need to be referenced as parameters in the expression, a new rule must be created to configure cross-model feature expressions.
In the application portal’s Developer Console, go to the Models page.
In the Custom Models or Shared Models tab, select Edit to enter the configuration page for the target model.
Note
When editing model elements of a shared model, you need to click the
Custom Configuration button in the top-left corner to switch to the custom configuration interface before making changes. The effective configuration of a shared model = custom configuration + unchanged parts of the original configuration.
3. Select Create Rules, then configure the basic information in the pop-up window according to the following rules, and click Confirm when done.
Name: The name of the rule.
Mapping Model: Select Click to check models in the popup.
If the current model is not inherited from another model, any model can be selected as the mapping model.
If the current model is inherited from another model, only the inherited parent model can be selected as the mapping model.
Description: A description of the rule.
Configure Rules¶
On the Property Rules page within the model details, select the
Configure button on the right of the target rule.Configure Default Property Rules: Reference only the elements of the current model as parameters in the expression.
Create Property Rules: Reference elements of other models as parameters in the expression.
On the rule configuration page, select the
Configure button on the right of the target model element.In the pop-up window, refer to the following details to select parameters, aggregation methods, and configure expressions, and then click Confirm when done:
Configuration Item |
Configuration Reference |
|---|---|
Parameters |
|
Aggregation Methods |
|