Pilot Customers
30
Active pilot customers
CEF Portfolio Control Environment
Fund: Clean Energy Fund | Reporting Period: Last 7 days
GroSolar Pilot
A controlled first environment for validating data flow, vending visibility, collection behaviour, device gaps, and management response before scaling into EML.
Pilot Customers
30
Active pilot customers
Cluster A Efficiency
96.2%
Normal collections
Cluster B Efficiency
84.8%
Below seven-day average
Offline Meter Events
1
After vending attempt
Vending Events Today
48
Captured by feed
Field Actions
2
Open technical follow-ups
Infrastructure
Asset
Customers
Health score
Uptime
Collection efficiency
Last signal
Assigned team
Expected vs actual daily collections in NGN millions
| Event | Meter | Customer | Amount | Status |
|---|---|---|---|---|
| VEND-441 | MTR-014 | PILOT-C014 | ₦18,000 | Recovered after retry |
| VEND-447 | MTR-019 | PILOT-C019 | ₦26,000 | Pending review |
| VEND-452 | MTR-014 | PILOT-C014 | ₦22,000 | Linked to offline meter alert |
Meter MTR-014 stopped reporting after a vending attempt and must be reconciled against customer credit status.
The pilot is proving which data fields must be mandatory before customer growth.
Vending records are visible, but failed retries need cleaner event classification.
Meter heartbeat and payment callback should be tied into one incident record.
Customer issue signal should create both finance and technical review context.
Keep GroSolar as the first proof environment.
Use failed vending events to test finance reconciliation and technical escalation.
Define mandatory fields for meter ID, customer zone, transaction status, amount, and signal freshness.
Collections can be visible before full-scale rollout.
Device gaps must be handled as management exceptions, not hidden platform issues.
Pilot reports should become EML readiness evidence.
GroSolar is the first proof environment. It validates collections, device signals, alerting, and field response before the model is expanded.