Pega CLM and KYC architecture and implementation
Pega Client Lifecycle Management and KYC uses layers with the aim of maximizing reuse in its architecture. It follows the Situational Layer Cake™ design in which each application is built on features of the underlying layers.
In the following image, click the + icons to learn more about the Pega CLM and KYC layers:
Pega CLM and KYC can manage different commercial segments and different localizations in a single application.
Clients decide, based on their organizational, business, and technology needs, if they want to implement Pega CLM and KYC as a single application that serves all these dimensions or as independent applications that cover the needs in a distributed manner.
For example, the U+ financial institution works in two different segments (Retail and Commercial Banking) and three different locations (Australia, the United Kingdom, and the United States). In this scenario, there are different implementation strategies to consider:
In this model, the application is deployed in a single environment with a unique implementation layer that manages the two segments and the three locations. Regardless of the segment, all cases are stored in a database table (work pool) and distributed to the appropriate teams based on the operating structure. Information and documentation collected for a given customer are available across segments and locations and due diligence outcomes, such as risk levels.
Suppose the customer has restrictions on the storage of their customer data. In that case, the customer might opt for a model with three different servers that are deployed in three different locations or data centers. This deployment gives flexibility in infrastructure but presents limitations when sharing customer information across locations. A server that is associated with one location does not have access to the information that provides the other locations (data silos). Clients can also consider the segregated implementation for segregated business segments.
Clients might also consider intermediate approaches in which multiple applications that are deployed on a single server can serve different business segments or locations. The main benefit of this approach is that customer data is reusable across applications (for example, in risk profiles and documentation). At the same time, there is enough flexibility to manage each of the applications independently.
The preferred and default implementation strategy for Pega CLM and KYC is as a single application. This deployment choice maximizes the reuse of business logic and customer data and simplifies the model in terms of development and deployment.
Check your knowledge with the following interaction: