Integration with Existing Systems

(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

Security and Access Control

(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

Data Modelling and Transformation

(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

Data Governance

(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

Data Engineering and Transition to IFS Cloud

What good looks like Background:  By September 2025, all IFS data currently residing in the Apps 10 solution will transition to the IFS Cloud environment. Commitment: Data Engineering commits to ensuring uninterrupted delivery of DataMarts sourced exclusively from IFS Cloud, enabling the continuity of reporting assets. Prerequisites for a Successful Transition 1.    Reduction of Views … Read more

Release 52

Additions Employee.Absence This view combines employee data (DIM_EMPLOYEE_OL) with absence details (QFACT_ABSENCE_DETAILS_OL$) to facilitate the creation of a dataset used for tracking and analysing employee absences in detail. It generates structured JSON data for efficient reporting, compliance, and analytical purposes. Employee.AbsenceLimit This view creates a structured dataset for tracking and analysing employee absence limits. It … Read more

Global.ForEx

Purpose The Global Foreign Exchange Rate view provides a structured dataset for analysing currency exchange rates relative to the British Pound (GBP) as the base currency. This view supports financial and operational use cases requiring reliable exchange rate data for reporting and analytics. Use Case Source DataMart Integration There are no DataMart identifiers Sample Exec … Read more

Employee.AbsenceLimit

Purpose This view creates a structured dataset for tracking and analysing employee absence limits. It links employee details (DIM_EMPLOYEE_OL) with their corresponding absence limit information (QFACT_ABSENCE_LIMIT_OVERVI_OL$), presenting the data in JSON format for improved integration and usability. Use Case Owner: Luisa WinderTypical Use Case: Style: Fact, Each row represents a unique Employee Limit Seq with … Read more

Employee.Absence

Purpose This view combines employee data (DIM_EMPLOYEE_OL) with absence details (QFACT_ABSENCE_DETAILS_OL$) to facilitate the creation of a dataset used for tracking and analysing employee absences in detail. It generates structured JSON data for efficient reporting, compliance, and analytical purposes. Use Case Owner: Luisa WinderTypical Use Case: Style: Fact, Each row represents a unique Employee Absence Seq with … Read more

Controller (Report Designer):

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