02
Engineering
Field work from my degree years — the kind of problems that don't have a undo button.
Tools & domains
- SCADA
- Relay protection
- Fault analysis
- Load balancing
- Bills of Quantities
- Cisco IoT / Networks
Field proof
Same discipline, two surfaces
Relay schematics and mobile UI share one habit — label what connects to what, then verify it under load.
Representative diagram — not from a live installation.
VersaRent — property management UI in development.
01
Kenya Power
Power Protection Engineer
Problem
Distribution feeders trip for reasons that are not always obvious from the customer end — relay mis-coordination, transient faults, or equipment stress. Someone has to trace the event, check the settings, and confirm the network can be safely re-energised.
Decision
I worked within existing protection standards and SCADA records: reviewing fault reports, verifying relay configurations, and documenting findings for the protection team to act on.
Outcome
Contributed to fault analysis and protection maintenance on live distribution infrastructure. The work reinforced how much grid reliability depends on correct settings paperwork, not just hardware.
Domains
- SCADA
- Relay protection
- Fault analysis
- Load balancing
02
Ministry of Public Works
Design Engineer
Problem
Public building projects need electrical designs and bills of quantities that match Kenyan standards and survive tender review. Drawings that are vague or non-compliant stall procurement.
Decision
I prepared design documentation to ministry specifications — load schedules, cable sizing, and BOQ line items — and coordinated with civil works so services routes did not clash with structure.
Outcome
Delivered design packages through departmental review. It was my first sustained exposure to how formal engineering documentation gates real construction spend.
Domains
- Bills of Quantities
- Electrical design
- Cisco IoT / Networks