Pega Client Lifecycle Management and KYC is designed to be a multidimensional application that can manage different commercial segments and different localizations in a single application.
The customers decide, based on their organizational, business, and technology needs, if they want to implement Pega Client Lifecycle Management and KYC as a single application serving all these dimensions, or as independent applications covering them in a distributed manner.
For example, the uPlus financial institution works in two different segments (Retail and Commercial Banking) and three different locations (Australia, the United Kingdom, and the US). In this scenario, there are different implementation strategies that can be considered:
- Single application
- Under this model, the application is deployed in a single environment with a unique implementation layer that manages the two segments and the three locations. All cases, regardless of the segment, 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, as well as due diligence outcomes, such as risk levels.
- Segregated implementation
- If the customer has restrictions on the storage of their customer data, the customer may opt for a model with three different servers deployed in three different locations or data centers. This deployment gives flexibility in terms of infrastructure but presents limitations when sharing customer information across locations. A server associated with one location does not have access to the information that provides the other locations (data silos). The segregated implementation can also be considered for segregated business segments.
- Hybrid implementation
- The customer could also consider intermediate approaches in which multiple applications deployed on a single server can serve different business segments or locations. The main benefit of this type of approach is that customer data can be reused across applications (for example, in risk profiles, documentation, and so on). At the same time, there is enough flexibility to manage each of the applications independently.
The preferred and default implementation strategy of Pega Client Lifecycle Management and KYC is as a single application. This kind of deployment maximizes the reuse of business logic and customer data, and at the same time, simplifies the model in terms of development and deployment.