17 User Roles and Access

The three basic roles defined in OFS LRM application are as follows:

• LRM Analyst: This user is responsible for defining and maintaining the user interface input parameters and definitions required by the application. This user is also allowed to execute the Runs defined within the application.

  LRM Analyst can define time buckets, business assumptions and Runs with the following access privileges: Add, View, Edit, Copy, Delete, Send for Approval, Make Active, Retire, Approval Summary, as well as execute the Runs created in the application. This user is not allowed to approve definitions. A business assumption or a Run is sent for approval by this user to the LRM approver.

• LRM Approver: This user is responsible for verifying and approving the tasks assigned to and completed by the LRM Analyst. Additionally, this user can execute the Runs created in the application. For instance, this user can approve, and execute a definition.

  LRM Approver can approve business assumptions and Runs defined by the LRM analyst with the following access privileges: View, Approve, Reject, Retire, Approval Summary, and execute the Runs created in the application.

• LRM System Administrator: This user is responsible for ensuring that all inputs required for the liquidity risk calculations have been specified in a functionally appropriate manner, in line with the bank’s liquidity risk objectives. LRM Administrator is responsible for preparing the metadata required for LRM, including access to Application Preferences window. This user is allowed to approve all tasks across functional areas of the Liquidity Risk Management application.

  LRM Administrator can perform the following functions: View, Delete, Send For Approval, Approve, Reject, and Approval Summary. This user is not allowed to perform the following functions: Add, Edit, Copy, Make Active, Retire, and execute the Runs created in the application.

The user roles defined in Deposit Insurance Calculation are as follows:

• DIC Analyst (DICANALYST): This user is responsible for defining and maintaining the user interface input parameters and definitions required by the application. This user is also allowed to execute the Runs defined within the application.

  DIC Analyst can define Runs with the following access privileges: Add, View, Edit, Copy, Delete, Send for Approval, Make Active, Retire, Approval Summary, as well as execute the Runs created in the application. This user is not allowed to approve definitions. A Run is sent for approval by this user to the DIC approver.

• DIC Approver (DICAPROVER): This user is responsible for verifying and approving the tasks assigned to and completed by the DIC Analyst. Additionally, this user can execute the Runs created in the application. For instance, this user can approve, and execute a definition.

  DIC Approver can approve Runs defined by the DIC analyst with the following access privileges: View, Approve, Reject, Retire, Approval Summary, and execute the Runs created in the application.

Note:

• Refer section Approval Work Flow for more information.
• You are allowed to create a user and assign all the above three roles. This user is a Super User.
• For information on how to map a user to a user group refer section ‘Mapping the User to User Group’ in OFS Liquidity Risk Solution 8.0.8 Installation Guide on OHC Documentation Library.