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
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
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 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
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
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
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
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
14.1 Key Points In this section, we summarise the critical elements of the Reporting Strategy that have been discussed throughout the document. 14.2 Benefits and Outcomes This section outlines the advantages and expected results of implementing the Reporting Strategy. The table below provides a concise overview of the key points and their corresponding benefits and … Read more
13.1 Futureproofing with Microsoft Fabric As Microsoft transitions to Fabric, an integrated end-to-end analytics platform, BMT must prepare to leverage its features effectively. The following steps will ensure readiness: Fabric integrates workloads like Data Engineering, Data Factory, Data Science, Data Warehouse, Real-Time Intelligence, Industry solutions, Databases, and Power BI into a shared SaaS foundation. Each … Read more