Energy monitoring and sub-metering
Track site and sub-meter data, trends, deviations and savings.
How does it work? →For specific problems. On a common platform.
First, get to know the operation, the result and the conditions of the introduction. You only need to contact us when you want to apply it to your own environment.
Solutions by operational area
Energy community operation
Measurement points, participants, sharing and accounting processes.
Detailed overview →Device and maintenance management
Device status, fault alerts, planned and event-driven maintenance.
The operating process →Mobile field enforcement
Tasks, walkthroughs, checkpoints, photos and offline work.
Field skills →GIS and site overview
Map display of devices, networks, zones and events.
Spatial operation →BIM-based technical view
Linking building model, location hierarchy and technical data.
GIS and BIM together →Smart city device monitoring
Distributed infrastructure, map state and event management.
Urban use →Water and network loss analysis
Examination of zones, water balance, consumption patterns and disorders.
Water overview →Customer and project processes
Customers, contracts, projects, billing and financial relationships.
Business connections →Energy monitoring and sub-metering
Intervention decision from consumption data.
The solution collects and organizes energy data into an organizational, site, building or submeter context. It not only shows how much weight has been lost, but also where it is worth looking into the discrepancy.
Measurement→Normalization→Comparison→Deviation→Action→Back measurement
Energy community
Measurement, participants and billing and allocation logic in one process.
Community production and consumption can be managed transparently if the measurement points, participant rights, sharing rules and billing and allocation periods are linked to the same data model.
It's the system's job
- assignment of participants and measurement points;
- processing of production and consumption data;
- management of sharing and aggregation rules;
- verifiable periodic calculation;
- preparation of report and billing relationships.
The exact billing and allocation and regulation operation is always determined by the given construction and contractual model.
Tool and maintenance
The event should not stop on the dashboard.
Technical data is related to device and location. Based on a verified rule, a deviation can trigger a notification, error ticket or maintenance task.
Typical process
- The device status or measurement value is different.
- The platform identifies the affected device and location.
- An alarm or task is generated for the person in charge.
- Field implementation documents the measure.
- Status sorting and closing are traceable.
Mobile field operation
The work continues even where there is no stable network.
The field user sees his own task, location and control points. The execution can be documented with a photo, measurement, comment and time stamp.
GIS, BIM and spatial hierarchy
Same tool in map, building and business process.
GIS shows the spatial relationships of sites, networks and outdoor infrastructure. BIM can add technical context within the building. Both relate to the same location and device registry.
Possible views
- locations and devices on a map;
- network sections, zones and events;
- building-level-room hierarchy;
- status data linked to a technical model;
- navigation from device to task or document.
BIM functions are a function of the available model and project configuration.
Smart city and water
Distributed infrastructure in a common operational picture.
The condition of city and public utilities can really be interpreted spatially. The platform supports the connection of zones, devices, telemetry, events and field interventions.
Business relations
A physical event can also have business consequences.
On the OrigSmart platform, the device, location and measurement data can be linked to a customer, contract, project or billing and allocation process. Thus, less manual transfer between technical and administrative systems is required.
Connection examples
- measurement point → customer or participant;
- device error → ticket or work task;
- project → location, means and cost;
- measurement period → billing and allocation input;
- report → management or sustainability decision.
Processes in practice
From planning to controlled decisions.
Project tasks and approvals are not isolated records: they remain traceable parts of daily operations.
