Technical buying guide
Parking Guidance System Components and Site Survey Basics
A parking guidance system can show drivers where spaces may be available, but a device list is not a design. Before choosing sensors, indicators or signs, an integrator needs to understand how the car park is divided, how drivers make decisions and what the operator wants to know when a detection point fails. A site survey turns those questions into a usable system brief.
This guide focuses on the information to collect and the relationships between components. It does not prescribe a particular detector or claim that one sensing method suits every garage. For a view of Zibor Park’s current product family, see our Parking Guidance Systems category; the final component models and interfaces are confirmed for each project.
Start with the decisions a driver has to make
Walk the route from the property entrance to the last parking zone. At each junction, ask what a driver can see, whether they can still change direction safely and how much advance notice they need before a turn. A sign placed after a decision point cannot help the driver choose a different level or aisle.
The operator’s view is equally important. Does the site need a count by level, by zone or by individual space? Do staff need to see only current availability, or also device faults and periods when counts appear unreliable? The answers determine the level of detection and the data path to the displays. More granular information can be useful, but it also means more field devices, mounting positions and maintenance points.
For a public facility, arrival patterns and signage at major route choices deserve special attention. Our Municipal & Public Parking solution provides the wider operating context; this article deals with the guidance survey itself.
Map the components as a chain, not a shopping list
Most proposals can be discussed as four connected functions:
| Function | What the project team must define | Useful evidence from the survey |
|---|---|---|
| Detection | What counts as occupied, vacant or unknown for a space or zone? | Stall layout, obstructions, lighting and vehicle mix |
| Local indication | What should a driver see near a space or aisle? | Sightlines, ceiling height and possible mounting points |
| Directional guidance | At which junction should availability be shown? | Driver route, turning points and sign visibility |
| Management and data | Who uses occupancy information, and how is a fault handled? | Network locations, operator roles and existing systems |
This is a functional breakdown, not a statement that every Zibor Park project includes all four functions or a particular sensor technology. A zone-counting approach and a space-by-space approach answer different questions. Agree on the required information before comparing equipment.
Survey the physical site before choosing hardware
Begin with current drawings, but verify them on site. Renovations, columns, low beams and revised traffic routes often make a drawing incomplete. Record the number of levels, aisles, spaces and entrances; distinguish general, reserved and restricted spaces. Note the directions of travel and any routes that reverse at different times. Mark areas where parked vehicles, signs or building elements block a device’s field of view.
For each proposed sign or indicator, photograph the position from the driver’s approach. Record mounting height and available structure without assuming the structure is approved for fixing. Identify power and network routes, as well as the party responsible for cable containment and building works. An installer should also identify areas where maintenance access would interfere with traffic.
Existing facilities need a different installation plan from a new build. If the garage must remain open, the buyer should state allowable work windows, whether zones can be closed in stages and who will verify the displayed counts after each stage. This helps avoid a proposal that is technically plausible but operationally difficult to install.
Define how availability is calculated and corrected
“Available spaces” sounds simple until a sensor is offline or a space is reserved for a particular user. The buyer should describe the intended counting rules. Should a blocked space be removed from the public count? What happens when a level entrance counter and a space-level count disagree? Who is allowed to correct an exceptional reading, and is that correction recorded?
Ask suppliers to show the data flow from each detection point to the display seen by drivers. Include the communications path, the expected behavior during a network interruption and how the operator is alerted to stale information. These are specification questions, not assumptions about functions already present in a given product.
If occupancy data is to feed another platform, identify the receiving system and its owner. Request the actual interface documentation and test plan for that integration. A general promise that two systems can be “connected” does not define data fields, refresh behavior or responsibility when the numbers differ.
Give bidders a comparable survey pack
A useful survey pack contains more than a floor plan. Include:
- A marked plan showing levels, zones, spaces, drive paths and decision points.
- Photographs of candidate mounting locations and the driver’s view of each sign.
- The distinction between public, reserved and restricted parking areas.
- Current power, network and equipment-room information, with unknowns marked clearly.
- The desired level of occupancy detail and a description of how exceptions should appear.
- Operating constraints such as phased installation and maintenance access.
- The site owner’s acceptance tests for counting, display updates and fault reporting.
Ask each bidder to separate confirmed scope from options and assumptions. If an existing counter, sign or management platform is to be reused, name it and request a compatibility check. This makes later quotations easier to compare without turning the survey into a promise about an unverified interface.
Test the driver journey and the operator journey
Acceptance testing should follow real journeys, not only a bench demonstration. Walk or drive the route through several decision points, then verify that the displayed message agrees with the agreed count for the destination zone. Repeat with a deliberately unavailable space or temporarily disconnected device where the test plan permits it. Check what the operator sees, whether an exception is obvious and how it is resolved.
The test method should be agreed before equipment is ordered. It should specify who records the observed state, who decides whether the result is acceptable and who corrects a mismatch. The IPMI parking technology glossary is useful for aligning terminology across vendors; it does not verify a particular Zibor Park component. The goal is not to claim perfect occupancy data in every condition, but to make expected behavior and recovery clear.
If you are preparing a guidance project, send us the marked layout, photographs of key junctions and your required occupancy detail. We can discuss the Parking Guidance Systems product path against those inputs and identify which component choices still need confirmation.