Data mapping
Data mapping in Pega Smart Investigate Agentic Automation™ (SIAA) relies on the Pega Common Data Model (CDM). The CDM provides a standardized integration layer that accelerates implementation and ensures consistency across your solution. This section explains how the CDM structures core entities such as transactions, accounts, parties, and reference data. It also describes how to map your existing data to these predefined models, perform data mapping analysis, use Pega Live Data to simplify integration, and apply data mapping tools to transition from legacy structures to the CDM.
Common Data Model for seamless integration
The Common Data Model delivers a data and integration layer that is easy to adopt and quick to implement. It provides:
- A logical data model that is well documented, consistent, and easy to test.
- Optional physical storage of core entities.
- Standard APIs for data access.
- Common and reusable data views.
- Accelerated implementation of resolution activities designed with Pega GenAI Blueprint™.
SIAA uses the Common Data Model for:
- Transactions
- Accounts
- Parties
- Reference data
Integrate the Common Data Model by completing these steps:
- Review the Common Data Model documentation.
- Analyze your current data landscape and map it to the CDM logical and physical models. Consider:
- Mapping party data to the Service Account model.
- Mapping transaction data to the Transaction and Transaction Module models.
- Identifying reference data requirements, including:
- Swift Bank Identifier Code (BIC) data
- Foreign Exchange (FX) rates
- Supported currencies
- Assess Pega Live Data to simplify mapping System of Record (SoR) data from your integration endpoints to the solution.
- Use available data mapping tools to convert legacy data to the new structure.
This Topic is available in the following Module:
Want to help us improve this content?