Agenda 02/11/2025 Item #16B 2 (Awarding RFP #23-8166 for the Collier County Transit Electronic Farebox to LECIP, Inc.)2/11/2025
Item # 16.B.2
ID# 2025-225
Executive Summary
Recommendation that the Board award Request for Proposal (RFP) No. 23-8166, Collier County Transit Electronic
Farebox, to LECIP, Inc., in the amount of $891,326.83, which is 100% funded with Federal Capital Grant dollars, and
authorize the Chairman to sign the attached Agreement.
OBJECTIVE: To replace the Electronic Farebox software and hardware system utilized for the Collier Area Transit
fare collection.
CONSIDERATIONS: The Public Transit & Neighborhood Enhancement ("PTNE") Division administers the Collier
Area Transit ("CAT") system, by providing transportation services for Collier County area residents and visitors. CAT
currently operates 16 Fixed Routes with 19 buses Mondays through Saturdays, and 13 Fixed Routes on Sundays. The
Transit System also consist of paratransit service known as CATConnect, which provides door to door trips to the
County's disadvantaged population.
The CAT system has utilized the existing farebox software and hardware for the past 12 years and those units are ready
for replacement. To improve existing products and services, system efficiencies, and customer convenience when
utilizing the system, PTNE prepared a solicitation to obtain proposals for a turnkey, industry-standard, integrated
Electronic Farebox solution. The new system will be integrated with the current CAT Mobile Ticketing system allowing
for a seamless user experience.
On October 28, 2023, the Procurement Services Division posted Request for Proposal (“RFP”) No. 23-8166, Collier
County Transit Electronic Farebox. The due date was extended two weeks, and staff conducted additional vendor
outreach. The County received two proposals by the December 19, 2023, submission deadline, with both proposers
being found responsive and responsible.
A selection committee met on January 31, 2024, evaluated the proposer's qualifications, and reviewed the references
provided by the proposers from clients of a similar size as the County for which they provided services similar in scope
and complexity within the past five years. After deliberating, the committee scored the proposals and shortlisted both
firms to move on to Step 2, oral presentations. On March 4, 2024, the selection committee reconvened for oral
presentations, and ranked the firms as follows:
Firm Final Ranking
LECIP (Chicago, Illinois),
Inc.
1
BEA Transit Technologies 2
Staff is recommending award to the top-ranked firm, LECIP (Chicago, Illinois), Inc. ("LECIP"). LECIP is authorized to
conduct business in Florida and has more than 70 years of experience in the Public Transportation industry. This will be
the County's first agreement with LECIP. Staff concluded that the proposed rates are fair and competitive in the current
market. The attached Agreement provides for an initial four-year term, with two additional one-year renewal options.
Historically, Transit Federal Grants have been utilized for funding the support and warranty of the farebox system, and
staff will continue to allocate such grant funding as awarded.
This item is consistent with the Collier County strategic plan objective to design and maintain an effective transportation
system to reduce traffic congestion and improve the mobility of our residents and visitors. Additionally, the item is
consistent with the objective to support access to health, wellness, and human services.
FISCAL IMPACT: The total agreement cost is $891,326.83 comprised of hardware cost, licensing fees, warranty and
six years of Maintenance Services. Funding for the Collier County Transit Electronic Farebox solution is available
within Transit Grant Fund 4031 through the Sections 5307 Federal Transit Administration Grant Programs.
Page 1116 of 3773
2/11/2025
Item # 16.B.2
ID# 2025-225
Ongoing support and warranty will also be funded through Transit Grant Fund 4031 and use of FTA Federal Grant
Programs.
GROWTH MANAGEMENT IMPACT: This item is consistent with the Transportation Element of the Growth
Management Plan.
LEGAL CONSIDERATIONS: This item is approved as to form and legality and requires majority vote for Board
approval. —SRT
RECOMMENDATIONS: To award Request for Proposal No. 23-8166, Collier County Transit Electronic Farebox, to
LECIP (Chicago, Illinois), Inc., in the amount of $891,326.83, which is 100% funded with Federal Capital Grant dollars,
and authorize the Chairman to sign the attached agreement.
PREPARED BY: Omar De Leon, Transit Manager, Public Transit & Neighborhood Enhancement Division
ATTACHMENTS:
1. 23-8166 NORA
2. 23-8166 Final Ranking
3. 23-8166 Solicitation
4. 23-8166 LECIP_Proposal
5. 23-8166 VS_LECIP
6. 23-8166 Affidavit_LECIP
7. 23-8166 InsurancePacket_LECIP
Page 1117 of 3773
Notice of Recommended Award
Solicitation: 23-8166 Title: Collier County Transit Electronic Farebox
Due Date and Time: December 19, 2023, at 3:00 P.M. EST
Respondents:
Company Name City County State Final Ranking Responsive/Responsible
LECIP Inc., authorized to do
business in Florida as, LECIP
Chicago, Illinois, Inc.
Bensenville DuPage IL 1 Yes/Yes
BEA Transit Technologies Inc Alameda Alameda CA 2 Yes/Yes
Utilized Local Vendor Preference: Yes No
On October 28, 2023, the Procurement Services Division released notices of Request for Proposal (RFP) No. 23-
8166, Collier County Transit Electronic Farebox, to eight thousand eight hundred and eighty-eight (8,888)
firms. Thirty-seven (37) firms viewed the solicitation information. The due date was extended two weeks, and
staff conducted additional vendor outreach. The County received two (2) proposals by the December 19,
2023, due date.
Staff reviewed the submittals, and all proposers were deemed to be responsive and responsible with minor
irregularities.
The Selection Committee met on January 31, 2024. After review of the proposals and deliberation, the
Committee scored the proposals and shortlisted both firms to move on to Step 2 oral presentations. On March
4, 2024, the Selection Committee reconvened for oral presentations, and the Committee ranked the firms as
follows:
LECIP Chicago, Illinois, Inc. ranked as 1
BEA Transit Technologies Inc ranked as 2
Staff is recommending award to the top-ranked firm, LECIP Inc., authorized to do business in Florida as, LECIP
Chicago, Illinois, Inc.
Contract Driven Purchase Order Driven
Required Signatures
Project Manager:
Procurement Strategist:
Procurement Services Director:
__________________________________ _________________
Sandra Srnka Date
DocuSign Envelope ID: 91F61DDE-7F18-4182-95DF-9ED6057DCE2E
3/20/2024
3/20/2024
3/20/2024
Page 1118 of 3773
Selection Committee
Final Ranking
RFP #: 23-8166
Title: Collier County Transit Electronic Farebox
Name of Firm Omar Deleon Alexander
Showalter
Corene
Sanger Neftali Albino Jecika Cook Total
Selection
Committee
Final Rank
LECIP Inc.1 1 1 1 1 5 1.0000
BEA Transit Technologies, LLC.2 2 2 2 2 10 2.0000
Procurement Professional Date 3/4/2024Kristofer Lopez
Page 1 of 1
Page 1119 of 3773
COLLIER COUNTY
BOARD OF COUNTY COMMISSIONERS
REQUEST FOR PROPOSAL (RFP)
FOR
COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
SOLICITATION NO.: 23-8166
PATRICK BOYLE, PROCUREMENT STRATEGIST
PROCUREMENT SERVICES DIVISION
3295 TAMIAMI TRAIL EAST, BLDG C-2
NAPLES, FLORIDA 34112
TELEPHONE: (239) 252-8941
Patrick.Boyle@colliercountyfl.gov (Email)
This solicitation document is prepared in a Microsoft Word format (Rev 8/7/2017). Any alterations
to this document made by the Vendor may be grounds for rejection of proposal, cancellation of any
subsequent award, or any other legal remedies available to the Collier County Government.
Page 1120 of 3773
2
SOLICITATION PUBLIC NOTICE
REQUEST FOR PROPOSAL (RFP)
NUMBER:
23-8166
PROJECT TITLE: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PRE-PROPOSAL CONFERENCE: N/A
LOCATION: PROCUREMENT SERVICES DIVISION, CONFERENCE ROOM A, 3295
TAMIAMI TRAIL EAST, BLDG C-2, NAPLES, FLORIDA 34112
DUE DATE: November 30, 2023, at 3:00pm EST
PLACE OF RFP OPENING: PROCUREMENT SERVICES DIVISION
3295 TAMIAMI TRAIL EAST, BLDG C-2
NAPLES, FL 34112
All proposals shall be submitted online via the Collier County Procurement Services Division Online Bidding System:
https://www.bidsync.com/bidsync-cas/
INTRODUCTION
As requested by the Public Transit & Neighborhood Enhancement (PTNE) Division (hereinafter, the “Division”), the Collier County
Board of County Commissioners Procurement Services Division (hereinafter, “County”) has issued this Request for Proposal
(hereinafter, “RFP”) with the intent of obtaining proposals from interested and qualified vendors in accordance with the terms,
conditions and specifications stated or attached. The vendor, at a minimum, must achieve the requirements of the Specifications or
Scope of Work stated.
The purpose of the RFP is to purchase and upgrade or obtain a replacement solution for the Farebox system. Historically, County has
spent approximately $117,275.00; however, this may not be indicative of future buying patterns. Collier Area Transit has recently
implemented Masabi Mobile Tracking solution and expects contractors to utilize the Masabi open API for integration of systems to
the extent possible.
BACKGROUND
Collier Area Transit (CAT) conducted an Intelligent Transportation Systems Evaluation and Schweiger Consulting LLC
recommended the County upgrade or replace the existing farebox system. The upgrade or full replacement will allow the County to
take full advantage of a modernized farebox system.
TERM OF CONTRACT
The contract term, if an award(s) is/are made is intended to be for four (4) years, with two (2) one (1) year renewal options. Prices
shall remain firm for the full term of this contract.
Surcharges will not be accepted in conjunction with this contract, and such charges should be incorporated into the pricing structure.
The County Manager, or designee, may, at his discretion, extend the Agreement under all of the terms and conditions contained in
this Agreement for up to one hundred eighty (180) days. The County Manager, or designee, shall give the Contractor written notice
of the County's intention to extend the Agreement term not less than ten (10) days prior to the end of the Agreement term then in
effect.
All goods are FOB destination and must be suitably packed and prepared to secure the lowest transportation rates and to
comply with all carrier regulations. Risk of loss of any goods sold hereunder shall transfer to the COUNTY at the time and
place of delivery; provided that risk of loss prior to actual receipt of the goods by the COUNTY nonetheless remain with
VENDOR.
Page 1121 of 3773
3
DETAILED SCOPE OF WORK
Collier Area Transit (CAT) is seeking an upgrade or replacement of the farebox solution. The solution shall meet the requirem ents
below. Items identified as “Alternate” are expected to be priced and included in the proposal, but Collier County may decide not to
implement.
SECTION 1. FAREBOX:
1. Farebox Functionality:
A. The Farebox shall be service proven and shall be installed on the entire fixed route bus fleet for Collier Area Transit. The
contractor shall demonstrate that the equipment can be conveniently used by persons with disabilities, including persons
with limited manual dexterity and persons with sight disabilities without the need for assistance or special training. The
Contractor will be asked to demonstrate how persons with sight impairment will locate the machine, have access to
instructions, and carry out transactions. Additionally, the contractor needs to provide a fully hosted solution as CAT does
not have any on-premises servers.
B. The Farebox shall automatically identify and count all U.S. coins in general circulation, including any U.S. coins that may
be issued during the service life of the Automatic Fare Collection system. The Farebox shall also be capable of automatically
rejecting foreign and counterfeit currency. The Fare Collection System shall be an open architecture, account-based system
with key system interfaces built, using Application Programing Interfaces (API’s) published by contractor, and fully owned
or licensed by the County.
C. The Farebox System must provide an Open Application Programming Interface (API) for reports to and from other
contractors.
D. Coin mechanism shall be capable of processing coins at an insertion rate of five items per second sustained.
E. The Farebox shall have a minimum of twenty (20) fare class presets per fare set. There shall be a minimum of 10 fare sets.
The preset amounts shall be between $000.01 and $999.99.
F. Each Farebox shall have a bill validator which accepts $1, $2, $5, $10, and $20 bills and capable of accepting bills of “street
quality” inserted flat and unfolded. The Farebox shall accept, correctly identify, and total valid U.S. bills while rejecting and
returning to the passenger torn, mutilated, partial, and counterfeit or foreign bills.
G. The Farebox shall be capable of recognizing all U.S. legal tender that may be issued over the service life of the system.
H. All U. S. coins and bills shall be deposited into a single Cashbox, securely compartmentalized to separate the coins and bills.
I. The Farebox shall be capable of electronically verifying all coins and bills inserted for fare payment. All coins and bills shall
be automatically verified and identified by denomination, without operator action. All U. S. coins and bills that cannot be
electronically verified shall be automatically rejected and returned to the passenger.
J. The Farebox shall assist operators with verification of the fare deposited by showing an immediate display of the value of
coins and bills inserted. If the coin or bill verification functionality is not available due to a jam or equipment malfunction,
the operator shall have the ability to place the coin or bill module into bypass mode. While in bypass mode, all coins inserted
shall be directly deposited into the Cashbox. The operator should have the ability to note the amount of money inserted
while in the bypass mode.
K. The Farebox shall be capable of printing transfer tickets and a day passes and alternate special passes that the PTNE Division
may request for Special Events. The farebox must also be capable of accepting these tickets/passes and accounting for them
when used.
L. Cashbox Receivers shall be installed at Collier Area Transit main facility in order to securely transfer cash from surface
vehicle to the Receiver. The Receivers shall empty the Cashboxes into a stationary cash vault that shall receive and store the
cash. The Cashbox Receivers and the vault shall maintain complete secure separation of all coins from bills.
M. The system shall have a secure area that will accept the cashbox/farebox vault to release the funds form the exterior Collier
Area Transit money counting room. The system shall have provisions for secure transfer into the interior of the counting
room. Cash shall not be accessible by personnel or the public from the time of its insertion into the Farebox, until the time
of emptying the cash box at the Revenue Collection Facility.
Page 1122 of 3773
4
N. The farebox shall conform to the reliability requirements in this specification while in revenue service operations. The
Farebox shall be accurate in its counting and data reporting and shall be secure in its retention and transfer of data and
collected revenue. The Farebox design shall keep operator intervention to a minimum while processing of fares on board
the bus.
O. The farebox shall function under the environmental and operational conditions specified and shall be designed and
manufactured to provide a high degree of security against forced entry and/or unauthorized manipulation.
P. Data integration shall be made available, open Application Programming Interface (API) will be required for Business
Intelligence integration.
Q. The fare collection system shall communicate with the Computer-Aided Dispatch/Automatic Vehicle Locator (CAD/AVL)
system for the exchange of data and in support of integrated operational functionality.
R. The CAD/AVL system will be the primary log-on and log-off system for the bus operator. The farebox startup sequence
shall require receipt and validation of AVL log-on information consisting of: Single sign on is a requirement between the
CAD/AVAL system and the Farebox system which displays, at minimum, the following information.
a. Operator ID
b. Block-ID
c. Log on date and time
S. The time and date on each Farebox must sync with that of the CAD/AVL system.
2. Farebox Technical Requirements:
A. The farebox shall be designed to fully validate the deposit of coins, and currency bills to ensure, without intervention by
Collier Area Transit personnel, the genuine validity of the deposited currency or tokens. Inserted coins, tokens or currency
bills rejected or determined to be invalid shall be promptly returned to the customer without intervention by Collier Area
Transit personnel.
B. The coin validator shall be configured to accept, validate, and count the value of pennies (1 cent), nickels (5 cents), dimes
(10 cents), quarters (25 cents), and dollar coins ($1.00). It shall be possible to configure the coin mechanism to accept,
validate, and count coins or tokens with a diameter and thickness between that of the U.S. dime and the U.S. half dollar coin.
C. The design of the coin bezels and coin acceptor channel shall be such that coins inserted into the farebox at the rate of fiv e
(5) coins per second are reliably, without jam, and channeled to the coin validator in an appropriate manner to ensure accurate
and reliable identification. A failure of the coin handling system to properly and reliably present coins to the coin validato r
shall be considered as a failure of the coin system.
D. The farebox logic shall maintain a record of total coins and tokens processed and total coins and tokens rejected, and this
record shall be transmitted to the data system at each data upload.
E. The farebox shall be capable of accepting, validating, and counting paper currency bills. The paper currency acceptance slot
shall be positioned in the general proximity of the coin insertion area and shall accept paper currency that has been opened
to its full area and is inserted lengthwise.
F. The bill validator shall be capable of validating not less than ten unique paper currency designs and shall be configurable to
accommodate new or changed currency designs without disassembly or mechanical modification. The bill validator and the
delivered supporting systems shall provide the means for Collier Area Transit to update the validator logic as necessary to
support currency changes without Contractor assistance or return of the validator unit. Any new currency design must be
comparable (size and detection technology) to banknotes in circulation at Notice to Proceed. The validating logic of the
validator shall examine the inserted bill for proper characteristics and upon validation of these characteristics shall accept
and count the currency.
G. The bill validator shall validate and count one-dollar ($1), five-dollar ($5), ten-dollar ($10) and twenty-dollar ($20) U.S.
banknotes of the types released into circulation during the period from 2000 until installation.
H. The farebox logic shall maintain a record of total bills processed, total bills rejected, and total bills overridden (if allowed)
in a register transmitted to the data system at each data download. Bills not properly processed due to a bill jam are handled
in two ways. If a bill jams in the bill scanner and the validation of the bill has not been completed, the value of the bill is not
known, and an "unknown document" event is recorded. If the jam occurs at the path down to the cashbox, the correct bill
value shall be stored.
Page 1123 of 3773
5
I. The top assembly is utilized to provide maintenance access. It shall be secured to the farebox upper portion by means of a
continuous hinge and high security lock. Additional or alternative maintenance access doors may be provided to permit
access to the interior of the farebox. They shall be secured by high security lock systems and, unless otherwise approved,
shall utilize a continuous hinge design.
J. If opening any maintenance access door or assembly is required to gain access to secondary maintenance access door, the
operation of those secondary maintenance access door(s) shall be interlocked to assure they cannot be left in the open
position when the top assembly is closed and locked.
K. The lower portion of the farebox shall be made of stainless steel. A revenue access door shall be provided to gain access to
the cavity that houses the cashbox. This door shall have a full-length hinge and be secured by means of at least a three-point
locking bar, actuated by means of a high security electronic lock. The design shall be such that there shall be no gaps
allowing prying to open the door with tools, chiseling, or other entry. Illegal entry shall be clearly indicated by noticeable
damage to the farebox and inability of the farebox to function.
L. Any keys or locks that are captive to the lower portion of the farebox and used to interface with the cashbox shall be securely
fastened and shall be removable only in an authorized manner. Guides shall be employed within the cashbox cavity to assure
that the cashbox is in alignment for proper operations.
M. Wires and cables that are run through the lower portion of the farebox to the upper portion shall be run in a protected channel
or raceway. No wires shall be visible when looking at the cashbox cavity.
N. The cashbox system shall be designed and constructed to ensure the highest level of security in the storage and transfer of
revenue. The cashbox shall be constructed in a configuration to fit within the dimensions of the lower portion of the farebox
and shall have two individual and separate compartments to receive and retain coins and bills, each in their respective
compartments. The separation of the bills from the coins shall be positive.
O. Except as provided by a secure maintenance configuration, the cashbox and its associated farebox shall be designed and so
interlocked in a function to preclude operation of the farebox for the purpose of accepting coin or currency without the
presence of a properly secured, fully functioning, and correctly operating cashbox.
P. The mechanism employed to open or close the cashbox shall be positive and smooth in operation. Internal locking
mechanisms shall be constructed of strong and durable materials. The term “internal locking mechanisms” refers to all
components, including levers, strokes, gears, pins, and locking feet that are required to release the cashbox from the farebox
or lock it in place in the farebox.
Q. The cashbox shall fit into the farebox only in a single correct position and shall be placed into the ready position to collect
revenue by a continuous single motion. The farebox shall remain inoperable until the cashbox is inserted and ready to accept
revenue, and the cashbox access door is closed and secured. Except as may be provided under a secure maintenance
configuration, it shall not be possible to place the farebox into a condition to accept coin or currency bills without the
presence of a properly inserted and fully functioning operational cashbox.
R. The opening of the cashbox access door to permit removal of the cashbox shall be accomplished only through an
authorization process and communication with the back office. The design and operation of the cashbox shall be such that
the cashbox must be in a closed and locked condition to be removed from the farebox unit. The design, mechanism, and
operation of the cashbox shall be positive and at no time shall expose the interior of the cashbox or any of its contents during
any portion of the collection or revenue transfer cycle.
S. Contractor shall provide two complete farebox systems capable of running on 120volt AC power. One farebox will be used
for training purposes, and one will be used as a test bench by maintenance for determining component failures.
3. Farebox Position on the Vehicle:
A. The farebox shall be installed adjacent to the operator position near the front door, and shall be positioned so that an entering
passenger, including persons with disabilities, may easily insert the fare into the farebox. The farebox position shall allow
the rapid and secure inspection of the Operator Control Unit (OCU) data or, if required, the positioning of the data probe,
and convenient removal of the cashbox from the farebox.
B. The farebox shall not impede the vehicle operator from ready access to the operator seat nor obstruct driver barriers.
C. Space and structural provisions shall be made for installation of the farebox. Location of the fare collection device shall not
restrict traffic in the bus, including wheelchairs if a front door loading device is used, and shall allow the driver to easily
reach the farebox controls and to view the fare register. The farebox shall not restrict access to the driver area, shall not
Page 1124 of 3773
6
restrict operation of driver controls and shall not — either by itself or in combination with stanchions, transfer mounting,
cutting, and punching equipment, or route destination signs — restrict the driver’s field of view. The location and mounting
of the fare collection device shall allow use, without restriction, by passengers. The farebox location shall permit
accessibility to the vault for easy manual removal or attachment of suction devices. Meters and counters on the farebox shall
be readable daily. The floor under the farebox shall be reinforced as necessary to provide a sturdy mounting platform and to
prevent shaking of the fare box.
D. CAT will approve the position of the fareboxes installation on all vehicles.
E. The Contractor shall provide approved mounting hardware and kits.
F. The Contractor shall analyze the correct placement of the farebox on each different make and model of bus and shall provide
drawings on the recommended placement for each different make and model of bus.
G. The Contractor shall ensure that the placement of the new fareboxes meets the required maneuvering and reach ranges of
Americans with Disabilities Act (ADA) compliance. Relocation, removal or installation of new railings or other elements
that may represent barriers that could be encountered in the vicinity of the new farebox shall be performed as necessary to
meet these requirements.
H. The Contractor shall position the farebox in such a way that oncoming passengers are not harmed in the event of an accidental
fall or collision with the farebox. Optionally, the Contractor may supply farebox safety guards.
I. The farebox position shall allow for the rapid removal of the farebox from the vehicle. The farebox shall be installed to
permit complete unrestricted opening of all maintenance lids and doors and the cashbox access door. It shall be possible for
an experienced maintenance technician, equipped with the proper tools, to remove the farebox from the bus in less than 15
minutes. In addition, the farebox top shall be removable without providing access to any fare media, coins, or bills in the
farebox.
J. On all types of buses, the location of the farebox and OCU will be established jointly between CAT operations personnel
and the Contractor.
K. The design of the farebox to meet all the requirements of the Technical Provisions shall be submitted for review and approval
by CAT.
4. Farebox Transactions
A. The farebox shall securely and accurately record all transactional information, including sales data, operational errors
and exception conditions, passenger information, and operator commands. At a minimum, the farebox shall record data
for all transactions as follows:
a. All payment transactions
b. Type of media processed.
c. All operator fare classification commands
d. Route
e. Block
f. Latitude and Longitude
g. Farebox power off.
h. Farebox power on
i. Operator log-on
j. Operator log off
k. Door/cover opened (including identification of door/cover)
l. Door/cover closed. (Including identification of door/cover)
m. Successful data probe of transactional data
n. Unsuccessful data probe of transactional data
o. Successful download of farebox configuration data
p. Unsuccessful download of farebox configuration data
q. Cashbox access door opened other than after probing.
r. Cashbox access door closed.
s. Cashbox removed by unique asset ID.
t. Cashbox inserted by unique asset ID.
u. Farebox errors and failures
v. Security errors and intrusions
w. Coin jams
x. Clearance of coin jams
y. Bill jams
Page 1125 of 3773
7
z. Clearance of bill jams
aa. New fare set selected.
bb. Lost Connection
cc. Date and time of payment
B. The farebox shall permit the operator to enter Passenger classifications through the OCU, which shall match such
Passenger classifications to fare amounts.
C. The farebox shall record all errors and exceptions including errors resulting from jammed bills or coins, mechanical
malfunctions, operator errors, and all such conditions where the normal operation of the farebox may be disrupted. An
individual record with date, time, and other relevant details, shall be written for each occurrence of an error or exception.
Errors and exceptions shall be recorded in such detail that an analysis of this information shall represent a full and
complete picture of the farebox performance.
D. In addition to transactional data, the farebox shall maintain running counts and totals such as total number of coins
rejected, total number of bills rejected, and other under no circumstances shall the farebox discard detail data or
substitute summary data, other than as configured by CAT.
E. All transaction and revenue data shall be date and time stamped to the highest resolution of the farebox clock.
F. All transaction and revenue data shall be assigned a unique (per farebox) incrementing record sequence number at the
time it is recorded.
G. The farebox shall provide adequate data storage capacity to store accurately and securely a minimum of 30 days of full
revenue and transactional data. When the capacity of the farebox data storage is reached, the farebox shall suspend
normal service and indicate that data probing is required.
H. Transactional data shall be transmitted to the Base Computer System when data is probed prior to revenue service. After
successful data probing, the Base Computer will direct the farebox to delete the data from the farebox.
I. Alternative technologies for the storage of data, which provide the same capacities and functionality, shall be permitted,
subject to the approval of CAT.
5. Farebox Communication With CAD/AVL System
A. The fare collection system shall communicate with the CAD/AVL system for the exchange of data and in support of
integrated operational functionality.
B. External communication architecture will be designed in conformance with open systems standards. The farebox shall
be provided with an asynchronous serial communications port compliant with the SAE J-1708 and J-1587 standards in
addition to communications ports utilized by Contractor provided devices. Coordination with CAD/AVL Contractor is
required to determine the appropriate means of data transfer to accomplish the goals of the scope.
C. The CAD/AVL system will be the primary log-on and log-off system for the bus operator. The farebox startup sequence
shall require receipt and validation of AVL log-on information consisting of: Single sign on is a requirement between
the CAD/AVAL system and the farebox system.
a. Operator ID
b. ii) Block-ID
c. iii) Log on date and time
D. The farebox shall monitor the J1708 interface for connection and data. If the AVL or J1708 link is determined to be out
of service after several communication attempts, the farebox will prompt the operator to log-on manually to the farebox.
E. A connection timeout period shall be a configurable parameter. The farebox shall automatically resume communication
with the AVL when the connection is restored.
F. Farebox time would sync with that of the CAD/AVL system.
G. In revenue mode, as the vehicle door opens, the farebox shall automatically tag each transaction with the following
information from the AVL:
a. Stop location (GPS Coordinates)
b. ii) Operator ID
c. iii) Block-ID
Page 1126 of 3773
8
H. Upon loss of AVL communication, the farebox shall detect invalid location (e.g., lat/long field is zero) or loss of AVL
communication and prompt the operator to enter the Block-ID, which is updated automatically when the AVL
communication is restored. When AVL communication is restored the farebox shall transfer the following information
to the AVL system:
a. Log on/Log off activity.
b. ii) Farebox Alarms
I. The farebox shall enter non-revenue mode or lockout fare transaction upon operator log-off or the farebox has been idle
for a time period. The farebox idle timeout shall be a configurable parameter.
J. H. The following alarm conditions shall be communicated to the AVL in real time:
a. Cashbox full.
b. ii) Cashbox removed - Alarm shall be created whenever a cashbox is removed from a vehicle on the road.
c. iii) Farebox bypass set – Alarm shall be created when the vehicle operator sets the farebox to bill or coin
bypass mode.
d. iv) Cashbox door opened in service - Alarm shall be created when the cashbox door is opened on a vehicle
on the road.
e. v) Maintenance Access - Alarm shall be created when any maintenance cover/door of the farebox is opened
when the vehicle is on the road.
f. vi) Farebox out of service - Alarm shall be created whenever a farebox event causes the farebox to be
automatically shut down.
g. vii) Cashbox inserted – if a cashbox has been removed and inserted without being vaulted, an alarm is required.
If a cashbox has been removed from a vehicle on the road and immediately reinserted. The cashbox number
shall be included with the message.
h. viii) Media level below a preset number
K. Data integration shall be made available, open API will be required for Business Intelligence integration.
6. Farebox Self-Test and Diagnostics
A. The farebox shall automatically test all components and functions on every power up. Errors detected during this self-
test function shall be recorded in the farebox transactional data and displayed to the operator on the OCU display.
B. The performance of the farebox shall be continuously monitored during operation, and all errors, exceptions, and
anomalies shall be recorded in the Farebox transactional data reported to the operator on the OCU.
C. All circuits within the farebox shall be designed to permit testing and/or voltage measurement of the various
components/boards through designated test points that are clearly indicated and accessible. If test points are not
provided, the use of extended boards is permissible with CAT approval.
SECTION 2. DRIVER CONTROL UNIT
1. DCU Functionality and Mounting Options:
A. Driver control and operation of the farebox shall be through the use of a Driver Control Unit (DCU). This unit shall provide
all driver operational display and input control functionality necessary to operate the farebox. Design and functionality of
the Driver Control Unit is subject to approval at the Design Review.
B. The DCU shall be integral to the farebox and not require separate mounting, power, or network communications from the
farebox.
C. The DCU shall function to provide all necessary farebox input and display to fully support the operation of the farebox. The
unit shall be designed to function without degradation in the vehicle operating environment, giving consideration to lighting,
temperature, dust, moisture, vibration, and other such conditions.
D. The DCU shall be designed to support driver key entry and information display while functioning in the operating vehicle
environment. Consideration for ergonomic and functional utility shall be inherent in the design, given the requirement to
support the driver population, operating conditions, and driver seating positions. It shall be incumbent upon Contractors to
familiarize themselves with the DCU design requirements.
Page 1127 of 3773
9
E. The DCU shall be readily readable by a driver in lighting conditions ranging from bright sunlight to darkness and by drivers
wearing polarized sunglasses. Readability of the display under adverse operating conditions is a critical requirement. As
specific adverse operating conditions are not definable, it is incumbent upon Contractors to familiarize themselves with the
adverse operation conditions that may be present and shall overcome those conditions. Display back lighting may be
provided if necessary to enhance functionality. Display controls for brightness and contrast shall be included, but they shall
not be capable of being adjusted to make the display not visible.
F. The display shall consist of several functional areas including:
a. Driver Revenue Display
i. The Driver Revenue Display shall minimally consist of a four numeric digits and decimal to
support display of revenue values between $00.00 and $99.99. Display of the "$" is optional and
shall be required only if the display area is utilized for other display information.
b. Driver Information Display
i. The Driver Information Display shall minimally display characters at least as large as that
required by accepted human factors design criteria for persons with 20/20 vision at the distance
and angle as seated drivers would be from the DCU in the installed position on all classes of
vehicles. Characters shall be sized for the most adverse mounting and driver position situation.
G. The DCU shall enable the driver to select from the applicable fare set (including concessionary, route, or time-based fares)
prior to riders depositing cash. Concessionary fares will include at least Adult, Senior / Disabled / Medicare (SDM), and
Youth.
H. The Driver Control Unit shall be operational at any time the farebox is operational. It shall not be necessary or possible to
independently turn on or turn off the Driver Control Unit. When operational, all displays, key functions, and operating
features of the DCU shall be operational and fully functional.
I. The Driver Control Unit shall display operator logon and route information transferred by the CAD/AVL system.
J. The operator shall log-on to the Farebox through the CAD/AVL system.
K. The DCU should have a single sign on to the CAD/AVL system.
L. The Driver Control Unit shall display operator log-on and route information transferred by the CAD/AVL system
M. The bi-directional communication link between the Farebox and the CAD/AVL system will allow the operator to log-off
both CAD/AVL and Farebox systems using either the CAD/AVL or the Farebox DCU. To initiate the log-off procedure
the operator shall press an assigned button combination.
2. Operator Log-on Communication Links:
A. The operator shall log-on to the farebox through the CAD/AVL system.
B. Coordination shall occur between farebox Contractor and CAD/AVL Contractor that proper interface is completed. J-1708
is noted in the following points but may differ depending on outcome of coordination between CAD/AVL and farebox
Contractors.
C. The Contractor shall ensure that the appropriate Society of Automotive Engineers (SAE) J-1708 message structure is
documented, implemented, and tested for this purpose. Communications error detection provided for by J-1708 and
retransmission of damaged messages provided for by SAE J-1587 shall be supported by the proposed interface and tested.
D. The Contractor shall certify that the SAE J-1708 protocol within the farebox is capable of handling all of the messages
transmitted to it without loss of any messages due to capacity constraints from either the farebox hardware or software.
E. The farebox shall have the capability to receive consecutive J-1708 messages separated by the minimum idle time described
in SAE J-1708 (approximately 1.2 milliseconds apart).
F. In the absence of external SAE J-1708 login data from the CAD/AVL system, prior to the farebox entering revenue service,
the operator shall have the ability to log on to the farebox. In this situation, the CAD/AVL system will be activated by the
farebox and the log-on or log-off process shall be established in the CA D/AVL system.
Page 1128 of 3773
10
G. Successful log-on shall require a valid operator ID, and Block-ID. Operator IDs shall be securely maintained at the Base
Computer System and shall be downloaded to the farebox.
H. Optional Smart Card/Employee Id Operator Log In: The farebox shall permit the logon and activation of the farebox using
an optional smart card-based Employee ID. Operator ID may be entered via the keypad as well as using the optional smart
card. This type of successful log on will activate the CAD/AVL system as described above.
I. The log-on information shall be retained in non-volatile memory. If the farebox is rebooted during revenue operation, the
operator or AVL/CAD log-on shall not be required. The log-on information shall be cleared during probe.
J. The farebox shall also support relief operator log-on, supervisor log-on, and manager log-on. Non-revenue service log-on
shall be possible for maintenance and revenue technicians.
K. Provision shall be included to display items entered, to display all entered selections, and to correct any mistaken entry
without re-entering all previous correctly entered selections.
L. At a minimum, the following security levels shall be software configurable:
i) Normal Operator
ii) Supervisor
iii) In training Personnel
iv) Manager
v) Maintenance Technician
vi) Revenue Service Agent
M. Functions and commands requested from operators with insufficient security shall be denied, and a transaction documenting
this denial shall be recorded in the farebox transactional data. Alternatively, the farebox shall only offer such functions that
comply with the permissions for the logged-on user.
N. Upon completion of the log-on process, a log-on record shall be established defining all of the above selections, together
with the date/time stamp.
O. The OCU should have a single sign-on to the CAD/AVL system.
3. Operator Log-off:
A. The bi-directional communication link between the farebox and the CAD/AVL system will allow the operator to log-off
both CAD/AVL and Farebox systems using either the CAD/AVL or the farebox OCU.
B. To initiate the log-off procedure the operator shall press an assigned button combination.
SECTION 3. SECURITY AND ACCESS
1. Security Design
A. The farebox and fare collection system shall be designed in a manner that establishes a direct audit trail between revenue
deposited into the farebox (“registered revenue”) and revenue counted in the money room (“deposited revenue”).
B. The fare collection system shall provide the following functions to support the secure revenue audit trail:
a. Each cashbox shall be delivered with a unique electronic ID resistant to duplication and counterfeiting.
b. The farebox shall read the cashbox electronic ID upon insertion of the cashbox and periodically during revenue
service.
c. The farebox shall record and track all revenue deposited into the cashbox, along with all other transactional detail
information, and shall report this data to the hosted computer system when probed for data during revenue service.
d. The farebox shall be capable of storing no less than thirty (30) days of full revenue and transactional detail
information, without resorting to storing such information in summary form.
e. The cashbox shall close securely and automatically lock prior to removal from the farebox, and the cashbox shall
be designed to prohibit removal from the farebox unless it is in a closed and locked state.
f. Upon removal from the farebox, no revenue within the cashbox shall be visible or accessible.
g. Unlocking of the cashbox to access the revenue shall not be possible without the “cashbox revenue key,” which
shall be available only in the money room or receiver/vaults. Alternative mechanisms for unlocking the cashbox
will be considered as long as they maintain revenue security.
Page 1129 of 3773
11
C. Cash Vaults shall have both a visible and an embedded electronic unique identifier code or serial number. Embedded ID
shall be readable by other components of the fare collection system.
2. Cashbox Access Door Security
A. A set of contacts shall be provided to indicate the cashbox door open. The contacts shall be pre-wired for external
termination. The Contractor shall be responsible for connection to the ACS terminal and for verifying proper operation of
the interface.
B. Cashboxes and cashbox receivers shall have a common cashbox key. If the removal and insertion of a cashbox into the
farebox or cashbox receiver is awkward and/or lends itself to damaging or misaligning the cashbox, farebox, cashbox
receiver or lock/key mechanisms, the system shall be rejected. Alternative vaulting concepts, which provide the same
security and similar access controls, shall be considered.
C. Lock combinations and keys for all identical functions shall be keyed alike. Different combinations shall be provided for
each function. Keys shall be separately serialized to permit easy insertion into the key control program.
D. Cashbox shall lock into farebox housing with an electronically activated lock to prevent unauthorized removal.
E. Cashbox must securely close and automatically lock prior to removal from the farebox.
F. Access control card based farebox security and access system for revenue collection and maintenance is a preferred method.
SECTION 4. DATA COLLECTION
1. Data Collection:
A. Electronic logic incorporated in the farebox shall receive value signals from the coin and currency bill module. The
electronic logic shall accumulate and store the amounts in an electronic register and such amounts shall be displayed on a
display available to the driver. The accumulated fares shall be recorded so that the total value received by the farebox can
be determined since the farebox was last interrogated and the total value received by the farebox since installation or
clearing of the farebox memory. Totals shall be reported for all cash revenues, token unit count and bills.
B. The farebox shall record, store, maintain, and upload to the back office an individual transaction representing a record of
fare collection operational activity. All transactions shall be date/time stamped and shall be assigned an incrementing record
sequence number unique to the farebox. Transactions shall be made of all significant activity, including but not limited to
the following:
a. Cash fare payments
b. Key fare payment entry (e.g., classification or tally)
c. Key entry operations (e.g., bill override, card issue)
d. Driver log• on, log• off, and log changes
e. Driver ID
f. Route
g. Run
h. Trip
i. Bus Stop
j. Direction
k. Fare Set
l. Farebox power on/off
m. Coin by-pass activation or clear
n. Cashbox threshold level event
o. Data storage threshold event
p. Data interrogation event
q. Electronic key event
r. Cashbox door open and close events
s. Cashbox removal and insertion events
t. Security events
u. Maintenance status events.
v. Maintenance access.
w. Maintenance/jam clear access
Page 1130 of 3773
12
C. In addition to transaction records, the farebox and/or the back office shall maintain aggregate data records and counts of
other system activity, including but not limited to:
a. Coins validated.
b. Coins rejected.
c. Bills validated.
d. Bills rejected.
e. MRU reads.
f. MRU misreads.
g. CSCP read.
h. CSCP misreads.
i. CSCP encode.
j. CSCP verify fail.
D. Exchange of configuration and revenue data with the farebox shall occur over the onboard mobile access router and a
garage wireless network. Specifics of data exchange shall be defined during design review. The specific data transfer
method used may vary, but the functional and operating requirements are constant. The wireless data transfer probing
process should maximize convenience and reliability while minimizing labor and time required for accomplishing this
essential task. The data transfer process must provide maximum security and involve as minimal intervention by Collier
Area Transit personnel as possible. Data upload should begin automatically as buses return to Collier Area Transit
designated probing area and when the farebox is within range of a wireless access point. Currently, there are routers on
every single bus. We want every bus to have access to connect to the wireless access point, which should be provided and
maintained by the contractor to their back office.
a. The average time to download/upload data shall be executed within a reasonable timeframe for all
vehicles. The wireless data transfer solution shall have the capability of uploading farebox configuration
data supporting farebox functionality. Contractor is required for necessary equipment for wireless
network.
E. Farebox interrogation and revenue collection authorization shall accomplish the following functions:
a. The data transfer action shall be authorized only when wireless communication has been activated in the
approved manner. Portable or wireless data transfer systems shall be designed to ensure functionality only
in an authorized or approved manner.
b. The farebox shall initiate contact with the back office and shall exchange identification data related to
farebox and cashbox serial number.
c. Farebox date, time shall be compared to the back-office date and time, and the back-office date and time
downloaded to the farebox.
d. All data stored by the farebox since the last upload shall be uploaded to the back office during data
exchange. This shall include cash transactions, alarms, warning alerts, bypass activation, use of electronic
keys, use of portable data units and other pertinent data.
e. The data system shall verify that only one set of data has been received from each farebox; where duplicate
data has been received, the data system shall reconcile the duplicate data.
f. The back office shall download all information scheduled to be downloaded to the farebox, including but
not limited to fare tables, authorized route/run/trip and driver parameters, and other specific parameters
and data.
g. The farebox shall not transmit the appropriate command to unlock the cashbox access door until all data
exchange is completed and verified and proper action has been taken by the vault puller to open the
cashbox door. A tone (warble) shall be sounded to alert revenue collection personnel to remove and empty
or replace the cashbox.
h. The cashbox removed event shall generate a transaction that includes the date and time and cashbox ID
number of the event.
i. The cashbox insertion and locking of the access door shall generate a transaction that includes the date
and time and cashbox ID number of the event to be transmitted during the next interrogation and transfer
of data.
j. The total time required to complete an interrogation of the farebox, complete a full exchange transaction
data, and authorize release of the cashbox access door shall not exceed 5 seconds. Time required to
exchange other data with the back office shall be established during design.
F. The back office shall download into the farebox memory the current fares for all the preset fare tables, the valid presets
for current routes, associated push button values, the function of each driver push button registration assignments, and
other such information as required by the farebox.
SECTION 5. REVENUE COLLECTION SYSTEM
Page 1131 of 3773
13
1. Revenue Collection System:
A. The Revenue Collection Receiver structure shall be free standing. Hardware shall also be supplied as part of the receiver
that shall allow application of a hasp lock. Alternatively, a separate key operated lock shall be provided on the receiver door
to permit the door to be locked closed. Under a “door locked” condition and with no cashbox in the receiver the receiver
shall be inoperative.
B. The thickness of the metal used in the receiver, its enclosure, and the vault structure shall be such as to serve for the intended
usage and security of collected revenues. The equipment shall be constructed of noncorroding materials, plated materials or
shall be cleaned, prepared, and painted with weather resistant enamel. The front surface, door and entire cavity of the receiver
shall be made of stainless steel for corrosion protection and wear.
C. Appropriate maintenance access apertures shall also be provided to aid in the maintenance of the Revenue Collection
System. Each aperture provided shall be keyed alike. All locks and keys for the Revenue Collection System shall be secured
with a high security locking system.
D. Each separate key and lock employed in the Revenue Collection System shall be different, except for the maintenance
apertures. The keys and locks employed in the Revenue Collection System shall be different from those employed elsewhere
in the Fare Collection System.
E. The Revenue Collection Vault shall be fitted with mechanical interlocks and/or electronic sensors to sense the presence of
a properly seated and open Mobile Safe. These interlocks shall be connected to the receiver above so that if the interlocks
are not satisfied, the receiver shall not be able to accept and process a cashbox. The interior cavity for the Revenue Collection
Vault shall have durable guide rails or plates to guide and position the Mobile Safe for insertion or removal.
F. The Revenue Collection Vault shall have provisions internal to the structure for permanently mounting the vault to a concrete
pad or floor by a minimum of four anchor bolts for each vault.
G. As revenue is received in the Revenue Collection Vault the data shall be uploaded in real time to the back office and visible
in the back-office interface including total collected and counts of all currency and coins.
H. To enhance the security and safety of our fare collection system, we are seeking a solution that includes the capability to
remotely unlock the cashbox within each farebox. Specifically, the desired functionality is that the cashbox will only be
accessible for removal when a secure signal is received by the farebox from a wireless device. Potential contractors should
provide a detailed description of their proposed solution, including any relevant technical specifications and implementation
requirements.
I. The revenue deposited into the Cashbox in each farebox shall be transferred manually to a stationary vault. The stationary
vault will consist of a Cashbox Receiver, secure vault housing and a Mobile Bin.
J. The Cashbox Receiver shall accept a Cashbox and by means of a mechanism operated in a secure manner. The Receiver
shall open the Cashbox and discharge its contents (coins and bills) into separate compartments in the Mobile Bin located
below the Receiver.
K. The Mobile Bin shall accept the separated coins and bills from the Receiver and store them in separate compartments. The
Mobile Bin shall be removable from the vault structure but only in a closed and locked condition. The Mobile Bin structure
and design shall permit lifting by a forklift for transport to the money counting room.
L. The vault structure shall be permanently installed. The vault structure and appurtenances shall be installed in the existing
vault room. The Contractor shall specify the installation, structural, environmental, and power requirements to operate and
maintain the vault system. The specification shall be detailed for Collier Area Transit assessment of the impact of the
Contractors vault system on cost and resources. The specification shall be quantitative and delineate construction and
installation details.
M. Audit Vault shall be configured with two separate interior compartments, one for coins and tokens and the other for U.S.
bills. During the revenue transfer process, the coins from the Cashbox will go into the coin compartment while the bills
and tickets will remain separated from coins and go into the bills compartment.
2. Stationary Vault
A. The cashbox in each farebox shall be ‘unlocked’ for removal when the farebox receives and electronic code from a
probe device.
Page 1132 of 3773
14
B. The revenue deposited into the Cashbox in each farebox shall be transferred manually to a stationary vault. The
stationary vault will consist of a Cashbox Receiver, secure vault housing and a Mobile Bin.
C. The Cashbox Receiver shall accept a Cashbox and by means of a mechanism operated in a secure manner. The Receiver
shall open the Cashbox and discharge its contents (coins and bills) into separate compartments in the Mobile Bin located
below the Receiver.
D. The Mobile Bin shall accept the separated coins and bills from the Receiver and store them in separate compartments.
The Mobile Bin shall be removable from the vault structure but only in a closed and locked condition. The Mobile Bin
structure and design shall permit lifting by a forklift for transport to the money counting room.
E. The vault structure shall be permanently installed. The vault structure and appurtenances shall be installed in the existing
vault room. The Contractor shall specify the installation, structural, environmental, and power requirements to operate
and maintain the vault system. The specification shall be detailed for CAT assessment of the impact of the Contractors
vault system on cost and resources. The specification shall be quantitative and delineate construction and installation
details.
3. Cashbox Receiver
A. The Cashbox Receiver shall have a mechanism at the top of the vault into which a Cashbox is inserted. The Cashbox shall
be accepted by the Receiver in one and only one orientation for revenue transfer. The Receiver shall have a heavy interlocked
door and designed so that the Cashbox is positively guided in and out. Once the door is closed and locked the Cashbox
contents shall be securely transferred into the dual compartments of the vault. The Receiver door shall remain locked until
the revenue transfer process is complete. During the transfer process, neither the interior of the cashbox nor the vault shall
be visible, nor shall access be allowed.
B. The revenue transfer process shall be manual in operation, require no electrical devices or components. In the event of power
or battery failure, it shall be possible to continue transfer revenue in a secure manner.
C. The revenue transfer process shall take no longer than ten (10) seconds, as measured from the time the cashbox receiver
door is closed until the door is opened.
D. Keys shall not be required to operate the Cashbox Receiver in normal revenue transfer use. All engagements and/or
alignments shall be positive and automatic.
E. All Cashbox Receivers shall be of the same dimensions and shall accept all Cashboxes supplied under this contract.
4. Vault Housing
A. All parts of the vault shall be made of non-corroding or plated materials or shall have been cleaned, prepared, and painted
with weather resistant coating. The front surface, door and interior of the Receiver shall be stainless steel for corrosion
resistance and wear. All doors on the vault and Receiver shall be structurally rigid with heavy-duty hinges, with high security
locks.
B. The interior of the vault shall have guide rails and plates to guide and correctly position the Mobile Bin upon insertion. The
vault shall have mechanical interlocks that sense the presence of a Mobile Bin properly seated and ready for operation. If
the interlocks are not satisfied, the Cashbox Receiver will not accept or process a Cashbox.
5. Mobile Bins
A. The Mobile Bin shall be configured with two separate interior compartments, one for coins and tokens and the other for U.S.
bills. During the revenue transfer process, the coins from the Cashbox will go into the coin compartment while the bills and
tickets will remain separated from coins and go into the bills compartment.
B. The Mobile Bin will have two large revenue discharge doors, one for coins and one for bills. Each door will be secured by
a high-quality security lock. Coins will be discharged from the bin by gravity using sloped stainless-steel bottom surfaces
to aid in the process. Revenue discharge doors and openings will be securely designed to prevent exposure of revenue except
when opened in an authorized manner.
C. The Mobile Bin shall have capacity to hold not less than a total of 10,000 in "street" money bills and not less than a total of
10,000 in coin.
Page 1133 of 3773
15
D. All of Mobile Bins provided under this contract shall be identical in manufacture and dimensions and shall be
interchangeable between any of the Cashbox Receivers and vault housing. The Contractor shall submit braking system
design for approval at the Preliminary Design Review.
SECTION 6. BACK OFFICE
1. Requirement
A. The back office shall consist of the application programs, system functionality, and operating capability to generate
responses, print reports, compile, and generate files, and make data available in response to user input and programmatic
requests against data maintained within the back office. It shall include the functional capability to access available data and
data elements, summarize and calculate the data, and format output as appropriate and necessary to generate the specified
user responses.
B. Collier Area Transit shall not host the back office. The system could be offered as Software as a Service or hosted through
a “cloud” based hosting service (AWS, Rackspace, etc.) subject to approval by Collier Area Transit. All transactional data
shall be owned and accessible by Collier Area Transit.
C. The back-office interface shall be achieved through a standard web browser, using appropriate user authentication.
D. The fare tables shall be easy to view, review, and test when entering during creation of initial tables and any future fare
updates. This shall be addressed during design and testing.
E. The System shall allow the Collier Area Transit to view and compare draft fare sets and changes to active and pending fare
sets by Collier Area Transit and regionally, by sales channel, and by fare product.
F. The System shall have the ability to roll back to a previously used fare set.
G. All fare product configurations shall be able to be performed by the Collier Area Transit, as well as by the Contractor during
implementation and throughout the warranty and software maintenance agreement terms.
H. The System shall allow fare set changes on a frequent, including daily, basis without regard to additional pending changes.
For example, Collier Area Transit could change fare rules regardless of other Agency changes that are pending.
I. The System shall be able to manage, store, and deploy an active fare set and at least two (2) pending fare sets. An active fare
set shall become effective immediately upon publication. Pending fare sets shall be able to be activated manually, or
automatically based on a future activation date configured.
J. Collier Area Transit intends to use Power BI for their primary reporting needs. Data shall be held in commercial off the shelf
relational database system and shall be accessible by standard commercial SQL query tools; Contractor shall provide Collier
Area Transit with a full data dictionary and schema and the ability to directly query the data.
K. The back office shall provide full capability to control, define, manage, and monitor farebox operations. This shall include
functions related to the management of:
a. Fare tables
b. Service Codes
c. System Log On including, employee number, route number, run number, and trip (block) number
maintenance.
d. Revenue collection operations, security, and access
e. Back Office access, user control, system operation, system configuration
L. The back office shall have the capability to manage fare tables maintained in the fareboxes. Fare table management
functionality shall also include the control and management of the fare table download process to the fareboxes.
2. Fare Structure
The fare payment system shall be able to support a variety of fare structure configurations at system launch and in the future.
Fare structure includes the supported fare policies, fare media, fare products, and distribution channels through which customers
purchase fare media and products. The fare structure shall be configurable by Collier Area Transit and the Contractor and
designed to create a simple, unified system that enables interoperability across current and future transit modes without additional
development.
Page 1134 of 3773
16
Collier Area Transit Mobile Ticketing Contractor is Masabi and the Farebox system will be required to be incorporated and
integrated into the Mobile Ticketing system to retrieve data. As part of our fare collection system, we require a solution t hat
allows the farebox to print a day pass that can be validated by Masabi's validator. The day pass should include all relevant
information required for validation, such as the date and time of issuance. Contractors are encouraged to propose a comprehensive
solution that meets this requirement, including any necessary hardware, software, and integration with Masabi's validator.
Proposals should include detailed technical specifications, implementation timelines, and any associated costs or fees.
A. Full capability shall be provided to manage the fare table maintenance process, including but not limited to, creating
fare table elements, changing, and deleting elements, and control of the fare table transmission (download) process.
B. Each fare table (table) shall include the capability to define, set, control, and manage the following system parameters:
a. Individual base fare amount ($0.00 - $99.99)
b. Key attributes – tally, tally/clear, or value increment
c. Non-cash (ticket/token/pass) acceptance parameters and attributes
d. Transfer processing attributes and operating parameters
e. Peak period time definitions
f. Fare table effective/discontinue dates.
g. Service codes
Below is the fare table the vendor is expected to manage through its system.
Service Category Full Fare Reduced
Fare
One-way Fare $2.00 $1.00
Children 5 years of age and younger Free Free
Marco Express – One-way Fare $3.00 $1.50
Transfers Free Free
Day Passes $3.00 $1.50
3. Back Office Reports
A. The following standard reports shall be available from the back office. Equivalent reports that provide the same
information may alternatively be provided. All reports shall include Collier Area Transit’s operating name, the date or
period for which data is reported and the date/time on which the report is generated in a consistent format or data block
area.
a. The farebox reporting system shall provide the capability to query the system database to produce reports for
auditing, revenue, media control, planning, fare management information, maintenance, and other similar
requirements.
b. The Coin Dispensing System (CDS) shall provide one or more reports to indicate the software and fare table
versions in effect on each device, including date of activation, based on events reported by the devices. Such
reports shall also indicate successful downloads of software and fare tables that are pending activation, and the
date of their successful download.
c. To the extent possible, the output format of all queries and reports shall be of similar style. Each report and
query shall produce data in tabular format with each column clearly titled on each page. Each row of output
data (excluding column titles) shall be consecutively numbered.
d. All reports shall provide users with the ability to sort the report rows by any column, user- selectable in
ascending or descending order.
e. All reports shall include the following information:
i. Title of the report
ii. Date and time the report was generated.
iii. Complete list of input parameters and sorting keys used to create the report.
f. It shall also be possible for the user to select query and report output in a form that is exportable to other
applications, such as spreadsheets and graphical report presentations programs.
g. The Contractor shall provide several queries and reports at time of delivery. The prepared queries and reports
shall be presented in a menu form for selection at any time. Each query and report shall have access permissions
assigned to limit availability to those users authorized to view data presented by the query or report.
h. Each prepared query and report shall also be capable of being automatically processed at predetermined dates,
times, and frequencies. It shall be possible for CAT to identify reports to be run daily, weekly (e.g., every
Wednesday), monthly (i.e., the first day, last day, or any specific day of each month), quarterly, and so on.
i. Reports of general nature and those that include a wide variety of input fields shall be configurable to narrow
the scope of the report. For example, using the menu-driven input forms, it shall be possible to limit a general
Page 1135 of 3773
17
query or report that provides total sales revenues to only sales associated with the Mobile Ticketing application.
j. Reports AD-Hoc Report. Shall provide the ability to create ad-hoc reports, all fields shall be available for the
purpose of creating reports.
B. At the Final Design Review, Contractor shall provide samples of all reports available from the system Collier Area
Transit will determine if any additional reports may be needed. Customized reporting will be done through PowerBI
accessing the back-office database directly using standard SQL queries.
C. It shall be possible set filters for all detail reports so that the data system shall provide information on one or more
specific buses, service codes, routes, runs, cashboxes, drivers and/or dates as is appropriate to the particular report.
Examples include but are not limited to:
a. Individual Farebox/Bus Reports
b. Route/Run Detail Reports
c. Cashbox Reports
d. Driver History Reports
4. Fare Transfers
A. The Fare Collection System shall support the granting of a transfer fare credit for a boarding (e.g., fare payment) that
occurs within a defined time period of another boarding. The transfer period (e.g., time during which a boarding is
eligible for a transfer) shall be configurable.
B. Transfers shall be supported for customers that pay fares using stored value and trip-based pass products.
SECTION 7. OPERATING ENVIRONMENT
6. Requirement
A. All elements of the system shall be designed, constructed, and tested to function properly in the existing Collier Area Transit
environment. The equipment shall be designed and tested to withstand structure- borne stresses and vibrations caused by the
motion of buses and daily customer usage and that components shall be designed, built, and tested for the harsh shock and
vibration operating environment on the vehicle.
B. In the event of a loss of electrical power, field equipment shall complete any transaction in process, retain all data, and
shutdown in an orderly manner. The equipment shall return to full operational status after a power failure without manual
intervention or adversely affecting the integrity of stored data.
C. All equipment shall be protected against damage or data loss under the following conditions:
a. Voltage fluctuations
b. Reverse polarity of the input voltage
c. Temporary voltage variations (0 to 50 V)
d. Over current draw
e. Stray currents
D. The onboard equipment provided by the Contractor shall be able to operate and not suffer any degradation in performance
under the following environmental conditions:
a. Storage temperature: - 22° to +150°F
b. Operating temperature: - 15°F to 140°F ambient
c. Thermal shock: Up to 50 degrees F in 1 hour, non• condensing
d. Relative humidity: 5 - 100%, non-condensing
e. Airborne dust: up to 180 micrograms per cubic meter, with iron and salt particles
f. Sunlight: direct sunlight, radiation loading of up to 789J/sec/m2
g. Inclination: 0° to 20° off vertical
h. Rainfall: 10 inches over 12 hours
i. Water/solvents: IEC529 to level IP54 or equivalent
j. Pollution: Fog (e.g., sulfur dioxide-laden air) and other forms of native air pollution
k. Other operational conditions: water spray, industrial cleaning solvents, and mud on system components from
cleaning vehicle floors and walls.
E. The onboard equipment shall be tested and certified to operate under the environmental conditions specified in Society of
Automotive Engineers (SAE) J1455 and all standards contained therein.
Page 1136 of 3773
18
F. Onboard equipment, including fareboxes and Driver Control Units, shall be designed to operate reliably from a vehicle’s
direct current power source, which consists of both 12 volts or 24 volts of direct current (VDC). Collier Area Transit prefers
that the fareboxes use the 24VDC circuit.
G. System equipment shall be equipped with Ground Fault Circuit Interrupter (GFCI) circuit breakers, which include a “push
to test” button, visible indication of a tripped condition, and ability to detect an earth leakage current of approximately 5
milliamperes in accordance with UL 1053 and the Florida Public Service Commission (FPSC) standards.
H. The connection between the front-end devices and back office shall be over a routable IP network. Where required, the
connections shall be secured using Transport Layer Security (TLS) and strong encryption, such as Triple Data Encryption
Algorithm (TDEA) or Advanced Encryption Standard (AES). All data sent via the internet shall be TLS encrypted using the
Hypertext Transfer Protocol Secure (HTTPS) protocol. Any IP communications must not preclude components of the system
utilizing IPv6.
I. The onboard modules shall be able to communicate over Ethernet and Transmission Control Protocol/Internet Protocol
(TCP/IP), at a minimum. The communication interface to be used shall be determined during design review and must provide
adequate support for all system capabilities and integrations. Additional communication standards may be used such as SAE
Vehicle communications standards (such as J1708/1939), Bluetooth, USB, etc.
J. The fareboxes and/or DCUs shall have Wi-Fi capabilities for communications with the back office while in the garage.
K. The farebox and DCU shall connect to the mobile access router via Ethernet.
L. The farebox and DCU shall connect with onboard mobile network to access the back-office system.
7. Standards
A. Contractor shall comply with all applicable standards, including federal, state, and local, along with federal ADA
requirements and industry standards for the fareboxes and their installation and maintenance.
B. All Contractor provided equipment shall be free from safety hazards and shall be designed to comply with relevant
Underwriter’s Laboratory (UL) Standards. All interior and exterior surfaces shall be free from sharp edges, protrusions,
exposed wires, or other hazards.
C. Contractor shall design the System to be compliant with relevant standards, laws, and regulations to ensure that the System:
a. Presents no safety hazards for customers and Collier Area Transit employees.
b. Shall withstand the rigors of the environments in which the equipment shall be installed, and the public use to
which it shall be subjected.
c. Provides for the secure storage and transmittal of data.
d. Is designed using state-of-the-art methods to maximize quality.
e. Satisfies federal, state, and other requirements for ergonomics and usability.
D. Applicable codes, laws, ordinances, statutes, standards, rules, and regulations include, but are not be limited to, the list
below. The latest revisions in effect at the time of Final System Acceptance shall apply.
a. Americans with Disabilities Act (ADA)
b. Americans with Disabilities Act Accessibility Guidelines (ADAAG)
c. Advanced Encryption Standard
d. AN Contractor X9.24, Financial Services Retail Key Management
e. European Norm EN55022, Emissions standards for CE marking
f. European Norm EN55024, Immunity standards for CE marking
g. FCC Part 15 Class B – Radio Frequency Devices
h. FIPS 140-2
i. IEEE 802.11 a/b/g/n standard for wireless data communications
j. IEEE 802.11 i standard for wireless data network security
k. IEEE 802.11-2016
l. International Electrotechnical Commission Standard 529 (IEC529)
m. ISO 9001
n. National Electrical Code (NFPA 70)
o. National Electrical Manufacturers Association Publication 250-2003
p. National Electrical Safety Code (AN Contractor C2)
q. National Fire Protection Association (NFPA) 130
r. Occupational Safety and Health Administration (OSHA)
s. Society of Automotive Engineers SAE J1113-13 Electrostatic Discharge
Page 1137 of 3773
19
t. Society of Automotive Engineers SAE J1455 Vibration and Shock
u. UL Standard 60950, “Information Technology Equipment – Safety”
E. In the case of conflict between the provisions of codes, laws, ordinances, statutes, standards, rules, and regulations, the more
stringent requirement shall apply.
8. Testing
A. Contractor shall develop a Testing Plan for the entire project. The Testing Plan should address each level of testing and be
incorporated into the design reviews. The Testing Plan should include device and network integration testing as part of
component development following an Agile software development lifecycle. The successful completion of the applicable
design reviews shall be a prerequisite to proceeding with testing. Contractor shall submit a Testing Plan for Collier Area
Transit ’s review and acceptance, to be used in connection with all inspections and tests. The Testing Plan shall include a
detailed schedule indicating the sequence of each test and where and when each test shall take place.
B. All system components and subsystems shall be tested individually and in integrated environments to make sure that they
meet all technical and functional capabilities in the specifications.
C. Sixty (60) days prior to the commencement of testing, Contractor shall deliver a final test plan to Collier Area Transit for
review; modification, if necessary; and approval.
D. Contractor shall be responsible for a test plan which shall be approved by Collier Area Transit. Test phases shall include
factory testing of the on-board equipment, integration testing in both lab and field environments and acceptance testing. The
final system acceptance tests shall begin on full system launch and last for at least six months until final system acceptance
is granted.
E. All tests and inspections shall be documented by Contractor and monitored and signed off by Collier Area Transit or their
representatives.
F. Testing shall consist of two phases, Unit Testing and Integration Testing.
G. The purpose of unit testing is to demonstrate in a controlled laboratory environment that each of the system components and
associated software furnished by Contractor meets all capabilities through final design, prior to full system integration.
Successful completion of component-level software development, and demonstration of production equipment on Collier
Area Transit premises are prerequisites.
H. Unit testing shall include the following phases or their equivalents:
a. First Article Inspection - First production unit
b. Factory Acceptance Testing - Human interface and environmental requirements
c. Production Acceptance - Production unit properly constructed.
d. Functional Unit Testing - Each component in a lab
I. When unit testing has been successfully completed, Contractor shall conduct integration testing in which all devices and
back-office applications are exercised. Integration testing is needed to confirm that when installed, the fully integrated
system shall perform, operate, and communicate as required in a controlled laboratory environment.
a. With successful completion and approval of integration testing, all software and configuration files shall be
“frozen,” and Contractor shall make no changes without Collier Area Transit authorization. Upon Collier Area
Transit approval, field testing of the system components may commence.
J. Integration testing shall include the following phases or their equivalents:
a. System Integration Testing - Integrated system in lab
b. Field Integration Testing - Integrated system in field
c. Pilot Testing - Test installed equipment in operation
d. Acceptance Testing - Acceptance of the system following launch.
K. Contractor shall conduct all field testing, including beta, friendly user and soft rollout using the production system.
L. Acceptance testing is the final phase of testing. Acceptance testing will be performed in the production environment with
all components, subsystems, and third-party networks completely functional, operational, online, and in service. Following
the completion of any acceptance testing, Contractor shall provide all testing data, reports, and other testing information to
Collier Area Transit for review and approval.
M. The pilot shall not commence until Field Integration Testing (FIT) has been approved. Pilot testing can commence before
Page 1138 of 3773
20
installation is complete.
N. The pilot shall continue for its scheduled duration unless a critical failure or failures cause suspension of the pilot. When a
critical failure has been resolved, the pilot shall resume for a duration determined by Collier Area Transit.
O. System Acceptance Test (SAT) shall commence upon successful completion of the pilot and 100% of the field equipment
has been installed. SAT shall be comprised of three consecutive 30-day periods in which all system components must meet
or exceed all system performance requirements. The acceptance test plan shall describe in detail how Contractor shall
measure and report on each of the performance requirements throughout System Acceptance Test (SAT).
P. If the performance requirements defined in these specifications are not attained during any one of the 30-day periods, the
System Acceptance Test (SAT) duration may be extended until all performance requirements are met during an agreed-upon
duration.
Q. Contractor shall be responsible to maintain a complete log of all First Article Tests conducted under this Article, showing
each test conducted and results. This log shall be submitted to Collier Area Transit at conclusion of the First Article Test for
review and approval. Results not meeting specification requirements are to be fully documented and explained by the
Contractor and a plan for corrective action submit ted. Collier Area Transit may delay delivery of any equipment until First
Article Test procedures are successfully completed and documented.
R. Functional Test
a. The purpose of this test is to demonstrate that for each item of equipment the functions specified throughout this
document, including all limiting conditions, are met. Each equipment shall be required to execute all hardware and
software functions, as detailed in these specifications, and meet the performance criteria requirements. The
procedures for handling maintenance (troubleshooting, fixing faults, etc.) and service functions (replacing paper,
emptying cashboxes, extracting data, etc.) shall also be demonstrated.
b. Each test conducted shall be repeated a minimum of three times prior to confirming success or failure. Each
equipment shall have passed the functional test before the environmental tests are started.
c. The contractor shall be responsible for developing a functional test procedure that satisfactorily demonstrates all
equipment functions, including Ethernet or J-1708/l587 compliance, and shall submit this test procedure to Collier
Area Transit for approval at the Final Design Review.
S. Maintainability Test
a. The contractor shall conduct a maintainability test of the equipment. The purpose of this test is to demonstrate that
each of the equipment types tested conforms to the specified maintainability requirements. This will be
accomplished by introducing faults into the equipment and then measuring the time required for a technician to
correct the fault.
b. At the Final Design Review the Contractor shall submit to Collier Area Transit a list of the faults to be introduced
into the equipment. The list of faults shall represent at least 100 known failure mode for each unit of equipment.
Next to each fault, the contractor shall identify a reasonable time limit for repair performed by an average
technician, based on field experience with the equipment. Collier Area Transit must approve this list prior to
conducting the maintainability test.
c. The test shall be conducted in the following steps:
i. The contractor shall provide multiple units of each type of equipment and introduce failed components,
maladjustments, and incorrect settings into the equipment. The simulated failures shall be introduced in
proportion to their expected failure rate.
ii. The contractor's maintenance personnel shall be unaware of the simulated failures and shall be assigned
to repair the equipment.
iii. The repair times shall be recorded and compared with the advance list provided by the contractor.
iv. All results will be reviewed by Collier Area Transit.
T. Equipment Interface Test
a. The Contractor shall perform the Equipment Interface Test. The purpose of this test is to demonstrate that all units
of fare collection equipment operate correctly together as a system and that all hardware, software and data
transmission functions are as specified.
Page 1139 of 3773
21
b. One hundred fares, including a selection of pass, ticket, coin, and bill fares shall be entered into the fare collection
system. The operations of the complete system shall then be demonstrated including:
i. Exchange of data between the CAD/AVL system and the Farebox
ii. Wi-Fi uploading of data to the base Computer system.
iii. Comparison of transmitted data to actual data entered.
iv. Reporting all data in fully transactional format, suitable for database reporting and summarization
v. Emptying of the cashbox and operations of all related hardware functions
U. Environmental Test
a. Contractor shall provide certification to Collier Area Transit that all equipment has been subjected to environmental
testing that proves the suitability of the system or subsystem to the environment in which it is intended to operate.
This shall include temperature, vibration, shock, electromagnetic interference, and radiated electromagnetic energy.
Contractor shall supply certification for these tests to include test protocols and procedures, actual test data
documenting the appropriate tests performed on the equipment and having successfully tested the equipment in
conditions that simulate or duplicate transit in-service conditions. The Contractor shall supply to Collier Area
Transit the name, address and phone number of all testing facilities used to perform such testing.
V. Installation and Acceptance Test
a. Before any equipment is permitted to go into revenue service, a functional test shall be conducted on all installed
equipment. This test shall be performed by the Contractor as part of the installation procedure. The installation
acceptance test shall be a sequential operation of all fare collection and processing functions on board the bus.
b. The Contractor shall submit a plan for the Installation Acceptance Test at the Final Design Review. Satisfactory
performance of the installation acceptance tests shall be documented by the Contractor and approved by Collier
Area Transit.
W. Pilot Testing by Collier Area Transit
a. At Final Design Review, Collier Area Transit will submit plans to conduct a Pilot installation acceptance test.
b. An initial pilot test will consist first of a ‘mini fleet’, a Collier Area Transit approved quantity of installations, no
less than 1 bus per vehicle series.
c. Upon successful completion of the mini fleet test, all equipment including all fareboxes and associated equipment,
as well as the Data System and the Central Computer System shall be installed and tested at that location.
d. Determination of the administration, schedule, duration, acceptance criteria, and actions upon failure for the pilot
test will be made by Collier Area Transit and the Contractor at Final Design Review.
e. Equipment shall be tested by Collier Area Transit to ensure that it is compliant with the specifications and performs
in an acceptable manger.
f. After successful completion of the ‘mini-fleet’ test, the Contractor will be given clearance to begin installation of
the remaining buses at the pilot division.
g. Upon successful completion of testing at the pilot division, the Contractor will be given clearance to begin
installation and testing at the next division.
h. Failure at any level during the pilot test will require the Contractor to make corrections or adjustments to the
equipment, after which pilot testing will start over.
i. Payments tied to pilot testing will be withheld until successful completion of testing.
j. Contractor shall be required to complete all training at the division prior to initiation of acceptance testing.
X. Final Acceptance
a. Final Acceptance will occur upon acceptance by Collier Area Transit of all critical items, including but not limited
to Collier Area Transit verified successful operations of all delivered farebox equipment, Collier Area Transit
approved documentation, and training. Collier Area Transit approved acceptance criteria will be defined by the
time of Final Design Review.
Page 1140 of 3773
22
9. Installation
A. Contractor shall be responsible for installation of all components of the system including fareboxes and revenue collection
equipment used for probing and vaulting in the garages. The Contractor shall be responsible for removal and disposition of
old farebox and revenue handling equipment. Disposal of equipment shall be completed per COLLIER AREA TRANSIT
guidelines. The prototypes for each fleet type and the design for installation of garage equipment shall be approved in design
review. Installation documents shall be developed for each vehicle type and shall be approved prior to start of installation.
Documentation shall include wiring diagrams, location of components, hardware used for installation, process for
installation, schedule for installation. These designs do not include the preconstructed pad or cable connections which will
be provided to Contractor.
B. Contractor shall prototype installations for on board equipment installations for all fleet types.
C. Contractor shall specify, following prototyping, the physical interfaces for network communications and power for on board
equipment for all fleet types. Commonality is desirable.
D. Contractor shall be responsible for supplying any custom hardware required for on board equipment installation for all fleet
types in sufficient quantities to install readers on all vehicles.
E. Contractor shall provide a Draft Installation Plan for review and approval at the Farebox Preliminary Design review.
Contractor shall submit the Final Installation Plan for COLLIER AREA TRANSIT approval at the Farebox Final Design
Review.
F. This Plan shall include, but not limited to the following:
a. Identification of required pit space and work area.
b. Service requirements to support the installation rate.
c. Placement of all farebox system equipment on the bus
d. Drawings for each bus class
e. Schematics for system and for bus interface and any connections
f. Detail handrail modification for each bus type as required.
g. Detail wiring location, size, identification, and clamping
h. Detail power pick up location and circuit breaker locations
i. Detail cabling requirements
j. Detail repair method of existing farebox mounting and cable holes. This method shall ensure the repaired area is
impervious to entry of water, fuel, other contaminants.
k. An installation test procedure for ensuring all functions, tickets, vaulting, cashbox operation operate correctly prior
to acceptance for revenue service.
l. Process for removal of old farebox and revenue handling equipment
m. Process for disposition of old farebox and revenue handling equipment
n. Installation process
o. Process to ensure proper bus numbers, lock codes, fare tables and other information as required is downloaded prior
to release for revenue service.
G. Contractor shall utilize existing DC electrical power available on Collier Area Transit vehicles and AC electrical power on
the property. Contractor shall supply any electrical equipment necessary to utilize existing voltages. If existing power
arrangements are unsatisfactory, Contractor must propose alterations. At minimum, Collier Area Transit will supply a 120
VAC, 60 Hz power source within 200 feet of the Revenue Collection System. Contractor to use solder and heat shrink
insulation for all wire connections.
H. Contractor shall provide a description of proposed installation plans by class of vehicle at the Farebox Preliminary Design
Review for approval, which in general shall be in the same location as the previous farebox. Contractor shall provide a
complete description of the final installation plan for each class of vehicle, including descriptive drawings, location of drilled
holes, power feeds, and data feeds at the Farebox Final Design Review
I. The plan shall include provisions for parallel fare collection process to support the existing system until the installation is
completed. This shall include a method for handling individual vehicle and garage operations as well as full system support
of both the present and newly installed system.
J. It is incumbent upon Contractor to identify at the farebox Preliminary Design Review (FPDR) and to confirm at the Farebox
Final Design Review (FFDR) any requirement to relocate, reposition, remove, or otherwise modify vehicle handrails, or
equipment to accommodate installation of the farebox equipment. Contractor shall inspect a sampling of each vehicle type
to verify the capability of the vehicle flooring and structure to support the farebox installation and shall advise Collier Area
Page 1141 of 3773
23
Transit if changes are required as part of the FPDR and FFDR submittal. The information to be supplied at farebox FPDR
and FFDR shall assume that the bus flooring and structure shall be the same for all vehicles of the same type as was
determined during the inspection. If during the farebox installation the Contractor find this is not the case, the Contractor
shall notify Collier Area Transit and request that Collier Area Transit take appropriate remediation action to allow the
farebox to be installed Collier Area Transit shall assume all responsibility for the cost, material, and labor to accomplish the
work specified by the Contractor supplied installation plan. Contractor shall be responsible for the cost, material, and labor
to modify vehicle handrails, or equipment structure not so identified in the Contractor supplied installation plan.
K. Contractor shall supply and install all the necessary wiring, protective devices, and mounting hardware necessary for the
proper installation and operation of the fareboxes. Wiring shall be between the farebox and the electrical circuit described
in Section 3.6.5.a. All new undercarriage wiring shall be installed in conduit and suitably protected against the road elements.
All wiring and conduit shall be fastened in a manner so as not to interfere with normal bus operation and maintenance. No
“butt connectors” or other splices shall be permitted under the bus flooring.
L. Every power lead must be fused at the beginning with the same type of circuit breaker that the bus already uses.
M. The standard farebox mounting shall provide a secure maintenance• free method to secure the farebox and associated fare
collection equipment to the vehicle structure. The system employed must ensure the security of the unit and must provide
adequate stability and restraint to ensure the components, at maximum weight, shall remain affixed to the mounting location
under circumstances of a lateral force of 4g in any direction.
N. Collier Area Transit will ensure a protected electrical circuit of the specified voltage and rating is made available on each
bus at the location(s) specified by the Contractor installation plan. If Contractor does not provide such information in the
installation plan, the Contractor shall have the responsibility to install a protected electrical circuit to the designated location
at no cost to Collier Area Transit. Collier Area Transit will be responsible to ensure the power service is reliable and free of
interruption or variation in excess of the specification. This power service shall include a grounded lead with both ground
and power wires enclosed in flexible conduit to provide protection from the elements.
O. Contractor shall fill out Collier Area Transit Disposal Form to record the equipment and associated data that is being
disposed.
10. Training
A. Contractor shall provide training for the fareboxes and for their maintenance. Collier Area Transit maintenance staff shall
be trained to operate and maintain the fareboxes through a train-the-trainer model for operations, and by classroom type
training for the maintenance team. Contractor shall provide an option for annual training for the fleet maintenance staff.
Training costs shall be all inclusive.
B. Contractor shall provide complete operating and maintenance manuals. Contractor will submit a plan for conducting training
that meets Collier Area Transit requirements.
C. Contractor shall provide a comprehensive program to educate and train personnel in all details of the System, enabling them
to properly operate, service, and maintain the system and each of its components throughout its useful life.
D. The project training program shall be based on Contractor’s established standard training courses modified as required to
reflect Collier Area Transit 's installed system. Training shall include course development, the providing of instructors, the
supply of handouts and manuals, the preparation of classroom aids, and all other items as required to satisfactorily prepare
personnel to operate Contractor supplied fare collection system.
E. Contractor shall develop and submit for Collier Area Transit review and approval a Training Plan that documents the design
of the program for training personnel and each course to be delivered.
F. Contractor shall be responsible for directly training the maintenance staff: Mechanics, Trainer, Supervisor, IT Staff,
Operations staff, and Finance team.
G. For additional areas, Contractor shall be responsible for training Collier Area Transit trainers. Additional courses include:
a. Driver Training
b. Revenue Collection Training
c. Reporting Training
d. Superuser Training
e. Admin Training
H. The initial training courses shall include Collier Area Transit trainers and Contractor shall supply sufficient additional
Page 1142 of 3773
24
training and materials for the trainers to allow the trainers to provide future training.
I. Contractor shall provide pricing for additional training courses to be offered throughout the life of the agreement as requested
by Collier Area Transit.
J. The Training Plan shall include a schedule for delivery of the training courses. The schedule shall consider the sequence of
training, hours of instruction, system readiness and proximity to startup, trainee availability, and venue for the training.
K. Contractor shall provide all necessary training materials and equipment for the delivery of each course (including train-the-
trainer) discussed in the Training Plan. Training documentation shall be separate from the operation and maintenance
manuals but may reference them.
L. Contractor shall provide instruction manuals that describe and illustrate in detail how to manage, operate, and maintain the
System delivered under the contract. The manuals shall include detailed documentation for all equipment, systems and
software.
M. Disaster recovery procedures shall be clearly specified in sufficient detail to consider all possible scenarios. Recovery
instructions shall describe detailed procedures to be followed in the event that system recovery is needed. Detailed data
backup and recovery procedures shall be provided.
11. Operations and Maintenance
A. Contractor shall warrant the system to be free of defects for 60 months commencing with system acceptance. Following the
warranty, Contractor shall provide ongoing software maintenance with a System Maintenance Agreement that provides for
credits to the maintenance fee if agreed service levels are not achieved. Contractor shall provide all PM schedules, parts
manuals, maintenance manuals, and user manuals for the equipment.
B. The Contractor shall warrant to Collier Area Transit that all of the equipment furnished under the procurement shall be free
from defects in material and workmanship under normal operating use and service.
C. The Contractor shall provide such a Warranty beginning at the time of final acceptance of the system and continuing for a
period of five (5) years on all equipment.
D. The Warranty shall cover all parts and labor costs during the Warranty period.
E. The warranty shall cover the following:
a. Repair or replacement of all equipment or systems required as a result of an identified hardware defect.
b. Software updates or re-writes required to repair all identified software defects or bugs and apply all necessary
patches or security updates released by the Contractor or third- party software providers throughout the term of the
warranty.
c. All labor associated with hardware and software testing and deployment, both in the lab and field environments,
needed to support warranty activities.
F. The Contractor shall also agree to repair or replace hardware, during the period of this Warranty, without expense to Collier
Area Transit, any and all parts which may be damaged due to defects in, or failure of such parts or of any other part or parts
of the equipment furnished under the Procurement.
G. Collier Area Transit shall maintain the equipment in accordance with the Contractor's instructions in order to maintain this
Warranty, and the Contractor shall be responsible for all shipping charges.
H. The Contractor shall be solely responsible for all materials and workmanship, including all specialties and accessories,
whether manufactured by it or others, used in the construction of the fare collection system and for adequate installation and
connection of all equipment, accessories, specialties, and components. Under no condition shall Contractor delegate this
responsibility to suppliers or other sources.
I. Any apparatus, device or material which experiences an "item" failure during the warranty period shall be brought to the
attention of the Contractor by Collier Area Transit at the conclusion of the first year but prior to the expiration of the
Warranty. The Contractor shall be required to repair or replace the apparatus, device or material (at his determination of the
problem and its cause) at no expense to Collier Area Transit.
J. Should a "fleet defect" occur during the warranty, the Contractor may be required by Collier Area Transit to extend the
Warranty on that item or class of equipment until the fleet defect problem has been eliminated. A fleet defect shall be
defined as a defect, failure or malfunction that affects 5% or more of any class of equipment delivered under this contract,
Page 1143 of 3773
25
or a systematic defect in the data system, software, several receivers or other subsystem, that affects the ability of the fare
collection system to achieve its intended purpose. The determination of a "fleet defect" shall be by Collier Area Transit and
shall assume that all equipment within its respective category has these defects and shall ultimately experience these same
failures.
K. In the event the Contractor fails to comply within ten working days to a request by Collier Area Transit to repair, replace or
correct damaged or defective work, materials, specialties, equipment and accessories, Collier Area Transit shall, upon
written notice to the Contractor, have authority to deduct the cost of labor and material incurred by Collier Area Transit
itself in making such repairs from any compensation due or to become due the Contractor. In the event the Contractor has
been paid, the Contractor agrees to reimburse Collier Area Transit for the cost thereof.
L. It is understood, however, that the said Warranty or Guarantee will not apply to any equipment which has been repaired or
altered without the knowledge or consent of the Contractor and which repair or altering affected its stability and/or reliability;
nor will said Warranty or Guarantee apply if the equipment has been subjected to other than normal use under conditions
which prevail in Collier Area Transit service. The burden of proof for any negligence on the part of Collier Area Transit
shall rest with the Contractor. Temperature, humidity, bus vibration and ambient electric conditions shall be considered
normal operating conditions for this equipment. The Warranty shall not cover the replacement and maintenance items (such
as light bulbs) made in connection with normal maintenance service.
M. Collier Area Transit does reserve the right to perform ‘hot swaps’, the exchange of faulty components, subassemblies, or
equipment, for working components, subassemblies, or equipment into Farebox equipment by qualified Collier Area Transit
staff at the Contractor’s consent and expense during the warranty period.
N. In event of a "fleet defect" labor to exchange faulty components, subassemblies or equipment and the shipping costs to return
such items to a service location nominated by the Contractor for repair or replacement as provided here shall be at the
expense of the Contractor. The shipping costs, including packing and insurance, to ship repaired or replaced items to Collier
Area Transit shall be at the expense of the Contractor.
O. Contractor guarantees that stock of replacement parts for the system, and all components thereof, will be available for a
period of not less than 15 years after the date of acceptance of the completed system under this contract by Collier Area
Transit.
P. The above warranties are in addition to any statutory implied warranties or remedies imposed on the Contractor.
Q. Contractor shall warrant that all of the software provided for the System by Contractor and Contractor-contracted suppliers,
shall be free from defects under normal operating use.
R. Prior to the start of the System Maintenance Agreement, all software maintenance activities shall be covered under warranty.
S. All software maintenance performed under warranty shall comply with Collier Area Transit -approved software maintenance
and quality assurance procedures.
T. The warranty shall cover software updates or re-writes required to repair all identified software defects or bugs, and apply
all necessary patches or security updates released by the Contractor or third-party software providers throughout the term of
the warranty.
U. As part of Final Design Review (FDR), Contractor shall develop and submit for Collier Area Transit review a draft warranty
plan outlining processes and procedures to be implemented to meet all specified warranty requirements. A final version shall
be provided a minimum of 90 calendar days prior to the start of the warranty term.
V. Contractor shall replace new any device, component or subsystem that has been repaired three (3) times for the same failure
within the warranty period.
W. Collier Area Transit shall be responsible for field checking equipment, including ensuring that power and network
connections are operational. If the equipment still fails, they shall replace it with a spare and send it to the Contractor for
repair or replacement. There shall be a service level agreement (SLA) to cover turnaround times for the equipment to be
repaired or replaced.
X. Contractor and Collier Area Transit shall enter into a System Maintenance Agreement, or SMA which shall take effect
immediately following the end of the warranty period. For a set annual fee, Contractor shall maintain the system to an agreed
upon Service Level. Any failure to meet the Service Level Agreement will result in a credit from Contractor to Collier Area
Transit for maintenance fees.
Page 1144 of 3773
26
Y. Performance of software maintenance activities shall be completed in a manner that does not disrupt or degrade system
operations, to the fullest extent possible.
Z. Software updates shall be clearly documented and submitted in advance of deployment for Collier Area Transit review and
approval.
AA. During the warranty and SMA terms, Contractor shall provide updated course instruction and materials resulting from any
significant system software changes.
BB. The Contractor shall keep all software environments (training, test, development, staging, and production) at the same
configuration and version level unless otherwise approved by the Agency PM.
CC. Contractor shall notify Collier Area Transit whenever corrections, modifications or revisions of system software are
available.
DD. As standard practice when repairing deficiencies and releasing device or back-office system fixes or upgrades, Contractor
shall prepare and run regression testing scripts to test that each software release delivered to the test environment does not
result in any issues with the devices and systems currently in operation, including those that are not being updated. Any
regression issues shall be documented as deficiencies and resolved accordingly.
EE. During the lifecycle of the fareboxes, Collier Area Transit may identify enhancements required to improve the functionality
of the System, improve performance, and comply with updated standards or newly identified Agency requirements. The
Contractor shall maintain the capability to design, develop, and test these changes throughout the life of the contract. At the
request of Collier Area Transit, The Contractor shall propose and then with Collier Area Transit ’s approval modify the
System software as necessary to meet COLLIER AREA TRANSIT ’s requirements.
FF. Contractor shall provide to Collier Area Transit all support required to develop and deploy such enhancements at the
Contractor's labor rates specified in the price schedule.
GG. Contractor shall be responsible for maintaining the System’s compliance with all required security standards and controls.
HH. Contractor shall be responsible for maintaining the Collier Area Transit test facility and test environment for the duration of
the contract.
II. Contractor shall provide pricing for all system parts, down to the Lowest Replaceable Component, good for the life of the
contract.
JJ. For fifteen (15) years after delivery and Final Acceptance of the fare collection system, Contractor shall maintain an adequate
inventory of spare parts for all the equipment furnished under this contract. In situations where part or component is no
longer available, Contractor shall identify a compatible replacement solution. The replacement solution shall represent the
most cost-effective approach that retains the overall functionality of the affected part or component and shall include
instructions as appropriate to support the implementation of the replacement solutions. Therefore, the replacement solution
may not be a form, fit, and function one-to-one replacement of the originally delivered part or component. Contractor shall
ensure that a sufficient number of original components are available through the base warranty.
KK. Collier Area Transit anticipates performing all levels of maintenance, preventative, field repair, shop- level, and overhauls
to all equipment in the fare collection system. Shop level repairs include repairs to the Lowest Replaceable Component
(LRC) level as defined by Contractor. A component is considered to be the lowest replaceable item, such as on a printed
circuit board.
LL. Contractor shall maintain internal controls to ensure the security of the region’s assets and to avoid and detect fraud and
theft.
MM. Contractor shall be responsible for maintaining the System’s fraud control capabilities for the duration of the contract.
NN. Contractor shall develop a Disaster Recovery Plan, identifying a set of procedures to recover the System in the event of an
unforeseen event that causes a disruption of service. A draft plan shall be submitted for Collier Area Transit ’s review for
Preliminary Design Review (PDR). A revised plan shall be submitted for Collier Area Transit ’s review and approval for
FDR.
OO. Contractor shall maintain the Disaster Recovery Plan for the duration of the contract.
PP. Disaster recovery procedures shall be clearly specified in sufficient detail to consider all possible scenarios. Recovery
instructions shall describe detailed procedures to be followed in the event that system recovery is needed. Detailed data
Page 1145 of 3773
27
backup and recovery procedures shall be provided.
QQ. System performance shall be measured using the data generated and stored by the System. Contractor shall automate data
capture and KPI calculation to the maximum extent possible. Data generated manually shall be used when it is the only
option for tracking an activity associated with a particular KPI.
RR. For validation purposes, Collier Area Transit shall have full access to the source data and code used to perform the
calculation.
SS. Contractor shall submit a Performance Measurement Plan for Collier Area Transit ’s review and approval during design
review identifying the approach to measuring and reporting on performance against KPIs.
TT. Contractor shall measure and report Key Performance Indicators (KPIs), specified herein, starting no later than
commencement of revenue service. These KPIs shall be used as the primary criteria for evaluating system performance
during the System Acceptance Test (SAT) and granting of Final System Acceptance.
UU. A subset of the KPIs shall be measured and reported by Contractor throughout the operations and maintenance agreement(s).
Failure to meet these requirements at any time following Final System Acceptance shall result in a credit being granted
against the monthly operations payments made to Contractor.
VV. Farebox accuracy shall be determined by comparing both the quantity and value (where available) of transactions generated
by the devices, as recorded within the device audit registers, to those received by the back office:
WW. Equipment Accuracy = (Equipment Audit Register Transaction Count - Back Office Transaction Count) / Equipment Audit
Register Transaction Count
XX. Equipment Accuracy = (Equipment Audit Register Transaction Value - Back Office Transaction Value) / Equipment Audit
Register Transaction Value
YY. Both the transaction count and value calculations (where applicable) for all Fareboxes frontend devices must meet or exceed
an accuracy of 99.99% in order to pass.
ZZ. Back-office accuracy shall be based on the number of incidents where a device or back office generated transaction is
recorded incorrectly within the associated system.
AAA. Performance shall only be measured for those applications for which Contractor is responsible.
BBB. Availability is a measure of the time that a component is operational and available for its intended use (e.g., uptime). Since
availability is dependent not only on a component’s performance (e.g., reliability), but also the time to respond to and
repair an issue, availability can only be measured for the parts of the System that Contractor is responsible for maintaining,
which is to say, the back-office applications.
CCC. Frontend device accuracy shall be determined by comparing both the quantity and value (where available) of transactions
generated by the devices, as recorded within the device audit registers, to those received by the Farebox:
DDD. Equipment Accuracy = (Equipment Audit Register Transaction Count - Back Office Transaction Count) / Equipment
Audit Register Transaction Count
EEE. Equipment Accuracy = (Equipment Audit Register Transaction Value - Back Office Transaction Value) / Equipment
Audit Register Transaction Value
FFF. Both the transaction count and value calculations (where applicable) for all Fareboxes frontend devices must meet or
exceed an accuracy of 99.99% in order to pass.
GGG. Contractor shall be responsible for reporting on performance against all KPIs on a monthly basis.
HHH. At a minimum, the following reports shall be provided:
a. Device reliability
b. Device accuracy
c. Device availability
d. Back-office accuracy
e. Back-office availability
Page 1146 of 3773
28
III. Failure of a Contractor-chargeable software KPI to meet the defined performance requirement shall result in a monetary
credit being granted by Contractor to Collier Area Transit. Hardware reliability KPIs shall be excluded from the credit
assessment.
JJJ. Credits shall be determined as a percentage of the operations payments made to the Contractor. The credit percentage and
operations payment associated with each KPI shall be determined during negotiations.
KKK. Contractor shall be responsible for reporting on credits in the System performance reports and shall deduct credits directly
from any invoices submitted to the Agency.
12. Documentation
A. The Contractor shall provide samples of all of the following documents for approval by CAT Transit 60 days before delivery
of the fareboxes. Final acceptance of the system shall not take place until the Contractor has received approval of all of these
documents:
a. Farebox Maintenance Manuals
b. Farebox Operations Manuals
c. Vault Manuals
d. Security Manuals
e. Hosted Computer System Operations Manuals
f. Hosted Computer System Data Dictionary
g. Hosted Computer System Manuals Maintenance
13. Maintenance Agreement
A. The Contractor will present options for maintenance and support of the entire fare collection system:
a. For a period of up to 5 years, commencing after completion of system implementation.
b. The proposed options shall include, but are not limited to:
i. On-Call maintenance support
ii. Patch/update installations
iii. Base Computer system updates
iv. Parts and parts availability
v. Communications
14. Project Management
A. Contractor shall provide project management services to support the design and installation of the fareboxes. The
Contractor’s plan for managing the project shall include the coordination and management of the installation, testing and
commissioning, including a project schedule, and any other tools necessary to manage tasks, schedule, risks, change and
any other project-related activities.
B. Time is of the essence for this project. Contractor shall propose a date for full installation and operation given the timeline
presented.
C. Contractor shall provide a robust project management team and project management plan to support completion of the
project. The Contractor's plan for managing the project shall clearly demonstrate an appropriate allocation of project
management resources that have the ability and experience to ensure that system design and implementation shall be properly
coordinated and managed and shall be completed on schedule and within budget. Contractor shall provide tools to manage
tasks, schedule, risk, change, and the other items listed in this section that are required to manage the project.
D. Contractor shall submit a Project Management Plan (PMP) shortly following Notice to Proceed (NTP) that details at a
minimum project organization, master schedule, and how project scope, cost, risk, quality, project changes, safety, and other
key aspects of the project shall be managed by Contractor.
E. The Project Management Plan (PMP) shall include but is not limited to the following elements:
a. Organization chart identifying key project personnel and contact information, including installation management
team.
b. Project Schedule, identifying key project milestones and activities.
c. Schedule for all project design and development elements that require Collier Area Transit ’s approval.
d. Project meetings and schedule for recurring meetings
e. Methodology to control project schedule, scope, cost, and risk
f. Risk management plan and risk register, including identified project risks and actions required to mitigate them.
g. Transition and change management processes and procedures
Page 1147 of 3773
29
h. Safety processes and procedures
i. Quality assurance processes and procedures to confirm that the requirements of the contract are being met.
j. Subcontractor management and communications
k. Document and Master Issues List (MIL) control processes and procedures, including version and traceability
controls.
l. Change management plan and procedures for all deliverables and subsequent revisions
m. Cost management
F. As part of the Program Management plan, Contractor shall create and maintain a Project Schedule for executing the work
for this Contract. Contractor shall generate the Project Schedule using Microsoft Project Professional or similar. The Project
Schedule shall conform to the Scope of Work and to schedule and delivery requirements set forth in the Terms and
Conditions of this Contract.
G. The Project Schedule shall contain at a minimum the following elements and milestones:
a. Design
b. Design Review
c. Testing
d. Prototyping
e. Acceptance of prototypes
f. Field integration testing
g. Installation of fareboxes
h. Acceptance testing
i. Training
j. Go Live
k. System acceptance
H. Contractor shall set a baseline upon initial acceptance of the Project Schedule and shall update the schedule according to
actual progress no less than weekly.
I. Contractor shall provide Collier Area Transit with a copy of the Project Schedule.
J. Contractor shall conduct two design reviews for the system: Preliminary Design Review (PDR), and Final Design Review
(FDR).
K. Preliminary design review activities shall include the following:
a. Contractor shall submit preliminary design review (PDR) design documents to Collier Area Transit for review.
b. Preliminary design review meeting(s) shall be held with Contractor where Contractor shall explain the design and
Collier Area Transit shall confirm and provide feedback on the information.
c. Where possible, issues shall be resolved during the design review meetings.
d. If necessary, Contractor shall re-submit updated PDR documents for Collier Area Transit review and approval that
incorporate needed changes identified during the reviews.
L. At a minimum, the Preliminary Design Review shall include:
a. Detailed technical descriptions of the farebox system major components, allowing a thorough understanding of the
implementation of the proposed System Components
b. Preliminary layouts for all System Components,
c. Drawing of passenger interface arrangements
d. Preliminary installation layouts for farebox, garage and office equipment.
e. Mounting arrangements and installation methods
f. Single line power diagrams, control schematics, and functional block diagrams for each subsystem, including a
functional overview.
g. A description of how each System Component, sub-system, or sub-component down to the lowest field replacement
unit goes into limited operating condition.
h. List of special tools and Diagnostic and Test Equipment (DTE) for each subsystem
i. List and description of all person machine interfaces
j. Software system level flow charts
k. Software data backup and recovery procedures
l. Software design descriptions (top level of software documentation) for all programmable System Components
supplied under this Agreement and Specifications
m. Software version control system
M. Final design review (FDR) activities shall include the following:
Page 1148 of 3773
30
a. Contractor shall develop and submit FDR design documents to Collier Area Transit for review that document
additional design details and address all remaining design decisions.
b. Final design review meeting(s) shall be held with the Contractor where Contractor shall explain the final design.
c. Where possible, any remaining issues shall be resolved during the design review meetings.
d. If necessary, Contractor shall re-submit updated FDR documents for Collier Area Transit review and approval that
incorporate needed changes identified during the reviews.
N. FDR shall include but not be limited to the following:
a. Latest revisions of the drawings and documentation submitted for the FPDR.
b. Assembly drawings down to the LLRU level
c. Software documentation at the second level, including all software development documentation available or used
in Contractor’s design process, consisting of structured data flow diagrams, event tables and/or dialogue diagrams
(as available) to the lowest level of decomposition with software module descriptions (or elemental process
descriptions) in structured narrative format. The second level of software documentation is one level above source
code.
d. Shutdown and startup sequences
e. Electrical schematic drawings, down to the individual signal or wire level, for each electrical circuit
f. Software flow charts or structure charts that give an overview of the processor software.
g. Demonstrate completed algorithms expressed in program design language or pseudo code.
h. Input data definitions
i. Output data definitions
j. Interrupt structure definition
k. Program parameters
l. Diagnostic routines for processor self-test and subsystem self-test
m. Error handling routines
n. Data Dictionary for all program, data storage and data staging database entities
o. Final installation plan and drawings
p. A complete parts list, down to the Lowest Replaceable component, including OEM part numbers.
q. Testing and Cutover Plan
15. Documentation
A. The Contractor shall provide samples of all the following documents for approval by Collier Area Transit 60 days before
delivery of the fareboxes. Final acceptance of the system shall not take place until the Contractor has received approval
of all these documents.
a. Farebox Maintenance Manuals
b. Farebox Operations Manuals
c. Vault Manuals
d. Security Manuals
e. Hosted Computer System Operations Manuals
f. Hosted Computer System Data Dictionary
g. Hosted Computer System Manuals Maintenance
16. Vouchers
A. Currently CAT sales one-way fares as a voucher to agencies and or anyone who is interested in purchasing in bulk, the
contractor shall describe how the system will allow for the sale of one-way fares and open day pass (not requiring the
use of the day pass the day it was purchase).
17. Fleet
The following is a tabulation of the current fleet within the Collier Area Transit Fixed Route System that will require Farebox
installation.
Number of
Buses Manufacturer/Model
11 Gillig 30’
12 Gillig 35’
4 Gillig 40’
1 Freightliner 30’ / Legacy
Page 1149 of 3773
31
2 Hometown Trollies/Villagers
30 Total
REQUEST FOR PROPOSAL (RFP) PROCESS
1.1 The Proposers will submit a qualifications proposal which will be scored based on the criteria in Evaluation Criteria for
Development of Shortlist, which will be the basis for short-listing firms.
The Proposers will need to meet the minimum requirements outlined herein in order for their proposal to be evaluated and
scored by the COUNTY. The COUNTY will then score and rank the firms and enter into negotiations with the top ranked
firm to establish cost for the services needed. The COUNTY reserves the right to issue an invitation for oral presentations
to obtain additional information after scoring and before the final ranking. With successful negotiations, a contract will be
developed with the selected firm, based on the negotiated price and scope of services and submitted for approval by the
Board of County Commissioners.
1.2 The COUNTY will use a Selection Committee in the Request for Proposal selection process.
1.3 The intent of the scoring of the proposal is for respondents to indicate their interest, relevant experience, financial capability,
staffing and organizational structure.
1.4 The intent of the oral presentations, if deemed necessary, is to provide the vendors with a venue where they can conduct
discussions with the Selection Committee to clarify questions and concerns before providing a final rank.
1.5 Based upon a review of these proposals, the COUNTY will rank the Proposers based on the discussion and clarifying
questions on their approach and related criteria, and then negotiate in good faith an Agreement with the top ranked Proposer.
1.6 If, in the sole judgment of the COUNTY, a contract cannot be successfully negotiated with the top-ranked firm, negotiations
with that firm will be formally terminated and negotiations shall begin with the firm ranked second. If a contract cannot be
successfully negotiated with the firm ranked second, negotiations with that firm will be formally terminated and negotiations
shall begin with the third ranked firm, and so on. The COUNTY reserves the right to negotiate any element of the proposals
in the best interest of the COUNTY.
RESPONSE FORMAT AND EVALUATION CRITERIA FOR DEVELOPMENT OF SHORTLIST:
1.7 For the development of a shortlist, this evaluation criterion will be utilized by the COUNTY’S Selection Committee to score
each proposal. Proposers are encouraged to keep their submittals concise and to include a minimum of marketing
materials. Proposals must address the following criteria:
Evaluation Criteria Maximum Points
1. Cover Letter / Management Summary 5 Points
2. Contractor’s Qualifications and Experience 20 Points
3. Equipment Functionality and Coverage 25 Points
4. Implementation Plan/Approach 25 Points
5. Cost for Equipment, Installation and Warranty 25 Points
TOTAL POSSIBLE POINTS 100 Points
Tie Breaker: In the event of a tie at final ranking, award shall be made to the proposer with the lower volume of work
previously awarded. Volume of work shall be calculated based upon total dollars paid to the proposer in the twenty-four
(24) months prior to the RFP submittal deadline. Payment information will be retrieved from the County’s financial system
of record. The tie breaking procedure is only applied in the final ranking step of the selection process and is invoked by the
Procurement Services Division Director or designee. In the event a tie still exists, selection will be determined based on
random selection by the Procurement Services Director before at least three (3) witnesses.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Each criterion and methodology for scoring is further described below.
***Proposals must be assembled, at minimum, in the order of the Evaluation Criteria listed or your
proposal may be deemed non-responsive***
EVALUATION CRITERIA NO. 1: COVER LETTER/MANAGEMENT SUMMARY (5 Total Points Available)
Provide a cover letter, signed by an authorized officer of the firm, indicating the underlying philosophy of the firm in
providing the services stated herein. Include the name(s), telephone number(s) and email(s) of the authorized contact
person(s) concerning proposal. Submission of a signed Proposal is Vendor's certification that the Vendor will accept any
awards as a result of this RFP.
Page 1150 of 3773
32
EVALUATION CRITERIA NO. 2: CONTRACTOR’S QUALIFICATIONS AND EXPERIENCE (20 Total Points
Available)
In this criteria, include but not limited to:
• Provide information that documents your firm’s and subcontractors’ qualifications to produce the required
deliverables, including abilities, capacity, skill, and financial strength, and number of years of experience in
providing the required services.
• Describe the various team members’ successful experience in working with one another on previous projects.
• Experience – Contractor should provide a corporate profile indicating their qualifications to provide the required
software, hardware, and technical support necessary to achieve objectives for the project.
The County requests that the Contractor submits no fewer than five (5) and no more than ten (10) completed
reference forms from clients during a period of the last 5 years whose projects are of a similar nature to this
solicitation as a part of their proposal. Provide information on the projects completed by the Contractor that best represent
projects of similar size, scope and complexity of this project using form provided in Form 5. Contractors may include two
(2) additional pages for each project to illustrate aspects of the completed project that provides the information to assess the
experience of the Contractor on relevant project work.
EVALUATION CRITERIA NO. 3: EQUIPMENT FUNCTIONALITY AND COVERAGE (25 Total Points
Available)
In this criteria, include but not limited to:
A. Software System/ Hardware Technology Description – Contractors should fully describe the software and hardware
being offered as part of this submission, along with any other (Information Technology Solutions) ITS technologies the
Contractor may be proposing. Contractors should clearly state the capabilities of each product and its suitability to the
task of addressing needs.
Contractors must list all software and hardware components/modules necessary to fully implement the project, including
third party software necessary to complete the total installation (e.g., report generation software, SQL, back-up software,
remote access software, etc.) required for a centralized solution. The technology must be 100% web based, not a web
front on top of a PC based solution.
B. Support and Warranty – Contractor should provide a detailed support and warranty program. Detailing Return Material
Authorization (RMA) Process and support of the software.
C. The attached Technical Architectural Compatibility and Supportability (TACS) forms need to be filled out completely
and returned with the Contractor’s proposal.
EVALUATION CRITERIA NO. 4: IMPLEMENTATION PLAN/APPROACH (25 Total Points Available)
In this criteria, include but not limited to:
A. Implementation Plan:
• Proposed implementation plan, project timeline, from Notice to Proceed testing, de-bugging to “live”
operations. Proposed timeline must include all project and implementation milestones.
• Implementation plan shall incorporate a transition process from the current technology. The implementation
plan must clearly state the roles and responsibilities and the scheduling of the integrated technology solution.
• Contractor to describe ability to maintain schedules and meet deadlines.
• Contractor to describe ability to manage the project cost.
• Technical support, maintenance, and warranty program.
• Contractor to describe close out process (no incomplete items upon turnover, warranties, training materials,
operating manuals, etc.).
• Contractor must describe and explain any circumstances or portions of their proposed solution that does not
conform to the requested scope of work.
• The software and ancillary equipment furnished hereunder must be tested, debugged, operating “live” and fully
functional within 12 months from Notice to Proceed.
B. Quality Assurance Plan:
Contractors should describe in detail their management strategies for overall quality assurance in the installation, start-
up, and operation of the scheduling and dispatching system software. At a minimum Contractors should address:
Project Management and Staffing:
• Describe the proposed individuals and team approach used to successfully communicate with the project
Page 1151 of 3773
33
personnel at County’s location. If contractors are used for any part of the installation, customization, or
maintenance of the proposed software system, this element of your overall approach must be identified here.
The Contractor must designate one individual with complete control over all installations:
• Quality Control – Describe steps and techniques employed by the Contractor to ensure the integrity of
databases.
• Maintenance, Support, and Upgrades – Describe the Contractor’s network of technical support during the
project, focusing both on the critical initial implementation period as well as long-term operation. Describe
procedures for rendering support, including the availability of technicians to provide on-site repairs and ability
to remotely access, diagnose, and make necessary repairs.
C. Training – Contractors must provide a detailed schedule and course outline for all necessary training of the cooperative
Collier Area Transit personnel. This section of the proposal should identify the training course content, the number of
courses required, and type of training (classroom, hands-on, etc.) that will be provided, the length of the training session,
etc. Contractors should indicate when the training should be provided in the context of the overall implementation time
schedule provided above in the implementation plan. Qualifications of the staff providing the training should be listed
as reference.
D. Contractor shall provide all proposed agreements or additional terms and conditions, including, but not limited to:
• Master Service agreement
• Subscription & Service agreement
• Merchant Payment Processing agreement
• Warranty and Service agreement
EVALUATION CRITERIA NO. 5: PRICE FOR EQUIPMENT, INSTALLATION, LICENSE AND WARRANTY
(25 Total Points Available)
A. Provide the projected total cost for which the Vendor will provide the work as described in this RFP. Total
project cost must be all-inclusive of equipment and installation and implementation, components, hardware, software,
licensing, warranties, testing, training, and any other items required for project completion.
B. Proposal shall include option for additional years of extended warranty, license and technical support after
implementation, for up to 5 (five) additional years.
C. Clearly describe any deviation from listed scope of work that would affect costs.
Hardware and Equipment (The Cost for individual items shall remain firm for the full term of this agreement).
Item Unit
Cost
Number
Required Total Cost
Equipment
Farebox 30 $ 0
Test Bench 1 $ 0
Fixed Vault 1 $ 0
Portable Vault 1 $ 0
Software and Implementation
Back Office/Central System 1 $ 0
Point of Sale Terminal 2 $ 0
Wireless Local Area Network (LAN) Access Points and Data
Transfer Software 1 $ 0
Implementation Cost (Project Management, Design,
Testing, Documentation, Install, Training, Integration, Etc.) 1 $ 0
Total Cost to Implement
Total Cost $ 0
License, Warranty, and Support (Year 2 - 5)
Page 1152 of 3773
34
Farebox Extended Warranty and Technical Support
Year 1 Warranty and Support – after acceptance
Included in
implementation
cost
Year 2 Extended Warranty, License and Technical Support 1 $ 0
Year 3 Extended Warranty, License and Technical Support
(Option) 1 $ 0
Year 4 Extended Warranty, License and Technical Support
(Option) 1 $ 0
Year 5 Extended Warranty, License and Technical Support
(Option) 1 $ 0
Year 6 Extended Warranty, License and Technical Support
(Option) 1 $ 0
Spare Hardware (Recommended List of Spare Parts)
Training Farebox 1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
1 $ 0
Initial pricing is for evaluation purposes and are subject to change during negotiations with the selected vendor.
VENDOR CHECKLIST
***Vendor should check off each of the following items as the necessary action is completed (please see, Vendor Check List)***
Page 1153 of 3773
Page 1154 of 3773
Page 1155 of 3773
Page 1156 of 3773
Page 1157 of 3773
Page 1158 of 3773
Company ID Number:
THE E-VERIFY
MEMORANDUM OF UNDERSTANDING
FOR EMPLOYERS
ARTICLE I
PURPOSE AND AUTHORITY
The parties to this agreement are the Department of Homeland Security (DHS) and
(Employer). The purpose of this agreement is to set forth terms and conditions which the Employer will follow
while participating in E-Verify.
E-Verify is a program that electronically confirms an employee’s eligibility to work in the United States after
completion of Form I-9, Employment Eligibility Verification (Form I-9). This Memorandum of Understanding
(MOU) explains certain features of the E-Verify program and describes specific responsibilities of the
Employer, the Social Security Administration (SSA), and DHS.
Authority for the E-Verify program is found in Title IV, Subtitle A, of the Illegal Immigration Reform and
Immigrant Responsibility Act of 1996 (IIRIRA), Pub. L. 104-208, 110 Stat. 3009, as amended (8 U.S.C. § 1324a
note). The Federal Acquisition Regulation (FAR) Subpart 22.18, “Employment Eligibility Verification” and
Executive Order 12989, as amended, provide authority for Federal contractors and subcontractors (Federal
contractor) to use E-Verify to verify the employment eligibility of certain employees working on Federal
contracts.
ARTICLE II
RESPONSIBILITIES
A. RESPONSIBILITIES OF THE EMPLOYER
1.The Employer agrees to display the following notices supplied by DHS in a prominent place that is clearly
visible to prospective employees and all employees who are to be verified through the system:
a.Notice of E-Verify Participation
b.Notice of Right to Work
2.The Employer agrees to provide to the SSA and DHS the names, titles, addresses, and telephone numbers
of the Employer representatives to be contacted about E-Verify. The Employer also agrees to keep such
information current by providing updated information to SSA and DHS whenever the representatives’ contact
information changes.
3.The Employer agrees to grant E-Verify access only to current employees who need E-Verify access.
Employers must promptly terminate an employee’s E-Verify access if the employer is separated from the
company or no longer needs access to E-Verify.
Page 1 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
LECIP Inc
2328571
Page 1159 of 3773
Company ID Number:
4.The Employer agrees to become familiar with and comply with the most recent version of the E-Verify
User Manual.
5.The Employer agrees that any Employer Representative who will create E-Verify cases will complete the
E-Verify Tutorial before that individual creates any cases.
a.The Employer agrees that all Employer representatives will take the refresher tutorials when
prompted by E-Verify in order to continue using E-Verify. Failure to complete a refresher tutorial will
prevent the Employer Representative from continued use of E-Verify.
6.The Employer agrees to comply with current Form I-9 procedures, with two exceptions:
a.If an employee presents a "List B" identity document, the Employer agrees to only accept "List B"
documents that contain a photo. (List B documents identified in 8 C.F.R. § 274a.2(b)(1)(B)) can be
presented during the Form I-9 process to establish identity.) If an employee objects to the photo
requirement for religious reasons, the Employer should contact E-Verify at 888-464-4218.
b.If an employee presents a DHS Form I-551 (Permanent Resident Card), Form I-766
(Employment Authorization Document), or U.S. Passport or Passport Card to complete Form I-9, the
Employer agrees to make a photocopy of the document and to retain the photocopy with the
employee’s Form I-9. The Employer will use the photocopy to verify the photo and to assist DHS with its
review of photo mismatches that employees contest. DHS may in the future designate other documents
that activate the photo screening tool.
Note: Subject only to the exceptions noted previously in this paragraph, employees still retain the right
to present any List A, or List B and List C, document(s) to complete the Form I-9.
7.The Employer agrees to record the case verification number on the employee's Form I-9 or to print the
screen containing the case verification number and attach it to the employee's Form I-9.
8.The Employer agrees that, although it participates in E-Verify, the Employer has a responsibility to
complete, retain, and make available for inspection Forms I-9 that relate to its employees, or from other
requirements of applicable regulations or laws, including the obligation to comply with the anti-
discrimination requirements of section 274B of the INA with respect to Form I-9 procedures.
a.The following modified requirements are the only exceptions to an Employer’s obligation to not
employ unauthorized workers and comply with the anti-discrimination provision of the INA: (1) List B
identity documents must have photos, as described in paragraph 6 above; (2) When an Employer
confirms the identity and employment eligibility of newly hired employee using E-Verify procedures, the
Employer establishes a rebuttable presumption that it has not violated section 274A(a)(1)(A) of the
Immigration and Nationality Act (INA) with respect to the hiring of that employee; (3) If the Employer
receives a final nonconfirmation for an employee, but continues to employ that person, the Employer
must notify DHS and the Employer is subject to a civil money penalty between $550 and $1,100 for each
failure to notify DHS of continued employment following a final nonconfirmation; (4) If the Employer
continues to employ an employee after receiving a final nonconfirmation, then the Employer is subject
to a rebuttable presumption that it has knowingly
Page 2 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1160 of 3773
Company ID Number:
employed an unauthorized alien in violation of section 274A(a)(1)(A); and (5) no E-Verify participant is
civilly or criminally liable under any law for any action taken in good faith based on information provided
through the E-Verify.
b.DHS reserves the right to conduct Form I-9 compliance inspections, as well as any other enforcement
or compliance activity authorized by law, including site visits, to ensure proper use of E-Verify.
9.The Employer is strictly prohibited from creating an E-Verify case before the employee has been hired,
meaning that a firm offer of employment was extended and accepted and Form I-9 was completed. The
Employer agrees to create an E-Verify case for new employees within three Employer business days after each
employee has been hired (after both Sections 1 and 2 of Form I-9 have been completed), and to complete as
many steps of the E-Verify process as are necessary according to the E-Verify User Manual. If E-Verify is
temporarily unavailable, the three-day time period will be extended until it is again operational in order to
accommodate the Employer's attempting, in good faith, to make inquiries during the period of unavailability.
10.The Employer agrees not to use E-Verify for pre-employment screening of job applicants, in support of
any unlawful employment practice, or for any other use that this MOU or the E-Verify User Manual does not
authorize.
11.The Employer must use E-Verify for all new employees. The Employer will not verify selectively and will
not verify employees hired before the effective date of this MOU. Employers who are Federal contractors may
qualify for exceptions to this requirement as described in Article II.B of this MOU.
12.The Employer agrees to follow appropriate procedures (see Article III below) regarding tentative
nonconfirmations. The Employer must promptly notify employees in private of the finding and provide them
with the notice and letter containing information specific to the employee’s E-Verify case. The Employer
agrees to provide both the English and the translated notice and letter for employees with limited English
proficiency to employees. The Employer agrees to provide written referral instructions to employees and
instruct affected employees to bring the English copy of the letter to the SSA. The Employer must allow
employees to contest the finding, and not take adverse action against employees if they choose to contest the
finding, while their case is still pending. Further, when employees contest a tentative nonconfirmation based
upon a photo mismatch, the Employer must take additional steps
(see Article III.B. below) to contact DHS with information necessary to resolve the challenge.
13.The Employer agrees not to take any adverse action against an employee based upon the employee's
perceived employment eligibility status while SSA or DHS is processing the verification request unless the
Employer obtains knowledge (as defined in 8 C.F.R. § 274a.1(l)) that the employee is not work authorized. The
Employer understands that an initial inability of the SSA or DHS automated verification system to verify work
authorization, a tentative nonconfirmation, a case in continuance
(indicating the need for additional time for the government to resolve a case), or the finding of a photo
mismatch, does not establish, and should not be interpreted as, evidence that the employee is not work
authorized. In any of such cases, the employee must be provided a full and fair opportunity to contest the
finding, and if he or she does so, the employee may not be terminated or suffer any adverse employment
consequences based upon the employee’s perceived employment eligibility status
Page 3 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1161 of 3773
Company ID Number:
(including denying, reducing, or extending work hours, delaying or preventing training, requiring an
employee to work in poorer conditions, withholding pay, refusing to assign the employee to a Federal
contract or other assignment, or otherwise assuming that he or she is unauthorized to work) until and unless
secondary verification by SSA or DHS has been completed and a final nonconfirmation has been issued. If the
employee does not choose to contest a tentative nonconfirmation or a photo mismatch or if a secondary
verification is completed and a final nonconfirmation is issued, then the Employer can find the employee is
not work authorized and terminate the employee’s employment. Employers or employees with questions
about a final nonconfirmation may call E-Verify at 1-888-464-4218 (customer service) or 1-888-897-7781
(worker hotline).
14.The Employer agrees to comply with Title VII of the Civil Rights Act of 1964 and section 274B of the INA
as applicable by not discriminating unlawfully against any individual in hiring, firing, employment eligibility
verification, or recruitment or referral practices because of his or her national origin or citizenship status, or
by committing discriminatory documentary practices. The Employer understands that such illegal practices
can include selective verification or use of E-Verify except as provided in part D below, or discharging or
refusing to hire employees because they appear or sound “foreign” or have received tentative
nonconfirmations. The Employer further understands that any violation of the immigration-related unfair
employment practices provisions in section 274B of the INA could subject the Employer to civil penalties,
back pay awards, and other sanctions, and violations of Title VII could subject the Employer to back pay
awards, compensatory and punitive damages. Violations of either section 274B of the INA or Title VII may
also lead to the termination of its participation in E-Verify. If the Employer has any questions relating to the
anti-discrimination provision, it should contact OSC at 1-800-255-8155 or 1-800-237-2515 (TDD).
15.The Employer agrees that it will use the information it receives from E-Verify only to confirm the
employment eligibility of employees as authorized by this MOU. The Employer agrees that it will safeguard
this information, and means of access to it (such as PINS and passwords), to ensure that it is not used for
any other purpose and as necessary to protect its confidentiality, including ensuring that it is not
disseminated to any person other than employees of the Employer who are authorized to perform the
Employer's responsibilities under this MOU, except for such dissemination as may be authorized in advance
by SSA or DHS for legitimate purposes.
16.The Employer agrees to notify DHS immediately in the event of a breach of personal information.
Breaches are defined as loss of control or unauthorized access to E-Verify personal data. All suspected or
confirmed breaches should be reported by calling 1-888-464-4218 or via email at E-Verify@uscis.dhs.gov.
Please use “Privacy Incident – Password” in the subject line of your email when sending a breach report to
E-Verify.
17.The Employer acknowledges that the information it receives from SSA is governed by the Privacy Act (5
U.S.C. § 552a(i)(1) and (3)) and the Social Security Act (42 U.S.C. 1306(a)). Any person who obtains this
information under false pretenses or uses it for any purpose other than as provided for in this MOU may be
subject to criminal penalties.
18.The Employer agrees to cooperate with DHS and SSA in their compliance monitoring and evaluation of
E-Verify, which includes permitting DHS, SSA, their contractors and other agents, upon
Page 4 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1162 of 3773
Company ID Number:
reasonable notice, to review Forms I-9 and other employment records and to interview it and its employees
regarding the Employer’s use of E-Verify, and to respond in a prompt and accurate manner to DHS requests
for information relating to their participation in E-Verify.
19.The Employer shall not make any false or unauthorized claims or references about its participation in
E-Verify on its website, in advertising materials, or other media. The Employer shall not describe its services
as federally-approved, federally-certified, or federally-recognized, or use language with a similar intent on
its website or other materials provided to the public. Entering into this MOU does not mean that E-Verify
endorses or authorizes your E-Verify services and any claim to that effect is false.
20.The Employer shall not state in its website or other public documents that any language used therein
has been provided or approved by DHS, USCIS or the Verification Division, without first obtaining the prior
written consent of DHS.
21.The Employer agrees that E-Verify trademarks and logos may be used only under license by DHS/USCIS
(see M-795 (Web)) and, other than pursuant to the specific terms of such license, may not be used in any
manner that might imply that the Employer’s services, products, websites, or publications are sponsored
by, endorsed by, licensed by, or affiliated with DHS, USCIS, or E-Verify.
22.The Employer understands that if it uses E-Verify procedures for any purpose other than as authorized
by this MOU, the Employer may be subject to appropriate legal action and termination of its participation in
E-Verify according to this MOU.
B. RESPONSIBILITIES OF FEDERAL CONTRACTORS
1.If the Employer is a Federal contractor with the FAR E-Verify clause subject to the employment
verification terms in Subpart 22.18 of the FAR, it will become familiar with and comply with the most current
version of the E-Verify User Manual for Federal Contractors as well as the E-Verify Supplemental Guide for
Federal Contractors.
2.In addition to the responsibilities of every employer outlined in this MOU, the Employer understands that
if it is a Federal contractor subject to the employment verification terms in Subpart 22.18 of the FAR it must
verify the employment eligibility of any “employee assigned to the contract” (as defined in FAR 22.1801).
Once an employee has been verified through E-Verify by the Employer, the Employer may not create a
second case for the employee through E-Verify.
a.An Employer that is not enrolled in E-Verify as a Federal contractor at the time of a contract award
must enroll as a Federal contractor in the E-Verify program within 30 calendar days of contract award
and, within 90 days of enrollment, begin to verify employment eligibility of new hires using E-Verify. The
Employer must verify those employees who are working in the United States, whether or not they are
assigned to the contract. Once the Employer begins verifying new hires, such verification of new hires
must be initiated within three business days after the hire date. Once enrolled in E-Verify as a Federal
contractor, the Employer must begin verification of employees assigned to the contract within 90
calendar days after the date of enrollment or within 30 days of an employee’s assignment to the
contract, whichever date is later.
Page 5 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1163 of 3773
Company ID Number:
b.Employers enrolled in E-Verify as a Federal contractor for 90 days or more at the time of a contract
award must use E-Verify to begin verification of employment eligibility for new hires of the Employer
who are working in the United States, whether or not assigned to the contract, within three business
days after the date of hire. If the Employer is enrolled in E-Verify as a Federal contractor for 90 calendar
days or less at the time of contract award, the Employer must, within 90 days of enrollment, begin to
use E-Verify to initiate verification of new hires of the contractor who are working in the United States,
whether or not assigned to the contract. Such verification of new hires must be initiated within three
business days after the date of hire. An Employer enrolled as a Federal contractor in E-Verify must begin
verification of each employee assigned to the contract within 90 calendar days after date of contract
award or within 30 days after assignment to the contract, whichever is later.
c.Federal contractors that are institutions of higher education (as defined at 20 U.S.C. 1001(a)), state
or local governments, governments of Federally recognized Indian tribes, or sureties performing under
a takeover agreement entered into with a Federal agency under a performance bond may choose to
only verify new and existing employees assigned to the Federal contract. Such Federal contractors may,
however, elect to verify all new hires, and/or all existing employees hired after November 6, 1986.
Employers in this category must begin verification of employees assigned to the contract within 90
calendar days after the date of enrollment or within 30 days of an employee’s assignment to the
contract, whichever date is later.
d.Upon enrollment, Employers who are Federal contractors may elect to verify employment eligibility
of all existing employees working in the United States who were hired after November 6, 1986, instead
of verifying only those employees assigned to a covered Federal contract. After enrollment, Employers
must elect to verify existing staff following DHS procedures and begin
E-Verify verification of all existing employees within 180 days after the election.
e. The Employer may use a previously completed Form I-9 as the basis for creating an E-Verify case for
an employee assigned to a contract as long as:
i.That Form I-9 is complete (including the SSN) and complies with Article II.A.6,
ii.The employee’s work authorization has not expired, and
iii.The Employer has reviewed the Form I-9 information either in person or in communications
with the employee to ensure that the employee’s Section 1, Form I-9 attestation has not changed
(including, but not limited to, a lawful permanent resident alien having become a naturalized
U.S. citizen).
f.The Employer shall complete a new Form I-9 consistent with Article II.A.6 or update the previous
Form I-9 to provide the necessary information if:
i.The Employer cannot determine that Form I-9 complies with Article II.A.6,
ii.The employee’s basis for work authorization as attested in Section 1 has expired or changed,
or
iii.The Form I-9 contains no SSN or is otherwise incomplete.
Note: If Section 1 of Form I-9 is otherwise valid and up-to-date and the form otherwise complies with
Page 6 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1164 of 3773
Company ID Number:
Article II.C.5, but reflects documentation (such as a U.S. passport or Form I-551) that expired after
completing Form I-9, the Employer shall not require the production of additional documentation, or use the
photo screening tool described in Article II.A.5, subject to any additional or superseding instructions that
may be provided on this subject in the E-Verify User Manual.
g.The Employer agrees not to require a second verification using E-Verify of any assigned employee
who has previously been verified as a newly hired employee under this MOU or to authorize
verification of any existing employee by any Employer that is not a Federal contractor based on this
Article.
3. The Employer understands that if it is a Federal contractor, its compliance with this MOU is a
performance requirement under the terms of the Federal contract or subcontract, and the Employer
consents to the release of information relating to compliance with its verification responsibilities under this
MOU to contracting officers or other officials authorized to review the Employer’s compliance with Federal
contracting requirements.
C. RESPONSIBILITIES OF SSA
1.SSA agrees to allow DHS to compare data provided by the Employer against SSA’s database. SSA sends
DHS confirmation that the data sent either matches or does not match the information in SSA’s database.
2.SSA agrees to safeguard the information the Employer provides through E-Verify procedures. SSA also
agrees to limit access to such information, as is appropriate by law, to individuals responsible for the
verification of Social Security numbers or responsible for evaluation of E-Verify or such other persons or
entities who may be authorized by SSA as governed by the Privacy Act (5 U.S.C. § 552a), the Social Security Act
(42 U.S.C. 1306(a)), and SSA regulations (20 CFR Part 401).
3.SSA agrees to provide case results from its database within three Federal Government work days of the
initial inquiry. E-Verify provides the information to the Employer.
4.SSA agrees to update SSA records as necessary if the employee who contests the SSA tentative
nonconfirmation visits an SSA field office and provides the required evidence. If the employee visits an SSA
field office within the eight Federal Government work days from the date of referral to SSA, SSA agrees to
update SSA records, if appropriate, within the eight-day period unless SSA determines that more than eight
days may be necessary. In such cases, SSA will provide additional instructions to the employee. If the
employee does not visit SSA in the time allowed, E-Verify may provide a final nonconfirmation to the
employer.
Note: If an Employer experiences technical problems, or has a policy question, the employer should contact
E-Verify at 1-888-464-4218.
D. RESPONSIBILITIES OF DHS
1.DHS agrees to provide the Employer with selected data from DHS databases to enable the Employer to
conduct, to the extent authorized by this MOU:
a.Automated verification checks on alien employees by electronic means, and
Page 7 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1165 of 3773
Company ID Number:
b. Photo verification checks (when available) on employees.
2. DHS agrees to assist the Employer with operational problems associated with the Employer's
participation in E-Verify. DHS agrees to provide the Employer names, titles, addresses, and telephone
numbers of DHS representatives to be contacted during the E-Verify process.
3. DHS agrees to provide to the Employer with access to E-Verify training materials as well as an
E-Verify User Manual that contain instructions on E-Verify policies, procedures, and requirements for both SSA
and DHS, including restrictions on the use of E-Verify.
4.DHS agrees to train Employers on all important changes made to E-Verify through the use of mandatory
refresher tutorials and updates to the E-Verify User Manual. Even without changes to
E-Verify, DHS reserves the right to require employers to take mandatory refresher tutorials.
5.DHS agrees to provide to the Employer a notice, which indicates the Employer's participation in
E-Verify. DHS also agrees to provide to the Employer anti-discrimination notices issued by the Office of Special
Counsel for Immigration-Related Unfair Employment Practices (OSC), Civil Rights Division, U.S. Department of
Justice.
6.DHS agrees to issue each of the Employer’s E-Verify users a unique user identification number and
password that permits them to log in to E-Verify.
7.DHS agrees to safeguard the information the Employer provides, and to limit access to such information to
individuals responsible for the verification process, for evaluation of E-Verify, or to such other persons or
entities as may be authorized by applicable law. Information will be used only to verify the accuracy of Social
Security numbers and employment eligibility, to enforce the INA and Federal criminal laws, and to administer
Federal contracting requirements.
8.DHS agrees to provide a means of automated verification that provides (in conjunction with SSA
verification procedures) confirmation or tentative nonconfirmation of employees' employment eligibility
within three Federal Government work days of the initial inquiry.
9.DHS agrees to provide a means of secondary verification (including updating DHS records) for employees
who contest DHS tentative nonconfirmations and photo mismatch tentative nonconfirmations. This provides
final confirmation or nonconfirmation of the employees' employment eligibility within 10 Federal Government
work days of the date of referral to DHS, unless DHS determines that more than 10 days may be necessary. In
such cases, DHS will provide additional verification instructions.
ARTICLE III
REFERRAL OF INDIVIDUALS TO SSA AND DHS
A. REFERRAL TO SSA
1. If the Employer receives a tentative nonconfirmation issued by SSA, the Employer must print the notice as
directed by E-Verify. The Employer must promptly notify employees in private of the finding and provide
them with the notice and letter containing information specific to the employee’s E-Verify case.
Page 8 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1166 of 3773
Company ID Number:
The Employer also agrees to provide both the English and the translated notice and letter for employees
with limited English proficiency to employees. The Employer agrees to provide written referral instructions
to employees and instruct affected employees to bring the English copy of the letter to the SSA. The
Employer must allow employees to contest the finding, and not take adverse action against employees if
they choose to contest the finding, while their case is still pending.
2.The Employer agrees to obtain the employee’s response about whether he or she will contest the tentative
nonconfirmation as soon as possible after the Employer receives the tentative nonconfirmation. Only the
employee may determine whether he or she will contest the tentative nonconfirmation.
3.After a tentative nonconfirmation, the Employer will refer employees to SSA field offices only as directed
by E-Verify. The Employer must record the case verification number, review the employee information
submitted to E-Verify to identify any errors, and find out whether the employee contests the tentative
nonconfirmation. The Employer will transmit the Social Security number, or any other corrected employee
information that SSA requests, to SSA for verification again if this review indicates a need to do so.
4.The Employer will instruct the employee to visit an SSA office within eight Federal Government work days.
SSA will electronically transmit the result of the referral to the Employer within 10 Federal Government work
days of the referral unless it determines that more than 10 days is necessary.
5.While waiting for case results, the Employer agrees to check the E-Verify system regularly for case updates.
6.The Employer agrees not to ask the employee to obtain a printout from the Social Security Administration
number database (the Numident) or other written verification of the SSN from the SSA.
B. REFERRAL TO DHS
1.If the Employer receives a tentative nonconfirmation issued by DHS, the Employer must promptly notify
employees in private of the finding and provide them with the notice and letter containing information
specific to the employee’s E-Verify case. The Employer also agrees to provide both the English and the
translated notice and letter for employees with limited English proficiency to employees. The Employer must
allow employees to contest the finding, and not take adverse action against employees if they choose to
contest the finding, while their case is still pending.
2.The Employer agrees to obtain the employee’s response about whether he or she will contest the tentative
nonconfirmation as soon as possible after the Employer receives the tentative nonconfirmation. Only the
employee may determine whether he or she will contest the tentative nonconfirmation.
3.The Employer agrees to refer individuals to DHS only when the employee chooses to contest a tentative
nonconfirmation.
4.If the employee contests a tentative nonconfirmation issued by DHS, the Employer will instruct the
Page 9 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1167 of 3773
Company ID Number:
employee to contact DHS through its toll-free hotline (as found on the referral letter) within eight Federal
Government work days.
5.If the Employer finds a photo mismatch, the Employer must provide the photo mismatch tentative
nonconfirmation notice and follow the instructions outlined in paragraph 1 of this section for tentative
nonconfirmations, generally.
6.The Employer agrees that if an employee contests a tentative nonconfirmation based upon a photo
mismatch, the Employer will send a copy of the employee’s Form I-551, Form I-766, U.S. Passport, or passport
card to DHS for review by:
a.Scanning and uploading the document, or
b.Sending a photocopy of the document by express mail (furnished and paid for by the employer).
7.The Employer understands that if it cannot determine whether there is a photo match/mismatch, the
Employer must forward the employee’s documentation to DHS as described in the preceding paragraph. The
Employer agrees to resolve the case as specified by the DHS representative who will determine the photo
match or mismatch.
8.DHS will electronically transmit the result of the referral to the Employer within 10 Federal Government
work days of the referral unless it determines that more than 10 days is necessary.
9.While waiting for case results, the Employer agrees to check the E-Verify system regularly for case updates.
ARTICLE IV
SERVICE PROVISIONS
A. NO SERVICE FEES
1. SSA and DHS will not charge the Employer for verification services performed under this MOU. The
Employer is responsible for providing equipment needed to make inquiries. To access E-Verify, an Employer
will need a personal computer with Internet access.
ARTICLE V
MODIFICATION AND TERMINATION
A. MODIFICATION
1. This MOU is effective upon the signature of all parties and shall continue in effect for as long as the SSA
and DHS operates the E-Verify program unless modified in writing by the mutual consent of all parties.
2. Any and all E-Verify system enhancements by DHS or SSA, including but not limited to E-Verify checking
against additional data sources and instituting new verification policies or procedures, will be covered under
this MOU and will not cause the need for a supplemental MOU that outlines these changes.
Page 10 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1168 of 3773
Company ID Number:
B. TERMINATION
1.The Employer may terminate this MOU and its participation in E-Verify at any time upon 30 days prior
written notice to the other parties.
2.Notwithstanding Article V, part A of this MOU, DHS may terminate this MOU, and thereby the Employer’s
participation in E-Verify, with or without notice at any time if deemed necessary because of the requirements
of law or policy, or upon a determination by SSA or DHS that there has been a breach of system integrity or
security by the Employer, or a failure on the part of the Employer to comply with established E-Verify
procedures and/or legal requirements. The Employer understands that if it is a Federal contractor, termination
of this MOU by any party for any reason may negatively affect the performance of its contractual
responsibilities. Similarly, the Employer understands that if it is in a state where E-Verify is mandatory,
termination of this by any party MOU may negatively affect the Employer’s business.
3.An Employer that is a Federal contractor may terminate this MOU when the Federal contract that requires
its participation in E-Verify is terminated or completed. In such cases, the Federal contractor must provide
written notice to DHS. If an Employer that is a Federal contractor fails to provide such notice, then that
Employer will remain an E-Verify participant, will remain bound by the terms of this MOU that apply to non-
Federal contractor participants, and will be required to use the E-Verify p rocedures to verify the employment
eligibility of all newly hired employees.
4.The Employer agrees that E-Verify is not liable for any losses, financial or otherwise, if the Employer is
terminated from E-Verify.
ARTICLE VI
PARTIES
A.Some or all SSA and DHS responsibilities under this MOU may be performed by contractor(s), and SSA and
DHS may adjust verification responsibilities between each other as necessary. By separate agreement with
DHS, SSA has agreed to perform its responsibilities as described in this MOU.
B.Nothing in this MOU is intended, or should be construed, to create any right or benefit, substantive or
procedural, enforceable at law by any third party against the United States, its agencies, officers, or
employees, or against the Employer, its agents, officers, or employees.
C.The Employer may not assign, directly or indirectly, whether by operation of law, change of control or
merger, all or any part of its rights or obligations under this MOU without the prior written consent of DHS,
which consent shall not be unreasonably withheld or delayed. Any attempt to sublicense, assign, or transfer
any of the rights, duties, or obligations herein is void.
D.Each party shall be solely responsible for defending any claim or action against it arising out of or related to
E-Verify or this MOU, whether civil or criminal, and for any liability wherefrom, including (but not limited to)
any dispute between the Employer and any other person or entity regarding the applicability of Section 403(d)
of IIRIRA to any action taken or allegedly taken by the Employer.
Page 11 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1169 of 3773
Company ID Number:
E. The Employer understands that its participation in E-Verify is not confidential information and may be
disclosed as authorized or required by law and DHS or SSA policy, including but not limited to, Congressional
oversight, E-Verify publicity and media inquiries, determinations of compliance with Federal contractual
requirements, and responses to inquiries under the Freedom of Information Act (FOIA).
F. The individuals whose signatures appear below represent that they are authorized to enter into this MOU
on behalf of the Employer and DHS respectively. The Employer understands that any inaccurate statement,
representation, data or other information provided to DHS may subject the Employer, its subcontractors, its
employees, or its representatives to: (1) prosecution for false statements pursuant to 18 U.S.C. 1001 and/or; (2)
immediate termination of its MOU and/or; (3) possible debarment or suspension.
G. The foregoing constitutes the full agreement on this subject between DHS and the Employer.
To be accepted as an E-Verify participant, you should only sign the Employer’s Section of the signature
page. If you have any questions, contact E-Verify at 1-888-464-4218.
Page 12 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1170 of 3773
Company ID Number:
Approved by:
Employer
Name (Please Type or Print) Title
Signature Date
Department of Homeland Security – Verification Division
Name (Please Type or Print) Title
Signature Date
Page 13 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
USCIS Verification Division
11/27/2023
Ning Diaz
Electronically Signed
LECIP Inc
11/27/2023
Electronically Signed
2328571
Page 1171 of 3773
Company ID Number:
Information Required for the E-Verify Program
Information relating to your Company:
Company Name
Company Facility Address
Company Alternate Address
County or Parish
Employer Identification Number
North American Industry
Classification Systems Code
Parent Company
Number of Employees
Number of Sites Verified for
Page 14 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
LECIP Inc
DU PAGE
336
10 to 19
2328571
881 IL Route 83
Bensenville, IL 60106
272014336
1 site(s)
Page 1172 of 3773
Company ID Number:
Are you verifying for more than 1 site? If yes, please provide the number of sites verified for in each State:
Page 15 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
IL 1
2328571
Page 1173 of 3773
Company ID Number:
Information relating to the Program Administrator(s) for your Company on policy questions or operational
problems:
Page 16 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
Email
Email
3126262525
3126262525
Linda Rozanski
Ning Diaz
2328571
Name
Name
Phone Number
Phone Number
Fax
Fax
officeadmin@lecipinc.com
officeadmin@lecipinc.com
Page 1174 of 3773
Company ID Number:
This list represents the first 20 Program Administrators listed for this company.
Page 17 of 17 E-Verify MOU for Employers | Revision Date 06/01/13
2328571
Page 1175 of 3773
Page 1176 of 3773
Page 1177 of 3773
Page 1178 of 3773
Page 1179 of 3773
Page 1180 of 3773
Page 1181 of 3773
Page 1182 of 3773
Page 1183 of 3773
Page 1184 of 3773
Page 1185 of 3773
Page 1186 of 3773
Addendum #3
Date: December 7, 2023
From: Kristofer Lopez, Procurement Strategist
To: Interested Bidders
Subject: Addendum #3 Collier County Transit Electronic Farebox
The following clarifications are issued as an addendum:
Change 1:
PROPOSAL OPENING
DAY/DATE/TIME:
THURSDAY, December 7, 2023 THURSDAY, DECEMBER 19,
2023 at 3:00 PM EST
If you require additional information, please post a question on our Bid Sync (www.bidsync.com) bidding
platform under the solicitation for this project.
Please sign below and return a copy of this Addendum with your submittal for the above
referenced solicitation.
(Signature)
Date
(Name of Firm)
Email: Kristofer.lopez@colliercountyfl.gov
Telephone: (239) 252-8375
LECIP Inc.
7 December, 2023
Page 1187 of 3773
Page 1188 of 3773
Page 1189 of 3773
Page 1190 of 3773
Page 1191 of 3773
Page 1192 of 3773
Page 1193 of 3773
Page 1194 of 3773
Page 1195 of 3773
Page 1196 of 3773
Page 1197 of 3773
Page 1198 of 3773
Page 1199 of 3773
Page 1200 of 3773
Page 1201 of 3773
Page 1202 of 3773
Page 1203 of 3773
Page 1204 of 3773
Page 1205 of 3773
Page 1206 of 3773
Researching the LECIP Solution
Beloit’s transit team was duly impressed with the LECIP proposal
and demonstration, but they did not know as much about LECIP
as a provider of fare collection solutions. They learned through
their research that LECIP has been a proven market leader in
Japan and throughout Asia since 1953 in farebox collection
equipment and support, as well as in transportation lighting
solutions. They also learned that LECIP has successful installations
across the United States. They were also quite pleased to learn
that LECIP has a corporate office and distribution facilities less
than 90 minutes away in Bensenville, Illinois, with manufacturing in
both New York and Illinois.
What was even more pleasing to the Beloit team was the quality of references they received
from LECIP’s long-term customers outside the USA as well as their newer customers in
America. According to Akio Fujii, Chief Operating Officer of LECIP Inc. “I believe that LECIP’s
commitment to developing business in the US Transit market based on our strong fare
collection references in Japan, Asia, and other countries had a positive influence over Beloit’s
decision to partner with us for the program.”4Page 1207 of 3773
LECIP Installation
LECIP also observed that passenger satisfaction was almost immediately enhanced, as had
been the hope of the Beloit Transit team, because the new system afforded the drivers
another opportunity to connect with the passengers and “put them at ease.” This was
especially important because many of the Beloit Transit System’s passengers are members of
the City’s older population.
Thompson, Operations Manager of the City of Beloit, Wisconsin’s transit system, confirmed
this on behalf of Beloit Transit: “The drivers all loved the smaller Fareboxes and their ease of
use, and the passengers quickly accepted them, despite it being a new technology.”
Information is King!
One of the greatest advantages to the new
LECIP system is the automated reporting
that the new system affords the City of
Beloit. Previously, there had been no ability
to receive reporting from the old farebox
systems. But the new LECIP system is
connected via Wi-Fi so that the fare
collection data is transferred automatically to
the management team to assist in counting
fares, validating ridership, and making
management decisions.
With the self-contained cashbox vaulting system, Beloit Transit no longer needs to
manually extract fares from each Farebox. In an active infectious disease environment, this
also means that transit employees no longer manually interact with potentially
contaminated bills or coins during revenue service. Information is also paramount to the
passengers. The LECIP LF-7000 Farebox presents the boarding passenger with a large color
display, backlit coin and bill location, as well as status indication, along with audible
prompts creating an intuitive passenger interface.
Partnering with LECIP a True Win-Win-Win
Because the installation and implementation of the new LECIP fare-collection system was
so successful, the City of Beloit has determined it to be a Win-Win-Win. The LECIP team
earned a win for designing, installing, and supporting a fare-collection system that
completely meets the needs of Beloit Transit. The City of Beloit transit team earned a win
because they resolved several issues, including the need for fare-collection data, an
expedited boarding process, and reduced interactions between transit personnel and the
fares that have been collected. But, most importantly, the Beloit Transit System
passengers are the big winners – for they are the beneficiaries of the convenient new
system that makes riding the bus even easier than it had been.5Page 1208 of 3773
6Page 1209 of 3773
Page 1210 of 3773
"With the TouchPasssystem well underway toward implementation, the RVTD team turned its attention toward
automation of the cash fare collection process. RVTD needed to ensure that they offered RVTD passengers who
preferred to pay with cash and tokens the best possible solution to pay their fares.
“We actually had to wait for the market to catch up with us,” said Paige West, RVTD Senior Planner, who was a
member of the procurement and selection evaluation team. “The typical fare collection and payment system solutions
from several of the market’s largest providers didn’t fit our needs. So, we crafted an RFP that included options for
integration with the TouchPasssystem, but focused primarily on our cash collection and processing needs.”
RVTD’s Associate Planner and Project Manager for the project, Jon Sullivan, said that the entire RFP process took a
little more than a year from initial inputs to final selection. During the process, the LECIP solution rose to the top.
“Other proposals were simply not as responsive [as LECIP’s],” said Sullivan. “The other companies wanted us to fit our
needs to their existing solutions, but LECIP approached our challenges the same way we did and maintained a cost
structure that worked within our budget. So, we selected the LECIP solution, because we knew that the LECIP solution
would be tailored to our needs and accomplish what we needed to maximize our customers’ satisfaction with the final
product.”
Comments from RVTD
"A lot of work went into integrating our automated fare payment and cash fare collection systems, and we are
so grateful to both LECIP and Delerrok for coordinating their efforts with very little need for our RVTD team to
get involved. Our passengers have embraced the new fare systems and we know that it is easier to ride our
buses than ever before."
QR Code ticket integration
Delerrok delivered the initial payment system of the TouchPass electronic fare payment system.
Integration with Equans CAD/AVL
RVTD issued an RFP for a new CAD/AVL system in 2020. One of the requirements in the RFP was integration with
the existing LECIP farebox. After Equans was awarded with the contract, LECIP worked closely with Equans to
Implement the following functions;
- Single point logon
- Geotagging of farebox log files with GPS coordinates and stop ID
- Reporting with data provided from CAD/AVL
8Page 1211 of 3773
9Page 1212 of 3773
Page 1213 of 3773
Page 1214 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 1
COLLIER COUNTY
SOLICITATION NO.: 23-8166
REQUEST FOR PROPOSAL (RFP)
FOR
COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL
3. EQUIPMENT FUNCTIONALITY AND COVERAGE
Submitted by LECIP Inc.
881 IL Route 83 Bensenville, IL 60106
(Tel) 312-626-2525 Fax 312-626-2524
Page 1215 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 2
Statement of Confidentiality
This document is in response to SOLICITATION NO.: 23-8166 REQUEST FOR PROPOSAL (RFP) FOR
COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX, released by COLLIER COUNTY on
October 28th, 2023
The information enclosed is of competitive nature.
This document contains information originated or owned by LECIP. Neither this document nor the
information disclosed herein shall be reproduced or transferred to other documents or used or
disclosed to others for manufacturing or any other purpose except as specifically authorized in
writing by LECIP
Page 1216 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 3
CONTENTS
1. System Overview ....................................................................................................................................... 5
2. Bus Layer ....................................................................................................................................................... 8
2.1 Farebox ......................................................................................................................................................... 8
2.1.1 Key Features ........................................................................................................................... 9
2.1.2 Fare Processing ................................................................................................................... 10
2.1.2.1 Coin Handling ............................................................................................... 10
2.1.2.2 Bill Handling ................................................................................................. 12
2.1.3 Passenger Interface ........................................................................................................... 12
2.1.3.1 Passenger Display ...................................................................................... 12
2.1.3.2 Audible Tone and Voice Messages ....................................................... 14
2.1.4 Operator Interface ............................................................................................................. 14
2.1.4.1 OCU Display .................................................................................................. 14
2.1.4.2 OCU Functions.............................................................................................. 15
2.1.4.3 Audible Tone ................................................................................................ 17
2.1.5 Construction ......................................................................................................................... 17
2.1.6 Farebox Operating Modes .............................................................................................. 22
2.1.6.1 Revenue Registration Mode Settings.................................................. 22
2.1.6.2 Operation Mode Settings ......................................................................... 23
2.1.6.3 Power Mode Settings ................................................................................ 23
2.1.7 Cashbox .................................................................................................................................. 23
2.1.8 Data .......................................................................................................................................... 25
2.1.8.1 Farebox Log - Transaction Log.............................................................. 25
2.1.8.2 Farebox Log - Operation Log ................................................................. 26
2.1.8.3 Status Data ..................................................................................................... 27
2.1.8.4 Configuration Data - Farebox Settings ............................................... 27
2.1.8.5 Configuration Data - Fare Table ........................................................... 27
2.1.8.6 Configuration Data – Farebox Access Card Setting ...................... 28
2.1.9 Clock/Time Zone ................................................................................................................ 28
2.1.10 Application ............................................................................................................................ 28
2.1.11 Memory .................................................................................................................................. 28
2.1.12 Data Protection and Integrity........................................................................................ 28
2.1.13 Self-Diagnostics ................................................................................................................... 29
2.1.14 Communication ................................................................................................................... 30
2.1.15 Technical Specification Summary ............................................................................... 30
3. Garage Layer ............................................................................................................................................. 35
3.1 Overview .................................................................................................................................................... 35
3.2 Revenue Collection Vault .................................................................................................................... 35
3.2.1 Overview ................................................................................................................................ 35
3.2.2 Construction ......................................................................................................................... 36
Page 1217 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 4
3.2.3 Cash Revenue Transfer .................................................................................................... 36
3.2.4 Locks and Keys .................................................................................................................... 36
3.2.5 Technical Specification Summary ............................................................................... 37
3.2.6 Access Card Activation Device ...................................................................................... 37
3.3 Revenue Transfer Process .................................................................................................................. 38
3.3.1 Revenue Transfer Process Flow ................................................................................... 38
3.3.1.1 Data Recorded .............................................................................................. 40
3.4 Test Bench ................................................................................................................................................. 40
3.5 Audit Unit (Portable Vault) ................................................................................................................ 41
3.6 Training Farebox (Option) ................................................................................................................. 41
4. Back Office System Layer .................................................................................................................... 42
4.1 Delivery of the System ......................................................................................................................... 42
4.2 Data Transfer between Field Devices and Central System ................................................... 42
4.3 Central System Web Portal ................................................................................................................ 43
4.3.1 Device Management Module ......................................................................................... 45
4.3.1.1 Farebox ........................................................................................................... 45
4.3.1.2 Vault ................................................................................................................. 47
4.3.1.3 Access Card Activation Device .............................................................. 47
4.3.2 Fare Management Module .............................................................................................. 47
4.3.3 Maintenance Module ......................................................................................................... 48
4.3.3.1 Fleet Management ...................................................................................... 48
4.3.3.2 Device Status – Farebox ........................................................................... 49
4.3.3.3 Device Status – Vault/ACAD ................................................................... 49
4.3.3.4 Device History .............................................................................................. 49
4.3.3.5 Error Codes ................................................................................................... 50
4.3.3.6 Component .................................................................................................... 50
4.3.4 Reports Module ................................................................................................................... 50
4.3.4.1 Canned (Pre-Defined) Reports .............................................................. 50
4.3.4.2 Cash Audit ...................................................................................................... 54
4.3.4.3 Email Reports ............................................................................................... 54
4.3.4.4 Day Definition .............................................................................................. 55
4.3.5 Administration Module .................................................................................................... 55
4.3.5.1 Users ................................................................................................................ 56
4.3.5.2 Defining User Roles.................................................................................... 56
4.3.5.3 Access Card ................................................................................................... 56
4.3.5.4 Distributions ................................................................................................. 57
4.3.5.5 Test Distributions ....................................................................................... 57
4.3.5.6 Fleet Distributions ..................................................................................... 57
4.3.5.7 Software Packages ..................................................................................... 58
4.3.6 System Alert Module ......................................................................................................... 58
4.3.7 Client ........................................................................................................................................ 58
Page 1218 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 5
1. SYSTEM OVERVIEW
The System Architecture consists of 3 key Layers:
■ Layer 1A: Bus Layer
■ Layer 1B: Garage Layer
■ Layer 2: Back Office System Layer
The equipment shown in the system architecture diagram on the next page is segregated into the
layers mentioned.
Page 1219 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 6
Farebox System Architecture with
Back Office System on AWS
Page 1220 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 7
The Bus Layer (Layer 1A) consists of the LF-7000 Validating Farebox, for passenger fare payment,
CAD/AVL Equipment (provided by other) for location retrieval/single-point-login and Onboard
Modem WiFi Router (provided by other) for data transfer. The LF-7000 Validating Farebox will use
either J1708 or Ethernet interfaces for integration with CAD/AVL Equipment. The Onboard Modem
WiFi Router connects the Bus (Layer 1A) to the Garage (Layer 1B) and Back Office (Layer 2) via
garage WiFi and/or cellular network.
The Garage Layer (Layer 1B) consists of Revenue Collection Vault used to physically dump and
store cash collected by the Farebox/Cashbox, Access Card Activation Device for activation of Access
Card, and Garage WiFi Router for data transfer between the Bus (Layer 1A) and the Garage (Layer
1B) and between the Garage (Layer 1B) and Back Office (Layer 2). In the garage, the Test Bench and
Audit Unit will be also installed. The Test Bench will communicate with the back office system layer
through the Collier Area Transit garage/office network.
The Back Office System Layer (Layer 2) consists of the Central System application and cloud
computing services provided by Amazon Web Services. All the required files for the farebox system
are either stored or generated on the Central System and sent to the appropriate devices. Collier Area
Transit administrators and staff will be able to access Central System web portal to change
equipment parameters and fare tables as needed. Collier Area Transit administrators and staff will
also be able to create and view reports with the equipment data stored in the database.
Page 1221 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 8
2. BUS LAYER
2.1 FAREBOX
The LF-7000 validating farebox hardware consists of the following items:
■ Validating Coin Acceptor (Coin Bypass mode equipped)
■ Coin Return Slot
■ Validating Bill Acceptor
■ Cashbox Compartment and Cashbox
■ Passenger Display (3.5 inch Color LCD)
■ Speaker
■ Operation Control Unit (built-in 5.0 inch Color LCD Touch Panel)
■ Access Card Reader (only for agency employees)
■ Controller Board (Main Logic Board)
■ Power Supply Board
■ Mounting Base
The farebox is housed by stainless steel and is specialized in cash transactions; validating, accepting
and securely storing coins and bills. The operator control unit (OCU) is built into the top cover of the
farebox, which saves onboard “real estates” necessary for the farebox. The photos below show the
farebox.
Page 1222 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 9
2.1.1 Key Features
The validating farebox has the following key features to meet all of Collier Area Transit’s passenger
and operator needs.
■ Cash Handling
■ Passenger and Operator Displays
■ ADA Compliant and “Talking” Functionality
■ Modular Design
■ Secure Cashbox Door
■ Data Collection and Transfer
Cash Handling
The farebox accepts and validates “street quality” U.S. coins and bills. The carefully designed coin slot
allows a passenger to insert one coin at a time so that the coin validator can validate coins one by one.
Bills are inserted and validated one at a time. Coins and bills that are successfully validated are
deposited into a cashbox that is securely located at the bottom compartment of the farebox.
Fare values and detailed information are displayed on the operator control unit (OCU) and passenger
display on the farebox for each transaction that takes places at the farebox.
Invalid, counterfeit, and/or foreign coins and slugs are rejected and returned to the coin return while
rejected bills are returned to the passenger through the bill insertion slot.
In addition, the farebox provides coin bypass functionality for revenue collection in the event that
proper validation is not possible.
Passenger and Operator Displays
All fare information, transactions, and messages that occur on the farebox for both passengers and
employees are displayed on the passenger display and OCU display.
The passenger display is positioned and equipped with an anti-glare clear cover so it is visible to the
passenger when entering the bus. This allows passengers to easily comprehend and view the fare
information which would help in reducing dwell time and customers to easily understand the fare
payment system.
The OCU is also equipped with an anti-glare clear cover and has a large viewing-angle so that the
screen is visible to bus operators from a seated position under a full range of ambient illumination
conditions typical in a bus environment. This allows bus operators to easily check the status of the
farebox and passenger transactions and minimizes operations with passengers, letting the operator
focus on driving.
ADA Compliant and “Talking” Functionality
LECIP has verified that the farebox meets the Americans with Disabilities Act (ADA) requirements.
This includes the “talking” feature of our farebox that provides audio and voice messages related to
transactions and messages. Not only does this feature help visually impaired passengers who want
to take the bus, it also enhances the overall passenger ride experience.
Page 1223 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 10
Modular Design
All components in the farebox are modular in construction so that they can be removed for inspection
and replacement without any tools. All major components of the farebox are fully interchangeable.
This functionality would make maintenance procedures and service work on the farebox more
efficient and quicker.
Secure Cashbox Door
The farebox provides a secure cashbox access door that is mechanically locked to the lower
compartment of the farebox. A pre-registered and activated access card must be tapped on the
farebox access card reader and authorized in order for the cashbox access door to be unlocked.
Data Collection and Transfer
The transaction log files are uploaded to the back office system either via cellular network or garage
WiFi. The collected data fully covers what is needed for analysis and reporting later on (e.g.
transaction details, events, alarms, errors). When cellular network is unavailable, the farebox will
store transaction logs until the cellular network becomes available or the bus enters the garage WiFi
range. The farebox is designed to erase transaction log files only after Central System successfully
received the files.
2.1.2 Fare Processing
The LECIP farebox is capable of handling all denominations of current US coins and bills.
Denominations to be enabled/disabled are configurable at the Central System and downloadable to
the farebox. Under the default setting, $50 and $100 bills are disabled.
2.1.2.1 Coin Handling
Accepting Coins
The LECIP coin handling unit provides the fastest coin handling speed that helps in reducing dwell
time of each passenger boarding the bus. The coin slot was designed to allow a passenger to insert
coins one by one to prevent coins from being jammed, while it helps to reduce the intervals between
coins.
Rejecting Coins
The coin acceptor automatically rejects and returns invalid, counterfeit, foreign coins, and slugs to
Page 1224 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 11
the passenger using the coin return. When multiple coins are dropped into the coin slot with a short
interval, the coin acceptor is capable of distinguishing between the valid and non-valid coins,
accepting the valid ones while rejecting the invalid ones to the coin return. As an indicator to the
passenger, the coin return illuminates when rejected coins are returned as seen in the figure below.
The passenger is also notified by audible announcement. The bus operator is notified by a text on the
OCU display.
Accepting Newly Issued Coins
When a new coin is issued by the U.S. government, there are ways to support that specific coin with
the current farebox with a firmware upgrade to the coin validator. When a next type of currency is
introduced, we will work with the coin validator vendor to upgrade the coin validation logic.
Coin Jam and Coin Bypass
When a coin jam cannot be cleared, the bus operator has the ability to use the bypass lever on the
back of the farebox allowing passengers to still be able to use the farebox for operation temporarily
without stopping the bus operation to get the coin validator fixed.
This bypass mode status is indicated on the OCU screen so that operators and maintenance staff can
easily check which fareboxes are in bypass mode. During coin bypass mode, all coins deposited
cannot and will not be validated by the farebox since the validator function is disabled.
An event data is also created and stored in the farebox when the coin bypass is activated / deactivated.
If the farebox is not powered at the time the coin bypass is activated or deactivated, the farebox
software recognizes the change of bypass state at the time of power-up and a transaction record is
created at that time.
In order to remove the Farebox from bypass mode, the technician will open the Farebox top cover
and physically reset the position of the coin validator. Other transactions including bill transactions
and tallies can still take place regardless of whether the coin bypass is ON or OFF.
Pull the lever
Page 1225 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 12
2.1.2.2 Bill Handling
Accepting Bills
The LECIP farebox offers a state-of-the-art bill handling unit for quick, accurate, and precise bill
payment validation.
The bill validator is capable of validating all legal existing U.S. bills presented in any of four (4)
orientations.
The farebox is capable of accepting and validating U.S. bills of “street quality”. Foreign bills,
counterfeit bills, partial bills and any other invalid bills are rejected and returned to the passenger
through the bill insertion slot.
The farebox is capable of validating, accepting, and registering a bill in approximately two (2) seconds.
The bill acceptor is equipped with beltless bill transport system to reduce maintenance costs. The bill
validator validates bills by optically reading the width and magnetically reading the material content,
and is capable of accurately and securely distinguishing valid bills by denomination.
Bill Override
LECIP farebox allows the operator to manually override bills on the validating farebox. The override
is performed by the operator by pressing a key on the OCU. The farebox records every instance that
the bill override button is used to make sure the button is not being abused.
This bill override feature is not always desired by agencies, and can be enabled or disabled from the
Central System.
Accepting Newly Issued Bills
In the case that a new bill is issued by the U.S. government, we will work with our bill validator
provider to upgrade the compatibility and validation capabilities.
2.1.3 Passenger Interface
2.1.3.1 Passenger Display
The passenger display resides on front side of the farebox top cover, and is a passenger-friendly, TFT
Page 1226 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 13
LCD (full color, full dot matrix, 3.5 inches, 320 x 240 dots) that clearly presents transaction data to
passengers. The LECIP full-dot matrix screen allows for displaying various kinds of information
including graphics in desired locations in desired sizes. The LECIP farebox passenger screen reduces
possible visibility conflicts with the bus operator and passengers.
Cash Transaction
During cash transactions, the passenger display can show the following information in the form of
messages and graphics.
■ Transaction Type (cash)
■ Passenger Class (full fare, discounted fare)
■ Transaction (Fare, Amount Paid)
The messages, character size, and layout are hardcoded. LECIP will work together with Collier Area
Transit to define the desired design of the display. The messages can be shown in multiple languages,
as long as the display size permits.
Display before transaction (left), during transaction (middle), after transaction (right)
The messages shown on the passenger display disappear when the next transaction has occurred or
a preset amount of time has elapsed. This preset time is configurable at the Central System and
downloadable to the farebox.
Tally (Free Transaction)
When the bus operator pushed a tally button on the OCU, tally type is displayed on the passenger
display.
Display after transaction
The messages shown on the passenger display disappear when the next transaction has occurred or
a preset amount of time has elapsed. This preset time is configurable at the Central System and
Page 1227 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 14
downloadable to the farebox.
2.1.3.2 Audible Tone and Voice Messages
LECIP is able to put additional audio instructions to go along with the message on the passenger
display to communicate with customers who are visually impaired.
The farebox is a “talking” farebox and its audio feature includes both audible tones and voice
messages. These voice files (wav. file format) can be recorded in English, Spanish, and other
languages if needed. For alerts, different default “beeping” noises can be set for different situations:
the completion of a fare transaction, fare rejection, or an error notification such as cashbox condition.
2.1.4 Operator Interface
The farebox has a built-in operator control unit (OCU) on back side of the top cover for operator
interface. The OCU utilizes color LCD touch panel providing information and control functionalities
necessary to operate the farebox by Collier Area Transit bus operator and maintenance staff. The
OCU is the perfect solution for agency staff by providing them with an easy-to-read visual interface,
noticeable alert events, and flexibility for configurations onboard. In addition to the indications and
messages on the OCU display, the farebox can produce various types of audible tones to alert the
operator of errors or events
2.1.4.1 OCU Display
Information that bus operators need to know are shown on a TFT LCD touch panel (full color, full dot
matrix, 5.0 inches, 800 x 480 dots). This user-friendly, easy-to-read display helps bus operators to
perform farebox tasks in a quick amount of time allowing them to efficiently carry out fare payment
tasks while still being able to drive safely in operation.
The display uses a glare resistant LCD panel with a back light, and is clearly readable in lighting
conditions ranging from bright sunlight to darkness and is visible for bus operators wearing
polarized sunglasses. Brightness of the display is also adjustable. The great viewing angle (-80° to
80°) of the display enables operators to see the information on the display from a seated position.
Using a full dot-matrix LCD allows the contents on the screen to be flexible for text placement, lines,
and complex characters.
Page 1228 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 15
2.1.4.2 OCU Functions
LECIP understands that a farebox system should ease and reduce driver operation so that they can
focus on the road. The LECIP OCU is developed based on our experience with transit agencies and
their concerns about operator user interface and the importance of balancing driver safety with
onboard flexibility. The OCU provides following principle functionalities;
■ Log-on/Log-off
■ Cash Transaction
■ Tally (Free Transaction)
■ Settings
Log-On/Log-Off
The farebox will be integrated with the existing CAD/AVL system for single point logon. The logon
process happens on the CAD/AVL MDT to start up both systems.
Alternatively, the farebox can be logged on by manually typing in the required information, such as
bus operator ID and Route ID, on the OCU.
Log-on Screen
All log-on attempts are recorded with the bus operator ID and date/time. Such information is
displayed on the OCU and the operator is prompted to confirm that the information is correct before
he/she begins running the routes. The OCU displays all entered selections and allows the operator to
correct any mistakes.
The farebox will automatically log-off after a configurable period of time (default time: 30 minutes)
during which no farebox activity has occurred. The farebox records and reports the automatic log-off
event to the Central System. The farebox will beep for a configurable period of time (default is 15
seconds) before initiating an auto-log off sequence to alert the bus operator. Once logged-off, the
farebox needs to be logged-on again.
Cash Transaction
Cash Windows are used to accept cash and to associate the cash with a fare product chosen by the
operator. In the Cash Windows, the operator can choose a fare product. Each Cash Window can
accommodate up to four fare products. If there are more than four fare products, OCU has the
capability to have multiple windows that can be navigated using the arrow keys (←/→). This screen
also shows date/time and operational messages and error messages if any at the bottom. There is
also a link (tab) to Tally Windows.
Page 1229 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 16
OCU Cash Window (left) and Cash Options Window (right)
Once cash is deposited to the farebox, the OCU display will automatically show the Cash Options
Window, in which fare amount and paid amount are shown. This screen also shows the following
buttons to facilitate the cash transaction;
■ Short Fare – Complete cash transaction with short fare. The deposited cash will be
registered as revenue associated with the fare product and ridership will be counted.
■ Dump – Complete cash transaction and dump the deposited cash. The deposited cash will be
registered as unclassified revenue and ridership will not be counted.
■ Extend – Reset the transaction timer (default is 30 seconds) which allows the passenger
more time to pay the remaining fare.
■ Products – Choose other fare product, if a correct fare product was not chosen before
deposition of money.
Once the deposited amount reaches the fare amount or Short Fare/Dump button is pushed, the Cash
Options Window will disappear and the default screen (Cash Window or Tally Window -
configurable) will be shown after the “OK Screen”.
Tally (Free Transaction)
Tally Windows are used to tally or count riders and to associate the riders with a tally typ e chosen
by the operator. Tally Windows can also accommodate a button for non-riders (e.g. bikes) for the
purpose to count the number of usages. In the Tally Window, the operator can choose a tally type.
Each Tally Window can accommodate up to four tally types. If there are more than four tally products,
OCU has the capability to have multiple screens that can be navigated using the arrow keys (←/→).
This screen also shows date/time and operational messages and error messages if any at the bottom.
There is also a link (tab) to Cash Windows.
OCU Tally Window
Page 1230 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 17
Once a tally type button is pushed, the default screen (Cash Window or Tally Window - configurable)
will be shown.
Settings
In the settings screen the operator can adjust the audio volume and display brightness. When a
maintenance technician logs on to the farebox with maintenance mode (refer to 2.1.6.2), more
functions are accessible under the Settings section.
Settings main screen (left) and brightness control screen (right)
Fare Policy and Icon Change
The fare product and tally type icon positioning and types can be added/rearranged through the
Central System if Collier Area Transit wishes to change the bus operation and fare policy in the future
after initial deployment. Please refer to the Central System: Fare Management Module section for
more information on the dynamic configurations regarding fare product and tally type icon
placement.
2.1.4.3 Audible Tone
The farebox can produce various types of audible tones to alert the operator and/or passenger of
errors or events, including:
■ Button is pressed
■ Transaction is completed
■ Deposited fare is not enough
■ Coin/bill rejected
■ An error occurred
■ Successfully log-on/log-off
Tone volume is configurable on OCU.
2.1.5 Construction
Mechanical Configuration
The farebox is constructed of 14 gauge thickness 304 grade stainless steel. The standard farebox
dimensions are W 9.25" x D 9.65" x H 35.50". The weight is approximately 64 lbs for the farebox and
9 lbs for the mounting base, which are carried and installed separately. All exterior surfaces are clean
with all corners rounded. There are no exposed bolt heads, nuts, sharp edges or cracks on the outside
surfaces.
Page 1231 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 18
Inside the farebox body, there are two compartments to house the internal components; the upper
compartment and lower compartment.
Upper Compartment: The upper compartment of the farebox contains core functional modules: coin
acceptor, bill acceptor, controller unit, and power supply unit. It is fully covered by the top cover
which is secured to the upper compartment by a continuous hinge and high security lock. The upper
compartment is not accessible without a key to open the top cover.
Lower compartment: The lower compartment securely holds the cashbox with the internal guides
for the cashbox to tolerate the vibration during operation. It also contains a cashbox access door to
secure the cashbox within the farebox. The cashbox access door is protected by a security plate to
deter insertion and use of prying tools. The door has a full length hinge and is secured by a three
point locking bar, actuated by a high security electronic lock. It is designed such that there are no
gaps for prying open the door with tools, chiseling or other entry. Illegal entry will clearly be
indicated by noticeable damage to the farebox and inability of the farebox to function.
The cashbox access door contains an electronic lock that automatically engages the cashbox access
door when it is fully closed and the cashbox ID has been detected and verified. The farebox does not
operate when the cashbox access door is open or unlocked.
Cashboxes have a permanent ID number engraved on them and is visible through the farebox window.
Cashbox ID number
Page 1232 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 19
Locks and Keys
The farebox has three locks listed below for maintenance and revenue collection purposes:
■ Top Cover Lock
■ Interior Lock
■ Cashbox Lock
The top cover lock protects internal electrical and mechanical components, such as a coin acceptor,
bill acceptor, controller board, and power supply board from unauthorized access.
LECIP uses MIWA “hybrid” lock for the Top Cover. MIWA is a worldwide, trusted manufacturer of
high security locks for industrial applications, including vending machines that stand outside
buildings without any surveillance. The model is VM99R, which features a “hybrid” design of
mechanical and magnetic technologies. Once locked, the key must match with the lock cylinder both
mechanically and magnetically before it can be unlocked. Each key is assigned with a unique ID that
is exclusively provided for LECIP. The combination of using a “hybrid” key and having a user unique
ID, means VM99R prevents duplications of the keys in the highly secure manner. The illustration
below shows how the magnetic key excels in securely compared to that of a typical mechanical key.
The interior lock is located inside the upper compartment of the farebox. This lock serves as an
additional security measure and blocks unauthorized access to cashbox. The locking mechanism for
the cashbox access door and mechanism for bill chute shutter, which automatically closes when the
top cover is opened, are protected by the interior lock. MIWA VM99R with a different key cut is used
for this lock.
The lock on the cashbox is a Takigen mechanical lock. TAKIGEN is also a trusted manufacturer of high
security locks for industrial applications, especially electric switchboard enclosures. The model is C-
288-S-L, which features “bias cut” design. Key dimples are located at corners of the key blade with an
Page 1233 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 20
angle, which makes the duplication of the key totally impractical. LECIP adopted this type of
mechanical key for the cashbox, because of its superior mechanical strength to withstand stress and
abrasion experienced in daily use of the cashbox.
“Bias Cut” Key Blade
Cashbox Access Door
The cashbox access door is unlocked only when
activated RFID access card is tapped on the farebox
RFID tag reader. The RFID access card is activated for a
certain period of time (configurable) after it’s tapped
on a RFID card reader/writer installed near the vault.
This way, the physical location of the cashbox access is
limited to the vicinity of the vault. The farebox records
card ID when the cashbox door is unlocked. Each RFID
access card is allowed to unlock only one
(configurable) farebox at a time, meaning that the RFID
access card can be used to unlock the next farebox only
after an empty cashbox is inserted to the previous
farebox and the cashbox access door is locked.
Modular Design
All the major components, including the coin handing unit, bill handling unit, controller board, and
power board, are modular in construction so that they can be removed without special tools for
inspection and replacement. Major components are fully interchangeable. These modules can also
be installed without any tools or handling wires.
All major sub-assembly modules have a permanent unique serial number in text and barcode with
adhesive labels. The farebox stores the electronic serial number of the farebox itself and numbers
for the coin validator, and bill validator.
Page 1234 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 21
Mounting Base
The farebox comes with the mounting base that is installed on the floor of the bus. The mounting
base and the farebox are firmly secured by four bolts and designed to fully tolerate the vibration
during operation. The mounting base is made of aluminum die casting. The base itself weighs 9 lbs.
The initial mounting base installation may require the installers to go underneath the bus, but once
installed, farebox removal and installation for maintenance would be an easier process which will
not require the installer to go underneath the bus to install or remove the farebox.
The mounting base incorporates a terminal block for power and communication wiring. The
terminal block is accessible using the access door located inside the cashbox compartment, without
removing the farebox, for quick wiring, but not accessible without opening the cashbox safety door
to ensure security.
Page 1235 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 22
Aluminum die-casting mounting base with a wiring terminal block
2.1.6 Farebox Operating Modes
The LECIP farebox has the following operating mode settings:
■ Revenue Registration Mode Settings
• Revenue Service Mode
• Non-Revenue Service Mode
■ Operation Mode Settings
• Operator Mode
• Maintenance Mode
■ Power Mode Settings
• Normal Power Mode
• Sleep Mode
2.1.6.1 Revenue Registration Mode Settings
In order to distinguish between “real live” transaction data and “tested” transaction data at the
Central System, all farebox can be set in Maintenance Mode for either “Revenue Service Mode” or
“Non-Revenue Service Mode”. LECIP recommends for both the training farebox and test bench to be
set at “Test Mode” at all times to make sure the cash transactions made on the equipment do not get
merged with the farebox data in Operation.
Page 1236 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 23
2.1.6.2 Operation Mode Settings
Operator mode is a mode used by bus operators to collect fares, while maintenance mode is used by
maintenance technicians to configure software settings, view event error history. Maintenance mode
is accessible only when a pre-registered RFID card is tapped on the farebox RFID card reader. Users
must register RFID access cards at the Central System beforehand.
2.1.6.3 Power Mode Settings
The farebox is fully functional in Normal Power Mode, and goes into Sleep Mode if there is no
transaction by passengers or key entries by the bus operator for a certain period of time. This
transition time is configurable from the Central System. In Sleep mode, there is nothing displayed on
the LCDs. The farebox will automatically transition back to Normal Power Mode with any key entry
or transaction, e.g. deposit of coins. The farebox can still perform data upload and/or software
download during Sleep Mode, and is useful when receiving updated software fro m Central System
using WiFi overnight.
2.1.7 Cashbox
The LECIP cashbox design is similar to the cashboxes commonly used in the U.S (in size, capacity, and
strength), so that agency staff do not have to learn new operations and methods. The cashbox is
designed to provide safe and easy transportation of monies from the farebox to the vault receiver.
LECIP cashbox has some major advantages over a typical cashbox in the US market, such as the use
of a contactless RFID tag as ID transmission (i.e. no battery used) and its light weight despite it being
completely secure and safe. The RFID tag is also used to store the quantity of bills and coins inside
the cashbox. The quantity information will be passed to the revenue collection vault and erased after
the revenue transfer process is complete.
The LECIP cashbox will hold maximum 2000 coins (or $500) and 800 bills. The farebox automatically
monitors the level of coins and bills deposited in the cashbox by comparing the coin / bill count and
cashbox capacity. The operator can be notified when a cashbox reaches a certain percentage of coin
/ bill capacity (configurable at the Central System) with a “return back to bus garage message”
without having the contents of the cashbox being disclosed and the notification alert being
specifically revealed to anyone else on the bus. Coin/bill acceptance will be automatically disabled
once the count reaches the preset value or percentage of the cashbox capacity. The parameters
mentioned are software configurable at the Central System and available for three different levels of
coin and bill capacity:
■ Full Capacity Alarm
■ Near Full Capacity Alarm
■ Half Full Capacity Alarm
The LECIP farebox is currently programmed to alarm when the cashbox has reached:
■ 1500 coins (near full) / 2000 coins (full)
■ 600 bills (near full) / 800 bills (full)
Construction
The following describes the hardware design of the cashbox.
Page 1237 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 24
The cashbox is made of 20 gauge thickness 304 grade stainless steel. The cashbox has two individual
and separate compartments to collect and retain both coins and bills in their respective
compartments.
The cashbox fits into the farebox and vault receiver only in one correct position and is easily placed
into the ready position to collect and dump revenue. The cashbox insertion and removal procedure
is designed to smoothly guide the cashbox in and out of the farebox and vault receiver.
The internal locking mechanisms of the cashbox are constructed using stainless steel. The cashbox
properly engages the stationary cashbox key mounted in the back wall of the farebox. The cashbox
is designed to make noticeable any physical attempt to gain access and such intrusive effort prevents
the cashbox from being placed in an operational condition.
The cashbox is provided with two handles to facilitate a two-hand grip and allows for a large gloved
hand to grasp it without interfering with the operation of the cashbox access door.
The handles are well-formed and firmly attached to the cashbox, which is used to remove and lift
cashbox from the farebox to the vault receiver. The dimensions of the cashbox are 7.3 x 6.7 x 17.4
inches, and unit without cash in it weighs 15 lbs. The interior capacity is approximately 730 cubic
inches for both coin and bill compartments combined.
Cashbox ID
The cashbox is assigned with an electronic unique ID, which is transmitted to the ID reader in the
farebox when the cashbox access door is closed and locked.
The cashbox ID is critical to ensure the cashbox is properly positioned in the farebox and also to track
where the cashbox is across the system.
While most cashboxes in the industry store the ID on a battery-powered board, for a LECIP cashbox,
the electronic ID is stored in a contactless RFID tag and transmitted to the farebox RFID reader
located inside the farebox. This method would greatly benefit the agencies, with a cashbox that does
not need any batteries. Transit agencies will no longer be required to replace the battery every time
it runs out.
Under normal operations, the farebox recognizes the presence of the cashbox by reading the cashbox
ID. With both the cashbox ID and cashbox access door lock properly recognized, the farebox judges
that the cashbox is properly engaged and ready for service. If a cashbox is not properly inserted into
a farebox, then the farebox will not be able to accept cash and an audible/visual alert will be
Page 1238 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 25
generated to alert the appropriate personnel.
Cashbox readings are automatic and the information relative to the cashbox IDs, date / time of
insertion / removal, are stored in the farebox memory for subsequent data transmission to Central
System.
Security
For the security of the cashbox, LECIP farebox provides the following features:
◼ The cashbox cover is securely locked and does not unlock when it is outside the farebox or
the vault receiver.
◼ The cashbox access door is electrically locked and does not open until a validated RFID access
card is tapped on the farebox RFID card reader and authorized. Users must register RFID
access cards at the Central System beforehand and validate them by a RFID card reader
installed near the vault every time before unlocking the cashbox access door.
◼ The length of time that the cashbox has been removed from the farebox or vaulted by the
receiver is monitored by and reported to the Central System so that you can make sure all the
cashboxes are handled properly.
◼ The farebox monitors the presence of the cashbox inserted. When the cashbox is removed
from the farebox, the farebox stores a record and generates an alarm if the cashbox is not
inserted back within a specified period of time. This timer is configurable from the Central
System.
◼ The farebox will not become functional unless the cashbox ID is correctly and properly
retrieved, and the cashbox access door is confirmed to be fully closed and locked.
◼ LECIP uses a passive contactless RFID tag. By using the radio frequency of the contactless
RFID card technology, the communication with the RFID tag reader in the farebox is very
stable and will not be lost due to the vibration during the revenue service which may happen
with a battery based ID transmitter and causes the farebox to become inoperable.
2.1.8 Data
All farebox data can be classified into the six categories below;
◼ Farebox Log - Transaction (Cash/Tally) Log
◼ Farebox Log - Operation (Error) Log
◼ Status Data
◼ Configuration Data - Farebox Settings
◼ Configuration Data – Fare Table
◼ Configuration Data – Farebox Access Card Setting
2.1.8.1 Farebox Log - Transaction Log
LECIP farebox records transaction logs containing various types of data for later analysis in the
Central System. The transaction log is stored for every single transaction (i.e. every single customer)
that is made on the farebox including tally operation. The following list describes typical transaction
Page 1239 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 26
log LECIP farebox does.
■ Header
■ Date/Time
■ Fare Amount
■ Paid Amount (number of each denomination paid)
■ Fare/Rider/Tally Type
■ Bus ID
■ Farebox ID
■ Operator ID
■ Route ID
■ GPS Location/Bus Stop Code (provided by CAD/AVL)
■ Payment Classification Code (such as paid normally, insufficient payment but transaction
completed, etc.)
■ Transaction Sequence Number
■ Checksum
2.1.8.2 Farebox Log - Operation Log
In addition to the transaction log, the farebox records operation related data. Types of operation
records range widely, including actions by bus operators, status change of farebox, alarms and errors.
Below lists the typical operation log collection that LECIP farebox does.
■ Log-On / Off
■ The Farebox entered Revenue Run / Non-Run Service / Operator / Maintenance / Normal
Power / Sleep Modes
■ The top cover is opened/closed
■ Cash handling
• Coin / Bill is Rejected
• Disabled Coin / Bill is Inserted
• Coin / Bill Jam Occurred / Cleared
• Coin Bypass is Activated / Deactivated
• Coin / Bill acceptor ID Changed
• Coin / Bill acceptor Operation Error
■ Cashbox
• Cashbox ID Error
• Cashbox Inserted/Removed
• Cashbox Access Door Locked/Unlocked
• Cashbox Access Door Time-out
• Cashbox Coin/Bill Half Full Level (configurable at CS) Reached
• Cashbox Coin/Bill Near Full Level (configurable at CS) Reached
• Cashbox Coin/Bill Full Level (configurable at CS) Reached
■ Data Storage
• Data Storage Near Full Level (configurable at CS) Reached
Page 1240 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 27
• Data Storage Full Level Reached
■ Communication errors between individual components and the farebox logic board
■ CPU communication error
■ Low / Over voltage error
2.1.8.3 Status Data
The farebox send status information to the Central System via Web API near real time when there is
a key status change and at a fixed interval (e.g. every 10 minutes) to provide status update while the
bus is in a revenue run, if the farebox can communicate with Central System via cellular network. The
status information includes the following;
◼ Farebox ID
◼ Bus ID
◼ Timestamp
◼ Coin bypass mode activated
◼ Coin jam
◼ Bill jam
◼ Cashbox access door open
◼ Top cover open
2.1.8.4 Configuration Data - Farebox Settings
Farebox Settings are the base parameters necessary for the farebox to provide functions as desired
by the agencies. The farebox settings are configurable on the Central System Web Portal. Please see
Section 4.3.1.1 for details. Such parameters are stored in configuration files and include:
■ Acceptable coin denominations
■ Acceptable bill denominations
■ Transaction time-out timer value (after this value elapsed the transaction goes to
Unclassified Revenue)
■ Display timeout value (after this value elapsed, the display returns to the screen before the
transaction occurred)
■ Log-off timeout value (after this value elapsed, the farebox is automatically logged out and
transitions to sleep mode.)
2.1.8.5 Configuration Data - Fare Table
The fare table differ by the fare policy of the Collier Area Transit and would affect the payment system.
LECIP will initially work with Collier Area Transit to define a fare table with the desired types of fares
and fare amounts. From there, fare tables can be changed and updated by the agencies without the
assistance of LECIP. The fare table is maintained by the Central System and is downloaded to the
farebox. Please see Section 4.3.2 for details.
For a flat fare system, the fare table will contain: fare product type and its fare and transfer fee, etc.
Implementation of the zonal fare system and off peak/peak hours is also possible. The farebox can
change from standard fare to special fares by selecting a fare product on the OCU.
Page 1241 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 28
System supports having one active and pending (future) fare tables at the Central System, at any
given time. These two fare tables are also downloaded and stored in the farebox. Pending fare tables
carry an activation date when they will become effective.
Please refer to Section 2.1.4.2 OCU Functions to see how the fare configurations affect OCU functions.
2.1.8.6 Configuration Data – Farebox Access Card Setting
The farebox access card is not encoded with access privileges. Instead, the farebox has a farebox
access card setting file, which lists all the card and defines privileges assigned to each card. The file
contains the hash value of the file contents to check the data integrity. Any modification to the file
outside the LECIP system will make the file invalid.
2.1.9 Clock/Time Zone
The farebox clock is synchronized with NTP servers regularly to keep the clock accurate all the time.
The farebox internally uses UTC, which guarantees that the farebox functions properly even if
daylight saving time is applied. All the data mentioned in the previous section is also timestamped
with UTC.
The farebox clock is set to US Pacific Time Zone. Daylight saving time is automatically adjusted. If
there is a change in starting and ending dates of daylight saving time in the future, the farebox can be
updated with the new time zone configuration distributed from the Central System.
2.1.10 Application
The farebox provides various applications to control fare transactions, display, sound/voice
announcement, operation monitoring, program/data updates, and others. These applications are
configurable and downloadable from the Central System.
The farebox application is modularly designed and therefore can securely be updated when needed
to do so.
2.1.11 Memory
Farebox provides battery-backed RAM on its controller board and non-volatile flash memory on OCU
board. The controller board manages ongoing transaction data, while OCU stores completed
transaction data. OCU can typically store transaction data for more than 2 weeks.
When the capacity of the farebox data storage is 80% (configurable at Central System) filled, the
operator will be warned by an error message. When the capacity is reached, the farebox will suspend
normal service and indicate that data transfer is required.
2.1.12 Data Protection and Integrity
In the event of loss of power, farebox retains the ongoing payment status in battery-backed RAM,
such as how much has been inserted. The farebox maintains all the completed transaction data and
operation data in the flash memory.
Page 1242 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 29
To ensure the data integrity, LECIP farebox application adds a check sum to every single fare
transaction and operation data.
2.1.13 Self-Diagnostics
The farebox provides the following self-diagnostic testing features. The results are recorded and
reported as the operation data to the Central System. They are also displayed on the OCU to ease the
on-site maintenance.
■ Monitoring of sensors to detect events, alarms, and errors
■ Power supply monitoring to record voltage status
■ Cashbox threshold to notify the near and/or full capacity level of the cashbox
The farebox currently provides about 200 events, alarms, and error codes with associated messages,
such as “Coin in Bypass Mode”, “Top Cover Open”, and “Bill Rejected due to XXX”. The complete list
of errors will be provided to Collier Area Transit as part of the Design Document Submittal.
Indicators
The OCU will visually and audibly indicate events, alarms, or errors that are detected, including major
modules, cashbox, sensors and motors in the farebox. The error code and short message describing
the error will be shown on the OCU display.
Power Supply Monitoring
The farebox monitors power voltage that is applied to its internal power board, and generates an
alarm when the voltage is outside the allowable range. The allowable range is configurable at the
Central System and downloadable to the farebox. It is initially set to 10 to 36 V DC. The generated
alarm will be stored in the maintenance data for later upload to Central System.
Security Door Alarm
The farebox has sensors to detect whether the cashbox access door is opened or closed, and whether
the door is locked or unlocked. The length of the time that the door is open is automatically monitored.
If it exceeds the pre-programmed period of time, the farebox will beep and generate an alarm. The
alarm will be shown on the OCU display with an error code and message, and also be transmitted to
the Central System. The time length to trigger the alarm is configurable at the Central System and
downloadable to the farebox.
Cashbox Security Alarm
The farebox has a contactless RFID tag reader just above where the cashbox would be stored. The
reader automatically communicates with the passive, contactless cashbox RFID tag, which will be
exposed to the reader when the cashbox cover is unlocked and fully opened inside the farebox. The
farebox monitors the presence of the cashbox by recognizing the cashbox RFID.
When the cashbox RFID tag is covered by the top lid of the cashbox being removed, the farebox starts
measuring the time length that the cashbox ID is not recognized. If the time exceeds the pre-
programmed period of time, the farebox will beep and generate an alarm. It will keep beeping until
the cashbox is inserted back and the ID tag is correctly recognized. The alarm will be shown on the
OCU display with an error code and message, and also be transmitted to the Central System.
The time length is configurable at the Central System and downloadable to the farebox.
Page 1243 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 30
2.1.14 Communication
LECIP farebox provides standard interfaces that are widely used across industries. The following
table summarizes the interfaces and potential applications the LECIP farebox supports.
Communication Interface
HW Interface SW Interface Potential Applications
Ethernet (2x) TCP/IP To onboard modem, CAD/AVL
SAE J1708 SAE J1587 To CAD/AVL
RS232C/RS485 To ticket printer
USB For manual data retrieval and manual software update
2.1.15 Technical Specification Summary
The table below describes technical specifications for the farebox.
Page 1244 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 31
Farebox Technical Specification Summary
Denomination 1¢, 5¢, 10¢, 25¢, 50¢, $1
Each denomination can be enabled or disabled.
Validation Speed Up to 10 coins per second
Other function Coin bypass mode
Cashbox capacity 400 in3
$500 or 2000 coins
Denomination $1, $2, $5, $10, $20
Each denomination can be enabled or disabled.
Validation Speed 1.7 seconds per bill
Other function Bill override
Cashbox capacity 330 in3
$800
Cashbox Access Door Authorization RFID Card
Cash Transaction
Tally Date/time, rider type, bus ID, farebox ID, operator ID, route No., GPS location
Error
Availability Data logged by fareboxes are uploaded to the Garage Computer and Central System for reporting
Type
Size
Viewing Angle -80° to 80° (H), -60° to 80° (V)
Resolution
-Audible sound and voice message (in wav format) configurable at the Central System
Type
Size
Resolution
Viewing Angle
Touchpanel
Material
Thickness
Size (including base)
Mass (Prototype)
Ethernet (2x)
SAE J1708
RS-232C/RS485
USB
Voltage
Current
Operating Temp.
Humidity
Inclination
Vibration
Shock
Top Cover Lock High security programmable lock
Interior Lock High security hybrid lock
Cashbox Lock High security mechanical lock
13% - 95% RH (No condensation)
0 ° - 10 ° off vertical unsustained
Tested per IEC 60068-2-64 with 0.67 G (longitudinal) / 1.0 G (transverse) / 1.1 G (vertical) RMS,10 to 200 Hz, 8 h
5 G (instantaneous)
To CAD/AVL for single point logon and geo-tagging
To ticket printer
For manual data retrieval and manual software update
Rated: 12 V DC or 24 V DC
Operating Range: 10 V DC to 36 V DC
2 A at 12 V
32 °F to 122 °F
Others
Cash Handling
Locks
TFT RGB colour display
Date/time, revenue, rider type, fare type, bus ID, farebox ID, operator ID, route No., GPS location
Date/time, error code, bus ID, farebox ID, operator ID, route No., GPS location
To onboard router and e-payment validator
3.5"
QVGA (320 x 240 pixels)
TFT RGB colour display
5.0"
WVGA (800 x 480 pixels)
-85° to 85° (H), -85° to 85° (V)
4-wire analog resistive
Body & Cashbox: 304 stainless steel
Body: 14 GA
Cashbox: 20 GA
Operation Control Unit (Embedded)
Construction
Communication Interface
Electrical Power
Environmental
W 9.33" x D 9.65" x H 35.50"
Body: 63 lbs.
Cashbox: 15 lbs.
Base: 9 lbs.
Bills
Coins
Data Logging
Passenger Display
Speaker
Page 1245 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 32
2.2 TICKET PRINTER
2.2.1 General
The ticket printer will be attached to the farebox. The ticket printer
receives print commands from the farebox and prints/issues tickets
based on the received print command. The types of tickets that the
Ticket Printer can issue are:
■ Day Pass Ticket
■ Transfer Ticket
■ Other ticket types
The ticket printer will issue out thermal paper slips/tickets.
2.2.2 Ticket with QR Code
The ticket printer can issue a ticket with a QR Code, which can be read by the existing Masabi
validator and eliminates the need for visual inspection of paper tickets. The QR Coded- tickets have
a QR Code obtained from the Masabi system, as well as human readable texts. The contents will be
discussed with Collier Area Transit upon contract award.
An example of a ticket with QR Code
2.2.3 Ticket without QR Code
When the farebox failed to obtain a QR Code information, the farebox will print a ticket without QR
Code. Paper tickets can have the following information printed on them:
■ Agency Name
Page 1246 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 33
■ Rider Type (such as Full Fare, Half Fare, if applicable)
■ Day Code
■ Expiration Date/Time
■ Issued Date/Time
■ Bus ID
■ Route ID
2.3 ONBOARD INTEGRATION
2.3.1 Integration with Masabi System
2.3.1.1 Approach
LECIP contacted Masabi and confirmed that Masabi offers an API that the LECIP farebox can interface
with on their back-end system.
LECIP offers a solution where the ticket printer, upon trigger by the bus operator and/or cash
insertion on the farebox, issues a QR Code-printed day pass, transfer, or other types of tickets that
Masabi system supports. The QR code is compatible and readable with the existing Masabi onboard
validator.
Please note that this integration requires the farebox to communicate with the Masabi’s back office
system real time through the existing onboard modem. If the farebox failed to obtain the QR Code
information from the Masabi ‘s back end system due to a network issue, the farebox will issue a ticket
with text information which can be visually validated by the bus operator.
2.3.1.2 Experience
LECIP has experience of integration with a cashless payment system from multiple vendors.
Especially at Rogue Valley Transportation District (RVTD) in Medford, Oregon, the LECIP farebox is
integrated with Cubic (Delerrok) system and capable of printing out a ticket with QR Code.
2.3.2 Integration with Equans System
2.3.2.1 Approach
LECIP farebox will interface with the existing onboard Equans CAD/AVL unit via J1708 or Ethernet
to perform the following actions:
◼ Performing Single-Point-Login and Single-Point-Logout
◼ Retrieving Location/GPS Coordinates
2.3.2.2 Single-Point-Login/Logout
LECIP Farebox will interface with a CAD/AVL system for implementing Single Point Login and Logout
as well. A valid login/logout from the CAD/AVL Terminal will automatically login/logout the Farebox.
Page 1247 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 34
Login data, including Operator ID, block ID, trip ID, and route ID, is retrieved from the CAD/AVL
terminal.
In the case that the CAD/AVL system is down, the Farebox can still operate independently through
manual login and logout that is separated from the CAD/AVL System, so that the bus can still collect
revenue on the bus.
2.3.2.3 Retrieving Location/GPS Data
In addition, LECIP Farebox can interface with the CAD/AVL system to retrieve stop ID/GPS
coordinates data that would be tagged onto each transaction data that the Farebox creates. By tagging
the location data to each Farebox transaction, Collier Area Transit would be able to clearly analyze
bus ridership patterns based on location.
2.3.2.4 Data Available on Central System Reports
Reports available on the Central System show all the fare transactions and maintenance records (e.g.
login/logout, error) with applicable data provided by CAD/AVL. The following table shows an
example of fare transaction data with Operator ID, Route, Stop ID, Trip ID, and GPS coordinates
provided by CAD/AVL.
2.3.2.5 Experience
The LECIP farebox system was integrated with CADAVL systems from various vendors including;
◼ Equans (former Engie)
◼ INIT
◼ Conduent
◼ Trapeze/TripSpark
◼ Passio
Page 1248 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 35
3. GARAGE LAYER
3.1 OVERVIEW
The LECIP Garage System provides state-of-the art equipment that allows for safe data transfer
between the onboard and administrative systems and provides smooth operations for handling cash
and revenue.
Our main objective for the revenue collection equipment is to improve upon the existing system while
minimizing the changes in the operational method that your staff may be used to. This allows your
current staff to still be able operate and maintain the new equipment with minimal training. Having
similar operations to the existing way would also reduce the errors that typically occur when
transitioning to new equipment.
The Garage System is to perform the following functionalities:
■ Unlock the cashbox access door of the Farebox for revenue collection
■ Monitor transfer of money from the cashbox of the farebox to the vault receiver
■ Transfer cashbox/vault related data to the back office system
The Garage System consists of the following hardware equipment:
■ Revenue Collection Vault (with Access Card Activation Device)
■ Test Bench
■ Training Farebox (Option)
3.2 REVENUE COLLECTION VAULT
3.2.1 Overview
The proposed revenue collection vault’s primary function is
to safely transport the money collected in the Farebox into
the cash container. The revenue collection vault is split up
into two main components;
◼ Top half - The vault receiver that accepts and opens
the cashbox and then discharges its contents (coins
and bills) into the vault cabinet located below the
receiver
◼ Bottom half - The vault cabinet that stores the bills
and coins dumped from the vault receiver
The design, manufacture, and operation of the revenue
collection system are designed to minimize the risk of
revenue loss and maximize security. The proposed revenue
collection system employs effective techniques to monitor,
track, and audit the movement of revenue and associated
Page 1249 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 36
electronic information, using cashbox IDs which monitor cashbox presence in the farebox and vault
receiver. With the cashbox RFID tag, the vault receiver can record cashbox insertion events that can
be used for monitoring cashbox opening activity.
3.2.2 Construction
The vault receiver has an access door for cashbox insertion and an operation crank that Collier Area
Transit staff will rotate to empty the cashbox. A contactless RFID tag reader is provided inside the
receiver to read the cashbox ID and to detect the cashbox.
The bottom surface of the cashbox compartment has two money discharge inlets – one for coins and
the other for bills. As the crank is rotated, the cashbox (inserted upside-down) will unlock, and its
cover will open. The coins and bills will then be discharged into the respective inlet to be gathered
and stored in the vault cabinet.
The vault receiver also has three LED lights – green, yellow, red – to indicate the operational progress
of the Vault Receiver. Collier Area Transit staff can only insert a cashbox when the green LED is lit.
3.2.3 Cash Revenue Transfer
It takes on average less than 20 seconds to remove the cashbox from the farebox, insert it to the vault
receiver, and empty the cashbox in the vault receiver.
This process is designed to be similar to that of the current vaulting system:
■ Insert Cashbox upside-down into the vault receiver
■ Close vault receiver access door (automatic locking mechanism activated)
■ Rotate handle on the vault receiver to open the cashbox from the inside to discharge
coins/bills into the vault cabinet below
■ The handle is rotated in the opposite direction manually
■ The cashbox cover is closed, locked and ready to be removed from the receiver
3.2.4 Locks and Keys
The vaulting equipment provides high security hybrid locks and keys (MIWA VM99R). None of the
MIWA VM99R locks and keys provided will be interchangeable for use with any of revenue collection
equipment other than the intended machine (i.e. the MIWA VM99R keys provided for vault receivers
will never work with any of fareboxes). Please see 2.1.5 for details.
The table below lists the physical high security locks that are used for the vaulting equipment.
Vault Receiver
Access Door MIWA VM99R lock
Top Cover 2x MIWA VM99R lock
Revenue Collection Vault
Revenue Discharge Door MIWA VM99R lock
Page 1250 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 37
3.2.5 Technical Specification Summary
3.2.5
The table below describes technical specifications for the Revenue Collection Vault.
SPECIFICATION DESCRIPTION
Model VLT-S002
Dimensions
(excluding handles,
doors, and lamps)
W 32” x H 66.89” x D 36”
Materials Vault Receiver surfaces exposed to the outside
environment: stainless steel
Other surfaces: carbon steel
Power Supply 110V AC 60Hz
Network Connection Ethernet
Mobile Bin Capacity Bills: 12000 cubic inches
Coins: 5900 cubic inches
Mass 849 lbs.
3.2.6 Access Card Activation Device
The access card activation device (ACAD) is installed in the vicinity of the vault and
used to verify and activate access card. The access card is activated only for a
certain period of time (e.g. 30 seconds, configurable). This way the farebox can be
unlocked only within a reasonable radius from the access card activation device.
When a cashbox puller taps activated access card on the card reader of the farebox,
the access card ID is verified again and checked for its privileges and its status
(active or inactive). After the access card is proven valid, the farebox cashbox
access door will open automatically so that the cashbox can be removed and taken
to the vault receiver.
Compared to the traditional infrared “probing”, authorization with the RFID card
has the following advantages;
◼ RFID card used to unlock the cashbox access door is recorded by the farebox and reported to
the Central System. It’s clear who unlocked which fareboxes.
◼ RFID card is verified instantly (less than a second).
◼ RFID card is light-weighted and not physically connected to the vault. This will improve the
safety and productivity of cashbox pullers.
◼ If a RFID card is damaged or lost, the card can be disabled on the Central System. RFID card
is cheaper than the infrared probe, which is often damaged by rough use.
Page 1251 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 38
3.3 REVENUE TRANSFER PROCESS
With the proposed farebox and revenue collection vault with access card activation device, revenue
in the farebox will be transferred to the vault in a secure manner together with the data required for
the cash audit as summarized below.
3.3.1 Revenue Transfer Process Flow
Cash in the farebox will be transferred to the vault as the following;
0. Devices involved in the process
1. Tap an access card on the access card activation device. The access card needs to be pre-
registered on the Central System with an appropriate privilege. The access card will be active
only for 30 seconds (configurable).
Page 1252 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 39
2. Tap the access card on the farebox card reader.
3. The cashbox access door is unlocked, if the card is valid and activated.
4. The cashbox puller can take out the cashbox from the farebox. If the location of the access card
activation device is optimum, this unlocking process will take less than 5 seconds.
Page 1253 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 40
3.3.1.1 Data Recorded
When the cashbox puller taps his/her card on the access card activation device or farebox, an event
log will be created with timestamp and card ID. Such event logs are sent to the back office system and
available on the reports. This will ensure that the access card is properly used.
When the cashbox access door is unlocked, contents of the cashbox is written on the RFID tag in the
cashbox. The RFID tag knows the number of bills and coins by denomination. This data will be read
by the vault when the cashbox is vaulted so that the vault knows how much monies have been
dumped. “Unvaulted” flag is also written on the RFID tag, which will prevent the cashbox from being
inserted without being vaulted.
3.4 TEST BENCH
The LECIP test bench is used for Collier Area Transit maintenance when testing out an individual
farebox component after preventative maintenance or clearing of a jam. The test bench has all the
same module that the farebox has, except broken down into a set of modules that can be worked at
on a table.
The test bench consists of the following modules grouped into one:
■ Operator Control Unit
■ Bill Acceptor
■ Coin Acceptor
■ Farebox Passenger Display
■ Farebox Logic Board
Testing and Software/Configuration Updates
Before making a software/Configuration update to the farebox in the entire fleet via Central System,
LECIP recommends that the user distribute the software/configuration update to the test bench first
and have staff test out the test bench before distributing the new software/Configuration update to
Page 1254 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 41
part of the fleet/entire fleet.
Please note that unlike the farebox onboard the bus, the test bench is not plugged into an onboard
router. In order for the test bench to communicate with the Central System for software updates, it
needs to be plugging into the internal network via Ethernet LAN.
3.5 AUDIT UNIT (PORTABLE VAULT)
LECIP will provide an audit unit, which unlock a cashbox for cash audit. It’s a simple device to open
the cashbox shutter so that the bills and coins can be dumped in small boxes in an authorized manner.
3.6 TRAINING FAREBOX (OPTION)
The LECIP training farebox is a farebox on a mounting stand with castors that can be used indoors
for internal training purposes. Unlike the typical farebox on the bus, the training farebox is set to run
using internal AC/DC converter and plug inside.
Testing and Software/Configuration Updates
Before making a software/Configuration update to the farebox in the entire fleet via Central System,
LECIP recommends that the user distribute the software/configuration update to the training
farebox first and have staff test out the training farebox before distributing the new
software/Configuration update to part of the fleet/entire fleet.
Please note that unlike the farebox onboard the bus, the farebox is not plugged into an onboard router.
In order for the farebox to communicate with the Central System for software updates, it needs to be
plugging into the internal network via Ethernet LAN.
Page 1255 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 42
4. BACK OFFICE SYSTEM LAYER
The LECIP Central System is the “Transit Business Data Centralization, Mastering and Business
Intelligence” layer that consolidates, aggregates, transforms, monitors and controls all elements of
the fareboxes system needs. All the system elements are connected to, will integrate with, and share
data with the Central System.
The Central System is hosted on cloud environments provided by Amazon Web Services (AWS) and
Collier Area Transit users and Collier Area Transit owned devices (i.e. farebox, revenue collection
vault) will access the system through the internet.
4.1 DELIVERY OF THE SYSTEM
The Central System is provided with the following components/services;
◼ Software
Central System application with BI tool
Database and other cloud computing infrastructure/services provided by Amazon
Web Services with proposed locations being Oregon
◼ Access
Access to the Central System Web Portal from a web browser
◼ Software support
Scheduled data backup/archive
Maintenance of database
Recovery of data when required
Information security services
Software update as required (e.g. security vulnerability, end of life)
◼ User Support
Support by phone/email
Support by Jira (issue tracking system)
◼ Monthly Report
Collier Area Transit and LECIP will conclude a Service Level Agreement (SLA) during design reviews
to define details of the service.
4.2 DATA TRANSFER BETWEEN FIELD DEVICES AND CENTRAL SYSTEM
The following diagram describes how data will be transferred between the field devices and the
Central System. The field devices are connected to the Internet through the existing Collier Area
Transit’s onboard or garage network. All the communication between the field devices and the
Central System is encrypted through the TLS protocol.
Page 1256 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 43
Data transfer between the field devices and Central System will be performed automatically when
the devices are connected to the network without any interaction by the bus operator or any of your
staff. The data transfer process is controlled and monitored by Central System.
4.3 CENTRAL SYSTEM WEB PORTAL
The Central System web portal will provide the following features and functions for the fareboxes
system.
■ Reporting and business intelligence for both revenue collection and operational reports
■ Creation and distribution of farebox setting and fare configuration
■ Security on all data within its control (both in access and data at rest)
■ Data integration with various data sources
■ Provide near real-time status update/notification from fareboxes
■ Utilize a data-driven and abstraction configuration approach to make updates,
enhancements, expansions and changes extremely easy
■ Scalable for future addition of devices (i.e. fareboxes, vaults, garages, etc.)
Page 1257 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 44
The LECIP Central System is a means for Collier Area Transit users to freely configure and setup end
device parameters, check and add inventory, create custom reports, retrieve status
alerts/maintenance diagnostics and much more.
The central system contains seven core modules, including a business intelligence layer backed by a
BI tool that allow for full management of reporting of the fare payment system. Each module plays
an important role in use and maintenance of the fare payment systems. The modules are as follows:
■ Device Management module
■ Fare Management module
■ Maintenance module
■ Reports module
■ Administration module
■ System Alert module
Page 1258 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 45
Each module and associated functionality will be described in detail on the following pages.
4.3.1 Device Management Module
The device management module allows users to add, edit and remove devices, as well as configure
the parameters of the fareboxes. The module enables a user to update available configuration settings
in an easy to use interface. The Central System will automatically create the required files for the
fareboxes and make them available for distribution to either your test or fleet buses. Users can
distribute the created files to the fareboxes under the Distributions section of the Administration
Module.
4.3.1.1 Farebox
The Farebox portion of the Device Management Module contains three core items:
■ Farebox Inventory
■ Farebox Settings
Farebox Inventory
The Farebox inventory page allows users to easily view and manage the Farebox inventory in the
system. The system automatically associates Fareboxes once they are powered on and information
reaches the central system.
Page 1259 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 46
In addition to the above, the Farebox Inventory page allows the user to complete the following:
■ View Details of the Farebox
Subcomponent IDs, assigned Bus IDs, assigned garage, etc.
■ Edit Farebox information
■ Add new Fareboxes to the system
■ Delete Fareboxes from the system
■ Assign and Unassign Fareboxes to/from vehicles
Farebox Settings
The Farebox settings page allows users to modify the parameters of the Farebox (not including fare
configuration) that will have a direct effect on the user’s, operator’s and cashbox puller’s experiences
with the Farebox, as well as implementing some fare payment policies. In the Farebox settings page,
the user can adjust the following settings:
■ Activation Date
■ Transaction Display time
■ Automatic transition to Sleep Mode settings
■ Automatic Logoff settings
■ Accepted coin/bill denomination
■ Automatic Transaction Complete (Dump) time
■ Insufficient Cash alert time
■ Cashbox removal alert
■ Cashbox capacity alerts
Threshold for bill/coin compartment half full, near full and full alerts
Page 1260 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 47
■ Cashbox door open alert
4.3.1.2 Vault
The device Management module also contains a subsection titled Vault that contains the detailed
information regarding the connected vaults in the system. From the vault inventory page, a user can
add, edit, remove or view details about the vaults in the system, as well as assign vaults to garages.
4.3.1.3 Access Card Activation Device
The access card activation device is also manageable from the Central System.
4.3.2 Fare Management Module
The fare management module is where Collier Area Transit will build out the cash fare policy. Similar
to the other modules, the fare management module is setup in a way to allow for a step-by-step, easy
to use process for creating your fare table. In setting up the fare table, the system allows the user to
setup an active, pending and test configuration.
■ Allows users to review Active Fare Settings
■ Allows users to add/enable/disable Rider Types to/from the system
■ Allows users to change fare settings based on Rider Type/Route Type
■ Allows users to arrange the OCU software screen that the operator will be using during bus
operation
Page 1261 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 48
4.3.3 Maintenance Module
LECIP understands the importance of transit asset management and the impact on operations and
costs to the agency. The maintenance module was designed to provide Collier Area Transit
maintenance personnel an at-a-glance view of near real time information regarding the status of the
farebox system, in addition to the maintenance of the fleet information. The LECIP Farebox system
collects and reports on various types of errors and alerts for the field devices. LECIP assigns serial
numbers to all major components of the Farebox to allow for easy reporting in the maintenance
module.
The maintenance module is broken into five (5) submenus:
■ Fleet Management
■ Device Status
Farebox
Vault
ACAD
■ Device History
■ Error Codes
■ Component
4.3.3.1 Fleet Management
The fleet management functionality includes the definition of vehicles, their associated garages and
deployment groups (Fleet/Test). Users can also re-assign Fareboxes to different vehicles in the case
where Fareboxes were removed and/or replaced.
Page 1262 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 49
4.3.3.2 Device Status – Farebox
The farebox status report has been created to alert individual users of the status of the fareboxes on
the vehicles.
■ Time of last connection to Central System
■ Cashbox access door status (open/closed)
■ Coin bypass status
■ Last error code and time stamp
4.3.3.3 Device Status – Vault/ACAD
The vault and ACAD device status report is inclusive of the detailed status of the system’s vault and
ACAD. Similar in structure to the on-board device status report, the user will automatically be
directed to the status page with a running list of the status of the vaults in the system.
4.3.3.4 Device History
In the device history page users can browse historical changes in combination of Fareboxes and their
major component for each Farebox.
Page 1263 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 50
4.3.3.5 Error Codes
The error codes page is a read-only help section that allows the user to search on an error to learn
its definition, the cause of the error and potential troubleshooting options. Users can export and print
the content, if desired.
4.3.3.6 Component
The component page shows history of errors for each major farebox component. This page allows
maintenance technicians to track history of each component, even if the components have been
swapped between fareboxes.
4.3.4 Reports Module
Report Module allows the Collier Area Transit staff to view, manage, and create specific reports using
the latest technology with dynamic filters, easy drill downs charts/graphs, and specified ad-hoc
reporting.
LECIP has embedded one of the world’s best business intelligence tools inside the central system: the
Tableau BI tool. Utilization of Tableau allows LECIP and Collier Area Transit significant flexibility in
the way that reports are generated.
The reports module is broken into eight (8) submenus.
■ Ridership – View ridership reports
■ Revenue – View revenue reports
■ Operations – View operations reports
■ Cash Audit – Enter/view cash audit results
■ Email Reports – Create/manage email report settings
■ Custom Reports – Create/manage custom reports
■ Report Templates – Provide report templates for custom reports
■ Day Definition – Define start/end time of a reporting day
4.3.4.1 Canned (Pre-Defined) Reports
Under Ridership/Revenue/Operations submenus, users can view canned reports. In the LECIP
system, the concept of canned reports has changed from a static, PDF or Excel-type report to an
interactive template that allows users to view full (underlying) data, filter settings, roll-up or rollout
data subsets and export the data into different formats. Historically agencies have received a large
number of pre-defined reports. LECIP has assessed the reports previously received by a number of
agencies and have defined the reporting templates below to support those reports.
Access to each type of reports (Ridership/Revenue/Operations) can be controlled in the Users page
in the Administration Module.
Please see below for lists of our canned reports.
Page 1264 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 51
RIDERSHIP REPORTS
Report Title Report Elements Filtering Notes
Ridership by Location GPS, ridership Year, Month, Week,
Day, Route
Map View with
underlying data
view
Ridership by Route Ridership by
route by media
type
Year, Month, Week,
Day, Hour, FBX, Media
Type, Rider Type,
Route
Route can be drilled
down to Stop ID
Ridership by Bus Ridership by bus
by year
Year, Month, Week,
Day, Hour, Route,
Media Type, Rider
Type
Ridership by Operator Ridership by
Operator ID
Year, Month, Week,
Day, Hour, Operator
ID, Route, Media Type
Graph View with
underlying data
view
Ridership by Rider Type Ridership by
route by rider
type
Year, Month, Week,
Day, Hour, Bus, Route,
Media Type, Rider
Type
Ridership by Fixed Route Ridership by
route by year
Year, Month, Week,
Day, Media Type, Rider
Type, Route
Ridership by Fixed Route Report with a drill down to month
Page 1265 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 52
REVENUE REPORTS
Report Title Report Elements Filtering Notes
Revenue by Operator Revenue by
operator ID
Year, Month, Week,
Day, Hour, Route,
Operator ID, Rider
Type, Transaction
Type
Graph view with
underlying data
view
Revenue by Fare Media Revenue by route
by fare media
Year, Month, Week,
Day, Hour, Route, Bus,
Transaction Type,
Rider Type
Revenue by Farebox Revenue by
farebox by year
Year, Month, Week,
Day, Hour, Route, FBX,
Transaction Type
Revenue by Rider Type Revenue by route
by rider type
Year, Month, Week,
Day, Hour, Route,
Transaction Type
Route can be drilled
down to Stop ID
Revenue by Bus Revenue by bus
by route by year
Year, Month, Week,
Day, Hour, Bus, Route,
Transaction Type,
Rider Type
Route can be drilled
down to Stop ID
Revenue by Route Revenue by route
by month
Year, Month, Week,
Day, Hour, Transaction
Type, Rider Type
Route can be drilled
down to Stop ID
Vs. Cash Audit Results Source
(Cashbox/Vault)
by cash type with
count comparison
Year, Month, week,
day, hour, source type,
source ID
Revenue by Fare Media Report
Page 1266 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 53
OPERATIONS REPORTS
Report Title Report Elements Filtering Notes
Coin Bypass Coin bypass by
month
Year, Month, Week, Day,
Hour, Route, Bus
Graph with
Underlying data
view
Bypass by Operator No. of coin
bypasses by
operator
Year, Month, Week, Day,
Hour, Route, Operator ID
Operator Logon Logoff Operator ID, Bus ID
against logon and
logoff time
Year, Month, Week, Day, FBD,
Operator ID, Bus ID, Logon
Type, Logon Method, Logoff
Method
Operator Dump No. of dumps and
dumped $ amount
by operator ID
Year, Month, Week, Day,
Hour, Route, Operator ID
Unlocked Not Vaulted Bus ID, FBX ID,
month
Year, Month, Week, Day
Mobile Bin
Removal/Replacement
Device ID against
date and time,
event type
Year, Month, Week, Day
Cashbox Vaulted No. of vaulting
events by cashbox
ID, bus ID, FBX ID
Year, Month, Week, Day, Bus
ID
Operator Dump Report
Page 1267 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 54
4.3.4.2 Cash Audit
The Cash Audit entry form is an electronic version of the forms that your audit team may fill out
manually now. The data entered on this page is used to compare the manual counted cash against
the Farebox numbers to ensure that the Farebox is operating properly.
A user who would like to create a new cash audit can easily go to the cash audit page, add new, and
select individual or multiple cashboxes and/or vaults for the cash count. The user also has the option
to count coins and bills or only one or the other. The system can be assigned to automatically create
a batch number or allow for manual entry of the batch number.
From that point, the user will be able to enter the cash count. This form can be saved, and a user can
return to complete it, or the form can be directly submitted for completion.
4.3.4.3 Email Reports
There is a submenu under the reporting module that allows users to create, edit and view all email
reports that are generated in the system. A user has the ability to create an email report directly from
the report, but the management of the email report will occur from this page.
Page 1268 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 55
Each email report is sent out with a report in PDF format. LECIP will use an SMTP server on AWS to
send emails.
4.3.4.4 Day Definition
In the day definition module, users can change the day switch time. For instance, if the day switch
time is set to 03:00 AM, all the transaction data between August 1st 03:00:00 AM and August 2nd
02:59:59 AM would be used to create ridership, revenue, and operations report for August 1st. Please
note that the day definition here affects only reports on the Central System.
4.3.5 Administration Module
The administration module is where the system administrator and deployment manager can
maintain the system. The administration module is comprised of the following items:
■ Users – Define Central System user and user roles
■ Access Card – Manage Farebox Access Card and define card type
■ Garages – Define garages which will be allocated to each bus/farebox/vault
■ Distributions – Distribute Farebox configurations and software
■ Software Packages – Upload software package to the system
■ Organizations – Define organizations which will be allocated to each user
■ Security Codes – Generate and distribute new security codes
■ Day Codes – Upload day code files
Page 1269 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 56
4.3.5.1 Users
User role and user management are critically important components of the system. LECIP has
developed a comprehensive user and user role management tool, as described below.
4.3.5.2 Defining User Roles
The central system has been setup such that your IT administrator can create and manage user roles.
User access is managed at a module or submenu level. In some scenarios, this requires tiered
management of roles and the appropriate controls have been put in place such that the administrator
cannot accidentally give access.
LECIP has a pre-defined group of user roles based on previous deployments. However, LECIP will
come to an agreed upon set of user roles with Collier Area Transit prior to design review. LECIP will
implement these roles in time for the factory acceptance test. A list of standard user roles is as follows:
■ System Administrator
■ Finance Manager
■ Finance User
■ Maintenance Manager
■ Maintenance Technician
■ Reporting User (generic access to reporting only)
4.3.5.3 Access Card
In this module, users can manage Farebox Access Card. Users can assign card type, garage, status
(active, lost, stolen etc.), expiration date to each card.
Card Type can be also configured in this module. You can define Card Types, such as bus operator,
revenue service technician, and mechanic, and assign an access privilege to each card type.
Page 1270 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 57
The available access privileges include;
◼ Cashbox Access Door
With ACAD – Normal vault puller
With Password – Power user who can open the cashbox without ACAD, although
authorization with password is still required
No Activation or Password – Power user who can open the cashbox without ACAD or
password. Only recommended for non-revenue devices.
◼ FBX Maintenance
Level 1
Level 2
Level 3
◼ ACAD Maintenance
Level 1
Level 2
◼ Bus Operator
You can assign more than one privilege to a single card type. The access card will not be encoded with
an access privilege. Instead, the access card list with an access privilege assigned to each card is
created by the Central System and sent to fareboxes and ACADs. You can remotely disable stolen/lost
access cards.
4.3.5.4 Distributions
Distribution of files generated inside the central system and uploaded software packages is managed
in the distributions submenu of the Administration Module. When distributing files from other
modules, this is the page that the user will get re-directed to (unknowingly). LECIP have designed the
distribution process such that there are three phases of distribution in the central system: Test,
Pending, and Active. When a user accesses the distribution page, there are two main categories: New
Configurations, Test distributions, and Fleet Distributions.
4.3.5.5 Test Distributions
A test distribution is a distribution that is only eligible to be sent to devices designated with the
attribute of test within the system. This would include items, such as test benches, training Fareboxes
and possibly contingency fleet vehicles (if used for testing.) Assignment of a vehicle as test occurs
within fleet management page under Maintenance Module.
4.3.5.6 Fleet Distributions
To complete a fleet-wide distribution, the user must have promoted all of the appropriate files to
pending or active. When completing a fleet distribution, the user does not have the option to select
the files. All files that will be distributed to the fleet are the files selected as pending and/or active.
All activation dates for individual files are defined when the file was promoted to pending or active.
Page 1271 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 3. EQUIPMENT FUNCTIONALITY AND COVERAGE
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 58
4.3.5.7 Software Packages
Under software packages, you can upload Farebox and Vault software to the Central System. To
distribute the software package, you will need to create a distribution under the distribution
submenu above.
4.3.6 System Alert Module
In the System Alert Module, users can overview common alerts needing immediate attention in the
fare collection system. The common alerts include coin/bill jam status and coin bypass status of the
Fareboxes and communication errors with fareboxes and vaults. The Central System can also send
out an email to notify new alerts to users.
4.3.7 Client
LECIP’s Central System web portal is accessible with a modern web browser such as Google Chrome.
No special client application will be required. Existing desktop computers connected to the internet
at the Collier Area Transit facilities should satisfy the requirements.
Page 1272 of 3773
Page 1273 of 3773
Page 1274 of 3773
Page 1275 of 3773
Page 1276 of 3773
Page 1277 of 3773
Page 1278 of 3773
Page 1279 of 3773
Page 1280 of 3773
Page 1281 of 3773
Page 1282 of 3773
Page 1283 of 3773
Page 1284 of 3773
Page 1285 of 3773
Page 1286 of 3773
Page 1287 of 3773
Page 1288 of 3773
Page 1289 of 3773
Page 1290 of 3773
Page 1291 of 3773
Page 1292 of 3773
Page 1293 of 3773
Page 1294 of 3773
Page 1295 of 3773
Page 1296 of 3773
Page 1297 of 3773
Page 1298 of 3773
Page 1299 of 3773
Page 1300 of 3773
Page 1301 of 3773
Page 1302 of 3773
Page 1303 of 3773
Page 1304 of 3773
Page 1305 of 3773
Page 1306 of 3773
Page 1307 of 3773
COLLIER COUNTY
SOLICITATION NO.: 23-8166 -COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL 5. PRICE FOR EQUIPMENT, INSTALLATION, LICENSE AND WARRANTY
PROPOSAL 5. PRICE FOR EQUIPMENT, INSTALLATION, LICENSE AND
WARRANTY
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 1
Confidential
COLLIER COUNTY
SOLICITATION NO.: 23-8166
REQUEST FOR PROPOSAL (RFP)
FOR
COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
PROPOSAL
5. PRICE FOR EQUIPMENT, INSTALLATION,
LICENSE AND WARRANTY
Submitted by LECIP Inc.
881 IL Route 83 Bensenville, IL 60106
(Tel) 312-626-2525 Fax 312-626-2524
Page 1308 of 3773
Item Unit
Cost
Number
Required Total Cost
Farebox $9,152.86 30 $274,585.80
Ticket Printer $1,432.60 30 $42,978.00
Test Bench $11,763.26 1 $11,763.26
Fixed Vault $67,893.77 1 $67,893.77
Portable Vault $3,553.30 1 $3,553.30
Back Office/Central System - SaaS Year 1 $12,617.58 1 $12,617.58
Back Office/Central System - SaaS Year 2 $12,996.11 1 $12,996.11
Back Office/Central System - SaaS Year 3 $13,385.99 1 $13,385.99
Back Office/Central System - SaaS Year 4 $13,787.57 1 $13,787.57
Back Office/Central System - SaaS Year 5 $14,201.20 1 $14,201.20
Point of Sale Terminal $4,375.00 2 $8,750.00
Wireless Local Area Network (LAN) Access Points and Data
TransferSoftware - 1 - Included in the fixed vault price.
Implementation Cost (Project Management, Design,
Testing, Documentation, Install, Training, Integration, Etc.)$180,139.91 1 $180,139.91
Integration cost payable to Equans $14,375.00 1 $14,375.00
Integration cost payable to Masabi $26,250.00 1 $26,250.00
Total Cost $697,277.49
Farebox Extended Warranty and Technical Support
Year 1 Warranty and Support - after acceptance
Included in
implementation
cost
Year 2 Extended Warranty, License and Technical Support $5,958.22 1 $5,958.22
Year 3 Extended Warranty, License and Technical Support
(Option)$6,256.13 1 $6,256.13
Year 4 Extended Warranty, License and Technical Support
(Option)$6,568.94 1 $6,568.94
Year 5 Extended Warranty, License and Technical Support
(Option)$6,897.39 1 $6,897.39
Year 6 Extended Warranty, License and Technical Support
(Option)$7,242.26 1 $7,242.26
Equipment
Software and Implementation
Total Cost to Implement
License, Warranty, and Support (Year 2-5)
The proposal doesn't include the following features mentioned in the RFP and Collier Area Transit's answers to vendor's questions;
MOBILE BIN
According to the drawing/photos provided by the Agency, the Agency currently uses a stationary vault and doesn't use a mobile bin. LECIP offers so
called "stationary vault" without a mobile bin so that the Agency doesn't need to change the existing method of collecting money.
MAGNETIC CARD READER/DISPENSER
LECIP's understanding is that the Agency doesn't need a magnetic card reader/dispenser, as Masabi's system and the paper ticket with QR Code will
provide the required functions.
SMARTCARD READER/DISPENSER
LECIP's understanding is that Masabi's onboard validator can accept a smartcard and the Agency doesn't need to procure additional smartcard readers.
RECURRING COST PAYABLE TO MASABI
Masabi informed LECIP that the integration between LECIP system and Masabi system will require monthly maintenance/support fee. The anticipated
fee is around $500-1000/month and dependent on the scope. Maintenance/support fee for each point of sale terminal will be around $350/month.
On top of the set up and maintenance, Masabi may also be required to instate a revenue share agreement for the passes/ticket sold through API.
Page 1309 of 3773
Spare Hardware (Recommended List of Spare Parts)
Training Farebox $9,953.77 1 $9,953.77
Farebox (Spare)$9,152.86 1 $9,152.86
TOUCH SCREEN $232.78 1 $232.78
BATTERY $12.68 1 $12.68
PC Board - CONNECTOR $65.66 1 $65.66
PC Board - TOP COVER I/F $331.32 1 $331.32
PC Board - ILLUMINATION $48.09 1 $48.09
RFID R/W ASSY $184.00 1 $184.00
CPU BOARD ASSY $442.92 1 $442.92
KEY ASSY $143.24 1 $143.24
BILL ACCEPTOR $849.16 1 $849.16
COIN ACCEPTOR $491.46 1 $491.46
CONTROLLER $404.04 1 $404.04
POWER-SUPPLY UNIT $306.38 1 $306.38
CONNECTING BASE $231.62 1 $231.62
DOOR LOCK $122.46 1 $122.46
RS232C-LAN Converter $820.00 1 $820.00
PC Board - CONTROLLER $424.26 1 $424.26
PC Board - DRIVER $90.21 1 $90.21
PC Board - DISPLAY $70.84 1 $70.84
PC BOARD - I/F CONVERTER $37.68 1 $37.68
Access Card Activation Device $2,420.00 1 $2,420.00
KEY $50.40 1 $50.40
GREASE $168.28 1 $168.28
DRYSURF $312.42 1 $312.42
THREAD LOCKER $29.90 1 $29.90
Page 1310 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 1
Transit Authority
Fareboxes Project
Service Level Agreement
Submitted by LECIP Inc.
881 IL Route 83 Bensenville, IL 60106
(Tel) 312-626-2525 Fax 312-626-2524
Page 1311 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 2
Revision History
Revision Date Description
1.0 Dec 1, 2023 First Issue
Page 1312 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 3
CONTENTS
A. Scope of Service .......................................................................................................................................... 5
B. Service Description ................................................................................................................................... 6
B.1 Cloud Computing Services for Central System ............................................................................ 6
B.2 Status Monitoring .................................................................................................................................... 6
B.3 Scheduled Maintenance of Databases ............................................................................................. 6
B.4 Scheduled Backup of Databases ......................................................................................................... 6
B.5 Recovery of Data ...................................................................................................................................... 6
B.6 Update/Upgrade of Middleware and Applications .................................................................... 7
B.6.1 Updates necessary to address critical security vulnerabilities ......................... 7
B.6.2 New features/functions ..................................................................................................... 7
B.6.3 Major release of a new version ....................................................................................... 7
B.7 Secure Access to Central System ....................................................................................................... 7
B.8 IP Address Restriction ........................................................................................................................... 8
B.9 Reporting ..................................................................................................................................................... 8
B.9.1 Monthly Report ..................................................................................................................... 8
B.9.2 Incident Report ..................................................................................................................... 8
C. Service Availability .................................................................................................................................... 8
C.1 Measurement of Service Availability ............................................................................................... 8
C.2 Service Availability Calculation .......................................................................................................... 8
C.3 Availability Goal ........................................................................................................................................ 9
D. Maintenance Types ................................................................................................................................... 9
D.1 Standard Maintenance ........................................................................................................................... 9
D.2 Major Maintenance .................................................................................................................................. 9
D.3 Emergency Maintenance/Update ..................................................................................................... 9
E. Customer Support................................................................................................................................... 10
E.1 Customer Support Accessibility ....................................................................................................... 10
E.2 Response Time ........................................................................................................................................ 10
E.3 Service Review Meeting ...................................................................................................................... 10
F. Support Organization ............................................................................................................................ 11
G. Handling of Data ...................................................................................................................................... 11
G.1 Data Ownership ...................................................................................................................................... 11
G.2 Data Accessibility ................................................................................................................................... 11
H. Force Majeure ........................................................................................................................................... 11
Page 1313 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 4
I. Termination of Service ......................................................................................................................... 12
J. Disclaimer .................................................................................................................................................. 12
Page 1314 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 5
This Service Level Agreement is entered into by and between LECIP Inc. (“LECIP”) and the Transit
Authority for Software as a Service (SaaS) stipulated in the Services Agreement. The purpose of this
agreement is:
1. To clarify LECIP’s scope of work
2. To set clear service level standard for SaaS to host Central System for LECIP Fareboxes System at
Transit Authority.
In the event that there is a conflict between the terms of Service Level Agreement and the terms of
Services Agreement, the terms of Services Agreement shall prevail.
A. SCOPE OF SERVICE
The scope of this agreement includes the following services as parts of SaaS:
◼ Cloud computing services for Central System (Section B. 1)
◼ Status monitoring (Section B. 2)
◼ Scheduled maintenance of databases (Section B. 3)
◼ Scheduled backup of databases (Section B. 4)
◼ Recovery of data, on an as needed basis (Section B. 5)
◼ Update/upgrade of middleware and applications (Section B. 6)
◼ Secure access to Central System (Section B. 7)
◼ IP address restriction (Section B. 8)
◼ Reporting (Section B. 9)
The following are NOT included within the scope of this agreement;
◼ Operations on the Central System user interface (e.g. user registration, user role control,
distribution of fare configurations).
◼ Retention of data longer than the pre-agreed duration (7 years). LECIP will give Transit
Authority a 30 days’ notice that the data retention will end.
◼ Transit Authority intranet settings to allow communication between the devices at Transit
Authority facilities and the cloud services.
Page 1315 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 6
B. SERVICE DESCRIPTION
B.1 CLOUD COMPUTING SERVICES FOR CENTRAL SYSTEM
LECIP will use cloud computing services provided by AWS, including AWS Lambda, Amazon
DynamoDB, Amazon API Gateway, Amazon Relational Database Service, and Amazon Simple Storage
Service, to host Central System for the Fareboxes System.
The system architecture and specifications will be decided by LECIP. The server location will be
chosen within the USA to minimize latency and maximize usability by Transit Authority. The
expected server location is Oregon.
B.2 STATUS MONITORING
(AWS Status Monitoring) Using health dashboard provided by AWS, status of cloud computing
services will be monitored by LECIP.
(Application Monitoring) All the major applications, middleware, and processes will be continuously
monitored to ensure health of the SaaS. Any signs of abnormal conditions will be investigated to
prevent an accident or performance issue.
(Security Monitoring) Using AWS GuardDuty and AWS WAF, LECIP will monitor for malicious activity
and unauthorized behavior to protect the SaaS and data kept within the service.
B.3 SCHEDULED MAINTENANCE OF DATABASES
Storage Auto Scaling is enabled for databases, meaning that disk space assigned to each database will
be automatically increased by AWS, when free available space is less than 10 percent of the allocated
storage.
LECIP will upgrade the database instance type if more CPU and/or memory resources need to be
assigned based on the results of database monitoring.
Databases will be monitored by Amazon CloudWatch. Amazon CloudWatch obtains health metrics,
including CPU utilization, free-able memory, read latency, and write latency, from databases every
minute. Amazon CloudWatch will be configured to send an alarm to LECIP staff, based on the value
of the metric relative to a pre-defined threshold.
B.4 SCHEDULED BACKUP OF DATABASES
A backup of the databases will be made around 3 am every day and will be kept for three months.
B.5 RECOVERY OF DATA
Should data loss occur, LECIP will use reasonable efforts to recover the lost data, using the available
backup data.
Page 1316 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 7
B.6 UPDATE/UPGRADE OF MIDDLEWARE AND APPLICATIONS
LECIP will check monthly if a new version of third-party middleware and applications is available.
LECIP will update/upgrade third party middleware and applications with due consideration of
dependency between components in accordance with the following policy.
B.6.1 Updates necessary to address critical security vulnerabilities
LECIP will evaluate the published release notes for the applicability of the security risks. The security
vulnerability identified to be critical by the supplier will be considered to be critical by LECIP, as long
as the components/functions in question are used for SaaS. Updates for major Central System
components will be applied as follows;
◼ Amazon RDS PostgreSQL
Auto Minor Version Upgrade will be disabled. The minor version upgrades addressing critical
security vulnerability will be manually applied by LECIP. The term “minor version upgrade”
here means that the released version is backward compatible.
◼ Python
Versions released by Python Software Foundation to address critical security vulnerability
will be applied, if the components/functions in question are used for SaaS.
◼ Tableau
Versions released by Tableau Software to address critical security vulnerability will be
applied.
If necessary, LECIP will perform verification for a new update to ensure the system integrity and
stability.
B.6.2 New features/functions
LECIP does not apply a new version of software only for the purpose to include new
features/functions.
B.6.3 Major release of a new version
In many cases of stable well-known software components, even if a new major version branch is
released, previous stable major branch(es) are supported for the maintenance updates. LECIP will
continue to support the original major version branch as long as the security update maintenances
are supported by the third-party component sources.
B.7 SECURE ACCESS TO CENTRAL SYSTEM
LECIP will provide secure https access to the cloud services.
Page 1317 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 8
B.8 IP ADDRESS RESTRICTION
LECIP will restrict the access to the cloud computing services by IP address and port so that only the
authorized accesses from Transit Authority and LECIP facilities are allowed, if requested by Transit
Authority.
B.9 REPORTING
B.9.1 Monthly Report
LECIP will submit monthly reports to Transit Authority. The reports will include monthly
quantitative metrics such as availability (%) of the service, percentage (%) of time when resource
usage has exceeded certain thresholds, as well as qualitative information such as results of data
backup, error logs and unauthorized access attempt to the services from IP addresses other than
Transit Authority and LECIP.
B.9.2 Incident Report
LECIP will submit an incident report within 5 business days after the incident, when incidents
affecting Transit Authority’s user experiences such as inaccessibility to the service or unavailability
of data are reported. The report will have description of the issue, cause of the issue, actions done to
recover from the issue, tentative actions/workarounds if applicable, and permanent corrective
actions.
C. SERVICE AVAILABILITY
C.1 MEASUREMENT OF SERVICE AVAILABILITY
LECIP will monitor the following metrics to calculate the service availability;
◼ Dummy login requests are sent to the Central System web portal every 10 minutes. Successful
login will be considered as a positive result. The positive result shows that the Central System
web portal is accessible from users and the Central System application and database are
running.
◼ Dummy requests are sent to Web API every 10 minutes. Successful response will be
considered as a positive result. The positive result shows that the Central System is accessible
from field deices and the Central System application is running.
The SaaS will be considered available during time periods between points when all the above metrics
show positive results.
C.2 SERVICE AVAILABILITY CALCULATION
Service availability is calculated by the following formula;
Page 1318 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 9
(Service Availability)%
=(𝐴𝑣𝑎𝑖𝑙𝑎𝑎𝑙𝑎 𝑃𝑎𝑟𝑖𝑙𝑎)
(𝑅𝑎𝑙𝑙𝑟𝑡𝑖𝑙𝑔 𝑃𝑎𝑟𝑖𝑙𝑎)−(𝐸𝑥𝑎𝑙𝑙𝑡𝑎𝑎 𝑃𝑎𝑟𝑖𝑙𝑎)−(𝑀𝑎𝑖𝑙𝑡𝑎𝑙𝑎𝑙𝑎𝑎 𝑃𝑎𝑟𝑖𝑙𝑎)× 100
Where
◼ Contract period is a one-year period, from a specified commencement date to a specified
completion date, as specified in the Services Agreement.
◼ Exempted period is a period of service unavailability caused by issues beyond LECIP’s control,
including but not limited to AWS unavailability and network outage.
◼ Maintenance period is a period of service unavailability required to conduct
scheduled/unscheduled maintenance.
◼ Available period is a period of service availability measured by the definition in clause C. 1.
C.3 AVAILABILITY GOAL
LECIP provides 99% availability of the SaaS. This availability goal is at its best effort and it shall not
be guaranteed that such availability can be achieved.
D. MAINTENANCE TYPES
There are three types of maintenance activities depending on the nature of the required changes.
SaaS will be partially/fully unavailable during the maintenance. The field devices, including the
Farebox and Revenue Collection Vault, are designed to work offline without connection to the Central
System at least for 7 days. Transit Authority can continue fare collection even if the Central System
is temporarily unavailable due to maintenance.
D.1 STANDARD MAINTENANCE
LECIP will conduct scheduled maintenance and non-emergency update/upgrade, during which the
SaaS needs to stop partially or fully, between Sunday 03:00 pm and Monday 03:00 am (EST/EDT).
Expected service downtime will be notified to Transit Authority at least 48 hours in advance.
D.2 MAJOR MAINTENANCE
If LECIP needs to conduct major maintenance which cannot be completed during the standard
maintenance time window, LECIP will notify Transit Authority of such necessity and agree on the
maintenance downtime at least 7 days in advance.
D.3 EMERGENCY MAINTENANCE/UPDATE
If the necessity of emergency maintenance/update arises, LECIP will notify Transit Authority of the
emergency and immediately stop the SaaS to conduct necessary maintenance or update. Unsaved
data on the user interface (e.g. manual count data for cash audit) could be lost in this case.
Page 1319 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 10
E. CUSTOMER SUPPORT
E.1 CUSTOMER SUPPORT ACCESSIBILITY
LECIP customer support will be accessible through JIRA Service Desk, email, or phone. The main
contact will be;
Service Manager
Tel: +1-312-626-2525
email:
Customer support will be accessible during the following business hours;
Customer Support Business Day and Hour
Monday to Friday 09:00 to 17:00 (EST/EDT)
Saturday and Sunday N/A
Holidays N/A
The field devices, including the Farebox and Revenue Collection Vault, are designed to work offline
without connection to the Central System at least for 7 days. Transit Authority can continue fare
collection even if the Central System becomes unavailable on weekends/holidays.
E.2 RESPONSE TIME
LECIP will respond to customer support request received during the Customer Support Business
Hour within 1 business day. If the reported issue severely affects the availability of the LECIP
Fareboxes system, LECIP will use reasonable efforts to resolve the issue by the end of the next
Customer Support Business Day.
E.3 SERVICE REVIEW MEETING
Regular service review meetings will be held between Transit Authority and LECIP to go over any
open JIRA tickets and any other related reports. These will be held monthly, as long as there are open
items. If there are no open items the meeting will be canceled by LECIP.
Page 1320 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 11
F. SUPPORT ORGANIZATION
The SaaS is provided by the support organization shown in the organization chart. When deemed
necessary, Transit Authority may escalate issues concerning the SaaS to Service Manager, CEO of
LECIP Inc. as well as QA General Manager of LECIP
Holdings Corporation in Japan.
G. HANDLING OF DATA
G.1 DATA OWNERSHIP
LECIP recognizes that all data collected within the Fareboxes System including but not limited to
transaction logs, data derived from the transactions logs, and cash audit results are owned by Transit
Authority. LECIP uses such data only to provide services to Transit Authority and to monitor and to
improve fare collection products.
G.2 DATA ACCESSIBILITY
LECIP will provide Transit Authority with read only access to the relational database so that Transit
Authority can make use of data with a third-party BI tool application. LECIP shall not be responsible
for issues caused by heavy queries to the database.
E.3 DATA RECOVERY
Reasonable effort (e.g. recovery by using backup data) will be made to recover the data loss. LECIP
shall not guarantee that the lost data will be fully recovered and shall not recover lost data beyond
LECIP’s reasonable effort. In the event data loss is caused by Transit Authority’s data operation,
LECIP shall not be liable for the data recovery.
H. FORCE MAJEURE
LECIP shall not be liable for any data loss or service unavailability under this Agreement arising out
of causes beyond its reasonable control including, but not limited to, acts of God or public enemies,
acts of other parties, acts of civil or military authority, labour disputes, fires, riots, war, embargoes,
epidemics, floods, unusually severe weather or shortage or absence of power or fuel or other
circumstances of the same nature and shall not recover such lost data.
CEO
Servie Manager
Engineer
QA General Manager
LECIP Japan
Page 1321 of 3773
LECIP Fareboxes Project
Agreement Number:1234567 Fareboxes Project
Service Level Agreement
21-91200-
P04
)
ｆｄ
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 12
I. TERMINATION OF SERVICE
When parties decided to terminate the SaaS, LECIP will provide necessary support to export data at
extra cost, as required.
J. DISCLAIMER
Since the cloud server platforms will be provided by Amazon Web Services, LECIP SHALL NOT BE
LIABLE FOR ANY KIND OF SERVICE UNAVAILABILITY OR DATA LOSS CAUSED BY AMAZON WEB
SERVICES. LECIP will contact Amazon.com to resolve the issue caused by Amazon Web Services, but
LECIP shall not guarantee the time to resolve the issue. LECIP will use reasonable efforts to recover
the service affected by such incidents.
Page 1322 of 3773
Transit Authority
Agreement Number: 21033-OS Fareboxes Project
Service Level Agreement
This document contains proprietary information originated or owned by LECIP. Neither this document nor the information disclosed herein shall be reproduced or
transferred to other documents or used or disclosed to others for manufacturing or any other purpose except as specifically a uthorized in writing by LECIP.
Page 1
Confidential
For Transit Authority
___________________________________________________
Signature
___________________________________________________
Print Name/Title
___________________________________________________
Date
For LECIP
___________________________________________________
Signature
___________________________________________________
Print Name/Title
___________________________________________________
Date
Page 1323 of 3773
Page 1324 of 3773
Page 1325 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Non-Technical Requirements Yes No Vendor's comments Collier County Comments Team responsible
CMA 5401 compliance
R X Vendors proposing to supply software
solutions to Collier County must comply
with County-Practices-and-Procedures-
(CMA) 5401 INFORMATION SYSTEMS
PROCUREMENT AND LIFECYCLE
MANAGEMENT
IT Managers
Vendors proposing to supply any software solutions to Collier County must fill out
this document, sign it, and return it to the Collier County IT Division to review.
R X IT Managers
Technical Requirements for Applications Hosted on the BCC Network R/O
Weighted for
optional
business
requirement for
depts. fielding
RFPS
Yes No Vendor's comments Collier County Comments Team responsible
Web-based candidate software shall utilize Microsoft's current Internet browser
(Chromium Edge), Chrome, and iOS Safari. Others can be supported , but
support would be on a case by case would basis and billable.R1 R X
LECIP's Central System suppots
Microsoft Edge and Google Chrome. It
deosn't support mobile devices
including iPhone.
The department purchasing the software
benefits from increased security,
efficiency, and lower support costs over
the life of the software
Service Desk
Please list any other browsers in column G, they may or may not be considered
as acceptable. Any non-Microsoft browser considered as acceptable may incur
dedicated support costs.R2 O Applications
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
Page 1326 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
The vendor must submit any applicable license agreements for any proposed
elements including a description of the licensing model, and list prices for all
license types and whether or not custom licensing arrangements are available.R3 R X LECIP uses OSS for embedded
software and back end software.
Allows the department that is purchasing
the software to determine the limitations of
the licensing and the short and long-term
costs
Applications
The vendor must submit any applicable maintenance agreements for any
proposed elements including a description of the maintenance plan, software
upgrade policies and exclusions, and list prices for all maintenance agreement
types and whether or not custom maintenance agreements are available.R4 R X
Service Level Agreement for Central
System is attached to this proposal.
Custom maintenance agreements are
available.
For the department purchasing the
software this information will help them
plan when will and how often these events
take place and to manage their costs
more efficiently.
Applications
SAP is Collier's financial application and as such:
• Applications cannot directly interface with SAP
• Applications that have a point of sales component must be able to produce a
batch file daily containing all financial transactions for that day
• The batch file will use the format supplied by the Collier County Clerk of Courts
R5 R
LECIP would like to discuss the
details of the requirements upon
contract awards. LECIP system is
capable of exporting sales data in
CSV/MS Excel formats.
Applications
All desktop software applications must utilize Microsoft Operating System,
current Collier Production Version release with current patches and service
packs, Windows 10 (64-bit).R6 R LECIP system doesn't require special
desktop software applications.Operations
Applications may not use Exchange Event Sinks or Exchange Public Folders.R7 R X LECIP system doesn't use Misrosoft
Exchange Operations
If US-CERT posts vulnerabilities associated with an application then the
application must be mitigated within a 30 day timeframe by the software vendor.R8 R X Operations
Page 1327 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
Software must comply with all Federal, State and Local regulation. Especially the
Florida Information Protection Act (FIPA Fla. Stat. 501.171). Vendors and
consultants must be able to show that their applications either a) do not store the
type of sensitive data mentioned in FIPA in their application's database or b) be
prepared to demonstrate how they secure the type of sensitive data mentioned in
FIPA in their application's database.
R9 R X Link to Sensitive Data questions Administrative
HIPAA compliance is required for any applications that contain an individuals’
electronic personal information if it is created, received, used, or maintained in
the software.
R10 R X
All applications that include point of sales systems or accept any type of
payments using credit cards must be PCI (Payment Card Industry Data Security
Standard) compliant and recertify every year. All credit card processing must be
done outside of the BCC network unless the credit card device encrypts all
information directly on the device.
R11 R LECIP system doesn't accept credit
cards.
Vendors are required to meet banking
industries PCI compliance requirements
All vendors requiring access to Collier County facilities and the computer
network must comply with current published County ordinances and policies.
Those ordinances and policies are same requirements that all county employees
must agree to, which include finger printing ,a background check, and signing
any user agreements required access the BCC computer network.
R12 R X
Any software which stores personally identifying information, including but not
limited to passwords, SSN, driver’s license numbers, etc.... or any financial
information, such as credit card numbers, bank routing information, etc... must
fully protect the information and disclose the methods of protection used, access
protection methods, and life cycle handling of this data. Industry standard
encryption methods utilizing at least 256 bit encryption techniques are required.
R13 R LECIP system doesn't store
personally identifying information.All IT teams
Software vendors will acknowledge in writing prior to selection, that Collier
County Government will own any and all data and the databases.R14 R X Applications
Page 1328 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
The candidate software application proposal must include a complete hardware
topology diagram and recommended hardware configurations.
Vendor Deliverables:
- Topology Diagram
- Recommended hardware requirements (workstation and server)
- Network bandwidth requirements
C1 R
LECIP provides embedded software
for the field devices and back office
system as SaaS. No special software
application will be required on
County's computers.
Technical specifications, hardware
requirements, and visual representations
of the candidate’s recommended software
solution will enable the selection
committee to understand the complexity
of the application and costs to support it.
Applications
Web-based software must utilize IIS 10 or newer with current patches and
service packs.C2 R X LECIP Central System uses AWS S3
to host the website.
The department purchasing the software
benefits from increased security,
efficiency, and lower support costs over
the life of the software
Operations
Applications that utilize a web browser for an internal or external access will
utilize TLS1.2 instead of SSL C3 R X LECIP system uses TLS 1.2.Operations
Software applications should support and run on current shipping release of
virtual servers, including:
- VMware ESX ( most current version )C4 R
LECIP provides embedded software
for the field devices and back office
system as SaaS. No special software
application will be required on
County's computers.
Operations
All software upgrades or changes required by the selected vendor must be fully
tested before being moved into the production environment. Therefore vendors
must include in their proposal the costs for licensing, professional services, and
annual maintenance to set up and maintain test and development environments.
C5 R X
The SaaS fee in this proposal includes
costs for licensing, professional
services and annual maintenance.
Applications
System must support the current the use of NetBackup in the Collier Production
environment with NetBackup most current version. C6 R X Operations
Page 1329 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
All server software applications must utilize Microsoft Operating System, current
Collier Production Version release with current patches and service packs,
current version is Server 2019 C7 R
LECIP Central System uses serverless
architecture and there will be no
server software application.
Standardizing the desktop operating
system to a few specific versions
decreases the management overhead for
support and lowers the cost to the agency.Operations
Solutions requiring a back-end database must utilize Microsoft SQL Server
Standard or Enterprise edition. The solution must use and support Microsoft SQL
Server 2016 (64-bit) SP2 or newer. Compatibility mode must match the version
of Microsoft SQL Server.
C8 R X LECIP Central System uses
PostgreSQL database.Development
For SQL Server based solutions, the use of the default SQL SA account is
prohibited. The use of the SA role for daily functions is also prohibited. The
solution will adhere to the least privilege principle.C9 R LECIP Central System doesn't use
Microsoft SQL Server.Development
Is the proposed application compatible with VSS?
Service Display Name: Volume Shadow Copy
Service Name: VSS
Path: C:\WINDOWS\system32\vssvc.exe
C10 R X
LECIP Central System uses serverless
architecture and there will be
Windows Server software.
Hard coding account access shall not be permitted.
C11 R X
Provides enhanced application security by
removing the issue of being unable to
change user account names and
passwords if that information is
compromised.
Operations/Development
If a geographic information systems (GIS) is included in the solution, the solution
must leverage ESRI ARGIS Online. Loosely couple architecture using the REST
endpoints is the preferred architecture solution. The County strives to keep its
ESRI GIS current with the latest released version.C12 R A geographic information systems
(GIS) is not included
If the solution must use On-Premise
ArcGIS Enterprise this should be talked
over with IT Managers and discussed to
make sure that this can be kept up to date
and that the Dedicated GIS servers can
accommodate.
Development
Page 1330 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
All optional items listed below may incur additional costs for support
and maintenance for the application that is proposed. All additional
costs, for implementation and ongoing maintenance would be borne
by the department purchasing the application.
R/O
Weighted for
optional
business
requirement for
depts. fielding
RFPS
Yes No Vendor's comments Collier County Comments
Incident Support providing 24x7/365 coverage shall be offered. Incident
response service levels shall be specified.
O1 O - 10 X Please see the attached service level
agreement.
This service is appropriate when a
department’s critical business is run
outside of the normal 8 to 5 Monday to
Friday work week ( example: evenings,
weekends, holidays) and the software
systems are proprietary or complex
enough that the BCC IT department
cannot always resolve the issue without
assistance from the vendor. There is
however, a premium associated with the
cost of this type of vendor support, which
the department purchasing the software
would bare.
Applications
Client software applications should support and the vendor should provide
package definition files with silent install without user interaction, using Microsoft
SCCM current version. Supported installation packages include:
MSI, Microsoft Windows installer MSI compatible O2 O - 10
LECIP provides embedded software
for the field devices and back office
system as SaaS. No special software
application will be required on
County's computers.
Results in lower support and maintenance
costs for the department that owns the
software.Applications
Page 1331 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
All software application vendors are required to notify Collier County when new
releases become available and when current releases and related systems are
no longer supported.O3 O - 10
LECIP provides embedded software
for the field devices and back office
system as SaaS. No special software
application will be required on
County's computers.
Allows the department that owns the
software to get the latest functionality that
the vendor is offering along with patches
that keep software security and
compatibility current.
Applications
Preferred solutions should take advantage of the County's Active Directory
environment and utilize Windows Authentication at the application, database and
server tier, run fully in the user context, and not require elevated permissions or
administrative permissions. Elevated permissions require adherence to all
relevant policies, such as the Elevated Privileges and Elevated Database
Permissions policies.
O4 O - 10
LECIP provides embedded software
for the field devices and back office
system as SaaS. No special software
application will be required on
County's computers.
Provides enhanced security by eliminating
the possibility of a disgruntled former
employee or vendor getting access to a
department's application since their
network account with be disabled.
All IT teams
Does the application require anti-virus exclusions Anti-Virus? If so please provide
paths & or processes
O5
LECIP provides embedded software
for the field devices and back office
system as SaaS. No special software
application will be required on
County's computers.
Credit Card Payment Processing
All credit card processing devices are prohibited from being connected to
any BCC computer or directly to the BCC network unless the device is
P2PE compliant and encrypts the data directly on the device.
R-15 R LECIP system doesn't accept credit
cards.
Credit Card payment devices must use a
separate phone or cable connection to the
Internet or is P2PE compliant
Applications
Security Software required by the Information Technology Division that
ALL Proposer's software must compatible with.Vendor's comments Collier County Comments
NNT R-16 X Security
Change Auditor R-17 X Security
Cisco AMP (Antivirus)R-18 X Security
If for some reason the proposing
vendor's software is not compliant with
CMA5401, then it is possibly to
mitigate the issues . However
mitigation would be a dedicated
service and the purchasing division
would be responsible to bare all of the
costs of the mitigation.Page 1332 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
Windows Firewall R-19 X Security
Flexera R-20 X Security
SCCM R-21 X Security
System Center Endpoint Security R-22 X Security
Cisco AnyConnect R-23 X Security
Vendor Required Software for their applications to run Yes No Vendor's comments Collier County Comments
Does the application require Flash?X Applications
Does the application require Java?X Applications
Does the application require Silverlight?X Applications
Does the application require any type of PDF software?X
If the County needs to view reports in
PDF format.Applications
Cloud or SAS Specific Applications and Services Yes No Vendor's comments Collier County Comments
ADFS for single sign on
O
X
LECIP Central System supports single
sign on. The proposal doesn't include
cost required for this integration.
Does the application require the installation of software, including browser plug-
ins on a end user's computer, list all the software and version number required in
cell H70.R
X
No special application software is
required to access Central System.
Software listed in this section will
require additional dedicated costs for
support.
If for some reason the proposing
vendor's software is not compliant with
CMA5401, then it is possibly to
mitigate the issues . However
mitigation would be a dedicated
service and the purchasing division
would be responsible to bare all of the
costs of the mitigation.
Page 1333 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
Provide a detailed architectural diagram of the application that includes links to
all servers, services, and IP addresses.
X
Please see the proposal. LECIP
Central System uses serverless
architecture and there will be no
server software application.
IP addresses will be provided after the
contract award.
If a vendor cannot provide a detailed
architectural diagram of their application
that includes links to all servers, services,
and IP addresses this will not necessarily
preclude a vendor from selling their
application to a Collier County division.
However, the Collier County Information
Technology Division will not be able to
troubleshoot any problems beyond the
edge of the BCC network and it will be the
vendors responsibility to resolve any
issues that occur.
Collier County uses a web filtering service. Does the proposing vendor's solution
work with a web filtering service. If it does, please provide all IP Addresses and
the services being delivered in cell H70.
X
IP addresses will be provided after the
contract award.
Variances are possible if a vendor does
not want or cannot supply the requested
information. However, if problems with the
application occur and the BCC network is
functioning as designed, it is the
responsibility of the vendor to
troubleshoot and resolve the issues.
If your application requires whitelisting, please provide a list of URL's to be
bypassed in the web filtering service.
X
URLs to be bypassed will be provided
after the contract award.
List the web browsers and versions that your application is compatible with in
cell H74
X
Microsoft Edge latest version
Google Chrome latest version
Mozilla Firefox latest version
Page 1334 of 3773
Collier County Information Technology Department
Version: 20
10/29/2020
Revised by: Paul Ducca
Vendor signature: Yasunori Goto
Date: Dec 4, 2023
Key for C18:C76 C =
If internal required, If hosted N/A
R= Required
O= Optional, but may include additional costs to support
Key for C18: C76 Place
an X in the YES or NO column, add any comments required in column H
Vendor name: LCIP Inc.
Application name: COLLIER COUNTY TRANSIT ELECTRONIC FAREBOX
Technical Architectural, Compatibility and Supportability Requirements Document (TACS)
Requesting Div./Dept.:
Describe your data backup and recovery process. Will a copy of the database be
available if requested and what format will it be in?
X
Please see the attached service level
agreement.
LECIP would like to discusse the data
backup format after the contract
award.
Is any type of sensitive data stored in the application database and if so what
steps are taken to protect that data?X
No sensitive data will be stared in the
database.Link to Sensitive Data questions
What colocation data center is the proposing vendor's application housed at ?LECIP uses AWS. The proposed
region is Oregon.
Minimum bandwidth required?
LECIP doesn't define a bandwidth
requirement. Normal broadband
bandwidth (e.g. 25 Mbit/s) should
suffice.
Web applications must support HTTPS, TLS 1.1 or higher LECIP Central System uses TLS 1.2.
Page 1335 of 3773
Page 1336 of 3773
Page 1337 of 3773
Page 1338 of 3773
Page 1339 of 3773
Page 1340 of 3773
Page 1341 of 3773
Page 1342 of 3773
Page 1343 of 3773
Page 1344 of 3773
Page 1345 of 3773
Page 1346 of 3773
Page 1347 of 3773
Page 1348 of 3773
Page 1349 of 3773
Page 1350 of 3773
Page 1351 of 3773
Page 1352 of 3773
Page 1353 of 3773
Page 1354 of 3773
Page 1355 of 3773
Page 1356 of 3773
Page 1357 of 3773
Page 1358 of 3773
Page 1359 of 3773
Page 1360 of 3773
Page 1361 of 3773
Page 1362 of 3773
Page 1363 of 3773
Page 1364 of 3773
Page 1365 of 3773
Page 1366 of 3773
Page 1367 of 3773
Page 1368 of 3773
Page 1369 of 3773
Page 1370 of 3773
Page 1371 of 3773
Page 1372 of 3773
Page 1373 of 3773
Page 1374 of 3773
Page 1375 of 3773
Page 1376 of 3773
Page 1377 of 3773
Page 1378 of 3773
Page 1379 of 3773
Page 1380 of 3773
Page 1381 of 3773
Page 1382 of 3773
Page 1383 of 3773
Page 1384 of 3773
Page 1385 of 3773
Page 1386 of 3773
Page 1387 of 3773
Page 1388 of 3773
Page 1389 of 3773
Page 1390 of 3773
Page 1391 of 3773
Page 1392 of 3773
Page 1393 of 3773
Page 1394 of 3773
Page 1395 of 3773
Page 1396 of 3773
Page 1397 of 3773
Page 1398 of 3773
Page 1399 of 3773
Page 1400 of 3773
Page 1401 of 3773
Page 1402 of 3773
Page 1403 of 3773
Page 1404 of 3773
Page 1405 of 3773
Page 1406 of 3773
Page 1407 of 3773
Page 1408 of 3773
Page 1409 of 3773
Page 1410 of 3773
Page 1411 of 3773
Page 1412 of 3773
Page 1413 of 3773
Page 1414 of 3773
Page 1415 of 3773
Page 1416 of 3773
Page 1417 of 3773
Page 1418 of 3773
Page 1419 of 3773
Page 1420 of 3773
Page 1421 of 3773
Page 1422 of 3773
Page 1423 of 3773
Page 1424 of 3773
Page 1425 of 3773
Page 1426 of 3773
Page 1427 of 3773
Page 1428 of 3773
Page 1429 of 3773
Page 1430 of 3773
Page 1431 of 3773
Page 1432 of 3773
Page 1433 of 3773
Page 1434 of 3773
Page 1435 of 3773
Page 1436 of 3773
Page 1437 of 3773
Page 1438 of 3773
Page 1439 of 3773
Page 1440 of 3773
Page 1441 of 3773
Page 1442 of 3773
Page 1443 of 3773
Page 1444 of 3773
Page 1445 of 3773
Page 1446 of 3773
Page 1447 of 3773
Page 1448 of 3773
Page 1449 of 3773
Page 1450 of 3773
Page 1451 of 3773
Page 1452 of 3773
Page 1453 of 3773