Month: January 2025

Identification Guide for Commercially Sensitive Data

by

Commercially sensitive data includes any information that, if compromised, lost, or disclosed without authorisation, could cause moderate financial, competitive, reputational, or operational harm to the organisation. Handling such data requires additional care to ensure compliance with internal policies, contractual obligations, and regulatory requirements. 1. Key Characteristics of Commercially Sensitive Data Commercially sensitive data typically falls … Read more

Standardised DataMart Model

by

Core Views and their Standard Structures Each DataMart will be built on six primary views: 1. Details (or Core) View Purpose: Schema: Column Name Data Type Description company VARCHAR Primary entity identifier object_id VARCHAR Unique object identifier (project_id) seq_json JSON Structured metadata reference for linking name VARCHAR Name of the project/entity description TEXT Brief descriptive … Read more

Release 54

by

Standardisation of DataMart View Queries for SQL OnDemand To enhance query consistency and readiness for SQL OnDemand, we have implemented a major standardisation across all DataMart view queries. Key Enhancements: ✅ Uniform Aliases for Data Sources – All table references now include consistent and meaningful aliases, improving readability and maintainability. ✅ Standard Positioning of — … Read more

Service Level Agreement (SLA) for DataMart availability

by

This draft framework provides a robust SLA for DataMart availability, balancing business needs, technical feasibility, and stakeholder communication. 1. Availability Target Set a clear uptime percentage that aligns with the criticality of the DataMart to your business processes. 2. Operational Hours Define the expected operational hours of the DataMart. Specify if it needs to be … Read more

Microsoft Fabric Readiness Review

by

Microsoft Fabric is designed to integrate multiple analytics workloads, including data engineering, data science, and business intelligence, within a unified platform. While our current Medallion structure already has a logical progression of data refinement (Bronze → Silver → Gold), there are key differences in architecture, tooling, and approach that we might consider while emulating a … Read more

Customer.InvoiceItem

by

Purpose The Customer Invoice Item data mart is designed to provide detailed insights into invoice-level transactional data for customers. It organises, validates, and enriches raw data from the source system into a structured and accessible format, enabling comprehensive analysis and reporting. Use Case Owner: Soon Tan Typical Use Case: Style: Fact, Each row represents a unique Invoice … Read more

Release 53.5

by

An interim release with no functional changes Notes 1. 🔴 MISSING IN PRD CONTAINER: customer_details_CAD.sql2. ⚠️ DIFFERENT: customer_details.sql3. ⚠️ DIFFERENT: project_cost_CAD.sql4. ⚠️ DIFFERENT: project_details_plus_CAD.sql5. ⚠️ DIFFERENT: project_details_CAD.sql6. ⚠️ DIFFERENT: project_revenue_CAD.sql Total number of different files: 5Total number of missing files in DEV CONTAINER: 0Total number of missing files in PRD CONTAINER: 1

Executive Summary

by

BMT’s reporting strategy aims to maximize data use through data governance, Microsoft-based and native IFS technologies, and a common data model for accuracy and consistency. This will enable advanced analytics to enhance decision-making. The strategy also includes the implementation of a federated data governance model, where regional businesses will follow a centralised set of Data … Read more

Annex A: High Level Reporting Requirements

by

These requirements have been derived to align with the Business Processes to shown alignment to the level 1 and level 2 processes arranged by business use case. ID Use Case Requirement L1 Process L2 Process Metric and Purpose Report Type Business Owner 1 Statutory Reporting / Board Campaign Summary Opportunity Management Lead Management Summarise the … Read more