ParkSense AI
Explore the product Request a demo
Request a demo Explore the product

Platform

Every vehicle and every space, in one operating view.

ParkSense analyzes camera video on site, keeps a current map of your lot and records what it sees as structured events. Your team searches, follows and reviews from one place, and the exceptions that need judgment reach a person who can act.

Explore the product Request a demo
  1. 03Structured eventsTyped, placed, timestamped
  2. 02Operator experienceSearch · map · timeline · review
  3. 01Edge processingOn site, next to the cameras

How it fits together

Three layers, each with one job.

The edge sees, the operator view makes it usable, and events make it shareable. Together they replace scattered feeds, walk-arounds and radio calls with a single picture of the lot.

  1. 01 / 03

    Edge processing on site

    Analysis runs on hardware at your facility, close to the cameras. It maps what each camera sees onto your zones, rows and spaces and turns that into observations, so the site relies less on streaming continuous video somewhere else.

    • Camera-to-space mapping
    • On-site analysis
    • Designed to keep working through network interruptions
  2. 02 / 03

    Operator experience

    One view for the people who run the lot: search for any vehicle, a spatial map of zones, rows and spaces, occupancy, an event timeline and a review queue with assignment and notes.

    • Vehicle search
    • Spatial lot map
    • Occupancy
    • Event timeline
    • Review queue
  3. 03 / 03

    Structured events

    Every observation is written as a consistent, documented record with a type, a place and a time. Reports and other authorized systems read the same events your team sees on screen.

    • Documented event types
    • Stable identifiers
    • Review history

Capabilities

What your team can do with it, every day.

01 — Find any vehicle

Find the right vehicle without walking the rows.

Search your inventory by stock reference or description and see where each vehicle was last observed: zone, row and space, with the time it was seen. Porters stop hunting, and sales staff walk a customer straight to the car.

  • Search by stock reference, description or zone
  • Last-observed location with its timestamp
  • Older observations are marked stale, never shown as current
Vehicle search Sample site
white compact SUV

3 vehicles · sorted by last observation

  • STK-24817 North display · R2 · 06 Compact SUV · White Seen 12:25
  • STK-24533 Service lane · 02 Compact SUV · White Seen 12:19
  • STK-24790 South display · R1 · 07 Mid-size SUV · Pearl StaleLast seen 10:02
Illustrative product view · synthetic identifiers

02 — Understand every space

A digital map of your lot, down to the space.

ParkSense keeps a map of your zones, rows and individual spaces and shows the state of each one: occupied, open, held for a test drive or waiting on a review.

When a zone has not been observed recently, the map says so plainly. Unknown is shown as unknown, not filled in from an old count.

Lot map · 12:31 Sample site
North display51 / 66
South displayAwaiting observations
Service lane5 / 8
Customer parking13 / 32
  • Occupied
  • Open
  • Held for test drive
  • Search result
  • Needs review
  • Awaiting observations
Illustrative product view · synthetic lot

03 — Follow movement over time

Every move becomes part of the vehicle’s history.

When it arrived, where it was staged, when it left on a test drive and where it was parked on return. Managers can answer “where has this car been today?” from the timeline instead of a walk-around.

  • A day timeline for any vehicle or space
  • Test drives logged out and back
  • Arrivals and departures for commercial parking
STK-24817 · Today Sample site
  1. 07:02 ArrivedService lane · 02 vehicle.located
  2. 09:18 Staged for displayNorth display · R3 · 14 vehicle.moved
  3. 11:40 Out on a test driveExit lane test_drive.started
  4. 12:25 Returned and re-parkedNorth display · R2 · 06 test_drive.returned
Illustrative product view · synthetic history

04 — Route exceptions to a person

Exceptions go to a person, not a pile of alerts.

Some observations need judgment: a vehicle outside a mapped space, movement after hours, a camera that stops reporting. ParkSense places each one in a review queue where it is assigned, annotated and resolved, with its full history kept beside the event.

