3 Scenario Threshold Editor

The Scenario Threshold Editor administration tool can be used to modify the threshold values that scenarios use to detect matches.

This chapter provides information on the following topics:

• Scenario Threshold Editor Screen Elements
• Using the Scenario Threshold Editor
• Review Test Scenario Results

When scenarios are created, thresholds are established that enable you to modify the values of these thresholds in a production environment. Once the application is in the production environment, any user assigned the Data miner role can use the Scenario Threshold Editor to modify threshold values of any installed scenario, and threshold sets to fine-tune how that scenario finds matches. Using this tool, you can enter a new value for a threshold (within a defined range) or reset the thresholds to their sample values.

Scenario Editor threshold page can be used for modifying the scenario thresholds and test run the scenario to know the number of matches that are generated through the test run. It can also be used to create a new threshold set based on the already available threshold set to modify the threshold and test the scenario.

A scenario is installed using the sample list of thresholds and values. This sample list of thresholds is referred to as the base threshold set. During deployment, you can create additional threshold sets to support specific business needs using the Oracle Financial Services Scenario Manager application.

Note:

Changing scenario threshold values can generate significantly more or less alerts, depending upon the modifications made. If Anti-Money Laundering (AML) is not enabled, editing of thresholds can be done through scenario manager.

The following subsections discuss features you encounter while using the Scenario Threshold Editor:

For more information about scenarios, refer to the respective Technical Scenario Description document (for example, for anti-money laundering scenario information, refer to the Anti-Money Laundering Technical Scenario Descriptions).

Note:

To test the scenario in the Threshold Editor, run the AAI server using the following command:

Path:"$FIC_HOME/ficdb/bin" ./agentstartup.sh

Threshold Sets

Threshold sets allow you to run the same scenario multiple times against a variety of sources (for example, exchanges, currencies, or jurisdictions) with separate threshold values for each source. For example, you may have a scenario with the base threshold set and two additional threshold sets that were created during deployment. You decide that you need this scenario to detect matches in transactions with a minimum value in US currency, European currency, and Japanese currency. Rather than changing the base threshold set for each situation, you can set the value of the base threshold set to detect US currency (for example, USD 100,000), the second threshold set to detect European currency (for example, EUR 150,000), and the third threshold set to detect Japanese currency (for example, JPY 125,000).

Since threshold sets two and three have only a few fields that differ from the base threshold set, you can check the Inherit Base Value check box feature for those fields that are exactly the same as the base threshold set. This feature associates the threshold values in the threshold set you are modifying with the corresponding values in the base threshold set. This association copies the corresponding base threshold set values to the set you are modifying and automatically updates them if the base value changes (refer to <Scenario–Threshold Set> Area for more information).

You do not have to run all three jobs all the time. Each threshold set has a unique ID, so you can tell the system which set to run and how often to run it. Refer to your scheduling tool’s (for example, Control-M) documentation to sequence these jobs.

Note:

Use the Scenario Threshold Editor to modify the values of existing threshold sets. Threshold sets can be created either through the add new threshold set button or through the Scenario Manager.

Inactive Thresholds

For scenarios to work properly, thresholds that are not being used by a scenario must have their values set to Inactive. The Mutually Exclusive Thresholds and Additional Scenario Thresholds groups of thresholds can have values set to Inactive.

Mutually Exclusive Thresholds

In some situations, scenarios apply the value of one threshold only when the value of another threshold is set to N for no, These types of thresholds are referred to as a mutually exclusive thresholds.

For example, the use of the Included Jurisdiction Codes threshold is contingent upon the value of the All Jurisdictions threshold. The following table shows how mutually exclusive thresholds work in two different situations.

Table 3-1 Mutually Exclusive Thresholds

Threshold	Situation 1	Situation 2
All Jurisdictions	Y	N
Included Jurisdiction Codes	Inactive	North, East

If the value of the All Jurisdictions threshold is set to Y for yes (Situation 1), then the Included Jurisdiction Codes threshold values are not used and have the value set to Inactive. Conversely, if the value of the All Jurisdictions threshold is set to N for no (Situation 2), then the scenario only uses the value specified by the Included Jurisdiction Codes threshold (that is, North, East).

Additional Scenario Thresholds

Your deployment may not need to utilize all the thresholds established within a particular scenario. The mutually exclusive thresholds not used by the scenario are set to Inactive.