2 About Oracle Financial Services Enterprise Case Management

This section provides a brief overview of the Oracle Financial Services Enterprise Case Management (OFS ECM) application.

Enterprise Case Management (ECM) supports the investigation and resolution of Anti-Money Laundering (AML), Know Your Customer (KYC), Customer Screening (CS), Studio (STDO), and third-party events. A newly created case passes through various statuses as part of the investigation and reaches closure through resolution actions. Enterprise Case Management supports the modification of the case details and the associated business data.

Investigation workflows can vary based on the type of case being investigated. The case investigation and resolution are supported by various actions, which can be specific to the case type. Access to types of cases and actions are controlled based on the user role and access privileges. Cases are generated from various sources and cases are also manually created in the ECM.

ECM supports product default case types that drive the Investigation workflow. Case types are configurable and can be defined by firms to meet their business need. ECM allows designing workflows using the Processing Modelling Framework.

Figure 2-1 ECM Work Flow

This image describes the ECM Work Flow.

The following sections describe the Administration and Configuration Activities.

Loading Data

Data is loaded from the landing area to the consolidated area in the ECM using processors and they are called connectors. The connector processes are used to bring the data from sources such as Oracle Behavior Detection (OBD), Oracle Know Your Customer (OKYC), Oracle Customer Screening (OCS), and third- party application to ECM. These connectors are used for event processing. For more information, see the Loading Data section.

Correlation

After the event data is loaded from OBD, OKYC, OCS, or third-party applications into ECM, you can correlate event-to-event based on business entities using configurable rule sets. This functionality is performed by the event correlation process. The group of events is identified for correlation-based on business entities in an application (BD, KYC, CS, or third-party). For more information, see the Configuring Correlation section.

Scoring

Scoring is a methodology to score events, correlation, and entity (customer or account). Every event that is correlated is scored. Initial Scoring and Adjustment Scoring are two methods of scoring. Event Scoring, Entity Scoring, Correlation Scoring, Pre-case Scoring are types of scoring. Inline Processing Engine (IPE) is used to configure scoring rules. For more information, see the About Scoring section.

Promoted to Case

Post scoring, the pre-case that crosses the promote to case threshold is promoted to the case. Hence, the case is created for analysis. For more information, see the Promoting to Case (PTC) section.

Processing Modelling Framework

The Enterprise Case Management Processing Modelling Framework (PMF) facilitates built-in tools for orchestration of human and automatic workflow interfaces. This enables the Administrator to create process-based ECM. It also enables the Administrator to model business processes and workflows.

Workflows created using the PMF are available in the Case Designer for the Administrator to associate with any Case Type. For more information, see the Configuring Processing Modelling Framework (PMF) section.

Case Designer

Case Designer allows the Administrator to configure Case Class, Case Type, and associated definitions. Based on the configuration, definitions are dynamically rendered in the Case Management application to investigate cases and take appropriate actions on them for case resolution. For more information, see the Managing Case Designer section.

Case Action Settings

Case Action configuration allows the Administrator to add new case statuses, configure case action data, configure standard comment data. The Administrator can configure whether or not the case actions require a comment, a reassignment, or a due date. For more information, see the Configuring Actions section.