BI,Sucess Story
SUCCESS STORY Engineering KPI Trust Share Reliable Data in a Regulated Industry
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
1/12
Introduction Enercity AG is the integrated partner for the energy and heat transition from the North. We build, operate, and connect renewable energies, heating systems, and stor- age facilities: By intelligently coupling electricity, heat, and mobility, we create a stable, future-proof, and climate-neutral overall system. We turn billions in investments into regional value creation and strengthen the location for industry, municipalities and households. We rely on technological flexibility solutions to keep energy prices stable through smart control and make the transition affordable. enercity is the reliable an- chor in a complex world - we turn the energy transition into a home advantage for the entire region and for Germany. With revenue of around EUR 6.21 billion and around 4,000 employees, the group is one of Germany’s largest municipal energy companies (as of the 2025 financial year).
Rebuilding the Data Platform: A Greenfield Approach
The replacement of the legacy data platform was not treated as a traditional migration project. In- stead of extending existing structures and carrying forward years of accumulated technical debt, enercity deliberately chose a greenfield approach. The existing platform had become increasingly difficult to evolve, limiting scalability, maintainability, and the ability to respond to new business and regulatory requirements. The decision to start with a clean foundation created the opportunity not only to modernize the technology stack but also to fundamentally rethink operating models, architecture principles, and organizational responsibilities. A key objective of the greenfield strategy was to avoid perpetuating historical complexity. Rather than replicating monolithic structures, the new platform was designed as a modular ecosystem built on clearly defined domains and standardized components. This approach enables independent de- velopment and evolution of individual platform capabilities while maintaining consistency across the overall landscape. At the same time, the initiative focused on building internal expertise and operational ownership. The platform was not intended to become another externally managed solu- tion but a strategic capability owned and understood by the organization itself. The clean-slate approach offered an opportunity to establish a scalable foundation capable of sup- porting future business growth, regulatory requirements, and the increasing demand for data-driv- en decision-making. By combining modern technology with internal competence development, the project achieved more than a simple platform replacement. It created the basis for a sustainable data ecosystem that can continuously evolve while remaining under the long-term control of the organization.
2/12
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
Controlling Challenges and Opportunities
Michael Palmer, 2006 “Data is just like crude. It’s valuable, but if unrefined, it cannot really be used.”
Ungoverned data can create the illusion of facts, leading to decisions based on figures that lack a shared definition, context and understanding.
At the same time that enercity recognized the need for a new data platform, Controlling faced the consequences of the existing data landscape in its daily work. Different platforms had developed with limited scalability. Data was held in separate silos, transparency across domains was restricted, and information could only be exchanged to a limited extent across regulatory boundaries. KPI defi- nitions and reported values were not always consistent across the organization. From a Controlling perspective, this exposed the tension captured by the three data metaphors. Data had the potential to become a valuable resource for steering the group and supporting better deci- sions. But without refinement, common definitions, transparent data flows, and agreed reporting perspectives, it also risked becoming an asbestos-like legacy. Every new report could add another val- ue, another interpretation, and another reconciliation task without necessarily creating more clarity. Consider the number of active customer contracts for electricity supply appearing in three different reports. Each value may be correct within its own context. One report uses the latest contract status from the source system, another reflects the portfolio at month-end, and a third applies a different organizational or product scope. None of the figures is necessarily wrong, but they answer different questions without making those differences transparent. Management cannot simply postpone deci- sions until every discrepancy has been resolved. Leaders have to bridge the remaining uncertainty with experience and professional judgement. For management, it was almost impossible to steer an organization, when the underlying informa- tion was difficult to compare, trace and align. Under these conditions, trust in data could not emerge. Before data could become a reliable basis for decision-making, enercity needed to make definitions, responsibilities, data flows and reporting perspectives transparent. The new data platform created the opportunity to address this challenge systematically. For Con- trolling, its promise was not to replace management judgement, but to build the consistent and ex- plainable foundation on which trust in data could grow step by step.
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
3/12
Unbundling and Group Structure
The transformation of the data platform was driven not only by technical requirements but also by the regulatory framework of the German energy market. As part of its corporate structure, enercity operates several subsidiaries with different responsibilities, including the legally independent grid operator, enercity Netz GmbH. Regulatory unbundling requires that network operations remain independent and that sensitive information is protected from unauthorized access. This creates ad- ditional challenges for data management, reporting, and collaboration across the group. The unbundling framework affects multiple dimensions of the organization. Information related to network operations must be protected and shared in a non-discriminatory manner. Financial trans- parency must be ensured through separate accounting structures, legal responsibilities are assigned to distinct entities, and organizational decision-making remains independent. These requirements mean that data cannot simply be consolidated into a single unrestricted environment, but must be managed in a way that balances regulatory compliance with business collaboration. For the data platform initiative, this regulatory context became a key architectural driver. The plat- form was designed to support the separation of subsidiaries while still enabling controlled collabo- ration and information exchange where permitted. Central functions can access cross-organization- al information when required, while individual subsidiaries retain ownership and control of their own data assets. This approach provides a compliant foundation for enterprise-wide reporting and analytics without compromising the independence required by unbundling regulations. As a result , the data platform enables trusted and governed data sharing across the group while preserving the autonomy of the participating organizations. Rather than viewing unbundling as a limitation, the project used it as a design principle for creating a scalable architecture capable of supporting both regulatory compliance and future collaboration across enercity’s subsidiaries.
Data Platform Architecture
The new data platform, aptly named “enCore”, was designed around a clear governance principle: data can be shared and reused across the organization while maintaining the strict separation re- quired between subsidiaries and organizational entities. Rather than creating a single centralized environment, the architecture establishes dedicated environments that support regulated collabo- ration while preserving autonomy and compliance requirements. Data flows through a common ar- chitectural framework from ingestion to business consumption, ensuring that information remains governed, traceable, and consistent throughout its lifecycle.
4/12
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
1
2
3
4
5
Source Systems
Staging Data Lake
Enterprise Warehouse
Information Delivery
Data Consumption
Azure Data Lake Iceberg
Snowflake Data Vault
Snowflake Marts
ERP
Internal apps
LAKE NETZ
NETZ
NETZ
Embedded workflows
CRM
Power BI
LAKE AG
AG
AG
Managed reporting
Customer support
API
LAKE CROSS
CROSS
CROSS
Other systems
Application interfacing
Python dbt
dbt
datavault4dbt
Python on k8s
datavault4dbt
Catalog & Lineage
OpenMetadata Ownership Discoverability
Code & Delivery
GitHub Enterprise Issue Management CI/CD
At the foundation of the platform, data is ingested into dedicated staging environments built on Azure Data Lake and Apache Iceberg. Separate data lake environments are maintained for the dif- ferent subsidiaries and shared service areas, allowing data to be collected, stored, and processed while respecting organizational boundaries. Scalable processing capabilities based on Python and Kubernetes provide a flexible foundation for integrating and preparing enterprise data. An enterprise data warehouse (EDW) built with Data Vault methodology serves as the foundation of the platform. The EDW resides on Snowflake and is implemented using dbt Platform and dat- avault4dbt - a package created by Scalefree to streamline and automate Data Vault implementation. This layer provides a scalable, auditable, and historically traceable repository for enterprise infor- mation. Separate warehouse structures for the individual subsidiaries and shared domains ensure that data ownership and access controls can be implemented consistently while still enabling controlled shar- ing of approved information. The Data Vault methodology also supports long-term maintainability and simplifies the integration of new business areas and future acquisitions. Above the warehouse layer, business-, and use-case-oriented information marts are created to pro- vide data products tailored to analytical and reporting requirements. This separation between en- terprise-wide storage and consumption-ready models ensures that business logic is implemented once and reused consistently across multiple use cases. As a result, analytical applications, opera- tional reporting, and management dashboards can rely on a common and trusted data foundation. The platform supports multiple consumption channels, including reporting solutions, internal appli- cations, embedded workflows, and API-based integrations. This enables business users and techni- cal consumers to access governed data products through the tools most appropriate for their needs while maintaining consistent KPI definitions and standardized reporting across the organization.
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
5/12
Supporting services are integrated across all layers of the architecture. OpenMetadata provides data cataloging, lineage tracking, ownership management, and discoverability, helping users understand where data originates and how it is used. Development and deployment processes are standardized through GitHub Enterprise, CI/CD pipelines, and automated delivery processes, while dbt Platform and Python enable scalable transformation, testing, and operationalization of data products. Togeth- er, these capabilities provide a modern platform that combines governance, transparency, scalabil- ity, and efficient collaboration across subsidiaries and business units.
Data Ingestion
Data Warehousing
DevOps
— Python — PySpark
— Snowflake — dbt Platform — datavault4dbt
— Kubernetes — GitHub Enterprise
— Argo Workflows — Azure Data Lake — Apache Iceberg
Introducing dbt Mesh
To enable a physical separation of development spaces, we introduced dbt Mesh into our core archi- tectural framework. It is a feature of dbt Platform to empower domain teams to build data models as data products in separated dbt projects, and share them programmatically to other projects on the same dbt account. Rather than maintaining a single monolithic platform in dbt, we established separate, autonomous projects for the subsidiaries enercity AG, and enercity Netz - and additionally a centralized Cross project. The latter is meant to manage cross-domain business logics and data use-cases. Despite op- erating independently, all teams follow unified implementation standards, including shared naming conventions and Data Vault modeling rules and best practices.
6/12
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
enercity Netz Data Platform
Cross Data Platform
enercity AG Data Platform
Data Lake
Data Lake
Data Lake
Raw Vault
Raw Vault
Raw Vault
Shares data models
Shares data models
Business Vault
Business Vault
Business Vault
Information Mart
Information Mart
Information Mart
Operative Netz Reporting
Performance Reporting
Operatives Emob Reporting
Data exchange across these domain boundaries occurs exclusively through dbt Mesh at the model level. Crucially, sharing is restricted to curated objects within the Business Vault layer - the tier where business logic and consolidation are applied. This ensures that data always flows in one di- rection through the architectural layers: from the data lake, to Raw Data Vault, Business Vault into different Information Marts. Additionally, all data sharing must adhere strictly to clearly defined governance frameworks and regulatory mandates to align with organizational and legal standards. Therefore, as a standard to maintain operational stability and trust, any team looking to share data (a.k.a. data producer) to an external team (a.k.a. data consumer) must satisfy three technical requirements before exposing a model via dbt Mesh: — Model contracts are mandatory. These enforce schema guardrails by strictly defining column attributes, data types, and primary key constraints, thereby blocking breaking structural chang- es prior to deployment and preventing downstream dashboards of consumers from crashing in production.
— Access control is automated - leveraging dbt to manage Snowflake permissions programmatical- ly, granting read-only access strictly to authorized consumer teams.
— Comprehensive quality testing runs data validations directly within the producer’s project prior to sharing, guaranteeing data integrity and full regulatory compliance across the mesh.
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
7/12
New Platform From a Controlling Perspective
The new platform turned this opportunity into a productive foundation that is being extended step by step. From a Controlling perspective, one of its most important achievements is the compliant exchange of data across organizational and regulatory boundaries. The different domains remain separated where regulatory unbundling requires them to be separated. This enables bidirectional KPI flows. Operational KPIs from business domains and source systems can be made available for Controlling and group-wide steering. In the opposite direction, centrally calculated financial KPIs can be shared with business units and teams. They can use the same figures for project steering and for aligning their activities with group targets and strategy. Instead of copying calculations into multiple reports, the platform creates the basis for reusing governed KPI logic while responsibilities remain with the appropriate domains. The platform also improves technical transparency. Shared implementation standards, documented ownership and data lineage make it easier to understand where a KPI originates, how it is trans- formed and who is responsible for its data product. This does not remove the need for business dis- cussion. It gives that discussion a common and traceable basis. Differences can be investigated in the underlying data flow instead of being reconciled only at the level of individual reports. Scalability is another important benefit. New subsidiaries and additional use cases can build on com- mon patterns rather than creating isolated reporting solutions from scratch. The platform therefore supports both local business expertise and a consistent group perspective. It provides the technical foundation for sharing data without dissolving ownership or regulatory boundaries. Despite this progress, Controlling continued to observe a high level of volatility in reported data. Together with Scalefree, enercity analyzed why KPI values could still change after they had already been calculated or presented. The analysis showed that the causes were not limited to the data plat- form. Many operational source systems had been developed internally around specific business needs. Operational source systems reflected ongoing business processes, including subsequent cor- rections and updates. These capabilities were useful for operational work, but created a challenge for management report- ing. A business event could belong to one reporting period while the corresponding information was entered or changed later. Without a shared understanding of which value was final for a reporting period, or an established communication process for subsequent changes, a KPI could be calculated consistently and still remain volatile over time. This was the next central lesson for Controlling: KPI trust requires more than a scalable architecture, shared definitions, and visible lineage. It also requires an agreed reporting perspective. The organi- zation needs to determine which information belongs to a reporting period, when the reported view becomes fixed, who is accountable for its completeness, and how later changes are communicated. The platform makes this possible, but deadlines, governance and a shared process turn the technical capability into a reliable basis for management reporting.
8/12
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
Volatility and Consistency of KPIs
This raised a practical business question: At what point should the reported values for a period stop changing? enercity addresses this question with a cut-off date. It is a business date on which all val- ues for a reporting period are frozen for management reporting. The cut-off date is different from the end of the business reporting period. The first quarter of a year ends on March 31st, but this does not mean that every relevant business event has already been entered, validated, and delivered by that date. Consider a contract that is finalized on the last day of the quarter. The business event belongs to Q1, but the detailed information may only be entered into the operational system on the following busi- ness day. The same can happen with approvals, corrections, or other processes completed shortly after period-end. If reporting only uses the data available on March 31st, relevant Q1 information will be missing. If it always used the latest available data, however, previously reported Q1 values could continue to change.
One definition, one calculation, one trusted KPI.
1
Start of business reporting period for one reported timeline.
2
01 Jan 2026 Q1 Start
End of business reporting period. All reported KPI entities need to be dated between Q1 start and Ql end.
3
31 Mar 2026 Q1 End
Latest technical delivery date that is accepted to be part in our quarterly reporting
4
Q1 Cut-off
15 Apr 2026
If KPIs need to change after the delivery end date, alignment with Controlling and all reporting users is needed
5
After 15 Apr 2026 Q1 Change Process
The cut-off date provides a way to resolve this tension. In the illustrative Q1 scenario, it could be set to 15 April. This gives relevant transactions time to reach the platform while establishing a defined perspective for reporting. In practice, an appropriate cut-off date needs to reflect reporting sched- ules, weekends, public holidays and the processes that supply the data.
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
9/12
Technical implementation alone, however, does not make a cut-off date binding across an organiza- tion. The next step is to strengthen the shared process around it. Data owners need to know when information must be complete and validated. Controlling and reporting consumers need a com- mon understanding of which perspective is used for management reporting. If relevant information changes after the cut-off date, the impact needs to be assessed, aligned, and communicated instead of silently changing an already reported figure. This process is still being developed into an organization-wide commitment. The technical founda- tion is available, and it makes responsibilities and changes visible in a way that was not possible before. The objective is not to prevent every correction. It is to ensure that everyone knows which KPI value supports a decision, why that value may change, and who must be involved when it does. A cut-off date can only create this confidence if all reporting consumers work with one definition, one calculation, and one trusted KPI. Freezing competing values would preserve inconsistency rath- er than resolve it. Standardized, fixed, and shared KPIs will build trust.
Concept for Data Solution Design
Without strict architectural guidelines, KPI calculations can easily become scattered across the data pipeline. While Data Vault 2 strongly advises against applying business rules before the Raw Data Vault to preserve historical auditability, many organizations fall into the opposite trap of embedding logic during data consumption. Building calculations directly in front-end reports or dashboards may offer great flexibility for report builders, but it inevitably creates multiple versions of the truth as different users freely apply varying filters and business perspectives. To prevent this, enercity adopted a strict “shift-left” paradigm while implementing KPI logics .
1
2
3
4
5
Source Systems
Staging Data Lake
Enterprise Warehouse
Information Delivery
Lean Consumption Pure Visualization Data Consumption
Azure Data Lake Iceberg
Snowflake Data Vault
Snowflake Marts
ERP
Internal apps
LAKE NETZ
NETZ
NETZ
Embedded workflows
CRM
Power BI
LAKE AG
AG
AG
Managed reporting
Customer support
API
LAKE CROSS
CROSS
CROSS
Other systems
Application interfacing
10/12
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
All KPI rules are implemented exclusively in the Business Vault layer, which is the earliest permis- sible stage in the data warehouse to introduce business logic. This enforces a strict, one-way data flow where finalized results are pushed out to information marts, ensuring that core calculations can be reliably reused across countless data products, or shared with external subsidiary teams via dbt Mesh. Within the Business Vault, we maintain a separation between base business rules and reporting period rules . Base business rules are centralized into “Base Objects,” which house shared, compa- ny-wide technical definitions for key concepts and metrics. For a KPI “active electricity supply con- tracts”, these logics determine the baseline qualifications: it must be an electricity product, and the status code must indicate it is active or pending termination. Base objects bring together data from disparate source tables and systems, then apply business rules in this single location. With this, a single source of truth for each KPI is established. On this foundation, we utilize “Timeslice Objects” to apply reporting time boundaries to the es- tablished baseline. Rather than altering the core logic of the KPI, timeslice objects simply evaluate whether a specific record should be counted within a given observation window, generating specific monthly, quarterly, or year-to-date views. To calculate the month-to-date number of active electrici- ty supply contracts, only contracts with creation date within the range of the first day of snapshot’s month to the snapshot date are counted. This allows a single KPI definition to seamlessly serve mul- tiple use-cases with completely different reporting cycles. To ensure these time-based views remain consistent, we rely on the core Data Vault 2 concept of the Snapshot Date , which establishes a unified timeline across the entire data warehouse. Agreed upon by the IT data teams, a daily synchronization occurs at 6:00 AM, fundamentally answering the question of what exactly was known in the data warehouse at that specific point in time. Be- cause every single object uses this exact same timeline, information from completely disconnected source systems can still be perfectly aligned. This baseline definition is maintained centrally in the Cross-project and distributed to the decentralized data projects via dbt Mesh. Ultimately, this snap- shot architecture enables the Controlling department to enforce strict reporting cut-off dates. For example, on the April 15th cut-off for Q1, the system simply locks in the 6:00 AM snapshot from that exact day to generate the previous quarter’s KPIs. This guarantees that reported figures remain con- sistent and reproducible even when source systems change over time. For the Controlling department, this implementation design directly resolves long-standing issues with high data volatility and inconsistent reporting. Historically, many in-house systems only stored current data views, and uncoordinated user modifications often led to retroactive changes that eroded management’s trust in the delivered metrics. By anchoring the architecture on the shift-left paradigm and immutable Data Vault snapshots, Controlling now establishes the foundation for “one definition, one calculation, one trusted KPI”. Once a KPI is generated at the specific reporting cut-off date, it becomes a standardized, locked value that all business units can confidently rely on, elimi- nating the confusion of moving targets and multiple versions of the truth.
Enercity AG Success Story - Engineering KPI Trust - Share Reliable Data in a Regulated Industry
11/12
Conclusion The new data platform enCore has established a scalable and governance-compliant foundation for data-driven decision-making at enercity. By combining regulatory-com- pliant data sharing, standardized KPI definitions, and modern platform technologies, it enables trusted reporting across subsidiaries while preserving the independence re- quired by unbundling regulations. At the same time, the platform creates transparency through clear ownership, meta- data management, and standardized development processes. This not only improves collaboration across organizational boundaries but also provides a foundation that can be scaled to additional subsidiaries and future use cases. The collaboration with Scale- free proved highly valuable, as their expertise and guidance played an important role in successfully establishing enCore and supporting its further evolution. While the transformation is still ongoing, the platform has already laid the ground- work for rebuilding trust in data, reducing silos, and enabling consistent, reliable KPIs across the organization. As the platform continues to evolve, it will further strengthen enercity’s ability to make informed decisions and support the energy and heat transi- tion with trustworthy data.
Scalefree International GmbH Schützenallee 3 30519 Hannover Germany
+49 (511) 879 893 41 contact@scalefree.com www.scalefree.com
CEOs: Michael Olschimke & Christof Wenzeritt
Page 1 Page 2 Page 3 Page 4 Page 5 Page 6 Page 7 Page 8 Page 9 Page 10 Page 11 Page 12Powered by FlippingBook