Training Mode
Training Mode — Explore and practice freely. Any items you create exist only in this browser session. Login as Admin to make permanent changes.

Platform Guide

Learn how to use every feature of this Data Governance platform, what each module does, and the recommended sequence to set up and operate a data governance program from scratch.

Recommended Journey

Follow this sequence to set up governance correctly. Each step builds on the previous one.

1. Domains 5 min
2. Glossary 30 min
3. Classify 15 min
4. Metadata 20 min
5. CDEs 10 min
6. Lineage 20 min
7. Approve 10 min
1
Set Up Data Domains
Go to Domains

Define your business areas first. Domains are the top-level organizational structure that everything else fits into.

What to do:
  • Review the 10 pre-loaded banking domains (Customer, Account, Transaction, etc.)
  • Assign a Domain Owner — the person accountable for data quality in that area. Terms without their own owner inherit the domain owner automatically.
  • Create Subject Areas within each domain to group related terms (e.g., Customer → KYC, Demographics, Segmentation)
  • AI Suggest: Click the button to let AI recommend subject areas and terms for your domain
  • Click into any domain to see its terms, subject areas, and ownership
Why first? Every business term must belong to a domain. You can't create a term without a domain to assign it to. Think of domains as filing cabinets — set them up before filing documents.
What are Subject Areas? Subject Areas are sub-categories within a domain that group related terms. For example, the Customer domain might have subject areas like KYC (Know Your Customer), Demographics (personal info), and Segmentation (customer profiling). They help organize a large domain into manageable sections.
AI-Assisted Setup Inside each domain, use the AI Suggest button to automatically generate recommended subject areas and business terms specific to your domain context. Review the suggestions and accept, modify, or reject each one.
2
Build the Business Glossary

The glossary is the heart of data governance. Define every important business term so everyone agrees on what the data means.

What to do:
  • Browse: Explore the 45 pre-loaded banking terms
  • Search: Use the search bar to find terms by name, domain, or keyword
  • Create: Click "Create Term" to add new business terms
  • AI Assist: Use the AI Suggest button to auto-generate definitions
  • Detail View: Click any term to see its full definition, metadata links, lineage, and history
AI-Powered Creation When creating a term, type the name and click "AI Suggest." The AI will generate a definition, suggest a classification, identify related terms, and recommend whether it should be a CDE — all specific to banking context. You can accept, modify, or reject the suggestions.
Term Lifecycle:
DRAFT PENDING REVIEW PENDING APPROVAL APPROVED
Terms go through a dual-approval workflow. A Data Steward reviews first, then a Data Owner gives final approval.
3
Classify Data Sensitivity
Review Classifications

Assign a sensitivity level to each term. This determines how data must be stored, encrypted, masked, and shared.

What to do:
  • Review each term's classification (set during creation)
  • Use AI Classification to get suggestions based on the term's definition and domain
  • Ensure PII terms (names, DOB, email) are marked as PII
  • Ensure payment card data is marked as PCI
  • The 6 levels: PUBLIC → INTERNAL → CONFIDENTIAL → HIGHLY CONFIDENTIAL → PII/PCI
Why classify? Classification drives security controls. A "CONFIDENTIAL" field gets encrypted; a "PII" field gets masked in non-production. Without classification, sensitive data might end up in an unprotected test database.
4
Map Technical Metadata
Go to Metadata

Connect business terms to their physical database tables and columns. This creates the traceability auditors require.

What to do:
  • Explore source systems (Core Banking, EDW, Risk Engine, etc.)
  • Browse systems → tables → columns in the metadata picker
  • Link business terms to their physical columns using the correct Link Type
  • For calculated fields, link multiple source columns as DERIVED_FROM
  • Add a derivation formula to document how columns combine
  • Verify links and review data types, primary key flags
  • Use Upload to import metadata from your own systems
