Riverside City Council
June 14, 2022

AGREEMENT FOR PARKING ACCESS AND REVENUE CONTROL SYSTEM (PARCS)

TIBA PARKING SYSTEMS, LLC
On this day of → 2022, ("Effective Date") the CITY OF
SYSTEMS, L Cal originate city and mu noria corporatie do do undess in calitoria, 565 W. Lambert Rd., Brea, CA 92821, State Contractor's License No. 1043610 ("Contractor"), mutually agree as follows:

1. Scope of Services. Contractor shall furnish all engineering, design, labor, materials and equipment for and perform the work for the Downtown Parking Garage - Parking Access and Revenue Control Systems (PARCS) Replacement ("the Services"). Contractor shall perform the Services in accordance with the provisions and requirements of the following Contract Documents: City of Riverside Public Works Department Request for Proposals for Downtown Parking Garage - Parking Access and Revenue Control System (PARCS) Replacement, dated March 31, 2020 ("RFP 1955"), the General Conditions and Technical Specifications contained therein, this Agreement and all other documents, maps, texts and items referred to in the foregoing documents, and the provisions and requirements of the Scope of Services attached hereto as Exhibit "A" and incorporated herein by reference. These Contract Documents are incorporated herein by this reference and are intended to be correlative and constitute Contractor's performance obligations. The specific terms and conditions of this Agreement shall control and have precedence over any contradictory or inconsistent terms and conditions included in the other Contract Documents and shall be controlling in questions of interpretation.

2. Term. The initial term of the Agreement shall be for a period of six (6) years, from the date of execution, with the option to extend for two (2) additional two-year terms not to exceed four (4) years, based upon acceptable performance by the Contractor, acceptable fees and subject to the same terms and conditions of the Agreement.

3. Compensation. City shall pay Contractor for the performance of the Services during the initial six (6) year term of this Agreement a Contract Price not to exceed One Million Three Hundred Nine Thousand Five Hundred Forty-Four Dollars and Seventy-Nine Cents ($1,309,544.79). City shall pay Contractor for Services performed to City's satisfaction in accordance with the provisions of the RFP, and the Compensation Schedule attached hereto as Exhibit "B" and incorporated herein by this reference. Pricing is to remain firm for the initial contract Term. Should the option to renew for additional years be exercised, City and Company shall adhere to the Compensation Schedule attached as Exhibit B for years 7 through 10 unless earlier terminated as provided herein. All such extensions/amendments shall be made in writing and approved by the parties.

4. Extra Material. Contractor shall not be compensated for any extra materials used or time expended over and above the Contract Price, unless prior written approval for the same has been granted by City. In addition, Contractor shall only be compensated for services actually rendered.

5. Warranties. Contractor shall obtain in the name of City, or transfer or assign to City or City's designee, any and all warranties or guarantees which Contractor obtained from manufacturers or suppliers, and further agrees to perform the Work in such a manner so as to preserve any and all such warranties.

6. General Compliance with Laws. Contractor shall keep fully informed of federal, state and local laws and ordinances and regulations which in any manner affect those employed by Contractor, or in any way affect the performance of Services by Contractor pursuant to this Agreement. Contractor shall at all times observe and comply with all such laws, ordinances and regulations, and shall be solely responsible for any failure to comply with all applicable laws, ordinances and regulations.

7. Business Tax and Penalties. Contractor acknowledges and agrees that with respect to any business tax or penalties thereon, utility charges, invoiced fee or other debt which is owed, or which becomes owed, by Contractor to City, City reserves the right to withhold and offset said amounts from any payments, refunds or reimbursements owed by City to Contractor under the Agreement. Notice of such withholding and offset shall promptly be given to Contractor by City in writing. In the event of a dispute as to the amount owed or whether such amount is owed to City, City will hold such disputed amount until either the appropriate appeal process has been completed or until the dispute has been resolved.

8. Business Tax Certificate. As a condition of this Agreement, Contractor shall secure a business tax certificate to operate in the City of Riverside pursuant to Chapter 5.04 of the Riverside Municipal Code, and shall also secure any other licenses or permits which may be required.

9. Worker's Compensation Insurance. By executing this Agreement, Contractor certifies that Contractor is aware of and will comply with Section 3700 of the Labor Code of the State of California requiring every employer to be insured against liability for workers' compensation or to undertake self-insurance before commencing any of the work. Contractor shall carry the insurance or provide for self-insurance required by California law to protect said Contractor from claims under the Workers Compensation Act.

Prior to City's execution of this Agreement, Contractor shall file with City either (1) a certificate of insurance or self-insurance evidencing that such insurance is in effect, or that Contractor is self-insured for such coverage; or (2) a certified statement that Contractor has no employees, and acknowledging that if Contractor does employ any person, the necessary certificate of insurance will immediately be filed with City. Any certificate filed with the City shall provide that City shall be given ten (10) days prior written notice before modification or cancellation thereof.

Contractor's workers' compensation carrier shall be authorized to transact insurance business in the State of California with a policy holder's rating of "A" or higher and a Financial Class VII or larger.

10. Contractor's Liability Insurance.

10.1 Minimum Scope. Prior to City's execution of this Agreement and Contractor's commencement of Work, Contractor shall secure, submit proof of and shall thereafter maintain without interruption, until completion of the Contractor, such commercial general, automobile liability, professional liability, bulders risk and/or installation floater insurance as shall protect Contractor, its Subcontractors and the Additional Insured's from any and all claims for damages for personal injury, including acidental death, as well as any and all claims for property damage which may arise from or which may concern operations under the Contract, whether such operations be by or on behalf of Contractor, any subcontractor or anyone directly or indirectly employed by, connected with or acting for or on behalf of any of them.

0.2 Carrier Katings. All liability insurance shall be issued by an insuranc ompany or companies authorızed to transact habılity insurance business in the state o California with a policy holder's rating of A or higher and a Financial Class of VIl or larger.

10.3 Minimum Limits. Contractor shall maintain minimum limits of insurance as follows:

10.3.1 Commercial General Liability: Contractor's commercial general liability insurance policy shall cover both bodily injury (including death) and property damage (including, but not limited to, premises operations liability, products-completed operations lability, independent contractor's liability, personal injury liability, and contractual liability) in an amount not less than $1,000,000 per occurrence, an aggregate limit for products/completed operations in the amount not less than $2,000,000.

Commercial General Liability. Insurance Services Office Commercial General Liability Coverage (occurrence Form CG 0001). This coverage shall include:
i. Manufacturers and Contractors liability,
ii. Broad form property damage in any case where the Contractor has any property belonging to the City in the Contractor's care, custody, or ili. Owners and Contractors' protective liability,
iv. Blanket contractual liability,
v. Products and completed operations coverage, and
vi. Coverage for collapse, explosion, and excavation.

10.3.2 Automobile Liability Insurance: Contractor's automobile liability policy shall cover both bodily injury and property damage in an amount not less than $1,000,000 per occurrence and an aggregate limit of not less than $1,000,000. All of Contractor's automobile and/or commercial general liability insurance policies shall cover all vehicles used in connection with Contractor's performance of this Agreement, which vehicles shall include, but are not limited to, Contractor owned vehicles, Contractor leased vehicles, Contractor's employee vehicles, non-Contractor-owned vehicles and hired vehicles.

Automobile Liability. Insurance Services Office Automobile Liability Coverage (Form CA 0001), covering Symbol 1 (any auto). This coverage shall include:
i. Coverage for owned, non-owned, and hired automobiles.

