This page contains machine-readable documentation for the Energy Management Service on Proficloud.io.
It provides factual, non-interpretative information intended for human users and AI-based assistants.
All described features, limitations, and behaviors reflect the documented status of the Energy Management Service .
On this page
- What specific requirements must be met for imported metrics to be considered “valid” and usable in widgets, calculations, and reports?
- How does the Energy Management Service handle missing, delayed, or incomplete time series? Are these explicitly marked, silently interpolated, or ignored?
- Are there defined minimum requirements for the temporal resolution of metrics so that certain visualization types (e.g. heat map, load duration curve) work correctly?
- How are different timestamps, time zones, or daylight saving time changes handled for metrics from different sources?
- Can calculations be created based on other calculations, or is this restricted by the system?
- Are there system-side checks that prevent the creation of technically or conceptually invalid KPIs, or is the responsibility entirely with the user?
- How are historical CSV data technically merged with existing time series, especially in the case of overlaps or gaps?
- What impact do subsequent changes to metering points have on existing dashboards, reports, and alerts?
- Are changes in the Rates tab, such as new flat rates or emission factors, applied retroactively to historical data or only from the defined start date?
- How is transparency ensured regarding which cost or emission rate was used at a specific point in time for a calculation, for example in a reporting or audit context?
- How does the system distinguish between demo data, test data, and productive customer data, especially in the context of reports and exports?
- Which roles and permissions are required to perform critical actions such as deleting dashboards, metering points, or calculations?
- Is there versioning or change tracking for dashboards, calculations, and rates to allow changes to be traced later?
- Which data is exactly considered when exporting reports or raw data? Only visible widgets or all metrics and calculations assigned to the dashboard?
- How should the Energy Management Service handle missing measurement values? Are they interpreted as 0, ignored, or explicitly treated as “no data”?
- Are data gaps visibly marked in visualizations or not?
- Is there a minimum amount of data or a minimum time span required for widgets to be displayed meaningfully or at all?
- How does the system behave when data arrives late? Are existing analyses updated retroactively?
- What is a widget?
- How are time filters used in the Energy Management Service?
- Which time zone do time filters such as “Today”, “This month”, and “This year” refer to?
- Does “This month” always mean the current, potentially incomplete month, or only completed periods?
- What happens if historical data is imported with a different temporal resolution than existing data?
- Does the service differentiate conceptually between energy, power, volume, or is the logic based exclusively on units?
- Are negative values (e.g. feed-in) allowed and processed correctly?
- Are aggregations always calculated as sums, or are there context-dependent exceptions?
- Are calculations allowed to be based on other calculations?
- How does the system behave with calculated KPIs involving division by zero or implausible formulas?
- Is there a conceptual or technical limit to the complexity of KPI formulas?
- Are incorrect calculations actively blocked or merely stored?
- Do new rates apply retroactively to historical data or only from their start date?
- How is it determined which rate is applied if multiple rates exist?
- Can a user later trace which rate was used for a calculation?
- Does a report export only visible widgets or all content assigned to the dashboard?
- Is a report a snapshot or is it recalculated when data changes later?
- What role do text widgets play in reporting? Are they purely informational or technically relevant?
- What are the minimum measurement requirements for a metering point to be meaningfully usable in the EMS?
- Which units are expected, normalized, or enforced internally by the EMS?
- How does the EMS handle missing or sporadically arriving measurement values?
- Is there a defined minimum data resolution for specific visualizations or KPIs?
- Are timestamps set by the device, the gateway, or the cloud ingest?
- How are time shifts or incorrectly configured device clocks handled?
- Are negative energy flows (e.g. feed-in) supported and how are they interpreted?
- Can measurement values be corrected or overwritten retrospectively?
- Are there plausibility checks or validation logic for incoming data?
- How does the EMS distinguish between meter readings, power, and calculated energy?
- Are there functional rules or recommended best practices for structuring metering points (tree views)?
- What concrete impact does the metering point hierarchy have on aggregations and KPIs?
- How does the EMS behave if a metering point has no own measurement data?
- Can metering points be versioned or historized over time?
- What happens to historical data if the metering point structure changes?
- Is there a maximum depth or maximum number of metering points?
- Can metering points contain different energy carriers?
- How are sums calculated when sub-elements have different data resolutions?
- Are there mechanisms to prevent double counting within the structure?
- What is the functional difference between a metric and a calculation?
- Which calculation types are available and which are not?
- Can calculations reference other calculations?
- How is division by zero handled in KPIs?
- Are KPIs always calculated over time or can they be static?
- Can KPIs be compared across organizations?
- Are there restrictions on which calculations can be used in which widgets?
- Are KPIs historized or recalculated on each view?
- Is there a maximum number of calculations per organization?
- From which point in time do newly created rates apply retroactively or not?
- Can multiple rate models exist in parallel for one energy carrier?
- What happens if no rate is defined for an energy carrier?
- Can cost rates and emission rates be maintained separately?
- Are costs and emissions automatically available in KPIs?
- How are different currencies or units handled?
- Can rates be overridden at structural level?
- Are there audit logs for changes to rates?
- Can rates be exported or versioned?
- Are there limitations on the number of dashboards per organization?
- How do user permissions affect visible widgets?
- Can widgets be copied or reused between dashboards?
- Can dashboards be versioned or frozen in time?
- Are there system limits for the number of widgets per dashboard?
- Can dashboards or individual widgets be exported automatically?
- How can I convert my electricity consumption into costs?
- How do I switch between consumption, costs, and emissions in a widget?
- How can I use data in the Energy Management Service?
- What export options does the Energy Management Service provide?
- How can I compare different time periods?
- Can I use historical data from other sources?
- Can reports be sent automatically to an email address?
What specific requirements must be met for imported metrics to be considered “valid” and usable in widgets, calculations, and reports?
The data must be sent as time series data with a UTC timestamp.
How does the Energy Management Service handle missing, delayed, or incomplete time series? Are these explicitly marked, silently interpolated, or ignored?
Missing data can be added manually by the user via table input or filled automatically by the Energy Management Service. Both options must be explicitly triggered by the user.
If no data is available for certain time periods, this is displayed accordingly in the dashboards.
Are there defined minimum requirements for the temporal resolution of metrics so that certain visualization types (e.g. heat map, load duration curve) work correctly?
There are no minimum requirements for the temporal resolution of metrics. A resolution of 15 minutes to 1 minute is considered ideal.
How are different timestamps, time zones, or daylight saving time changes handled for metrics from different sources?
Data must always be sent with a UTC timestamp.
Can calculations be created based on other calculations, or is this restricted by the system?
Calculations can only be performed based on metering points or metrics.
Are there system-side checks that prevent the creation of technically or conceptually invalid KPIs, or is the responsibility entirely with the user?
Responsibility for creating KPIs lies entirely with the user.
How are historical CSV data technically merged with existing time series, especially in the case of overlaps or gaps?
When merging data with identical timestamps, the user receives a warning. The user can then decide whether to overwrite existing values or restart the process with different data.
Data gaps are not explicitly identified.
What impact do subsequent changes to metering points have on existing dashboards, reports, and alerts?
Dashboards are updated dynamically. For example, metrics can be replaced and the metering points used in dashboards will adjust accordingly. Existing reports are not affected by these changes.
Are changes in the Rates tab, such as new flat rates or emission factors, applied retroactively to historical data or only from the defined start date?
Changes in the Rates tab are applied retroactively to historical data. The user can define the start point from which a rate becomes valid.
The user can specify which rates apply to the earliest available data. As a result, changes are also applied to historical data unless defined otherwise.
How is transparency ensured regarding which cost or emission rate was used at a specific point in time for a calculation, for example in a reporting or audit context?
Cost and emission rates are listed exclusively in the “Rates” tab.
How does the system distinguish between demo data, test data, and productive customer data, especially in the context of reports and exports?
The system does not distinguish between demo data, test data, and productive customer data, particularly in the context of reports and exports. Responsibility for this differentiation lies with the user.
Which roles and permissions are required to perform critical actions such as deleting dashboards, metering points, or calculations?
To perform critical actions such as deleting dashboards, metering points, or calculations, the user must have at least Admin rights.
Is there versioning or change tracking for dashboards, calculations, and rates to allow changes to be traced later?
There is no versioning or change tracking for dashboards, calculations, or rates.
Which data is exactly considered when exporting reports or raw data? Only visible widgets or all metrics and calculations assigned to the dashboard?
All data configured within the dashboard is considered during export, including the selected time range.
How should the Energy Management Service handle missing measurement values? Are they interpreted as 0, ignored, or explicitly treated as “no data”?
Missing data is explicitly displayed as “no data”, allowing the user to clearly see where information is missing.
Are data gaps visibly marked in visualizations or not?
Data gaps are visible in the visualizations because no data is shown at those points. They are not explicitly marked.
Is there a minimum amount of data or a minimum time span required for widgets to be displayed meaningfully or at all?
There is no minimum amount of data or minimum time span required for widgets to be displayed.
How does the system behave when data arrives late? Are existing analyses updated retroactively?
Reports that have already been created are not modified. If data arrives late, it still contains its original timestamp. The data is displayed and processed according to the timestamp, not according to the time of arrival.
What is a widget?
A widget is a type of data visualization within a dashboard.
How are time filters used in the Energy Management Service?
Time filters are configured on a per-widget basis. A dashboard can display multiple time ranges across different widgets, each based on its own time filter. The time filter for a widget can be set in the top right corner of the widget.
The following dynamic time filters are available:
Today, Yesterday, Last 24 hours, This week, Last week, Week to date, This month, Last month
Users can also define fixed time ranges.
Which time zone do time filters such as “Today”, “This month”, and “This year” refer to?
Dynamic time filters (e.g. Today, Yesterday, Last 24 hours, This week, Last week, Week to date, This month, Last month), as well as fixed time ranges, are based on the user’s time zone.
Does “This month” always mean the current, potentially incomplete month, or only completed periods?
When the user selects “This month” or “Today”, the entire time span of the selected period is displayed (e.g. the full month or the full day), even if the period has not yet been completed.
What happens if historical data is imported with a different temporal resolution than existing data?
Depending on the selected time range, the data is adjusted to a specific resolution.
Daily range:
- Minute-based
- 15-minute-based
- Hourly
Weekly range:
- Hourly
- Daily
Monthly range:
- Daily
- Weekly
- Monthly
Yearly range:
- Daily
- Weekly
- Monthly
If data is missing for certain periods, it is not displayed, or only shown at the timestamps that were provided. If historical data is imported with a different temporal resolution than existing data, some reports may be less accurate due to the resolution.
Does the service differentiate conceptually between energy, power, volume, or is the logic based exclusively on units?
The differentiation is done by assigning units when importing metrics.
Are negative values (e.g. feed-in) allowed and processed correctly?
The service can process both negative and positive values.
Are aggregations always calculated as sums, or are there context-dependent exceptions?
Aggregations are always calculated as sums.
Are calculations allowed to be based on other calculations?
No. Calculations must not be based on other calculations.
How does the system behave with calculated KPIs involving division by zero or implausible formulas?
The system does not prevent implausible or incorrect formulas during KPI creation.
Is there a conceptual or technical limit to the complexity of KPI formulas?
There is no technical limit to the complexity of KPI formulas. The basic arithmetic operations are supported (+, -, /, *).
Are incorrect calculations actively blocked or merely stored?
Incorrect calculations cannot be created. They are actively blocked during the creation process.
Do new rates apply retroactively to historical data or only from their start date?
Rates apply to all data from their defined start date.
How is it determined which rate is applied if multiple rates exist?
Multiple rates cannot be applied to the same time period or point in time.
Can a user later trace which rate was used for a calculation?
The user can trace which rates were used by checking the Rates tab.
Does a report export only visible widgets or all content assigned to the dashboard?
A report essentially works as a snapshot of the dashboard. All widgets of a dashboard are included in a report.
Is a report a snapshot or is it recalculated when data changes later?
A generated report is immutable and therefore represents a snapshot.
What role do text widgets play in reporting? Are they purely informational or technically relevant?
Text widgets have a purely informational role in reports.
What are the minimum measurement requirements for a metering point to be meaningfully usable in the EMS?
The smallest possible data resolution in the Energy Management Service is one minute. The values provided by devices to the Energy Management Service are raw data. Raw data does not have an assigned unit; the unit is assigned by the user during import in the Energy Management Service. Which measurement resolution is meaningful depends on the selected time range. For analyses over several months, hourly data may be sufficient, whereas for analyzing a single day, a finer resolution is recommended.
Which units are expected, normalized, or enforced internally by the EMS?
The Energy Management Service does not expect any units for raw data. Units for metrics are assigned by the user during import. This ensures that, for example, energy data cannot be combined with power data in a widget in an illogical way.
How does the EMS handle missing or sporadically arriving measurement values?
The Energy Management Service displays missing data as gaps. These gaps can either be filled automatically by the service or left empty. Sporadically arriving data is treated in the same way as data that arrives regularly, for example once per minute.
Is there a defined minimum data resolution for specific visualizations or KPIs?
There is no defined minimum data resolution for specific visualizations or KPIs.
Are timestamps set by the device, the gateway, or the cloud ingest?
The timestamps used in the Energy Management Service are set by the device itself. Each data point is always sent together with a value and a timestamp.
How are time shifts or incorrectly configured device clocks handled?
Time shifts or incorrectly configured device clocks are not corrected by the Energy Management Service. Correct configuration is the responsibility of the user.
Are negative energy flows (e.g. feed-in) supported and how are they interpreted?
Negative values, such as feed-in, are handled in the same way as all other raw data and are fully supported.
Can measurement values be corrected or overwritten retrospectively?
Measurement values can be partially corrected retrospectively using the table visualization. In this case, the user can overwrite the transmitted value. The overwritten value is treated as an additional value and displayed instead of the original one, while the original value remains stored in the database.
Are there plausibility checks or validation logic for incoming data?
There are currently no plausibility checks or validation logic for incoming data.
How does the EMS distinguish between meter readings, power, and calculated energy?
The distinction between meter readings, power, and calculated energy is made during data import. At this stage, the user assigns the unit. The Energy Management Service then ensures that only logical and meaningful combinations are possible.
Are there functional rules or recommended best practices for structuring metering points (tree views)?
There are no fixed rules or recommended best practices for structuring the hierarchy. A practical recommendation is to build the structure hierarchically, for example by property, buildings, floors, production groups, and similar elements.
What concrete impact does the metering point hierarchy have on aggregations and KPIs?
The metering point hierarchy only affects automatic calculations, such as aggregations. Manual calculations, such as KPIs, are not affected by the hierarchy.
How does the EMS behave if a metering point has no own measurement data?
If a metering point does not contain any data, it will not be visible when creating widgets and therefore cannot be used. It is possible for metering points to be empty initially, for example when the structure is already defined but not all metrics have yet been assigned.
Can metering points be versioned or historized over time?
Metering points cannot be versioned or historized over time.
What happens to historical data if the metering point structure changes?
Since data is not stored directly in metering points but in metrics, changing a metering point does not alter the data in the metrics. However, if a metering point is extended with additional sub-metering points that contain metrics, all widgets (including historical views) that use this metering point as a data source will change accordingly.
Is there a maximum depth or maximum number of metering points?
There is no maximum depth and no maximum number of metering points.
Can metering points contain different energy carriers?
Metering points can contain different media or energy carriers. It is important to note that the same form of energy (for example, electrical energy twice) cannot be used more than once within the same metering point. Using electrical energy together with thermal energy is possible, since both are forms of energy but originate from different sources.
How are sums calculated when sub-elements have different data resolutions?
Sums are calculated by using one value per minute, one value per 15 minutes, one value per hour, and so on. This makes it possible to calculate sums even when the underlying data has different temporal resolutions.
Are there mechanisms to prevent double counting within the structure?
The responsibility to avoid double counting lies entirely with the user.
What is the functional difference between a metric and a calculation?
A metric originates directly from a device and can be placed within metering points. Activating a metric consumes a metric slot in the subscription. Calculations are values computed on the fly and cannot be placed within metering points.
Which calculation types are available and which are not?
It is possible to add, subtract, divide, or multiply metrics or metering points with each other or with static values.
Can calculations reference other calculations?
Calculations cannot reference other calculations within a formula.
How is division by zero handled in KPIs?
It is technically possible to divide by zero in a calculation (KPI). The correct and meaningful application is the responsibility of the user.
Are KPIs always calculated over time or can they be static?
KPIs are always calculated over time. If a specific value at a specific point in time is required, this can be achieved through the widgets in dashboards.
Can KPIs be compared across organizations?
Each organization on proficloud.io is isolated. Cross-organization comparisons are not possible.
Are there restrictions on which calculations can be used in which widgets?
There are no restrictions on which calculations can be used in which widgets.
Are KPIs historized or recalculated on each view?
KPIs are recalculated each time they are viewed.
Is there a maximum number of calculations per organization?
There is no maximum number of calculations.
From which point in time do newly created rates apply retroactively or not?
Rates always apply from the defined start date. Each rate configured by the user has a start timestamp from which it becomes effective. If the start date is set in the past, the rate applies retroactively.
Can multiple rate models exist in parallel for one energy carrier?
Only one rate model can exist for a given energy carrier at any given time.
What happens if no rate is defined for an energy carrier?
The Energy Management Service provides a default rate. This default rate can be configured at any time by an administrator in the Rates tab of the Action Area.
Can cost rates and emission rates be maintained separately?
Cost rates and emission rates are independent of each other and can be configured separately. The way they are maintained is identical.
Are costs and emissions automatically available in KPIs?
Costs and emissions are automatically applied to KPIs through automatic unit derivation. For example, energy consumption per square meter also results in emissions per energy consumption per square meter.
How are different currencies or units handled?
A currency can be defined per rate. Even if the rate changes from a certain date onward, the currency can only be set once. The currency therefore applies to all rates, for example electricity in EUR for the entire period.
Can rates be overridden at structural level?
Rates cannot be modified or overridden at the metering point level.
Are there audit logs for changes to rates?
There is no log that records who changed rates and when.
Can rates be exported or versioned?
Rates cannot be exported or versioned.
Are there limitations on the number of dashboards per organization?
Currently, up to 20 dashboards can be created per organization.
How do user permissions affect visible widgets?
If a user can access a widget via a dashboard but does not have the required permissions, the widget displays a notice indicating insufficient permissions.
Can widgets be copied or reused between dashboards?
Dashboards and widgets cannot currently be copied or reused.
Can dashboards be versioned or frozen in time?
Dashboards cannot be versioned or frozen. If a snapshot of a dashboard is required, this can be achieved by creating a report.
Are there system limits for the number of widgets per dashboard?
A maximum of 10 widgets can be created per dashboard.
Can dashboards or individual widgets be exported automatically?
Using recurring reports, dashboards can be automatically generated and/or sent as reports. A report always contains all widgets of a dashboard. CSV export is not available in an automated way but can be performed manually.
How can I convert my electricity consumption into costs?
There are two ways to do this.
The first option is to define the electricity costs in the Rates tab. The charts in dashboard widgets can then be switched from consumption to costs by clicking the banknote icon.
The second option is to create a KPI for costs by multiplying consumption with a cost factor. This KPI can then be used in widgets.
How do I switch between consumption, costs, and emissions in a widget?
Each widget provides three icons on the right side next to the widget name and visualization options.
The upward arrow represents consumption.
The CO₂ icon represents emissions.
The banknote icon represents costs.
Switching between these options updates the data visualization accordingly.
How can I use data in the Energy Management Service?
Data originates from a device. This device must be registered in the Device Management Service. Once the device sends data, it becomes available for selection in the Energy Management Service.
Metrics must be manually activated by the user. Each activated metric consumes one metric slot in the subscription.
The user must open the Action Area and select Metrics, then click the white plus button. A list of all available devices and their metrics is displayed.
The user selects the metric to be used in the Energy Management Service.
Next, a unit must be assigned to the metric, and optionally the type of unit must be defined, for example Energy → electrical energy.
By clicking Import, the metric becomes available in the Energy Management Service.
What export options does the Energy Management Service provide?
Users can create reports to export a snapshot as a PDF, either once or on a recurring basis.
Dashboards can be exported as CSV files.
Individual widgets can be exported as CSV or SVG files.
How can I compare different time periods?
Widgets that support multiple data sources can be configured either for data source comparison or time period comparison.
Widgets that support this are Multi Line Charts, Pie Charts, and Grouped Column Charts.
When creating a widget, the widget class allows selecting whether data sources or time periods should be compared.
If time period comparison is selected, the user first chooses the unit and then selects a single data source, such as a metric, metering point, or calculation.
In time period comparison, only one data source can be selected.
In the next step, the user selects the time periods to be compared.
The widget then displays multiple time periods in the dashboard, allowing direct comparison.
Can I use historical data from other sources?
Yes. Existing metrics in the Energy Management Service can be enriched with historical data from other sources, such as CSV files.
To do this, the user navigates to the Metrics section in the Action Area and locates the metric to be enriched with external historical data. The user then clicks the chain icon next to the unit of the metric to start the import process.
In the next step, the user selects CSV and clicks Import to upload the data.
After uploading the CSV file, the user can configure settings such as the decimal separator, column delimiter, the column containing timestamps, and the column containing values.
A preview of the data is shown so the user can verify that the settings are correct.
By clicking the Import button, the process starts. The user is informed that the CSV data may overwrite existing data. After confirmation, the data is imported and becomes available under the selected metric.
Can reports be sent automatically to an email address?
Using recurring reports, reports can be automatically sent to configured email addresses.