Informatica Intelligent Data Management Cloud (IDMC) Reviews

The solution is robust. We can connect with quality analysis tools for summarizing the data as well. It has all the essential features.

The solution's cloud-based version has a few limitations compared to its on-premise version.

I have been using the solution for eight years.

The solution is highly stable. We never had any issues with the cloud version. I rate its scalability a ten out of ten.

The solution is highly scalable. I rate its pricing an eight or nine out of ten.

The solution's technical support team is well-skilled.

The solution's initial setup is straightforward. I rate the process a ten out of ten. It takes a little time to deploy and requires minimal staff.

Our vendor manages the solution's implementation.

Our clients evaluated Profisee and Precisely before. Comparatively, Informatica provides better integration with quality analysis, data governance, and data integration tools.

I advise others to know their company's requirements before implementing the solution. I rate it an eight out of ten.

We use Informatica Axon for MDM purposes.

The most valuable feature of Informatica Axon is that it is flexible and user-friendly.

Informatica Axon needs more integration connectors so that it can connect to systems and different kinds of datasets.

I have been using Informatica Axon for two years.

I rate Informatica Axon an eight out of ten for stability.

Ten engineers are using Informatica Axon in our organization. I rate Informatica Axon an eight out of ten for scalability.

Informatica Axon's installation, configuration, and user access take two to three days.

Informatica Axon eliminates all MDM-related problems quickly.

Informatica Axon is a costly solution. I rate Informatica Axon a four out of ten for its pricing.

I am using the latest version of Informatica Axon. I recommend Informatica Axon to users as it is a good and flexible tool that gets the work done.

Overall, I rate Informatica Axon a seven out of ten.

We use the solution for data modularization.

The solution has the best feature for parameterization. We can apply it at the mapping and task flow levels. It helps with auto-linking and dynamic linking options for flexible data integration.

The solution's capability to handle large volumes of data compared to its on-premise version needs improvement. Its features for partitioning and optimization could be better as well. There needs to be more options for partitioning, including database partitioning, pass-through partitioning, etc. Additionally, it doesn't support XML data types for SQL server databases. Also, it captures success and targets rows only within a system-defined area. It should be able to capture and track the number of rows processed by each pipeline.

Presently, users need to write code against the existing APIs to access information data. It is a complicated process due to the limited functionality of APIs. Instead, there could be an option to write queries against repository tables to fetch the data like its on-premise version.

We have been using the solution for two years.

The solution's technical support team could be responsive. We have to contact their global support team to raise new feature requests. Currently, we encounter issues with parameterizing email IDs at the task level to configure features for success, warning, and failure. We sent a request to them back in 2020, but they are yet to add those features.

I rate the solution a seven out of ten.

I manage the environment and admin-related tasks.

I have integrated Axon into EDC, PowerCenter, and data quality tools, and I face no difficulty integrating with those tools.

I also handle installation, configuration, and troubleshooting issues, in addition to when users face access issues or need help seeing their DQ technical roles.

With Axon, you can easily call and verify DQ rules. You can also upload your business gallery, and the business team can easily verify your data because it is secure.

Some of Axon's valuable features include creating your business glossaries, importing DQ rules, and creating change management.

They could improve technical support because it is not good enough at the moment.

I am a consultant and have been working with Informatica Axon for three years.

I rate the stability an eight out of ten because I have not yet seen the environment go down.

I rate the scalability of the solution a five out of ten. We have faced some performance issues. We have about five or six Axon business users who are data owners and stewards. They are not very active with the solution.

Personally, for the last month, I have not touched Axon or the servers. There are no plans to expand Informatica Axon's usage at the moment.

I rate the initial setup a seven out of ten. The clients gave us their Linux servers, and I set up the solution on-premises.

I could set up the environment, the installation, and the configuration in one day.

My organization's initial steps required us to get licenses for the installation, and we needed specific kinds of ports opened from our environment. We first needed to install the Axon agent and Axon server on different directories. Once we did that, we needed to update a couple of files to communicate with data quality and other functions.

The solution requires some maintenance. I might have to perform a sync-up or make sure the environment is not down, but that is very rare.

The solution was implemented in-house, with me deploying the solution single-handedly.

I rate the pricing a six or a seven out of ten because the price is neither too high nor too low.

Informatica is a big name in the market and the tools are trustworthy, which is why our client chose Informatica Axon-EDC. I rate the solution an eight out of ten.

