Fueltek case study · Emergency services
Norfolk Fire & Rescue
Four complete fuel-management sites built from the ground up.
Norfolk Fire & Rescue was introducing fuel management for the first time. The project therefore combined physical infrastructure with training, commissioning and support so the service could operate the new systems confidently.
Sector context image
Project approach
From operational problem to working system.
Norfolk’s first managed-fuel deployment combined four complete installations with commissioning, training and ongoing support.
Build resilient coverage for a large rural county
- There was no existing fuel management system across the selected sites.
- Four strategically positioned locations were needed to support emergency vehicles across Norfolk.
- Training and practical understanding were as important as the hardware because this was the organisation’s first managed-fuel deployment.
Install complete systems and train the teams who would use them
- Installed complete Fueltek storage and dispensing packages at King’s Lynn, Great Yarmouth, Dereham and North Earlham.
- Integrated FT4000 fuel management with the storage tanks and added TankWatch monitoring.
- Connected FMO reporting and provided commissioning, user training and ongoing support.
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.
A first deployment with a practical handover.
Norfolk Fire & Rescue was introducing fuel management for the first time at the selected sites. Four strategically positioned locations were required to support emergency vehicles across a large rural county. The project therefore had to establish both the physical fuel facilities and the knowledge needed to use them.
Fueltek installed complete storage and dispensing packages at King’s Lynn, Great Yarmouth, Dereham and North Earlham. FT4000 management was integrated with the storage tanks, TankWatch added monitoring, and FMO provided connected reporting.
Commissioning, user training and ongoing support formed part of the delivery. For an organisation moving to managed fuelling for the first time, the handover mattered alongside the hardware: staff needed to understand the operating process and the information available after a fuel issue.
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.
Complete fuel management
System roles
- Storage
- Dispensing
- Monitoring
- Reporting
Configured together around the site.
Storage, dispensing, monitoring and reporting as one project
A complete fuel-management package is useful where the organisation wants the storage, dispensing, access control, tank monitoring, reporting and commissioning to be designed together. The value is coordination: capacities, pump duties, user access, communications and reporting requirements can be resolved as one system rather than through several unrelated equipment decisions.
Explore Complete fuel management →FT4000
Authorised dispensing and transaction control
The FT4000 is the control layer at the fuelling point. It can be used to authorise dispensing, associate a transaction with an approved user or vehicle and create a structured transaction record instead of leaving the pump as an isolated piece of equipment. Where the project configuration captures additional fields such as mileage or identification data, those details can sit alongside the quantity dispensed so later reporting has operational context.
Explore FT4000 →TankWatch
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 first deployment, plan training and handover at the same time as the equipment. Include representative users and agree who will maintain identities, review records and raise support requests once the sites are operational.
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 emergency services project needed to solve?
Build resilient coverage for a large rural county. There was no existing fuel management system across the selected sites. Four strategically positioned locations were needed to support emergency vehicles across Norfolk.
Which Fueltek systems are connected with this case study?
This project brought together Complete fuel management, FT4000 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.
Norfolk Fire & Rescue gained a four-site fuelling network designed around resilience, remote visibility and straightforward operation by trained staff.
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.
