The main use case for Collibra Lineage is focused on the data product integration. They want the data lineage, data product lineage, and data products. They have some AWS platform in their state, and they have implemented external layers on top of that, including iceberg tables. The data lineage and delta are used to write a model with data products in Snowflake. In the Snowflake layer, they have their reporting in Tableau.

They have implemented a model with data products in Snowflake, which helps them in reporting in Tableau.

The features of Collibra Lineage that I have found most valuable include its non-integrated, non-native nature, which is one of the unique features for customization. In my case, data engineers have created their approach with Snowflake. By using a customized approach, they develop simple solutions and integrate with Collibra. A custom lineage, technical lineage helps me to design or join all these multiple layers. For example, connecting three Oracle instances to AWS is not available out-of-the-box, so there is a function to customize.

The main benefits that Collibra Lineage provides include measurable advantages. Once I have Lineage implemented, I can implement any automation on top of that. When I classify the D's on the data product, I can transform that data word to all the related columns using automation and workflow. This functionality avoids needing to do everything manually, and business only has to handle it at one layer, which is the data product. The lineage connects backward, allowing me to push back all these D's across all connected columns and registers. It's useful for the technical team to understand how all the data businesses seem different.

When discussing potential areas of improvement for Collibra Lineage, there are several cases to consider. If we discuss Lineage, which is the major part I work with, solutions are implemented in PySpark, and Collibra does not have out-of-the-box features for that. If a developer implements ETL in Glue or PySpark, Collibra cannot capture lineage out of that. This is an area for improvement, alongside integration with Starburst, which is another area where lineage capability is lacking.

I have been working with Collibra Lineage for five years.

I rate the stability of Collibra Lineage as seven. This is a fair assessment compared to alternative tools such as IBM Cloud Pak for Data, which I've also worked with.

In terms of scalability, Collibra Lineage's performance is reliable, as the lineage harvest runs on the lineage server which operates on Collibra cloud. I have not faced any issues concerning scalability. Despite earlier concerns when it took eight hours for one data job, recent improvements have reduced this time to three to four hours, though it still depends on metadata volume.

For technical support, I would rate it as eight because with premium support, the service is excellent.

The initial setup of Collibra Lineage is very simple nowadays. You can drag lineage from the UI by selecting and dropping whatever configuration you want. For configuring Lineage capability for Snowflake, there are multiple options available. It's particularly efficient since last year when they moved lineage to UI.

I have not used data flow mapping with Collibra Lineage. I question the helpfulness of visualization features for Collibra, particularly lineage visualization.

I agree with the assessment that lineage visualization in Collibra is valuable.

Overall rating: 7 out of 10.

My domain is master data management. In master data management, basic data quality, lineages, rule profilings, and similar processes come under Collibra profiling. I use it for these purposes.

I find the rule modification and the replication of the rules in Collibra happens very quickly. This is one of the aspects I appreciate the most. Additionally, the data lineage and catalog features have improved significantly over the years. While they were not perfect three years ago, they are much more mature now and continue to grow each year.

The domain-based approach could be more helpful for aspects such as customer 360 and product 360. Moving towards this could create significant value.

I have been working with Collibra for approximately four years.

I would rate the stability as eight out of ten.

I rate scalability a six out of ten. There is some room for improvement in terms of scalability.

I rate the technical support from Collibra as nine out of ten.

The setup is very simple.

The price is average, and it provides good value for the money.

The main competitors on the market that I consider are SAP and Informatica.

Overall, I would rate Collibra Governance as a seven out of ten. I can recommend it to other users for sure.

We are a customer of Collibra. Collibra Governance is applied in our data management workflows by creating all the business functions separately, maintaining the data sources of those KPIs and everything separately on those businesses.

Collibra Governance provides ease of use. The portal is self-explanatory with lots of documentation on its usage, making implementation and understanding simple for our team.

The most important feature is the ease of use. The portal is very self-explanatory and robust. The tool also provides integration with a lot of sources.

There should be more detailed documentation on the selectors and certain information, and a reduction in cost as compared to other tools. The data marketplace solution could be more flexible in filtering capabilities. Additionally, their responsive time in technical support can be quicker.

I have been working with Collibra Governance for almost two years.

The solution is stable, and I would rate it as a seven out fo ten.

On a scale of one to ten, the scalability of the solution is around seven or eight out of ten.

Technical support is effective in providing solutions. That said, their response time can be improved. I would rate it around five or six out of ten.

We have not used another solution till now but are considering others, especially due to cost.

It is mostly straightforward, especially if you have the infrastructure ready.

