11.1 Training and User Support Requirements Develop training programmes to help users effectively utilise reporting tools. Establish a support system for addressing user queries and issues. 11.2 Training To support the digital skills development of user the Power BI and Data Visualisation is generally applicable to new users or users who are new to this … Read more
10.1 Distribution and Delivery Requirements Development of Reports: Reports shall follow a lifecycle management approach to ensure that changes to reports do not impact live reports. User Searchability: Users should have a range of options to utilise reports from ad-hoc searches to inclusion in meetings. Alerts and Notifications: Implement alerting mechanisms to notify users of … Read more
8.1 Report Design Guidelines Requirements Users should be able to drill down into detailed data for deeper insights. Provide interactive features for data exploration and analysis. 8.2 Style Guide A standardised reporting layout, structure and use of visuals is essential to enable users of Power BI reports across BMT seamlessly move between reports. To achieve … Read more
5.1 Reporting Tools and Technologies Requirements Reports should be accessible and optimised for viewing on desktop and mobile devices. Ensure a responsive design for a consistent user experience across devices. 5.2 Reporting Framework and Tools The Reporting Framework (repeated at Figure 6.1) identified 4 typical reporting methods: 5.3 In-System Data Reports and Lobbies For many users … Read more
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