Informatica Intelligent Data Management Cloud (IDMC) Reviews

We were trying to publish a compendium of all our various assets using an Oracle-based data warehouse. We also had vendor-based solutions like Epic for electronic medical records on an SQL Server base. We had many research systems on various platforms because it's a cancer research institution. 

We wanted to pull together a comprehensive data catalog to show people all the different assets we had and where they could go to find things. If there were vendor-based definitions of things, we'd pull in the definitions and various attributes. It's a heterogeneous environment data-wise. We get a lot of value from a comprehensive enterprise catalog.

It's available on our intranet through a data governance portal. You could go there for a catalog, quality reports, etc. In a year, there may have been 500 unique visitors. It was my job to publicize it, but I didn't necessarily do a good job. I worked with research groups and clinicians to get their stuff on it, and they would tell other people about it. The nice thing about Informatica is that it was easy to link from our internal web portal to their catalog. I had excellent developers working for me. It didn't require much development, and it took less and less as time went on. 

I like EDC's self-service capabilities. You can put the catalog on the intranet inside the organization, so users can search for something. People in the research world have specialized systems, and you might find data from various places that sound similar. 

The purpose of the Enterprise Data Catalog was to build an internally searchable catalog of stuff. You may not have permission to see this data but at least you could find out where it was and contact the person who owns it. 

Interoperability is one area where EDC has room for improvement. It was challenging when the faculty took over the data world and had specific vendors they wanted to use, and some were not particularly open platforms. 

It was a challenge to promote data visibility while also jumping through hoops to take some of the proprietary things and make them part of the calling, especially when the vendor doesn't necessarily support interoperability. You need to export things from a vendor program and import them again. 

We used Informatica for a lot of the data governance stuff I worked with when I joined the company, including things like cataloging and profiling data. The organization has really changed a lot in the last year and went with Informatica EDC. They're moving from the on-prem version to the cloud.

Informatica is a strong company, and EDC is a solid platform. 

The scalability is excellent. Informatica really knows what it's doing. They're smart people and great engineers. 

Informatica's customer service and support were decent. They listen to their customers. If something is missing or wasn't working, they will put it on their roadmap. They were listening to customers for roadmap stuff. 

We wound up building a staging database to pull stuff out of the EDC, stage it, and then access that. It was open, so we would often have an intermediary layer at Oracle. If we wanted to show, for example, data quality over time, we would have a weekly quality process that would run. We staged that in an Oracle database, and the portal could access that.

We had to build Informatica pipelines and do some Azure work to feed data to them. With data warehousing, you typically have static data that is timestamped daily or weekly and sometimes monthly or annually.  We were trying to get real-time data, like blood pressure monitoring and stuff like that. That was a lot of work. I didn't do it. The integration team. 

When I joined the company, it was an Oracle-based solution. Then Epic took over, which was SQL Server-based. After that, they went to Azure. Now, all the analytics are supposed to be on this platform, and it's not particularly open. 

Setting up Informatica EDC is usually pretty straightforward. The challenge is working with vendors like Oracle and Microsoft, which have APIs for integrating things. You can query what they have. They want it to play well with other vendors because they know customers don't only have one brand of product. In some cases, you get vendors in there that are, "No, we're not going to do that because we're so special." It was a challenge. The platform of choice for data initiatives at the cancer research institution is Palantir. 

We didn't look for an alternative, but Azure has its own catalog.

I rate Informatica Enterprise Data Catalog nine out of 10. It's a great solution, and I was happy with it. It did everything I wanted, and Informatica dramatically increased the integration points over time. When we started, it was like Oracle and SQL Server, but now they're adding NoSQL databases and others.

Informatica has user groups and listens to user input. One of the people that worked for me hosts an annual Informatica user group in Houston. You can try to build your own Oracle-based or SQL-based solution. They listened to the market, and they're working on improving the interoperability. Maybe it works better with Palantir since I left, but they work across all platforms. They're making it Cloud-based. I didn't know anything about them before I got here. I was dropped into a department where Informatica had been for at least five or six years, and it was a good choice.

We use Informatica MDM for various clients for integration, removing duplicates, and centralizing data in one place.

