A fuel and convenience site — pumps, canopy, coolers and back-of-house plant.
IndustryWorked example / Fuel and convenience retail
What runs on the twinAsset records, serials and warranties, compliance dates
This is a worked example on a fuel-and-convenience demo twin rather than a customer deployment. It shows what an asset register looks like when every pump, cooler and rooftop unit is a place in the building you can look at, instead of a numbered row in a spreadsheet.
The problem this example is built around: the asset list exists, in a spreadsheet, with serial numbers and install dates — and it still cannot tell anyone which cooler row 14 refers to. Staff turnover takes that knowledge off site with it.
A new starter finds the asset by looking at it. The register stops being something you have to be here five years to read.
Worked example On a fuel-site demo twin — not a customer deployment
Every tracked asset is attached to the element it is — the cooler, the pump, the rooftop unit — with make, model, serial and warranty on the record. Finding one is looking at it rather than decoding a naming convention.
Compliance dates ride on the same record, so an inspection due is visible on the building rather than buried in a column somebody has to remember to sort by.
Assets in place:
Pumps, coolers and rooftop units tagged on the element they are.
Serials and warranties:
Make, model, serial and warranty carried on the record itself.
Compliance in view:
Inspection dates read off the building, not a column somebody must sort.
Bring the files you already have. We will show you the twin you keep for the life of the building.