Collibra Integration
LeanIX Collibra integration enhances data governance by aligning enterprise and data architecture. With increased transparency and accessibility, stakeholders can make informed decisions on data management and compliance.
Overview
Collibra EDC (Enterprise Data Catalog) is a data catalog platform and tool that helps organizations better understand and govern their data assets. LeanIX Collibra integration enhances data governance by ensuring alignment and synergy between enterprise architecture and data architecture. With accurate and real-time data, you can make informed decisions regarding data management, application rationalization, technology investments, and compliance initiatives. This integration provides insights into the impact of data policies, regulations, and standards on IT architecture.
This guide provides a comprehensive overview of the integration's benefits, details on what data is synchronized between Collibra and LeanIX, activation instructions, and instructions on how to sync data from Collibra to LeanIX and vice versa.
Benefits
Some of the benefits of Collibra integration include:
- Increased Data Transparency: Collibra integration offers clarity on where the data is mastered and how it flows within the IT landscape, helping stakeholders to identify data dependencies, optimize data flows, and ensure data integrity and security throughout its lifecycle.
- Enhanced Data Accountability: The integration automates the mapping of data owners from Collibra to LeanIX, ensuring clear ownership and improved accountability.
- Expanded Data Accessibility: Enables you to leverage data across the enterprise while facilitating sound data governance practices.
Scope of Integration: Data Synchronization Between Collibra and LeanIX
Collibra EDC (Enterprise Data Catalog) application gives a comprehensive overview of the metadata / all data assets in the organization, making it convenient for users to find, describe, govern, and manage data.
Scope of LeanIX Collibra Integration
LeanIX Collibra integration provides the following:
- Synchronize conceptual data layer from Collibra Data Catalog to data object fact sheets in LeanIX. To learn more, see Conceptual Data Layer Mapping from Collibra to LeanIX.
- Synchronize names, data hierarchies, categories, descriptions, and relations between Data Assets into LeanIX, facilitating analysis of data usage and data management down to the application and interface level.
- Map responsible owners of the data assets from Collibra to subscriptions in LeanIX.
- Map application fact sheets from LeanIX to Technology Assets in Collibra Data Catalog. To learn more, see Fact Sheet Mapping from LeanIX to Collibra.
- Map business capability fact sheets from LeanIX to Business Assets in Collibra Data Catalog. To learn more, see Fact Sheet Mapping from LeanIX to Collibra.
- Map interface fact sheets from LeanIX to Technology Assets in Collibra Data Catalog. To learn more, see Fact Sheet Mapping from LeanIX to Collibra.
- Map relations between data objects, applications, business capabilities, and interface fact sheets to relations between assets in Collibra. To learn more, see Relation Mapping from LeanIX to Collibra.
Best Practices and Essential Concepts
Aligning on single sources of truth and fostering collaboration between data governance and enterprise architecture teams are crucial for a successful integration of SAP LeanIX and Collibra. Follow these best practices and understand the essential concepts to ensure effective collaboration between data governance and enterprise architecture teams.
Define the Sync Scope
To start with, define the sync scope by identifying which data is most meaningful for you as an Enterprise Architect or for your data governance colleagues. Consider the following questions to begin the discussion:
- What conceptual data is used by which applications and to what extent?
- How does data flow through the application landscape?
- Who owns the data?
- What technical assets exist in our data architecture?
Establish Clear Sources of Truth
Acknowledge that Collibra is the single source of truth for all data, while SAP LeanIX is the single source of truth for applications, business capabilities, interfaces, and their relationships to data objects. This alignment from the outset avoides discussions in the future over where to establish relationships between data objects and applications. Since LeanIX is the source of truth for applications, the associations to data objects should also be maintained there. This ensures that any changes in the application landscape are reflected in the data objects and synced back to Collibra, keeping both systems up to date.
Focus on the Conceptual Data Layer
To effectively manage and integrate your data, it's important to understand the different data layers within Collibra :
- Conceptual Data Layer: This layer represents the highest data level, such as data domains and data concepts (e.g., Customer, Employee, Prospect, etc.)
- Logical Data Layer: Data entities and data attributes (e.g., The customer lives in a street with a zip code).
- Physical Data Layer: Schemas, tables, columns (e.g., the specific database and column for customer addresses).
Different Data Layers
Image source: Collibra Documentation.
Focus on gaining visibility into Collibra’s conceptual data layer, as this is most meaningful for enterprise architecture management. This primarily involves syncing business assets and their subcategories—data domains and data concepts—into LeanIX.
Note
Avoid syncing everything to LeanIX, as it swamps your inventory and does not help answer questions of value for your Enterprise Architecture team. Focus on aligning and analyzing only the data that adds value to your objectives while Collibra remains the source of truth for data.
Create A Dedicated User Account for Integration
You need an admin role in SAP LeanIX for setting up the configuration, as well as in Collibra. On the Collibra side, as a best practice, ensure the integration is linked to a dedicated user account specifically created for this purpose with greater permissions than a regular user account. This also ensures proper access management and continuity. For a detailed guide on configuration, see Configuring Collibra Integration.
Establish Clear Responsibilities and Collaboration
The integration assumes Collibra is the system of record for assets, while SAP LeanIX is the system of record for applications, business capabilities, interfaces, and their relationships. This assumption guides your integration journey, especially in discussions with data governance teams.
A common understanding is crucial to avoid discrepancies and manual corrections. For example, while you can establish relationships between assets and applications in both Collibra and SAP LeanIX, LeanIX is the primary tool for managing the application landscape. If these relationships are maintained in Collibra, chances are high that changes might go unnoticed when the landscape evolves.
Strengthen collaboration between application owners and data stewards/guardians. No matter who drives the initiative of modeling the relationship between application and data objects, discussions on data privacy categorization, sensitivity, and usage should be a collaborative process. Use collaboration features in LeanIX, such as surveys for data collection and comments for resolving discrepancies. Additionally, establish quarterly or semi-annual check-ins to ensure data accuracy and updates using quality seals. To learn more, see Collaboration.
Key Concepts and Their Mapping
The following are some terms and their definitions that help Enterprise architects understand Collibra’s operating model:
Source of the table: Collibra Documentation.
| Collibra Term | Description | Representation in LeanIX |
|---|---|---|
| Community | A community is a grouping of subcommunities and domains. It often corresponds to functional divisions in a company and works best if it is aligned with the company's governance organization. | Can be synced as a data object with a parent-child relation with its respective domains. |
| Domain | A domain is a logical grouping of assets that belongs to exactly one community. Its domain type specifies which asset types can be created in the domain. | Can be synced as a data object with a parent community and the underlying assets as parent-child relations. |
| Asset/Asset Types | An asset is the fundamental building block or resource for which you want to capture information. An asset belongs to exactly one domain and has a unique name within that domain. An asset is the instance of exactly one asset type (e.g., Business asset, data asset, governance asset, issue, technology asset). To learn more, see Overview of Packaged Asset Types. | Assets are imported from Collibra into LeanIX as data objects. Currently, the integration supports two asset types: business assets and data assets. Business assets are particularly relevant for this integration. |
| Attribute | An attribute is a specific piece of information that captures information about an asset. One asset can contain many attributes. | Synced as fields, such as name or description. |
| Relation | A relation is a link between exactly two assets. It captures how two assets are related to each other. One asset can have many relations. A relation is the instance of exactly one relation type. | 'Groups' relations from Collibra are represented as relations between data objects. |
Recommended Workflow for SAP LeanIX and Collibra Integration
- Sync conceptual business assets to SAP LeanIX.
- Create the relations to applications in LeanIX using interface fact sheets.
- Enrich the data object with data classification, application usage, and data privacy categorization.
- Sync applications, interfaces, business capabilities and respective relations to Collibra.
Recommended Workflow for SAP LeanIX and Collibra Integration
Key assumptions made here:
- Conceptual business assets are managed in Collibra
- Applications, interfaces, business capabilities, and all inherent relations are managed in SAP
LeanIX
Updated 5 days ago