Configuring operating structure
Before you proceed with the creating of your application, you must configure your operating structure. The operating structure is a tree that represents the business lines, countries, branches, and booking entities that participate in your application, as well as the work groups and work baskets that the application uses to manage and route the work.
Pega Client Lifecycle Management and KYC relies on the Operating Structure model that Pega Foundation for Financial Services provides to define how to route and organize the work within your organization. The model includes two main components:
- Taxonomy – Let users define a template with the different levels (for example, business line, country, branch, booking entity) that your organization manages per business segment. A taxonomy is an abstract view of your organization, a set of rules that define the structure of the actual organization.
- Operating structure – The actual realization of the taxonomy. The operating structure defines the operating model of your organization using the model and structure dictated by the taxonomy, and by referring to specific entities or your organization.
If you installed the Pega FS sample application, you can use the sample taxonomy UPlus Financial Services taxonomy as reference.
- In the header of Dev Studio, click , and select the Taxonomy tab.
- In the View operational structure for field, select UPlus Financial Services and click Submit.
At this point of the process, you do not need to define the whole structure upfront. You can set the focus in defining a base taxonomy and in creating a branch that has at least the first three levels of your taxonomy (for example, organization, business line, and country). You can refer later on to these three entities during the creation of your application. After the application is created, you can add the remaining entities that may have been left outside in this initial configuration.
Depending on whether you are working on a new environment or not, you will be in one of the following scenarios:
- No organization has been created yet – If you are installing CLM/KYC of a fresh environment where no organization was created yet, you will need to create a new one and its taxonomy by following the instructions below (see Creating a new operating structure).
- An organization was created but with no taxonomy – If you are installing CLM/KYC in an environment that already has an organization but which taxonomy was not initialized, you will need to convert the organization and then create the appropriate taxonomy (see Converting an existing organization).
- An organization and its taxonomy was already created – If you already created a Operating Structure for other PFFS application and you want to reuse it for CLM/KYC, you just need to review that its taxonomy and implementation meets your needs. If required, you can make changes as described in Configure your operating structures. Otherwise, you can move on to the next topic.
Creating a new operating structure
The operating structure is an asset that can be shared across different Financial Services applications. Check first if you have the operating structure for your organization already in the system. If you do not have any, you can create a new one by completing the following steps:
- In the header of Dev Studio, click .
- Click New.
- In the Name field, enter a name for the bank. The ID field is automatically populated with a 6-character ID.
- In the Top level class field, enter the class name that you can use to maintain the enterprise class structure.
- Optional: Modify the Calendar and Currency fields.
- Click Submit.
As the result of this process, the system creates a new organization entity Data-Admin-Organization that is ready to sustain a new operating structure. You should now define its taxonomy and its realization – see Defining the taxonomy of the organization.
Converting an existing organization
If there is already an organization defined in your system and you want to use it as the base of your operating structure, you should convert it first.
- In the header of Dev Studio, click .
- Select from the list View operating structure for the organization you want to reuse.
- Click Convert.
As the result of this process, the system updates the selected Data-Admin-Organization so that it can support a new operating structure. You should now define its taxonomy and its realization – see Defining the taxonomy of the organization.
Defining the taxonomy of the organization
Use the Taxonomy tab to set up the blueprint for your organizational chart. The taxonomy chart defines the types of entities that appear in your organizational chart. All taxonomies must contain at least four default levels (Financial Institution, Business Line, Jurisdiction, and Balance Sheet), but additional levels can be created as required.
The following table shows the different levels that can be used to build your taxonomy:
| Level | Examples | Description |
| Financial Institution | UPlus Financial Services | Node that represents the top-level entity (your organization). Cannot be modified. |
| Business Line | Retail Banking, Commercial Banking | Represents the different types of business that your organization manages. |
| Geographical | Americas, EMEA, APAC | Main geographical regions in which your business is present. |
| Jurisdictional | Australia, UAE, United States | Jurisdictions or countries where your business is present and that may have operating and regulatory implications. |
| Balance Sheet | New York, Sydney, Madrid | Branches or booking entities used to commercialize your products. |
- In the header of Dev Studio, click and select your organization.
- Click the Taxonomy tab.
- In the new taxonomy, click Specialize and select the type of business line to create.
- Click Add to assign a new operational level to the business line.
- Enter a name for the new level and select the level type.
- Click Save.
Configure your operating structure
Use the Organization chart tab to define the specific business lines, countries, branches, and booking entities that participate in your application.
Use the Add links to add new nodes to the tree. Depending on where you are in the tree, the attributes that you must provide are different. You always need to provide a name and an identifier. In elements of the second level (business lines), you also must provide the financial business segment for that node (that, in the case of specialized taxonomies, determines the taxonomy under that node), as well as a default calendar and currency.
The system initializes each of the new nodes with a set of departments and work queues. You can use them as they come or modify them as per your business needs.
After a node is created, you can edit it by clicking on the 
icon that appears at the right column of
the list.
Previous topic Defining implementation strategy Next topic Creating the application