It has improved our organization because it has made our data more reliable. Data is the most important asset these days, and in order to trust your data, you need these tools to make sure that your data is clean and reliable.

The match and merge function is good.

New machine learning could be added to Informatica MDM because the solution is outdated and is not moving with the current trends. The solution is good, but it definitely needs a lot of improvement and needs to speed up as per the market.

Artificial intelligence is something which they should add to the solution.

They need to do MDM on real-time data as well.

The price is a big factor. We try to convince our clients to go for Informatica, but the cost is too high, and they choose another product.

I've been using this solution for 15 years.

It's a reliable and perfectly stable solution.

It is scalable but to a certain limit.

I'm satisfied with the technical support.

Previously, I used IBM MDM, Orchestra Networks MDM, SAP MDM, and Oracle MDM. I have used a lot of MDM tools, and I've found that Informatica is the best solution out of all of them in terms of the architecture and user-friendliness. Also, the graphical user interface is very simple to use.

The initial setup is not very straightforward but not very complex either. It's somewhere in the middle.

Deployment can take six to seven months to a year or two years. It depends on the number of domains and the number of data sets you need to implement.

A team of eight to nine people can usually handle the deployment.

We mostly deploy on-premises and sometimes on the cloud. Informatica is very weak on cloud-based computing though.

We implement the solution for our clients.

Based on my clients' feedback, they have seen a return on investment in the long-term. After five or six years, they can definitely see that the value of their data is growing.

Informatica MDM is very expensive. Apart from licensing fees, they have broken down their products into multiple products, and they charge for each and every product. If the data is huge, they charge for the data. At times, we have to use third party services for data cleaning, and they charge for that as well.

If you are choosing Informatica, then you need to employ the right kind of service provider. If you don't have good implementers, you'll not be able to leverage the product. So, choose your consultant and service provider wisely; then, you will not have any issues when implementing Informatica.

I would rate Informatic MDM at eight on a scale from one to ten.

The most valuable features of Informatica MDM are it is cloud-enabled and has all the elements that are supposed to have in terms of MDM as a solution. All the features that are there. It is very well-integrated with any of the SAP and non-SAP applications. It is quite user-friendly. The user experience that you receive in Informatica MDM is quite good.

From multiple masters that are there in Informatica MDM, we can improve the financials.

I have been using Informatica MDM for approximately four years.

The stability of Informatica MDM is good.

Informatica MDM has very good scalability. When we say scalability it refers to the ability to add custom fields as per the requirement and then upgrade the overall data model the way you want for the client. 

The scalability is one of the most important features because the clients do not want to use a common data model. They want to have scalability so that they can upgrade the data model the way they want.

We have approximately 25 people using this solution in my organization. The users of the solution include data stewards, business data owners, data sponsors, technical architects, and testers. All kinds of people are using the solution.

There are certain challenges with the support from Informatica MDM, however, I did not directly contact them. It was somebody in my team who did.

I rate the support from Informatica MDM a three out of five.

I did not use another solution previously.

The initial setup of Informatica MDM is complex but is okay if you have experience. The full deployment took approximately five to six months.

Where one is the easiest and five is the most complex, I rate the complexity of the initial setup of Informatica MDM a two out of five.

The deployment of Informatica MDM was done by a whole team, approximately eight to ten people involved, and they had multiple roles. Each person looked after a different section, such as data, validation, and testing.

My advice to others is they need to first ensure that the functions of the solution are stable and the people who are supposed to implement it should have a good functional understanding. It is important that the team that is working on, in terms of standardization and data quality check, that it is a robust team, a strong team to take care of the solution. If we upload data in the system and then the data is not correct, then it becomes a very difficult job to clean afterward.

I rate Informatica MDM an eight out of ten.

Informatica MDM is used for all data management practices use cases, such as centralized master data, cataloging, and metadata management.

The most valuable features of Informatica MDM are its reliability, match functions, and integration capabilities. The out-of-box functionality of deduplication and built-in data models ensure faster implementation.

Informatica MDM could improve the interdependency with integration. The solution sometimes becomes a bit difficult to change considering a lot of interdependency with the integration. There can be some improvement in the workflows and they can introduce more artificial intelligence.

In a future release, Informatica MDM could improve the UI and create an easier way to change the existing setup.

