Loading...
The URL can be used to link to this page
Your browser does not support the video tag.
Backup Documents 05/08/2012 Item #16A 8
16A 83 'UF [HE ur I i(;L OF I HE C 4 r, i7 ,-r)0, 177 Purchasing Department , �JTOPNIF' _W Coif 3327 Tamiami Trail East Y „ Naples, Florida 34112 AcIrrunisbatkne SeNces OMsion 2112 "' " ` _ c j {, `.t Telephone: (239) 252 -mil rl � Y -9 A"! 18 Purchasing FAX: (239) 252 -6597 Email: DianaDeLeon @colIiergov.net www.colliergov.net ITEM NO.: DATE RECEIVED: FILE 0.:11 -PRC -02093 / ROUTED ✓ t�` �� DO NOT WRITE ABOVE THIS LINE ,y Request for Legal Services y C Date: May 8, 2012 To: Scott R. Teach S County Attorney's Office /J From: Diana DeLeon for Rhonda Cummings, FCCN, CPPB, Procurement Strategist Re: Amendment #1 to Contract #11 -5753 Electronic Fareboxes Contractor: Fare Logistics Corp. BACKGROUND OF REQUEST: This amendment was approved by the BCC on May 8, 2012 Agenda Item 16.A.8 ACTION REQUESTED: Contract amendment review and approval. OTHER COMMENTS: Please forward to the BCC office for signature after approval. If there are any questions concerning the document, please contact me at the telephone number or email address above. Purchasing would appreciate notification when the documents exit your office. C: Glama Carter, Public Transit Manager 0/ G/ Acquisitions/ AgentFormsandLefters /RiskMgmtReviewofl nsurance4 /15/2010/16/09 OWE EXHIBIT A -1 Contract Amendment #1 to Contract I1 -5753 "Electronic Fareboxes" This amendment, dated tkk j j 2012 to the referenced agreement shall be by and between the parties to the original Agreement, Fare Logistics Corporation (to be referred to as "Contractor ") and Collier County, Florida, (to be referred to as "County"). Statement of Understanding RE: Contract # 11 -5753 "Electronic Fareboxes" The Contractor agrees to amend the above referenced Contract by replacing Exhibit A -Scope of Services with the attached Exhibit A -Scope of Services, which incorporates technical clarifications to the original language. The additions to the existing language are shown herein by underlinine; deletions are shown by All other terms and conditions of the agreement shall remain in force. IN WITNESS WHEREOF, the Contractor and the County have each, respectively, by an authorized person or agent, hereunder set their hands and seals on the date(s) indicated below. ATTEST: Dwight E. Brock, Clerk Approved as to form and Le sufficienc puty � CountyAtttorney Name OWNER: BOARD OF COUNTY COMMISSIONERS COLLIE&gO JJNTY, FLORIDA By: W. CO Fred W. Coyle, Chairman First Witness TType /print witness nameT Second Witn •s 711'Y1 L�1 �lonl TType /print witness nameT NAYAN P. GHELANI Commission # 1625490 z Notary Public - California z z Riverside County D My Comm. Expires Dec 31, 2012 16A 81 Fare Logistics Corporation Contractor By: Signature Typed signature and title Stable d t',,a>Wyd S' - befaa► me aft wbo prayed to me an the basis of satWwtory evidence to be the persons whore names) is/aadsubsaabed b the wilco inslnxraent and a knowl4W to nae daafpBsheMaey executed the same in bil wAbOauthorited cigixq(w), and hat by giflhe" aaipNaa u*s) on the insOwraed Me persons), or hs eaatity upon b" d which he pwsoaa(s) acted. exeaAW he m*wnent. ph�Iaaae�and wider #e Isws d tie a CaSfanit M Aae WITNESS my hand and WicW seal. 16A 8 EXHIBIT A Scope of Services 11 -5753 Electronic Fareboxes Contract Overview The tasks and sub -tasks listed below are based on a current understanding of the project requirements. During the progression of the project, the County project manager and project manager for the Contractor will monitor the progress of each task and sub -task, and adjust the resource allocation and schedule as needed. The administration of the contract shall be as follows: 1. Any changes shall be mutually agreed upon in writing, but will not require a formal change order unless the change(s) would exceed the overall contract amount. 2. It is expressly stated and understood by the parties that zero dollar changes, including, but not limited to, time extensions not exceeding 20% of the overall contract, and time and /or sequence changes to Milestones may be made through the use of a Change by Letter signed by the County Project Manager or his /her Designee. 3. The Change by Letter will include a line for the Consultant's representative or designee's signature. Copies of the duly signed letter shall be forwarded to the appropriate Procurement Strategist for final signature and forwarding to the Finance Division. I. Work to Be Performed By Contractor The Contractor shall perform the following work: A. The Contractor shall be responsible for all work and expenses relating to the design, manufacture, delivery and installation of the equipment to the Collier Area Transit ( "CAT ") facility. B. Project to be completed, and final invoice must be submitted by February 28, 2013. C. The equipment, subsequent to testing, shall be complete in every respect and suitable for revenue service. D. For those items of equipment to be installed by the Contractor, the Contractor shall provide all hardware and other materials and all personnel and supervision necessary for installation in accordance with the schedule proposed by the Contractor and approved byCounty. 1. The Contractor shall supply such materials and supervision as may be necessary for the proper configuration and installation of the fareboxes, revenue equipment, Fare Collection Management and Reporting System (FCMRS) and any options exercised by County. All equipment shall be tested in accordance with a startup test procedure to be developed by the Contractor and approved by County. The Contractor shall provide on -site supervision of all installation efforts at all times during the installation. The Contractor shall adhere to the agreed installation schedule and procedures and provide the necessary documentation of work performed during the installation work. 2. The Contractor shall remove the existing fare collection system, including all existing fareboxes from the buses and the revenue servicing equipment in the cashbox vaulting lanes of the CAT facility. The Contractor shall be responsible for transporting such removed items to a central storage location at or near the CAT facility as designated by County. 3. For those items of equipment to be installed by the Contractor, a list shall be provided of all items of hardware and the required Contractor and CAT personnel and supervision for installation work in accordance with the schedule proposed by the Contractor and approved by County. Page 1 of 61 16A 8 e 4. Contractor shall provide personnel to supervise, inspect and adjust the equipment prior to, during and through final acceptance of the final system. E. All equipment shall be of the latest engineering change level available and shall incorporate suitable modifications for all known operational problems identified during the PDR/ CDR reviews and during testing at factory. The Contractor shall retrofit all known problem solutions (engineering changes) to the equipment installed prior to the initial testing and any additional upgrades, recalls, campaigns, etc. that are made available to other customers during the warranty period. The Contractor shall notify County in writing of all such upgrades. F. The Contractor shall propose an installation schedule for the CAT's approval. Installation shall be completed over two (2), two -day weekends. G. The Contractor shall deliver the equipment to the location specified by the County, for purposes of temporary storage. County will provide suitable storage facilities prior to installation of the equipment and will assume sole responsibility for the equipment while in storage. H. Revenue collection vault(s) equipment, software and specifications shall be provided by contractor to County. County will provide a specific unobstructed site at its facility for the installation of the vault. This site shall be level and of suitable construction for such installation. If it is necessary to pour a concrete pad for the vault, County will be responsible for this work as well as for the construction of the vault; and the contractor shall be responsible to provide required pad size dimensions, load requirements, and mounting hardware to be embedded in the pad and any electrical or data conduit requirements that are to be embedded in the pad. J. The Contractor shall make available full and competent engineering services to identify and correct all problems associated with the performance of its equipment in a timely manner. K. Contractor shall be responsible for repairs under the terms and conditions of the warranty and maintenance support provisions indicated herein. Subsequent to the warranty period any parts, assemblies, and equipment shipped to the Contractor for repairs shall be subject to repair charges in accordance with an agreed upon schedule of prices or quotation for parts and labor. L. The Contractor shall provide the services of a qualified representative to meet with County to provide consultation and instructions regarding installation of the equipment specified herein. For operation of fareboxes on the bus, the Contractor shall use the existing DC electrical power available on CAT buses. M. The Contractor shall prepare all deliverables in both Microsoft Office (Word, Excel or PowerPoint) and Adobe PDF formats, with County granted full rights to reprint as needed. N. All work shall be in accordance with the schedule described herein or a modified schedule approved in writing by the County. O. The Contractor shall inspect the existing bus fleet and the power available with the existing batteries to ensure that there is sufficient power available for operation of the new Fare Collection System. If there are any deficiencies, these shall be identified by bus type to the County for a mutually acceptable resolution of the issues. 1. Where data system installation or other electrical installation is involved, the Contractor shall be responsible for all work involved and must coordinate with the County's CAT and IT staff in the running of any overhead or underground conduits for data cable, stringing supported or unsupported cables from probe points to the computer and providing adequate electrical service for the equipment provided. Plans for such work shall be approved by County and meet all requirements of all applicable building codes. 2. Electrical requirements and all cable to the extent indicated in these specifications shall be furnished by the Contractor. Contractor shall inspect and coordinate with the County's IT staff the site where the facility equipment is to be installed and determine with County's approval if the existing conduit can be used within the new fare collection system. Contractor shall certify that this effort has been Page 2 of 61 16A 8 completed and include the usage of the existing conduit in the installation plan if such use is found to be appropriate. 3. The Contractor shall provide the services of a qualified representative to meet with representatives of County involved in this procurement to provide consultation and instructions relative to the proper provisions and work for the installation of equipment specified in these specifications. P. The Contractor shall furnish electrical requirements and all cable to the extent indicated in these specifications. Q. The Contractor shall be responsible for providing base dimensions and load requirements. Provisions shall be included by the Contractor to allow for the vaulting area to include methods to minimize the effect of moisture in the vault location to degrade the operation and/ or security of the vaulting equipment. R. The Contractor shall be responsible for hosting computer hardware and software required as part of the FCMRS (please refer to Section 5 for further requirements). County shall be able to access this hosted system over a secured network without any Contractor intervention, unless necessary for software support. The database used in the hosted FCMRS shall be secured and County shall be the complete owner of the data. County shall have full system administrator privileges to manage the user access levels and password - protection for the FCMRS. S. The Contractor will deliver the County's requested "remote Hosted solution," which will encompass the Contractor maintaining the Transfare system database, wireless communication to farebox devices for revenue data collection, installation of the TransMedia workstation connected to the Contractor's Private Network, as well as an ISP web portal to be used for County management to access reporting by means of a website URL to access the TransFare system. II. Work to Be Performed By County A. County will make buses available to the Contractor for installation work. County shall provide movement of buses as necessary. County shall approve all installation plans and procedures by the Contractor. B. County shall assist the Contractor in coordinating the actual farebox and other equipment installation. County will provide a mechanic and supervisor at the facility location where installation tasks are performed. C. County will provide AC power for all tools and lighting needed by the Contractor for physical installation. D. County will provide adequate storage space at its facility location to store the fareboxes and related equipment upon delivery from the Contractor. This storage shall be secure and protected from the weather. County shall also provide personnel and material handling equipment to bring the fareboxes (and other equipment) from such storage place to the designated installation sites. E. County will be responsible for and provide any and all material handling equipment and personnel required to lift or otherwise manipulate the vaults, collection bins, or their contents during day -to -day revenue transfer operations. F. County will provide a specific unobstructed site at its facility for the installation of the vault. This site shall be level and of suitable construction for such installation. If it is necessary to pour a concrete pad for the vault, County will be responsible for this work as well as for the construction of the vault; and the Contractor shall be responsible to provide required pad size dimensions, load requirements, and mounting hardware to be embedded in the pad, and any electrical or data conduit requirements that are to be embedded in the pad. G. County shall provide 120 VAC, 15 amp electrical services in proximity to the agreed upon location for the arel�iststemisan beRc� �nt�t Collection Vault. H. County shall coordinate with the Contractor regarding the system configuration of computer hardware and software required as part of the remote hosting of FCMRS at Contractor's facility. Page 3 of 61 16A 8 j III. General Design Requirements The fare collection system specified herein shall be designed to function reliably in the intended transit environment specified. All normal conditions for this environment, including, but not limited to dust, moisture, electromagnetic interference, power line fluctuations, vibration, and exposure to atmospheric conditions shall not affect the reliability or service life of the equipment provided. The range of these environmental conditions shall be tested during the First Article Testing (FAT). A. Design Life - The fare collection system hardware and software shall be designed to provide a usable life for a minimum of twelve (12) years subject to proper preventive maintenance being performed. B. Modular Components -_All equipment shall be designed as modular. Modules from equipment of the same type shall be exchangeable between items of equipment without hardware or physical modification. Components, subsystems, assemblies, and subassemblies shall be of modular design for ease of maintenance and interchangeability and shall conform to the operational, storage and functional requirements as incorporated herein. C. Human Engineering 1. The fare collection system hardware and software shall be designed to provide for ease of use by a properly trained individual. 2. All software shall be designed to be user friendly, allowing the user to access all features through graphical user interfaces, pull down menus, and on -line help features based on assigned password privileges. D. Interchangeability All of the equipment furnished shall be identical in manufacture and function. The equipment and the components of the equipment shall be completely interchangeable. E. Maintainability and Accessibility 1. All components shall be packaged in replaceable and repairable modules. Standard hardware and components shall be used for flexibility and ease of maintenance. Standardized commercially available hardware and components shall be used to achieve flexibility in use and to facilitate maintenance. There shall be sufficient latitude in the operating tolerances to permit the substitution of modules without the necessity of making any electrical or mechanical adjustments. Modules and sub - assemblies shall be easily accessible and removable without the need for special tools. 2. All system elements provided under this contract to be used by the general public shall conform to the requirements that are in effect on the date of this proposal. For the purposes of this specification, all references to ADA requirements shall include the requirements imposed by any and all of the laws and regulations. 3. Entry codes shall be performed using internal keypads, with delayed alarm triggered if the proper code is not used. In equipment which contains revenue, the use of an internal access code and exterior access control system (PIN code, identification card or other security scheme) shall be required. F. Security and Safety All fare collection equipment shall be designed, manufactured, assembled and installed in a safe manner. Once the system is installed and available for use, there shall be no hazard to the public upon use of the fare collection equipment. The fare collection equipment shall pass County's safety verification as part of the First Article Test. G. External Surfaces 1. External surfaces of all system equipment shall be clean, with no projections, sharp edges or corners that can cause any person injury or damage to property. External surfaces shall not contain cracks, weld marks, burrs, discolorations, or distortions resulting from fabrication, shipment or installation. Page 4 of 61 16A g 1 2. Surfaces not of stainless steel, aluminum, or plated shall be painted with a corrosion resistant paint. Painted surfaces shall be free of rust, scale, grease and foreign matter immediately preceding the first priming coat. Paint applied to any internal surface shall be designed to last for the life of the particular component to which it is applied. Paint applied to any external surface shall be baked enamel or other coating designed to last for a minimum of twelve (12) years before needing to be repainted. 3. The Contractor shall spray paint and bake all surfaces that are painted in order to give them a hard enamel finish. Any paint shall be uniformly applied over all surfaces to be covered, and shall be free from runs, sags, dirt or other application defects. 4. Color, metal protection materials and processes, and finish of all paintwork to be used on internal and external surfaces of all lane equipment shall be subject to County selection and approval. H. Locks 1. The Contractor shall provide all cashbox vaulting lane equipment with locked covers to prevent unauthorized access. 2. System equipment of the same type shall have identical locks that open with the same key number, and each type of equipment shall require different key numbers for access. 3. Separate access shall be provided, where possible, for operating personnel to perform routine maintenance and shall be keyed differently to equipment areas requiring access only by technical maintenance personnel. I. Reliability 1. The reliability of the fare collection shall be as follows at the conclusion of all acceptance testing: • Farebox: 2,000 Mean Cycles Between Failures • RCVS 10,000 Mean Cycles Between Failures 2. One (1) cycle for the farebox shall be defined as one (1) complete fare verification at a farebox, including required bus operator button presses. 3. One (1) cycle for the RCVS shall be defined as one (1) complete emptying cycle of a cashbox into the receiver vault. END OF SECTION IV. ON -BOARD EQUIPMENT The farebox shall be a mounted, freestanding device used to collect and securely store fares using a variety of fare media. This shall include processing cash, tokens and magnetic transfers and passes. The farebox shall be controlled by electronic logic and supported by electronic memory, displays and indicators. It shall permit the easy insertion of fare media by boarding customers; provide a display for customer information; and an CCU with human factors engineering practices and industrial design considerations. The farebox shall be reliable in revenue service operations, accurate in its counting and data reporting, and secure in its retention and transfer of data and collected revenue. Under normal operating conditions, processing of fares shall require the minimum effort by bus operators to accurately and correctly account for customer fare payment and collection of revenue. Operational Features -- The farebox shall have the following operational features: • Accept, validate, count and register US coins and paper currency, • Return coins, bills and tokens and other objects that are not valid or acceptable to the system; • Accept, validate and count magnetic farecards; • Print and issue a transfer, day pass and other agreed -upon types of passes; • Print, encode and issue a farecard for fare overpayment (i.e., a "change card ") • Permit the recording of various types of fare transactions using bus operator activated pushbuttons. Page 5 of 61 16A 8.4 4.1 General Performance Requirements A. The farebox, as defined within these specifications, shall include all hardware and software installed on- board any CAT bus for purposes of accepting payment of the fare by a customer by: cash, token (as defined by County) and magnetically coded transfers and passes as valid fare payment methods. The system software and hardware shall include means for validation and acceptance of new currency to be issued in the future by the United States Treasury Department. B. The farebox shall be installed on each bus, adjacent to the bus operator, and in proximity of the front door. It shall be positioned so that an entering customer may easily insert the required fares into the farebox, using a fare payment of coins without blocking exiting customers. This position shall permit the bus operator to readily determine the customer's fare payment method, observe all of the digital readouts provided on the bus operator side of the farebox (including the OCU), and reach and manipulate various bus operator controls from the seated position. The farebox location shall permit all of the required maintenance functions to be performed, as well as to provide easy access for the removal of the cashbox and meet all ADA requirements for customer entry and exit. C. The mounting of the farebox shall be designed to minimize movement or rattling of the farebox. D. The farebox shall be a solid -state logic controlled validating farebox with supported memory used to accept, validate, count and securely store paid fares. E. The farebox shall function under the environmental and operational conditions stated in these specifications and shall be designed and manufactured to provide a high degree of security against forced entry into the cashbox area and /or unauthorized manipulation of farebox modules. F. The farebox shall permit the customer to easily and rapidly insert the required fares and for the bus operator to readily ascertain that the correct fare has been paid, regardless of the fare payment method employed. The capacity of the farebox shall be such as to securely retain the collected fares until such time as they are removed under authorized conditions. The farebox shall function in a reliable manner so as to provide service on an uninterrupted basis, consistent with the performance requirements contained herein. G. The farebox shall function to provide specific information relative to the daily operations of the farebox; the revenue amounts, types and quantities of customers, bus operator and work run identification; bus location data, and other information which may be used in providing audit trails; ridership data and accountability of the specific items of equipment and of the system operations. The degree and extent of this information and the means and methods of its generation and reporting shall be as described in these specifications. H. The electronic boards utilized within the farebox, including associated electronic components, shall be capable of operating ten thousand (10,000) hours between failures provided there is no abuse, vandalism, operation beyond standards or lack of maintenance per the Contractor's instructions. I. On -board equipment shall have a mean time to repair of ten (10) minutes. Repair shall be defined as the diagnosis, removal and replacement of one (1) or more defective assemblies (such as a coin unit, bill transport, MSR, OCU, cashbox, electronic board, etc.) to put the equipment back into operating condition. Repair of the defective assembly will not be included in mean time to repair. J. The farebox shall have the ability to create and store summary records as well as transactional records, K. The activation and deactivation of bus operator log -on /log -off with the OCU shall be settable and modified only via downloaded fare table parameters from the Fare Collection Management and Reporting System (FCMRS). L. A switch shall be located within the farebox to disconnect it from the vehicle power. Location of this switch shall be identified on the farebox design drawings and shall be subject to review and approval of County. Page 6 of 61 16A 841 M. Contractor shall provide stickers and other graphics for the fareboxes to identify the various slots and displays, which shall identify the correct insertion of payment and fare media. These shall be provided by the Contractor for County review at PDR and approved at CDR. 4.2 Coin Acceptance A. Operation 1. The farebox coin unit shall accept, validate and count the value of pennies (1 1), nickels (54), dimes (10¢), quarters (254), half - dollars (50¢), and (Susan B. Anthony /Sacagawea) dollar coins ($1.00); and accept and validate a token as desired by County. Validation of the coins shall be by weight, density, magnetic properties, size and /or other means which will guarantee that only valid US coins are accepted and validated. 2. The coin slot shall permit ease of coin entry and shall be designed to last the life of the equipment. 3. Acceptance and registration of coins shall be at a coin insertion rate of not less than ten (10) coins per second. The coin unit and associated logic may be utilized to _ identify other sizes of coins without necessity of replacement or remanufacture of the coin unit or other hardware change. 4. Subsequent to insertion and registration, coins shall be directed to a cashbox located within the base of the farebox. Within the cashbox the coins shall be maintained separate from the bills. 5. The counting logic of the farebox shall increment the appropriate non - resettable counter for each denomination of coin and each type registered and accepted. 6. Any remaining value displayed on the OCU and the Customer Information Display shall clear after the display clear time has elapsed. County shall have the ability to set the display clear time in one (1) second increments from zero (0) to sixty (60) seconds via the FCMRS. 7. The coin unit shall meet the following criteria: • Ninety -nine percent (99.0 %) of valid coins shall be accepted and validated upon initial insertion. • Ninety -nine and eight- tenths percent (99.8 %) of valid coins shall be accepted and validated upon one (1) reinsertion. • All known counterfeit coins, common slugs, foreign coins, and coins of denominations not valid shall be rejected upon every insertion. • Validation accuracy of accepted coins shall be at least ninety -nine and ninety -five hundredths percent (99.95 %). 8. Each coin unit shall be permanently inscribed with a clearly visible unique serial number. B. Coin Return 1. A coin return cup or tray shall be provided on the farebox, located within easy reach of a customer and conforming to all ADA requirements. 2. Any coin which the customer inserts into the farebox and the coin validator cannot automatically validate shall be returned to the customer via the coin return cup. This shall include deformed coins and coins otherwise not meeting the specified valid coin criteria. 3. The farebox shall note in its memory and retain for data transmission the instances of coin returns. This information shall be forwarded to the FCMRS to assist in failure diagnosis. C. Deformed Coins 1. The coin unit shall have the capability of handling, without jamming, coins which are deformed. That is, coins which, within certain limits, are bent or bulged, not perfectly round or have attached foreign material. 2. The coin unit shall process and accurately validate coins with the following deformations: Page 7 of 61 16A 8 a) Coins bent or bulged having overall thickness ranging up to 0.020 inch greater than the coins' standard thickness. b) Coins having attached, relatively complete and uniform layers of foreign material (such as epoxy, solder or hardened gum) ranging up to 0.040 inch in thickness. c) Coins not perfectly round (examples: squashed or flat edges) having diameters up to plus or minus 0.020 inch different from standard diameter at the point of deformity. D. Coin By -Pass 1. A coin by -pass mechanism shall be provided for the passage of coins to the cashbox by- passing the coin unit (in the event of, for example, a coin jam in the coin unit or a failure of the electronic logic). When a farebox is placed in by -pass mode, the FCMRS shall record this event. 2. The activation of the coin by -pass mechanism shall be by a deliberate action on the part of the bus operator. Coins processed in this manner shall not be counted nor registered by the farebox but shall be passed directly into the cashbox. 3. In the operation of any device to achieve a coin by -pass, the security of the farebox and the retention of the revenues shall not be diminished. When the mechanism is used, it shall not be possible for the bus operator to reset it from outside of the farebox. 4. The farebox shall note in its memory and retain for data transmission, the exact time when the by- pass is activated and deactivated. A record shall also be created when the by -pass is activated and again when the by -pass is deactivated. 5. The resetting of the mechanism shall require access to the farebox interior by authorized personnel. 6. When the coin by -pass is activated, bills, magnetically encoded and smart cards shall continue to be accepted, registered and processed. 4.3 Bill Acceptance A. The farebox shall be capable of accepting, validating and counting U.S. $1, $2, $5, $10 and $20 bills oriented in any of four (4) directions. The paper currency acceptance slot shall be positioned in the general proximity of the coin insertion area, and shall accept bills which have been opened to their full area and inserted lengthwise. The dimensions of the currency slot shall hinder the accidental entry of coins into it. The currency slot shall be illuminated to permit ease of bill entry in diminished lighting conditions using LED lighting designed to last the life of the farebox. The unit employed to transport the inserted bills shall be positive and not require precise insertion by the customer. A guide bezel shall be provided to assist in the entry of the bill into the currency slot. The bill shall be inserted approximately one (1) inch before the transport shall become operational and advance the bill to the validation area. B. The bill transport shall employ a roller mechanism to positively engage an unfolded and folded bill, regardless of condition without jamming. It shall require no force to cause the transport to start. C. The bill shall be advanced to the cashbox (in the lower portion of the farebox) after validation. Any remaining value displayed on the OCU and customer display shall clear after the display clear time has elapsed. D. Bills shall be processed at a maximum rate of one (1) bill per second. This time shall be measured from the time that the bill is sensed in the bill insertion slot to the time that the value of the bill is displayed to the customer and the bus operator. E. The bill transport shall have the capability of handling, without jamming, paper media which is deformed. That is, paper media which is subject to the conditions of daily "street" use, including wrinkled, torn, folded, or damp media. F. The bill transport shall process and accurately validate bills with the following conditions: 1. Bills which are not uniformly flat or in "new' condition. Page 8 of 61 fl-WM0411 2. Bills which are torn to a depth of two (2) inches from the edge of the bill. 3. Bills which are damp but not saturated. 4. Bills having tape or other foreign material adhering which can fit through the opening in the currency slot. G. Each bill transport shall be permanently inscribed with a unique serial number, clearly visible when the maintenance apertures of the farebox are opened. H. Bill processing and acceptance shall meet the following criteria: 1. 97% of valid bills shall be validated and accepted upon initial insertion. 2. 98.5% of valid bills shall be validated and accepted within two (2) insertions. 3. All known counterfeit bills, color photocopies of valid bills, duplicates made by other known means, foreign bills, and bills of denominations not valid shall be rejected upon every insertion. 4. Validation accuracy of accepted bills shall be at least 99.95 %. I. The acceptance sensitivity of each denomination of bill accepted shall be adjustable. J. Bills and other paper items placed in the bill insertion slot that are not accepted shall be returned to the customer at the bill insertion slot. 4.4 Operator Control Unit A. The farebox shall be equipped with an Operator Control Unit (OCU). Integral to each OCU shall be a keypad and display or touch screen to operate the farebox. The OCU shall be capable of initializing a farebox and its electronics for route and run setup. B. The OCU shall not be integral to the farebox but shall be housed in a separate compact console constructed of revenue service tested materials. Mounting hardware shall be provided to permit mounting on the vehicle dashboard or other appropriate location, facing the bus operator. The OCU shall be positioned not less than twenty -five (25) inches from the bus floor. The OCU shall be mounted on an adjustable and lockable ball joint that allows the bus operator to provide for ease of button operation and viewing of the display. The installed CCU shall not interfere with any bus controls, block any bus indicators or other bus operator displays, or create a safety hazard. All mounting arrangements shall be approved by County. The OCU shall be connected to and communicate with the farebox via protected cabling. C. The OCU shall be provided with a two (2) line electroluminescent display, a light emitting diode display or a backlit liquid crystal display (LCD) or an approved equivalent such as a full context touch screen with not less than twenty (20) alphanumeric characters per line, and which shall be fully dot addressable, capable of displaying graphics and capable of displaying a minimum of two (2) lines of text. The OCU shall be able to show the full ASCII character set. For backlit LCD displays, the OCU contrast shall be adjustable and backlighting shall be capable of being turned on or off via the OCU keypad. The display shall be of sufficient brightness to be visible in all forms of ambient lighting within the bus and shall be sufficiently protected by a panel of clear plastic which shall also reduce glare. D. Under normal operations when the farebox is static, the bus operator information display shall be extinguished to preserve its operating life. It shall be active when it is required to display operational information, when the bus operator inputs data, and when a given push -button is depressed. Alternatively, County may elect to have this display show the current time when the farebox is static, the time being extinguished when it is necessary for the display to provide information. E. The bus operator information display shall indicate to the bus operator the status of any ongoing transaction and other information pertinent to the operation of the farebox, including: 1. The amount of money inserted into the farebox in the form of coins and bills and the fare due. 2. The current function of the soft (programmable) function keys. Page 9 of 61 16 a i� 3. The function of a given button on the keypad when that button is depressed. 4. Confirmation for any bus operator input information. 5. Bus operator sign -on and sign -off prompts. 6. Upon completion of the farebox "boot sequence' the farebox shall be required to be set with ' Fareset' for the run. As coins and bills are validated, this display shall count upward, reflecting the amount of money inserted. If a preset fare is used, when the full fare is reached, or when the bus operator presses a button indicating acceptance of a reduced fare (student, senior, etc.), a tone shall sound, and the display shall automatically subtract the proper fare from the amount on the information display and display the remainder. G. If a transaction is not completed, the bus operator information display shall be automatically reset after the last coin /bill has been validated based on the duration of the user settable timer. This timer shall permit County to set the display clear time from zero (0) to sixty (60) seconds in one (1) second increments. Any remaining value displayed shall be added to the "unclassified revenue" data register. It shall be possible for the bus operator to delay resetting by pushing a designated "hold" button which shall reset the timer to zero. H. The CCU if other than a full context touch screen shall have a minimum of twenty (20) pushbuttons, including digits 0 through 9, ENTER, CANCEL, and user - definable function keys. All bus operator pushbuttons shall be fully programmable, shall provide tactile and audio feedback and shall be sealed against the intrusion of liquids and other foreign material. I. The CCU touchscreen keypad shall enable the bus operator to classify reduced or special fares and perform all other on -board tasks connected with the operation of the farebox in revenue service. J. Each of the classification buttons on the keypad shall be capable of being programmed to: 1. Register a specific value ($0.01 to $99.99) with the option to also record the fare in the designated category with the option to reset the register display to "0.00." 2. Increment a zero -value tally counter. 3. Be disabled (nonfunctional). K. The fare values assigned to each classification button shall be individually programmable for each fareset. The values assigned to these buttons will be changeable in a matrix format; that is, each preset activated by the bus operator may have a different value assigned, depending on the fareset and requirements of County. This matrix shall be stored in the non - volatile memory of the farebox, and shall be changeable only via the means outlined in these specifications. L. Each time a button is activated, the bus operator's information display shall indicate the key number pressed and show the value assigned. Cash fare registration pushbuttons shall be able to be activated prior to, during, or after the validation of money in the farebox to obtain the proper farebox setting. Pushbutton keys used as tally counters shall require no money to be inserted to obtain a count. Each time a pushbutton is pressed in the proper manner, a tone shall sound, indicating that a count has been made in the corresponding farebox data register. Individual pushbuttons shall also be able to be deactivated and these shall have no effect on the registration of fares or tally count by the farebox. M. The farebox logic shall provide for the storage of entered log -on information including route number, run number, trip number, fareset, and bus operator number into the farebox memory. This shall be accomplished using the trail of the identity of the bus operator and other log -on information for later transmission to the FCMRS upon Liata tiansfci- using wyJwlcss comunications}4cA44- 1. N. A farebox that has gone into the "Idle" mode shall remain in that mode until the Avail System (or the bus operator in backup mode) has logged -on to the farebox. O. Log -off from the farebox shall occur in four (3) ways: Bus operator sign -off via the CCU Page 10 of 61 2. Automatic time -out log -off (based on a preset time period of farebox inactivity). 3. Automatic log -off following data transfer After log -off of the farebox by any method, a message shall be immediately forwarded to the OCU and the OCU and other displays shall be placed in the idle mode. This shall include those occasions when a bus operator prematurely signs -off the farebox. P. All push- buttons shall be of sealed construction to prevent entry of foreign material which might degrade performance. Design of the buttons shall provide a tactile indication to the bus operator that electric contact has been made. Q. It shall not be possible to program the farebox with information that would normally be transferred from the FCMRS by using the OCU. R. A bus operator actuated function, shall be used for the purpose of displaying the contents of various information registers on the OCU. These registers shall be user definable via the FCMRS and their display shall be password protected. 4.5 Customer Information Display A. The customer information display unit shall be provided in the form of a 2 -line (minimum) 20- character alphanumeric back lit LED or CAT - approved equivalent. The back lighting shall provide for adjustable intensity to provide clear visibility in bright lighted conditions and during night operations. B. The display shall be positioned on the farebox facing the boarding customers approaching the farebox. C. Under normal operations when the farebox is static, the customer information display shall be extinguished to preserve its operating life. It shall be active when: a coin, bill, magnetically encoded pass or a token is processed by the farebox and when the bus operator classifies a fare. In addition County shall have the ability to program a message on the display (e.g., "Welcome Aboard ") rather than have the display inactive. D. The display shall be able to show the full ASCII character set. E. The customer information display shall indicate specific messages programmable by County through the FCMRS relative to use including: 1. Validity (for passes) 2. Amount deducted and remaining value to be deposited by the customer 3. Remaining value for stored value based farecards 4. Cash inserted in the farebox 5. Amount due 6. Farecard step -by -step loading instructions (i.e., for adding stored value to an existing farecard) F. The customer information display shall provide displayed messages programmable by County through the FCMRS to the customer for selected fare media processing difficulties including: 1. Card misread (applies to farecards used in the TPU or the MSR) 2. Insufficient value remaining 3. Invalid card (including bad card list match) 4. Fare media expired G. When a cash transaction is initiated, the display shall show the amount deposited and the amount of the fare. When a magnetically- encoded card is read using the TPU or MSR, the display shall show relevant information such as: 1. Expired or Invalid Page 11 of 61 16A 8 2. Please Try Again 3. Value remaining 4. Amount due (if no remaining value on farecard) H. Information on the operation of the customer information display and all such conditions sensed, reported and displayed shall be provided at the PDR. 4.6 Audible Signals and Spoken Messages A. The audio transducer shall be provided with a sound level of not less than 65 db at a nominal 12 volts DC. The audio transducer shall sound the specified tone under the conditions stated below. A minimum of three (3) clearly distinguishable tones shall be provided. Tones shall be programmable by County through the FCMRS. Designation of initial tones for testing are provided below in parentheses. 1. The audio transducer shall sound each time a valid fare is inserted and registered (Tone 1). 2. The audio transducer shall sound a multiple signal when an invalid or expired fare medium is used (Tone 2). 3. The audio transducer shall sound a multiple signal when a permit or reduced fare medium is used (Tone 3). 4. The Audio transducer shall sound a multiple signal as acknowledgment that the bus operator has completed the sign -on procedure and that the data has been received by the farebox (Tone 1). 5. The audio transducer shall sound a multiple signal as acknowledgment the data has been extracted properly (Tone 1). 6. The audio transducer shall sound a multiple signal when a button unassigned to the active pre -set is pressed (Tone 2) B. The farebox shall also be capable of generating spoken messages using digitized human voice. It shall be possible to enable and to disable the spoken messages via the FCMRS. Spoken messages shall be triggered by County defined farebox operating conditions and include messages such as, "Transfer Not Valid ", "Please Swipe Card Again ", and "Please Insert Card Again." County shall be able to choose from a list of standard and custom spoken messages and assign them to the relevant functions by use of sound files located in a FCMRS data file. 4.7 Fare Structures A. The fare collection system shall provide for no less than ten (10) individual fare tables that describe separate fare structures. B. It shall be possible for County to change the fare values in any fare table by means of data entered by the FCMRS and the PDU, without the necessity of removing or replacing any of the farebox electronic components. C. Each fare table shall include all information required to provide for proper processing of the customers based on County's fare structure and associated usage rules including: the base fare, the value of any tokens, the valid customer categories plus their associated fares, day passes accepted, day passes issued (plus appropriate charges), other passes accepted, and "cash drops" for other pass types. D. Means shall be provided for the bus operator to switch between the fare tables at the start of a route and during a run on certain routes, such as express services. The means shall not require any special components. The farebox shall only accept a valid fare table based upon the information downloaded to the farebox from the FCMRS. E. Upon completion of changing the fare table a "Change Fare Table" record shall be created defining the new pre -set and a summary record shall be stored. Page 12 of 61 16A 8 4.8 Fare System Presets The farebox shall be capable of operating in two (2) distinct modes: 1. Preset fare mode 2. Manual mode (no preset fare) A. In preset mode, the farebox shall count up and display the value of the inserted amount. When the amount of the preset is reached, the farebox will automatically count the preset fare as one (1) adult customer and decrease the register readout by the amount of the fare. The Bus operator may also press a button to indicate that a fare classification other than the preset fare applies and the farebox will be temporarily set to accept the alternate fare classification. When the proper fare is paid, the fare will be counted and the register readout decreased by the amount of the fare classification. Any overpaid balance shall remain displayed for a programmable time -out period and then return to zero unless overridden by the Bus operator. B. In manual mode, the farebox shall count up and display the value of the inserted amounts. When the bus operator presses the category of fare, a unit count shall be added to a specific register representing that fare category. The overpaid balance shall remain displayed for a programmable time -out period and then return to zero unless overridden by the Bus operator. C. In either case, the overpaid amount shall be able to be used toward an additional fare unless the bus operator resets the register reading to $ 0.00. F. The farebox shall have the ability to have a minimum of ten (10) preset amounts, programmed into the electronic logic. A preset amount shall be between $0.05 and $19.95 in value. 4.9 Memory and Data Storage Requirements A: The farebox shall have sufficient memory to store a minimum of 10,000 transaction records, 2,000 records (including time segment records) and 2,000 event /alarm records. This memory shall be backed up with a redundant data module B. The farebox shall be able to hold and support the volatile portion of the memory after being removed from power for not less than fourteen (14) days after removed from a primary power source. Lead -acid batteries, which may leak, shall not be used for this purpose. C. Under no circumstances shall the failure of a battery corrupt the data or affect the ability of the farebox to collect the proper fare, perform validation of coins and bill and other fare media or compromise any security feature of the fare collection system. A message shall be provided using the OCU to notify the bus operator of a low battery condition that will allow adequate time (at least twenty-four (24) hours of operation) to replace the battery. A report shall also be made via FCMRS of low- battery condition. D. Electronic logic incorporated in the farebox shall receive value signals from the coin unit, bill transport, ticket processing unit and the swipe reader. The electronic logic shall accumulate and store the amounts in an electronic register and such amounts shall be displayed on the OCU. The accumulated fares shall advance revenue registers which shall accumulate the total value received by the farebox since the farebox was last probed and the total value received by the farebox since installation or clearing of the farebox memory. Totals shall be stored for all cash revenues and tally counts retained for number of magnetic swipe cards read. Separate counts shall also be stored for each type of fare media accepted. E. A separate count shall be accumulated for all cash that is displayed on the OCU and not accounted for via push button activation. All such revenue shall be included on an unclassified revenue register. A transaction record shall also be stored recording the amount dumped and the associated fareset number. Each fareset shall be set to activate or deactivate this pushbutton. F. Transaction Records The following data shall be generated by and stored in the farebox and be available for the generation of reports and queries when transferred to the FCMRS: Page 13 of 61 16A 8 1. The fare collection system shall generate a transaction record for each customer processed which shall be transferred to the FCMRS. Each transaction record shall be unique within the system. This transaction record shall include the following information: a) date and time of transaction b) magnetic card serial number c) bus number d) farebox number e) route number f) run number g) direction code h) fareset number i) trip number j) customer type (adult, student, senior, etc.) k) fare type - bus fare, transfer charge, short fare and overpayment 1) amount paid m) method of payment n) cash denominations and quantities o) expiration date p) transaction number q) service type; local, express and special run 2. The fare collection system shall generate a transaction record for each vaulting and wireless data communications incident. 3. The fare collection system shall generate a transaction record for each bus operator log -on and log - off by any of the four (4) methods described in this specification. 4. The fare collection system shall generate a transaction record for each event sensed by the farebox. 5. The fare collection system shall generate a transaction record for each alarm initiated. This information shall be stored in a separate security file, access to which shall be protected by security password. 6. The fare collection system shall generate the transaction records necessary to provide the maintenance information. 7. The fare collection system shall generate a transaction record whenever any of the following events takes place: a) The bus operator log -on operation is altered. b) When a route /run record is recorded. c) Midnight and other date /time changes d) The farebox is placed in bypass e) The farebox is removed from bypass f) The cashbox is removed (cashbox number shall be saved) g) The cashbox is inserted (cashbox number shall be saved) Page 14 of 61 16A g h) The cashbox access door is closed after a time -out period of five (5) minutes (this period to be FCMRS settable as an operations parameter) i) The cashbox access door is opened at other than the time of normal eta }�l�iPc cnt i Seri icing. j) The cashbox access door is closed at other than the time of normal �a��n Rc�cnuc Sery -icing k) The farebox data transfer starts 1) The farebox data transfer ends m) The farebox internal clock fails n) The record storage is about to overflow o) Changing from one (1) pre -set to another p) All payment transactions, including the value of coins and the value of bills c) All ridership registration transactions r) Farebox power off s) Farebox power on t) Bus operator log -on u) Bus operator log off v) Unsuccessful data transfer w) Successful download of farebox configuration data x) Unsuccessful download of farebox configuration data y) Farebox errors and failures z) Security errors and intrusions aa) Coin jams bb) Clearance of coin jams cc) Bill jams dd) Clearance of bill jams ee) New fare table selected ff) Farebox percentage full (settable threshold of 50 -100 %) for coin gg) Farebox percentage full (settable threshold of 50- 100 %) for currency G. Time Synchronization 1. The farebox shall contain a real time clock which shall store the time that will be used for printing; recording; validating; time and date stamping of transactional data, and fare media; for display of transaction records on the CCU; and as part of bus operator and customer information. This clock shall record and display hours, minutes, seconds and date in appropriate formats. This clock shall be capable of being reset to the correct time automatically upon log -on and each time data is transmitted from the farebox and shall be accurate to within one (1) minute per year. 2. The Fare Collection System shall have its own time synchronization function through the County LAN to the FCMRS clock for standalone operation. In this mode synchronization of the computers to the LAN shall be performed at least once every twenty -four (24) hours, and synchronization to the farebox will occur when the farebox is probed by the FCMRS, J. Time Segment Records Page 15 of 61 16A 8 1. All fareboxes shall be provided means to permit the bus operator to make a "summary count record" within the farebox memory. This function shall provide means to aggregate data for a segment of a route to, for example, gather number of boarding customers at a user specified interval. The default period for the time records shall be fifteen (15) minute summaries. 2. The memory capacity of the segmenter shall be suitable to compile a minimum of 2,000 records (as a part of the total number of records) per farebox vaulting. 3. The information stored in the segmenter shall not be accessed through the bus operator's information display, but shall be stored and transferred to the FCMRS. Once stored in the farebox, data shall not be available to the bus operator for editing in any fashion. 4. To create a "record ", the bus operator shall press specific buttons in a prescribed sequence. The information display shall confirm this by showing the words "Make Summary Record ". The bus operator shall then be required to confirm or cancel. 5. In addition, County may elect to have a summary record initiated automatically at set intervals based on the real time clock in the farebox. These intervals may be every ten minutes, every fifteen minutes or every twenty minutes or more as required by County. This feature shall be set to be activated by downloading from the FCMRS. 6. A summary record shall be created with a special code indicating the type of event that took place, e.g. bus operator initiated, automatic based on time, farebox placed in bypass, etc., and this shall be reported in the data system when the appropriate reports are accessed. The special code may be a predetermined number not otherwise used by County. K. Farebox Diagnostic and Operational Reporting 1. The farebox and its electronic logic shall be designed to provide the specified degree of operational self testing, diagnostic operations, reporting and indication. These elements are required for effective maintenance of the equipment, to provide audit trails to determine proper farebox operation. 2. Indicator Lamps - A series of LED indicator lamps shall be provided which shall indicate to a technician the proper operation of all of the major modules. An LED indicator shall be used to indicate proper voltages from the main power supply. 3. Automatic Sequence Testing - The farebox logic shall be designed to provide an automatic sequence testing of each of the major operational assemblies. The automatic sequencing shall be initiated by the insertion of a "test plug" or USB stick or other approved means, thereby placing the farebox in a "test mode ". Each assembly shall be caused to fully operate a minimum of four (4) times during the automatic sequence. The sequence shall continue for an indefinite period until stopped by external intervention. The amount of time during which the testing sequences was run shall be recorded by the farebox in terms of minutes and seconds. This time shall be available for display on the OCU. 4. Coin /Bill Totals - The farebox logic shall provide specific counts of individual coin and token types by quantity. This is above and in addition to the requirements for accumulating value, as described elsewhere in these specifications. The farebox shall also provide a unit count of the quantity of bills processed by denomination. The farebox shall also provide total counts of all coins processed and all bills processed. These counts shall also be used for preventative maintenance and audit purposes and as a second determinant of validation factors associated with each farebox coin unit and bill transport. 5. Power Supply Monitoring. The farebox shall monitor and report the number of times the primary power source has gone to zero (0) volts and back to normal. This serves to indicate an intermittent power line or poor ground connection or faulty switches. The farebox shall also monitor and report the number of times the power supply drops below the minimum voltage, but not to zero (0). This is indicative of a heavy load on the bus electrical system or a possibly defective bus battery cell. These counts shall be reported through the data reporting system. Page 16 of 61 6. Security Door /Cashbox Alarms - The farebox shall be provided with a sensing device capable of monitoring real time and the length of time that the cashbox security door is open. If the door is open for longer than three (3) minutes (programmable), an alarm signal shall be transmitted to the data storage within the farebox memory. The real time at which this alarm was sensed along with the length of time the door was open shall also be stored in memory. The next time the farebox is probed, the transmission shall contain a "security door alarm ", indicating the time of the alarm, the length of time the door was open, and how much revenue was in the farebox at the time of the alarm. The farebox shall be provided with a sensing device capable of monitoring the presence of a cashbox in the farebox. If a cashbox is removed at a time that varies by more than three (3) minutes (programmable) from the time that the farebox is probed, a cashbox alarm shall be created and stored in the farebox memory. The real time at which this alarm was sensed along with the length of time the cashbox was not in place shall also be stored in memory. The next time the farebox is probed, the transmission shall contain a "cashbox alarm ", indicating the time of the alarm, the length of time a cashbox was not in place in the farebox, and how much revenue was in the farebox at the time of the alarm. 7. Cashbox Full Indicator - The farebox shall be provided with a visible indicator on the OCU to prompt the bus operator when either the coin compartment or the bill compartment in the cashbox reaches eighty percent (80 %) (programmable) of their respective capacities of coins or bills. The indicator shall remain visible until the cashbox is extracted and the coin compartment and the bill compartment registers are automatically set back to zero. The coin compartment and bill compartment amounts required to activate the visible indicator shall be programmable. 8. Farebox Reporting - All amounts, quantities, and other information developed as a consequence of compliance with the requirements of these specifications shall be stored in the farebox memory and shall be transmitted to the FCMRS for later report printing of the information for each farebox. 9. Maintenance Information - The farebox shall include resettable transaction counters that maintain the number of payment cycles for the coin unit, bill transport, TPU, MSR and the entire farebox. The individual transaction counters, as well as the farebox transaction counter shall be capable of being reset by the technician whenever the module is removed for maintenance. This counter information shall be stored within the farebox and transferred to the FCMRS upon data wireless data tiarnsmissionpi-obiii 10. Door Open - The farebox shall store an alarm transaction when one (1) of the doors on the farebox is opened including the top cover, cashbox door and maintenance access doors. The cashbox alarm shall be an audible alarm and alarm message only if the door is open for more than the user settable period of time or if the door is opened without proper authorization. The alarm shall not sound and the alarm message shall not be created in any other instance. 4.10 Cashbox Removal, Identification and Locking System A. Cashbox Removal 1. The cashbox door shall be fitted with internal devices which shall only release and open the door B. Cashbox Identification System 1. The farebox shall have the ability to automatically read a unique identification number of each inserted cashbox. This serial number shall be a minimum of four (4) digits. 2. The means and methods employed shall not require electrical contacts, plugs or other physical connections between the farebox and the cashbox. 3. Readings shall be automatic, and the information relative to the serial number shall be stored in the farebox memory for subsequent data transmission to the FCMRS. Only one (1) serial number record shall be stored for each cashbox insertion and for each removal from the farebox and receiver. Page 17 of 61 16A 8 4. If a battery is used in the cashbox, the system shall be designed such that the battery shall have a minimum lifetime in this application of three (3) consecutive years and shall provide an advance warning on the OCU and FCMRS sufficient to allow for battery replacement before battery failure. C. Cashbox Door Locking System 1. The farebox shall incorporate within its logic elements, the ability to retain a specific code or other secure means to release the cashbox door. The action of closing the cashbox access door and holding it in the closed position for approximately one -half (0.5) second shall cause the farebox mechanism to engage the door locking pins and lock the cashbox access door. If the door is slammed, with rebound, the mechanism shall not engage. 4.11 Magnetic Swipe Reader Fareboxes shall be provided with an integrally mounted read only magnetic swipe reader (MSR) located on the top surface of the farebox. The reader provides a longitudinal slot in which a magnetic card is manually traversed past a read head. A. Function 1. The MSR shall be able to accept magnetically encoded cards that have been previously encoded with data such as date of expiration, type of service, conditions of use, serial number and other information relative to its proper operation in revenue service. The farebox shall function to read the information on the card(s) and determine whether the card is "valid" or "invalid" based upon the preprogrammed parameters in the farebox as compared with the encoded information on the card. 2. The MSR shall automatically process a correctly inserted, valid magnetic card in one -half (1/2) second or less. The operation and usage of the MSR shall not impede customer boarding or flow in any manner. Magnetic card insertion, swipe through and removal by the customer shall be in the general flow of customers boarding the bus 3. Cards shall be read on first proper insertion with an accuracy of not less than 99.0 %, assuming each card is valid, is fully inserted such that all coded information passes across the read head, and the card is not damaged sufficient to destroy the ability of the MSR to correctly read the coded data. 4. If a card is not valid for the current class of service, the farebox shall display the amount to be inserted by the customer. Additionally, the farebox shall accept and separately register additional cash fare payments in accordance with the fare structure. Registration of additional cash fares shall cause the card to be accepted without requiring the bus operator to push a button. This cash data shall be accumulated in a separate register. 5. The card read head assembly shall be held in place by not more than two (2) readily accessible fasteners. Electrical connections shall be plug -in and screw type connectors, or equivalent, approved by County. A trained maintenance technician shall be able to replace the read head assembly within five (5) minutes. 6. The MSR shall be capable of operating under the same environmental conditions as the fareboxes. 7. The MSR shall not encode any data on the card read but shall be a read -only device used for reading information encoded on cards. B. Visual and Audible Indicators 1. The OCU display shall allow the bus operator to monitor magnetic card activity as required, indicating the type of transaction being conducted, any problems or other messages. 2. In event of a challenge between the bus operator and customer regarding the use of magnetic card or cash deposit, the bus operator may depress a button to retain the information on the OCU display. Page 18 of 61 16A 8 3. For each card accepted by the farebox as a valid fare the farebox shall sound a tone indicating that a proper fare has been paid. A recognizably different tone shall be sounded in event the transaction is refused by the farebox and the CCU and customer display shall indicate "INVALID" and additional information to explain why C. Passback Protection 1. Passback protection shall be provided as specified elsewhere in these specifications. D. Data Encryption 2. Magnetic stripe data shall be encrypted to provide for data security. The security scheme used shall be presented and explained at the PDR and finalized between the Contractor and County at CDR. 4.12 Magnetic Stripe Farecard Stock A. The magnetic stripe farecards shall be the standard credit ticket size of 2 -1/8 inches by 3 -3/8 inches. The magnetic stripe shall be 1/4" wide, located 3/8" from and parallel to one long edge. Manufacturing specifications shall define farecards that are fully compatible with the farebox equipment. B. All magnetic media shall utilize high coercivity magnetics of not less than 2,000 oersteds. 4.13 Interface For Connections To On -board Systems The farebox shall be capable of connecting to other devices on the bus over industry standard interfaces including SAE J- 1708/) -1587 and SAE J1939. These other devices include CAD /AVL system to be installed by Avail Technologies. The on -board interface with Avail Technologies shall allow the following: 1. Single -point operator logon (using operator ID and run ID) and logoff via MDC 2. Accepting run, route, trip and operator information provided by MDC 3. Sending farebox alarms to MDCs 4.14 System Security A. The fare collection system shall incorporate the highest level of security in order to ensure that all revenues inserted into the farebox are securely deposited into the cashbox. In addition, the system shall provide for secure transportation and collection of all deposited funds from the time the cashbox is removed from the farebox to the time the monies are counted. B. The goal of the fare collection system is to provide for the secure collection and transfer of all deposited revenues and to provide appropriate alarms under those circumstances when there is risk of revenue leakage by means of data manipulation or by unauthorized access to the cashbox, including the potential unauthorized use of keys during the revenue collection procedure. A. The system security shall employ software controls, monitoring, security interlocks and other similar subsystems and controls to achieve these goals to the highest degree. Hardware and /or software security provisions shall be provided for the following: 1. Access to Cashbox Interior - Each cashbox shall be provided with a high security lock to inhibit unauthorized access to the contents of the cashbox. 2. Access to the cashbox within the farebox shall require the downloading of data prior to unlocking the cashbox access door. Download shall be via tethered probe or optional wireless means. 3. Access to the contents of the cashbox from the top of the farebox shall be prohibited when the cash processing modules are properly in place. When these modules are removed or not installed properly, an alarm message shall be created and transmitted via the Avail on -board system to the central dispatch workstation. 4. Unique alarms shall be created for the following events as a minimum: a) When the cashbox emptying time exceeds a preset limit (settable from 5 seconds to 5 minutes in one (1) second increments). Page 19 of 61 16A 81 b) When the top cover of the farebox is opened, whether in service or not. c) When the cashbox access door is opened and when it is closed while in service. d) When the time that the cashbox access door is open exceeds a preset limit specified elsewhere herein. 4.15 Equipment Construction A. This section describes the general constructional requirements to be included for the on -board fare collection equipment. 1. Mechanical Details a) The farebox and its mounting fixtures shall be constructed in a manner to discourage vandalism and theft. Finishes shall resist corrosion, abrasion and scratching. All exterior surfaces shall be clean with all corners rounded. There shall be no exposed bolt heads, nuts, sharp edges or cracks on the outside surfaces. b) The upper portion of the farebox shall be made of brushed or satin finish stainless steel, not less than 14 gauge, suitably reinforced for rigidity, and with no external and /or removable fasteners that provide access to the interior of the farebox. County will review other revenue service- proven materials proposed to determine their suitability and provide the appropriate approvals. c) A top assembly shall be provided on the upper portion of the farebox which shall serve as the bezels for the entry of coins and bills, the slot for the MSR and to provide primary maintenance/ inspection access to the interior of the farebox. This assembly shall have two (2) entry slots for cash, one (1) for coins and one (1) for bills. The top casting material shall be aluminum or stainless steel, with minimum wall thickness of 1/8 inch and suitable reinforcing ribs for added strength. d) The coin slot shall be used to direct inserted coins into the farebox and shall be sized no larger than a dollar coin. Its design shall be such as to deter the entry of paper and lint into the coin slot and the formation of coin jams. e) The bill slot shall have a protruding lip to assist in the sliding of the bill into the slot. The casting shall be painted with black epoxy enamel or powder- coated, over a suitably cleaned and primed surface. The surface of the casting shall be free of chips, blisters and other imperfections which lead to chipping of paint or unattractive appearance. f) The top casting shall have affixed to it, by means of high yield adhesive, multi -color decals which indicate the function of the respective card, coin and bill slots and provide instructive information as to their use. These decals shall utilize different colors than the top casting and shall be subject to the approval of County. g) The top assembly shall be secured to the farebox upper portion by means of a continuous hinge and high security lock. h) For maintenance purposes, additional maintenance access doors may be provided to permit access to the interior of the farebox. If it is possible to get access to any revenue by opening any maintenance access door or assembly, the operation of other maintenance access door(s) shall be interdependent upon the authorized opening of the top assembly, with interlocks provided to assure that these doors /panels are not left in the open position when the top assembly is closed and locked. i) The lower portion of the farebox shall be made of stainless steel. The material shall be not less than 14 gauge, reinforced for rigidity. A revenue access door shall be provided to protect and conceal the cashbox within the farebox. This door shall have high strength components to protect the cashbox from unauthorized entry including a high security electronic lock mounted in a secure location. The farebox shall have a provision to allow employees and managers to determine that the cashbox is present and open to receive Page 20 of 61 16A 8 revenue. The design shall be such that there shall be no gaps allowing prying the door open 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. j) Keys and /or locks which 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. The cashbox door shall not close if the cashbox is improperly aligned. k) Wires and cables which are run through the lower portion of the farebox to the upper portion shall be run in a protected channel and /or raceway. No wires shall be visible when looking at the cashbox cavity. 1) A base plate shall be used, and shall be affixed to the lower portion of the farebox to permit mounting to the bus floor. The dimensions and construction of this base plate shall provide the necessary lateral stability, without secondary anchorages. The base plate shall be affixed to the floor by means of "carriage bolts" from the interior of the bus, with the washer plates and nuts on the underside of the floor. The base plate material shall be cast aluminum or stainless steel, with reinforced metal deposits surrounding each bolt hole for maximum strength. If a base plate is not used, the mounting of the farebox shall be by internal means utilizing four (4) high yield bolts. The lower part of the farebox shall be suitably designed and reinforced to prevent deformation or wear in service, oxidation, deterioration or accumulation of tolerance which might allow the farebox to be subjected to increased vibration, wear, metal fatigue or other degradation. m) The upper and lower portions of the farebox shall each be securely fastened together by means of high yield bolts, accessible from the interior of the farebox. The completed assembly shall measure not less than thirty-one inches (31 "), and not more than forty -one inches (41 ") high, as measured from the bus floor, and not more than eleven inches (11 ") in cross section, excluding the mounting base plate. (In certain classes of buses, it may be necessary to exceed this height to allow for comfortable operation of the farebox by the bus operator. Such buses are to be identified by the Contractor, and the Contractor shall propose an alternative means for mounting the farebox, which shall be subject to approval by County prior to completion of the CDR. n) The coin unit shall be modular in construction so as to be removable within one (1) minute for inspection and /or replacement. The coin unit and any materials thereon shall be fastened by mechanical devices. Adhesives requiring scraping and cleaning with solvents shall not be used. The farebox shall have a guide chute integral to its construction to guide the coins into the cashbox. There shall be no protrusions on which coins can snag, causing a jam. o) The bill transport shall be a self- contained module which may be removed and replaced. It shall be built of reinforced materials for rigidity, provided with captive fasteners and be self - aligning upon insertion. It shall be capable of being locked within the farebox. The farebox shall have a guide plate integral to its construction to guide the bills into the cashbox. There shall be no protrusions on which bills may snag, causing a jam. p) All major subassembly modules shall have a unique serial number inscribed or permanently applied. No two (2) serial numbers shall be the same on any two (2) modules of any type. County shall be provided with a list of all serial numbers and the modules to which they have been applied prior to installation of any item of equipment. Subassembly modules to which such numbers shall be applied shall include, but not be limited to, coin unit, bill transport, electronic lock, cashbox, upper case, lower case, TPU and MSR. q) Approvals shall be explicitly requested of County by the Contractor for use of any alternate composition materials in place of materials specified herein. Any such approvals shall include revenue service experience in similar conditions. Failure by the Contractor to Page 21 of 61 16A 8 request the necessary approvals shall deem those not identified by the Contractor as materials unacceptable for this project. r) A baffle system in the coin chute shall be employed to prohibit access to or "fishing" of coins from the cashbox upon removal of the coin unit from the farebox cabinet. s) A baffle system or other mechanism shall be employed to prohibit access to or "fishing" of bills from the cashbox upon removal of the bill transport from the farebox cabinet. 2. Electrical Details a) The electrical termination of the farebox, for purposes of connecting it to a power source shall be by means of a polarized, snap connect plug on the underside of the farebox. b) The electronics shall be of the solid state type, assembled on reinforced printed circuit boards. These boards shall be modular (plug connected) and removable for inspection and /or maintenance. The components mounted on the board shall be soldered in place, or for those items to be readily removed, high quality sockets with retainers shall be used. c) All major electrical/ electronic subassemblies and devices shall be interconnected by means of polarized positive plug connectors with self - locking retaining features to assure proper connections and preclude intermittent performance due to poor contacts. All plug -in components shall be retained with a positive force holding them in position to ensure they do not work loose with the vibration that can be expected in the buses. d) Wires and multi - conductor cables, where used, shall be color coded and /or marked to permit positive identification. It shall not be possible to improperly insert a plug -in component into a connector. e) Display characters shall be of high intensity type viewable through a range of not less than a sixty degree (600) arc when mounted within the farebox cabinet, and have a rated life of not less than 10,000 hours of operation without segment failure. f) Fuses, circuit breakers or other protective devices shall be employed to protect the electronics, motors and other components from overload and damage. Where used, they shall be accessible without disassembly of components. Location shall permit inspection and /or replacement through normal maintenance access doors or panels. g) A master "disconnect" switch shall be provided, internal to the farebox to disconnect the farebox and OCU from the incoming power supply. This switch shall be identified and marked, and be of the two (2) position type. h) The farebox power supply shall be large enough to provide adequate power to the various farebox components and provide additional power for the electronic memory, MSR, TPU and OCU. i) The complete loss of power to the farebox shall not cause any information or data contained in electronic memory to be lost or altered. The electronic memory logic shall be capable of maintaining electronic memory without bus power for a minimum of one (1) month j) The farebox electronics and logic shall be protected against stray electro- magnetic interference (EMI) radiations, vibrations, ultraviolet light, or other environmental conditions which would cause the farebox to become inoperative and /or lose the data contained therein k) Where electronic circuit boards are employed and where they are to be inserted and /or removed by means of board guides, they shall be provided with lifting tabs. 1) All circuit boards shall be provided with polarized plug connectors. No harness wiring shall be directly connected by means of solder to any board which shall be removed for maintenance or inspection. Page 22 of 61 16A 8 m) All circuit boards shall be factory pre- tested for a minimum of seventy-two (72) hours prior to their final inspections within a given farebox. n) All electronic displays shall be tested for all segment functions for a minimum of forty eight (48) hours. o) The arrangements of the electrical and electronic components shall be such as to permit adequate ventilation to disperse the heat created and to preclude degradation of components and performance. p) Access to the electronics, power supplies, and other electrical components for maintenance, replacement or repair shall not require the removal of the cashbox from the farebox or the removal of the farebox from the bus. q) The farebox circuits shall be designed to draw minimum power from the bus battery. The farebox shall incorporate the following power levels: • Normal operation during which time operating power required shall be five (5) amps or less. • Idle mode which shall be activated upon time out of the predetermined interval timer. During the "Idle" mode the OCU shall provide a visible indicator, such as a blinking character, and the coin and bill entry light shall remain illuminated. The farebox shall be ready to collect revenue. r) The above electrical requirements shall apply to all modules connected to or contained within the farebox, including the TPU, MSR and OCU. 4.16 Cashbox Requirements A. Physical Cashbox Criteria 1. The cashbox shall be made of plated or stainless steel, 20 gauge minimum. It shall be a welded construction with no external fasteners exposed which affect security. Those areas of the cashbox which come in direct contact with the farebox shall be abrasion resistant. Neither insertion into and /or removal of the cashbox from the farebox in revenue service operations nor vibration or shock experienced while the cashbox is in revenue service in the farebox, shall cause any distortion of the cashbox material, which may adversely affect its ability to function properly. County will review other revenue service - proven materials and designs proposed to determine their suitability and provide the appropriate approvals. 2. The cashbox shall be constructed in a configuration to fit within the dimensions of the lower portion of the farebox. The cashbox shall have two (2) individual separate compartments to receive and retain coins and bills, each in their respective compartments. 3. The cashbox, when empty, shall weigh no more than twenty (20) pounds. It shall be provided with a handle or handles to allow it to be safely carried by a person with gloved hands. 4. A permanent serial number shall be securely affixed to the cashbox where it will be visible when the cashbox is in the farebox and the farebox door is closed and locked. B. Coin Mix Definition 1. Whenever there is a reference to and /or requirement for "mixed coin ", the following mix of coins in multiples or fractions shall be used: C. Bill Mix Definition 1. Whenever there is a reference or requirement for "bill validation" the term shall refer to the acceptance and condition of 100 bills in multiple or pro -rated quantities which are to be fed into the farebox in a flat, unfolded condition. For performance and testing purposes, the ability to accept and validate the following mix of bills for each denomination shall be demonstrated at the First Article Test: All bills shall be dry and not mended (not taped), and folds shall not exceed 1/16 of an Page 23 of 61 u u 0 nt inch in diameter. The circulated and worn bills shall be drawn from the revenue collected by the present County fareboxes as follows: Coin Mix Definition Penny $0.01 100 $1.00 Nickel $0.05 100 5.00 Dime $0.10 250 25.00 Quarter $0.25 240 60.00 Half Dollar $0.50 2 1.00 SBA $1 $1.00 5 5.00 Sacagawea $1 Coin $1.00 10 10.00 Total US Coin 5 707 $107.00 A. Cashbox Configuration 1. Cashboxes shall have the capacity to hold and completely transfer to a receiver vault $500 in mixed coin and 700 bills in unfolded "street money" (not "brick" or mechanically stacked or compressed) bills, or paper equivalent. 2. The operation of the cashbox shall be such that the cashbox is in a closed and locked condition whenever the cashbox is removed from the farebox. When the cashbox is out of the farebox it shall be able to be opened only with the valid revenue key. 3. The 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 therein, during any portion of the collection or revenue transfer cycle. Bill Mix Definition New, uncirculated bills: No folds 5 1 fold halves 5 2 folds (thirds) 5 2 folds fourths 5 Circulated bills (not torn or limp): No folds 10 1 fold halves 20 2 folds (thirds) 15 2 folds fourths 15 Worn bills (small tears and limp): No folds 5 1 fold halves 5 2 folds thirds 5 2 folds (fourths) 5 4. The cashbox shall fit into the farebox only in a singularly correct position. The farebox shall remain inoperable until the cashbox is inserted and ready to accept revenue, and the cashbox access door is closed and locked. 5. The cashbox shall not have removable lids, covers or other elements which may be detached from the cashbox. The cashbox shall be automatically locked and sealed when removed from the farebox. Page 24 of 61 16A 8 6. The locks (and keys) used on the cashbox shall be of the high security type as specified herein. The operation of any keys within the locks shall not require excessive torque, which may damage either the key or the lock. 7. The mechanism employed to open and /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, locking feet and other elements that are required to release the cashbox from the farebox or to lock it in place in the farebox. Aluminum or plastic components are examples of materials that shall not be accepted. 8. The interior of the cashbox shall afford complete gravity discharge of coins and bills in the revenue transfer cycle, while maintaining their separation. No ledge or other areas shall be present where coins may lodge and impede the operation of the cashbox. 9. The materials and construction techniques shall be such that a fully loaded cashbox, if dropped in the upright position to a hard floor and landing on its bottom or bottom corner from a height of forty -eight inches (48 "), shall suffer no operational impediment or security breach. The farebox and cashbox shall not be distorted when carrying a full revenue load. 10. Metal parts not constructed of stainless steel shall be painted, plated or constructed of corrosion resistant material. 11. The farebox /cashbox shall be designed and fabricated in such a manner as to prevent extensive tolerance buildup and resultant vibration which could be detrimental to the proper operations of the farebox or cashbox in service. 12. The cashbox shall function in a dependable manner in the operating environment of the transit system. It shall be capable of operation for two- thousand (2,000) days, mean time between failures. B. Cashbox Construction 1. The cashbox and farebox shall be fitted with devices to determine and report that the cashbox has been properly inserted into the farebox so as to allow the revenue access door to be fully closed and locked plus the cashbox has been opened (in place) and is ready to receive revenue. The devices used shall be tamper resistant, solid state and not subject to malfunction due to bus vibration. C. Cashbox Identification 1. The cashbox shall provide the ability to automatically read and transmit a four (4) digit (minimum) serial identification number of the inserted cashbox that shall be read by the farebox once the cashbox is locked in the farebox. END OF SECTION V. REVENUE COLLECTION VAULT SYSTEM AND AUDIT UNIT 5.1 General and Equipment Configuration A. The revenue collection vault system (RCVS) shall provide for the secure transfer of cashbox revenue into revenue collection vaults. B. The cashboxes shall be inserted into the cashbox receiver located above the revenue collection vault and the cashboxes shall empty all of their contents into the vault. C. The cashbox receiver and revenue collection vault shall be of heavy duty construction. D. All openings and high wear areas shall be constructed to be durable and able to accommodate rough handling. E. The system shall track the cashboxes that are emptied into the revenue collection vault and shall provide means for the reconciliation of revenues collected. Page 25 of 61 16A 8 j F. The cashbox receiver components shall operate reliably and perform all functions without difficulty and last a minimum of ten (10) years in the environmental conditions existing at the CAT facility. This shall include moisture and wash water spray, humidity, airborne dust and bus exhaust, temperature extremes, electromagnetic interference and grounding factors. 5.2 Cashbox Receiver A. The cashbox receiver shall employ a door that is opened to receive the cashbox. After the cashbox is inserted into the receiver in the correct orientation and the door is closed and locked, a crank or similar mechanism shall be utilized to open and empty the cashboxes in a secure manner. B. The receiver shall be interfaced to the FCMRS and shall read and report the cashbox serial number automatically read from the cashbox. Cashbox serial number shall be forwarded to the FCMRS only if the emptying cycle takes place and is successfully completed. C. The cashbox receiver design shall provide a secure interlocking of shutters sealing off the receiver from the revenue collection vault's bill and coin storage areas such that access is prevented to these areas when: (1) the door is open and, (2) there is no cashbox within the receiver. D. The emptying mechanism shall not be able to be turned partially and returned to the starting position. When the cashbox is inserted, it shall be required to fully complete the emptying cycle before the cashbox can be removed. E. The emptying cycle shall be completed and the cashbox lid closed and locked before the cashbox receiver door shall be able to be opened. F. The cashbox receiver shall incorporate three (3) indicators to visually identify the current status of the cashbox receiver 1. One (1) indicator that the emptying cycle is taking place 2. One (1) indicating that the cycle is completed. 3. One (1) indicating that the receiver bin is full or not in place and the door shall not open. G. The cashbox receiver shall only operate - door close, perform emptying cycle, door re -open - when a cashbox is placed properly and securely within the receiver. If a cashbox is not properly in place, the door shall not close and the emptying cycle shall not commence. H. The emptying cycle shall be completed in no more than ten (10) seconds to completely empty the full cashbox. I. The openings into which the cashboxes are inserted shall be constructed of materials able to sustain high wear resistance and shall be durable under rough handling. J. The cashbox receiver shall be protected by a door to deny access to the receiver opening and shall provide manual locking means for security purposes when the receiver is not being employed for revenue servicing. K. Keys and locks which are retained in the receiver lock cylinder and used to interface with the cashbox shall be securely fastened and shall be accessible and removable only in an authorized manner. L. Guides shall be employed within the receiver cavity to assure that the cashbox is in alignment for proper operation. 5.3 Revenue Collection Vault A. The design of the revenue collection vault shall take into consideration strength and security requirements so as to resist forced and unauthorized entries. B. The openings in the receiver into which the revenue collection vaults are inserted shall be constructed of materials able to sustain high wear resistance and shall be durable under rough handling. The lower portion of the receiver shall have steel guides, constructed of durable steel, to properly position the vault below the receiver. Page 26 of 61 16A 8 C. The cashbox receiver shall be protected by a door to deny access to the receiver opening and shall provide manual locking means for security purposes when the receiver is not being employed for revenue servicing. D. Hinges shall not be exposed and there shall be no pry points available for forced entry. E. The vault shall contain two (2) storage areas: 1. Coins shall be stored in one (1) area with a capacity of $10,000 in mixed coins. Coins shall be stored in a sealed compartment within the vault cabinet with a high security locked access cover that is designed to facilitate the controlled release of coins directly into the coin counting machine. The coin compartment shall have a smooth sloped bottom to allow the coins to discharge under gravity. 2. Bills shall be stored in a separate area with a capacity of 10,000 bills. Bills shall be stored in a removable bin completely within the vault cabinet and locked in place with a separate high security lock. A method shall be provided for easily removing collected currency from the revenue bin when this function is performed in a secure location. F. High security looks and an interlocking mechanism shall be employed to provide access to the receiver for maintenance purposes. 5.4 Audit Unit A. An audit unit shall be provided to permit the emptying of a single cashbox for audit purposes. B. The audit unit shall weigh not more than 200 pounds when empty and shall be mounted on wheels to permit ease of movement. The top portion of the audit unit shall incorporate a cashbox receiver to accept cashboxes for emptying. C. The audit unit shall contain two (2) compartments - one (1) for coins and one (1) for bills. The audit unit shall have capacity of not less than 1,000 bills and $1,000 in mixed coins. D. The audit unit shall be a stand -alone unit and shall not communicate with the FCMRS, unless so designed to improve the security of the cash handling procedure. 5.5 Locks and Keys A. All locks and keys used on the farebox and the revenue collection equipment shall be of the security type, Medeco or approved equivalent. Lock combinations and keys for all identical functions shall be keyed alike. Different combinations shall be provided for each function as detailed in the following table, where locks that are keyed alike have the same key type letter. All keys and spare locks shall be delivered to the CAT General Manager. Lock Location Key Type Retentive Receiver Mobile Vault Cover Door A Yes Receiver Door B No Receiver Service Doors C Yes Receiver Service Door Rear C Yes Farebox Cashbox Revenue Access D Yes Farebox Top and Maintenance Access Doors E No Mobile Vault Coin Compartment F Yes Mobile Vault Banknote Compartment F Yes Audit Receiver F Yes Cashbox receivers shall open the cashboxes via a cashbox key mounted in the back wall of the cashbox receptacle. Cashboxes secured within a farebox shall open via a cashbox key mounted in the back wall of the cashbox receptacle in the lower portion of the farebox. The cashbox shall only be able to be inserted in a singularly correct position in the farebox and cashbox receiver, and shall easily be placed Page 27 of 61 16A 8 into the ready position to transfer revenues. The cashbox insertion and removal procedure shall be designed to positively guide the cashbox into and out of the farebox and cashbox receiver. END OF SECTION VI. FARE COLLECTION MANAGEMENT AND REPORTING SYSTEM 6.1 General System Description A. General The Contractor shall host the FCMRS at its facility (please see Sections 2.1 and 5.1 [C]) for hosting requirements). The FCMRS shall communicate with the fareboxes to extract transaction and event data and download operating parameters and related information. The FCMRS shall communicate with the vault to extract cashbox identification from cashboxes inserted in the receiver. The FCMRS shall be complete and fully functional, with all necessary items of hardware and software installed and tested, and shall be furnished with such software licenses as may be required. The FCMRS shall include data probes linked to the database server identified in section C. The FCMRS shall be capable of generating comprehensive management reports for use by County. B. Application/ Database Server Hardware Requirements- Proposers shall describe the infrastructure to be used for hosting FCMRS for County. Please refer to the Appendix section for general IT requirements. Further specific requirements regarding the FCMRS application are as follows: 1. Workstation Connectivity to the Application/ Database Server -- The FCMRS application (including configurable security levels allowing full functional configuration ability and reporting) shall be accessible from existing computer County CAT workstations via a secured web -based interface (e.g., via Hypertext Transfer Protocol Secure [HTTPS]) and /or a client /server type configuration over secured network connection (e.g., web access via virtual private network [VPN]) which is compliant with County's IT requirements provided in the Appendix section. The vendor will train County to configure and support FCMRS access on County CAT workstations. Further, County shall be able to use currently installed network printers for printing information from FCMRS. 2. Operation of the computer to generate data system reports shall not prevent Revenue Seryicin<, of the fareboxes. The hard disk drive shall be capable of storing all of the data from up to 50 fareboxes with maximum route /run records. As new farebox records are added, the oldest records on the disk drive shall be automatically deleted. County shall be able to specify how many days of detailed data and months of summary data shall be saved. 3. The FCMRS shall be written in a standard, commonly available computer language not proprietary to this application. All communications shall be accomplished using standard networking protocols and hardware. The FCMRS shall utilize a relational database management system (RDMBS) [e.g., Microsoft SQL Server] which shall provide open database connectivity (ODBC) capability to third party tools/ applications for custom reporting or other purposes. 4. The FCMRS server shall be installed with redundant power supply and hard -drive configurations. Further, the FCMRS application shall be hosted in a high - availability configuration such that a secondary instance of FCMRS is immediately available to County in the event the primary FCMRS application fails. All data must be protected in the FCMRS database in the event of an application crash. C. System Operation -- The data collection and reporting system shall be configured in the following manner: D. Wireless Data Communications - In place of the `tethered probe" functionality that �N 'as specified the proposed Fare Logistics' Transl`,11T 'solution employs a secure bi- directional process utilizing state ol" the art wireless communications technologn . The data communications process for either in upload and /or download data between the Farebox and the back -end centr 'll d its SN "Jem is desi�ncd to be automatic. Page 28 of 61 Tlie C0111MLnalcatiolls function commences once a bus tray °cls into the ralage of a TransFarcrl' �, fireless access point and successfully authenticates a login The Voyager Electronic AValidating, Farebox sof of Farebox data softi, are and coni7i61uration files. The average download for a day's �n'orth of transactions is completed in less than one minute. Furthermore, valid transaction files are automatically imported into the T'ransFare"I database; ho%ycver this process requires the central server to be a node on the same netx��ork as the " ireless access point. ted –ice ra-cc� i —i -ii t uaa t+ t+r I iCen the frcn aieatt�{tirr 1 tae f z� rein s +} 3c n ;jia1! _1 usk active aiid 1 ,,,I4„l--toi' cl dlt — F�i-klbe— - �1,,, . data F' '�h � —cc,� ,�crt� -r 'rcill 1, .di 7 a ,F I -+ 1 1' -1 a 4.,4,,-n1is,J of data shall coiraraaeii(_ 'l t isillission seeond,), the - laiiip ", stea(44-�i1r,c'- f., .,ho, s1, -,II a�. The ,,;nershrlhhe i�aariatcbrrlfci -i�3 tfie r�,at t t -1,a n be el 4 a f, lidit . The ma ter list totak Computer Operations -- If the data computer had been previously shut off, it shall automatically load the proper software upon power up and prepare itself to process data without further attention from the operator. The data system shall then be left for automatic operation. The password used to get access to the application menu shall be changeable by means of a higher level password. The system shall have the capability of recording and reporting, upon interrogation by a user with a high level password, all uses of passwords for the previous 60 day period, the date and time of password use, the amount of time the system was in use with the password, and what reports or other functions were accessed. If it becomes necessary to change the high level password in the computer for security or operational reasons, it shall be readily accomplished via the operator keyboard. It shall be possible to use the data computer to change the fare tables in all fareboxes probed at the garage. These changes shall include the full fare value and the values and function of each driver pushbutton. In addition, the time of day shall be transmitted to correct the farebox clock if required. At County's discretion, changes to the fare tables and farebox clock shall be downloaded to each farebox automatically during routine prot*i— ,Revenue Servicing activities. All operator entries shall go into a transaction log capable of being printed on demand. Software shall be available in the data system to allow backup and retrieval of files. Software shall be available in the data system to allow archiving of transactional data as needed. - .,_Access to Computer Reports -- Both summary and detailed farebox data shall be stored on a password- protected database server to ensure that the original revenue and ridership data cannot be modified. This data shall be capable of being converted to a comma - delimited ASCII file format for export to third -party software. Software shall be available in the data system to allow backup and retrieval of files. The data system shall have multitasking capability and shall be able to accommodate \ fireless data transmission, p+t4i+4,., report generation, and other tasks simultaneously. Lockup of one task shall have no effect on concurrent tasks. 1.1?ircless dPata transmission "'shall not be slowed due to operation of concurrent tasks. Table -- The data system shall have the capability of changing the fare tables in the fareboxes per the procedure previously described. Each fare table assigns the value of a full fare as well as any reduced fares (student, elderly, etc.). Each individual fare amount may be between $0.01 and $99.99. It shall be possible to change the values through the farebox keypad or data system without removing or replacing any of the farebox electronic components. In addition, the following shall be transmittable: a) Current time and date (any valid time and date) Page 29 of 61 b) Electronic lock code (any five digit number) c) Start /stop times for AM and PM peak periods d) Keypad attributes (tally, tally /clear display, and value increments from 0.01 to 99.99) e) Fare table store option (the data system should transmit the fare structure to each farebox Transfer acceptance parameters h _ Tickets /Tokens /Passes acceptance parameters and other attributes Configurable Parameters The data system shall have the ability to enable or disable various functions such as ticket types, or other designated parameters as previously defined in this document. 6.2 Standard Reports The following standard reports, at a minimum, shall be available from the data system. All reports shall carry the CAT name, the date or period for which data is reported, and the date on which the report was generated and printed by the system. All reports shall be generated through "user friendly" menu - driven software. A. Individual Farebox /Bus Reports 1. For individual farebox reports, the printed report shall show the following categories of data at minimum: • Current revenue y} • To -date revenue • Unclassified revenue • Total full fare riders (ridership data shall be supplied for each fare table in use) • Total number of riders at each fare level • Tickets /Tokens /Passes • Total tokens • Total stored ride /value cards • Total passes • Total bills • Total coins by denomination • Technical Maintenance Reports • Bus Farebox Maintenance History 2. The first line of each individual farebox report (the "master list ") shall indicate the date and time of day the farebox was probed and the bus number and farebox number. Cumulative totals for the activity of that farebox shall be printed, corresponding to the column headings. 3. Trip -by -trip route /run data lists shall be printed next, following printing of the master list. Each route /run record shall be printed in the order in which it was created, along with notations of driver or route number(s) and the time the record was created. It shall be possible to transcribe this data from hard disk to other electronic storage medium for archiving or analysis purposes. B. Daily Summary Report Page 30 of 61 16A a 1. The daily summary report shall be printable, on request, at the end of the operating day. County shall have the ability to designate the end of the operating day as any time from 12:00 A.M. to 5:00 A.M. so that all buses that have operated on a given day shall be accounted for, regardless of whether they are probed after midnight. The daily summary report shall contain the same data categories listed above, less any that may be inactive or suppressed. Summary totals from master lists from all fareboxes reeenuc serviced pr+) ae4-that day shall be provided. Route /run data shall not be provided. 2. The full matrix of fare tables (excluding any inactive or suppressed tables) shall be printed showing the cumulative total ridership in each cell of the matrix. The daily summary report shall also provide a report of total daily ridership. The daily summary report shall print a summary of the data from the exception report, indicating the total number of buses revenue serviced pr4ed security door and cashbox alarms, bypass alarms, maintenance required (including power supply), memory cleared, unknown driver, unknown bus, unknown route, unknown run and other anomalous data from the exception report. A list of the buses not revenue scrvicedp�#, by bus number, shall also be printed. C. Periodic Summary Reports The data system shall have the ability to generate summary reports for specific periods, as follows: 1. Monthly Summary Report: This report shall summarize all activity fleetwide for a given month. Monthly summary information can be saved for up to 128 months. Totals shall be given for all active pre -sets and keys, revenue, tokens, bills, fare document types, etc., by day and totaled for the month. It shall be possible to print bar charts giving total revenue by date and total ridership by date. 2. Annual Summary Report: This report shall summarize the information given in the monthly summary report and give totals by week, quarter and year to date. It shall be possible to show each value of revenue, pre -set and key plotted by week in a separate bar chart. 3. Daily Route Summary Report: This report shall summarize all totals by route for a given day fleetwide. 4. Monthly Route Summary Report: This report shall summarize all totals by route for an entire month 5. Route /Sum Report: This report shall allow data daily or over a period of time to be sorted first by route, then by run, or by time /date. Ridership shall also be calculated and printed. For each route printed, the number of route run records included in the summary shall be indicated. The data in the route /run reports shall be based on when the route /run record was actually created (actual date and time), regardless of when the bus was re\;cnue serviced and da to was dm 7jiloadedpiobed. D. Exception Report 1. It shall be possible to generate a daily exception report listing operator entry errors (invalid route, run driver or trip numbers) as validated against lists of valid numbers maintained by the data system. 2. Security Reports The data system shall have the ability to generate security reports, which shall indicate all cashbox, door open and memory clear alarms. For each alarm, the time of day and the bus number shall be indicated. For the security door and cashbox alarms, the report shall also indicate the amount of revenue that was in the cashbox at the time the alarm was generated. 3. Editing Data It shall be possible to edit data in the data system in restricted ways. In order to preserve the security of the data system, only operator entries (route, run, driver and trip numbers) shall be changeable. 4. Transaction Log Page 31 of 61 16A 8 A transaction log shall be maintained in the data system computer. The transaction log shall maintain a record of all uses of passwords to access reports, the reports accessed, the time of log on and log off, etc. In particular, all editing of data in the system shall be recorded in the transaction log. The transaction log shall maintain this information for a minimum of 60 days. It is not to be subject to editing by users through any Contractor data system software. 6.3 Transactional Database and Reporting A. The farebox and data system shall be equipped with the software necessary to support a transactional database in which selected farebox transactions and /or events shall be individually time - stamped and recorded in farebox memory for uploading to the data system during routine Revenue Surviving activities pig. At the option of County, the transactional database shall be capable of recording: 1. Events only (e.g., farebox }i frevenue serviced, cashbox door open, route/ run record created) 2. Events and non -cash fare transactions 3. Events and both cash and non -cash fare transactions. B. The transactional database shall have the ability to capture the serial number of the card used in each transaction and report it to the data reporting system. It shall be possible to track all uses of a given card, category of card, or employer account for any time period, route, etc. This information may be used for audit and security purposes, especially where high -value cards or credit card acceptance is implemented. C. Each transaction shall be individually recorded in such a way that it is possible to determine day, time, route, run, latitude, longitude and stop ID for each fare paid. D. The transactional database shall be in a format that allows interfacing to the ODBC (Open Data Base Connectivity) standard, thereby making it possible to work with the database using ODBC - compliant third -party query and report generation tools. E. To maintain the security of the database, all database transactions shall be logged. Data shall be stored in a format that is not alterable by general database tools. The software driver for the ODBC interface shall be configured in read -only mode and shall not allow the user to modify revenue data directly. F. The transactional database shall be capable of storing the following types of transactions: 1. Cash fare; includes fare type (full fare or pushbutton), plus time (minutes and seconds), latitude, longitude 2. Period pass; includes serial number, time, latitude, longitude 3. Stored value card; fare deducted, remaining value, serial number, time, latitude, longitude 4. Stored ride card; remaining rides, serial number, time, latitude, longitude 5. Transfer accepted; Route, direction, serial number, time, latitude, longitude 6. Transfer issued; Key used to issue, time, latitude, longitude 7. Non - magnetic ticket or token processed; time, latitude, longitude 8. Credit & Debit Cards; latitude, longitude 9. 3rd party ID cards (e.g., a college ID card); latitude, longitude G. For period pass transactions, the database shall be capable of storing the following information at minimum: 1. Pass serial number 2. Pass type 3. Passenger category 4. Employer account number if applicable Page 32 of 61 16A 81 H. Other data fields shall be provided to permit recording of peak /off -peak usage. END OF SECTION VII SUPPORT SYSTEM EQUIPMENT 7.1 n,,,.t bl n.,t., Unit 4 PeI #a� _ ;ate llec-t da1a441om- farebo es and +, -ansf +t -data to the r -MR-S. ThP nnI j ;>. >�.nrr�: +.ze sa, ; d as that provided c . the + F +I e-syslemr When po, :,`,Fed_up the 12PU shall display a t --}Qe31 — Mowing s F„1 t,,.,_o +t, 5 �t.�t tie b z- �.i— rvs -o„ f;e�_,�,z- cr +ted too - elect !�1 „L +t_.. C._17.. � �'., �+; .. ith I`zti-& �����'I I I; 1 + e ane Elef�ttlt: — �'gir.��,.cc Prebe4a3 -ebex. ReuIew -lastdaLa. Use Drib ! I itiT44 Read far-ebox data. Fog off. Using the a , -;+„ methodology as the data +,• f +_lied. described above, zh nnr i shall + + f ?5)seconds ,I + the f t' - tl- r �vrrz-+-rc farvh P8- hard drive. A a default h time tl �ur,_Ivc_iiSct (selection "II" above). Reading the fafebox data without resAting or- deleting the sto}-ed fareb©r data (selection '4" above) shall " rd- The PPU shall cause the fai-e-10oX fe ine-111—f the 41011-rese4able 12DU counter to be incremented each ti"Ie the VDU is used to download the fairebox data. A similaF j-egister shall be PFOVidL-d tO the u..,Iaer of times that the PP i h been used to tread data f,.,,,,, fareb o An event recofc], whieh includes the ser f, ebb each time the VPU is used to dow floc I fa ebo data. A similar event .7 shall be time the PP 7 used to d ,I t f f b* b Revenue Processing Terminal A. A method for revenue tracking shall be furnished to provide County with the ability to track all revenues received and reconcile the registered revenues against the counted revenues on a vault basis. For this system, a terminal shall be provided in the Money Room supervisor's office interfaced to the FCMRS for transfer of the manually entered count data. B. The Money Room supervisor will sign on to the terminal to enter the count information. The date, vault location and vault number shall be entered into the terminal. The counts from the bill and coin counting equipment shall be entered into the record and the record shall be closed when all fields have been populated. C. Entry of the count information shall be via a form data entry interface, with the cursor automatically moving to the next field after a value has been entered into a field. When all fields are completed, the record shall be automatically closed and modifications to that record shall not be possible by a revenue operator. Page 33 of 61 16A 8 D. The counts for each denomination of bill and coin obtained from the counting equipment shall be entered via the terminal. Fields for manual counts of coins and bills shall be provided and data separately entered to account for money not processed in the counting equipment. This information shall be subsequently used to obtain the difference between the Money Room counts and the registered counts provided by the fareboxes, on a money reconciliation report. This information shall not be displayed to the revenue operator. E. An authorized County user shall be able to add the deposit information to this reconciliation record. The user shall enter the information from the bank deposit slip, and the day or days for which the deposit applies. The system shall calculate the difference in the revenue counted by the fareboxes and the deposited revenues shall be identified in a separate row on a reconciliation report. F. The terminal provided for the Money Room supervisor shall have no local intelligence or data storage capacity. All data shall be stored at the FCMRS. G. The FCMRS shall maintain records of the users who create, access, and modify all revenue reconciliation records. 7.32 Revenue Reporting Requirements A. A database of all data transferred from the fareboxes and the cashbox receivers to the FCMRS, and from the revenue processing terminal to the FCMRS shall be available to County for the production of reports. Menu driven report generation software with the same requirements and characterizes described for the fare collection system data reporting shall be provided to allow the user to design and store an unlimited number of report formats, which are to be used for generation of system reports. B. Every access to FCMRS application from County CAT workstations shall be tracked to be reported for security purposes. This report shall be sorted by FCMRS user (e.g., CAT workstation ID or FCMRS user ID) and shall include all manual activities, each remote terminal (node) and all downloading activities. The time and description of all access at computer shall be reported. All PDU activities shall be similarly reported. The Contractor shall submit all log messages for County for approval at CDR. County has the right to request addition, deletion or modification of any log message in order to meet system requirements. 7.34 Revenue Accounting System The fare collection system shall provide for the automatic reconciliation of registered revenues against counted revenues and provide a summary of the differences. This software shall operate as follows. A. Once the counts for both the coins and bills have been entered and stored for each vault, the FCMRS system software shall automatically compare the counts of the bills (by denomination) and coins (by denomination) and store data for the differences. B. At the end of a day (and also upon request) a reconciliation report showing the differences by vault shall be generated. This reconciliation report shall be provided only through the use of a high level password. The report shall also provide a daily total and summary for all vaults and an overall revenue accuracy figure. C. The FCMRS shall maintain an inventory of the following revenue elements: 1. Vaults and probes. 2. Cashboxes. D. The supervisor shall be able to enter the information on the bank deposit slips into the system in order to permit automatic reconciliation of the funds reported by the bank against those entered at the Money Room. This shall be accomplished through a high level function with a special password and user name. 1. A report shall be produced that provides details on the monies collected, counted and reconciled including all cashboxes emptied into a vault and all vaults counted. . Page 34 of 61 16A 8 j E. Summary totals of the registered revenues, by denomination, shall be included for each segment of the report. The level of detail to be provided for the report shall also be selectable by the user. F. The FCMRS shall provide the ability to report the contents of the receiver vaults at the end of the transit day. This report shall include the number and value of bills and coins in the receiver vault. END OF SECTION VIII. TESTING AND ACCEPTANCE 8.1 General A. The objective of the Test Program is to ensure that all equipment furnished under this Contract shall meet all of the applicable requirements specified in this document, including operation under environmental stress conditions. Testing and acceptance shall be conducted to satisfy production and delivery schedule requirements. The tests to be conducted shall be: 1. First Article Test (FAT) - One (1) of each item of equipment to be furnished, including on -board revenue collection and data collection, shall be tested to ensure that all the features and functions identified within these specifications are provided. Successful completion of this test shall be a prerequisite for the production and delivery of the full complement of equipment. 2. Production Acceptance Test (PAT) -The Contractor shall certify when production is completed in order to obtain County authorization for shipment of equipment. The Contractor shall certify that a functional test has been passed prior to shipping any item of equipment. County will identify, when necessary, required modifications to be made and demonstrated before approving release for shipment. 3. Pre - Installation Checkout (PIC) - Five (5) sets of on -board equipment, selected at random, shall be tested with sufficient transactions to verify proper transaction processing and data reporting. Successful completion of this test shall be a prerequisite for the installation of the equipment on- board the buses. In addition, one (1) item of each type of revenue and data collection equipment shall be tested in the same manner to ensure proper collection and reporting of funds. The Network Acceptance Test is considered to be part of the PIC. 4. Installation Acceptance Test (IAT) - Before any equipment is permitted to go into revenue service a functional test shall be performed by the Contractor on each item of equipment that is installed. Satisfactory performance shall be approved by County. 5. In- Service Qualification Test (ISQT) - This test shall run for a period of not less than four (4) weeks and shall verify that the system is operating in a reliable and accurate manner. This shall encompass all fare collection equipment installed at the garage plus the PDU, FCMRS units and the money room terminal. 6. Reliability, Maintainability and Accuracy Test (RMAT) - This test shall run for a period of not less than ninety -one (91) days and shall verify that the complete system is operating in a reliable and accurate manner for all installed equipment. Responsibilities for Testing are identified below: Article Test (FAT) Iuction Acceptance Test (PAT) Installation Checkout (PIC)* allation Acceptance Test (IAT) ervice Qualification Test USOT Contractor's Contractor's CAT Facility CAT Facility CAT Facilitv Page 35 of 61 Contractor/ CAT Contractor CAT Contractor CAT CAT Contractor 16A 8 Reliability, Maintainability & Accuracy CAT Facility CAT Contractor Test (RMAT) B. * Includes Network Acceptance Test C. The Contractor shall be responsible for preparation of all testing materials and the test script prior to the performance of any tests. These materials will be approved by CAT prior to commencement of the specified test. 8.2 Methodology A. The First Article Equipment shall be subjected to the First Article Test (FAT) at the factory. This test shall be comprised of the following series of tests: 1. Functional Tests 2. Maintainability Test 3. Interface Test 4. Cycling Test 5. Dust Test❖ 6. Environmental Tests 7. Vibration and Shock Tests :• 8. Radiated and Conducted Energy Test 9. Radiated Interference Test ❖ 10. Temperature / Humidity Test County may grant exemptions for items identified as ❖ above providing that the Proposer can provide details related to all such tests being successfully completed by a certified test laboratory and evidence of a minimum of 1,000 fareboxes in operation for at least two (2) years with more than two (2) transit systems that have a networked operation with a fare collection computer system in operation. B. At this level of testing the first articles shall be representative of the final production items. The purpose of this test shall be to demonstrate that for all items of equipment to be furnished under this Contract, the functions specified in this document will be met. C. Pre - installation Checkout (PIC) tests shall include tests to verify proper functioning and interfacing of the equipment before installation. The PIC tests shall be conducted prior to the ISQT and prior to the fleetwide installation. D. Upon start of fleetwide revenue service, the first seven (7) days shall be considered as the system start- up period prior to beginning the RMAT. The twenty -eight (28) day settling period shall be monitored for equipment performance during the RMAT. The RMAT shall be conducted for a period of 91 days. E. Final System Acceptance shall be a prerequisite for the start of the hardware and software Warranty. 8.3 Test Program Plan A. For all tests to be conducted, a final test plan shall be submitted for approval by County at least thirty (30) days prior to the start of the FAT. Testing shall not commence until the test plan has been approved. B. The test plan and applicable procedures which shall govern the conduct of activity, surveillance, direction and methods of observing and recording the pertinent data including handling of failures of equipment and inaccuracies of reports. C. The following elements shall be included in the test plan for each of the tests required in the project: Page 36 of 61 16A 8 1. Support, calibration instrumentation, test equipment and tools to be used 2. Technical publications to be referenced 3. Spares and consumables to be available 4. Maintenance facilities needed 5. Personnel requirements to be available for Contractor and County 6. Personnel scheduling 7. The report format and specific data to be collected during the test period together with the method used to report the test results 8. Preventive maintenance tasks (if any) to be performed during the test 9. Corrective action to be taken when failures and inaccuracies occur 8.4 Test Procedure Outline A. The test procedure shall include, as a minimum, the following requirements: Objective of test 1. Test environmental conditions 2. Detailed description of test specimens including drawings, part numbers, inspection and test records, maintenance records and calibration records 3. Detailed procedure of test 4. Test equipment to be used. Include any measuring equipment and /or any equipment aiding in the performance of the tests 5. The level and schedule of preventive maintenance during the test 6. Pass /Fail criteria 7. Retest procedure 8. Test script procedures for assessing Pass /Fail /Re -Test, including provisions for maintenance during tests. 9. Test notification 10. Test Reports B. The procedure to be followed for the resolution of test problems, failures, inaccuracies and general test conduct ground rules shall be defined 8.5 First Article Tests A. Functional Tests 1. The purpose of this test shall be to demonstrate that for each type of equipment the functions specified throughout this document, including all limiting conditions, shall be met. Each item of 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 (trouble shooting, and correcting faults) and service functions (extracting data) shall also be demonstrated. 2. The Contractor shall be responsible for developing a functional test procedure that satisfactorily demonstrates all equipment functions and shall submit this test procedure to County for approval at least thirty (30) days in advance of the test. 3. Each function specified shall be tested at least ten (10) times prior to confirming success or failure. Each piece of equipment shall have passed the functional test before the environmental tests listed below are started. Page 37 of 61 16A s B. Vibration (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. The Contractor shall ensure that for the bus fleets, vibration conditions expected in the area of installation are taken into account to ensure that proper isolation/ protection is built in the on -board equipment design. In addition, the following requirements shall be met. 2. The on -board equipment shall be tested per the procedure of MIL - STD -810D, Method 514.3, Category 8, with the following changes: a. Basic transportation, common carrier environment curves, Figures 514.3 -1, 514.3 -2 and 5 14.3 -3 shall be used with an overall RMS level of 1.5g for the vertical axis and 1 .Og for the transverse and longitudinal axes. b. The cycling time shall be two (2) hours on each axis for a total of six (6) hours. The on -board equipment shall operate normally during and after this acceleration test and the equipment shall not experience broken or loosened parts from this vibration. c. At the conclusion of each axis frequency sweep cycle, the on -board equipment shall be subjected to a vibration of 3g's at a frequency sweep between 7 and 14 Hz for a period of one (1) minute and 4 g's at a frequency sweep between 70 and 140 Hz for a period of one (1) minute. The equipment shall operate normally after these acceleration tests and shall not experience broken or loosened parts from this vibration. C. Shock (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. The on -board equipment shall be tested per Procedure I of MIL - STD -810D with the following changes: a. The half sine shock pulse shall have a peak value (A) of 5g and duration (D) of 20 milliseconds. b. The on -board equipment shall operate normally after the shock tests and shall not have experienced broken or loosened components as a consequence of these tests. D. Electromagnetic Effects (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. Susceptibility to Radiated Electromagnetic Energy - The on -board equipment and revenue collection equipment shall be tested for susceptibility to radiated electromagnetic energy per the requirements of MIL - STD -461C for radiated emissions, electric field. The equipment shall not sustain any permanent damage as a result of the exposure to these electromagnetic fields nor shall it lose its data in RAM storage. Loss of data relative to a farebox transaction during the exposure is considered tolerable though undesirable. 2. Susceptibility to Conducted Electromagnetic Energy - The on -board and revenue collection equipment shall be tested for susceptibility to conducted electromagnetic energy per the procedures of MIL -STD- 461C, Requirement CS06, utilizing the 400 volt, 5 microsecond pulse of both positive and negative polarity. The equipment shall not sustain any permanent damage as a result of application of the pulse energy nor shall it lose its data in RAM storage. E. Radiation of Electromagnetic Interference (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. The Contractor shall be responsible for compliance with applicable Federal Communication Commission regulations (i.e., FCC Rules, Part 15, and Subpart J) concerning conducted and radiated radio frequency energy. F. Temperature/ Humidity 1. The on -board equipment shall be allowed to stabilize for a period of two (2) hours at each of the given environmental condition settings. Thereafter, the number of fare payment cycles to be processed shall be as indicated below. Page 38 of 61 16A 8 Test No. 1 # of Cycles 125 Temp ('F) 32 Non 20-45% 2 125 110 97% 3 125 85 75% 4 125 65 95% 5 125 95 20-45% 6 125 95 99% 2. Specific conditions to be met for the on -board equipment shall be: a. Accuracy shall meet the following requirements: 1) Preventive maintenance shall not be permitted during the environmental tests. 2) Failures -During the conduct of this test, failures shall not exceed two (2) intermittent failures not requiring corrective maintenance. 3) Jams requiring release(s) necessitating opening the farebox shall not be permitted. Should any occur, the test shall be repeated. Revenue collection equipment shall be subject to temperature /humidity tests 2, 3, 5 and 6 as identified in the above table for twenty (20) cycles each. G. Maintainability Test In conjunction with the Functional Tests, the Contractor shall conduct a Maintainability Test of the equipment. The purpose of this test is to determine that the equipment tested conforms to the following maintainability requirements. This will be accomplished by introducing faults into the equipment and then measuring the time required for a technician to diagnose and correct the failure, from arriving at the device through returning the device back to service, and shall include swapping out the affected module. Mean Time To Repair (MTTR) MTTR (90% max) Chi -board Equipment 0.4 hour 0.9 hour Revenue Collection Vault System 1 hour 1.3 hours 2. At least thirty (30) days prior to the FAT, the Contractor shall submit to County a test outline which shall be prepared in accordance with the County approved maintainability test plan and shall show the basis of sample size selection and list of faults to be introduced into the equipment. This list shall represent every 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. County shall approve this list and the repair times prior to conducting the maintainability test. 3. The test shall be conducted in the following steps: a. The Contractor shall provide multiple units of the equipment to introduce failed components, incorrect adjustments and incorrect settings. The simulated failures shall be introduced in proportion to their expected failure rate. b. The Contractor's maintenance personnel shall be unaware of the simulated failures and shall be assigned to repair the equipment. c. The repair times shall be recorded and MTTR shall be compared with the advance list provided by the Contractor. All results will need to be approved by County. H. Interface Test Page 39 of 61 16A 8 1. The following equipment interfaces shall be evaluated for hardware, software, and data transmission. These tests shall be performed under ambient conditions and shall demonstrate all functions specified for the system. The interfaces are: a. Between the TPU and the farebox. b. Between the MSR and the farebox. c. Between on -board equipment and the revenue transfer and collection equipment. d. Between the revenue transfer and collection equipment and the FCMRS. e. Between the FCMRS and the County network. I. Design Qualification Waivers 1. The Contractor shall demonstrate that each component or subsystem of the fare collection system supplied meets or exceeds the specification requirements. Wherever a component or subsystem is substantially similar in design and application to equipment previously used in a similar application, the design may be qualified through submission of revenue service data. 2. If a component or subsystem in question is considered by County to be substantially identical in design to equipment previously deployed in other transit applications, design qualification tests on that equipment may not be necessary. Contractor shall provide a formal request for a Design Qualification Testing waiver for consideration by County for each applicable component or subsystem which shall include the following data as a minimum: a. List of the locations and quantities of current equipment installations, including duration of revenue service. b. Description of all relevant differences among the other installations and the requirements of this specification. c. Description of all differences between the currently installed equipment and the specified equipment. d. Test results of any relevant design qualification tests that have been conducted on this equipment. e. Reliability data for previously installed equipment, verifiable through purchasers. 3. Based on the submitted data, County will determine if the requirements for design qualification testing shall be waived. Specific requirements for each piece of equipment will be considered individually, and waivers will be issued on an individual basis. Waiver of design qualification for a component or subsystem shall not satisfy integrated testing of components. 4. The Contractor shall supply certification for those tests for which exemption is requested. This shall include actual test data documenting the appropriate tests performed on the on -board and revenue collection equipment to meet the requirements specified and having successfully operated the equipment on transit buses under revenue service conditions for at least six (6) months. The Contractor shall supply to County the name, address and phone number of all testing facilities and the person(s) involved in performing such testing. 5. The certificates shall be approved by County to exempt the Contractor from performing the tests. J. Cycling Test The cycling test shall be conducted for the on -board equipment as follows: 1. Cash Payments - a minimum of 500 coin only transactions and 500 bill only transactions for the payment of the base fare shall be performed. A minimum of 200 coin /bill transactions for payment of the full fare base fare shall be performed. A minimum of 1/2 of all transactions shall provide for the loading of a stored value card with credited amount for overpayment and a transfer. 2. Pass Usages - a minimum of 500 pass transactions for each activated pass type shall be performed. 3. Count Transactions - a minimum of 100 transactions shall be initiated for each of the tally buttons. Page 40 of 61 16A 8 4. On -board Pass Sale /Activation Transactions - a minimum of 100 transactions each for sale /activation of each type of pass (Day, Week, Month) purchased on -board shall be performed using cash (pass sale). 5. Transfer Transactions - a minimum of 100 transactions shall be initiated. 6. Pass Activations - a minimum of 50 transactions for the activation of a pre - purchased pass shall be performed using both full fare and reduced fare passes. 7. Stored Value and Stored Ride Transactions - a minimum of 100 transactions using magnetic stored value farecards and 100 transactions using magnetic stored ride farecards for the base fare, and 100 transactions using each for the reduced fare shall be performed. K. Dust Test 1. This test shall be performed to verify that the on -board fare collection equipment is capable of meeting the environmental requirements of these specifications as well as the following combination of conditions: a. High temperature b. High humidity c. Moderate winds d. Dust conditions 2. The Contractor shall prepare a test procedure, for review and approval by County not less than thirty (30) days prior to the commencement of the environmental test. This dust test shall include varying lengths of exposure by the on -board equipment, from one (1) minute to one (1) hour in fifteen (15) minute intervals. 8.6 Pre - Installation Checkout A. Upon successful completion of the FAT, County or its consultant will issue a production release to the Contractor to deliver all equipment specified. Prior to installation, a Pre - Installation Checkout (PIC) Test shall be conducted. CAT or its consultant will select five (5) on -board assemblies at random from delivered items plus the FCMRS, including software to run all reports; and Data Probe (or wireless equipment), as supplied, with associated hardware. The PIC test shall take place at the County facility. B. The test objectives are: 1. To confirm that there was no visible damage in the delivered equipment. 2. To visually inspect a random sample of on -board equipment for conformance with specifications. 3. To verify that the on -board equipment works as expected by checking the bus operator sign -on /sign- off function and to verify other operating functions by processing various fares. 4. To ensure that all data reports are produced in accordance with specifications. 5. To determine by these procedures if installation can begin or corrections and /or adjustments are needed followed by a retest before installation can begin. C. This equipment shall be set up at the County CAT facility by the Contractor in such a manner as to permit all of the above listed test objectives to be evaluated. The following sequence of tests shall be conducted as a minimum: 1. The on -board equipment shall be powered using a power supply furnished by the Contractor. 2. The on -board equipment shall be programmed for bus number and correct fare tables and related information downloaded from the FCMRS. 3. Visual inspection of the on -board equipment shall be made to ensure that there is no physical damage and that all specified displays, messages and prompting sequences including tone coordination occur as specified. Page 41 of 61 16A 8 Ii. 4. Sign -on procedures shall be completed followed by processing at least ten (10) fares of each type. 5. Cashboxes shall be vaulted at least twice per farebox tested. Sign -off procedure and data collection shall be completed and FCMRS printouts reviewed. 8.7 Network Interface Test A. As part of the PIC, the system shall be provided with test data simulating the County database for purposes of this test. Throughout this test, the date and time shall be modified a minimum of ten (10) times incorporating dates from a minimum of five (5) different years. B. All interface connections shall be inspected for proper installation. All functions requiring interface to the FCMRS, including all alarm and boundary conditions and security provisions, in all possible combinations, shall be tested. These functions shall include, but not be limited to, the following: 1. Alarm transmission and all other device/ component monitoring functions 2. Data transmission to the FCMRS 3. Data transmission from the FCMRS 4. Fare Table modification, download and verification 5. Automatic report generation at the FCMRS C. The Contractor shall identify each integrated function in its Test Procedures, including the boundary conditions and security provisions for each item of equipment and operation. D. All data transmissions shall be inspected and tested for accuracy. Inaccurate data transmissions shall be recorded as a failure. The Contractor shall take any corrective action necessary to ensure the proper performance of all functions. E. Samples of all reports available shall be generated by the FCMRS. Format, layout, page and column headers, data and all other information shall be reviewed to confirm compliance with the designs approved at the Final Design Review. Contents of the reports shall be compared with the known contents of the data. Successful completion of the test requires no discrepancies between report contents and known data as well as proper formats. 8.8 In- Service Qualification Test A. On successful completion of the PIC, County will issue a release for the Contractor to install equipment. After approval of the IAT results, the ISQT will begin. The Contractor shall supply adequate spare modules, assemblies, parts and consumables to be used throughout the ISQT. B. Object And Conditions Of The ISQT 1. The purpose of this test shall be to operate the equipment listed above in revenue service for a period of four (4) weeks. This test shall be conducted with buses operating on their designated routes in revenue service. 2. The first seven (7) days shall be designated as a settling period, but with all normal operations for revenue service being carried out and accuracy and reliability data being documented. Prior to this period a Failure Review Board (FRB) shall be set up. The FRB will ascertain what constitutes a failure and what the satisfactory corrective actions will be to prevent recurrence when the ISQT begins. Failures shall be established in conformance with guidelines specified. At the end of the settling period, the ISQT shall begin and shall be conducted over the next twenty-one (21) days. 3. The Contractor shall be responsible for performing all maintenance actions during ISQT C. Test Requirements 1. The equipment shall be operated in full revenue service. The measures to determine acceptance of equipment shall be the Accuracy Test and the Reliability Test. Page 42 of 61 16A 8 D. Accuracy Test 1. This test shall be conducted with all the ISQT on -board equipment. This on -board equipment shall be monitored daily during the ISQT 2. The minimum accuracy requirements stated above shall be achieved during the conduct of the test in order to continue the ISQT. If the accuracy requirements specified are not met at the periods indicated, County will have the right to suspend the ISQT until changes are made to achieve this accuracy. Data handling, data storage and the production of printed data on all reports shall be without error for the duration of the ISQT. Over and under amounts will be added algebraically to determine overall accuracy. 3. In addition to the verification of the accuracy of the collected revenues, a data accuracy review shall be performed. This data accuracy shall serve to ensure that all data are reported properly and accurately, that information is consistent between reports, that all column and row totals are properly calculated and that all alarms and messages sensed are recorded and reported. A complete batch of all reports shall be printed on five (5) random days, as selected by County during the ISQT, for this purpose. E. Reliability Test 1. For on -board equipment (including probes) - This test shall be conducted with all the ISQT on -board equipment. They shall be monitored for report of any failures. All conditions of equipment errors, repairs, adjustments, replacements, malfunctions of on -board equipment (including parts /modules thereof) shall be fully documented for the entire test period. The minimum reliability requirements stated above shall be achieved during the conduct of the test in order to continue the ISQT. If the MCBF requirements specified are not met at the period indicated, County will have the right to suspend the ISQT until changes are made to achieve this reliability. 2. For the duration of the ISQT there shall be no more than one (1) failure of the FCMRS, data probe, revenue collection equipment or interface to the County network. F. Pass /Fail Criteria 1. Requirements specified for both the Accuracy Test and the Reliability Test shall be met in order to pass the ISQT. When the ISQT is passed, the equipment shall remain in revenue service. The ISQT test results and data collected shall be reviewed weekly by County. G. Failure of ISQT 1. In the event that the equipment fails the ISQT the Contractor shall have up to ninety (90) days to correct or update the equipment and retest until a pass category is reached. The Contractor shall maintain a qualified representative responsible for making adjustments and repair of equipment at the depot where the ISQT is being performed. Failure to pass the ISQT after this additional ninety (90) days shall be cause for termination for Default as defined in the Contract Conditions. Page 43 of 61 16A B 8.9 Reliability, Maintainability and Accuracy Test A. The RMAT will begin after a seven (7)-day transition period at the successful conclusion of all equipment installations and shall be conducted over a period of ninety -one (91) days. The first twenty -eight (28) days are a settling period during which records will be kept, but performance will only be measured and verified during the final sixty -three (63) days. The Contractor shall be responsible for maintenance during RMAT. B. During the RMAT, reliability, maintainability and accuracy will be recorded by Contractor personnel and reviewed by County at the fourth (4th), eighth (8th) and thirteenth (131h) week stages to evaluate the performance for the preceding period. RMAT test results and data collected shall be reviewed weekly with County. Reliability, maintainability and accuracy at each stage shall meet the performance requirements specified. 8.10 Final System Acceptance A. Final system acceptance of the fare collection system by County shall be contingent upon passing the RMAT and the Contractor furnishing all required hardware, software, spare parts, documentation, training, supplies and all other items identified in these specifications. B. The warranty of the system shall commence upon final acceptance of the fare collection system and shall continue for a one (1) year period. 8.11 Test Performance Requirements A. General Requirements 1. The equipment shall be operated in full revenue service. The measures to determine acceptance of equipment shall be the Reliability Test and the Accuracy Test as follows: 2. The procedures described below shall start on day 1 of revenue service and shall be continued during the RMAT period. B. Sampling Method for Accuracy Test 1. The accuracy test shall be based on performance related to on -board equipment using a ten (10) cashbox sample. This sample shall be comprised of a control group which would be the same five (5) on -board pieces of equipment every day. The balance shall be audited on a predetermined schedule developed by County. 2. On -board equipment will be excluded from the daily audit sample if it was reported to have any malfunction or failure in terms of its mechanical or electronic operating functions, which could have corrupted its data. C. Accuracy Requirements 1. The RMAT accuracy trend specified shall be achieved during the conduct of the RMAT. If the accuracy requirements specified are not met at the periods indicated, County will have the right to interrupt the RMAT until changes are made to achieve this accuracy. Data handling, data storage and the production of all reports shall be in accordance with requirements specified. 2. During the RMAT, accuracy shall be monitored with reviews at the (4th), eighth (8th) and thirteenth (13th) week stages to evaluate the performance for the preceding period. Accuracy at each stage and Page 44 of 61 16A 8 cumulative to date accuracy performance shall also be evaluated and shall meet the requirements specified. D. Method for Calculating Accuracy The accuracy of the on -board equipment shall be calculated as for the ISQT. E. Reliability Test 1. All conditions of equipment errors, adjustments, replacements, malfunctions and failures shall be fully documented by the Contractor for the entire test period for the RMAT. 2. The following procedures shall be used to log chargeable failures associated with RMAT. The Failure Review Board (FRB) shall ascertain what constitutes a failure in the event of a disagreement. a. Operating Malfunctions An operating malfunction is defined as a random malfunction that does not cause the equipment to be inoperable but would require some form of maintenance to be rendered, such as a blown bulb. b. Operating Failures An operating failure is defined as any condition that causes the equipment to cease working (e.g., logic board failure). An operating malfunction becomes an operating failure when the same malfunction occurs on three (3) different pieces of on -board equipment. An example is a bus operator display burning out in three (3) different pieces of on -board equipment. b. Item Failures An item failure is defined as an operating failure of a particular module which occurs three (3) or more times. For example: if the bill transport in farebox #123 shows three (3) operating failures this would be logged as one (1) item failure. c. Design Failures A design failure is defined as a failure of a given type of module in ten percent (10 %) of the modules provided. An example is if there are 20 fareboxes in use and two (2) different farebox bill transports are each charged with an item failure, this constitutes a design failure. 3. Customer induced malfunctions are non - chargeable. 4. A daily maintenance diary shall be kept which records all malfunctions and failures by type. Malfunctions and failures shall be recorded by major module classification. 5. An equipment maintenance report shall be prepared to record all maintenance related incidents and the determination of chargeability. 6. If a design failure occurs, continuation of the test is at the discretion of County. F. Failure of RMAT 1. In the event that the equipment fails the RMAT the Contractor shall have up to twenty-eight (28) days to correct or update the equipment and retest for a minimum of twenty-eight (28) additional days until a pass category is reached. 2. In the event of a retest, the Contractor shall be required to maintain, on a full time basis for the entire repeated RMAT period, a qualified representative responsible at the test location for making all adjustments and to repair all equipment at the expense of the Contractor. 3. Failure to pass the RMAT after this additional twenty-eight (28) days shall be cause for Termination for Default. G. Failure Category Definition The following conditions shall be used as a guide to classify failures. 1. Relevant Failures: Page 45 of 61 16A 8 a. A relevant failure is any malfunction which prevents fare collection equipment from performing its designated function, or meeting its performance criteria, when used and operated under the environmental and operational conditions stated in these specifications. Example: If a farebox fails to boot up into operation, it is a relevant failure. But if it is determined that the bus battery had no charge, it will not be a chargeable failure. b. All relevant failures shall be chargeable failures when attributable to one (1) or more of the following reasons: 1) Equipment design 2) Equipment manufacture 3) Equipment quality 4) Parts design 5) Parts manufacture 6) Parts quality 7) Software errors (If software errors are corrected and verified for twenty -eight (28) days in revenue service during the tests, such errors shall not be chargeable as equipment failures.) 8) Equipment installation. 9) Contractor furnished operating, maintenance or repair procedures, tools and equipment that cause equipment failure. (If procedures are correct and verified, such failures shall be chargeable as equipment failures.) 2. Non - Relevant Failures a. A non - relevant failure is a malfunction caused by a condition external to the equipment under test, which is neither a functional, environmental, nor a test requirement in this specification and is not expected to be encountered during normal and correct operation of the equipment in revenue service. b. Non - relevant failures shall be considered non - chargeable failures and shall include the following: 1) Accident or mishandling. 2) Failure of test facility or test instrumentation. 3) Equipment failures caused by externally applied over stress conditions in excess of the approved specifications requirements contained herein. Certain customer induced failures such as use of torn or mutilated fare media and abuse of equipment. 4) Normal operating adjustments not as prescribed in the approved equipment operating and maintenance manuals. 5) Dependent failure(s) occurring with the independent failure that caused them. 6) Failures of expendable items having a specified life expectancy when operated beyond the defined replacement time of the item. 7) Failures caused by incorrect operating, maintenance or repair procedures. C. If incorrect procedures are employed it is not a chargeable failure. H. Failure Review Board (FRB) 1. During the first seven (7) days of the ISQT a Failure Review Board (FRB) shall be established. The FRB will include two (2) members representing County and one (1) member representing the Contractor. 2. The FRB will ascertain what constitutes a failure and what the satisfactory corrective actions will be to prevent recurrence when the RMAT is run. Page 46 of 61 16A 8 3. Failures shall be established in conformance with guidelines. The end of the ISQT and first twenty - eight (28) day period of the RMAT the FRB shall review all data from each test and finalize plans for continuing. 4. The RMAT data will be reviewed and approved by the Failure Review Board before it will become official. The FRB shall agree on the procedures to resolve issues related to "Fleet Defects ". This applies to any hardware or software conditions that result in an unacceptable performance and that this occurs in more than twenty percent (20 %) of the fleet. I. Data Verification 1. During each of the acceptance test periods, the data transferred from the farebox to the FCMRS will be verified by County. This shall include the verification of all connectivity aspects associated with transfer of data, production of reports and operation alerts and alarms. 2. Each day a specific farebox will be selected and the detail data will be printed. This data will be verified against the data transferred to County departments to verify that it has been transferred properly. In addition, all transactional data for that farebox will be verified against the summary data compiled and reported. 3. The periodic reports (daily summary, weekly summary, monthly summary and annual summary) will be printed each day to verify that the totals are being accumulated properly. On a random basis verification of alarms and events will be verified. 4. None of these tests shall fail. All data shall be transferred and properly available for review and manipulation by the County network. J. Corrective Action If the Reliability, Maintainability and Accuracy requirements specified are not attained during the RMAT, the Contractor shall be responsible to redesign, provide retrofit kits and furnish labor to correct and /or change the equipment at no additional cost to County. The corrective action and /or the resolution of the problem(s) shall be subject to approval by County. END OF SECTION IX. TRAINING 9.1 General Training Requirements and Plan A. The Contractor shall be responsible to train County designated personnel according to the requirements specified herein. Training shall include course development, providing instructors, supplying handouts, manuals, classroom aids, etc. Practical training on equipment shall occupy a significant portion of all training classes. The training presentations and material shall be in English. B. Instruction shall be designed to include courses described below and shall cover equipment familiarization and systems operations. The training shall be provided to bring those employees designated to the level of proficiency required for performing their respective duties. Formal training shall include both classroom and practical work, and shall be augmented by informal follow -ups as needed. C. The Contractor shall provide experienced and qualified instructors to conduct all training sessions at County designated training facilities. The Contractor is responsible for insuring that the instructors teaching these training courses are not only familiar with technical information, but are able to utilize proper methods of instruction, training aids, audiovisuals and other materials to provide for effective training. D. The Contractor is responsible for providing all training aids, audiovisual equipment and visual aids for the conduct of these courses. At least one (1) session of each different training course shall be recorded on DVD by the Contractor. E. All training materials are to become the property of County at the conclusion of training. Page 47 of 61 16A 8 a F. Initial sessions shall be provided for maintenance and operations training not less than thirty (30) days prior to the commencement of installation of any portion of the system. Final maintenance technician training shall commence during the time period when equipment is installed on the buses, prior to revenue service of the system. G. At the request of County, the Contractor shall, during the warranty period, provide three (3) additional refresher training sessions of any of the courses provided under this contract. These refresher training sessions shall be held in Naples, FL during the warranty period at no additional cost. H. At the request of County, the Contractor shall, during and up to 60 days after implementation, provide equipment to demonstrate and train the public on the use of electronic fareboxes. These training sessions shall be held in Naples, FL in locations, dates and times selected by County no additional cost. 9.2 Submittal and Approval Requirements A. Submittal 1. The Contractor shall submit the training curricula and materials for review and approval by County. No training shall occur until training materials have been approved by County. The curricula shall meet all training requirements and indicate course content, training time requirements, and who should attend. Training curricula shall be provided for County review sixty (60) days prior to commencement of equipment installation. 2. Should this material include information as provided in the system documentation and manuals, any updates to that documentation which affect the training materials shall be updated in the training materials as well. B. Required Curricula and Materials The following curricula and materials related to training shall be provided subject to approval by the County. 1. Instruction Material: The primary source of instructional material shall be the applicable equipment operating and maintenance manuals. In addition, the Contractor shall develop, for each course specified, notebooks containing such additional drawings, descriptive information and procedures necessary to ensure that all learning objectives are met in an orderly and timely manner. 2. Student Guides: All students shall be furnished with a guide containing material which mirrors information in the instructor guides and provides the information necessary to effectively train the students. 3. Instructional Equipment and Training Aids: Training shall be conducted using fare collection equipment in normal operating condition. In the event such equipment has been accepted by County, the equipment will be made available to the Contractor for training purposes. 4. Training Schedule: Training classes shall be prescheduled at least thirty (30) days in advance and in coordination with County. Classes will be conducted at facilities provided by County. 5. Training Materials: a. Course materials, including notebooks, instructor manuals, and handbooks will become the property of the students and instructors, as appropriate, at the conclusion of the training course. b. At the completion of all training courses one (1) set of camera - ready, letter quality reproducible documents or computer files for each course outline, lesson plans, training aids and notebooks shall be provided to the County. 9.3 Bus Operator Training A. The Contractor shall provide an instructor who is experienced and qualified in the operation of the fare collection equipment. One (1) portable standalone fare collection equipment training units with a 110 volt AC power supply shall be supplied for the training. The standalone training units will become the property of County at the conclusion of training. Page 48 of 61 16A a B. The purpose of this training is to instruct County CAT bus operator instructors who in turn can train bus operators in the operation of the equipment. C. At the completion of training, County CAT instructors will demonstrate competency in the operation of the equipment by taking and passing a performance test and written examination. D. This course shall be designed to provide management, supervisory and operating personnel with a functional understanding of all of the fare collection equipment. The functions of each module shall be covered, including the interrelationship of the equipment with the customer. Personnel attending this course, in addition to bus operators and transit supervisors, will include the following categories: management (at the overview level), marketing, public relations; and operating, financial and other administrative personnel. E. The instructor classes shall conclude four (4) weeks prior to the start of the ISQT in order to allow for the training of bus operators. 9.4 Revenue Service Training The Contractor shall provide an experienced and qualified instructor who shall conduct training classes for the complete revenue collection /revenue service operation. 9.5 Data Management and Reporting System Training (Documentation Only) 1. The following shall be included in the FCMRS documentation: a. External interfaces. b. Development assumptions. C. Processing scripts. d. Data dictionaries. System flows. 2. Data diagrams shall be provided to County. All programs shall be defined and described fully, showing all inputs /outputs, samples of reports, logic flows and major functions described, as well as assumptions used during program development. Detailed system functional requirements shall also be provided. 3. Explanation of the software instructions and methods employed to make changes in software programs shall also be taught. Use of software documentation shall also be fully covered. 9.6 Data Management and Reporting System User Training A. The Contractor shall provide an experienced and qualified instructor who shall conduct user orientation training for FCMRS users, including staff who will be responsible for the generation of system reports and queries. B. The purpose of this class will be to provide basic training and to describe to personnel the data structure, program logic and data transmission operation functions and how the software in the FCMRS can be used to perform data sorts and selective data reporting, file retrieval from back up files, and how other programmable functions are achieved. C. The goal of the training shall be to make the participants competent to both operate and teach others the proper operation of the report generation system. D. This course shall include the use of simulated or actual data provided by the Contractor. This data shall include sufficient information to cover multiple months and shall include events and transaction data from all types of equipment furnished. Page 49 of 61 16A 84 9.7 Equipment Maintenance Training A. The Contractor shall provide an instructor who is experienced and qualified in the maintenance of the fare collection equipment. B. The purpose of this training is to instruct technicians in the maintenance of fareboxes, the RCVS and all related equipment that County technicians will be maintaining. C. Fare collection equipment shall be provided for the training sessions. D. At the completion of training, technicians will demonstrate competency in the maintenance of the equipment as indicated by taking and passing troubleshooting and repair tests and written examinations. E. This maintenance training information shall include troubleshooting and diagnostics of all known problems for all types of fare collection equipment furnished. 9.8 Additional Training A. In addition to the training as specified above, small sessions with 1 -3 County staff members shall also be provided as described below 1. Security Training - Individuals shall be trained in the understanding of all security components and interlocks within the system, including fareboxes, cashbox receivers, revenue collection vaults and associated software. It is anticipated that this effort shall require four (4) to six (6) hours of training during a one (1) day period. 2. Administrative Training - Selected individuals shall be trained in the overall understanding of the fare collection system basics. It is anticipated that this effort shall require four (4) to six (6) hours of training during a one (1) day period. 3. Planning Training - Individuals shall be trained in the understanding of the origin and meaning of all system data and how to manipulate the data to provide needed reports and information. It is anticipated that this effort shall require six (6) to eight (8) hours of training during a one (1) day period. 4. Revenue Tracking System Training - Individuals shall be trained in the operation and understanding of the revenue tracking system, including the meaning of all system data and understanding reconciliation reports as well as all cashbox movements. It is anticipated that this effort shall require four (4) to six (6) hours of training during a one (1) day period. 9.9 Bus Operator Training Video A. At the end of the training, the Contractor shall provide County with five (5) copies of a video recording in DVD format that contains the training that would normally be provided by an experienced trainer showing complete operation of the farebox from the perspective of a bus operator. B. This video recording shall include all procedures required by the system at the start of, during, and at the end of revenue service. The video shall highlight customer displays, bus operator displays, button presses, farebox indicators and farebox actions (card issue /return, etc.) as well as customer service features of the farebox such as the MSR, TPU, coin and bill validation, etc. C. The video recording shall be updated within thirty (30) days after the final acceptance of the system to accommodate any operational changes. D. The video recording shall be approximately ten (10) to fifteen (15) minutes in length; and presented in an edited and professional format including a sound track, introduction, appropriate graphics and other features E. Actual training sessions and recordings from other transit properties may be used for some aspects of this video recording, but County shall have final approval of contents and quality. END OF SECTION Page 50 of 61 16A a4 X. DOCUMENTATION 10.1 General Requirements A. All documentation shall be in English, using US measurements and be submitted directly to County. Any documentation submitted through a third party will not be considered received. All documentation shall be provided in hard copy and electronic formats similar to those used for Microsoft products. B. Preliminary drafts of all manuals shall be supplied ninety (90) days before installation begins at the first depot. The documents shall be as complete and as comprehensive as possible. Ten (10) sets of each type of preliminary draft document, manual and drawing as described in this section shall be provided by the Contractor. These documents will be reviewed and comments furnished to the Contractor within thirty (30) calendar days of their receipt. C. Complete final manuals in the quantities and quality as described in this section shall be supplied no less than five (5) days prior to the commencement of the first depot installation. D. Post warranty manuals shall be provided at the successful completion of the initial warranty period. These shall be of the latest revision and shall have incorporated all modifications or changes made to any part of the fare collection system covered under this specification. The documents shall not be considered final without the approval of County. Post warranty manuals may be submitted for approval up to sixty (60) days prior to initial warranty expiration. E. The warranty period shall not end until complete and final post warranty documents as specified herein have been furnished by the Contractor and approved by County. F. The Contractor shall provide a list of all special or custom tools or instruments required to maintain or adjust any component within the Fare Collection System. G. Diagrams and drawings shall identify each and every component in the Fare Collection System and call out each component with the unique part number as referenced in the Bill -of- Materials. H. The Contractor shall provide a parts layout for every printed circuit board, specifically calling out each component, be it mechanical or electrical in nature, and showing its exact location. I. The Contractor shall provide drawings showing the location of all of the traces on the top and bottom and any through board connections of each printed circuit board. These drawings shall be laminated and suitable for use during shop repair of components. J. Each type of maintenance manual shall contain, but not be limited to: a description of operation; installation procedures; a complete parts identification diagram and list, troubleshooting procedures; inspection procedures; preventive maintenance procedures and program; repair procedures; diagnostic procedures; wiring diagrams; electrical schematics with board and cable identification; and adjustment procedures. K. Subcontractor's names and part numbers shall be cross referenced with the Contractor's part numbers for the required parts lists. L. Electrical and electronic drawings shall be supplied to show engineering changes made to any component or module up to the end of the warranty period of the Fare Collection System supplied. M. The manuals shall be complete, accurate, up -to -date, and shall contain only that information which pertains to the system installed and shall be written in English only. 10.2 System Documentation Requirements A. Manuals required shall include the following parts, as applicable: 1. System Characteristics a. A physical description of the subsystem and pertinent technical characteristics. Page 51 of 61 16A 81 b. A description of the functions that the subsystem is designed to perform and the general methods employed to accomplish those functions. 2. Principles of Operation (for maintenance manuals) a. Detailed discussion of the theory of operation. b. Interface between subsystem elements. c. Signal flow sequence correlated to block diagram(s). 3. Operating Procedures a. Turn-on and turn -off procedures. b. Detailed bus operator instructions sufficient to operate the equipment in each mode of operation. C. Emergency operating procedures. 4. Maintenance Procedures (for maintenance manuals) a. Preventive maintenance procedures, schedules and manufacturer's recommended products. b. Fault isolation and analysis procedures. C. Corrective maintenance and repair procedures. d. System calibration and test procedures. e. Illustrated parts catalog. B. A document control method shall be proposed by the Contractor and approved by County. C. The Contractor shall submit to County for approval a Table of Contents and sample formats for each type of manual and for the Illustrated Parts Manual. 10.3 Security Manual A. To the greatest extent feasible, the Contractor shall not, in any of the following documentation, include items related to the specific operations of, or maintenance of, security devices which may be used for fraudulent purposes. B. Information of this type, shall be identified and submitted separately, stamped CONFIDENTIAL. It shall be the Contractor's responsibility to meet with the County Project Manager to determine what information shall be considered confidential. C. County regards the documentation of certain software programs and certain aspects of maintenance to be security related. Also considered as security related are revenue collection and revenue transfer information; revenue equipment construction and locking information; and other similar elements. 10.4 Bus Operator Manual A. The manual shall contain succinct instructions on how to operate each on -board item of fare collection equipment. Pictograms and photos are encouraged. Fault procedures need to be described as well as directions for dealing with customer service issues related to equipment operation. B. The manual shall contain all information needed for safe, proper, and efficient operation of the on- board equipment. All normal operational sequences shall be described in detail. C. The manual shall be printed on plastic coated paper, or the equivalent, for durability and be no larger than 3 -1/4 inches wide by 6 inches long by 1/4 inch thick Page 52 of 61 16A 8 10.5 Revenue Collection Manual The revenue collection manual shall include a complete description of the operation of all revenue collection equipment, including cashboxes, receivers, and receiver vaults, necessary to operate the revenue collection system. 10.6 Maintenance Manuals A. The Contractor shall provide a manual covering each item of fare collection equipment furnished, including exercised options, with drawings which identify the various parts and assemblies in the equipment. The materials provided shall contain, but not be limited to: a description of operation; installation procedures; preventive maintenance procedures and program; repair procedures; diagnostic procedures; wire diagrams; electrical schematics with board and cable identification; and adjustment procedures. B. The manuals shall identify any special tools required for any of the procedures. C. Durable materials shall be used to provide extended life for these manuals in the maintenance shop environment. D. An electronic copy of all manuals, in Adobe PDF or other form approved by County, shall be provided on four (4) sets of CD -ROMs as well as one (1) printed master copy on 8 -1/2 x 11 inch paper. E. Manual Contents shall be as specified herein and shall be consistent with training. 1. Preventive Maintenance Section: shall contain all information needed to enable maintenance technicians to perform all periodic inspection and preventive maintenance tasks including lubrication, inspection and replacement of consumable items. The manual shall contain recommended PM schedules. 2. Troubleshooting and Corrective Maintenance Section: shall contain all information needed to diagnose problems and make adjustments and repairs to all Fare Collection System components and sub - assemblies to restore the system to a normal operational condition in an efficient and timely manner. The manual shall include at a minimum a general description of each subsystem, component and subassembly; functional block diagrams; detailed schematics; troubleshooting flow charts and wiring diagrams. 3. Shop Repair Section: shall contain detailed descriptions of each assembly and subassembly sufficient to service, maintain, repair, replace, rebuild, and overhaul the equipment. Systematic procedures, wear and tolerance limits for determining when overhauls are needed; overhaul procedures; and special tools and equipment required shall be included. 4. Illustrated Parts Section: shall describe and identify each module, sub - assembly and part within each piece of equipment with its related supplier identification number and Contractor identification number. Exploded drawings shall be provided to permit identification of all parts not readily identified by description. 10.7 Test Equipment Manual The Contractor shall provide manuals for each type of test equipment furnished. Manuals shall include all information necessary to allow proper and full use of all test and calibration equipment furnished. 10.8 Fare Collection Management and Reporting System Manual A. The Contractor shall provide a Fare Collection Management and Reporting System Manual, to include drawings which identify the various parts and assemblies of the system. The manuals shall contain start -up procedures, operating modes, interconnection diagrams, preventive maintenance procedures and program; diagnostic procedures and wiring diagrams with board and cable identification. B. Equipment Manuals shall be provided for the hardware and components used to configure the system. The manuals shall include those instructions and maintenance manuals furnished by the supplier of Page 53 of 61 each type of processor, keyboard, modem, fixed disk drives, other backup system, uninterruptible power supply, and other components. shall be complete and detailed. It shall be the Contractor's respo information from the respective manufacturers. C. Software Manual and Program Documentation 16 A g �' storage media, monitor, printer, The content of this information risibility to acquire the required 1. The Contractor shall provide complete documentation for each Contractor developed and furnished computer software program for the FCMRS, including the money room terminal and any other subsystems using a microprocessor or other computer. 2. The software documents shall be furnished for review and approval by County prior to installation by County of the equipment on County property. The original and each amended version of a software program shall require new copies of the documentation to be furnished for review and approval by County prior to installation by County. The software documentation shall not be distributed beyond the authorized personnel. 3. The documentation for each version of each program shall be complete and comprehensive to include, but not be limited to: complete source code listings with fully documented statements; comprehensive flow charts; and block diagrams explaining the system as a whole and showing how the individual programs are interrelated. 4. The software documents shall clearly identify what data elements are stored; the source of each data element; and how data is structured, transferred and utilized. This shall include the software logic, processing rules, restrictions and exceptions, default conditions, hard and soft wired parameters and the overall process by which each of the reports specified is generated. 5. Software manuals from suppliers of third party software components included as part of the system shall be provided as a part of this program documentation. END OF SECTION XI. SPARE MODULES, SPARE PARTS AND CONSUMABLES 11.1 Spare Modules and Parts A. Spare modules and parts shall be furnished in accordance with the listing furnished with the Price Proposal Form. B. Spare modules and parts should be new and manufactured to the specifications of the original parts in the delivered fareboxes and completely interchangeable. C. A list of vendors providing spare parts and consumables should be provided by the Contractor to County within sixty (60) days after NTP. D. The spare modules and parts shall be manufactured concurrently with production of modules and parts for delivered equipment. The Contractor shall prepare and submit to County a spare modules and parts list detailing the part number and description of each module and part that is to be furnished. 11.2 Spare Parts List Contents A. A comprehensive list of spare modules and parts for all equipment shall be provided to County within sixty (60) days after NTP. This listing shall include all items that can fail or that require replacement due to wear over a ten (10) year period. B. In addition, the Contractor shall provide at County's request at any time the equipment is being used in revenue service, a complete parts and modules list, together with prices, parts numbers and descriptions for all modules, parts and parts within the modules for all equipment furnished by the Contractor. Page 54 of 61 16A B 11.3 Consumables A. Contractor shall provide all consumables necessary to operate the system, or any particular system component that has been installed based upon projected ridership levels provided by County, for a one (1) year period of operation. B. A comprehensive list of system consumables shall be provided to County within sixty (60) days after NTP. C. The Contractor shall provide the consumables upon the installation of the equipment. Should the In- Service Qualification Test (ISQT) not be passed initially, the Contractor shall note the level of consumables and replace any consumables utilized from that point until the ISQT has been passed successfully. This procedure shall apply for all revenue service acceptance tests. 11.4 Support Equipment The Contractor shall provide the testing, service and other special tools and equipment required for proper operation and maintenance of the system as a part of the initial equipment delivery. 11.5 Future Supply Provisions A. For twelve (12) years after Final System Acceptance, the Contractor shall make available, for delivery within sixty (60) days, all Contractor designed equipment, modules and parts as are or may be necessary to service and maintain the equipment delivered to County. B. Alternately, during the twelve (12) year period, the Contractor shall ensure that County can obtain the equipment, modules and parts from other suppliers for a comparable price (generally within ten percent (10 %) of the part or module price on the Contractor's most recent price list). The Contractor shall also offer County the opportunity of ordering the equipment, modules and parts at least six (6) months before discontinuing their production.- It shall be the Contractor's responsibility to alert the County of this situation and to provide to the County's applicable drawings, parts lists and at least two (2) sources for obtaining parts that were previously supplied by the Contractor. C. As an alternative, the Contractor may upgrade or retrofit all of the Contractor supplied equipment to use modules and parts that are readily available from the Contractor or other suppliers at a comparable price to meet the requirements of this subsection. The entire cost of any such upgrade or retrofit shall be at the Contractor's expense. D. The Contractor shall also notify County in a timely manner when improvements or modifications to parts or modules are fabricated that could improve the operation of County's system. E. In the event that the Contractor cannot furnish any system equipment, modules or parts within sixty (60) days after receipt of an order, and there is no suitable alternative supplier, County will have the right to fabricate or have fabricated from drawings and specifications provided by the Contractor, such equipment, modules or parts. The Contractor shall provide, at its sole expense, any necessary patent releases. If the Contractor is not the manufacturer of a particular part or module within the system, the Contractor shall make every effort to assist in obtaining the necessary information to fabricate the necessary parts or modules that are necessary for proper system operation, which have been discontinued. F. The Contractor's undertaking herein is a covenant, promise, representation, and warranty made in consideration of the price or prices to be paid by County for the equipment to be delivered hereunder, as well as for such spare modules and parts. END OF SECTION Page 55 of 61 16A 8 1 XII SCHEDULE OF EVENTS 12.1 General A. The Contractor shall furnish County with a detailed project schedule in bar chart form identifying all major milestones, to meet the critical delivery, installation and testing dates and task duration as specified in Section 2.0. The following items shall be addressed as a minimum: 1. Submittals and Documentation 2. Design Phase 3. Software Development 4. Manufacturing 5. In- Factory Testing 6. Shipping of System Equipment 7. Installation S. Installation Verification 9. Testing (by test) 10. Final System Acceptance B. The Contractor shall prepare all deliverables in both Microsoft Office (Word, Excel or PowerPoint) and Adobe PDF formats, with County granted full rights to reprint as needed. 12.2 Project Status Tracking The Contractor shall prepare a System Implementation Plan (SIP), including the detailed implementation activities/ schedule, progress milestones/ status and assigned staff. The Contractor shall also include a Safety Management Plan in their SIP, which shall detail their responsibilities and procedures for safety during the different phases of the project, including (1) conducting pre - installation surveys to identify potential project safety hazards; (2) identifying project hazard control procedures, including occupational (worker) and public hazards; (3) providing project safety orientation and training to its subcontractors and the transit agency staff who will be involved in the project; and (4) furnishing procedures and training for project accident reporting and investigations, The initial draft of the SIP shall be provided to County within two weeks from Notice to Proceed (NTP). The revised SIP, addressing comments from the first onsite meeting, shall be provided to County within two weeks after this meeting. The SIP must be approved and accepted by County before it can become effective. An updated SIP shall be submitted to County at the beginning of each month. The Contractor shall maintain an Action Items List (AIL), indicating for each item the following: (1) item number; (2) date generated; (3) brief item descriptive title; (4) assigned person with lead resolution responsibility; (5) date resolved; and (6) ongoing dated notes on resolution status. The AIL shall be sorted, primarily by unresolved vs. resolved items and secondarily by the date the item was generated. Page 56 of 61 16A 81 12.3 Program Plan The Contractor shall prepare and submit a Preliminary Program Plan for County approval within ten (10) days of Notice to Proceed. The Preliminary Program Plan shall be a summary document indicating the manner in which the Contractor has broken down the major tasks necessary to comply with the Contract requirements. 12.4 Project Schedule The Contractor shall, within ten (10) days of notice to proceed, submit a reproducible copy of the project schedule showing the start and completion of all major events, operations and contract items planned for County approval. The Contractor shall update the project schedule on a monthly basis and forward the updates to County to reflect revised completion dates. The Contractor shall notify County immediately of any changes that are expected to delay the completion of the project more than two (2) weeks. 12.5 Monthly Progress Report and Weekly Conference Calls The Contractor shall participate in weekly conference calls with County Project Manager, other County staff and outside consultants as determined by County Project Manager. The agenda for these meetings will be to discuss the most current status of and plans related to all issues identified in the recent releases of the SIP and AIL. County reserves the right to identify for discussion any additional issues beyond those in the SIP and AIL. A status report shall be issued to County at least two days prior to each conference call, including (1) an agenda for the upcoming conference call highlighting key discussion items; and (2) an updated AIL with the updates incorporating the discussions of the previous bi- weekly conference call as well as other subsequent developments since the previous AIL release. The Contractor shall be represented in these conference calls by at minimum their Project Manager, as well as any additional Contractor staff necessary to properly address the current issues and project status. County will be represented by their designated implementation management representatives. Conference call facilities will be arranged and paid for by the Contractor. The Contractor shall submit minutes within two days of each conference call Each month the Contractor shall submit a report describing work accomplished in the preceding month, work to be completed during the next month, and a discussion of any outstanding or expected problems. County approved modification to the project schedule shall be included as part of the report. In addition, monthly progress reports shall include a list of specific action items which require input or resolution by the parties involved in the project. 12.6 Minimum Required Onsite Work At the first onsite meeting, the Contractor shall be prepared to discuss County feedback on draft SIP and conduct Requirements Review. At the second onsite meeting, the Contractor shall be prepared to discuss County feedback on draft Design Review documentation. During the third and subsequent onsite efforts, the Contractor shall install system and conduct acceptance testing. These onsite installation and testing efforts will occur over an extended period, and will likely involve several different onsite trips and a range of different Contractor staff. Page 57 of 61 16A a1 12.7 Invoicing The Contractor shall only submit an invoice once a fully- signed Acceptance Certificate is generated by County indicating that a progress payment milestone has been achieved. County will withhold 10% retainage on each invoice. Upon acceptance by County of each stage of the project, the total retainage for that stage will be paid to the Contractor. 12.8 Design Review The Contractor shall participate in the Requirements Review (RR), as part of the first onsite meeting. The RR meeting shall discuss, for each contract requirement, the following: (1) County design intent; (2) the intended Contractor design approach; and (3) the general Contractor approach to demonstration through the acceptance testing process. The Contractor shall submit draft Design Review Documentation (DRD) within four weeks of the RR meeting. The DRD shall include the following materials: (1) an overview of the equipment, system and configuration proposed for implementation; (2) detailed technical documentation for each equipment item; (3) detailed technical documentation on all software, addressing the functions of each module, the format of all user interface screens, the format of all reports, the data fields to be included in all data exchange interfaces and any other software aspects warranting advance agreement with County prior to system customization/ configuration; and (4) a table detailing the approach taken in the design to address each individual contract requirement. The second onsite meeting will include discussions with County on their feedback on the DRD, and shall occur within four weeks after the draft DRD has been submitted. The Contractor shall submit the updated DRD within three weeks of the second onsite meeting. The DRD is intended only to reduce the chance of any misunderstandings on the design intent or interpretation of the contract requirements. The DRD shall not alter the need for the successful formal demonstration of each requirement through the Acceptance Testing process The Contractor shall submit Installation Design Documentation (IDD), for County approval prior to undertaking any installations. The IDD shall provide text, drawings, illustrations and images using adequate detail to allow for quality installation by a technician without further training in conjunction with other installation instructions provided by the vendors of individual equipment components. The IDD shall include details on (1) equipment installation locations/ mounting; (2) routing, conductors, color - coding, labeling, and connectors for power, communications and vehicle ground circuits; (3) connections with, any required modifications to and restoration of existing infrastructure; (4) work area and equipment storage requirements (5) methods and quality standards; and (5) supervision and quality assurance procedures. END OF SECTION XIII WARRANTY 13.1 General A. Basic Warranty The Contractor shall guarantee all workmanship, materials, components and equipment for a period of one (1) year after installation and full acceptance of the fare collection system. Page 58 of 61 16A 8 2. If during the period of the warranty any defects or faulty materials, equipment or software are found, the Contractor shall immediately, upon notification from County, proceed with corrective action at the Contractor's expense to replace, repair or otherwise return the system to full working order. 3. The Contractor shall provide sufficient spare modules and parts to operate the system at not less than 99% availability at any time for the period of the initial warranty. These spare parts shall be furnished with the first equipment delivery. 4. The Contractor shall develop, test, and provide all applicable software "patches," upgrades and other remedies necessary to keep the system software in good order. The installation of such remedies will be performed by the County in close coordination with the Contractor. 5. All Proposers shall submit, with their proposals, a copy of their standard warranty as well as any special terms and conditions covering the equipment and software described in these specifications. B. Extended Warranty The contract includes a total of 5 years warranty for all the equipment 13.2 Coordination with On -Going Maintenance Support The basic and extended warranty provisions of this section are intended to be in conformance with and enhance the provisions of the section of these specifications describing Maintenance Support during the period in which the basic and extended warranties are in place. END OF SECTION XIV. MAINTENANCE SUPPORT 14.1 Support Requirements A. From Installation to System Acceptance Contractor shall provide on -site personnel qualified to troubleshoot all aspects of the system from the time of first equipment installation through system acceptance. These personnel shall be responsible for preventive maintenance, troubleshooting failures, removing and replacing defective parts, returning the unit to service, and initiation and follow -up of remedial actions. As an alternative, the Contractor may use County maintenance personnel to perform some or all of these activities at the Contractor's sole additional expense as long as regular maintenance of County buses and facilities is not affected. B. From System Acceptance Through Warranty Period Contractor shall assist County maintenance personnel in performing preventive and corrective maintenance including troubleshooting, removal of replacement parts and any warranty repairs, service, and campaigns. Both on -call telephone support and on -site technical support, when required by County for troubleshooting and support, shall be provided as part of the system warranty. Contractor's field representatives shall also be available for a minimum of three (3) visits to the location where equipment is installed during the period between system acceptance and expiration of the warranty to provide general aid and instruction to transit system personnel. In the event of a fleet defect that appears to County's project administrator to be a generalized problem that may affect all similar equipment, or a systematic defect (a defect in the data system, receivers or other subsystems that affects the ability of the fare collection system to achieve its intended purpose) Page 59 of 61 16A 8? the manufacturer's representative shall arrive as soon as possible, but no later than thirty-six (36) hours from the time of notification, at the County facility to review the problem and set up needed corrective action. The Contractor shall contract with a qualified company approved by County that can be called on for maintenance of the computer hardware and standard operating software and short response time critical troubleshooting on an emergency basis when the Contractor's staff may not be available. C. After Expiration of Warranty On -call maintenance support shall be provided by the Contractor for the life of the equipment after system acceptance. On -call support shall be provided via telephone conversation for hardware and software problems and operational troubleshooting at no additional cost to the County. On -site technical support, when required for troubleshooting, training or other similar activities required by County shall be provided at standard Contractor rates as per Exhibit B for preferred customers. D. The Contractor shall provide the maintenance support and warranty services described in these specifications to cover all depots on all equipment required to be provided by the Contractor. E. Contractor shall maintain on -site, a spare parts supply sufficient to meet maintenance and warranty obligations set forth herein from installation through the end of the five (5) year warranty period. 14.2 Test Equipment A. The Contractor shall supply test equipment which shall provide means for County maintenance personnel to bench test and repair each major module and /or subassembly of the on -board fare collection equipment. B. Maintenance Test Stand (Optional): This equipment shall be configured such that the following items are mounted on a stand or board and interconnected to provide a fully operational set of on -board fare collection equipment, plus software installed on a heavy duty service laptop computer to act as a fully functioning FCMRS. The maintenance test stand shall include at a minimum the following separate components: 1. Bill transport, including security mechanism 2. Coin unit 3. Logic boards 4. Data port to probe data 5. Data transfer probe 6. Electronic lock assembly 7. Cashbox ID unit 8. All displays and the tone generator(s) 9. Power supply 10. Magnetic swipe reader 11. Ticket processing unit C. All interconnections including wiring, harnesses, plugs, sockets and other connections shall be the same as used in a fully assembled Fare Collection System. The maintenance test stand shall be arranged in such a manner that each module can be separately exercised to perform its operating functions. D. Coin Unit Calibrator: Equipment shall be provided to calibrate and test the coin unit and related components. E. Bill Transport Calibrator: Equipment shall be provided to calibrate and test the bill transport and related components. 13.3 Availability and Performance Requirements A. During the period when Contractor personnel are on -site: Page 60 of 61 16A 8 7 1. Maintenance on fare collection equipment aboard the buses shall be performed in such a manner as to provide for 100% availability of all buses needed by County to meet pull -out each day at each depot. 2. Farebox equipment shall be brought back into service within four (4) business hours of reporting any incident. This shall be by module swap out or correction of the problem. B. During the period when on -call service is provided: 1. All questions shall be answered and requests for information shall be provided within a twenty - four (24) hour period. 2. Spare parts requested by County shall be delivered within forty -eight (48) hours of receipt of fax, email or telephone request from County. 3. Correction of software deficiencies shall be completed within a time as agreed between County and the Contractor, based on the severity and critical nature of the deficiency. At no time however, shall this time period exceed ten (10) business days, unless prior approval is provided in writing by County. 13.4 Computerized Maintenance Reports As an integral part of maintenance support, the Contractor shall include computerized reports as described in other sections of this specification that are designed to assist County to perform regular preventative maintenance on systems, equipment and components provided in these specifications. This shall include preventative maintenance scheduling as well as warning and alarm conditions and adequate training of maintenance managers and technicians in the proper and regular use of this capability. END OF SECTION Page 61 of 61 16A 8 EXHIBIT A -1 Contract Amendment #1 to Contract 11 -5753 "Electronic Fareboxes" This amendment, dated l� 2012 to the referenced agreement shall be by and between the parties to the original Agreement, Fare Logistics Corporation (to be referred to as "Contractor ") and Collier County, Florida, (to be referred to as "County"). Statement of Understanding RE: Contract # 11 -5 753 "Electronic Fareboxes" The Contractor agrees to amend the above referenced Contract by replacing Exhibit A -Scope of Services with the attached Exhibit A -Scope of Services, which incorporates technical clarifications to the original language. The additions to the existing language are shown herein by underlining; deletions are shown by str-ikethr-e All other terms and conditions of the agreement shall remain in force. IN WITNESS WHEREOF, the Contractor and the County have each, respectively, by an authorized person or agent, hereunder set their hands and seals on the date(s) indicated below. ATTEST: Dwight E. Brock, Clerk Approved as to form and Le sufficienc TrEputy County Attorney l- Il ,Ca-t t Name OWNER: BOARD OF COUNTY COMMISSIONERS COLLIE C Ty, FLORIDA By: W. Fred W. Coyle, Chairman First Witness Y f Etta- T TType /print witness nameT Second W i tn-& s TType /print witness nameT NAYAN P. GHELANI Commission # 1525490 z Notary Public - California z z Riverside County r My Comm. Expires Dec 31, 2012 16A 8 Fare Logistics Corporation Contractor By: Signature Typed signature and title County d S bafwe ms who proved to me on the basis d satisfactory evidence to be the persons whose narrte(s) is/ardwbsa�ed to the witetirt insbument and adcnowledped to 1110pdsh� sxecuted the same in ~04 autoved cap&*fm), and Oct by AiOherO& sgnak*s) an to insbur W the persan(s). or the enMy upon MW Of WtO the persons) acted, executed the instnune t 1 under PENALTY OF PERJURY under the taws d the of CaVw* #mt fns psraprspa is bus and Domed WITNESS my hand and dfcial seal. 16A g EXHIBIT A Scope of Services 11 -5753 Electronic Fareboxes Contract Overview The tasks and sub -tasks listed below are based on a current understanding of the project requirements. During the progression of the project, the County project manager and project manager for the Contractor will monitor the progress of each task and sub -task, and adjust the resource allocation and schedule as needed. The administration of the contract shall be as follows: 1. Any changes shall be mutually agreed upon in writing, but will not require a formal change order unless the change(s) would exceed the overall contract amount. 2. It is expressly stated and understood by the parties that zero dollar changes, including, but not limited to, time extensions not exceeding 20% of the overall contract, and time and/or sequence changes to Milestones may be made through the use of a Change by Letter signed by the County Project Manager or his /her Designee. 3. The Change by Letter will include a line for the Consultant's representative or designee's signature. Copies of the duly signed letter shall be forwarded to the appropriate Procurement Strategist for final signature and forwarding to the Finance Division. I. Work to Be Performed By Contractor The Contractor shall perform the following work: A. The Contractor shall be responsible for all work and expenses relating to the design, manufacture, delivery and installation of the equipment to the Collier Area Transit ( "CAT ") facility. B. Project to be completed, and final invoice must be submitted by February 28, 2013. C. The equipment, subsequent to testing, shall be complete in every respect and suitable for revenue service. D. For those items of equipment to be installed by the Contractor, the Contractor shall provide all hardware and other materials and all personnel and supervision necessary for installation in accordance with the schedule proposed by the Contractor and approved byCounty. 1. The Contractor shall supply such materials and supervision as may be necessary for the proper configuration and installation of the fareboxes, revenue equipment, Fare Collection Management and Reporting System (FCMRS) and any options exercised by County. All equipment shall be tested in accordance with a startup test procedure to be developed by the Contractor and approved by County. The Contractor shall provide on -site supervision of all installation efforts at all times during the installation. The Contractor shall adhere to the agreed installation schedule and procedures and provide the necessary documentation of work performed during the installation work. 2. The Contractor shall remove the existing fare collection system, including all existing fareboxes from the buses and the revenue servicing equipment in the cashbox vaulting lanes of the CAT facility. The Contractor shall be responsible for transporting such removed items to a central storage location at or near the CAT facility as designated by County. Page 15 of 79 L 0 A 0 OW040 3. For those items of equipment to be installed by the Contractor, a list shall be provided of all items of hardware and the required Contractor and CAT personnel and supervision for installation work in accordance with the schedule proposed by the Contractor and approved by County. 4. Contractor shall provide personnel to supervise, inspect and adjust the equipment prior to, during and through final acceptance of the final system. E. All equipment shall be of the latest engineering change level available and shall incorporate suitable modifications for all known operational problems identified during the PDR/ CDR reviews and during testing at factory. The Contractor shall retrofit all known problem solutions (engineering changes) to the equipment installed prior to the initial testing and any additional upgrades, recalls, campaigns, etc. that are made available to other customers during the warranty period. The Contractor shall notify County in writing of all such upgrades. F. The Contractor shall propose an installation schedule for the CAT's approval. Installation shall be completed over two (2), two -day weekends. G. The Contractor shall deliver the equipment to the location specified by the County, for purposes of temporary storage. County will provide suitable storage facilities prior to installation of the equipment and will assume sole responsibility for the equipment while in storage. H. Revenue collection vault(s) equipment, software and specifications shall be provided by contractor to County. I. County will provide a specific unobstructed site at its facility for the installation of the vault. This site shall be level and of suitable construction for such installation. If it is necessary to pour a concrete pad for the vault, County will be responsible for this work as well as for the construction of the vault; and the contractor shall be responsible to provide required pad size dimensions, load requirements, and mounting hardware to be embedded in the pad and any electrical or data conduit requirements that are to be embedded in the pad. J. The Contractor shall make available full and competent engineering services to identify and correct all problems associated with the performance of its equipment in a timely manner. K. Contractor shall be responsible for repairs under the terms and conditions of the warranty and maintenance support provisions indicated herein. Subsequent to the warranty period any parts, assemblies, and equipment shipped to the Contractor for repairs shall be subject to repair charges in accordance with an agreed upon schedule of prices or quotation for parts and labor. L. The Contractor shall provide the services of a qualified representative to meet with County to provide consultation and instructions regarding installation of the equipment specified herein. For operation of fareboxes on the bus, the Contractor shall use the existing DC electrical power available on CAT buses. M. The Contractor shall prepare all deliverables in both Microsoft Office (Word, Excel or PowerPoint) and Adobe PDF formats, with County granted full rights to reprint as needed. N. All work shall be in accordance with the schedule described herein or a modified schedule approved in writing by the County. O. The Contractor shall inspect the existing bus fleet and the power available with the existing batteries to ensure that there is sufficient power available for operation of the new Fare Collection System. If there are any deficiencies, these shall be identified by bus type to the County for a mutually acceptable resolution of the issues. Where data system installation or other electrical installation is involved, the Contractor shall be responsible for all work involved and must coordinate with the County's CAT and IT staff in the running of any overhead or underground conduits for data cable, stringing supported or unsupported cables from probe points to the computer and providing adequate electrical service for the equipment provided. Plans for such work shall be approved by County and meet all requirements of all applicable building codes. Page 16 of 79 2. Electrical requirements and all cable to the extent indicated in these specifications shall be furnished by the Contractor. Contractor shall inspect and coordinate with the County's IT staff the site where the facility equipment is to be installed and determine with County's approval if the existing conduit can be used within the new fare collection system. Contractor shall certify that this effort has been completed and include the usage of the existing conduit in the installation plan if such use is found to be appropriate. 3. The Contractor shall provide the services of a qualified representative to meet with representatives of County involved in this procurement to provide consultation and instructions relative to the proper provisions and work for the installation of equipment specified in these specifications. P. The Contractor shall furnish electrical requirements and all cable to the extent indicated in these specifications. Q. The Contractor shall be responsible for providing base dimensions and load requirements. Provisions shall be included by the Contractor to allow for the vaulting area to include methods to minimize the effect of moisture in the vault location to degrade the operation and/ or security of the vaulting equipment. R. The Contractor shall be responsible for hosting computer hardware and software required as part of the FCMRS (please refer to Section 5 for further requirements). County shall be able to access this hosted system over a secured network without any Contractor intervention, unless necessary for software support. The database used in the hosted FCMRS shall be secured and County shall be the complete owner of the data. County shall have full system administrator privileges to manage the user access levels and password - protection for the FCMRS. S. The Contractor will deliver the County's requested "remote Hosted solution," which will encompass the Contractor maintaining the Transfare system database, wireless communication to farebox devices for revenue data collection, installation of the TransMedia workstation connected to the Contractor's Private Network, as well as an ISP web portal to be used for County management to access reporting by means of a website URL to access the TransFare system. II. Work to Be Performed By County A. County will make buses available to the Contractor for installation work. County shall provide movement of buses as necessary. County shall approve all installation plans and procedures by the Contractor. B. County shall assist the Contractor in coordinating the actual farebox and other equipment installation. County will provide a mechanic and supervisor at the facility location where installation tasks are performed. C. County will provide AC power for all tools and lighting needed by the Contractor for physical installation. D. County will provide adequate storage space at its facility location to store the fareboxes and related equipment upon delivery from the Contractor. This storage shall be secure and protected from the weather. County shall also provide personnel and material handling equipment to bring the fareboxes (and other equipment) from such storage place to the designated installation sites. E. County will be responsible for and provide any and all material handling equipment and personnel required to lift or otherwise manipulate the vaults, collection bins, or their contents during day -to -day revenue transfer operations. F. County will provide a specific unobstructed site at its facility for the installation of the vault. This site shall be level and of suitable construction for such installation. If it is necessary to pour a concrete pad for the vault, County will be responsible for this work as well as for the construction of the vault; and the Contractor shall be responsible to provide required pad size dimensions, load requirements, and mounting hardware to be embedded in the pad, and any electrical or data conduit requirements that are to be embedded in the pad. G. County shall provide 120 VAC, 15 amp electrical services in proximity to the agreed upon location for the data probing system isolation Revenue Collection Vault. Page 17 of 79 16A g H. County shall coordinate with the Contractor regarding the system configuration of computer hardware and software required as part of the remote hosting of FCMRS at Contractor's facility. III. General Design Requirements The fare collection system specified herein shall be designed to function reliably in the intended transit environment specified. All normal conditions for this environment, including, but not limited to dust, moisture, electromagnetic interference, power line fluctuations, vibration, and exposure to atmospheric conditions shall not affect the reliability or service life of the equipment provided. The range of these environmental conditions shall be tested during the First Article Testing (FAT). A. Design Life - The fare collection system hardware and software shall be designed to provide a usable life for a minimum of twelve (12) years subject to proper preventive maintenance being performed. B. Modular Components - -All equipment shall be designed as modular. Modules from equipment of the same type shall be exchangeable between items of equipment without hardware or physical modification. Components, subsystems, assemblies, and subassemblies shall be of modular design for ease of maintenance and interchangeability and shall conform to the operational, storage and functional requirements as incorporated herein. C. Human Engineering 1. The fare collection system hardware and software shall be designed to provide for ease of use by a properly trained individual. 2. All software shall be designed to be user friendly, allowing the user to access all features through graphical user interfaces, pull down menus, and on -line help features based on assigned password privileges. D. Interchangeability All of the equipment furnished shall be identical in manufacture and function. The equipment and the components of the equipment shall be completely interchangeable. E. Maintainability and Accessibility 1. All components shall be packaged in replaceable and repairable modules. Standard hardware and components shall be used for flexibility and ease of maintenance. Standardized commercially available hardware and components shall be used to achieve flexibility in use and to facilitate maintenance. There shall be sufficient latitude in the operating tolerances to permit the substitution of modules without the necessity of making any electrical or mechanical adjustments. Modules and sub - assemblies shall be easily accessible and removable without the need for special tools. 2. All system elements provided under this contract to be used by the general public shall conform to the requirements that are in effect on the date of this proposal. For the purposes of this specification, all references to ADA requirements shall include the requirements imposed by any and all of the laws and regulations. 3. Entry codes shall be performed using internal keypads, with delayed alarm triggered if the proper code is not used. In equipment which contains revenue, the use of an internal access code and exterior access control system (PIN code, identification card or other security scheme) shall be required. F. Security and Safety All fare collection equipment shall be designed, manufactured, assembled and installed in a safe manner. Once the system is installed and available for use, there shall be no hazard to the public upon use of the fare collection equipment. The fare collection equipment shall pass County's safety verification as part of the First Article Test. G. External Surfaces Page 18 of 79 16A 8 1. External surfaces of all system equipment shall be clean, with no projections, sharp edges or corners that can cause any person injury or damage to property. External surfaces shall not contain cracks, weld marks, burrs, discolorations, or distortions resulting from fabrication, shipment or installation. 2. Surfaces not of stainless steel, aluminum, or plated shall be painted with a corrosion resistant paint. Painted surfaces shall be free of rust, scale, grease and foreign matter immediately preceding the first priming coat. Paint applied to any internal surface shall be designed to last for the life of the particular component to which it is applied. Paint applied to any external surface shall be baked enamel or other coating designed to last for a minimum of twelve (12) years before needing to be repainted. 3. The Contractor shall spray paint and bake all surfaces that are painted in order to give them a hard enamel finish. Any paint shall be uniformly applied over all surfaces to be covered, and shall be free from runs, sags, dirt or other application defects. 4. Color, metal protection materials and processes, and finish of all paintwork to be used on internal and external surfaces of all lane equipment shall be subject to County selection and approval. H. Locks 1. The Contractor shall provide all cashbox vaulting lane equipment with locked covers to prevent unauthorized access. 2. System equipment of the same type shall have identical locks that open with the same key number, and each type of equipment shall require different key numbers for access. 3. Separate access shall be provided, where possible, for operating personnel to perform routine maintenance and shall be keyed differently to equipment areas requiring access only by technical maintenance personnel. I. Reliability 1. The reliability of the fare collection shall be as follows at the conclusion of all acceptance testing: • Farebox: 2,000 Mean Cycles Between Failures • RCVS 10,000 Mean Cycles Between Failures 2. One (1) cycle for the farebox shall be defined as one (1) complete fare verification at a farebox, including required bus operator button presses. 3. One (1) cycle for the RCVS shall be defined as one (1) complete emptying cycle of a cashbox into the receiver vault. END OF SECTION IV. ON -BOARD EQUIPMENT The farebox shall be a mounted, freestanding device used to collect and securely store fares using a variety of fare media. This shall include processing cash, tokens and magnetic transfers and passes. The farebox shall be controlled by electronic logic and supported by electronic memory, displays and indicators. It shall permit the easy insertion of fare media by boarding customers; provide a display for customer information; and an OCU with human factors engineering practices and industrial design considerations. The farebox shall be reliable in revenue service operations, accurate in its counting and data reporting, and secure in its retention and transfer of data and collected revenue. Under normal operating conditions, processing of fares shall require the minimum effort by bus operators to accurately and correctly account for customer fare payment and collection of revenue. Operational Features -- The farebox shall have the following operational features: • Accept, validate, count and register US coins and paper currency, • Return coins, bills and tokens and other objects that are not valid or acceptable to the system; • Accept, validate and count magnetic farecards; • Print and issue a transfer, day pass and other agreed -upon types of passes; Page 19 of 79 • • • Print, encode and issue a farecard for fare overpayment (i.e., a "change card ") • Permit the recording of various types of fare transactions using bus operator activated pushbuttons. 4.1 General Performance Requirements A. The farebox, as defined within these specifications, shall include all hardware and software installed on- board any CAT bus for purposes of accepting payment of the fare by a customer by: cash, token (as defined by County) and magnetically coded transfers and passes as valid fare payment methods. The system software and hardware shall include means for validation and acceptance of new currency to be issued in the future by the United States Treasury Department. B. The farebox shall be installed on each bus, adjacent to the bus operator, and in proximity of the front door. It shall be positioned so that an entering customer may easily insert the required fares into the farebox, using a fare payment of coins without blocking exiting customers. This position shall permit the bus operator to readily determine the customer's fare payment method, observe all of the digital readouts provided on the bus operator side of the farebox (including the OCU), and reach and manipulate various bus operator controls from the seated position. The farebox location shall permit all of the required maintenance functions to be performed, as well as to provide easy access for the removal of the cashbox and meet all ADA requirements for customer entry and exit. C. The mounting of the farebox shall be designed to minimize movement or rattling of the farebox. D. The farebox shall be a solid -state logic controlled validating farebox with supported memory used to accept, validate, count and securely store paid fares. E. The farebox shall function under the environmental and operational conditions stated in these specifications and shall be designed and manufactured to provide a high degree of security against forced entry into the cashbox area and /or unauthorized manipulation of farebox modules. F. The farebox shall permit the customer to easily and rapidly insert the required fares and for the bus operator to readily ascertain that the correct fare has been paid, regardless of the fare payment method employed. The capacity of the farebox shall be such as to securely retain the collected fares until such time as they are removed under authorized conditions. The farebox shall function in a reliable manner so as to provide service on an uninterrupted basis, consistent with the performance requirements contained herein. G. The farebox shall function to provide specific information relative to the daily operations of the farebox; the revenue amounts, types and quantities of customers; bus operator and work run identification; bus location data, and other information which may be used in providing audit trails; ridership data and accountability of the specific items of equipment and of the system operations. The degree and extent of this information and the means and methods of its generation and reporting shall be as described in these specifications. H. The electronic boards utilized within the farebox, including associated electronic components, shall be capable of operating ten thousand (10,000) hours between failures provided there is no abuse, vandalism, operation beyond standards or lack of maintenance per the Contractor's instructions. I. On -board equipment shall have a mean time to repair of ten (10) minutes. Repair shall be defined as the diagnosis, removal and replacement of one (1) or more defective assemblies (such as a coin unit, bill transport, MSR, OCU, cashbox, electronic board, etc.) to put the equipment back into operating condition. Repair of the defective assembly will not be included in mean time to repair. J. The farebox shall have the ability to create and store summary records as well as transactional records, K. The activation and deactivation of bus operator log -on /log -off with the OCU shall be settable and modified only via downloaded fare table parameters from the Fare Collection Management and Reporting System (FCMRS). Page 20 of 79 16A 8 L. A switch shall be located within the farebox to disconnect it from the vehicle power. Location of this switch shall be identified on the farebox design drawings and shall be subject to review and approval of County. M. Contractor shall provide stickers and other graphics for the fareboxes to identify the various slots and displays, which shall identify the correct insertion of payment and fare media. These shall be provided by the Contractor for County review at PDR and approved at CDR. 4.2 Coin Acceptance A. Operation 1. The farebox coin unit shall accept, validate and count the value of pennies (1 4), nickels (54), dimes (104), quarters (254), half- dollars (504), and (Susan B. Anthony /Sacagawea) dollar coins ($1.00); and accept and validate a token as desired by County. Validation of the coins shall be by weight, density, magnetic properties, size and/or other means which will guarantee that only valid US coins are accepted and validated. 2. The coin slot shall permit ease of coin entry and shall be designed to last the life of the equipment. 3. Acceptance and registration of coins shall be at a coin insertion rate of not less than ten (10) coins per second. The coin unit and associated logic may be utilized to identify other sizes of coins without necessity of replacement or remanufacture of the coin unit or other hardware change. 4. Subsequent to insertion and registration, coins shall be directed to a cashbox located within the base of the farebox. Within the cashbox the coins shall be maintained separate from the bills. 5. The counting logic of the farebox shall increment the appropriate non- resettable counter for each denomination of coin and each type registered and accepted. 6. Any remaining value displayed on the OCU and the Customer Information Display shall clear after the display clear time has elapsed. County shall have the ability to set the display clear time in one (1) second increments from zero (0) to sixty (60) seconds via the FCMRS. 7. The coin unit shall meet the following criteria: • Ninety -nine percent (99.0 %) of valid coins shall be accepted and validated upon initial insertion. • Ninety -nine and eight - tenths percent (99.8 %) of valid coins shall be accepted and validated upon one (1) reinsertion. • All known counterfeit coins, common slugs, foreign coins, and coins of denominations not valid shall be rejected upon every insertion. • Validation accuracy of accepted coins shall be at least ninety -nine and ninety -five hundredths percent (99.95 %). 8. Each coin unit shall be permanently inscribed with a clearly visible unique serial number. B. Coin Return 1. A coin return cup or tray shall be provided on the farebox, located within easy reach of a customer and conforming to all ADA requirements. 2. Any coin which the customer inserts into the farebox and the coin validator cannot automatically validate shall be returned to the customer via the coin return cup. This shall include deformed coins and coins otherwise not meeting the specified valid coin criteria. 3. The farebox shall note in its memory and retain for data transmission the instances of coin returns. This information shall be forwarded to the FCMRS to assist in failure diagnosis. C. Deformed Coins Page 21 of 79 16A 1. The coin unit shall have the capability of handling, without jamming, coins which are deformed. That is, coins which, within certain limits, are bent or bulged, not perfectly round or have attached foreign material. 2. The coin unit shall process and accurately validate coins with the following deformations: a) Coins bent or bulged having overall thickness ranging up to 0.020 inch greater than the coins' standard thickness. b) Coins having attached, relatively complete and uniform layers of foreign material (such as epoxy, solder or hardened gum) ranging up to 0.040 inch in thickness. c) Coins not perfectly round (examples: squashed or flat edges) having diameters up to plus or minus 0.020 inch different from standard diameter at the point of deformity. D. Coin By -Pass 1. A coin by -pass mechanism shall be provided for the passage of coins to the cashbox by- passing the coin unit (in the event of, for example, a coin jam in the coin unit or a failure of the electronic logic). When a farebox is placed in by -pass mode, the FCMRS shall record this event. 2. The activation of the coin by -pass mechanism shall be by a deliberate action on the part of the bus operator. Coins processed in this manner shall not be counted nor registered by the farebox but shall be passed directly into the cashbox. 3. In the operation of any device to achieve a coin by -pass, the security of the farebox and the retention of the revenues shall not be diminished. When the mechanism is used, it shall not be possible for the bus operator to reset it from outside of the farebox. 4. The farebox shall note in its memory and retain for data transmission, the exact time when the by- pass is activated and deactivated. A record shall also be created when the by -pass is activated and again when the by -pass is deactivated. 5. The resetting of the mechanism shall require access to the farebox interior by authorized personnel. 6. When the coin by -pass is activated, bills, magnetically encoded and smart cards shall continue to be accepted, registered and processed. 4.3 Bill Acceptance A. The farebox shall be capable of accepting, validating and counting U.S. $1, $2, $5, $10 and $20 bills oriented in any of four (4) directions. The paper currency acceptance slot shall be positioned in the general proximity of the coin insertion area, and shall accept bills which have been opened to their full area and inserted lengthwise. The dimensions of the currency slot shall hinder the accidental entry of coins into it. The currency slot shall be illuminated to permit ease of bill entry in diminished lighting conditions using LED lighting designed to last the life of the farebox. The unit employed to transport the inserted bills shall be positive and not require precise insertion by the customer. A guide bezel shall be provided to assist in the entry of the bill into the currency slot. The bill shall be inserted approximately one (1) inch before the transport shall become operational and advance the bill to the validation area. B. The bill transport shall employ a roller mechanism to positively engage an unfolded and folded bill, regardless of condition without jamming. It shall require no force to cause the transport to start. C. The bill shall be advanced to the cashbox (in the lower portion of the farebox) after validation. Any remaining value displayed on the OCU and customer display shall clear after the display clear time has elapsed. D. Bills shall be processed at a maximum rate of one (1) bill per second. This time shall be measured from the time that the bill is sensed in the bill insertion slot to the time that the value of the bill is displayed to the customer and the bus operator. Page 22 of 79 16A 8 E. The bill transport shall have the capability of handling, without jamming, paper media which is deformed. That is, paper media which is subject to the conditions of daily "street" use, including wrinkled, torn, folded, or damp media. F. The bill transport shall process and accurately validate bills with the following conditions: 1. Bills which are not uniformly flat or in "new' condition. 2. Bills which are torn to a depth of two (2) inches from the edge of the bill. 3. Bills which are damp but not saturated. 4. Bills having tape or other foreign material adhering which can fit through the opening in the currency slot. G. Each bill transport shall be permanently inscribed with a unique serial number, clearly visible when the maintenance apertures of the farebox are opened. H. Bill processing and acceptance shall meet the following criteria: 1. 97% of valid bills shall be validated and accepted upon initial insertion. 2. 98.5% of valid bills shall be validated and accepted within two (2) insertions. 3. All known counterfeit bills, color photocopies of valid bills, duplicates made by other known means, foreign bills, and bills of denominations not valid shall be rejected upon every insertion. 4. Validation accuracy of accepted bills shall beat least 99.95 %. I. The acceptance sensitivity of each denomination of bill accepted shall be adjustable. J. Bills and other paper items placed in the bill insertion slot that are not accepted shall be returned to the customer at the bill insertion slot. 4.4 Operator Control Unit A. The farebox shall be equipped with an Operator Control Unit (OCU). Integral to each OCU shall be a keypad and display or touch screen to operate the farebox. The OCU shall be capable of initializing a farebox and its electronics for route and run setup. B. The OCU shall not be integral to the farebox but shall be housed in a separate compact console constructed of revenue service tested materials. Mounting hardware shall be provided to permit mounting on the vehicle dashboard or other appropriate location, facing the bus operator. The OCU shall be positioned not less than twenty -five (25) inches from the bus floor. The OCU shall be mounted on an adjustable and lockable ball joint that allows the bus operator to provide for ease of button operation and viewing of the display. The installed OCU shall not interfere with any bus controls, block any bus indicators or other bus operator displays, or create a safety hazard. All mounting arrangements shall be approved by County. The OCU shall be connected to and communicate with the farebox via protected cabling. C. The OCU shall be provided with a two (2) line electroluminescent display, a light emitting diode display or a backlit liquid crystal display (LCD) or an approved equivalent such as a full context touch screen with not less than twenty (20) alphanumeric characters per line, and which shall be fully dot addressable, capable of displaying graphics and capable of displaying a minimum of two (2) lines of text. The CCU shall be able to show the full ASCII character set. For backlit LCD displays, the OCU contrast shall be adjustable and backlighting shall be capable of being turned on or off via the OCU keypad. The display shall be of sufficient brightness to be visible in all forms of ambient lighting within the bus and shall be sufficiently protected by a panel of clear plastic which shall also reduce glare. D. Under normal operations when the farebox is static, the bus operator information display shall be extinguished to preserve its operating life. It shall be active when it is required to display operational information, when the bus operator inputs data, and when a given push - button is depressed. Alternatively, County may elect to have this display show the current time when the farebox is static, the time being extinguished when it is necessary for the display to provide information. Page 23 of 79 - E. The bus operator information display shall indicate to the bus operator the status of any ongoing transaction and other information pertinent to the operation of the farebox, including: 1. The amount of money inserted into the farebox in the form of coins and bills and the fare due. 2. The current function of the soft (programmable) function keys. 3. The function of a given button on the keypad when that button is depressed. 4. Confirmation for any bus operator input information. 5. Bus operator sign -on and sign -off prompts. 6. Upon completion of the farebox "boot sequence" the farebox shall be required to be set with ' Fareset' for the run. F. As coins and bills are validated, this display shall count upward, reflecting the amount of money inserted. If a preset fare is used, when the full fare is reached, or when the bus operator presses a button indicating acceptance of a reduced fare (student, senior, etc.), a tone shall sound, and the display shall automatically subtract the proper fare from the amount on the information display and display the remainder. G. If a transaction is not completed, the bus operator information display shall be automatically reset after the last coin /bill has been validated based on the duration of the user settable timer. This timer shall permit County to set the display clear time from zero (0) to sixty (60) seconds in one (1) second increments. Any remaining value displayed shall be added to the "unclassified revenue" data register. It shall be possible for the bus operator to delay resetting by pushing a designated "hold" button which shall reset the timer to zero. H. The OCU if other than a full context touch screen shall have a minimum of twenty (20) pushbuttons, including digits 0 through 9, ENTER, CANCEL, and user - definable function keys. All bus operator pushbuttons shall be fully programmable, shall provide tactile and audio feedback and shall be sealed against the intrusion of liquids and other foreign material. I. The OCU touchscreen keypad shall enable the bus operator to classify reduced or special fares and perform all other on -board tasks connected with the operation of the farebox in revenue service. J. Each of the classification buttons on the keypad shall be capable of being programmed to: 1. Register a specific value ($0.01 to $99.99) with the option to also record the fare in the designated category with the option to reset the register display to "0.00." 2. Increment a zero -value tally counter. 3. Be disabled (nonfunctional). K. The fare values assigned to each classification button shall be individually programmable for each fareset. The values assigned to these buttons will be changeable in a matrix format, that is, each preset activated by the bus operator may have a different value assigned, depending on the fareset and requirements of County. This matrix shall be stored in the non - volatile memory of the farebox, and shall be changeable only via the means outlined in these specifications. L. Each time a button is activated, the bus operator's information display shall indicate the key number pressed and show the value assigned. Cash fare registration pushbuttons shall be able to be activated prior to, during, or after the validation of money in the farebox to obtain the proper farebox setting. Pushbutton keys used as tally counters shall require no money to be inserted to obtain a count. Each time a pushbutton is pressed in the proper manner, a tone shall sound, indicating that a count has been made in the corresponding farebox data register. Individual pushbuttons shall also be able to be deactivated and these shall have no effect on the registration of fares or tally count by the farebox. M. The farebox logic shall provide for the storage of entered log -on information including route number, run number, trip number, fareset, and bus operator number into the farebox memory. This shall be accomplished using the trail of the identity of the bus operator and other log -on information for later transmission to the FCMRS upon data transfer using wireless comunicationspelxg. Page 24 of 79 M, E918 • N. A farebox that has gone into the "Idle" mode shall remain in that mode until the Avail System (or the bus operator in backup mode) has logged -on to the farebox. O. Log -off from the farebox shall occur in four (3) ways: 1. Bus operator sign -off via the OCU 2. Automatic time -out log -off (based on a preset time period of farebox inactivity). 3. Automatic log -off following data transfer After log -off of the farebox by any method, a message shall be immediately forwarded to the OCU and the OCU and other displays shall be placed in the idle mode. This shall include those occasions when a bus operator prematurely signs -off the farebox. P. All push - buttons shall be of sealed construction to prevent entry of foreign material which might degrade performance. Design of the buttons shall provide a tactile indication to the bus operator that electric contact has been made. Q. It shall not be possible to program the farebox with information that would normally be transferred from the FCMRS by using the OCU. R. A bus operator actuated function, shall be used for the purpose of displaying the contents of various information registers on the OCU. These registers shall be user definable via the FCMRS and their display shall be password protected. 4.5 Customer Information Display A. The customer information display unit shall be provided in the form of a 2 -line (minimum) 20- character alphanumeric back lit LED or CAT - approved equivalent. The back lighting shall provide for adjustable intensity to provide clear visibility in bright lighted conditions and during night operations. B. The display shall be positioned on the farebox facing the boarding customers approaching the farebox. C. Under normal operations when the farebox is static, the customer information display shall be extinguished to preserve its operating life. It shall be active when: a coin, bill, magnetically encoded pass or a token is processed by the farebox and when the bus operator classifies a fare. In addition County shall have the ability to program a message on the display (e.g., "Welcome Aboard ") rather than have the display inactive. D. The display shall be able to show the full ASCII character set. E. The customer information display shall indicate specific messages programmable by County through the FCMRS relative to use including: 1. Validity (for passes) 2. Amount deducted and remaining value to be deposited by the customer 3. Remaining value for stored value based farecards 4. Cash inserted in the farebox 5. Amount due 6. Farecard step -by -step loading instructions (i.e., for adding stored value to an existing farecard) F. The customer information display shall provide displayed messages programmable by County through the FCMRS to the customer for selected fare media processing difficulties including: 1. Card misread (applies to farecards used in the TPU or the MSR) 2. Insufficient value remaining 3. Invalid card (including bad card list match) 4. Fare media expired Page 25 of 79 16A $1 G. When a cash transaction is initiated, the display shall show the amount deposited and the amount of the fare. When a magnetically- encoded card is read using the TPU or MSR, the display shall show relevant information such as: 1. Expired or Invalid 2. Please Try Again 3. Value remaining 4. Amount due (if no remaining value on farecard) H. Information on the operation of the customer information display and all such conditions sensed, reported and displayed shall be provided at the PDR. 4.6 Audible Signals and Spoken Messages A. The audio transducer shall be provided with a sound level of not less than 65 db at a nominal 12 volts DC. The audio transducer shall sound the specified tone under the conditions stated below. A minimum of three (3) clearly distinguishable tones shall be provided. Tones shall be programmable by County through the FCMRS. Designation of initial tones for testing are provided below in parentheses. 1. The audio transducer shall sound each time a valid fare is inserted and registered (Tone 1). 2. The audio transducer shall sound a multiple signal when an invalid or expired fare medium is used (Tone 2). 3. The audio transducer shall sound a multiple signal when a permit or reduced fare medium is used (Tone 3). 4. The Audio transducer shall sound a multiple signal as acknowledgment that the bus operator has completed the sign -on procedure and that the data has been received by the farebox (Tone 1). 5. The audio transducer shall sound a multiple signal as acknowledgment the data has been extracted properly (Tone 1). 6. The audio transducer shall sound a multiple signal when a button unassigned to the active pre -set is pressed (Tone 2) B. The farebox shall also be capable of generating spoken messages using digitized human voice. It shall be possible to enable and to disable the spoken messages via the FCMRS. Spoken messages shall be triggered by County defined farebox operating conditions and include messages such as, "Transfer Not Valid ", "Please Swipe Card Again", and "Please Insert Card Again." County shall be able to choose from a list of standard and custom spoken messages and assign them to the relevant functions by use of sound files located in a FCMRS data file. 4.7 Fare Structures A. The fare collection system shall provide for no less than ten (10) individual fare tables that describe separate fare structures. B. It shall be possible for County to change the fare values in any fare table by means of data entered by the FCMRS and the PDU, without the necessity of removing or replacing any of the farebox electronic components. C. Each fare table shall include all information required to provide for proper processing of the customers based on County's fare structure and associated usage rules including: the base fare, the value of any tokens, the valid customer categories plus their associated fares, day passes accepted, day passes issued (plus appropriate charges), other passes accepted, and "cash drops" for other pass types. D. Means shall be provided for the bus operator to switch between the fare tables at the start of a route and during a run on certain routes, such as express services. The means shall not require any special Page 26 of 79 16A 8 components. The farebox shall only accept a valid fare table based upon the information downloaded to the farebox from the FCMRS. E. Upon completion of changing the fare table a "Change Fare Table" record shall be created defining the new pre -set and a summary record shall be stored. 4.8 Fare System Presets The farebox shall be capable of operating in two (2) distinct modes: 1. Preset fare mode 2. Manual mode (no preset fare) A. In preset mode, the farebox shall count up and display the value of the inserted amount. When the amount of the preset is reached, the farebox will automatically count the preset fare as one (1) adult customer and decrease the register readout by the amount of the fare. The Bus operator may also press a button to indicate that a fare classification other than the preset fare applies and the farebox will be temporarily set to accept the alternate fare classification. When the proper fare is paid, the fare will be counted and the register readout decreased by the amount of the fare classification. Any overpaid balance shall remain displayed for a programmable time -out period and then return to zero unless overridden by the Bus operator. B. In manual mode, the farebox shall count up and display the value of the inserted amounts. When the bus operator presses the category of fare, a unit count shall be added to a specific register representing that fare category. The overpaid balance shall remain displayed for a programmable time -out period and then return to zero unless overridden by the Bus operator. C. In either case, the overpaid amount shall be able to be used toward an additional fare unless the bus operator resets the register reading to $ 0.00. F. The farebox shall have the ability to have a minimum of ten (10) preset amounts, programmed into the electronic logic. A preset amount shall be between $0.05 and $19.95 in value. 4.9 Memory and Data Storage Requirements A. The farebox shall have sufficient memory to store a minimum of 10,000 transaction records, 2,000 records (including time segment records) and 2,000 event/ alarm records. This memory shall be backed up with a redundant data module B. The farebox shall be able to hold and support the volatile portion of the memory after being removed from power for not less than fourteen (14) days after removed from a primary power source. Lead -acid batteries, which may leak, shall not be used for this purpose. C. Under no circumstances shall the failure of a battery corrupt the data or affect the ability of the farebox to collect the proper fare, perform validation of coins and bill and other fare media or compromise any security feature of the fare collection system. A message shall be provided using the OCU to notify the bus operator of a low battery condition that will allow adequate time (at least twenty -four (24) hours of operation) to replace the battery. A report shall also be made via FCMRS of low- battery condition. D. Electronic logic incorporated in the farebox shall receive value signals from the coin unit, bill transport, ticket processing unit and the swipe reader. The electronic logic shall accumulate and store the amounts in an electronic register and such amounts shall be displayed on the OCU. The accumulated fares shall advance revenue registers which shall accumulate the total value received by the farebox since the farebox was last probed and the total value received by the farebox since installation or clearing of the farebox memory. Totals shall be stored for all cash revenues and tally counts retained for number of magnetic swipe cards read. Separate counts shall also be stored for each type of fare media accepted. E. A separate count shall be accumulated for all cash that is displayed on the OCU and not accounted for via push button activation. All such revenue shall be included on an unclassified revenue register. A Page 27 of 79 16A 8 transaction record shall also be stored recording the amount dumped and the associated fareset number. Each fareset shall be set to activate or deactivate this pushbutton. F. Transaction Records The following data shall be generated by and stored in the farebox and be available for the generation of reports and queries when transferred to the FCMRS: 1. The fare collection system shall generate a transaction record for each customer processed which shall be transferred to the FCMRS. Each transaction record shall be unique within the system. This transaction record shall include the following information: a) date and time of transaction b) magnetic card serial number c) bus number d) farebox number e) route number f) run number g) direction code h) fareset number i) trip number j) customer type (adult, student, senior, etc.) k) fare type - bus fare, transfer charge, short fare and overpayment 1) amount paid m) method of payment n) cash denominations and quantities o) expiration date p) transaction number q) service type; local, express and special run 2. The fare collection system shall generate a transaction record for each vaulting and wireless data communications incident. 3. The fare collection system shall generate a transaction record for each bus operator log -on and log - off by any of the four (4) methods described in this specification. 4. The fare collection system shall generate a transaction record for each event sensed by the farebox. 5. The fare collection system shall generate a transaction record for each alarm initiated. This information shall be stored in a separate security file, access to which shall be protected by security password. 6. The fare collection system shall generate the transaction records necessary to provide the maintenance information. 7. The fare collection system shall generate a transaction record whenever any of the following events takes place: a) The bus operator log -on operation is altered. b) When a route /run record is recorded. c) Midnight and other date/ time changes Page 28 of 79 16A 8 . I d) The farebox is placed in bypass e) The farebox is removed from bypass f) The cashbox is removed (cashbox number shall be saved) g) The cashbox is inserted (cashbox number shall be saved) h) The cashbox access door is closed after a time -out period of five (5) minutes (this period to be FCMRS settable as an operations parameter) i) The cashbox access door is opened at other than the time of normal Revenue Servicing. j) The cashbox access door is closed at other than the time of normal data pfebingEtKenue Servicing k) The farebox data transfer starts 1) The farebox data transfer ends m) The farebox internal clock fails n) The record storage is about to overflow o) Changing from one (1) pre -set to another p) All payment transactions, including the value of coins and the value of bills q) All ridership registration transactions r) Farebox power off s) Farebox power on t) Bus operator log -on u) Bus operator log off v) Unsuccessful data transfer w) Successful download of farebox configuration data x) Unsuccessful download of farebox configuration data y) Farebox errors and failures z) Security errors and intrusions aa) Coin jams bb) Clearance of coin jams cc) Bill jams dd) Clearance of bill jams ee) New fare table selected ff) Farebox percentage full (settable threshold of 50- 100 %) for coin gg) Farebox percentage full (settable threshold of 50 -100 %) for currency G. Time Synchronization 1. The farebox shall contain a real time clock which shall store the time that will be used for printing; recording; validating; time and date stamping of transactional data, and fare media; for display of transaction records on the CCU; and as part of bus operator and customer information. This clock shall record and display hours, minutes, seconds and date in appropriate formats. This clock shall be capable of being reset to the correct time automatically upon log -on and each time data is transmitted from the farebox and shall be accurate to within one (1) minute per year. Page 29 of 79 2. The Fare Collection System shall have its own time synchronization function through the County LAN to the FCMRS clock for standalone operation. In this mode synchronization of the computers to the LAN shall be performed at least once every twenty-four (24) hours, and synchronization to the farebox will occur when the farebox is probed by the FCMRS, J. Time Segment Records 1. All fareboxes shall be provided means to permit the bus operator to make a "summary count record" within the farebox memory. This function shall provide means to aggregate data for a segment of a route to, for example, gather number of boarding customers at a user specified interval. The default period for the time records shall be fifteen (15) minute summaries. 2. The memory capacity of the segmenter shall be suitable to compile a minimum of 2,000 records (as a part of the total number of records) per farebox vaulting. 3. The information stored in the segmenter shall not be accessed through the bus operator's information display, but shall be stored and transferred to the FCMRS. Once stored in the farebox, data shall not be available to the bus operator for editing in any fashion. 4. To create a "record ", the bus operator shall press specific buttons in a prescribed sequence. The information display shall confirm this by showing the words "Make Summary Record ". The bus operator shall then be required to confirm or cancel. 5. In addition, County may elect to have a summary record initiated automatically at set intervals based on the real time clock in the farebox. These intervals may be every ten minutes, every fifteen minutes or every twenty minutes or more as required by County. This feature shall be set to be activated by downloading from the FCMRS. 6. A summary record shall be created with a special code indicating the type of event that took place, e.g. bus operator initiated, automatic based on time, farebox placed in bypass, etc., and this shall be reported in the data system when the appropriate reports are accessed. The special code may be a predetermined number not otherwise used by County. K. Farebox Diagnostic and Operational Reporting 1. The farebox and its electronic logic shall be designed to provide the specified degree of operational self testing, diagnostic operations, reporting and indication. These elements are required for effective maintenance of the equipment, to provide audit trails to determine proper farebox operation. 2. Indicator Lamps - A series of LED indicator lamps shall be provided which shall indicate to a technician the proper operation of all of the major modules. An LED indicator shall be used to indicate proper voltages from the main power supply. Automatic Sequence Testing - The farebox logic shall be designed to provide an automatic sequence testing of each of the major operational assemblies. The automatic sequencing shall be initiated by the insertion of a "test plug" or USB stick or other approved means, thereby placing the farebox in a "test mode ". Each assembly shall be caused to fully operate a minimum of four (4) times during the automatic sequence. The sequence shall continue for an indefinite period until stopped by external intervention. The amount of time during which the testing sequences was run shall be recorded by the farebox in terms of minutes and seconds. This time shall be available for display on the OCU. Coin/ Bill Totals - The farebox logic shall provide specific counts of individual coin and token types by quantity. This is above and in addition to the requirements for accumulating value, as described elsewhere in these specifications. The farebox shall also provide a unit count of the quantity of bills processed by denomination. The farebox shall also provide total counts of all coins processed and all bills processed. These counts shall also be used for preventative maintenance and audit purposes and as a second determinant of validation factors associated with each farebox coin unit and bill transport. Page 30 of 79 16A 84 5. Power Supply Monitoring. The farebox shall monitor and report the number of times the primary power source has gone to zero (0) volts and back to normal. This serves to indicate an intermittent power line or poor ground connection or faulty switches. The farebox shall also monitor and report the number of times the power supply drops below the minimum voltage, but not to zero (0). This is indicative of a heavy load on the bus electrical system or a possibly defective bus battery cell. These counts shall be reported through the data reporting system. 6. Security Door /Cashbox Alarms - The farebox shall be provided with a sensing device capable of monitoring real time and the length of time that the cashbox security door is open. If the door is open for longer than three (3) minutes (programmable), an alarm signal shall be transmitted to the data storage within the farebox memory. The real time at which this alarm was sensed along with the length of time the door was open shall also be stored in memory. The next time the farebox is probed, the transmission shall contain a "security door alarm ", indicating the time of the alarm, the length of time the door was open, and how much revenue was in the farebox at the time of the alarm. The farebox shall be provided with a sensing device capable of monitoring the presence of a cashbox in the farebox. If a cashbox is removed at a time that varies by more than three (3) minutes (programmable) from the time that the farebox is probed, a cashbox alarm shall be created and stored in the farebox memory. The real time at which this alarm was sensed along with the length of time the cashbox was not in place shall also be stored in memory. The next time the farebox is probed, the transmission shall contain a "cashbox alarm ", indicating the time of the alarm, the length of time a cashbox was not in place in the farebox, and how much revenue was in the farebox at the time of the alarm. 7. Cashbox Full Indicator - The farebox shall be provided with a visible indicator on the OCU to prompt the bus operator when either the coin compartment or the bill compartment in the cashbox reaches eighty percent (80 %) (programmable) of their respective capacities of coins or bills. The indicator shall remain visible until the cashbox is extracted and the coin compartment and the bill compartment registers are automatically set back to zero. The coin compartment and bill compartment amounts required to activate the visible indicator shall be programmable. 8. Farebox Reporting - All amounts, quantities, and other information developed as a consequence of compliance with the requirements of these specifications shall be stored in the farebox memory and shall be transmitted to the FCMRS for later report printing of the information for each farebox. 9. Maintenance Information - The farebox shall include resettable transaction counters that maintain the number of payment cycles for the coin unit, bill transport, TPU, MSR and the entire farebox. The individual transaction counters, as well as the farebox transaction counter shall be capable of being reset by the technician whenever the module is removed for maintenance. This counter information shall be stored within the farebox and transferred to the FCMRS upon data wireless data transmissionpfebft 10. Door Open - The farebox shall store an alarm transaction when one (1) of the doors on the farebox is opened including the top cover, cashbox door and maintenance access doors. The cashbox alarm shall be an audible alarm and alarm message only if the door is open for more than the user settable period of time or if the door is opened without proper authorization. The alarm shall not sound and the alarm message shall not be created in any other instance. 4.10 Cashbox Removal, Identification and Locking System A. Cashbox Removal 1. The cashbox door shall be fitted with internal devices which shall only release and open the door B. Cashbox Identification System 1. The farebox shall have the ability to automatically read a unique identification number of each inserted cashbox. This serial number shall be a minimum of four (4) digits. 2. The means and methods employed shall not require electrical contacts, plugs or other physical connections between the farebox and the cashbox. Page 31 of 79 16A 8 3. Readings shall be automatic, and the information relative to the serial number shall be stored in the farebox memory for subsequent data transmission to the FCMRS. Only one (1) serial number record shall be stored for each cashbox insertion and for each removal from the farebox and receiver. 4. If a battery is used in the cashbox, the system shall be designed such that the battery shall have a minimum lifetime in this application of three (3) consecutive years and shall provide an advance warning on the OCU and FCMRS sufficient to allow for battery replacement before battery failure. C. Cashbox Door Locking System 1. The farebox shall incorporate within its logic elements, the ability to retain a specific code or other secure means to release the cashbox door. The action of closing the cashbox access door and holding it in the closed position for approximately one -half (0.5) second shall cause the farebox mechanism to engage the door locking pins and lock the cashbox access door. If the door is slammed, with rebound, the mechanism shall not engage. 4.11 Magnetic Swipe Reader Fareboxes shall be provided with an integrally mounted read only magnetic swipe reader (MSR) located on the top surface of the farebox. The reader provides a longitudinal slot in which a magnetic card is manually traversed past a read head. A. Function 1. The MSR shall be able to accept magnetically encoded cards that have been previously encoded with data such as date of expiration, type of service, conditions of use, serial number and other information relative to its proper operation in revenue service. The farebox shall function to read the information on the card(s) and determine whether the card is "valid" or "invalid" based upon the preprogrammed parameters in the farebox as compared with the encoded information on the card. 2. The MSR shall automatically process a correctly inserted, valid magnetic card in one -half (1/2) second or less. The operation and usage of the MSR shall not impede customer boarding or flow in any manner. Magnetic card insertion, swipe through and removal by the customer shall be in the general flow of customers boarding the bus 3. Cards shall be read on first proper insertion with an accuracy of not less than 99.0 %, assuming each card is valid, is fully inserted such that all coded information passes across the read head, and the card is not damaged sufficient to destroy the ability of the MSR to correctly read the coded data. 4. If a card is not valid for the current class of service, the farebox shall display the amount to be inserted by the customer. Additionally, the farebox shall accept and separately register additional cash fare payments in accordance with the fare structure. Registration of additional cash fares shall cause the card to be accepted without requiring the bus operator to push a button. This cash data shall be accumulated in a separate register. 5. The card read head assembly shall be held in place by not more than two (2) readily accessible fasteners. Electrical connections shall be plug -in and screw type connectors, or equivalent, approved by County. A trained maintenance technician shall be able to replace the read head assembly within five (5) minutes. 6. The MSR shall be capable of operating under the same environmental conditions as the fareboxes. The MSR shall not encode any data on the card read but shall be a read -only device used for reading information encoded on cards. B. Visual and Audible Indicators The OCU display shall allow the bus operator to monitor magnetic card activity as required, indicating the type of transaction being conducted, any problems or other messages. Page 32 of 79 16A 8 2. In event of a challenge between the bus operator and customer regarding the use of magnetic card or cash deposit, the bus operator may depress a button to retain the information on the OCU display. 3. For each card accepted by the farebox as a valid fare the farebox shall sound a tone indicating that a proper fare has been paid. A recognizably different tone shall be sounded in event the transaction is refused by the farebox and the OCU and customer display shall indicate "INVALID" and additional information to explain why C. Passback Protection 1. Passback protection shall be provided as specified elsewhere in these specifications. D. Data Encryption 2. Magnetic stripe data shall be encrypted to provide for data security. The security scheme used shall be presented and explained at the PDR and finalized between the Contractor and County at CDR. 4.12 Magnetic Stripe Farecard Stock A. The magnetic stripe farecards shall be the standard credit ticket size of 2 -1/8 inches by 3 -3/8 inches. The magnetic stripe shall be 1/4" wide, located 3/8" from and parallel to one long edge. Manufacturing specifications shall define farecards that are fully compatible with the farebox equipment. B. All magnetic media shall utilize high coercivity magnetics of not less than 2,000 oersteds. 4.13 Interface For Connections To On -board Systems The farebox shall be capable of connecting to other devices on the bus over industry standard interfaces including SAE J- 1708/J -1587 and SAE J1939. These other devices include CAD /AVL system to be installed by Avail Technologies. The on -board interface with Avail Technologies shall allow the following: 1. Single -point operator logon (using operator ID and run ID) and logoff via MDC 2. Accepting run, route, trip and operator information provided by MDC 3. Sending farebox alarms to MDCs 4.14 System Security A. The fare collection system shall incorporate the highest level of security in order to ensure that all revenues inserted into the farebox are securely deposited into the cashbox. In addition, the system shall provide for secure transportation and collection of all deposited funds from the time the cashbox is removed from the farebox to the time the monies are counted. B. The goal of the fare collection system is to provide for the secure collection and transfer of all deposited revenues and to provide appropriate alarms under those circumstances when there is risk of revenue leakage by means of data manipulation or by unauthorized access to the cashbox, including the potential unauthorized use of keys during the revenue collection procedure. A. The system security shall employ software controls, monitoring, security interlocks and other similar subsystems and controls to achieve these goals to the highest degree. Hardware and /or software security provisions shall be provided for the following: 1. Access to Cashbox Interior - Each cashbox shall be provided with a high security lock to inhibit unauthorized access to the contents of the cashbox. 2. Access to the cashbox within the farebox shall require the downloading of data prior to unlocking the cashbox access door. Download shall be via tethered probe or optional wireless means. 3. Access to the contents of the cashbox from the top of the farebox shall be prohibited when the cash processing modules are properly in place. When these modules are removed or not installed properly, an alarm message shall be created and transmitted via the Avail on -board system to the central dispatch workstation. Page 33 of 79 16A 8 4. Unique alarms shall be created for the following events as a minimum: a) When the cashbox emptying time exceeds a preset limit (settable from 5 seconds to 5 minutes in one (1) second increments). b) When the top cover of the farebox is opened, whether in service or not. c) When the cashbox access door is opened and when it is closed while in service. d) When the time that the cashbox access door is open exceeds a preset limit specified elsewhere herein. 4.15 Equipment Construction A. This section describes the general constructional requirements to be included for the on -board fare collection equipment. 1. Mechanical Details a) The farebox and its mounting fixtures shall be constructed in a manner to discourage vandalism and theft. Finishes shall resist corrosion, abrasion and scratching. All exterior surfaces shall be clean with all corners rounded. There shall be no exposed bolt heads, nuts, sharp edges or cracks on the outside surfaces. b) The upper portion of the farebox shall be made of brushed or satin finish stainless steel, not less than 14 gauge, suitably reinforced for rigidity, and with no external and /or removable fasteners that provide access to the interior of the farebox. County will review other revenue service - proven materials proposed to determine their suitability and provide the appropriate approvals. c) A top assembly shall be provided on the upper portion of the farebox which shall serve as the bezels for the entry of coins and bills, the slot for the MSR and to provide primary maintenance/ inspection access to the interior of the farebox. This assembly shall have two (2) entry slots for cash, one (1) for coins and one (1) for bills. The top casting material shall be aluminum or stainless steel, with minimum wall thickness of 1/8 inch and suitable reinforcing ribs for added strength. d) The coin slot shall be used to direct inserted coins into the farebox and shall be sized no larger than a dollar coin. Its design shall be such as to deter the entry of paper and lint into the coin slot and the formation of coin jams. e) The bill slot shall have a protruding lip to assist in the sliding of the bill into the slot. The casting shall be painted with black epoxy enamel or powder- coated, over a suitably cleaned and primed surface. The surface of the casting shall be free of chips, blisters and other imperfections which lead to chipping of paint or unattractive appearance. f) The top casting shall have affixed to it, by means of high yield adhesive, multi-color decals which indicate the function of the respective card, coin and bill slots and provide instructive information as to their use. These decals shall utilize different colors than the top casting and shall be subject to the approval of County. g) The top assembly shall be secured to the farebox upper portion by means of a continuous hinge and high security lock. h) For maintenance purposes, additional maintenance access doors may be provided to permit access to the interior of the farebox. If it is possible to get access to any revenue by opening any maintenance access door or assembly, the operation of other maintenance access door(s) shall be interdependent upon the authorized opening of the top assembly, with interlocks provided to assure that these doors/ panels are not left in the open position when the top assembly is closed and locked. i) The lower portion of the farebox shall be made of stainless steel. The material shall be not less than 14 gauge, reinforced for rigidity. A revenue access door shall be provided to Page 34 of 79 16A 8 protect and conceal the cashbox within the farebox. This door shall have high strength components to protect the cashbox from unauthorized entry including a high security electronic lock mounted in a secure location. The farebox shall have a provision to allow employees and managers to determine that the cashbox is present and open to receive revenue. The design shall be such that there shall be no gaps allowing prying the door open 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. j) Keys and /or locks which 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. The cashbox door shall not close if the cashbox is improperly aligned. k) Wires and cables which are run through the lower portion of the farebox to the upper portion shall be run in a protected channel and /or raceway. No wires shall be visible when looking at the cashbox cavity. 1) A base plate shall be used, and shall be affixed to the lower portion of the farebox to permit mounting to the bus floor. The dimensions and construction of this base plate shall provide the necessary lateral stability, without secondary anchorages. The base plate shall be affixed to the floor by means of "carriage bolts" from the interior of the bus, with the washer plates and nuts on the underside of the floor. The base plate material shall be cast aluminum or stainless steel, with reinforced metal deposits surrounding each bolt hole for maximum strength. If a base plate is not used, the mounting of the farebox shall be by internal means utilizing four (4) high yield bolts. The lower part of the farebox shall be suitably designed and reinforced to prevent deformation or wear in service, oxidation, deterioration or accumulation of tolerance which might allow the farebox to be subjected to increased vibration, wear, metal fatigue or other degradation. m) The upper and lower portions of the farebox shall each be securely fastened together by means of high yield bolts, accessible from the interior of the farebox. The completed assembly shall measure not less than thirty-one inches (31 "), and not more than forty-one inches (41 ") high, as measured from the bus floor, and not more than eleven inches (11 ") in cross section, excluding the mounting base plate. (In certain classes of buses, it may be necessary to exceed this height to allow for comfortable operation of the farebox by the bus operator. Such buses are to be identified by the Contractor, and the Contractor shall propose an alternative means for mounting the farebox, which shall be subject to approval by County prior to completion of the CDR. n) The coin unit shall be modular in construction so as to be removable within one (1) minute for inspection and/or replacement. The coin unit and any materials thereon shall be fastened by mechanical devices. Adhesives requiring scraping and cleaning with solvents shall not be used. The farebox shall have a guide chute integral to its construction to guide the coins into the cashbox. There shall be no protrusions on which coins can snag, causing a jam. o) The bill transport shall be a self - contained module which may be removed and replaced. It shall be built of reinforced materials for rigidity, provided with captive fasteners and be self - aligning upon insertion. It shall be capable of being locked within the farebox. The farebox shall have a guide plate integral to its construction to guide the bills into the cashbox. There shall be no protrusions on which bills may snag, causing a jam. p) All major subassembly modules shall have a unique serial number inscribed or permanently applied. No two (2) serial numbers shall be the same on any two (2) modules of any type. County shall be provided with a list of all serial numbers and the modules to which they have been applied prior to installation of any item of equipment. Subassembly Page 35 of 79 16A 8 modules to which such numbers shall be applied shall include, but not be limited to, coin unit, bill transport, electronic lock, cashbox, upper case, lower case, TPU and MSR. q) Approvals shall be explicitly requested of County by the Contractor for use of any alternate composition materials in place of materials specified herein. Any such approvals shall include revenue service experience in similar conditions. Failure by the Contractor to request the necessary approvals shall deem those not identified by the Contractor as materials unacceptable for this project. r) A baffle system in the coin chute shall be employed to prohibit access to or "fishing" of coins from the cashbox upon removal of the coin unit from the farebox cabinet. s) A baffle system or other mechanism shall be employed to prohibit access to or "fishing" of bills from the cashbox upon removal of the bill transport from the farebox cabinet. 2. Electrical Details a) The electrical termination of the farebox, for purposes of connecting it to a power source shall be by means of a polarized, snap connect plug on the underside of the farebox. b) The electronics shall be of the solid state type, assembled on reinforced printed circuit boards. These boards shall be modular (plug connected) and removable for inspection and /or maintenance. The components mounted on the board shall be soldered in place, or for those items to be readily removed, high quality sockets with retainers shall be used. c) All major electrical/ electronic subassemblies and devices shall be interconnected by means of polarized positive plug connectors with self- locking retaining features to assure proper connections and preclude intermittent performance due to poor contacts. All plug -in components shall be retained with a positive force holding them in position to ensure they do not work loose with the vibration that can be expected in the buses. d) Wires and multi- conductor cables, where used, shall be color coded and /or marked to permit positive identification. It shall not be possible to improperly insert a plug -in component into a connector. e) Display characters shall be of high intensity type viewable through a range of not less than a sixty degree (600) arc when mounted within the farebox cabinet, and have a rated life of not less than 10,000 hours of operation without segment failure. f) Fuses, circuit breakers or other protective devices shall be employed to protect the electronics, motors and other components from overload and damage. Where used, they shall be accessible without disassembly of components. Location shall permit inspection and /or replacement through normal maintenance access doors or panels. g) A master "disconnect" switch shall be provided, internal to the farebox to disconnect the farebox and OCU from the incoming power supply. This switch shall be identified and marked, and be of the two (2) position type. h) The farebox power supply shall be large enough to provide adequate power to the various farebox components and provide additional power for the electronic memory, MSR, TPU and OCU. i) The complete loss of power to the farebox shall not cause any information or data contained in electronic memory to be lost or altered. The electronic memory logic shall be capable of maintaining electronic memory without bus power for a minimum of one (1) month j) The farebox electronics and logic shall be protected against stray electro- magnetic interference (EMI) radiations, vibrations, ultraviolet light, or other environmental conditions which would cause the farebox to become inoperative and /or lose the data contained therein k) Where electronic circuit boards are employed and where they are to be inserted and/or removed by means of board guides, they shall be provided with lifting tabs. Page 36 of 79 16A 8 1) All circuit boards shall be provided with polarized plug connectors. No harness wiring shall be directly connected by means of solder to any board which shall be removed for maintenance or inspection. m) All circuit boards shall be factory pre- tested for a minimum of seventy -two (72) hours prior to their final inspections within a given farebox. n) All electronic displays shall be tested for all segment functions for a minimum of forty eight (48) hours. o) The arrangements of the electrical and electronic components shall be such as to permit adequate ventilation to disperse the heat created and to preclude degradation of components and performance. p) Access to the electronics, power supplies, and other electrical components for maintenance, replacement or repair shall not require the removal of the cashbox from the farebox or the removal of the farebox from the bus. q) The farebox circuits shall be designed to draw minimum power from the bus battery. The farebox shall incorporate the following power levels: • Normal operation during which time operating power required shall be five (5) amps or less. • Idle mode which shall be activated upon time out of the predetermined interval timer. During the "Idle" mode the OCU shall provide a visible indicator, such as a blinking character, and the coin and bill entry light shall remain illuminated. The farebox shall be ready to collect revenue. r) The above electrical requirements shall apply to all modules connected to or contained within the farebox, including the TPU, MSR and OCU. 4.16 Cashbox Requirements A. Physical Cashbox Criteria 1. The cashbox shall be made of plated or stainless steel, 20 gauge minimum. It shall be a welded construction with no external fasteners exposed which affect security. Those areas of the cashbox which come in direct contact with the farebox shall be abrasion resistant. Neither insertion into and /or removal of the cashbox from the farebox in revenue service operations nor vibration or shock experienced while the cashbox is in revenue service in the farebox, shall cause any distortion of the cashbox material, which may adversely affect its ability to function properly. County will review other revenue service- proven materials and designs proposed to determine their suitability and provide the appropriate approvals. 2. The cashbox shall be constructed in a configuration to fit within the dimensions of the lower portion of the farebox. The cashbox shall have two (2) individual separate compartments to receive and retain coins and bills, each in their respective compartments. 3. The cashbox, when empty, shall weigh no more than twenty (20) pounds. It shall be provided with a handle or handles to allow it to be safely carried by a person with gloved hands. 4. A permanent serial number shall be securely affixed to the cashbox where it will be visible when the cashbox is in the farebox and the farebox door is closed and locked. B. Coin Mix Definition 1. Whenever there is a reference to and /or requirement for "mixed coin ", the following mix of coins in multiples or fractions shall be used: C. Bill Mix Definition 1. Whenever there is a reference or requirement for "bill validation" the term shall refer to the acceptance and condition of 100 bills in multiple or pro -rated quantities which are to be fed into the Page 37 of 79 ITOIW,OO farebox in a flat, unfolded condition. For performance and testing purposes, the ability to accept and validate the following mix of bills for each denomination shall be demonstrated at the First Article Test: All bills shall be dry and not mended (not taped), and folds shall not exceed 1/16 of an inch in diameter. The circulated and worn bills shall be drawn from the revenue collected by the present County fareboxes as follows: Coin Mix Definition Penny $0.01 100 $1.00 Nickel $0.05 100 5.00 Dime $0.10 250 25.00 Quarter $0.25 240 60.00 Half Dollar $0.50 2 1.00 SBA $1 $1.00 5 5.00 Sacagawea $1 Coin $1.00 10 10.00 Total US Coin 5 707 $107.00 A. Cashbox Configuration 1. Cashboxes shall have the capacity to hold and completely transfer to a receiver vault $500 in mixed coin and 700 bills in unfolded "street money" (not "brick" or mechanically stacked or compressed) bills, or paper equivalent. 2. The operation of the cashbox shall be such that the cashbox is in a closed and locked condition whenever the cashbox is removed from the farebox. When the cashbox is out of the farebox it shall be able to be opened only with the valid revenue key. 3. The 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 therein, during any portion of the collection or revenue transfer cycle. Bill Mix Definition New, uncirculated bills: No folds 5 1 fold halves 5 2 folds thirds 5 2 folds fourths 5 Circulated bills (not torn or limp): No folds 10 1 fold halves 20 2 folds thirds 15 2 folds fourths 15 Worn bills (small tears and limp): No folds 5 1 fold halves 5 2 folds thirds 5 2 folds fourths 5 4. The cashbox shall fit into the farebox only in a singularly correct position. The farebox shall remain inoperable until the cashbox is inserted and ready to accept revenue, and the cashbox access door is closed and locked. Page 38 of 79 16A 8 1 5. The cashbox shall not have removable lids, covers or other elements which may be detached from the cashbox. The cashbox shall be automatically locked and sealed when removed from the farebox. 6. The locks (and keys) used on the cashbox shall be of the high security type as specified herein. The operation of any keys within the locks shall not require excessive torque, which may damage either the key or the lock. 7. The mechanism employed to open and/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, locking feet and other elements that are required to release the cashbox from the farebox or to lock it in place in the farebox. Aluminum or plastic components are examples of materials that shall not be accepted. 8. The interior of the cashbox shall afford complete gravity discharge of coins and bills in the revenue transfer cycle, while maintaining their separation. No ledge or other areas shall be present where coins may lodge and impede the operation of the cashbox. 9. The materials and construction techniques shall be such that a fully loaded cashbox, if dropped in the upright position to a hard floor and landing on its bottom or bottom corner from a height of forty-eight inches (48 "), shall suffer no operational impediment or security breach. The farebox and cashbox shall not be distorted when carrying a full revenue load. 10. Metal parts not constructed of stainless steel shall be painted, plated or constructed of corrosion resistant material. 11. The farebox /cashbox shall be designed and fabricated in such a manner as to prevent extensive tolerance buildup and resultant vibration which could be detrimental to the proper operations of the farebox or cashbox in service. 12. The cashbox shall function in a dependable manner in the operating environment of the transit system. It shall be capable of operation for two- thousand (2,000) days, mean time between failures. B. Cashbox Construction 1. The cashbox and farebox shall be fitted with devices to determine and report that the cashbox has been properly inserted into the farebox so as to allow the revenue access door to be fully closed and locked plus the cashbox has been opened (in place) and is ready to receive revenue. The devices used shall be tamper resistant, solid state and not subject to malfunction due to bus vibration. C. Cashbox Identification 1. The cashbox shall provide the ability to automatically read and transmit a four (4) digit (minimum) serial identification number of the inserted cashbox that shall be read by the farebox once the cashbox is locked in the farebox. END OF SECTION V. REVENUE COLLECTION VAULT SYSTEM AND AUDIT UNIT 5.1 General and Equipment Configuration A. The revenue collection vault system (RCVS) shall provide for the secure transfer of cashbox revenue into revenue collection vaults. B. The cashboxes shall be inserted into the cashbox receiver located above the revenue collection vault and the cashboxes shall empty all of their contents into the vault. C. The cashbox receiver and revenue collection vault shall be of heavy duty construction. D. All openings and high wear areas shall be constructed to be durable and able to accommodate rough handling. Page 39 of 79 16A 84 E. The system shall track the cashboxes that are emptied into the revenue collection vault and shall provide means for the reconciliation of revenues collected. F. The cashbox receiver components shall operate reliably and perform all functions without difficulty and last a minimum of ten (10) years in the environmental conditions existing at the CAT facility. This shall include moisture and wash water spray, humidity, airborne dust and bus exhaust, temperature extremes, electromagnetic interference and grounding factors. 5.2 Cashbox Receiver A. The cashbox receiver shall employ a door that is opened to receive the cashbox. After the cashbox is inserted into the receiver in the correct orientation and the door is closed and locked, a crank or similar mechanism shall be utilized to open and empty the cashboxes in a secure manner. B. The receiver shall be interfaced to the FCMRS and shall read and report the cashbox serial number automatically read from the cashbox. Cashbox serial number shall be forwarded to the FCMRS only if the emptying cycle takes place and is successfully completed. C. The cashbox receiver design shall provide a secure interlocking of shutters sealing off the receiver from the revenue collection vault's bill and coin storage areas such that access is prevented to these areas when: (1) the door is open and, (2) there is no cashbox within the receiver. D. The emptying mechanism shall not be able to be turned partially and returned to the starting position. When the cashbox is inserted, it shall be required to fully complete the emptying cycle before the cashbox can be removed. E. The emptying cycle shall be completed and the cashbox lid closed and locked before the cashbox receiver door shall be able to be opened. F. The cashbox receiver shall incorporate three (3) indicators to visually identify the current status of the cashbox receiver 1. One (1) indicator that the emptying cycle is taking place 2. One (1) indicating that the cycle is completed. 3. One (1) indicating that the receiver bin is full or not in place and the door shall not open. G. The cashbox receiver shall only operate - door close, perform emptying cycle, door re -open - when a cashbox is placed properly and securely within the receiver. If a cashbox is not properly in place, the door shall not close and the emptying cycle shall not commence. H. The emptying cycle shall be completed in no more than ten (10) seconds to completely empty the full cashbox. I. The openings into which the cashboxes are inserted shall be constructed of materials able to sustain high wear resistance and shall be durable under rough handling. J. The cashbox receiver shall be protected by a door to deny access to the receiver opening and shall provide manual locking means for security purposes when the receiver is not being employed for revenue servicing. K. Keys and locks which are retained in the receiver lock cylinder and used to interface with the cashbox shall be securely fastened and shall be accessible and removable only in an authorized manner. L. Guides shall be employed within the receiver cavity to assure that the cashbox is in alignment for proper operation. 5.3 Revenue Collection Vault A. The design of the revenue collection vault shall take into consideration strength and security requirements so as to resist forced and unauthorized entries. Page 40 of 79 16A 8'i B. The openings in the receiver into which the revenue collection vaults are inserted shall be constructed of materials able to sustain high wear resistance and shall be durable under rough handling. The lower portion of the receiver shall have steel guides, constructed of durable steel, to properly position the vault below the receiver. C. The cashbox receiver shall be protected by a door to deny access to the receiver opening and shall provide manual locking means for security purposes when the receiver is not being employed for revenue servicing. D. Hinges shall not be exposed and there shall be no pry points available for forced entry. E. The vault shall contain two (2) storage areas: 1. Coins shall be stored in one (1) area with a capacity of $10,000 in mixed coins. Coins shall be stored in a sealed compartment within the vault cabinet with a high security locked access cover that is designed to facilitate the controlled release of coins directly into the coin counting machine. The coin compartment shall have a smooth sloped bottom to allow the coins to discharge under gravity. 2. Bills shall be stored in a separate area with a capacity of 10,000 bills. Bills shall be stored in a removable bin completely within the vault cabinet and locked in place with a separate high security lock. A method shall be provided for easily removing collected currency from the revenue bin when this function is performed in a secure location. F. High security looks and an interlocking mechanism shall be employed to provide access to the receiver for maintenance purposes. 5.4 Audit Unit A. An audit unit shall be provided to permit the emptying of a single cashbox for audit purposes. B. The audit unit shall weigh not more than 200 pounds when empty and shall be mounted on wheels to permit ease of movement. The top portion of the audit unit shall incorporate a cashbox receiver to accept cashboxes for emptying. C. The audit unit shall contain two (2) compartments - one (1) for coins and one (1) for bills. The audit unit shall have capacity of not less than 1,000 bills and $1,000 in mixed coins. D. The audit unit shall be a stand -alone unit and shall not communicate with the FCMRS, unless so designed to improve the security of the cash handling procedure. 5.5 Locks and Keys A. All locks and keys used on the farebox and the revenue collection equipment shall be of the security type, Medeco or approved equivalent. Lock combinations and keys for all identical functions shall be keyed alike. Different combinations shall be provided for each function as detailed in the following table, where locks that are keyed alike have the same key type letter. All keys and spare locks shall be delivered to the CAT General Manager. Lock Location ' Key Type Retentive Receiver Mobile Vault Cover Door A Yes Receiver Door B No Receiver Service Doors C Yes Receiver Service Door Rear C Yes Farebox Cashbox Revenue Access D Yes Farebox Top and Maintenance Access Doors E No Mobile Vault Coin Compartment F Yes Mobile Vault Banknote Compartment F Yes Audit Receiver F Yes Page 41 of 79 16A 8 Cashbox receivers shall open the cashboxes via a cashbox key mounted in the back wall of the cashbox receptacle. Cashboxes secured within a farebox shall open via a cashbox key mounted in the back wall of the cashbox receptacle in the lower portion of the farebox. The cashbox shall only be able to be inserted in a singularly correct position in the farebox and cashbox receiver, and shall easily be placed into the ready position to transfer revenues. The cashbox insertion and removal procedure shall be designed to positively guide the cashbox into and out of the farebox and cashbox receiver. END OF SECTION VI. FARE COLLECTION MANAGEMENT AND REPORTING SYSTEM 6.1 General System Description A. General The Contractor shall host the FCMRS at its facility (please see Sections 2.1 and 5.1 [C]) for hosting requirements). The FCMRS shall communicate with the fareboxes to extract transaction and event data and download operating parameters and related information. The FCMRS shall communicate with the vault to extract cashbox identification from cashboxes inserted in the receiver. The FCMRS shall be complete and fully functional, with all necessary items of hardware and software installed and tested, and shall be furnished with such software licenses as may be required. The FCMRS shall include data probes linked to the database server identified in section C. The FCMRS shall be capable of generating comprehensive management reports for use by County. B. Application/ Database Server Hardware Requirements- Proposers shall describe the infrastructure to be used for hosting FCMRS for County. Please refer to the Appendix section for general IT requirements. Further specific requirements regarding the FCMRS application are as follows: 1. Workstation Connectivity to the Application/ Database Server -- The FCMRS application (including configurable security levels allowing full functional configuration ability and reporting) shall be accessible from existing computer County CAT workstations via a secured web -based interface (e.g., via Hypertext Transfer Protocol Secure [HTTPS]) and /or a client /server type configuration over secured network connection (e.g., web access via virtual private network [VPN]) which is compliant with County's IT requirements provided in the Appendix section. The vendor will train County to configure and support FCMRS access on County CAT workstations. Further, County shall be able to use currently installed network printers for printing information from FCMRS. 2. Operation of the computer to generate data system reports shall not prevent Revenue Servicing pra n of the fareboxes. The hard disk drive shall be capable of storing all of the data from up to 50 fareboxes with maximum route /run records. As new farebox records are added, the oldest records on the disk drive shall be automatically deleted. County shall be able to specify how many days of detailed data and months of summary data shall be saved. 3. The FCMRS shall be written in a standard, commonly available computer language not proprietary to this application. All communications shall be accomplished using standard networking protocols and hardware. The FCMRS shall utilize a relational database management system (RDMBS) [e.g., Microsoft SQL Server] which shall provide open database connectivity (ODBC) capability to third party tools/ applications for custom reporting or other purposes. 4. The FCMRS server shall be installed with redundant power supply and hard -drive configurations. Further, the FCMRS application shall be hosted in a high - availability configuration such that a secondary instance of FCMRS is immediately available to County in the event the primary FCMRS application fails. All data must be protected in the FCMRS database in the event of an application crash. C. System Operation -- The data collection and reporting system shall be configured in the following manner: Page 42 of 79 16A 8 D. Wireless Data Communications - In place of the "tethered probe' functionality that was specified, the proposed Fare Logistics' TransFareTM solution employs a secure bi- directional process utilizing state of the art wireless communications technology. The data communications process for either an upload and/or download data between the Farebox and the back -end central data system is designed to be automatic. The communications function commences once a bus travels into the range of a TransFareTM wireless access point, and successfully authenticates a login. The Voyager Electronic Validating Farebox software is programmed to initiate the upload and download of Farebox data, software and configuration files. The average download for a day's worth of transactions is completed in less than one minute. Furthermore, valid transaction files are automatically imported into the TransFareTM database; however this process requires the central server to be a node on the same network as the wireless access point. DR Wr. IM, WIN", 1000 HIM 2L.1. Computer Operations -- If the data computer had been previously shut off, it shall automatically load the proper software upon power up and prepare itself to process data without further attention from the operator. The data system shall then be left for automatic operation. The password used to get access to the application menu shall be changeable by means of a higher level password. The system shall have the capability of recording and reporting, upon interrogation by a user with a high level password, all uses of passwords for the previous 60 day period, the date and time of password use, the amount of time the system was in use with the password, and what reports or other functions were accessed. If it becomes necessary to change the high level password in the computer for security or operational reasons, it shall be readily accomplished via the operator keyboard. It shall be possible to use the data computer to change the fare tables in all fareboxes probed at the garage. These changes shall include the full fare value and the values and function of each driver pushbutton. In addition, the time of day shall be transmitted to correct the farebox clock if required. At County's discretion, changes to the fare tables and farebox clock shall be downloaded to each farebox automatically during routine prelin gRevenue Servicing activities. All operator entries shall go into a transaction log capable of being printed on demand. Software shall be available in the data system to allow backup and retrieval of files. Software shall be available in the data system to allow archiving of transactional data as needed. X2. Access to Computer Reports -- Both summary and detailed farebox data shall be stored on a password - protected database server to ensure that the original revenue and ridership data cannot be modified. This data shall be capable of being converted to a comma - delimited ASCII file format for export to third -party software. Software shall be available in the data system to allow backup and retrieval of files. The data system shall have multitasking capability and shall be able to accommodate wireless data transmission, pig report generation, and other tasks simultaneously. Lockup of one task shall have no effect on concurrent tasks. Wireless dPata transmission shall not be slowed due to operation of concurrent tasks. 43. Fare Table -- The data system shall have the capability of changing the fare tables in the fareboxes per the procedure previously described. Each fare table assigns the value of a full fare as well as any reduced fares (student, elderly, etc.). Each individual fare amount may be between $0.01 and $99.99. Page 43 of 79 16A 8 It shall be possible to change the values through the farebox keypad or data system without removing or replacing any of the farebox electronic components. In addition, the following shall be transmittable: a) Current time and date (any valid time and date) b) Electronic lock code (any five digit number) c) Start/ stop times for AM and PM peak periods d) Keypad attributes (tally, tally /clear display, and value increments from 0.01 to 99.99) e) Fare table store option (the data system should transmit the fare structure to each farebox abed) pf g}D-Transfer acceptance parameters h)4_Tickets / Tokens/ Passes acceptance parameters and other attributes 4. Configurable Parameters The data system shall have the ability to enable or disable various functions such as ticket types, or other designated parameters as previously defined in this document. 6.2 Standard Reports The following standard reports, at a minimum, shall be available from the data system. All reports shall carry the CAT name, the date or period for which data is reported, and the date on which the report was generated and printed by the system. All reports shall be generated through "user friendly" menu - driven software. A. Individual Farebox /Bus Reports 1. For individual farebox reports, the printed report shall show the following categories of data at minimum: • Current revenue (sinee last pf eb4ig) • To -date revenue • Unclassified revenue • Total full fare riders (ridership data shall be supplied for each fare table in use) • Total number of riders at each fare level • Tickets /Tokens /Passes • Total tokens • Total stored ride /value cards • Total passes • Total bills • Total coins by denomination • Technical Maintenance Reports • Bus Farebox Maintenance History 2. The first line of each individual farebox report (the "master list ") shall indicate the date and time of day the farebox was probed and the bus number and farebox number. Cumulative totals for the activity of that farebox b shall be printed, corresponding to the column headings. Page 44 of 79 16A 8 3. Trip -by -trip route /run data lists shall be printed next, following printing of the master list. Each route /run record shall be printed in the order in which it was created, along with notations of driver or route number(s) and the time the record was created. It shall be possible to transcribe this data from hard disk to other electronic storage medium for archiving or analysis purposes. B. Daily Summary Report The daily summary report shall be printable, on request, at the end of the operating day. County shall have the ability to designate the end of the operating day as any time from 12:00 A.M. to 5:00 A.M. so that all buses that have operated on a given day shall be accounted for, regardless of whether they are probed after midnight. The daily summary report shall contain the same data categories listed above, less any that may be inactive or suppressed. Summary totals from master lists from all fareboxes revenue serviced that day shall be provided. Route /run data shall not be provided. The full matrix of fare tables (excluding any inactive or suppressed tables) shall be printed showing the cumulative total ridership in each cell of the matrix. The daily summary report shall also provide a report of total daily ridership. The daily summary report shall print a summary of the data from the exception report, indicating the total number of buses revenue serviced pfebed-ai+d not pr-ebed , security door and cashbox alarms, bypass alarms, maintenance required (including power supply), memory cleared, unknown driver, unknown bus, unknown route, unknown run and other anomalous data from the exception report. A list of the buses not revenue serviced, by bus number, shall also be printed. C. Periodic Summary Reports The data system shall have the ability to generate summary reports for specific periods, as follows: 1. Monthly Summary Report: This report shall summarize all activity fleetwide for a given month. Monthly summary information can be saved for up to 128 months. Totals shall be given for all active pre -sets and keys, revenue, tokens, bills, fare document types, etc., by day and totaled for the month. It shall be possible to print bar charts giving total revenue by date and total ridership by date. Annual Summary Report: This report shall summarize the information given in the monthly summary report and give totals by week, quarter and year to date. It shall be possible to show each value of revenue, pre -set and key plotted by week in a separate bar chart. 3. Daily Route Summary Report: This report shall summarize all totals by route for a given day fleetwide. 4. Monthly Route Summary Report: This report shall summarize all totals by route for an entire month. 5. Route /Sum Report: This report shall allow data daily or over a period of time to be sorted first by route, then by run, or by time /date. Ridership shall also be calculated and printed. For each route printed, the number of route run records included in the summary shall be indicated. The data in the route /run reports shall be based on when the route /run record was actually created (actual date and time), regardless of when the bus was revenue serviced and data was downloaded. D. Exception Report It shall be possible to generate a daily exception report listing operator entry errors (invalid route, run driver or trip numbers) as validated against lists of valid numbers maintained by the data system. 2. Security Reports The data system shall have the ability to generate security reports, which shall indicate all cashbox, door open and memory clear alarms. For each alarm, the time of day and the bus number shall be indicated. For the security door and cashbox alarms, the report shall also indicate the amount of revenue that was in the cashbox at the time the alarm was generated. 3. Editing Data Page 45 of 79 16A 8 It shall be possible to edit data in the data system in restricted ways. In order to preserve the security of the data system, only operator entries (route, run, driver and trip numbers) shall be changeable. 4. Transaction Log A transaction log shall be maintained in the data system computer. The transaction log shall maintain a record of all uses of passwords to access reports, the reports accessed, the time of log on and log off, etc. In particular, all editing of data in the system shall be recorded in the transaction log. The transaction log shall maintain this information for a minimum of 60 days. It is not to be subject to editing by users through any Contractor data system software. 6.3 Transactional Database and Reporting A. The farebox and data system shall be equipped with the software necessary to support a transactional database in which selected farebox transactions and /or events shall be individually time- stamped and recorded in farebox memory for uploading to the data system during routine Revenue Servicing activities Wig. At the option of County, the transactional database shall be capable of recording: 1. Events only (e.g., farebox pFebe Irevenue serviced, cashbox door open, route /run record created) 2. Events and non -cash fare transactions 3. Events and both cash and non -cash fare transactions. B. The transactional database shall have the ability to capture the serial number of the card used in each transaction and report it to the data reporting system. It shall be possible to track all uses of a given card, category of card, or employer account for any time period, route, etc. This information may be used for audit and security purposes, especially where high -value cards or credit card acceptance is implemented. C. Each transaction shall be individually recorded in such a way that it is possible to determine day, time, route, run, latitude, longitude and stop ID for each fare paid. D. The transactional database shall be in a format that allows interfacing to the ODBC (Open Data Base Connectivity) standard, thereby making it possible to work with the database using ODBC - compliant third -party query and report generation tools. E. To maintain the security of the database, all database transactions shall be logged. Data shall be stored in a format that is not alterable by general database tools. The software driver for the ODBC interface shall be configured in read -only mode and shall not allow the user to modify revenue data directly. F. The transactional database shall be capable of storing the following types of transactions: 1. Cash fare; includes fare type (full fare or pushbutton), plus time (minutes and seconds), latitude, longitude 2. Period pass; includes serial number, time, latitude, longitude 3. Stored value card; fare deducted, remaining value, serial number, time, latitude, longitude 4. Stored ride card; remaining rides, serial number, time, latitude, longitude 5. Transfer accepted; Route, direction, serial number, time, latitude, longitude 6. Transfer issued; Key used to issue, time, latitude, longitude 7. Non - magnetic ticket or token processed; time, latitude, longitude 8. Credit & Debit Cards; latitude, longitude 9. 3rd party ID cards (e.g., a college ID card); latitude, longitude G. For period pass transactions, the database shall be capable of storing the following information at minimum: Page 46 of 79 16A 8 1. Pass serial number 2. Pass type 3. Passenger category 4. Employer account number if applicable H. Other data fields shall be provided to permit recording of peak /off -peak usage. END OF SECTION VII SUPPORT SYSTEM EQUIPMENT 7.1 Per-table Data Unit the felleiving functio n n I highlighted the seleet one (1) of �Pf a-41f; Review last data-. 11se 1 1 1 1 11t i l:ties Log cif. Using the the r data t-r-anss-fe-F r with dese--A-h-ed- seleetion the as PD-1-1 same seeur-ity methodology as data ftOfn th-a-m tiventy ffl-efhed- five above, ext-r-aid all the 44 off-M—Aien the StWed a single -i-n -ne- ffl-efe (25) seeonds and StOFe the faFebo* on data be r 42 r shall fese 242 the PE)U is to download the faFebox data. A be to indieate the used times that the PPU has been used tO Fead An event r similar register- data ftffin a farebox. shall r plus date and provided time, shall number o alsse- be stered in the Revenue Processing Terminal A. A method for revenue tracking shall be furnished to provide County with the ability to track all revenues received and reconcile the registered revenues against the counted revenues on a vault basis. For this system, a terminal shall be provided in the Money Room supervisor's office interfaced to the FCMRS for transfer of the manually entered count data. B. The Money Room supervisor will sign on to the terminal to enter the count information. The date, vault location and vault number shall be entered into the terminal. The counts from the bill and coin counting Page 47 of 79 16A 8 equipment shall be entered into the record and the record shall be closed when all fields have been populated. C. Entry of the count information shall be via a form data entry interface, with the cursor automatically moving to the next field after a value has been entered into a field. When all fields are completed, the record shall be automatically closed and modifications to that record shall not be possible by a revenue operator. D. The counts for each denomination of bill and coin obtained from the counting equipment shall be entered via the terminal. Fields for manual counts of coins and bills shall be provided and data separately entered to account for money not processed in the counting equipment. This information shall be subsequently used to obtain the difference between the Money Room counts and the registered counts provided by the fareboxes, on a money reconciliation report. This information shall not be displayed to the revenue operator. E. An authorized County user shall be able to add the deposit information to this reconciliation record. The user shall enter the information from the bank deposit slip, and the day or days for which the deposit applies. The system shall calculate the difference in the revenue counted by the fareboxes and the deposited revenues shall be identified in a separate row on a reconciliation report. F. The terminal provided for the Money Room supervisor shall have no local intelligence or data storage capacity. All data shall be stored at the FCMRS. G. The FCMRS shall maintain records of the users who create, access, and modify all revenue reconciliation records. 7.32 Revenue Reporting Requirements A. A database of all data transferred from the fareboxes and the cashbox receivers to the FCMRS, and from the revenue processing terminal to the FCMRS shall be available to County for the production of reports. Menu driven report generation software with the same requirements and characterizes described for the fare collection system data reporting shall be provided to allow the user to design and store an unlimited number of report formats, which are to be used for generation of system reports. B. Every access to FCMRS application from County CAT workstations shall be tracked to be reported for security purposes. This report shall be sorted by FCMRS user (e.g., CAT workstation ID or FCMRS user ID) and shall include all manual activities, each remote terminal (node) and all downloading activities. The time and description of all access at computer shall be reported. All PDU activities shall be similarly reported. The Contractor shall submit all log messages for County for approval at CDR. County has the right to request addition, deletion or modification of any log message in order to meet system requirements. 7.34 Revenue Accounting System The fare collection system shall provide for the automatic reconciliation of registered revenues against counted revenues and provide a summary of the differences. This software shall operate as follows. A. Once the counts for both the coins and bills have been entered and stored for each vault, the FCMRS system software shall automatically compare the counts of the bills (by denomination) and coins (by denomination) and store data for the differences. B. At the end of a day (and also upon request) a reconciliation report showing the differences by vault shall be generated. This reconciliation report shall be provided only through the use of a high level password. The report shall also provide a daily total and summary for all vaults and an overall revenue accuracy figure. C. The FCMRS shall maintain an inventory of the following revenue elements: 1. Vaults and probes. 2. Cashboxes. Page 48 of 79 16A 81 D. The supervisor shall be able to enter the information on the bank deposit slips into the system in order to permit automatic reconciliation of the funds reported by the bank against those entered at the Money Room. This shall be accomplished through a high level function with a special password and user name. 1. A report shall be produced that provides details on the monies collected, counted and reconciled including all cashboxes emptied into a vault and all vaults counted. . E. Summary totals of the registered revenues, by denomination, shall be included for each segment of the report. The level of detail to be provided for the report shall also be selectable by the user. F. The FCMRS shall provide the ability to report the contents of the receiver vaults at the end of the transit day. This report shall include the number and value of bills and coins in the receiver vault. END OF SECTION VIII. TESTING AND ACCEPTANCE 8.1 General A. The objective of the Test Program is to ensure that all equipment furnished under this Contract shall meet all of the applicable requirements specified in this document, including operation under environmental stress conditions. Testing and acceptance shall be conducted to satisfy production and delivery schedule requirements. The tests to be conducted shall be: 1. First Article Test (FAT) - One (1) of each item of equipment to be furnished, including on -board revenue collection and data collection, shall be tested to ensure that all the features and functions identified within these specifications are provided. Successful completion of this test shall be a prerequisite for the production and delivery of the full complement of equipment. 2. Production Acceptance Test (PAT) -The Contractor shall certify when production is completed in order to obtain County authorization for shipment of equipment. The Contractor shall certify that a functional test has been passed prior to shipping any item of equipment. County will identify, when necessary, required modifications to be made and demonstrated before approving release for shipment. 3. Pre - Installation Checkout (PIC) - Five (5) sets of on -board equipment, selected at random, shall be tested with sufficient transactions to verify proper transaction processing and data reporting. Successful completion of this test shall be a prerequisite for the installation of the equipment on- board the buses. In addition, one (1) item of each type of revenue and data collection equipment shall be tested in the same manner to ensure proper collection and reporting of funds. The Network Acceptance Test is considered to be part of the PIC. 4. Installation Acceptance Test (IAT) - Before any equipment is permitted to go into revenue service a functional test shall be performed by the Contractor on each item of equipment that is installed. Satisfactory performance shall be approved by County. 5. In- Service Qualification Test (ISQT) - This test shall run for a period of not less than four (4) weeks and shall verify that the system is operating in a reliable and accurate manner. This shall encompass all fare collection equipment installed at the garage plus the PDU, FCMRS units and the money room terminal. 6. Reliability, Maintainability and Accuracy Test (RMAT) - This test shall run for a period of not less than ninety -one (91) days and shall verify that the complete system is operating in a reliable and accurate manner for all installed equipment. Responsibilities for Testing are identified below: Page 49 of 79 16A 8 First Article Test (FAT) Contractor's Contractor /CAT CAT Production Acceptance Test (PAT) Contractor's Contractor ---- - - - - -- Pre- Installation Checkout (PIC)* CAT Facility CAT Contractor Installation Acceptance Test (IAT) CAT Facility Contractor ----- - - - - -- In- Service Qualification Test (ISQT) CAT Facility CAT Contractor Reliability, Maintainability & Accuracy CAT Facility CAT Contractor Test (RMAT) W 8.3 L:1 * Includes Network Acceptance Test C. The Contractor shall be responsible for preparation of all testing materials and the test script prior to the performance of any tests. These materials will be approved by CAT prior to commencement of the specified test. Methodology A. The First Article Equipment shall be subjected to the First Article Test (FAT) at the factory. This test shall be comprised of the following series of tests: 1. Functional Tests 2. Maintainability Test 3. Interface Test 4. Cycling Test ❖ 5. Dust Test❖ 6. Environmental Tests ❖ 7. Vibration and Shock Tests ❖ 8. Radiated and Conducted Energy Test 9. Radiated Interference Test ❖ 10. Temperature/ Humidity Test ❖ County may grant exemptions for items identified as ❖ above providing that the Proposer can provide details related to all such tests being successfully completed by a certified test laboratory and evidence of a minimum of 1,000 fareboxes in operation for at least two (2) years with more than two (2) transit systems that have a networked operation with a fare collection computer system in operation. B. At this level of testing the first articles shall be representative of the final production items. The purpose of this test shall be to demonstrate that for all items of equipment to be furnished under this Contract, the functions specified in this document will be met. C. Pre - installation Checkout (PIC) tests shall include tests to verify proper functioning and interfacing of the equipment before installation. The PIC tests shall be conducted prior to the ISQT and prior to the fleetwide installation. D. Upon start of fleetwide revenue service, the first seven (7) days shall be considered as the system start- up period prior to beginning the RMAT. The twenty -eight (28) day settling period shall be monitored for equipment performance during the RMAT. The RMAT shall be conducted for a period of 91 days. E. Final System Acceptance shall be a prerequisite for the start of the hardware and software Warranty. Test Program Plan A. For all tests to be conducted, a final test plan shall be submitted for approval by County at least thirty (30) days prior to the start of the FAT. Testing shall not commence until the test plan has been approved. Page 50 of 79 16A 8 B. The test plan and applicable procedures which shall govern the conduct of activity, surveillance, direction and methods of observing and recording the pertinent data including handling of failures of equipment and inaccuracies of reports. C. The following elements shall be included in the test plan for each of the tests required in the project: 1. Support, calibration instrumentation, test equipment and tools to be used 2. Technical publications to be referenced 3. Spares and consumables to be available 4. Maintenance facilities needed 5. Personnel requirements to be available for Contractor and County 6. Personnel scheduling 7. The report format and specific data to be collected during the test period together with the method used to report the test results 8. Preventive maintenance tasks (if any) to be performed during the test 9. Corrective action to be taken when failures and inaccuracies occur 8.4 Test Procedure Outline A. The test procedure shall include, as a minimum, the following requirements: Objective of test 1. Test environmental conditions 2. Detailed description of test specimens including drawings, part numbers, inspection and test records, maintenance records and calibration records 3. Detailed procedure of test 4. Test equipment to be used. Include any measuring equipment and /or any equipment aiding in the performance of the tests 5. The level and schedule of preventive maintenance during the test 6. Pass /Fail criteria 7. Retest procedure 8. Test script procedures for assessing Pass /Fail /Re -Test, including provisions for maintenance during tests. 9. Test notification 10. Test Reports B. The procedure to be followed for the resolution of test problems, failures, inaccuracies and general test conduct ground rules shall be defined 8.5 First Article Tests A. Functional Tests 1. The purpose of this test shall be to demonstrate that for each type of equipment the functions specified throughout this document, including all limiting conditions, shall be met. Each item of 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 (trouble shooting, and correcting faults) and service functions (extracting data) shall also be demonstrated. Page 51 of 79 MOA, 1 2. The Contractor shall be responsible for developing a functional test procedure that satisfactorily demonstrates all equipment functions and shall submit this test procedure to County for approval at least thirty (30) days in advance of the test. 3. Each function specified shall be tested at least ten (10) times prior to confirming success or failure. Each piece of equipment shall have passed the functional test before the environmental tests listed below are started. B. Vibration (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. The Contractor shall ensure that for the bus fleets, vibration conditions expected in the area of installation are taken into account to ensure that proper isolation/ protection is built in the on -board equipment design. In addition, the following requirements shall be met. 2. The on -board equipment shall be tested per the procedure of MIL - STD -810D, Method 514.3, Category 8, with the following changes: a. Basic transportation, common carrier environment curves, Figures 514.3 -1, 514.3 -2 and 5 14.3 -3 shall be used with an overall RMS level of 1.5g for the vertical axis and 1 .Og for the transverse and longitudinal axes. b. The cycling time shall be two (2) hours on each axis for a total of six (6) hours. The on -board equipment shall operate normally during and after this acceleration test and the equipment shall not experience broken or loosened parts from this vibration. c. At the conclusion of each axis frequency sweep cycle, the on -board equipment shall be subjected to a vibration of 3g's at a frequency sweep between 7 and 14 Hz for a period of one (1) minute and 4 g's at a frequency sweep between 70 and 140 Hz for a period of one (1) minute. The equipment shall operate normally after these acceleration tests and shall not experience broken or loosened parts from this vibration. C. Shock (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. The on -board equipment shall be tested per Procedure I of MIL - STD -810D with the following changes: a. The half sine shock pulse shall have a peak value (A) of 5g and duration (D) of 20 milliseconds. b. The on -board equipment shall operate normally after the shock tests and shall not have experienced broken or loosened components as a consequence of these tests. D. Electromagnetic Effects (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. Susceptibility to Radiated Electromagnetic Energy - The on -board equipment and revenue collection equipment shall be tested for susceptibility to radiated electromagnetic energy per the requirements of MIL - STD -461C for radiated emissions, electric field. The equipment shall not sustain any permanent damage as a result of the exposure to these electromagnetic fields nor shall it lose its data in RAM storage. Loss of data relative to a farebox transaction during the exposure is considered tolerable though undesirable. 2. Susceptibility to Conducted Electromagnetic Energy - The on -board and revenue collection equipment shall be tested for susceptibility to conducted electromagnetic energy per the procedures of MIL -STD- 461C, Requirement CS06, utilizing the 400 volt, 5 microsecond pulse of both positive and negative polarity. The equipment shall not sustain any permanent damage as a result of application of the pulse energy nor shall it lose its data in RAM storage. E. Radiation of Electromagnetic Interference (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) Page 52 of 79 1. The Contractor shall be responsible for compliance with applicable Federal Communication Commission regulations (i.e., FCC Rules, Part 15, and Subpart J) concerning conducted and radiated radio frequency energy. F. Temperature/ Humidity The on -board equipment shall be allowed to stabilize for a period of two (2) hours at each of the given environmental condition settings. Thereafter, the number of fare payment cycles to be processed shall be as indicated below. Test No. 1 # of Cycles 125 Temp (T) 32 Humidity Non CondensinR 2045% 2 125 110 97% 3 125 85 75% 4 125 65 95% 5 125 95 2045% 6 125 95 99% 2. Specific conditions to be met for the on -board equipment shall be: a. Accuracy shall meet the following requirements: 1) Preventive maintenance shall not be permitted during the environmental tests. 2) Failures - During the conduct of this test, failures shall not exceed two (2) intermittent failures not requiring corrective maintenance. 3) Jams requiring release(s) necessitating opening the farebox shall not be permitted. Should any occur, the test shall be repeated. Revenue collection equipment shall be subject to temperature/ humidity tests 2, 3, 5 and 6 as identified in the above table for twenty (20) cycles each. G. Maintainability Test 1. In conjunction with the Functional Tests, the Contractor shall conduct a Maintainability Test of the equipment. The purpose of this test is to determine that the equipment tested conforms to the following maintainability requirements. This will be accomplished by introducing faults into the equipment and then measuring the time required for a technician to diagnose and correct the failure, from arriving at the device through returning the device back to service, and shall include swapping out the affected module. Mean Time To Repair MTTR) MTTR (90% max) On -board Equipment 0.4 hour 0.9 hour Revenue Collection Vault System 1 hour 1.3 hours 2. At least thirty (30) days prior to the FAT, the Contractor shall submit to County a test outline which shall be prepared in accordance with the County approved maintainability test plan and shall show the basis of sample size selection and list of faults to be introduced into the equipment. This list shall represent every 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. County shall approve this list and the repair times prior to conducting the maintainability test. 3. The test shall be conducted in the following steps: a. The Contractor shall provide multiple units of the equipment to introduce failed components, incorrect adjustments and incorrect settings. The simulated failures shall be introduced in proportion to their expected failure rate. Page 53 of 79 16A 8 b. The Contractor's maintenance personnel shall be unaware of the simulated failures and shall be assigned to repair the equipment. c. The repair times shall be recorded and MTTR shall be compared with the advance list provided by the Contractor. All results will need to be approved by County. H. Interface Test The following equipment interfaces shall be evaluated for hardware, software, and data transmission. These tests shall be performed under ambient conditions and shall demonstrate all functions specified for the system. The interfaces are: a. Between the TPU and the farebox. b. Between the MSR and the farebox. c. Between on -board equipment and the revenue transfer and collection equipment. d. Between the revenue transfer and collection equipment and the FCMRS. e. Between the FCMRS and the County network. I. Design Qualification Waivers 1. The Contractor shall demonstrate that each component or subsystem of the fare collection system supplied meets or exceeds the specification requirements. Wherever a component or subsystem is substantially similar in design and application to equipment previously used in a similar application, the design may be qualified through submission of revenue service data. 2. If a component or subsystem in question is considered by County to be substantially identical in design to equipment previously deployed in other transit applications, design qualification tests on that equipment may not be necessary. Contractor shall provide a formal request for a Design Qualification Testing waiver for consideration by County for each applicable component or subsystem which shall include the following data as a minimum: a. List of the locations and quantities of current equipment installations, including duration of revenue service. b. Description of all relevant differences among the other installations and the requirements of this specification. c. Description of all differences between the currently installed equipment and the specified equipment. d. Test results of any relevant design qualification tests that have been conducted on this equipment. e. Reliability data for previously installed equipment, verifiable through purchasers. 3. Based on the submitted data, County will determine if the requirements for design qualification testing shall be waived. Specific requirements for each piece of equipment will be considered individually, and waivers will be issued on an individual basis. Waiver of design qualification for a component or subsystem shall not satisfy integrated testing of components. 4. The Contractor shall supply certification for those tests for which exemption is requested. This shall include actual test data documenting the appropriate tests performed on the on -board and revenue collection equipment to meet the requirements specified and having successfully operated the equipment on transit buses under revenue service conditions for at least six (6) months. The Contractor shall supply to County the name, address and phone number of all testing facilities and the person(s) involved in performing such testing. 5. The certificates shall be approved by County to exempt the Contractor from performing the tests. J. Cycling Test The cycling test shall be conducted for the on -board equipment as follows: Page 54 of 79 16A 8 1. Cash Payments - a minimum of 500 coin only transactions and 500 bill only transactions for the payment of the base fare shall be performed. A minimum of 200 coin /bill transactions for payment of the full fare base fare shall be performed. A minimum of 1/2 of all transactions shall provide for the loading of a stored value card with credited amount for overpayment and a transfer. 2. Pass Usages - a minimum of 500 pass transactions for each activated pass type shall be performed. 3. Count Transactions - a minimum of 100 transactions shall be initiated for each of the tally buttons. 4. On -board Pass Sale /Activation Transactions - a minimum of 100 transactions each for sale /activation of each type of pass (Day, Week, Month) purchased on -board shall be performed using cash (pass sale). 5. Transfer Transactions - a minimum of 100 transactions shall be initiated. 6. Pass Activations - a minimum of 50 transactions for the activation of a pre - purchased pass shall be performed using both full fare and reduced fare passes. 7. Stored Value and Stored Ride Transactions - a minimum of 100 transactions using magnetic stored value farecards and 100 transactions using magnetic stored ride farecards for the base fare, and 100 transactions using each for the reduced fare shall be performed. K. Dust Test 1. This test shall be performed to verify that the on -board fare collection equipment is capable of meeting the environmental requirements of these specifications as well as the following combination of conditions: a. High temperature b. High humidity c. Moderate winds d. Dust conditions 2. The Contractor shall prepare a test procedure, for review and approval by County not less than thirty (30) days prior to the commencement of the environmental test. This dust test shall include varying lengths of exposure by the on -board equipment, from one (1) minute to one (1) hour in fifteen (15) minute intervals. 8.6 Pre - Installation Checkout A. Upon successful completion of the FAT, County or its consultant will issue a production release to the Contractor to deliver all equipment specified. Prior to installation, a Pre - Installation Checkout (PIC) Test shall be conducted. CAT or its consultant will select five (5) on -board assemblies at random from delivered items plus the FCMRS, including software to run all reports; and Data Probe (or wireless equipment), as supplied, with associated hardware. The PIC test shall take place at the County facility. B. The test objectives are: 1. To confirm that there was no visible damage in the delivered equipment. 2. To visually inspect a random sample of on -board equipment for conformance with specifications. 3. To verify that the on -board equipment works as expected by checking the bus operator sign -on /sign- off function and to verify other operating functions by processing various fares. 4. To ensure that all data reports are produced in accordance with specifications. 5. To determine by these procedures if installation can begin or corrections and/or adjustments are needed followed by a retest before installation can begin. C. This equipment shall be set up at the County CAT facility by the Contractor in such a manner as to permit all of the above listed test objectives to be evaluated. The following sequence of tests shall be conducted as a minimum: Page 55 of 79 16A 8 1. The on -board equipment shall be powered using a power supply furnished by the Contractor. 2. The on -board equipment shall be programmed for bus number and correct fare tables and related information downloaded from the FCMRS. 3. Visual inspection of the on -board equipment shall be made to ensure that there is no physical damage and that all specified displays, messages and prompting sequences including tone coordination occur as specified. 4. Sign -on procedures shall be completed followed by processing at least ten (10) fares of each type. 5. Cashboxes shall be vaulted at least twice per farebox tested. Sign -off procedure and data collection shall be completed and FCMRS printouts reviewed. 8.7 Network Interface Test A. As part of the PIC, the system shall be provided with test data simulating the County database for purposes of this test. Throughout this test, the date and time shall be modified a minimum of ten (10) times incorporating dates from a minimum of five (5) different years. B. All interface connections shall be inspected for proper installation. All functions requiring interface to the FCMRS, including all alarm and boundary conditions and security provisions, in all possible combinations, shall be tested. These functions shall include, but not be limited to, the following: 1. Alarm transmission and all other device/ component monitoring functions 2. Data transmission to the FCMRS 3. Data transmission from the FCMRS 4. Fare Table modification, download and verification 5. Automatic report generation at the FCMRS C. The Contractor shall identify each integrated function in its Test Procedures, including the boundary conditions and security provisions for each item of equipment and operation. D. All data transmissions shall be inspected and tested for accuracy. Inaccurate data transmissions shall be recorded as a failure. The Contractor shall take any corrective action necessary to ensure the proper performance of all functions. E. Samples of all reports available shall be generated by the FCMRS. Format, layout, page and column headers, data and all other information shall be reviewed to confirm compliance with the designs approved at the Final Design Review. Contents of the reports shall be compared with the known contents of the data. Successful completion of the test requires no discrepancies between report contents and known data as well as proper formats. 8.8 In- Service Qualification Test A. On successful completion of the PIC, County will issue a release for the Contractor to install equipment. After approval of the IAT results, the ISQT will begin. The Contractor shall supply adequate spare modules, assemblies, parts and consumables to be used throughout the ISQT. B. Object And Conditions Of The ISQT 1. The purpose of this test shall be to operate the equipment listed above in revenue service for a period of four (4) weeks. This test shall be conducted with buses operating on their designated routes in revenue service. 2. The first seven (7) days shall be designated as a settling period, but with all normal operations for revenue service being carried out and accuracy and reliability data being documented. Prior to this period a Failure Review Board (FRB) shall be set up. The FRB will ascertain what constitutes a failure and what the satisfactory corrective actions will be to prevent recurrence when the ISQT begins. Page 56 of 79 16A 8 Failures shall be established in conformance with guidelines specified. At the end of the settling period, the ISQT shall begin and shall be conducted over the next twenty -one (21) days. 3. The Contractor shall be responsible for performing all maintenance actions during ISQT C. Test Requirements The equipment shall be operated in full revenue service. The measures to determine acceptance of equipment shall be the Accuracy Test and the Reliability Test. D. Accuracy Test 1. This test shall be conducted with all the ISQT on -board equipment. This on -board equipment shall be monitored daily during the ISQT 2. The minimum accuracy requirements stated above shall be achieved during the conduct of the test in order to continue the ISQT. If the accuracy requirements specified are not met at the periods indicated, County will have the right to suspend the ISQT until changes are made to achieve this accuracy. Data handling, data storage and the production of printed data on all reports shall be without error for the duration of the ISQT. Over and under amounts will be added algebraically to determine overall accuracy. 3. In addition to the verification of the accuracy of the collected revenues, a data accuracy review shall be performed. This data accuracy shall serve to ensure that all data are reported properly and accurately, that information is consistent between reports, that all column and row totals are properly calculated and that all alarms and messages sensed are recorded and reported. A complete batch of all reports shall be printed on five (5) random days, as selected by County during the ISQT, for this purpose. E. Reliability Test 1. For on -board equipment (including probes) - This test shall be conducted with all the ISQT on -board equipment. They shall be monitored for report of any failures. All conditions of equipment errors, repairs, adjustments, replacements, malfunctions of on -board equipment (including parts /modules thereof) shall be fully documented for the entire test period. The minimum reliability requirements stated above shall be achieved during the conduct of the test in order to continue the ISQT. If the MCBF requirements specified are not met at the period indicated, County will have the right to suspend the ISQT until changes are made to achieve this reliability. 2. For the duration of the ISQT there shall be no more than one (1) failure of the FCMRS, data probe, revenue collection equipment or interface to the County network. F. Pass/ Fail Criteria 1. Requirements specified for both the Accuracy Test and the Reliability Test shall be met in order to pass the ISQT. When the ISQT is passed, the equipment shall remain in revenue service. The ISQT test results and data collected shall be reviewed weekly by County. G. Failure of ISQT Page 57 of 79 16A 8 1. In the event that the equipment fails the ISQT the Contractor shall have up to ninety (90) days to correct or update the equipment and retest until a pass category is reached. The Contractor shall maintain a qualified representative responsible for making adjustments and repair of equipment at the depot where the ISQT is being performed. Failure to pass the ISQT after this additional ninety (90) days shall be cause for termination for Default as defined in the Contract Conditions. 8.9 Reliability, Maintainability and Accuracy Test A. The RMAT will begin after a seven (7) -day transition period at the successful conclusion of all equipment installations and shall be conducted over a period of ninety -one (91) days. The first twenty -eight (28) days are a settling period during which records will be kept, but performance will only be measured and verified during the final sixty -three (63) days. The Contractor shall be responsible for maintenance during RMAT. B. During the RMAT, reliability, maintainability and accuracy will be recorded by Contractor personnel and reviewed by County at the fourth (4th), eighth (81h) and thirteenth (13th) week stages to evaluate the performance for the preceding period. RMAT test results and data collected shall be reviewed weekly with County. Reliability, maintainability and accuracy at each stage shall meet the performance requirements specified. 8.10 Final System Acceptance A. Final system acceptance of the fare collection system by County shall be contingent upon passing the RMAT and the Contractor furnishing all required hardware, software, spare parts, documentation, training, supplies and all other items identified in these specifications. B. The warranty of the system shall commence upon final acceptance of the fare collection system and shall continue for a one (1) year period. 8.11 Test Performance Requirements A. General Requirements 1. The equipment shall be operated in full revenue service. The measures to determine acceptance of equipment shall be the Reliability Test and the Accuracy Test as follows: 2. The procedures described below shall start on day 1 of revenue service and shall be continued during the RMAT period. B. Sampling Method for Accuracy Test The accuracy test shall be based on performance related to on -board equipment using a ten (10) cashbox sample. This sample shall be comprised of a control group which would be the same five (5) on -board pieces of equipment every day. The balance shall be audited on a predetermined schedule developed by County. 2. On -board equipment will be excluded from the daily audit sample if it was reported to have any malfunction or failure in terms of its mechanical or electronic operating functions, which could have corrupted its data. C. Accuracy Requirements 1. The RMAT accuracy trend specified shall be achieved during the conduct of the RMAT. If the accuracy requirements specified are not met at the periods indicated, County will have the right to Page 58 of 79 m m 0 interrupt the RMAT until changes are made to achieve this accuracy. Data handling, data storage and the production of all reports shall be in accordance with requirements specified. 2. During the RMAT, accuracy shall be monitored with reviews at the (41h), eighth (8th) and thirteenth (13th) week stages to evaluate the performance for the preceding period. Accuracy at each stage and cumulative to date accuracy performance shall also be evaluated and shall meet the requirements specified. D. Method for Calculating Accuracy The accuracy of the on -board equipment shall be calculated as for the ISQT. E. Reliability Test 1. All conditions of equipment errors, adjustments, replacements, malfunctions and failures shall be fully documented by the Contractor for the entire test period for the RMAT. 2. The following procedures shall be used to log chargeable failures associated with RMAT. The Failure Review Board (FRB) shall ascertain what constitutes a failure in the event of a disagreement. a. Operating Malfunctions -- An operating malfunction is defined as a random malfunction that does not cause the equipment to be inoperable but would require some form of maintenance to be rendered, such as a blown bulb. b. Operating Failures An operating failure is defined as any condition that causes the equipment to cease working (e.g., logic board failure). An operating malfunction becomes an operating failure when the same malfunction occurs on three (3) different pieces of on -board equipment. An example is a bus operator display burning out in three (3) different pieces of on -board equipment. b. Item Failures An item failure is defined as an operating failure of a particular module which occurs three (3) or more times. For example: if the bill transport in farebox #123 shows three (3) operating failures this would be logged as one (1) item failure. c. Design Failures A design failure is defined as a failure of a given type of module in ten percent (10 %) of the modules provided. An example is if there are 20 fareboxes in use and two (2) different farebox bill transports are each charged with an item failure, this constitutes a design failure. 3. Customer induced malfunctions are non - chargeable. 4. A daily maintenance diary shall be kept which records all malfunctions and failures by type. Malfunctions and failures shall be recorded by major module classification. 5. An equipment maintenance report shall be prepared to record all maintenance related incidents and the determination of chargeability. 6. If a design failure occurs, continuation of the test is at the discretion of County. F. Failure of RMAT 1. In the event that the equipment fails the RMAT the Contractor shall have up to twenty -eight (28) days to correct or update the equipment and retest for a minimum of twenty -eight (28) additional days until a pass category is reached. 2. In the event of a retest, the Contractor shall be required to maintain, on a full time basis for the entire repeated RMAT period, a qualified representative responsible at the test location for making all adjustments and to repair all equipment at the expense of the Contractor. 3. Failure to pass the RMAT after this additional twenty-eight (28) days shall be cause for Termination for Default. Page 59 of 79 16A 8 G. Failure Category Definition The following conditions shall be used as a guide to classify failures. 1. Relevant Failures: a. A relevant failure is any malfunction which prevents fare collection equipment from performing its designated function, or meeting its performance criteria, when used and operated under the environmental and operational conditions stated in these specifications. Example: If a farebox fails to boot up into operation, it is a relevant failure. But if it is determined that the bus battery had no charge, it will not be a chargeable failure. b. All relevant failures shall be chargeable failures when attributable to one (1) or more of the following reasons: 1) Equipment design 2) Equipment manufacture 3) Equipment quality 4) Parts design 5) Parts manufacture 6) Parts quality 7) Software errors (If software errors are corrected and verified for twenty -eight (28) days in revenue service during the tests, such errors shall not be chargeable as equipment failures.) 8) Equipment installation. 9) Contractor furnished operating, maintenance or repair procedures, tools and equipment that cause equipment failure. (If procedures are correct and verified, such failures., shall be chargeable as equipment failures.) 2. Non - Relevant Failures a. A non - relevant failure is a malfunction caused by a condition external to the equipment under test, which is neither a functional, environmental, nor a test requirement in this specification and is not expected to be encountered during normal and correct operation of the equipment in revenue service. b. Non - relevant failures shall be considered non - chargeable failures and shall include the following: 1) Accident or mishandling. 2) Failure of test facility or test instrumentation. 3) Equipment failures caused by externally applied over stress conditions in excess of the approved specifications requirements contained herein. Certain customer induced failures such as use of torn or mutilated fare media and abuse of equipment. 4) Normal operating adjustments not as prescribed in the approved equipment operating and maintenance manuals. 5) Dependent failure(s) occurring with the independent failure that caused them. 6) Failures of expendable items having a specified life expectancy when operated beyond the defined replacement time of the item. 7) Failures caused by incorrect operating, maintenance or repair procedures. C. If incorrect procedures are employed it is not a chargeable failure. H. Failure Review Board (FRB) Page 60 of 79 16A 8 1. During the first seven (7) days of the ISQT a Failure Review Board (FRB) shall be established. The FRB will include two (2) members representing County and one (1) member representing the Contractor. 2. The FRB will ascertain what constitutes a failure and what the satisfactory corrective actions will be to prevent recurrence when the RMAT is run. 3. Failures shall be established in conformance with guidelines. The end of the ISQT and first twenty - eight (28) day period of the RMAT the FRB shall review all data from each test and finalize plans for continuing. 4. The RMAT data will be reviewed and approved by the Failure Review Board before it will become official. The FRB shall agree on the procedures to resolve issues related to "Fleet Defects ". This applies to any hardware or software conditions that result in an unacceptable performance and that this occurs in more than twenty percent (20 %) of the fleet. I. Data Verification 1. During each of the acceptance test periods, the data transferred from the farebox to the FCMRS will be verified by County. This shall include the verification of all connectivity aspects associated with transfer of data, production of reports and operation alerts and alarms. 2. Each day a specific farebox will be selected and the detail data will be printed. This data will be verified against the data transferred to County departments to verify that it has been transferred properly. In addition, all transactional data for that farebox will be verified against the summary data compiled and reported. 3. The periodic reports (daily summary, weekly summary, monthly summary and annual summary) will be printed each day to verify that the totals are being accumulated properly. On a random basis verification of alarms and events will be verified. 4. None of these tests shall fail. All data shall be transferred and properly available for review and manipulation by the County network. J. Corrective Action If the Reliability, Maintainability and Accuracy requirements specified are not attained during the RMAT, the Contractor shall be responsible to redesign, provide retrofit kits and furnish labor to correct and /or change the equipment at no additional cost to County. The corrective action and /or the resolution of the problem(s) shall be subject to approval by County. END OF SECTION IX. TRAINING 9.1 General Training Requirements and Plan A. The Contractor shall be responsible to train County designated personnel according to the requirements specified herein. Training shall include course development, providing instructors, supplying handouts, manuals, classroom aids, etc. Practical training on equipment shall occupy a significant portion of all training classes. The training presentations and material shall be in English. B. Instruction shall be designed to include courses described below and shall cover equipment familiarization and systems operations. The training shall be provided to bring those employees designated to the level of proficiency required for performing their respective duties. Formal training shall include both classroom and practical work, and shall be augmented by informal follow -ups as needed. C. The Contractor shall provide experienced and qualified instructors to conduct all training sessions at County designated training facilities. The Contractor is responsible for insuring that the instructors teaching these training courses are not only familiar with technical information, but are able to utilize Page 61 of 79 16A 8 proper methods of instruction, training aids, audiovisuals and other materials to provide for effective training. D. The Contractor is responsible for providing all training aids, audiovisual equipment and visual aids for the conduct of these courses. At least one (1) session of each different training course shall be recorded on DVD by the Contractor. E. All training materials are to become the property of County at the conclusion of training. F. Initial sessions shall be provided for maintenance and operations training not less than thirty (30) days prior to the commencement of installation of any portion of the system. Final maintenance technician training shall commence during the time period when equipment is installed on the buses, prior to revenue service of the system. G. At the request of County, the Contractor shall, during the warranty period, provide three (3) additional refresher training sessions of any of the courses provided under this contract. These refresher training sessions shall be held in Naples, FL during the warranty period at no additional cost. H. At the request of County, the Contractor shall, during and up to 60 days after implementation, provide equipment to demonstrate and train the public on the use of electronic fareboxes. These training sessions shall be held in Naples, FL in locations, dates and times selected by County no additional cost. 9.2 Submittal and Approval Requirements A. Submittal 1. The Contractor shall submit the training curricula and materials for review and approval by County. No training shall occur until training materials have been approved by County. The curricula shall meet all training requirements and indicate course content, training time requirements, and who should attend. Training curricula shall be provided for County review sixty (60) days prior to commencement of equipment installation. 2. Should this material include information as provided in the system documentation and manuals, any updates to that documentation which affect the training materials shall be updated in the training materials as well. B. Required Curricula and Materials The following curricula and materials related to training shall be provided subject to approval by the County. 1. Instruction Material: The primary source of instructional material shall be the applicable equipment operating and maintenance manuals. In addition, the Contractor shall develop, for each course specified, notebooks containing such additional drawings, descriptive information and procedures necessary to ensure that all learning objectives are met in an orderly and timely manner. 2. Student Guides: All students shall be furnished with a guide containing material which mirrors information in the instructor guides and provides the information necessary to effectively train the students. 3. Instructional Equipment and Training Aids: Training shall be conducted using fare collection equipment in normal operating condition. In the event such equipment has been accepted by County, the equipment will be made available to the Contractor for training purposes. 4. Training Schedule: Training classes shall be prescheduled at least thirty (30) days in advance and in coordination with County. Classes will be conducted at facilities provided by County. 5. Training Materials: a. Course materials, including notebooks, instructor manuals, and handbooks will become the property of the students and instructors, as appropriate, at the conclusion of the training course. Page 62 of 79 16A 8 b. At the completion of all training courses one (1) set of camera - ready, letter quality reproducible documents or computer files for each course outline, lesson plans, training aids and notebooks shall be provided to the County. 9.3 Bus Operator Training A. The Contractor shall provide an instructor who is experienced and qualified in the operation of the fare collection equipment. One (1) portable standalone fare collection equipment training units with a 110 volt AC power supply shall be supplied for the training. The standalone training units will become the property of County at the conclusion of training. B. The purpose of this training is to instruct County CAT bus operator instructors who in turn can train bus operators in the operation of the equipment. C. At the completion of training, County CAT instructors will demonstrate competency in the operation of the equipment by taking and passing a performance test and written examination. D. This course shall be designed to provide management, supervisory and operating personnel with a functional understanding of all of the fare collection equipment. The functions of each module shall be covered, including the interrelationship of the equipment with the customer. Personnel attending this course, in addition to bus operators and transit supervisors, will include the following categories: management (at the overview level), marketing, public relations; and operating, financial and other administrative personnel. E. The instructor classes shall conclude four (4) weeks prior to the start of the ISQT in order to allow for the training of bus operators. 9.4 Revenue Service Training The Contractor shall provide an experienced and qualified instructor who shall conduct training classes for the complete revenue collection/ revenue service operation. 9.5 Data Management and Reporting System Training (Documentation Only) 1. The following shall be included in the FCMRS documentation: a. External interfaces. b. Development assumptions. C. Processing scripts. d. Data dictionaries. e. System flows. 2. Data diagrams shall be provided to County. All programs shall be defined and described fully, showing all inputs /outputs, samples of reports, logic flows and major functions described, as well as assumptions used during program development. Detailed system functional requirements shall also be provided. Explanation of the software instructions and methods employed to make changes in software programs shall also be taught. Use of software documentation shall also be fully covered. 9.6 Data Management and Reporting System User Training A. The Contractor shall provide an experienced and qualified instructor who shall conduct user orientation training for FCMRS users, including staff who will be responsible for the generation of system reports and queries. B. The purpose of this class will be to provide basic training and to describe to personnel the data structure, program logic and data transmission operation functions and how the software in the Page 63 of 79 16A 8 FCMRS can be used to perform data sorts and selective data reporting, file retrieval from back up files, and how other programmable functions are achieved. C. The goal of the training shall be to make the participants competent to both operate and teach others the proper operation of the report generation system. D. This course shall include the use of simulated or actual data provided by the Contractor. This data shall include sufficient information to cover multiple months and shall include events and transaction data from all types of equipment furnished. 9.7 Equipment Maintenance Training A. The Contractor shall provide an instructor who is experienced and qualified in the maintenance of the fare collection equipment. B. The purpose of this training is to instruct technicians in the maintenance of fareboxes, the RCVS and all related equipment that County technicians will be maintaining. C. Fare collection equipment shall be provided for the training sessions. D. At the completion of training, technicians will demonstrate competency in the maintenance of the equipment as indicated by taking and passing troubleshooting and repair tests and written examinations. E. This maintenance training information shall include troubleshooting and diagnostics of all known problems for all types of fare collection equipment furnished. 9.8 Additional Training A. In addition to the training as specified above, small sessions with 1 -3 County staff members shall also be provided as described below 1. Security Training - Individuals shall be trained in the understanding of all security components and interlocks within the system, including fareboxes, cashbox receivers, revenue collection vaults and associated software. It is anticipated that this effort shall require four (4) to six (6) hours of training during a one (1) day period. 2. Administrative Training - Selected individuals shall be trained in the overall understanding of the fare collection system basics. It is anticipated that this effort shall require four (4) to six (6) hours of training during a one (1) day period. 3. Planning Training - Individuals shall be trained in the understanding of the origin and meaning of all system data and how to manipulate the data to provide needed reports and information. It is anticipated that this effort shall require six (6) to eight (8) hours of training during a one (1) day period. 4. Revenue Tracking System Training - Individuals shall be trained in the operation and understanding of the revenue tracking system, including the meaning of all system data and understanding reconciliation reports as well as all cashbox movements. It is anticipated that this effort shall require four (4) to six (6) hours of training during a one (1) day period. 9.9 Bus Operator Training Video A. At the end of the training, the Contractor shall provide County with five (5) copies of a video recording in DVD format that contains the training that would normally be provided by an experienced trainer showing complete operation of the farebox from the perspective of a bus operator. B. This video recording shall include all procedures required by the system at the start of, during, and at the end of revenue service. The video shall highlight customer displays, bus operator displays, button presses, farebox indicators and farebox actions (card issue /return, etc.) as well as customer service features of the farebox such as the MSR, TPU, coin and bill validation, etc. Page 64 of 79 • C. The video recording shall be updated within thirty (30) days after the final acceptance of the system to accommodate any operational changes. D. The video recording shall be approximately ten (10) to fifteen (15) minutes in length; and presented in an edited and professional format including a sound track, introduction, appropriate graphics and other features E. Actual training sessions and recordings from other transit properties may be used for some aspects of this video recording, but County shall have final approval of contents and quality. END OF SECTION X. DOCUMENTATION 10.1 General Requirements A. All documentation shall be in English, using US measurements and be submitted directly to County. Any documentation submitted through a third party will not be considered received. All documentation shall be provided in hard copy and electronic formats similar to those used for Microsoft products. B. Preliminary drafts of all manuals shall be supplied ninety (90) days before installation begins at the first depot. The documents shall be as complete and as comprehensive as possible. Ten (10) sets of each type of preliminary draft document, manual and drawing as described in this section shall be provided by the Contractor. These documents will be reviewed and comments furnished to the Contractor within thirty (30) calendar days of their receipt. C. Complete final manuals in the quantities and quality as described in this section shall be supplied no less than five (5) days prior to the commencement of the first depot installation. D. Post warranty manuals shall be provided at the successful completion of the initial warranty period. These shall be of the latest revision and shall have incorporated all modifications or changes made to any part of the fare collection system covered under this specification. The documents shall not be considered final without the approval of County. Post warranty manuals may be submitted for approval up to sixty (60) days prior to initial warranty expiration. E. The warranty period shall not end until complete and final post warranty documents as specified herein have been furnished by the Contractor and approved by County. F. The Contractor shall provide a list of all special or custom tools or instruments required to maintain or adjust any component within the Fare Collection System. G. Diagrams and drawings shall identify each and every component in the Fare Collection System and call out each component with the unique part number as referenced in the Bill -of- Materials. H. The Contractor shall provide a parts layout for every printed circuit board, specifically calling out each component, be it mechanical or electrical in nature, and showing its exact location. I. The Contractor shall provide drawings showing the location of all of the traces on the top and bottom and any through board connections of each printed circuit board. These drawings shall be laminated and suitable for use during shop repair of components. J. Each type of maintenance manual shall contain, but not be limited to: a description of operation; installation procedures; a complete parts identification diagram and list; troubleshooting procedures; inspection procedures; preventive maintenance procedures and program; repair procedures; diagnostic procedures; wiring diagrams; electrical schematics with board and cable identification; and adjustment procedures. K. Subcontractor's names and part numbers shall be cross referenced with the Contractor's part numbers for the required parts lists. Page 65 of 79 L. Electrical and electronic drawings shall be supplied to show engineering changes made to any component or module up to the end of the warranty period of the Fare Collection System supplied. M. The manuals shall be complete, accurate, up -to -date, and shall contain only that information which pertains to the system installed and shall be written in English only. 10.2 System Documentation Requirements A. Manuals required shall include the following parts, as applicable: 1. System Characteristics a. A physical description of the subsystem and pertinent technical characteristics. b. A description of the functions that the subsystem is designed to perform and the general methods employed to accomplish those functions. 2. Principles of Operation (for maintenance manuals) a. Detailed discussion of the theory of operation. b. Interface between subsystem elements. c. Signal flow sequence correlated to block diagram(s). 3. Operating Procedures a. Turn -on and turn -off procedures. b. Detailed bus operator instructions sufficient to operate the equipment in each mode of operation. C. Emergency operating procedures. 4. Maintenance Procedures (for maintenance manuals) a. Preventive maintenance procedures, schedules and manufacturer's recommended products. b. Fault isolation and analysis procedures. C. Corrective maintenance and repair procedures. d. System calibration and test procedures. e. Illustrated parts catalog. B. A document control method shall be proposed by the Contractor and approved by County. C. The Contractor shall submit to County for approval a Table of Contents and sample formats for each type of manual and for the Illustrated Parts Manual. 10.3 Security Manual A. To the greatest extent feasible, the Contractor shall not, in any of the following documentation, include items related to the specific operations of, or maintenance of, security devices which may be used for fraudulent purposes. B. Information of this type, shall be identified and submitted separately, stamped CONFIDENTIAL. It shall be the Contractor's responsibility to meet with the County Project Manager to determine what information shall be considered confidential. C. County regards the documentation of certain software programs and certain aspects of maintenance to be security related. Also considered as security related are revenue collection and revenue transfer information; revenue equipment construction and locking information; and other similar elements. Page 66 of 79 16A 8 10.4 Bus Operator Manual A. The manual shall contain succinct instructions on how to operate each on -board item of fare collection equipment. Pictograms and photos are encouraged. Fault procedures need to be described as well as directions for dealing with customer service issues related to equipment operation. B. The manual shall contain all information needed for safe, proper, and efficient operation of the on- board equipment. All normal operational sequences shall be described in detail. C. The manual shall be printed on plastic coated paper, or the equivalent, for durability and be no larger than 3 -1/4 inches wide by 6 inches long by 1/4 inch thick 10.5 Revenue Collection Manual The revenue collection manual shall include a complete description of the operation of all revenue collection equipment, including cashboxes, receivers, and receiver vaults, necessary to operate the revenue collection system. 10.6 Maintenance Manuals A. The Contractor shall provide a manual covering each item of fare collection equipment furnished, including exercised options, with drawings which identify the various parts and assemblies in the equipment. The materials provided shall contain, but not be limited to: a description of operation; installation procedures; preventive maintenance procedures and program; repair procedures; diagnostic procedures; wire diagrams; electrical schematics with board and cable identification; and adjustment procedures. B. The manuals shall identify any special tools required for any of the procedures. C. Durable materials shall be used to provide extended life for these manuals in the maintenance shop environment. D. An electronic copy of all manuals, in Adobe PDF or other form approved by County, shall be provided on four (4) sets of CD -ROMs as well as one (1) printed master copy on 8 -1/2 x 11 inch paper. E. Manual Contents shall be as specified herein and shall be consistent with training. 1. Preventive Maintenance Section: shall contain all information needed to enable maintenance technicians to perform all periodic inspection and preventive maintenance tasks including lubrication, inspection and replacement of consumable items. The manual shall contain recommended PM schedules. 2. Troubleshooting and Corrective Maintenance Section: shall contain all information needed to diagnose problems and make adjustments and repairs to all Fare Collection System components and sub - assemblies to restore the system to a normal operational condition in an efficient and timely manner. The manual shall include at a minimum a general description of each subsystem, component and subassembly; functional block diagrams; detailed schematics; troubleshooting flow charts and wiring diagrams. 3. Shop Repair Section: shall contain detailed descriptions of each assembly and subassembly sufficient to service, maintain, repair, replace, rebuild, and overhaul the equipment. Systematic procedures; wear and tolerance limits for determining when overhauls are needed; overhaul procedures; and special tools and equipment required shall be included. 4. Illustrated Parts Section: shall describe and identify each module, sub - assembly and part within each piece of equipment with its related supplier identification number and Contractor identification number. Exploded drawings shall be provided to permit identification of all parts not readily identified by description. Page 67 of 79 16A 8 10.7 Test Equipment Manual The Contractor shall provide manuals for each type of test equipment furnished. Manuals shall include all information necessary to allow proper and full use of all test and calibration equipment furnished. 10.8 Fare Collection Management and Reporting System Manual A. The Contractor shall provide a Fare Collection Management and Reporting System Manual, to include drawings which identify the various parts and assemblies of the system. The manuals shall contain start -up procedures, operating modes, interconnection diagrams, preventive maintenance procedures and program; diagnostic procedures and wiring diagrams with board and cable identification. B. Equipment Manuals shall be provided for the hardware and components used to configure the system. The manuals shall include those instructions and maintenance manuals furnished by the supplier of each type of processor, keyboard, modem, fixed disk drives, other storage media, monitor, printer, backup system, uninterruptible power supply, and other components. The content of this information shall be complete and detailed. It shall be the Contractor's responsibility to acquire the required information from the respective manufacturers. C. Software Manual and Program Documentation 1. The Contractor shall provide complete documentation for each Contractor developed and furnished computer software program for the FCMRS, including the money room terminal and any other subsystems using a microprocessor or other computer. 2. The software documents shall be furnished for review and approval by County prior to installation by County of the equipment on County property. The original and each amended version of a software program shall require new copies of the documentation to be furnished for review and approval by County prior to installation by County. The software documentation shall not be distributed beyond the authorized personnel. 3. The documentation for each version of each program shall be complete and comprehensive to include, but not be limited to: complete source code listings with fully documented statements; comprehensive flow charts; and block diagrams explaining the system as a whole and showing how the individual programs are interrelated. 4. The software documents shall clearly identify what data elements are stored; the source of each data element; and how data is structured, transferred and utilized. This shall include the software logic, processing rules, restrictions and exceptions, default conditions, hard and soft wired parameters and the overall process by which each of the reports specified is generated. 5. Software manuals from suppliers of third party software components included as part of the system shall be provided as a part of this program documentation. END OF SECTION XI. SPARE MODULES, SPARE PARTS AND CONSUMABLES 11.1 Spare Modules and Parts A. Spare modules and parts shall be furnished in accordance with the listing furnished with the Price Proposal Form. B. Spare modules and parts should be new and manufactured to the specifications of the original parts in the delivered fareboxes and completely interchangeable. C. A list of vendors providing spare parts and consumables should be provided by the Contractor to County within sixty (60) days after NTP. Page 68 of 79 D. The spare modules and parts shall be manufactured concurrently with production of modules and parts for delivered equipment. The Contractor shall prepare and submit to County a spare modules and parts list detailing the part number and description of each module and part that is to be furnished. 11.2 Spare Parts List Contents A. A comprehensive list of spare modules and parts for all equipment shall be provided to County within sixty (60) days after NTP. This listing shall include all items that can fail or that require replacement due to wear over a ten (10) year period. B. In addition, the Contractor shall provide at County's request at any time the equipment is being used in revenue service, a complete parts and modules list, together with prices, parts numbers and descriptions for all modules, parts and parts within the modules for all equipment furnished by the Contractor. 11.3 Consumables A. Contractor shall provide all consumables necessary to operate the system, or any particular system component that has been installed based upon projected ridership levels provided by County, for a one (1) year period of operation. B. A comprehensive list of system consumables shall be provided to County within sixty (60) days after NTP. C. The Contractor shall provide the consumables upon the installation of the equipment. Should the In- Service Qualification Test (ISQT) not be passed initially, the Contractor shall note the level of consumables and replace any consumables utilized from that point until the ISQT has been passed successfully. This procedure shall apply for all revenue service acceptance tests. 11.4 Support Equipment The Contractor shall provide the testing, service and other special tools and equipment required for proper operation and maintenance of the system as a part of the initial equipment delivery. 11.5 Future Supply Provisions A. For twelve (12) years after Final System Acceptance, the Contractor shall make available, for delivery within sixty (60) days, all Contractor designed equipment, modules and parts as are or may be necessary to service and maintain the equipment delivered to County. B. Alternately, during the twelve (12) year period, the Contractor shall ensure that County can obtain the equipment, modules and parts from other suppliers for a comparable price (generally within ten percent (10 %) of the part or module price on the Contractor's most recent price list). The Contractor shall also offer County the opportunity of ordering the equipment, modules and parts at least six (6) months before discontinuing their production.- It shall be the Contractor's responsibility to alert the County of this situation and to provide to the County's applicable drawings, parts lists and at least two (2) sources for obtaining parts that were previously supplied by the Contractor. C. As an alternative, the Contractor may upgrade or retrofit all of the Contractor supplied equipment to use modules and parts that are readily available from the Contractor or other suppliers at a comparable price to meet the requirements of this subsection. The entire cost of any such upgrade or retrofit shall be at the Contractor's expense. D. The Contractor shall also notify County in a timely manner when improvements or modifications to parts or modules are fabricated that could improve the operation of County's system. E. In the event that the Contractor cannot furnish any system equipment, modules or parts within sixty (60) days after receipt of an order, and there is no suitable alternative supplier, County will have the right to fabricate or have fabricated from drawings and specifications provided by the Contractor, such equipment, modules or parts. The Contractor shall provide, at its sole expense, any necessary patent releases. If the Contractor is not the manufacturer of a particular part or module within the system, the Page 69 of 79 16A 8 Contractor shall make every effort to assist in obtaining the necessary information to fabricate the necessary parts or modules that are necessary for proper system operation, which have been discontinued. F. The Contractor's undertaking herein is a covenant, promise, representation, and warranty made in consideration of the price or prices to be paid by County for the equipment to be delivered hereunder, as well as for such spare modules and parts. END OF SECTION XII SCHEDULE OF EVENTS 12.1 General A. The Contractor shall furnish County with a detailed project schedule in bar chart form identifying all major milestones, to meet the critical delivery, installation and testing dates and task duration as specified in Section 2.0. The following items shall be addressed as a minimum: 1. Submittals and Documentation 2. Design Phase 3. Software Development 4. Manufacturing 5. In- Factory Testing 6. Shipping of System Equipment 7. Installation 8. Installation Verification 9. Testing (by test) 10. Final System Acceptance B. The Contractor shall prepare all deliverables in both Microsoft Office (Word, Excel or PowerPoint) and Adobe PDF formats, with County granted full rights to reprint as needed. 12.2 Project Status Tracking The Contractor shall prepare a System Implementation Plan (SIP), including the detailed implementation activities/ schedule, progress milestones/ status and assigned staff. The Contractor shall also include a Safety Management Plan in their SIP, which shall detail their responsibilities and procedures for safety during the different phases of the project, including (1) conducting pre - installation surveys to identify potential project safety hazards; (2) identifying project hazard control procedures, including occupational (worker) and public hazards; (3) providing project safety orientation and training to its subcontractors and the transit agency staff who will be involved in the project; and (4) furnishing procedures and training for project accident reporting and investigations, The initial draft of the SIP shall be provided to County within two weeks from Notice to Proceed (NTP). The revised SIP, addressing comments from the first onsite meeting, shall be provided to County within two weeks after this meeting. The SIP must be approved and accepted by County before it can become effective. An updated SIP shall be submitted to County at the beginning of each month. Page 70 of 79 16A 8 The Contractor shall maintain an Action Items List (AIL), indicating for each item the following: (1) item number; (2) date generated; (3) brief item descriptive title; (4) assigned person with lead resolution responsibility; (5) date resolved; and (6) ongoing dated notes on resolution status. The AIL shall be sorted, primarily by unresolved vs. resolved items and secondarily by the date the item was generated. 12.3 Program Plan The Contractor shall prepare and submit a Preliminary Program Plan for County approval within ten (10) days of Notice to Proceed. The Preliminary Program Plan shall be a summary document indicating the manner in which the Contractor has broken down the major tasks necessary to comply with the Contract requirements. 12.4 Project Schedule The Contractor shall, within ten (10) days of notice to proceed, submit a reproducible copy of the project schedule showing the start and completion of all major events, operations and contract items planned for County approval. The Contractor shall update the project schedule on a monthly basis and forward the updates to County to reflect revised completion dates. The Contractor shall notify County immediately of any changes that are expected to delay the completion of the project more than two (2) weeks. 12.5 Monthly Progress Report and Weekly Conference Calls The Contractor shall participate in weekly conference calls with County Project Manager, other County staff and outside consultants as determined by County Project Manager. The agenda for these meetings will be to discuss the most current status of and plans related to all issues identified in the recent releases of the SIP and AIL. County reserves the right to identify for discussion any additional issues beyond those in the SIP and AIL. A status report shall be issued to County at least two days prior to each conference call, including (1) an agenda for the upcoming conference call highlighting key discussion items; and (2) an updated AIL with the updates incorporating the discussions of the previous bi- weekly conference call as well as other subsequent developments since the previous AIL release. The Contractor shall be represented in these conference calls by at minimum their Project Manager, as well as any additional Contractor staff necessary to properly address the current issues and project status. County will be represented by their designated implementation management representatives. Conference call facilities will be arranged and paid for by the Contractor. The Contractor shall submit minutes within two days of each conference call. Each month the Contractor shall submit a report describing work accomplished in the preceding month, work to be completed during the next month, and a discussion of any outstanding or expected problems. County approved modification to the project schedule shall be included as part of the report. In addition, monthly progress reports shall include a list of specific action items which require input or resolution by the parties involved in the project. 12.6 Minimum Required Onsite Work At the first onsite meeting, the Contractor shall be prepared to discuss County feedback on draft SIP and conduct Requirements Review. Page 71 of 79 16A 8 At the second onsite meeting, the Contractor shall be prepared to discuss County feedback on draft Design Review documentation. During the third and subsequent onsite efforts, the Contractor shall install system and conduct acceptance testing. These onsite installation and testing efforts will occur over an extended period, and will likely involve several different onsite trips and a range of different Contractor staff. 12.7 Invoicing The Contractor shall only submit an invoice once a fully - signed Acceptance Certificate is generated by County indicating that a progress payment milestone has been achieved. County will withhold 10% retainage on each invoice. Upon acceptance by County of each stage of the project, the total retainage for that stage will be paid to the Contractor. 12.8 Design Review The Contractor shall participate in the Requirements Review (RR), as part of the first onsite meeting. The RR meeting shall discuss, for each contract requirement, the following: (1) County design intent; (2) the intended Contractor design approach; and (3) the general Contractor approach to demonstration through the acceptance testing process. The Contractor shall submit draft Design Review Documentation (DRD) within four weeks of the RR meeting. The DRD shall include the following materials: (1) an overview of the equipment, system and configuration proposed for implementation; (2) detailed technical documentation for each equipment item; (3) detailed technical documentation on all software, addressing the functions of each module, the format of all user interface screens, the format of all reports, the data fields to be included in all data exchange interfaces and any other software aspects warranting advance agreement with County prior to system customization/ configuration; and (4) a table detailing the approach taken in the design to address each individual contract requirement. The second onsite meeting will include discussions with County on their feedback on the DRD, and shall occur within four weeks after the draft DRD has been submitted. The Contractor shall submit the updated DRD within three weeks of the second onsite meeting. The DRD is intended only to reduce the chance of any misunderstandings on the design intent or interpretation of the contract requirements. The DRD shall not alter the need for the successful formal demonstration of each requirement through the Acceptance Testing process The Contractor shall submit Installation Design Documentation (IDD), for County approval prior to undertaking any installations. The IDD shall provide text, drawings, illustrations and images using adequate detail to allow for quality installation by a technician without further training in conjunction with other installation instructions provided by the vendors of individual equipment components. The IDD shall include details on (1) equipment installation locations/ mounting; (2) routing, conductors, color - coding, labeling, and connectors for power, communications and vehicle ground circuits; (3) connections with, any required modifications to and restoration of existing infrastructure; (4) work area and equipment storage requirements (5) methods and quality standards; and (5) supervision and quality assurance procedures. END OF SECTION Page 72 of 79 • XIII WARRANTY 13.1 General A. Basic Warranty The Contractor shall guarantee all workmanship, materials, components and equipment for a period of one (1) year after installation and full acceptance of the fare collection system. If during the period of the warranty any defects or faulty materials, equipment or software are found, the Contractor shall immediately, upon notification from County, proceed with corrective action at the Contractor's expense to replace, repair or otherwise return the system to full working order. 3. The Contractor shall provide sufficient spare modules and parts to operate the system at not less than 99% availability at any time for the period of the initial warranty. These spare parts shall be furnished with the first equipment delivery. 4. The Contractor shall develop, test, and provide all applicable software "patches," upgrades and other remedies necessary to keep the system software in good order. The installation of such remedies will be performed by the County in close coordination with the Contractor. 5. All Proposers shall submit, with their proposals, a copy of their standard warranty as well as any special terms and conditions covering the equipment and software described in these specifications. B. Extended Warranty The contract includes a total of 5 years warranty for all the equipment 13.2 Coordination with On -Going Maintenance Support The basic and extended warranty provisions of this section are intended to be in conformance with and enhance the provisions of the section of these specifications describing Maintenance Support during the period in which the basic and extended warranties are in place. END OF SECTION XIV. MAINTENANCE SUPPORT 14.1 Support Requirements A. From Installation to System Acceptance Contractor shall provide on -site personnel qualified to troubleshoot all aspects of the system from the time of first equipment installation through system acceptance. These personnel shall be responsible for preventive maintenance, troubleshooting failures, removing and replacing defective parts, returning the unit to service, and initiation and follow -up of remedial actions. As an alternative, the Contractor may use County maintenance personnel to perform some or all of these activities at the Contractor's sole additional expense as long as regular maintenance of County buses and facilities is not affected. B. From System Acceptance Through Warranty Period Contractor shall assist County maintenance personnel in performing preventive and corrective maintenance including troubleshooting, removal of replacement parts and any warranty repairs, service, and campaigns. Both on -call telephone support and on -site technical support, when required by County for troubleshooting and support, shall be provided as part of the system warranty. Page 73 of 79 16A 81 Contractor's field representatives shall also be available for a minimum of three (3) visits to the location where equipment is installed during the period between system acceptance and expiration of the warranty to provide general aid and instruction to transit system personnel. In the event of a fleet defect that appears to County's project administrator to be a generalized problem that may affect all similar equipment, or a systematic defect (a defect in the data system, receivers or other subsystems that affects the ability of the fare collection system to achieve its intended purpose) the manufacturer's representative shall arrive as soon as possible, but no later than thirty-six (36) hours from the time of notification, at the County facility to review the problem and set up needed corrective action. The Contractor shall contract with a qualified company approved by County that can be called on for maintenance of the computer hardware and standard operating software and short response time critical troubleshooting on an emergency basis when the Contractor's staff may not be available. C. After Expiration of Warranty On -call maintenance support shall be provided by the Contractor for the life of the equipment after system acceptance. On -call support shall be provided via telephone conversation for hardware and software problems and operational troubleshooting at no additional cost to the County. On -site technical support, when required for troubleshooting, training or other similar activities required by County shall be provided at standard Contractor rates as per Exhibit B for preferred customers. D. The Contractor shall provide the maintenance support and warranty services described in these specifications to cover all depots on all equipment required to be provided by the Contractor. E. Contractor shall maintain on -site, a spare parts supply sufficient to meet maintenance and warranty obligations set forth herein from installation through the end of the five (5) year warranty period. 14.2 Test Equipment A. The Contractor shall supply test equipment which shall provide means for County maintenance personnel to bench test and repair each major module and /or subassembly of the on -board fare collection equipment. B. Maintenance Test Stand (Optional): This equipment shall be configured such that the following items are mounted on a stand or board and interconnected to provide a fully operational set of on -board fare collection equipment, plus software installed on a heavy duty service laptop computer to act as a fully functioning FCMRS. The maintenance test stand shall include at a minimum the following separate components: 1. Bill transport, including security mechanism 2. Coin unit 3. Logic boards 4. Data port to probe data 5. Data transfer probe 6. Electronic lock assembly 7. Cashbox ID unit 8. All displays and the tone generator(s) 9. Power supply 10. Magnetic swipe reader 11. Ticket processing unit C. All interconnections including wiring, harnesses, plugs, sockets and other connections shall be the same as used in a fully assembled Fare Collection System. The maintenance test stand shall be arranged in such a manner that each module can be separately exercised to perform its operating functions. D. Coin Unit Calibrator: Equipment shall be provided to calibrate and test the coin unit and related components. Page 74 of 79 16A 8 1 E. Bill Transport Calibrator: Equipment shall be provided to calibrate and test the bill transport and related components. 13.3 Availability and Performance Requirements A. During the period when Contractor personnel are on -site: 1. Maintenance on fare collection equipment aboard the buses shall be performed in such a manner as to provide for 100% availability of all buses needed by County to meet pull -out each day at each depot. 2. Farebox equipment shall be brought back into service within four (4) business hours of reporting any incident. This shall be by module swap out or correction of the problem. B. During the period when on -call service is provided: 1. All questions shall be answered and requests for information shall be provided within a twenty - four (24) hour period. 2. Spare parts requested by County shall be delivered within forty -eight (48) hours of receipt of fax, email or telephone request from County. 3. Correction of software deficiencies shall be completed within a time as agreed between County and the Contractor, based on the severity and critical nature of the deficiency. At no time however, shall this time period exceed ten (10) business days, unless prior approval is provided in writing by County. 13.4 Computerized Maintenance Reports As an integral part of maintenance support, the Contractor shall include computerized reports as described in other sections of this specification that are designed to assist County to perform regular preventative maintenance on systems, equipment and components provided in these specifications. This shall include preventative maintenance scheduling as well as warning and alarm conditions and adequate training of maintenance managers and technicians in the proper and regular use of this capability. END OF SECTION n� Page 75 of 79 Martha S. Vergara From: Sent: To: Cc: Subject: Tracking: Morning All, 16A`*8R Martha S. Vergara Tuesday, May 15, 2012 10:31 AM DeLeon, Diana; Cummings, Rhonda; Teach, Scott; Patricia L. Morgan Mitchell, Ian Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract # 11 -5753) Recipient DeLeon, Diana Cummings, Rhonda Teach, Scott Patricia L. Morgan Mitchell, Ian The aforementioned contract has the following issues: Read Read: 5/15/2012 10:34 AM 1. The agenda provided to the Board is the same as one contract (the one that starts with page 15 of 79) but is missing the first 14 pages and pages 76 through 79. 2. One contract starts with page 1 of 61, the other starts with page 15 of 79 (again missing pages 1 through 14 and 76 through 79) — Exhibit A Scope of Services. Thanks, Martha Vergara, Deputy Clerk Minutes and Records Dept. Clerk of the Circuit Court & Value Adjustment Board Office: (239) 252 -7240 Fax: (239) 252 -8408 E -mail: martha.vergarana,colherclerk.com 1 Martha S. Vergara From: MitchellIan <IanMitchell @colliergov.net> Sent: Tuesday, May 15, 2012 10:32 AM To: Martha S. Vergara Subject: Read: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Attachments: Read: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Under Florida Law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by telephone or in writing. 16A 8 Martha S. Vergara From: Patricia L. Morgan To: Martha S. Vergara Sent: Tuesday, May 15, 2012 10:34 AM Subject: Read: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Your message To: Patricia L. Morgan Subject: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Sent: Tuesday, May 15, 2012 10:31:12 AM (UTC- 05:00) Eastern Time (US & Canada) was read on Tuesday, May 15, 2012 10:33:33 AM (UTC- 05:00) Eastern Time (US & Canada). Martha S. Vergara 16A 8olr.. From: MitchellIan <IanMitchell @colliergov.net> Sent: Tuesday, May 15, 2012 10:34 AM To: Martha S. Vergara Cc: Patricia L. Morgan Subject: RE: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract # 11 -5753) Thank you good email. From: Martha S. Vergara jmai Ito: Martha.Veraara colIierclerk.coml Sent: Tuesday, May 15, 2012 10:31 AM To: DeLeonDiana; CummingsRhonda; TeachScott; Trish L. Morgan Cc: MitchellIan Subject: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Morning All, The aforementioned contract has the following issues: 1. The agenda provided to the Board is the same as one contract (the one that starts with page 15 of 79) but is missing the first 14 pages and pages 76 through 79. 2. One contract starts with page 1 of 61, the other starts with page 15 of 79 (again missing pages 1 through 14 and 76 through 79) — Exhibit A Scope of Services. Thanks, Martha Vergara, Deputy Clerk Minutes and Records Dept. Clerk of the Circuit Court & Value Adjustment Board Office: (239) 252 -7240 Fax: (239) 252 -8408 E-mail: martha.vergara ,collierclerk.com Please visit us on the web at www.colliercierk.com This electronic communication is confidential and may contain privileged information intended solely for the named addressee(s). It may not be used or disclosed except for the purpose for which it has been sent. If you are not the intended recipient, you must not copy, distribute or take any action induced by or in reliance on information contained in this message. Unless expressly stated, opinions in this message are those of the individual sender and not of the Office of the Clerk of the Circuit Court of Collier County. If you have received this communication in error, please notify the Clerk's Office by emailing helpdesk @collierclerk.com quoting the sender and delete the message and any attached documents. The Collier County Clerk's Office accepts no liability or responsibility for any onward transmission or use of emails and attachments having left the CollierClerk.com domain. Under Florida Law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by telephone or in writing. Under Florida Law e -mail addresses are public records. If you do not want your e -mail address released in response to a public records request, do not send electronic mail to this entity. Instead: contact this office by telephone or in writing. Martha S. Vergara 16A 8 From: DeLeonDiana <DianaDeLeon @colliergov.net> Sent: Tuesday, May 15, 2012 10:43 Affil To: Martha S. Vergara Subject: Read: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Attachments: Read: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Under Florida Law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by telephone or in writing. 16A g Martha S. Vergara From: TeachScott <ScottTeach @colliergov.net> Sent: Tuesday, May 15, 2012 10:49 AM To: Althouse, Tammy Cc: Mitchell, Ian; Martha S. Vergara; Cummings, Rhonda; Patricia L. Morgan; DeLeon, Diana Subject: RE: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract # 11 -5753) Tammy, Please pick up this contract from Martha so we can review and make sure that the exact contract on the agenda is attached. Scott R. Teach Deputy County Attorney Collier County, Florida Tel: (239) 252 -8400 Fax: (239) 252 -6300 Office of the County Attorney, 3299 East Tamiami Trail, Suite 800, Naples, FL 34112 Under Florida Law, e -mail addresses are public records. if you do not want your e -mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by telephone or in writing. From: Martha S. Vergara [ mai Ito: Martha.Vergara @colIierclerk.com1 Sent: Tuesday, May 15, 2012 10:31 AM To: DeLeonDiana; CummingsRhonda; TeachScott; Trish L. Morgan Cc: MitchellIan Subject: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Morning All, The aforementioned contract has the following issues: 1. The agenda provided to the Board is the same as one contract (the one that starts with page 15 of 79) but is missing the first 14 pages and pages 76 through 79. 2. One contract starts with page 1 of 61, the other starts with page 15 of 79 (again missing pages 1 through 14 and 76 through 79) — Exhibit A Scope of Services. Thanks, Martha Vergara, Deputy Clerk Minutes and Records Dept. Clerk of the Circuit Court & Value Adjustment Board Office: (239) 252 -7240 Fax: (239) 252 -8408 E -mail: martha.vergara kcollierclerk.com 1 16A 84 Please visit us on the web at www.collierclerk.com This electronic communication is confidential and may contain privileged information intended solely for the named addressee(s). It may not be used or disclosed except for the purpose for which it has been sent. If you are not the intended recipient, you must not copy, distribute or take any action induced by or in reliance on information contained in this message. Unless expressly stated, opinions in this message are those of the individual sender and not of the Office of the Clerk of the Circuit Court of Collier County. If you have received this communication in error, please notify the Clerk's Office by emailing helpdesk(cbcollierclerk.com quoting the sender and delete the message and any attached documents. The Collier County Clerk's Office accepts no liability or responsibility for any onward transmission or use of emails and attachments having left the CollierClerk.com domain. Under Florida Law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by telephone or in writing. 16A 8 : Martha S. Vergara From: DeLeonDiana <DianaDeLeon @colliergov.net> Sent: Tuesday, May 15, 2012 11:47 AM To: Teach, Scott Cc: Mitchell, Ian; Martha S. Vergara; Cummings, Rhonda; Patricia L. Morgan; Althouse, Tammy; Ward, Kelsey Subject: RE: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract # 11 -5753) Scott, Kelsey and I figured out what happened. I've printed out Exhibit A, with the numbering matching Agenda Central, and will be taking two copies to Minutes and Records. Regarding the original contract, you had requested the proposal and RFP be added to it, and I walked those documents over to CAO that same day. However, Minutes and Records has not received that item yet. Please check to see if the original contract 11 -5753 with Fare Logistics is still at CAO. Thanks, Viana Viaz `%%Coon, CPPS Collier County BCC Purchasing Dept. 3327 Tamiami Trail East Naples, FL 34112 Phone: 239/252 -8375; Fax: 252 -6597 From: TeachScott Sent: Tuesday, May 15, 2012 10:49 AM To: AlthouseTammy Cc: MitchellIan; Martha S. Vergara; CummingsRhonda; Trish L. Morgan; DeLeonDiana Subject: RE: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Tammy, Please pick up this contract from Martha so we can review and make sure that the exact contract on the agenda is attached. Scott R. Teach Deputy County Attorney Collier County, Florida Tel: (239) 252 -8400 Fax: (239) 252 -6300 Office of the County Attorney, 3299 East Tamiami Trail, Suite 800, Naples, FL 34112 Under Florida Law, e -mail addresses are public records. If you do not want your e -mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by telephone or in writing. From: Martha S. Vergara jmai Ito: Martha .Vergara(&colIierclerk.coml 1 0 A Sent: Tuesday, May 15, 2012 10:31 AM To: DeLeonDiana; CummingsRhonda; TeachScott; Trish L. Morgan Cc: MitchellIan Subject: Agenda Item #16A8 from the 5/8/2012 BCC Meeting (Amendment #1 for Contract #11 -5753) Morning All, The aforementioned contract has the following issues: 1. The agenda provided to the Board is the same as one contract (the one that starts with page 15 of 79) but is missing the first 14 pages and pages 76 through 79. 2. One contract starts with page 1 of 61, the other starts with page 15 of 79 (again missing pages 1 through 14 and 76 through 79) — Exhibit A Scope of Services. Thanks, Martha Vergara, Deputy Clerk Minutes and Records Dept. Clerk of the Circuit Court & Value Adjustment Board Office: (239) 252 -7240 Fax: (239) 252 -8408 E -mail: martha.vergara&collierclerk.com Please visit us on the web at www.collierclerk.com This electronic communication is confidential and may contain privileged information intended solely for the named addressee(s). It may not be used or disclosed except for the purpose for which it has been sent. If you are not the intended recipient, you must not copy, distribute or take any action induced by or in reliance on information contained in this message. Unless expressly stated, opinions in this message are those of the individual sender and not of the Office of the Clerk of the Circuit Court of Collier County. If you have received this communication in error, please notify the Clerk's Office by emailing helpdesk @collierclerk.com quoting the sender and delete the message and any attached documents. The Collier County Clerk's Office accepts no liability or responsibility for any onward transmission or use of emails and attachments having left the CollierClerk.com domain. Under Florida Law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by telephone or in writing. 16A 8n MEMORANDUM Date: May 15, 2012 To: Diana De Leon, Contract Technician Purchasing Department From: Martha Vergara, Deputy Clerk Minutes & Records Department Re: Amendment #1 to Contract #11 -5753 "Electronic Fareboxes" Contractor: Fare Logistics Corporation Attached is an original copy of the referenced above (Agenda Item #16A8), which was approved by the Board on Tuesday, May 8, 2012. An original has been kept by the Minutes and Record's Department, and will be kept as part of the Board's Official Records. If you have any questions, please contact me at 252 -7240. Thank you • [MR, • EXHIBIT A -1 Contract Amendment #1 to Contract 11 -5753 "Electronic Fareboxes" This amendment, dated ING�j 2012 to the referenced agreement shall be by and between the parties to the original Agreement, Fare Logistics Corporation (to be referred to as "Contractor ") and Collier County, Florida, (to be referred to as "County "). Statement of Understanding RE: Contract # 11 -5753 "Electronic Fareboxes" The Contractor agrees to amend the above referenced Contract by replacing Exhibit A -Scope of Services with the attached Exhibit A -Scope of Services, which incorporates technical clarifications to the original language. The additions to the existing language are shown herein by underlining; deletions are shown by All other terms and conditions of the agreement shall remain in force. IN WITNESS WHEREOF, the Contractor and the County have each, respectively, by an authorized person or agent, hereunder set their hands and seals on the date(s) indicated below. ATTEST: �t E. Brock, Cl( ARM 4$ to 061* Approved as to form and Le sufficienc putyCounty Attorney ,l& 11 y -A e_4 A 1 Name 1 OWNER: BOARD OF COUNTY COMMISSIONERS COLLIEP,tCQVNTY, FLORIDA By: W. Fred W. Coyle, Chairman First Witness TType /print witness nameT Second Witn s 71 M Lc-fty nl TType /print witness nameT Oi� NAYAN P. GHELANI Commission # 1825490 z Notary Public - California z Riverside County My Comm. Expires Dec 31, 2012 1 Fare Logistics Corporation Contractor By: Signature , MuQS�a Typed signature and title Vii-- .—j County d S ' bdoro me personaAy who proved to me on the basis of satisfactory evidence to be the persons whose nanhe(s) is/aifsubscribed to the within intrurnent and acknowledged to me llhatbd� executed the same In bib wAbOW authorized capadty(ies), and that by tWherO* sonallure(s) an the msWment the persons), or the entity upon b" of which the person(s) acted, executed the instrument. I cww V Qu Y wider the laws d the d Cabtomie tM the parawo Is bw OW M. WITNESS my hand and official seal. Mat EXHIBIT A Scope of Services 11 -5753 Electronic Fareboxes Contract Overview The tasks and sub-tasks listed below are based on a current understanding of the project requirements. During the progression of the project, the County project manager and project manager for the Contractor Will monitor the progress of each task and sub-task, and ad-just the resource allocation and. schedule as needed. The administration of the contract shall be as follows: 1. Any changes shall be mutually agreed upon in writing, but will not require a formal change order unless the change(s) would exceed the overall contract amount. 2. It is expressly stated and understood by the parties that zero dollar changes, including, but not limited to, time extensions not exceeding 20% of the overall contract, and time and/or sequence changes to Milestones may be made through the use of a Change by Letter signed by the County Project Manager or his/her Designee. 3. The Change by Letter will include a line for the Consultant's representative or designee's signature. Copies of the duly signed letter shall be forwarded to the appropriate Procurement Strategist for final signature and forwarding to the Finance Division. 1. Work to Be Performed By Contractor The Contractor shall perform the following work: A. The Contractor shall be responsible for all work and. expenses relating to the design, manufacture, delivery and installation of the equipment to the Collier Area Transit ("CAT") facility. B. Project to be completed, and final invoice must be submitted by February 28, 2013. C. The equipment, subsequent to testing, shall be complete in every respect and suitable for revenue service. D. For those items of equipment to be installed by the Contractor, the Contractor shall provide all hardware and other materials and all personnel and supervision necessary for installation in accordance with the schedule proposed by the Contractor and approved byCDunty. 1, The Contractor shall supply such materials and supervision as may be necessary for the proper configuration and installation of the fireboxes, revenue equipment, Fare Collection Management and Reporting System (FCMRS) and any options exercised by County. All equipment shall be tested in accordance with a startup test procedure to be developed by the Contractor and approved by County. The Contractor shall provide on-site supervision of all installation efforts at all. times during the installation. The Contractor shall adhere to the agreed installation schedule and procedures and provide the necessary documentation of work performed during the installation work. 2. The Contractor shall remove the existing fare collection system, including all existing fareboxes from the buses and the revenue servicing equipment in the cashbox vaulting lanes of the CAT facility,, The Contractor shall be responsible for transporting such removed items to a central storage location at or near the CAT facility as designated by County. Page 15 of 79 3, For those items of equipment to be installed by the Contractor, a list shall be provided of all items of hardware and the required Contractor and CAT personnel and supervision for installation work in accordance with the schedule proposed by the Contractor and approved by County. 4. Contractor shall provide personnel to supervise, inspect and adjust the equipment prior to, during and through final acceptance of the final system. F. All equipment shall be of the latest engineering change level available and shall incorporate suitable modifications for all known operational problems identified during the PLR/ CDR reviews and during testing at factory. The Contractor shall retrofit all known problem solutions (engineering changes) to the equipment installed prior to the initial testing and any additional upgrades, recalls, campaigns, etc. that are made available to other customers during the warranty period, The Contractor shall notify County in writing of all such upgrades. F. The Contractor shall propose an installation schedule for the CAT's approval. Installation shall. be completed over two (2), two-day weekends. G. The Contractor shall deliver the equipment to the location specified by the County, for purposes of temporary storage. County will provide suitable storage facilities prior to installation of the equipment and will assume sole responsibility for the equipment while in storage. H. Revenue collection vault(s) equipment, software and specifications shall be provided by contractor to County. L County will provide a specific unobstructed site at its facility for the installation of the vault. This site shall be level and of suitable construction for such installation, if it is necessary to pour a concrete pad for the vault, County will be responsible for this work as well as for the construction of the vault; and the contractor shall be responsible to provide required pad size din-tensions, load requirements, and mounting hardware to be embedded in the pad and any electrical or data conduit requirements that are to be embedded in the pad. J. The Contractor shall make available full and competent engineering services to identify and correct all problems associated with the performance of its equipment in a timely manner. K Contractor shall be responsible for repairs under the terms and conditions of the warranty and maintenance support provisions indicated herein. Subsequent to the warranty period any parts, assemblies, and I - equipment shipped to the Contractor for repairs shall be subject to repair charges in accordance with an agreed upon schedule of prices or quotation for parts and labor. L. The Contractor shall provide the services of a qualified representative to meet with County to provide consultation and instructions regarding installation of the equipment specified herein. For operation of fareboxes on the bus, the Contractor shall use the existing DC electrical power available on CAT buses. N1. The Contractor shall prepare all deliverables in both Microsoft Office (Word, Excel or PowerPoint) and Adobe PDF formats, with County granted full rights to reprint as needed. N. All. work shall. be in accordance with the schedule described herein or a modified schedule approved in writing by the County. O. The Contractor shall inspect the existing bus fleet and the power available with the existing batteries to ensure that there is sufficient power available for operation of the new Fare Collection System. If there are any deficiencies, these shall be identified by bus type to the County for a mutually acceptable resolution of the issues. 1. Where data systern installation or other electrical installation is involved, the Contractor shall be responsible for all work involved and must coordinate with the County's CAI' and. IT staff in the running of any overhead or underground conduits for data cable, stringing supported or unsupported cables from probe points to the computer and providing adequate electrical service for the equipment provided. Plans for such work shall be approved by County and meet all requirements of all applicable building codes. Page 16 of 79 16A 8 2. Electrical requirements and all cable to the extent indicated in these specifications shall be furnished by the Contractor. Contractor shall inspect and coordinate with the County's IT staff the site where the facility equipment is to be installed and determine with County's approval if the existing conduit can be used within the new fare collection system. Contractor shall certify that this effort has been completed and include the usage of the existing conduit in the installation plan if such use is found to be. appropriate. I The Contractor shall provide the services of a qualified representative to meet with representatives of County involved in this procurement to provide consultation and instructions relative to the proper provisions and work for the installation of equipment specified in these specifications. P. The Contractor shall furnish electrical requirements and all cable to the extent indicated in these specifications. Q. The Contractor shall be responsible for providing base dimensions and load requirements. Provisions shall be included by the Contractor to allow for the vaulting area to include methods to minimize the effect of moisture in the vault location to degrade the operation and/ or security of the vaulting equipment. R 'The Contractor shall be responsible for hosting computer hardware and software required as part of the FCMRS (please refer to Section 5 for further requirements). County shall be able to access this hosted system over a secured network without any Contractor intervention, unless necessary for software support. The database used in the hosted FCMRS shall be secured and County shall be the complete owner of the data. County shall have full system administrator privileges to manage the user access levels and password-protection for the FCMRS. S. The Contractor will deliver the County's requested "remote Hosted solution," which will encompass the Contractor maintaining the Transfare system. database, wireless communication to farebox devices for revenue data collection, installation of the TransMedia workstation connected to the Contractor's Private Network, as well as an. ISP web portal to be used for County management to access reporting by means of a website URL to access the TransFare system. 11. Work to Be Performed By County A. Countv will make buses available to the Contractor for installation work. County shall Provide movement of buses as necessary. County shall approve all installation plans and procedures by the Contractor. B. County shall assist the Contractor in coordinating the actual farebox and other equipment installation. County will provide a mechanic and supervisor at the facility location where installation tasks are performed. C. County will provide AC power for all tools and lighting needed by the Contractor for physical installation. D. County will provide adequate storage space at its facility location to store the fareboxes and related equipment upon delivery from the Contractor. This storage shall be secure and protected from the weather. County shall also provide personnel and material. handling equipment to bring the fareboxes (and other equipment) from such storage place to the designated installation sites. E. County will be responsible for and provide any and all material handling equipment and personnel required to lift or otherwise manipulate the vaults, collection bins, or their contents during day-to-day revenue transfer operations. F County will provide a specific unobstructed site at its facility for the installation of the vault This site shall be level and of suitable construction for such installation. If it is necessary to pour a concrete pad for the vault, County will be responsible for this work as well as for the construction of the vault; and the Contractor shall be responsible to provide required pad size dimensions, load requirements, and mounting hardware to be embedded in the pad, and any electrical or data conduit requirements that are to be embedded in the pad. G. County shall provide 120 VAC, 15 amp electrical services in proximity to the agreed upon location for the ,4aiil of-45;4R V-1Ult. Page 17 of 79 Il County shall coordinate with the Contractor regarding the system configuration of computer hardware and software required as part of the remote hosting of FC&RS at Contractor's facility. III General Design Requirements The fare collection system specified herein shall be designed to function in the intended transit environment specified. All normal conditions for this environment, including, but not limited to dust, moisture, electromagnetic interference, power line fluctuations, vibration, and exposure to atmospheric conditions shall not affect the reliability or service life c6 the equipment provided. The range of these environmental conditions shall be tested during the First Article Testing (FAT). A. Design Life -The fare collection system hardware and software *buU he designed to provide a usable life for a minimum of twelve (12) years subject to proper preventive maintenance being performed. & Modular Components -_All equipment ybaU be designed d-na modular, Modules from equipment of the same type shall be exchangeable between items of equipment without 6urd`°nne or physical modification. Components, sobsyabems, assezo66es, and so6uxs0006Gey shall be of modular design for ease of maintenance and interchangeability and shall conform to the operational, storage and functional requirements as incorporated herein. C. Human Engineering l. The fare collection system hardware and software shall be designed to provide for ease of use by a Properly trabnedbzdivid�za. 2 All software shall. 6e designed to be user friendly, allowing the user to access all features through graphical user interfaces, pull down menus, and on-line help features based on assigned password privileges. D. Interchangeability All of the equipment furnished shall be identical in manufacture and functiooThe equipment and the components of the equipment shall be completely interchangeable. E. Maintainability and Accessibility 1. All. components shall 6e packaged. to replaceable and repairable modules. Standard hardware and components oba8 be used for flexibility and ease of maintenance. Standardized cnmmezcbdly available hardware and components shall be used to achieve flexibility in use and to facilitate maintenance. There shall be sufficient latitude in the operating tolerances to permit the substitution of modules without the necessity of making any electrical ormechanical adjustments, KJm6ulea and sub'assenm6lieeshoObeeumilvaccem8leoodreouovob\evvi8zootL6eneedfo«aoecialhouis. z� All system elements provided under this contract to bc used 6y the general public shall conform to the requirements that are bn effect on the date. nf this proposal, For the purposes of this specification, all references to f\D6 requirements shall include the requirements imposed by any and all of the laws and regulations. 3. Entry codes shall be performed using internal with delayed alarm triggered if the proper code is not used. In equipment which contains revenue, the use of an internal access code and exterior access control system (PIN code, identification card or other security scheme) a6oD be required. F. Security and Safety All faze collection equipment shall be designed, manufactured, assembled and installed in a safe manner. Once the system binstalled and available for use, there shall be no hazard to the public upon use of the fare collection equipment. The faze collection equipment shall pass o safety verification ao part o6 the First Article Test. G. External Surface Page 1. 8 of 79 16A 8;-1 I , External surfaces of all system equipment shall be clean, with no projections, sharp edges or corners that can cause any person injury or damage to property. External surfaces shall not contain cracks, weld marks, burrs, discolorations, or distortions resulting from fabrication, shipment or installation. 2. Surfaces not of stainless steel, aluminum, or plated shall be painted with a corrosion resistant paint. Painted surfaces shall be free of rust, scale, grease and foreign matter immediately preceding the first priming coat. Paint applied to any internal surface shall be designed to last for the life of the particular component to which it is applied. Paint applied to any external surface shall be baked enamel or other coating designed to last for a minimum of twelve (12) years before needing to be repainted. 1 The Contractor shall spray paint and bake all surfaces that are painted in order to give them a hard enamel finish. Any paint shall be uniformly applied over all surfaces to be covered, and shall be free from runs, sags, dirt or other application defects. 4. Color, metal protection materials and processes, and finish of all paintwork to be used on internal and external surfaces of all lane equipment shall be subject to County selection and approval. H. Locks 1. The Contractor shall provide all cashbox vaulting lane equipment with locked covers to prevent unauthorized access. 2. System equipment of the same type shall have identical locks that open with the same key number, and each type of equipment shall require different key numbers for access. 1 Separate access shall be provided, where possible, for operating personnel to perform routine maintenance and shall be keyed differently to equipment areas requiring access only by technical maintenance personnel. I. Reliability 1. The reliability of the fare collection shall be as follows at the conclusion of all acceptance testing: • FaTebox: 2,000 Mean Cycles Between Failures • RCVS 10,000 Mean Cycles Between Failures 2. One (1) cycle for the farebox shall be defined as one (1) complete fare verification at a farebox, including required bus operator button presses. 3. One (1) cycle for the R(--VS shall be defined as one (1) complete emptying cycle of a cashbox into the receiver vault. END OF SECTION IV. ON-BOARD EQUIPMENT The farebox shall be a mounted, freestanding device used to collect and securely store fares using a variety of fare media. This shall include processing cash, tokens and magnetic transfers and passes. The farebox shall be controlled by electronic logic and supported by electronic memory, displays and indicators. It shall permit the easy insertion of fare media by boarding customers; provide a display for customer information; and an CCU with human factors engineering practices and industrial design considerations. 'The farebox shall be reliable in revenue service operations, accurate in its counting and data reporting, and secure in its retention and transfer of data and collected revenue. Under normal operating conditions, processing of fares shall require the minimum effort by bus operators to accurately and correctly account for customer fare payment and collection of revenue. Operational. Features -- -The farebox shall have the following operational features: Accept, validate, count and register US coins and paper currency, • Return coins, bills and tokens and other objects that are not valid or acceptable to the system; • Accept, validate and count magnetic farecards,- • Print and issue a transfer, day pass and other agreed-upon types of passes; Page 19 of 79 16A 8 • Print, encode and issue a farecard for fare overpayment (i.e., a "change card") • Permit the recording of various types of fare transactions using bus operator activated pushbuttons. 4.1 General Requirements A. The fareboxxadefinedwithin these specifications, shall include all hardware and software installed m+ board any CAT bus for purposes of accepting payment of the fare byucustomer by: cash, token (as defined by County) and magnetically coded transfers and paoa*y as valid fare payment methods. The system software and hardware shall include means for validation and acceptance of new currency to be issued in the future 6y the United States Treasury Department. B. Tbebreboz shall be installed no each bus, adjacent to the bus operator, and in proximity o6 the front door. It shall be positioned so that an entering customer znay easily insert the required fazes into the 6,rc6ox, using fare payment of coins without blocking exiting customers. This position shall permit the bus operator to reuddy determine the customer's fare payment method, observe all of the digital readouts provided on the bus operator side of the 6muebox (including the OCD), and reach and manipulate various bus operator controls from the seated position. The farebox location shall permit all of the required maintenance functions to be performed, as well as to provide easy access for the removal of the cashbox and meet all ;\DA requirements for customer entry and exit. C The mounting of the farebox shall be designed to minimize movement oz rattling of the brebox. D. Be farebox shall be a solid-state logic controlled validating farebox with supported memory used to accept, validate, count and securely store paid fares. E. The farebox shall function under the environmental and operational conditions stated in these specifications and shall he designed and manufactured to provide a high degree of security against forced entry into the cashbox area and/or unauthorized manipulation of farebox modules. F. The fureboxshall permit the customer toeayilyand rapidly insert the required fares and for the bus operator to zeeJUv ascertain that the correct fare has been paid, regardless of the fare payment method employed. The capacity of the 6zebox shall he such o*Loaecuoeiy retain the collected fares until such time as thev are removed under authorized conditions. The farebox shall function in a reliable manner so as to provide service on an uninterrupted 6uas' consistent with the performance requirements contained herein. G. The faTebox shall function to provide specific information relative m the daily operations of the farebox; the revenue amounts, types and quantities of customers; bus operator and work run identifica��bus location daba, and other information which may be used in providing audit trails; ridership data and accountability of the specific items of equipment and of the system operations. The degree and extent of this information and the o`oane and rv,d`ndm ofits generation and reporting shall 6euo described in these specifications. H. The electronic boards utilized within tbe6ansbox' including associated electronic components, y6aO be capable of operating ten d6oumeod (18'000) hours between failures provided there is no abuse, vandalism, operation beyond standards or lack of maintenance per the Contractor's instructions. I. On-board equipment shall have e mean time to repair of ten (10) minutes. Repair shall b* defined asthe diagnosis' removal and replacement ofone (l) or more defective assemblies (such as a coin unit, 6i|\ transport, M8R, (}CU' cashbox, electronic board, etc.) to put the equipment back into operating condition. Repair of the defective assembly will not be included in mean time to repair. J. The brpbuxshall have the ability to create and store summary records as well as transactional records, K The activation and deactivation of bus operator log-nn/}og-offwith the OCD o6aD besettahle anti modified only via downloaded fare table parameters from the Fare Collection Management and Reporting System (f[MICS). Paae20of79 16A 8 L A switch shall be located within the farebox to disconnect bfrom the vehicle power. Location of this switch shall 6e identified on the faze6uxdesign drawings and shall 6e subject to review and approval of County. M. Contractor shall provide stickers and other graphics for the 6u/e6uxeyUoidentify the various slots and displays, which shall identify the correct insertion of payment and fare media. These shall be provided 6v the Contractor for Coonty review atPDR and approved utCDR. 4.2 Coin Acceptance A. Operation 1. I'he farebox coin unit shall accept, validate and count the value of pennies (I 1�), nickels (5c), dimes (10c), quarters (25c), half-dollars (5Oc), arid (Susan B. Anthony/ dollar coins ($J.00) and accept and validate a token as desired by County. Validation of the coins ybaD be by weight, density, ouagmabc properties, size and/or other means which will guarantee that only valid US coins are accepted and validated. 2 The coin slot shall permit ease of coin entry and shall be designed to last the life of the equipment. l Acceptance and registration of coins shall beota coin insertin,rate r6 not less than ten (1O) cob` per second. The cnbz unit and associated logic may be utilized to identdv other ybeo of cobs vvi8znnt necessity of replacement or remanufacture of the coin unit or other hardware change. 4. Subsequent Loinsertion and registration, coins shall. 6e directed Uoa cashbox located within the base of the farebox, Within the cashbox the coins shall be maintained separate from the bills. 5. The counting logic of the fazebox mbaO increment the appruprimtenoo-rcsehable counter for each denomination of coin and each type registered and accepted. 6. Any remaining value displayed on the OCU and the Customer Information Display shall clear after the display clear time has elapsed. County shuD have the ability to et the display clear time in one (1) second increments from zero (0) to sixty (60) seconds via the F[MRS. � The coin unit shall meet the following criteria: • Ninety-nine Pe/cent (99.0%) of ,obd coins ybuU be accepted and validated upon initial insertion. • Ninety-nine and eigbt-tenths lercent (99810)of valid coins shall be accepted and validated upon one (I)reinsertion. • All known counterfeit coins, common slugs, foreign coins, and coil-is of denominations not valid shall be rejected upon every insertion. • Validation accuracy of accepted coins shall be at least ninety-nine and ninety-five hundredths percent (0@.95%) 8. Each coin unit shall be permanent1v inscribed with u clearly visible unique serial number. B. Coin Return L A coin return cup or tray shall be provided uo the fazcbox located within easy reach ofacustomer and conforming to all ADA requirements. 2. Any coin which the customer inserts into the farebox and the coin validator cannot automatically validate shall be returned to the customer via the coin zetono cup, This shall include deformed cobs and coins otherwise not meeting the specified valid coin criteria. 3. The fa,ebox shall note iu its memory and retain for data transmission the instances of coin returns. This information shall 6e forwarded to the R[MRS to assist in failure diagnosis. C. Deformed Coins Page 21 of 79 l. The coin unit ybaD have the capability of handling, without jamming, coins which are deformed. That is, coins which, within certain limits, are bent or bulged, not perfectly round m have attached foreign material. 2. The coin unit shall process and accurately validate coins with the following deformations: a) Coins bent mbulged having overall thickness ranging upmU,02Oinch greater than the coins' standard thickness. b) Coins having attached, relatively complete and uniform lavers of foreign material (such as epoxy, solder or hardened gum) ranging optoO.040 inch in thickness. c) Coins not perfectly round (examples: squashed or flat edges) having diameters up to plus or minus 0.020 inch different from standard diameter at the point of deformity. [l Coin 8v-Pass l� Acoin mechanism shall be provided for the passage of coins ho the cashbox the min unit (in the event of, for example, a coin jam in tile coin unit oza failure of the electronic logic). When afaoeboxia placed in by-pass mode, tile FCMRS shall record this event. 2. The activation of the coin by-pass mechanism shall be by a deliberate action on tile part of tile bus operator. Coins processed in this manner shall not 6ecounted no, registered by 8ze6mebvx but shall. be passed directly into the cashbox. 3. In the operation of any device to achieve acoin the security of the farebox and the retention of the revenues shall not lediminished. When the mechanism is used, it shall not 6e possible for the bus operator to reset it from outside of the furebox. 4. Z6efarpboz s6uU note in its memory and retain for data transmission, the exact time when the by- pass is activated and deactivated. 4^ record x6aU also be created when Ge6v-paso is activated and again when the by-pass isdeactivated. 1 The resetting of the mechanism shall require access to tile farebox interior by authorized personnel. 6� When the coin by-pass is activated, bills, magnetically encoded and smart cards shall continue to be accepted, registered and processed. 4.3 Bill Acceptance A, The farebox shall be capable �accepting, validating and counting US. $1'�55, $10 and $20 bills oriented in any of four (4) directions. The paper currency acceptance slot shall be positioned in the general proximity of the coin insertion area, and shall accept bills which have been opened to their full area and inserted lengthwise. The dboeoanoy of the Currency slot shall hinder the accidental entry of cuba into it, The currency slot shall be illuminated to permit ease of bill entry in diminished lighting conditions using LED bghdo8 designed to last the life of the 6azebox. The unit employed to transport the inserted bills shall be positive and not require precise insertion by the customer. A guide bezel shall be provided to assist in the entry of the bill into the currency a|oL The bill shall be inserted approximately one (l) inch before the transport shall become operational and advance the bill to t6* validation area. D� Me bill transport shall employ a roller mechanism to positively engage ao unfolded and folded bill, regardless of condition without jamming. IL shall require oo force bo cause the transport tostart. C, The bill shall be advanced to the cashbox (in Hle lower portion of the faebox) after validation. Any remaining value displayed on the OClJand customer display shall clear after the display clear dzuehay elapsed. D� Bills shall be processed at ooaxivauoo rate of one (1) bill per second. This time sbuU be measured from the time that the bill is sensed in the bill insertion slot to the time that the value of the bill ia displayed tn the customer and the bus operator. Page 22uf79 16A 81 E. 'The bill transport shall have the ' of handling, without jamming, paper media which is That is, paper media which is subject to the conditions of daily "street" use, including vvzbuk&ed, torn, folded, or damp media. F. The bill transport shall process and accurately validate bills with the following conditions: l. Bills which are not uniformly flat min "new" condition. 2 Bills which are torn toa depth of two (2) inches from the edge of the bill. 1 Bills which are damp but not saturated. 4, Bills 6uvbag tape or other foreign material adhering which can 6t 800uo6 the opening in the currency slot. G� Each bill transport shall be permanently inscribed with a unique serial number, clearly visible when the maintenance apertures of the 6mnebox are opened. H Bill processing and. acceptance shall meet the following criteria: I. 97%of valid bills shall be validated and accepted upon initial insertion. 2. A8.5%of valid bills shall be validated and accepted within two (Z)insertions. 3. All known counterfeit bills, color photocopies of valid bills, dnp|icmbao made by other bzorvo means, foreign bills, and bills of denominations not valid shall be rejected upon every insertion. 4. Validation accuracy oi accepted bills shall bewt least 99.95% l. The acceptance sensitivity of each denomination of bill accepted shall be adjustable. T Bills and other paper items placed in the bill insertion slot that are not accepted shall be returned to the customer ut the bill insertion slot. 4.4 Operator Control Unit A. Tbefarebox shall be equipped with anOperator Control Unit (CCU). Integral to each [CD skoO be 8��e� ��OCD��6e ��d���ga keyPadnn6�b�byorLoucbx�reenhxo��ca�e x� `�;"".= 6oebox and its electronics for route and run setup. B. The OCO shall not be bnte87o1 to the ka/ebnx but s6uO be housed in a separate compact console constructed of revenue service tested materials'. Mounting 6a/6vvace abaD be provided to permit mounting on the vehicle dashboard or other appropriate location, facing the bus operator. The OCU shall be positioned not less than twenty-five (25) inchesfrom the bus floor. The OCU shall be mounted on an adjustable and lockable ball joint that allows the bus operator to provide for ease of button operation and viewing ,d the display, The installed OCU shall not interfere with any bus controls, block any bus indicators w, other bus operator displays, or create a safety b aza oJ . All mounting arrangements shall be approved 6v County, The [x]J shall be connected to and communicate with the fare6nx via protected cabling. C. The L}CD shall 6e provided with a two (2) line electrn|uozbaeecent display, a light emitting diode display ozabacklit liquid cz�oudd�p�y�1�D|orao approved e9u��a�otsuch aam6uU context toncbscrccm°�h ' not less than twenty (20) alphanumeric characters � per and which abaU be fully dot addressable, capable ofdisplaying graphics and capable of displaying a minimum of two (2) lines c6 text. Th. eO[J shall he able to e* the full ASCII character set. For backlit [[D displays, the CCU contrast shall be adk�stbleand backIig6�n�sbaDbecuoa6�of being turned onoz off via 8a�OCl7 keypad. The disp&y shall ' \�ofon���ot- brightness leinoDformso/mobieot6o66ng within the bus and shall be sufficiently protected bya panel ofclear plastic which shall also reduce glare. D, Do6ec normal operations when the farebox is static, the bus operator information display shall be extinguished to preserve its operating life. Itshall be active when bis required to display operational information, when the. bus operator inputs data' and when a given push-button is depressed. Alternatively' C��m�e�t�h���6��y��w�����me���ef��xiss��the ����o��� dme�������d w�it����c������� . Page 23o[79 16A 81 E. The bus operator information display shall indicate to the bus operator the status of any ongoing transaction and other information pertinent to the operation of the farebox, including: L The amount of money inserted into the farebox in the form of coins and bills and the fare due. 2. The current function of the soft (programmable) function keys. 3. The function of a given button on the keypad when that button is depressed. 4. Confirmation for any bus operator input information. 5. Bus operator sign -on and sign-off prompts. 6. Upon completion of the farebox "boot sequence" the farebox shall be required to be set with 'Fareset' for the run. F. As coins and bills are validated, this display shall count upward, reflecting the amount of money inserted- If a preset fare is used, when the full fare is reached, or when the bus operator presses a button indicating acceptance of a reduced. fare (student, senior, etc.), a tone shall sound, and the display shall. automatically subtract the proper fare from the amount on the information display and display the remainder. G. If a transaction is not completed, the bus operator information display shall be automatically reset after the last coin/bill has been validated based on the duration of the user settable tinier. This timer shall permit County to set the display clear time from zero (0) to sixty (60) seconds in one (1) second increments. Any remaining value displayed shall be added to the "unclassified revenue" data register. It shall be possible for the bus operator to delay resetting by pushing a designated "hold" button which shall reset the timer to zero. H. The OCU it other than a full context touch screen shall have a minimum of twenty (.20) pushbuttons, including digits 0 through 9, ENTER, CANCEL, and user - definable function keys. All bus operator pushbuttons shall be fully programmable, shall provide tactile and audio feedback and shall be sealed against the intrusion of liquids and other foreign material.. I. The OCU touchscree.n keypad shall enable the bus operator to classify reduced or special fares and I perform all other on-board tasks connected with the operation of the farebox in revenue service, J. Each of the classification buttons on the keypad shall be capable of being programmed to: 1. Register a specific value ($0.01 to 599-99) with the option to also record the fare in the designated category with the option to reset the register display to "O.OW' 2. Increment a zero-value tally counter. 3. Be disabled (nonfunctional). K. The fare values assigned to each classification. button shall be individually programmable for each fareset. The values assigned to these buttons will be changeable in a matrix format; that is, each preset activated by the bus operator may have a different value assigned, depending on the fareset and requirements of County. 'This matrix shall be stored in the non-volatile memory of the farebox, and shall be changeable only via the meal-is outlined in these specifications. L. Each time a button is activated, the bus operator's information display shall indicate the key number pressed and show the value assigned. Cash fare registration pushbuttons shall be able to be activated prior to, during, or after the validation of money in the farebox to obtain the proper farebox setting. Pushbutton keys used as tally counters shall require no money to be inserted to obtain a count. Each time a pushbutton is pressed in the proper manner, a tone shall sound, indicating that a count has been made in the corresponding farebox data register. Individual pushbuttons shall also be able to be deactivated and these shall have no effect on the registration of fares or tally count by the farebox. M. The farebox logic shall provide for the storage of entered log-on information including route number, run number, trip number, fareset, and bus operator number into the farebox memory. This shall be accomplished using the trail of the identity of the bus operator and other log-on information for later transmission to the FCMRS upon ditta trarisler using wireles,,_, coniunicatiun Page 24 of 79 16A 8'i N. A farebox that has gone into the "Idle" mode shall remain in that mode until the Avail System (Or the bus operator in backup mode) has logged-on to the farebox. O. Log-off from the farebox shall occur in four (3) ways. 1. Bus operator sign-off via the OCU 2. Automatic time-out log-off (based on a preset time period of farebox inactivity,). 0 3. Automatic log-off following data transfer After log-off of the farebox by any method, a message shall be immediately forwarded to the OCU and the OCU and other displays shall be placed in the idle mode. This shall include those occasions when a bus operator prematurely signs-off the farebox. P. All push-button-, shall be of sealed construction to prevent entry of foreign material which might degrade performance. Design of the buttons shall provide a tactile indication to the bus operator that electric contact has been made. Q. It shall not be possible to program the farebox with information that would normally be transferred from the FCMRS by using the OCU. R. A bus operator actuated function, shall be used for the purpose of displaying the contents of various displaying information registers on the CCU. These registers shall be user definable via the FCMRS and their display shall be password protected. 4.5 Customer Information Display A. The customer information display unit shall be provided in the form of a 2-line (minimum) 20-character alphanumeric back lit LED or CAT-approved equivalent. The back lighting shall provide for adjustable intensity to provide clear visibility in bright lighted conditions and during night operations. B. The display shall be positioned on the farebox facing the boarding customers approaching the farebox. C. Under normal operations when the farebox is static, the customer information display shall be extinguished to preserve its operating life. It shall be active when: a coin, bill, magnetically encoded pass or a token is processed by the farebox and when the bus Operator classifies a fare. In addition County shall have the ability to program a message on the display (e.g., "Welcome Aboard") rather than have the display inactive. D. The display shall be able to show the full. ASCII character set. E. The customer information display sha.11. indicate specific messages programmable by County through the FCMRS relative to use including: 1. Validity (for passes) 2. Amount deducted and remaining value to be deposited by the customer 3. Remaining value for stored value based farecards 4. Cash inserted in the farebox 5. Amount due 6. Farecard step-by-step loading instructions (i.e., for adding stored value to an existing farecard) F. The customer information display shall provide displayed messages programmable by County through the FCMRS to the customer for selected fare media processing difficulties including: 1. Card misread (applies to farecards used in the TPU or the MISR) 2. Insufficient value remaining 3. Invalid card (including bad card list match) 4. Fare media expired Page 25 of 79 i.4 AL G. When. a cash transaction is initiated, the display shall show the amount deposited and the amount of the fare. When a magnetically- encoded card is read using the TPU or M'-;R, the display shall show= relevant information such as: 1. Expired or Invalid 2, Please Try Again 3. Value remaining 4. amount due (if no remaining value on farecard) H. Information on the operation of the customer information display and all such conditions sensed, reported and displayed shall be provided at the PDR. 4.6 Audible Signals and Spoken Messages A. The audio transducer shall be provided with a sound level of not less than 65 db at a nominal 12 volts DC. The audio transducer shall sound the specified tone under the conditions stated below. A minimum of three (3) clearly distinguishable tones shall be provided. Tones shall be programmable by County through the FCMRS. Designation of initial tones for testing are provided below in parentheses. 1. The audio transducer shall sound each time a valid fare is inserted and registered (Tone 1). I The audio transducer shall sound a multiple signal when an invalid or expired fare medium is used (Tone 2). 3. The audio transducer shall. sound a multiple signal when a permit or reduced fare medium is used (Tone 3). 4. The audio transducer shall. sound a multiple signal as acknowledgment that the bus operator has completed the sign -on procedure and that the data has been received by the farebox (Tone 1). 5. 'The audio transducer shall sound a multiple signal as acknowledgment the data has been extracted properly (Tone 1). 6. The audio transducer shall sound a multiple signal when a button unassigned to the active pre -set is pressed (Tone 2) B. The farebox shall also be capable of generating spoken messages using digitized human voice. It shall be possible to enable and to disable the spoken messages via the FCMRS. Spoken messages shall be triggered by County defined farebox operating conditions and include messages such as, "'Transfer Not Valid ", "Please Swipe Card Again ", and "Please Insert Card Again." County shall. be able to choose from a list of standard and custom spoken messages and assign them to the relevant functions by use of sound files located in a FCMRS data file. 4.7 Fare Structures A. The fare collection system shall provide, for no less than ten (10) individual fare tables that describe separate fare structures. B. It shall be possible for County to change the fare values in any fare table by means of data entered by the FCMRS and the PDU, without the necessity of removing or replacing any of the farebox electronic components. C. Each fare table shall include all information required to provide for proper processing of the customers based on County s fare structure and associated usage rules including: the base fare, the value of any tokens, the valid customer categories plus their associated fares, day passes accepted, day passes issued (plus appropriate charges), other passes accepted, and "cash drops" for other pass types. D. Means shall be provided for the bus operator to switch between the fare tables at the start of a route and during a run on certain routes, such as express services. The means shall not require any special Page 26 of 79 16A � �� � �� mmponents.The farebox shall only accept u valid fare table based upon the information downloaded to the 6urebos from the FCMRS. G. Upon cozopbsbno of changing the fozo table a "Change Fare Table" record shall be Created defining the new pre-set and a summary record shall bestored. 4.8 Fare System Presets The farebox shall be capable ofoperating in two (2) distinct modes: 1. Preset fare mode 2. Manual mode (no preset fare) A. In preset mode, the farebox shall count up and display the value of the inserted amount. When the amount of the preset is reached, the farebox will automatically count the preset faze as one (I) adult customer and decrease the register readout 6v the amount n { the 6a re� The Bus opezxtormoyalsopzeooa button to indicate that a fare classification other than the preset (are applies and the farebox will be temporarily set to accept the alternate. fare classification. When the proper fare is paid' the fare will be counted and the register readout decreased by the aozoontoft�e 6oec��aifi�ut�o� /�oy overpaid ' balance shall. remain displayed for a programmable time-out period an d then m tocuto zero unless overridden by the Bus operator. B � In manual mode, the farehox shall count upand display the value of the inserted amounts. When the 6h category of a�ni�conotmhal be husnpc��z�m�es �ca ��ryo �' shall that fare category. The overpaid balance shall remain displayed for programmable time-out per iod and then return ba zero unless overridden by the Bus operator. C. In either case, the overpaid amount shall be m6he to be used mvvazd an additional fare unless the bus operator resets the omgiabs reading to$0,K d��H� �� The &,ze6nxs6aD have the ab��pbm have andn�uoouof ten (l0) preset uuzoon�'pco07nmoac electronic logic. A preset amount shall 6e between $Q.O5 and 9l9.95iovalue. 4.9 Memory and Data Storage Requirements A �e���s��h���������«��m�lU'����o���� � records (including time segment records) and 2,OOO event/ alarm records. This memory shall bebacked up with a redundant data module B . 'Theborebox shall be able to hold and support the volatile portion of the memory after being removed from power for not less than fourteen (1.4) days after removed from a primary power source. Lead-acid batteries, which nwv leak, shall not b* used for this purpose. C. Under no circumstances shall the failure ofn battery corrupt the data oz affect the ability of the fure6mx to collect the proper fare, perform validation of coins and bill and other fare media or compromise any security feature nf the fare collection system, A message shall beprovided using dze[CD »unotdvthe bus operator of a low battery condition that will allow adequate time (at least twenty-four (24) hours of operation) tu replace the battery. A report shall also he made via FCMOl8of low-battery condition. D . Electronic logic incorporated in the farebox shall receive value signals from the coin unit, bill transport, ticket processing unit and the swipe reader. 'The electronic logic shall accumulate andstore the amounts in. an electronic register and such amounts shall be displayed on the OCD.The accumulated ndbi�� 6a8 accumulate total voloe��eb��b� dhe6are6ox 6/as�6uDod�uncere�eouerez��z s aucuznu ' ob�e the 6ame6oz was l�t~ probed and the total value received by the 6oe6os since installation or clearing ofthe fare6nx memory. Totals shall be stored for all cash revenues and. boD y counts na tabm6 for number of magnetic swipe cards read. Separate counts shall also bestored for each type of fare media accepted. E A separate count shall be accumulated for all cash that is displayed on the OCU and not accounted for via push button activation. All such revenue shall bc included on. auunclassified revenue register. A Page 27of79 transaction record shall also bestored recording the amount dumped and the associated fareset number. Each fareset shall be set to activate m deactivate this pushbutton. F. Transaction Records The following data shall be generated by and stored inthe farebox and hoavailable for the u--_--- of reports and queries when transferred tothe F[MR'S': I . The fare collection system shall generate abaneoc6on record for each customer processed which shall b* transferred uothe F[Iv{8S. Each transaction record shall be unique within the system. This transaction record shall include the following information: a) date and time of transaction b) magnetic card serial number c) bus number d) fareboxoom6er e) te ronumber rounumber run number g) direction code b) faresetoumber i) trip mnnzbez D customer type (adult, student, senior, etc.) k) fare type - bus fare, transfer charge, short fare and overpayment l) amount paid m) method of payment o) cash denominations and quantities o) expiration date transaction number [� �»��o ou q) service type; local, express and special run 2 The fare collection y��o sbu�eners�a transaction record for eachvau��g and wireless data � communications incident. 3, The fare collection system shall generate a transaction record for each bus operator log-on and log- off 6yanyv/8, four (4) methods described inthis specification. 4� The fare collection system shall generate a transaction record. for each event sensed by the farebox. 5 The fare collection system ubuO generate a transaction record for each alarm �i�abx�, This � information shall be stored in a separate security file, access to which shall be protected by security password. 6. The fuze collection system abul generate the tzaoaucdun records necessary to provide the maintenance information. 7. The fare collection system shall generate a transaction record whenever any of the following events takes place: a) The bus operator log-on operation b+altered. 6) When a route/ run record iamecoxded. c) Midnight and other date/ time changes Page 28 of79 16A 8 d) The farebox is placed in bypass e) The farebox is removed from bypass f) The cashbox is removed (cashbox number shall be saved) g) The cashbox is inserted (cashbox number shall be saved) h) The cashbox access door is closed after a time -out period of five (5) minutes (this period to be. FCVIRS settable as an operations parameter) i) The cashbox access door is opened at other than the time of normal�rY' = < -" j) The cashbox access door is closed at other than the time of normal k) The farebox data transfer starts 1) The farebox data transfer ends m) The farebox internal clock fails n) The record storage is about to overflow o) Changing from one (1) pre -set to another P) All payment transactions, including the value of coins and the value of bills q) All. ridership registration transactions r) Farebox power off s) Farebox power on t) Bus operator tog -on u) Bus operator log off v) Unsuccessful data transfer w) Successful download of farebox configuration data x) Unsuccessful download of farebox configuration data y) Farebox errors and failures Z) Security errors and intrusions aa) Coin jams bb) Clearance of coin jams cc) Bill jams dd) Clearance of bill jams ee) New fare table selected ff) Farebox percentage full ( settable threshold of 50- 100°0) for coin gg) Farebox percentage full (settable threshold of 50- 100 %) for currency G. `Time Synchronization 1. The farebox shall contain a real time clock which shall store the time that will be used for printing; recording; validating; time and date stamping of transactional data, and fare media; for display of transaction records on the OCU; and as part of bus operator and customer information. This clock shall record and display hours, minutes, seconds and date in appropriate formats. This clock shall be capable of being reset to the correct time automatically upon log -on and each time data is transmitted from the farebox and shall. be accurate to within one (1) minute per year. Page 29 of 79 �o�o the County 2 The Fare Collection System ~'�` ^'",= its ~``^^ time synchronization —computers LAN to Intbiymu6esyucbzo�zabonuf�ecmopo�r '~~^ ond svod� onizabuubo ^~~` ^~ -- ' -- -- �ou (24)bours , to the L/\��oba�6e pe,6nrro*d at\e�tonceevery twenty r 'u^= ,�^"~ ~^^^^~.--' — the 6azetmx will occur when the fa/ebnnis probed by the FCMDS, ���a Time Segment l ' All ^~rehoxes shall be provided means to permit the bus Operator to make o "summary oary couo, record" within the far*b»x meo»g/� This 6auc�oo shall provide means to aggregate data for a segment of a route ho' for example, gather number of boarding customers at m user specified J shall 6e fifteen (15) minute summaries. intervaL3�ede6mz}tperiodfo�Hoet�uerecur o Z. The memory capacity o fthe *e�nmu b r shall b* suitable to compile a minimum of2,000 records (as m part of the total number of records) per 6mze6onvmnlbu& 3 The information stored in 8n o*gmen�r shall out be accessed 6�uneh �e bus operator's � b shall he stored and to t6e����DS Once stored in de fazcbus, information display, but � data shall not 6e available tn the bus operator for editing bz any fashion. 4 �o create a ''zecord" the bus operator shall press specific boUonu in a prescribed sequence. The � ' information display shall confirm this by showing the words Wake Summary Record". The bus operator shall dbenbe required to confirm orcancel, D. in addition, County may elect to have u summary record initiated automatically at set intervals doo ����duc��Ge��bnx. These ��rvo�may be every h�m�nh�,e�ry6�eo "= �"�� more required Tb�fe�ores6aD6ee�hobe oobzotes or every twenty ou or �mr ' � activated hy downloading from H`eFCMDS. 6 /�eonoo�aryreco,ds6allbecreabed"'�baopecialcodeiodicu�ngd6etypenfevent(huth/nkp(ace' � e.Q. bus operator initiated, automatic 6oye6nutioe'fareboxybuedinbypaao,etc,und6dsu6aDbe reported bz the data system when the appropriate reports are accessed. The special code may be a predetermined number not otherwise used by County. K, Farebox Diagnostic and Operational Reporting l . The farebox and its electronic logic shall be designed. to provide the specified degree of operational self testing, diagnostic operations, reporting an d indication, 'These element` are required for effective maintenance of the equipoueut to provide audit trails to determine proper 6anabox �a be �h�b�a �����* 2 ���o��L��s ' �nede of �d��� �m� �a yzo�u� wm � — technician the proper operation uf all of the major nu dules� An LED indicator shall he used k/ indicate proper voltages from the main power supply. 3 ��uhuruo�cE�gne�ceTey�n� Tbefare6oxio�cyba�he designed bo provide anautomatic eequence � d�� hli���au�om���gue��gobuD6ein�a�dby be����eachofd���or«��u �sem ' inthe insertion ofa "test plug" ozDSBabckozot6erapprovedoeaoa'denebypl ac b the farcb oz a "test ooda" —Each assembly shall he cuuse 6tofully operate minim-Lim uf four (4) times during the automatic `~`q~ ence . The sequence shall continue for ao indefinite period until stopped byexternal shall ��meo�n 76e amount d���� �6�b d� ��dn� ������ �oy om _ � � 0C� intervention. f minutes desn a 7his�zoesbaD6�uv��ab|e6ordispk�yon e Uue6arebnxbo�szuoo onou am ouu � _' 4 (�cJo/�iD7u��'�he��ebox|o��e6okprovidempec��conn�of�db/idua]coinun6boksntyp*y ' 6yquzmti�T6-�—��a����d�udd�no� 8 � requirements for accumulating value, e6�c�e . eoevherei these s --i{icabousTheforeboxsbaDalmmprovi6eaonitcouutofdxequaodtyofhille processed by denomination. The 6urebox shall also provide total counts of at] coins processed and all bills processed. These counts shall also be used for preventative maintenance and audit purposes and as a determinant uf validation factors associated with each 6urebon coin unit and bill transport. Page S0of79 16A 8 5. Power Supply Monitoring. The farebox shall monitor and report the number of times the primary power source has gone to zero (0) volts and back to normal. "This serves to indicate an intermittent power line or poor ground connection or faulty switches. The farebox shall also monitor and report the number of times the power supply drops below the minimum voltage, but not to zero (0). This is indicative of a heavy load on the bus electrical system or a possibly defective bus battery cell. These counts shall be reported through the data reporting system. 6. Security Door/ Cashbox Alarms - The farebox shall be provided with a sensing device capable of monitoring real time and the length of time that the cashbox security door is open. If the door is open for longer than three (3) minutes (programmable), an alarm signal shall be transmitted to the data storage within the farebox memory. The real time at which this alarm was sensed along with the length of time the door was open shall also be stored in memory. The next time the farebox is probed, the transmission shall contain a "security door alarm ", indicating the time of the alarm, the length of time the door was open, and how much revenue was in the farebox at the time of the alarm. The farebox shall be provided with a sensing device capable of monitoring the presence of a cashbox in the farebox. If a cashbox is removed at a time that varies by more than three (3) minutes (programmable) from the time that the farebox is probed, a cashbox alarm shall be created and stored in the farebox memory. The real time at which this alarm was sensed along with the length of time the cashbox was not in place shall also be stored in memory. The next time the farebox is probed., the transmission shall contain a. "cashbox alarm ", indicating the time of the alarm, the length of time a cashbox was not in place in the farebox, and bow much revenue was in the farebox at the time of the alarm. T Cashbox Full Indicator - The farebox shall be provided with a visible indicator on the OCU to prompt the bus operator when either the coin compartment or the bill compartment in the cashbox reaches eighty percent (130 %) (programmable) of their respective capacities of coins or bills. The indicator shall remain visible until the cashbox is extracted and the coin compartment and the bill compartment registers are automatically set back to zero. The coin compartment and bill compartment amounts required to activate the visible indicator shall be programmable. & Farebox Reporting - All amounts, quantities, and other information developed as a consequence of compliance with the requirements of these specifications shall be stored in the farebox memory and shall be transmitted to the FCMRS for later report printing of the information for each farebox. 9. Maintenance Information - The farebox shall include resettable transaction counters that maintain the number of payment cycles for the coin unit, bill transport, TPU, MSR and the entire farebox. The individual transaction counters, as well as the farebox transaction counter shall be capable of being reset by the technician whenever the module is removed for maintenance. This counter information shall be stored within the farebox and transferred to the FCMRS upon data 10. Door Open - The farebox shall store an alarm transaction when one (1) of the doors on the farebox is opened including the top cover, cashbox door and maintenance access doors. The cashbox alarm shall be an audible alarm and alarm message only if the door is open for more than the user settable period of time or if the door is opened without proper authorization. The alarm shall not sound and the alarm message shall not be created in any other instance. 4.10 Cashbox Removal, Identification and Locking System A. Cashbox Removal i . The cashbox door shall be fitted with internal devices w =hich shall only release and open the door B. Cashbox Identification System 1. The farebox shall have the ability to automatically read a unique identification number of each inserted cashbox. 'Phis serial number shall be a minimum of four (4) digits. Z. The means and methods employed shall not require electrical contacts, plugs or other physical connections between the farebox and the cashbox. Page 31 of 79 �� -�'���� 8 . � 3 �0beu��u���d�����o �a���d���)nmo�r�a bc�o�d�the meouoz�^ ' — ta�nu�i6erxecmrd ~� --'--- �� ��i t"tbe�����S{}nb'ooe(I)�� fareLmxooeoznry for subsequent data tcuooco on . ~'-'--'-- shall be stored ior each cashbox insertion and for each removal from the farebox and receiver. 4 If 6ud�ry � used in the U�syo�zo shall be designed such that the ba�ezy shall have a � and sbeJlprowideau�dvasue mini�mm'|i�dme in this application of �n� �) consecutive ye�� warning oo tile [)CD and FCMRSsufficient tu allow for battery replacement before battery failure. C. Cashbox Door Locking System l.The farebox shall incorporate within its logic elements, the ability to retain specific code mother secure means to release the cashbox door. 2 The action o� closing the cashbox access door and bok1��g � in the closed position for � dsb � tbe[axe6ox mechanism to engage the door locking approximately one'ba1�N�5)��»n au cause � slammed, with the mechanism sbuU piny and lock the cashbox access door. If the door yazo�e ' ' mnteugage. 4.11 Magnetic Swipe Reader Fazeboxes shall be provided with an z�r�r�c� ����������� bop surface of the fazebox. The reader ~r integrally a lougitodinaialnt in which a zougocdc card is manually traversed past a read head. A. Function encoded. cards that have been encoded '' The - ' magnetically with data such as date of expiration, type of yen/ice' conditions of use, serial number and other information relative to its proper operation io revenue service. Tbe6aze6nx y6aO function to read the information on the car6(a) and determine whether the card ie^vali6" or "invalid" based upon the preprogrammed parameters in the 6ure6nxascompared with the encoded information ontile card. 2 . The MSR shall automatically process a correctly inserted, va lid magnetic card ioone-half (1/2) second orleso Tbeopernbnuaodumn�eoft6cDiSDs6aDnotiopedecoshouzerboardingor8m`�to � �� through �� e��� � |�cua�z�rsb�� � 8e an�ozanoer�K1a�oetkcar6bme,txn,y swipe r ' general flow of customers boarding the bus 3, Cards shall be read on first proper insertion with an accuracy of not less than 99.0%, assuming each card is valid, is fully inserted such that all coded information passes across the read head, and the card is not damaged sufficient to destroy the ability of the MSD10 correctly read the coded data. 4 if a curd is un� valid for 8� current class o� service, the 6urobox shall d�Dbx� the amount to be � inserted by tile customer. oer� Additionally, the fa re b ux y 6aD accept and separately register additional cash fare paymenm��cu,dumcewi&U���otmc��.8eg��o�oonfadd�ona}c�b6o�ohaD cause the o�r6 hn6eaccepted without requiring the bus operator to push a button. This cash data shall beaccumulated ina separate register. 5 The ���a h�da�emb��a be���o�e6ym�mo��n�mCD�a�y���6� � �� ��� c��a a� � p�-� �d �� connectors, or ���� approved ' by County. �\ trained maintenance - technician shall be able to replace the read lead assembly within five (5)minutes. 6. The NISR shall be capable of operating under the same environmental conditions as the fareboxes. 7. The MSRyball not encode any data unthe curd read but shall be a read-only device used for reading information encoded oucards. B. Visoaand&odibleImicator l. The ()CU display o6aD allow the bus operator to monitor magnetic card activity as required, indicating the type of transaction being conducted, any problems n, other messages. Page ]2o[70 16A 8 2. In event of a challenge between the bus operator and customer regarding the use of magnetic card or cash deposit, the bus operator may depress a button to retain the information on the OCU display. 3. For each card accepted by the farebox as a valid fare the farebox shall sound a tone indicating that a proper fare has been paid. A recognizably different tone shall be sounded in event the transaction is refused by the farebox and the OCU and customer display shall indicate "INVALID" and additional information to explain why C. Passback Protection L Passback protection shall be provided as specified elsewhere in these specifications. D. Data Encryption 2. Magnetic stripe data shall be encrypted to provide for data security. The security scheme used shall be presented and explained at the PDR and finalized between the Contractor and County at CDR. 4.12 Magnetic Stripe Farecard Stock A. The magnetic stripe farecards shall be the standard credit ticket size of 2-1/8 inches by 3-3/8 inches. The magnetic stripe shall be 1/4" wide, located 3/8" from and parallel to one long edge. Manufacturing specifications shall define farecards that are fully compatible with the farebox equipment. B. All magnetic media shall utilize high coercivity magnetics of not less than 2,000 oersteds. 4.13 Interface For Connections To On-board Systems The farebox shall be capable of connecting to other devices on the bus over industry standard interfaces including SAE J-1708/J-1587 and SAE J1939. These other devices include CA6,/AVL system to be installed by Avail Technologies. The on-board interface with Avail Technologies shall allow the following: L Single-point operator logon (using operator ID and run ID) and logoff via MDC 2. Accepting run, route, trip and operator information provided by MDC 3. Sending farebox alarms to MDCs 4.14 System Security A. The fare collection system shall incorporate the highest level of security in order to ensure that all revenues inserted into the farebox are securely deposited into the cashbox. In addition, the system shall provide for secure transportation and collection of all deposited funds from the time the cashbox is removed .from the farebox to the time the monies are counted. B. The goal of the fare collection system is to provide for the secure collection and transfer of all deposited revenues and to provide appropriate alarms under those circumstances when there is risk of revenue leakage by means of data manipulation or by unauthorized access to the cashbox, including the potential unauthorized use of keys during the revenue collection procedure. A. The system security shall ernploy software controls, monitoring, security interlocks and other similar subsystems and controls to achieve these goals to the highest degree. Hardware and/or software security provisions shall be provided for the following: 1 Access to Cashbox Interior - Each cashbox shall be provided with a high security lock to inhibit unauthorized access to the contents of the cashbox. 2. Access to the cashbox within the farebox shall require the downloading of data prior to unlocking the cashbox access door. Download shall be via tethered probe or optional wireless means. 3. Access to the contents of the cashbox from the top of the farebox shall be prohibited when the cash processing modules are properly in place. When these modules are removed or not installed Properly, an alarm message shall be created and transmitted via the Avail on-board system to the central dispatch workstation. Page 33 of 79 4. Unique alarms shall be created for the following events asuminimum: a) W6eo the cashbox emptying time exceeds a preset limit frnoz5 seconds to 5 minutes in one (1) second inczemeoty). b) When the top cover of the fareboxis opened, whether bm service or not. d When the cashbox access door is opened and when itisclosed while in service. d) When the time that the cashbox access door is open exceeds o preset limit specified elsewhere herein. 4.15 Equipment Construction A.This section describes the general constructional requirement-, to be included for the on-board fare collection equipment. I, Mechanical Details a) The farebnxmnd its mounting fixtures shall 6econstructed inamanner to discourage vandalism and theft. Finishes shall resist corrosion, abrasion and youtcbing, All exterior surfaces shall be clean with all corners rounded. 'There shall be no exposed bolt heads, nuts, sharp edges or Cracks oo the outside surfaces. h) The upper portion nfthe farebox shall be made of brushed msatin finish stainless steel, not less than 14gauge, ynib,bh/ reinforced for rieidity, and with no external and/or removable fasteners that provide access to 6� interior of the foxebmx. County will review v8zez revenue service-proven materials proposed to determine their suitability and provide the appropriate approvals. d z� top aumenmbb/y6aUbe provided oo the upper por�uuof the fure6oxvvhic6 shall serve ao the bezels �r' the entry of coins and bills, the slot for the MSR and to provide primary maintenance/ inspection access Lo the interior ofthe farebox.This assembly shall have two (2) entry slots for cny6' one (I) for coins and one (1) for bills. The top casting material shall be aluminum or m�bz�y o�e� vv�6 miobnuru vvuD thickness of 1/8 inch and ooitub|e reinforcing ribs for added strength. 6) The coin slot shall be used to direct inserted coins into the 6azebos and shall be sized no larger than a dollar coin. Its design shall be such as to deter the entry of paper and lint into the coin slot and the formation of coin jams. e) The bill slot shall have a protruding lip to assist in the sliding of the 6U1 into the slot. The casting shall be painted with black epoxy enamel or powder-coated, over a suitably cleaned and primed surface. The surface of the casting ybuD be free of chips, blisters and other imperfections which lead W chipping of paint or unattractive appearance. 8 The top casting shall have affixed to it, by oneuos of high yield adhesive, multi-color decals which indicate the function of the respective card' coin and bill slots and provide instructive information. as to their use. These decals shall utilize different colors than the top casting and shall be subject ho the approval ofCounty. gd The Lop assembly shall be secured to the 6oe6oxupper portion by means o f u continuous ooy hinge and high security lock. b) For maintenance purposes, additional maintenance access doors may be provided to permit access to the interior of the farebox. if it is possible to get access to any revenue by opening any maintenance access door or aamooblv' the nperation of other maintenance access door(s) obuD be interdependent upon the authorized opening of the Lop assembly, with interlocks provided to assure that these doors/ panels are not left in the open position when the top assembly is closed and locked. V 'Me lower portion of the farebox shall be made of stainless steel. The material shall be not less than 14 gauge, reinforced for rigidity. A revenue access door shall be provided to Page 34of79 16A 8 protect and conceal the cashbox within the fozebox.This door shall have high strength ��� �����om��o�o�e entry including components to Protect the �=" . electronic lock mounted in auecure location. The 6uoabox shall have a provision Umallow employees and managers to determine that the cashbox is present and open to receive revenue. The design shall he such that there shall 6eno gaps allowing prying the door open with tools, chiseling or other entry. Illegal entry shall be clearly indicated by noticeable damage to the 6zebox and inability of the faoe6onLofunction. j) Keys and/or locks which are "captive" to the lower portion of the 6are6oxand used to interface with the cashbox shall be securely fastened and shall he removable onlv in an authorized manner. Guides shall beemployed within the cashbox cavity ho assure [6atthe cashbox is in alignment for proper operations, The cashbox door shall not clone if the cashbox is improperly aligned. k) Wires and cables which are run through the lower portion of the fa,ebox to the upper portion shall be run bno protected channel and/or raceway. No wires shall bp visible when looking at the cashbox ravity� U A base plate shall be used, and shall be affixed to the lower portion of the farebox to permit mounting to the bus floor. The dimensions and construction of this base plate shall provide the necessary lateral stabilitv, without secondary anchorages. The base plate shall be affixed to the floor by means of "carriage bolts" from the interior mf the bus, with the washer plates and nuts on the underside of the floor. The base plate material shall be cast aluminum o, stainless steel, with reinforced metal deposits surrounding each bolt bn|e for maximum strength. If base plate is not used, the mounting ofthe 6anebox shall be by internal. means utilizing four (4) high yield bolts. The lower part of the farebox shall be suitably designed and reinforced to prevent deformation no wear in service ' oxidation, deterioration or accumulation of tolerance vvbicb might allow the fo,e6ox to be subjected to increased vibration, °venz' metal fatigue o« other degradation. in) 'The upper and lower portions of the6ane6ux shall each be securely fastened together by means of 6iob yield bolts, accessible from the interior of the fambox. The completed aeeenb|v shall Measure not less than thirty-one inches (31')' and not more than forty-one inches (4I") high, am measured from the bus floor, and not more than eleven inches (11") in oono wpcbou' excluding the mounting 6nme plate. (In certain classes of buses, it may he oecessuryho exceed this bei�6tLouUovv6xcaruforta6eoperabonof the 6xmeboxbytz bus opera��� Such buses �e - to he identified 6r the Contractor, and the Contractor shall propose ao alternative meuno for mounting the farehox' which shall be subject h*approval of the CDR. 6y County yhurtocooxpie� uu o n) The coin unit shall be modular in construction so as to be removable within one (1) minute for inspection and/oz replacement. The coin unit and any materials tbenmu shall be fastened 6v mechanical devices. Adhesives requiring scraping and cleaning with onbeota shall not bc used. The 6are6nx shall have a guide chute integral bo its construction hoguide the coins into the cashbox. There shall benn protrusions oo which coins can snag, causing a jaoz� o) The bill transport shall be a self-contained module which may be removed and replaced. It shall be built ofreinforced materials for rigidity, provided with captive fasteners and be ee8-utigning upon insertion. It shaft be capable of being locked within the facebos, The farehmx shall have u guide plate integral to its construction to guide the LbOo into the cashbox. There shall be no protrusions on which bills may snag, causing a jam. p) All major subassembly modules shall have a unique serial number inscribed or permanently applied. No two �)sedalnuoubers shall 6e the san�eon any two (2)ouo6u�s of any type. - County shall be provided with a list nf all serial numbers and the modules to which they have been applied prior to installation of any item of equipment. Subassembly Page 35 of 79 FF-& modules to which such numbers shall he shall include, b�n�bebm�d\�m� applied �°�rcaae 7PU and �1BR. onit6Olbmzmpurte&cbmoic�ck.cssbbox'uppczcaae ' q) Approvals obaU be explicitly requested ofCounty by the Contractor for use of any alternate composition materials in place ofmaterials specdiedbereim Any such approvals sxuu include revenue service experience in similar conditions. Failure by the Contractor to request the necessary approvals ybaU deem those not identified by the Contractor as materials unacceptable for this project. r) A baffle system in the coin chute shall beemployed to prohibit access to or "fishing" of c*bofrn` othe cashbox upon removal nf the coin unit from the 6areboncabbiet. s) A baffle uyu�o or other mechanism shall be employed to prohibit access to or "fishing" of biDsfrom the cashbox upon removal of the bill transport from the fareboxcabinet. Z Electrical Details a) The �rm�a�oof���sbx,��pn�o�sofmo���gb�apmv��o�e electrical shall be6v means nfa polarized, snap connect plug the underside of the 6oe6ox . 6) The e&uizooicy shall be of the solid state type, aaaccnNed on reinforced printed circuit boards 'These boards shall modular (plug connected) and removable for inspection � ty mounted on board s6aO6eoobd�e6in place, or and/nz�a���oce�Thecn�P»neo �omn�v sockets with ���us��be��d for Umseheoe�heread8v removed, high g�U�mc � retainers . c) All major electrical/ electronic subassemblies and devices shall be interconnected by means of polarized positive plug connectors with self-locking retaining features to assure proper connections and yrec|o6c intermittent performance due to poor contacts. All phg-in component-, shall be retained with a positive force holding them in position to ensure they do not work loose with the vibration that can 6e expected in the buses. d) Wires and multi-conductor cables, where used, shall be color coded and/or marked to permit positive identification. � shall not be possible to improperly insert a plug-in ' component into aconnector. e) Display characters shall be nf high intensity type viewable through range of not less than o sixty degree (600 arc when mounted within the 6xrobox cabinet, and have a rated life of not less than lU,O .houroofoyerationwdbuotse@poeotfailure. 8 Fuses, circuit breakers or other Protective devices abaU be employed to protect the tn 6 overload and ducnu�e Where they electronics, motors and other cnoz�o�y` nnu mver � , sbuU be accessible without disassembly of components. Iocabon shall permit inspection and/or replacement through normal maintenance access doors nrpanels. g) A omakr "disconnect" switch shall be provided, iohccoa\ to the [o,rhox to disconnect the fa,ebox and OCU from the incoming power supply. This switch shall bcidentified and marked. and 6eofthe two (2) position type b) The 6^neboz power supply shall te large enough uo provide adequate power to the various 6uns6ovconxponeo<s and provide additional power for the electronic memory, MSR'TPD aodOCD. i) The complete, loss of power bu the 6oe6ox shall not cause aoybz6oro�adunor data contained in electronic oaezuoay to hebmtoz altered. The electronic ozao�ory 6o i y6uDbecapoblenf onabx�inio—electronicomemory,vithoutbo*pop'er6oraodnio,ozuofome(I)znoo8z i) The hxrebos electronics and logic shall be protected against stray e|ecbo-magnetic interference (EN1l) radiations, vibrations, ultraviolet light, or other environmental conditions which v,ou|6 cause the 6arcbox to become inoperative and/or lose the data contained therein k) "'hexe electronic circuit boards are employed and *here they are to be inserted and/or 6 Uhe provided �6Dfdo�ba6n �m�edLyuea�ofho�6��es,��s a pz � . Page 30of79 16A U All circuit boards shall be with polarized plug conoecto No harness wiring shall be directly connected by means of solder to any board which shall be removed for maintenance orinspecdoo m.) All circuit boards shall be factory pre-tested for aminimum ofaevenq-uwo(72) hours prior Lo their final inspections within a given 6xrebon. o) All electronic displays shall be tested for all segment functions for a minimum of forty eight (48) hours. o) T he arrangements �8 e �d d �� �e�� electronic � pnm� � shaU — b e y oc� as to permit adeguate ventilation to disperse the heat created and to preclude degradation of comyoneob and yerfozmance� p) Access Uo the electronics, pnwersupp|ies,nn6 other electrical components for maintenance, replacement o, repair shall not require the removal of the ca o6boxfrom the bazeboxnzthe removal of the 6oebox from the bus. q) The fazebox circuits shall le designed todraw minimum power from the bus battery. The e 6aze6ox shall incorporate the following power levels: • Normal operation during which time operating power required shall be five (5)amps or less. • Idle mode which shall be activated upon time out of the predetermined interval timer, During "Idle" mode 8heOCJ shall provide u visible indicator, such os abbnkbng character, and the coin and bill entry light shall remain illuminated. The [maboxs6aO 6* ready ho collect revenue. r) The above electrical requirements shall apply to all nn 6oley connected to or contained wi6dotha6rebox,inuludiogLbeTF-O'dSRnod0C'U^ Cashbox Requirements A. Phv�a[�b�x[d�� ' be ����b���be�a��n��dm��e �e 2U�n��n�u�b��awau� '� �8�m�b� --- --- d vv��6 affect Those areas construction with no external bstenecyexpose � .. —'_ cashbox which come in direct contact with the fazchoz shall he abrasion �resistant Neither insertion into and/or removal of the cashbox from the 6uzcboxbn revenue service operations nor vibration nr » revenue service in the 6ure6ox'obaD cause any diytozd*n shock ezpez�ncedvb�athe cashbox isbo of o| � c «p b�o� material, bic6 oay adversely affect its ability ho function properly. County will gospropoaed to determine their suitability revievodherrrvenoosery ic e-prov enmatezials and Jed and provide the appropriate approvals. Tke cashbox shall be constructed ioa configuration to t� itbinthe dimensions of the lower portion of the 6uro6ox. The cashbox shall have two (2) individual separate compartments to receive and retain coins and bills, each io their respective compartments. The cashbox when empty, shall weigh no more than twenty (20) pounds. It shall be provided with o handle or handles ooallow itou6e safely carried hya person with gloved hands. }\ permanent serial number shall he securely affixed to the cashbox where d will bevisible when the cashbox ia in. the 6a/eb*x and the fuce6ox door is closed and locked. 2. I B. coin Mix Definition Whenever there isareference to and/or requirement for "mixed ooin",the following mix of coins in multiples mr fractions shall 6eused: C, Bill NlixDefinitin l . Whenever there is u reference or --�---- 6o "bill validation" the term shall refer to the acceptance and condition of 100 6iUo in multiple or pro-rated quantities which are ho6* fed into the Page 37o[7P 16 A fareboxinuflat, unfolded condition, �d po�o��deaW6����� - performance an d validate the following mix o1bills for each denomination shall be demonstrated at the. First Article Test: AObills shall � Jryandootmeuded(nmttape d) ' and folds shall not exceed 1/I6 ~� ao inch in diameter. Thecbcolated and poo bills shall be drawn from the revenue collected 6ythe. present County farebnxe,asfollows: A. Cashbox Configuration I . Cashboxes shall have the capacity m hold and completely transfer bnareceiver vault $500 in mixed coin and 7O0bills in unfolded "street money" (not "bric'" or mechanically stacked or compressed) bills, co paper equivalent. 2 The oyera�onof the cambbnxsbuK locked ckedcooJ��sn � whenever the cashbox is removed from the farebox. When the cashbox is out of the farebox it shall be able to be opened only with the valid revenue key. 3 The mechanism and operation of the cashbox shall be positive and at no time shall expose the of contents revenue interior o ' transfer cycle. Bill Mix Definition New, uncirculated bills' I No folds 5 1 fold (halves) 2 folds 'thirds) Circulated bills inot torn o-- No folds 1, fold (halves) 2 folds (thirds) 15 2 folds (fourths) 15 Worn bills (small tears and limp): No folds 5 1 fold halves) 5 2 folds thirds) 5 2 folds (fourths) 5 ���e�x���mu� 4 The cashbox ahoU61���e���mno�maaugpmr�mu=`position. � bzoIx�able^until the cashbox is inserted. and ready to accept revenue, and the cao66oxaccess door is closed and locked. Page 38of79 16A 8 5. 'The cashbox shall not have removable lids, covers or other elements which may be detached from the cashbox, The cashbox shall be automatically locked and sealed when removed from the farebox. 6. The locks (and key,) used on the cashbox v6a8 beofthe high security type as specified herein. The operation c6 any keys within the locks shall not require excessive torque, which may damage either the key oc the lock. 7, The mechanism employed to open and/or close the cashbox e6aD be positive and smooth in operation. Internal locking mechanisms sbaDbecomwbucted nf strong and durable materials. The term "internal locking mechanisms" refers to all components, including levers, strokes, gears, pins, locking feet and other elements that are required to release the cashbox from the farebox or to lock it io place io the 6nrebux. Alooubnuoz or plastic components are examples of materials that shall not be accepted. 8, The interior of the cashbox shall afford complete gravity discharge of coins and 60s in the /avenue transfer cycle, while maintaining their separation. No ledge or other areas shall be present where coins may lodge and impede the operation o{ the cashbox. 9. The materials and construction techniques u6aD be such that foDv loaded cashbox, if dropped in the upright position to uhur6 floor and landing on its bottom or bottom corner from u height nf forty-eight inches (48"), shall suffer no operational impediment or security breach. The 6aze6nxand cashbox shall riot he distorted when carrying a full revenue load. 10. Metal parts riot constructed of stainless steel shall be painted, plated or constructed of corrosion resistant material. ll. The farebox/xawbbnx sb*D be designed and fabricated in such a manner as to prevent extensive tolerance buildup and resultant vibration which could be detrimental to the proper operations of the 6a/eboxor cashbox bnservice. lZ The cashbox shall function bn a dependable manner in the operating environment of the boumit system. It shall be capable of opera tionfor two-dicrusand (2,000) days, mean time between failures. B. Cashbox Construction L The cashbox an6farebox shall be fitted with devices to determine and report that the cashbox has been ��d������s���������c�d���f����d - | � cashbox has locked plus ^ place) . ' used shall be tamper resistant, solid state and not subject to malfunction due to bus vibration. [ Cashbox Identification l� The cashbox shall provide the ability to automatically read and transmit a four (4)digit serial identification. number of the inserted cashbox that shall be read by the fareboxomce the cashbox is locked in the farebox. END OF SECTION V. REVENUE COLLECTION VAULT SYSTEM AND AUDIT UNIT 5.1 General and Equipment Configuration A. The revenue collection vault system (RCVS) shall provide for the secure transfer of cashbox revenue into revenue collection vaults. B The cashboxes shall be inserted into thecasli}ox receiver located above the revenue collection vault and the cashboxes shall empty all of their contents into the vault. C� The cashbox receiver and revenue collection vault shall be of heavy duty construction. D. All openings and high wear areas shall be constructed iohedorab]euu6abbetoaccnouozodate/oogb handling. Page 39 of 79 TIFT E. The system shall track the cashboxes that are emptied into the revenue collection vault and shall provide means for the reconciliation of revenues collected. F. The cashbox receiver components shall operate reliably and perform all functions without difficulty and last a minimum of ten (1.0) years in the environmental conditions existing at the CAT facility. This shall include moisture and wash water spray, humidity, airborne dust and bus exhaust, temperature extremes, electromagnetic interference anti grounding factors. 5.2 Cashbox Receiver A. The cashbox receiver shall. employ a door that is opened to receive the cashbox. After the cashbox is inserted into the receiver in the correct orientation and the door is closed and locked, a crank or similar mechanism shall be utilized to open and empty the cashboxes in a secure manner. B. 'The receiver shall be interfaced to the FCMRS and shall read and report the cashbox serial number automatically read from the cashbox. Cashbox serial number shall be forwarded to the FCMRS only if the emptying cycle takes place and is successfully completed. C. The cashbox receiver design shall provide a secure interlocking of shutters sealing off the receiver from the revenue collection vault's bill and coin storage areas such that access is prevented to these areas when: (1) the door is open and, (2) there is no cashbox within the receiver. D. The emptying mechanism shall not be able to be turned partially and returned to the starting position. When the cashbox is inserted, it shall be required to fully complete the emptying cycle before the cashbox can be removed. E. The emptying cycle, shall be completed and the cashbox lid closed and locked before the cashbox receiver door shall be able to be opened. F. The cashbox receiver shall incorporate three (3) indicators to visually identify the current status of the cashbox receiver 1. One (1) indicator that the emptying cycle is taking place 2. One (1) indicating that the cycle is completed. 3. One (1) indicating that the receiver bin is full or not in place and the door shall not open. G. The cashbox receiver shall only operate - door close, perform emptying cycle, door re -open - when a cashbox is placed properly and securely within the receiver. If a cashbox is not properly in place, the door shall not close and the emptying cycle shall not commence. H. The emptying cycle shall be completed in no more than ten (1.0) seconds to completely empty the full cashbox. I. The openings into which the cashboxes are inserted shall be constructed of materials able to sustain. high gear resistance and shall be durable under rough handling. J. 'The cashbox receiver shall be protected by a door to deny access to the receiver opening and shall provide manual locking means for security purposes when the receiver is not being employed for revenue servicing. K. Keys and locks which are retained in the receiver lock cylinder and used to interface with the cashbox shall be securely fastened and shall be accessible and removable only in an authorized manner. L. Guides shall be employed within the receiver cavity to assure that the cashbox is in alignment for proper operation. 5.3 Revenue Collection Vault A. The design of the revenue collection vault shall take into consideration strength and security requirements so as to resist forced and unauthorized entries. Page 40 of 79 16A 89 B. The openings in the receiver into which the revenue collection vaults are inserted shall be constructed of materials able to sustain high wear resistance and shall be durable under rough handling. The lower portion of the receiver shall have steel guides, constructed of durable steel, to properly position the vault below the receiver, C. The cashbox receiver shall be protected by a door to deny access to the receiver opening and shall provide manual locking means for security purposes when the receiver is not being employed for revenue servicing. D. Hinges shall not be exposed and there shall be no pry points available for forced entry, E. The vault shall contain. two (2) storage areas: 1. Coins shall be stored in one (1) area with a capacity of $10,000 in mixed coins. Coins shall be stored in a sealed compartment within the vault cabinet with a high security locked access cover that is designed to facilitate the controlled release of coins directly into the coin counting machine. The coin compartment shall have a smooth sloped bottom to allow the coins to discharge under gravity. 2. Bills shall be stored in a separate area with a capacity of 10,000 bills, Bills shall be stored in a removable bin completely within the vault cabinet and locked in place with a separate high security lock. A method shall be provided for easily removing collected currency from the revenue bin when this function is performed in a secure location. F High security looks and an interlocking mechanism shall be employed to provide access to the receiver for maintenance purposes, 5.4 Audit Unit A. An audit unit shall be provided to permit the emptying of a single cashbox for audit purposes. B. The audit unit shall weigh not more than 200 pounds when empty and shall be mounted on wheels to permit ease of movement. The top portion of the audit unit shall incorporate a cashbox receiver to accept cashboxes for emptying. C. The audit unit shall contain two (2) compartments - one (1) for coins and one (1) for bills. The audit unit shall have capacity of not less than. 1,000 bills and $1,000 in mixed coins. D. The audit unit shall be a stand-alone unit and shall not communicate with the FCMRS, unless so designed to improve the security of the cash handling procedure, 5.5 Locks and Keys A. All locks and keys used on the farebox and the revenue collection equipment shall be of the security type, Medeco or approved. equivalent. Lock combinations and keys for all identical functions shall be keyed alike. Different combinations shall be provided for each function as detailed in the following table, where locks that are keyed alike have the same key type letter, All keys and spare locks Shan be delivered to the CAT General Manager. Lock Location Key Type Retentive Receiver Mobile Vault Cover Door A Yes Receiver Door B No Receiver Service Door s) C Yes Receiver Service Door Rear C Yes Farebox Cashbox Revenue Access D Yes Farebox Top..and Maintenance Access Door(s) E No Mobile Vault Coin Compartment F Yes Mobile Vault Banknote Compartment F Yes Audit Receiver F Yes Page 41 of 79 16A 84 Cashbox receivers shall open the cashboxes via ucashbox key mounted in the back wall of the cashbox receptacle. Cashboxes secured within a farebox shall open via a cashbox key mounted in the back wall o6 the cashbox receptacle in the lower portion nfthe 6oebox. The cashbox shall only he able to be inserted ioa singularly correct position bu the fare6oxand cashbox receiver, and shall easily 6eplaced into the ready position to transfer revenues. The cashbox insertion and removal procedure shall be designed to positively guide the cashbox into and out o/ the 6oebox and cashbox receiver. END OF SECTION VI. FARE COLLECTION MANAGEMENT AND REPORTING SYSTEM 6.1 General System Description A. Genera The Contractor shall host the FCMRS at its facility (please see Sections 2] and 5,I[CI)for hosting requirements). The FCMRS shall communicate with the fareboxes to extract transaction and event data and download operating parameters and related information. The FCM16 shall communicate with. the vault to extract cashbox identification from cashboxes inserted in the receiver. The FCBJRS shall. be complete and fully functional, with aDoeceemary items of hardware and software installed and tested, and shall be furnished with such software licenses as may be required. The FCMRS shall. include data probes linked to the database server identified in section [. The FCMORSshall 6* capable ofgenerating comprehensive management reports for use byCounty, B. Application/ Database Server Hardware Requirements- Proposers shall describe thabzfrastroctorebobe used for hcmdo0 F[MR56o County. Please refer to the Appendix section for general IT requirements. Further specific requirements regarding the FCMRS application are as follows: I, Workstation Connectivity to the Application/ Database Server --The FCMR_S application (including configurable security levels allowing full functional configuration ability and reporting) obaD be accessible from existing computer County CAT' workstations via u secured web-based interface (e.g.' via Hypertext Transfer Protocol Secure [BI7IS]) and/or a client/server type configuration ovez secured network connection (e.g.' web access via virtual private oetwv/k !VPN/) ,v6icb is compliant with County's IT requirements provided in the Appendix section. The vendor will train Couotyto configure and support FC&I&S access on County CAT vvmzkstadons. Further, County shall be able to use Currently installed network printers for printing information from FCMRS. 2. Operation of the computer to generate data system reports shall not prevent of the fareboxes. The hard disk drive shall be capable of storing all of the data from up to 50 6arebox- co with maximum route/run records. As or~6a ,e 6o x records are added, the oldest mccox 6o on the disk drive shall beautoozadrnUydeleted. County shall be «6(e to specify how many days of detailed data and months uf summary data shall besaved. I 'The FCMRS shall be written in a standard, commoniv available computer language not proprietary to this application. All communications shall be accomplished using standard networking protocols and hardware. The F[MRS sbaDutflize a relational database management system (RDK1IS) [e.g.' Microsoft S(DLServer] which shalt provide open database connectivity (3DB{) capability to third party tools/ applications for custom reporting or other purposes. 4. The FCMOlSyen/ez shall he installed with redundant power supply and hard-drive configurations. Further, the FCMDS application shall be hosted in. a high-availability configuration such that secondary instance ofFCMRSis immediately available to County in the event the pzbna,? F[MD5 application fails. All data must be protected in the RCMRSdatabase bu the event ofaoapplication crash. C, System Operation —The data collection. and reporting system ubaD be configured in the following Page 42of79 16A 84 ell', Utill o tie L"Llar -n S or Ire -ut02 Computer Operations - If the data computer had been previously shut off, it shall automatically load the proper software upon power up and prepare itself � process �mot ��6c r attention from the operator. The data system shall Uzeu be left for unbonua6z operation. The password used io get access ho the application menu shall be changeable bv means ofa higher level password. The system shall have the cepa6ilit recording a 6dgb level paoavvocd, all uses of pamovrocda for the previous 60 day period, the date and dzne of password use, �e amount ofbnz 8e �s��� vvaa bm use with the password, and what reports or other functions were accessed. {fbbecomes necessary to change the high level password io the computer for security or operational reasons, it shall. bereadily accomplished via the operator keyboard. l± shall 6e possible to use the data computer to change the fare tables in. all fareboxcs T6 b 6mOiododethe 6uU fare value and the values and }vmchoo of �cobedmt�e�ar���� ��c changes farebox clock if required. �� County's discretion, c�m��y � 8e fare tables �d �re6on du«k y�� he - ' - All downloaded uo each 6oe6ox automatically during routine operator entries shall go into a transaction log capable of being printed on demand. Software shall be available in the data system to allow backup and retrieval of files. Software shall 6e available iothe data system hu allow archiving of transactional data. uoneeded. :-.^�Accea to [ooynuer Reports -- Both summary and detailed ferebox data shall be stored no a password-protected database server to ensure that the original revenue and ridership data cannot be modified, This data shall be capable of being converted to acnm000a-dcbznbed ASCII file format for export un third-party software. Software shall be available in the data aysteco to allow backup and retrieval of0es. The data system shall have moLbtamkiug capability and shall be able to accommodate �iTeit�si Aata rep"r�8�ne�a�nn,aodot6ez�akmyinultuoeou�v� Lockup of one task shall = ~ haveoo effect on concurrent tasks, buU not he slowed due tw operation of concurrent tasks. 4,3jure Table -The data system abaD have the capability of changing the fare tables in the 6areboxen per the procedure pzevionob/deuor��d.Each fare bbleass�nsthe value ufa6zU fare ayp/eOaeany ' reduced fares (ato6eot, elderly, dz.).Each individual fare amount may behetween$0.0Iund$99.99 . Page 43uC7q 16A 8d It shall be ��am�dav�u� 8���o m����m��n� p""""'~ ~ through removing or replacing any of the 6,,ebox electronic components- ln^ 6i600 the following shall 6e transmittable: a) Current time and date (any valid time and date) h) Electronic lock code (any five digit number) c) Start/ stop times for AM and PMpeak periods d0 Keypad attributes (taDv'taDy/cleur display, and value increments from 0OlU»99�99) e) Fare table store option (the data system should transmit the fare structure to each 6are6ox ,,)tj7ransfez acceptance parameters kets/ Tokens/ Passes acceptance parameters and other attributes Configurable Parameters The data system shall have the ability to enable or disable various furictions such as ticket types, or other designated pucuzoaGeoaopzeviwoslydefinedin8zis document. 6.2 Standard Reports The following standard reports, at a minimum, shall be available from the data system. All reports shall ca��[�����ed�����wh�J���p��e��d�����npo� w'na generated and printed by the system. All reports shall be generated through "user friendly' menu- driven software. A. Individual Fare6o /Bus Reports I. For individual fareboxopurts, the printed report shall show the following categories of data at w Current revenue * Io'dntereveoue ° Unclassified revenue ° Total number ofriders at each fare level ° 'rickets/Tokens/ Paosey • Total tokens • TotmIstoocdride/valpcca/de • Total passes ° Total bills w Total coins 6vdenomination * Technical Maintenance Reports ~ Bus Fncehum Maintenance History 2 The first bzdivi6oalfacebox report (the "master list") y6*D bz6��e 8uedate and time of � | daythe 6are6ox was pro b d and ��busoon��mn66/ebnxou��er . Cumulative totals for the activity of that fare6ox shall be printed, corresponding ho the column headings. Page #nf79 16A 84 3. Trip-by-trip route/run data lists shall be printed next, following printing of the master list. Each route/run record shall be printed in the order in which it was created, along with notations of driver or route numbeT(s) and the time the record was created. It shall be possible to transcribe this data from hard disk to other electronic storage medium for archiving or analysis purposes. B. Daily Summary Report 1. The daily summary report shall be printable, on request, at the end of the operating day, Count", shall have the ability to designate the end. of the operating day as any time from 12:00 A.M. to 5,00 given day shall be accounted for, regardless of A.M. so that all buses that have operated on a whether they are probed after midnight. The daily summary report shall contain the same data categories listed above, less any that may be inactive or suppressed. Summary totals from master lists from all fareboxes L.e ,,enue, semcp T-r- that day shall be provided. Route/ run data shall not be provided. 2. The full matrix of fare tables (excluding any inactive or suppressed tables) shall be printed showing the cumulative total ridership in each cell of the matrix. The daily summary report shall also provide a report of total daily ridership. The daily summary report shall print a summary of the data from the exception report, indicating the total number of buses LL a{ � c 4Lv'- security door and cashbox alarms, bypass alarms, maintenance required (including power supply), memory cleared, unknown driver, unknown bus, -unknown rou te, unknown run and other anomalous data from the exception report A list of the buses not 2LI12:z�: by bus number, shall also be printed. C. Periodic Summary Reports The data system shall have the ability to generate summary reports for specific periods, as follows: 1. Monthly Sunimanj Report: This report shall summarize all activity fleetwide for a given month. Monthly summary information can be saved for up to 128 months. Totals shall be given for an active pre-sets and keys, revenue, tokens, bills, fare document types, etc., by day and totaled for the month. It shall be possible to print bar charts giving total revenue by date and total ridership by date. 2. Annual Sunutianj Report: This report shall summarize the information given in the monthly summary report and give totals by week, quarter and year to date. it shall be possible to show each value of revenue, pre-set and key plotted by week in a separate bar chart. 3. Daily Route Suinniary Rep(-wt: This report shall summarize all totals by route for a given day fleetwide. 4. Monthly Route Summary Report: This report shall summarize all totals by route for an entire month. 5. Route /Sung Report: This report shall allow data daily or over a period of time to be sorted first by route, then by run, or by time/date. Ridership shall also be calculated and printed. For each route printed, the number of route run records inc luded in the summary shall be indicated. The data in the route / run reports shall be based on when the route / run record was actually created (actual date and time), regardless of when the bus was D. Exception Report 1. It shall be possible to generate a daily exception report listing operator entry errors (invalid route, run driver or trip numbers) as validated against lists of valid numbers maintained by the data system. 2. Security Reports The data system shall have the ability to generate security reports, which shall indicate all cashbox, door open and memory clear alarms. For each alarm, the time of day and the bus number shall. be indicated. For the security door and cashbox alarms, the report shall also indicate the amount of revenue that was in the cashbox at the time the alarm was generated. 3. Editing Data Page 45 of 79 84/ 16A It shall be ������8�����������dw�s�loo�e��e�mode r---- dr�� and trip numbers) shall be ����of the ��aT�m mz�op�ahne��s(nmu��� � / 4. Transaction Log A transaction tog shaft be maintained in the data systemmmpbn The transaction log shall maintain a record of all uses of passwords to access reports, the reports accessed, the time of log on and log off, etc. Du particular, all edibo o6��� the syy�m�a beo�or�d�8e�����n log. The transaction \ngshaDzouiotaio~ is information for a minimum of 60 days. It is not to be subject to editing by users through any Contractor data system software. Transactional Database and Reporting �o��o�l A ����s�dd���e��«�o��������s����a A. ^- shall time-stamped and database io~,�cboe�c�d6�ehoxbaouacbone and/or even� u��� recorded in 6are6ox memory for uploading to the data sy*bzon during routine At the option of County, the transactional database shall be capable of recording: l. Events only (e.g,faoebox cashbox door open, route/ run record created) 2 Events and non-cash fare transactions 3. Events and both cash and non-cash fare transactions. B. The transactional database shall have the ab�����������r�n��e� ' �m���be ���aD���a��e transaction and report it to the data reporting yys . �nymm� ^` card category of�acd, or account any hoae period, route, etc. This �fozo�abonouoybe ' used for audit and security purposes, especially where high -value cards or credit card acceptance is implemented. C. Each transaction shall be individually recorded in such a*my that it is pnoai6be to determine day, time, route, run, latitude, longitude and stop TD for each fare paid. D . The transactional database shall be in u format that allows interfacing to the0[BC (Open Data Base possible hn k with the database using {}DB[-coonpUant ��000ec��by) standard, thereby noukio� it�ooy vvor third-party query and report generation tools. E. To maintain the security of the database, all database transactions shall be logged. Data shall be stored Loa format that is not alterable by general database tools. The software driver for the ODB[interface shall be configured in read-only mode and shall not allow the user to modify revenue data directly. F. The transactional database shall 6e capable ufstoring the following types oftransactions: I Cash fare; includes fare type (full fare or pushbutton), p|oy time (minutes and seconds), latitude, longitude 1 Period pass; includes serial number, time, latitude, longitude 3. Stored value card; fare deducted, remaining value, serial number, time, latitude, longitude 4. Stored ride card; remaining rides, serial number, time, latitude, longitude 5. Transfer accepted; Route, direction, serial number, time, latitude, longitude 6. Transfer issued; Key used ho issue, time, latitude, longitude 7. Non-magnetic ticket nc token processed; time, latitude, longitude 8. Credit & Debit Cards; latitude, longitude 9. 3rd party D] cards (e.g..a college DDca/J); latitude, longitude G. For period pays transactions, the database obaU be capable of storing the 6oDmvviug bdbzo,adou at Pagre46of7V 16A 8 1. Pass serial number 2. Pass type I 3, Passenger category 4. Employer account number if applicable 11. Other data fields shall be provided to permit recording ng of peak /off -peak usage. END OF SECTION VII SUPPORT SYSTEM EQUIPMENT 7.1 7-2- Revenue Processing Terminal A. A method for revenue tracking shall be furnished to provide County with the ability to track all revenues received and reconcile the registered revenues against the counted revenues on a vault basis. For this system, a terminal shall be provided in the Money Room supervisor's office interfaced to the FCMRS for transfer of the manually entered count data. B. The Money Room supervisor will sign on to the terminal to enter the count information. The date, vault location and vault number shall be entered into the terminal. The counts from the bill and coin counting Page 47 of 79 .4 &44 7-2- Revenue Processing Terminal A. A method for revenue tracking shall be furnished to provide County with the ability to track all revenues received and reconcile the registered revenues against the counted revenues on a vault basis. For this system, a terminal shall be provided in the Money Room supervisor's office interfaced to the FCMRS for transfer of the manually entered count data. B. The Money Room supervisor will sign on to the terminal to enter the count information. The date, vault location and vault number shall be entered into the terminal. The counts from the bill and coin counting Page 47 of 79 equipment shall be entered into the record and the record shall heclosed when all fields have been populated. C ' Entry of the count information shall be via wform data entry interface, with the cursor automatically moving to the next field after a value has been entered into u field. When all fields are completed, the record o6aD beaotnozoticaUv closed and modifications to that record shall not 6e possible bya revenue operator, D � The counts for each denomination of bill and coin. obtained from the counting equipment shall be entered via the terminal. beida for manual counts of coins and 6�s shall be provided and data � separately entered to account for money not processed bn the counting equipment. This information shall be subsequent�used �o��t�dJ���e���o the Mm�Room covn�a�t�� registered counts provided by the fareboxee, on u money reconciliation report. This information shall not be 6bp\ayedto the revenue operator. E , 4n authorized County user shall be able to add the deposit information to this reconciliation record. The user shall enter the bzborozaboo from the bank deposit slip' and the day or days for which the deposit applies. The system shall calculate the difference in the revenue counted by the 6areboxem and the deposited revenues shall be identified in a separate row on a reconciliation report. F� The terminal provided for the Money Room supervisor shall have no local intelligence or data storage capedty . All data shall be stored ut8eFCMlS. G. The FCMRS y6aU maintain records of the users who create, access, and ozodi6/ all revenue reconciliation records. 7.32 Revenue Reporting Requirements A���L���d�b����m����������������6� ' �n terminal to �e �C�[�� o6aU be available to County 6n the production of 8zc revenue processing rozuxa/ n� characterizes reports, Menu driven ,opoz� generation software with the same requirements � ^ --'—dbedfor the fare collection system data reporting shall te provided d to allow the user to design and store ao unlimited number c6 report formats, which are tn8e used. for generation of system reports. B � Every access k`FCMRIS application from County CAT workstations shall be tracked to6e reported for security purposes. This report shall besorted bypCMRS user (e.g,CAT workstation ID ozF[BJDSuser ID) and shall include all manual activities, each remote terminal (node) and all downloading activities. The time and description o{ all access a± computer shall be repor ted . All P]Q activities shall 6esinilac)y reported. �+Cuntoa�orshaOsu6uzbaDlogzneaoagey6orCouo�'6orayprnvsdotCDR.County6am�e � right to request addition, 6eladmm or modification of mov log oceouge in mcdcz to meet svateo requirements. �4, Revenue Accounting System The fare collection system shall �����/�m��mofre������ c�z� ' of Ibisyof�vuz*ob�lopeza»ean�nDovva xevenoes^o�prov��asuconmazyn differences. . A {)o�e the cuo�� for the coins and bills have been entered and stored for each vault the F[B�RS A. yvobenu software shall automatically compare 8 e counts of the bills (by denomination) and coins (by denomination) and store data for the differences. B At the end of u day (and also upon request) a. reconciliation report sbuv,bog the differences by vault shall be generated. This reconciliation report shall be provided only Hhzougb the use of a high level Pussword,TheceportohaDabmpzovideadaibhota|andyonuurytora D vaults and an overall accuracy figure. C. The FCMRS shall maintain xu inventory of the following revenue elements: l. Vaults and probes. 2. Cashboxes. ��48of7O 16A 81 D. The supervisor shall be able to enter the information on the bank deposit slips into the system in order to permit automatic reconciliation of the funds reported by the bank against those entered at the Money Room. This shall be. accomplished through a high level function with a special password and user name. 1. A report shall be produced that provides details on the monies collected, counted and reconciled including all cashboxes emptied into a vault and all vaults counted. . E. Summary totals of the registered revenues, by denomination, shall be included for each segment of the report. The level of detail to be provided for the report shall also be selectable by the user. F. The FCMRS shall provide the ability to report the contents of the receiver vaults at the end of the transit day. This report shall include the number and value of bills and coins in the receiver vault. END OF SECTION VIll. TESTING AND ACCEPTANCE 81 General A. The objective of the "Pest Program is to ensure that all equipment furnished under this Contract shall meet all of the applicable requirements specified in this document, including operation under environmental stress conditions. Testing and acceptance shall be. conducted to satisfy production and delivery schedule requirements. "The tests to be conducted shall be: 1. First Article Test (FAT) - One (1) of each item of equipment to be furnished, including on -board revenue collection and data collection, shall be tested to ensure that all the features and functions identified within these specifications are provided. Successful completion of this test shall be a prerequisite for the production and delivery of the full complement of equipment. 2. Production. Acceptance Test (PAT) -The Contractor shall certify when production is completed in order to obtain County authorization for shipment of equipment. The Contractor shall certify that a functional test has been passed prior to shipping any item of equipment. County will identify, when necessary, required modifications to be made and demonstrated before approving release for shipment. 3. Pre- Installation Checkout (PIC) - Five (5) sets of on -board equipment, selected at random, shall be tested with sufficient transactions to verify proper transaction processing and data reporting. Successful completion of this test shall be a prerequisite for the installation of the equipment on- board the buses. In addition, one (1) item of each type of revenue and data collection equipment shall be tested in the same manner to ensure proper collection and reporting of funds. The Network Acceptance Test is considered to be part of the PIC. 4. Installation Acceptance Test (IAT) - Before any equipment is permitted. to go into revenue service a functional test shall be performed by the Contractor on each item of equipment that is installed. Satisfactory performance shall be approved by County. 5. In- Service Qualification Test (ISQT) -This test shall run for a period of not less than four (4) weeks and shall verify that the system is operating in a reliable and accurate manner. This shall encompass all fare collection equipment installed at the garage plus the PDU, FCMKS units and the money room ternninaI. 6. Reliability, Maintainability and Accuracy Test (RMAT) - This test shall run for a period of not less than :ninety-one (91) days and shall verify that the complete system is operating in a reliable and accurate manner for all installed equipment. Responsibilities for Testing are identified below: Test Description Location Performed by Witnessed by Page 49 of 79 16A 84 rst Article Test (FAT) Contractor's Contractor/CAT CAT reduction Acceptance Test (PAT) Contractor's Contractor --- --- - -- re- installation. Checkout (PIC)* CAT Facility CAT Contractor istallation Acceptance Test (IAT) CAT Facility Contractor - --------- i-Service Qualification Test (.TSQT) CAT Facility CAT Contractor eliabilitv, Maintainability & Accuracy CAT Facility CAT Contractor est (RMAT) Ld * Includes Network Acceptance Test C. The Contractor shall be responsible for preparation of all testing materials and the test script prior to the performance of any tests. These materials will be approved by CAT prior to commencement of the specified test. 8.2 Methodology A. The First Article Equipment shall be subjected to the First Article Test (FAT) at the factory. This test shall be comprised of the following series of tests: L Functional Tests 2, Maintainabilih, Test 3, Interface'. 1'est 4. Cycling Test 5, Dust Test-*.- 6, Environmental Tests + 7. Vibration and Shock Tests 8, Radiated and Conducted Energy Test ❖ 9. Radiated Interference Test «- 10. Temperature / Humidity Test + County may grant exemptions for items identified as 4• above providing that the Proposer can provide details related to all such tests being successfully completed by a certified test t laborat ory and. evidence of a minimum of 1.,000 fareboxes in operation for at least two (2) years with more than two (2) transit systems that have a networked operation with a fare collection computer system in operation. B. At this level of testing the first articles shall be representative of the final production items. The purpose of this test shall be to demonstrate that for all items of equipment to be furnished under this Contract, the functions specified in this document will be met. C. Pre-installation Checkout (PIC) tests shall include tests to verify proper functioning and interfacing of the equipment before installation. The PIC tests shall be conducted prior to the ISQ)T and prior to the fleetwide installation, D. Upon start of fleetwide revenue service, the first seven (7) days shall be considered as the system start- up period prior to beginning the RMAT. The twenty-eight (28) day settling period shall be monitored for equipment performance during the RMAT. The RMAT shall be conducted for a period of 91. days. E. Final System Acceptance shall be a prerequisite for the start of the hardware and software Warranty. 8.3 Test Program Plan A. For all tests to be conducted, a final test plan shall be submitted for approval by County at least thirty (30) days prior to the start of the FAT. Testing shall not commence until the test plan has been approved. Page 50 of 79 16A 84 B. The test plan and applicable procedures which shall govern the conduct of activity, surveillance, direction and methods of observing and recording the pertinent data including handling of failures of equipment and inaccuracies of reports, C. The following elements shall be included in the test plan for each of the tests required in the project: 1. Support, calibration instrumentation, test equipment and tools to be used 2- 'Technical publications to be referenced 3. Spares and consurnables to be available 4. Maintenance facilities needed 5. Personnel requirements to be available for Contractor and County 6. Personnel scheduling 7 test period together with the method The report format and specific data to be collected during the used to report the test results & Preventive maintenance tasks (if any) to be performed during the test 9. Corrective action to be taken when failures and inaccuracies occur 8.4 Test Procedure Outline A, The test procedure shall include, as a minimum, the following requirements: Objective of test 1. Test environmental conditions Detailed description of test specimens including drawings, part numbers, inspection and test records, maintenance records and calibration records 3. Detailed procedure of test 4. 'Test equipment to be used. Include any measuring equipment and/or any equipment aiding in the performance of the tests 5. The level and schedule of preventive maintenance during the test 6. Pass/Fail criteria 7. Retest procedure 8. Test script procedure-, for assessing Pass/Fail/Re-Test, including provisions for maintenance during tests. 9. Test notification 10. Test Reports B, The procedure to be followed for the resolution of test problems, failures, inaccuracies and general test conduct ground rules shall be defined 8.5 First Article Tests A. Functional Tests 1. The purpose of this test shall be to demonstrate that for each type of equipment the functions specified throughout this document, including all limiting conditions, shall be met. Each item of equipment shall lye, required to execute all hardware and software functions as detailed in these specifications, and meet the performance criteria requirements. The procedures for handling maintenance (trouble shooting, and correcting faults) and service functions (extracting data) shall also be demonstrated. Page 51 of 79 16A 2, The Contractor shall be responsible for developing a functional test procedure that satisfactorily demonstrates all equipment functions and shall submit this test procedure to County for approval at least thirty (30) days in advance of the test. 3. Each function specified shall be tested at least ten (1.0) times prior to confirming success or failure. Each piece of equipment shall have passed the functional test before the environmental tests listed below are started. B. Vibration (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. The. Contractor shall. ensure that for the bus fleets, vibration conditions expected in the area of installation are taken into account to ensure that proper isolation/ protection is built in the on -board equipment design.. In addition, the following requirements shall be met. 2. The on -board equipment shall be tested per the procedure of MIL- S`I'D -810D, Method 314.3, Category 8, with the following changes: a. Basic transportation, common carrier environment curves, Figures 314.3 -1, 514.3 -2 and 5 14.3 -3 shall be used with an overall RMS level of 1.5g for the vertical axis and 1 .Og for the transverse and longitudinal axes. b. The cycling time shall be two (2) hours on each axis for a total of six (6) hours. The on- board. equipment shall operate normally during and after this acceleration test and the equipment shall not experience broken or loosened parts from this vibration. c. At the conclusion of each axis frequency sweep cycle, the on -board equipment shall be subjected to a vibration of 3g's at a frequency sweep between 7 and 14 Hz for a period of one (1) minute and 4 g's at a frequency sweep between. 70 and 140 Hz for a period of one (1) minute. The equipment shall operate normally after these acceleration tests and shall not experience broken or loosened parts from this vibration. C. Shock (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. The on -board equipment shall be tested per Procedure I of MIL - STD -810D with the following changes: a. The half sine shock pulse shall have a peak value (A) of 5g and duration (D) of 20 milliseconds. b. The on -board equipment shall operate normally after the shock tests and shall not have experienced broken or loosened components as a consequence of these tests. D. Electromagnetic Effects (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) 1. Susceptibility to Radiated Electromagnetic Energy - The on- board equipment and revenue collection equipment shall be tested for susceptibility to radiated electromagnetic energy per the requirements of MIL - STD -461C. for radiated emissions, electric field. The equipment shall not sustain any permanent damage as a result of the exposure to these electromagnetic fields nor shall it lose its data in RAM storage. Loss of data relative to a farebox transaction during the exposure is considered tolerable though undesirable. 2. Susceptibility to Conducted Electromagnetic Energy - The on -board and revenue collection equipment shall be tested for susceptibility to conducted electromagnetic energy per the procedures of MIL-_" 'D- 461C, Requirement C906, utilizing the 400 volt, 5 microsecond pulse of both positive and negative polarity. The equipment shall not sustain any permanent damage as a result of application of the pulse energy nor shall it lose its data in RANI storage. E. Radiation of Electromagnetic Interference (exemption will be granted with proof of previous testing at a certified Environmental Testing Laboratory) Page 52 of 79 16A 8+i 1. The Contractor shall be responsible for compliance with applicable Federal Communication Commission regulations (i.e., FCC Rules, Part 15, and Subpart J) concerning conducted. and radiated radio frequency energy. F. Temperature/ Humidity 1. The on-board equipment shall be allowed to stabilize for a period of two (2) hours at each of the given environmental condition settings. Thereafter, the number of fare payment cycles to be processed shall be as indicated below. 1 125 J 32 I 20-45% 2 1,25 110 97% [_3 125 85 75% 4 125 65 915% — - - ---------------- - ------------- 5 125 95 ...... . ......... . 20-45% ........ 6 125 95 2. Specific conditions to be met for the on-board equipment shall be: a. Accuracy shall meet the following requirements: 1) Preventive maintenance shall not be permitted during the environmental. tests. Failures - During the conduct of this test, failures shall not exceed two (2) intermittent failures not requiring corrective maintenance. 3) jams requiring release(s) necessitating opening the farebox shall not be permitted. Should any occur, the test shall be repeated.. Revenue collection equipment shall be subject to temperature/ humidity tests 2, 3, 5 and 6 as identified in the above table for twenty (20) cycles each. G. Maintainability Test 1. In conjunction with the Functional Tests, the Contractor shall conduct a Maintainability Test of the equipment. The purpose of this test is to determine that the equipment tested conforms to the following maintainability requirements. This will be accomplished by introducing fault-, into the equipment and then measuring the time required for a technician to diagnose and correct the failure, from arriving at the device through returning the device back to service, and shall include swapping out the affected module. Mean Time To Repair (NIT F' MYFR (90% max) On-board Equipment 0-4 hour 0.9 hour Revenue Collection Vault System I hour 1.3 hours I At least thirty (30) days prior to the FAT, the Contractor shall submit to County a test outline which shall be prepared in accordance vvith the County approved maintainability test plan and shall show the basis of sample size selection and list of faults to be introduced into the equipment. This list shall represent every 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. Counh, shall approve this list and the repair times prior to conducting the maintainability test. 3. The test shall be conducted in the following steps: a. The Contractor shall provide multiple units of the equipment to introduce failed components, incorrect adjustments and incorrect settings. The simulated failures shall be introduced in proportion to their expected failure rate. Page 53 of 79 16A 84 b. 'The Contractor's maintenance personnel shall be unaware nd the simulated failures and shall be assigned to repair the equipment, c, The repair times shall be recorded. and MTTR shall be compared with the advance list provided 6v the Contractor. All results will need to be approved by County. }�b-tterfaceTest I , The following equipinen bz�r�� � shall be evaluated for hardware, software, and data transmission, Tbwae tests shall be performed under ambient conditions and obaU demonstrate all functions specified for the syoteou� The interfaces are: a. Between the TPIJ- and the farebox. b Between the MSR and the fare6ox. c. Between on-board equipment and the revenue transfer and collection equipment. d. Between the revenue transfer and collection equipment and the FCMRS, e. Between the FCMRS and the County network. Design Qualification Waivers l The Contractor shall demonstrate that each component msubsystem of the fare collection system supplied meets or exceeds the specification requirements- Wherever a component or subsystem is substantially similar in design and application to equipment previously used in a similar application, the design may be qualified through submission of revenue service data. 2. Ka component orsubsystem io question iy considered by County to besubstantially identical in design Lo equipment previously deployed io other transit applications, design qualification tests on that equipment may not be necessary. Contractor sbuO provide a fozoaoL request for a Design Qualification Testing waiver for consideration by County for each applicable component or subsvotem which shall include the following data asaminimum: a. List ufthe locations and quantities of current equipment installations, including duration of revenue service. b, Description of all relevant differences among the other installations and the requirements of this specification. c. Description nf all differences between the currently installed equipment and the specified equipment. d. Test results of anty relevant design qualification tests that have been conducted on this equipment. e, Reliability data for previously installed equipment, verifiable through. purchasers. 3 Baedomhesubmteddua'[oumy wldaezmnef&e egurrmens for desgnqoahbcamn � testing shall be waived. Specific requirements for each piece of equipment will be considered individually, and waivers will be issued ooaoindividual basis. Waiver nf design qualification for component or subsystem shall not satisfy integrated testing of components. 4, The Contractor shall supply certification for those tests for which exemption is requested. This shall include actual test data documenting the appropriate tests performed on the on-board and revenue collection equipment to meet the requirements specified and having successfully operated the equipment on ba oa d buses under revenue service conditions for at least six (6) months. The Contractor shall supply toCounty the name, address and phone number nf all testing facilities and the yersou(s) involved io performing -such testing. 5. The certificates shall be approved bv County hu exempt the Contractor from performing theteyts� J, CyclingTest �Dmw The cvcbng�s xbaU6ecouduc�dko�e on-board e9vbpozeotas m,vm' Pa�54of?9 16A 80 1. Cash Payments - a minimum of 500 coin only transactions and 500 bill only transactions for the payment of the base fare shall be performed. A minimum of 200 coin/bill transactions for payment of inimum of 1, of all transactions shall provide for the the full fare base fare shall be performed . minimum. A n loading of a stored value card with credited amount for overpayment and a transfer. I Pass Usages - a minimum of 500 pass transactions for each activated. pass type shall be performed. 1 3. Count Transactions - a minimum of 100 transactions shall be initiated for each of the tally buttons. 4. On-board Pass Sale/Activation Transactions - a minimum of 100 transactions each for safe/activation of each type of pass (Day, Week, Month) purchased on-board shall be performed using cash (pass sale). 5, Transfer Transactions - a minimum of 1.00 transactions shall be initiated. 6. Pass Activations - a minimum of 50 transactions for the activation of a pre-purchased pass shall be performed using both full fare and reduced fare passes. 7, Stored Value and Stored Ride Transactions - a minimum of -100 transactions using magnetic stored value farecards and 200 transactions using magnetic stored ride farecards for the base fare, and 100 transactions using each for the reduced fare shaft be performed. K. Dust `Test L This test shall be performed to verify that the on-board fare collection equipment is capable of meeting the environmental requirements of these specifications as well as the following combination of conditions: a. High temperature b. I ligh humidity c. Moderate winds d. Dust conditions I The Contractor shall prepare a test procedure, for review and approval by County not less than thirty (30) days prior to the commencement of the environmental test. This dust test shall include varying lengths of exposure by the on-board equipment, from one (1) minute to one (1) hour in fifteen (15) minute intervals. 8.6 Pre-Installation Checkout A. Upon successful completion of the FXT, County or its consultant will issue a production release to the Contractor to deliver all equipment specified. Prior to installation, a Pre-installation Checkout (PIC) Test shall be conducted. CAT or its consultant will select five (5) on-board assemblies at random from delivered items plus the FCMRS, including software to run all reports; and Data Probe (or wireless equipment), as supplied, with associated hardware, The PIC test shall take place at the County facility. B. The best objectives are: 1. To confirm that there was no visible damage in the delivered equipment. 2 To visually inspect a random sample of on-board equipment for conformance with specifications. I To verify that the on-board equipment works as expected by checking the bus operator sign-on/sign- off function and to verify other operating functions by processing various fares. 4. To ensure that all data reports are produced in accordance with specifications. 5. To determine by these procedures if installation can begin or corrections and/or adjustments are needed followed by a retest before installation can begin. C. This equipment shall be set up at the County CAT facility by the Contractor in such a mariner as to permit all of the above listed test objectives to be evaluated. The following sequence of tests shall be conducted as a minimum: Page 55 of 79 16A 8 1. The on-board equipment shall be powered using a power supply furnished by the Contractor. 2. The on-board equipment shall be programmed for bus number and correct fare tables and related information downloaded from the FCMRS. 1 Visual inspection of the on-board equipment shall be made to ensure that there is no physical damage and that all specified displays, messages and prompting sequences including tone coordination occur as specified. 4. Sign-on procedures shall be completed followed by processing at least ten (10) fares of each type. 5. Cashboxes shall be vaulted at least twice per farebox tested. Sign-off procedure and data collection shall be completed and FCMRS printouts reviewed. 8.7 Network Interface Test A. As part of the PIC, the system shall be provided with test data simulating the County database for purposes of this test. Throughout this test, the date and time shall be modified a minimum of ten (10) times incorporating dates from a minimum of five (5) different years. B. All interface connections shall be inspected for proper installation. All functions requiring interface to the FCMRS, including all alarm and boundary conditions and security provisions, in all possible combinations, shall be tested. These functions shall include, but not be limited to, the following: I.. Alarm transmission and all other device/ component monitoring functions 2. Data transmission to the FCMRS 3. Data transmission from the FCMRS 4. Fare Table modification, download and verification 5. Automatic report generation at the FCMRS C. The Contractor shall identify each integrated function in its 'Test Procedures, including the boundary conditions and security provisions for each item of equipment and operation. D. All data transmissions shall be inspected and tested for accuracy. Inaccurate data transmissions shall be recorded as a failure. 'The Contractor shall take any corrective action necessary to ensure the proper performance of all functions. E. Samples of all reports available shall be generated by the FCMRS. Format, layout, page and column headers, data and all other information shall be reviewed to confirm. compliance with the designs approved at the Final Design Review, Contents of the reports shall be compared with the known contents of the data. Successful completion of the test requires no discrepancies between report contents and known data as well as proper formats, 8.8 In-Service Qualification Test A. On successful completion of the PIC, Coulitv, will issue a release for the Contractor to install equipment. After approval of the 1AT results, the ISQT will begin. The Contractor shall supply adequate spare modules, assemblies, parts and consurnables to be used throughout the ISQT. B. Object And Conditions Of The ISQT 1. The purpose of this test shall be to operate the equipment listed above in revenue service for a period of four (4) weeks. This test shall be conducted with buses operating on their designated routes in revenue service. 2. The first seven (77) days shall be designated as a settling period, but with all normal operations for revenue service being I carried out and accuracy and reliability data being documented. Prior to this period a Failure Review Board (FRB) shall be set up. The FRB will ascertain what constitutes a failure and what the satisfactory corrective actions will be to prevent recurrence when the ISQT begins. Page 56 of 74 16A 81 Failures shall be established in conformance with guidelines specified. At the end of the settling period, the ISQT shall begin and shall be conducted over the next twenty-one (21.) days. 1 The Contractor shall be responsible for performing all. maintenance actions during ISQT T C. Test Requirements If 1. The equipment shall be operated in full revenue service. The measures to determine acceptance o equipment shall be the Accuracy Test and the Reliability Test. I (settling period) z 5,000 2 77,500 3 9,000 4 10,000 D. Accuracy Test (MCBF) Cashboxes) — -------- -------- - - 17,500 99,3% 9c).6% '18,500 99.5% 4- - % — 99,7 20,000 i _'0 99.7% 99,83 21,300 99.7 %� L This test shall be conducted with all the ISQT on -board equipment. This on-board equipment shall be monitored daily during the ISQT 2, The minimum accuracy requirements stated above shall be achieved during the conduct of the test in order to continue the ISQT. If the accuracy requirements specified are not met at the periods indicated, County will have the right to suspend the LSAT until changes are made to achieve this, accuracy. Data handli . ng, data storage and the production of printed data on all reports shall be without error for the duration of the LSQT. Over and under amounts will be added algebraically to determine overall accuracy. 3. In addition to the verification of the accuracy of the collected revenues, a data accuracy review shall be performed. This data accuracy shall serve to ensure that all data are reported properly and accurately, that information is consistent between reports, that all column and row totals are properly calculated and that all alarms and messages sensed are recorded and reported. A complete batch of all reports shall. be printed on five (5) random days, as selected bv County during the ISQT, for this purpose. E. Reliability Test 1. For on-board equipment (including probes) - This test shall be conducted with all. the ISQT on-board equipment. They shall be monitored for report of any failures. All. conditions of equipment errors, repairs, adjustments, replacements, malfunctions of on-board equipment (including parts/ modules thereof) shall be fully documented for the entire test period. The minimum reliability requirements stated above shall be achieved during the conduct of the test in order to continue the ISQT. If the MCBF requirements specified are not met at the period indicated, County will have the right to suspend the ISQT until changes are made to achieve this reliability. 2. For the duration of the ISQT there shall be no more than one (1) failure of the FCMRS, data probe, revenue collection equipment or interface to the County network. F. PaS5/Fail Criteria Requirements specified for both the Accuracy Test and the Reliability Test shall be met in order to pass the ISQT. When the ISQT is passed, the equipment shall remain in revenue service. The ISQT test results and data collected shall be reviewed weekly by County. G. Failure of ISQT Paize 57 of 79 16A 810 1, In the event that the equipment fails the ISQT the Contractor shall have up to ninety (90) days to correct or update the equipment and retest until a pass category is reached. The Contractor shall maintain a qualified representative responsible for making adjustments and repair of equipment at the depot where the ISQT is being performed. Failure to pass the ISQT after this additional ninety (90) days shall be cause for termination for Default as defined in the Contract Conditions. 8.9 Reliability, Maintainability and Accuracy Test A. The RMAT will begin after a seven. (7)-day transition period at the successful conclusion of all equipment installations and shall be conducted over a period of ninety-one (91) days. The first twenty-eight (28) days are a settling period during which records will be kept, but performance will only be measured and verified during the final sixty -three (63) days. The Contractor shall be responsible for maintenance during RMAT. B. During the RMAT, reliability, maintainability and accuracy will be recorded by Contractor personnel and reviewed by County at the fourth (41h), eighth (861) and thirteenth (13") week stages to evaluate the performance for the preceding period. RMAT' test results and data collected shall. be reviewed weekly with Countv. Reliability, maintainability and accuracy at each stage shall meet the performance requirements specified. 8.10 Final System Acceptance A. Final system acceptance of the fare collection system by County shall be. contingent upon passing the RMAT and the Contractor furnishing all required hardware, software, spare parts, documentation, training, supplies and all other items identified in these specifications. B. The warranty of the system shall commence upon final acceptance of the fare collection system and shall continue for a one (1) year period. 8.11 Test Performance Requirements A. General Requirements L The equipment shall be operated in full revenue service. The measures to determine acceptance of equipment shall be the Reliability Test and the Accuracy Test as follows: 99.8% 1-4 9,000 20,000 99.7% . ............ 12-13 10,000 22,000 99.700' 99.8% 2. The procedures described below shall start on day I of revenue service and shall be continued during the RMAT period. B. Sampling Method for Accuracy Test 1. The accuracy test shall be based on performance related to on-board equipment using a ten (10) cashbox sample. This sample shall be comprised of a control group which would be the same five (5) on-board pieces of equipment every day. The balance shall be audited on a predetermined schedule developed by County. 2. On-board equipment will be excluded from the daily audit sample if it was reported to have any malfunction or failure in terms of its mechanical or electronic operating functions, which could have corrupted its data. C. Accuracy Requirements 1. The RMAT accuracy trend specified shall be achieved during the conduct of the RMAT. If the accuracy requirements specified are not met at the periods indicated, County will have the right to Page 58 of 79 16A 81 interrupt the RMAT until changes are made to achieve this accuracy. Data handling, data storage and the production of all reports shall be in accordance with requirements specified. 2. During the RMAT, accuracy shall be monitored with reviews at the (4al), eighth (8th) and thirteenth (13,11) week stages to evaluate the performance for the preceding period Accuracy at each stage and cumulative to date accuracy performance shall also be evaluated and shall meet the requirements specified. 1.). Method for Calculating Accuracy The accuracy of the on- board equipment shall be calculated as for the ISQF, F. Reliability Test 1. All conditions of equipment errors, adjustments, replacements, malfunctions and failures shall be fully documented by the Contractor for the entire test period for the RMAT. 2. The following procedures shall be used to log chargeable failures associated with RMAT. The Failure Review Board (FRB) shall ascertain what constitutes a failure in the event of a disagreement. a. Operating Malfunctions — An operating malfunction is defined as a random malfunction that does not cause the equipment to be inoperable but would require some form of maintenance to be rendered, such as a blown bulb. b. Operating Failures An operating failure is defined as any condition that causes the equipment to cease working (e.g., logic board failure). An operating malfunction becomes an operating failure when the same malfunction occurs on three (3) different pieces of on- board equipment. An example is a bus operator display burning out in three (3) different pieces of on -board equipment. b. Item Failures An item failure is defined as an operating failure of a particular module which occurs three (3) or more times. For example: if the bill transport in farebox #123 shows three (3) operating failures this would be. logged as one (1) item failure. c. Design Failures A desig n failure is defined as a failure of a given type of module in ten percent (10 %) of the modules provided. An example is if there are 20 fareboxes in use and two (2) different farebox bill transports are each charged with an item failure, this constitutes a design failure. 3. Customer induced malfunctions are non - chargeable. 4. A daily maintenance diary shall. be kept which records all malfunctions and failures by type. Malfunctions and failures shall be recorded by major module classification. 5. An equipment maintenance report shall be prepared to record all maintenance related incidents and the determination of chargeability. 6. If a design failure occurs, continuation of the testis at the discretion of County. F. Failure of RMAT 1. In the event that the equipment fails the RMA the Contractor shall have up to twenty -eight (28) days to correct or update the equipment and retest for a. minimum of twenty -eight (2$) additional days until a pass category is reached. 1 In the event of a retest, the Contractor shall be required to maintain, on a full time basis for the entire repeated RMAT period, a qualified representative responsible at the test location for making al.I adjustments and to repair all equipment at the expense of the Contractor. 1 Failure to pass the RMA.f after this additional twenty -eight (28) days shall be cause for Termination for Default. Page 59 of 79 M�Lf. G. Failure Category Definition The following conditions shall be used as a guide to classify failures. 1. Relevant Failures: a. A relevant failure is any malfunction which prevents fare collection equipment trom performing its designated function, or meeting its performance criteria, when used and operated under the environmental and operational conditions stated in these specifications. Example: If a farebox fails to boot up into operation, it is a relevant failure. But if it is determined that the bus battery had no charge, it will not be a chargeable failure. b. Add relevant failures shall be chargeable failures when attributable to one (1) or more of the following reasons: 1) Equipment design 2) Equipment manufacture 3) Equipment quality 4) Parts design 5) Parts manufacture 6) Parts quality 7) Software errors (If software errors are corrected and verified for twenty-eight (28) days in revenue service during the tests, such errors shall not be chargeable as equipment failures.) 8) Equipment installation. 9) Contractor furnished operating, maintenance or repair procedures, toots and equipment that cause equipment failure. (If procedures are correct and verified, such failures shall be chargeable as equipment failures.) 2. Non-Relevant Failures a. A non-relevant failure is a malfunction caused by a condition external to the equipment under test, which is neither a functional, environmental, nor a test requirement in this specification and is not expected to be encountered during normal and Correct operation of the equipment in revenue service. b. Non-relevant failures shall be. considered non-chargeable failures and shall include the following: 1) Accident or mishandling, 2) Failure of test facility or test instrumentation. 3) Equipment failures caused by externally applied over stress conditions in excess of the approved specifications requirements contained herein. Certain customer induced failures such as use of torn or mutilated fare media and abuse of equipment. 4) Normal operating adjustments not as prescribed in the approved equipment operating and maintenance manuals. 5) Dependent failure(s) occurring with the independent failure that caused them. 6) Failures of expendable items having a specified life expectancy when operated beyond the defined replacement time of the item. 7) Failures caused by incorrect operating, maintenance or repair procedures. C. If incorrect procedures are employed it is not a chargeable failure. H. Failure Review Board (FRB) Pagge 60 of 79 16A 84 L Durinod����v�(�days�d�BQTa����v�wDw���)��bee�b�h�The ~ members �oun���m�[U member �e ��B r,iD ��|u6e ��o �� ��poseo�o� ^�r==^'"^ys Contractor. 2. The FRB will ascertain what constitutes a failure and what the satisfactory corrective actions will be to prevent remrTe.nce when the RMATisrun. 3. Failures shall 6e established io conformance with guidelines, The end o[ the ISQT and first twenty- eight (28)dayperioJo[theDMAIthe FRB shall review all data from each test and finalize plans for continuing. 4. The RMAT data will be reviewed and approved by the Failure Review Board before it will become official. The FRB ebaD agree no the procedures to resolve issues related to "Fleet Defects". This applies to any hardware or software conditions that result in an unacceptable performance and that this occurs io more than twenty percent (20%)of the fleet. l Data Verification L During each of He��b�d��d6omJe�e�x�&u�M�w� ~ This yb�U - the verification ofuOcunoecdv�yaopec�aasoci�sd with 6ever��d6v[oonty� mcuzue transfer of data, production of reports and operation alerts and alarms. 1 Each day aspecific fazebox will be selected and the detail data will be printed. This data will be verified against the data transferred to County departments to verify that iLhas been transferred properly. In addition, all transactional data for dhatfa,ebox will be verified against the summary data compiled and reported. 1 The periodic reports (daily summary, weekly summary, monthly summary and annual summary) will 6e printed each day to verify that the totals are being accumulated properly. Cna random basis verification of alarms and events will beverified. 4. None of these tests shall fail. All data shall be transferred and properly available for review and manipulation by the County network. Corrective Action If the ���u�z�y�qu�e�eo� a�m�a�doeddor�g�eDM&T ' - re�o�tkdsand furnish labor tucorn�taml/co t6e��o��acto� s6aDbe responsible to p�deo��� provide change the equipment at no additional cost to County. The corrective action and/or the resolution ofthe prnb\eu(e) shall be subject ho approval byCounty. END OFSECTION ix. TRAINING 9] General Training Requirements and Plan A� The Contractor shall be ���[u�d� u�md�gto8mmg�me�/ ' ���octu 6mm600t� spec��dherein, Training ubaU�ckzdecourse deve�poneut providing o�aopp?yu�� manuals, classroom aids, etc, Practical training on equipment shall occupy u significant portion ofall training classes, The training presentations and material shall 6einEnglish. B. Instruction y6uD be designed to include courses described below and shall cover equipment familiarization and systems operations. The training obaD he provided to 6dog those aoolovea designated tothe level c6proficiency required for performing their respective duties. Formal training shall include both classroom and practical work, and shall be augmented by informal follow-ups as needed. C. The Contractor shall provide experienced and qualified ba1rucbno ho conduct all training sessions et Couotv designated training facilities. The Contractor isresponsible for insuring that the instructors teaching these training courses are not only familiar with technical information, but are able umutilize Page 61 of 79 16A 84 proper methods of instruction training aids, audiovisuals and other materials to provide for effective training. D. The Contractor is responsible for providing all training aids, audiovisual equipment and visual aids for the conduct of these courses. At least one (l) session of each different training course ybuU be recorded ooDVDhv the Contractor. E. All training materials are to become the proper�, of County at the conclusion of training. F. Initial sessions shall be provided for maintenance and operations training not less than thirty (30) days prior to the commencement of installation of any portion of the system. Final maintenance technician training shall commence during the time period when equipment is installed on the buses, prior to revenue service of the system. G. At the request ofCounty, the Contractor shall, during the warranty period, provide three (3) additional refresher training aesaions nf any of the courses provided under this contract. These refresher training sessions shall be held in Naples, FL during the warranty period at no additional cost- H. At the request o[ County, �e{�ombactory6oD'during and nptn60 days aHezioop�mrnha�on,provide equipment to 6ecuouubu<e and buio the public on the use of electronic 6azeboxea. These training sessions shall be held in Naples, FL in locations, dates and times selected by County no additional cost. 9.2 Submittal and Approval Requirements A. Submittal I. The Contractor shall submit the training curricula and materials for review and approval by County. No training shall occur until training materials have been approved by Connty� The n time corzbcola shall meet all training requirements and indicate course content, b requirements, and who should attend. Training curricula shall be provided for County review sixty (60) days prior to commencement of equipment installation. 2 Should this material include bzfonoubmz as provided in the system documentation and manuals, any updates bo that documentation which affect the training materials shall b e updated in the training materials amwell. B. DequiredCurricula and Materials The �bv� -6uUnp/iogcnrzicola and ozuhezbsbe related to �ainingmbaDLm provided ynbj�tuoayprova ' w County. l, Instruction Material: The primary source of instructional material shall be the applicable equipment operating and maintenance manuals. In addition, the Contractor shall develop, for each course specified, notebooks containing muc6adcbtiooa1dzop/ingu'deacdpdveinforonadonuoJpromedures necessary to ensure that all learning objectives are met in an orderly and timely manner. 1 Student Guides: All students shall be furnished with u guide containing material wbkb mirrors information in the instructor guides and provides the information necessary »n effectively train the students. 3. Instructional Equipment and Training Aids: Izubsizg mbaU be conducted using fare collection equipment in normal operating condition. In the event such equipment has been accepted by County, the equipment will be made available twthe Contractor for training purposes. 4� Training Schedule: 7rabd d u�aysess6ull6*p/en beJuledatleast&drty(3V)dayoinadvance and in coordination with County. Classes will be conducted ut facilities provided byCounty. 5. Training Materials: a. Course materials, including notebooks, instructor manuals, and handbooks will become the property of the students and instructors, as appropriate, at the conclusion of the training course. Page 62of7V 16A $'" b. At the completion of all training courses one (1) set of camera-ready, letter quality reproducible documents or computer files for each course outline, lesson plans, training aids and notebooks shall be provided to the County. 9.3 Bus Operator Training A. The Contractor shall provide an instructor who is experienced and qualified in the operation of the fare collection equipment. One (1) portable standalone fare collection equipment training units with a 110 volt AC power supply shall be supplied for the training. The standalone training units will become the property of County at the conclusion of training. B. The purpose of this training is to instruct County CAT bus operator instructors who in turn can train bus operator-, in the operation of the equipment. C. At the completion of training, County CAT instructors will demonstrate competency in the operation of the equipment by taking and passing a performance test and written examination. D. This course shall be designed to provide management, supervisory and operating personnel with a functional understanding of all of the fare collection equipment. The functions of each module shall be covered, including the interrelationship of the equipment with the customer. Personnel attending this course, in addition to bus operators and transit supervisors, will include the following categories: management (at the overview level), marketing, public relations; and operating, financial and other administrative personnel. E. The instructor classes shall conclude four (4) weeks prior to the start of the ISQ'I' in order to allow for the training of bus operators. 9.4 Revenue Service Training The Contractor shall provide an experienced and qualified instructor who shall conduct training classes for the complete revenue collection /revenue service operation. 9.5 Data Management and Reporting System Training (Documentation Only) 1. The following shall be included in the FCMILS documentation: a. External interfaces. b. Development assumptions. C. Processing Scripts. d. Data dictionaries. e. System flows. 2. Data diagrams shall be provided to County. All programs shall be defined and described fully, showing all inputs/outputs, samples of reports, logic flows and major functions described, as well as assumptions used during program development. Detailed system functional requirements shall also be provided. 3. Explanation of the software instructions and methods employed to make changes in software programs shall also be taught. Use of software documentation shall also be fully covered. 9.6 Data Management and Reporting System User Training A. The Contractor shall provide an experienced and qualified instructor who shall conduct user orientation training for FCMRS users, including staff who will be responsible for the generation of system reports and queries. B. The purpose of this class will be to provide basic training and to describe to personnel the data structure, program logic and data transmission operation functions and how the software in the Page 63 of 79 ECNIRS can be used to perform data sorts and selective data reporting, file retrieval from back up files, and how other programmable functions are achieved. C. The goal of the training shall be to make the participants competent to both operate and teach others the proper operation of the report generation system. D , This course shall include the use o{ simulated or actual data provided hy the Cuotra��x. 'This data shall include sufficient information to cover multiple months and shall include events and transaction data from all types of equipment furnished. 9.7 Equipment Maintenance Training d�� n�d�d�8�ma��n�ce�d� A. The {�on�acbxy6aDprovide ao�s�uchurvvbo is experienced 9u fare collection equipment. B� The purpose of this training is to instruct technicians in the maintenance of fareboxes, the RCVS and all related equipment that County technicians will bemaintaining. C� Fare collection equipment shall be provided for the training sessions. D. At the ������b��o w�d�m�b�cnm����&cmu�b�n�ofd� completion equipment as b`6�aUa6 by taking and passing troubleshooting and repair and written exaozh`odoua. E. This maintenance training information o6aU include troubleshooting and diagnostics of all kvuv/u problems for all types of fare collection equipment furnished. 9.8 Additional A�Io addition mthe training as specified. above, small sessiouwi&I-3County staff members shall also be provided ay described below 1. SecurityToiniog'Individuals shall 6e trained in the understanding of all security components and interlocks nd8ziu theayotem' including farehuzes' cashbox receivers, revenue collection vaults and associated software. It is anticipated that this effort obaOncguire6our (4) to six (6) hours of training during a one (I) day period. 1 AdmiuistzudveTrabzing - Selected individuals a6ad be trained in the overall understanding of the fare collection system basics. It is anticipated that this effort shall require four (4) to six (6) hours of training during a one (I)day period. 1 Planning Training - Individuals shall be trained in the understanding of the origin and meaning of all system data and how to manipulate. the data to provide needed reports and information. It is anticipated that this effort shall require six (6) to eight (8) bnuzm of training during u one (I) day period. 4, Revenue Tzmckbz8 SySystem 6v� Training - Individuals shall be trained in the operation and understanding of the revenue trackio syotem, including &e meaning of all system data and understanding reconciliation reports as well as all cashbox movements. It is anticipated that this effort shall require four (4) to six (6) hours of training during a one (1) day period. 9.9 Bus Operator Training Video A. At the end. of the training, the Contractor shall provide County with five (5) copies of a video recording inDVD format that contains the training that would normally 6e provided by ao experienced trainer showing complete operation of the fanebox from the perspective ofa bus operator, B. This video recording shall include all procedures required by the system nt the start of, during, and at the end. of revenue service. 'The video shall highlight customer displays, bus operator diaoiuvm, button pue*yey' Fare6ox indicators and 6are6ox actions (card issue/return, �tc.) as wen as czouanzez service features of the farebnx such as the MSK'TPU,coin and bill validation, etc. Page 04oy79 16A 8 w� C. The video shall be updated within thirty 8Ndays after the final acceptance ofthe system to accommodate, any operational changes. D The video �cvrdingshaD8e approximately �n(I0)to6f�eu(I5)ooiuobein�og8;and presented in D. an edited and professional format including a sound track, introduction, appropriate graphics and other features E� Actual training sessions and recordings from other transit properties maybe used for some aspects of this video recording, but County shall have final approval of contents and quality. END OFSECTION X. DOCUMENTATION 10.1 General Requirements A. All -` � - shall. bein ~ using[Smemurementsmdbesu6mitted directly to County. A-documentation submitted through a third party will not he considered received. All ilm/ to those used for documentation shall be provided in hard copy and electronic formats oio Microsoft products. B, Prelimdnarvdrafts of all manuals shall be supplied ninety (90 days before installation begins at the first ts of �� 6�o T�domme���be� -m as as . T��N�� of preliminary draft document, manual and drawing as described in this section shall be provided by im [on�aztur. These documents °iUbcreviewed and comments furnished to the Contractor v�b thirty (30) calendar duysc6 their receipt. C. Complete final manuals in the quantities and quality as described in this section shaft be supplied no less than five (5) days prior to the commencement of the first depot installation. D. Pootvvazrant-v manuals shall 6e provided at the successful completion of the initial warranty period. '[heseybaU beofthe latest revision and shall have incorporated all modifications or changes zondc to any part of the fare collection system covered under this specification- The documents o6a8 not be considered 6oul vvb6not the approval of County. Pont warranty manuals may be submitted for approval np0n sixty (60) days prior to initial warranty expiration. E The warranty period shall not end until complete and final post warranty documents as specified herein have been fornis6eJbv the Contractor and approved bvCounty. F. The Contractor y6aO provide a list of all special or custom tools or instruments required to nzatubin or adjust any component within the Fare Collection System. G� Diagrams and drawings shall identify each and every component in the Fare Collection System and call out each component with the, unique part number as referenced the Bill-cf4vlateriab . H. The Contractor shall provide a parts layout for every printed circuit board, specifically calling out each component, 6eit mechanical orelectricalbzoatzna and showing its exact location. I. The Contractor shall provide drawings showing the location of all of the traces on the top and bottom and any through board connections of each printed circuit board. These drawings shall be laminated and suitable for use during shop repair of components. J. Each type of maintenance manual shall contain, but not ba limited to: a description of operation; q n prinstallation procedures; a complete part-, identification and list; tin inspection procedures; preventive maintenance procedures and program; repair procedures; diagnostic procedures; Wiring diagrams; electrical schematics with board and cable. identification; and adjustment procedures, K. Subcontractor's names and part numbers shall 6ecross referenced with the Contractor's part numbers for the required parts lists. Page d5of79 16A 81 L. Electrical and electronic drawings shall be supplied to show engineering changes made to any component or module Lip to the end of the warranty period of the Fare CollectionSvstem supplied. M. The o`nnua|y shall becomplete, accurate, up-to-date, and shall contain oo{y that information which pertains ho the system installed and shall be written ioEnglish only. 10.2 System Documentation Requirements A. Manuals required shall include the following parts, asapplicable: 2. System Characteristics a, A physical description of the subsystem and pertinent technical characteristics. 6� A description of the functions that the ynby9sheru is designed to perform and the general medbodyecoployed ho accomplish those functions. 2. Principles of Operation (for maintenance manuals) a. Detailed discussion of the theory ofoperation. b. Interface between subsystem elements. c. Signal Govv sequence correlated boblock diagram(s). 3. Operating Procedures a. Turn-on and turn-off procedures, b. Detailed bus operator instructions sufficient to operate the equipment in each mode of operation. C. Emergency operating procedures, 4. Maintenance Procedures (for maintenance manuals) a. Preventiveozaioteouncapzoce6uoe'ec6edu6esandmanufactorer'oxecoznmendedproducts. b. Fault isolation and analysis procedures. c. Corrective maintenance and repair procedures. d. Svmeom calibration. and test procedures. e. Illustrated parts catalog. V, A document control method shall be proposed by the Contractor and approved by County. C. The Contractor s6uD submit to County for approval aIable of Contents and sample formats for each type of manual and for the Illustrated Parts Manual. I0'3 Security Manual A. To the greatest extent feasible, the Contractor shall not, in any of the following documentation, include items related to the specific operations of, or maintenance of, security devices which may be used for fraudulent purposes. B Information of this ��e' shall be identified and submitted separately, stamped CONFIDENTIAL. It shall be the Contractor's responsibility to meet with the County Project Manager to determine what infor-mation shall 6e considered confidential. C. County regards the documentation of certain software programs and certain aspects of maintenance to besecurityrelated. Also considered aasocuchyrelated are revenue collection and revenue transfer information; revenue equipment construction an � locking information; modother similar elements. Page h6oy7p 16A 84 10.4 Bus Operator Manua] A, The manual shall contain succinct instructions on how to operate each on-board item of fare collection equipment. Pictograms and photos are encouraged. Fault procedures need to be described as well am directions � fo,dea/ingvritbcn$ouzerserviceinyueyre|oted Lo equipment ope,u tio m B. The manual shall contain all biformatioo needed for safe, proper, and efficient operation of the on- board equipment,&Doo,n-tal operational sequences shall be described indetail. C. The manual shall be printed on plastic coated paper, or the equivalent, for durabilitv and be no larger than 3'I/4 inches wide by6 inches long byI/4 inch thick 10.5 Revenue Collection Manual The revenue collection manual shall include complete description of the operation of all revenue collection � �8�e�cnoemD��n equipment, including cashboxes, receivers, and receiver vaults, necessary operate. .. ay^her,, I0L6 Maintenance Manomalo A, The Contractor shall umo�a covering ���m�����d�ne��me����b�. including exercised ^��'������w/ i6�b�d�vm�ua��a���b�y�t� equipment. The materials provided shall contain, but not be limited ho: a description of operation,- installation procedures; preventive maintenance procedures and program; repair procedures; diagnostic procedures; wire diagrams; electrical schematics with board and cable identification; and adjustment procedures. B, The manuals shall identify any special tools required for any ofthe [� Durable materials shall be used to provide extended life for these manuals in the maintenance shop environment. D. An electronic copy of all manuals, in Adobe F'DF Or other form approved by County, shall be provided on four (4) sets of CD-ROMs as well as one (1) printed master copy on. 8-1/ix 11 inch paper. E� Manual Contents shall be as specified herein and shall be consistent with training. l. Preventive Maintenance Section: shall contain all information needed to enable maintenance technicians to perform all periodic inspection and preventive maintenance tasks buludbuQ lubrication, inspection and replacement of consumable items. The manual shall contain recommended IN{schedules. 2 and Corrective Maintenance Section: �a c���aD��ma�n�e�d� diagnose problems - and make adjustments and zepnbo to all Fare Collection System components and sub-assemblies to restore the svytem too normal operational condition iopn efficient and dzneh/ manner. The manual shall include otaminimum u general description of each subsystem, component and subassembly; functional block diagrams, detailed schematics; troubleshooting flow charts and wiring diagrams. 1 Shop Repair Section: ehnU contain detailed descriptions of each aaseo`6h/ and subassembly sufficient to service, maintain, repair, replace, rebuild, and overhaul the equipment. Systematic procedures; wear and tolerance limits for 6ehzoinbog vv6eu overhauls are needed; overhaul procedures; and special tools and equipment required shall 6eincluded. 4� lDnytra/sJ Parts Section: ohmD describe and identify each module, sub-assembly and part within each piece of equipment with its related supplier identification number and Contractor identification number. Exploded drawings shall be provided to permit identification of all parts not readily identified 6vdescription. Page d7of79 16A 8'0 I0.7 Test Equipment Manual The Contractor shall provide manuals for each type of test equipment furnished. Manuals shall include all information necessary to allow proper and full use of all test and calibration equipment furnished. I0~0 Fare Collection Management and Reporting System Manual A . The Contractor shall provide a Fare Collection Management and Reporting system Manual, to include dzuwtoQs vvbicb identifv 66e various parts and aese��6�cs of the system. The manuals ohuDcootoio ' start-up procedures, operating modes, interconnection diagrams, preventive maintenance procednns and program; diagnostic procedures and wirio�diagrams v,iLbboard and cable idenb6cabon. B Equipment ��aooubsbaDbeprov�ed� G �G`eha/�wuzeuu��omponentsusedto�ougure8eoyntem. � The manuals shall include those instructions and maintenance manuals furnished 6v the supplier of each type of processor, keyboard, rnn6enu' fixed disk drives, other storage media, monitor, pzbnhcr' The content ofthis information 6ockop system, uubntezroptib|e power supply, and other components. shall be complete and detailed. It shall be the Contractor's responsibility to acquire the required information from the respective manufacturers. C. Software Manual and. Program Documentation l . The Contractor shall provide complete documentation for each Contractor developed and furnished computer software program for t6eFCMDS, including the money room terminal and any ntbcz subsystems using a microprocessor or other computer. 2 The snfhvaze documents sbaDbe furnished for review and approval by County prior to installation � by County of the equipment on County F«operty� 'The original and each amended version of u software program shall require new copies of the documentation to be furnished for review and approval by County prior to installation by County. The software documentation shall not be distributed beyond the authorized personnel, 3, The documentation for each version of each program shall be complete and comprehensive to include, but not be limited to: comp/ete source code listings with fully documented statements; comprehensive flow charts; and block diagrams explaining the system aya whole and showing how the individual programs are interrelated. 4 The software docuo�entaabmDc{ear}r identify pvba1data elezneuto are stored,- the source of each � data e�oeo� and how data � structured, ' transferred and utilized. This shall include the snH`vaze logic, processing rules, restrictions and exceptions, default cmudibora' hard and soft wired parameters and the overall process by which each of the reports specified is generated. 5. Software manuals from suppliers of third party software components included as part of the system shall he provided asa part of this program dncuu` otudnn. END OFSECTION X1. SPARE MODULES, SPARE PARTS AND CONSUMABLES IIJ Spare Modules and Parts A. Spare modules anti pmrt-,shall be furnished in. accordance with the listing furnished with the Price Proposal Form. B, Spare modules and parts should be new and manufactured to the specifications of theOTiginal parts in the delivered 6uze6oxes and completely interchangeable. C. A list ofvendors providing spare pads and coosuoza6lea y6001d be. provided by the Contractor to County within sixty (6O) days after N7P. Page 60of79 16A 81 D . The spare modules and parts shall be manufactured concurrently With production of modules and parts for delivpre6egu�nzuotThe CunbacbxybaDprepare and yubnnittu County a spare o`o6o|esand paz� botdo���—�the part number and description nfeacbomduleand part that ishobefurnished. 11.2 Spare Parts List Contents A ��mop,e���cUstufspuoemudu6��dPe�6oraDe�dpmeote�8bepzn�d�toCoun�wd6� A. sixty (60) days after NTP.This listing include all items that can fail orthat require replacement due tn wear over a ten (IO) year period. B . In addition, the Contractor shall provide at County's request at any time the equipment is being used in revenue service, a complete, parts and modules list, together with prices, parts numbers and descriptions modules, parts and parts within the modules for all equipment furnished by the Contractor. 11.3 Consurnables A �o��o �� aUco�u�a�s�o�a��o���He���or�y ��m A. - ` levels 6vCnunt�,��aooe coo�yonentthat has been �s�l�dbased upon prcjec�d�dersbip �rnv�4e4 ' (I) year period c6operation. B. Acozuprebensb/e list of system coosumabkes shall be provided to County within sixty (60) days after NTR C 7lx� Contractor shall 8`e cpoou�nab�s upon the installation of the eqoipouuz� Should the In- Service ' i� o��6 �� Contractor �a �� 8� &�e � 5�rvicm {)oa�d�cadoo Test (IS(}T) not ^ onzua/g,, � u ^ uonaomables and replace any conooroah|em utilized From that point until the lS(7T has been passed successfully,This procedure shall apply for all revenue service acceptance tests. 11.4 Support Equipment 'The Contractor shall provide the testing, service and other special tools and equipment required for proper operation and maintenance cf the system aso part of the initial equipment delivery. 11.5 Future Supply Provisions A. For twelve Final Sys' tem Acceptance, the Contractor shall make available, for delivery within sixty (60) days, all Contractor designed equipment, modules and parts as are or may be necessary to service and maintain the equipment delivered toCounty. B Alternately, during the twelve p2) year period, the Contractor shall ensure that County can obtain the � equipment, ' modules and parts from other suppliers for a comparable price (generally within ten percent (l)%) of the part or module price on the Contractor's most recent price hat). The Contractor shall also offer County the opportunity of ordering the equipment, oo du"ley and parts at least six (h) months before discontinuing their production- It shall be the Contractors responsibility to alert the County of this situation and to provide to the County's applicable drawings, parts lists and at least two (2) sources for obtaining PaTtS that were previously supplied by the Contractor. C . Asanalternative, the Contractor may upgrade or retrofit all of the Contractor supplied equipment to use modules and parts that are readily available from the Contractor or other suppliers at a comparable price bn meet the requirements of this subsection. The entire cost of any such upgrade nz retrofit shall bea1 the Contractor's expense. D. The Contractor shall also notify County in a timely manner when improvements or modifications to parts or modules are fa6zicated'8zat Could improve the operation ofCoontvssystem. E. In the event that the Contractor cannot furnish any system equipment, modules or parts within sixty (60) days after receipt c6aoorder, and there is no suitable alternative supplier, County will have the dubLhofa6zic�emzhave�bccatedErnmdrup"��gsondsper�codoosprovidedbv8be[oN�acbx,sucb ~ equipment, modules co The C ou trac�xs6nDp,ovide . at its sole expemoe , any necessary patent par ts . releases. If the Contractor is not the manufacturer of a particular part u« module within the system, the Page 69nf79 16A 801 obtaining the necessary information to fabricate the Contractor shall make every effort to assist in which have been necessary= parts or modules that are necessary for proper system operation, discontinued. F. The Contractor's undertaking herein is a covenant, promise, representation, and warranty made in consideration of the price or prices to be paid b y County for the equipment to be delivered hereunder, as well as for such spare modules and parts. END OF SECTION X11 SCHEDULE OF EVENTS 12.1 General A. The Contractor shall furnish County with a detailed project schedule in bar chart form identifying all major milestones, to meet the critical delivery, installation and testing dates and task duration as specified in Section 2.0. The following items shall be addressed as a minimum: 1. Submittals and. Documentation 2, Design Phase 3, Software Development 4, Manufacturing 5. In-Factory Testing 6, Shipping of System Equipment 7, Installation & Installation Verification 9. Testing (by test) 10. Final System Acceptance B. The Contractor shall prepare all deliverables in both Microsoft Office (Word, Excel or PowerPoint) and Adobe PDF formats, with County granted full rights to reprint as needed. 12.2 Project Status Tracking The Contractor shall prepare a System Implementation Plan (SIP), including the detailed implementation activities/ schedule, progress milestones/ status and assigned staff. The Contractor shall also include a Safety Management Plan in their SIP, which shall detail their responsibilities and procedures for safety during the different phases of the project, including (1) conducting pre-installation surveys to identify potential project safety hazards; (2) identifying project hazard control procedures, including occupational (worker) and public hazards; (3) providing project safety orientation and training to its subcontractors and the transit agency staff who will be involved in the project, and (4) furnishing procedures and training for project accident reporting and investigations, The initial draft of the SIP shall be provided to County within two weeks from Notice to Proceed (NTP). The revised. SIP, addressing comments from the first onsite meeting, shall be provided to County within two weeks after this meeting. The SIP must be approved and accepted by Count-,, before it can become effective. An updated SIP shall be submitted to County at the beginning of each month. Page 70 of 79 16A The Contractor shall maintain an Action Items List (All,), indicating for each item the following: (1) item number; (2) date generated; (3) brief item descriptive title; (4) assigned person with lead resolution responsibility; (5) date resolved; and (6) ongoing dated notes on resolution status. The AIL shall be sorted, primarily by unresolved vs. resolved items and secondarily by the date the item was generated. 12.3 Program Plan The Contractor shall prepare and submit a Preliminary Program Plan for County approval within ten (10) days of Notice to Proceed. The Preliminary Program Plan I shall be a summary document indicating the manner u-i which the Contractor has broken down the major tasks necessary to comply with the Contract requirements. 12.4 Project Schedule The Contractor shall, within ten (10) days of notice to proceed, submit a reproducible copy of the project schedule showing the start and completion of all major events, operations and contract items planned for County approval. he Contractor shall update the project schedule on a monthly basis and forward the updates to County to reflect revised completion dates. The Contractor shall notify County immediately of any changes that are expected to delay the completion of the project more than two (2) weeks. 12.5 Monthly Progress Report and Weekly Conference Calls The Contractor shall participate in weekly conference calls with County Project Manager, other County staff and outside consultants as determined by County Project Manager. The agenda for these meetings will be to discuss the most current status of and plans related to all issues identified in the recent releases of the SIP and AIL. County reserves the right to identify for discussion any additional issues beyond those in the SIP and AIL. A status report shall be issued to County at least two days prior to each conference call, including (1) an agenda for the upcoming conference call highlighting key discussion items; and (2) an updated AIL with the updates incorporating the discussions of the previous bi-weekly conference call as well as other subsequent developments since the previous AIL release. The Contractor shall be represented in these conference calls by at minimum their Project Manager, as well as any additional Contractor staff necessary to properly address the current issues and project status. County will be'represented by their designated implementation management representatives. Conference call facilities will be arranged and paid for by the Contractor. The Contractor shall submit minutes within two days of each conference call. 8� Each month the Contractor shall submit a report describing work accomplished in the preceding month, work to be completed during the next month, and a discussion of any outstanding or expected problems. County approved modification to the project schedule shall be included as part of the report. In addition, monthly progress reports shall include a list of specific action items which require input or resolution by the parties involved in the project. 12.6 Minimum Required Onsite Work At the first onsite meeting, the Contractor shall be prepared to discuss County feedback on draft SIP and conduct Requirements Review. Page 71 of 79 At the second onsite meeting,,, the Contractor shall be prepared to discuss County feedback oil draft Design Review documentation. During the third and subsequent onsite efforts, the Contractor shall install system and conduct acceptance testing. These onsite installation and testing efforts will occur over an extended period, and will likely involve several different onsite trips and a range of different Contractor staff. 12.7 Invoicing The Contractor shall only submit an invoice once a fully-signed Acceptance Certificate is generated by County indicating that a progress pavinent milestone has been. achieved. County will withhold 10% retairiage on each invoice. Upon acceptance by County of each stage of the project, the total retainage for that stage will be paid to the Contractor. 12.8 Design Review The Contractor shall participate in the Requirements Review (RR), as part of the first onsite meeting. The RR meeting shall discuss, for each contract requirement, the following: (1) County design interit, (2) the intended Contractor design approach; and (3) the general Contractor approach to demonstration through the acceptance testing process. The Contractor shall submit draft Design Review Documentation (DRD) within four wee", of the RR meeting. The DRD shall include the following materials: (1) an overview of the equipment, system and configuration proposed for implementation; (2) detailed technical documentation for each equipment item; (3) detailed technical documentation on all software., addressing the functions of each module, the format of all user interface screens, the format of all reports, the data fields to be included in all data exchange I interfaces and any with County prior to system other software aspects warranting advance agreement I customization./configuration; and (4) a table detailing the approach taken i:i-i the design to address each individual contract requirement. The second onsite meeting- will include discussions with County on their feedback on the DRD, and shall occur within four weeks after the draft DRD has been submitted. The Contractor shall submit the updated DRD within three week,-, of the second onsite meeting. The DRD is intended only to reduce the chance of any misunderstandings on the design intent or interpretation of the contract requirements. The DRD shall not alter the need for the successful formal demonstration of each requirement through the Acceptance Testing process The Contractor shall submit Installation Design Documentation (IDD), for County approval prior to undertaking any installations. The IDD shall provide text, drawings, illustrations and images using adequate detail to allow for quality installation by a technician without further training in conjunction with other installation instructions provided. by the vendors of individual equipment components. The IDD shall include details on (1.) equipment installation Locations / mounting; (2) routing, conductors, color- coding, labeling, and COnneCtOTS for power, communications and vehicle ground circuits; (3) connections with, any required modifications to and restoration of existing infrastructure; (4) work area and equipment storage requirements (5) methods and quality standards; and (5) supervision and quality assurance procedures. END OF SECTION Page 72 of 79 16A 8`4 X111 WARRANTY 13.1 General A. Basic Warranty 1, 'The Contractor shall guarantee all workmanship, materials, components and equipment for a period of one (1) year after installation and full acceptance of the fare collection system, 2. If during the period of the warranty any defects or faulty materials, equipment or software are found, the Contractor shall immediately, upon notification from County, proceed with corrective action at the Contractor's expense to replace, repair or otherwise return the system to full working order. 3. The Contractor shall provide sufficient spare modules and parts to operate the system at not less than 99% availability at any time for the period of the initial warranty. These spare parts shall be furnished with the first equipment delivery. 4. The Contractor shall develop, test, and provide all applicable software "patches," upgrade,-, and other remedies necessary to keep the system software in good order. The installation of such remedies will be Performed by the County in close coordination with the Contractor. 5. All Proposers shall submit, with their proposals, a copy of their standard warranty as well as any special terms and conditions covering the equipment and software described in these specifications. B. Extended Warranty The contract includes a total. of 5 years warranty for all the equipment 13.2 Coordination with On-Going Maintenance Support The basic and extended warranty provisions of this section are intended to be in conformance with and enhance the provisions of the section of these specifications describing Maintenance Support during the period in which the basic and extended warranties are in place. END OF SECTION XIV. MAINTENANCE SUPPORT 14.1 Support Requirements A. From Installation to System Acceptance Contractor shall p rovide on-site personnel. qualified to troubleshoot all aspects of the system from the time of first equipment installation through system acceptance. These personnel shall be responsible for preventive maintenance, troubleshooting failures, removing Y and replacing defective parts, returning the unit to service, and initiation and follow-up of remedial actions. As an alternative, the Contractor may use County maintenance personnel to perform some or all of these activities at the Contractor's sole additional expense as long as regular maintenance of County buses and facilities is not affected. B. From System Acceptance Through Warranty Period Contractor shall assist County maintenance personnel in performing preventive and corrective maintenance including troubleshooting, removal of replacement parts and any warranty repairs, service, and campaigns. Both on -call telephone support and on-site technical support, when required by County for troubleshooting and. support, shall be provided as part of the system warranty. Page 73 of 79 16A Contractor's field a��m����a��m����)v����� ' and im�� of the where equipment is installed during the period between system acceptance o ex� - i� Laid od���uc�no*o��os��s»empezaon�� vvuzraorytopro� e���ero � . Io the event ofa fleet defect that appears to County's project administrator to6ea generalized problem that mav affect all similar equipment, ocusystematic defect (a defect in the data system, receivers or other subsystems that affects die ability of the fare collection system to achieve its intended purpose) the manufacturer's representative shall arrive as soon as possible, but no later than thirty-six (36) hours from the time of notification, at the County facility to review the problem and setup needed corrective action. The Contractor shall contract with a qualified company approved by County that can be called on for maintenance of the computer hardware and standard operating software and short response time critical troubleshooting on an emergency basis when the Contractor's staff may not be available. C After Expiration of Warranty �� On-call maintenance support shall be provided by the Contractor for the life of the equipment system acceptance. On-call support shall be provided via telephone conversation for hardware and software problems and operational troubleshooting at no additional cost to the [mpuLy (}n-site technical support, when required for troubleshooting, training or other similar activities required by County shall be provided at standard Contractor rates as per Exhibit B for preferred customers. D� The Contractor shall provide the maintenance support and vvaoaoLy services described in these specifications to cover all depots on all equipment required to be provided by the Contractor. B. Contractor shall maintain on-site, a spare parts yppph/ sufficient to meet maintenance and warrant-y obligations set forth herein from installation through the end nf the five (5) year warranty period. 14.2 Test Equipment A. The Contractor shall suo�v��e��me�wb��� means 6n�o�'ma��n�o personnel to bench test supply repair each major module and/or subassembly of the on-board 6zne collection equipn,ent B, Maintenance Test Stand (Optional). This equipment shall be configured such that the following items are mounted on a stand or board and interconnected to provide a fully operational set of on-board fare collection e4uipmen�plus software �staUedooa heavy duty service &apbpcompnbrbo act aaafuDv functioning FCMBS, The maintenance best stand shall include at a zuiuinnom the following separate components: l B0 transport, including security mechanism 2. Coin unit 3. Logic boards 4. Data port bo probe data 5� Data transfer probe 6, Electronic lock assembly 7. Cashbox lDunit 8. All displays and the tone genezauzz(s) 9� Power supply lO� Magnetic swipe reader ll. Ticket processing unit C. All interconnections including wiring, harnesses, plugs, sockets and other connections shall 6e the same as used iom fully assembled Fare Collection System. The maintenance test stand shall 6e arranged b` such a manner that each module can be separately exercised to perform its operating functions. D. [nbo [nit Calibrator: Equipment shall be provided to calibrate and test the coin unit and related components. ftyze74of7n �06 16A 8 E. Bill Transport Calibrator: Equipment abaU be provided to calibrate and test the bill transport and related components. 13.3 Availability and Performance Requirements A. During the period when Contractor personnel are on-site: I. Maintenance oo fare collection equipment aboard the buses shall be performed in such a manner as to Provide for I00%availability of all buses needed by County to meet pull-out each day at each depot 2. Farebox equipment shall be brought back into service pdt6iu four (4) business hours of reporting anv incident. This shall be by module swap out or correction of the problem. B. During the period when on-call service is provided: E All questions shall be answered and requests for bfornzubom shall he provided within a twenty- four (Z4) hour period. 2. Spare pads requested by County shall be delivered within forty-eight (48) hours of receipt of fax, email oz telephone request from Cnnnt�. 3. Correction of software deficiencies shall be completed within a time as agreed between County and the Contractor, based on the severity and critical nature of the deficiency. At no time however, shall this time period exceed ten (10) hoshays days, unless prior approval is provided in writing by County 13.4 Computerized Maintenance Reports As an integral part o{ maintenance support, the Contractor shall include computerized reports asdescribed in other sections o(this specification that are designed to assist County, to perform regular preventative maintenance on systems' equipment and components provided in these specifications. This s6oDinclude preventative maintenance scheduling aswell us warning and alarm conditions and adequate training c6 maintenance managers and technicians in the proper and regular use of this capability. END OF SECTION Pap 75 of 79