Rsmart Biz Functional Spec (Phase 1)

GROOMING PEOPLE FOR BETTER
LIVELIHOOD
LAGOS, NIGERIA
Functional Specifcation
Rmsart Biz Upgrade
December 2021
GC RSmartBiz Upgrade
DOCUMENT PURPOSE
Document Purpose:
DOCUMENT CONTROL
Document Title: GC RSmartBiz Upgrade
Document ID:
Document Version: 1.0
Effective Date:
DOCUMENT PUBLICATION HISTORY

Document Prepared By: Chukwuemeka Louisa (Head, Digital Operations)
Document Reviewed By:
Document Approved By:
Initial Release Version:

Initial Release Date:
DOCUMENT REVISION HISTORY
Versio Change Change

Description Revision Date
n Author Approver
DOCUMENT DISTRIBUTION LIST

Name Name Organization Purpose
Copyright (C) 2021: Proprietary and Confdentiaa

i|Page
1. INTRODUCTION
3.1.
3.2. Grooming Centre seeks to increase the efciency of our products
and services through automation and digitalization. This is aimed at
expanding our fnancial services to New Client Segments such as
Entrepreneurial Youths, who are digitally-savvy and also improve the
existing customer’s experience by leveraging on the existing digital asset
(RSmartBiz) to introduce efciencies and value -added services for existing
customers.
3.3.
1.1. Preambles
3.4. RSmartBiz Software is a Point of Sale (POS) Inventory Management
Platform, which was commissioned as a MasterCard Center Sponsored
project. The major components of the platform are:
 A mobile POS application that was designed to run on smartphone

hardware as well as tablets.
 A back-ofce platform that provides core back-ofce functionality as well
as associated business rules to guide the operations and data gathering
capabilities of the overall platform.
 An optional Bluetooth printer used to generate receipts.
3.5.
3.6. Platform Features
3.7. The RSmartBiz Software was designed to have two modes of
operation:
 The Mobile app (With an Ofine Capability): The mobile app can run on
both android tablets and phones.
 The Web Platform
3.8.
3.9. User 3.10. The platform allows for User authentication and
Authentication role based management and also allow ONLY registered
and authorized members access to the application.
3.11. Paymen 3.12. Incorporation of payment channels with the option
t Channels of Cash, QR code or MPOS. Multiple store locations with
their associated POS devices can be created and the POS
device can be monitored & tracked
3.13. SMS 3.14. SMS sent to the market women on the handheld
device while also having the option of using a mobile app
integrated feedback system to interact with them.
3.15. Inventor 3.16. Each inventory item contains the cost of the item,
y Items and the planned selling price (Last Price). This planned
selling price is editable at the point of adding items to the
cart.
3.17. There is also an option of attaching
pictures/images to all inventory items.
3.18. Back- 3.19. To ease the process of on-boarding new
ofce Module shops/merchants (market women), the back-ofce
module should incorporate some lists of predefned
shop/merchant categories and predefned inventory item
categories which can be quickly applied to a new shop at
the point of set up
3.20. Multiple 3.21. The mobile app has multiple shopping cart

2|Page
Shopping Cart capability and also allows for the continuity of unfnished
sales.
3.22. Each shop/merchant have ability to add multiple
staff (employees) and shops.
3.23. Total 3.24. The mobile app dashboard shows the total sales
Sales View for both previous and current day, while the back-ofce
dashboard shows the total sales for all devices attached
to each shop/merchant.
3.25.
3.26. The dashboard includes flters that enables the
viewing of sales for today, yesterday, this week, this
month, date range, sales by employees, sales per
shop/merchant, etc.
3.27. Loan 3.28. The mobile app includes a loan calculator option in
Calculator its main menu. Which is used for calculating the initial
repayment amount and monthly installment as applicable
to the different Loan Products
3.29. Reportin 3.30. The platform has a robust reporting system that
g and Analytics shows sales, volume, location, number of employees,
Capabilities purchases, items on high demand, and sales growth
among others. They include:
 Daily and Weekly Sales Summary,
 Daily and Weekly Top Selling Items,
 Low Stock Items,
 Weekly and Monthly Sales Charts,
 Daily Sales Report,
 Monthly and Quarterly Sales Summary,
 Stock Items Listing Report,
 Items With Irregular Cost/Price Ratio Report
 Daily POS Device Logs
3.31.
3.32. The Reporting capabilities have the ability to
export in pre-defned format (Excel/CSV).
3.33. Location 3.34. The mobile app has a location service to help show
Service shop/merchant distribution on a map
3.35. Integrat 3.36. The integrated feedback system includes the
ed Feedback ability to solicit the shop/merchant for additional
System information like number of staff, etc.
3.38. The mobile app includes the following options:
3.37. Receipts
Receipts, Tax, and Discounts
, Tax, and
Discounts
3.40. Printing capability extended to new, old receipts
3.39. Printing
and refund receipts as well as low stock items
Capability
 Inventory and Product Management,
3.41. Miscella
 Back-Ofce Web Client
neous
 Notifcations
 Live Chat and remote assist capabilities
3.42.
3.43. Pending Tasks
1. Allow for partial payment/credit sales.
2. Implement a Warehouse module for some stores that maintain a separate
warehouse from where goods are taken to main store (example Bakeries).
3.44.

3|Page
1.2. Objectives
3.45. The goal of this project is therefore,
 To re-introduce and customize the RSmartBiz Platform to appeal to
more customer segments such as the Micro Loans, SME, Public Sector
etc.;
 Provide customer self-service tools, particularly for loan applications,
repayments or non-fnancial services;
 Integrate the RSmartBiz Platform with the Branch Process Automation
(BPA) platform so as to leverage on a centralized database.
3.46.
1.3. Outcome
3.47. It is expected that the upgrade of the RSmartBiz Platform will
provide the following outcomes:
 Provision of online avenue for secure loan application, application
processing, and acceptance notifcation,
 Links to accept loan repayment via Online Banking and Automatic Teller
Machine (ATM).
3.48.

4|Page
2. BRIEF DESCRIPTION OF THE SYSTEM

