DEV and PRD Usage, Expectations & Accountability Audience: Analysts, Report Authors, Data EngineersApplies to: Common Data Model (CDM), Data Marts, Power BI reportingPurpose: To ensure shared understanding of how data environments are intended to be used, and to protect confidence in reporting. 1. Purpose of Separation The separation between DEV (Development) and PRD (Production) environments … Read more
How data is structured, governed, and consumed across the organisation 1. Purpose To provide a stable, governed data platform that: 2. Core Principle Data is not delivered as tables — it is delivered as structured, governed objects with defined behaviour 3. Platform Structure 3.1 Canonical Data Model (CDM) The platform is built on a consistent … Read more
Purpose The Data Dictionary is the overarching governance process used to maintain the meaning, structure, lineage, quality rules, and operational control of data assets across the Data Platform. Rather than existing as a single document or table, the Data Dictionary is delivered through a set of linked artefacts, each addressing a distinct aspect of data … Read more
✅ Green — Available and fit for purpose Use Green when: Outcome: Report builder can proceed with confidence. ⚠️ Yellow — Present, but not where/what we expected Use Yellow when: Outcome: Needs a small piece of investigation/remapping, but not a dead end. ❌ Red — Critical gap (blocking) Use Red when: Outcome: Requires Data Engineering … Read more
1. Treat the DWH as the system of record for the week Our existing rhythm is actually very strong: That already gives us something most organisations lack: a weekly data contract. Reports must key off that. 2. Reports should always trail the DWH by one controlled step With DEV → UAT → LIVE workspaces, we … Read more
This process describes how to take a new data source from landing → Bronze → DataMart view, and fully define its attribute lineage in myBMT. 1. Prepare and review the new data source 2. Catalogue and land the source 3. Plan the DataMart view(s) 4. Set up attribute lineage in myBMT For each new view … Read more
Purpose To provide a clear, sustainable leadership structure for the Data & Analytics function by separating accountability for: while maintaining shared ownership of standards and governance. This model is intended to: Context The Data & Analytics function currently spans: These responsibilities place competing demands on a single leadership role: To reduce strain and increase effectiveness, … Read more
Role Purpose The Head of Reporting & Analytics Delivery provides leadership for the organisation’s reporting, analytical outputs, and stakeholder-facing data products. The role exists to ensure that: The role focuses on: Scope and Impact The role: The Head of Reporting & Analytics Delivery operates with: Key Responsibilities (SFIA-8 Aligned) Strategy and Direction (SFIA: Information Strategy, … Read more
Issued by: Data & Analytics TeamApplies to: All data integrations, pipelines, and views entering or leaving the Data WarehouseStatus: Approved DraftDate: [Insert Date]Version: 1.0 1. Purpose This standard defines the structure and principles for integrating data from source systems—including ERP (IFS), Dynamics 365, Power Apps, and SharePoint—into the enterprise Data Warehouse. It ensures that data … Read more
Purpose To help Data, Engineering & Analytics (DE&A) leaders assess current maturity across the five BHAG areas, identify natural strengths, and agree three actions to progress capability and culture. BHAG 1: Culture & Stakeholder Engagement Theme: How people use, trust, and talk about data and information. Ask: BHAG 2: Data Acquisition & Integration Theme: How … Read more