Overview:


The RADAR solution is built to interface with core banking solutions like FINACLE to ensure that corrected data are captured and stored for all regulatory reports and other vital areas which require correct information. The RADAR solution is a breakthrough into real time data capture with core banking applications like FINACLE. Though a nascent technology, its approach is simple and very flexible.

Finacle Operations Covered in Radar

  1. Cash Deposit.
  2. Cash Receipt.
  3. Account to Account Transfer.
  4. NEFT Transaction
  5. RTGS Cheque Deposit.
  6. Account opening Customer creation.
  7. AEasy access to ODBC database fields.

Cash Deposit/Receipt, Account to Account transfer, and Cheque Deposit are attached to the TM menu of Finacle. In this way we will be able to capture all the relevant transactions in one location. Account opening is attached to the OAAC and OAACAU menus Customer creation is attached to the CUMM menu. Cheque Deposit returns on the OCTM menu

Online Data Capture

When a user is capturing transaction, a pop-up form like the one shown here appears if any of the set conditions are met
These conditions include:
When a set threshold is met.
When an identifier or account number or name exist in a watch list table.
When a transaction is suspicious.
When a commit is made, finacle transfers control to Radar for the complete data capture. An existing data is validate while non existing data is captured before control is handed over banck to finacle

Trucations Posting in Finacle

TM Menu Operation for Example The TM menu as mentioned earlier is used for the posting of the following transactions:
  1. Cash Deposit.
  2. Cash Receipt.
  3. Account To Account Transfer.

On commit of the transaction, a pop-up browser will be displayed

Account Opening

A pop-up form will be displayed for both corporate and individual account. All the signatories details will be captured and validated then stored on the RADAR system. In-case customer details already existing in the RADAR system, the existing record(s) are displayed in grid layout for the user to see with override message

Off-Line Data Capture

Adroit Solution Ltd When a user intends to create a new record or modify an existing record, the RADAR central login system is used.
Here users, based on their assigned roles, can create or modify customer records for their assigned branch.

Radar Technical Overview

The software is comprised of two main facets:

  1. The Finacle scripting facet: This handles all that deals with connectivity with Finacle and all the other business processes and customizations. This facet is scripted and open and thus can be modified by the Bank to add or remove restrictions /rules provided that the interface specification is not broken.
  2. The RADAR core which comprises the application server itself. This server is written using JEE and runs on Jboss application server. This server contains the various business and validation rules required for the implementation of the NFIU specification.

Finacle Facets

Adroit Solution Ltd As noted earlier this module or facet contains all the customization required to implement the NFIU specification in Finacle.

There are two main types of operations in Finacle:

  1. Transaction Processing
  2. Account/Customer operation.

Account/Customer Operations

The relevant menus that are affected are: OAAC, OAACAU, and CUMM.

The key script is attached to listen on key commit of the various menus.
The collected information is forwarded to the radar server for further processing.

Radar Core

The relevant menus that are affected are:
OAAC, OAACAU, and CUMM.
The key script is attached to listen on key commit of the various menus.
The collected information is forwarded to the radar server for further processing.

The radar application can be setup to run in its own environment and thus does not intrude on any default settings on the system.

It is a highly scalable application that was written using the JEE framework and is completely a 3-tiered system that can be configured by the bank to suits its deployment options.

It is written using JDK 1.6 and uses the Jboss Seam framework to architect the JEE specifications.