Understand EDW information model
- Last UpdatedAug 20, 2026
- 2 minute read
The Engineering Data Warehousing (EDW) manages information in the form of asset records, which are identified by business identifiers such as tag and document numbers.
The result is an object-centric model with one or more associated asset records, as illustrated in the following diagram:
An object must have at least one identifier that uniquely identifies the object and is used to map asset records to it. Additional identifiers may be applied to identify similar information across different information systems.
An object may be optionally classified, providing a hierarchical understanding of the object. Classification may be changed over time – for example, an object may be classified as a Pump and later classified as a Centrifugal pump. Within the EDW, classification, along with any Information Standard expectations and rules, may be changed over time, even changing Centrifugal Pump to a Pump or Pressure Safety Valve, if this sho uld be required. Classification is optional since any object without a class assigned is assigned a classification of unknown, indicating the EDW has observed an object but is unable to understand what it is due to insufficient information. This might reflect old information that should be removed from a source system or document, or a valid object for which the EDW has insufficient information.
As the classification hierarchy is treated as an ontology, a specific class (one with no child classes) is permitted.
Information is mapped to a model described within the Information Standard, according to rules within that standard.
Attribute rules may then be used to define associations between information (for example, a parent tag or an associated document). This then forms the premise for connecting information together, which primarily sho uld be from managed information (specified by information owners and contributors), but in the worst case may be discovered in document content by AVEVA Gateways.
To learn more about processes and interfaces that can help you to work with EDW model, refer to the following: