Collibra Governance Reviews

We're a very large pharmaceutical organization so it's difficult to quantify exactly how many users are using Collibra.

Within our organization, there is a data governance team that we had set up. I am the person in charge of that team. While working on the data governance processes, we thought of leveraging Collibra for things like data dictionaries, developing data lineage, ensuring that business artifacts like KPI catalogs and board catalogs can be built within Collibra itself. 

This solution has done a lot for our organization and the trust amongst the data that we've been using has definitely improved. Earlier, these things were happening in silos, there were people who were doing manual documentation. Now, things are centrally available on Collibra, so it is more of a centralized platform. People are now able to track what is happening in the background of the data that they are using. Essentially, it has provided us with more trust and transparency — this is the real benefit that we've got out of Collibra.

Also, connecting the dots — things that used to be done in silos, now we have a centralized platform. Every team is aligned with what others are doing. It is not as if I am reporting a KPI, which has an "A" definition and somebody else is reporting a KPI with a "B" definition. When things are consolidated from a country level or a regional level and you're trying to present it to the leadership team, then there is a different picture to it. You're not using consistent calculations and definitions. This ability has been really effective for our organization.

It's a one-stop solution for all of our queries related to data that we are leveraging for our reporting. Pharma is totally dependent on what people are turning out as a report and what analysis or analytics they can derive out of it. From there, leadership accordingly makes a decision. It gives us more confidence in having a go-to platform that acts as a one-stop-shop solution for all of our queries.

Due to technological advancement and data becoming more critical for all reporting and analytics purposes, we are no longer restricted to primitive tools like Excel, etc. Earlier, we were leveraging these tools because we used to source data directly from data sources, but now, things have moved to the Azure platform and we have much more freedom in the cloud.

It's now really important for technical people to have some kind of lineage for these data sources because currently, we are not just leveraging data from the source and reporting it somewhere. We have thousands of reports with some transformation that occurs in between. Data is moving from one layer to another — all types, including raw, curated, and rich.

When our technical team works on it and our business demands new modifications, it becomes difficult for them to track that lineage and what impact it's going to have on the upstream and downstream system. This is one functionality of Collibra that we have leveraged extensively. 

We are in the process of migrating all our data sources towards the data lake — some has already been done and more is on the way. We want to connect all of our reports, which are either based on ClickView, Tableau, or PBA, directly to Collibra, as our data platform. If a business user wants to track down a KPI in a report to the rawest data from which we are sourcing it, there are a number of layers and transformations happening in between.

It is important for business users to track what is happening in the background. Are we leveraging the right thing? Are we applying the right kind of transformation or the right business-logic to arrive at a certain KPI? At the same time, the IT team needs to be able to know what kind of lineages there are. For example, If I make a change to one of these things, what impact will it have on the backend? This is one of the powerful functions of Collibra which we as an organization think is really useful — as an organization, we have been reaping the benefits thanks to this solution.

I am a business person — I am a team leader. My duty is to ensure that the data governance processes are set up; that's how I started to use Collibra. There are certain limitations I have observed in Collibra. With regards to our data lake, Collibra doesn't give us direct connectivity to the Azure Data Lake. We have to establish data lineages. We have to browse those files manually and then connect them via Collibra — that's how data dictionaries get published. Overall, it's quite a manual type of process which needs a lot of human intervention.

I've been hearing that tools like Talent are going to be available soon, which we hope to leverage in the near future. Talent is similar to other ETL or Informatica-type tools. It directly connects to the source system, captures all the transformation tools, and provides you with a spreadsheet that talks about data lineage, which can be fed into Collibra. If this functionality could be improved, it would be a great time-saving solution. It would require less effort and it would be a more automated kind of system, less dependent on human operation, which means that it would be less prone to errors as well.

We create and issue the management of workflows with Collibra. In regards to workflows, I find that they can be made very simple. For example, a request goes directly to the person who is in charge of that particular asset and some simpler workflows can be assigned to it. Recently, I find that the default process of issue management in Collibra is really complex — It wasn't really helpful to us.

I have been using Collibra Governance for one and a half years.

If deployed correctly and leveraged properly by the people, if the commercialization of the product within your organization, post-deployment, is good and you're able to transfer that value to people, then this solution definitely has huge power. In terms of data governance, as I mentioned, it can be a one-stop solution for all of your data governance needs. 

If commercialization, onboarding, and value from Collibra are conveyed properly to the teams, then definitely it's a powerful data governance tool.

No. Things were happening in silos. Everybody had their own way of doing data governance. There wasn't any connection or central platform to do that. Everybody was using their own method, platform, files, etc.

We have one person from our leadership team who has experience in data governance — 20 years of experience. Similarly, we had certain technical team members as well. The initial setup was a collaborative effort. Overall, I found the process to be a little complex. 

You actually need to get into a lot of theory to be able to understand the backend of Collibra and then be in a position to be able to implement it. Initially, it's a little complex but now that I've spent one and a half years working on it, I find it a little easier, but at the time of initiation, we found it to be a little complex.

Deployment took us roughly nine to ten months. 

Our data governance lead oversaw the initial deployment. In my team, there were around five team members who were supporting us through deployment. There were two technical members from the same organization that I worked for who were actually involved in the technical assessment. Then there were onshore business people, too. This was all new to our company — we just made decisions and then we started to go ahead with them. 

There was one expert from Collibra that our organization has partnered with because it was a new thing for us. That person actually acted as a guide and mentor, leading workshops and assessments — showing us what should go into Collibra. In a nutshell, these were all the people who were involved.

From a technical perspective, maintenance is required after deployment. We have a dedicated team who looks after this, we don't have to do anything. From an operation perspective, for the maintenance of the asset, you have to ensure that your information is real-time and updated on a regular basis. You cannot just feed this information once and then never look at it — in the data world, things keep on changing. You need to ensure that those dynamics are being catered to. From an operational perspective, yes, there are monthly processes in place that are there to ensure that whatever we have posted on Collibra is up to date and relevant.

From a technical perspective, I cannot contribute much because there is a dedicated team that makes all of the decisions. If we are upgrading Collibra, they are the ones who get the notification, they work with the team and then they agree on the next steps and then we just get notified that new features are going to be available. 

I was not involved in the licensing of this solution. 

We evaluated the pros and cons of another tool (I forget the name of it). From a forward-looking approach and long-term perspective, I think Collibra is far more powerful than the other tool.

Before you deploy or implement Collibra, just ensure that you have certain use cases that really qualify for leveraging Collibra. Assessment and evaluation are really important, first. Benefit analysis is the most important key.

What are the transformational changes that Collibra is going to bring? If it's going to improve your ROI by deploying it, then migrate over to it; just don't do it because everyone else is doing it — that's not a good enough reason. 

There are certain tools out there that can analyze data and generate reports with a few simple clicks. Collibra doesn't work like that until you have the ground knowledge of the metamodel — how the backend works and how your assets should be categorized. You cannot expect to directly deploy Collibra. You need certain experts in that area who do extensive research and understand the backend of Collibra, only then can you proceed with it. Once you are pro with it, it becomes much easier, but initially, it does require some research and hard work.

From what I have leveraged out of Collibra thus far, on a scale from one to ten, I would give it a rating of seven.

The main use case for our organization was to collect and collate information for our business users, such as definitions, business rules, etc. 

The customers' names were stored in a data warehouse on Oracle, and with this product, you could insert information related to the customer. You could use Excel, for example, to add in data. You'd have all the information you collected from other places on one tool that users could navigate across to see all of the information.

One of the projects that we had with a client, was to collect and add all the information related to the HR functions. We collected technical information and data quality checks and so on. We inserted this information into Collibra. Once we did that, the user could enter in and read the collected information. That way, they didn't have to go to IT to pull queries for them. They were empowered to do it themselves. This solution basically reduced the search time. They no longer had to go to IT to open a ticket, or to go to an external supplier to recreate some already captured information.

The solution is very user-friendly, especially in comparison to other tools. 

Even a business user, which no technical competencies can manage this product rather easily. 

There are great workflows and other features that really simplify various aspects of the product.

The log information is easy to navigate.

The customization and the dashboards are pretty good.

Collibra, as far as I know, does not have a connector like Oracle, or a mainframe. It's important to have a connector so that you have access to up-to-date information. Sometimes the data can be out-of-date as the updates are not automatic. Users could be looking at obsolete information.

You need to be precise about the names of the field and you have to develop them yourself.

It's my understanding that they are working on a solution where you can import all the information that you need from a data validation too, or from a CRM. It's something they really need to get better at.

It would be better if there was a way to import all data and metadata in an automatic way in one block form.

I used the solution for one year.

The stability was very good. We never struggled with any downtime at all.

I'm not sure if the solution is scalable. I never really tested it. We only really handled a few areas of the data log analysis. For three functional areas it seemed to be pretty good, however, I couldn't say for sure if that would be the case if there was six or ten functional areas.

I've been in touch with technical support in the past and I found them to be quite helpful and knowledgeable. I've been satisfied with the assistance I've received.

I previously used Informatica as a data governance solution.

Informatica is better from a technical point of view. For example, in Informatica, you can buy these connectors which are very complete. You can import a lot of information from tables, names, matrices, and so on, from, for example, Data Visualization Tool, from Qlik, Tableau, from everything. You do not have to write code either in order to develop an API or to upgrade connectors by yourself. In Collibra, there are connectors, however, you have to upgrade them, if you, for example, need more information, more metadata, and so on. It's just not as easy. Informatica is more mature from a technical point of view. You get a complete data lineage and can see the data life cycle of all of your metadata.

The initial setup was not so complex. It was pretty straightforward. Collibra has, for example, workflows and other features that help you to import information. It's all very simple to understand and to use. You sort-of knew what to do from the outset and setting everything up was pretty easy as you just followed along.

The deployment doesn't take long. It's a matter of days or maybe weeks. It certainly doesn't take months.

I started the initial phase with the development of all the information. We got the metadata that we needed from the business user. Then we added the information to the data model. The data model related to Collibra was done by the Collibra administrator. We added this information to the data model. After that, we deployed everything by exporting metadata that we inserted into an Excel format, and then we deployed this information to the production environment by loading the Excel details into the new environment. 

I was never the administrator of the solution, and therefore, I don't know too much about ongoing maintenance and what might be involved with that. I do not believe there to be a lot of technical maintenance needed.

I handled the deployment myself. I didn't need the assistance of an integrator or consultant.

If you compare the solution to Informatica, it is much cheaper.

The licensing for this product is on a yearly basis and you have to pay for the type of users that access the platform. For example, if you want to have a user in read access mode, you don't have to pay for them. 

However, if you want a write access user, for example, to insert information, to upload data, and so on, you have to pay for that license. Therefore there are two main charges. You have the license cost of the tool and the cost of the users that have write access. Beyond that, it's my understanding that there are no other costs.

We're just customers. We're end-users of the product.

If a company wants to implement a solution more focused on the business aspects, this solution works well. However, if a company needs to, for example, have a solution that covers a 360 overview of a data governance implementation or a project where you have to collect business information, and also need to connect that business information to technical information, to create a data lineage and so on, there are other solutions that cover this part better. That said, Collibra is really user-friendly. It's really easy to use. For a non-technical business user, it's easy to access, to navigate information, and so on. Typically business users don't want to have an interface or don't want to use technical tools, so a company should be mindful of that.

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

Collibra Governance reduces the time-consuming aspects of the process. You'll need only one-fifth of the team as it'll depend on two to three people, and that's really important to businesses.

I find the metadata feature valuable because it replaces the coding. The metadata creation happens via Collibra, and it reduces the code. 

We have an issue with metadata history. If someone changes the metadata, we can't see who changed it. But they are trying to upgrade the system with this feedback and are still working on it. We are still waiting for a proper log to maintain the solution.

I have been using Collibra Governance for the last four years.

I haven't found any limitations or obstacles with scalability. It completely depends on who is managing the solution. We have placed Java resources, and we didn't face any limitations with that. 

On a scale from one to ten, I would give their technical support a seven. 

This is because they still haven't completely provided the solutions we asked for. They're a new product and are lacking in some areas. They can provide 80 to 90%, they have fixed some things in the public sector, but there are some gaps. 

If you're going to start a completely new project, the deployment takes at least six months. But if you're looking to establish particular effective information governance or something like that, it could take maybe 10 to 20 days.

We have had a return on our investment because we don't use the same manpower that we used to for the code.

Before using Collibra Governance for metadata development, you need a business analyst with extensive domain expertise. Collibra Governance is just a metadata creator. You need business knowledge to understand how you're going to create the metadata and how it will link with your business applications.

Collibra Governance isn't the only part where you're going to develop everything. Collibra plays a major role, but you still have to add other components. For example, you need Java resources, Oracle and you need to integrate all this stuff into the Collibra before making the project list.

It demands a high level of visibility. The technology component idea, database knowledge, and more should be made available to a select group of people. If that's not there and everyone is new, and you're using Collibra Governance for the first time, you're going to have many problems.

The teams should have proper knowledge of background modeling, and they should have proper knowledge of the existing business. If they're creating a completely new team and the new team doesn't have any business knowledge, expect project failure.

On a scale from one to ten, I would give Collibra Governance an eight.

We have a client that was planning to do a digital transformation. They came up with the use cases and they have a couple of departments. They are mainly based on legal systems including corporate trust, etc., that they want the data to govern. Their requirement was basically if any new person is hired, they would have everything in Collibra, including all of the business glossary or the tables or the reports. Basically, everything for their onboarding process was available there. It was also necessary to give that to anyone that wanted to know about their department.

We only just started with this project and have only started learning Collibra.

On the client-side right now, any onboarding or any seminars or any training they are conducting, they can just pull the data from Collibra and show it to anyone. Every single data source, we can connect with the Collibra and we can pull out any data. We can create our traceability diagrams or trace any connections, like end-to-end connections, and link the data to the report. Some will be encrypted data, however, we will know which is related to each business term.

We can create our own policies, and we can link with the data quality rules. Collibra can even provide some validation rules. If there is a business term that exists without a description, the validation result will show as false. It is pretty customizable and pretty user-friendly so far.

The most valuable feature of this solution is mainly on the report side. They have a couple of reports in finance and we can connect with Tableau or Power BI, or even SSDT. We have connected with Power BI and Tableau right now. Once we connect with the source, we can pull all the data, and we can create a hierarchy based on that, and then we can link each attribute in the report with the table name and the column name. After that, we can link it with the business terms as well. It's like an end-to-end flow. We can create even traceability diagrams, views inside the system.

The reporting is very good. The solution offers a good business glossary. The diagrams are also pretty easy to understand for everyone. We had to link with the IT department, which had some difficult workflows, and they want to automate everything. The solution can do that for them. It's still a work in progress, however.

The solution is quite customizable. If I took a business term account, I could link it with the table account, and then I could link it with the account ID, and then there'd be some account receivables report. Each attribute in this report account ID, I can link to and create a linked diagram. This can be shown to the business users. The business users need to see the glossary and the attributes and if we can link anything we can create relationships with the data. There are some out-of-the-box attributes, which are present in Collibra, however, in addition to that, we can also create our own any.

If you compare the solution to something like Axon, it's pretty user-friendly. Anyone can come and understand the tool very easily. Axon isn't as user-friendly compared to Collibra. 

It's not a complicated product. Collibra also has Collibra DG and Collibra Console, but in Informatica Axon, everything is all together. Everything, including the backup schedule and all these things, has another web application in order to maintain all that information. 

While connecting with the data source, it's not very easy. If there's a firewall, it is difficult to connect with the database. It's not easy when you are configuring on the database.

Right now, the client is decommissioning the MuleSoft integration and they're moving to APIs. Collibra Connect and MuleSoft integration were there before, however, now there's a move to API. Within a year or two, they will all move to API. Whoever is using it now with MuleSoft and Collibra Connect needs to find another way for connecting with the API. 

I don't think they are providing additional software for MuleSoft integration. Primarily, they are telling us, okay, we will decommission this and move to API. The only thing that's lacking in terms of the change is when connecting to database. Sometimes the connection causes issues if the data is breaking the firewall and ingesting the data.  

I'm currently using the solution. I've been working with the solution since March of 2020.

The stability has been good. We haven't had any complaints. It seems to be quite reliable. We've deployed into production and until now we haven't had any page loading issues or refresh issues.

