FAQ & industry knowledge

Level counting answers “which floor has room.” Per-space detection answers “which space.” If your complaint is drivers circling a full deck, counting solves it for a fraction of the cost. If your complaint is drivers circling a deck that has room but they can't see it — long aisles, columns, mixed bay types — you need per-space.

Most garages end up mixed: counting on commuter levels, per-space on visitor and patient levels.

Both are routine. Retrofits are mostly a question of pathway — where conduit can run and what the deck will allow. Camera-based heads cover several bays at once and reduce the number of penetrations, which is often what makes a retrofit viable.

Counting systems drift, because every missed or double-counted vehicle is permanent until corrected. That is handled with scheduled recalibration against a known state, usually overnight. Per-space systems don't drift the same way — each bay reports its own truth — but sensors do need cleaning and aim checks.

A failed bay reports as unknown rather than open, so the sign never sends a driver to a space that isn't there. The fault surfaces in the monitoring dashboard, and it falls under the service agreement.

Usually yes — occupancy counts and plate reads are the two data feeds most PARCS platforms accept. We consult on this pairing regularly, including on projects where the access system came from another vendor.

Yes. Bay classes are configured separately, with their own indicator color and counting rule, and misuse can raise an alert rather than just a log entry.

Real occupancy by hour and by zone, dwell-time distribution, and turnover per bay. That is the evidence base for repricing, reassigning permit areas, or justifying not building an additional deck.

We do. Same-day attention on support concerns, and warranty clients have historically paid nothing for wear-and-tear repairs.