Reference · built on requestOperator by FibricProperty & tenants

Parking Overflow

Vehicles counted at gates and cameras against permits on file, with an overflow lot opening, a visitor hold, or a tow notice proposed.

Request accessPricing ↗

About

A lot is full when the gate says so, and the gate rarely says so. Parking Overflow counts instead. It reads gate events from Brivo Access, Avigilon Alta, or Verkada, plate reads from LPR cameras through Verkada or Eagle Eye Cloud VMS, and zone entry and exit transitions from Camera Vision at lot entrances. It reads the permits on file: license plates held as credentials by access users, or the permit list you keep in Google Sheets, keyed to the unit and resident on record in Buildium or Entrata.

When the count nears the lot's capacity, or a plate has no permit, it proposes the next move: open the overflow lot, hold new visitor passes, or draft a tow notice. Nothing moves until you approve it. It opens no gate and calls no tow truck.

This is a reference listing. It documents what Fibric would read from Parking Overflow and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Gate events by access point from Brivo /events/access, entry activity from Avigilon Alta, and Verkada access events on the vehicle gates
  • License plates seen by Verkada LPR cameras, and een.lprPlateReadEvent.v1 events from Eagle Eye Cloud VMS, with time and camera
  • Zone entry and exit transitions and occupancy per zone from Camera Vision at lot entrances and rows
  • Permits: license plates held as credentials by access users in Verkada, or a permit list in Google Sheets or a SharePoint list, keyed by unit
  • Residents and units in Buildium or Entrata, to find who is on record for a permit or a space
  • Visitor passes: Verkada Guest visits and ButterflyMX visitor and delivery keys with their time windows, and your capacity and towing rules per lot

Proposed actions

  • Target capability: propose opening the overflow gate by a Brivo schedule state change or an Avigilon Alta timed entry state, with the revert time
  • Target capability: propose a visitor hold: pause new Verkada Guest visits or ButterflyMX visitor keys for the lot until the count falls
  • Target capability: propose a tow notice to the resident on record through Twilio SMS, naming the plate, space, and notice period, with the clip attached
  • Target capability: propose a mismatch list of plates with no permit for a patrol, appended as rows to your permit sheet
  • Target capability: propose a saved clip or bookmark of the plate read, through Rhombus spliceV3 or a Milestone XProtect bookmark, before a notice goes out

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Open the overflow lot before the main lot fills

    Camera Vision reports zone entries and exits at the main lot entrance. Near your capacity rule, the operator proposes an Avigilon Alta timed entry state on the overflow gate, with the time it reverts.

    With Camera Vision (RTSP), Avigilon Alta

  • Find the plates that have no permit

    Verkada LPR reads plates overnight. The operator matches them to access-user plates and your Google Sheets permit list, then proposes a mismatch list and a Twilio notice to the unit on record in Entrata.

    With Verkada, Google Sheets, Entrata, Twilio

  • Pause visitor passes on event nights

    Brivo gate events show the lot near full. The operator proposes holding new ButterflyMX visitor keys for the garage until the count drops, and a note for the front desk.

    With Brivo Access, ButterflyMX

  • Keep the clip before the notice

    An Eagle Eye plate read matches no permit again. The operator proposes a Rhombus saved clip of the entry and a tow notice draft for a person to review before anything is sent.

    With Eagle Eye Cloud VMS, Rhombus

Requirements

  • An access control connector on the vehicle gates: Brivo Access, Avigilon Alta, or Verkada
  • A source of vehicle counts or plates: Camera Vision on RTSP feeds, Verkada LPR cameras, or Eagle Eye Cloud VMS plate read events
  • Permit records it can read: plates as access credentials, or a permit list in Google Sheets or SharePoint tied to units in Buildium or Entrata
  • A messaging connector such as Twilio for notices, and your capacity, overflow, and towing rules per lot
Authentication
It reads gates, cameras, and permits through the access, video, file, and property connectors you attach; each keeps its own credentials and scopes, and the operator keeps none.

Limits

  • Counts come from what gates and cameras see. A lot with an ungated exit drifts, and the proposal shows when the count was last reset.
  • A plate read is only as good as the camera angle and the light. A mismatch is a list for a person, not a verdict.
  • It opens no gate, tows no vehicle, and issues no fine on its own. A tow notice is a draft and a message you approve.
  • Towing notice rules differ by city and state. It follows the notice period and wording you configure.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Parking Overflow ↗

Questions and answers

What am I approving when the lot fills?
One action per event: the overflow gate change with its revert time, the visitor hold and its end, or the tow notice text. The proposal shows the count, the gate and camera events behind it, and any plate matches. You approve, edit, or decline.
Where is the evidence kept?
In the receipt: the events and plate reads cited, the permit match or its absence, the saved clip or bookmark id, the gate or schedule change and its revert, the message id from Twilio, and who approved each step.
Can it have a car towed?
It cannot. It drafts the notice and the message to the resident on record. Calling the tow contractor, and any fine or fee, stays with your staff and your lot rules.
Ask about Parking Overflow

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy