• Documentation
• Managing Global Asset Elements

Managing Global Asset Elements

The global asset element list displays both OLAP and non-OLAP sources that are commonly used in the current environment. When synchronizing OLAP metrics from EnOS Metric Management at the global level, it may be necessary to manually create new elements or merge existing ones. Non-OLAP source metrics can also be created at the global level and will be displayed in the global asset element list.

It is recommended to create global asset elements for metrics that are widely used across domains. If a metric is only used in a specific OU, you can Configuring OU Asset Elements.

Creating OLAP Source Elements

Prerequisites

• Business objects such as station type, device type, component type, and custom type have been created at the global level and associated with models. For more information, see Configuring Global Business Objects.
• Dimensions have been created in Metric Management, and the Additional Attributes of the dimensions contain tags for the required business objects. The Key is fixed as amcType, and the Value is the Identifier of the configured business object in Configuration Center. For more information, see Managing a Dimension Definition.
• Atomic and derived metrics have been created and published in Metric Management and are associated with the above dimensions. For more information, see Managing Metrics.

When Configuration Center synchronizes OLAP metrics, manual processing may be needed under the following situations:

- The atomic metric has not been associated with an existing element in the asset element library. In this case, you need to create a new element in Configuration Center and associate it with the atomic metric. If a derived metric and compound metric exist under the atomic metric, mapping will be created under this asset element synchronously.

- Other derived metrics or compound metrics are created under this atomic metric after there are already elements created based on this atomic metric in Configuration Center. In this case, you need to merge the derived metrics and compound metrics to the existing element.

Viewing Pending OLAP Metrics

Follow the steps below to view OLAP source metrics.

1. Select Global Asset Elements from the left navigation pane.
2. Select the Sync button at the top of the page to go to the pending metric page.
   • Pending Metric Elements: Displays atomic metrics that are not associated with asset elements already in the asset element library. The derived metrics are displayed as metric mappings and can be expanded by selecting . New elements can be created based on these metrics in Configuration Center.
   • Pending Metric Mappings: Displays all OLAP source derived metrics that can be merged with existing elements in Configuration Center metric library.

Creating Elements Based on OLAP Metrics

When an atomic metric is not yet associated with an existing element in the asset element library, it appears on the Pending Metric Elements tab. Follow the steps below to create a new element and associate it with the atomic metric.

1. On the Pending Metric Elements tab, create an element using one of the following methods:
   • Select Create Element for the corresponding metric.
   • Check the metrics that need to be created as elements in Configuration Center, then select Batch Create Elements.
2. The newly created element will be displayed in the asset element list with the same name as the atomic metric. Select Map to view the synchronized metric mappings.

Merging OLAP Metrics to Elements

When new derived metrics are created under the atomic metrics associated with the elements, these secondary metrics will appear on the Pending Metrics Mapping tab. Follow the steps below to merge the secondary metrics to the corresponding asset elements mapping.

1. On the Pending Metrics Mapping tab, display the name of the atomic metric corresponding to the metric and the name of the element to be associated. Check the metrics that need to be merged and associated, and select Batch Link to Element.
2. After association, the metric will be synchronized to the metric mapping of the corresponding asset element, and can be viewed by selecting Map .

Creating Non-OLAP Source Elements

Supports creating non-OLAP source metrics or virtual data points in Configuration Center. The elements created at the global level are universal across all OUs.

Prerequisites

Global business objects such as station type, device type, component type, and custom type have been created and associated with models. For more information, see Configure Global Business Objects.

Procedure

1. Select Global Asset Elements from the list on the left.

2. Select Create Element, and enter the following information on the page:

   • Element Type: Supports KPI and calculation points. KPI is used to register metrics, and calculation points are used to register virtual data points.

   • Asset Classification: Select the asset classification associated with the element, and multiple selections are supported.

   • Conditions: Select the data type of the metric.

     • Interval and Summary Method: Corresponding to metrics of time periods such as D, M, Y, 15m, 30m, etc.
     • Time Range: Corresponding to metrics of time periods such as TD (current day), MTD (current month), L (latest), etc.

   • Dimension: After selecting the element type as calculation point, select the dimension table that needs to be mapped to semantically map the data of virtual data points.

   • Station/Device/Component/Group Type: Select the specific asset type.

   • Standard Terminology: Select a standard terminology.

   • Interval/Time Range: Select the specific time period type of the element.

   • Time Aggregation Method: Specify the aggregation of all data points within a specified time period (granularity).

   • Spatial Aggregation Method: Aggregate simultaneously along one or all objects.

   • Aggregation Dimension: Define the aggregation dimension that the data source can support for metric queries.

   • Name: Element name.

   • Alias: Element alias.

   • Identifier: Fill in the unique identifier of the metric.

   • Interface Identifier: Automatically generated by the system, no need to fill in.

   • Abbreviation: Element abbreviation.

   • Data Type: Type of data obtained by the interface.

   • Unit: Unit of the data. If customization is needed, please contact the system administrator to configure it at the global level.

   • Description: Description of the element.

     
     

     Note

     To obtain the metadata and mapping data of the corresponding business type of the element through the Common Data Service API, a standard metric or virtual data point with the same identifier as the element in Configuration Center need to be created.

3. Once finished, select Save. After creating the feature, you can choose one of the following configurations as needed:

   • Create a mapping: create a secondary indicator under the current feature, and map it to the derived metric in the Metric Management or the cumulative metric in Common Data Service through the identifier.
   • Create an expression: obtain a secondary indicator by simply calculating the feature through an expression.

Creating Mappings

A mapping is an indicator obtained by accumulating the feature values over a specific period of time based on the time range or interval, corresponding to the derived metric in the Metric Management and the cumulative metric in Common Data Service.

If the feature has been mapped to the atomic metric in Metric Management, its derived metrics will be automatically synchronized to Configuration Center and marked as Automatic in the mapping list. You can create a mapping on an existing feature manually, and the manually created mapping will be marked as Manual in the list.

1. Select Global Asset Features in the left-hand list.

2. Select Mapping corresponding to the feature, and select Create a New Mapping on the mapping list page.

3. Enter the mapping Source in the pop-up window and select the Asset Type, Time Range/Interval, and Mapping Identifier that the mapping needs to be associated with.

   Note

   To obtain the metadata and mapping data of the corresponding business type through the Common Data Service API, a secondary metric associated with the same asset type, time range/interval, and mapping identifier needs to be created in Common Data Service.

4. Select Save to complete the creation.

Note

If an expression already exists under the feature, a mapping cannot be created.

Creating Expressions

After creating an expression, an indicator is formed based on simple operations (such as unit conversion) on the feature through the expression. To correspond to the virtual metric in Common Data Service, make sure that:

• The feature identifier is consistent with the identifier of the standard metric in Common Data Service.
• The expression is consistent with the expression configured for the virtual metric.

1. Select Global Asset Features in the left-hand list.
2. Select Expression corresponding to the feature, and select Create a New Expression on the mapping list page.
3. Enter the Type of the asset in the pop-up window, select the Time Range/Interval of the feature, and enter the Expression.
4. Select Save to complete the creation.

Note

If a Manual mapping already exists under the feature, an expression cannot be created.