Solution Architecture

Release 64

by

Summary of Changes by View 1. project_details_plus_USD & project_details_plus_CAD Status Logic Updated Project Manager Email Added 2. project_details_plus_CAD & project_details_USD Column Name Adjustment 3. project_details_plus_APC, customer_details_APC, project_details_APC PRU Code Mapping Enhancement 4. global_company & global_company_202409 Expanded Source 5. global_organisation & global_organisation_202409 Same as Above 6. employee_item_codes_absence, employee_item_dates_absence, employee_item_values_absence Minor Logic Refinements 7. dates_DIM_DATE_202409 Performance Optimisation … Read more

CDM Migration Playbook

by

Purpose This playbook guides the phased migration from existing DataMart views (202409) to CDM-standard views, including core, meta (dates, codes, values), and item tables. It supports the transition to IFS Cloud and ensures a consistent, scalable data model across all domains. MVP Scope Domains required for MVP: Phased Delivery Approach Phase 1: Live Data Seeding … Read more

Release 63

by

🆕 What’s New New Project View (Item 207) Added project_details_plus_APC to complete the set for regional project reporting. Improved Date Views (Items 20–21, 27–30, 204–205) Programme ID Enhancements (Items 206, 208) Integrated clearer programme identification fields from MIS80 into global organisation views, allowing for cross regional identification. 🔂Development/Improvements for cdm Notes The following files were … Read more

Project: Regional Business Opportunity Pipeline Data Integration

by

Project Description This initiative aims to integrate Business Opportunity Pipeline data from SharePoint Lists and Deltek Vision sources into the central Data Warehouse. The primary objective is to enable consistent, automated global reporting ahead of the GMIS ERP rollout across the APAC, NA, and EU regions. The integration will align with the existing Business Opportunity … Read more

Value Presence Verification (RPV) + Last-Seen Tracking Framework

by

🎯 Purpose This framework ensures that values in complex metadata structures (e.g. project earned value, invoice accounting, or employee attributes) are verified for presence even when using incremental loads. It protects against stale data persistence or silent value loss, using metadata-driven auditing. 🧩 Problem Context In many CDM views, values are upserted using procedures like … Read more

CDM Value Presence Reconciliation Framework

by

🎯 Objective To proactively expire or flag metadata rows that are no longer present in the source data even if their values haven’t changed, avoiding persistence of stale or misleading data. 1. 🏗 Recommended Table Extension Add these optional columns to any table using patch_upsert or put_update: 2. 📥 Staging Input Table – stage.project_values_current Your … Read more

Row Presence Verification (RPV)

by

🎯 Core Issue: 🔍 Risks of the Current Approach Scenario Problem Value disappears entirely You keep the last-seen value forever unless a new version overwrites Value moves to another key The old one is retained, and the new one appears as duplicate context Periodic reporting gaps Reporting shows a “stale” value that’s no longer present … Read more

cont.table_templates

by

Summary The [cont].[table_templates] table defines the structure and metadata behaviour for CDM-managed tables. It acts as a schema blueprint for dynamic table creation, upsert controllers, checksum logic, indexing, and JSON payload generation. All metadata-driven procedures—such as [cdm].[create_table], [cdm].[patch_upsert], and [upsert].[meta]—rely on this table to align logic with the CDM design pattern. ✅ Current Column Structure … Read more

upsert.entity

by

Summary The [upsert].[entity] procedure registers or updates an entity object in the Common Data Model. It constructs a standardised payload using object_code and object_class, along with derived metadata like domain, entity label, and schema. This payload is then passed to [cdm].[patch_upsert]. It is used for adding or updating entries in core tables (e.g. project_core, employee_core) … Read more

upsert.meta

by

Summary The [upsert].[meta] procedure is a lightweight controller for inserting or updating metadata attributes related to a specific object. It constructs a compact JSON payload and delegates the logic to [cdm].[patch_upsert]. It is ideal for managing metadata flags, status indicators, or classifications for objects like projects, employees, customers, and more. 🧭 Key Steps 🧪 Example … Read more