Technical buying guide
Parking System Integrator Site Survey Checklist
The first site visit should answer more than “how many barriers do we need?” A parking system has to work within real vehicle paths, building constraints, operating rules and existing IT. If those inputs are missing, a quotation may be neat on paper and difficult to install.
This checklist is for the integrator’s field survey. It focuses on what to observe, measure and clarify at the property. Once those facts are recorded, the buyer can use our separate Parking Access System RFQ Checklist to request comparable supplier offers. Keeping survey evidence and commercial scope separate helps avoid repeating the same generic questions in two documents.
Bring the right people and documents
Ask for the latest site plan, traffic plan, lane drawings, electrical information and network diagram. Mark their revision dates. Invite the person who runs the parking operation and someone who can explain the site’s electrical and IT boundaries. A facility manager may know where drivers queue; an IT manager may know whether a proposed device can reach the required network. Neither perspective replaces the other.
Before walking the lanes, agree whether the project concerns a new site, a retrofit or a partial replacement. Identify the equipment that must remain in service during work. Record the person who can approve a closure, a cable route or a change to access rules. If a drawing or interface document is missing, mark it as an open item rather than filling the gap with an assumption.
Walk every vehicle route in both directions
Start before the entrance, not at the barrier cabinet. Observe where drivers slow down, whether vehicles can queue without blocking a public road, and where a driver can safely stop if authorization fails. Follow the route through the lane and into the parking area. Repeat for exit traffic, delivery vehicles and any special or emergency routes defined by the operator.
Measure the usable lane width at the device position, not only the painted width elsewhere. Note kerbs, columns, overhead services, sloped ground and drainage. Photograph the approach from a driver’s eye level and the proposed device location from several sides. A boom arm or terminal may fit dimensionally but still leave a camera with a poor view, a screen in glare or a maintenance door against a wall.
The project engineer should decide what measurements and local approvals are required for the actual site. This article does not provide a universal arm length, clearance or safety distance. The Products overview shows Zibor Park’s product families; the site geometry must determine which of them are relevant.
Record each lane as a separate work item
Two lanes at the same property may need different equipment or rules. A simple lane schedule keeps them distinct:
| Field | What to record on site |
|---|---|
| Lane ID and direction | Entrance or exit; normal and exceptional route |
| Geometry | Usable width, grade, overhead constraints and arm movement space |
| Traffic | Vehicle types, peak arrival pattern, queue location and pedestrian crossings |
| Identification | Registered users, visitors, tickets, plate reading or other methods proposed |
| Decision point | Where the driver stops and where the barrier releases |
| Services | Power source, cable path, network point and equipment room |
| Safety | Detection positions, visibility, manual operation and site-specific approvals |
| Existing assets | Devices to keep, remove or integrate, with model and owner |
Use a unique photograph set and sketch for each lane. If the entrance is shared with a loading route, note truck movements and the operator’s rules for them. Our Logistics & Warehouse Access solution explains that application context, while the lane schedule records the evidence for this particular site.
Ask operators to show the exception workflow
The normal trip is often obvious: a credential is recognized, authorization is checked and the barrier opens. The survey should focus on the moments when that sequence breaks. What does an attendant do when a plate is unreadable, a visitor is not registered, a driver loses a ticket or a vehicle stops in the wrong place? Which action can be taken locally, and which needs approval?
Watch the existing process if the site is operating. Record the screen, phone call or paper log that staff use today. Do not assume that a proposed software feature can reproduce it until the product configuration and interface are confirmed. The buyer should also identify who will train staff and who will own the operating procedure after handover.
For payment-related facilities, separate parking access decisions from charging and reconciliation. Write down who sets tariffs, how a payment result reaches the exit decision and who handles a disputed charge. These questions establish scope without presuming a particular Zibor Park payment function or external integration.
Locate power, communications and installation constraints
Identify the available electrical supply and the party responsible for protection, isolation and any civil work. Locate the nearest approved network point and ask who controls addressing, firewall rules and remote access. A nearby socket or network port is not proof that it is available for the project.
Mark the proposed foundations, cable routes, equipment cabinets and maintenance access. For retrofit work, ask whether buried services have been surveyed and whether the facility can close a lane during installation. If the site must stay open, note the sequence of work and the temporary traffic plan that the responsible contractor must develop.
The survey should record environmental exposure too: rain, direct sun, wash-down practices, dust and temperature conditions at the device position. Product-specific ratings and protection measures must come from approved model documents, not from a generic product family name.
Leave with a decision log, not just photographs
Before leaving, review open questions with the owner. Separate what was measured, what was reported by staff and what remains unverified. Assign an owner and due date to each missing drawing, interface document or approval. A clear decision log prevents a rough site note from becoming an untested design assumption.
The output of the survey should be a marked site plan, lane schedule, photo register, existing-equipment register, operating workflow and open-items list. These become inputs to design and to the later RFQ. The IPMI parking technology glossary can help buyers and integrators use consistent equipment terms. Neither a glossary nor a survey replaces qualified local engineering or code review.
If you are planning a parking access project, share those survey materials when you discuss the product scope with Zibor Park. We can use the actual lanes and workflows to identify suitable product families and the model details still needing confirmation.