OpenMetadata Integration Overview

This section describes how to integrate the Triodian Metamodel with OpenMetadata, enabling organizations to bridge business architecture with data platform governance.

Why Integrate?

The Gap Between Business and Data

Organizations often face a disconnect:

Business Architecture	Data Platform
Capabilities, value streams, stakeholders	Tables, pipelines, dashboards
Strategic objectives and KPIs	Data quality metrics
Business policies and governance	Technical governance rules
Organizational accountability	Data ownership and stewardship

This disconnect leads to:

• Data assets without business context
• Business decisions without data visibility
• Governance policies that don't reach data platforms
• Accountability gaps between business and technical teams

Integration Benefits

Benefit	Description
Business context for data	Every data asset linked to business capabilities
Unified governance	Business policies enforced in data platforms
Traceability	End-to-end lineage from strategy to data
Accountability	Clear ownership from business to technical layers
Impact analysis	Understand business impact of data changes

Integration Architecture

OpenMetadata Concepts

For those new to OpenMetadata, here are the key concepts:

OpenMetadata Concept	Description	Triodian Equivalent
Table	Database table or view	Information component
Topic	Message queue or event stream	Information (messaging)
Dashboard	Visualization or report	Performance indicator
Pipeline	Data workflow or DAG	Value stream (data flow)
ML Model	Machine learning model	Technology component
Data Product	Packaged data offering	Products domain
Glossary Term	Business definition	Domain entity definitions
Tag	Classification label	Domain attributes
Policy	Governance rule	Policy domain
Owner	Accountable person	Stakeholder
Domain (OM)	Organizational grouping	Organization domain

Integration Approaches

Approach 1: Custom Properties

Add Triodian context to OpenMetadata entities using custom properties:

{
  "customProperties": {
    "businessCapability": "CAP-CRM-001",
    "valueStream": "VS-CUSTOMER-ONBOARDING",
    "businessOwner": "STK-RETAIL-HEAD",
    "strategicAlignment": "Digital-first customer acquisition"
  }
}

Pros: Non-invasive, works with existing OpenMetadata setup Cons: Requires manual or scheduled synchronization

Approach 2: Glossary Integration

Use OpenMetadata glossary to embed Triodian terminology:

{
  "glossaryTerm": {
    "name": "Customer Onboarding Capability",
    "description": "Capability to register and verify new customers",
    "relatedTerms": ["CAP-CRM-001"],
    "tags": ["business-capability", "customer-domain"]
  }
}

Pros: Native OpenMetadata feature, supports relationships Cons: Limited to terminology mapping

Approach 3: Full API Integration

Bi-directional synchronization via OpenMetadata and Triodian APIs:

Pros: Real-time, bi-directional, comprehensive Cons: Requires development effort

Getting Started

Prerequisites

• OpenMetadata instance (v1.0+ recommended)
• Triodian Metamodel data (JSON format)
• API access to both platforms

Quick Start Path

1. Map entities — Define how Triodian domains map to OpenMetadata entities
2. Export glossary — Create OpenMetadata glossary from Triodian terminology
3. Add custom properties — Define custom property schemas in OpenMetadata
4. Populate context — Add business context to key data assets
5. Automate sync — Build or configure synchronization process

Recommended Sequence

Phase	Activities	Effort
Phase 1	Glossary import, manual custom properties	1-2 weeks
Phase 2	Automated custom property sync	2-4 weeks
Phase 3	Bi-directional integration	4-8 weeks

Section Contents

This integration section includes:

Page	Description
Entity Mapping	Detailed mapping between Triodian and OpenMetadata entities
Use Cases	Five practical integration scenarios
Terminology Bridge	Business architecture to data platform vocabulary
API Patterns	Code examples for integration implementation

Related Documentation

• Information Domain — Triodian's information modeling
• Stakeholder Domain — Business ownership and accountability
• Policy Domain — Governance policy modeling
• Performance Domain — KPIs and metrics