1 About this Guide

This guide explains the concepts of Oracle Financial Services Behavior Detection application and provides step-by-step instructions for navigating the Oracle Financial Services web pages, analyzing cases, and researching the business information.

This section focuses on the following topics:

·        Who Should Use this Guide

·        How this Guide is Organized

·        Where to Find More Information

·        Conventions Used in this Guide

Who Should Use this Guide

This guide is designed for the following users:

·        Alert Viewer

·        Mantas Admin

·        Data Miner

·        WLM Supervisor

How this Guide is Organized

NOTE:   

Upgrading customers, please note that the dispositioning of alerts through Alert

Management (AM) is no longer supported. AM is only used for verifying the output

of the behavior detection scenarios and is no longer used for alert review. By using

AM for dispositioning alerts customers will be out of compliance with their support

contract.  

The Event Correlation module in Enterprise Case Management (ECM) should be used to

correlate events from the FCCM Behavior Detection engine or those ingested from external

applications. Customers are required to use ECM for reviewing and investigating alerts.

A restricted use license of ECM is provided with the BDF license which replicates

the functionality available in AM to the best that is currently available within

ECM. Implementations should use the available batch processes to automatically move

Alerts from BDF into ECM where correlation rules will promote them to a case.  From

the case all levels of investigation can occur. If this updated process is not clear

to your implementation team it is advised that you contact Oracle Partner Network

or Oracle Consulting to be trained.

This help set includes the following sections:

·        About Behavior Detection, provides an overview of the Behavior Detection applica­tion, how it works, and what it does.

·        Getting Started,explains common elements of the interface. includes instructions on how to configure your system, access Behavior Detection, and exit the application.

·        Managing Watch List Management, describes the Oracle Financial Services Watch List Management feature.

·        Setting User Preferences, explains how to setup Oracle Financial Services Behavior Detection preferences.

·        Appendix A, Alert Components and Tables, provides the additional information on various com­ponents and tables of Behavior Detection.

·        Appendix B, Business Tabs, identifies the possible business tab pages that the Oracle Financial Services application displays for a specific scenario class and focus type.

·        Appendix C, Using Behavior Detection UI, explains common elements of the interface.

·        Appendix D, Security within OFSAAI, explains how Oracle Financial Services Analytical Applica­tions Infrastructure (OFSAAI) security is used.

·        Appendix E, Calculating Risk, describes how  Oracle Financial Services Behavior Detection appli­cation uses risk calculations as part of managing sensitivity when detecting behaviors of inter­est.

Where to Find More Information

For more information about  Oracle Financial Services Behavior Detection, refer to the following documents:

·        Administration Guide

·        Administration Tools User Guide

·        Configuration Guide

·        Data Interface Specification (DIS)

·        Financial Services Data Model Reference Guides

·        Scenario Manager User Guide

·        Scenario Wizard Configuration Guide

·        Installation Guide

·        Anti-Money Laundering Technical Scenario Descriptions

·        Fraud Technical Scenario Descriptions

·        Glossary

·        lRelease Notes

These documents are available at the following link:

http://docs.oracle.com/cd/E60570_01/homepage.htm

To find more information about Oracle Financial Services and our complete product line, visit our Web site www.oracle.com/financialservices.

Conventions Used in this Guide

Table 1 provides the conventions used in this guide.

Table 1:   Conventions Used in this Guide

This convention. . .

Stands for . . .

Italics

·        Names of books as references

·        Emphasis

·        Substitute input values

Bold

·        Menu names, field names, options, button names

·        Commands typed at a prompt

·        User input

Monospace

·        Directories and subdirectories

·        File names and extensions

·        Code sample, including keywords and variables within text and as separate paragraphs, and user-defined program elements within text

<Variable>

Substitute input value