✅ 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 you 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, you … 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
Purpose: Enable BMT to make informed, confident, and responsible decisions through trusted, accessible, and intelligent data. BHAG 1: Culture and Stakeholder Engagement Foster a culture where people, systems, and decisions are guided by evidence, shared understanding, and confidence in data and information. BHAG 2: Data Acquisition and Integration Build connected and reliable information flows across … Read more
This note explains how to turn the current views (wide–from–tall) into a report‑friendly table using Power Query (recommended) or DAX. It covers two common layouts: It also shows how to extract a human‑readable Description from the JSON in VALUE_METADATA. Source schema (tall, meta-driven) Expected columns: Assumption: Each (OBJECT_SEQ, [META_TYPE], ATTRIBUTE) appears at most once for … Read more
To ensure efficiency, compliance, and trust in the Data Warehouse, we commit to the principle of non-proliferation of information. This means that data will be held and processed in a way that avoids unnecessary duplication, ensures clear lineage, and retains only what is required for business and regulatory purposes. Standards This approach ensures the Data … Read more