A hospital facilities team needed Veeder Root fuel tank data exposed to a BACnet/IP building automation system under a tight validation window. Chipkin QuickServer replaced a legacy gateway path and delivered a working fuel-monitoring handoff in time for on-site BAS verification.
This project mattered because the monitored system was part of a hospital’s critical infrastructure. The customer needed dependable fuel tank visibility on the BAS side, but the existing gateway history did not transfer cleanly to the new deployment. The new installation had to be rebuilt around the actual Veeder Root setup, the current BAS requirements, and the schedule of the on-site technician validating the handoff.
At a Glance
- Industry: Healthcare / facilities infrastructure
- Customer: Hospital facilities team
- Facility type: Hospital campus
- Client role: Maintenance and building automation stakeholders
- Project scale: 2 monitored fuel tanks on a hospital BAS
- Protocols: From: Veeder Root over RS-485 → To: BACnet/IP
- Chipkin product: Chipkin QuickServer Enhanced FS-QS-2XX0
- Project start: October 2021
Veeder Root fuel tank system → RS-485 → Chipkin QuickServer → BACnet/IP hospital BAS
Veeder Root to BACnet/IP Challenge
The upstream/server side was a Veeder Root fuel tank monitoring system using serial communication. The downstream/client side needed those values on a BACnet/IP building automation platform. For the hospital team, this was not a nice-to-have dashboard project. It was part of an operational visibility workflow tied to emergency-power readiness and facility awareness.
The project had two practical challenges. First, the new QuickServer deployment could not rely on an older gateway path as a drop-in shortcut. The configuration had to be rebuilt around the current Veeder Root system documents and the actual site layout. Second, the customer had a live scheduling constraint: an on-site BAS technician visit was already approaching, so the configuration handoff had to happen quickly enough to be validated during that window.
The integration also needed to account for real site details, including two fuel tanks, RS-485 source communication, and the BAS-side expectations for discovery and point visibility. That made the project a good example of a deadline-driven facilities integration rather than a generic lab setup.
Why Chipkin
This was a strong fit for Chipkin because the customer needed a gateway platform plus responsive engineering support under schedule pressure. Chipkin QuickServer provided the protocol conversion path, but the project still depended on collecting the right Veeder Root system details, rebuilding the mapping around the current installation, and getting a usable configuration to the customer before the BAS validation window closed.
Chipkin support added value by moving quickly once the site documents were in hand. Instead of turning the project into a long discovery cycle, the team narrowed the requirements, rebuilt the config around the real system setup, and kept the customer moving toward BAS discovery and validation.
The Solution
Chipkin gathered the Veeder Root system setup details, node information, BAS point expectations, and site communication settings needed to build the new Chipkin QuickServer deployment. With that information in place, the team created a fresh configuration for the QuickServer Enhanced instead of trying to force-fit an older gateway pattern into a new environment.
The work centered on exposing the serial fuel tank data to the downstream/client BAS over BACnet/IP and making sure the BAS side could actually discover the device during the customer’s validation window. Same-day iteration mattered here because the on-site BAS technician was already scheduled.
After the updated configuration was loaded and tested, the customer was able to find the device on the BAS and move into normal validation with the site technician instead of still waiting on gateway readiness.
Fuel Tank Monitoring Results
The project delivered a working Veeder Root to BACnet/IP handoff for a hospital facilities deployment.
Project proof points:
- 2 fuel tanks were brought into the monitoring scope.
- The configuration was rebuilt around the current site documents instead of depending on an older gateway history.
- A same-day delivery cycle helped the customer meet a live BAS technician validation window.
- The device became discoverable on the BAS after the updated configuration was applied.
The customer’s confirmation captured the outcome clearly:
“It looks to me like the device is connected. I can find it on the BAS. So, I’ll make sure that everything looks good to the Siemens tech, but for now I think we’re good!! Thank you all!”
— Maintenance technician, hospital facilities team
Have a Similar Veeder-Root-to-BACnet Project?
Need to expose Veeder Root fuel-system data to a BACnet/IP BAS without losing time to commissioning delays? Chipkin can help with QuickServer configuration, serial-to-BACnet integration, and site-ready validation support. Tell us about your project.