ParkSense flags. People decide. What counts as an exception, who receives it and how it is closed are set with your team for each site.

  1. 01FlaggedAn event that needs judgment opens a review item.
  2. 02AssignedIt reaches the role that owns that kind of exception.
  3. 03In reviewNotes and context stay attached to the event.
  4. 04ResolvedThe outcome is recorded for the next shift and for reporting.
Review queue 2 open
  • Inventory vehicle in customer parking In review

    Customer parking · C1 · 08 · 12:22

    Owner
    Lot manager
    Source
    exception.opened
    Note · 12:29

    Detail team staged it for photos. Moving it back to North display after lunch.

    1. Flagged
    2. Assigned
    3. In review
    4. Resolved
  • Zone not reporting Open

    South display · since 10:02

  • Movement after hours Resolved

    North display · R1 · 01:47 · scheduled transport

Illustrative product view · synthetic events

05 — Share events with your systems

The anatomy of an event.

Every observation becomes a consistent, documented record. Reports, dashboards and other authorized systems read the same events your team sees, so a question asked in a meeting and a question asked on the lot get the same answer. Which systems connect, and how, is scoped with each site.

Sample recordtest_drive.returned
{  "event_id": "evt_7Q2M9K4R1X",  "event_type": "test_drive.returned",  "site": "sample-dealership",  "zone": "north-display",  "row": "R2",  "space": "N-R2-06",  "vehicle_ref": "STK-24817",  "observed_at": "2026-10-14T12:25:08Z",  "recorded_at": "2026-10-14T12:25:09Z",  "source": "edge/camera-n02",  "review_state": "none",  "mode": "sample"}
Synthetic values for illustration
  1. event_id

    A unique, stable identifier. A record resent after a network interruption is recognized as the same event rather than counted twice.

  2. event_type

    A small, documented vocabulary of types, so every consumer interprets an event the same way.

  3. site · zone · row · space

    Place, expressed in your own lot map: the same names your team uses on the radio and on the signs.

  4. vehicle_ref

    Your inventory reference for the vehicle, matched to the map. Events describe vehicles and spaces.

  5. observed_at · recorded_at

    When something was seen and when it was written are kept separately, so late records still sort into the right place.

  6. review_state

    Connects the event to the review queue: none, open, assigned or resolved, with notes kept alongside.

Sample recordzone.occupancy
{  "event_type": "zone.occupancy",  "zone": "south-display",  "capacity": 32,  "occupied": null,  "fresh": false,  "last_observed_at": "2026-10-14T10:02:41Z",  "mode": "sample"}

Unknown is null, not zero.

When a zone has not reported recently, its count is left empty and the record says it is not fresh. The operator view shows the zone as awaiting observations instead of presenting an old number as the current one.

Sample event vocabulary

  • vehicle.located
  • vehicle.moved
  • vehicle.arrived
  • vehicle.departed
  • test_drive.started
  • test_drive.returned
  • zone.occupancy
  • exception.opened
  • exception.resolved

Who uses it

One platform, four points of view.

Each role starts from the part of ParkSense that answers its everyday question, and sees what that role needs.

  1. 01

    Porters and sales staff

    Starts fromVehicle search

    Type a stock reference or a description and walk straight to the zone, row and space where the vehicle was last seen. Log a test drive out and back without a radio call.

  2. 02

    Lot and operations managers

    Starts fromLot map · timeline

    See the whole lot at once: occupancy by zone, what moved today, which vehicles are out and which exceptions are waiting on someone.

  3. 03

    Security teams

    Starts fromReview queue

    After-hours activity arrives as a short list of specific events with time, place and history. Each one has an owner, notes and a clear outcome.

  4. 04

    Parking operators and property teams

    Starts fromOccupancy · review queue

    Availability by zone with observation times and busy periods help operators plan the next shift; property teams bring clear observations to allocation, signage and tenant conversations.

See it working

Try the operator view with a sample site.

The product tour runs entirely in your browser on generated data. Switch between a dealership and a commercial parking facility, search inventory, filter events and work through the review queue.

Explore the product

Solutions

Talk to us

See how ParkSense would map your lot.

Share your layout, the cameras you have or plan, and the questions your team asks every day. We will walk through coverage, the operator view and how events would reach the people who need them.

Request a demo Explore the product