Design, configure, and complete initial deployment of a Master Data Management (MDM) SaaS solution for a single data domain, focused on modernizing Informatica on-premises MDM capabilities to the Intelligent Data Management Cloud (IDMC) platform.
Build an MDM data model, that includes business entities, their relationships, and a hierarchy structure, along with reference data configuration, page layouts, user roles, data quality rules, and survivorship/validation logic. Match model configuration and tuning will be performed, and approval workflows will be configured, with business events enabled for downstream consumption targets.
Establish initial data migration ingress mappings from existing on-premise cross-reference tables, implement daily incremental ingestion pipelines to maintain data currency across those sources, and configure three egress processes to support downstream consuming systems.
Development occurs in the Customer's Dev environment with completed MDM and integration components promoted to the Customer's QA environment upon completion.
• MDM asset inventory documented
• Modernization plan and level of effort estimates defined
• Modernization approach defined and current state assessment complete
• MDM SaaS solution architecture for a single data domain (e.g., customer, supplier, or product) completed
• Data model translation completed for up to thirty (30) base objects converted to three (3) business entities in MDM SaaS
• Reference data assessment and alignment to MDM SaaS solution architecture for up to sixty (60) reference sets
• Integration dependencies and potential impact to migration documented
• UI assessment completed for up to four (4) business entity views or subject areas, including analysis of data quality rules, Informatica data director user exits, and Entity 360 (E360) external calls that implement UI validation and enrichment rules
• Analysis completed for up to ten (10) inbound data sources for the applicable MDM SaaS solution
• Up to four (4) ActiveVOS workflows and approval processes assessed and prioritized, for modernization
• Up to eight (8) user exits reviewed for functional alignment to MDM SaaS
• Data cleansing and enrichment inventory completed with functional categorization and recommendations for modernization approach
• Technical debt identified along with approach to modernization (replace, remove, ignore)
• Hierarchy design assessment completed for four (4) hierarchies with up to ten (10) relationships
• If applicable, Informatica IDMC modernization tool configured and executed in proof of concept environment
• If applicable, Customer has appropriate full Reference 360 License (SaaS Edition - Reference 360)
MDM SaaS Component Scope:
• MDM SaaS design and configuration for a single data domain
• Finalized design and configuration for up to three (3) business entities from thirty (30) on-premise base objects and up to forty (40) additional attributes
• MDM SaaS data model expanded to include up to three (3) base object relationship table translations
• Up to sixty (60) reference data sets configured and populated for use as MDM picklist attributes (e.g. drop-down lists, look-up tables)
• Up to two (2) MDM BUI page layouts configured per business entity
• Up to three (3) hierarchies with up to five (5) relationships each designed and configured
• Match model configuration completed with two (2) rounds of match tuning for up to six (6) match models
• Standard platform configuration of one(1) approval workflow with up to four (4) distinct processes configured
• Data cleansing, validation, and data quality rules configured for up to twenty-five (25) attributes with up to five (5) application integration plug-in rules
• Trust and survivorship rules configured for up to forty (40) attributes
• Up to fifteen (15) MDM SaaS user roles designed and configured
• Up to ten (10) business events configured for downstream consumption targets
• Informatica IDMC modernization tool steps executed in the Customer's Dev environment
Integration Components Scope:
• Initial data migration ingress mappings from MDM on-premise cross-reference tables for up to ten (10) sources
• CDI ingress configured for daily incremental updates for up to ten (10) source systems
• Up to three (3) egress processes configured from up to three (3) business entities
Promotion to QA Environment:
• MDM and data integration components migrated to the Customer's QA environment
Note: The following are excluded:
• Real-time webservices or Customer application programming interfaces via Cloud Application Integration “wrapper” processes
• Data enrichment to third party applications
• Customizations
- User exits that do not translate to MDM SaaS functionality
- E360 user interface external calls
- Custom workflows
• Quality assurance/testing support for system integration testing, user acceptance testing, performance testing, and regression testing of on-premises functionality
• Production deployment and hypercare support
• MDM SaaS Technical Design Document
• IDMC modernization project mapping files
• MDM SaaS export file of configuration for code migration to QA environment
• MDM SaaS Production Runbook
PSU Catalog
652
MDM Customer 360
MDM Product 360
MDM Reference 360
MDM Supplier 360
Multidomain MDM
Professional Services Units
Configure
Implement
PSU-MDM-097
200+ units
August 2026
MDM SaaS Modernization Pack
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.