What is your primary use case for Informatica Supplier 360?

I use the solution for financial institutions, where we push our data into the warehouses and analytics platforms. We query the Kafka messaging services and see whatever message we get. We used to take the API responses and load them into different target systems, some cloud-based and some on-prem. For some security reasons, we used to push the data to the on-prem and then the cloud versions.

It improves the workflow.

I use the solution in my company and have worked with two tools from Informatica, both on on-premises and cloud models. I have experience with Informatica Axon, and I have used the cloud services under Informatica CDGC. The use case of the tool is basically in the banking sector. It is used to optimize certain areas of a project. In Europe, we have a GDPR implementation. In the Middle East, there is the Central Bank of the UAE and UAE data protection law. Implementing data protection laws and ensuring that all the policies are enforced for financial security is my use case. I have to make sure the bank or financial institution meets the requirements of the Central Bank of the UAE. Data quality is another use case where my company handles corporate and retail customer data, and protecting their information is known as PII. The tool ensures that the system holds the PII data properly.

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 Data Quality offers functionalities such as profiling and address standardization. It identifies discrepancies in data through profiling, providing statistical insights similar to other data quality tools. What sets IDQ apart is its integration with PowerCenter, Informatica's flagship data integration tool. IDQ includes a developer tool with a wide range of transformations like Cost, Standardizer, and Cleanser, which are essential for data quality management. It operates as a batch-based tool, distinguishing itself in the market. While IDQ focuses on these aspects, it doesn't directly relate to tools like TDM or MDM, which are separate solutions.

We use the solution for data cataloging and lineage.

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

Informatica Enterprise Data Catalog was used by our company as proof of concept for projects related to comprehensive data governance.

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.

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.

Informatica MDM is used for our customers' master data management journey. The solution meets our client's requirements for their customer-supplier or any other entities.

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.

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.

A stand-alone application used for any integration with third party tools, like Oracle, it may be SAP, or it can be their local in-house build, or HRMS. It can be any application from A to Z. But this acts like in the web services.

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.

We use the tool to collect, integrate, and process the data from different sources. Later, we direct the processed data to the required solution for analysis purposes.

It's about mastering various domains. For example, an organization might want to master customer data residing within their IT landscape. This includes all master attributes related to customers, like name, email ID, phone number, address, and potential information like stores they visit. Ideally, if the organization also stores data related to those stores, all that information, files, and everything would be included. So, these master attributes would lie within the MDM system. Here's where things get interesting. I'd bring this data from disparate sources. For example, accounting systems hold phone numbers, email addresses, and maybe even bank information (just an example). But another system, like the ER system, might have different information, like the customer's spouse. So, I'd likely get streams from both these systems, but there might be an additional attribute in the ERP system, like the spouse's name. Now, looking at all these different attributes lying in different systems, one system might have my name as "Raja S.," while another might have it as "Raja Soni." So, the question becomes: are Raja S. and Raja Soni the same person? How do you identify them from these records? They try to match these records based on phone numbers or any other common attribute between the two systems. Then, I would have a complete record in MDM, which is called the "Golden Record" - the single version of truth within the system. Furthermore, MDM can also contain additional attributes that the ERP or accounting systems didn't have. So, imagine ten different applications or data sources feeding customer information. I can gather all of that information and create a single version of the truth for a particular customer within the MDM system. Additionally, if I want my customers to update any information, I can provide a form where they can enrich their data. For example, they could potentially enter their Social Security number (although this wouldn't be common practice). This is just an example of how someone might want to collect this information. So, I can create a form and say, "Okay, can you directly feed this into the MDM system?" This becomes an enrichment opportunity as well.

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

I use Informatica Data Quality to consolidate master data across our organization, ensuring consistent and high-quality data. Combining MDM and data quality features, we address issues like customer data inaccuracies. Additionally, we document business terms in our data catalog for a unified view across the company.

We use the solution for party data management. The tool ensures that the information is the same in every business system so that all the systems have the same view of what parties are involved in an agreement.

I mainly use it for data management.

We use Informatica Cloud Data Integration to migrate to the cloud, upgrade our data warehouse, and implement master data management. It helps us with in-depth analysis, leveraging shared history, and addressing data governance questions.

My company works with our different customers to implement and install the solution.

We use Informatica Axon to make sure our data is in good shape across different apps. It helps us work with clients to set rules for data and keep things organized. For a bank, it makes sure customer info, like contact details, is correct and follows privacy rules. Axon also made it easy for our team to check and trust the data we were using. It is like a tool that brings everyone together and helps us find and use data better.

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.

We use the product for building static and automatic data lineages.

I use Informatica MDM to align data in my company.

A wide range of solutions exist because data is primary, and my company looks over many overall data management solutions, from which Informatica Data Quality becomes one of our biggest priorities.

Our use cases were related to the financial and banking sectors. We created data and transferred it to the enterprise level.

My company does not specifically focus on selling the solution to a particular sector. My company generally sells the solution to various sectors, including manufacturing and finance.

We use it for various use cases, including data provisioning, data validation, continuous monitoring of data quality, and data standardization.

