Data Products Configuration in Collibra Data Intelligence Cloud

Data Products in Collibra provide a structured way to package, govern, and share data so business and technical users can discover and consume it.

Tagged in:

Data Governance

Steve

Novak

Vice President

View bio

In the context of data mesh, "data products" refer to self-serve, domain-oriented data assets that encapsulate a specific business capability. The concept of data mesh, popularized by Zhamak Dehghani, emphasizes decentralizing data ownership and treating data as a product.

By adopting the principles of data mesh, organizations aim to overcome challenges related to data silos, centralization, and scalability, ultimately improving the agility and effectiveness of their data capabilities.

5 steps to configure Data Products in Collibra

Define Data Products

A business intelligence report may be classified as a data product. Figure 1 shows a PowerBI-based Inflation report in Collibra. The report also includes a custom attribute for the value that has been assigned to the report.

‍

Develop Derived Data Products

Derived data products are based on one or more data products. For example, a bank has an Office of the Comptroller of the Currency (OCC) Compliance data product, which is derived from the Report Certification data product, which is derived from several report data products including Inflation (see Figure 2).

Figure 2: Banking data products relating to OCC compliance and report certification

‍

Establish Data Quality Scores for Data Products

The data quality score from Collibra OwlDQ may be appended as a custom attribute to the data product. For example, the data quality index for the Customer Master data product is 80 percent (see Figure 3).

Figure 3: Customer Master data product has a data quality score of 80 percent

‍

Agree on Data Privacy Rules for Data Products

Data products need to be constrained by data privacy rules. For example, the Chat Log data product is constrained by a rule that highly confidential data such as Social Security Number must be masked before usage for analytics (see Figure 4).

Figure 4: Privacy rule for chat log data product

‍

Create Customer-Specific Contractual Rules for Data Products

Data products also need to be constrained by contractual rules that are specific to customers. For example, an investment manager may have customer contracts that permit differing levels of data usage. The investment manager’s contracts with IBM and Honeywell only permit usage of 401(k) participant data within the app. However, the contract with Information Asset does not have any such usage restrictions (see Figure 5).

Figure 5: Mapping of data products to privacy and contractual rules

Other articles

Foundation First: The Root Cause and the Path Forward

Data Governance

Best Practices

Data Value Realization

Part 2 of The Three Failures That Will Define Who Survives AI. Why treating data as a technology concern instead of its own strategic pillar is the root cause, and what Foundation First looks like in practice.

The Three Failures That Will Define Who Survives AI

Data Governance

Best Practices

Data Value Realization

Over 80% of AI projects fail to reach production. The problem is not the technology. Three predictable failure modes are turning enterprise AI into the most expensive technology failure in corporate history.

The Model Isn’t the Problem

Data Governance

Best Practices

Healthcare AI pilots stall before reaching production. The model is rarely the issue. The gap between training data and production data is what breaks deployment.

Client testimonial