Skip to content
SecurityGuidesSafety

Health and safety patrols on open car parks

How to run recurring patrols for abandoned vehicles, overheating EV batteries, fluid leaks, and fire risk on open car parks using thermal and PTZ on a wheeled quadruped.

OLO Robotics Team · · Updated · 6 min read

Open car parks carry quiet health and safety risks that only show up when something goes wrong: a vehicle that has not moved for a month, a warm battery pack on a charger row, a dark patch under an engine that was not there last week, or a bay blocked when fire routes need to stay clear. Walk-rounds drift. Fixed CCTV does not follow the bays that matter. What estates and security teams need is the same loop, the same camera angles, and a dated record per stop so review is comparison, not memory.

This guide is for facilities, estates, and security leads who patrol large open-surface car parks for health, safety, and enforcement issues on the parking surface itself. It covers thermal and PTZ capture on a wheeled quadruped for long-stay and abandoned vehicles, overheating EV batteries, fluid leaks, charger heat, and blocked fire routes. The patrol workflow sits in our routine automated security patrols overview.

What car park patrols should catch

When enforcement, insurance, or the fire service asks what you knew and when, gaps usually look like this:

  • Abandoned and long-stay vehicles. No fixed frame on each bay block, so a car that arrived weeks ago blends into every other still.
  • EV and charger heat. Pack or cable joints warm on thermal long before smoke is visible on a quick visual pass.
  • Fluid leaks. Oil, coolant, or ad‑blue pools under bays are easy to miss at walking speed and become slip or environmental hazards.
  • Fire routes and pinch points. A vehicle parked across a ramp crown or exit aisle is a health and safety finding, not only a nuisance.
  • Fly-tipping and refuse. Piles along fence lines can hide heat and block pedestrian paths between rows.

Fixed stops that still read in six months

Walk the surface with security and facilities. Mark stops that stay meaningful as seasons and occupancy change. Charger banks, disabled bays, permit zones, and main pedestrian exits stay useful. Temporary event barriers do not.

Health and safety patrol stops on open car parks
StopWhy it worksWhat to watch
EV charger row or cable trayThermal baseline for pack and cable heat before smokeRain and frost shift apparent temperature; note conditions in the run log
Named bay block (for example row C bays 12–24)PTZ frame tight enough to spot plates, body style, and fluid stains week on weekMoving the waypoint breaks the archive; flag new vehicles, do not nudge stops
Ramp crown or deck fire routeCatches abandoned vehicles blocking egressStanding water and leaf litter; log, do not skip the stop
Permit or long-stay zoneEnforcement evidence with repeatable framingAgree plate visibility and GDPR handling before you store stills
Contractor compound or moving barriersPoor fixed stopMoves weekly and breaks side-by-side comparison

Large open surfaces suit wheeled quadrupeds better than tight multi-storey decks with low clearance. If your route includes stairs between levels, read picking the right robot for the patrol route before you fix hardware.

Thermal: fire risk, chargers, and heat anomalies

Thermal is not a replacement for a certified fire system. It is an extra scheduled pass that highlights heat you would miss on a visual walk:

  • EV batteries and charger runs. Elevated temperature on a pack, gun, or cable joint against a cool row of parked cars.
  • Combustion vehicles. Unusual bonnet or underbody heat on a static vehicle worth a human check before occupants return.
  • Refuse and fly-tipping. Composting heat under sheeting along fence lines.

Save a thermal still at each stop with the same palette and stand-off every run. Flag spikes for human review unless your procedure already defines thresholds. Our thermal inspection in simulation demo shows capture on a quadruped payload; on site you apply the same idea at charger rows and bay blocks.

PTZ: abandoned vehicles, leaks, and enforcement evidence

PTZ gives a repeatable visual frame at each waypoint for problems that evolve slowly:

  • Long-stay and abandoned vehicles. Same zoom and pan on bay blocks so a vehicle that never moved for fourteen days is obvious when you scrub runs.
  • Fluid leaks and stains. Dark patches under engine bays, diffs, or sumps compared with the reference still for that bay.
  • Blocked bays and damage. Open doors, broken glass in parked cars, deflated tyres, or debris in fire lanes.
  • Operational records. Timestamped stills for lease enforcement, insurance, or handover without arguing when the photo was taken.

Agree whether number plates are in scope for your policy and GDPR process. Many estates store full frames internally and share redacted exports externally.

Camera rules worth agreeing upfront

  1. Dual capture at charger and thermal stops. Thermal still plus matching PTZ wide or tight bay shot, saved as one named action in the mission.
  2. Presets, not live tweaking. Field of view, zoom, and pan saved in the route. Operators adjust only under teleop with a reason logged.
  3. Night or quiet window. Patrol when the site is quiet and headlights do not wash every frame when you can.
  4. Weather. Wet tarmac changes thermal read. Note heavy rain or frost on the run.
  5. Escalation. Charger heat, large fluid pools, or blocked fire routes go to facilities or the fire liaison path in your procedure—not only to security logs.

Name stops and runs in OLO

Place a waypoint at each patrol stop and name it the way your control room already does: charger row A, row C bays 12–24, north ramp crown, permit zone B. Thermal and PTZ captures stay in the recording with the waypoint name and run time. Name the scheduled round as well (night loop, weekday estate code) so whole patrols are easy to find alongside each stop.

A two-week pilot on one loop

  1. Days 1–2: Walk the loop with security and facilities. Mark charger rows, bay blocks, ramp crowns, and permit zones. Drop stops tied to temporary barriers.
  2. Days 3–5: One manual patrol at every stop. Agree thermal palette, PTZ presets, and naming. Treat this set as the contract reference.
  3. Week 2: Map in OLO, place waypoints, and run the first autonomous rounds on schedule.
  4. End of week 2: Compare reference and autonomous runs. If the control room would act on long-stay, leak, or thermal flags from the recording, keep the schedule.

Try night-loop waypoints in simulation on the personal plan. When you are ready to map your car park, talk to our team or compare plans.

For the developersof robotics.

Test in simulation. Visualise, teleoperate and script in the browser. No installation required.

TypeScript and Python SDKs
Browser-based development
AI-assisted code generation