erwin Data Intelligence (DI) for Data Governance Overview

erwin Data Intelligence (DI) for Data Governance is the #2 ranked solution in our list of Data Governance tools. It is most often compared to Informatica Axon: erwin Data Intelligence (DI) for Data Governance vs Informatica Axon

What is erwin Data Intelligence (DI) for Data Governance?

The erwin Data Intelligence Suite (erwin DI) combines data catalog and data literacy capabilities for greater awareness of and access to available data assets, guidance on their use, and guardrails to ensure data policies and best practices are followed. Automatically harvest, transform and feed metadata from a wide array of data sources, operational processes, business applications and data models into a central data catalog. Then make it accessible and understandable within context via role-based views. This complete metadata-driven approach to data governance facilitates greater IT and business collaboration.

erwin Data Intelligence (DI) for Data Governance is also known as erwin DG, erwin Data Governance.

erwin Data Intelligence (DI) for Data Governance Buyer's Guide

Download the erwin Data Intelligence (DI) for Data Governance Buyer's Guide including reviews and more. Updated: July 2021

erwin Data Intelligence (DI) for Data Governance Customers

Oracle, Infosys, GSK, Toyota Motor Sales, HSBC

erwin Data Intelligence (DI) for Data Governance Video

Pricing Advice

What users are saying about erwin Data Intelligence (DI) for Data Governance pricing:
  • "The whole suite, not just the DI but the modeling software, the harvester, Mapping Manager — everything we have — is about $100,000 a year for our renewals. That works out to each module being something like $8,000 to $10,000."
  • "The solution is aggressively priced."
  • "We operate on a yearly subscription and because it is an enterprise license we only have one. It is not dependent on the number of users."
  • "erwin's pricing was cheaper than its competitors."
  • "You buy a seat license for your portal. We have 100 seats for the portal, then you buy just the development licenses for the people who are going to put the data in."
  • "The licensing cost is around $7,000 for user. This is an estimation."
  • "There is an additional fee for the server maintenance."
  • "erwin is cheaper than other solutions and this should appeal to other buyers. It has a good price tag."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
RickDe Avila
Data Architect at NAMM
Real User
Top 20
Enabled us to centralize a tremendous amount of data into a common standard, and uniform reporting has decreased report requests

What is our primary use case?

We're a medical company and we have our own source systems that process claims from multiple organizations or health plans. In our world, there are about 17 different health plans. Within each of those health plans, the membership, or the patients, have multiple lines of businesses, and the way our company is organized, we're in three different markets with up to 17 different IPAs (Independent Physician Associations). While that is a mouthful, because of data governance, and our having own data governance tool, we understand those are key concepts and that is our use case: so that everybody in… more »

Pros and Cons

  • "The biggest benefit with erwin DI is that I have a single source of truth that I can send anybody to. If anybody doesn't know the answer we can go back to it. Just having a central location of business rules is good."
  • "The solution gives us data lineage which means we can see an impact if we make a change. The ability for us to have that in this company is brilliant because we used to have 49 data stewards from some 23 different groups within six major departments. Each one of those was a silo unto itself. The ability to have different glossaries — but all pointed to the same key terms, key concepts, or key attributes — has made life really simple."
  • "The fact that I sometimes have to go in and out of different applications, even though it's all part of the whole erwin suite, perhaps means it could be architected a little bit better. I think they do have some ideas for improvements there."
  • "There was a huge learning curve, and I'd been in software development for most of my career. The application itself, and how it runs menus and screens when you can modify and code, is complex. I have found that kind of cumbersome."

What other advice do I have?

Our first goals were data literacy and data as an asset. Those were our two big, ultimate goals three years ago. Data literacy turned out to be 10 times more important than a data warehouse. We could look at existing data sets and, just by educating people, it gave them an advantage almost immediately. The fact that the data governance was able to put a framework around data literacy helped us focus on the right answer, even if it wasn't the first one given. In other words, sometimes we'd have the same answer three or four times, and it would shift until we nailed it. But without governance…
Tracy Hautenen Kriel
Sr. Manager, Enterprise Data Modeling CoE/COP at a insurance company with 10,001+ employees
Real User
Top 5Leaderboard
We always know where our data and metadata are, versus having to spend weeks hunting down information

What is our primary use case?

We have many use cases. We have a use case to understand our metadata, understand where it is, and understand where our authoritative data systems are. We need to understand the data systems that we have. We also need to link the data models that we have to these data systems so that we know which data models are supporting which database applications. We're also linking our business data models to our physical implementation so that our data governance team is driving our data and our understanding of our data. That is one use case for the Metadata Manager. Another is the creation of… more »

