Open data interfaces pay off for reporting and integration

Key takeaways
- Collecting meter data is only the first step. Its long-term value depends on whether it can be accessed, processed and shared with the systems that need it, rather than remaining confined to a single platform.
- An open data interface supports integration between applications, makes data easier to reuse and can reduce dependence on a single supplier. These benefits depend on the quality of documentation, access conditions and practical interoperability.
- Data can be made available through different mechanisms, including REST APIs, MQTT communication, HTTP(S) push and CSV exports. Each serves a different purpose, from automated system integration to periodic data exchange.
- A cloud platform without suitable data access or export options can create operational risks. Changes in pricing, service availability or supplier arrangements may make migration difficult, particularly when historical data cannot be exported in a usable form.
- A well-designed data interface should provide clear documentation, appropriate authentication and access controls, and reliable data exchange. Depending on the application, useful capabilities may also include filtering, querying, standardised formats and support for growing data volumes.
- When selecting metering devices or data collection platforms, utilities and building operators should check supported interfaces, documentation, data ownership and export options, licensing conditions and integration responsibilities. Open access does not mean unrestricted access: data must remain appropriately protected.
Data collection is not enough. You do need control. Today, data collection itself is no longer surprising. The real challenge is how to use data afterwards. Not only storing and displaying it, but also providing it to systems that need to process it. The format and openness of data determine whether it will remain usable in the long term.
That is why an open data interface is a key element of modern infrastructure. Unlike proprietary protocols, it allows standardised processing and sharing across applications. The result is greater flexibility, lower vendor lock-in and long-term sustainability.
What an open data interface is and how it works
An open data interface is a standardised way of transmitting and storing data. Thanks to a unified format, it enables efficient processing and the ability to combine data in different applications. Open formats and protocols bring four major benefits: Support across a wide range of tools and libraries, long-term compatibility and backward readability, easy data sharing between users and systems and the possibility to preserve analysis results in a form that remains usable.
Practical examples of open interfaces include API (Application Programming Interface), a structured way to automatically retrieve or send data. MQTT (Message Queuing Telemetry Transport), a lightweight protocol for IoT devices. HTTP(S) Push, an active sending of data to a defined address. CSV export, an universally readable format for Excel and other tools, generated directly in the cloud.
Why cloud-only access is not enough
Cloud services simplify data collection and visualisation, but without an open interface they become a black box. Data is controlled by the provider, not you. If pricing changes or the service is discontinued, you risk losing access or facing a difficult export.
An open interface, by contrast, provides independence. Users can export data, combine it with other sources and use it in their own tools. In practice, this means being able to:
- create customised dashboards and results,
- combine consumption with other data (e.g. production, weather),
- connect company reporting systems (Power BI, Excel, EMS, SAP),
- automate ESG and ISO 50001 reporting,
- integrate data into higher-level systems (BMS, SCADA).
What a quality data interface looks like in practice
To be truly usable, an interface should meet several essential parameters:
Well-documented API
- clear descriptions of query and response structures,
- usage examples, SDK and versioning,
- access to both real-time and historical data.
Secure authentication and encryption
- support for OAuth2, tokens or API keys,
- communication via HTTPS,
- permission management by user or application.
Standard formats and protocols
- JSON, XML, CSV,
- MQTT, HTTP, WebSocket.
Filtering and querying capabilities
- selection by time, data type or device.
Scalability and stability
- ability to handle multiple clients and higher volumes without outages.
Open interfaces are applied across different industries, for example in water utilities, where consumption data combined with meteorological information helps predict network load depending on weather conditions. In district heating meter data flows directly into the SCADA system, supporting boiler operation optimisation and fuel efficiency. In property management sector MQTT transmissions from meters integrated with a BMS system enable immediate reactions to consumption spikes, e.g. automatic load reduction during peak times. Such scenarios clearly show that open interfaces are not just a technical detail, but a tool with a direct impact on efficiency and costs.
Common mistakes in implementation
Despite their advantages, open interfaces are often implemented with recurring mistakes:
- choosing solutions with proprietary protocols that restrict further development,
- insufficient verification of documentation quality and support,
- lack of performance testing with larger data volumes,
- underestimating security and authentication.
Avoiding these mistakes helps protect investments and ensures that the system remains fit for the future.
Think about openness when choosing technology
When purchasing metering equipment or data collection systems, always ask about the availability of open interfaces. Quality documentation, standard protocols and the absence of restrictive licences are decisive factors.
Devices from ACRIOS Systems are built on this openness – converters and gateways with support for MQTT, HTTP(S), REST API, CSV export (processed on the server) and direct integration into building management systems give users the confidence to work with their data completely freely. In the era of digitalisation and energy optimisation, an open data interface is the key to efficiency, sustainability and independence from third parties.
Glossary of terms used
- API (Application Programming Interface): a defined set of rules that allows software systems to request or exchange data and functions
- BMS (Building Management System): a system that monitors and controls a building’s technical equipment, such as heating, ventilation and lighting
- ESG (Environmental, Social, Governance): environmental, social and governance factors used to assess and report on an organisation’s performance and sustainability-related impacts
- HTTP(S) push: a method in which a system actively sends data to a specified HTTP or HTTPS endpoint, for example at scheduled intervals or when a defined event occurs
- ISO 50001: an international standard for energy management systems that helps organisations monitor and improve their energy performance
- JSON, XML and CSV: widely supported text-based data formats: JSON and XML represent structured data, while CSV organises data into rows and columns
- MQTT: a lightweight messaging protocol commonly used to send data from IoT devices to servers
- OAuth2: an authorisation framework that enables applications to obtain controlled access to protected resources using access tokens, without requiring users to share their passwords
- Open data interface: a documented interface that allows data to be accessed or exchanged with other systems, supporting interoperability and reducing dependence on proprietary integrations
- Proprietary protocol: a communication protocol owned and controlled by a single company, whose specification may not be publicly available
- SCADA (Supervisory Control and Data Acquisition): a system used to monitor and control technical processes and infrastructure, such as pumping stations and water networks
- Vendor lock-in: dependence on a single supplier or proprietary technology that makes switching to another solution difficult or costly
FAQs
You do not need to abandon such a system immediately. What matters is whether your provider allows exporting data to open formats or offers an API. This way, you can still work with your data outside their environment.
The most common issues are missing documentation, limited filtering options, or the absence of standard protocols. This is why it is essential to review interface parameters when selecting the technology.
Usually not very complex. Standard protocols such as MQTT, HTTP or CSV are supported by most platforms. It only becomes demanding if a company requires highly specific data combinations or very complex scenarios.
Without proper documentation, an interface is practically unusable. It is advisable to request API documentation samples before signing a contract and to test their functionality.
Open does not mean freely accessible. A good interface uses authentication (OAuth2, API keys), secure transmission (HTTPS), and supports permission settings by user or application roles.
Ready to implement an open data interface in your system? Let’s design a solution that connects your devices and platforms using open standards. Contact us to learn how we can support your reporting and integration needs.


























































