Connected operations · Buyer guide
What should you check before installing fuel or IoT monitoring?
A fuel and IoT monitoring checklist for Ethiopian sites: measurements, sensors, gateways, connectivity, calibration, alerts and management reporting.
Jump to the project checklist
The short answer
Define the decision you want to make, then check the equipment, measurement method, power and connectivity. A useful monitoring system connects a trustworthy reading to a dashboard and a responsible person. Fuel reconciliation also needs delivery and usage records; an alert alone does not prove a loss.
Choose the information that changes a decision.
| Operating question | Information needed | Site check |
|---|---|---|
| Is a tank running low? | A suitable level or volume reading and threshold | Tank geometry, probe compatibility and calibration |
| Did a generator stop? | Agreed running-state and power signals | Accessible equipment signals and backup power |
| Do fuel records reconcile? | Measured stock, deliveries and supported usage records | Time alignment, missing records and measurement uncertainty |
Check the measurement before trusting the screen.
A sensor must suit the asset and the environment. For a fuel tank, document dimensions, available fittings and the required reading. For a cold room, agree sensor location and the temperature range that matters. The equipment selection and installation belong in a site assessment.
A level reading and a volume estimate are different. Ask how calibration is performed and how abnormal or missing readings are identified. Equipment condition and the quality of existing records affect what conclusions a manager can draw.
Decide what happens when the connection is unavailable.
IoT architectures may connect devices directly to a platform or through a local gateway. A gateway can collect or translate readings and, when designed for it, handle selected local processing. The exact arrangement depends on the devices and requirements.
At each Ethiopian site, check available power and connectivity rather than assuming the same conditions everywhere. Specify whether readings are buffered, how gaps appear on the dashboard and which actions remain local. Test these behaviours before handover.
Give every alert an owner and a response.
Choose thresholds around a business action: check a generator, arrange a delivery or inspect an unexpected change. Agree who gets notified, when another person is contacted and how an event is closed. Too many low-value alerts can hide the important ones.
For fuel, compare the reading with deliveries, transfers and usage or sales records where available. Consider measurement and record problems before treating a discrepancy as an incident. A dashboard should make uncertainty visible.
Prove one site before connecting the rest.
Use a representative asset and test normal readings, a connection gap and an agreed alert. Compare the screen with an appropriate on-site check. Confirm timestamps, access permissions and the reports the manager needs.
Black Mount can assess monitoring and fuel requirements, install suitable equipment, connect the platform and train the people responding to readings. Multi-site expansion should repeat the verified setup while allowing for each site’s conditions.
Project checklist
Bring these to a monitoring assessment
- The assets, tank details or equipment signals to monitor
- The decision, reading frequency and reports you need
- Power and connectivity at each site
- Existing delivery, usage or sales records
- Alert recipients, response rules and acceptance checks
References & further reading
Primary sources for the technical background. Our comparisons and checklists are planning guidance; the project scope follows an assessment.
- Microsoft: IoT architecture design
Reference layers from sensing and networking through processing and presentation.
- Veeder-Root: automatic tank gauging
An example of equipment supporting fuel inventory visibility. Compatibility and procurement require assessment.