The architecture doesn't constrain the data. It structures it.
A complete model. Not separate pieces.
DATUM covers the complete data cycle — from strategy to data products — in an integrated, governed and secure-by-design model.
Three complementary planes working together within a continuous data flow.
El gobierno define las reglas. La plataforma ejecuta el ciclo del dato. La explotación activa el valor. Esa separación clara permite que cada plano evolucione sin romper los demás.
Strategic plane
Governance model, roles, policies, data office, committee, backlog and business-aligned decision criteria.
Platform plane
Metadata engines, DataOps, quality, observability and publication that turn the framework into real operations.
Exploitation plane
KPIs, dashboards, data products, business domains, governed self-service and AI foundation.
Del origen al producto de datos
Sources & capture
Operational systems, APIs, files and events. The platform supports batch ingestion and, optionally, streaming and real-time.
Raw & standardisation
First technical landing of the data, initial traceability, structural control and organisation by metadata-governed layers.
Common Data
Corporate common model with entities, relationships, shared semantics and a foundation for cross-business exploitation.
Quality & control
Rules, scorecards, observability, remediation and traceability integrated into the data operations flow.
Business & KPIs
Indicator calculation, aggregations, semantic models and controlled publication for reporting, BI and governed self-service.
Data products & AI
Business exposure by domain, data products, internal marketplace and consistent foundation for advanced analytics and artificial intelligence.
Each plane has a distinct responsibility and its own language.
Governance model, roles, policies, data office, committee, backlog and business-aligned decision criteria.
Metadata engines, DataOps, quality, observability and publication that turn the framework into real operations.
KPIs, dashboards, data products, business domains, governed self-service and AI foundation.
Four decisions that determine whether the architecture scales or becomes technical debt.
No son opciones — son principios que deben estar presentes desde el primer día. Añadirlos a posteriori siempre cuesta más que diseñarlos desde el inicio.
Gobierno, operación y explotación son planos distintos con responsabilidades distintas. Mezclarlos genera dependencias que impiden escalar.
El metadato no es documentación — es el mecanismo que conecta gobierno, DataOps y consumo. Sin él, cada pieza opera de forma aislada.
La arquitectura no se diseña para hoy. Se diseña para que mañana pueda añadirse un dominio, un patrón de streaming o un producto de datos sin rehacer el modelo.
Cualquier dato en cualquier capa debe poder explicar de dónde viene, cómo ha sido transformado y quién lo ha tocado. Esto no es opcional — es la base de la confianza.
One architecture for multiple execution patterns.
The architecture does not limit how data is executed. Batch, streaming and governed publication coexist within the same framework without fragmenting the model.
Scheduled processing for periodic loads, consolidations and structured transformations with integrated quality control.
Additional capability from Governed level for events and lower-latency use cases, and native in more advanced levels.
Data exposure via KPIs, corporate datasets and, at higher levels, domain data products.
Monitoring, logging, alerting and operational metrics to understand what happens in each process and sustain the platform.
From architecture to the operating model
datum_architecture_page.related.lead
DATUM architecture is not a technical choice. It is a set of non-negotiable principles.
These principles are the product quality contract. A CTO·CIO or architect who reads them knows exactly what DATUM guarantees and what it cannot compromise. These are not best practices — they are design constraints.
It does not belong to a system or an isolated technical team. It has a functional owner, quality rules, traceability and authorised use.
First the metadata is defined. Then technical structures are generated. Never the other way around.
Not IT. Not architecture. The glossary and functional dictionary are the Data Owner's responsibility, validated with the technical team.
Each plane has distinct responsibilities and can evolve independently without breaking the others.
Landing, Operational, Common Data, Business. No mixing of responsibilities between layers.
Structures, rules, pipelines and publication are generated from metadata. The architecture is deterministic, not artisanal.
Adding a new domain does not mean rewriting the model. It means parameterising the existing structure.
The same input always produces the same output. Running a process once or a hundred times produces the same result. No variability by state.
Not added afterwards. Quality rules are part of the DataOps circuit from the first ingestion layer.
Ingestion, transformation and publication patterns are reusable across domains. No arbitrary embedded SQL. No artisanal code per project.
Any data in any layer can explain where it came from, how it was transformed and who touched it. Lineage is not optional.
Classification, least privilege, masking and continuous audit are part of the model from day one. Not added at the end.
Each user accesses only the data they need for their function. Access is justified, documented and reviewed.
It is a formal, controlled and traceable delivery. Business accesses published data — not internal operational layers.
It must be governed, justified and traced. Cross-domain access is preferably done through governed publication, not direct access.
A specific profile, a real question.
La deuda técnica crece con cada iniciativa. Cambiar una tecnología rompe el modelo. Añadir un nuevo dominio requiere rediseñar lo que ya existe. La arquitectura que funciona para hoy no aguanta mañana.
Rediseño de arquitectura DATUM con Common Data corporativo, DataOps industrializado y publicación gobernada para analítica multi-país.
The architecture is not valuable for what it contains, but for what it allows to operate.
Next step