Headless Master Data Management Primer

Informatica will work with the Customer to establish a foundational understanding of headless master data management using Informatica's Master Data Management (MDM) SaaS Model Context Protocol (MCP) capabilities.

Key activities include:

(i) Discovery and use case assessment. Up to two (2) one-hour sessions to:

• Review Customer requirements and identify candidate use cases for Artificial Intelligence (AI)-driven master data management.

• Assess use cases involving customer identification, master-record retrieval, customer and organization resolution, golden record access, duplicate prevention, and governed master-data operations.

• Evaluate and confirm the complexity and scope of up to three (3) agreed-upon use cases involving customer, supplier, product, or other master data entities.

(ii) MCP client setup for one (1) client, limited to the following:

• Set up and configure one (1) supported MCP client using out-of-the-box capabilities.

• Establish connectivity to supported Informatica MDM SaaS MCP servers, subject to Customer-provided access and permissions.

(iii) MDM SaaS MCP working sessions: Up to three (3) one-hour sessions to:

• Review supported customer identification and MDM SaaS MCP capabilities

• Demonstrate how AI agents and MCP-enabled applications can identify, retrieve, and access trusted master data records and golden records.

• Review supported read-only operations and applicable controlled write or workflow operations for agreed-upon use cases.

(iv) Architecture and solution guidance, limited to the following:

• Provide guidance on connecting AI assistants and agents to trusted MDM SaaS records through supported MCP capabilities.

• Review considerations for maintaining existing matching, survivorship, security, stewardship, and governance controls.

• Identify authentication, authorization, and human-in-the-loop approval considerations for AI agent-driven master-data operations.

Notes:

(i) Discovery activities are limited to a maximum of two (2) sessions, and MCP working sessions are limited to a maximum of three (3) sessions.

(ii) MCP client setup is limited to one (1) supported MCP client. Custom MCP client development is excluded.

(iii) Informatica will evaluate and confirm the complexity of Customer use cases and determine how many (up to three (3)) will be addressed within the working sessions.

(iv) Informatica will not develop or implement multi-agent orchestration.

(v) Custom MCP server development, extensions, or builds are excluded.

(vi) Demonstrations and assessments will leverage only currently supported, generally available or preview Informatica MDM SaaS MCP capabilities. Development of new MCP surfaces is excluded.

(vii) Write or workflow operations will be considered only where supported by available MCP capabilities and subject to established Customer governance controls and appropriate approvals.

(viii) Customer will provide the required MCP client environment, access credentials, permissions, connectivity, and configured MDM SaaS entities and data required for demonstrations.

(viii) Changes to existing MDM configurations, matching rules, survivorship rules, data models, and stewardship workflows are excluded.