Access-only projects
Specify allowed and refused journeys before listing readers or gates.
Review parking access controlSpecifications and project requirements
Parking system specifications and RFP planning
Define what your parking system must do, which equipment it needs and how you will verify the installation. Lexoh manufactures access and payment kiosks and develops Security Center. Use this guide to prepare comparable proposals covering lane equipment, software and installation responsibilities.
Start with the operation
Write requirements that can be demonstrated
A feature name such as “cloud,” “license plate recognition (LPR)” or “integration” leaves important decisions open. State the user, starting condition, expected result and evidence. Keep the specification tied to the actual site, and distinguish mandatory behavior from optional equipment or later phases. For paid parking, include parking access and revenue control (PARCS), payment configuration and transaction reconciliation in the project requirements.
| Requirement area | What to state | Evidence to request |
|---|---|---|
| Access | Approved and expired users, zones, periods and credential types. | Demonstration of allowed and refused entries at the intended lane. |
| Payment | Tariff, validation, receipt and correction journeys. | A complete test transaction and the corresponding operator record. |
| Interfaces | System owner, data fields, update timing and failure handling. | A tested data exchange, including a rejected or delayed update. |
| Delivery | Civil work, power, network, training and documentation boundaries. | A responsibility schedule and documented acceptance results. |
From policy to the lane
Prepare the operating brief, equipment schedule and acceptance plan
Operating brief and lane schedule
Identify the site, user groups, entrances, exits and approved policies. For each lane, list vehicle types, required identification, payment location and assistance path. Attach a site plan and clearly label facts that still need a field survey.
Equipment schedule and interface register
List proposed or retained equipment by role and reference. Define the owner of power, communications, civil preparation and each software interface. Ask suppliers to state exclusions and dependencies beside the item they affect, so quotations cover the same scope.
Acceptance plan and handover package
Pair the user journeys with test cases and responsible approvers. Define the operating records, configuration inventory, staff training and support handover to be delivered. Include a process for recording exceptions that remain open at acceptance. Record an owner and closure conditions for each unresolved item.
Planning exampleSee the documented Scotiabank installation →
Replace “visitor management included” with a test case
For an illustrative requirement, specify that an authorized operator issues a visitor right for an approved period and zone. The visitor receives usable arrival instructions; the right works during that period and is refused after expiry. Require a record showing the relevant access result. The supplier then explains the supported credential and configuration. Retain the access result and the configuration used for the test so the project team can verify the delivered behavior.
Prepare the scope
Copy these headings into the project brief
Site and user groups: identify the property, operator, permit populations and public visitors. Mark information that still needs a survey.
Lane schedule and physical constraints: show entrances, exits, vehicle types, stopping points, pedestrian paths, power and network locations.
Access and payment journeys: describe approved, expired and exceptional arrivals; include tariff, receipt and correction cases where payment applies.
Equipment and interface responsibilities: list retained and new models, data owners, hosting, licences, administrator access, backups and outage behavior. Separate required scope from options.
Acceptance tests and evidence: name the starting condition, expected result, record to retain and approver. Include failed reads, delayed updates and an unavailable network.
Training and support handover: identify configuration records, operator training, support contacts, maintenance responsibilities and unresolved items to close.
Specification questions
Questions to settle before selecting the equipment and configuration.
No. It is a technical planning structure for the parking scope. The project team must complete the site design, purchasing requirements and contractual documents appropriate to its own process.
Name it when a verified requirement depends on it, such as compatible existing credentials. Otherwise describe the arrival, environment and expected result, and ask suppliers to explain the proposed method and limitations.
Use the same responsibility schedule for every proposal. Identify who supplies civil work, power, networking, integrations, commissioning and ongoing services. Resolve missing items before comparing the delivered totals.
Request the same itemized schedule from each supplier: equipment, civil and electrical work, configuration, confirmed interfaces, commissioning, training and recurring services. Require quantities, exclusions and optional items to be visible so the comparison reflects a deliverable system.
Lexoh uses a hybrid cloud and offline architecture with mesh communication between site devices. Describe the outage to test: loss of the internet connection, loss of a local network link and loss of equipment power are different conditions. Record the credentials and permissions available before each test, the expected access result and how changes will be checked after reconnection. Specify payment authorization, remote access and external software exchanges separately; local device communication alone does not establish their availability.
Review the operating brief before requesting equipment
Share your lane schedule and required user journeys. We can review the Lexoh scope, interfaces and demonstrations needed for the project.