Director of product management at a manufacturing company with 10,001+ employees
Real User
Top 5
Jun 26, 2024
We use Informatica Axon primarily to manage product attributes with different roles and responsibilities across various business units. This involves complex approval processes and workflows tailored to each business unit. We have four to five business units. Additionally, we perform data quality checks to make sure everything goes through proper authorization and adherence to compliance guidelines. Different teams, including our compliance group and business unit-specific groups, so there are some parallel workflows and nested workflows within Informatica Axon. The platform also enables report generation, email alerts, and other functionalities. We have a small vendor team with expertise in Informatica, but the majority of the involvement (80%) is directly from the client, with only 20% vendor participation.
We use the product to store data. We have established a structured system where we store all relevant information, including donor details, images, and series, ensuring easy accessibility for users.
It is used for our SharePoint data, and it is used for our financial data, so we prepare some kind of data lakes about data. And for a lot of financial things. For example, when somebody has to put the user, like, what we have in your organization. You have a user, and some joint venture partners are there. So, we use it for multiple financial master data. Basically, financial master data, we use it.
Learn what your peers think about Informatica Intelligent Data Management Cloud (IDMC). Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
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.
Regional sales manager at StarLink - Trusted Security Advisor
Real User
Apr 25, 2023
Axon is a tool for data governance that lets you define personas of people who can define policy and implement those policies and have a check on them. So it's part of a data governance solution.
Lead Data Engineer at a tech services company with 51-200 employees
Real User
Feb 14, 2023
Informatica Axon is based on the needs of business people. A business analyst or salesperson would be able to make the most of its features. It is important to have three tools for a successful data governance project. These are Informatica Axon, a data catalog, and data quality. They need to be integrated, whether it is an on-premise or cloud project. The purpose of Informatica Axon is to help us manage our technical metadata and business metadata. Technical metadata is information about our source systems, such as what type of system they are, for example, Oracle, SQL, Snowflake, Cloud; and what data is being extracted from them such as table columns or source systems. Business metadata is information about our data, such as its meaning or purpose. When it comes to business metadata, we can mention that starting from the roles, responsibilities, policies, processes, and whatever the complete organization follows. We can bring all these business metadata, and we can map or tag each technical metadata and business metadata using glossaries. Informatica Axon could be a one-stop shop where we can understand the data. If we want to understand the data, we need to know where it comes from, whether this data can be trusted, whether the data quality is good, and whether this data has access to everyone or whether we are restricting the user privileges. These are the things we'll be considering when using Informatica Axon.
I'm a freelance consultant, so I work for a few different clients on different projects. Sometimes I do system integrations, and sometimes it's more of the deployment of the tool itself. Informatica Axon is mainly used for master data management because it's quite a powerful tool. Lots of clients are struggling because Collibra is not an MDM tool. Azure has some possibilities in the data factory for MDM, but in the end, it doesn't have the engine that Informatica has. I see quite a few clients bring Informatica into the architecture for ETL processes. They use it to extract, transfer, and load data, in addition to MDM, since they're a bit restricted with other tools.
Axon is a platform that lets everyone see all the data assets, business glossaries, lineage, catalog, classification, etc., but the real activities are being done on EDC. We have only been using Axon for a short time in my organization, and we are decommissioning it, but I used the solution at my previous organization for data governance projects. Data owners, software developers, and architects all access the solution. In total, we have around 150 to 200 users on it.
Consulting Associate at a consultancy with 1,001-5,000 employees
Real User
Feb 4, 2022
The organizations I work with often have trouble getting buy-in from business users and understanding how data governance relates to them or where the data lineage is. We use Axon in two key areas. The first is automating data governance processes, policies, and roles in terms of data stewards, data owners, etc. Those process flow charts are typically stored in a PowerPoint, Excel, or board document. Everyone involved in data governance would have to send emails manually and such. Axon allows them to automate all that. So if there's a data owner that needs to update a definition, a request that needs to be flagged, or a data quality error, all that is embedded into the Axon system. That's one reason our clients go with it. The use case is embedding the data or the business glossary into the day-to-day workflow. For example, we could integrate it with Tableau. When people are looking at a Tableau report, they understand exactly what the data lineage is and where this data is coming from. They'll also know exactly what those business glossary terms mean, so they can more accurately interpret and analyze the report.
Data Architect at a retailer with 10,001+ employees
Real User
Top 5
Oct 15, 2021
The solution is typically a bridge between business and IT. You use Axion as a tool for governance within the organization. The business people could use this tool to understand what information is being entered by IT. For example, if I'm an IT guy and if I'm using something called a column name or a table name which could be pretty technical out there, I just say, for example, BT_DT. I understand what BT_DT is, which, in this case, is birth date. That's the table name. However, the business side wouldn't really understand this. Therefore, I could actually tag BT_DT as birth date in Axon and I could relate it to this particular column and then the business side can use it from there. Apart from that, you could define your data governance policies, your workflows, who's going to approve the data, who's going to use the data, and who should be consuming it. It can assure that data shouldn't get out of certain boundaries.
Informatica Intelligent Data Management Cloud (IDMC) offers seamless integration of master data management, data quality, and data integration with a cloud-native architecture supporting multiple data management styles, optimizing data governance through metadata management.IDMC enhances data synchronization and mapping tasks, utilizing a broad range of connectors to interact efficiently with data sources. Its precise address validation via AddressDoctor and intuitive navigation bolster user...
We use Informatica Axon primarily to manage product attributes with different roles and responsibilities across various business units. This involves complex approval processes and workflows tailored to each business unit. We have four to five business units. Additionally, we perform data quality checks to make sure everything goes through proper authorization and adherence to compliance guidelines. Different teams, including our compliance group and business unit-specific groups, so there are some parallel workflows and nested workflows within Informatica Axon. The platform also enables report generation, email alerts, and other functionalities. We have a small vendor team with expertise in Informatica, but the majority of the involvement (80%) is directly from the client, with only 20% vendor participation.
Informatica Axon is typically used for data governance, where we establish policies and business glossaries.
We use the product to store data. We have established a structured system where we store all relevant information, including donor details, images, and series, ensuring easy accessibility for users.
It is used for our SharePoint data, and it is used for our financial data, so we prepare some kind of data lakes about data. And for a lot of financial things. For example, when somebody has to put the user, like, what we have in your organization. You have a user, and some joint venture partners are there. So, we use it for multiple financial master data. Basically, financial master data, we use it.
Our use cases were related to the financial and banking sectors. We created data and transferred it to the enterprise level.
We use the solution for mass data management.
The primary use case is for data governance, data quality, data lineages, and data cataloging.
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.
Axon is a tool for data governance that lets you define personas of people who can define policy and implement those policies and have a check on them. So it's part of a data governance solution.
Informatica Axon is based on the needs of business people. A business analyst or salesperson would be able to make the most of its features. It is important to have three tools for a successful data governance project. These are Informatica Axon, a data catalog, and data quality. They need to be integrated, whether it is an on-premise or cloud project. The purpose of Informatica Axon is to help us manage our technical metadata and business metadata. Technical metadata is information about our source systems, such as what type of system they are, for example, Oracle, SQL, Snowflake, Cloud; and what data is being extracted from them such as table columns or source systems. Business metadata is information about our data, such as its meaning or purpose. When it comes to business metadata, we can mention that starting from the roles, responsibilities, policies, processes, and whatever the complete organization follows. We can bring all these business metadata, and we can map or tag each technical metadata and business metadata using glossaries. Informatica Axon could be a one-stop shop where we can understand the data. If we want to understand the data, we need to know where it comes from, whether this data can be trusted, whether the data quality is good, and whether this data has access to everyone or whether we are restricting the user privileges. These are the things we'll be considering when using Informatica Axon.
I'm a freelance consultant, so I work for a few different clients on different projects. Sometimes I do system integrations, and sometimes it's more of the deployment of the tool itself. Informatica Axon is mainly used for master data management because it's quite a powerful tool. Lots of clients are struggling because Collibra is not an MDM tool. Azure has some possibilities in the data factory for MDM, but in the end, it doesn't have the engine that Informatica has. I see quite a few clients bring Informatica into the architecture for ETL processes. They use it to extract, transfer, and load data, in addition to MDM, since they're a bit restricted with other tools.
I'm a senior architect and we are partners with Informatica.
We essentially use Informatica Axon to set up a data governance framework for a corporation, usually a medium-sized or large organization.
Axon is a platform that lets everyone see all the data assets, business glossaries, lineage, catalog, classification, etc., but the real activities are being done on EDC. We have only been using Axon for a short time in my organization, and we are decommissioning it, but I used the solution at my previous organization for data governance projects. Data owners, software developers, and architects all access the solution. In total, we have around 150 to 200 users on it.
The organizations I work with often have trouble getting buy-in from business users and understanding how data governance relates to them or where the data lineage is. We use Axon in two key areas. The first is automating data governance processes, policies, and roles in terms of data stewards, data owners, etc. Those process flow charts are typically stored in a PowerPoint, Excel, or board document. Everyone involved in data governance would have to send emails manually and such. Axon allows them to automate all that. So if there's a data owner that needs to update a definition, a request that needs to be flagged, or a data quality error, all that is embedded into the Axon system. That's one reason our clients go with it. The use case is embedding the data or the business glossary into the day-to-day workflow. For example, we could integrate it with Tableau. When people are looking at a Tableau report, they understand exactly what the data lineage is and where this data is coming from. They'll also know exactly what those business glossary terms mean, so they can more accurately interpret and analyze the report.
The solution is typically a bridge between business and IT. You use Axion as a tool for governance within the organization. The business people could use this tool to understand what information is being entered by IT. For example, if I'm an IT guy and if I'm using something called a column name or a table name which could be pretty technical out there, I just say, for example, BT_DT. I understand what BT_DT is, which, in this case, is birth date. That's the table name. However, the business side wouldn't really understand this. Therefore, I could actually tag BT_DT as birth date in Axon and I could relate it to this particular column and then the business side can use it from there. Apart from that, you could define your data governance policies, your workflows, who's going to approve the data, who's going to use the data, and who should be consuming it. It can assure that data shouldn't get out of certain boundaries.
We primarily use it as an enterprise-level firewall.
Some of my clients use it as a front end tool for the data quality governing process.