Informatica Intelligent Data Management Cloud (IDMC) Reviews

It improves the workflow.

In terms of the user experience, it's very Integrated, and the implementation is very fast. You can integrate the platforms for different services to deliver all the banking needs.

It is expensive.

I have been using Informatica Cloud Data Integration for two years.

I rate the solution’s stability a ten out of ten.

The scalability is impressive. Implementing something is easy, and there's no need to wait for licenses or other potential roadblocks. It is a highly efficient and smooth process, which makes it even more appealing.

The main reason for the switch was the cost. IBM solutions are quite expensive, and migrating to the cloud platform is complicated. Another significant expense comes from the database, as IBM typically recommends DB2 when implementing DataStage, and using Db2 can be costly. The company considered moving to a more versatile platform that supports different databases and cloud providers. With IBM, there are limitations, and the cloud strategy is more rigid, which influenced the decision to explore other platforms.

Deployment is straightforward. I have experience implementing the platform for various customers here in Brazil, where I live, and I can confirm that it's quite easy to implement. It takes around six months to deploy.

Data has been migrated from IBM DataStage to Informatica Cloud. In this process, we worked with NextPath MSA, which generated new metadata based on the iDMC platform. After this, the company produced the data, and here at the bank, we are validating the conversion from this process. In some cases, adjustments or parameterization were needed with Informatica to refine the processes. The company is responsible for translating the code and generating the required information for each project. We migrate this to the development environment, then to the test environment for validation, and finally to production, where about sixty percent of the projects are implemented for data integration. The entire process, from creation to production, has taken approximately six months.

We are reviewing all components and executions, and overall, the migration process has been a success, with only minor adjustments. It’s interesting to see how the company has successfully converted the original metadata to the new metadata, showcasing its expertise in the process. We have 40-50 professionals involved.  We have different levels of specialists across various areas involved in this project. For example, we have experts with extensive knowledge of IBM DataStage, others with experience in IBM CA, and some professionals specializing in databases. Each group brings expertise and experience with these solutions, contributing significantly to the project's success.

They do have additional costs in terms of usage.

The bank acquired the platform and utilized almost all its services except MDM. We use APIs, messaging, data governance, and data integration for the enterprise. The platform's full range of services is involved. The combination of data integration with application integration is precious to us. It allows us to acquire information through APIs, treat this information via data integration, and generate files or intermediary databases for future consumption by messaging systems. This type of usage is efficient and straightforward to implement. The implementation and usage are simple and effective for our needs.

In our daily operations, we receive data from external and internal systems for Kuzena and generate information in real-time for various departments within the bank, such as the risk and human resources departments. The platform’s ability to efficiently deliver this information is precious.

When a platform provides data from external systems and other sources, combined with HEP implementation and fast integration, the platform ensures high data quality and the ability to deliver information efficiently. This simplicity allows all departments in the bank to adopt and explore this type of usage easily.

I know of other companies using Informatica Cloud, like Ferrero in Chicago. They used Informatica Cloud for three years but migrated to SAP CPI this year. While I know why they made the switch, it's hard to justify it fully. For context, Ferrara produces candies and is owned by Ferrero Rocher in Italy. The IT team in Italy used SAP CPI for data integration, closing their operations with Informatica products. It's surprising, especially because Ferrero had given us positive feedback about Informatica Cloud regarding usage, implementation, and cost.

Its open platform allows it to connect with everything you need, making it very versatile and efficient for various integrations.

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

The solution helps with cataloging and obtaining the data lineage. Informatica Enterprise Data Catalog also helps in identifying vital datasets, including the critical data elements and cataloging them. In our company, we have to manage the life cycle of the critical data elements and maintain the business glossary.

The definitions of the critical data elements, their linkage, lineage, as well as the relationships are managed using the solution. Informatica has been in the industry for decades, so they are one of the top SMB partners. 

At our company, along with the solution, we also use Informatica Intelligent Cloud Services REST API for app and system integrations in the packaging industry. Of our total portfolio, we integrated applications for about 20%, but we did not have any cloud presence; only a setup application was in the cloud. But for all the on-prem projects, the key components of the customer's product were integrated and governed by using Informatica. 

Data lineage is a valuable feature when, at our company, we design the physical elements and the logical components and need to identify the relation between them. 

The duplicate identification feature for two tickets, synonymous fields, or attributes is another vital aspect of Informatica Enterprise Data Catalog. The categorization of whether data is critical or not in the business glossary is another vital feature of the tool.  

The product is difficult for an untrained professional to operate. Specialized skills need to be acquired by learning the tool and executing it for data operations. Informatica Enterprise Data Catalog needs to be more user friendly, the UI is extremely complex.

