Automation of SACCOs - FSD Kenya
Automation of SACCOs - FSD Kenya
Automation of SACCOs - FSD Kenya
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Level 1 Level 2 Description<br />
AUTOMATION OF SACCOS: ASSESSMENT OF POTENTIAL SOLUTIONS • 23<br />
Application Usability Generally a logical graphical user interface (GUI) is required and the menu structure needs to<br />
be logical given content and workflow. The screens need to be consistent with regard to layout,<br />
wording, and use <strong>of</strong> colour. Reports need to be available as graphs.<br />
Data Interfaces The system needs to support a multi-branch installation and be tolerant to connection downtimes.<br />
This is especially relevant to enable a network independent <strong>of</strong> where the account has been opened or<br />
the member is domiciled. The system needs to ensure data consistency across all system entities in<br />
different branches and allow for integration between any stand-alone systems in the branches.<br />
Data Interfaces The system needs to support batch report generation and export <strong>of</strong> data to Excel.<br />
Data Interfaces The system needs to allow upload <strong>of</strong> statements and salary lists provided by different banks and<br />
employers.<br />
Data Interfaces The system needs to allow for integration with external systems and specific devices such as those<br />
for capturing fingerprints, point <strong>of</strong> sale (POS) devices, mobile phones to and similar to enable mobile<br />
banking, ATM, Vigo money transfer, and employers’ systems.<br />
Data Interfaces The system needs to demonstrate thorough integration <strong>of</strong> the core functionality for FOSA, BOSA<br />
and the accounting function. Additionally it needs to have an architecture that allows expanding the<br />
system in an integrated design to include functionality for provision <strong>of</strong> PEARLS or CAMEL reports,<br />
credit scoring and human resource management.<br />
Data Data The data model needs to provide a unique member identifier, be based on a single database and<br />
provide unrestricted access to historical data.<br />
Security and control Access authorisation The system needs to provide access rights to users based on value based limits, role and hierarchy.<br />
The system needs to distinguish between read and write access. Access needs to be based on<br />
passwords that follow certain robustness and are frequently replaced. The basis for the access rights<br />
is a user pr<strong>of</strong>ile framework.<br />
Security and control Audit trail and logging The system needs to provide an audit trail and log attempts <strong>of</strong> unauthorised access and session data.<br />
Environment Technology The application vendor needs to have an accurate version control process in place and the database<br />
management system needs to ensure the security and integrity <strong>of</strong> the data. The database needs to<br />
be relational.<br />
Environment Operations The system administrator needs to have access to the database, the source code and have a dedicated<br />
module for administration. The system needs to be robust and ran stably.<br />
Environment Backup and recovery The system needs to support an automated daily backup and have recovery functionality in place.<br />
Documentation and<br />
support<br />
Documentation and<br />
support<br />
Documentation and<br />
support<br />
Documentation and<br />
support<br />
Documentation The vendor needs to supply exhaustive documentation including user manual and technical system<br />
documentation.<br />
Training The vendor needs to provide application training and timely and responsive support,<br />
Support The vendor needs to agree to a service level agreement with the SACCO. The service needs to include<br />
on-site support and troubleshooting severe operational issues or after the implementation <strong>of</strong> system<br />
upgrades, respectively.<br />
Maintenance The vendor needs to enter a maintenance agreement including application support and application<br />
maintenance. Reasonable requirements for new functionality should also be covered.