Construction · mixed site estate · fleet-of-plant
Secure remote monitoring for mixed construction site estates
TrackSyte® delivers secure remote asset monitoring for mixed construction site estates — security towers, PID, plant, generators and hybrids, pumps, welfare and the other hire assets that share one compound. One gateway. CAN, Modbus, Ethernet, LTE — into one monitoring stack, so exceptions across asset types reach TrackSyte® Portal before scattered truck rolls become the default.
This is construction plant remote monitoring / mixed plant asset monitoring for a fleet-of-plant site estate — not generic fleet-management software, not a utilisation / idle% plant-ops FMS, and not a LiveLink or Trackunit replacement. It is a multi-protocol field gateway plus Portal for site assets. GNSS is fitted as standard on Neo 2 — a full-constellation GPS/GNSS receiver that can support tracking and GPS-related functions, alongside the gateway and Portal monitoring stack. For deep plant / CAN machine telematics, see construction equipment telematics — that page owns protocol depth for excavators, diggers and dumpers; this page owns the mixed estate view.

Why mixed construction fleets still run blind
Scattered construction assets still run half-blind across UK sites. A silent CCTV tower, a genset that stopped overnight, a sump that stopped clearing, or a piece of plant that needs a status check often only shows up when someone drives out — or when a client calls asking why the compound went dark. By then the visit cost is spent across asset types that could have shared one operational view.
That pattern is expensive for main contractors and hire desks: unused call-outs across towers, pumps and power burn fuel and margin because nobody could see which exceptions were real.
Remote visibility across mixed asset types closes that gap without inventing fleet-locator SaaS claims beyond confirmed Neo 2 positioning — one Portal for the operational estate, not another van-telematics dashboard.
What one Portal view covers across asset types
With TrackSyte® you see mixed construction assets in one Portal view — towers, power, pumps, welfare and plant status where each asset is wired into the gateway stack. Status and alerts surface so ops and hire desks can prioritise real faults across types: offline links, power anomalies and site conditions that justify a visit, versus noise that can wait until morning.
Ops, hire desks and site managers share one estate view — useful when the person who can fix a tower SIM is not the plant fitter. Clear status reduces duplicated truck rolls when several asset types sit on one compound.
Fewer unnecessary visits across a mixed fleet means lower operating cost. See commercial impact or the site visit calculator. TrackSyte is built for UK hire fleets from Cornwall — About covers who we are.
How Neo 2 connects a mixed site fleet
TrackSyte Neo 2 is the multi-protocol gateway for a mixed construction estate. Interfaces fitted and in scope: Ethernet, RS485 (on Neo 2 — not Hub-only), CAN, 12V, Bluetooth, cellular IoT (LTE-M / NB-IoT), and full-constellation GNSS as standard. Which protocol leads depends on the asset.
Security towers typically lead Ethernet / LTE / GPIO (RS485 where the perimeter needs it). PID / perimeter often uses LTE / Ethernet / GPIO / Modbus / RS485. Generators, hybrids and BESS lean on RS485/Modbus, Ethernet, cellular, and Victron/BMS/Smart Shunt where fitted. Pumps and sumps use RS485/Modbus, Ethernet, cellular and GPIO. Construction plant leads on CAN — with deep proof on construction equipment telematics and the CAN bus capability page.
Capability explainers: Ethernet, RS485 / Modbus, cellular IoT, CAN bus. Family depth: hardware integrations. We do not invent Canvas naming, Offer prices, fake compliance seals, or fleet-locator marketing beyond confirmed Neo 2 positioning.
- Ethernet, RS485 (Neo 2 — not Hub-only), CAN, 12V, Bluetooth
- LTE-M / NB-IoT cellular IoT
- GNSS fitted as standard — full-constellation GPS/GNSS that can support tracking and GPS-related functions
- Towers → Ethernet / LTE / GPIO; PID → LTE / Ethernet / GPIO / Modbus / RS485
- Power → RS485/Modbus · Ethernet · cellular · Victron/BMS/Smart Shunt where fitted
- Pumps → RS485/Modbus · Ethernet · cellular · GPIO
- Plant → CAN (machine bus) — deep proof on CET
Construction fleet monitoring vs construction equipment telematics
These two pages serve different jobs — keep them distinct for buyers and for search.
This page owns the mixed site estate under one Portal: towers, security PID, power, pumps, welfare, plus plant as one operational estate (fleet-of-plant). The story is gateway + secure remote asset monitoring across asset types — construction plant remote monitoring and mixed plant asset monitoring, not utilisation FMS. Head phrasing: mixed site estate / fleet-of-plant remote monitoring.
CET (/construction-equipment-telematics) owns deep CAN / machine telematics for construction plant (excavators, diggers, dumpers, etc.). The story is protocol-depth + plant proof. Head phrasing: construction equipment telematics / plant CAN.
Plant-telematics giants that lead on utilisation, idle time and machine-ops dashboards typically leave the CCTV / PID / Victron–EFOY unify gap this page fills. If the conversation starts with excavators and machine buses, start on construction equipment telematics and CAN bus. If it starts with a whole compound under one Portal, stay here. Do not rewrite CET’s CAN-deep H2s here, and do not chase “fleet management software”, “fleet telematics software” or “GPS fleet tracker” as the head claim.
Typical setups
Main contractor compound. A live build site with security towers, temporary power, pumps and some plant needs one operational view. Neo 2 paths vary by asset; Portal unifies exceptions so the diary is driven by real faults, not standing check visits.
Hire desk multi-asset fleet. Hire operators with towers, gensets, pumps and welfare scattered across counties need one place to see which assets are healthy. Portal is that shared view — not a generic fleet-SaaS product for vans.
Civils site with pumps, generators and towers. Wet-site and power compounds often sit next to perimeter towers. Cross-link pump and sump monitoring and hybrid and temporary power for depth; keep this page as the mixed-estate umbrella.
Plant-heavy yard → soft handoff to CET. When the estate is mostly excavators, diggers and dumpers and the conversation is machine-bus depth, hand off to construction equipment telematics. This page still covers the surrounding site assets; CET owns the plant CAN story.
- Main contractor compound — towers, power, pumps, plant
- Hire desk multi-asset fleet
- Civils site with pumps, generators and towers
- Plant-heavy yard — soft handoff to CET for CAN depth
Security — physical site and cyber basics
Physical. Construction fleets sit on compounds and temporary sites where theft, tamper and overnight outages are real. Remote monitoring of power, connectivity and status supports that job across mixed types — without replacing cameras, PID panels or manufacturer controllers.
Cyber. Authentication, TLS, certificates and MQTT protect the data path. We state those basics plainly; no invented ISO, SOC or compliance badges.
FAQs
Is this fleet management software?
No. TrackSyte’s primary category is secure remote asset monitoring via a multi-protocol gateway plus Portal for mixed construction site estates (fleet-of-plant). This is not utilisation / idle% plant-ops FMS, not a LiveLink or Trackunit replacement, and not generic fleet-locator software for vans. Plant CAN depth lives on construction equipment telematics.
How does this differ from construction equipment telematics?
This page owns the mixed site fleet under one Portal (towers, PID, power, pumps, welfare, plus plant as one estate). CET owns deep CAN / machine telematics for excavators, diggers and dumpers. Start on CET when the conversation is plant/CAN depth; stay here for the whole-compound view.
Does Neo 2 include GPS / GNSS for construction fleets?
Yes. GNSS is fitted as standard on Neo 2: a full-constellation receiver that can support tracking and GPS-related functions, alongside the gateway and Portal monitoring stack. We do not invent fleet-locator marketing beyond confirmed Neo 2 positioning.
Does Neo 2 support CAN and RS485 on mixed estates?
Yes. Neo 2 is fitted with Ethernet, RS485 (not Hub-only), CAN, 12V, Bluetooth, cellular IoT and GNSS as standard. Plant typically leads on CAN; pumps and power often lead on RS485/Modbus. See /capabilities/can-bus and /capabilities/rs485-modbus.
Where should plant-heavy buyers start?
If the estate is mostly excavators, diggers and dumpers and the conversation is machine-bus depth, start on /construction-equipment-telematics. This page still covers surrounding site assets under the same Portal.
See construction fleet monitoring on a demo
If you run a mixed construction site fleet and want one Portal view across towers, power, pumps and plant, book a demo. We will map Neo 2 interfaces by asset type, show Portal exceptions, and point you to construction equipment telematics when the conversation goes deep on CAN plant. Bring a real estate shape if you can; we map honestly and stay inside product truth.
