Bronze Lakehouse

Version 1.1 by Dimitri Rupp on 2026/06/11 09:16
Warning
For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Bronze Lakehouse

Information

Medallion-Stage: Bronze β€” Raw Ingestion Layer
Quality goal: As close to the source as possible

Overview

The Bronze Lakehouse layer contains data from various source systems with the data quality matching as close to the source as possible. Data is stored in distinct Lakehouses depending on the source system. Depending on the source, the orchestration method used to get data into these Lakehouses can be a Data Pipeline, Gen2 Dataflow or a Synapse Notebook.

Source-to-Bronze Flow

The diagram below shows which source system feeds which dedicated Bronze Lakehouse, and which orchestration method is used.

flowchart LR
    subgraph SRC["**Source systems**"]
        direction TB
        S1[BMD
ERP] S2[Rimo DWH
SPL Software] S3[Board
Planning DB] S4[SharePoint
Lists & Files] S5[H3A
Database] end subgraph BRZ["**Bronze Lakehouses**"] direction TB L1[(BMD Bronze)] L2[(Rimo Bronze)] L3[(Board Bronze)] L4[(SharePoint Bronze)] L5[(H3A Bronze)] end S1 -->|Data Pipeline| L1 S2 -->|Data Pipeline| L2 S3 -->|Gen2 Dataflow| L3 S4 -->|Gen2 Dataflow / Notebook| L4 S5 -->|Data Pipeline| L5 BRZ --> SIL[Silver Lakehouse
cleansed & conformed] classDef src fill:#e3f2fd,stroke:#1976d2,stroke-width:1px classDef brz fill:#f4a261,stroke:#b85c00,stroke-width:1px,color:#000 classDef sil fill:#c0c0c0,stroke:#555,stroke-width:1px class S1,S2,S3,S4,S5 src class L1,L2,L3,L4,L5 brz class SIL sil

The five Bronze Lakehouses

πŸ—„οΈ BMD

Data from the BMD database β€” SPL Tele's ERP system. Hosts financial postings, customer and vendor master data, and accounting transactions.

β†’ BMD Bronze Lakehouse

πŸ—„οΈ Rimo

Data from the Rimo DWH β€” SPL Tele's own software product. Provides project, resource and operational data used by Power Users.

β†’ Rimo Lakehouse

πŸ—„οΈ Board

Data from the Board database β€” used for planning and controlling. Loaded via Gen2 Dataflow.

β†’ Board Bronze Lakehouse

πŸ—„οΈ SharePoint

Data from SharePoint sites β€” typically lists, libraries and Excel files maintained by business teams. Used to bring decentralised data into the Lakehouse without a dedicated source database.

β†’ SharePoint Bronze Lakehouse

πŸ—„οΈ H3A

Data from the H3A database β€” third-party operational system. Loaded via Data Pipeline.

β†’ H3A Bronze Lakehouse

Orchestration methods

Three methods are in use, chosen per source system:

MethodTypical useStrength
Data PipelineDatabase sources (BMD, Rimo, H3A)Native Fabric orchestration; copy + transform; parameterizable
Gen2 DataflowSources reachable via Power Query (Board, SharePoint Lists)Low-code; reuses existing Power Query knowledge
Synapse NotebookComplex transformations, file parsing, custom logicFull PySpark / Python control; ideal for non-trivial SharePoint payloads

Design principles

  • One Lakehouse per source system β€” keeps Bronze stable and the lineage obvious.
  • Schema close to source β€” no joins, no enrichment in Bronze; only raw or near-raw tables.
  • Idempotent loads β€” pipelines and dataflows can be re-run without breaking history.
  • Append where possible, full-load where cheaper β€” chosen per table based on volume and change pattern.

Where Bronze fits in the bigger picture

Information

Bronze β†’ Silver β†’ Gold. Bronze is only the raw landing zone. Cleansing, conforming and business-friendly modelling happens in the Silver and Gold Lakehouses.


Information

Migration footer
Source: Bronze Lakehouse (SharePoint)
Original author: Bukkerji Sreejith β€” Sreejith.Bukkerji@spl-tele.com
Original last-modified: 2025-10-17
Migration date: 2026-05-24
Migrated by: Dimitri Rupp via ClaudeAI
Notes: EN-Original preserved; decorative Hubble stock images omitted; Mermaid source-to-Bronze flow added; orchestration table extracted from prose; cross-links to all 5 sub-Lakehouses + Silver/Gold/Architektur.


Verwandte Themen

Kuratiert β€” kann direkt im Editor ergΓ€nzt werden://

Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:IT-Wiki.Makros.Verwandte-Themen.WebHome]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.


Status: Migriert β€” Team-Review ausstehend Β· Owner: (festlegen) Β· Letzter Review: 2026-06-11