3.49.
3.50. The RSmart Biz Platform (hereafter the System) shall:
a. be a cloud-based solution;
b. have a responsive web-based platform for loan origination to streamline the
sourcing, processing, approval and monitoring process of loan;
c. also have an app-based tablet/mobile solution for loan origination and processing
by repeat client or existing users;
d. be interfaced with the tools like predictive analysis, scorecards, identity validation,
business analytics, algorithms etc.
3.51. Assumptions
a. Grooming Logo would be used for the web and app version
b. Grooming Color (color code: #ac3973) would be used for the web and app version
c. Notifcations: The solution should have the ability of Notify concerned borrowers at
every stage of the loan application process.
3.52.
3.53. Sub-systems
3.54. The System shall include, at least, the following sub-systems:
a. Staff Management
b. Data Entry
c. Reporting
d. System Management
 User Management Module
 Administrative Module

5|Page
3. FUNCTIONAL SPECIFICATION
3.55. Staff Management Sub-systems

3.56. The system shall implement a staff management module identifying to
whom various Loan Portfolios are assigned. The module shall allow the system
administrator to add, update or delete the information about the staff, including
his/her name, department, branch feld ofce, etc. This information shall allow the
system to track the current working staff at Grooming Centre and prevent
assigning Loan Portfolio to non-working staff.
3.57.
3.58.
3.59. Field Name 3.60. Description
N
3.61.
3.62.Staff ID 3.63. GC Staff ID
1
3.66. This feld should be a pre-defned feld.

3.64. The System shall allow for DESIGNATIONS
3.65.Staff Designation
2 to be maintained as parameters
3.67.
3.68.Surname 3.69. Last Name of Staff
3
3.70.
3.71.First Name 3.72. First Name of Staff
4
3.73.
3.74.Gender 3.75. Male or Female
5
3.76.
3.77.Mobile 3.78. Mobile Numbers
6
3.79.
3.82. Staff Email (Validate with
7 3.81.E-mail
‘@groomingcentre.org’)
3.80.
3.83. 3.84.Branch 3.86. This feld should be a pre-defned feld.
8 The system shall allow for BRANCHES to be
3.85. maintained as parameters.
3.87. 3.89. This feld should be a pre-defned feld.

3.88.Department The system shall allow for DEPARTMENTS
9
to be maintained as parameters.
3.90.
3.91. Data Entry Sub System

3.92. The proposed system should provide a responsive web portal as well as a
tablet/mobile application for repeat clients or existing clients for loan origination
and processing, which shall comprise of the functionalities including, but not
limited to:
3.93.

6|Page
3.94.
Copyright (C) 2021: Proprietary and Confdentiaa 7|Page

3.95.
The proposed system shall have the Core Features as depicted above:
 Homa Page
 Dashboard
 Profle Management
 Notifcations
 Inventory
 Statements
 Loan Management
 Complaint Management
 Help (FAQ/CONTACT US)
 Log out
3.96.
3.97. Note: Data Confdentiality Clause displayed on each page.
3.98.
3.99. PROJECT PHASES
3.100. The proposed system will be implemented in three phases:
 Phase 1 - Existing Clients
o Web Version
3.101.
 Phase 2 - New Clients

8|Page
Web Version
o
3.102.
 Phase 3 - New/Existing Clients
o App Version
3.103.
3.2.1. HOME PAGE:

3.104.Web Version
3.105. The frst step in performing any operation within the RSmartBiz System is
to log on to the system. For the web-enabled version, the correct URL needs to be
specifed and the system displays the CLIENT LOGIN Page.
3.106.
3.107.APP Version
3.108. The frst step in performing any operation within the RSmartBiz System is
to log on to the system. The App should be downloadable from a Play Store; after
which it can be clicked to display the CLIENT LOGIN Page.
3.109.
3.110. Irrespective, of the RSmartBiz Version (Web/App); the system is expected
to authenticate all users, barring potential unauthorized persons from accessing
the application.
3.111.
3.2.2. VALIDATION PROCESS:

3.112. This is the second step in the RSmartBiz system. The system should
prompt if this is an “Existing Client” or a “First Timer”. If a “First Timer”, the
process is as follows:
3.113.
3.114. Fi
3.115. Description
N eld Name
3.118. The borrower clicks on a Link “First
Timer”; the system prompts a dialog box requesting
the borrower to inputs his/her BVN Number;
3.119.
3.120. The borrower inputs the BVN Number
and tabs out of the feld:
3.121.
3.122. The system validates that the BVN Number
is Unique, 11 Digits and also does exist within the
3.116.
3.117. BV NBISS BVN database.
1 N Number 3.123.
3.124. On completion of the validation, the
system displays the under listed information:
3.125.
 Surname
 Middle Name
 First Name
 Mobile Number
 Date of Birth
3.126.
3.127.
3.128. Su
2 rname 3.129. Displayed based on BVN
3.130.
3.131. Mi 3.132. Displayed based on BVN

9|Page
3 ddle Name
3.133.
3.134. Fir
4 st Name 3.135. Displayed based on BVN
3.136.
3.137. M
5 obile Number 3.138. Displayed based on BVN
3.139.
3.140. M
6 obile Number 2 3.141. 11 Digits Validation
3.142.
3.143. E
6 mail Address 3.144. Free text; the system should validate “@”
3.145.
3.146. Co 3.147. If the felds above have been updated, the
7 ntinue Button system prompts the user to click on the “Continue”
button;
3.148.
3.149. Once the “Continue” button has been clicked, the system displays a new
page “Login” as follows:
3.150.
3.151. Fi
3.152. Description
N eld Name
3.153.
3.154. M 3.155. A temporary PIN has been sent to your
1 essage Display Email Address and Mobile Number.
3.156.
3.157.
3.158. The borrower’s email is displayed
2 Email
3.159.
3.160.
3.161. The borrower’s Mobile Number is displayed
3 Mobile Number
3.162.
3.163. Ac
3.164. The borrower’s name is displayed
4 count
3.167. The borrower is expected to check his
3.165.
3.166. Te
email or SMS for a 10 Digit Validation Code; and input
5 mporary PIN
it in the feld “Temporary PIN”
3.170. If the felds above have been updated, the
3.168.
3.169. Lo
system prompts the user to click on the “Login”
6 gin
button;
3.171.
3.172. S
3.173. GC-183362856 is your Temporary PIN
7 MS Message
3.176.
3.177. Dear “First Name”,
3.178.
Thank you for registering your details.
3.174.
3.175. E
3.179.
6 mail Message
When requested for a password, enter the following
temporary PIN: GC-183362856
Thank You
3.180.
3.181. Once the “Login” button has been clicked, the system displays a new page
“Set Password” as follows:
3.182.
3.183.
3.184.
3.185. Fi
3.186. Description
N eld Name

10 | P a g e
3.187.
3.188. Ne
3.189. New Password
1 w Password
3.191.
3.190.
Repeat 3.192. Repeat Password
2
Password
3.195. Aleast one letter
3.196. Aleast one capital letter
3.193.
3.194. Ins
3.197. Aleast one number
3 tructions
3.198. Aleast 6 character
3.199. New password must match
3.200.
3.201. Se
system prompts the user to click on the “Set
4 t Password
Password” button;
3.203.
3.204. Once the “Set Password” button has been clicked, the system displays
the borrower’s dashboard with the trigger to update KYC Details. Refer to
“Dashboard” for more details.
3.205.
3.206. If the applicant is a “Existing Client”, and the “Existing Client” button
has been clicked, the system displays the “Login” as follows:
3.207.
3.208. Fi
3.209. Description
N eld Name
3.210.
3.211. M 3.212. To login, please enter your email and
1 essage password
3.213.
3.214. E
3.215. Validate “@”
2 mail Address
3.216.
3.217.
3.218. Password
3 Password
3.221. This should enable the user to reset a
3.219.
3.220. Fo forgotten password.
4 rgot Password 3.222. Refer to “Reset Password” for more
details
3.223.
3.224. Se
4 t Password
Password” button;
3.226.
3.227. Reset Password
3.228.
3.229. Fi
3.230. Description
N eld Name
3.231.
3.232. M 3.233. If you have forgotten your password, you
1 essage may request a new password by email.
3.234.
3.235. E
3.236. Validate “@”
2 mail Address
3.237.
3.238. Da
3.239. The borrower enter the Date of Birth
3 te of Birth
3.240.
3.241. Re Password” button;
4 set Password 3.243.
3.244. A message is sent to the borrower’s email
for a Password Reset

11 | P a g e
3.245.
3.246. Once the “Set Password” button has been clicked, the system displays
the borrower’s dashboard with all applicable features (Module).
3.247.

12 | P a g e
3.2.3. DASHBOARD:
3.248. The Dashboard Display is dependent if the borrower is a “First Timer” or
“Existing Client”.
3.249.
3.250. If a “First Timer”, this means that the system does not have the KYC
Details of the borrower, the system should prompt for update of KYC Details.
3.251.
3.252. KYC Details
3.253. The system should allow for two types of Clients:
 Individual Clients (I)
 Non Individual Clients (NI) e.g., Corporate Clients.
3.254.
3.255. INDIVIDUAL CLIENTS (I)
3.256. Personal Information
3.257.
3.258. Fi
3.259. Description
N eld Name
3.260.
3.261. Cu
3.262. I - Individual
1 stomer Type
3.263.
3.264. Su
3.265. Displayed from BVN
2 rname Name
3.266.
3.267. Fir
3 st Name
3.269.
3.270. Mi
4 ddle Name
3.272.
3.273. Tit
3.274. This is a pre-defned list
5 le
3.275.
3.276. Ge
3.277. Either Male or Female
6 nder
3.278.
3.279. Da
7 te of Birth
3.281.
3.282. Ag
3.283. Calculated Age is displayed
8 e
3.284.
3.285. M
9 obile Number 1
3.287.
3.288. M 3.289. Alternate Mobile Number (Validate the 11
10 obile Number 2 Digits)
3.290.
3.291. E
3.292. ‘@’ should be validated
11 mail
3.293.
3.294. M
3.295. This is a pre-defned List
12 arital Status
3.296.
3.297. M
3.298. free text
13 aiden Name
3.299.
3.300. Ed
3.301. This is a pre-defled list
14 ucational level

13 | P a g e
3.302.
3.303. Residential Address Information
3.304. The borrower completes the address information:
3.305.
3.306. Fiel
3.307. Description
N d Name
3.308.
3.309. Resi
3.310. Free Text
1 dential Address:
3.312.
3.311. Addr
3.313. Display Field (Nigeria)
2 ess Country:
3.314.
3.315. Addr
3.316. Pre-Defned Pick list
3 ess State:
3.318.
3.317. Addr
4 ess State LGA:
3.320.
3.321. Next of Kin Information
3.322. The borrower completes the Next of Kin Information:
3.323.
3.324.
3.325. Field 3.326. Descri
N Name ption
3.327.
3.328. Next of
3.329. Free text
1 Kin Surname:
3.330.
3.331. Next of
3.332. Free text
2 Kin Middle Name:
3.333.
3.334. Next of
3.335. Free text
3 Kin First Name:
3.336.
3.337. Next of
3.338. Date Picker (DD/MM/YYYY)
4 Kin Date of Birth:
3.339.
3.340. Next of
3.341. Free text
5 Kin Address:
3.342.
3.343. Next of
6 Kin Address Country:
3.345.
3.346. Next of
3.347. Pre-defned Pick list
7 Kin Address State:
3.348.
3.349. Next of
3.350. Pre-defned Pick list
8 Kin Address LGA:
3.351.
3.352. Next of 3.353. Pre-defned Pick List (Brother, Sister
9 Kin Relationship: etc.)
3.354.
3.355. Next of
3.356. Numeric Value (11 Digits)
10 Kin Mobile No.:
3.358. Next of
3.357.
Kin Alternate Mobile 3.359. Numeric Value (11 Digits)
11
No. 2:
3.360.
3.361. Next of
3.362. Pre-defned Pick List
12 Kin ID Type:
3.363.
3.364. Next of 3.365. Free text

14 | P a g e
13 Kin ID Number:
3.366.
3.367. Business Information/Employment Information
3.368. The borrower completes the Business Information or Employment
Information:
3.369. If Business Information (Business Loan)
3.370.
3.371. Fi
3.372. Description
N eld Name
3.373.
3.374. B 3.375. This is a pre-defned list. The borrower
1 usiness Type should select from the pre-defned list
3.376.
3.377. B
3.378. Free text
2 usiness Name
3.380. B
3.379.
usiness 3.381. Free Text
3
Address:
3.383. A
3.382.
ddress 3.384. Display Field (Nigeria)
4
Country:
3.385.
3.386. A
3.387. Pre-Defned Picklist
5 ddress State:
3.389. A
3.388.
ddress State 3.390. Pre-Defned Picklist
6
LGA:
3.392. B
3.391.
usiness Start 3.393. This is a date Picker. DD/MM/YYYY
7
Date
3.395. Y
3.394.
ears In 3.396. Display Field
8
Business
3.397.
3.398. S
9 ector
3.400.
3.401. In
10 dustry
3.405. This is the closest branch to the Business
3.403.3.404. Cl
Address; the system provides a picklist that matches
11 osest Branch
the closest branch to the business.
3.406.
3.407. If Employment Information (Public Sector Loan)
3.408.
3.409. Fi
3.410. Description
N eld Name
3.411.
3.412. 3.413. Pre-Defned Picklist (The Ministry list is to
1 Ministry: be provided)
3.416. Pre-defned List – the MDAs associated
3.414.
3.415. M
within the Ministry selected should be displayed for
2 DAs
selection.

15 | P a g e
3.417.
3.418. Jo
3.419. Pre-defned List
3 b Role/Grade:
3.421. E
3.420. 3.422. Free Entry: The system validates the
mployment/
4 Oracle ID
Oracle ID:
3.424. E
3.423.
mployment 3.425. Date Picker
5
Date:
3.427. Y
3.426. 3.428. System Display - (Validation on Max 34
ears-In-
6 years)
Service:
3.430. R
3.429.
etirement 3.431. Date Picker
7
Date:
3.432.
3.433. S 3.434. Display Field ( Should populate once the
8 alary Pay Day: MDA is selected )
3.435.
3.436. S
9 ector:
3.438.
3.439. In
10 dustry:
3.441.
3.442. Mi 3.443. Pre-Defned Picklist (The Ministry list is to
11 nistry: be provided)
3.445. D
3.444.
epartment/Age 3.446. Pre-defned List
12
ncy:
3.447.
3.448. Jo
13 b Role/Grade:

16 | P a g e
3.450.
3.451.
3.452. NON INDIVIDUAL CLIENTS (NI) E.G., CORPORATIONS.
3.1. 3.2. Field 3.453.
3.3. Description
N Name 3.453.
3.4. 3.5. Custo 3.453.
3.6. NI – Non-Individual
1 mer Type 3.453.
3.7. 3.8. Corpor 3.453.
3.9. Free Text
2 ation Name 3.453.
3.10.3.11. Corpor 3.453.
3 ation 3.453.
3.12. Free Text 3.453.
Preferred
Name 3.453.
3.13.3.14. Registr 3.453.
4 ation Date 3.15. Date Picker 3.453.
(DD/MM/YYYY) 3.453.
3.16.3.17. Regist 3.453.
3.18. Display 3.453.
5 ered Years
3.19.3.20. Incorp 3.453.
6 oration 3.21. Alpha Numeric 3.453.
Number 3.453.
3.22.3.23. Openin 3.453.
3.24. Date Picker 3.453.
7 g Date
3.25.3.26. No. Of 3.453.
3.27. Field Population 3.453.
8 Employees
3.28. 3.453.
3.29. Industr 3.453.
1 3.30. Mandatory (Predefned Picklist)
y 3.453.
0
3.31. 3.453.
1 3.32. Sector 3.33. Mandatory (Predefned Picklist) 3.453.
1 3.453.
3.34. 3.453.
1 3.35. Email 1 3.36. Mandatory "@" Should Be Validated 3.453.
2 3.453.
3.37. 3.453.
1 3.38. Email 2 3.39. "@" Should Be Validated 3.453.
2 3.453.
3.40. 3.453.
3.41. Websit 3.453.
1 3.42. Not Mandatory
e 3.453.
3
3.453.
3.454.
3.455.
3.456.
3.457.
3.458.
3.459.
3.460.
3.461.
3.462.
3.463.

17 | P a g e
3.464.
3.465.
3.466.
3.467.
3.468.
3.469. Business Account Number
3.43.3.44. Field 3.470.
3.45. Description
N Name 3.470.
3.46.3.47. Bank 3.470.
3.48. Mandatory
1 Name 3.470.
3.49.3.50. Bank 3.470.
2 Account 3.51. Mandatory 3.470.
Name 3.470.
3.52.3.53. Bank 3.470.
3 Account 3.54. Mandatory 3.470.
Number 3.470.
3.55.3.56. Bank 3.470.
4 Account Date 3.57. Mandatory (DD/MM/YYYY) 3.470.
Opened 3.470.
3.470.
3.471.
3.472.
3.473. Business Address
3.58.3.59. Field 3.474.
3.60. Description
N Name 3.474.
3.61.3.62. Ofce 3.474.
3.63. Mandatory
1 Address 3.474.
3.64. 3.474.
3.65. State 3.66. Mandatory (Predefned Pick List)
2 3.474.
3.67.3.68. Town / 3.69. Mandatory (Predefned Pick List Based 3.474.
3 LGA On State) 3.474.
3.70.3.71. Countr 3.474.
3.72. Mandatory (Defaulted To Nigeria) 3.474.
4 y
3.73.3.74. Current 3.474.
3.75. Mandatory 3.474.
5 Address (Y/N)
3.76.3.77. Date 3.474.
6 Address 3.78. Mandatory 3.474.
Occupied 3.474.
3.79.3.80. Period 3.474.
7 At Current 3.81. Mandatory 3.474.
Address 3.474.
3.82.3.83. Accom 3.474.
8 modation 3.84. Not Mandatory 3.474.
Type 3.474.
3.474.
3.475.
3.476.
3.477.
3.478.
3.479.

18 | P a g e
3.480.
3.481.
3.482.
3.483.
3.484.
3.485. Business Information
3.85.3.86. Field 3.486.
3.87. Description
N Name 3.486.
3.88.3.89. Busine 3.486.
3.90. Free text
1 ss Name 3.486.
3.91.3.92. Industr 3.486.
2 y 3.486.
3.94. 3.486.
3.95. Sector 3.96. Pre-defned List 3.486.
3
3.97.3.98. Busine 3.486.
3.99. Mandatory 3.486.
4 ss Type
3.100.
3.101. Busine 3.486.
3.102. Mandatory 3.486.
5 ss Start Date
3.103.
3.104. Years 3.486.
3.105. Display 3.486.
6 In Business
3.106.
3.107. Busine 3.486.
3.108. Free Text 3.486.
7 ss Address:
3.486.
3.109.
3.110. Addres 3.486.
8 s Country: 3.486.
3.112.
3.113. Addres 3.486.
3.114. Pre-Defned Picklist 3.486.
9 s State:
3.486.
3.115.
3.116. Addres 3.486.
1 3.117. Pre-Defned Picklist
s State LGA: 3.486.
0 3.486.
3.487.
3.488.
3.489.
3.490.
3.491.
3.492.
3.493.
3.494.
3.495.
3.496.
3.497.
3.498.
3.499. Contact Person’s Information
3.500. The Contact Person’s Information should be multi-valued to accommodate
the profle of all Contact Persons in the organization.

19 | P a g e
3.118. 3.121.
3.120. Field
3.119. 3.122. Description 3.501.
Name
N 3.123. 3.501.
3.124.
3.125. Contac 3.501.
1 t Person’s 3.126. Free text 3.501.
BVN 3.501.
3.127.
3.128. Contac 3.501.
Surname 3.501.
3.130.
3.131. Contac 3.501.
First Name 3.501.
3.133.
3.134. Contac 3.501.
Middle Name 3.501.
3.136.
3.137. Contac 3.501.
5 t Person's 3.138. Free text 3.501.
Position 3.501.
3.139.
3.140. Email 3.501.
3.141. Mandatory "@" Should Be Validated
6 1 3.501.
3.142.
3.143. Email 3.501.
3.144. Not Mandatory "@" Should Be Validated
7 2 3.501.
3.145.
3.146. Mobile 3.501.
3.147. Mandatory
8 No. 1 3.501.
3.148.
3.149. Mobile 3.501.
3.150. Not Mandatory
9 No. 2 3.501.
3.151. 3.501.
3.152. Date of
1 3.153. Mandatory 3.501.
Birth
0 3.501.
3.154. 3.501.
3.155. Gende
1 3.156. Mandatory 3.501.
r
1 3.501.
3.157. 3.501.
3.158. Reside
1 3.159. Mandatory 3.501.
ntial Address
2 3.501.
3.160. 3.501.
3.161. Reside
1 3.162. Mandatory 3.501.
ntial State
3 3.501.
3.163. 3.501.
3.164. Reside 3.165. Mandatory (Predefned Pick List Based On
1 3.501.
ntial LGA State)
4 3.501.
3.166. 3.501.
3.167. Reside
1 3.168. Mandatory (Defaulted To Nigeria) 3.501.
ntial Country
5 3.501.
3.169.
3.170. Contac 3.501.
1 t Person 3.171. Mandatory 3.501.
6 Photo 3.501.
3.172.
3.173. Contac 3.501.
1 t Person 3.174. Mandatory 3.501.
7 Signature 3.501.
3.175.
3.176. Contac 3.501.
3.177. Mandatory (Picklist List); (International
1 t Person 3.501.
Passport, Driver’s License, National Identity
8 Identifcation 3.501.
Card, Others
(+) 3.501.
3.178. 3.501.
3.179. Id
1 3.180. Mandatory 3.501.
Number
9 3.501.
3.181.
3.182. Id 3.501.
2 Validity 3.501.
3.184. Mandatory
0 Period 3.501.
3.183.
3.185.
3.186. Front
2 Copyright
Photo of Id
(C) 2021: 3.188.
Proprietary Not
and Mandatory
Confdentiaa
1 203.187.
|Page
3.189.
3.190. Back
2 Photo of Id 3.192. Not Mandatory
2 3.191.
3.501.
3.502.
3.503.
3.504.
3.505.
3.506.
3.507.
3.508.
3.509.
3.510.
3.511.
3.512.
3.513.
3.514.
3.515.
3.516.
3.517.
3.518.
3.519.
3.520.
3.521.
3.522. Business Documentations Required
3.193. 3.196. 3.523.
3.194.
3.195. Field Name 3.197. Description
3.524.
N 3.198.
3.524.
3.199.
3.200. Documentations (
3.524.
1. Memorandum Of
3.524.
Association,
3.524.
2. Articles of Association,
3.524.
3. Certifcate of
3.524.
Incorporation,
3.201. Mandatory (Applicable 3.524.
4. Founding Statement,
Documents Should Be Selected) 3.524.
5. Certifcate to Commence
3.202. 3.524.
Business,
3.524.
6. Trust Deed,
3.524.
7. Partnership Agreement,
3.524.
8. Constitution,
3.524.
9. Certifcate,
3.524.
10. Change Of Name)
3.524.
Document Uploads
3.525. The borrower uploads all required documents depending on the Loan
product.
3.526.
3.527. F
3.528. Description
N ield Name
3.529.
3.530. 3.531. Pre-Defned Pick list (The Document Types
1 Document

21 | P a g e
Type are listed)

3.532.
3.533. U 3.534. This is a button that enables the borrower
2 pload to upload the documents
3.535.
3.536. Once the details are fully updated; the system allows the borrower to
‘Submit’ the application and also provides a SUMMARY OVERVIEW, which can
be printed by the borrower and presented to the Closest Branch for Sign Off.
3.537. SUMMARY OVERVIEW
3.538. KYC DETAILS (+)
3.539.
3.540. If an “Existing Client”, this means that the KYC Details of the client
already exist on the system, hence, the Basic Information and the associated
Modules is displayed.
3.541.
3.542.
3.543. F
3.544. Description
N ield Name
3.545.
3.546.
3.547. Good Afternoon! *Client Names*
1 Greetings
3.548.
3.549. L
3.550. Last Login: Date & Time
2 ogin Details
3.551.
3.552. C 3.553. Saving Account: Inflows/Outflows (Graphical
3 ashflows Representation) within a Month
3.554.
3.555. CASHFLOWS
3.556. **Inflows **Outflow
MONTH/YEAR
3.557.
3.558. 5T
3.559.
3.560. 2T
3.561.
3.562. 0T
3.563.
3.2.4. PROFILE MANAGEMENT

3.564. This includes:
3.565.
1. Clients Basic Details
3.566.
3.567. F
3.568. Description
N ield Name

22 | P a g e
3.569.
3.570. Cl
3.571. Display Field
1 ient ID
3.572.
3.573. S 3.574. Display Field
2 urname
3.575.
3.576. M 3.577. Display Field
3 iddle Name
3.578.
3.579. Fi 3.580. Display Field
4 rst Name
3.581.
3.582. P 3.583. Display Field
5 assport
3.584.
3.585.
2. Password Change
3.586.
3.587. Fi
3.588. Description
N eld Name
3.589.
3.590. Cu
3.591. Input Field
1 rrent Password
3.592.
3.593. Ne 3.594. Input Field
2 w Password
3.596. Co 3.597. Input Field
3.595.
nfrm New
3
Password
3.598.
3.599. Se
4 t Password
Password” button;
3.601.
3. Update Client Information
3.602.
3.603. Fi
3.604. Description
N eld Name
3.605.
3.606. E
3.607. Input Field
1 mail Address
3.608.
3.609. Mo 3.610. Input Field
2 bile Number
3.611.
3.612. Co 3.613. Select to Update
3 nfrm Button
3.614.
3.2.5. NOTIFICATIONS
3.615.
3.616. Fi
3.617. Description
N eld Name
3.619. Pr
3.618. 3.620. GC Product Descriptions. (Refer to
oduct
1 Appendix A)
Description
3.621.
3.622. Kn 3.623. GC ‘’Know Your Right”. (Refer to Appendix
2 ow Your Right A)

23 | P a g e
3.625. La
3.624. 3.626. GC ‘Lady Kate Okafor Scholarship” (Refer
dyKate Okafor
3 to Appendix A)
Scholarship
3.627.
3.2.6. INVENTORY
3.628. The inventory module is an existing module within the RSmartBiz System.
The current functionalities should be maintained.
3.629. 3.631.
3.630. Functionalities
N Remarks
 User Authentication 3.633.
 Payment Channels 3.634.
 SMS 3.635.
 Inventory Items 3.636.
 Back-ofce Module 3.637.
 Multiple Shopping Cart 3.638.
 Total Sales View 3.639.
3.632.  Loan Calculator 3.640. Functionality Available
 Reporting and Analytics
Capabilities
 Location Service
 Integrated Feedback System
 Receipts, Tax, and Discounts
 Printing Capability
 Miscellaneous
3.641.
3.642.
3.2.7. STATEMENTS
3.643. Statement Module should be sub divided into:
 Savings Statement(s) - the system should allow for one or more savings
Statements depending on the number of Savings Accounts.
3.644.
CLIENT SAVINGS
STATEMENT.xls
3.645.
 Loans Statement(s) - the system should allow for one or more loans Statements
depending on the number of Loans Accounts.
CLIENT LOAN
STATEMENT.xls
3.646.
3.2.8. LOAN MANAGEMENT

3.647.
1. Loan Application
3.648. The system should allow the borrower completes the loan application
tailored to specifc loan product;
3.649. If a “First Timer”;

24 | P a g e
3.650. The Loan Application is received by Portfolio Manager in the closest branch
indicated; the frst step done by the Portfolio Manager is to review the application
for accuracy, genuine & completeness. If all the required felds are not completed,
the application will be returned to the borrower on the portal requesting for the
missing information.
3.651. If “Existing Client”;
3.652. The Loan Application is received by Portfolio Manager in the client’s branch,
the system should validate against client with running loan of same product.
3.653.
3.654. The “Loan Calculator” should be used for displaying the “Proposed
Loan Schedule”.
3.655.
3.656. Fi
3.657. Description
N eld Name
3.660. This feld should show the list of
documentations to be uploaded:
3.661.
3.659. Lis  ID Proof / Address proof: Voter ID, NIN,

t of Required International ID Card etc;
3.658.
Documents to  Current Employment Information including Salary
1 be uploaded Slip;
either in PDF or
JPEG  Bank statement & Previous Loan Statement.
 Staff ID Card
 Passport
 Signature
3.662.
3.663. Ap 3.664. The system displays the application date
2 plication Date as Today’s date
3.665.
3.666. Pr 3.667. This is a pre-defned list; the borrower
3 oduct should be able to select the Loan Product applicable.
3.668.
3.669. Lo 3.670. The system should allow for a Numeric
4 an Amount Value.
3.673. This is a pre-defned list; the borrower
3.671.
3.672. Te should be able to enter the number and frequency of
5 nor the Loan Repayment dependent on the Loan product.
It could be Weekly or Monthly. E.g., 24 – Weeks, 3 –
Months etc.
3.674.
3.675. Lo 3.676. This is a pre-defned list; the borrower
6 an Purpose should be able to select from the defned attributes.
3.677.
3.678. La 3.679. The system displays a numeric value. This
7 st Loan Amount is applicable if the borrower is a repeat client.
3.681.
3.680.
3.682. La 3.683. The system displays a date. This is
8 st Repaid Loan applicable if the borrower is a repeat client.
Date
3.684.
3.685. Pr 3.687.
9 oposed Loan 3.688. The system displays the under listed Loan
Schedule Attributes dependent on the Loan Product:
3.689.

25 | P a g e
3.690. Charges relevant to the products should

be displayed:
3.691.
 Loan Form Fee Display (where Applicable)
 Passbook Display (where Applicable)
 Risk Premium Display (where Applicable)
 Admin Charge Display (where Applicable)
 Loan Amount: Display (where Applicable)
 Service Charge: Display (where Applicable)
3.692.
3.686. (L 3.693. Loan Repayment Terms relevant to the
oan products should be displayed:
Calculator) 3.694.
 Tenor: Display (where Applicable)
 Loan Amount with S.C.: Display (where Applicable)
 No of Loan Installments: Display (where
Applicable)
 Monthly/ Weekly Repayment Amount: Display
(where Applicable)
 Total Repayment Amount: Display (where
Applicable)
 Loan Security Fund: Display (where Applicable)
 Loan Cycle: Display (where Applicable)
3.695.
3.696.
3.697. Account Details
3.698. The borrower completes the deposit account details that will be used for
disbursement:
3.699.
3.700. Fi
3.701. Description
N eld Name
3.702.
3.703. Ba 3.704. This is a pre-defned list, the borrower
1 nk selects the Bank name applicable
3.706. Ac
3.705. 3.707. The borrower inputs the 10-digits bank
count Number
2 account number
(NUBAN)
3.710. The Account Name is displayed;
3.711.
3.708.
3.709. Ac 3.712. Note; if the Account Name displayed not
3 count Name does match the BVN Name, the system should prompt
the borrower and discontinue the process.
3.713.
3.714.
3.715.
3.716.
3.717.
3.718.
2. Application Status
3.719.Loan 3.720. 3.721. 3.722.
Product Date Submitted Status

26 | P a g e
Applied
3.724. 3.725. 3.726.
3.723.
3.728. 3.729. 3.730.
3.727.
3.732. 3.733. 3.734.
3.731.
3.735. LINKS --- Start New Application----
3.736. ** The Loan Status should reflect as currently embedded on BPA. e.g.,
Awaiting Approval, Loan Approved/Awaiting Disbursement, Loan
Disbursed etc.
3.737.
3. Loan Transaction History
3.738. The system should allow for one or more loans transaction history
depending on the number of Loans Accounts.
3.739.
LOAN REPAYMENT
HISTORY.xlsx
3.740.
3.2.9. COMPLAINT MANAGEMENT

3.741.
1. Compliant/Feedback
3.742.
3.743. Fi
3.744. Description
N eld Name
3.745.
3.746. Cli
3.747. Display
1 ent ID
3.748.
3.749. Na
3.750. Display
2 me
3.751.
3.752. E
3.753. Display
3 mail 1
3.754.
3.755. Mo
3.756. Display
4 bile Number 1
3.757.
3.758. Ca 3.759. PARAMETR TABLE – Possible Values:
5 tegory 3.760. General, Products, Savings, Loans
3.761.
3.762. Su
3.763. Free Text
6 bject
3.765. Co
3.764.
mplaint 3.766. Free Text
7
Feedback
3.769. Once the Submit Button is submitted, the
rcord is updated and displays “Successful”.
3.767.
3.768. Su
3.770.
8 bmit Button
3.771. Case ID is also generated with a Prefs
“GC” e.g., GC -00011
3.772.

27 | P a g e
2. View Compliant/Feedback Status
3.773.
3.774. Fi
3.775. Description
N eld Name
3.778. The generated Case IDs are displayed.
3.776.
3.777. Ca
3.779.
1 se IDs
3.780. The User should select and of the IDs
3.781.
3.782. Su 3.783. Based on the Selected IDs, the system
2 bject displays the Subject of the Case
3.786. Based on the Selected IDs, the system
3.784.
3.785. St
displays the Status e.g., In Progress, Closed, Resolved,
2 atus
Re-Opened etc.
3.787.
3.2.10. HELP
3.788.
1. Contact Us
3.789.
3.790. Fi
3.791. Description
N eld Name
3.792.
3.793. Ad 3.794. Grooming Centre Head Ofce, 120 Egbe
1 dress Rd, Ejigbo, Lagos
3.795.
3.796. Mo
3.797. +234 815 098 9340
2 bile No
3.798.
3.799. Tol
3.800. 0800-47666464, (0800-Grooming)
3 l Free Line
3.801.
3.802. E
3.803. info@groomingcentre.org
4 mail
3.804.
2. FAQ
3.805. To be provided.
3.806.

28 | P a g e
3.807. General Operations

3.808. The System shall support the following operations:
 Search functions shall be available in all pages that contain the list of Loan
Products that have been applied by the borrower, where no Loan Application have
been applied; the system should display that “No Loan Application have been
submitted using this profle.
 Save Only: This operation allows borrowers to save a Loan Application that is not
fully completed.
 Edit felds. This operation allows users to adjust or correct felds. This is possible
only when the record has a Save Only status.
 Loan Status: The system should have the ability to update the status of a
submitted Loan Application. e.g., Submitted, Review In Progress, Declined,
Approved, Disbursed and Fully Repaid.
3.809.
3.810. Reporting Sub-system

3.811. The system shall implement a reporting module. The reporting module
shall be accessed through the reporting Module. All reports shall be available for
extracting into Excel or PDF fles. The system shall implement the following
standard reports:
3.812.
3.813.3.814. Repo
3.815. Description
N rt type
3.816.3.817. Onlin 3.818. This report provides information
1 e KYC Report about the KYC Details registered Online.
3.820. Onlin 3.821. This report shall have all the Online
3.819. e Loan Loan Applications that were Submitted,
2 Applications Review In Progress, Declined, Approved,
– Status Disbursed and Fully Repaid.
3.823. Credit
3.822. 3.824. This report shall have all the Online
Appraisal
3 Loan Applications – Credit Appraisals
Report
3.825.3.826. Client 3.827. This report shall have the Client’s
4 Portfolio Profle Account details.
3.829. Client
3.830. This report shall have the Client’s
3.828. Loan
Repayment schedule, which is generated
5 Repayment
once is Loan disbursed.
Schedule
3.832.
3.831. Clients 3.833. This report shall have the Client’s
6 Statement – Repayment Details on a disbursed loan.
Loans
3.835. Client
3.834. 3.836. This report shall have the Client’s
s Statement
7 Deposit Details.
– Savings
3.838. Loan
3.839. This report shall have the Client’s
3.837. Risk
Risk Classifcation Status on his disbursed
7 Classifcation
Loans.
Status

29 | P a g e
3.840.
3.841. Report generation module shall have a rich search and fltering module,
which allows fltering of the records before the generation of the report. Filtering
options shall include all available felds of the Loan and assigned account ofcers.
3.842. Report generation module shall allow the user to select the aggregation
options. For each report, the user shall be able to select the aggregation category
(per Branch etc)
3.843.
3.844. User Management Sub-system

3.845. The System shall implement user and permissions management module,
which allows creating, editing, deleting users of the system and managing their
permissions.
3.846. The system shall have the ability to create a group of users. The system
shall have the following pre- defned group of users available in the system.
3.847.
 System Administrator. This group of users has all the necessary permissions to
perform any operation in the system.
 Loan Application Administrator. This group of users can perform operations
like Application Processing, Loan Appraisals, etc.
 Field (including Head Ofce) Ofcer. Field ofcer shall be able to accept Loan
Application assigned to his/her branch for processing.
 Reporting User. This user has no rights to perform data entry operations and can
only search for Loan information and/or prepare reports.
3.848. When creating the user, The System shall collect the following information:
3.849.
3.851. F
3.850.
ield 3.852. Description
N
Name
3.853. 3.854. U 3.855. Full name of the user (First Name /
1 sername Last Name)
3.857. D 3.858. This feld should be a selected item.
3.856.
esignati The System shall allow for a list of the
2
on positions to be maintained for system users
3.859. 3.860. M
3.861. Mobile phone numbers
3 obile
3.862. 3.864. 3.866. This feld shall serve as a unique

identifer for the user. User must enter the
3.863. 3.865. E system via e-mail and the password (only
4 -mail grooming centre email account)
3.869. 3.871. This feld should be a selected item.

3.867. The system shall allow for a list of branch
3.870. E ofces /departments (and the places where
3.868. mploym the system is available) to be maintained for
5 ent system users (Start and expiry date of the
place contract)
3.872.
3.873. When the administrator frst creates a user in the system, the confrmation
email shall be sent to the user. The email shall contain the activation link and the

30 | P a g e
temporary PIN for the user. User must activate the account via the link and
change password after the frst login. The function of confrmation email shall be
optional and confgurable through the system management interface.
3.874. The user management module shall allow the performance of the following
actions:

31 | P a g e
3.203. 3.204. Funct 3.205. Description
N ion
3.206.
GC RSmartBiz 3.208.
Upgrade 3.210. The System shall have a front page
for the user login. Front page shall contain
3.207. 3.209. User
the email and password felds, as well as the
1 login
links for the, forgot password action
3.875.
described below.
3.876.
3.215. Through this action, the user can
3.877. 3.211. request a password change. The system
2 3.214. User shall provide a separate window where the
3.878.
Forgot user shall enter his email address. If the
3.212.
3.879. Password email exists in the system, the user will
3.213. receive an email with the password reset
3.880.
link.
3.881.
3.220. With the password reset link
3.882. 3.216. 3.218. described above, the user shall enter the
web page where he/she can provide and
3.883. 3.217. 3.219. User
Reset confrm a new password. The password shall
3.884. 3 Password have minimum length and complexity
requirements.
3.885.
3.223. The System shall provide an interface
3.886.
3.222. List for the administrator to list all the users of
3.221.
3.887. and Search the system, to search the user(s) by name,
4
Users contact details, employment place, and
3.888.
position.
3.889.
3.230. Any user of the system with
3.890. administrative privileges can register a user
3.224. 3.227. from the system. This administrator shall
3.891.
enter the user-related information as
3.225. 3.228.
3.892. described in the table for the user attributes.
3.226. 3.229. Regist After flling in all the required felds, the
3.893.
5 er user system shall create a user and send the
3.894. activation email to the user with the email
entered by the administrator.
3.895.
3.235. The administrator of the system shall
3.896. 3.231. 3.233.
be able to grant and revoke permission to
3.897. 3.232. 3.234. Assign the user of the system. The permission
assignment and revoke details should be
3.898. 6 permission
stored in the database for audit purposes
3.899.
3.242. The administrator shall have the
3.236. 3.239.
3.900. possibility to block/suspend the users of the
3.237. 3.240. system temporarily. In which case, the user
3.901.
will not be able to enter into the system. On
3.238. 3.241. Block/
3.902. the other hand, the user record will not be
7 Suspend user
deleted from the system.
3.249. With this function, the administrator
3.246. shall be able to unblock the user, which was
3.243.
blocked/suspended before. After unblocking
3.247.
3.244. the user, this user will regain the ability to
3.248. Unblo enter the system and perform the actions
3.245.
ck/Reinstate authorized by the administrator. The user
8
User must reset the password once reinstated by
the administrator.
3.254. Administrator shall be able to
deactivate a user from the system. By this
3.250. 3.252. action, all access and operational rights of
the user will be withdrawn. The user should
3.251. 3.253. Deacti not be able to login or request a password
9 vate user reset. The system should prevent deletion of
the user if the user has an active asset
custody record.
3.257. The System shall provide an interface
for the administrator to view the user
32 | P a3.255.
g e 3.256. Audit
activity log. This means that the system
10 user actions
shall record all the actions performed by the
user and store these in a special table.
3.903. System Management Sub-system

3.904. System Management shall allow the performance of the following
functions:
3.905.
a. Backup of the System Database: The System shall provide a user-friendly
interface for the system administrators to be able to back up the system database
manually. The System shall provide the special link in the administrative menu of
the system to access the system backup web page. The system administrator
shall be able to activate the backup operation and select the location where the
database backup will be stored. The system shall be designed in a way that it shall
continue to run and serve the requests from the users of the system during the
backup operation of the system. The system shall support the creation of
automatic backups at defned intervals.
3.906.
b. Management of System Parameters: System parameters are the classifers for
the attributes of the system objects. The parameters shall allow the classifcation
of objects into various groups to facilitate further reporting needs.
3.907. System Parameters shall be available only for the system administrators.
The system shall provide a special link in the administrative menu of the system to
access the System management module.
 The system administrator shall be able to select a parameter for the further
standard operations. Standard operations include create, edit, delete, search
and show the lists.
 Data entry personnel shall not have access to the system management
module.
 System Management module shall allow the standard data entry functions
including:
3.908.
o Listing of the parameterized records. (If the records have more than
20 items in the list, the system shall implement paging functionality for
viewing the parameterized records)
o Search the record item by name. Each record shall have a possibility to
search record (s) by id, name, branch, product etc
o Add new record item. The system shall prevent the double entry in case
the record with the same name already exists in the database
o Edit the record item. The system shall prevent the double entry in case a
record with the same name already exists in the database.
o Delete a record item. The system shall prevent the deletion of the record
if the record has already been used by any of the other related records in
the database
o All system parameters shall have an option to edit the name feld and add
additional records when required.
o The available parameter values shall be populated during the initialization
of the system and the systems administration should be able to add and
amend parameter content
3.909. General Requirements

 The system shall have a lingual user interface – English.
 The system shall be accessible for the users only through the HTTPS protocol.

33 | P a g e
 The system shall preferable have a modular structure.

 The system shall be accessible through modern browsers, particularly Google
Chrome or Chromium-based browsers.
 The system shall be user-friendly with access through desktop computers,
tablet devices and smartphones (responsive UI).
3.910. Documentation Requirements

 User’s Manual: the content of the user’s manual should be explicit and
understandable in the presentation of all the processes available to the users.
In particular, the logic of data entry and report generation should be explained
in a perceivable and step-by-step basis for each of the modules. The manual
shall contain screenshots of important steps/operations
 Administrator’s Manual: this document will offer all the guidelines and
instructions necessary for the management of the system. The content shall
include system and data storage; restoration of the system and database;
launch and disconnection of the system; security management of the users
and data; minutes of data communication and applicable procedures; and
maintenance of the log table.
 All users’ manuals should be presented in English version. Technical guidelines
should be compiled in English. The manuals must be submitted as a
deliverable in both printed and electronic versions. Electronic versions should
be open to modifcation in cases when there is a need to revise system
environment, functional properties, and operational properties.
3.911. Training Requirements

3.912. There is a need for two types of trainings:.
 Administrator Training. A training to transfer the ownership of the system
administration. The topics of this training shall include the installation,
operation, and maintenance of the system..
 User Training. Training of the end-users on the use of the system. The user
manual shall be used as a primary source for the training. The training shall be
done at Grooming Centre premises.
 Training venue will be arranged and provided by Grooming Centre, the
company should provide i) training material and ii) trainers to conduct above
mentioned trainings.
3.913.
3.914. Testing Requirements