We had around 100s of business users using collibra, we never faced any performance issue. And we had SSO configuration enabled for all users. Performance wise collibra is stable. 

The scalability is good. If a company needs to expand, they should be able to quite easily.

In terms of technical support, they have documentation from Collibra University. They have subcategories that you can search through. That can help with a lot of troublshooting.

However, if we are facing an issue in production, they will reply in a short span of time, usually within half an hour or 15 minutes. They will connect with us to resolve the issue.

If it is in our working environment, it will lag by four or five hours. They try to prioritize service and get to you as quickly as they can only in critical situations.

Our client has taken some Collibra hours as well. We can schedule some sessions with the Collibra team to learn the system. We have taken around 36 hours approximately and have utilized the service alongside purchasing the product.

While I've seen Axon, I haven't worked much with it. From the look and feel, and from my navigation, I find it's very difficult compared to Collibra, which seems to be rather straightforward.

I was involved in the initial setup and I did not find the implementation overly complex.

Once we started setting up the Collibra tool, they provided a pretty detailed user guide. Along with that, there are so many videos available in Collibra University, which is pretty self-explanatory. We just needed to go through that and understand it all. 

You will get all end-to-end details of what software can connect, what data sources it accepts, etc. Lately, they have changed a lot of the certification levels. Earlier, it was level one, level two, level three. Now, they changed in each area. There are certifications for solution architect, business analyst, workflow manager, etc.

We had three people from our organization that assisted with the initial setup. One person was the cloud administrator. He set up everything with the cloud. Another person was doing the console setup, it was a single sign-on, so he was adding all the AD directory. We had two environments, actually, one production and one dev. The third setting up the environments. In the console only, we needed to mainly set up all these things, add all the data sources, JDBC drivers, SSN configuration, email configuration, all these things needed to be done in the console. That was the primary setup.

Deployment took, in total, about two weeks. Post-deployment, there really isn't any maintenance necessary. We can schedule backup, either on a weekly or daily basis. Whatever changes we make, we can take to the backup. If we make a mistake the backup will be available to override it.

The client is pretty happy with the Collibra work so far. They have achieved their digital transformation goals for 2020 and therefore they were pretty satisfied with the tool. We can connect with IDQ or anything we need to. It's been a successful project.

There are two license types - author and consumer. The author has all of the rights. He can edit and catalog anything. The consumer has limited access. We have around 10,000 consumers and 40 author licenses.

Professional training costs are in addition to licensing costs.

The pricing is pretty high if you compare it to other governance tools. 

We didn't evaluate other options before choosing this product.

We are Collibra Partners. We have a business relationship with the organization.

If we have a Collibra expert on your team, it will be easy. Otherwise, new users should expect a bit of a learning curve. ANyone working closely with it should take some Collibra training alongside the product purchase. Professionals will help you and guide you in creating an organization level or department level unit with a glossary and everything. They can give you more insight. I'd also advise users to try to take the certification, which is free of cost in Collibra University, or try a partner training certification.

Overall, I would rate the solution eight out of ten.

Our primary use case of this product is for metadata information for our technology assets. We also use it for all the governance dictionaries, and for minutes as well.

The solution is very useful for IT people but it's also helpful for those not literate or knowledgeable in IT. The sales department, for example, can track where the information is coming from, where the transformation is happening and where they can find a report for any specific asset. It's very important for them to have it handy, and I believe that for the people who need to know that information, it's very good.

The diagram showing the limits is absolutely magnificent. It shows an end-to-end business term or any asset going from end-to-end. From a visual perspective on the diagram, it's simply beautiful.

The workflows and the language they use needs to be improved. Programming the needs for every user on the workflows is a key improvement that is required. In addition, they haven't updated their training solution in a while. We need to implement a lot of things ourselves and they want us to move to the cloud but there are a lot of glitches in the system. There are three environments - stage, development and production. Often things work well in the first two stages and then when you get to production, they don't work. It happens a lot and their response is slow. 

I've been using this solution for 18 months. 

I would say that stability is around 85%-90%. It's very stable compared to other solutions on the market. 

Scalability is very good, excellent. 