Pros and Cons

  • "The data management is, obviously, key in understanding where the data is and what the data is. And the governance can be done at multiple levels. You have the governance of the code sets versus the governance of the business terms and the definitions of those business terms. You have the governance of the business data models and how those business data models are driving the physical implementation of the actual databases. And, of course, you have the governance of the mapping to make sure that source-to-target mapping is done and is being shared across the company."
  • "We always know where our data is, and anybody can look that up, whether they're a business person who doesn't know anything about Informatica, or a developer who knows everything about creating data movement jobs in Informatica, but who does not understand the business terminology or the data that is being used in the tool."
  • "The metadata ingestion is very nice because of the ability to automate it. It would be nice to be able to do this ingestion, or set it up, from one place, instead of having to set it up separately for every data asset that is ingested."
  • "We chose to implement on an Oracle Database because we also had the erwin Data Modeler and Web Portal products in-house, which have been set up on Oracle Databases for many years. Sometimes the Oracle Database installation has caused some hiccups that wouldn't necessarily have been caused if we had used SQL Server."

What other advice do I have?

Erwin currently supports two implementations of this product: one on a SQL Server database and the other on an Oracle Database. It seems that the SQL Server database may have fewer complications than the Oracle Database. We chose to implement on an Oracle Database because we also had the erwin Data Modeler and Web Portal products in-house, which have been set up on Oracle Databases for many years. Sometimes the Oracle Database installation has caused some hiccups that wouldn't necessarily have been caused if we had used SQL Server. We are not currently using forward engineering capabilities of…
Learn what your peers think about erwin Data Intelligence (DI) for Data Governance. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
521,189 professionals have used our research since 2012.
Manoj Narayanan
General Manager - Digital & Analytics Practice at HCL Technologies
Real User
Top 5Leaderboard
Metadata harvesters, data catalogs, and business glossaries help standardize data and create transparency

What is our primary use case?

Our clients use it to understand where data resides, for data cataloging purposes. It is also used for metadata harvesting, for reverse engineering, and for scripting to build logic and to model data jobs. It's used in multiple ways and to solve different types of problems.

Pros and Cons

  • "erwin has tremendous capabilities to map right from the business technologies to the endpoint, such as physical entities and physical attributes, from a lineage standpoint."
  • "Another area where it can improve is by having BB-Graph-type databases where relationship discovery and relationship identification are much easier."

What other advice do I have?

It is a different experience. Collaboration and communication are very important when you want to harvest the value from the humongous amount of data that you have in your organization. All these aspects are soft aspects, but are very important when it comes to getting value from data. Data pipelines are really important because of the kinds of data that are spread across different formats, in differing granularity. You need to have a pipeline which removes all the complexities and connects many types of sources, to bring data into any type of target. Irrespective of the kind of technology you…
Maximilian Te
Business Intelligence BA at a insurance company with 10,001+ employees
Real User
Top 10
Good traceability and lineage features, impact analysis is helpful in the decision-making process, and the support is good

What is our primary use case?

Our work involves data warehousing and we originally implemented this product because we needed a tool to document our mapping documents. As a company, we are not heavily invested in the cloud. Our on-premises deployment may change in the future but it depends on infrastructure decisions.

Pros and Cons

  • "Overall, DI's data cataloging, data literacy, and automation have helped our decision-makers because when a source wants to change something, we immediately know what the impact is going to be downstream."
  • "There is room for improvement with the data cataloging capability. Right now, there is a list of a lot of sources that they can catalog, or they can create metadata upon, but if they can add more then that would be a good plus for this tool."

What other advice do I have?

My advice for anybody who is considering this product is that it's a useful tool. It is good for lineage and good for documenting mappings. Overall, it is very useful for data warehousing, and it is not expensive compared to similar solutions on the market. I would rate this solution a nine out of ten.
SA
Sr. Manager, Data Governance at a insurance company with 501-1,000 employees
Real User
Top 20Leaderboard
Lets me have a full library of physical data or logical data sets to publish out through the portal that the business can use for self-service

What is our primary use case?

We don't have all of the EDGE products. We are using the Data Intelligence Suite (DI). So, we don't have the enterprise architecture piece, but you can pick them up in a modular form as part of the EDGE Suite. The Data Intelligence Suite of the EDGE tool is very focused on asset management. You have a metadata manager that you can schedule to harvest all of your servers, cataloging information. So, it brings back the database, tables, columns and all of the information about it into a repository. It also has the ability to build ETL specs. With Mapping Manager, you then take your list of… more »

Pros and Cons

  • "They have just the most marvelous reports called mind maps, where whatever you are focused on sits in the middle. They have this wonderful graphic spiderweb that spreads out from there where you can see this thing mapped to other logical bits or physical bits and who's the steward of it. It's very cool and available to your business teams through a portal."
  • "There are a lot of little things like moving between read screens and edit screens. Those little human interface type of programming pieces will need to mature a bit to make it easier to get to where you want to go to put the stuff in."

What other advice do I have?

If you have the ability to pull a steering committee together to talk about how your data asset metadata needs to be used in different processes or how you can connect it into mission-critical business processes so you slowly change the culture, because erwin DI is just part of the processes, that probably would be a smoother transition than what I am trying to do. I'm sitting in an office by myself trying to push it out. If I had a steering committee to help market or move it into different processes, this would be easier. Along the same lines as setting up an erwin Workgroup environment, you…
MJ
Solution Architect at a pharma/biotech company with 10,001+ employees
Real User
Has the ability to run automation scripts against metadata and metadata mappings

What is our primary use case?

The three big areas that we use it for right now: metadata management as a whole, versioning of metadata, and metadata mappings and automation. We have started to adopt data profiling from this tool, but it is an ongoing process. I will be adding these capabilities to my team probably in Q1 of this year.

Pros and Cons

  • "The possibility to write automation scripts is the biggest benefit for us. We have several products with metadata and metadata mapping capabilities. The big difference when we were choosing this product was the ability to run automation scripts against metadata and metadata mappings. Right now, we have a very high level of automation based on these automation scripts, so it's really the core feature for us."
  • "The SDK behind this entire product needs improvement. The company really should focus more on this because we were finding some inconsistencies on the LDK level. Everything worked fine from the UI perspective, but when we started doing some deep automation scripts going through multiple API calls inside the tool, then only some pieces of it work or it would not return the exact data it was supposed to do."

What other advice do I have?

I learned how to automate in the data area and how this is very different from any CI/CD development platforms that I was working on before. I learned that we need totally different things to automate properly in the data area. We need very accurate metadata. We need precise mappings reviewed by different data stakeholders. I would rate this product as an eight (out of 10). I can imagine some capabilities for this product that would make it even better.
Jim Marr
Analytics Delivery Manager at DXC
Reseller
Top 5Leaderboard
Value is in the accuracy, quality, and completeness of the migration source to target mapping and acceleration of development through code automation.

What is our primary use case?

We use DI for Data Governance as part of a large system migration supporting application refresh and multi-site consolidation. Metadata Manager is utilized to harvest metadata which is augmented with custom metadata properties identifying rules criteria which drive automated source to target mapping. Custom build code generation connector then automates forward engineering code generation groovy. We've developed a small number of connectors supporting this 1:1 data migration. It's a really good product that we've been able to make very good use of.

Pros and Cons

  • "We use the codeset mapping quite a bit to match value pairs to use within the conversion as well. Those value pair mappings come in quite handy and are utilized quite extensively. They then feed into the automation of the source data extraction, like the source data mapping of the source data extraction, the code development, forward engineering using the ODI connector for the forward automation."
  • "One big improvement we would like to see would be the workflow integration of codeset mapping with the erwin source to target mapping. That's a bit clunky for us. The two often seem to be in conflict with one another. Codeset mappings that are used within the source to target mappings are difficult to manage because they get locked."

What other advice do I have?

We haven't integrated Data Catalog and Data Literacy yet. Our client is a little bit behind on being able to utilize these aspects that we've presented for additional value. My advice would be to partner with an integrator. erwin has quite a few of them. If you're going to jump into this in earnest, you're going to need to have that experience and support. The biggest lesson I have learned is that the only limitation is the imagination. Anything is possible. There's quite a strong capability with this product. I've seen what you can come up with as far as innovative flows, processes…
BM
Data Program Manager at a non-tech company with 201-500 employees
Real User
Wide range of widgets enables a user to find information quickly. However, the configuration and structuring of this solution is not straightforward.

What is our primary use case?

This solution is still an experiment for us. My company is in the process of defining the data governance process, which is not settled right now. We have used erwin DG for the purpose of getting acquainted with data governance from a technical point of view. We want to see how it fits in our organization because data governance is neither IT nor a business matter. It is in-between. We have to put the proper organization in place in order for an IT solution to meet all the requirements. This has been in the works for almost two years now, where we have been formerly under an experiment with… more »

Pros and Cons

  • "There is a wide range of widgets that enables the user to find the proper information quickly. The presentation of information is something very valuable."
  • "If we are talking about the business side of the product, maybe the Data Literacy could be made a bit simpler. You have to put your hands on it, so there is room for improvement."

What other advice do I have?

erwin is very good for companies who have a very structured, data governance process. It puts every possible tool around a company's data. This is very good for companies who are mature with their data. However, if a company is just looking for a tool to showcase their data in a data catalog, then I would advise companies to be careful because erwin is sometimes really complex to master and configure. Once it is set up, you have to put your hands in the gears of the software to model how your data works. It is more of a company process modeler than a directory of all data available you need…