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.

It can be used for different kinds of use cases. You can use it for data deduplication purposes for any industry. For example, in the pharma, healthcare, or life science sector, often a lot of medical data gets duplicated across different business functions of the enterprise. As a result, the sales and marketing channels may face a lot of challenges in marketing their medicines to the right physicians. In such a scenario, Informatica MDM could be really helpful in standardizing the data and creating a golden copy of it, which can then be published to the sales and marketing channel so that the sales representatives have accurate data to market their medicine or product. This is one of the use cases.

Its deployment depends on the project and client requirements. I don't have Informatica MDM deployed for my organization. We build solutions for our clients by using Informatica MDM. So, it entirely depends on what a client wants. For some of the projects, it is deployed on-prem, and for some of the projects, it is deployed on the cloud. In the most recent scenarios, it is mainly on the cloud. Informatica, just like other MDM solutions, is also moving toward the SaaS platform. So, I'm sure that going forward, for any kind of project opportunity, we'll be using the SaaS model when it comes to the deployment of Informatica MDM.

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

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

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.

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.

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 have used it to elaborate on a project for Golden Record, for IDQ data quality, and create business cases for the control parties.

Informatica MDM is used for customer affiliations and sites and hierarchy management.

I use MDM to collect customer information and ensure that there is no duplicate information on our system.

We primarily use the solution for tasks such as masking. It's used to mask the customer data.

We use Informatica MDM for various clients for integration, removing duplicates, and centralizing data in one place.

Informatica MDM is used for all data management practices use cases, such as centralized master data, cataloging, and metadata management.

It is generally used for the data integration between multiple ERPs. We have ERPs, and then we have third-party exchanges that sell products. The third parties are partnered up with some of the customers, so they create deeds, and we pull in orders and quote requests.

We're trying to get to the latest version. We're two revisions behind right now. It is a local install. 

It is on-prem, and we're trying to get to all-cloud. We do use the cloud for configuration, but we deploy it to the agents locally. We're using the cloud instance of Informatica to deploy to, and we're currently on Azure.

Primary use case is generally for product items and demonstration. 

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 have worked with two clients implementing Informatica MDM. One use case was for the regulatory master data in big pharma (using multidomain edition), on premise installation. The other installation was related to several data domains implemented using Informatica multi-domain MDM edition, but hosted by vendor.

Each use case is basically based on two pillars, one is MDM tools (for better consolidated integrated master data) and the second pillar is the e-governance (the quality dimension).

You can build something, you can expose it as a service, which can be consumed by anyone. But there is a good benefit that helps us on boarding new applications, having a seamless connectivity between these. Our center which plays a very good role in ATL, also works well. It has an ADT Meta Data Management business glossary, for filing those kind of components, and it helped us in really maturing from a governance point of view and from an infrastructure set-up point of view.

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.

We use this solution for MDM in the commercial sector. I'm a lead software engineer for EPAM Systems.

I use Informatica MDM to align data in my company.

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.

We use this solution primarily for core master data management and deduplication.

Recently, they have come up with cloud versions, which I have not experienced. It's mostly deployed on-premise.

We have a limited number of users who are using this solution and working with the master data.

We have it deployed on the cloud, but I don't think Informatica has been involved much with cloud-based solutions. They have multiple issues, especially related to LDAP and other configurations. Plus, their certified and supported versions are also not what every client has, so they're still evolving in terms of AWS. I don't think they have any support on Azure. They say that for the time being in the Azure setup, you can install MDM the way you would install it on-premise, but we don't have a built-in solution as they have for the on-prem database. That is my understanding for now.

I mainly use it for data management.

Typical use cases for Informatica MDM include consent management (for a large telecom vendor in Australia), master-data consolidation and analytics for vendors, facilitating vendor onboarding, and syndicating and automating global data synchronization networks.

I am not quite sure that the product will be part of our use cases anymore. We started off with it because of the data lineage. In other words, we used it because we also used the older Informatica program and it had been serving a purpose for us as a data management tool. But now we are in the process of developing our own solution for at least part of that functionality.  

We currently plan to keep Informatica MDM, but not for the complete handling of the data analytics. We use MDM for data gathering in big data environments. We start with Informatica and do further analysis outside the product.  

To create and launch new products/services on telecom security.

We are using the product data for building maintenance and item creation, then putting all the structures in for our new e-Catalog launch. It has been performing well.

To cleanse and create standardization third-party data by implementing business rules and Address Doctor.