CCMS Design Document
Author
Ashis KS
Srinivas Pilli
1
Table of content
Key Drivers & Solutions
Scope
Context Diagram
Architectural Decisions
2
KYC – Key Drivers & Proposed Solution
Key Drivers Proposed Solution
Multiple Systems are being used for Processing Single System for processing
BOT functionalities are not working as per business BOT functionalities will be revisited and issues will be
requirement addressed according to requirement
No provision to upload & download documents Upload & Download functionality will be provided
Cards information not available from BPM, Same information will be archived to
EDMS post case completion
Business Rules for automatically identify customer &
BPM will interact with Prime via OMW to fetch Card
non-customer
details
Customer historic documents are not available in the
Customer documents will be fetched from EDMS
system for processing cases
system
Details from swift system are not available in order to
Statements from swift system will be fetched from
investigate the transaction details
DWH
Customer Search based on Name match
Name Search : Will be interacted with DWH based
Arabic & English option missing on BIS portal process ( SPs)
User Interface Look and feel Oracle 11g support Arabic Text and same
functionality will be provided to users
Missing Process Level Audit Trail
Client side Controls from BPM toolkit
FIRCO Implementation
Process level Audit Trail to be implemented
Fields to capture court letter specific information
FIRCO to be implemented
33
Scope – Functional Requirements – CCMS
Functional Requirements
BOT will get the list of Court order cases and Pass those to BPM
BPM will create instances and perform the data gathering from various systems like FLEX, Prime, DWH.
Fetch necessary documents from EDMS based on Customer Id.
Show the attachments that comes from CCMS.
Maker review
Checker review
Additional Data fetch based on demand
Case reassignment
Search Cases
Exception Queue
Send all the data(filled by Maker) to BOT so that BOT can update the Portal.
Archive case specific documents in EDMS.
Microsoft Excel
Worksheet
4
Solution Architecture
5
System Context Diagram
Prime
ails CCMS
c co u nt Det
ate A
1. Login
to the C 8. Upd a ils
CMS t C a se Det
(Captch Application 2. G e
a)
Command Center EDMS
Agent 9. Send Case Documents
4. Account Relate
d Information
OMW Flex
CCMS
3. Customer Search, Customer Details,
Maker Account Details, Islamic Account
Details, Corporate Linked Customer
Details, Customer Account Deposit
5. Data Verification Summary, Freeze and Unfreeze Funds
6. Se
Checker nd E
m ail
s Email Server
g
e routin 7. A
Cas rab
ic Dat
10. Customer Name Search a Tr
an s
Swift Transaction fetch lati
on
Microsoft Azure
Assignor DWH
6
Solution Architecture Diagram
Command Center
Assignor
Checker
Atomic
Maker
Agent EDMS
Email
Transfer Server
Documents
Actors
4. Transfer Get
Send Emails
1. Logs into CCMS Portal 10. Transfer
Documents Documents & 8. Translate
Documents Assignor Checker Maker Microsoft
Create Cases Browser Azure
11. Logs into CCMS Portal Browser Browser
for Freezing
2. Get Case
6. Create
Details and
Case
Attachments
Place / 9. Send Court Letter Process
12. Run BOT
Place / Attachments
BPM
Retrieve
CCMS Retrieve Docs
Docs
13. Get Case 17. Invoke Service
Blue Data to update Status
14.Update Case Micro Services
Prism/RPA (Spring Boot) REST
data and 3. Send Case
Upload docs Data Request for Data
7.1. SOAP/HTTPS
15. Update Final
case Status 7.2. Data Gathering Online
5. Insert Case Data
Middleware(IIB)
MS SQL Server Oracle
Existing Component App
DWH Schema Inserts/Retrieve/Update
New Component (Archival) Case Data Flex Prime
7
Assumptions
Command Center Agent will be available whenever BOT needs to login to CCMS.
After BOT updates the CCMS Portal the case cycle will be over. And that same case can’t be pushed to BPM again.
After completion of process, associated documents with the cases should be purged.
External Portal (CCMS) should be Up and Running on the BOT scheduled time.
Any changes in the Portal leads to change in the code and that will be implemented through Change Request (CR).
Users should have the internet connection as we will be invoking Azure Web service from the User browser
Request type and Request Sub Type - These are the categories available in CCMS to help agents understand the bank's
request. Irrespective of this the business ask is to give them ability to input account information, provide comments and
attachments.
User will need to manually click on the button to freeze or Unfreeze Funds. BPM will create case in EDMs queue for
processing the account freezing request.
8
JAVA Architecture Overview
9
Java Component Layer Overview
Spring Boot framework is identified as the development framework for Java Component Layer
considering ease of use in Java-based applications Development, Unit Test and Integration Test Process
and increased productivity as well as integration with Spring Ecosystem like Spring JDBC, Spring ORM,
Spring Data, Spring Security etc. providing robust application infrastructure.
The main goal of Spring Boot Framework is to reduce Development, Unit Test and Integration Test time
and to ease the development of Production ready applications very easily compared to existing
Framework, besides offering easily scalable and pluggable component architecture. Commercially
available off the shelf plugins to develop and test makes Spring Boot Applications very to develop and
deploy using Build Tools like Maven
The Spring Framework is released under version 2.0 of the Apache License.
http://www.springframework.net/license.html
Commercial support information (https://pivotal.io/support/oss) in case if commercial support is
required, even though spring applications can be supported by experienced java - spring team.
10
High level Application Architecture
Application Server
Spring Boot IOC Container
Front End
Service Layer BO Layer Data Access Layer
JSON
DAO
Service
Service Component
(REST) Spring Data
JSON
Entity
BPM
JPA JDBC
JDBC
DB
11
Integration Architecture
JAVA Layer (Spring Boot Application)
SMTP
Service JMS Automic REST Email
proxy Adapter Adapter Service Component
BPM
Automic
SOAP REST File
Service Service JMS Transfer
Service
DB Enterprise Integration Tier (OMW)
External Systems
12
Thank you
13
