Release 95

by

This release materially strengthens the platform by:

  • Advancing sustainability and compliance domains
  • Establishing metadata-driven pipeline foundations
  • Introducing clear enterprise domain structure
  • Separating identity (Person) from employment (Employee)
  • Creating a scalable identity bridge model
  • Improving resource modelling for planning and reporting

1. Catalogue & Metadata-Driven Pipeline Foundations

  • New catalogue core views created:
    • catalogue_core_details_businessreports
    • catalogue_core_details_datamart
    • catalogue_core_details_source
    • catalogue_core_details_views
  • Outcome:
    Establishes metadata-driven data sources to support scalable and repeatable pipeline development.

2. Enterprise Domain Expansion

  • Introduced a new Enterprise Domain grouping, consolidating:
    • Customer Feedback
    • Compliance
    • Sustainability
    • Utilities (including Catalogue)
  • Rationale:
    Moves these domains from “areas of convenience” into a structured, governed domain model, improving discoverability, ownership, and long-term alignment.

3. Sustainability & Compliance Enhancements

  • global_item_values_co2factor
  • sustainability_item_values_co2factor
  • Renamed:
    • infrastructure_item_codes_osh → compliance_item_codes_osh
  • Outcome:
    Strengthens sustainability and compliance reporting capabilities, aligning naming and structure with enterprise domains.

4. Employee Domain Standardisation (UKS Alignment)

Renamed and aligned all Employee views to UKS versioning:

  • employee_core_details → employee_core_details_UKS
  • employee_core_details_archive → employee_core_details_UKS_archive
  • employee_meta_codes → employee_meta_codes_UKS
  • employee_meta_codes_archive → employee_meta_codes_UKS_archive
  • employee_meta_dates → employee_meta_dates_UKS
  • employee_meta_dates_archive → employee_meta_dates_UKS_archive

Key Changes

  1. Version Alignment
    • Introduced UKS versioning in preparation for IFS Cloud transition
    • Reflects current reality: minimal multi-region employee coverage
  2. Domain Separation
    • Rebalanced responsibilities between Employee and Person
    • Moved Person-in-Company dependent attributes away from Person domain
    • Reinforces:
      • Employee = organisational & assignment context
      • Person = identity & cross-system linkage

5. Resource Domain – Activity Model Refactor

New views introduced:

  • Codes:
    • resource_item_codes_activity
    • resource_item_codes_activity_EMP
    • resource_item_codes_activity_RES
  • Values:
    • resource_item_values_activity
    • resource_item_values_activity_EMP
    • resource_item_values_activity_RES

Change Summary

  • Split activity data into:
    • Employee on Project (EMP)
    • Resource on Project (RES – job/grade based)
  • Re-collated via cvw layer for unified consumption.
  • Outcome:
    Enables clearer planning, reporting, and future modelling of workforce vs resource constructs without losing a single consumption surface.

6. Identity Domain – New Bridge Architecture

New views:

  • identity_bridge_entra
  • identity_bridge_payroll
  • identity_bridge_personid

Purpose

Introduces a dedicated Identity Domain to resolve complex person identification across systems.

  • Supports:
    • Multiple aliases / proxy addresses
    • Cross-system identifiers
    • Canonical identity resolution
  • Outcome:
    Establishes a bridge-based identity model, enabling consistent and governed linkage across domains.

7. Person Domain (Controlled Identity Layer)

New / updated views:

  • person_core_details_UKS
  • person_core_details_ROW
  • person_meta_codes_UKS

Purpose

Provides a governed and curated person layer centred on a canonical PERSON_UID.

  • Covers:
    • Identity attributes
    • Cross-system linkage
    • Restricted classifications
    • Limited mirrored assignment context
  • Design Position
    • Person ≠ Employee replacement
    • Intended for:
      • Identity resolution
      • Secure linkage
      • Person-based reporting where appropriate

Delivery Pattern

  • Exposed via:
    • cvw.person_meta_codes
  • Combines:
    • Key business attributes
    • Joined contextual metadata via META_TYPE

Leave a Comment