Using it together requires traceable relationships, time references and data quality.
- 01Buildings & devices
- 02Mapping & quality
- 03Analysis & workflows
Clarify the relationships first
A technical identifier alone does not explain which property or period a value belongs to. Define business relationships and who maintains them before integration.
- Map properties, devices and periods unambiguously
- Define units and formats
- Account for missing data and later changes
The solution approach
Data from different sources is ingested, normalized and checked for correct relationships. This creates a foundation for analysis and further operational workflows.
Missing or unusual values are made visible. When estimates are used, they should remain distinguishable from measured values. Suitability for billing needs a separate business assessment.
How to evaluate the implementation
Useful measures include completeness for defined periods and traceable data mapping. The operating model specifies how failed deliveries and corrections are handled.
- Trace sources and processing steps
- Define quality rules for the intended analysis
- Identify and handle missing deliveries