Skip to content
Davide Scuteri Moretti
Senior Data Architect
Curriculum Vitae
CV / 2026
Portrait of Davide Scuteri Moretti, Senior Data Architect & Head of Development for Data

Davide Scuteri Moretti

Senior Data Architect & Head of Development for DataBeta 80

Senior data architect and technology leader specialising in governed Data Platforms, semantic Lakehouse architectures, computational Data Objects, distributed processing, scientific and clinical data, emergency-response systems, IT service management and metadata-driven engineering.

Enterprise Data PlatformsComputational ArchitectureSemantic Data ModellingData GovernanceAI-Ready Systems
davide.scuteri@beta80group.itMilan, Italy
§ 01 Professional Profile

Davide Scuteri Moretti is a Senior Data Architect and technology leader specialising in the conception of enterprise Data Platforms, semantic Lakehouse architectures, governed Data Objects and computational systems for transforming heterogeneous information into reusable, auditable and analytically meaningful assets.

As Head of Development for Data at Beta 80, he is responsible for the architectural direction of the company's data-development initiatives and for the design of the logical, semantic and technological foundations of complex Data Platforms. His work combines enterprise architecture, database engineering, distributed computation, mathematical modelling, interoperability, privacy engineering, data governance and advanced analytics.

Within Beta 80, Scuteri Moretti has conceived and led the architectural design and technical specification of projects spanning healthcare, emergency management, scientific imaging, pharmaceutical logistics, clinical research, IT service management and standardised clinical-data modelling.

A mature Data Platform must preserve source evidence while separating it from the identities, events, meanings and relationships required by the wider organisation.
§ 02 Current Position
Beta 80

Senior Data Architect & Head of Development for Data

Current

Scuteri Moretti leads the architectural design of Data Platform solutions and the evolution of Beta 80's data-development capabilities.

  • Defining logical, semantic, application and technology architectures.
  • Coordinating the evolution of OCTAVIA as a computational Data Framework.
  • Supervising Data Object modelling and Bronze, Silver, Gold and Data Product boundaries.
  • Establishing ingestion, transformation, reconciliation and publication patterns.
  • Designing metadata-driven and contract-first pipelines.
  • Coordinating integration across relational, semi-structured, streaming, document and scientific sources.
  • Specifying data-quality, lineage, quarantine and replay mechanisms.
  • Defining privacy, masking, pseudonymisation, access and retention controls.
  • Guiding engineering teams from architectural design to executable pipelines.
  • Aligning platform architectures with advanced analytics, machine learning, process mining, graph analysis and generative AI.
  • Translating business, clinical, scientific and operational requirements into implementable technical specifications.

His role spans strategic design and delivery: from executive-level platform positioning to physical data models, DDL, APIs, Airflow DAGs, Spark transformations, Python ETL modules, data contracts, quality rules and infrastructure sizing.

§ 03 Selected Architecture Portfolio
01

OCTAVIA — Computational Enterprise Data Framework

RolePrincipal Architect and architectural owner
DomainEnterprise Data Framework, governed Data Objects, metadata-driven Lakehouse and AI-ready data products

Conceived OCTAVIA as a computational method for transforming dispersed enterprise information into governed, reproducible and reusable knowledge structures: source-preserving Bronze ingestion, task-based semantic decomposition, Silver entity reconstruction, Gold metrics and analytical products, metadata-driven execution, drift management, executable quality and lineage, privacy engineering, selective quarantine and controlled publication.

02

OCTAVIA OME-Zarr Scientific Imaging Framework

RoleLead Data and Solution Architect
DomainBiomedical imaging, computational biology and scientific analytics

Designed the end-to-end architecture for acquiring, governing and transforming OME-Zarr scientific-imaging packages into OCTAVIA Data Objects. PostgreSQL manages batches, state, staging, audit and lineage; object storage retains OME-Zarr assets, CSV publication packages and Parquet datasets; Airbyte acquires, Airflow orchestrates, Python interprets OME-Zarr structures and Spark materialises. Reference workload: 40 metadata nodes, 18 multidimensional arrays, six scales per scientific product and 41,116 expected chunks. Delivered for Clepio Biotech, an academic spin-off of the University of Florence born of research between the University, LENS and the CNR, and extended internationally through the EIC Transition project 3D PATH with the University of Bern.

03

RMS-EMMA — Bronze-Only Emergency Data Object Architecture