The use cases attached to Informatica MDM may vary for different industries. Suppose I talk about industries related to healthcare and life sciences. In the aforementioned scenario related to healthcare and life sciences, there have been situations where a lot of sales representatives have issues while trying to set up calls with different physicians. Informatica or any MDM solution usually helps people in the healthcare industry optimize their business processes, especially when setting up calls with different physicians. Typically, Informatica MDM helps to reduce the number of duplicate details related to a physician or the data related to a particular organization data so that the sales representatives don't end up sending duplicate call invites to the same physician, especially those physicians who have probably different versions of their own name.

We use the product to define policies and for data discovery management.

We use the solution for mass data management.

We use Informatica MDM to enable the master data for getting the customer's product 360.

We are using it for multiple purposes, such as real-time data integration and data migration. It allows seamless integration of various cloud-based applications and services.

The primary use case is for data governance, data quality, data lineages, and data cataloging.

Data Quality involves quality checks and data profiling. It scans through the data, providing metrics like the number of nulls and unique values. Informatica Data Quality profiles the data.

In my company, we use Informatica Cloud Data Integration because I work in the insurance sector, where we use the tool for data migration from one environment to another. We also use Informatica Cloud Data Integration in scenarios where the clients switch from their legacy system to Informatica Cloud using Azure Synapse, because of which we have to migrate all the data to Azure Synapse.

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.

We use the solution for ETL purposes.

We use Informatica Cloud Data Integration for data integration and building data pipelines.

Informatica MDM is a multi-domain product for any master data management. We could use it for customer master data management or supplier data. Given the nature of the business, we can apply Informatica MDM to master the core data entities within an organization.

We use Informatica Axon for MDM purposes.

We use the solution for data modularization.

I am a consultant and I use the solution to scan databases and lineages for my clients.

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.

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

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.

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.

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

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.

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.

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 used the solution for data storage, and data cleaning to improve data quality. The solution also served as a data lake for reporting purposes.

We use Informatica as our one-stop cloud integration solution. We are connecting two different data systems like SAP or Salesforce, integrating on-site financial data with some applications that process financial information like an ERP to plan budgets and forecast revenue. I'm creating a data warehouse and using that with tools like Power BI to create reports and dashboards.

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.

The primary use case of this solution is to extract technical metadata, tag the data dictionary, and profiling. We also use it for lineage and relationship aspects.

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.

Informatica Enterprise Data Catalog is being used for recording enterprise assets, such as customers' products and vehicles. We a consulting service that provides information on how to enter the catalog or forms to collect the data catalog and enter them into Informatica Enterprise Data Catalog.

We use the solution for Salesforce data integration, multi-cloud approaches and processing bottlenecks. We deploy the solution in a hybrid format.

We primarily use the solution for data integration as well as application integration. Currently, we have a multiple-source system. With Oracle ERP, it's very hard to pull data from Oracle ERP, since it's API based. Therefore we have to make use of Informatica Application Integration to pull data from Oracle ERP. We are pulling our supplier information, customer data, and data for projects related to information.

The client has integrated all their internal systems and external systems using Informatica Cloud Data Integration, including all transactional information for different systems, such as SAP ECC or SAP HANA as a business intelligence suite. The solution is used to exchange data between the invoices in Italy and USA, and to exchange information about materials using all sectors around the world. We use the solution to establish a connection between different systems. For example, to generate payments for different companies such as human services, data warehouses, and external companies.

We are using Informatica Cloud Data Integration in a large organization, and we have customers all across the world. Informatica Cloud Data Integration is for migrating data from a source to a target. The major advantage of working with this solution is that it can handle large amounts of data. The drawback is the performance is a bit slow but it can handle a large amount of data compared to other tools.

We use Informatica Cloud Data Integration because we have multiple sources for data integration, and we transform that data and load it into the database or QuickBooks. There are fewer than 10 people using this solution in my organization. I'm an integrator. I'm working with the latest version. It's deployed on cloud.

We export APIs, and anyone can seek those APIs to have the data for target use cases. We hit the APIs that are exposed by external systems, and we get the data from them and process it. We're using the latest version. It's deployed on cloud. There are about five people who are using this solution in my organization. We chose Cloud API Integration to connect to Salesforce.

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.

The product is used for data governance. It's a tool for data governance, a technical metadata dictionary, and a data lineage repository.

I'm a senior architect and we are partners with Informatica.

We don't use profiling as much, however, we do use it, in certain cases, for profiling. We use the Analyst tool to do out-of-box, high-level profiling of data to see high-level quality of completeness, and uniqueness, et cetera. Mainly, we use the Developer tool to connect to the sources and to write data quality rules.

We use MDM to get more data quality. We are partners with Informatica and I'm a senior technical lead and practice architect.

We are currently working on a project with the Oracle Fusion system, so we have multiple use cases and often need to pool data in different source systems. In the project, we have multiple sources and target systems. Based on the requirements, clients, and what they propose, we need to make decisions or check the technical feasibility of whether it is possible to complete the integration.

We use Informatica Supplier 360 to provide a New Zealand-based national product catalogue for the health sector.