Ormat Kenya/Support/Roadmap & delivery

Roadmap & delivery

What each remaining module covers, the phase plan behind it, and the controls the system is built to.

Modules by phase
Phase 2

Drafts & returned claims

One workspace for anything you have started but not submitted, plus claims sent back for correction with the reviewer's comment attached.

Scoped for this module
Resume a part-completed wizard at the exact step you left it
Returned claims open with the reviewer's comment pinned to the offending field
Bulk delete and cancel with a confirmation modal
Draft age warnings against the term submission deadline
Delivery plan
PhaseDurationDeliverables
Requirements
8am – 10amRequirements, process maps, approval matrix and limits
Design & Architecture
10am – 1pmAligning processes per expense
Development
3 weeksCore modules
Integrations
3 – 4 weeksOkta, Email, SSO
Testing
2 – 3 weeksUAT, Security
Training & Go-live
1 – 2 weeksTraining & deployment
Hypercare
2 weeksSupport
Controls
RBAC
Role-based access
Every module and action is granted per role, and the permission matrix is the single place it is set.
MFA
Multi-factor authentication
Okta SSO with a second factor, and biometric unlock on the mobile app.
Encryption
Data at rest and in transit
Stored documents and database contents are encrypted, and every request is over TLS.
Audit Trails
Track changes
Who, what, when, from which IP — including every view of a supporting document.
SoD
Segregation of duties
Approval roles are kept separate, and conflicts are flagged on the users screen.
Ormat
ORMAT Kenya
Expense Management

One route for every
expense, receipt
and approval.

School fees programmes, travel, mileage and reimbursements — validated against budget and policy before they reach Finance.

Sign in

Use your Ormat corporate identity. Access is role-based.

Prototype build — any password of six characters or more signs you in. Switch between the nine approval levels from the role picker in the top bar.