to display the Ask Oracle window.
The following window is displayed.To configure your transaction monitoring system, follow these steps:
1. Click Open Ask Oracle
to display the Ask Oracle window.
The following window is displayed.
Figure: Application Menu
2. Click Transaction Monitoring Performance in the above menu to display the Configure your Transaction Monitoring System window. The following window is displayed.
Figure: Configure your Transaction Monitoring System
3. Click Start to configure your transaction monitoring system.
Topics:
· Setting up Jurisdiction Codes, Scenarios and Thresholds
· Mapping Jurisdiction Codes to Segments
· Setting up Jurisdiction Codes, Segments, Accounts, Channels, and Limits
· Reviewing your Transaction Monitoring System
This section outlines the steps to duplicate your transaction monitoring system in OFSCA. You'll specify jurisdiction codes or segments at your institution, choose the scenarios that will be monitored, and set thresholds for each scenario.
Figure: Set up Jurisdiction Codes, Scenarios, and thresholds
To set up jurisdiction codes, scenarios and thresholds, follow these steps:
· Click Download SQL Script to download SQL script and execute the script against data in Oracle's Financial Crime Data Model to extract the required data.
4. Click Download Template to download the template and format the extracted data into CSV file.
NOTE:
· You should not modify jurisdiction, scenario_name, and scenario_id in the CSV file.
· If you are not using the default risk tiers (RR/MR/HR) at your institution, each of these thresholds (e.g., Min_Amt_RR, Min_Amt_MR and Min_Amt_HR) should be set to the same value.
5. To upload
the CSV file with the necessary data, simply drag and drop it into the
designated field or click on 
the
icon to open the file selector dialog box and choose the file.
Once the CSV file is loaded, the following window is displayed.
Figure: Uploaded CSV File
NOTE:
You can remove the uploaded CSV file if required by using the Clear button.
6. Click Continue to navigate to the Map jurisdiction codes to segments step.
Or
Click Discard to discard the current activity and return to the Configure your Transaction Monitoring System window. Click Start to start the Configure your Transaction Monitoring System from the initial steps again for configuration.
In this section, you will map jurisdiction codes in Oracle's Transaction Monitoring Solution to segments at your institution.
Figure: Map Jurisdiction Codes to Segments
To map jurisdiction codes to segments, follow these steps:
1. Enter the required name in the Segment field.
Or
Enable the checkbox jurisdiction codes are the same as segments at my institution if segments are equivalent to jurisdiction codes.
2. Click Continue to navigate to the Setup jurisdiction codes, segments, accounts, channels and limits step.
In this section you will configure the various products (accounts and channels) offered to various segments within your institution. You will also specify any limits or restrictions imposed on these products for each segment.
Figure: Set up Account, Channels, and Limits
To set up an account, channels, and limits, follow these steps:
1. Enable the Add default risk levels (RR, MR, HR) to segment names in the template check box if your institution uses Oracle's default risk tiers - RR, MR, and HR and if each customer segment at your institution is mapped to one of these risk tiers.
2. Click Download Template to download the template and populate the template with required data.
NOTE:
· You can update details in the Channel and Withdraw_Limit columns as per requirement.
· Specify the channel name as CASH, MI, and WIRE in the Channel column.
· Withdrawal limits refer to hard limits on how much funds can be withdrawn from an account type through a specific channel.
3. Drag and drop
the CSV file into the Drag and Drop
field or click icon to open
the file selector dialog box and select the required file.
Once the CSV file is loaded, the following window is displayed.
Figure: Uploaded CSV file to Set up Account, Channels, and Limits
NOTE:
· If a channel does not have a withdrawal limit, this can be indicated as NA instead of a number.
· You can remove the uploaded CSV file if required by using the Clear button.
4. Click Continue to navigate to the Create an agent for each segment step.
This section describes how to create an agent for each segment. Whenever a new agent is created, by default, a Human Trafficking (HT) agent is created.
You can create a new agent for the following situations:
· If the expected activity of the segment changes and hence the target amount has to change.
· When the distribution of accounts used by customers in the segment changes and hence distribution of accounts changes.
Figure: Create an Agent
To create an agent, follow these steps:
1. Click Create Agent to create an agent for each segment. The New Agent window is displayed.
Figure: New Agent
2. Enter the Agent Description.
The description can be used to note any specific products or channels the agent has access to. A good description should help you determine if this agent can be reused in future experiments.
3. Select the required option from the Target Account drop-down list. In this example, the available options are RBK, CBK, and RBR.
4. Enter the Maximum and Minimum amount for the segment in the respective fields.
NOTE:
· The maximum and minimum should be equal to amounts that are in the unusual range for the segment.
· To calculate target amounts, see the suggested query in the How to Calculate the Target Amount section.
· Ensure that the Max Target Amount is set such that the granularity (Max Target Amount/20) is lower than any limits that have been set. E.g., if the limit for a channel is $ 10,000 then the Max Target Amount should be lower than $200,000.
5. Enter the amount in the following fields:
§ Average monthly credit amount
§ Average monthly debit amount
§ Peak monthly credit
§ Peak monthly debit
§ High Risk Geography monthly credit
§ High Risk Geography monthly debit
§ Standard deviation of monthly credit
§ Standard deviation of monthly debit
NOTE:
· Historical Activity (per month) field is displayed only if the CIB scenario is loaded in the system.
· To calculate CIB parameter, see the suggested query in the How to Calculate the CIB Parameter section.
6. Select the required Intermediate Account from the drop-down list.
NOTE:
You can create a maximum of four intermediate accounts for each segment.
7. Select the required Distribution percentage from the drop-down list.
The distribution should approximately reflect the product portfolio for the chosen segment. If a segment has more than four products, the four most widely used or four most riskiest products can be considered.
NOTE:
The total distribution percentage of all the intermediate accounts should be equal to 100 percentage.
8. Click Close icon
to close the Intermediate
Account for the segment.
9. Click Add Another to add another intermediate account for the segment.
10. Click Create Agent to create an agent. The following window is displayed.
Figure: Agent Created
Similarly, you can create an agent for the remaining segments.
11. Click Continue to navigate to the Review step.
This section describes how to edit the created agent for each segment if required.
To edit the created agent, follow these steps:
1. Click Edit Agent to edit the required fields. The following window is displayed.
Figure: Edit Agent
2. Click Save Agent to save any modifications made to the agent.
In this section, you can view the uploaded data and created agents for each of the segments.
Figure: Review the System
1. Click View icon 
in Jurisdiction
codes, segments, accounts, channels, and limits
to view the uploaded products and transaction constraints.
The following window is displayed.
Figure: Uploaded Products and Transaction Constraints
2. Click Cancel to exit the window.
3. Click View icon in Scenarios
and thresholds to view the uploaded
scenario thresholds.
The following window is displayed.
Figure: Uploaded Scenario Thresholds
4. Click Cancel to exit the window.
Figure: Review the System
5. Click Submit to configure your transaction monitoring system. This will trigger experiment of type "Initial Set Up" for each of the segments you have configured.
6. Navigate to Experiments tab and you can view the created experiment is in In progress status as shown below:
Figure: Experiments
Once the experiment is completed, the status of the experiment will change from "In Progress" to "Completed". If the experiment has run successfully, the dashboard will be updated as shown below:
Figure: Transaction Monitoring Performance