Collibra provides one-on-one technical support, which gives access to a very knowledgeable person and their customer service is amazing. The only problem is that sometimes they don't know the answer so they have to check it out and get back to us. Sometimes you reach a dead end and that's the main problem of their system. We also now get in-house support.

We didn't switch from another solution, but we were using other solutions to control metadata. We used Infomatica for our transformation things. It wasn't like a governance tool. We also used Spark IS, an information solution, to harvest the data we needed.

The initial setup took a week because our systems are tricky due to security considerations. Deployment throughout the company took about six months, but that's an internal issue because of training implementation and that adds to the time. It's our main governance system so we had to move carefully. We already have 2,100 people using it. Operations uses it a lot and sales uses it for everything. 

For now, only 60% of our company is using it, so there's no ROI yet. 

Collibra started at a very reasonable price and then they increased the cost significantly by about 150% and almost lost us as a customer. It was something that the people from procurement and from finance ask whether the solution is really necessary.

At the time we also evaluated Unify, which became Boomi after it was purchased by Dell. That's an amazing tool as is Informatica. The issue there was that the price was too high. We went with Collibra because of the price and what it gives the end user.

Sometimes the technical support is messy but the system is great. It's a very good tool and I would suggest speaking directly with the technicians who develop the tool, rather than customer service. It's a great tool for a medium size company. if you're in a larger company, I would recommend implementing team by team. It's a tool that the end user needs to understand so if you implement it all at the one time, people will have difficulties and you won't have the support. 

I would rate this solution a seven out of 10. 

Our clients are typically using it for metadata management. From a broader perspective, Collibra establishes an excellent foundation on which to build an enterprise data governance program. 

The most valuable aspect of the solution is its collaboration platform, which includes the workflows, the data lineage, and some of the communities. The ability to collaborate and approve business terms for the business glossary data dictionary is excellent.

The breadth of available connectors for metadata ingestion need to grow quickly to support customers as they expand their data governance programs to include a diverse list of source systems from which they want to derive business value. The connectors are needed  to bring metadata into Collibra and enable lineage, workflows, definitions, etc.  That said, this is not just a Collibra problem - this is an everybody problem. The central challenge is the availability of APIs to ingest text structural metadata, which is a common problem across any data governance platform or even any integration platform, honestly.

To be fair, I would say that Collibra's purpose and primary value is as a collaboration platform, which is the core value of business-centric data governance, and not as an integration platform.  For this purpose, they are clearly the leading solution.

We've been using the solution for six or seven years. We've used it longer than almost anybody.

The stability is very good. It's not buggy and it doesn't have glitches. It doesn't crash or freeze. It's reliable.

It's really scalable, it's really solid. If an organization needs to expand their solution, they should be able to do so easily.

We've reached out to technical support rather frequently. That said, it depends on the topic. I would say that their tech support is excellent, but it is not necessarily an overly large team because they are still a growing company.

They have some really good, smart people, however, they don't have a team of experts for each target subject area.  They don't have a team of 20 people for each application component that can just go, "Oh, yeah. We set an appointment tomorrow!" You might have to wait a few days for the right person.  Having said that, their focus on making detailed self-driven education and training available online enables clients easily to investigate application areas.

The way we view data governance is this: it has to be led by the business. It has to be business-facing. Although there's a number of applications that might have a data catalog, for instance, like Alation, Informatica or Talend, we're vendor-neutral. If we find something better, we'll switch. We're open about that.

With Collibra, their strength is that they were the only data governance platform built specifically to address data governance as it was being formed as a discipline. Virtually every other solution in the marketplace is built as some sort of data management application aimed at IT, and has either morphed from an ETL or something else into that. Alation morphed from a code scanning application into data governance solution (data catalog) for instance. 

Collibra also took a business-centric approach. Their application is the only one that you could throw a business person in front of, and they would understand it intuitively, they'd say, "Oh, okay. So this is where I approve items. This is where I request them. This is where I see things. This is a dashboard that I can look at our progress." You're not going to get a sales VP going into Collibra, but if a sales VP went into Collibra, they would understand it. That's another reason why this has been the data governance solution we have recommended to clients, and still do.

