Applicable to Master Data Management (MDM) - Customer 360 or MDM Multidomain (On-premise or Informatica Cloud Hosted Service (ICHS)).
Assess the Customer's existing infrastructure, data landscape, and business readiness for implementation. Review the source system landscape at a high level to understand data origins, key data domains, approximate data volumes, and integration touchpoints relevant to the MDM initiative.
If applicable, conduct a comprehensive review of the out-of-the-box (OOTB) data model to assess any extensions required for implementation.
Hold a workshop to facilitate identification of the Customer's business drivers, data needs, use cases, and functional requirements to drive the implementation.
Facilitate the Customer's development of an initial operating model to drive MDM adoption and engagement, including a business roll-out plan with use cases the Customer plans to address in the first year.
Assess organizational readiness, change management needs, and any regulatory or compliance requirements that may impact the solution design.
The typical workshop schedule is as follows:
• Workshop: one (1) meeting (1.5 hours) - limited up to fifteen (15) people
• Informatica MDM On-Premise/ICHS license and Informatica Data Quality (IDQ) On-Premise/ICHS (if applicable) license procured and made available by Customer prior to commencement (both MDM and IDQ must be On-premise or both must be ICHS)
• Customer to provide documented business objectives and business requirements
• Customer to provide a list of its stakeholders from various relevant departments (e.g., business users, data analysts, data engineers, data architects) and ensure their availability to participate in the workshop, requirements validation and review meetings
• Customer to provide a high-level overview of source systems and data domains
• Customer to provide currently identified priorities and use cases
• Customer to confirm MDM version and license and add-ons in scope (e.g., hierarchy manager, ActiveVOS, provisioning tool)
• Customer to confirm geographies and countries of customer data to determine population file requirements (US or non-US)
• Customer to confirm any known regulatory or compliance requirements applicable to the solution
• Customer to confirm whether an existing MDM or de-duplication system is currently in use
• Customer to confirm planned infrastructure (operating system, database platform, and application server) against the MDM Multidomain Product Availability Matrix (PAM) for the target version prior to commencement (if applicable)
• Confirmation of key business drivers and associated initiatives
• Functional requirements for implementation of one (1) data domain identified and prioritized
• Integration landscape identified and captured
• High-level source system landscape reviewed, including system names, data domains, and approximate data volumes and record counts
• Data model validated against business requirements and objectives and data model extensions documented (if applicable)
• MDM version, licensed components, and add-ons (if applicable) are confirmed and documented; application server platform and database platform confirmed
• Existing MDM or de-duplication tools identified (if applicable)
• Regulatory and compliance requirements captured (if applicable)
• Environment topology confirmed, including number of nodes and server allocation
• High-level infrastructure needs and sizing considerations captured to inform environment setup and installation planning
• Match population file requirements identified
• High-level match and merge requirements identified
• OOTB workflow requirements confirmed
• Infrastructure validated against the MDM Multidomain PAM
• High-level operating structure, including steering and working entities, overall program governance structure, and initial governance processes identified
• Business roll-out plan drafted
• Workshop discussions and observations summary
• High-level architecture diagram
• Data model diagrams (e.g., entity-relationship diagrams)
• High-level data entity inventory and attribute glossary
• High-level MDM Operating Model Document
• Draft Business Roll-out Plan & Change Strategy
• Infrastructure & Technical Readiness Summary (covering MDM version and licensing, server topology (application, ActiveVOS, Elasticsearch), database platform, environment topology, and population file requirements) (on-premise only)
PSU Catalog
144
MDM Customer 360
MDM Multidomain
Professional Services Units
Design
Plan
PSU-MDM-114
101-150 units
October 2026
A la carte
MDM C360 Rapid
MDM Multidomain Rapid
Additional Information
Professional Services Units can be converted into Training Units upon written request submitted to the Customer’s assigned Informatica Delivery Manager. The conversion ratio is one (1) Professional Services Unit to ten (10) Training Units. The converted Training Units can be used for any training currently offered in the Informatica University catalog other than training subscriptions. View available learning paths or log in to browse the full Informatica University catalog at https://now.informatica.com/All-Training-Paths.html. Educational Services are governed by the description and terms at https://now.informatica.com/Informatica-University-Terms.html.