Skip to main content
LIOMO

05 · Smart Parking

Every free space known, and drivers sent straight to it

A LIOMO parking system senses vehicles at bays, entries and exits, shows drivers where to go, and gives operators and municipalities live occupancy data to manage access, pricing, enforcement and planning.

Availability

Delivered as a project

Scoped and built for each car park or street by LIOMO, from sensor selection and installation coordination to software, integration and support.

Illustrative interface · demo data. A top-down view of a car park level with three rows of bays. Most bays are occupied, free bays are highlighted, and one bay sensor is not reporting. Side panels show free spaces per level and today's entries and exits.

The problem

Parking is managed with too little information

Operators know their capacity but rarely know, minute by minute, how it is used. Drivers search, queues form at entrances, and decisions on pricing and planning rest on occasional counts.
  • 01

    Drivers searching

    Without guidance, drivers circle levels and streets looking for a space, adding traffic, emissions and frustration.

  • 02

    Occupancy guessed

    Counts are taken by hand or estimated, so nobody knows how full a car park or street really is at a given time.

  • 03

    Access that does not fit

    Permit holders, staff, visitors and deliveries share the same spaces, managed with barriers, tickets and lists that are hard to keep in step.

  • 04

    Separate systems

    Payment, permits, enforcement and signage each run on their own, so their data cannot be combined or acted on together.

The solution

Sensing, guidance and access in one system

A LIOMO project combines detection hardware suited to each site with guidance, access control and a platform that turns individual detections into occupancy you can use.
  • Bay-level detection with ultrasonic, magnetometer or camera-based sensors, chosen per site.
  • Entry and exit counting for zones, levels and whole car parks.
  • Guidance displays at entrances and junctions showing free spaces by level or zone.
  • Access control for permit holders, staff and visitors, linked to barriers or number-plate recognition where fitted.
  • Occupancy data shared with payment, permit and enforcement systems.

How it works

How a LIOMO parking system works

Every LIOMO system follows the same four stages. In a car park or on the street, they look like this.
  1. 01

    Connect

    Bay sensors are fitted overhead or in the bay surface, and counters or cameras are placed at entries and exits. Each is linked through gateways using LoRaWAN, NB-IoT, LTE-M or a wired network, depending on the site.

  2. 02

    Collect

    Every arrival and departure is reported as an event with its bay, zone and time, and stored so occupancy can be rebuilt for any moment.

  3. 03

    Understand

    The platform calculates live occupancy per bay, zone and site, cross-checks bay sensors against entry and exit counts to catch faults, and builds patterns by hour, day and season.

  4. 04

    Act

    Guidance displays update, access rules open or hold barriers, and enforcement teams see overstays. Occupancy data flows on to payment, permit or city systems.

Capabilities

What a project can include

What a LIOMO parking project can cover, from a single car park to on-street zones across a district.
  • 01

    Site survey

    A review of layout, surfaces, entries and exits, power and network coverage, and the decisions the data needs to support.

  • 02

    Bay sensors

    Overhead ultrasonic sensors for covered car parks, and surface or in-ground magnetometer sensors for open bays and streets, chosen for detection reliability, battery life and installation method.

  • 03

    Entry and exit counting

    Induction loops, beams or cameras at entrances, exits and ramps, for zone or level occupancy where bay sensors are not needed.

  • 04

    Guidance and signage

    Displays at entrances, junctions and levels showing free spaces, and bay indicator lights where drivers need them.

  • 05

    Access control

    Barriers, permit lists, RFID or number-plate recognition, with rules for staff, residents, visitors, deliveries and time windows.

  • 06

    Occupancy dashboards

    Live and historical occupancy by bay, zone and site, with stay duration, turnover and peak periods for operators and planners.

  • 07

    Enforcement support

    Overstays and unauthorised use flagged to enforcement teams, with the bay, zone and time attached.

  • 08

    Payment and permit integration

    Occupancy, session and access data exchanged through REST APIs with payment, permit, enforcement and city data systems.

  • 09

    Installation and support

    Coordination of installation and commissioning, and ongoing support for sensors, gateways, displays and software.

Use cases

Where it fits

Parking systems are shaped by who parks, for how long, and who needs the data.
  • Multi-storey and underground car parks

    Level and bay guidance with counts at every ramp, so drivers find spaces without searching every floor.

  • On-street parking

    Bay sensors in streets and loading zones, giving municipalities live occupancy and overstay data.

  • Workplace and campus parking

    Access for staff, visitors and fleet vehicles, with the data to plan space allocation and shared use.

  • Retail, hospital and venue parking

    Guidance and occupancy for visitors arriving at busy times, with payment and access linked.

Business value

What it changes for the business

The aim is to use existing spaces better, and to base pricing, enforcement and planning on measured use.
  • 01

    Less searching

    Drivers are guided to free spaces, which shortens queues at entrances and reduces traffic inside the site.

  • 02

    Better use of existing spaces

    Occupancy data shows where and when capacity sits unused, before any decision to build more.

  • 03

    Consistent access and enforcement

    Rules are applied the same way every time, and enforcement effort goes where overstays actually occur.

  • 04

    Evidence for planning

    Patterns by hour, day and season support decisions on pricing, permits and future parking provision.

FAQ

Questions buyers ask

Do we need a sensor in every bay?

Not always. Bay sensors give the most detail and support bay-level guidance and enforcement, while entry and exit counting is often enough for zone or level occupancy. Many sites combine both, with bay sensors only where detail matters, such as accessible bays, loading zones or short-stay spaces.

How are bay sensors installed and powered?

Surface-mounted and in-ground sensors are usually battery-powered and fixed to or set into the bay, so no cabling is needed. Overhead ultrasonic sensors in covered car parks are normally wired. The survey determines which suits each area.

Can it work with our payment or permit system?

Usually, if that system offers an interface. Occupancy, session and access data can be exchanged through REST APIs or scheduled file transfers, and the integration is defined during the project rather than assumed.

Can we keep our existing barriers?

Often, yes. Many barrier and access systems can be read or controlled through their existing controllers. The assessment checks what is in place and what can be connected before anything new is proposed.

How long does a project take?

It depends on the number of bays and sites, the installation method, and any work on roads or structures that needs permits. A typical sequence is a survey, a pilot on one zone or level, a review of the data, and then a staged rollout.

Discuss Smart Parking for your operation

Tell us what you run and what you need to see. We will show you how it would work, with no obligation.