For instance, if I have to view the tool, the first deterrent is that it gets highly technical. Thus, a limited number of professionals can understand the tool processes. Unless you are a data professional, it's very difficult to use Informatica Enterprise Data Catalog. The tool operates with Power BI sometimes.  

I have been using Informatica Enterprise Data Catalog for eight years. 

At our company, we haven't faced any downtime or business issues with the solution. The solution allows a limited number of users, so it's easier for the vendor to manage stability. 

I believe the solution is scalable and integrates satisfactorily. Our company was successful with scalability because, for the majority of our applications, where the key data was being hosted, we could integrate the apps quite easily with the cloud.

If Informatica Enterprise Data Catalog is being used, scaling the data up or down shouldn't be a problem. The solution's cloud integrations make scalability easier, unlike the on-prem version, which requires implementing complex security protocols. 

I would rate the customer support a nine out of ten. The product's support team has been highly responsive while solving the issues faced by our organization. 

Positive

At our company, during the product deployment, we had to asses our applications and APIs that would be connected, whether they were available out of the box or not. But the capabilities of customer connections are available with similar tools.

Informatica Enterprise Data Catalog offers custom connectivity. Therefore, the deployment process has been troublesome for our organization except for the mainframe. But as we kept using the tool we realized the integrations could be smoothly completed. At our company, we implement the product if customers are convinced to integrate the tool and make it their central, single source of data management for integrators and technicians. 

The deployment of the solution took more than a year in our organization, which included upgrades, contract renewals, and demonstrations similar to IDMC, provided by the same vendor. For deploying the on-prem version of Informatica Enterprise Data Catalog, a team of five engineers was needed in our company to manage the whole deployment and support process.

A couple of business analysts are needed to gather the users' requirements. Our organization has about ten members who provide on-call support on Informatica for its customers, comprising developers, business analysts, and testers. 

In our organization, we were able to derive about 70% of the critical data lineage. 

It's a costly solution. I would rate the pricing of Informatica Enterprise Data Catalog as six out of ten. 

The automated data lineage feature utilization depends upon the integration, which is why, in our organization, we had all our key applications integrated that derived automated lineages. But there were unknown applications as well, which, due to the lack of integrations, needed to be manually plugged in.

The mainframe integration with Informatica Enterprise Data Catalog is highly complex. At our organization, due to the aforementioned complexity, we had to import all the data of the mainframe into Informatica. If you are able to integrate the tool with your core applications and systems, then the data lineage duration is pretty simple and this structure is the same for competitor tools as well. 

In our company, we might explore in the near future how Informatica Enterprise Data Catalog can assist with AI capabilities. I would overall rate the solution as eight out of ten. To anyone looking to use Informatica Enterprise Data Catalog, I would say if they are willing to understand the company data, then the professional should gather sufficient technical knowledge about the product or take assistance from an Informatica expert because it's not a straightforward tool. 

We use the tool to implement customer, product, and entity masters. We also use TDM to generate synthetic data, but not in real-time scenarios.

It's a multi-domain master data management system. The solution is easier to use compared to the other solutions. The security is good. The governance model is good. All the elements that I expect are available in the product.

The user interface can be a bit more functionality-aligned.

I have been using the solution for the last 15 years.

I rate the stability a nine out of ten.

The product is scalable.

The support team does not provide much support.

Negative

The initial setup was okay. I rate the ease of setup a five out of ten. The tool can be deployed in a minimum of eight to ten months. The implementation requires at least a team of five members. Maintenance depends on the customer's requirements. If the customer's requirements keep changing, we need a team to maintain the tool. Otherwise, one or two Informatica developers are sufficient to maintain the product.

The price is comparable.

All the tools have similar capabilities. There is nothing superior in Informatica. I'm a software integrator. I work for an IT company. I'm not the consumer. I will recommend the product to others, but it depends on the customers’ needs.

If an organization needs a good customer master, product master, or partner master, Informatica MDM will be a good choice. The solution has been in the industry for quite a long time. It has all the elements I look for in a master data management system except for customer support. All other things are fine.

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

We had proof of concepts where certain test cases were given to improve the functionality of the vendor regarding the supply chain.

So, it was a proof of concept. It was not applied in production.

It was just illustrating the capabilities of the platform, and we were comparing it with other platforms.

If we use it comprehensively, we can improve the data quality metrics or KPIs. 

So use as much data as you process, and have a solid strategy in place. If you don't have a comprehensive approach, then you don't draw any benefits or value from such a complicated platform. So, you have to have the objectives very well set up and be part of your daily activities in order to benefit from such a platform.

I like the connectivity and richness of features for the technical team, the maturity of the product, and that it had a cloud version. There is Informatica Cloud, and it is part of the Informatica Cloud platform.

