25.10.2013 Views

Automation of SACCOs - FSD Kenya

Automation of SACCOs - FSD Kenya

Automation of SACCOs - FSD Kenya

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

56 • AUTOMATION OF SACCOS: ASSESSMENT OF POTENTIAL SOLUTIONS<br />

ID opportunity Benefit obstacle Change requirement System requirement<br />

2 Use the core system for as many<br />

performance management<br />

and management reporting<br />

purposes as possible.<br />

3 Enable read/write access<br />

between core-system and<br />

stand-alone systems. E.g.<br />

between the core system and<br />

a dedicated credit scoring<br />

application.<br />

4 Allow the system to capture the<br />

outcome <strong>of</strong> business processes<br />

and write to the DB or update<br />

the system. E.g. in the event <strong>of</strong><br />

delinquency the system could<br />

automatically make provisions<br />

and take collections actions<br />

such as sending an email, an<br />

SMS or print letters to be signed<br />

and sent.<br />

Ensure consistency by using<br />

one source for all data and<br />

one system that holds all<br />

definitions.<br />

Reduce effort to produce<br />

reports by eliminating<br />

stand-alone reports<br />

produced in Excel.<br />

Logical connection<br />

between reports and<br />

processes facilitating<br />

identification and execution<br />

<strong>of</strong> necessary mitigating<br />

action, especially if drilldown<br />

capability is provided<br />

through the system.<br />

The main purpose is to<br />

provide a consistent view <strong>of</strong><br />

the members regardless <strong>of</strong><br />

which system is accessed.<br />

By connecting the systems<br />

the manual effort required<br />

to transfer data from the<br />

external application is<br />

eliminated.<br />

Reduces manual effort.<br />

Increases integrity by<br />

reducing manual effort.<br />

Increased compliance with<br />

policy.<br />

Transparency is unchanged<br />

as even if a person does not<br />

execute a task they know<br />

by which rules the system<br />

executes it.<br />

Not applicable. Develop a performance<br />

management approach<br />

(can be as simple as<br />

using e.g. PEARLS in<br />

operations).<br />

Determine who is<br />

looking at what<br />

information when and<br />

why (identify the key<br />

KPIs per role).<br />

The system needs to have<br />

reporting functionality that<br />

is customisable and a user<br />

interface that can be tailored<br />

to each role. Alternatively<br />

provides customisable<br />

templates for each role.<br />

Not applicable. Not applicable. The systems need to be<br />

connected.<br />

The point solution needs<br />

to be allowed to read from<br />

the central data base in<br />

order to ensure that all<br />

basic customer information<br />

is consistent between the<br />

systems. Any updates in<br />

the process should be done<br />

in the core application as<br />

otherwise the stand-alone<br />

would need to be allowed<br />

to overwrite data in the<br />

database which is not<br />

desirable.<br />

The central database needs<br />

to allow the point solutions<br />

to write to specific parts <strong>of</strong><br />

the database and publish<br />

the information with other<br />

customer data.<br />

Accept decreased access. Processes and rules need<br />

to be clearly specified and<br />

documented in order to<br />

adapt the system and train<br />

users.<br />

The system must be closely<br />

configured to the business<br />

processes.<br />

Allow the users to choose<br />

between automatic<br />

postings or prompts to<br />

make a posting.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!