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

Project.Dates

Purpose: The purpose of this DataMart view is to provide a comprehensive timeline overview of a project’s key dates, from its creation to completion. It consolidates important project milestones such as planned and actual start and finish dates, delivery estimates, and project modifications. This view is designed to help stakeholders monitor project timelines, identify delays, … Read more

Employee.Employment

Purpose: The purpose of this DataMart view is to provide a clear snapshot of an employee’s current and historical employment status within a company. It captures essential details such as employment dates, employment type, and agreement, with a focus on determining whether an employee is currently active or not. This view is useful for HR … Read more

Employee.LeaveEntitlement

Purpose The Employee Leave Entitlement fact table is designed to display quantitative data related to employees. This table integrates with dimension tables, such as employee_details_plus, to provide detailed insights into various aspects of employee performance, compensation, and other metrics. The primary purpose is to support data-driven decision-making across the organisation. Use Case Owner: Sam Jopson-WhiteTypical … Read more

Resource.Details

Purpose The Common View for Resource Details, excluding dates or measures, acts as a unified and reliable source for data on project resources. It is accessible to different departments and systems across the organisation. This view supports integration with fact tables for reporting and analysis and provides a limited set of dimension attributes. Use Case … Read more

Employee.Headcount

Purpose The Employee Headcount fact table is designed to display quantitative data related to employees. This table integrates with dimension tables, such as Employee_Details, to provide detailed insights into various aspects of employee performance, compensation, and other metrics. The primary purpose is to support data-driven decision-making across the organisation. Use Case Owner: Sam Jopson-WhiteTypical Use Case: Resource … Read more

Employee.Details_Plus

Purpose The Employee.Details_Plus view extends the foundational Employee.Details dataset, offering enriched employee data for segmentation, reporting, and integration across organisational systems. It consolidates employment, organisational, and job-related details into a comprehensive, consistent format to support analytical and operational needs. Use Case Owner: Sam Jopson-WhiteTypical Use Case: Integration with fact tables for enhanced reporting and analysis, such as … Read more

Employee.Hours

Purpose The Employee Hours fact table is designed to display quantitative data related to employees. This table integrates with dimension tables, such as Employee_Details, to provide detailed insights into various aspects of employee performance, compensation, and other metrics. The primary purpose is to support data-driven decision-making across the organisation. Use Case Owner: Sarah MartinoTypical Use Case: Calculation … Read more

Employee.Details

Purpose The Common View for Employee Details provides a unified and reliable source for core employee data, suitable for integration across departments and systems. It focuses on maintaining essential and concise information, enabling integration with fact tables for reporting and analysis while ensuring compatibility with slicers and dashboards. Use Case Owner: Data EngineeringTypical Use Case: Provides contents … Read more