It also has integration with other data governance tools from Infromatic, which is also good. 

It offers integration with some of the latest data platforms, streaming platforms like Kafka, for example. And the setup of the platform is very challenging.

Regarding the cloud, it is deployed in the private cloud of the vendor, so it poses challenges regarding the security of the data and the confidentiality of the data. There was no offering of a cloud version deployable in the client's tenant where all the data would reside.

I used it for a couple of months because it was only demoed for the client.

It is a stable product. 

The customer servive and support could be faster. There is a slow turnaround. 

Neutral

We just compared the data profiling features or data quality features between the tools. There was a rich functionality available in the system, but we did not draw any conclusions regarding how it improved or may have improved.

It was set up by the vendor for the demo. To deploy the Informatica Enterprise Data Catalog, you need at least two admins and architects. 

It enables business processes by providing trusted data that can be integrated into many processes around data.

It's very expensive. It's subscription-based. There are several levels of subscription.

The price is high, but the competitors are even higher and more experienced, like Collibra.

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

I would recommend it due to the consistency of vision and very good integration between different products of Informatica. It offers wide coverage, the widest coverage of technologies from the major players.

I use the solution for preparing the data according to the data quality rules.

The mapping and mapplet features are valuable. The product improves data quality. The processes are running smoothly. The interface is good. Data integration is easy.

I use the solution to integrate on-premise and cloud products. There are issues with connectors to cloud applications. The integration process is not easy. The customer experience must be improved. When we implemented it, we did it with the help of Informatica professionals. I would not recommend them as an implementer. They didn't have any experience. It was very hard. The customer experience was not good. It's hard to understand the new features of the HR list. The tool must have more options for connectors. It is hard to connect to some of the applications. The remediation process is not straightforward.

I have been using the solution for one and a half years.

I rate the tool’s stability an eight out of ten.

I rate the tool’s scalability a six out of ten. It is a bit complex to scale. We have 20 users.

The technical support is not good. The support team must improve the quality of support.

The product is cloud-based.

We got a 50% discount.

We couldn’t deliver the full project. I will not recommend the product to others. Overall, I rate the solution a seven out of ten.

We use Informatica Cloud Data Integration to load data from files to TelSource or Oracle tables. We also apply business rules to transform the data before loading it into the respective targets.

Most of the features are good. The advanced features like task flow and conditional integration are particularly useful. There are multiple transformations we can use in Dashflow, which are beneficial. We don't use features like centralization and data marketing because they aren't relevant to our use case. Our primary focus is on task flow, which allows us to design our jobs and execute them conditionally.

Some features require an additional license, such as Elastic Mappings. Most of the features provided are through Elastic Mappings, not the data integration service which causes restrictions. For example, the recently enabled source partitioning isn't applicable to Salesforce, which we use as our target or source. We primarily seek features that enhance performance for Salesforce and ICS Integration, aiming to reduce job execution time.

We don't have the license for Elastic Mapping, so we can't use that feature. Most of the new features added by Informatica are through Elastic Mapping. It would be helpful to have features like multithreading or partitioning for Salesforce to enhance performance.

I have been using Informatica Cloud Data Integration for five years.

The product is stable.

I rate the solution’s stability a seven out of ten.

20-30 users are using this solution.

I rate the solution’s scalability a five out of ten.

Support is good.

Positive

The initial setup is very easy. When I first started using it, I installed a 30-day trial version. I personally explored it during that period, and it was good.

It takes 30-40 minutes depending on the jobs.

I rate the initial setup a ten out of ten, where one is difficult, and ten is easy.

The team is very user-friendly, meeting our expectations much like PowerPoint does.

It supports integration with most cloud sources, including AWS, and has various cloud connectors. So, It's a good choice for anyone.

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

Informatica Axon is typically used for data governance, where we establish policies and business glossaries.

Users can benefit from Axon's business lineage. Axon has something called Overlay, which can be used to extend the technical lineage. You can also extend it to stakeholders, all the compliance policies, and all the overlaying business rules. All of these can be seen in the same lineage.

I want to get a deeper understanding of the logic that is being used in the ETL. Informatica Axon does not provide complete transparency about the level of detailing you need and the logic used in ETL. I cannot use Google Fusion for ETL because I don't have a connector within Informatica Axon. I am stuck if I don't have a connector with an ETL tool.

One of the biggest disadvantages of Informatica is that it's very expensive. Many clients don't want to go with Informatica Axon because of its cost structure. You have to buy every component separately. If a customer wants governance, they obviously would need cataloging and lineage also.

Other tools like Collibra have cataloging, lineage, and governance in the same package. You don't need to buy them separately. With Informatica, you have to buy Axon for governance and EDC for cataloging and lineage. So, it becomes difficult for customers to pay for every component.