The setup is not complex. It is straightforward. Collibra's very good at doing setups very quickly, so we typically leave this to them. They sell a cloud installation. Essentially, they formerly were both on-prem and cloud, however, now they're focused only on a cloud delivery model based on customer demand.  Thankfully, it is extremely straightforward, as this is the box we need to check prior to helping clients move forward on their data governance program.

The costs vary. I don't have details on the exact pricing of the solution as we do not resell it even though we recommend it.  This enables us to maintain our neutrality as a client advisor.

Their licensing model focuses primarily on the advanced technical users to help to establish the data governance foundation and manage and maintain it as more and more business groups are brought on board.  What I like about their licensing model is that they try to remove barriers to adoption by making it very inexpensive to add "data citizens" across the organization, i.e.  normal, "lite" users who are using, but not developing, connectors, workflows, communities, etc.

In that sense, the marketplace perhaps is not aware of the beneficial TCO of Collibra's license structure, because it causes them to focus on the initial cost of the heavy advanced users, while not realizing that they will be able to bring the overall corporate community onboard at a relatively minimal cost. Therefore, their pricing can appear high per user, however, in fact, for a community or population of data governance users, it's, not actually that high, it's just front-end loaded to establish the technical foundation and basis for the data governance program.

We are experts on implementing business-centric data governance programs, as that is the only model for success.  As such, we are implementation partners with Collibra, and in fact are one of, if not the, longest-standing Collibra partners globally.

The advice I'd give to other potential users would be the same I'd give to people implementing any sort of governance. I would first advise clients to have your data governance business cases ready in advance, or at least start by identifying potential business outcomes that can be delivered through clear and documented access to data. From there, they can target the relevant source systems needed to delivere on these business cases.

From a technical perspective, there are different approaches to ingest structural metadata, i.e.  tools and connectors that are available to assist with this.  While Collibra is hands-down the best data governance collaboration platform, clients should review the different options to ingest metadata based on the targeted source systems.  Of course, Collibra's catalog is the first option that should be considered, but available connectors need to be reviewed.

Overall, on a scale from one to ten, I'd give it a nine. based on its excellence as a data governance business collaboration platform.  From the perspective of metadata ingestion,  I'd probably give it a seven - I like their current roadmap and designated approach, but connectors are a work in progress, as they are for everyone.

Collibra Governance helps us set the business rules and define critical data elements.

It is user-friendly, and other companies use Collibra Governance as well.

I have been using this solution for about a year and a half.

It is a stable solution. 

It is a scalable solution. When we initially migrated, it was a little tough, but we are getting used to it.

We had issues during setup, so we had to bring in a third party for the initial setup and migration from IGC to Collibra Governance. We didn't have technical knowledge then, so we needed help.

I do not have details on the licensing costs.

I rate this solution a seven out of ten. However, we like the solution, and I recommend it to others. It is better than the IGC solution we used in the past.

Our use case is to manage master data inside of Governance.

The solution is deployed on cloud. We have around 10 data analysts using the solution.

The most valuable feature is the discovery process for the data catalog because we get it in a visual format as a way to understand and classify it. It's good to generate insights and get the context of the data.

When we are doing discovery for unstructured data sources, I would suggest a quality report of the data that would indicate what was unable to process.

The main issue is the data quality and that we can't control dealing with the real-world data. It's good to measure this and compare it between different data sources.

The Collibra products are very consolidated in the market. I think it's harder to analyze different domains of the data. Through Data Lineage, I think Collibra could add a relationship graphic analysis. They could add a feature that is a new way to explore the data.

I have used this solution for six months.

It's pretty stable. It hasn't suffered any outages so far.

I'm not sure if you can improve or optimize the performance to streamline it, but in terms of stability, I haven't had any issues.

We haven't scaled up, so I don't know if we will have any issues with this.

I would rate this solution 8 out of 10. 

The entirety of Data Intelligence is good, but I can't talk about all the products inside. I can't give it a 10, at least for the pieces of Collibra that I know.

There are many pieces of the platform, and I think everyone should at least test the Data Catalog and Data Privacy or deploy it and combine it. If we mix with other vendors that can deliver these things, it will be complex to get things done.

It's very tight with the Data Catalog and Data Lineage. It's more than just an integration and an API for your services.