CCBS- DFC Project Status as on 15.05.

2015

S
N
1

4
5
6

Activity
Meeting with ED-DFC

Decision to do GAP Study &

documentation to freeze
requirement as earlier proposal was
in Submitted to DFC in May 2014
Meeting with DFC for discussion
over Requirement document for
feedback, changes incorporation
Finalization of Requirement
Document
Discussion over existing status of
KYC data & General ledger heads
Proposal submission from NICSI

Submission of new proposed

General heads for review &
finalization
8
Proposal acceptance & Fund
submission to NICSI by DFC
9
Finalization of GL Still scope for
modification
10 Review meeting at DFC
11 Field sharing related to GL
Scheme, Customer & Account
details
Activity completed till date by NIC:
1.
2.
3.
4.
5.
6.
7.

Date

Remarks

21.01.2015

Shown Interest to start

Computerisation of DFC by
customizing CCBS
28.01.2015- Interaction with DFC officials to
04.02.2015 understand the working &
documentation of requirement
09.02.2015 Requirement document
-16.02.2015 feedback
20.02.2015

Requirements freezed

23.02.2015

Large gap with existing

customer data
Project proposal submitted
alongwith time and cost
estimates
feedback not received till
28.04.2015

16.03.2015

20.03.2015

DD Dated
15.04.2015
28.04.2015
30.04.2015
06.05.2015

NICSI accepted the payment

& opened project on 07.5.15
GL head and related code
generation
Next meeting date 18.05.2015
DFC has to analyze their data
as per the required fields

Requirement understanding & documentation finalization

General Ledger Head finalization & code allocation
Data study of customers
Preparation of data capture Tool Software (for Customer & Account data)
Login system to application
Define User profile & roles
Preparation of DFC-CCBS Application (customer creation Individual + Firm &
account creation)

Activity Pending by DFC:

1.
2.
3.
4.
5.
6.
7.
8.

Existing data study & related data collection & migration strategy
Data Readiness & check
Process re-engineering / changes required considering centralized CCBS
Module wise testing & Acceptance as per requirement document
Functional / logical clarity as applicable
Trail balance & other Cross reference document for data audatibility
Guideline formulation for missing/ambiguous information e.g. mis-match account
Readiness Hardware & Network at DFC level