Applicable to Master Data Management SaaS – Customer 360, or Master Data Management SaaS – Supplier 360, or Master Data Management SaaS – Multidomain.
Review and evaluate the applicable Master Data Management SaaS (MDM SaaS) solution implementation and recommend improvements and/or corrective actions aligning with Informatica-recommended best practices for MDM SaaS architecture and design.
Provide design options (upon request) to leverage Intelligent Data Management Cloud features intended to improve overall efficiency, performance and Customer experience of the MDM SaaS solution.
The assessment evaluates multiple aspects of MDM SaaS configuration, focusing on the following areas:
(i) real-time and/or batch ingress and egress
(ii) end-to-end business entity and Cloud Data Quality (CDQ) rules configuration
(iii) business application configuration of pages, roles and data access rules
(iv) Application Programming Interface (API) usage
(v) MDM SaaS - Reference 360 integration
• Customer to provide list of pain points or problem areas for consideration during the engagement
• Customer to provide access to the MDM SaaS org with out-of-the-box Intelligent Data Management Cloud ‘MDM Designer’ role
• Customer to provide list of its technical subject matter experts and program/technical leads (e.g., MDM SaaS architects, enterprise architects, platform administrators, Informatica administrators, network administrators,) to participate in the assessment work and provide feedback
• Customer to provide all requirements and architecture/solution design documents needed for the assessment
• Customer to provide any other relevant collateral, as needed
• Current MDM SaaS implementation challenges identified
• Up to four (4) medium complexity Cloud Data Integration (CDI) or Cloud Application Integration (CAI) integrations reviewed for batch or real-time inbound integrations (MDM ingress) (see note below for complexity definitions)
• Up to four (4) medium complexity CDI or CAI integrations reviewed for batch or real-time outbound integrations (MDM egress) (see note below for complexity definitions)
• Business Entity (BE) configuration reviewed and documented, including the following:
(i) data model design for up to two (2) BEs and hierarchies
(ii) one (1) match model per BE and survivorship configuration
(iii) one (1) match model performance evaluation per BE
(iv) CDQ advanced rules and rule logic used in selected BEs
(v) business events and workflow configurations for BEs
(vi) one (1) business application
(vii) custom security roles configuration and BE privileges used in business application
(viii) data and search pages using custom roles used in BE
(ix) up to four (4) API reviews for usage and security (e.g. search/match/create/update/job APIs, API usage best practices enablement)
Note: Complexity definitions for CAI and CDI integrations are as follows:
CAI:
(i) low: basic API calls (simple rest/SOAP calls with static end points and parameters), simple event notifications or alerts without complex routing, simple data handling (no data transformations, minimal parsing), standard automation
(ii) medium: conditional routing, data transformations, error handling (basic error handling and retry), multiple steps in task flow
(iii) complex: multiple application integration orchestration, dynamic API integration, comprehensive error handling, complex data handling (nested JSON/XML) and transformations; streaming/event driven integrations
CDI:
(i) low: direct mapping, basic filtering, basic aggregations, basic data type conversion, no lookups
(ii) medium: lookups, multiple transformations, conditional logic, addition of information to targets, reference tables
(iii) complex: joins, advanced aggregations, data pivoting/normalizer (rows to columns or columns to rows), data cleansing, dynamic mapping, looping logic
• Assessment and findings presentation
• MDM SaaS Technical Wellness Assessment Document
PSU Catalog
46
Customer 360
MDM Multidomain SaaS
Supplier 360
Professional Services Units
Optimize
All Use Cases
PSU-MDM-068
26-50 units
July 2025
A la carte
MDM SaaS Wellness Assessment
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.