Employee.Meta_Codes_SkillsBase

Purpose Produces attribute‑level metadata for people and skills sourced from skl.people and augmented with IFS person/employment lookups. Attributes include EMAIL, ID, TEAM_ID, ROLE_ID, LOCATION_ID, DOMAIN, and recent assessment dates. The view follows the CDS object + meta_codes pattern: the item is the Employee object and each row represents a single coded attribute/value, normalised for downstream … Read more

Template.DataMart

<Domain.Object_ViewName> Template note: Replace all <placeholders> with your content. Keep sections, even if marked “N/A”, so views stay consistent across the Common Data Standard (CDS). Purpose A concise paragraph stating why this view exists and how it aligns to the CDS item & values table pattern. Mention the primary decision/use it supports. Example prompt: “This … Read more

Architecture Rules of the Road

A calm, consistent, and clever approach to data engineering. 🔹 1. Look in the Box First Before inventing a workaround, check what already exists.If Microsoft or IFS built it, use it — it’s likely more robust, secure, and supported. 🔹 2. Easy Landings Data should arrive safely and predictably.Keep import containers simple, standardised, and transformation-free.Bronze … Read more

BHAGs: Diagnostic Questions

Purpose To help Data, Engineering & Analytics (DE&A) leaders assess current maturity across the five BHAG areas, identify natural strengths, and agree three actions to progress capability and culture. BHAG 1: Culture & Stakeholder Engagement Theme: How people use, trust, and talk about data and information. Ask: BHAG 2: Data Acquisition & Integration Theme: How … Read more

BHAGs: Maturity Matrix

Purpose: Enable BMT to make informed, confident, and responsible decisions through trusted, accessible, and intelligent data. BHAG 1: Culture and Stakeholder Engagement Foster a culture where people, systems, and decisions are guided by evidence, shared understanding, and confidence in data and information. BHAG 2: Data Acquisition and Integration Build connected and reliable information flows across … Read more

Feedback.Response

The Feedback.Response (Dataverse) table records the progress of project closure feedback requests within the CSMS solution. Each project has one row, which updates as it moves through the feedback workflow. 🧭 How It Works When a project status changes to “Completed”, the Project Manager is automatically sent a feedback approval request. At this point: 🧩 … Read more

Power BI guide: managing the current views & a simple pivot pattern

This note explains how to turn the current views (wide–from–tall) into a report‑friendly table using Power Query (recommended) or DAX. It covers two common layouts: It also shows how to extract a human‑readable Description from the JSON in VALUE_METADATA. Source schema (tall, meta-driven) Expected columns: Assumption: Each (OBJECT_SEQ, [META_TYPE], ATTRIBUTE) appears at most once for … Read more

Standards Statement: Non-Proliferation of Information

To ensure efficiency, compliance, and trust in the Data Warehouse, we commit to the principle of non-proliferation of information. This means that data will be held and processed in a way that avoids unnecessary duplication, ensures clear lineage, and retains only what is required for business and regulatory purposes. Standards This approach ensures the Data … Read more