Oracle FLEXCUBE · GAP analysis

FLEXCUBE GAP analysis: find out what the target version already covers.

A Fit-to-Standard analysis, module by module, for a new implementation or an upgrade. Your scenarios run on the target environment, and every requirement gets a status and evidence.

Build your scope ↓
weeks for a typical scope
6–8weeks for a typical scope
weeks for an express assessment
2–3weeks for an express assessment
streams in parallel
3–4streams in parallel
statuses in the GAP register
6statuses in the GAP register

Why the GAP analysis comes before the estimate

An upgrade estimate is only as good as the list of what has to change. Documentation says what a release can do. It does not say how it behaves with your products, your settings and your exceptions.

So we check the standard in practice: the bank's own scenarios, reproduced on the target version, with postings, statuses and the end-of-day result recorded as evidence. The outcome is a register the bank can decide on.

Build your scope

Pick the modules in scope

Your scope5module streams selected

A typical scope: plan 6–8 weeks with 3–4 streams in parallel. If you only need the main risks first, an express assessment takes 2–3 weeks.

* Working days of one stream, sessions and documenting included. Streams run in parallel, so the days do not add up to calendar time and are not person-days.

Plan by scope

How long it takes depends on what you bring

Work / week12345678

Typical scope shown. Pick a row to see what happens in it.

Typical scope6–8 weeks

About 8–10 module groups of average complexity, current and target configuration available, 3–4 analysts in parallel, owners who answer within 2 working days.

Module sessions

2–3 sessions of 90–120 minutes per module. The bank shows the real operation and the analyst reproduces it on the target.

Inside one module

Five steps, one business scenario at a time

03
To-Be on the targetThe analyst reproduces the scenario on the target version and checks postings, statuses and the EOD result.

Beyond the normal operation: rejection, cancellation, correction, boundary dates and exchange with other systems.

The GAP register

Every requirement ends with one of six statuses

Open

Not enough data yet. It never counts as Fit, and it gets an owner and a date to close.

Example entry (illustrative)TD-014

Requirement: block closing a linked account while an active deposit exists.

Evidence: scenario TD-07, exact release, setup and test record.

Status: Open

What the bank receives

  • Fit / GAP matrix by module, with test records
  • Agreed To-Be processes, accounting and integration changes
  • Prioritized backlog with owners, dependencies, effort by role and a budget range
  • Implementation plan with stages, risks, migration reconciliations and the basis for SIT / UAT

After the analysis

The results support a decision: launch the programme, study some blocks further, change the scope or postpone. Approving the analysis does not close the GAPs or replace system acceptance. Development, SIT / UAT and migration are planned separately, and there is no obligation to continue with us.

Free guide · DOCX · fillable Word file

FLEXCUBE Upgrade Assessment Questionnaire

30 questions with ready answer options that score your bank's readiness for a FLEXCUBE upgrade — a fillable Word file to complete with your team before the assessment workshop.

Get the guide →

Frequently asked questions

More FLEXCUBE services

Start with the scope

Send us the versions, the modules in scope and when a test environment can be ready. We will come back with a plan for the analysis.