I have been using Informatica MDM for approximately 20 years.

Informatica MDM is stable.

Informatica MDM is scalable. However, sometimes it becomes difficult to perform the change. When it comes to volumes, it's fantastic and very fast.

We have an entire organization of approximately 80,000 using the solution.

The technical support from Informatica MDM is good.

I have previously used IBM, SAP MDG, and Parallels.

If an organization has a quite complex setup with different systems then I would recommend Informatica SAP MDM because of the integration capabilities. If the organization only has one ERP, then it's not advisable to use Informatica MDM because SAP MDG is quite integrated with SAP.  The IBM solution I use quite a long time before, but I don't know how they are doing today.

The setup of Informatica MDM is easy.

We have two people that do the development and maintenance of the solution.

Informatica MDM recently changed its pricing model. It's usage-based but I don't have much insight into the current pricing.

Whether to use Informatica MDM or not is highly depends upon what is the use case and the core structure you have in the organization. If you have a small company with limited systems, then you use something lightweight MDM. Where you have more than one ERP, all technology interacting with each other, then I would suggest a solution, such as Informatica MDM, it is a good deal.

I rate Informatica MDM a seven out of ten.

It can be used for different kinds of use cases. You can use it for data deduplication purposes for any industry. For example, in the pharma, healthcare, or life science sector, often a lot of medical data gets duplicated across different business functions of the enterprise. As a result, the sales and marketing channels may face a lot of challenges in marketing their medicines to the right physicians. In such a scenario, Informatica MDM could be really helpful in standardizing the data and creating a golden copy of it, which can then be published to the sales and marketing channel so that the sales representatives have accurate data to market their medicine or product. This is one of the use cases.

Its deployment depends on the project and client requirements. I don't have Informatica MDM deployed for my organization. We build solutions for our clients by using Informatica MDM. So, it entirely depends on what a client wants. For some of the projects, it is deployed on-prem, and for some of the projects, it is deployed on the cloud. In the most recent scenarios, it is mainly on the cloud. Informatica, just like other MDM solutions, is also moving toward the SaaS platform. So, I'm sure that going forward, for any kind of project opportunity, we'll be using the SaaS model when it comes to the deployment of Informatica MDM.

The Provisioning tool is something that is really handy for everyone. It is my pick as the best feature.

It is a very mature tool. It has been in the market for more than a decade.

If I compare it with other MDM solutions in the market, one thing that can definitely be improved is automation to help with the configuration. Currently, when we are creating any staging of base object tables, all the columns have to be configured manually in the Informatica Hub Console. A lot of tables and different kinds of business columns have to be configured manually. There should be an automated process for this, especially in the Dev environment. When people are creating tables and columns from scratch, if there is a backend automated process for that, it would be really helpful. In Stibo, a similar feature is there wherein you can tag attributes to certain objects. It would be helpful if Informatica also provides a similar option. It would reduce the manual effort. It could be that such a feature is already there, but I am not aware of it.

Their support can also be improved. They sometimes take long when an incident is not a priority incident.

I have been using Informatica MDM for the past five or six years.

It has been in the market for more than a decade. Over the last decade, Informatica has proved to be the best MDM solution that is available in the market. Informatica is one of the leaders as per Gartner and Forrester. There are no second thoughts about the stability of the tool. It's definitely the best one in the market right now.

I would rate them a four out of five. There is definitely room for improvement when it comes to technical support. Sometimes, when an incident is not a priority incident, they take their own sweet time to meet the SLA. For a priority one incident, they jump in and resolve the issue really fast. 

For someone trying it for the first time, it would definitely be a little bit complex, but once you get used to it, over a period of time, the complexity reduces. With experience, it becomes easier.

The deployment duration depends on the complexity of the configuration and the complexity of the import configuration on Informatica MDM. There is a feature called import where you get the chance to import it from the lower environment to a higher environment. The import process is pretty straightforward, but sometimes, when very complex configurations are done in the lower environment, it can get a little bit complicated to import the delta changes. It can take a while. 

Its maintenance isn't a big headache. For on-prem deployments, the maintenance is pretty easy and straightforward. It is not a very big overhead. With the SaaS solution, there is no overhead at all.

It was done in-house. There was no third party.

