Volume
8,412 gal
Product volume in the tank at the moment of the poll. Compared against the capacity and the low-volume threshold you set per tank, so a "delivery needed" alarm is a number rather than a hunch.
Tank monitoring
Tank levels read straight
off the Veeder-Root console.
A direct TCP connection to your TLS-350, TLS-450 or TLS-450PLUS, polled every five minutes. Volume, height, water, temperature and ullage for every tank, with alarms that reach a person rather than a log file.
- Poll interval 5 minutes
- Console commands 22
- Consoles TLS-350 · 450 · 450PLUS
- Alarm delivery Email + SMS
MADISON RD #4118
TLS-450PLUS · 10.24.8.11:10001 · polled 47s ago
In-tank inventory
- T1 / Regular 87 8,412 gal
- H 68.2 in
- H₂O 0.4 in
- 54.8 °F
- Ullage 2,338 gal
- 78%
- T2 / Premium 93 4,388 gal
- H 38.6 in
- H₂O 0.2 in
- 55.1 °F
- Ullage 6,362 gal
- 41%
- T3 / Diesel 1,802 gal
- H 16.4 in
- H₂O 1.9 in
- 53.2 °F
- Ullage 8,948 gal
- 17%
Device health
- Status Online
- Last poll 47s ago
- Last success 47s ago
- Last error None
- Consecutive failures 0
Recent commands
- System Inventory 09:41:12 OK
- In-Tank Status Report 09:41:14 OK
- CSLD Test Results 09:36:08 OK
- System Alarm Summary 09:36:09 Warn
Delivery needed
T3 Diesel below low threshold
09:36 · email + SMS sent
Illustrative rendering of the Location portal tank surface
What comes off the console
Five numbers per tank, every five minutes
ManageSync does not ask anyone to walk out and read a stick. It opens a socket to the automatic tank gauge, runs the command, parses the response and writes a reading. Fill percentage comes out of those five, not off the console.
Product height
68.2 in
Probe height, straight off the console. The value the gauge itself works from, kept alongside the derived volume rather than in place of it.
Water level
0.4 in
Water sitting under the product. Set a water threshold per tank and crossing it raises a high-water alarm on the next poll.
Ullage
2,338 gal
Remaining space in the tank. This is the number a driver needs before a drop, and the number that decides whether a full load will fit or overfill the tank.
Temperature
54.8 °F
Product temperature per tank, recorded with every reading.
Fill percentage · derived
78 %
Not a reading — volume against configured capacity, worked out on the dashboard so a 10,000-gallon tank and a 4,000-gallon tank read the same way. High and low thresholds are set per tank, not per site.
Capacity is set per tank, along with low, high and water thresholds. The thresholds are what turn a reading into an alarm, so they belong to the tank rather than to a global site setting.
Alarms
The console raises it. Somebody’s phone rings.
Six alarm types are tracked against every device. Critical alarms go out by email and by SMS, because a notification nobody sees is not a notification.
Alarm types
- 01
Leak
Raised from leak-detection results reported by the console.
- 02
Overfill
Volume crossing the configured high threshold for that tank.
- 03
High water
Water level above the per-tank water threshold.
- 04
Sensor fault
Liquid and smart sensor faults reported back from the console.
- 05
Delivery needed
Volume approaching the point where a drop has to be scheduled.
- 06
Low volume
Volume under the configured low threshold for that tank.
The path an alarm takes
- 01
Raised on a poll
The alarm is created from the parsed console response, not from someone reading a screen.
- 02
Deduplicated
A condition that persists across polls stays one alarm. It does not become a hundred messages.
- 03
Delivered
Critical alarms go out by email and by SMS through Twilio. Everything lands on the alarms page in the Location portal.
- 04
Acknowledged, then cleared
Acknowledge with a note so the next person knows what was done. Clearing is a deliberate manual act.
- Severity per alarm
- Deduplicated
- Acknowledge with note
- Manual clear
Command coverage
Twenty-two console commands, on a schedule or on demand
Each command carries its own poll schedule. Any of them can also be fired by hand from the manual command console, and the parsed report is stored the same way a scheduled one is.
The manual command console
Pick a supported command, run it against the device, and read the response. Useful when a technician is standing at the site, when an inspector asks a question, or when you want a fresh test result rather than the one from this morning.
- Runs against TLS-350, TLS-450 and TLS-450PLUS
- Raw response and parsed report both stored
- Same parser as the scheduled polls
- Four-digit TLS-450PLUS variants handled
Inventory & delivery
- System Inventory
- In-Tank Status Report
- In-Tank Delivery Report
- In-Tank Temperature Report
Leak detection
- In-Tank Leak Detect Report
- CSLD Test Results
- Tank Leak Test History
- Line Leak Test Results (PLLD)
- Line Leak Test History (PLLD)
System & alarms
- System Status Report
- System Alarm History
- System Alarm Summary
Sensors
- Liquid Sensor Status
- Liquid Sensor Alarm History
- Smart Sensor commands
TLS-450PLUS
- Four-digit command variants
Telemetry into the record
The gauge is also your compliance evidence
CSLD results and line leak tests already exist inside the console. ManageSync pulls them on a schedule, keeps the raw output, and parses it into structured compliance results.
Nothing gets retyped from a printout, and nothing depends on somebody remembering to file it. The compliance side reads what the hardware said.
CSLD TEST RESULTS · JUL 30 2026
TANK 1 REGULAR 87
TEST STATUS PASS
LEAK RATE
0.08 GPH
TANK 3 DIESEL
TEST STATUS PASS
LEAK RATE
0.11 GPH
- 01
Command runs
On its schedule, or on demand from the console page.
- 02
Raw response stored
The console output is kept as returned, so the original is always there to check.
- 03
Parsed into a result
Test type, tank, date and outcome, pulled out as structured fields.
- 04
Read by compliance
CSLD and line leak results land in the compliance pipeline as records the score can use.
In the portal
Where the telemetry lands
Live readings are only useful if they are in front of the person who can act on them, on the screen they already have open.
Readings update without a refresh
The tank surface is wired to Supabase Realtime. New readings and new alarms appear on screen as they land, so a dashboard left open on the back-office monitor stays current.
Daily reconciliation reports
A daily report per site, built from the readings already collected.
A dedicated alarms page
Not a badge buried in a menu.
Tanks monitored and devices online, on the dashboard
The Location dashboard carries a "Tanks monitored" card and a "Devices online" card. Two numbers that tell you whether the telemetry you are paying for is actually arriving.
Nothing for sites without tanks
Tank monitoring is a per-facility flag. Switch it off and the whole surface disappears for that location.
What it costs
Tank monitoring is $45 per location, per month
That is the Tank Monitoring plan: live levels, alarm monitoring, email and SMS alerts and daily reconciliation reports, on top of everything in the Marketplace plan. The $60 Compliance plan adds state and EPA reporting, the compliance scorecard and the walkthrough portal.
- Tank Monitoring $45
- Compliance $60
Questions
Hardware, network and everything else
Which tank gauge consoles does ManageSync support?
Veeder-Root TLS-350, TLS-450 and TLS-450PLUS, over a direct TCP connection. The integration is validated against real hardware. Twenty-two preset commands are supported, including the four-digit command variants used by the TLS-450PLUS and the Smart Sensor commands.
What does the console need on the network?
A reachable host and TCP port. ManageSync opens the socket, issues the command and reads the response. Nothing is installed on the console, and there is no local gateway or polling PC sitting in between. Each command can carry its own poll schedule, and the standard inventory poll runs every five minutes.
What happens if a console goes offline?
Every device carries a health record: last poll, last success, last error and a consecutive failure count. Readings hold their last known values rather than vanishing, and the failure count makes a flapping connection obvious before anyone phones it in. When the console comes back the schedule resumes, and you can run any supported command manually to catch up.
How do alarms reach me?
Six alarm types are tracked: leak, overfill, high water, sensor fault, delivery needed and low volume. Each alarm carries a severity and is deduplicated, so a condition that persists across polls stays a single alarm. Critical alarms are sent by both email and SMS through Twilio. Acknowledge an alarm with a note, or clear it manually, from the alarms page in the Location portal.
How does tank telemetry feed compliance reporting?
Reports pulled from the console are stored raw and then parsed into structured compliance results. CSLD test results, tank leak test history and line leak (PLLD) results arrive in the compliance pipeline with a test type, a date and an outcome, which is what the compliance score reads from. Nothing is retyped from a printout.
We run sites without tanks. Can we hide all of this?
Yes. Tank monitoring is controlled by a per-facility flag. Turn it off and the entire tank surface disappears for that location: no tanks, no readings, no alarms page. Sites that do have tanks are unaffected.
Get started
Put your consoles on the screen
Bring a site, a console and a network path. We open the socket on the call, and your own tank readings land in the dashboard before we hang up.