3.915. During the preparation stage, the GC shall develop a system testing and
acceptance plan, which shall include testing scenarios and testing environment.
3.916. Mquid shall install the testing environment for Grooming Centre. The
testing environment shall be available during the design, development, testing
and post-implementation stages. The testing environment shall use a separate
database and separate endpoint. Mquid shall provide all the necessary credentials
for Grooming Centre to perform all the operations on the testing environment.
3.917.
3.918. User Acceptance Testing (UAT) of the system shall be conducted at
Grooming Centre. This shall be organised by DigitalOps with Mquid’s support.
During the UAT, all the fnal functional requirements shall be tested with feed-back
to the Vendor. To conduct the UAT, Mquid’s shall develop functional requirement
checklists for UAT in agreement with DigitalOps. The DigitalOps staff shall be
trained on the use of these checklists to fll them during the testing. UAT shall be

34 | P a g e
conducted in cycles. After each testing cycle, the flled checklists from the Client
staff shall be collected and analysed by Mquid. In the case of revealed discrepancy
between functional requirements specifcations and UAT testing, Mquid shall
identify the revealed bugs and appropriately fx them. In the following cycle, the
revealed bugs need to be re-tested by DigitalOps, and the next cycle checklist will
be provided to the DigitalOps. This process shall go on until all the requirements in
the checklists are tested and identifed as correct by the DigitalOps and approved
in compliance with the fnal functional requirements.
3.919.
3.920. Hardware Requirements