There is no doubt that it is very expensive, but the brand value comes at a cost. Other MDM solutions in the market that haven't proven themselves like Informatica are also pretty expensive. We need to understand that MDM itself is very expensive to implement. So, Informatica is also pretty expensive. I would rate it a two out of five for being pretty expensive.

One piece of advice that I would like to give to anyone implementing Informatica MDM or any other MDM solution is to be in regular touch with business users during the implementation. Because it's an MDM solution, it's business-driven rather than IT-driven. So, always stay in constant touch with business users or data stewards to best understand the data. Never try to make decisions related to the data on your own. It is always good to be in regular touch with business users and let them make the decisions. Based on their decisions, you do the implementation. Do not make any decisions yourself because the businesses understand their own data best, and they are the best decision-makers when it comes to their own data. 

I would rate Informatica MDM a nine out of ten.

Our clients need to perform data masking to comply with GDPR rules or the company's internal data security policies. Data masking restricts who can look at the private customer data. Informatica provides a comprehensive solution for on-the-fly or real-time data masking. 

One use case is masking the data for a test environment, so developers and testers can't see production data. This is something you have to do regularly with large amounts of data.

The second use case is in a production environment. Sometimes you need to mask the data on the fly when the data consumers are retrieving reports from the data platform. You are masking the data for certain groups who don't have permission to see that data. 

Informatica should simplify the rules for setting classifications and user access management permissions. It's too complex to define, configure, and make work.

One feature I would like to see is the ability to do data sampling when anonymizing a test environment. It would save you the trouble of having to replicate or perform complex configurations when moving to another environment for testing or development. You should be able to easily configure the data sampling when you are preparing an environment with anonymized data.

We are a system integrator, and we've been one of Informatica's biggest partners for around two years. My team integrates Persistent Data Masking for our clients, but I don't use it personally. I understand the product and its capabilities, and the clients give me feedback on it.

Persistent Data Masking is stable and ready to scale. It has to be. You are working with large amounts of data.

I rate Informatica support eight out of 10. Informatica provides standard support during deployment. A vendor that doesn't offer support isn't a good company. Informatica is willing to make a straightforward deployment because they care about feedback from the client. 

They don't mind investing some money at the beginning to make it run. They care about retaining clients for a long time. Client satisfaction is essential.

Positive

I rate Persistent Data Masking eight out of 10 for ease of setup. It's straightforward. You can deploy a proof of concept in three weeks. It takes two or three people to deploy, but one guy is fine for maintenance. Then again, it depends on the scope and how many anonymizations you have to do, but it doesn't require a big team.

It's usually a yearly subscription, but customers can go with a different pricing model. Typically, it's a yearly subscription for the cloud solution. If you're buying an on-premise solution, it's a one-time payment and annual license for support.

I rate Informatica Persistent Data Masking seven out of 10. 

It is generally used for the data integration between multiple ERPs. We have ERPs, and then we have third-party exchanges that sell products. The third parties are partnered up with some of the customers, so they create deeds, and we pull in orders and quote requests.

We're trying to get to the latest version. We're two revisions behind right now. It is a local install. 

It is on-prem, and we're trying to get to all-cloud. We do use the cloud for configuration, but we deploy it to the agents locally. We're using the cloud instance of Informatica to deploy to, and we're currently on Azure.

In the latest version, I like the outlay of the business roles creation. I like seeing that visualization as you're building it, as opposed to going through metatables or XML mappings. We liked that piece, and it makes it more intuitive for the business. 

Its GUI interface definitely helps visualize what we're trying to accomplish. There is always a disconnect between IT and the business, and it helps in creating the feeds that follow the business process flows with some of the types involved with the business.

It is so broad in what it can do. Their services have expanded beyond what they originally built it out to be. The best thing I like about it is that each time they add a new service to the platform, it easily integrates with the core, which is really nice.

The biggest pain point for us is the documentation. Typically, you have to go through knowledge forums and knowledge groups to find out about the syntax issues for interfacing with new products. Typically, you've got to deal with someone who has been through the pain before. Their documents are not really up to date with current innovations happening in the industry. As big as they are, you can't really expect it, but that's our pain point.

We've been using this solution for about four years.