RoleLead Data Architect and Data Model Designer
DomainEmergency response, public safety and mission-critical operations

Designed a deliberately evidential, source-aligned and non-relational Bronze layer with wide Data Objects, task-based provenance (TASK and TASK_COLUMN), and strict rules: no foreign keys among Bronze Data Objects, no central event hub, no silent normalisation of source identifiers, no loss of original payloads. Silver adds source evidence, field lineage and auditable match decisions. The governed NUE 112 historical corpus supports algorithm evaluation, semantic research, simulation and benchmarking within an engineering ecosystem rooted in Beta 80's Politecnico di Milano origins and its university relationships.

04

IFO Pharmaceutical Logistics Data Programme

RoleLead Data Architect and Metadata-Driven ETL Designer
DomainHealthcare logistics, pharmaceutical consumption, budgeting and cost control — Istituti Fisioterapici Ospitalieri (IFO), Rome

Designed the architecture for populating an analytical pharmaceutical-consumption domain from AL healthcare Data Objects: 59 field-level rules, 10 logical source domains, 5 target Data Objects and 17 transformation categories. A modular Python ETL turns the Excel mapping matrix into executable metadata; deterministic business-key hashes support idempotent MERGE and safe replay. Positioned institutionally as a strategic information foundation for IFO — a dual-IRCCS research hospital comprising the Istituto Nazionale Tumori Regina Elena and the Istituto Dermatologico San Gallicano — giving executive management, hospital pharmacy, clinical departments, finance and research leadership a governed common language for consumption, cost, budget and forecast, and making the domain research-ready for IFO's academic network (Sapienza, Tor Vergata, Roma Tre, Siena, L'Aquila, Unitelma Sapienza, Campus Bio-Medico, Cattolica del Sacro Cuore and others).

05

OMOP Common Data Model Architecture Catalogue

RoleClinical Data Architect and OMOP Model Designer
DomainClinical data standardisation, observational research and real-world data

Designed an implementation-oriented catalogue of the principal objects and fields of the OMOP Common Data Model, specifying for each field the category and table, datatype, required status, key membership, references, semantic domain, interpretation, ETL conventions and formal-specification reference.

06

OCTAVIA / ServiceNow Semantic Data Object Architecture

RolePrincipal Semantic Architect
DomainIT Service Management, CMDB, CSDM and operational intelligence

Designed the integration of ServiceNow into OCTAVIA as a computational representation of work, service, time, risk, identity, topology and knowledge — eight semantic Data Objects rather than a ticketing replica — balancing semantic fidelity against governance and consumption complexity.

07

SUN IN SEAD — Bio-Clinical Data Platform

RoleLead Data and Solution Architect for Beta 80
DomainPrecision medicine, molecular diagnostics and clinical research

Programme PR Calabria FESR FSE 2021–2027, project code J49I24001710005. Defined the architectural framework connecting biomedical experimentation, clinical information, biological samples, genetic analysis, Raman spectroscopy and machine-learning validation, separating direct patient identity from laboratory sample identity through pseudonymised identifiers.

§ 04 Core Competencies

Enterprise Data Architecture

  • Data Platforms, Data Lakes, Lakehouses and logical Data Warehouses.
  • Enterprise Data Object modelling.
  • Domain, canonical, event, temporal and longitudinal modelling.
  • Data-product and semantic-layer design.
  • Metadata-driven and contract-first architecture.
  • Federated and multi-domain data environments.

Data Engineering

  • Batch and streaming ingestion.
  • ETL and ELT architecture.
  • CDC and replication.
  • Python-oriented pipelines, Airflow DAGs, Spark and PySpark.
  • Kafka event integration, APIs and file-based exchange.
  • Idempotent loading, selective replay and schema evolution.

Governance and Quality

  • Technical and semantic metadata.
  • Record- and field-level lineage.
  • Data catalogues and quality rules.
  • Publication gates, quarantine and reject management.
  • Masking, pseudonymisation, privacy and retention policies.
  • Audit, reproducibility and versioning.

Advanced Analytics and AI

  • Feature-space and training-dataset design.
  • Operational anomaly detection and process mining.
  • Graph analytics and entity resolution.
  • Deterministic and confidence-based matching.
  • NLP, text embeddings, semantic search and RAG foundations.
  • Change-risk, SLA-risk and scientific-classification preparation.