I have been using Informatica Axon for seven years.

We haven’t faced any stability issues with Informatica Axon.

Scalability is not really a factor in data governance because the volume and storage of metadata is not more than a couple of gigabytes.

The solution provides good technical support.

Positive

The solution's initial setup is easy, but you typically need Informatica support to run some of the preliminary tests. I've heard that the solution will be available on the cloud. Once it is available as software as a service (SaaS), you don't need to install it; you only need to configure it.

Typically, it takes around two days for the solution's installation and integration with the entire Active Directory and EDC. Then, it may take another day for testing. One engineer is enough to do all this work.

Only using Axon will not give you all the benefits, but you will see benefits when Axon, EDC, and IDQ are all plugged in together. It is difficult to get benefits from Axon as a standalone solution.

The solution's pricing model is easy, but it is very expensive.

Informatica Axon has a Marketplace that comes at an additional cost. Other tools like Collibra have built-in collaboration features, and you don't need to buy them separately. Collaboration features like collaborating on data sets, tagging them, and making a request are available in the Informatica Axon Marketplace.

It's not difficult to maintain the tool as long as someone has been trained in administration because Axon has many components. You need to understand how to change the logo of your screen size and how to change the dashboard wizard.

You also need to understand the product's configurations with other tools, personalize your dashboard, customize it, and add roles. There is a learning curve there. You need to train a person to be an administrator, and once they are trained, they can do the role better.

There is an NLP enabled with the solution, but it is not really that great. There is still room for growth in Informatica Axon's AI space.

Although expensive, Informatica Axon is very easy to learn, and you don't need to customize it much. Once you have the tool, you start uploading things. The solution is very easy to use because it has proper documentation and user guides.

If you want to set up business rules, Informatica Axon will give you a readymade template and ask you to start filling it out. You will be told about the mandatory and non-mandatory fields, and as long as you understand what the fields are required for, it's very easy to start filling out. Someone new to governance can get the hang of it and easily start filling in the details. You can have Axon implemented very quickly.

I am more involved with governance, cataloging lineage, EDC, and IDQ. I am getting a little bit into master data management and data security.

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

So my use case was on migration.  I've been using these products for migration activities. And providing any QA solution for the integration to other platforms like Databricks.

There are newer technologies in the market that offer better solutions compared to traditional ETL operations. For example, if we use Spark on Databricks, it's more optimized and runs much faster due to its backend capabilities. Whereas Informatica Inc.'s Cloud Services provide cloud-based solutions. The ETL works on the Informatica engine, which is comparatively slow. But the compatibility of data and other integration and data warehouse works well for IICS.

The interface is really good. Another valuable feature is that it is user-friendly.

There are a few improvements which can be done. So those are on data governance and making an image of each object that is being created on top of Informatica, I mean, on top of applications. So those need areas to be improved.

The logging methods are really traditional. So logging, in order to track any operations happening on this interface, will catch a log file. That needs to be more precise.

In future releases as well, I would like to see additional features. So there is no platform where code conversion can happen easily. For example, if you want to move Informatica jobs in various areas, it's quite easy and straightforward. But still, you require some manual intervention for code changes that need to be done throughout the platform. So these things need to be improved. 

And other things are the compatibility of other services. For example, if you have a running Spark code and you want to run the Spark code into Informatica IICS, which is not compatible, so you need to rewrite the whole syntax to make it compatible. So those are the areas that really need improvement.

I have been using Informatica for three years. We currently use the version Informatica Cloud IICS.

Stability is good. I would rate it a seven out of ten. 

Scalability is good since from on-prem to cloud, there's a huge performance boost. So on a scale from one to ten, I would rate it eight.

The setup is complex. Because it's not about the data; it's about the complexity of the pipeline, the complexity of models which have been designed for data engineering. And it's not something straightforward, and the migration cost goes higher on this aspect for this reason.

We have multiple platforms with it. Some of them are running on-prem, and some of them are running on the cloud.

There is definitely an ROI because many companies are preferring to put data in the cloud, and they want to reduce the migration cost. So without any major efforts or challenges in the migration activities, if that's the case, then moving from Informatica on-prem to IICS is a better choice.

Comparatively, other services are providing a lower price, but since moving from Informatica on-prem to IICS, the pricing factor is much better. So when we compare two platforms of the same vendor, it's a good price.

On the evaluation, I have personally evaluated the migration work that I have done. So it is really easy for Informatica users who have been using the same on-prem product. For them, there won't be any challenges in learning any technical aspects of the cloud. So it is almost straightforward. And there are good services provided by Informatica, like integrated things and driver compatibility. So, everything looks much better when it is in the cloud.

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