4.1 Data Sources There are numerous data sources in BMT many are integrated together in some way, and some are large scale Enterprise Applications and others are smaller. The Enterprise Applications within BMT is frequently under review as we rationalise and modernise our global systems. 4.2 Integrations Strategy The Integration Strategy prioritises seamless connections between … Read more
3.1 High Level Business Reporting Requirements We recognise that specific report requirements are too detailed for a strategy document so instead we will introduce high level functional requirements and non-functional requirements derived from our data governance procedures. An outline framework showing specific requirements is contained at the Annex. The relationship between high level requirements, reports … Read more
2.1 BMT’s Strategy and Vision BMT aims to be a global leader in addressing the most significant engineering challenges of our time. Our vision is to excel in ship design and become a credible digital competitor by transforming asset life cycle and environmental services. We strive to be recognised for our collaborative approach, investing in … Read more
1.1 Why We Need a Data and Reporting Strategy In BMT we see a rapidly changing landscape of risks, opportunities and constraints around data. Whether this is the data we use to make decisions every day to how we support our customers or our employees. Our Business Strategy and our Business Risks build a picture … Read more
(Redrafted for Alignment with Integration Strategy) Key Takeaways 13.1 Integrations Strategy The Integration Strategy prioritises seamless connections between Enterprise Applications and the Global Data Warehouse to ensure standardised and accurate reporting. Key Objectives: The strategy is designed to support both real-time and batch data processing requirements, with scalability to accommodate future applications. 13.2 Integrations Architecture … Read more
(Redrafted for Alignment with Data Operations Plan) Key Takeaways 9.1 Security and Access Control Requirements 9.2 Security and Controlling Access All of our systems, data sources, data warehouses, data marts and reports are developed considering confidentiality, integrity and availability (CIA Triad). The CIA Triad is an important concept in Information Security including ISO27001 and data … Read more
(Redrafted for Alignment with Data Operations Plan) Key Takeaways 7.1 Data Modelling and Transformation Requirements The following requirements have been identified relating to Data Modelling and Transformation: 7.2 Reporting Framework and Data Transformation The Reporting Framework (repeated at Figure 7.1) identified 3 typical data types used in various levels of reporting. It is recognised that elements … Read more
(Redrafted for Alignment with Data Operations Plan) Key Takeaways 5.1 Compliance and Governance Requirement Ensuring compliance with industry regulations, internal governance, and data protection standards such as GDPR and ISO 27001 is paramount. Regular audits, risk assessments, and a robust data governance framework will underpin these efforts. Reporting practices will incorporate legal, commercial, and regulatory … Read more
Treating the Report Designer as the Controller in Power BI makes sense because they are responsible for orchestrating how data (Model) interacts with the user interface (View). The designer’s decisions define how business rules are applied, how data is processed, and how the user interacts with it. In this sense, the Report Designer does act … Read more
1. Model (Data Model in Power BI): 2. View (Report/Visualisation in Power BI): 3. Controller (User Interaction in Power BI): Application of MVC to Power BI Workflow: Practical Example in Power BI: Benefits in Power BI: In conclusion, although Power BI doesn’t directly follow the traditional MVC framework, its architecture of separating the data model … Read more