Design, build and delivery of the four-role bursary administration portal — student application through school verification, committee approval, disbursement and reporting.
Omevision proposes to build the Tibiyo Bursary Management System as a single web platform serving four distinct user groups: students, class teachers, participating schools, and the Tibiyo bursary committee.
The system replaces manual bursary administration with a tracked pipeline. A student applies once; their class teacher verifies academic standing; the committee assesses the application against configurable qualifying criteria and an enforced budget cap; the school claims and confirms attendance each term; and every disbursement is recorded against proof of payment. Committee members see the full position across all four regions at any moment — applications, commitments, disbursements, dropouts and grade failures.
Five delivery areas — four user-facing portals and the shared platform services beneath them.
Fixed price against the scope defined in clause 2.0. Effort is stated in person-weeks; calendar delivery is shorter through parallel work.
| Ref | Deliverable | Weeks | Amount |
|---|---|---|---|
| 3.1 | Discovery, data architecture and technical designRequirements confirmation, data model, integration and security design | 1.5 | 60,000 |
| 3.2 | Authentication, role permissions and institutional onboardingFour role types, school and staff account provisioning | 1.5 | 62,000 |
| 3.3 | Student portalApplication, history, status tracking, transfer requests | 2.5 | 100,000 |
| 3.4 | Academic report card moduleSubjects, marks, grading scale, class position, term comments | 1.5 | 62,000 |
| 3.5 | Teacher verification portalVerification queue, grade progression logic, failure classification | 1.5 | 60,000 |
| 3.6 | School portalClaims, term attendance, dropout reporting, payment proofs | 2.5 | 100,000 |
| 3.7 | Administration portal — pipeline, waitlist, transfers, paymentsCommittee review workflow and disbursement register | 2.5 | 102,000 |
| 3.8 | Qualifying criteria engine and budget control engineConfigurable thresholds, live eligibility evaluation, cap enforcement | 2.0 | 84,000 |
| 3.9 | Analytics dashboardApplication, approval, demographic, dropout and failure analysis | 1.5 | 65,000 |
| 3.10 | Statutory reporting and data exportsExecutive, financial, regional and school reports; PDF and CSV | 1.5 | 60,000 |
| 3.11 | Document management and notificationsSecure upload and storage, SMS and email at each stage | 1.0 | 45,000 |
| 3.12 | Quality assurance, security review, deployment and trainingTest cycles, penetration review, go-live, staff and school training | 2.5 | 95,000 |
| Total contract value | 22.0 | 895,000 |
Where a single approval is not practical, the engagement can be split into two contracts. Phase 1 delivers a complete bursary cycle end to end; Phase 2 adds the analysis and control layer.
| Ref | Phase | Weeks | Amount |
|---|---|---|---|
| 4.1 | Phase 1 — live cycle capabilityCovers refs 3.1, 3.2, 3.3, 3.5, 3.6, 3.7, 3.11 and apportioned 3.12. Runs a full application-to-disbursement cycle. | 10 | 580,000 |
| 4.2 | Phase 2 — control and intelligence layerCovers refs 3.4, 3.8, 3.9, 3.10 and apportioned 3.12. Report cards, criteria and budget engines, analytics and reporting. | 8 | 335,000 |
| Total, phased | 18 | 915,000 |
SZL 25,000 per month, commencing at go-live and invoiced monthly in advance.
The system holds live financial commitments and student records across multiple cycles, and carries its heaviest load in a short annual window. This is a managed service rather than a maintenance retainer. Omevision operates the platform, staffs a support desk for schools and teachers, absorbs hosting and notification costs, and carries a standing monthly allowance for changes requested during the year.
| Severity | Definition | Response | Resolution |
|---|---|---|---|
| Critical | System unavailable, or applications cannot be submitted or approved | 2 hours | Same day |
| High | A module is unusable but a workaround exists | 4 hours | 2 days |
| Normal | Defect with limited operational impact | 1 day | Next release |
| Request | Change or enhancement request | 2 days | By assessment |
Resolution times are stated in business days unless expressed in hours. During the January to March application window, critical response reduces to one hour.
Priced separately and not included in clause 3.0. Each may be commissioned at any time, before or after go-live.
| Ref | Extension | Amount |
|---|---|---|
| 6.1 | USSD and SMS application channelAllows students without smartphone or data access to apply and check status from any handset. Recommended — the applicant population is predominantly rural. | 120,000 |
| 6.2 | Bank integration for disbursement and reconciliationAutomated payment instruction and matching against school claims, replacing manual reference capture. | 95,000 |
| 6.3 | Historical data migrationImport of prior bursary cycles and student records from existing registers. | 65,000 |
| 6.4 | Student mobile applicationNative iOS and Android application with push notifications. | 180,000 |
Sixteen weeks from contract signature to go-live, assuming a two-person delivery team and Tibiyo feedback within five business days at each review point.
Stage A concludes with written design sign-off. Stage C concludes with the Phase 1 user acceptance review. Stage G concludes with go-live acceptance and handover of all source code, documentation and credentials.