KORNTE PowerEnergy & asset performance

Know what your assets produced, and what they need next.

Sites, systems, generation, consumption, maintenance plans and service jobs on one record — so a yield dispute is answered with data and the next service visit is planned, not reactive.

For solar EPCs, energy service companies and estates managing installed equipment.

KORNTE Power · assets
OverviewPortfolio performance
Live
Sites42
Generation18.4MWh
Services due9
Generation vs target 103%Live
Preventive plans raisedLive
Client yield reports to sendPending
Illustrative interface · configured menus and figures vary by deployment
1application
9data models
8menus and screens
0printed reports
0scheduled jobs
01Runs on KORNTE ERP
02Kenyan statutory and payment ready
03On-premise or hosted
04Supported after go-live
Before anything is sold

Performance argued from memory is a dispute you lose.

Generation reported from inverter screens and hand-read meters leaves nothing to show a client when the yield question arrives.

01

Performance argued from memory

Generation and consumption are reported from inverter screens and hand-read meters, so a client dispute over yield has no evidence behind it.

02

Maintenance is reactive

Service visits happen when something breaks, and preventive plans live in a technician's head or a paper diary.

03

Installations become orphans

The site, the equipment installed, the warranty and the commissioning record are never joined up, so the second visit starts from zero.

What changes

Evidence for the client, a plan for the equipment.

Generation and consumption recorded per site, service history attached to the asset, and commissioning records that survive the first visit.

Settle performance questions with records

Generation and consumption are recorded per site and system, so yield, savings and shortfalls are a report rather than a debate.

Evidence per site

Move from breakdowns to planned service

Preventive maintenance plans generate service jobs before the fault, and every visit is recorded against the asset.

Planned uptime

Keep the installation history with the installation

Assets, warranties, commissioning documents and service visits stay attached to the site for its whole life.

Full asset history

Report to clients and financiers from one dataset

Portfolio views roll sites into a single performance picture without a spreadsheet rebuild each month.

Portfolio view
The operating difference

From the paper diary to the preventive plan.

Sites, assets, generation, consumption and service in one register.

AreaHow it runs todayHow it runs on KORNTE Power
Site history
A folder per installation
Site record with systems, assets, commissioning and service history
Performance
Hand-read meters
Generation and consumption records per site and system
Maintenance
Reactive and undocumented
Preventive plans with service jobs, parts and outcomes
Client reporting
Rebuilt each month
Site and portfolio reports produced from the same records
What ships on day one

Site to service job, configured.

Sites and systems, asset register, generation, consumption, preventive maintenance, service jobs and dashboards — shipped.

01

Sites and energy systems

Site records with systems, capacity, commissioning details and documents.

02

Asset register

Panels, inverters, batteries, meters and generators recorded per site with serials and warranties.

03

Generation records

Production logged per system and period, with the source of each reading recorded.

04

Consumption records

Client-side consumption captured so savings and offset can be calculated.

05

Preventive maintenance

Plans by asset type and interval, generating service jobs with checklists and parts.

06

Service jobs

Scheduled and reactive jobs with technician, findings, parts used and closure notes.

07

Dashboards

Site and portfolio dashboards for generation, service load and open jobs.

08

Command centre

A single operational overview across sites, jobs and exceptions for the operations lead.

Who logs in

Operations, technicians, clients.

The same production figures reaching the operations desk and the client report.

O

Operations manager

Which sites underperformed this month, which jobs are overdue, and what it costs to fix.

F

Field technician

The site, the asset, the plan and the last visit — on a phone, at the installation.

C

Client and financier reporting

Portfolio performance and service evidence produced from the same records the field team uses.

Fit and boundaries

What KORNTE Power does, and what it deliberately does not.

A short, honest list. We would rather disqualify a bad fit in the first meeting than discover it in month four.

Discuss your requirement
  • •KORNTE Power records and reports performance; it does not control inverters or switch loads.
  • •Monitoring depends on the site's own connectivity and API availability.
  • •Engineering design, sizing and simulation are out of scope.
  • •This document describes shipped capability; anything not listed here is a change request, not an included feature.
  • •Country-specific statutory formats are configured per deployment and are not universal.
How the rollout actually runs

Six weeks, and you know exactly what happens in each one.

No mystery phases. This is the plan we hold ourselves to for a single-site KORNTE Power deployment; multi-site and multi-phase rollouts stretch the same sequence rather than replacing it.

Week 1–2

Discovery and process mapping

We sit with the people who do the work today and write the process down, including the exceptions nobody documents.

Week 2–4

Configuration against your paperwork

Numbering, tariffs, access groups, approval limits, print templates and the lists your vertical depends on.

Week 3–5

Data migration and parallel run

Sites, installed assets, commissioning records and service history — migrated, reconciled and run in parallel with the old method until the numbers agree.

Week 5–6

Training by role, then sign-off

Each role is trained on its own screens with its own work, and signs off before go-live rather than after.

Week 6 onward

Go-live and support

A named team on call through the first close, then a quarterly review of what to configure next.

What we migrateSites, installed assets, commissioning records and service history.
Who is on the projectThe people in the discovery meeting are the people who configure and train.
What you signA fixed-price scope before any contract, and a written scope change before any new work.
Next step

Bring a site. We will show you its production and its next service.

Bring a commissioning record and a month of generation data. We will show you the asset register, the performance report and the maintenance plan it drives.

30 minutes, screen-shared. Your workflow on our screens, not a slide deck.
A written scope. Modules, users, integrations and a fixed-price quotation.
A staged plan. Data migration, training and go-live in phases you can absorb.
Let’s talk
WhatsAppCallGet Started