How Cornelissen Transport gained near real-time profit control with a custom BI platform

Project Background & Context

The Netherlands Enterprise Agency (RVO) supports sustainable growth, innovation, and energy initiatives across the Netherlands. As part of national energy programs, smart meters were installed in buildings to capture real energy usage data.

However, while data was being collected at the source, there was no centralized platform to manage this information or make it accessible to authorized third parties in a controlled and secure way.

This led to the creation of the Datastelsel Werkelijk Energie Utiliteit (DSWEU), a secure, centralized energy data management platform.

The Challenge

RVO faced several critical challenges:

1. No Centralized Data Management

   Smart meters produced valuable energy usage data, but:

   • Data was fragmented
   • There was no single source of truth
   • Access and governance were unclear

2. Secure Data Sharing Requirements

   Energy usage data is sensitive and regulated.
   Any platform had to ensure:

   • Strong access control
   • Secure data exchange
   • Compliance with government standards

3. A First-of-Its-Kind Platform

   This was not a standard implementation:

   • No existing reference platform
   • No proven national blueprint
   • High expectations from multiple stakeholders

Why Existing Approaches Were Not Enough

Before this platform:

• Energy data remained siloed at the source
• Sharing relied on manual or fragmented processes
• There was no validated model for secure, structured third-party access

A traditional off-the-shelf system would not meet:

• Public-sector security requirements
• Long-term scalability needs
• Cross-organizational governance expectations

RVO needed a long-term technology partner, not a short-term vendor.

Solution Strategy

Strategic Goal

To design and launch a secure, centralized energy data management platform that could be expanded and reused across future initiatives.

Approach Chosen

Crebos focused on:

• Central data ingestion from smart meters
• Secure storage with clear governance boundaries
• Controlled access for authorized third-party providers

Risk Mitigation

• Security-first platform architecture
• Explicit access models for external parties
• Validation using real-world energy data

The safest way to introduce large-scale government data platforms is to design them with security, governance, and future expansion built in from day one.

Core Integrations Implemented

Kadaster Integration

• Linked energy usage data to authoritative property records
• Enabled building-level insights and reporting
• Ensured consistent identifiers across systems

Smart meter (Slimme Meter) Integrations

• Electricity usage data ingestion
• Gas and utility usage data ingestion
• Secure, reliable data flows into the central platform

Secure API Layer

• Controlled third-party access
• Role-based permissions
• Full logging and auditability

In simple terms:

The platform connects what a building is (Kadaster) with how much energy it actually uses (slimme meters), all in one secure and governed system.

Security, Quality & Service Management (Applied in Practice)

This platform was delivered using Crebos’ certified practices:

ISO 27001 — Information Security

Applied to:

• Secure integrations with Kadaster and slimme meters
• Encrypted data flows and API communication
• Access control, logging, and audit trails
• Continuous risk assessment

ISO 9001 — Quality Management

Applied to:

• Clear integration requirements and acceptance criteria
• Documented data models and decisions
• Structured testing and validation

ISO 20000 — IT Service Management

Applied to:

• Controlled platform operations
• Incident and change management
• Production readiness and continuity planning

Outcome:

Outcome:A platform that government stakeholders can trust, audit, and extend.

Key Takeaways

• Integrating property and energy data unlocks real insight
• Platform-based approaches reduce long-term risk
• Security-first design accelerates government adoption
• Clean integrations prevent future rework