Sources
ERP, CRM, accounting, online shop, point of sale or planning. Each system remains the system of record for its own process; the platform only takes data from it.
Data platform
To build a data platform is to collect data from your source systems centrally, model it and make it available for dashboards, analysis, AI and apps. Data Analytics B.V. builds the data warehouse and the data model; ENABLE is the usage layer in which your organisation uses the data securely.
You build a data platform to bring data from separate systems, such as your ERP, CRM, online shop and planning, together in one place and make it usable for reporting, analysis and AI. A good data platform consists of layers: sources, a loading process, central storage, a data model and a usage layer.
Data Analytics B.V. builds the data warehouse and data model for organisations, and with ENABLE provides the usage layer: a secure portal with Power BI dashboards, a SQL Explorer with AI, apps and a Data API. That way the platform is not only technically sound, but also in daily use.
Many data platform projects stall because they start with the technology. We start with the question of what people need to be able to do with the data, and work back from there to the model and the sources.
Key points
ERP, CRM, accounting, online shop, point of sale or planning. Each system remains the system of record for its own process; the platform only takes data from it.
Data is loaded periodically from the sources into the warehouse, for example with Airbyte or via the source system's API. This happens outside the ENABLE portal.
Each organisation has its own PostgreSQL database where the data comes together. ENABLE reads from it over an encrypted connection with read-only queries.
Tables and definitions that make the data understandable: customers, orders, revenue, margin. The model is the foundation for dashboards and for AI.
A portal in your own branding with embedded Power BI dashboards, SQL with AI, apps and access profiles per role.
Publish saved queries as REST endpoints with an API key, so other systems use the same data as your dashboards.
A modern data platform is not a single product but a chain. Each layer has its own task, and the quality of the whole is determined by the weakest link. A polished dashboard on a messy model still produces questionable figures.
| Layer | What happens | Example |
|---|---|---|
| 1. Sources | Systems where the work happens | ERP, CRM, online shop, point-of-sale system |
| 2. Loading | Data is retrieved and stored centrally | Standard connector or custom integration via the API |
| 3. Storage | Central database or data lake | PostgreSQL data warehouse |
| 4. Model | Cleaning, linking and defining data | Fact and dimension tables, KPI definitions |
| 5. Use | People and systems use the data | Dashboards, SQL with AI, apps, Data API (ENABLE) |
When you build a data platform, you come across three types of storage. They solve different problems. For reporting, KPIs and questions about business figures, a data warehouse is usually sufficient and the simplest to manage. A data lake or data lakehouse becomes interesting when you have large volumes of raw or unstructured data.
| Data warehouse | Data lake | Data lakehouse | |
|---|---|---|---|
| What it is | Database with cleaned, modelled tables | Storage of raw files in any format | Lake storage with warehouse features on top |
| Type of data | Mainly tables: orders, invoices, customers | Everything: tables, log files, documents, images | Structured and unstructured |
| Strong at | Reliable reporting and KPIs | Storing lots of raw data cost-effectively | Analytics and data science in one place |
| Watch out for | Less suited to unstructured data | Quickly becomes unmanageable without a model and governance | Requires more technology and management |
| Often suits | Organisations that mainly steer on business figures | Organisations with lots of raw or unstructured data | Organisations with their own data engineering team |
Most problems when building a data platform are not technical. They arise because the goal is unclear or because nobody owns the figures.
Terms such as enterprise data platform, cloud data platform and data lake platform sound big, but the question is always the same: what data do you have, who uses it and for what? For many organisations, a central data platform with a data warehouse, a good model and one portal is enough. Larger stacks with a data lake, streaming and notebooks suit organisations with lots of raw data and their own data team.
ENABLE itself runs in the cloud, at Vercel in the Frankfurt region. Where your data warehouse is located depends on your organisation; ENABLE connects to it over an encrypted connection with read-only queries.
ENABLE is the layer where the platform becomes visible to the organisation. Users open Power BI dashboards in a portal in your own branding, ask questions in plain language in the SQL Explorer and use apps that run on the same data. Queries in the SQL Explorer are read-only, with a timeout of 45 seconds.
ENABLE also takes care of the things that are often forgotten: access profiles, row-level security, two-factor authentication, an activity log and insight into which dashboards are used. With the Dashboard Builder, currently in pilot, users create their own dashboards on approved data sources.
In ENABLE
We start with the questions and dashboards you need, as a sketch or prototype, before anything is built.
Data from your source systems is loaded into your own PostgreSQL data warehouse. We determine the best loading route per source during the intake.
We define tables, relationships and KPI definitions, so dashboards and AI calculate with the same definitions.
In ENABLE we link dashboards, queries and apps to access profiles, in your own branding.
Using usage statistics and the daily Power BI health check, Data Analytics monitors what is used and where attention is needed.
FAQ
A data platform is the central infrastructure an organisation uses to collect, store, model and make available data from its systems. It usually consists of sources, a loading process, a data warehouse or data lake, a data model and a usage layer with dashboards, analytics and APIs.
You need access to your source systems, usually via an API or database, central storage such as a data warehouse, a data model with agreed definitions and a usage layer for dashboards and analysis. It is also important that someone in your organisation owns the key KPIs.
A data warehouse contains cleaned, modelled tables and is designed for reliable reporting. A data lake stores raw data in any format, including documents and log files, and is more flexible but quickly becomes unmanageable without governance. For reporting on business figures, a data warehouse is usually the logical choice.
A data lakehouse combines the cheap, flexible storage of a data lake with data warehouse features such as tables and SQL. It suits organisations with lots of varied data and their own data engineering team. For most reporting questions it is not necessary.
ENABLE is the usage layer of a data platform: the portal in which you use dashboards, SQL with AI, apps and the Data API. The data warehouse and the loading of sources are also part of the platform, but happen outside the portal. Data Analytics B.V. builds those parts for you.
In an online demo we show you the portal: dashboards per role, row-level security, plain-language questions and how we set it up and manage it for you.