Asset model
- Last UpdatedAug 23, 2024
- 2 minute read
You can leverage the asset model capability of AVEVA Insight™ having the following objectives, such as:
-
AVEVA BI Gateway operates as an abstraction layer by processing the dimensional model regardless of the distinct assets and FQN/Tagnames to consider.
-
AVEVA BI Gateway needs to resolve
-
“what to do” (for example: populates a dimension, compute a measure calculation, execute backfill processing,and run a scheduled refreshed) from the dimensional model and its internal mechanism (custom queries, and scheduler).
-
“How to do” (for example: which FQN to consider for populating batch dimension, which retrieval mode to consider, does it require dataset manipulation, and which asset and asset’s behavior to consider) from the asset model capability of AVEVA Insight.
-
Asset model structure
The asset model concept can be configured through different AVEVA Insight layers such as:
-
Managed Historian – Tagname Dictionary (built-in and extended properties)
-
MES - Equipment Efficiency Model
-
CIM – Common Intelligent Model
It can be combined in such a way as:
-
Basic asset model
-
Managed Historian only
-
-
Intermediate asset model
-
Managed Historian
-
MES Efficiency
-
-
Advanced asset model (Future Release)
-
Common Intelligent Model
-
REST APIs
AVEVA Insight contents are mainly exposed through three REST APIs which allow interacting with the solution such as:
-
Historian Data REST API (Managed Historian API)
-
Equipment Efficiency REST API (MES API)
-
Common Intelligent Model REST API (CIM API)
For more information about available API endpoints, see the Custom Query section.

Each of the above APIs allows upload or retrieval requests using a web browser or a client-side applications such as:
-
Microsoft Excel (2013, 2016, or Office 365)
-
Business Intelligence (BI) systems
-
Tableau
-
Microsoft Power BI
-
-
Postman