Redstrata Knowledge Base

CLMP Data Governance and DQ Engagement

4 min read

CLMP Data Governance and DQ Engagement

Updated 2026-07-24 based on S-2026-07-24-weekly-briefing — routes a time-critical vendor-driven evidence-continuity risk (Collibra CLI lineage harvester EOL 31 Jul) into Open questions / blockers; no change to the engagement design.

Status: active Started: 2026-05-04 (planned) Last touched: 2026-07-24

Why this project exists

Design a single, joined-up data governance operating model for the CLM Transformation Programme at an Irish Tier-1 retail bank that embeds data quality management into the target credit data architecture, with a defined transition into a sustainable BAU operating state owned by the business and the credit risk function [S-2026-04-25-paul-clmp-brief].

Current state

  • 3-month engagement scoped, 15 tasks across three phases [S-2026-04-25-paul-clmp-brief].
  • Workbook saved at DRAFT v0.1: ~/AgentData/ClaudeAccess/Projects/03 Credit Lifecycle/Briefs/2026-04-26 CLMP DG and DQ Delivery Plan v0.1 DRAFT.xlsx.
  • Anchors: BCBS 239 / ECB RDARR Guide May 2024 / DAMA-DMBOK v2 / DCAM v3; target DCAM 4 at CLM R2.

Phase 1 Mobilise & Discover (4 tasks, 4–29 May 2026):

  • T1 Mobilisation & stakeholder map.
  • T2 Current-state governance review.
  • T3 Current-state DQ process assessment.
  • T4 Gap analysis vs BCBS 239 / ECB / DCAM v3 → Deliverable 1.

Phase 2 Design (4 tasks, 1 Jun – 3 Jul 2026):

  • T5 Target Operating Model design → Deliverable 2.
  • T6 Forum interlock & ToR updates.
  • T7 DQ framework embedded in TOM → Deliverable 3.
  • T8 In-flight controls & remediation playbook.

Phase 3 Socialise & Transition (7 tasks, 1 Jun – 31 Jul 2026):

  • T9 Design workshops & socialisation with BDO, CRO rep, ODS Owner, Reference Data Owners, Enterprise DG.
  • T10 CLMP-to-BAU transition roadmap → Deliverable 4.
  • T11 Capability, skills & tooling assessment.
  • T12 Final design pack consolidation.
  • T13 CRO / BCBS 239 alignment review.
  • T14 Programme Director / BDO sign-off → Deliverable 5.
  • T15 Engagement closeout & handover.

Decisions made

  • 2026-04-25 — Brief is role-agnostic / generic; engagement scoped as 3-month initial rather than full glidepath duration; governance forums referenced generically (Enterprise DG Council, ARB, DQ Forum, BCBS 239 attestation forum) [S-2026-04-25-paul-clmp-brief].
  • 2026-04-25 — Layout: A4, 1 page, header table (Programme / Workstream / Engagement / Reports to / Anchors / Status), six sections (Objective, Why this matters, Role, Responsibilities, Outcome, Deliverables) plus Acceptance line; verified to render as exactly 1 page in PDF [S-2026-04-25-paul-clmp-brief].
  • 2026-04-26 — 15-task delivery plan saved as Excel template with three sheets (Delivery Plan, Phase Summary, Notes) [S-2026-04-25-paul-clmp-brief].

Open questions / blockers

  • Whether the 3-month initial engagement will be re-contracted for follow-on phases as assumed.
  • Whether the forum interlock as designed can absorb the in-flight CLM Design Sub-Committee ToR v0.1 without conflict.
  • Acceptance criteria (Programme Director, BDO, CRO sign-off) not yet secured at point of capture.
  • 2026-07-24 (weekly briefing) — time-critical, EOL 31 Jul: the Collibra CLI lineage harvester and single-file custom-technical-lineage option reach End of Life on 31 July 2026. Any client feeding BCBS 239 / FCA-PRA lineage evidence from the Collibra CLI harvester faces an evidence-continuity break requiring migration (typically to Edge-based harvesting) with re-validation of lineage completeness. Action: check whether this engagement (or the wider CLM lineage evidence chain) has a dependency on the CLI harvester before the deadline and log the outcome [S-2026-07-24-weekly-briefing].
  • 2026-07-31 (weekly briefing) — EOL now effective; move from “check” to dated evidence: the Collibra CLI harvester and single-file definition are confirmed End of Life as of today, and the 2026.07 release additionally flips the Import API default to continueOnError=true. Action, now past deadline: verify any affected client has completed the Edge migration and re-validated the lineage evidence chain, test the continueOnError=true default flip as a silent ingestion-quality risk, and record the outcome as a dated BCBS 239 evidence-continuity note rather than leaving it as a standing check [S-2026-07-31-weekly-briefing].

Connected wiki pages

History

  • 2026-04-25 — Brief design decisions taken.
  • 2026-04-26 — Delivery plan DRAFT v0.1 saved.

S

Graph View

Backlinks

Recently updated

See 113 more →