We love it. It is very stable. It is probably the best thing we've seen in a while.

It can out scale our ERP. So, scalability is not an issue for us. However, it can overload our system, but that is not related to the scalability of MDM. It is related to the scalability of the system it feeds.

We have five business roles that are using it, and there are two admins who are supporting it. Basically, it is supporting an environment of about 5 billion in revenue. That's a lot for that amount of revenue. It is a lot of people.

We're trying to extend or expand more modules. We have MDM, and we're going into Supplier 360 and Product 360. We found that it is the most robust platform to integrate with our e-commerce platform. Basically, we have four different e-commerce realms, and we're going to consolidate them. So, Informatica helps with the supplier stuff coming in, harmonizing the data, propagating it out to the sites. In the future, the four sites are going to be combined and consolidated into one site, and then we'll be dealing with four different ERPs, and Informatica will be very key in that as well.

Their technical support is excellent. Whenever we had issues, they were pretty quick to respond. There was never an issue in finding them. The longest we had to wait for getting a resolution was a couple of hours.

I walked into this, so I don't know what they had before.

I wasn't involved with its setup.

It is expensive. That's probably the biggest drawback. The business has heartache paying the license, but that's mainly because they don't realize what value it brings. The key thing about the MDM solution is that it is in the backend, and no one sees what it is actually doing. You don't know it is a problem until it is not there.

I would advise making sure that you have a very well-defined design before you decide you need an MDM. In our case, after MDM was in place and we turned it on, we realized that there are other processes that we needed to refactor for the purpose of MDM, which extended the rollout. This was not an MDM issue. It was a process issue in the business. That's why you need to make sure that the design is well defined. It helps to have their partners involved as well. We're dealing with Informatica consulting today to help design a Supplier 360 portal. 

It is hard to find people who are well versed in Informatica. It is hard to pluck one out of the place. You've got to go and poach for them. They're not out there open and looking for jobs.

I would rate Informatica MDM an eight out of 10.

At our company, we use Informatica MDM for data architecture and numerous other aspects of data warehouse, such as data designing or modeling. We recommend Informatica products to our customers based on their use cases, data volume, budget, and environment suitability.  

The product isn't mature enough to provide suitable connectors to various data engines. The performance of the solution in transporting data between data lakes and Big data infrastructure is not up to the mark. At our company, we use a similar solution called Spark, which is much better than Informatica MDM in terms of performance and speed. The data support capabilities of Informatica MDM can be improved. 

It's a stable product without any bugs or glitches. But overall Kafka is a better product than Informatica MDM. 

The product exhibits satisfying scalability. 

The tech support is satisfying from the vendor. The support team was able to respond and solve the issues in a very short time. I would rate the tech support an eight out of ten. 

Positive

Informatica MDM easily integrates with the Informatica environment as well as with third-party tools. But for some integrations, for instance, when Informatica MDM is integrated with SAP, the functionality slows down drastically; the task that would take five minutes with Spark takes five hours with Informatica MDM.

The same scenario occurs when Kafka is integrated with Informatica MDM. For popular database integrations such as Oracle and SQL, Informatica MDM functions well enough. 

The initial setup of the solution is straightforward. Our company professionals suggest that Informatica MDM should be on a Linux server instead of Windows. 

The product is very expensive compared to other competitor tools. Informatica MDM is not meant for small businesses but rather used by large enterprises like banks or government organizations. Informatica MDM can be purchased as a stand-alone product and doesn't come in an Informatica bundle. The support for Informatica MDM is not included in the standard licensing fees and must be purchased separately.  

I recommend that others test Informatica MDM with different integration tools before making a purchase decision. I also advise others to evaluate the use cases before choosing a product. Other popular competitor tools in the market include Collibra and SAP MDG. 

Informatica MDM fits our organization's use cases perfectly. When a customer of our company has a plethora of business products, VOCs need to be implemented, even if it's a different MDM solution than Informatica MDM.

Some customers depend on a single technology ERP, while others work with Oracle ERP or SAP, and sometimes they are using ERP and Informatica MDM in combination or migrating from one ERP to another. These use cases will impact the setup that already exists on the customer's site, and thus, the solution needs to be configured accordingly. I would rate Informatica MDM as eight out of ten.