The most valuable features of Informatica MDM are the IDQ and RDM data management. PowerCenter is the most widely used feature of Informatica MDM.

Informatica MDM has a complex user interface, which could be improved.

I have been using Informatica MDM for four years.

I rate Informatica MDM an eight out of ten for stability.

I rate Informatica MDM a ten out of ten for scalability. We plan to increase the usage of the solution in the future.

I rate Informatica MDM a four or five out of ten for ease of initial setup.

Our organization's deployment process for Informatica MDM took two to three months. A third-party team did the solution's deployment. Around 10 to 12 IT specialists and engineers were required for the solution's deployment.

Informatica MDM's pricing is not cheap but comparable to other vendors.

I advise others looking into using Informatica MDM in the future to have their use cases in order and know what they want to use it for.

Overall, I rate Informatica MDM a six out of ten.

The solution is mostly used to automate MDM, send keyword dimension sites to the engineering team, or address historical records for the training-based employee.

The valuable feature is that we can automate the integration part. Also, it's suitable for data quality. The solution also helps create the data that has been helpful in data governance. We performed some effective or administrative charges in real-time and, most recently, in a real-time solution. So, it allows enrollment to capture and transform the data anytime.

Most of the demand is about how MDM can be automated so the changes occur automatically.

The whole server will change the storage engine, like any tool key, so everything can be automated.

Informatica MDM has limitations with connectivity. This is evident when we connect with our console, especially sometimes the process gets filled. With the tools we are locally running from our end, there should be some specific instance to register that is helpful and can support Informatica in running its modeling.

More automation is much required nowadays, as mainly the work will convert into a complete normal manual process.

There should be some specific integration tools, the managed services, involving the application, and then the code they use. That should be sufficient, meaning there should be leverage to openly adopt any new integration environment like PySpark that we will use. Some resiliency with the particular application, the code, and the type of files only can we address.

I have been using Informatica MDM for more than ten years.

It is a stable solution.

It is a scalable solution for sending any new setup or data. Approximately six hundred users are using the solution.

The technical support team is good. The administration has access to both servers. They can only provide access to run the tool, allow authentication, and how data can be secured. I rate the service and support as ten out of ten.

Positive

Previously, I have used Microsoft SSIS and AWS Glue, but Informatica is capable of doing multiple things for integration purposes, but also for data evaluation.

The initial setup is straightforward. The deployment took ten to fifteen minutes, and almost fifteen administrators were needed for the deployment.

I would say that based on the current scenario, the market trends show that it is not required for the price to be increased. But, functionality-wise, and considering that now as the trend of microservices is going on in the market if Informatica MDM can be replaced in a similar way with particular tools or components to meet the client's demands, we can use only those particular things for the DDoS service covering, for the backup, for the security, and data encryption. So that can be helpful. Part-wise, if somebody needs only the pipelines to be created, someone needs to get a complete data flow task, or someone requires only the MDMs to get in place and not complete information that they need to make. We have licenses, and we are provided with certain particular services in the solution.

I urge those planning to use the solution to understand how they are modeling data encryption and data governance activities. Suppose you are implementing without knowing your data quality and data governance. In that case, the installation of those sources through MDM is not affected. So better to better understand the basics.

Then it will be helpful to use something specific.

I rate the overall solution a seven out of ten.

We have used it to elaborate on a project for Golden Record, for IDQ data quality, and create business cases for the control parties.

The product could be improved in the area of architecture and technology. All the parts are old.

I would like to migrate it to a new technology. It's better to have a new method for every IT system. Integrate with API, Kafka, and JMS, as API has in Jira code or Jira.

I have used Informatica MDM for ten years. I have used Version 8.6 and 9.1 of this solution.

I think that it's a good solution, but it's an old solution. It is stable because we have the experience to deploy this solution.

I think it's based on ODBC drivers, and they are not good for scalability.

We have not contacted customer service.

The initial setup was complex. It must have taken around eight or nine months to deploy all Informatica systems. The deployment processes for on-premise and cloud are different. For on-premise, we must deploy the data models, and then we must deploy the rules. We must also deploy a .Go file extension and an exposition of the vendor code, among other things.

It's different if we have an on-premise solution. The stability is for the on-premise infrastructure. It builds the IT of enterprises of clients because Informatica is at 'Legacy' level.