I wish the tool could be less expensive compared to other tools.

We are looking into Purview due to costs and features differences.

The tool is intuitive, easy to learn, and would be better if the costs were reduced.

I'd rate the solution seven out of ten.

The primary use case for the solution is the governance of data dictionaries. It is useful for managing and classifying data on a large scale.

The product has significantly improved data governance by providing a centralized platform for managing data assets and ensuring consistent definitions. It has led to better data quality and more efficient compliance with regulatory requirements.

The product's most valuable features are cataloging and classification.

They could simplify the platform's setup and design process. It requires significant IT involvement and expertise, which can be a barrier for smaller organizations.

We have been using Collibra Governance for approximately five years.

The product is stable and reliable. I rate the stability an eight.

The product is scalable, but the extent to which it scales effectively depends on how well it is designed and implemented.

I rate the scalability an eight.

The product's pricing is high, which its comprehensive features and capabilities may justify. However, the cost can be a consideration for smaller organizations or those with limited budgets.

As a data governance advisor, I evaluate various solutions based on their fit for the client's requirements. While I recommend this solution when it meets the organization's needs, there are more than one-size-fits-all solutions.

Integration with it can vary based on the client's IT landscape. For some organizations, integration is straightforward, while for others, it can be quite complex.

Its user interface is generally user-friendly, but it could benefit from some enhancements to improve ease of navigation and customization. While functional, a more intuitive design could help users operate the platform more efficiently.

Its performance can vary depending on how well it is configured and the scale at which it is deployed.

It has strong data privacy and security features, including robust encryption and access controls. It is designed to comply with various data protection regulations, crucial for maintaining data security.

It offers extensive customization, allowing tailored configurations to meet specific organizational needs. However, achieving this level of customization often requires considerable time and technical expertise.

It has strong user adoption and satisfaction due to its comprehensive features and capabilities. However, user experiences can vary based on the organization's specific needs and the solution's implementation.

I rate it a seven out of ten.

We have a full-time user interface in-house.

The solution makes data more discoverable and transparent.

We can easily connect to sources. It is like plug-and-play.

The workflow documentation must be improved. It is our number one pain point.

I have been using the solution for six to seven years.

The customer service is bad. It is not the best. I rate support two or three out of ten. The support team must be communicative and stay in touch with the customers.

The core functionality is good. The initial setup becomes challenging if there are any vulnerabilities or changes because not much documentation is available.

I am using the tool because my current organization decided to use it. My previous organization used a more enhanced tool. There are other tools with better functionalities. Overall, I rate the tool a six out of ten.

We use the solution's Data Stewardship part. We tried to explore the policy management piece, but we were unable to get through it. We haven't worked excessively on that. It was just some POCs or MVPs, but this is something that we would like to explore in the future. This is something that will be our future requirement in six to seven months down the line.

We use the solution's Data Stewardship part.

We are not able to ingest all the data in Collibra, and that's why we cannot do element-to-element level data tracking.

I have been using Collibra Governance for two years.

I rate the solution's initial setup as medium because it's not very difficult. We have to look at a few nuances from the infrastructure and performance perspectives. We have to consider whether we would have the leverage capabilities for that. So, all these things need to be considered from the engineering side.

Collibra Governance is an expensive solution.

Our current focus is more on the solution's stewardship, cataloging, and reference data features. The one feature of Collibra Governance we would like to explore is the automated tagging of PII data. We do deal with such kinds of data within our organization. It would be helpful if there were any videos available for us to go through because this is something that will help us in the near future.

We are not extensively using the solution's data lineage functionality because we are simply building over it. The only challenge for us is from the connective side. We are not able to ingest all the data in Collibra, and that's why we cannot do element-to-element level data tracking.

The major Broadlock would be the integration piece. If that is done, we'll be able to have all our data in the Collibra. The data lineage functionality is a really good feature, and we would really love to leverage it. The challenge is that the connectors are not available in the pipeline.

Collibra Governance is deployed on the cloud in our organization.

Overall, I rate the solution a seven out of ten.

Collibra Governance is a stable solution.

The solution's data lineage is a little difficult and will not support all the source systems on the database.

I have been working with Collibra Governance since last year.

Collibra Governance is a scalable solution.

Collibra Governance's documentation is clear. We can get all the documents from Collibra University.

Collibra Governance's initial setup is complex.

It takes more than 15 to 20 days to deploy Collibra Governance.

Collibra Governance is an expensive solution.

Collibra Governance is a good tool that has some pros and cons.

Overall, I rate Collibra Governance a seven out of ten.