Paul Miles — CLM Data Taxonomy Glidepath & Confluence Governance
Tag: S-2026-03-20-paul-clm-data-taxonomy
Type: own-writing
Author(s): Paul Miles (Red Strata)
Date of source: 2026-03-20 (Confluence design notes); 2026-03-22 (glidepath context, Phase 1b, Phase 2, Phase 2b)
Date ingested: 2026-05-17
Authority weight: own-writing.
Raw file: Open Brain corpus snapshot at /_raw_sources/open-brain-2026-05-17-corpus.md.
What it claims
Overall context. A retail bank in Ireland is running a Credit Lifecycle Management (CLM) Programme transforming Corporate, Capital and SME credit processes, technology, and data. A strategic workstream defines, develops and implements a CLM Data Taxonomy with associated governance, operating model, roles, skills, and tooling. The glidepath runs H1 2026 → end of 2029, taking the organisation from low to high data maturity. The taxonomy must be embedded across the full change delivery lifecycle and eventually transitioned to a permanent operational state.
Confluence page structure. Top-level parent: Credit Lifecycle Data Taxonomy. Under this: (1) Credit Management Workstream — child pages for Policy Data Glossary and Covenants Data Glossary; (2) Matrix Workstream — child page for Tier Matrix Data Glossary (already live and fully governed); (3) CLM Workstream — child page for ODS Data Glossary covering Day 2 terms. Each child page governs one Excel-based Data Glossary artefact using Comala workflow for review and approval.
Required page sections (per governed glossary page):
- Current Approved Document section — displays the approved Excel attachment prominently; previous versions retained as attachments for audit.
- Authorised Reviewers and Approvers list.
- Artefact Description — scope, Data Owner name, list of Data SMEs / Data Stewards with roles (author, reviewer, contributor).
- Continuous Improvement and Remediation — linked JIRA Epics and Stories, plus remediation / improvement activities.
- Comala Workflow — embedded for internal review and final approval before the artefact becomes live.
Recommended labels. clm-taxonomy, data-glossary, workstream name (credit-management, matrix-workstream, clm-workstream), status labels (draft, in-review, approved), data-owner name or team, and subject area (policy, covenants, tier-matrix, ods-day2).
Glidepath phases.
- Phase 1b Business Glossaries & SREP 2026 (H1–H2 2026) — parallel to taxonomy design. The 2026 SREP action requires Business Glossaries to be developed and embedded for key CLM workstreams: Credit Management (Policy and Covenants), Matrix (Tier Matrix — already live), CLM (ODS Day 2). Governed via Confluence + Comala. Meeting the SREP deadline in H2 2026 is a top priority.
- Phase 2 Ways of Working & Data Standards (H2 2026 – 2027) — embed taxonomy practices across the full change delivery lifecycle.
- Phase 2b Apply Taxonomy in CLM Programme (2027–2028) — actively use Business Glossaries, Business and Technical metadata, lineage, and DQ artefacts in actual programme deliverables (solution design documents, data models, test cases, reports).
Notable quotes
None — own-writing.
What’s speculative vs. asserted
- Asserted: the glidepath structure, Confluence design, required sections, labels, SREP 2026 priority.
- Speculative: Phase 2 and 2b sit in 2026–2028 and are forward-looking; success is not yet evidenced.
Topics this feeds
Open questions raised
- Whether the 2026 SREP deadline (H2 2026) will be met on time.
- How the Comala workflow integrates with the in-flight CLM Design Sub-Committee ToR v0.1 referenced in S-2026-04-25-paul-clmp-brief.
Ingestion note
Consolidates Open Brain thoughts dated 3/20 (three: Confluence structure, required sections, labels) and 3/22 (three: overall context, Phase 1b SREP, Phase 2, Phase 2b).