So, there are plans for licensing. There are subscription-based and usage-based licenses. Also, there are licenses for exceptional analytics, etc. In short, there are different models of licensing for every enterprise.

I think there is a new Jira-driven event, Jira-driven data, for the flows and extensions. So in this power center technology, I think that it's complex to navigate through the solution without new technology. Overall, I rate the solution a seven out of ten.

We use Axon for controlled and governed data sharing as well as for the policies and principles from a data governance perspective. Our use case was for an airport company and we used Axon in tandem with Datacat Log EDC. We customize data search and data sharing. We have a partnership with Informatica. 

The management of the policy is very useful. The ability to customize data search and data sharing is useful. The solution has all the necessary features. 

The GUI needs to be a little more user-friendly and appealing. Salesforce, for example, although in a different category, is very user-friendly and I think if they were to include some of the Salesforce principles, it would be helpful. Informatica needs to do a better job in terms of educating users. 

I've been using this solution for three years. 

The solution is stable and dependable as long as we keep an eye on the servers. 

The solution is scalable. 

The support process needs to be more agile. 

The initial setup took a few days. It wasn't very complex but there were some initial challenges because we were trying to setup the Informatica Data catalog, EDC, at the same time. The deployment was reasonable but not very smooth. We have around 300 users.

Licensing costs are generally on the higher side.

Collibra was a solution we evaluated but Informatica was the final choice.

I rate this solution seven out of 10.

Our organization operates in the financial industry and we utilize the solution to gather and incorporate high-quality data, making it available in the data marketplace.

We are satisfied with the entire solution in its current state and eagerly anticipate its transition to cloud technology.

The tools required to migrate existing mappings and server rules through cloud data quality are not available. Additionally, there is no alert mechanism in place for the existing IDQ that can be integrated with email alerts.

I have been using the solution for over ten years.

I give the stability a ten out of ten.

I give the scalability an eight out of ten.

The technical support responds quickly.

Positive

The initial setup is straightforward. I give the setup a nine out of ten. The deployment took around one and a half hours and two administrators.

The implementation is completed in-house.

I give the solution a ten out of ten.

We have a two-person admin team that takes care of the maintenance.

I would recommend Informatica Data Quality as it has been consistently identified by Gartner as one of the leading solutions in the market.

We use Informatica MDM for master data maintenance across our organization. We have multiple departments, like material real estate, trading, and supply. We use it for consolidation, harmonization, and central master data maintenance. We are also integrating it with the nonrecipient systems.

I like that Informatica MDM has robust matching technology. Informatica MDM is also porting the external Java applications for validations. I can consider that a must-have. It is also exposed to Rest API calls, and we can engage in real-time integrations with any third-party systems.

The configurations could be better. It is a bit confusing because we must develop two tools when building a data model in Informatica MDM. Even though Informatica MDM is a single tool, we have our hub console plus the provisioning tool within that. Whatever data model we are building in the hub console, we have to develop it in the provisioning tool again. It is double the work to create a data model. 

We are also using external calls or the Java custom plans functions. This can be both positive and negative. Since MDM as a client does not support any complex validation, we have to depend on the external call or a Java call. Every time we deployed, the entire solution was impacted if something went wrong. 

I have been using Informatica MDM for four years.

Informatica MDM can be more stable. There are some issues and some crashes, and sometimes, with the data load, we usually feel like we are doing an initial data load for any project. Sometimes, it could also be down to the production environment.

On a scale from one to ten, I would give stability a six.

Informatica MDM is a scalable solution. We probably have 1000 direct and indirect users with multiple use cases. But people solely working with Informatica MDM might be around 200 or 300. Most users are from business IT data support.

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

Technical support is very responsive.

Positive

I was using SAP MDM, which is currently end of its life, so we migrated from SAP MDM to Informatica MDM.

The initial setup is straightforward. We have to make a jar file which we have to download from the link and download it as a client in our local mission. However, there are some challenges if we deploy Informatica MDM with IDQ on-premises. The deployment time depends on the use case. One or two people can maintain this solution.

We have seen a return on investment. From a business perspective, there have been many improvements since we migrated from SAP MDM.

I would recommend Informatica MDM to potential users. Even though Informatica MDM does not come with data quality, Informatica as a whole has some of the right tools. We have embedded the MDM with the IDQ informatic data quality in ways we can interact. It is the best fit for non-SAP systems.

On a scale from one to ten, I would give Informatica MDM an eight.