Exhibit_E-DAB_PARCS_Functional_Requirements_Matrix.xlsx
XLSX spreadsheet 41 KB Posted
- Solicitation number
- 26-P-32JD
- Issued by
- Volusia County, Florida
About this file
This is a Parking Access and Revenue Control System (PARCS) Functional Requirements Matrix exhibit for Daytona Beach International Airport (DAB), operated by Volusia County, Florida. The document establishes comprehensive technical and operational specifications for a new PARCS to be procured, installed, and operated at five parking facilities: Short Term Parking Lot, Long Term Parking Lot, VIP Parking Lot, East Employee Parking Lot, and West Employee Parking Lot. The system must include automated public entry and exit lanes with barcode/QR code capabilities, mobile scan-to-pay functionality, License Plate Recognition (LPR) technology, Access Credential Management System (ACMS) for employees and tenants, real-time command center monitoring, VoIP intercom systems, EMV/NFC credit card processing, dynamic message signage, and comprehensive reporting capabilities. The system must be fully redundant, cloud-based or hybrid, with complete County ownership of data and export rights in non-proprietary formats. The contractor must design and install all necessary electrical and communications infrastructure, provide a test bed with fully functional entry and exit equipment, and deliver the system compliant with applicable standards including PCI DSS, ADA, and environmental requirements (NEMA Type IV, operation from -30°F to 130°F). Acceptance testing includes Factory Acceptance Test (FAT), Lane Acceptance Tests (LAT), and 30 consecutive days of System Acceptance Test (SAT) with strict availability requirements.
The contractor must provide comprehensive warranty coverage for twenty-four (24) months beginning upon substantial completion notification, including all manufacturer-recommended preventative maintenance, emergency repair services with multiple notification methods, free software upgrades and patches, and monthly project review meetings at no additional cost. Post-warranty support includes factory-trained and certified County staff for Level 1 and Level 2 hardware service, semi-annual site inspections, and 24/7 on-call support for complex issues. The contractor shall propose recommended spare parts with pricing and provide guaranteed component pricing for three years following final system acceptance, using only newly manufactured equipment. All software and licenses must be issued to and registered to the County with perpetual licensing and unrestricted usage rights regardless of physical location and number of simultaneous users. The contractor must provide comprehensive training for parking ambassadors, management staff, system administrators, accounting personnel, and maintenance staff in initial, mid-warranty, and final sessions not exceeding four hours each, with instructional materials in hardcopy and electronic formats. Service level requirements include weekly out-of-service reports, monthly repair and preventative maintenance reports, and reimbursement to the County for quantifiable lost revenue directly related to contractor errors. The file does not specify pricing terms, award dates, contract term duration, renewal options, set-asides, incumbent contractor information, or funding sources; these details are contained in other RFP exhibits referenced but not included in this functional requirements matrix.
View the file
Other files
Show all 19
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PARCS Functional Requirements Exhibit E-DAB Parking Access and Revenue Control System (PARCS)
| Response Code | Definition |
| Y—Yes | The functionality will be implemented 'out of the box' without configuration, customizations or modifications to the existing applications or reports. |
| N—No | Requirement will not be provided. |
| CO—Configuration | Requirement will be met through changes to settings of tables, switches, and rules without modification to source code. Include any changes to the existing or "out of the box" workflow functionality. |
| CU—Customization | Requirement will be met by changing existing software or through the use of software tools such as application report writer, query, etc. Note: In the Comments column next to this response, you must indicate the following: Description of customization. Estimated level of complexity (High, Medium, Low). If there is an additional cost it must be included in the cost proposal. |
| F—Future | Requirement will be met by software that is currently under development, in Beta test, or not yet released. Note: In the Comments column next to this response, indicate the date when requirement will be available for implementation. If possible, also indicate any additional costs. |
| 3—Supplied by 3rd Party | The requirement will be met by a third-party software for which the solution provider does not have an established practice area, and the third party software is included in this Proposal for implementation. Note: In the Comments column, indicate the name of the proposed 3rd party software and indicate the interface/integration services being proposed. |
One Response per Document COMMENTS Provide information, description, clarification, or explanation to assist the County in making an informed decision.
| Y/N | CO | CU | F | 3 | |
| Overview & System Objectives | |||||
| Contractor shall provide a complete Parking Access and Revenue Control System (PARCS) for Daytona Beach International Airport (DAB), including all hardware, software, licensing, installation, testing, training, warranty, and post-warranty support. | |||||
| PARCS shall leverage technologies to enhance the DAB passengers' parking experience, providing an efficient and effective management system for all parking operations. | |||||
| PARCS shall accurately document all required financial and statistical data for the parking operation by producing reports for revenue and other activities as defined herein. | |||||
| PARCS shall provide complete audit, accountability, and traceability of all parking activity and revenues. | |||||
| The PARCS system should be fully redundant and be cloud-only or hybrid | |||||
| The County shall have real-time access to the PARCS and all related data. County retains full ownership of all data; right to export in non-proprietary formats (CSV, JSON, XML) and/or via documented APIs at any time without Contractor intervention. | |||||
| PARCS must support multiple integrations and interfaces with other PARCS modules, County applications, and third-party sales channels. | |||||
| PARCS equipment must be able to be purchased and maintained by any Contractor (non-proprietary). | |||||
| Parking Facilities | |||||
| PARCS shall serve the following facilities: Short Term Parking Lot, Long Term Parking Lot, VIP Parking Lot, East Employee Parking Lot, and West Employee Parking Lot. | |||||
| Related Requirements & Standards Compliance | |||||
| PARCS shall conform to: National Electrical Code (NEC), ANSI, NEMA, UL, NFSA, FCC, PCI DSS (latest version), PCI SSF (latest version), ADA, and all applicable Federal, State, and Local laws. | |||||
| Contractor shall identify and notify the County of any changes to applicable standards between NTP and PARCS implementation and certify that the software meets those requirements. | |||||
| Future System Expansion | |||||
| PARCS shall support expansion of additional parking facilities and products for the next ten (10) year and shall be readily upgradable, scalable, and modular in design to accommodate additional parking equipment, facilities, features, and functionalities. | |||||
| PARCS shall support open APIs to interface with third-party applications. | |||||
| PARCS shall support firmware or software upgrades without the need to replace field devices. | |||||
| PARCS shall be capable of interfacing with a future parking reservations system with seamless functionality. | |||||
| PARCS shall be capable of interfacing with a future parking loyalty system with seamless functionality. | |||||
| System Requirements — Primary Components/Features | |||||
| Automated public entry lanes with barcode/QR code tickets and Automated public exit lanes with no cashiers. | |||||
| Allow for roving ambassadors with handhelds, providing assistance with exception transactions in automated lanes and accepting cash and credit card payments. | |||||
| Command center for equipment monitoring, alarms, remote management, intercom response, event logging, and remote transaction processing. | |||||
| Mobile device ticket scan-to-pay payment capability. | |||||
| VoIP intercom system for two-way communication between lane devices and command center. | |||||
| EMV/NFC credit card payments at all payment-accepting devices. | |||||
| Pre-capture LPR as a credential at all public entry and exit lanes. | |||||
| Online and physical validation system. | |||||
| Access Credential Management System (ACMS) for County employees, tenants, and contract parkers, supporting AVI, proximity card, barcode/QR code credentials. | |||||
| Dynamic variable message signage at all public exit lanes. | |||||
| Browser-based application software accessible from any workstation or mobile device web browser. | |||||
| Offline functionality for all lane devices during network communication failures. PARCS shall support core field operations during internet outages/cloud interruptions via documented offline/degraded mode (lane operation, credential validation, transaction queuing). | |||||
| Uninterruptible power supplies (UPS) for all PARCS field equipment. | |||||
| Test bed with fully functional entry and exit lane equipment. | |||||
| Environmental Requirements | |||||
| All exterior equipment shall be rated NEMA Type IV weather resistant or equivalent, with heaters and cooling fan units and metal enclosures shall be finished in acrylic enamel to match other equipment | |||||
| Equipment shall operate in ambient temperatures -30°F to 130°F (with solar loading), humidity 0-99%, and blowing rain, sleet, snow, ice, dust, fine sand, and insect/rodent intrusion. | |||||
| Lightning protection shall be provided on all conductors. Electrostatic and electromagnetic forces shall have no effect on PARCS integrity or operation. | |||||
| Equipment shall be designed to prevent entry of condensing/dripping moisture, windblown dust, foreign objects, rain, snow, and ice. | |||||
| Warranty/Support | |||||
| Warrant all parts, materials, and workmanship for a minimum of twenty-four (24) months beginning upon County notification of substantial completion. | |||||
| Provide all manufacturer-recommended preventative maintenance services for PARCS hardware during warranty at no additional cost. | |||||
| Provide emergency repair service in accordance with the specified service level requirements. | |||||
| Provide three (3) methods of emergency notification (telephone, email, SMS text message) with tracking capability. | |||||
| Provide all PARCS software version upgrades, patches, service packs, and updates free of charge during installation, warranty, and post-warranty periods. | |||||
| Participate in monthly project review meetings throughout the warranty period at no cost to the County. | |||||
| Scheduled maintenance shall generally occur between 12:00 AM and 4:00 AM local time, or no earlier than 30 minutes after the last scheduled flight arrival, whichever is later. | |||||
| Submit maintenance requests to the County at least three (3) business days in advance of any scheduled maintenance, including description, anticipated impact, and estimated duration. | |||||
| Post-Warranty Support | |||||
| Post-warranty software support shall conform to warranty-period software support requirements. | |||||
| Factory train and certify County staff to perform Level 1 and Level 2 hardware service, including manufacturer-recommended preventative maintenance. | |||||
| Perform semi-annual site inspections and equipment preventative maintenance overhauls during post-warranty period. | |||||
| Provide on-call 24/7 hardware support for issues beyond the expertise of County staff. | |||||
| Spare Parts | |||||
| Propose a list of spare parts (type and quantity) recommended to be maintained on site, with pricing. | |||||
| Provide guaranteed component pricing for three (3) years following final system acceptance. | |||||
| Provide newly manufactured equipment and parts only; refurbished parts are not acceptable. | |||||
| Provide ability to order subcomponent parts to facilitate repair of assemblies without ordering entire replacement assemblies. | |||||
| Will order replacement spare parts within 72 hours of use. | |||||
| Software Licensing | |||||
| Provide all software and software licensing required by the system, including perpetual licenses and/or authorization. | |||||
| All software, licenses, and user credentials shall be issued to and registered to the County. | |||||
| Provide a site license with unrestricted usage regardless of physical location. | |||||
| No limitations on the number of simultaneously logged-in users. | |||||
| Database & Operating System | |||||
| Maintain data in ODBC-compatible formats for the database management system. | |||||
| For local/onsite server (if proposing a hybrid solution): operating system shall be Windows Server 2022 or newer | |||||
| If workstations are proposed, OS shall be Windows 11 or latest available version. | |||||
| PARCS Application Software | |||||
| Software shall be PA-DSS validated for new deployments per PCI and maintain valid PCI compliance report throughout installation, warranty, and post-warranty and shall utilize P2PE architecture listed on PCI-approved website and operate per PCI SSF requirements. | |||||
| PARCS shall not store or transmit unencrypted credit card data and no sensitive cardholder data shall be retained. | |||||
| Provide relevant SOC II report for IT security standards, submitted annually. Disclose any material security incidents within last 36 months. | |||||
| Software shall be upgradeable to maintain PCI standards throughout the life of the system. | |||||
| Operate on independent, Contractor-provided LAN accessible with County-approved user ID and password protocols. | |||||
| System shall support role-based access control (RBAC) and enforce least-privilege access for all users and administrators. | |||||
| Manage, display, and report all PARCS-related activity. | |||||
| Automatic detection and reporting of fault conditions and equipment failures with configurable severity levels and alarm notifications via GUI, email, and/or SMS. | |||||
| Support network performance monitoring tools for all PARCS devices. | |||||
| Provide audit trail for central controls within the PARCS database by user ID, time, device controlled, and action taken. | |||||
| Configurable parking rates (including special event rates), grace periods, and time increment changes restricted to County-designated users with audit trail. | |||||
| Remote real-time communication with all devices for general broadcast (rate changes, software updates) and individual device communication. | |||||
| Correct calculation and processing of parking fees during daylight savings time transitions, leap years, and rate change transitions. | |||||
| Programmable rate structure: variable rates by time of day, day of week, season, special events; hourly progression, daily/weekly/monthly maximums, grace times, and complimentary periods. | |||||
| Programmable tax rate configuration applied to parking fees. | |||||
| Ability to reconcile credit card revenue collected through PARCS to clearinghouse bank deposits. | |||||
| Ability to audit remote transaction processing activity by user with detailed transaction reports. | |||||
| Create system-generated alarms with configurable event types, priorities, audible tones, and distribution settings. | |||||
| Ability to export all query results and reports to multiple formats including PDF, CSV, and XLS. | |||||
| Reporting | |||||
| Reports available online and on demand for County personnel with proper access, viewable, printable, and exportable from the GUI. | |||||
| Detailed revenue and non-revenue transaction reports by user-selectable parameters (such as user type, date/time range, device). | |||||
| Detailed and summary revenue reports for daily, weekly, and monthly PARCS activity. | |||||
| Credit card transaction reports by date/time range, terminal ID, card type, transaction type (amount, approvals, declines, voids). | |||||
| Validation reports: detailed and summary by validation issued, amount, time, issuer (user ID), and user-selectable parameters. | |||||
| System event reports by user-selectable parameters including PARCS device and date/time range. | |||||
| Manual gate vend report showing each vend, lane ID, date/time, user ID, and sum total for selectable timeframe by lane ID and user ID. | |||||
| Occupancy, duration of stay, and turnover reports. | |||||
| Access credential reports: detailed and summary credential activity by individual credential or account number including credential type, entry/exit times, and fees. | |||||
| Ability to prepare custom reports using PARCS data including via CSV file format | |||||
| Financial accounting system scheduled data exports in CSV, XLSX, JSON, and XML formats, with scheduled or on-demand exports to County directories or secure FTP locations. | |||||
| Provide audit trails to track and verify exported data batches. | |||||
| Electrical & Communication Infrastructure | |||||
| Contractor shall design, permit, and install all new 120V electrical infrastructure required for PARCS where existing service does not exist. | |||||
| PARCS components shall be powered via hardwired connections. Solar power or batteries are not acceptable as primary power sources. | |||||
| PARCS shall reside on an independent, Contractor-provided communications network completely separate from the County's network and shall design, permit, and install all new TCP/IP communications infrastructure | |||||
| Provide a new hardwired, high-speed ISP connection to the toll plaza parking office and a wireless (cellular or satellite) backup in the event the primary ISP connection fails | |||||
| Configure all field component communications such that no single point of failure causes an operational failure of surrounding devices. | |||||
| All PARCS equipment shall communicate directly with the PARCS server (hybrid or cloud-hosted). | |||||
| Application and Data Servers | |||||
| Contractor shall provide all relevant servers and configuration (physical, virtual, or cloud-based) for centralized PARCS management. | |||||
| PARCS servers shall contain all application and database software for operation, data storage, and reports. | |||||
| Cloud-Based Requirements (if applicable) | |||||
| Upon contract termination, provide complete data export within ten (10) business days and certify deletion from Contractor systems within thirty (30) days. | |||||
| All data encrypted in transit (TLS 1.2 or higher, TLS 1.3 preferred) and at rest (AES-256 or equivalent). | |||||
| Cloud service uptime SLA of ≥ 99.9% (excluding scheduled pre-announced maintenance). | |||||
| Provide documented Disaster Recovery and Business Continuity plan with daily backups per County retention policy. | |||||
| Identify cloud hosting provider and primary/secondary (DR) data center regions | |||||
| Maintain immutable audit logs for all financial transactions, rate/parameter changes, user admin actions, and device events, exportable per County requirements. | |||||
| Disclose all subcontractors/third parties that store, process, or access County data. No material change to hosting provider without prior written County notice. | |||||
| Host all system data in Microsoft Azure or Amazon Web Services (AWS), unless alternative approved by County. | |||||
| All County data stored in logically dedicated (separate tenant/account) environment with no commingling of data with other customers. | |||||
| County data shall not be sold, licensed, monetized, shared, mined, aggregated, or combined with other customers' data for any purpose. | |||||
| Command Center | |||||
| Provide online, real-time monitoring and control platform performing: equipment monitoring, system alarms, equipment management, customer intercom response, event logging, and remote transaction processing. | |||||
| Command center shall provide a view of all parking facilities on one screen with alarm notification for high-level monitoring of the entire system. | |||||
| Provide ability to drill down from global view to individual device with alarm details. | |||||
| Monitor entry and exit lane status: lane open/closed, device online/offline, mirrored device screen display, ticket jams, gate failure/stuck up, low/out ticket supply, illegal exit,illegal entry, backou, low/out receipt paper | |||||
| Alarms shall be user-selectable by event type with configurable alarm priority, displayed on workstations or sent via email/SMS to authorized users. | |||||
| Abnormal status displayed with alarm priority level and audible alarm until condition corrected; acknowledgement from any command center workstation. | |||||
| Equipment management: put lane in/out of service, open/close barrier gates, barrier gate vend with drop-down reason selection (up to 6 County-defined reasons), and event logging of all remote/local gate vends. | |||||
| Event log shall record all system events, viewable/exportable, sortable by activity code, facility, device ID, with detailed reports by time/facility/location/device/user. | |||||
| Customer intercom call shall automatically bring detailed lane status screen and initiate pinhole camera feed at workstation. | |||||
| Remote transaction processing: LPR lookup to find entry date/time, auto-compute fee; lost/stolen ticket manual entry or fixed rate; unreadable ticket manual input; detailed transaction reports for remote attendants. | |||||
| Access Credential Management System (ACMS) | |||||
| ACMS shall manage access credentials and accounts for County employees, tenant employees, non-domiciled crew, contractors/vendors, and VIPs. | |||||
| Primary credential: AVI transponder; secondary: QR code or LPN match as fallback. | |||||
| Credential holders may pay monthly via credit card on file or through invoicing, or not be charged; auto shut-off for expired/declined cards. | |||||
| Account management: assign credentials to master accounts with individual detail, authentication via login/password. | |||||
| Credential activation, deactivation, and blocking recognized in lane immediately upon action at PARCS workstation. | |||||
| Allow authorized users via browser to create accounts and activate/deactivate credentials. | |||||
| Manage credential lifecycle: inventory, issuance, deactivation, and replacement. | |||||
| Support unlimited in/out privileges with and without restricted days/times. | |||||
| Support accounts with limited credentials allowed in facilities at one time; access blocked when exceeding allowed number. | |||||
| Allow multiple credentials registered to an individual user but only one credential in a facility at a time. | |||||
| Provide master accounts with sub-accounts, with access restrictions by facility, account, and credential for time of day and day of week. | |||||
| Provide hard and soft passback set by individual credential, master account, subaccount, and facility, working across shared exit plazas. | |||||
| Record all credential usage including lane ID, entry/exit date/time, facility, credential number, and parking fee. Retain history after deactivation and re-issuance. | |||||
| Troubleshoot faulty credentials with quick look-up of status, lane activity, and payment history. | |||||
| Store customer credit cards on file (encrypted/tokenized) for recurring payment and pay-per-use charges. | |||||
| Automatic notification to permit holders for annual renewals and credit card expiration. | |||||
| Ability to send emails to customer groups. | |||||
| ACMS data input fields per credential account: unique credential number, credential type, customer ID, account number, holder name, validity period, organization, phone, email, parking privilege codes, license plate number(s), vehicle make/model. | |||||
| Credit Card Processing Subsystem | |||||
| PCI-compliant credit card processing such that no product prevents County from achieving/maintaining PCI compliance. | |||||
| Solution validated per PCI P2PE program with current validation maintained throughout contract. | |||||
| System shall transmit credit card information to server in direct communication with authorizing clearinghouse for real-time approval of each transaction. | |||||
| Process and store credit card transactions at each field device in PCI-compliant offline mode during communication loss, with capacity for at least 2,500 offline transactions per device and forward stored transactions for approval upon communication restoration; County receives notice of denied transactions. | |||||
| Insertion-style and NFC-enabled credit card reader: magnetic stripe, EMV chip, NFC tap, mobile payments (Apple Pay, Google Wallet, Samsung Pay), American Express, Discover, MasterCard, Visa; P2PE certified. | |||||
| Accept credit card payments online for mobile device scan-to-pay and credit card on file payments. | |||||
| VoIP Intercom Subsystem | |||||
| Provide VoIP intercom system for two-way communication between PARCS field devices and command center, deployed as on-premises solution and include audio recording capability. Intercom units for all entry stations and exit stations, with integration to pinhole cameras | |||||
| Intercom system classified as critical component, essential for cashless, unattended lane environment; include in spare parts inventory with fully redundant backup system. | |||||
| Noise cancellation capability for background noise (traffic, aircraft, wind). | |||||
| Ability to queue calls and view all queued calls on command center workstation monitors. | |||||
| Individually programmable volume control, programmable call routing to County-designated phone numbers, and call forwarding feature. | |||||
| Physical push button or touchscreen softkey call initiation with microphone, loudspeaker, and in-use LED housed in one unit. | |||||
| Entry Station (ES) | |||||
| ES provided at all public entry lanes and test bed per PARCS Equipment Matrix. | |||||
| Color touchscreen display, minimum 10" diagonal, with visual instructions and universal icons/graphics. Push button/touchscreen-activiated intercome integrated into ES face. | |||||
| Customer interface with two user-selectable languages minimum (English and Spanish). | |||||
| Push button/touchscreen-activated ticket dispenser issuing one barcode/QR code ticket per entry, with unique lane ID, date/time, transaction number, LPN, and scan-to-pay QR code printed on each ticket. | |||||
| Proximity card reader integrated into ES face for County-issued and PARCS-generated badges. | |||||
| Barcode/QR code reader integrated into ES face for standard barcodes, QR codes, printed and mobile-displayed codes. | |||||
| Ticket stock low and out alarms generated in PARCS application. | |||||
| Interface with LPR camera, AVI reader (if applicable), barrier gate, and vehicle detectors in respective lanes. | |||||
| Mobile Device Scan-to-Pay | |||||
| Provide scan-to-pay solution: customers scan QR code on ticket with mobile device to pre-pay parking fee prior to exit with no mobile app download required. QR code scan directs mobile browser to online payment portal; adaptive website adjusting to any device/tablet screen. | |||||
| Payment portal landing page shall be white label, fully customizable to match County branding (graphics, colors, fonts, unlimited characters, messaging). | |||||
| Payment portal shall provide ability for customers to enter email/mobile number for receipts. | |||||
| All scan-to-pay revenue and activity reported through the PARCS. | |||||
| Exit Station (EX) | |||||
| EX provided at all public exit lanes and test bed per PARCS Equipment Matrix. | |||||
| Color touchscreen display, minimum 7" diagonal, with visual instructions, universal icons/graphics, and two user-selectable languages (English and Spanish). | |||||
| Proximity card reader integrated into EX face for County-issued and PARCS-generated badges. | |||||
| Barcode/QR code reader integrated into EX face; reads and verifies unpaid, paid, and validated tickets. | |||||
| Insertion-style and NFC-enabled credit card reader: magnetic stripe, EMV chip, NFC tap, mobile payments (Apple Pay, Google Wallet, Samsung Pay), American Express, Discover, MasterCard, Visa; P2PE certified. | |||||
| Cancel button/softkey icon and push button/softkey intercom integrated into EX face. | |||||
| Receipt printer producing receipts for all transactions with: County-approved header, transaction number, lane number, LPN, entry/exit date/time, length of stay, fee, validation/discount, payment type, card type, last 4 digits. User-configurable auto-issue or by request. | |||||
| Receipt stock low and out alarms generated in PARCS application. | |||||
| Pinhole camera with integration to command center; automatic activation on intercom call. | |||||
| Interface with LPR camera, AVI reader (if applicable), barrier gate, and vehicle detectors in respective lanes. | |||||
| Barrier Gate (BG) | |||||
| BG provided at all entry and exit lanes per PARCS Equipment Matrix. | |||||
| Straight (non-articulating) aluminum or fiberglass gate with padded arm and illuminated LED lights (red/green for closing/closed/opening/open states). | |||||
| Electronically controlled rebound feature; manual open/close switch inside housing and shall have sufficient power/resistance to prevent manual forced opening | |||||
| Microprocessor-controlled gate controllers with directional logic, electronic outputs for alarms/counters, communication of gate status to PARCS workstations. | |||||
| BG shall default to open position in event of power failure. | |||||
| Receive commands from PARCS workstations for remote opening/closing. | |||||
| Vehicle Detection Devices | |||||
| Provide new in-ground and surface-mount loops per PARCS Equipment Matrix; detect vehicular presence, legal entry/exit, illegal entry/exit, and back-out. | |||||
| Two (2) vehicle detection loops per public entry lane (ES activation and BG closing) and per public exit lane (EX activation and BG closing). | |||||
| Sensitive tailgate recognition system resolving two automobiles within one (1) foot of each other on standard loop. | |||||
| Fully microprocessor-based loop detectors with adjustable sensitivity modes for vehicles of varying height/size. | |||||
| Handheld Point-of-Sale Device | |||||
| Provide handheld POS device for County operations team to process cash, credit card, and exception transactions in unstaffed lanes. Mark ticket as paid in PARCS in near real-time so ticket scanned at EX opens gate. | |||||
| Process bankcards with real-time encryption; process validations as payment option; issue receipt to customer. | |||||
| Interface/integrate with PARCS: record all revenue, provide transaction counts and amounts by payment type, reconcile handheld to PARCS, process all exception transaction types, close open transactions. | |||||
| LPR Subsystem | |||||
| Furnish LPR at all public entry and exit lanes, fully interfaced and integrated into the PARCS. | |||||
| Tie LPN captured at entry to unique entry credential information for every transaction; record LPN at exit for matching. | |||||
| Support frictionless processing: Fee via license plate (auto-compute at exit), grace ticket (free exit within grace period), registered LPN credential, validated credential, paid ticket via scan-to-pay, and QR/barcode/NFC credential with LPN match. | |||||
| Pre-capture camera placement: LPN captured prior to vehicle pulling up to ES/EX. | |||||
| On-board processor within each LPR camera for OCR functions; infrared primary illumination with full-color secondary capture/overview of vehicle. | |||||
| LPR workstation functionality: review/correct LPR data, manage exceptions, remote processing via automated software tool with minimal mouse clicks and no manual data entry required. | |||||
| LPR N Factor accuracy rating of 96% (all characters read correctly) for all non-exception vehicles and LPR N-1 Factor accuracy rating of 98% (all but one character correct) for all non-exception vehicles. | |||||
| Automated configuration for N or N-1 matching levels from workstation. | |||||
| Provide means to remotely score LPR subsystem to verify performance; ambient lighting shall have no effect on accuracy. | |||||
| Recommend and provide protection for LPR cameras from vehicle strikes. | |||||
| AVI System | |||||
| Provide AVI subsystem as part of ACMS for shuttle bus, employee, tenant, crew, and VIP access to parking facilities. | |||||
| Provide AVI antennas with readers and mounting structures in designated lanes per PARCS Equipment Matrix. | |||||
| Provide two types of transponders: windshield (thin, flexible, beam-powered, non-battery, non-transferable) and license plate (915MHz, beam-powered, non-battery, water-resistant). | |||||
| Read and accurately identify no less than 99.9% of properly mounted tags passing through read zone. | |||||
| During communication loss, AVI reader shall open gate for any transponder within validity range (including newly set up transponders). | |||||
| AVI system fully auditable with integrated reports; FCC regulatory compliance. | |||||
| Online Validation System | |||||
| Provide online validation scanners that scan ticket barcode and apply pre-programmed validation value to digital record in software. | |||||
| Validation types: dollar discount, time discount, and percentage discount. | |||||
| Record all validation creation and usage data: date/time, device ID, user ID, account number, validation value/parameters, customer name, reason; entry media number, exit data, lane ID, fee details. | |||||
| Provide detailed and summary validation activity reports by account for invoicing purposes. | |||||
| Validations shall allow use restrictions by quantity, facility/area, time of day, day of week, expiration date, and programmable duration limits. | |||||
| Pinhole Camera System | |||||
| Camera feed automatically displays on command center workstation when intercom call is answered. | |||||
| Camera shall legibly display ticket sequence numbers, credential numbers, and ID numbers held up by customers. | |||||
| Each camera shall support RTSP with minimum of one stream for PARCS and one available for County security systems. | |||||
| Record continuous video 24/7/365, stored for minimum 30 days per County retention policies. Live and recorded feeds accessible in real-time by County security. | |||||
| UPS | |||||
| Provide outdoor-rated UPS for all PARCS field equipment per PARCS Equipment Matrix. | |||||
| Minimum 30 minutes of full lane functionality on battery backup with at least 30% overhead capacity. | |||||
| Sealed, maintenance-free VRLA or Lithium-Ion batteries with minimum 5-year design life, hot-swappable, automated self-diagnostics, recharge ≤6 hours to 90%. Pure (true) sine wave output with automatic voltage regulation (AVR). | |||||
| Remote monitoring via SNMP v3, email/SMS alerts, and browser-based GUI; monitoring of input/output voltage/frequency, battery charge/health/runtime, alarms, and event history. | |||||
| Dynamic Signage | |||||
| Provide entry lane OPEN/CLOSED LED signs displaying "OPEN" in green and "CLOSED" in red per PARCS Equipment Matrix. | |||||
| Provide exit plaza overhead dynamic message LED signs (full color RGB) per PARCS Equipment Matrix. Messages include OPEN, ONLINE PRE-BOOKED RESERVATIONS ONLY, PRE-PAID, CREDIT CARD ONLY, CLOSED, etc. | |||||
| Provide all sign mounting analysis, design, materials, and labor. LED matrix dimensions approximately 20"H x 120"W, pixel pitch 8mm or smaller. | |||||
| Installation | |||||
| Procure shipping insurance for all shipments; replace damaged/lost items at no additional cost. | |||||
| Install all PARCS equipment per manufacturer recommendations with documentation and approval for any software patches/upgrades during installation. | |||||
| Maintain approved project schedule from NTP through final system acceptance with weekly updates. | |||||
| Multi-factor authentication required for remote PARCS access; individual accounts required (no group accounts). | |||||
| Acceptance Testing | |||||
| Conduct Factory Acceptance Test (FAT) to verify functional performance of all systems, subsystems, and components prior to equipment shipment. | |||||
| Conduct Lane Acceptance Tests (LAT) for each entry and exit lane after installation, including PARCS equipment and software tests. | |||||
| Conduct System Acceptance Test (SAT) for 30 consecutive 24-hour periods with all equipment under actual operating conditions. No individual subsystem unavailable ≥4 hours cumulative or >2 consecutive hours. | |||||
| Submit test scripts for each acceptance test at least fourteen (14) days prior to each test. Provide all ancillary items and personnel for testing. | |||||
| Contractor shall credit County for travel/labor costs from additional effort required due to Contractor-caused test failures. | |||||
| Training | |||||
| Provide comprehensive training: Initial (pre-operational), Mid-Warranty (12-month refresh), and Final (end of warranty knowledge transfer). All sessions on-site at DAB. | |||||
| Training groups: parking ambassadors, management office staff, system administrators/IT staff, accounting/audit, and maintenance staff. | |||||
| Train maintenance staff to Level 1 (basic: gate arms, paper jams, reboots) and Level 2 (advanced: diagnosing malfunctions, replacing components). | |||||
| Final two months or final two occurrences of warranty-period preventative maintenance performed on-site with County staff for hands-on training. | |||||
| No training session shall exceed four (4) hours. Provide instructional notebooks/user's manuals in hardcopy and electronic format. Instructor shall speak fluent English. | |||||
| Service Level & Maintenance Tracking | |||||
| Provide service tracking system to monitor/record all maintenance/repair services during installation, warranty, and post-warranty with unique work order numbers, device IDs, problem descriptions, date/time, corrective actions, and parts used. | |||||
| Create annual preventative maintenance schedule listing each device; submit monthly PM reports with updated schedule. | |||||
| Provide weekly out-of-service report, monthly repair service report by problem/lane ID, and monthly PM report of all maintenance performed. | |||||
| Reimburse County for quantifiable lost revenue directly related to Contractor errors (e.g., incorrect rate updates, system misconfiguration). |
File details come from the government source that posted it. Updated .