top of page

The Tower Stayed Online. Costs Climbed.

19 minutes ago
3 min read

An energy review for Nigerian TowerCo and telecom decision makers.


A tower can meet its availability target and still need a closer look at its energy costs. Consider an illustrative October review: the site stayed online throughout the reporting period, yet its power bill increased. Finance wants an explanation. The next fuel allocation is due.

Finance and Operations need the same operating record to establish what changed. A higher bill could reflect more site load, a change in energy prices or a greater reliance on generator power. It could also reveal an operating pattern that deserves investigation.

For leaders managing towers across Nigeria, October is a practical moment to examine those differences before the next maintenance and spending decisions.||


Separate the price change from the operating change


Start with comparable periods and a complete enough record. Check total energy consumed, each source's contribution and the costs used in the calculation. Identify equipment additions, outages and gaps in monitoring that could distort the comparison.


If consumption rose after equipment was added, part of the increase may be expected. If energy use stayed similar but generator contribution increased, examine the supply and operating sequence. Confirm which organisation carries the relevant energy and maintenance costs under the site's arrangements.


This gives Finance and Operations a specific explanation to test, rather than treating every increase as a maintenance failure.


A Lagos example worth examining

At Kikspro Meats and Farmers Market, a Lagos cold-chain business, enee.io's published case study reports that diesel supplied 16% of energy consumed but accounted for almost half the monthly energy cost. The investigation identified generator-use and switching issues despite substantial grid availability. [1]


Working with Boyls Engineering, monitoring was combined with changes to generator dispatch and automatic transfer switching. This was a cold-chain installation. Its relevance to tower operations is the investigation: establish how power-source choices affect the bill before forecasting what a particular site can save.


 

Examine why the generator keeps running


For a tower site, place generator events alongside grid information, battery behaviour and site load. If generator operation continues after grid supply returns, ask the engineer to establish the reason.


Supply quality, charging requirements, transfer settings or operational delays may explain the sequence. A start or stop event alone cannot establish whether runtime was unnecessary. Check the engineering records and operating requirements before changing settings.


Prioritise repeated patterns and material costs. Compare sites with similar configurations and operating conditions, then assign the investigation to a named owner. Use the site's measured fuel consumption and applicable prices when assessing the cost of any runtime that can be avoided.


Give seasonal maintenance an operating record


As harmattan preparation progresses, connect local conditions with the equipment maintenance plan. Cummins advises more frequent maintenance for generators operating in hot or dusty conditions. Apply the relevant manufacturer's guidance and inspection findings at each location. [7]


Review repeated warnings with the maintenance team. A recurring alert should lead to a documented investigation and a follow-up review of the readings after work is completed. That record helps establish whether the operating pattern changed.


Bring the evidence into the next decision

enee.io brings monitored energy-source and consumption information into site reporting. Proteus supports comparisons across monitored locations and reviews of recurring issues. Teams can use those records to prioritise technical investigation and support maintenance or investment discussions. [2] [3]


For the next review, select one site with a rising power bill. Record the suspected driver, the evidence available and the action needed to verify it. Agree who will investigate and when the team will review the result.


Bring that site question to an enee.io demonstration. Which operating pattern would your team most want to understand before approving the next tower power spend?



Sources

Sources checked on 22 October 2026. Keep the relevant links with the published article and the case credit in the video.

Source for the 16% energy and almost half the energy-cost comparison, the site context and the work with Boyls Engineering.

Source for voltage, current, optional battery-temperature monitoring and historical site information.

Source for site comparisons, reporting and recurring-issue review.

Source for configured generator, grid, ambient-temperature and battery alerts; availability depends on monitoring scope and battery type.

Distinguishes inspection and initial measurements from controlled discharge testing.

[6] Schneider Electric  Easy UPS runtime calibration guidance

Supports the general dependence of battery runtime on load, charge and age. Its product-specific test procedure is not a tower testing instruction.

Source for maintenance recommendations in hot or dusty operating conditions.

Stay up to date

Subscribe to our mailing list and keep up to date with our exciting developments. We won’t share your details and you can unsubscribe at any time.

enee.io is the fitness tracker for energy systems

Customers
Login
Support

enee.io increases access to reliable and affordable energy by improving the life and efficiency of energy systems. Through plug-and-play sensors, mobile phone applications and web-based reporting, enee.io provides customers with the information they need to optimize energy usage, improve energy system health and safeguard backup power supplies.

Follow us!

  • LinkedIn
  • Instagram
  • Facebook

enee.io Ltd, DiSH Manchester, Heron House, 47 Lloyd Street, Manchester, UK, M2 5LE

Copyright 2023   Registered in England and Wales. Company No: 12189365. VAT No. 334 3660 13.

bottom of page