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.

Informatica Cloud Data Integration is being used to transform data. Primarily, it is for creating data pipelines.

Informatica Cloud Data Integration is being used to transform data. Primarily, it is for creating data pipelines.

Integration is a valuable feature. Currently, the integration makes our security more robust, especially when compared to IICS, where we would need to make arrangements through native or other ways to handle that, and here using sum up makes our lives easier.

With the solution, we had some issues, and we have every day, and we used to open a ticket. Sometimes, there are data issues and transformation issues. So things are not very mature. They need to improve in the aforementioned areas. We are hoping that it will be sorted out in some time, and we will get to experience a hassle-free life.

My company does business with Informatica. We are using their product. I have been using Informatica Cloud Data Integration for four to five years. I am an end user of the solution. Also, I am using the solution's latest version.

I think they are working. Their engineers are still working on some transformations and some features. It is not as stable as they are thinking, but in the last two years, we have seen good progress. So, we are hoping for a similar thing in the future as well. So it is scalable. But, stability-wise, I think that a more stable version is going to come.

I think it is a scalable product. Around a hundred users are using the solution in my company.

The support is very good. On a scale of one to ten, I rate the technical support between eight and ten.

Positive

So we've got many solutions. Not before going to Informatica, but we were evaluating and working with other sets of tools as well. So, on AWS, it is EMR and Glue. We quite frequently use Glue for data pipelines. We also use SAP S/4HANA for delegation. I like IPC and IICS because I have experience in them for the last fifteen years, and I'm working using the same tools. So, I mean, it is my biased opinion. Otherwise, since I have not caught exposure to the other tools in the market that the people in my company are using in different teams, I don't have much exposure to them. Had I gone through those experiences, I would probably have recommended some other tools as well. Currently, I'm in this industry using this tool only, so I recommend it only for that reason. 

The initial setup was very easy. Currently, we are in a deployment process. We've not yet orchestrated that part, but we are in the process of creating the deployment pipelines.

I have deployed the solution on the cloud. Also, there is no maintenance required for the solution.

Cost-wise, I think it is on the higher side, and that is why we are looking for some better options. Licensing costs are huge compared to other players in the market and for my company.

It's a good tool to start with in the beginning.

The product is maturing and has not matured yet. If I look at the market, there are other tools that are providing this stable solution. I rate the overall solution between five to 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.

Test data management is a common use case. When conducting testing in lower environments, we want to avoid exposing sensitive information. To achieve this, we use Data Masking to modify the data. 

For example, we change personally identifiable information, phone numbers, and emails so that they cannot be viewed. The modified data retains the structure and format but doesn't reveal the actual information.

The tool is mainly valuable for testing teams, as it helps protect sensitive data during testing. It can also be used to mask production data for different users, ensuring that only authorized individuals can access sensitive information. These are the main reasons why we use this tool.

I think there's only one area that could be improved. Currently, when we apply the Data Masking rate, we don't have a way to view the masked data. It would be helpful if there was a feature to allow us to see the actual information.

Once the data is masked, it cannot be reversed. Having the ability to revert it back to the actual value would be beneficial, especially if we need to see the original information. Although our enrollment has decreased, it would still be helpful to have that feature.

I have used Data Masking as part of my work.

Stability is good. It's definitely reliable.

Scalability is good. It's definitely scalable to handle higher volumes across different platforms as well. It performs well in terms of scalability. 

Additionally, when it comes to implementing more source systems, there haven't been any issues.

Our experience with customer service from Informatica has been excellent. They are always available and responsive.

Positive

The initial setup is generally straightforward. However, there can be some challenges during the on-prem installation process, even though we have the steps and prerequisites. Dealing with installation issues is quite common, but overall, it's not excessively complex to set up.

The need for maintenance depends on the team. Sometimes, the solution you configure in the tool determines the level of maintenance required. However, overall, maintenance hasn't been a significant issue.

Overall, I would rate the solution an eight 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.