3.921. Mquid shall develop and discuss the hardware requirements for the system.
During the preparatory stage (described later) detailed hardware specifcations of
the hardware components shall be developed and provided to DigitalOps for
approval. Based on these specifcations, Grooming Centre will conduct a separate
procurement process to gather all the required hardware components for the
system. Mquid jointly with DigitalOps, shall install and confgure the hardware in
GC Datacentre (server equipment) and train DigitalOps on how to use the
peripheral hardware components such as barcode readers and printers

35 | P a g e
3.922.
St
3.923. art
3.924.
HOME
3.925. PAGE
3.926. YE
NEW S
3.927.
3.928. NO
LOGIN BVN
VALIDATE
NO
VALIDATI
ON
NO
YE
S
CLIENT PAGE
DASHBOARD PROFILE MGT NOTIFICATIO INVENTORY STATEMENTS LOAN MGT. COMPLAINTS HELP LOG OUT
NS
 Client  Items  Savings  Loan  Complaints  Contact Us
Profle  KYR  Categories Statement. Application  Compliant  FAQ
 Change  Product  Discounts  Loans . Status
Password Desc.  Customer Statement.  Application
 Update  Scholarship  Stores Status
Client s  Merchants  Transactio
Information  Income/Ex n History
p.
YE
S St
op
Copyright (C) 2021: Proprietary and Confdentiaa 36 | P a g e

