Multiple data sources, no unified view
The client operated across several regulatory and commercial data environments. Interval meter data arrived via NEM12 files from their retailer on a 24-hour lag. Device readings came in near-real-time from on-site loggers. Third-party CSV exports provided additional context around production and process data. Each source had different formats, different cadences, and different access controls — and none of them talked to each other. Decision-making was slow because every data request required manual aggregation.
Security requirements that shaped the architecture
The client's data governance requirements were non-negotiable: all data in transit had to be encrypted, and access to specific datasets had to be controlled at the user level rather than the organisation level. Some dashboards were for internal operations staff; others were intended for external stakeholders with a narrower view. Conexie designed an ingestion pipeline using SFTP with key-based authentication for file-based sources and configured role-based access controls at the dashboard and widget level within the platform.
Solving for irregular data cadence
The most technically challenging aspect of the project was reconciling data sources that updated at very different intervals. NEM12 data arrived once daily. Device readings updated every five minutes. CSV exports were sometimes weekly, sometimes triggered manually. Conexie implemented a normalisation layer that presented all sources on a unified timeline, with clear indicators of data freshness per source so that dashboard users could see at a glance whether they were looking at real-time or delayed figures.
Bespoke dashboard design
Rather than applying a standard template, Conexie worked with the client's operations and reporting teams to design dashboards that matched how each group actually used the data. The operations dashboard prioritised real-time device status and threshold alerts. The management dashboard showed trend lines and period-on-period comparisons. The external stakeholder view was read-only, scoped to a specific subset of sites, and required separate login credentials with no access to internal operational data.
Outcomes and ongoing value
The client now has a single environment where all their data sources converge — accessible securely by the right people, at the right level of detail. Reporting that previously required an analyst to spend half a day pulling and merging files is now self-serve. The platform's alerting layer has also surfaced several operational anomalies that would have been invisible in the previous siloed environment, including a production process running outside its scheduled window that was driving peak demand charges.