Fueltek case study · Plant & machinery
S.E. Davis & Son
Three fuel products managed through one integrated site system.
S.E. Davis & Son required a complete system capable of handling diesel, gas oil and AdBlue while giving the business one joined-up approach to storage, dispensing, monitoring and reporting.
Sector context image
Project approach
From operational problem to working system.
A triple-compartment tank, Twin dispenser and dedicated AdBlue unit brought three products into one managed site arrangement.
Control three products without splitting the operation into separate systems
- The site needed secure storage capacity for three different products.
- Diesel and gas oil required managed dispensing alongside a dedicated AdBlue solution.
- Tank information and transaction reporting needed to sit within one operational workflow.
Combine multi-compartment storage with dedicated Fueltek hardware
- Installed a 52,500-litre triple-compartment tank: 35,000 litres diesel, 15,000 litres gas oil and 2,500 litres AdBlue.
- Used an FT4000AP Twin for diesel and gas oil with an FT4000AB for AdBlue.
- Added TankWatch across all three compartments together with Fueltek FMO, commissioning and staff training.
Project in context
The brief, explained in more detail.
The project brought together the equipment and operating processes described below. Explore how the installation worked and the considerations for a similar system at your site.
Three products, with a dedicated path for each.
S.E. Davis & Son required controlled storage and dispensing for diesel, gas oil and AdBlue. The aim was a joined-up operating and reporting approach while keeping the physical storage and dispensing requirements of the three products distinct.
Fueltek installed a 52,500-litre triple-compartment tank: 35,000 litres for diesel, 15,000 litres for gas oil and 2,500 litres for AdBlue. An FT4000AP Twin served diesel and gas oil, with an FT4000AB providing the dedicated AdBlue dispensing route.
TankWatch covered all three compartments, and FMO, commissioning and staff training completed the described package. The result was one managed facility with product-specific equipment. Its value lies in coordinating the fuel paths and their records, rather than treating different fluids as interchangeable within one dispenser.
System architecture
How the Fueltek layers worked together.
A fuel-management project normally has several distinct jobs to do: physically store or dispense product, decide who is allowed to use it, measure what is held in storage, and turn activity into information that managers can review. The cards below show the roles of the systems connected with this case study.

Integrated twin dispensing with managed transactions
The FT4000AP Twin brings two dispensing positions or product paths into one managed arrangement. The important point is not simply having two hoses: both dispensing paths sit within the same controlled fuel-management approach, allowing the site to avoid running separate unmanaged dispensing equipment where a combined installation is more practical.
Explore FT4000AP Twin →
Dedicated AdBlue dispensing and management
The FT4000AB provides a dedicated managed dispensing route for AdBlue. In multi-product projects this keeps AdBlue separate from diesel or gas-oil dispensing while allowing it to sit within the wider Fueltek management and reporting structure. That is useful where the site wants one operational approach without pretending every stored fluid can share the same pump hardware.
Explore FT4000AB →
Independent tank-level and stock monitoring
TankWatch measures what is physically held in the storage tank using tank probes and a local control layer. That gives the operator information such as current stock, available capacity, deliveries, stock movements and throughputs. It complements pump transaction data because it answers a different question: the pump records what the system says was dispensed, while tank monitoring measures what is actually happening in storage.
Explore TankWatch →Operational workflow
From fuel on site to usable information.
The steps below explain the roles of the technologies discussed in this project. The exact operating sequence depends on the equipment and identification process specified for the installation.
Store & receive
Bulk product is received into the site storage arrangement. Tank capacity, product compatibility and delivery access are part of the physical specification before the management system can add useful control.
Authorise
The managed dispensing layer checks that the user or vehicle is permitted to draw fuel before the transaction proceeds. The exact identification method depends on the project configuration.
Dispense & record
Fuel is dispensed through the managed pump or controller. The quantity dispensed becomes a transaction record rather than remaining only as a mechanical pump total.
Measure stock independently
TankWatch measures the physical tank level. This gives the operator a second information source for stock, deliveries and movements alongside the pump transaction record.
Planning a similar project
What should be defined before specification.
The case-study equipment should not be copied blindly. A new installation needs to be sized and configured around the actual operation. These are the main questions We need to understand before choosing the appropriate hardware and software.
Fuel & storage
Which products are stored? What is the expected daily usage, peak usage, delivery frequency and reserve requirement? These answers influence tank capacity and whether multiple compartments are appropriate.
Vehicles & dispensing
Vehicle type, fill-point position, desired flow rate, hose reach and simultaneous fuelling demand determine the practical pump, hose and nozzle arrangement.
Access & accountability
Define whether authorisation should be tied to a driver, vehicle, department, contractor or another operational identity, and what information needs to be captured with each transaction.
Tank visibility
Decide what the site needs to know about physical stock: current level, ullage, deliveries, movement, alarms and how that information should be reconciled with pump transactions.
Reporting & users
Identify who needs reports, whether the organisation is single-site or multi-site, which managers need local or central access and what exceptions should be easy to investigate.
Installation & handover
Existing equipment, electrical and data connections, vehicle movements, groundwork, commissioning windows, staff training and any fixed go-live date all affect the delivery plan.
Apply the learning
What to take into your own project.
For a similar multi-product site, specify each compartment, pump, hose and identification workflow around its intended fluid. Then agree how the separate records and tank information will be reviewed within the wider operation.
Read the project outcome →Case-study FAQ
Project detail and specification questions.
These answers separate the recorded facts of this case study from the decisions that would need to be made for a new installation.
What was the main issue this plant & machinery project needed to solve?
Control three products without splitting the operation into separate systems. The site needed secure storage capacity for three different products. Diesel and gas oil required managed dispensing alongside a dedicated AdBlue solution.
Which Fueltek systems are connected with this case study?
This project brought together FT4000AP Twin, FT4000AB and TankWatch. Each system has a distinct role in fuel control, storage, monitoring or reporting.
Why use both pump records and tank monitoring where both are installed?
They measure different parts of the operation. Managed dispensing records the authorised transaction at the pump, while tank monitoring measures physical stock and movements in storage. Reviewing both gives the operator more context than either source on its own.
Would a new project use exactly the same specification?
Not automatically. A similar project should be specified around fuel type, storage capacity, peak dispensing demand, hose reach, user and vehicle access, communications, reporting requirements, installation constraints and any existing equipment that is suitable to retain.
What should be defined before a site survey or quotation?
Useful starting information includes the products to be stored, approximate daily and peak usage, current tank and pump details, vehicle types, required flow rate, number of users or vehicles, preferred access method, reporting expectations, communications available at the site and any installation or handover deadline.
Project outcome
What changed.
The completed facility brought all three products into one managed site arrangement supported by tank monitoring, browser-based reporting and staff training.
Relevant Fueltek systems
Explore the technology used.
Equipment is specified around the site, fuels, users, reporting requirements and existing infrastructure. The links below show the closest current Fueltek product areas connected with this project.
Plan your own system
Have a similar operational challenge?
Fueltek can review your tanks, pumps, vehicles, users, reporting requirements and existing equipment before recommending the most practical route forward.
Customer feedback
“The sales and after service we have received from Fueltek has been excellent.”
Director, S.E Davis & Son
Customer feedback from this installation.