Sei sulla pagina 1di 14

KOMIDA :

Implementing Digital
Microfinance In Indonesia

ADITYA WARDHANA
HENDY LIM
KHOMAS
SRIMIATY BURMAN
► Microfinance : small business & households with no
collateral (not eligible) for bank loans.

► KoperasiMitra Dhuafa (KOMIDA) : 2nd largest


microfinancing institution (MFI), serving low-income
women in Indonesia

► KOMIDA aim to go mobile & digital by end of 2018


(improve efficiency & reliability of nationwide
operation)
KOMIDA SERVICES
► Financial Assistance
► Savings
► Loan

► Non Financial Assistance


► Health Training
► Financial Management
► Funding Education
► Funding Water & Sanitation
► Funding Household Appliances
► Micro-business
Reason for Technological
Improvement

- Efficiency & Effectiveness

- Improve Controls & Reduce


Fraud Transactions

- Competition was heating up with


new Microfinance Institution & mid-tier
bank
- Provide more transparency & data

- Improve accountability (data


collection)
KOMIDA Management Information System
2005 - 2009 ► Paper Based System with excel spreadsheet for data analysis

2008 ► Began developing a Management Information System (MIS)

2009 - 2012 ► Implemented offline MIS (head & field office not yet connected)

► Implemented online MIS (field office had MIS terminal linked to central
2011 - 2013
MIS system)

2010 - 2012 ► Deploy & later cancelled smart card system

2015
► Began project to develop new digital mobile system
Process : Implementing Prodigy In KOMIDA
► KOMIDA explore the possibility for new digital mobile
Enter TBOP : system
Implementing ► TBOP Presented it’s mobile banking system (Prodigy) to
Prodigy in KOMIDA
KOMIDA ► Prodigy was chosen because the features &
functionalities also wireless access for branch offices

► Bogor branch chosen to be pilot site (test findings &


lesson learned could easily applied elsewhere)
Project Scope ► Provide project plan detail at gross level; modules for
& Timeline field managers & officers to be tested on mobile tablets
Process : Implementing Prodigy In KOMIDA

► TBOP study KOMIDA’s process flow, procedures, and


Project
Implementation business policies
: Challenges & ► Develop Field Officers module & do testing in Bogor office
Delays ► Build application forms, do data reliability testing

DIffering ► KOMIDA’s business policies & rules were more complex


Prespectives in compare to other MFI
KOMIDA & ► There are last minute surprise request (new forms)
TBOP ► No fully dedicated staff to the project & financial support
(founders & donors)
► Keeping up the digital age; need vendor whom familiar with
The Road
Ahead : process & products
Securing Quick ► Need to resolve database integration & data
Wins synchronisation issue
► KOMIDA explore the possibility for new digital mobile system
Enter TBOP : ► TBOP Presented it’s mobile banking system (Prodigy) to KOMIDA
Implementing Prodigy ► Prodigy was chosen because the features & functionalities also wireless access for
in KOMIDA branch offices

Enter TBOP : Implementing prodigy


in KOMIDA
People Risk and Process IT, Communication, and Control
Scalability Technology risk
► KOMIDA only look at TBOP ► Internal team does not
presentation, 3 bid quotes understand the database
required to minimise architecture or core banking
subjectivity system from old vendor.
► Wireless access required to Company has no control on
expand scalability of KOMIDA the IT division
operation.
► Bogor branch chosen to be pilot site (test findings & lesson learned could easily
Project Scope & applied elsewhere)
Timeline ► Provide project plan detail at gross level; modules for field managers & officers to
be tested on mobile tablets

Prodigy implementation : project


scope and timeline
People Risk and Process IT, Communication, and Control
Scalability Technology risk
► Imbalance workload ► Utilisation of mobile tablet for
management. Eighty percent training modules for field
of the workload lies with pak manager and officers.
Ade
► Bogor selected as the
headquarter to increase
process scalability as bogor
has 4700 member
► TBOP study KOMIDA’s process flow, procedures, and business policies
Project ► Develop Field Officers module & do testing in Bogor office
Implementation : ► Build application forms, do data reliability testing
Challenges & Delays

Prodigy implementation :
challenges and delays
People Risk and Process Scalability IT, Communication, and Control
► Repetitive request on interface Technology risk
and function from KOMIDA
► Field officer is not using the SOP ► Several errors is occurred, due
to resolve issues to the data is not
► Deviation of data collection synchronized
significantly affect of reliabilities ► MIS system that KOMIDA use is
of data, the detection of such more complex than the
issues and the actual
estimation and only one
synchronization become manual
person is familiar with the
labor and time taxing
system namely Pak Ade
DIffering ► KOMIDA’s business policies & rules were more complex compare to other MFI
Prespectives in ► There are last minute surprise request (new forms)
KOMIDA & ► No fully dedicated staff to the project & financial support (founders & donors)
TBOP

Prodigy implementation : differing


perspective in KOMIDA and TBOP
People Risk and Process IT, Communication, and Control
Scalability Technology risk
► Inadequate manpower leads ► Data transfer from field officer
to system failure. TBOP does to MIS requires special
not dedicated staff for database and cleaner
prodigy. KOMIDA does not ► Minimum using of
really capable with their own communication technology
databases leads to last minute change
► Lack of supervisory during
system transition
► Keeping up the digital age; need vendor whom familiar with process &
The Road Ahead : products
Securing Quick ► Need to resolve database integration & data synchronisation issue
Wins

The road ahead : Securing Quick


Wins
People Risk and Process IT, Communication, and Control
Scalability Technology risk
► Decision maker needs to ► Pilot project selection needs
understand the business to take the member number
process and actual field into account to speed up the
condition IT implementation process
► Vendor selection has to be
more systematic so it can
answer the company needs
Summary
► Lesson learnt from Komida
► Technology vendor selection was done in direct appointment
► Lack of Human Resource who master the database (IT)
► Lack of internal communication which leads to unclear problem
definition at the beginning of the project
► People on the field have not well trained on the SOP and project
standard. Leads to performance deviation
► Synchronization between the old and new system is not running
smoothly

► Reccommendation
► Focus on SOP implementation, Improve form, Invite expert to evaluate
and improve technology.
► iInternal audit needs to be implemented
► Risk division need to be dedicated
► Sustainable training
Thank You!
SOMEONE@EXAMPLE.COM

Potrebbero piacerti anche