I use the solution for enterprise-wide data discovery and traceability, providing business context to data and collaboration between different stakeholders of data.

My organization, being a service provider, uses the product to develop domain PoCs, customer PoCs, develop data management and governance use cases, etc. The major issue with enterprises are the ability to quickly develop an MVP and showcase it to business and other data users for greater buy-in. This is important as these are new technologies - and hence, users might not easily adopt.

We were trying to publish a compendium of all our various assets using an Oracle-based data warehouse. We also had vendor-based solutions like Epic for electronic medical records on an SQL Server base. We had many research systems on various platforms because it's a cancer research institution. 

We wanted to pull together a comprehensive data catalog to show people all the different assets we had and where they could go to find things. If there were vendor-based definitions of things, we'd pull in the definitions and various attributes. It's a heterogeneous environment data-wise. We get a lot of value from a comprehensive enterprise catalog.

It's available on our intranet through a data governance portal. You could go there for a catalog, quality reports, etc. In a year, there may have been 500 unique visitors. It was my job to publicize it, but I didn't necessarily do a good job. I worked with research groups and clinicians to get their stuff on it, and they would tell other people about it. The nice thing about Informatica is that it was easy to link from our internal web portal to their catalog. I had excellent developers working for me. It didn't require much development, and it took less and less as time went on. 

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.

I use Informatica Enterprise Data Catalog for searching for PII data, tagging different kinds of data, and for data lineage.

We are using it to understand the assets that we have from their technical metadata perspective, but we're also using it to align our business glossaries with the actual physical data location where the data is stored. Using their Claire or AI engine helps facilitate that. We've been doing that for a while.

The other thing we're trying to do is extend that metadata capability to include extended lineage and provenance attributes. We're trying to incorporate those into the existing EDC environment, and hopefully, when we get Axon, we'll try to figure out how we would expose that to the customer. We will figure out whether we're going to expose that directly or whether we're going to have to augment Axon with an additional UI layer.

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.

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

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

We primarily used the solution because we wanted to be aware of metadata management solutions for our Data Lake, in order to manage the assets in the Data Lake and also to manage the ETL or the data ingestion into the Data Lake.

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

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.

We used Informatica Enterprise Information Catalog to find hidden data assets in our organization. We have data spread across disparate systems like Oracle, SQL Server, Teradata, Redshift, mainframes, etc. Informatica EIC has connectivity to a surprising number of systems and we use this to our advantage creating connections to most of our data sources. We used a 40 node hortonworks cluster and ran the scanners to crawl through our data swamp. It has ran for three days now and we have a fair understanding of our data sources.