The Bridge Technical metadata is the bridge between business language and IT reality. When a business user says "Account Balance," this mapping shows it lives in ACCOUNT_MASTER.WORKING_BALANCE (DECIMAL 18,2).
Understanding Link Types
DEFINES This column is the authoritative source for the business term (1:1 match)
POPULATED_BY This column is loaded/populated from another source into a downstream table (e.g. EDW, ODS)
DERIVED_FROM This column is used as an input to calculate the business term (ratios, aggregates, formulas)
REFERENCED_IN This column references the term indirectly (e.g. in reports, views, lookup tables)
Calculated / Derived Fields For terms like Net Interest Margin or Debt-to-Income Ratio that combine multiple columns, link each source column as DERIVED_FROM and add a derivation formula to document how they combine (e.g. INTEREST_INCOME / AVERAGE_ASSETS * 100).
5
Identify Critical Data Elements
CDE Registry

Mark which terms are CDEs — the data elements essential for regulatory reporting and risk management.

What to do:
  • Review the CDE Registry to see all flagged CDEs
  • Verify each CDE has at least one metadata mapping (not "unmapped")
  • Check verification status and confidence scores
  • Filter by domain to see CDEs per business area
  • Flag new terms as CDE during term creation if needed
BCBS 239 Requirement Regulators expect every CDE to be traceable end-to-end: from source system to report. An unmapped CDE is a red flag during audits. The CDE Registry shows you which CDEs need attention.
6
Document Data Lineage

Track how data flows from source to destination. Document every transformation rule and business logic applied.

What to do:
  • Lineage List: Browse all 10 lineage mappings with source→target details
  • Lineage Graph: See a visual flow diagram of data movement
  • Review transformation types (DIRECT, TRANSFORM, LOOKUP, AGGREGATION, etc.)
  • Check transformation logic (SQL rules, business formulas)
  • Verify CDE lineage is complete and documented
Impact Analysis Lineage also enables impact analysis. If a column in Core Banking changes, you can trace forward to see every downstream system, report, and KPI affected. This prevents "surprise breakages" in production.
7
Review & Approve
Approval Inbox

All terms go through a formal dual-approval workflow to ensure quality and accountability.

What to do:
  • Check the Approval Inbox for pending items (badge shows count)
  • Review term definitions, classifications, and metadata mappings
  • Approve or reject with comments
  • Track approval history for audit purposes
  • Only APPROVED terms are considered "official" in the glossary
Dual Approval First, a Data Steward reviews the term (checks accuracy, completeness). Then, a Data Owner gives final approval (checks business relevance, authority). This two-step process ensures quality from both technical and business perspectives.

Additional Features

Taxonomy
Visual hierarchy of domains, subject areas, and terms

See how all your governance entities relate in a tree structure. Expand domains to see subject areas, and subject areas to see terms.

View Taxonomy
Upload Data
Import metadata from CSV/Excel files

Bulk-import business terms, metadata definitions, or data from your own systems. The upload wizard validates and previews data before importing.

Upload Data
Analytics & Dashboard
Governance metrics and KPIs

Monitor governance program health: term coverage by domain, approval rates, classification distribution, CDE verification progress, and trend analytics.

Audit Log
Complete trail of all actions

Every action in the platform is logged: term creation, edits, approvals, classification changes. Essential for regulatory audits and compliance reviews.

View Audit Log
AI Assistant
Chat with an AI expert on data governance

Ask questions about data governance concepts, best practices, compliance requirements, or get help with platform features. Supports Claude, OpenAI, and Azure OpenAI.

Users & Roles
Manage platform access and permissions

Configure users with roles: Admin, Data Owner, Data Steward, Data Custodian, and Viewer. 10 sample users are pre-loaded across departments.

Manage Users
Quick Tips
Global Search
Use the search bar in the top nav to quickly find any term by name. Press Enter to search across the entire glossary.
CDE Quick Filter
In Browse Terms, check the "CDEs Only" filter to see just the critical data elements. Great for regulatory reviews.
AI Everywhere
When creating a term, click "AI Suggest" to auto-generate definitions. The AI understands banking context — KYC, AML, PCI-DSS, BCBS 239.
Bulk Import
Have hundreds of terms? Use the Upload feature to import from CSV or Excel. The platform validates data before importing.
Visual Lineage
The Lineage Graph provides an interactive visual map. Click nodes to see details. Great for presentations to stakeholders.
Approval Badge
The sidebar shows a count badge next to Approval Inbox when items are waiting. Check it regularly if you're a Data Steward or Owner.
Need to Review Concepts?

Go back to the educational content about data governance fundamentals.

Data Governance Concepts