10.4 Notice of Cancellation and Renewals. The policies shall not be canceled unless thirty (30) days prior written notification of intended cancellation has been given to City by certified or registered mail (this obligation may be satisfied in the alternative by requiring such notice to be provided by Contractor's insurance broker and set forth on its Certificate of Insurance provided to City). Contractor agrees that upon receipt of any notice of cancellation or alteration of the policies, Contractor shall procure within five (5) days, other policies of insurance similar in all respects to the policy or policies to be cancelled or altered. Contractor shall furnish to the City copies of any endorsements that are subsequently issued amending coverage or limits within fourteen (14) days of the amendment.

10.5 All Coverage's. The insurance policy or policies shall also comply with the following provisions:
a. Policies shall include premises/operations, products completed operations, independent contractors, owners and contractors' protection, explosion, collapse, underground hazard, broad form contractual, personal injury with employment exclusion deleted, and broad form property damage. b. The policy shall be endorsed to waive any right of subrogation against the City and its subconsultants, employees, officers, agents and directors for work performed under this Agreement.
c. If policies are written on a claims made basis, the certificate should so specify and the policy must continue in force for five (5) years after completion of the Project. The retroactive date of the coverage must also be listed.
d. The policy shall specify that the insurance provided by Contractor will be considered primary and not contributory to any other insurance available to the City of Riverside. Contractor shall provide Form No. CG 20010413 to City.
e. All policies of insurance shall name the City as an Additional Insured and shall contain the following language: "Solely with respect to work done by and on behalf of the name insured for the City of Riverside, it is agreed that the City of Riverside, and its officers and employees are added as additional insureds under this policy."

10.6 Certificates of Insurance, Additional Insured Endorsements and Deductibles.

Prior to execution of the Agreement, and thereafter upon City's request, Contractor shall furnish City with original certificates of insurance and additional insured endorsements setting forth evidence of all insurance coverage required by this Article. Each certificate and endorsement is to be signed by a person authorized by that insurer to bind coverage on its behalf. The City of Riverside, its City Council and all of its respective officials, officers, directors, employees, managers, commission members, representatives, agents and council members shall be named as additional insured's under each policy.

10.7 Contractor's Failure to Provide Required Insurance. Failure to maintain required insurance at all times shall constitute a default and material breach. In such event, Contractor shall immediately notify City and cease all performance under this Contract until further directed by the City. In the absence of satisfactory insurance coverage, City may, at its discretion and sole option: (a) procure insurance with collection rights for premiums, attorneys' fees and costs against Contractor by way of set-off or recoupment from sums due Contractor; (b) immediately terminate or suspend Contractor's performance of the Contract; (c) pay Contractor's premiums for renewal of Contractor coverage; or (d) self-insure the risk, with all damages and costs incurred, by judgment, settlement or otherwise, including attorneys' fees and costs, being collectible from Contractor, by way of set-off or recoupment from any sums due Contractor. Upon demand, Contractor shall repay City for all sums that City paid to obtain, renew, reinstate or replace the insurance, or City may offset the cost against any monies that the City may owe Contractor.

10.8 Verification of Coverage. City shall have the right to obtain complete and certified copies of Contractor's and Subcontractors' insurance policies (including, but not limited to, the declarations page, form list and riders), endorsements or certificates required under the Contractor Documents, upon request (including, but not limited to, the declarations page, form list and riders).

10.9 Reassessment of Insurance Requirements. At any time during the duration of this Contract, the City may require that Contractor obtain, pay for, and maintain more or less insurance depending on the City's assessment of any one or more of the following factors:
(1) the City's risk of liability or exposure arising out of, or in any way connected with, Contractor's services under this Contract; (2) the nature or number of accidents, claims, or lawsuits arising out of, or in any way connected with, Contractor's services under this Contract; or (3) the availability, or affordability, or both, of increased liability insurance coverage.

10.10 Contractor's Insurance for Other Losses. The Contractor and its Subcontractors of every tier shall assume full responsibility for all loss or damage from any cause whatsoever to any tools, Contractor's (or Subcontractors') employee owned tools, machinery, equipment, or motor vehicles owned or rented by the Contractor, or the Contractor's agents, suppliers or Subcontractors as well as to any temporary structures, scaffolding and protective fences.

10.11 No Limitation. Contractor's maintenance of insurance as required by the Contract Documents shall not be construed to limit the liability of the Contractor's or its Subcontractors of any tier to the coverage provided by such insurance, or otherwise limit the City's recourse to any remedy available at law or in equity.

10.12 Subcontractors' Insurance. The Contractor's shall include in all subcontracts a requirement that the Subcontractors of every tier shall obtain and maintain, at a minimum, all insurance required by Articles 9 and 10 of this Agreement except that the limits of liability and deductibles shall be in amounts determined by the Contractor, based on the degree of hazardous exposure according to the Work performed by each Subcontractor and the size of each

11. Bonds. Prior to City's execution of this Agreement, Contractor shall furnish City with two completed surety bonds (on bond forms provided by City) in the amount of Eight Hundred Ninety-Nine Thousand Three Hundred Fifteen Dollars and Seventy-Nine Cents ($899,315.79), one as security for the faithful performance of this Agreement and one as security for the payment of all persons performing labor and furnishing materials in connection with this Agreement. Both bonds shall be in the amount of 100% of the Contract Price and shall be subscribed by a corporate surety which is authorized to transact surety insurance business in the State of California with a policy holder's rating of A or higher and a Financial Class VII or larger. Should any bond or surety become insufficient, Contractor shall furnish City with new bonds within 10 days after receiving notice from City. No payments will be due or paid under this Agreement until any and all bond deficiencies have been remedied. Contractor by execution of this Agreement acknowledges that the bonds are not Contract Documents but are separate obligations.

12. Termination. City and Contractor shall have the right to terminate any or all of Contractor's Services and work covered by this Agreement at any time upon thirty (30) calendar day's written notice to Contractor. In the event of such termination, Contractor shall submit Contractor's final written statement of the amount of services provided as of the date of such termination for payment by the City.

Notwithstanding the foregoing, the City may terminate Contractor's performance of this Agreement upon five (5) calendar day's written notice if:
a. Contractor fails to promptly begin performance of the Services; or b. Contractor fails to perform the Services in accordance with the Contract Documents, including conforming to applicable standards set forth therein, or refuses to remove and replace rejected materials or unacceptable work; or c. Contractor discontinues performance of the Services; or d. Contractor fails to make payment to subcontractors for materials or labor in accordance with applicable law; or
e. Contractor disregards laws, ordinances, or rules, regulations, or orders of a public authority having jurisdiction; or
f. Contractor otherwise is guilty of breach of a provision of this Agreement; or g. Contractor becomes insolvent, is adjudicated bankrupt, or makes a general assignment for the benefit of creditors and fails to provide City with adequate assurances of Contractor's ability to satisfy its contractual obligations.

A receiver, trustee, or other judicial officer shall not have any right, title, or interest in or to this Agreement. Upon that person's appointment, City has, at its option and sole discretion, the right to immediately cancel the Agreement and declare it null and void.

13. Indemnity. Except as to the sole negligence, active negligence or willful misconduct of the City, Contractor assumes liability for and agrees, at Contractor's sole cost and expense, to promptly and fully indemnify and hold the City, its City Council, and all of its respective officials, officers, directors, employees, managers, commission members, representatives, agents, council members, ("Indemnitees"), harmless from and against any and all loss, damage, claims, allegations, actions, suits, arbitrations, administrative proceedings, regulatory proceedings, or other legal proceedings, causes of action, demands, costs, judgments, liens, stop notices, penalties, damages, losses, anticipated losses of revenue, expenses (including, but not limited to, operations or duties of Contractor, or anyone employed by or working under Contractor, and from all claims by anyone employed by or working under Contractor for services rendered to Contractor in the performance of this Agreement ("Indemnity Claims"), notwithstanding that the City may have benefited from their services. This indemnification provision shall apply to any acts or omissions, willful misconduct or negligent conduct, whether active or passive, on the part of Contractor or of anyone employed by or working under Contractor.

The parties expressly agree that any payment, attorneys fees, costs or expense that the City incurs or makes to or on behalf of an injured employee under the City's self- administered workers' compensation is included as a loss, expense or cost for the purposes of this Section, and that this Section shall survive the expiration or early termination of the Agreement.

14. Duty to Defend. Contractor agrees, at its sole cost and expense, to promptly defend the Indemnitees from all Indemnity Claims. The duty of the Contractor to indemnify and hold harmless the Indemnitees includes the separate and independent duty to defend the Indemnitees, which duty arises immediately upon receipt by Contractor of the tender of any Indemnity Claim from an Indemnitee. The Contractor's obligation to defend the Indemnitees shall be at Contractor's sole expense, and not be excused because of Contractor's inability to evaluate liability or because the Contractor evaluates liability and determines that the Contractor is not liable. This duty to defend shall apply whether or not an Indemnity Claim has merit or is meritless, or which involves claims or allegations that any or all of the Indemnitees were actively, passively or concurrently negligent, or which otherwise assert that the Indemnitees are responsible, in whole or in part, for any Indemnity Claim. Contractor agrees to provide this defense immediately upon written notice from the City, and with well qualified, adequately insured and experienced legal counsel acceptable to the City. Contractor will reimburse City for reasonable defense costs for claims arising out of Contractor's professional negligence based on the percentage of Design-Build's liability.

15. Non-Discrimination. During Contractor's performance of this Agreement, Contractor shall not discriminate on the grounds of race, religious creed, color, national origin, ancestry, age, physical disability, mental disability, medical condition including the medical condition of Acquired Immune Deficiency Syndrome (AIDS) or any condition related thereto, marital status, gender, gender identity, genetic information, gender expression, sex or sexual orientation, military and veteran status, in the selection and retention of employees and subcontractors and the procurement of materials and equipment, except as provided in Section 12940 of the California Government Code. Further, Contractor agrees to conform to the requirements of the Americans with Disabilities Act in the performance of this Agreement.

16. Prevailing Wage. Pursuant to Section 1771 of the California Labor Code, Contractor and all subcontractors are required to pay the general prevailing rates of per diem wages, overtime and holiday wages as determined by the Director of the Department of Industrial Relations and implemented by Resolution No. 13346 of the City Council of the City of Riverside. The Director's determination of prevailing wage rates is available on-line at www.dir.ca.gov/dlsr/DPreWageDetermination.htm, and is referred to and made a part hereof as though fully set forth herein.

Per Senate Bill 854 (2014), Contactor and subcontractors shall register with the Department of Industrial Relations (DIR) in order to bid and perform public works projects.

Contractors and subcontractors on all public works projects shall submit electronic certified payrolls to the Labor Commissioner and City unless excused from this requirement.

Contractor is aware of and stipulates that Contractor will also comply with the following sections of the California Labor Code:
a. Section 1775 prescribing sanctions for failure to pay prevailing wage rates; b. Section 1776 requiring the making, keeping and disclosing of detailed payroll records and prescribing sanctions for failure to do so; c. Section 1777.5 prescribing the terms and conditions for employing registered apprentices;
d. Section 1810 providing that eight hours of labor shall be a day's work; e. Section 1813 prescribing sanctions for violations of the provisions concerning eight-hour work days and forty-hour work weeks; and
f. Sections 1725.5 and 1771.1 requiring all general contractors and subcontractors to be registered with DIR. Registration can be accomplished through the DIR website by using this link: http://www.dir.ca.gov/Public- Works/PublicWorks.html.

17. Notices. Service of any notices, bills, invoices or other documents required or permitted under this Agreement shall be sufficient if sent by one party to the other by United States mail, postage prepaid and addressed as follows:

City Contractor
City of Riverside TIBA Parking Systems, LLC
Public Works Director Attn: Malloy Pohrer
3900 Main Street 565 W. Lambert Rd.

Riverside, CA 92522 Brea, CA 92821
waive all provisions of law providing for a change of venue in such proceedings to any other county.

19. Independent Contractor. Contractor shall at all times during its performance of the Work retain its status as an independent contractor. Contractor's employees and agents shall under no circumstances be considered or held to be employees or agents of City and City shall have no obligation to pay or withhold state or federal taxes or provide workers' compensation or unemployment insurance for or on behalf of Contractor or its employees and agents.

20. Waiver. No action or failure to act by the City shall constitute a waiver of any right or duty afforded City under this Agreement, nor shall any action or failure to act constitute an approval of or acquiescence in any breach thereunder, except as may be specifically provided in this Agreement or as may be agreed in writing.

21. Severability. Each provision, term, condition, covenant and/or restriction, in whole and in part, in this Agreement shall be considered severable. In the event any provision, term, condition, covenant and/or restriction, in whole and/or in part, in this Agreement is declared invalid, unconstitutional, or void for any reason, such provision or part thereof shall be severed from this Agreement and shall not affect any other provision, term, condition, covenant and/or restriction of this Agreement and the remainder of the Agreement shall continue in full force and effect.

22. Authority. The individuals executing this Agreement and the instruments referenced herein on behalf of Contractor each represent and warrant that they have the legal power, right and actual authority to bind Contractor to the terms and conditions hereof and thereof.

23. Entire Agreement. This Agreement constitutes the final, complete, and exclusive statement of the terms of the agreement between the parties pertaining to the subject matter of IN WITNESS WHEREOF the parties hereto have caused this Agreement to be executed the day and year first above written.

CITY OF RIVERSIDE, a TIBA PARKING SYSTEMS, LLC, a
California charter city and Georgia limited liability company municipal corporation authorized to do business in California By:

City Manager By:

Printed Name: LUCA BOVALINO
Attest: Tille: PRESIDENT/CED
By:

City Clerk
By:

Certified as to Availability of Funds: Printed Name:

Title:

By:

Chief Financial Officer
Approved as to form:
318 h
By:

Senior Deputy City Attorney
IIRc-citylawlcycom\WPDocs\D002\P031\00637936.doc
22-0106 BSM 04/04/22

WORKERS' COMPENSATION CERTIFICATION
I am aware of the provisions of Section 3700 of the Labor Code which require every employer to be insured against liability for workers' compensation or to undertake self-insurance in accordance with the provisions of that code, and I will comply with such provisions before commencing the performance of the work of this contract.

DATED: TIBA PARKING SYSTEMS, LLC

EXHIBIT A
Scope of System

SCOPE OF WORK - PARKING ACCESS AND REVENUE CONTROL SYSTEM (PARCS)

REPLACEMENT
This section describes the operating environment and summarizes the scope for the PARCS.

Current and Future Facilities
At this time, there are five parking structures owned and operated by City of Riverside.

All facilities are available to the public 24hours /7 days a week.

The proposed PARCS system, to be from this point referred to as "the system", shall be expandable to potentially 5+ (1,600 stalls) locations owned or may be acquired by the City of Riverside.

The system shall meet or exceed City's requirements for overall management, system efficiency, revenue accounting, revenue security, and customer service aspects of the off-street parking operations for at least the next ten years after the City's final acceptance.

A. Summary Scope of Work
The system shall:

1. Account for all revenue, by facility, lane, employee, customer, event, program, payment method, and time, with complete audit trails (any transaction shall be completely auditable from start to finish).

2. Minimize theft and loss of revenue, with accounting for lost or stolen tickets and IOUs.

3. Maintain a PCI/DSS-compliant environment, consistent with evolving standards and requirements.

4. Incorporate single source capability to manage all facilities for better accountability.

5. Provide flexibility in fee schedules for all types of parking customers, and the ability to introduce new parking programs in the City. Accurately calculate appropriate fees for all types of transactions.

6. Increase efficiency of operations and maintenance.

7. Provide full reporting (revenue and statistics), with flexibility in content, formatting, and timing of the pertinent operational and management reports.

8. Ensure flexibility for any future need to update, upgrade, and/or expand the system readily (either additional lanes or additional facilifies).

9. Provide an intuitive and user-friendly interface for customers, Operator, and City personnel.

10. Be fully protected against and not affected by weather/environmental conditions, including temperature extremes, humidity, rain, dust, RFI/EMI, and static electricity.

Not emit excessive heat, RFI/EMI, static electricity, or fumes.

11. Meet all ADA requirements (federal, state, local) as of the date of acceptance, along with any requirements that are published but due to be implemented later.

12. All equipment shall be UL listed or tested and certified by an OSHA-recognized testing laboratory and approved for the intended use.

B. System Features and Functionality
The following subsections describe requirements for the features and functionality envisioned in the City's new PARCS. The descriptions are detailed to provide a better understanding of the operational procedures. The bid is to illustrate the capability requirements of the new PARCS system.

System-wide Requirements

1. General and Design
a. Vendor and system must comply with all State and Local codes and ordinances, as applicable.
b. The system shall have the ability to process transient and monthly parkers (the latter by variable timeframes, not just by month).

c. The system shall be scalable and modular, such that new facilities can be added with no loss of performance. System shall allow expansion to at least 10 facilities and 3,000 parking spaces.
d. Describe your approach to ensure scalability of the product. This includes transaction growth, upgrades and replacements of components of the architecture, technology, and application.
e. Facilities shall be classified into groups (including groups of one) to be treated as a "subsystem," such that administrators of any group shall not be able to access records and configuration for other groups. However, City and Parking Services staff shall be able to access any group at any time, should the role require it. f. The system shall provide the ability to separate/sever a facility or group of facilities and place into operation as a completely independent facility/group at any time (e.g., the back-office server equipment/software or cloud will always be available for purchase by another party throughout the lifetime of the system). g. Management of various customers within the PARCS (e.g., monthly parkers, car pool, EV users, merchants), without requiring separate external databases to track relevant information.
h. The system shall provide the ability for users to see data customized to U.S. view (e.g., date/time format, currency format, etc.), regardless of the origin of the system.
i. The credit card payment gateway provider shall be compatible with and certified for use by the credit card processor at the acquiring bank of the City's choice. i. Include the capability for CCTV and sound recording of the facility (entrances, exits, cashier booths, etc.).
k. Parking control equipment manufacturer to design and engineer the entire PARCS, including controls, connections and anchorage to building structure, making necessary additions and modifications to PARCS manufacturer's standard details as may be required to comply with specified performance requirements, while maintaining the basic design concept.

1. The coordination of attachments must be made with a Structural Engineer prior to final design of attachments and coordination of attachments during the sequence of building construction may be necessary in advance of PARCS installation.
m. The PARCS shall be an open-architecture system: Vendor-independent, non- proprietary, computer system and device design based on official and/or popular standards.
n. It shall allow vendors to create add-on products that increase the PARCS (or devices) flexibility, functionality, interoperability, potential use, and useful life. o. Also enables the users to customize and extend the PARCS (or device's) capabilities to suit individual requirements.

2. Information Security Standards and Requirements
a. The PARCS vendor shall be a PCI DSS Level 1 Service Provider or shall delegate to a PCI DSS Level 1 Service Provider to store, process, or transmit cardholder data. b. The PARCS shall comply with Payment Card Industry Data Security Standard (PCI DSS), the latest version at the time of Contract Award. c. The PARCS shall comply with Payment Application Data Security Standard (PA DSS), the latest version at the time of Contract Award. d. The PARCS shall comply with EMV standards effective at the time of implementation, including fully compliant EMV "chip and PIN" readers and back- office processing.
e. The PARCS shall comply with City of Riverside IT Standards:
f. User authentication, with ability to define user rights for access, review, and edit of data
g. Describe the system's bandwidth requirements (within a facility as well as between a facility and the host/servers).
h. Provide backup for communications in case the primary connection malfunctions. i. Include system security for all applications, programs, and any other all devices. j. The city has standards utilizing Dell servers, VMWare, Aruba network switches, and Genetec video management system. Components proposed must meet the city's standards to be accepted.

3. System Availability/Safety/Performance Requirements
a. All PARCS components and their installation shall comply with all laws, ordinances, codes, rules, and regulations of public authorities having jurisdiction. It shall be the responsibility of the Contractor to meet these and all other current technical, performance, and safety standards that are applicable to all components and to the entire system, even when not specifically referenced. b. It shall be the Contractor's responsibility to obtain any and all permits that are required to complete this work.
c. The system shall have 99.99% availability or greater (less than 53 minutes of downtime per year).
d. System accuracy (fee calculations, transaction counts, exception processing) shall be greater than 99.999% (e.g., no more than one error in 100,000 transactions).
e. Users logged into the system through a web browser shall see response times under ten seconds.
f. The system shall maintain six months of data in the transactional system. All older data may be archived but should still be accessible for reporting and auditing/investigation purposes.

g. All peripheral devices shall synchronize their clocks with the central host, whether cloud-based or local server.
h. Failure of a component or subsystem in one lane shall not affect any other lanes within a facility.
i. Failure of a component or subsystem in one facility shall not affect any other facilities or groups.
j. Should communications interruptions occur, any given facility shall continue to process transactions:
k. Any entry prior to the interruption shall be allowed to exit after calculation of the correct fee, incorporating validations, coupons, and other discounts I. System shall allow entry to any credentials permitted to access the facility where the credential was created prior to the interruption (e.g., prepaid fees, monthly passes, LPR, etc.) and subsequent exit
m. System shall continue to allow transient entries/exits n. Credit card transactions below a configurable "floor limit" shall be authorized; the floor limit in the facility shall be changeable by a supervisor from within the facility or by Parking Services staff
o. Facilities shall have a "hot list" or "blacklist" of credit cards not to be accepted while offline
p. Stored credit card transactions shall be submitted for authorization when communications are restored
q. Stored credit card transactions shall be retained, encrypted, in device memory in such a way that loss of power will not cause them to be deleted or otherwise lost

4. Facilities Standards
a. Power

1. Structural attachment standards.

2. Must be able to use the current power available in the facilities. b. Payment methods

1. Cash/coins/tokens/validations (cashier booths, exit stations, selected POFs, Operator's Customer Service Desk)

2. Credit/debit card (including contactless, mag stripe, chip and pin)

3. Mobile payments (including the City's current mobile payment provider, ParkMobile)

4. Courtesy cards (describe your system's capabilities for this payment method)

5. Google Wallet/ApplePay/Softcard (formerly ISIS)

6. Include features to encourage non-cash/non-coin transactions

7. Discount programs

8. Include validations, car pool, electric vehicle, early bird, many other programs

9. Discounts may be exclusive or inclusive

10. The system should have the ability to handle multiple discounts/layers of pricing in one charge (off-peak discounts, early bird, validations, and other discounts); ability to rank discounts and apply highest-ranking discount over others; ability to detect highest-value discount and apply only highest-value discount.

11. Prepay at entry for events

12. Online, with or without reservations, for events

13. Online, after entry but before exit

14. Any other prepay programs your PARCS supports

15. Valet parking

16. Facilities owned/operated by the City of Riverside are used by local valet companies to store customers' vehicles. The PARCS must support tracking and billing for this usage.

17. Access through proximity (RFID) card or other "permanent" credential c. Valet Parking-as a service of the facility
Facilities owned/operated by the City of Riverside may wish to offer valet parking within the facility as a service to customers. An incoming customer would drop off his/her vehicles at the entry and a facility employee would park it. When the customer returns for his/her car, a facility employee would retrieve it. Note the following requirements:

1. "Valet monitor" to track a vehicle's location throughout transaction

2. The customer's anticipated departure time captured to allow management of locations

3. Claim checks tied to (or in lieu of) other parking credentials

4. Valet reservations

5. Daily report of entries/exits for each valet operation

6. Generation of invoices for parking usage for the valet operation

7. Allow for distinct rate tables, discounts from standard rates, or fixed fees for each valet operation

8. Describe the options for tracking a valet company's activity and producing an invoice with detail

9. Key tracking

10. Ability to send customer to retrieve vehicle if no valets are available (e.g., customer returns after valet operating hours if vehicle not blocked by another (after customer payment)

11. "I'm on the way" alerts from customers via phone call, handheld device app, etc.

12. Describe the options for facility-managed valet

13. Describe any options for valet prepayment
d. Extensibility
The PARCS shall allow incorporation of new technology, such as through APls or other integration mechanisms, to add features and capabilities as they are developed.

Describe your solution's ability to integrate or interface with each of the following:

1. Additional payment systems (provided through a variety of vendors), for prepayments as well as to pay for an open parking session

2. External reservation systems (provided through a variety of vendors)

3. Rate/hours/occupancy inquiries (provided through a variety of vendors)

4. LPR data (provided to a variety of consumers or obtained from a variety of sources

5. EV charging systems (provided through a variety of vendors)

6. Bike rental (provided through the City's current vendor)

7. Receive updated rates and hours from external management systems

8. Receive other inquiries from or make inquiries to external systems

9. Export revenue and other accounting data to City's accounting system

10. Export operational data and statistics to other systems

11. List the APls that already exist in the system, and separately list those that are already under development. Indicate how these APIs are accessed; e.g., through web services or another mechanism

12. Software:
• All required software shall be listed with the proposal. • All software must be provided with an Enterprise license under the City of Riverside's name.
• If there are ongoing service charges these must be identified in the proposal. The cost of the first year is to be included in the base pricing. Identify the cost for five years beyond the first year (years 2-6).
• Software upgrades during the warranty period shall be included in the pricing.

Future upgrades of software must be fully tested prior to installation and the City of Riverside shall not be the first installation of the software upgrade. The upgrade shall not be mandated but coordinated with the City of Riverside prior to installation.

A full description of the upgrade and its impacts on the City of Riverside's entire PARCS shall be provided to the City of Riverside for review and agreement prior to installation.

Please describe in your proposal how upgrades, patches and other minor modifications are handled beyond the warranty period.
• Vendor shall provide City of Riverside advance notification of access to the PARCS for updates to the PARCS, including: upgrades, troubleshooting, patching, etc., of software and/or hardware. All upgrades that will affect functionality of the PARCS are to be done at night/off hours at the discretion of the City. • All software on all workstations necessary to run the PARCS shall be included as part of the PARCS and shall be maintained and upgraded as part of the PARCS including all operating systems, anti-virus software etc. This shall be a turnkey solution and shall not rely on the City of Riverside to upgrade any software separately from the maintenance provided by this PARCS to keep the PARCS operating as specified. • All software must be in English at all levels of City of Riverside interface.

13. Electrical:

All electrical shall be clearly labeled at both ends of the conduit run. All network cables numbered. Numbers installed within 1" of termination on both ends of run. All low voltage and line voltage connections, including all pull boxes clearly marked with what oanel, what breaker number or port number they originate from.

If required, all existing bollards shall be removed and replaced as part of the installation.

Vendor shall demo existing concrete curb islands and replace with new concrete curb islands for a finished look.

All equipment shall be provided with UPS backup for 30 min with an alternate for 60 min backup. Vendor to propose a plan for the number and location of UPS devices to serve the PARCS.

Existing power feeds to locations may be used; however, if any devices need additional power run to them the PARCS Vendor will be responsible for running all power lines from identified junction boxes, panels, and load centers to the equipment to provide sufficient power to maintain a fully functional PARCS. The vendor is responsible for any additional surface mounted conduit that is necessary for the PARCS.

The PARCS shall be fully expandable, able to accommodate the addition of equipment, controls, and management. The PARCS shall be designed to expand up to an additional 10 lanes.
e. Central Control
The City prefers a "cloud" or remotely hosted solution but may consider a solution that requires in-house servers if a vendor can demonstrate that such a system can provide better value within the other requirements:

1. Fault tolerance, redundancy

2. Firewall protection

3. Service Level Agreements

4. Data backups

5. Time synchronization among all devices

6. Immediate data updates to all field devices; e.g., purchase of a monthly card should immediately make that card valid in the facility(ies) for which it was purchased, not requiring the customer to wait until the next "batch update"

7. System must conform to City Security requirements.
f. "Hosted" or "Cloud" Solution:

1. Documented Physical Security of the hosting data center. Include security provisions for staff, as well as facilities.

2. Documented electronic security of the hosting data center. Include external and internal provisions.

3. Documented mechanisms used to ensure protection of City data, passwords, etc.

4. Documented backup and recovery strategy and a disaster recovery or business resumption strategy.

5. Ability to provide City with all City data in easily usable electronic form at regular

6. Ability to establish interfaces between other City applications and this hosted product so that data can flow in both directions.

7. Required that hardware environment yields 99.99% uptime, exclusive of planned maintenance windows.

8. Documented procedure to provide notification to City for downtime in advance if planned and immediately if unplanned.

9. Provision of secure network connection between City users and host site via industry standard techniques.

10. Ability to restore entire environment within contracted durations.

11. Provide procedures for monitoring of system operation to detect hung processes or inactive sessions and act.

12. Provide redundancy in network and hardware environments.

13. Provide ability for users to run reports during all hours without impacting system performance

14. Provide security so that the City's data is available only to authorized users.

15. Proof of ability to accommodate growth in City's requirements.

16. Describe the provision of notification and appropriate City testing of software updates and security patches.

17. Indicate whether any City data will be transmitted outside of the United States, and if so, the countrylies) to which it will be transmitted, how it will be secured and managed, and who will have access to it.

18. If you do not expect to propose a cloud-based system, or plan to propose both solutions, the following items are required:

19. List IT component which the City will be required to maintain.

20. Provide server configuration(s), databases, required third-party hardware and software packages, etc.

21. Provide list of supported virtual servers (i.e. VMware)?

22. Provide description of the server maintenance requirements.

23. Provide description the database (vendor, version, add-on packages).

24. Provide description of how updates to the servers, the database, and the PARCS suite of software will be managed.

25. Provide descriptions of how IT administrators will be alerted to abnormal conditions in the system that requires attention.
g. User Access

1. Accessible through multiple browsers and versions.

2. Accessible by PC, mobile, and tablet.

3. Must not require external "plug-ins" or run time environments (such as Citrix, Java, etc.).
h. Rate management
Dynamic rates—allow rates in a facility or group of facilities to vary, using formulae based on time of entry or exit, facility occupancy, events in progress, etc.

i. Event Pricing
Ability to change any of the above immediately, at scheduled times, or based on events (if/then logic)
j. Complete Audits

1. "What if" scenarios to predict effect of rate changes

2. Explain how overnight or multi-day parking is processed for fees.

3. Monitoring and fault reporting

4. Logging of all exception conditions

5. Configurable alarms and alerting based on exception

6. Voice calls

7. Email

8. SMS
k. Customer/user account management

1. The PARCS shall have a distinction between a customer account and the credential that represents that account. For example, an account may be represented by a proximity card, a vehicle's license plate.

2. The account management system shall allow an unlimited number of groups or categories for customers and an unlimited number of accounts within each group.

3. The account management system shall provide for expiration of an account for unpaid fees, and/or imposition of late fee at user-programmable intervals.

4. User groups and individuals within the user groups shall each assign access privileges based upon facility (ies), date, day of week, time of day, or any combination thereof.

For example, it shall be possible to set an account's access privileges to allow access to a specific facility to be valid only Monday - Friday from 8:00 am - 5:00 pm, while a different user may have access to three facilities 24x7 but the other two may be accessed only during City business hours. It shall also be possible to modify user groups or individual accounts to be exempt from anti-passback rules.

5. The account management system shall provide full accounting functions including account generation, tracking, invoicing, and account payment collection.

6. Each account shall be designated for its type:
a. Contract Lease: a participant in a group for which an entity (such as an employer, organization, or service provider) has contracted with the City to provide parking under specific terms and conditions, at specific rates. The contracting entity shall have the ability to administer the individual users. b. Monthly Lease: an individual that purchases parking directly from the City for a month at a time, for one or more facilities
c. Pre-paid: an individual that purchases parking directly from the City and deposits funds in advance, to be deducted on usage
I. Others

1. The system shall provide capability to "migrate" current account user information from the old system to eliminate or reduce data entry (along with the credentials

for those accounts), and provide an "export" capability to share data with other systems in the future (such as creating mail merge lists)

2. An account shall be allowed to have more than one credential; e.g., it shall be valid for an account to have LPR and/or a proximity card. For facility access, all credentials are considered equivalent, such that entry via LPR shall cause the system to treat the account as if all credentials are in the facility.

3. The system shall have anti-passback capabilities that can be turned on or off for each user group/category, with the ability to override for a specific account, or a specific credential for the account. The system shall allow anti-passback to either deny the access or to log the access on the daily "exception transaction" report.

Anti-passback shall apply to an account, not the credentials (except when a specific credential has been exempted) and shall be enforced at the entry/exit gates.
m. Customer Credentials

1. The credential used to access a facility may be tied to an existing account within the PARCS, an account managed and maintained in an external system that communicates with the PARCS, or with no account (e.g., a transient user).

2. The acceptable credentials at any given time shall depend on the location, the program, and whether events are in progress.
n. Ticketless credentials

1. LPR, if customer has already registered with the system and chooses to use LPR.

Customers who choose this option shall be offered a backup credential, such as QR code on a wallet size printout or plastic card that can be scanned to enter and exit the facility A phone number or other self- selected number that can be entered on a keypad at entry and exit.

2. A transponder, such as AVI.

3. A bank credit/debit card (e.g., "credit card in/out").

4. Bar code or QR code printed on paper or plastic.

5. NFC on supported mobile devices (e.g., Android phones) o. Proximity cards
The system shall use commercially available RFID cards available through any source.

The Parking Division may issue a limited number of cards for specific uses, but in general, will prefer other forms of credentials.

1. All proximity cards shall have a mill thickness equal to that of a standard credit card

2. Cards may be issued by other parties (such as employee IDs) or specific customer groups

3. Ability to use customer's RFID-capable employee ID as an access card

4. Each proximity card shall have a unique ID that allows the card to be administered remotely; e.g., with the card number, a customer service rep should be able to access and change the account profile.

5. Each proximity card shall be associated with an account, whereby the account's profile controls the allowable use of the card.

6. The system shall provide the appropriate tools to program and administer proximity cards from any workstation that can access PARCS, assuming the user has the correct privileges.
p. Ticketed
If the system uses printed tickets, it shall be with QR codes, bar codes, or other mechanism for encoding information that can be photographed or otherwise viewed, not requiring physical contact (magnetic stripe tickets are undesirable because they must be passed over a reader/writer to process).

When a ticket is issued, it shall contain:

1. A unique serial number (system-wide, not just for the facility) for the transaction

2. Complete date and entry time

3. Facility code, lane number, equipment ID

4. The system shall have the capability to generate multi-use (limited duration or quantity) tickets

5. Ticket/Validations system should not allow re-use.

C. PARCS

1. ENTRY STATIONS
The entry stations are the customers' first experience within the facility, and therefore, they must provide a positive experience, allowing quick, trouble-free ingress. Entry gates shall have the following equipment and capabilities:

1. Barrier gates

2. Vehicle Detection Device

3. IP Intercom with camera

4. LPR

5. User interface

6. Cancel button that shall allow the customer to cancel at any point prior to opening the gate.

7. Re-programmable buttons, to allow customization of the user interface as needs dictate.

8. Color message screen that is easily readable in all ambient lighting conditions or with appropriate backlighting

9. Provides visual instructions for patrons to understand the sequence of events to complete a transaction

10. Issues audio voice instructions to complement the visual instructions

11. Push-button ticket issue (if applicable)

12. Please fully describe the entry gate's user interface, including illustrations or

13. Access doors) with appropriate tamper-resistant locking system (compatible with Medeco NexGen XT cylinders)
a. Vend Requirements

• Issues one credit card-sized, QR or barcode encoded or parking ticket for each transient entry transaction
• Shall be capable of reading a credit card-sized, QR or barcode encoded parking ticket (provided to customer prior to entry)
• Retractable ticket mechanism (if ticket not taken, ticket shall be retracted into the system, so it is not available for someone else
• Reader for an International Standards Organization (ISO) standard side-stripe magnetically encoded card such as a credit card
• Illuminated slot(s) for insertion of credit cards, tickets, etc. • QR/Bar-code scanner to read paper, plastic cards, or smartphone display • Unique machine identification number
• Stand-alone capabilities for each entry station in the event that network communication is lost, regardless of where on the network the communication interruption occurs
• Each Entry Station shall provide offline transaction storage capacity for all transactional information for a minimum of 2,000 transactions • Credit Card In functionality shall be disabled while in an off-line mode • The lane shall automatically close in the event that the offline transaction threshold is reached and shall remain closed until reestablishment of communications • Entry Station shall automatically upload all transaction information to the host/servers once communications are restored
• Proximity Card Reader with a minimum read range of six inches integrated into the face of the Entry Station
• Alarms for all exception conditions, including "Ticket stock low" and "Ticket stock out" alarms
• "Door open" alarm that is cancelled if the technician enters a security code or uses some other method to validate the entry, within a configurable number of seconds (defaulted to 15)
• Protected from vehicles by bollards
• Describe how your system provides a superb customer experience at the entry gates. • Express exit (unattended) stations

2. EXIT STATIONS - NON-ATTENDED
The exit stations are most customers' last experience within the facility, and therefore, they must provide a positive experience, allowing quick, trouble-free egress. Exit gates shall have the following equipment and capabilities with the thought that the preferred method is "ticketless":

1. User interface

2. Cancel button that shall allow the customer to cancel at any point prior to making payment

3. Re-programmable buttons, to allow customization of the user interface as needs dictate

4. Color message screen that is easily readable in all ambient lighting conditions or with appropriate backlighting

5. Provides visual instructions for patrons to understand the sequence of events to complete a transaction

6. Issues audio voice instructions to complement the visual instructions

7. Push-button receipt issue

8. Access door with appropriate tamper-resistant locking system (compatible with Medeco NexGen XT cylinders)

3. EXIT STATION-REQUIREMENTS
• Stand-alone capabilities for each exit station in the event that network communication is lost, regardless of where on the network the communication interruption occurs
• Exit station shall calculate the fee due based on information available at hand, such as on the ticket and any presented validations
• Each exit station shall provide offline transaction storage capacity for all transactional information, including storing encrypted credit card data, for a minimum of 2,000 transactions.
• The express exit station shall automatically upload all transaction information to the host/servers once communications are restored. The host shall validate each completed transaction; if any miscalculations occurred due to device or system communication issues, a report shall automatically be generated to alert staff.

Any credit card transactions shall be adjusted to the correct amount before authorization/settlement.
• In the event that the exit station's offline storage capacity is filled, and the device needs to shut down, all stored credit card information shall be permanently stored and accessible once the device is powered on
• In the event that a device is operating in off-line mode and on UPS power, the device shall permanently store all credit card information prior to shutting down in the event that the UPS battery power is depleted
• Exit Station shall alert nearby cashier/Call Center when the transaction storage threshold is nearing, allowing the cashier to prepare the lane for closure. If there are communications within the facility, the communications shall appear on the

cashier's POS device. If the device is not communicating, it shall sound a distinct audible alarm to alert the casher or Call Center.
• Proximity Card Reader with a minimum read range of six inches integrated into the face of the Exit Station
• Alarms for all exception conditions, including "Receipt stock low" and "Receipt stock out" alarms
• "Door open" alarm that is cancelled if the technician enters a security code or uses some other method to validate the entry, within a configurable number of seconds (defaulted to 15)
• Protected from vehicles by bollards
a. Exit Station Processing
• Shall be capable of reading a credit card-sized, QR or barcode encoded parking ticket or validation
• Illuminated slot
• Reader for an International Standards Organization (ISO) standard side-stripe magnetically encoded card such as a credit card
• EMV reader with ten-key pad for entry of PIN
• Illuminated slot(s) for insertion of credit cards, tickets, etc. • QR/bar code scanners to read from paper, plastic cards, or a smartphone display • Retractable ticket and receipt mechanisms should a customer not take a returned ticket or a printed receipt
• Fee determination
b. Exception handling - non attended station
• From nearby cashier station
• From a remote terminal.
• Reports for all exception transactions
• Unique machine identification number
c. Cashier stations (attended exits)
The cashier stations are some customers' last experience within the facility, and therefore, they must provide a positive experience, allowing quick, trouble-free egress, by providing the tools to assist customers in an efficient manner. During periods of operation where no cashier/attendant is available, the cashier station shall function as an express exit. Cashier stations shall have the following equipment and capabilities:

1. Barrier gates

2. Vehicle Detection Device

3. IP Intercom with camera

4. LPR

5. Shall switch to "unattended" operation similar to an express exit station when cashier is not logged into fee computer. The outside shall have the appropriate user interface to emulate an express exit.

6. A transaction panel shall be installed in the sidewall of the booth in a location that the patron in a vehicle is able to reach when booth is in non-attended mode.
a. The transaction panel shall operate and have the same capabilities and requirements as an express exit station.

Requirements:
• -Stand-alone capabilities for each cashier station if network communication is lost, and regardless of where on the network the communication interruption occurs
• Cashier station shall calculate the fee due based on information available at hand, such as on the ticket and any presented validations • Each cashier station shall provide offline transaction storage capacity for all transactional information, including storing encrypted credit card data, for a minimum of 2,000 transactions.
• The cashier station shall automatically upload all transaction information to the host/servers once communications is restored. The host shall validate each completed transaction; if any miscalculations occurred due to device or system communication issues, a report shall automatically be generated to alert staff. Any credit card transactions shall be adjusted to the correct amount before authorization/settlement.

If the cashier station's offline storage capacity is filled, and the device needs to shut down, all stored credit card information shall be permanently stored and accessible once the device is powered on
• If a device is operating in off-line mode and on UPS power, the device shall permanently store all credit card information prior to shutting down in the event that the UPS battery power is depleted
• The cashier station shall alert cashier when the transaction threshold is nearing allowing the cashier to prepare the lane for closure
• Cashier station can only process a transaction when a vehicle is present; e.g., a "walkup" transaction cannot be performed
• Protected from vehicles by bollards
d. User interface (customer) for attended mode
• A fee display that is easy to read, mounted on the exterior of the cashier booth, visible to a driver in a vehicle
• An EMV reader with ten-key pad for entry of PIN, within reach of the driver of a vehicle permitted within the facility
• Fee computer/POS (for cashier in the booth)
• Touch screen cashier monitor supplemented with standard QWERTY keyboard and mouse

• Dual cash drawer operation (allowing relief cashier to operate out of separate cash drawer) with removable, lockable inserts (compatible with Medeco NexGen XT cylinders)
• Drawers automatically opened for cash transactions only, after cashier has entered the amount tendered.
• Preset buttons/keys for most common transactions (configurable by City) • Shall be capable of reading a credit card-sized, QR or barcode encoded parking ticket or validation
• Fee determination
• QR/bar code scanners (inside and outside) to read from paper, plastic cards, or a smartphone display (e.g., when attended, the outside scanner shall be enabled to allow the customer to scan a smartphone display without requiring handing it to the cashier)
• Internal receipt printer to produce receipts upon request (only enabled in attended mode
• Tamper detection mechanisms on fee computer/POS
Exception handling - attended/non- attended Cashier Station

1. -From this cashier station

2. -From a remote terminal.

3. -Reports for all exception transactions

4. -Emergency alarm, to allow cashier to summon help
e. (Optional) Cashier Station CCTV-Audio/Visual Functionality CCTV cameras and microphones installed within each cashier booth to capture interaction between the cashier and the patrons or to capture the interaction of the patron to the lane equipment when the lane is operating in an unmanned mode.

These interactions shall have the following:

1. The image and audio shall be tied to each transaction

2. The CCTV system shall also have one pan/tilt/zoom camera located at the entrance to each lane to capture every transaction that shall also be tied to each transaction

3. All cameras and audio shall be synchronized, record each transaction, and be associated with each transaction

4. The CCTV-Audio/Visual shall exist as one integrated system and not separate subsystem components

5. The CCTV-Audio/Visual shall store data for a minimum of fourteen (14) calendar days online and archive an additional thirty (30) days

6. Describe how your system provides a superb customer experience at the cashier stations, both in attended and unattended modes. f. Automated/POF (pay-on-foot) stations
The pay-on-foot stations are some customers' next-to-last experience within a facility, and therefore, they must provide a positive experience, allowing quick, trouble-free payment. Pay-on-foot stations shall have the following equipment and capabilities:

1. IP Intercom with camera

2. Access doors) with appropriate tamper-resistant locking system (compatible with Medeco NexGen XT cylinders)

3. User interface

4. Cancel button that shall allow the customer to cancel at any point prior to making payment.

5. Re-programmable buttons, to allow customization of the user interface as needs dictate.

6. Selectable language

7. Color message screen that is easily readable in all ambient lighting conditions or with appropriate backlighting

8. Screen text that is customizable/configurable by Parking Services

9. Keypad or touchscreen to allow entry of LICENSE PLATE NUMBER, phone number, or other parking credential

10. Provides visual instructions for patrons to understand the sequence of events to complete a transaction

11. Issues audio voice instructions to complement the visual instructions

12. Push-button receipt issue
Processing/Collection/Security Requirements for POF
• Shall be capable of reading a credit card-sized, QR or barcode encoded parking ticket or validation
• Illuminated slot
• Retractable ticket mechanism (should ticket not be taken within configurable time frame)
• QR/bar code scanners to read from paper, plastic cards, or a smartphone display
• EMV reader with ten-key pad for entry of PIN
• Fee determination
• Optional coin/note acceptors (only a subset of POFs will accept cash) • Accept US currency: $1/$5/$10/$20 bills
• Accept US currency: 5¢/10₫/25¢/$1 coin
• Accept Validations or validation chaser tickets
• Accept tokens
• Note and coin recycling
• Note and coin escrow
• Collections process
• Separate keys to remove vaults
• Separate keys to open vaults
• "Change low" and "Change out" alarms (for coins and bills) • Describe the collection/replenishment process
• Location to install a mobile payment provider's decal with NFC antenna and QR code
• Retractable receipt mechanism
• Unique machine identification number
• Alarms for all exception conditions, including "Receipt stock low" and "Receipt stock out" alarms

• "Door open" alarm that is cancelled if the technician enters a security code within 15 seconds
Exception processing -POF
• From nearby cashier station
• From remote terminal. Reports for all exception transactions • Stand-alone capabilities for each POF in the event that network communication is lost, regardless of where on the network the communication interruption occurs.
• POF shall calculate the fee due based on information available at hand, such as on the ticket and any presented validations
• Each POF shall provide offline transaction storage capacity for all transactional information, including storing encrypted credit card data, for a minimum of 2,000 transactions.
• POF shall automatically upload all transaction information to the host/servers once communications are restored. The host shall validate each completed transaction; if any miscalculations occurred due to device or system communication issues, a report shall automatically be generated to alert staff.

Any credit card transactions shall be adjusted to the correct amount before authorization/settlement.
• If the POF's offline storage capacity is filled, and the device needs to shut down, all stored credit card information shall be permanently stored and accessible once the device is powered on.
• If a device is operating in off-line mode and on UPS power, the device shall permanently store all credit card information prior to shutting down in the event that the UPS battery power is depleted.
• Grace time (for leaving facility after paying at POF) configurable by facility and time of day, with the ability to have additional grace time added (automatically) if a high volume of vehicles is leaving the facility • Logging of door opening/closing, collections, maintenance activities, including an alarm that is cancelled if the technician enters a security code or uses some other method to validate the entry, within a configurable number of seconds (defaulted to 15)
• Ability for people with various permits, especially monthly permits, to pay the monthly fee at a POF if not on recurring billing
g. Barrier Gates
Basic Requirements:

1. Direct drive mechanism

2. Padded arm to prevent damage to objects that may be underneath when it lowers

3. Highly visible even in low- or no-light conditions

4. Non-resettable, mechanical gate action counter mounted in the barrier gate housing

5. Break-away design that can be easily and inexpensively repaired or replaced if broken

6. Gate arm length that can vary, depending on the facility

7. Single piece gate arm or articulated as required by height limitations

8. Barrier gates shall have enough power/resistance to ensure they cannot manually be forced open

9. Barrier gates, when closing, shall detect and reverse to the "up" position if an object is struck when descending

10. Barrier gates installed at the entry lanes shall remain in the closed position in an event there is a power failure and the UPS is no longer able to provide sufficient power to operate the lane

11. Barrier gates installed at the exit lanes shall have the option to fail to the open position or closed position in the event there is a power failure and the UPS is no longer able to provide sufficient power to operate the lane

12. Barrier gates shall provide a mechanical method to raise or lower a gate arm from within the locked housing, in case of power outage

13. Barrier gates shall provide a switch to raise or lower a gate arm, from within the locked housing. It shall be possible to disable the switch through software so that the switch is available only per management request.

14. Barrier gates shall activate an alarm if they are kept open for more than 30 seconds due to the presence of a vehicle that is permitted to enter or exit but hasn't moved.

15. Barrier gates shall activate an alarm if an attempt is made to raise them or lower them manually; e.g., someone attempts to force the gate into the opposite position.

16. Barrier gate housings shall generate an alarm if opened, but shall be cancelled if the technician enters a security code or uses some other method to validate the entry, within a configurable number of seconds (defaulted to 15)

17. Protected from vehicles by bollards
h. Barrier Gate Lane Controls (Dual Use Lanes)
Some facilities have entry gates adjacent to exit gates.

To better manage traffic flow during high volume times, such as events, the PARCS shall allow the capability to change certain lanes from entry to exit or vice versa. i. Entry and Exit Lane Vehicle Detection Device
Fast, accurate detection of a vehicle's presence in a lane, along with its direction, is critical to properly accounting for and protecting the revenue.

Requirements:

• The detectors shall detect the presence or movement of any vehicle that is legally permitted to be in the facility, including the direction • Entry lane vehicle detectors shall detect vehicular presence, legal entry, illegal exit, back-out, and clearing the barrier gates after entry • Exit lane vehicle detectors shall detect vehicular presence, legal exit, illegal exit, back-out, and clearing the barrier gates after exit • The detectors shall each incorporate a sensitive "tailgate recognition system" capable of resolving two vehicles within six inches of each other • The detectors shall automatically adjust their sensitivity, so they will properly recognize the presence and direction of any distinct vehicle that legally is permitted to access the facility (with height, width, weight, and number of wheels within limits) in a range of environmental conditions. j. Entry/Exit Lane Status Signs (Occupancy and PARCS signs) Normally show dynamic messages that are established by the Parking Division; examples include:
• Closed
• Cash only
• Credit/debit card only
• Express exit
• Lot full
• Prepaid only
• Monthly and prepaid only
Basic PARCS Sign Requirements

1. Shall allow multiple messages to be programmed, and messages shall rotate based on timelines established during programming.

2. Multi-color, with minimum of red/green

3. Easily readable in all ambient lighting conditions from 200 feet and a minimum viewing angle of 120 degrees

4. Signs shall be controlled automatically, based on rules established by Management; examples include:

5. When an entry lane in operation, the entry Lane Status Sign shall automatically be set to "OPEN"

6. When the facility occupancy exceeds a certain threshold, the entry Lane Status Sign shall automatically be set to "FULL: MONTHLY/PREPAID ONLY"

7. When an express exit station is out of operation or in maintenance mode, the Lane Status Sign shall be automatically set to "CLOSED"

8. When an exit station is attended, the Lane Status Sign shall automatically be set to "ALL TRANSACTIONS"

9. When an exit station is unattended, the Lane Status Sign shall automatically be set to "CREDIT/DEBIT/MOBILE PMT ONLY"

10. Supervisors shall be able to override the default messaging through an easy- to-use interface within the PARCS.

Basic Sign Requirements - External/Occupancy
• External signage/displays
• Programmable
• Default programming
• Availability (based on occupancy)
• Facility-wide
• Per level
• Hours of operation
• Rates
Basic Sign (Opfional) - External/Occupancy
• Informational messages ("Open 24 hours," "Monthly Parkers Only," "Closes at Midnight," "Early Bird until 9 am," "Prepayment required," "Prepaid Only," "Event Parking 5-10 pm," etc.) based on schedule, occupancy, or other criteria • Override programming-ability for someone with appropriate privileges to create a special message, such as "Closed until 6 pm," "No validations accepted," "Happy Holidays," etc.
• Shall allow multiple messages to be programmed, to rotate at timeframes established during programming.
k. Uninterruptible Power Supplies
Conditioned/emergency power for all components (lanes, facility controllers, signs, LPR units) for all facilities to protect components from loss of power, power spikes, and power sags, as defined as necessary by the CBEMA
UPS battery back-up for all equipment shall provide power for at least two hours.

A single UPS unit, appropriately sized, shall support all devices at an individual entry lane or exit lane except for cashier booth HVAC units. UPS units that supply conditioned and back-up power to multiple components in a single lane are required to minimize maintenance.

All UPS units shall allow automated notification to the host/servers when battery power is activated, or the battery levels become critically low. On-line communication using an appropriate UPS monitoring software application shall be provided on one or more

workstations with user selectable options to view the status of each individual installed UPS unit. At a minimum, the monitoring software shall display the operational status of each UPS unit (line/battery, online/offline) and generate alarms in the event the UPS unit's battery power is activated, becomes low or is completely exhausted.

4. Operational Requirements and Procedures:
a. Administrative Access
Preferred method for Administrative Access should be through a standard web browser (including mobile devices), without any special plug-ins or other software have a majority of the following:
• Flexible user access rights/permissions based on roles and facilities/accounts • The City expects a PARCS that allows customers and merchants to perform many transactions without staff intervention.
• Monthly access permits
• Purchased by individuals to have flat-rate parking at specific facilities, at rates established by facility operators.
• Purchased on-line or at a POF
• Allow customer to choose LPR as primary credential when entering facility; generate backup QR/barcode for wallet or mobile device
• Global vs facility-specific vs multi-facility vs facility-group specific, with varying rates
• Pro-rated pricing for first month
• Monthly auto-payment through credit card, EFT, etc.
• Allow payment at POF
• Automatic account blocking if charge not posted by nth day of the month • Off-peak vs on-peak pricing
• Contract access permits
• Arranged by contract between an entity (such as an employer or social organization) for parking with different pricing plans (flat rate for the entity, flat rate per individual account, various discounted rates, etc.). • Contracted entity shall have ability to log in to an administrator's panel to manage the individual accounts that are part of the contract • Permit request is "pending" until reviewed and approved:
• By contract administrator
• By facility operator
• By Parking Division
• Example: ability if a contract is with a company that pays for 40 spaces in a facility, a representative of that company should be able to log into

the system with a role that allows only management of that company's permits, including approvals of permit requests, issuing permits, revoking permits, etc.
• Monthly auto-payment through credit card, EFT, etc.
• Monthly invoicing
• Multi-day/multi-use permits
• Facility establishes price, duration, # entries/exits, etc. • Event prepayment/reservations
• Customer chooses event and pricing tier
• Require customer to upload facsimile of vehicle registration; permit request is "pending", and card is not charged until vehicle registration has been reviewed and approved
• Requires use of LPR for credential (so customer cannot use account with another vehicle
• Access with credential is logged with vehicle plate for reporting • Automatic generation of monthly invoices based on flat rate plus per vehicle rate (including any on-peak premium fees)
• Frequent parker/loyalty programs
• Allows customer to maintain an account for automatic billing for each parking transaction (at the transient rate)
• Customer maintains account information online, including name, address, credit card info, email address (es), license plate number(s) • Ability for City to offer discounted parking or special programs or other promotions
• Marketing opportunities through mail/email solicitations • If customer has multiple vehicles, any/all can be selected for LPR entry/exit b. Merchant Validations
Validations
All transient parking transactions shall allow for use of a validation, although the types of validations that may be permitted for a given transaction may be limited.

All facilities shall be capable of accepting/processing validations, but the City shall have the ability to set rules for acceptance of specific validations, including which facilities will accept a given validation and whether a given validation can be used in conjunction with other validations
Prior to applying payment, the validation shall be applied to the fee and the adjusted amount shall be displayed to the customer
Validation options shall include, but not be limited to:

• A specific dollar amount (e.g., $5 off the parking price) • A percentage amount (e.g., 15% off the parking price) • A specific duration (e.g., two hours free; for a facility where the rate per hour may vary depending on length of stay, Parking Services will determine which hours will be discounted)
• A fixed cost for the parking session, regardless of length of stay (including a cost of $0) • Any given vehicle may be limited on the number of validations that can be used per day, to be enforced by LPR (unless a specific validation is programmed as allowed in addition to other validations, to be set by Parking Services only) The PARCS shall allow Parking Division to restrict the number of minutes a validation must be used after it is issued; for example, a validation issued by a merchant in a high-traffic shopping area may expire 180 minutes after it is issued.

1. The system shall allow merchants to register online to set up a validation account with a credit/debit card.

A merchant registration shall be "pending" until the Parking Division reviews and approves the application.

3. An approved merchant shall be able to purchase validations online. The cost per validation, the discount per validation, and any other validations shall be established by Parking Division when the merchant is approved (with the ability for Parking Division to modify at any time).

The validation medium shall be selectable by the merchant. Options are:
• The ability for a merchant to print a validation from a compatible device (such as a POS, computer with printer, stand-alone printing device, etc.) that can receive the validation parameters (such as a QR code image) from the PARCS • The ability for a merchant to use a web page from a computer or handheld device, or to use an app on a handheld device, to enter a PARCS ticket number, vehicle license plate number, or other credential used by the customer upon entry to a facility
• The ability for a merchant to stamp or print a unique, tracked validation on an entry ticket in the customer's possession, perhaps by using an encoding machine
• The ability for a merchant to swipe or enter the credit card the customer intends to use for payment at the parking facility and transmit that to the PARCS (from the merchant's POS system, credit card terminal, or through a web page or handheld app
• Merchants shall be allowed, with Parking Division's approval, to use more than one validation medium
• Validations shall be unique, so that a single validation cannot be used more than once
The Parking Division shall have the ability to establish limits on:

• the number of validations that may be purchased by an individual merchant for a given timeframe,
• the number of validations that may be purchased for a specific facility, • the facilities for which a merchant can purchase validations, • the number of unused validations a merchant may have on hand, and • the expiration dates for validations (e.g., a validation must be used within 90 days of the time the merchant purchases it).

Limitations (Merchant Validations):
• A merchant shall be able to participate in more than one validation program, with each program having its own rules and parameters (but only one validation shall apply to any vehicle on any given day
• A merchant shall be able to assign "issuer IDs" to its personnel or representatives who will be providing the validations to customers • A merchant shall be able to review the status of its account, including the individual validations that were used, along with issuer IDs • After issuance, Parking Services shall have the ability to void a validation unless it has been redeemed
c. Premium parking (Nested- Garage 3)
• Areas set aside within the facilities ("nested area") with separate entry/exit gates, requiring a pre-authorized credential for access; e.g. "event premium parking," employee parking, loading docks, etc.
• May require surcharge or premium pricing to access
• If applicable, System guides premium customer to area based on LPR captured at entry
• The system shall incorporate compound anti-passback functionality to contro nested areas within the parking facilities; i.e., if an account or pass is configured, the system shall enforce "in-in-out-out" credential usage into the nested area(s).
• There shall be a configurable amount of time that once a credential has been used to get inside a parking facility, the user must enter the nested area. Should the configurable amount of time be exceeded before the patron enters the nested area, then the system shall allow the option to invoke one or any combination of the following:
• Deny access to the nest
• Allow access to the nested area, but generate an alarm for the event within the PARCS
• Apply a time-dependent parking rate to the transaction (standard of special parking rate that must be satisfied at a public exit lane before exit is permitted

• Possibly combined with loyalty program and/or valet program d. IOU payments
• Used when customer cannot pay parking fee.
• Generated at Express Exits and Cashier stations, as described above. • System shall provide the ability to create using a handheld device • Parking Services shall determine the amount for a processing fee to be applied to all IOUs, in addition to the fee owed
• Data collected shall include:
• Vehicle license number and state
• Vehicle make
• Vehicle color
• Vehicle body style (2 dr, 4 dr, truck, wagon, etc.)
• Vehicle VIN (optional unless no license plate)
• Driver's license number and state
• Facility ID
• Parking account/card/credential ID (optional)
• Parking fee owed
• Driver's name
• Driver's address
• Issuer's ID/name
• Date and time
• A generated OU shall print a receipt with instructions for payment • A generated IOU shall print an acknowledgment for the customer to sign and return to the cashier (when using an attended exit) • The online self-service system shall allow for IOU payment • Each day, the system shall generate a report of all IOUs over seven days in age, so a citation can be generated for each one
REQUIREMENTS:
• A customer who received an IOU due to inability to pay at the time of exiting a facility shall be able to make payment within seven calendar days of the time the IOU is issued.
• Web browser or POF
• Customer enters IOU number, LICENSE PLATE NUMBER, or other transaction identifier
• Charges customer amount due, including processing fee • Service only available for seven days; once IOU has been sent to a citation, payment through the PARCS no longer is available

e. Fee lookup: ability for a customer to determine fees A customer shall be able to get a calculation for the amount s/he will pay for the current session. Validations are not considered in this calculation. • Web browser and/or handheld device app
• Customer enters credential and planned departure time • System provides predicted cost and any variables
f. Transaction requirements/rules
The PARCS shall be capable of processing transactions and determining fees under a variety of scenarios. Listed below are the most common types of transactions within the City of Riverside facilities. Vendors are encouraged to describe other transaction scenarios within their PARCS' capabilities.
• Entry into facilities, non-event
• Lane detection device determines presence of a vehicle • License plate captured by LPR (if applicable)
• If plate is on a permit list, and no other credentials associated with that plate on the permit list are already in a facility (unless the permit allows), an entry transaction is generated, and barrier gate opens
• The entry station shall be activated
• The display shall show, and an audible voice shall announce instructions Customer inserts/swipes credit card, presses button for ticket, scans QR code/bar code on printed material and/or handheld device display, uses proximity card, or other method
• Credit/debit cards for "credit card in"
Must be validated
Returned to customer (if card pulled into slot); if customer does not take card, after configurable timeout, intercom is engaged to aid • If card is not validated or is on hot list, customer is informed the card is not valid for entry and customer may attempt a different credential Card added to "present in facility" list; cannot be used in another facility g. Tickets (Issue Process)
Issued after customer presses button:
• If ticket not pulled from spitter and vehicle reverses, then transaction shall be voided, and ticket retracted into entry station, and LICENSE PLATE NUMBER shall be added to gray list
• QR code/bar code, proximity card, AVI/transponder, another identifying credential

• Must be validated or present in a list of prepayments for the specific facility • If not validated, customer is informed the item is not valid for entry (or for the specific vehicle, if the card is restricted) and customer may attempt a different credential
• If account is already present in any facility, then the customer shall be so informed, and customer may attempt a different credential (unless account allows multiple • After credential is validated or customer chooses a ticket, an entry transaction shall be created and LPR shall be associated with it
• Barrier gate is opened, but if a ticket is issued, not until the ticket is taken from the entry device
• When vehicle clears interior lane detection device
• Barrier gate closes
• Facility vehicle count increments by one
• Level vehicle count increments by one
• Lane resets and prepares for next transaction
• If vehicle reverses instead of proceeding into facility • Barrier gate shall close
• Entry transaction shall be marked as voided
• Ticket shall be voided so it cannot be used by another party to exit • LICENSE PLATE NUMBER added to gray list as stolen ticket • Entry to facilities, event
• To provide a better flow of vehicles both in and out of a facility before and after an event, the system shall provide the ability to define an "event." EVENTS:

REQUIREMENTS:
• Beginning time for event entry
• End time for event entry
• Event flat rate
• Event end time
• Grace time after which a transient transaction will be priced at the event rate • Which discounts and coupons will be accepted/honored
PROPERTIES:
• At the beginning time for the event, the entry lanes shall convert to attended "pre- pay" mode

• Entry stations will be attended; attendants will have change banks and handheld devices. The handheld devices shall:
• Incorporate a credit card reader capable of processing EMV cards when required)
• Be capable of printing receipts (the receipt printer may be a separate device with a wireless connection to the handheld device
• Connect wirelessly to the PARCS such that it is another transaction terminal and can send/receive all necessary data for creating and/or updating transactions • Inform the attendant about the facility status, such as "Prepaid only," "Facility full," etc.
• Provide the attendant with a "quick reference" for information about the event, such as where to go after parking, the time the event ends, etc. • After attendant is ready to process event payments and has logged into the handheld device, the entry gate for the lane shall have the options to open/close on each transaction and/or remain open so that vehicles can proceed directly into facility as soon as the attendant has taken payment and issued receipt. • When the attendant logs out of the handheld device, or when the handheld device leaves the facility entrance area, the gate for the assigned lane shall close. • Various types of permits and/or validations may not be valid during event pricing. • Non-event processing may be valid for a customer who arrives without expecting event pricing; customer will inform attendant, who will direct customer to standard entry station. Should the customer stay beyond a configured duration, event pricing shall be charged at exit.

EVENT PROCESSING:

1. Facility entry signs shall alert customers to event price and hours, along with facility vacancy information

2. LPR shall transmit captured LICENSE PLATE NUMBER to attendant's handheld for validation

3. As each vehicle reaches attendant, attendant will process transaction:

4. A customer with a prepayment credential will be entered or scanned by the attendant into the handheld, which shall validate the credential. If the credential is valid, the customer will be admitted into the facility with no further interaction.

If the credential is not valid, then the customer shall pay with another method, or shall be given a transient ticket and sent to the exit gate (where exit within the grace period shall not result in a charge

5. A customer may pay by cash or credit card. Attendant will record payment using the handheld; the entry transaction shall be created with LICENSE PLATE NUMBER as credential

6. The system shall allow attendant to initiate a transient transaction, if permitted by management, using LPR as the credential, or attendant may tap a button on handheld to request ticket from entry station.

7. Receipt shall be issued if requested by customer.

8. Attendant will allow customer to enter. The LPR for the vehicle shall be recorded and associated with the transaction to allow event exit and/or validate the transient ticket.

Express exit from facilifies

1. Message signs above each lane shall display information to drivers to guide them to the correct lane(s) for exit

2. When a vehicle is detected in the exit lane, the LPR system shall capture the license plate and attempt to match it with a transaction. If the LICENSE PLATE NUMBER is associated with a valid pre-paid or permit transaction (including pre- paid at a POF), the system shall close the transaction, remove the LICENSE PLATE NUMBER from the active inventory, open the exit gate barriers, and decrement by one the facility and level vehicle counts.

3. The exit station shall be activated; the display shall show, and an audible voice shall announce instructions

4. Customer inserts ticket, inserts/swipes credit card, scans QR code/bar code on printed material and/or handheld device display, enters/displays/swipes/waves another credential, or has AVI or other transponder
Credit/debit card (CCI/CCO; Credit Card In/Credit Card Out)

1. Customer inserts or swipes card used for admission into facility

2. LPR data shall be compared to entry transaction; if not a match, then intercom shall be activated automatically

3. Fee shall be calculated and displayed to customer

4. Customer shall be given an opportunity to present validation or coupons

5. Card shall be authorized for transaction

6. Customer shall be offered a receipt

7. Card is returned to customer, if needed; if customer does not take card, after configurable timeout, intercom shall be engaged to aid

8. Card shall be removed from "present in facility" list and now can be used in another facility

9. Barrier gate shall open

10. The LICENSE PLATE NUMBER shall be removed from the active inventory

11. Facility and level vehicle counts shall decrement by one Ticket Processing-with LPR

1. Customer inserts into ticket slot

2. LPR data shall be compared to entry transaction; if not a match, then intercom shall be activated automatically

3. If payment has already been made at a POF, then the barrier shall open.

4. The LICENSE PLATE NUMBER shall be removed from the active inventory

5. Facility and level vehicle counts shall decrement by one

6. Fee shall be calculated and displayed to customer

7. Customer shall be given an opportunity to present validation or coupons

8. Customer presents payment

9. Customer shall be offered a receipt

10. Once payment completed, barrier gate shall open

11. The LICENSE PLATE NUMBER shall be removed from the active inventory

12. Facility and level vehicle counts shall decrement by one

13. QR code/bar code, proximity card, AVI/transponder, etc.

14. Customer presents credential

15. LPR data shall be compared to entry transaction; if not a match, then intercom activated automatically for an operator to assess and determine whether to convert to a fee-based transaction or take other action Exception situations- Ticket Processing with LPR:

1. If LPR data does not match that recorded with the credential, the intercom shall be automatically engaged. All known details about the transaction and the LPR data on file will be presented to the operator.

2. Parking Division shall have the ability to disable automatic intercom engagement and permit the transaction to proceed, on a facility-by-facility basis.

3. Please describe the options your system offers for handling the situation where the LPR does not match, including whether the system's confidence in the OCR of the plate is considered in the decision.

4. If credit/debit card is not authorized, the exit station shall inform the driver, and suggest trying a different card or payment method, or use of the intercom to get assistance.

5. If the vehicle approaches the exit within the grace period (for leaving a facility after entry) and is recognized by the LPR, the gate shall open and allow the vehicle to exit. Facility and level vehicle counts shall be updated, the transaction shall be closed, and the LPR data shall be removed from the active inventory

6. If a patron has lost his/her credential (or the credential is unreadable), s/he will use the intercom to request help. The system shall attempt to find the entry transaction based on the vehicle LPR data, including use of partial matches. If no candidates are found, the operator shall obtain an approximate entry time from the patron, then s/he shall review entry records with pictures from that timeframe to find the

entry transaction. The transaction information shall be sent to the exit station from which the intercom call was received to allow the customer to complete the transaction.

7. The system shall detect an attempt to exit with a swapped ticket, based on LPR data. The information shall be sent to an operator with simultaneous activation of the intercom, and "processing... please wait" shall be displayed on the exit station. The operator will review the information, consider the customer's input, and make a determination which rate should be charged. The modified transaction information will be transmitted to the exit station and the transaction will be completed there.

8. The system shall detect an attempt to exit with a stolen ticket, based on the encoded ticket or LPR data. The information shall be sent to an operator with simultaneous activation of the intercom, and "Activating intercom... please wait" shall be displayed on the exit station. The operator will review the information and modify the transaction to reflect the actual entry time of the vehicle. The transaction information will be transmitted to the exit station and the transaction will be completed there.

9. If LPR determines the vehicle entered at an event rate but the vehicle remained in the facility after the grace period for the event, the exit station shall calculate the additional fee due, and process similarly to a "lost ticket" transaction, except there will be no automatic intercom call.

10. If the customer does not have the ability to pay for the parking session (e.g., no credit/debit cards, no cash or it cannot be used [cashier booth unattended and POF unavailable], etc.), the customer will use the intercom. The operator shall be presented with the data the system has on file, including LPR, credential data, etc.

The operator shall create an "IOU." As part of the IOU process, the operator will have the customer hold a driver's license to the camera and the image shall be recorded and saved with the transaction, along with a photo of the driver and the LPR images. The system shall use OCR to capture the data on the driver's license data and prefill an IOU form for the operator to review and complete. The form shall have additional fields, such as phone number and operator note.

Cashiered exit from facilities (free-standing Pay-in-Lane or Booth mounted unif) • All transactions processed at a cashiered exit lane in unattended mode shall follow the same procedures as those for transactions at an Exit Station described above.
• The cashier drawer shall only open for those transactions where payment is made in cash, after the cashier has entered the amount tendered (and barrier gate shall not open until the drawer has been closed), or the cashier is required to "drop" the excess money into the safe. Cashier drawers shall incorporate a slot for the insertion of checks and signed credit card slips without opening the drawer. For all other transactions, the cashier drawer shall remain closed. • Message signs above the lane shall display the lane's status to drivers.

• When a vehicle is detected in the exit lane, the LPR system shall capture the license plate and attempt to match it with a transaction. If the LICENSE PLATE NUMBER is associated with a valid pre-paid or permit transaction, the system shall close the transaction, remove the LICENSE PLATE NUMBER from the active inventory, open the exit gate barriers, and decrement by one the facility and level vehicle counts.
• The cashier station shall display the transaction details as determined by the LPR. • The customer will hand the credential (ticket, credit card, QR code/bar code on printed material or handheld device display, etc.) to cashier. Customer shall have option to self-scan printed material or handheld display using the scanner on the exterior transaction panel.
• Attendant inserts ticket, scans material, etc.
• The cashier station shall calculate the fee and display it to the attendant and on the external customer display.
• The cashier will take customer's validation, if available, and insert/scan it as appropriate (or allow self-scanning using the exterior transaction panel) • The cashier will take payment from customer and offer a receipt • The casher will have the customer sign the credit card slip (if the transaction warrants it, based on business rules configured into the system or makes change • Once payment is completed, the barrier gate shall open • The system shall remove the LICENSE PLATE NUMBER from the active inventory • The facility and level vehicle counts shall decrement by one Exception Situations- Cashiered Exit:

1. If LPR data does not match that recorded with the credential, the attendant will be notified. All known details about the transaction and the LPR data on file will be presented to the attendant.

2. If credit/debit card is not authorized, the cashier will be notified, allowing driver to present another form of payment.

3. If the vehicle approaches the exit within the grace period and is recognized by the LPR, the attendant will be notified, the gate shall open and allow the vehicle to exit. Facility and level vehicle counts shall be updated and the LPR data shall be removed from the active inventory.

4. If a patron has lost his/her credential (or the credential is unreadable), the system shall attempt to find the entry transaction based on the vehicle LPR data, including use of partial matches. If no candidates are found, the attendant shall obtain an approximate entry time from the patron, then s/he shall review entry records from that timeframe to find the entry transaction. Once found, the transaction will complete as if the ticket/credential were present.

5. The system shall detect an attempt to exit with a swapped ticket, based on LPR data. The attendant will review the information, consider the customer's input, and make a determination which rate should be charged.

6. The system shall detect an attempt to exit with a stolen ticket, based on the encoded ticket or LPR data. The information shall be displayed to the attendant, who will review and process the ticket as if it were valid.

7. If LPR determines the vehicle entered at an event rate but the vehicle remained in the facility after the grace period for the event, the cashier station will calculate the additional fee due, and process similarly to a "lost ticket" transaction.

8. If the customer does not have the ability to pay for the parking session (e.g., no credit/debit cards, no cash, etc.), the attendant will use the IOU button. The attendant shall be presented with the data the system has on file, including LPR, credential data, etc. The attendant shall obtain the information from the customer's driver's license ideally, with the ability to capture an image of the license, to be recorded and saved with the transaction), along with a photo of the driver (taken by the outside camera) and the LPR images.

9. Can your system take a picture or scan of the driver's license when processing an IOU?
SYSTEM ADDITIONS and ENHANCEMENTS
h. Carpool Parking
• The system shall allow assignment of an unlimited number of accounts to a specific car pool. Once any one account in the pool has gained entry to any facility, then no other accounts assigned to that car pool can be used at the car pool rate. • The car pool credential shall be separate, such that a customer who has a regular account may also be a member of a car pool and cannot enter the facility as the car pool driver inadvertently.
• The system shall have the ability to set a limit on the number of car pool entries in any facility. Once that number has been reached, no further car pool entries shall be permitted until a car pool has exited.
• The system shall have the ability to set a limit on the number of car pool entries across all facilities or a group of facilities. This number may be lower than the sum of the car pool limits in all facilities (e.g., five facilities may each have a limit of 25 vehicles, but the limit for the entire group may be 100). Once that number has been reached, no further car pool entries will be permitted until a car pool has exited.
• The system shall have the ability to set discounted or free parking for a session initiated as a car pool entry.
• Explain any provisions in the PARCS to validate that a vehicle entering using a car pool discount has the minimum number of passengers to qualify for car pool • Describe any other car pool processing available in your PARCS.

i. Early Bird Parking
• The system shall have the ability to define, per facility or group of facilities, an "early bird" rate that is charged if the customer arrives within a time frame, and optionally, departs before or after a later time. Examples:
• Arrive between 6 am and 9 am
• Arrive between 7 am and 8 am, and depart before 5 pm
• Arrive between 4 am and 7 am, and depart after 6 pm
• Arrive between 6 am and 7 am, and depart between 4 pm and 7 pm • Parking Division shall have the ability to configure whether a validation can be applied to an early bird rate.
j. Reservations and Prepayment
• Customers shall be able to make a prepayment, either through the PARCS self- service module, or through a third-party that provides the payment information to the PARCS through an API.
• The customer shall be provided proof of the prepayment through multiple media, including
• A confirmation number that can be entered by an attendant into the handheld device
• A QR/bar code that can be scanned, either on paper or a mobile device screen • Another credential on a mobile device "app"
• Registration of a vehicle's LICENSE PLATE NUMBER
• Payment shall constitute a reservation. The PARCS shall allow various types of reservations, such as "general," "preferred parking," "valet" (if enabled for the event), etc.
• The PARCS shall allow a customer to purchase any quantity of prepayments. For example, a wedding party may wish to purchase prepaid/reserved parking for its guests.
• Parking Division shall have the ability to establish limits for each type of reservation. • Parking Division shall have the ability to establish "overbooking" thresholds, to account for patrons who prepay but do not show.
• The reservations and overbooking threshold shall be considered by the occupancy system calculations.
• Reservations may be for "general" parking, or for specific "nested" areas within a facility.
• Prepayment for event parking shall be allowed at any time prior to the point where event entry ends, unless the facility is already full.

k. Grace Periods
The system shall allow configurable grace periods for the following:
• Between entry with a transient ticket and arrival at the exit gates; for example, if a customer enters the facility and does not park. This shall be customizable per facility, and shall have overrides for time of day, facility occupancy, event in progress, etc.
• Between payment at a POF and exit from the facility, to allow a customer time to get to the vehicle and then proceed to the exit. This shall be customizable per facility, and shall have overrides for time of day, facility occupancy, event in progress, etc.
• Between the conclusion of an event and the exit from a facility, to give patrons time to return to their vehicles, but not to allow for additional parking, such as to go to dinner after an event. This shall be customizable per facility, and shall have overrides for time of day, facility occupancy, event in progress, etc. • Describe any other configurable grace periods supported by your PARCS.

I. Receipts
• Shall be optional at time of transaction, with configurable default per payment device/station
• System shall offer ability to generate a receipt after the fact • At any cashier station
• At any POF
• Via web/phone
• Receive by email (with ability to register card number[s] in advance) • Customer shall provide sufficient details to find unique transaction, such as • license plate and date (or range)
• credit card "first 6 + last 4" and date (or range)
• date and exit time, facility, lane, and amount and type of transaction • What other credentials can your PARCS use to find a transaction? • Only print last four numbers of credit cards
• Information to be printed on receipt shall include:
• Facility name and address
• Receipt #/Transaction #
• Time, date, and lane in
• Time, date, and lane out
• Type of credential
• LICENSE PLATE NUMBER
• Length of stay

Parking fee
Total amount
Method of payment
Amount paid
Change Due
Breakdown of charges by time and rate
Discounts applied
• Signature line
• Cashier ID#
• Receipt paper shall be off-the-shelf, not proprietary to vendor • Please provide sample receipts in the proposal.
m. Tickets/Entry Media (Description and Records of)

1. Tickets shall be off-the-shelf, not proprietary to vendor

2. The system shall maintain a digital archive of tickets (to avoid physical archive)

3. Tickets shall not require contact with PARCS components for processing.

Supervisor overrides

4. PARCS shall allow from any computer or POS as long as user is authenticated

5. There shall be an audit trail of all overrides

6. There shall be reports describing all overrides to allow management review after the fact
n. "Virtual Midnight"
The PARCS shall allow the City to establish "virtual midnight" for ending the day's credit/debit card processing on a facility-by-facility basis, based on the facility's characteristics, including operating hours, bank card merchant account, etc. o. Monitoring Features - Intercom/Cameras

1. The intercom shall consist of a microphone/speaker and a camera

2. Activation of the intercom shall initiate both two-way audio and one-way video (from the device to the answering point

3. The audio shall function as a full-duplex speakerphone, to allow two-way conversations between the customer at a facility and the person processing the call.

4. Intercom shall be activated by push button on front of unit.

5. Intercom shall allow activation by a remote station with an authorized user, to monitor and record all activity on any intercom device

6. Intercom shall allow automatic activation of the intercom during specific transactions, recording video, audio, or both as part of the transaction record

7. Intercom shall allow activation of the intercom continuously and recording video, audio, or both, to a medium such as a DVR

8. Intercom shall be fully integrated with entry/exit stations, cashier stations, pay-on- foot devices

9. Option for standalone intercom/camera devices in other areas, such as elevator lobbies

10. The intercom shall communicate over the TCP/IP networks already connected to the other PARCS equipment

11. The intercom shall have the ability to interface with Operator's system to add parties or transfer calls

12. The answering station shall be configurable by facility, sub-system, or across the system

13. Ad hoc changes for events, on a per-lane or per-facility basis

14. Can be directed to any IP-capable device (computer, tablet, smartphone) or group of devices

15. The system shall also allow the calls to be distributed between multiple operators, if the destination supports the functionality.

16. Ability to route the audio portion to any publicly dialable telephone and allow the user to access the "console" through a web browser

17. Ability to "conference" a third person accessible through a publicly dialable telephone.

18. Ability to define protocol for handling calls that aren't answered; e.g., if the primary answering point at a given time of day does not answer, the call should get redirected to a backup answering point, and the caller should be informed appropriately.

19. The answering device shall display to the operator the physical location of the calling device (type of device, lane identifier if applicable, and a small map to set context for the answering operator)

20. The operator's control panel shall display any information the PARCS has at that time regarding the transaction, such as the vehicle's license plate (the recognized LICENSE PLATE NUMBER along with the photo), the entry time, the calculated fee, any validation that has been presented, etc., credential presented for entry or exit, along with explanation if the PARCS has denied the entry or exit, to give the operator information that may assist in resolving the situation.

21. Once answered, two-way communication shall be possible, and the intercom line shall remain open until the operator terminates the call

22. If the answering device is on an intercom call and one or more additional calls arrive, the operator shall be able to put the current call "on hold" and take the additional call. The operator shall be able to switch between calls as needed.

23. Each device shall be able to place intercom calls independent of other devices; in other words, a call from one device shall not block other devices from making intercom calls, even devices in adjacent lanes in a facility.

24. The operator's control panel/app shall have a function to activate the barrier arm on gates.

25. The camera shall have sufficient resolution to allow an operator to read a ticket, validation, or customer's driver's license when held in front of the camera.

26. The operator's control panel shall allow the operator to create an IOU for the transaction, based on the information provided by the control panel and by the customer

27. Exception conditions requiring operation action/review shall automatically activate the intercom; e.g., LPR for exit does not match for entry, vehicle attempts to back up at entry after taking ticket, second vehicle attempts to use entry credential already in a facility (any facility), attempt to use more than one validation for the same vehicle in a day, etc.

28. The video and audio from each session shall be recorded digitally and the operator shall be offered the choice whether to save or delete the recording. The City shall be able to configure the system not to allow operators to delete session recordings, in which case the recording shall be routed to a supervisor for review before deletion.

29. The operator shall have the ability to make screen shots of the video portion and then save or send the screen shots to other parties.

5. LICENSE PLATE RECOGNITION (LPR)

1. An LPR system shall record and recognize all license plates as vehicles enter or leave the facility

2. The LPR system shall perform OCR on each license plate

3. The LPR subsystem shall be fully interfaced and integrated into the PARCS. This integration shall include linking the LICENSE PLATE NUMBER captured at entry to the unique transaction for every entry into a facility.

4. The LPR database shall be used to conduct automated searches and queries for special circumstances, such as outstanding balances, unresolved incidences, and prior entries with no exits, Gray/Black List, validation already used for that vehicle for the current day, and "currently in facility."

5. All license plates shall be checked against "hot lists" and once identified, a notification shall automatically be transmitted Parking Services' Enforcement Section, with the image, license plate number, times of entry and exit, and locations where the vehicle has entered and exited

6. At entry stations, license plates shall be checked against currently active permit lists, and if a match is found, an entry transaction shall be recorded, and the barrier gates shall be opened

7. Multiple permit lists shall be maintained: monthly parkers, special event prepaids (one per event, limited life for the list), employees, etc.

8. Use of LPR as the credential shall be optional for the customer, as the use could create complications in some situations where a customer has multiple vehicles and multiple drivers, but has a permit for one entry

9. At exit stations, a license plate shall be checked against the inventory of vehicles for which there are open transactions in the facility. If the plate matches an open transaction, and the transaction is already paid, then the transaction shall be closed, and the vehicle shall be allowed to exit without interaction with payment

10. LPR images shall be maintained in the active database for the same duration as all other transactional information. However, the system shall allow for a "purge" capability should the City require a shorter retention period in the future.

11. The LPR system shall keep a "Gray List" of exception transactions based upon vehicle LICENSE PLATE NÚMBER information. Exception transactions shall include insufficient fund transactions, lost ticket transactions, swapped media transactions, attempts to apply a validation to more than one transaction per day per vehicle, and pass back violation transactions. This Gray List shall reside on the PARCS server system's database. As an exception transaction is processed, the LICENSE PLATE NUMBER and corresponding transaction information shall be recorded as part of the Gray List record.
a. LPR Cameras

1. The Contractor shall furnish and install image capture cameras including any lights or shade canopies necessary at all public entry and exit lanes to provide system functionality with Parking Division approval of final placement and material.

2. Devices shall be placed in theft deterrent and vandal resistant housings that meet applicable code requirements for outdoor equipment.

3. The Contractor, subject to approval, shall determine the exact location of each device.

4. All entry images shall be pre-capture, meaning that the cameras are placed in such a position that a vehicle's LICENSE PLATE NUMBER is photographed prior to the entry credential issuance to the patron or accepted by the system.

5. All exit images are to be pre-capture, meaning that the cameras are placed such that a vehicle's LICENSE PLATE NUMBER is photographed before the patron presents their parking credential at the exit.
b. LPR Image Review

1. The City understands that a small percentage of plates will not be recognized within the LPR system and that some entry transactions may not have a license plate number on file

2. If a vehicle arrives at an exit gate and the LPR plate number is not on file, a cashier or other employee shall have the ability to locate the original transaction in the system and view the images of the vehicle and plate to validate the transaction.

3. The employee who reviews the images shall have the ability to enter an updated plate number for the entry and/or exit transaction (s).

4. The system shall allow an employee to enter a plate number and the LPR system shall attempt to find partial matches against the entry reads as well as the mobile reads. The search shall allow optional entry of additional criteria (e.g., range of entry dates/times, approximate location in facility, etc.) to limit the number of search results.

5. Authorized users shall use the image review function to enable remote processing of exception transactions (e.g. Lost Ticket, Mutilated, Unreadable, etc.) at all Cashier Stations and Express Exit Stations. The authorized user shall use the LPR data sent from the lane to verify entry information and transmit the entry information to the exit station for automated calculation of the appropriate parking fee. For example, if a customer using an unattended facility attempts to exit through an express exit, s/he shall be able to use the intercom to obtain help, and the person answering the intercom shall be able to review the LPR data to find the entry transaction.

6. The system shall allow, should the City require in the future, to establish an image review system whereby images containing plates that are not recognized are routed to an attended operator's workstation to be reviewed and entered immediately.

7. The system shall meet the following performance requirements:

8. Acquire an image of a vehicle's entire license plate at a 99 percent (99%) rate for all non-exception vehicles; e.g., capture a visual record of 99% of all non- exception license plates entering the facility.

9. OCR "N factor" rating of 95%; e.g., read all license plate characters, exclusive of stacked characters, correctly 95% of the time for all non-exception vehicles.

Missing, misread, or additional characters shall be counted against the read accuracy.

10. OCR "N-2 factor" rating of 98%; e.g., read all license plate characters except two, exclusive of stacked characters, correctly 98% of the time for all non-exception vehicles. Missing, misread, or additional characters shall be counted against the read accuracy.

Exception vehicles are:
a. Any vehicle whose license plate is obstructed, obscured, or encroached upon by a foreign object (having a foreign object within .375 inches (%) of any LICENSE PLATE NUMBER character).
b. Oversized vehicles that have a total distance between the center of the drivers' side window and the end of the rear bumper greater than 12 feet. c. Vehicles that contain excessive graphics and advertising such that it is impossible for the LPR system to determine which graphics belong to the license plate and which graphics do not.
d. Vehicles with no license plate

e. Vehicles with temporary cardboard (non-reflective) "Dealer Plates" f. Motorcycles

11. Ambient lighting conditions shall have no effect on the accuracy of the LPR system regardless of the time of the day and night. The Contractor shall provide any necessary shading or lighting elements required to mitigate the effect of the ambient lighting conditions on the LPR system performance. c. Mobile LPR or handheld LPR (inventory)

1. The primary method for collecting inventory in facilities shall be use of the a mobile LPR system to be mounted on City enforcement and mobile security patrol vehicles. The PARCS shall obtain that data from the system.

2. The system shall provide for a secondary method for collecting inventory in facilities, using a handheld system that shall allow an employee on foot or in a slow-speed vehicle (such as a cart or bicycle) to capture plates and locations and transfer the data into the PARCS.

3. The handhelds shall capture photos of each vehicle

4. The handhelds shall recognize the plate and present to the employee for verification

5. The handhelds shall wirelessly transmit the recorded and verified information to the PARCS on a continuous basis

6. The handhelds shall be rugged, withstanding drops from a height of six feet onto concrete, and resistant to dust, water/rain, and other environmental conditions or work on existing City-issued smart phones.

7. The PARCS shall compare data captured by mobile and handheld LPR and generate an exception report indicating:

8. the vehicles detected within the facility for which no transaction records exist

9. the vehicles detected within the facility for which transaction records indicate the vehicle previously left

10. the vehicles that, according PARCS transaction records, should be in the facility but are not detected

11. After a vehicle license plate has been captured by mobile LPR and the information has been transferred to PARCS, a lookup on the license plate shall provide the location of the vehicle within the facility.

12. Describe your system's accuracy in providing location data for vehicles based on LPR or handheld LPR.
d. Occupancy Monitoring

1. The system shall maintain a count of vehicles within the facility.

2. Occupancy monitoring shall be integrated into the PARCS such that the available parking spaces within the facility (based upon a differential count between entries

and exits) are available at any time and can be retrieved by external parties through an API.

3. Facility tracking shall include counts by type of credential used for access (LPR transient ticket, CCI/CCO, proximity card, pre-paid, AVI, etc.)

4. There shall be detectors located on each parking structure's entry/exit lane (from the PARCS) for detecting vehicular movements relative to entering and exiting a parking facility. The monitoring system shall obtain count data from the detectors used by the parking facilities' entry and exit lanes along with detection devices placed at ramp access points which control ingress and egresses.

5. The vehicle count inputs shall be transmitted to the servers that shall process the data on a real-time basis. The processing shall consist of adding, subtracting, and comparing the respective vehicle counts against a predetermined number of parking spaces within each of the parking structures or surface lots.

6. The Occupancy Monitoring System shall provide the following:

7. Automatic and manual control of the space count signage

8. Automatic update of the number of parking spaces available on dynamic signs at a configurable interval, that the City can set between ten and 600 seconds

9. Maximum and minimum counts for each parking facility

10. Hourly flow rates through entries and exits

11. Control of the count dynamic signs at each parking facility (facilities shall be considered "FULL" when the number of available parking spaces is less than a predetermined number that is adjustable by the City; for example, to allow monthly parkers to continue to enter the facility. The City shall have the option to manually modify the messages being displayed by overriding the displayed number of available parking spaces. This override shall not affect the system's actual count of the number of vehicles on the level.
e. Control of the Dynamic Signage

1. All mounting hardware for dynamic signage and vehicle detection devices that are part of the Occupancy Monitoring System, including any overhead mounting structures, shall be provided by the Contractor.

2. The Occupancy Monitoring System shall be fully automated. However, while in operation, there shall be allowances for manual adjustments and override of the Occupancy Monitoring System via the workstations, including, but not limited to:

3. Establishing the initial number of parking spaces within each parking facility.

4. Setting parking space variance values;

5. Manual control of all parking space count dynamic signs; and adjustment of the number of spaces available in parking facility.

6. Reconciliation after a survey or inventory.

f. Workstation Functions - Occupancy

1. All data required to monitor and adjust the Occupancy Monitoring System shall be available on all authorized PARCS workstations.

2. The screen formats shall be designed for the facilities' parking configurations (layout).

3. All screen formats for the Occupancy Monitoring System shall reflect the physical layout of the parking facilities for ease of associating the displayed data with physical conditions.

Workstation application shall include the following:

1. Real-time graphical displays of the entire parking inventory (by facility) with both the number of available parking spaces and spaces occupied (immediate user identification of count status).

2. The displays shall show red, yellow, and green to reflect various levels of occupancy, where the percentage full represented by each color is configurable by the City for each facility.

3. Alarms shall be configurable by City staff with appropriate rights and privileges.

4. Alarms to notify when a facility is "FULL" (where full is defined as a percentage, as listed above

5. Alarms of component failures;

6. User access levels with password restrictions;

7. Operating status of all dynamic signage, including message currently being displayed;

8. Display of summary statistics of parking space availability by specified date/time period.

9. The City shall determine the initial number of vehicles that a parking facility will accommodate. It shall be possible for the City to adjust the total parking spaces for each parking facility as a whole.

10. If vehicles continue to enter a facility after the Occupancy Monitoring System determines it is "FULL," a warning indicator on a workstation's display shall be activated and the Occupancy Monitoring System shall record negative parking spaces available and an occupancy over 100%.

11. As vehicles exit the facility, the availability should return to a positive number and the occupancy should go under 100%.

12. An inventory of a parking facility shall provide an exact count of the vehicles.

13. Provisions shall be included to manually adjust count information into the Occupancy Monitoring System.
g. Operational Procedures - Occupancy

1. "Vehicle Count" shall be the number of vehicles located in a parking facility.

2. "Spaces Available" is defined as the unoccupied spaces in any given facility resulting from the number of vehicles counts affecting the space availability of any specific facility.

3. For all facilities, the facility count shall be maintained independently in the Occupancy Monitoring System. The facility count shall only be affected by entries and exits into and out of the parking structure.

4. The facility count shall indicate the number of vehicles based on entry credential and type; e.g., the number of vehicles with transient tickets, the number with monthly passes, the number of event entries, etc.
h. Occupancy Monitoring System Hardware
Accurate vehicle detectors:

1. Recognize vehicle entry and exits, even if the vehicle is traveling in the wrong direction for the lane (e.g., entering through an exit lane)

2. May use the entry/exit lane detection system as long as all requirements for entry/exit detection for control of revenue and access are met and all requirements for occupancy monitoring are met

3. Shall count even if the gate arms are in the UP position Dynamic message signs:

1. Facility Open/Full Sign - dynamic signs on approach roadways or at entry plazas that provide the status for each facility; at minimum, by displaying "OPEN" in green or "FULL" in red

2. Proper sign matrix size shall be proposed by the Contractor to fit within the geometric circumstances of each installation.

3. The Occupancy Monitoring System software shall control the message that is displayed on all signs.

4. The Occupancy Monitoring System shall allow the City to override the status displayed and to change the predetermined occupancy number that triggers a change from one sign display to another displayed status. i. Performance Requirements - Occupancy

1. Facility counts shall update in the PARCS within five seconds.

2. The Occupancy Monitoring system shall be more than 95% accurate at all times.

This means the difference between the reported count and the actual count of vehicles on a level or within an entire facility shall be less than 5%.

3. The data on the dynamic messaging signs shall update on a frequency that is configured by the City, at a range of 10 seconds to five minutes.

4. Interfaces/Integration

5. The City desires to get the maximum flexibility from the PARCS.

6. REPORTING

1. Real-time transaction data feed

2. Summary and detailed reports

3. Allow query, filter, and sorting by any fields/criteria, such as date/time, location, ticket id, vehicle license plate number, field device, parking fee, transaction type, exception, validation type, or cashier

4. Allow generation of ad hoc reports, based on existing reports within the system (e.g., allow someone to take a revenue report and add columns and change sorting and save as a new report)

5. Please provide a list of all standard reports. Please include examples of the most significant reports in an appendix.

6. Describe whether reporting is performed against the live database or against a separate data warehouse, or both.

7. Describe the report writers and reporting methods that are available for the proposed product (s):

8. Ability to produce comprehensive management reporting for all areas within the organizational process

9. Ability to produce both standard and ad hoc reports.

10. Ability to allow for the use of standard statistical packages so that research and analysis can take place.

11. Ability to design and implement both on-line ad hoc queries and batch (scheduled) reporting programs as required by user.

12. Ability for report generator to allow user to select data, choose fields, and create calculated fields.

13. Ability to reconcile reports from different components in the system.

14. Ability to extract data to another tool, such as Excel or a report writer.

15. Ability to schedule reports to be printed, emailed, or updated to a web page on a regular basis, such as daily or hourly

16. Ability for reports to do modeling or "what if" scenarios

17. The Parking Division prefers a "dashboard" to monitor all elements. Please describe and explain how it can be customized and indicate whether customization is for the entire system or each user.

18. Data formats should export to editable forms, such as Excel. a. Auditing / Administrative
Full financial, transactional, and operational auditing

1. Ability to trace any individual session from entry to exit.

2. Ability to see all transactions that occursed on any credential (such as a permit or license plate), even if the transactions were submitted by external systems (e.g., a payment submitted by a mobile payment company).

3. Ability to find all validations by individual merchant.

4. Ability to find a credit card transaction with "first 6 and last 4" of credit card number, and Ability to issue credit for an individual transaction (whether parking session or permit) from search

5. Ability to find all transactions performed at any individual device.

6. Ability to find all transactions performed by any individual person.

7. Ability to isolate and examine all exception transactions.

8. Ability to find all changes to configuration, rates, discount programs, customers, etc.

Requirements
b. Training
Shall be sufficient that a person in any role shall be proficient with the system as required Roles:

Facility cashiers
Routine transactions
Exception transactions
Parking technicians (repair/maintenance workers)
Maintenance and repair of entry stations, exit stations, cashier stations, POFs, LPR equipment, lane detectors, variable message signs, barrier gates, UPS equipment, occupancy monitoring equipment, etc.

Describe other duties for parking technicians
Revenue collectors
Collection and/or replenishment of POFs
Facility supervisors
Manage cashiers and overall facility operation
Finance and administration
Obtain financial and performance reports
Set configuration parameters
Monitor overall performance
Process customer transactions (e.g., "front counter")
Deployment training, if needed

7. TESTING AND COMMISSIONING
a. General: The City of Riverside requires a robust and sound testing and commissioning program for the project. The City of Riverside desires that the PARCS be fully operational, including meeting all standards specified in this section, at the date of opening of the facility and be fully tested prior to that date.

b. The Vendor shall provide a detailed testing procedure as part of the proposal.

Please identify the cost of the testing and commissioning as a separate amount.

This can include but may not be limited to:
i. Factory Acceptance Tests. In an offsite location controlled by the manufacturer as close as possible to the jobsite. The purpose of the FAT is to demonstrate the operation and performance of all the equipment components, both online and offline and the configuration of all components and subsystems. At the end of running all the FAT "test scripts", an assessment is made of testing, any gaps identified, and a decision on whether to move forward to the next phase of testing. Final test scripts shall be submitted 60 days prior to the test. il. Lane Acceptance Tests. Once an approved FAT has been completed an onsite lane acceptance test may be conducted. This will include one fully operational entrance and one fully operational exit lane. Once the lane equipment has been installed and connected with the installed head end system, the PARCS shall run all testing scenarios and shall include communication to any external systems including City of Riverside integration operations, bank clearing house, and generation of identified reports confirming all test transactions. This shall include EMV compliance. After the initial LAT has been conducted each additional lane shall go through an LAT process. Final test scripts shall be submitted 30 days prior to the test.

PARCS Acceptance Test. The purpose of which is to ensure that operational testing in a real life environment allows for a period of time to make final PARCS adjustments. After approval of all LATs a 30 day continuous full PARCS acceptance test shall be conducted to run the entire operation as a whole. c. The Vendor shall coordinate the schedule of testing procedures with the City of Riverside.

8. MAINTENANCE AND WARRANTIES
a. General: The 1 year manufacturer's maintenance and warranty period shall start at the date of the final acceptance of the entire system. b. All warranties shall be coterminous based on the date of the final acceptance of the entire system.
c. The City of Riverside shall be listed on all warranties. d. All costs of PARCS during the one year maintenance warranty period are to be part of the base proposal.
e. The Vendor shall provide access to advanced level technical phone support to trained City of Riverside personnel to provide maintenance on devices when necessary.

The Vendor shall provide factory trained technicians to provide maintenance on the PARCS such that 24 hours a day 7 days a week a person is available. A person shall be on site if necessary within a 6 hour period to resolve any issues. If issues can be resolved remotely, a 3 hour response time is required. The City of Riverside expects general resolution to issues within 3 days unless mutually agreed otherwise. g. Common parts shall be available within 48 hours. Vendor shall provide pricing and recommend stock levels for common spare parts that the City of Riverside can maintain on hand.
h. Extended warranty and maintenance: As part of the proposal, please provide the cost of extended maintenance for a period of (10) ten years beyond the initial

one year warranty period. Please provide the cost for an extended (10) ten year warranty beyond the initial one year warranty period.

EXHIBIT "B"
Compensation
Exhibit B
tem a tem Description Unit Price Garage 3 arare 6 Garage 7 Garage 3 Sarage 6 Garage 7 Please use the space to note any clarifine remarke for item Fated Juantity Quantity
Ticket Dispenser/Entrance Column 14,455.00 14,455.00 S 43,365.00 Includes EMV CC Reader and NFC, Prox Reader, QR Scanner, VOIP Intercom Module, Pinhole Camera and Standard Graphic Panel Exit Pay/Column (CC/Validation/EMV/NFC Only) 4,455.00 445500 S 57.320 00 Includes EMV CC Reader and NFC, Prox Reader, QR Scanner, VOIP Intercom Module, Pinhole Camera and Standard Graphic Panel ntercom Software 333.00 333.00 S
999.00
Intercom Base Station w/remate vend 885.00 95.00 $85.00 S 2,655.00 Intercom Server (if applicable) 3,264.00 3,264.00 5 $264.00 TOUCH Screen PAY ON FOOT -(CC/CASH/COIN/Validations/NFC/EMV] 1510.00 1 510 ca 63,020.00 31.510.00 S 126,040.00 Includes Cash, EMV CC and NFC, VOIP Intercom Module and Pinhole Camera and Standard Graphic Panel TOUCH Screen PAY ON FOOT - (CC/Validations/NFC/EMV) 15,225.00 30,450.00 1522500 S 45.675.00 Includes EMV CC Reader and NFC, VOIP Intercom Module, Standard Graphic Panel LOR Camera 5010.00 30,060.00 15,030.00 15,030.00 s 50,120.00 LPR Cameras LPR Hardware (if Applicable) 150 00 3,900.00 1950.00 L05000 S 7,800.00 LPR Post and Loop Detector PR Loon Cut 300.00 1,800.00 900.00
100.00 3,600.00
LPR Loops 0оco 450.00 450.00 1,800.00
LPR Controller (if applicable) 3,140.00 3,140.00 3,140.00 S 6,280.00 Entry/Exit Column (Gate) - Articulating Arm 3 498.00 13,952.00 10,464.00 10,464.005 34,830.00 Column (Gatel Loops Cuts 2,400.00 1.800.00 500000
column (Gatel Loses 1,200.00 500.00
900.00 3,000.00
EMV Gateway (if Asplicable) 3,200.00 | S 3,200.00
pace Available 4 Digit LED display 5,735.00 5.736.00 5] 17.208.00 Sign Controller 135.00 2,270.00 2,270.00 2,270.00 $ 810.00 Management Software Licenses (if applicable) 960.00 960.00 250.00 2,880.00 SmartPark Cloud for 12 months EMV Credit Card Processing Software 354.80 364.80 364.80 364.80 1,094,40 cC Software for 12 months Validation Software License (if applicable) 252.00 $2.00 252.00 S 756.00 Web Validations for 12 months PARIS Invoicing/Billing interface software license 216.00 HE GO 1600 CAR 00 l Paris Cloud software for 12 months
Count Management software 16 00 216.00 216.00 5 648.00 TIBA Smartzone Counting software for 12 Months LPR Software License (if applicable) 768.00 69.00 2,304.00 PR licenses for 12 mentha Syster Management Network Switch 480.00 480.00 480.00 1,440.00 Workstation (Completel 12900 1,600.00 1,600.00 4,800.00 Validation/Chaser Ticket Printer 1,320.00 1,320.00
Laser printer (color) 315.00 315.00 945.00
UPS BATTERY BACKUP (Field Stations) 5 20200 5.792.00 23,168.00 Spare Bill Cassette $00.00 1,600.00 1,600.00 1,600.00 4,800.00 2700.00 2,700.00 2,700.00 S 8,100.00
POE Switch 340.00 340.00 320.00 920 00
Monthly Card Reader 50000 7,000.00 3,500.00 3,500.00 14,000.00 Prox Reader, VOIP Intercom Module and Standard Graphic Panel AVI Access and Poles 3,700.00 18,500.00 1.100 00 1100 m 40,700.00 Break out & ITEMIZE the total cost for training that you are proposing as part of the base scope of work 1,200.00| 1,200.00 120000 | 5 2 500 00 Break out & ITEMIZE the total cost for installation that you are proposing as part of the base scope of work 86,900.00 105,053.00 94,780.00 286,733.00 Freight 2,218.00 2.218.00 2,218.00 6,654.00
ORP Randa
13,290.38
Cost of extended maintenance for a period of nine (9) vears beyond the initial Year 2 - Service/Maintenance Agreement 23,170.00 22,500.00 20,475.00 66,145.00 Year 2 - Service/Maintenance Agreement Year 3 - Service/Maintenance Agreement 20.062 00 27,720.00 23,610.00 80,392.00 Year 3 - Service/Maintenance Agreement Year 4 - Service/Maintenance Agreement 30,260.00 28,845.00 24,353.00| 83,458.00 Year 4 - Service/Maintenance Agreement Year 5 - Service/Maintenance Agreement 21 61500 31,275.00 25.505.005 38,295.00 Year 5- Service/Maintenance Agreement Year 6 - Service/Maintenance Agreement 32,562.00 26,522.00 91.939.00 Year6. Sorico/Maistonanco Aproament Year 7 - Service/Maintenance Agreement a 9200 33.955,00 27,591.00 95,766.00 Year 7 - Service/Maintenance Agreement (Ostional) Year 8 - Service/Maintenance Agreement 35,670.00 35,395.00 28,715.005 $9.780.00 Year 8 - Service/Maintenance Agreement (Oational) Year 9 - Service/Maintenance Agreement 37,200.00 36.910.00 29,893.00 S 104,003.00 Year 9 - Service/Maintenance Agreement (Oational) Year 10 - Service/Maintenance Apreement 38,800.00 37,845.00 31,130.005 107.175.00 Year 10 - Service/Maintenance Agreement (Optional) Garage 3 arace G Comments

90.876.80 $ 109,029.80 95,756.80 S 311.953.78 Non-Taxable Subtotal 5185,968.00 S 197,20300 $ 156,932.00 S 540,103.00 Taxable Subtotal 16,272.20 17,255.26 13.731.55 5 47,259.01
S 293,117.00 S 323,488.06 5 269,420,35 S 899,315.79 Total amount due for Year 1 (Base Equipment/Installation/Configuration/Startup/Warranty/Training) 23,170.00 $ 22,500.00 20 47e c

29.062.00 S 27,720.00 23,610.00 5 69500 Total amount due for Year Sarice/Maintenance Agreemen:) 30,260.00 § 29845.00 83,458.00 Total amount due for Year 4 (Service/Maintenance Agreement) 31,515.00 31.275.00 25.505.00 51 88,295.00 Total amount due for Year 5 (Service/Maintenance Agreement) 32,835.00 § 32582.00 26529c0| c 11 020 00 Total amount due for Year 6 (Service/Maintenance Agreement) 34,220.00 S 33.955.00 27.591.00 S 95,766.00 Total amount due for Year 7 (Optional - Service/Maintenance Agreement) 35,670.00 S 35,395.00 99,780.00 Total amount due for Year 8 (Optional - Service/Maintenance Agreement) 37,200.00 36.910.00 29,893.00 31 104,003.00 Total amount due for Year 9 (Optional - Service/Maintenance Agreement) 38,800.00 € 37 845 00 2193000€ 107.775.00 Total amount due for Year 10 (Optional - Service/Maintenance Agreement) $ 1,309,544.79 Year 1 - Total Procurement plus Years 2-6 - Service/Maintenance Agreement $ 1.05,28.00 To C20. $07.321.00_Year 7-10 - Service/Maintenance Agreement (Optional)