§ 05 Technology Landscape
Data processing and orchestration
Python, Pandas, Polars, Apache Airflow, Apache Spark, PySpark, Scala, R
Databases
PostgreSQL, Microsoft SQL Server, Oracle, Oracle RAC, Oracle Exadata, MySQL
NoSQL and distributed platforms
MongoDB, Cassandra, HBase, Redis, CouchDB, Hadoop, Cloudera
Streaming and integration
Apache Kafka, Airbyte, REST, OpenAPI, JSON, XML, CSV and controlled file exchange
Cloud and platform engineering
Kubernetes, Docker, Helm, Terraform, Azure, Google Cloud, object storage and Databricks
Data formats
Parquet, JSONB, OME-Zarr, OME-NGFF, DICOM, FASTQ, VCF and OpenDocument formats
Governance and validation
Collibra, JSON Schema, Pydantic, Great Expectations, Deequ and Unity Catalog
Observability
Prometheus, Grafana, Alertmanager, Loki and OpenSearch
ETL and enterprise integration
SSIS, IBM DataStage, Talend, Informatica PowerCenter, SAS Data Integration, Oracle Data Integrator and Oracle GoldenGate
Business intelligence
Power BI, Tableau, MicroStrategy, SAP BusinessObjects, Pentaho and Apache Superset
§ 06 Healthcare and Scientific Standards
HL7 v2, HL7 FHIR, CDA and C-CDA.
DICOM.
OMOP Common Data Model.
OME-Zarr and OME-NGFF.
SNOMED-oriented terminology.
Genomic formats including FASTQ and VCF.
Clinical laboratory and diagnostic-reporting models.
Biobank, specimen and experimental-data traceability.
Healthcare privacy and pseudonymisation.
§ 07 Previous Professional Experience
IBL Banca

Head of Data and Business Intelligence Area · Senior Data Architect & Data Scientist

2014–2019

Led functional analysts and data scientists responsible for enterprise reporting, direct data analysis, Data Warehouse development and Big Data environments.

  • The bank's SQL Server and Oracle Data Warehouse.
  • Departmental Data Marts.
  • Real-time data flows.
  • A Cloudera-based Big Data environment.
  • Multiple MongoDB information domains.
  • Kafka- and Spark-based processing.
  • Executive and departmental reporting.
  • Machine-learning tools supporting strategic decision-making.

He coordinated teams and external consultants across analytics, database, infrastructure and reporting activities.

§ 08 Leadership and Delivery

Scuteri Moretti has coordinated multidisciplinary teams including data engineers, database administrators, functional analysts, data scientists, software developers, cloud and infrastructure engineers, external consultants, clinical and scientific stakeholders, and governance and security specialists.

Artefacts produced
Executive architectural documents.
Detailed technical specifications.
Logical and physical data models.
Data dictionaries and DDL.
API contracts and pipeline designs.
Governance artefacts.
Cost and sizing estimates.
Implementation roadmaps.
Training and knowledge-transfer materials.

He communicates the same architecture to executives, business owners, clinicians, scientists and engineering teams without reducing it either to managerial abstraction or to unnecessary technical detail.

§ 09 Technical Writing and Thought Leadership

Scuteri Moretti is also the author of extensive technical writing on the architecture, semantics and philosophy of Data Platforms. His work includes two collections of fifteen essays: A Computational Culture of Data Platforms, and The Discipline of Data Platforms.

The essays address semantic latency, Data Objects, contract-first architecture, determinism, reproducibility, idempotence, append-only systems, semantic versioning, schema and semantic drift, executable lineage, data quality as a computational property, quarantine, governance by design, data minimisation and the Data Platform as an internal product.

§ 10 Professional Positioning

Davide Scuteri Moretti's distinctive professional contribution is the ability to connect four dimensions that are often separated:

01Enterprise strategy, which determines why a platform must exist.
02Semantic architecture, which determines what data are allowed to mean.
03Engineering, which determines how the platform actually runs.
04Governance, which determines why its outputs can be trusted.

His architectures move from mathematical abstraction to executable systems, from source-specific data to stable enterprise objects, from clinical or operational requirements to distributed pipelines, and from technical storage to reproducible analytical products.

He approaches the Data Platform not as a passive repository, but as an institutional computational capability: a system through which an organisation can explain what it knows, how it came to know it and under which conditions that knowledge may be used.
Begin a conversation →