ICICI Bahrain — TM Efficacy Engagement

11-week AML TMS efficacy engagement for ICICI Bank Bahrain. 5 workstreams across data audit, coverage assessment, segmentation design, threshold calibration, and rule advisory against AMLOCK.

Active

Start

11 Jun 2026

Target

12 Aug 2026

Duration

61 days (11 weeks)

Week

Week 3 of 11

Days elapsed

15 of 61 days

Days to go

46d

Engagement Timeline

Expected position (25%)

Actual progress (9%)

Project is 16% behind expected pace

At Week 3 of 11, the engagement should be 25% complete. Actual progress is 9%. The gap is driven by 0 issues blocked at ICICI Bank Bahrain, including the engagement kick-off and all 0 required data files.

Delay Attribution

Held by: ICICI Bank Bahrain (Client)

The engagement cannot progress because ICICI Bank Bahrain has not yet provided data access or the 0 required data files. The engagement kick-off itself is blocked pending this access.

0 Data Files Not Received

Expected by Today — Week 3

Based on a standard 11-week AML engagement timeline, the following should be in progress or completed by Week 3. Items still blocked or unstarted indicate a schedule risk.

🟡

Define ongoing data quality controls and produce Sanctions Field Completeness Report

To-Do — behind expected schedule · WS1 · Data Audit

To-Do

🟡

Classify all ICore field gaps by severity and assign remediation routes

To-Do — behind expected schedule · WS1 · Data Audit

To-Do

🟡

Validate inward/outward transaction classifications and product-to-segment mappings

Waiting on ICICI — behind expected schedule · WS1 · Data Audit

Waiting on ICICI

🟡

Assess ICore → AMLOCK data completeness — join keys and residency flags

In Progress — behind expected schedule · WS1 · Data Audit

In Progress

🟡

Engagement kick-off — confirm data access and technical contact

Waiting on ICICI — behind expected schedule · Engagement Setup

Waiting on ICICI

All Tasks (36)

In Progress13

AMLOCK NRISR Transactions

Waiting on ICICI

NRISR Transations

Waiting on ICICI

NRISR Customer Data

Waiting on ICICI

ICORE Transactions Data

Waiting on ICICI

AMLCOK Transaction Data

Waiting on ICICI

AMLOCK Accounts Data

Waiting on ICICI

ICORE Accounts Data

Waiting on ICICI

AMLOCK Customer Data

Waiting on ICICI

ICORE Customer Data

Waiting on ICICI

Identify field-level gaps in ICore — 12 critical TM fields

Waiting on ICICI

Validate inward/outward transaction classifications and product-to-segment mappings

Waiting on ICICI

Assess ICore → AMLOCK data completeness — join keys and residency flags

In Progress

Engagement kick-off — confirm data access and technical contact

Waiting on ICICI

Planned — Not Yet Started23

Engagement close — compile and hand over full deliverable packHighTo-Do20d ago

Final deliverable review session with ICICI Bank BahrainHighTo-Do20d ago

Rule rationalisation — merge candidates and deletion candidatesHighTo-Do20d ago

New scenario design — Anticipated Profile DeviationMediumTo-Do20d ago

New scenario design — Terrorist Financing DetectionHighTo-Do20d ago

New scenario design — Trade Finance MonitoringMediumTo-Do20d ago

New scenario design — Post-STR Enhanced MonitoringHighTo-Do20d ago

New scenario design — NRI Enhanced MonitoringHighTo-Do20d ago

CR-ready modification recommendations — all 13 live rulesHighTo-Do20d ago

Final simulation run — confirm optimal thresholds and produce UAT test casesUrgentTo-Do20d ago

P50–P90 percentile analysis and segment-specific calibration — all 13 live rulesUrgentTo-Do20d ago

Establish performance baseline for all 13 live rulesUrgentTo-Do20d ago

Define segment-specific threshold parameters and produce AMLOCK implementation reportMediumTo-Do20d ago

Define segment flag specifications for AMLOCK implementationHighTo-Do20d ago

Design customer segmentation framework — tiers and cross-border corridorsHighTo-Do20d ago

Smell Test — qualitative sanity check across all 26 rulesishikaHighTo-Do19d ago

Document full configuration of all 13 live rules — Scenario Configuration CatalogueprekshaUrgentTo-Do18d ago

Repeated Alert Analysis — same-rule and cross-rule repeatersishikaHighTo-Do19d ago

Assess design completeness and implementation readiness of 13 pipeline rulesHighTo-Do0d ago

Identify unmonitored customer populations and productsHighTo-Do0d ago

Map all 26 rules against customer segments, products, and jurisdictions — RAG-rate eachUrgentTo-Do0d ago

Define ongoing data quality controls and produce Sanctions Field Completeness ReportHighTo-Do0d ago

Classify all ICore field gaps by severity and assign remediation routesHighTo-Do0d ago

Workstream Status

Blocked

Active

Planned

Delivered

WS1 · Data Audit

Data reconciliation, quality checks, field gap analysis

4 issues

2 in progress2 planned

WS2 · Rules Coverage

26-rule assessment, configuration catalogue, noise analysis

9 issues

9 planned

WS3 · Segmentation

Customer segmentation framework and AMLOCK flag design

3 issues

3 planned

WS4 · Calibration

Threshold tuning, percentile analysis, simulation & UAT

1 issues

1 planned

Advisory / New Scenarios

CR recommendations, new scenario design, rule rationalisation

6 issues

6 planned

Deliverables

Formal deliverable packs and review sessions

2 issues

2 planned

Deadline

12 Aug 2026

46 days remaining

Progress9%

Expected: 25%−16% behind