3.929.
3.930.
3.931.
3.932.
3.933.
3.934.
3.935.
3.936.
3.937.
3.938.
3.939.
3.940.
3.941.
3.942.
3.943.
3.944.
3.945.
3.946.
3.947.
3.948.
3.949.
3.950.
3.951.
3.952.
3.953.
3.954.
3.955.
3.956.
3.957.
3.958.

37 | P a g e

Rsmart Biz Functional Spec (Phase 1)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Rsmart Biz Functional Spec (Phase 1)

Uploaded by

Copyright:

Available Formats

GROOMING PEOPLE FOR BETTER

DOCUMENT PUBLICATION HISTORY

Document Approved By:

Initial Release Version:

DOCUMENT REVISION HISTORY

Versio Change Change

DOCUMENT DISTRIBUTION LIST

Copyright (C) 2021: Proprietary and Confdentiaa

 A mobile POS application that was designed to run on smartphone

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

2. BRIEF DESCRIPTION OF THE SYSTEM

Copyright (C) 2021: Proprietary and Confdentiaa

3.55. Staff Management Sub-systems

3.66. This feld should be a pre-defned feld.

3.87. 3.89. This feld should be a pre-defned feld.

3.91. Data Entry Sub System

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa 7|Page

Copyright (C) 2021: Proprietary and Confdentiaa

