Snapshot & Temporal Reporting – Technical Oversight Proposal

by

Purpose This document outlines the proposed technical direction for introducing governed snapshot reporting into the CDM-based Data Warehouse, while preserving the existing temporal and dynamic reporting capabilities. The intention is to support: without reverting to large static snapshot table architectures. Existing Temporal Capability The CDM already supports temporal replay using effective-dated rows. Core temporal fields: … Read more

Snapshot Reporting in the Data Warehouse

by

Overview The Data Warehouse supports both live operational reporting and historical replay through effective-dated CDM views. To support consistent month-end and period-end reporting, a lightweight Snapshot Reporting approach is being introduced. This allows the business to: Current reporting challenge Operational systems are continuously changing. As projects, people, forecasts, and assignments evolve, live reports may produce … Read more

Using asat Mode in get.myview

by

Overview get.myview now supports As At timestamping for CDM views that contain temporal history. This allows reports and analysts to request the state of a DataMart view as it existed on a specific date, rather than always returning the current active position. This is an important step toward consistent historical, trend, and period-end reporting. Why … Read more

CDM Rules of the Road

by

How to use the Common Data Model correctly Why this exists The CDM is designed to provide consistent, reliable, and scalable data across the business. It is not a flat reporting dataset. If used incorrectly, you will see: These rules ensure you get the right answers. 1. Respect Domain Boundaries Each domain has a specific … Read more

Introducing History Mode in get.myview

by

Overview As part of the continuing development of get.myview, we can now expose historical records from current CDM views through a controlled parameter-driven approach. This enhancement allows users and report developers to move beyond the current-state snapshot and review how values have changed over time, using the same trusted view structures already in use today. … Read more

IFS Cloud Datamart – Priority Order

by

🟥 Tier 1 — Foundation / Programme‑Critical If these are unclear or unstable, everything else becomes noisy. These views establish identity, structure, and comparability.They must come first. 1️⃣ Project (Core Project / Delivery Context) Why it’s #1 Minimum viable preparedness If Project is wrong or ambiguous, nothing downstream can be trusted. 2️⃣ Order / Contract … Read more

IFS Cloud Datamart – Preparedness Statement

by

Purpose This statement defines what “prepared” means for the IFS Cloud datamart during the ERP transition period. Its intent is to: This is a deliberately scoped definition. It describes minimum viable preparedness, not full production readiness. What the IFS Cloud Datamart Is For At this stage of the programme, the IFS Cloud datamart exists to … Read more

Roles & Responsibilities

by

Effective change management depends on clear ownership, timely decisions, and coordinated delivery. Delays are often caused less by technical complexity and more by uncertainty over who is responsible for action. This page defines the typical roles involved in managing changes across data, reporting, and analytics services. The objective is to ensure requests are progressed efficiently, … Read more

Emergency Change Route

by

The Emergency Change Route provides a controlled mechanism for implementing urgent changes where waiting for the standard delivery cycle would create unacceptable business risk. Emergency changes are exceptions to the normal change process. They should be used sparingly, assessed quickly, and managed with discipline. Urgency alone does not automatically qualify a request as an emergency. … Read more