3.2.1. HOME PAGE:

3.2.2. VALIDATION PROCESS:

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

Type are listed)

3.2.4. PROFILE MANAGEMENT

Copyright (C) 2021: Proprietary and Confdentiaa

3. Update Client Information

Copyright (C) 2021: Proprietary and Confdentiaa

3.2.8. LOAN MANAGEMENT

Copyright (C) 2021: Proprietary and Confdentiaa

3.659. Lis  ID Proof / Address proof: Voter ID, NIN,

Copyright (C) 2021: Proprietary and Confdentiaa

3.690. Charges relevant to the products should

Copyright (C) 2021: Proprietary and Confdentiaa

3.2.9. COMPLAINT MANAGEMENT

Copyright (C) 2021: Proprietary and Confdentiaa

2. View Compliant/Feedback Status

Copyright (C) 2021: Proprietary and Confdentiaa

3.807. General Operations

3.810. Reporting Sub-system

Copyright (C) 2021: Proprietary and Confdentiaa

3.844. User Management Sub-system

3.862. 3.864. 3.866. This feld shall serve as a unique

3.869. 3.871. This feld should be a selected item.

Copyright (C) 2021: Proprietary and Confdentiaa

Copyright (C) 2021: Proprietary and Confdentiaa

3.903. System Management Sub-system

3.909. General Requirements

Copyright (C) 2021: Proprietary and Confdentiaa

 The system shall preferable have a modular structure.

3.910. Documentation Requirements

3.911. Training Requirements