Addendum_3.pdf

6 Saint Paul Street, Baltimore, MD 21202-1614 | 410.539.5000 | 1.866.RIDE.MTA | TTY 410.539.3497 | mta.maryland.gov

TO: All Prospective Offerors

FROM: Maryland Transit Administration

SUBJECT: Addendum No. 3 RFP No.: LOT-24-049-GM Small Buses for LOTS and Mobility

DATE: July 3, 2024

Effective today, Addendum No. 3 is applicable to the subject RFP. This addendum provides the responses to vendor questions, revised specifications, and Approved Equal Chart.

Offerors shall acknowledge receipt of this Addendum by completing and returning this form with the proposal submission package.

All other terms and conditions to the RFP remain unchanged.

Sincerely, Heather Martin Heather Martin Procurement Officer

MDOT MTA

Acknowledgement of receipt of Addendum No. 3 to RFP No. LOT-24-049-GM.

Vendor Name: ___________________________________________________________

Authorized Representative’s Signature Date

Small Buses for LOTS and Mobility

LOT-24-049-GM

Please replace Table A in RFP §2.3.12 with enclosed version.

Please utilize the Approved Equals Chart in the attachments to list all Approved Equals/Clarifications submitted by the Offeror to allow ease of tracking.

Please see the Attachment W Digital Video Surveillance Systems for Transit Vehicles is enclosed with this addendum.

Number Spec Question MTA Response

1.2 4 Requirements: Vehicle assembler, converter, or second stage manufacturer whose product is offered, as part of their proposal must be formally approved by the chassis manufacturer for the additions made to/upon the chassis.

Offeror shall provide a letter or certificate for the body manufacturer from the chassis manufacturer verifying full compliance with the manufacturer’s transit vehicle quality program and that all warranties offered by the original chassis manufacturer shall be transferred to the Operating Agency. Failure to provide such certification with the proposal will result in rejection of the proposal as non-responsive.

Ford no longer offers the QVM Certification and GM has never provided this.

The MTA will remove the requirement for the certification.

1.2.8 The gross vehicle weight rating (GVWR) shall exceed the weight of a fully loaded vehicle. A fully loaded vehicle equals the weight of the vehicle equipped to meet these specifications, verified by a weight ticket, plus the weight of the passengers (150 pounds for each ambulatory placement, 600 pounds for each wheelchair placement).

Clarification on weight of w/c placement. ADA is calculated at 300 pounds per person and a standard mobility "lift" has a design load of 600 lbs. Typically the w/c location spot on the weight analysis is calculated at 300 pounds. Please verify for weight calc purposes.

Please resubmit as an Approved Equal, with sufficient justification for using the 300 pound weight for wheelchairs, as the testing requirement is 600 pounds for Altoona testing.

1.13.1.1 Offeror shall submit with the proposal, documentation certifying that the proposed vehicle meets all applicable Federal Motor Vehicle Safety Standards (FMVSS) Regulations in effect on the date of manufacture of the bus body. At a minimum the following standards shall be included in the certification: 102, 104, 119, 205, 207, 208, 209, 210, 217, 220, 221, 302, 403 and 404

Per Braun, a commercial ramp does not need to comply with FMVSS 403 or FMVSS 404 NHSTA Compliancy. Therefore, we do not meet the 403 and 404 requirement.

The requirement for FMVSS 403 and 404 applies to lifts only.

1.5.10 Drilled holes and cutouts in exterior surfaces shall be made prior to cleaning, priming, and painting. The bus shall be completely painted prior to installation of exerior lights, windows, mirrors, and other items that are applied to the exterior of the bus.

Buses are sent to the paint shop after bus is completely built. Paint shop tapes off all exterior parts to make sure there is no paint/overspray on these components. It is illegal to drive a bus without lights and mirrors. Will this be accepted if the bus is going to be painted?

The intention of the this requirement is to insure that all metal edges are coated and protected from corrosion prior to installation of components. Please resubmit as an Approved Equal with suffucient engineering and technical information to justify the request.

1.6 General Dimensions: Wheelchair Ramp Location (As applicable) - Behind rear axle, curbside

Request clarification as ramps are typically located behind the front axle curbside.

The ramp location shall be at the passenger access door - see section 31.2. The spec language for 1.6 will be updated accordingly.

Maryland Transit Administration Responses to Questions and Clarifications

RFP Number LOT-24-049-GM

Maryland Transit Administration Responses to Questions and Clarifications

RFP Number LOT-24-049-GM

6 1.6 General Dimensions: Wheelchair envelope: 30" x 54" Do all w/c positions in the bus need to be 30" x 54" or if one is this dimension can the other be 30" x 48" if there is not enough room for both?

Please resubmit as an Approved Equal for consideration.

1.7.7 and 1.7.7.3: 12/2 Seating - Seated Passenger Capacity - 14 minimum

Requesting clarification on how many ambulatory passengers you are wanting. Are you wanting foldaway/flip seats to be placed in the w/c positions, so these would make up the 14 passengers?

The seated passenger capacity should be 12. The specification will be corrected for section 1.7.7.3.

5.15 A Fleet Telematics Modem shall be provided on-board for

communication of vehicle data to the end users maintenance system.

Do you have a specific brand you are currently using? There are many vendors for this type of system that may not be compatible with current systems being used.

There is not a specific brand required.

34.5.1 The contractor shall provide and install the most recent model AngelTrax, Apollo or Seon Trooper TL five camera system, or approved equal system, as selected by the end user, that meets the requirements Attachment W.

Can you please provide a copy of Attachment W? I could not seem to locate in the specs.

Attachment 'W' will be provided in this Addendum.

10 1. Page 9 – Section 2.3.12 The section first asks for a 1 year 50,000-mile warranty and then further down it appears to ask for 5 years unlimited warranty.

Please confirm for all bidders the state’s requirement.

As stated in the RFP, this is the base warranty for the vehicle. Specific subsystems and components are warranted and guaranteed to be free from defects and related defects for more than 12 months are given in Table A.

11 1. Page 9 – Section 2.3.13

The warranty requested in this section appears to be beyond the standard warranty for the sub-components. Is it the intention of the state for the bidders to purchase extended warranties for the subcomponents?

The MTA has provided a revised Table 'A' with this addendum. Please submit an Approved Equal for any specific standard warranty requests.

12 Options Would the state be willing to include the Q-One restraint system from Q-straint as an option as this is becoming more and more common.

The MTA will evaluate this request as part of the Approved Equals process.

1.7.10 Type 6A – 212” Wheelbase, Low Floor DRW with 16/2 seating, Battery Electric

We planned to offer the Optimal product for Line item 10, Type 6A, but have a concern. We were just made aware yesterday that the vehicle is weight restricted. For this line item would MTA accept a reduced capacity of 13 passenger and 2 WC?

Please resubmit as an Approved Equal for consideration, including all technical backup with the proposed seating layout and weight calculation -as required in the RFP.

1.7.10 Type 6A – 212” Wheelbase, Low Floor DRW with 16/2 seating, Battery Electric

We represents Vicinity Motor Coach in the greater Mid Atlantic Region. We are asking if you will accept this medium duty offering for Line item 10, Type 6A.

The MTA will NOT accept a Medium Duty bus for this procurement.

Responses to Questions and Clarifications

RFP Number LOT-24-049-GM

15 Section 2.3.3 Approved Equals Process

MDOT spec states “Requests for approved equals shall be submitted in Microsoft Word format. The request for Approved Equal form will be provided electronically by the MTA to all prospective bidders.” Question - will we be allowed to provide an excel spreadsheet for Approved Equals?

The MTA will change the requirement for Approved Equals to be provided in a Microsoft Excel spreadsheet, with backup information in PDF or Word. The spreadsheet will be provided.

16 Section 2.3.9 Delivery/Acceptance on page 7

Adjust the delivery requirement to the following which represents a reasonable time line based on today’s industry conditions:

Delivery: 270 days from receipt of purchase order Type 1A – 138” wheelbase, single rear wheel, gas engine Type 2A – 138” wheelbase, dual rear wheel, gas engine Type 3A – 158” wheelbase, dual rear wheel, gas engine Type 4A – 178” wheelbase, dual rear wheel, gas engine Type 7A – 180” wheelbase, Promaster 3500 low floor, gas engine Delivery: 420 days from receipt of purchase order Type 3B – 158” wheelbase, dual rear wheel, battery electric Type 4B – 178” wheelbase, dual rear wheel, battery electric Type 6A – 212” wheelbase, low floor, battery electric Delivery: 365 days from receipt of purchase order Type 5A – 165”wheelbase, low floor, gas engine Type 5B – 191” wheelbase, low floor, gas engine Type 5C – 210” wheelbase, low floor, gas engine Type 8A – 178” wheelbase Ford Transit Low Floor, gas engine

The MTA will evaluate the delivery requirements as part of the Approved Equals process and will adjust them as deemed necessary.

Section 2.3.14 Pre-Production Meeting - After the contract has been awarded, the MTA shall conduct a Pre-Production Meeting, at the bidder’s location, to determine that the vehicle ordered meets all specifications prior to actual production.

Will MTA be responsible for the travel costs associated for the Pre- Production meeting at the bidder's location?

The MTA is responsible for the travel costs associated for the Pre-Production meeting.

Responses to Questions and Clarifications

RFP Number LOT-24-049-GM

Section 2.3.15 In-Plant Inspections - The MTA shall conduct in-plant inspections , at the vehicle assembly plant, to ensure that each vehicle meets specifications. Any deviations from the specifications shall be corrected by the manufacturer, at the manufacturer’s expense, prior to the vehicle completing the production process.

Will MTA be responsible for the travel costs associated for in-plant inspections?

The MTA is responsible for the travel costs associated for in-plant inspections.

Section 7 RFP Attachments and Appendices - A Proposal submitted by the Offeror must be accompanied by the completed forms and/or affidavits identified as “with Proposal” in the “When to Submit” column in Table 1 below. All forms and affidavits applicable to this RFP, including any applicable instructions and/or terms, are identified in the “Applies” and “Label” columns in Table 1.

Are digital signatures allowed with this RFP?

Digital signatures are allowed except for the performance bond which must have original signatures and seals as noted.

20 Section 3.4 Liquidated Damages on page 17

We respectfully request the addition liquidated damages of of $100 per calendar day after required delivery date be add to the specifications for LOT-24-049-GM Small Buses for LOTS and Mobility.

Having vendors guarantee, with financial penalties, to a definitive delivery date at the time of order is the only method to insure responsible bidding from suppliers. Delivery requirements and liquidated damage similar to what we are proposing have been included in recent MD DOT solicitation.

The MTA will review this request as part of the Approved Equal process.

TABLE A

ITEM YEARS MILEAGE

OEM chassis (as listed below) 3 36,000 Engine assembly - Gas 5 60,000 Transmission 5 60,000 Alternator 3 36,000 Rear axle 5 60,000 Front axle 5 60,000 Frame rails/ cross members and engine/transmission mounts

5 60,000

Cab or body corrosion/perforation 5 100,000 Emissions equipment 5 Unlimited Exhaust System and Diesel Particulate Filter System 5 50,000 Bus body warranty 5 Unlimited Air conditioning/heating system 2 Unlimited Door System 1 Unlimited Electronic Destination Sign System 3 Unlimited Camera System 3 Unlimited Fire Suppression System 2 100,000 Floor, including wheel wells 5 Unlimited Floor Covering 5 Unlimited Wheelchair lift 3 Unlimited

ATTACHMENT W

DIGITAL VIDEO SURVEILLANCE SYSTEM

FOR TRANSIT VEHICLES

1 OVERVIEW OF PROJECT

1.1 SCOPE OF WORK AND SPECIFICATIONS

1.1.1 The system shall be a turn-key system. That is, it shall include all equipment, wiring, cabling and software for the installation of digital recording units, digital video cameras and audio recording devices in the designated vehicles. The system shall further include all fixed-end information system components, including wiring, cabling, hardware, and software, required for the system’s installation and MTA’s retrieval, viewing and permanent storage of recorded images and sound. The system shall also include training, maintenance, troubleshooting and end user support.

1.1.2 MTA anticipates continued growth in the amount and complexity of services it provides.

MTA desires to purchase a system with full featured capabilities that allows for planned additions and future technology.

1.1.3 Digital video recording system (DVRS) shall refer to the system in its entirety. Digital video recording unit (DVR) shall refer to the individual digital recording unit installed in each transit vehicle.

1.2 SAFETY

1.2.1 No item installed in the interior of any vehicle shall increase the risk of injury to occupants during events related to a vehicle collision.

1.2.2 No item installed in the interior of any vehicle shall increase the risk of injury to occupants during events related to a vehicle collision.

1.2.3 Exposed exterior surfaces, corners, fasteners, and controls that could be contacted by a vehicle occupant during a collision shall be of a design that minimizes the potential for injury.

1.2.4 All system controls and components shall be located and designed to minimize driver distraction and shall not interfere with the view of the driver or front seat passengers.

1.2.5 All installed equipment shall be properly fused to minimize shock and fire hazards.

1.2.6 All systems shall be properly grounded.

1.2.7 No parts of the system that can come into contact with a person’s skin shall reach a temperature capable of causing a burn injury.

1.3 QUALITY ASSURANCE PROVISIONS

1.3.1 All materials and equipment installed shall be new, unused, and free of defects and of current manufacture. Prototype or discontinued models are not acceptable. All software shall be the most current, stable version available for the proposed equipment.

1.3.2 The Contractor shall conform to these specifications and shall not omit any unit, component, or both, part or detail necessary to fully implement the DVRS, even though such part(s), detail(s) or function(s) may not be specifically mentioned in these specifications. In absence of a specification, the Contractor shall adhere to its manufacturing standards. In absence of a best practice, the Contractor shall secure the earliest possible written agreement from MTA or MTA’s contractor.

1.3.3 All termination and installation of equipment and software shall be performed by Contractor technicians who have either successfully completed the manufacturer's training course(s) for this type of work or have successfully completed a similar and adequate training program offered by an authorized distributor of the equipment and software.

1.3.4 Care shall be exercised in installing equipment and wiring to avoid damage to both the newly installed and existing wiring and equipment. Connections shall be made with mechanical connectors specifically designed for heavy-duty automotive applications. All wiring and connectors shall be installed in strict adherence to standard communications installation practices and to federal, state or local applicable codes. The Contractor shall be fully responsible for documenting and correcting any defective installation and repairing any damage caused by the installation of wiring and cabling, at no additional cost to MTA.

1.3.5 MTA shall have final approval of the placement and method of installation of all equipment and materials required for the selected DVRS.

1.3.6 Equipment, materials, and installation will adhere to the requirements of the latest revisions of the National Electrical Code (NEC) and Underwriter’s Laboratories Inc. (UL).

The equipment and materials shall be developed in adherence to relevant standards of the Society of Automotive Engineers (SAE) and Electronic Industry Association (EIA). The Quality Management System for the proposed digital video recording system and its component parts shall be ISO9001 certified. In case of conflict between the requirements of the scope and specifications, and those listed documents, the requirements of the listed documents shall prevail.

1.3.7 Copies of certifications shall be supplied with the proposal to show that the proposed equipment has met testing standards for use in on-board vehicle environments. These documents shall include but not be limited to the following:

• Mil-Spec Rated: STD-810G.

• ISO 7637-2 “Electrical Disturbances”, conduction and coupling.

• SAE Rated: J1455 for vibration and shock and include a shock absorbing mounting kit.

1.3.8 The DVR shall be capable of operating in the working environment of a transit vehicle.

This environment includes exposure to climatic conditions such as bad weather, exhaust, detergents, solvents, dust, grit, and sand, as well as rough handling, dropping, constant acceleration and deceleration.

2 GENERAL SYSTEM REQUIREMENTS

2.1 POSITIONING OF CAMERAS AND AUDIO RECEIVERS

2.1.1 Each vehicle will be equipped with up to six (6) video cameras. Four (4) cameras with audio receivers shall be mounted inside the vehicle and two (4) on the outside of the vehicle. The interior cameras shall be positioned such that the interior seating of the bus, the door entrance, front windshield (oncoming traffic), and rear window (toward roadway), is recorded. The exterior cameras must record both sides of the bus.

Proposals shall indicate the number of cameras and the positioning of the cameras for each bus type.

2.2 PLACEMENT OF DVR UNITS

2.2.1 The Location of the DVR should be protected from vandalism. The system shall record onto a removable Solid-State Drive (SSD), or transit rated hard drive designed for mobile applications, equipped with a key lock to prevent tampering and shall be ‘swappable’ for use in any same model DVR.

2.3 MOUNTING OF EQUIPMENT

2.3.1 DVRs, cameras or any other type of equipment that needs to be mounted in the vehicles shall be through mounted with lock nuts to assure that each piece of equipment is properly secured. No sheet metal screws shall be allowed for equipment mounting and installation.

2.4 ON-BOARD ELECTRICAL REQUIREMENTS

2.4.1 Nominal voltage: 12 - 24 volts DC nominal (auto or transit battery).

2.4.2 Operating range: 9VDC – 36 VDC.

2.4.3 Equipment shall be able to withstand sustained voltage levels of up to 48 VDC for up to ten (10) minutes and suffer no damage or data loss in memory.

2.4.4 Equipment shall not suffer corruption of data when power dips below 9VDC. The system will go into standby mode when vehicle voltage drops below an acceptable level.

2.4.5 Equipment shall not be damaged by very high peak voltage (twenty (20) times nominal voltage) of short duration (up to ten (10) milliseconds).

2.4.6 The equipment, including all cables and connectors to and from the recorder, must be electrically protected to withstand low voltage, high voltage and electrical spikes resulting from jump-starting. The equipment shall be capable of “self-reset” in the event of one of these conditions.

2.4.7 The system can be powered on/shutdown in three minutes or less.

2.4.8 The Contractor shall be responsible for any filters, power stabilizers, rectifiers and other devices that protect the DVR from spikes, drops, harmonic resonance and other power issues routinely experienced in a transit environment; and the DVR shall meet the requirements of ISO 7637-2 “Electrical disturbances from conduction and coupling”.

2.4.9 The Contractor shall ensure that the DVR fully performs in the intended operational environments without being affected by, or causing harmful interference to, other on-board systems. Protection shall be provided against radio frequency and electromagnetic interference (RFI/EMI) emission sources, high voltage power lines, traffic signals, neon signs, etc., as well as internal heating/cooling, and conductive or inductive emissions.

2.5 WIRING AND CABLING

2.5.1 All Power wiring must be at a minimum 16 AWG.

2.5.2 All wiring shall be multi-strand, flame retardant and made of flexible material.

2.5.3 All connectors and sockets shall be of positive locking design and shall be equipped with gold contacts. Plug in connectors shall have soldered wiring. Connections shall be made at terminal block ends or be soldered.

2.5.4 No crimp style connectors, Scotch Lok, T-Taps or butt connectors shall be used.

2.5.5 All wire sizes and insulation shall be based on the current carrying capability, voltage drop, mechanical strength, temperature, and flexibility requirements.

2.5.6 Wiring shall be uniformly color coded and tagged.

2.5.7 Wiring shall be prefabricated into standardized harnesses, wrapped, and tied with “all weather UV type” nylon ties.

2.5.8 The power source wires must be 12AWG and appropriately meet the specified requirements for unit start up and normal operation and should prevent unacceptable voltage drops.

2.5.9 All Video and audio cables shall be shielded and gauged to minimize signal loss.

2.5.10 Installed equipment, wiring and cabling shall be firmly held in place. Installed wiring and cabling shall be installed in a manner consistent with other vehicle wiring. Fastenings, supports, and hangers shall be adequate to support their loads and meet transit usage.

2.5.11 A protective plastic or rubber grommet must be installed in every hole that provides passage for conduit or wiring to avoid chaffing or cutting of the conduit or wiring.

2.6 RECORDING DEVICES

2.6.1 On-board Digital Video Recording Unit

2.6.1.1 The DVR shall have a programmable embedded or otherwise non-corruptible operating system. Windows-based operating systems will not be accepted. The programmable parameters shall not be subject to corruption by environmental factors, powering down, power failure, transient power fluctuations, power surges or other irregularities. The parameters shall be capable of being stored for a minimum of five years without power.

2.6.1.2 The DVR shall power-down at a user selectable time after switched power is removed.

The unit shall tolerate having power removed suddenly with no negative effect on the DVR, system hardware, operating system, stored data/video/audio, or on the system’s ability to function normally once power is restored.

2.6.1.3 If the system stops or stalls during startup due to some power irregularity, it shall automatically restart once full power is restored.

2.6.1.4 The DVR shall be designed specifically for use in mobile applications such as transit.

The DVR shall be SAE Rated: J1455 for vibration and shock and include a shock absorbing mounting kit. It shall incorporate internal shock and vibration isolation systems that allow recording while the unit is subjected to the vibration and impacts that occur in a moving transit vehicle.

2.6.1.5 The DVR shall be designed to operate reliably in the environmental situations typical of transit usage. Its ability to accurately record shall not be affected by dirt, moisture, solvents, detergents, oil, and other environmental contaminants. The on-board system shall operate in humidity ranges between 0% and 95%.

2.6.1.6 The DVR shall be designed to store and operate reliably in the face of temperature fluctuations. On-board system equipment shall be storable in temperature ranges between -40° and 160° Fahrenheit and shall include a heater for operating in temperature ranges between -20° and 130° Fahrenheit.

2.6.1.7 The DVR shall capture high quality images and sound in a digital format. The images and sound shall be stored on a high-capacity solid state drive with access to the video onboard using a laptop computer or wirelessly. Proposals shall describe in detail how the proposed system captures and stores images and sound. Proposals shall also explain in detail the benefits and tradeoffs of the proposed format(s) for MTA.

2.6.1.8 Video files shall be recorder in an ‘.avi’ file format to allow recorder video to be viewed without any file conversion or proprietary viewing software.

2.6.1.9 The solid-state disk drive or hard drive shall be removable. It shall be housed in a rugged enclosure that locks to the recording unit. The system shall record onto a removable solid state disk drive equipped with a key lock to prevent tampering and shall be ‘swappable’ for use in any same model DVR.

2.6.1.10 If a new SSD or hard drive is inserted into the DVR, the DVR will connect to the disk, check the formatting, and automatically format the disk if required. No additional user intervention shall be required to begin recording.

2.6.1.11 Each time a new SSD or hard drive is inserted into the DVR, the serial number shall be logged for maintaining chain of custody.

2.6.1.12 A common key shall be used for all the DVRs. The DVR shall be designed to restrict access, prevent alteration of images, and prevent tampering with the unit.

2.6.1.13 The DVR shall provide an external connection to off load data and run set-up diagnostics via a laptop computer. A cable shall be included with each DVR. Any additional pieces or brackets required for connection shall be included in the proposed pricing.

2.6.1.14 The DVR shall continually digitize video from the installed cameras and audio from the installed audio recording device. The DVR shall accommodate, at a minimum, twelve

(12) cameras and eight (8) microphone inputs.

2.6.1.15 As the DVR video file disk drive space is filled, new information shall overwrite old in a linear sequence that shall continue indefinitely.

2.6.1.16 The Digital Video Recorder shall be Mil-Spec Rated: STD-810G and SAE Rated: J1455 for vibration and shock and include a shock absorbing mounting kit.

2.6.2 Video Cameras

2.6.2.1 All cameras shall be High-Definition color capable of recording at 1080P video at 30 frames per second. Under all operating conditions and applications, the camera images shall be of sufficient quality to distinguish facial features, apparel details and activity. Still and video images obtained from the system must be of sufficient quality to support prosecution of offenders and resolution of legal claims.

2.6.2.2 MTA’s vehicles operate from early in the morning until late in the evening on various routes and a range of roads and conditions. The cameras must maximize image quality and be adjustable through the range of lighting conditions including extremely low light and nighttime operation. MTA, therefore, requires that all interior facing cameras be color/infrared and capable of supporting video down to 0.0 Lux. The front-facing/curbside cameras shall be color day/night and capable of supporting down to

0.05 Lux.

2.6.2.3 All cameras shall utilize a progressive scan high resolution CMOS image sensor no less than 1080P.

2.6.2.4 The minimum resolution for interior and exterior cameras shall be 800 TV Lines. The resolution shall be user adjustable to allow higher resolution for selected cameras.

2.6.2.5 The focal length, angle and adjustability of each camera lens shall be selected to maximize viewable area and image quality for each camera. The camera must have automatic exposure, and automatic white balance built in.

2.6.2.6 The Camera housing must be all aluminum construction with a glass or plastic lens.

The Camera must be adjustable after installation for 360° horizontal, 180° vertical, and 360° rotation of ball to allow proper aim adjustment in all mounting positions.

2.6.2.7 The power to the cameras shall be provided through the recorder.

2.6.2.8 The cameras shall be synchronized by the recorder.

2.6.2.9 The DVR unit shall have an internal clock to time and date stamp recorded video.

2.6.2.10 The system shall synchronize each vehicle’s on-board clock with GPS-based time or synchronize each DVR directly. The proposed DVRS must have a means of avoiding time drift. This may be achieved by synchronizing each DVR with the on-board clock or by directly obtaining GPS time. Proposals shall explain how their proposed unit shall accomplish this specification.

2.6.2.11 The DVR unit’s internal clock shall operate independently of the DVR’s and vehicle’s main power supply. Powering down or sudden removal of power shall have no negative effects on the DVR unit’s ability to continue accurate time and date stamping of recorded video.

2.6.2.12 All interior cameras shall feature built-in, automatic IR illuminators for night vision, as well as built-in microphones to capture audio.

2.6.3 Audio Recording Device

2.6.3.1 All interior cameras shall have built-in microphone with noise cancelling technology for audio recording capability. The use of audio in each camera shall be selectable thru software. The audio level shall be adjustable for ideal recording volume.

2.6.3.2 Audio recordings shall be of sufficient quality to identify speakers, provide the content of their speech, and support prosecution of offenders and resolution of legal claims.

The audio level shall be adjustable for ideal recording volume.

2.6.3.3 Audio shall be fully synchronized with video.

2.6.4 Recording Method

2.6.4.1 As pre-allocated video hard drive space is filled, the oldest video stored shall be automatically overwritten so that video is recorded on a continuous basis.

2.6.4.2 Video that has been recorded shall not be lost if the DVR unit must restart or reboot for any reason. The unit shall have the capability to prevent erasures and record-overs of previously recorded information.

2.6.5 Recording Capacity

2.6.5.1 Each of the video channels shall have a user programmable frame rate from four (4) frames per second to 30 frames per second at 1080P HD picture quality.

2.6.5.2 The DVR shall be capable of recording video at a rate of 30 frames per second per camera at 1080P HD picture quality for up to sixteen (16) cameras simultaneously. A minimum 4 TB SSD drive is required.

2.6.5.3 The system must have the capability of recording data from all cameras while they are operating at different frame rates.

2.6.5.4 For MTA’s purposes, the camera capturing passengers boarding through the front door and the camera facing forward through the front windshield shall record at a minimum of 30 frames per second and up to 240 frames per second. The other cameras shall record from 30 to 240 frames per second based on MTA’s needs for each camera.

2.6.5.5 MTA’s goal is to have the DVR store up to 1,700 hours of recorded video and audio per vehicle (based on six (6) cameras and four (4) audio channels, with each camera operating at a minimum of 30 fps.

2.6.5.6 Systems shall have programmable options for the rate at which images are recorded and stored. Proposers shall explain how many different ways their system can trigger and store an enhanced frame rate.

2.6.5.7 The system shall have user selectable video compression levels.

2.6.5.8 The system shall provide smooth playback of video regardless of frame rate.

2.7 On-Board GPS

2.7.1 The System shall include a GPS based mapping utility that is interactive with search capabilities. The search capability must allow for searching by location or speed in a “point and click” manner. The entire route that the vehicle has been traveling shall be viewable and searchable using this feature on playback.

2.7.2 The GPS receiver shall be capable of:

2.7.2.1 Time synchronizing the DVR.

2.7.2.2 Supplying latitude and longitude data for storage on the DVR as metadata

2.7.2.3 Supplying vehicle speed data for storage on the DVR as metadata

2.7.3 The GPS receiver shall be an external all-in-one design with built-in antenna for optimum reception strength. Unites with the GPD receiver built-in to the DVR will not be acceptable.

2.7.4 The GPS receiver shall have the capability to trigger an event by driving beyond a preset GPS coordinate geo-fence or exceeding a preset speed limit.

2.7.5 The DVR shall be able to synchronize the time thru the GPs satellite system.

2.8 On-Board Wireless Capabilities

2.8.1 The system shall include wireless cellular capabilities as well as a built-in WIFI Access Point for setup of the DVR and viewing of cameras. There shall be a built-in WIFI client for transfer of video files and remote viewing thru a connection to an existing network.

2.8.2 The system shall perform wireless download of tagged video clips and/or equipment status information.

2.8.3 Downloading shall require no assistance from operators or other personnel.

2.8.4 Surveillance system back-office equipment shall include the necessary interface to schedule a download and store the downloaded video/audio.

2.8.5 Proposers shall include, as an option all back-office equipment (servers) required to schedule download and store the downloaded video/audio.

2.8.6 System software shall provide archiving options to save specific video clips to long-term storage.

2.8.7 Software shall provide the ability for a user to request a specific video clip based upon a specific vehicle and time frame.

2.8.8 Proposer shall describe any requirements or limitations utilizing any provider for cellular capabilities for the purpose of transmitting video and data for the DVRS.

2.8.9 As an additional option, proposers shall include the option for wireless LAN equipment for downloading video clips automatically once vehicles return to MTA property.

2.8.10 Proposals shall also include at least five (5) references for transit agencies that have been using a wireless download system successfully for at least six (6) months.

2.9 Event Tagging

2.9.1 The DVR system installed in each vehicle shall permit tagging/marking of both the video and the SSD drive for a period of time before and after selected events, from a Contractor-supplied event switch (i.e., a driver panic button). The time parameters shall be user programmable and shall allow marking for up to fifteen (15) minutes before an event and up to thirty (30) minutes after. Event tagging must also be plainly evident on its recorder/storage mode after-the-fact (i.e., as having occurred).

2.9.2 Proposers shall discuss the additional and optional capability of the DVR system installed in each vehicle to perform event tagging automatically (i.e., using certain pre-defined/pre-programmed “trigger” actions) and per the same kind of requirements discussed previously.

2.10 Viewing Method

2.10.1 Recorded video shall be viewed by removing the SSD drive and viewing the contents of the hard drive at a central viewing station. Software and hardware shall be supplied and installed to establish two (2) central viewing stations. Both viewing stations shall be in the end user’s operational and maintenance facility.

2.10.2 Recorded video may also be viewed by connecting a laptop computer directly to the DVR or via a portable hard drive docking unit. The Contractor shall include one (1) docking stations and playback software and hardware shall be supplied and installed to set up one (1) viewing stations.

2.10.3 Recorded video must also be viewed by the system’s main software platform that provides an archive of video all vehicles in the end user fleet.

2.10.4 MTA requires that designated, existing Operations area PC workstations and laptops be used for viewing purposes. If there is a compelling reason why the existing Operations PC workstations or laptops cannot be used, the proposer shall, in their proposal, explain the reasons, delineate the system requirements and provide pricing for permitting each such requirement.

2.10.5 The system shall support simultaneous viewing by multiple users.

2.10.6 Live video shall be viewable remotely using any authorized agency device including a laptop computer. Viewing must be supported on a portable device such as cell phone / tablet style computers. Proposers shall state devices that are compatible with live viewing software.

2.11 Viewing and Administrative Software

2.11.1 The software shall provide the ability to set up multiple user “accounts” and shall provide the ability to configure each user account with specific privileges for the use of the software.

2.11.2 The DVRS software shall have the option to include, at a minimum, date, time, vehicle identification number and camera source on the stored and printed images.

2.11.3 The software shall allow the user to configure download criteria into the supplied software.

2.11.4 The software shall allow analyzing and review of video and audio recordings and allow download of recordings to end user’s designated server.

2.11.5 The proposed viewing system shall equip the central viewing station and laptop computers with the same essential functions for viewing and managing video.

2.11.6 A user shall be able to perform the following functions:

• Search and retrieve video based on a specific date and specific time. The search feature must also be capable of searching the video from the specific day by speed graph and or location on the Google Map interface.

• The Video Clip must include embedded player software.

• The Video Clip shall be Encrypted and Watermarked with a visible symbol that confirms Encryption and Watermarking are intact and no tampering has taken place.

• Playback previously recorded video at user-selectable speed.

• Step forward or back in increments of one frame during playback.

• Skip to the beginning or end of the selected video recording.

• Maximize the size of the selected image to the largest image window.

• Pause the video during playback.

• Display one or multiple video viewing windows. Use all tools for the selected viewing window.

• Zoom in and out on the selected image.

• Sharpen or smooth an image to enhance the image.

• Restore an image back to its pre-enhanced state.

• Change the brightness and contrast of an image.

• Preview an image before printing.

• Save an image in a variety of standard graphic formats.

• Synchronize all recorded audio with the associated video files.

• Save an entire video clip, portion of a clip, or selected image.

• Save a video clip from an existing video clip using the hard drive.

• Be allowed to save recorded images and audio to server, CD, DVD, or any other digital media.

2.11.7 Proposers shall explain how other parties outside of MTA, such as the police, shall be able to view recorded video and audio. If proprietary equipment or software is required for this purpose, the proposer shall fully describe such equipment or software and provide necessary, optional pricing information.

2.11.8 Proposers shall discuss their DVRS’s capability to assemble a “case file” or complete video/audio documentation per MTA input of parameters concerning a specific incident.

2.11.9 Diagnostics of DVR and Other On-Board Equipment

2.11.9.1 The DVR operating system shall include a fleet-wide diagnostic software program that provides information about the operating condition of the DVRs and cameras.

2.11.9.2 Software shall display, in user-friendly format vehicle connection status and system information along with any errors, including the type experienced by DVRs or on-board cameras.

2.11.9.3 Software shall provide the option of downloading a video clip associated with any system error to assist in troubleshooting the cause of the system error / failure.

2.12 System Status Display

2.12.1 The DVR shall perform a self-test upon power-up.

2.12.2 The DVR shall have a system status display visible to the operator. The display shall not obstruct visibility or distract the operator’s attention. It shall provide information about whether the recording system is functional or not. Proposals shall explain how the system status displays operate and describe status display options.

2.12.3 MTA shall have final say as to the location of the display.

2.13 Data Integrity and Authentication of Imagery

2.13.1 Data transferred from a device or system shall be safeguarded so it will not be purged or recorded over until a successful data transfer is confirmed.

2.13.2 Features shall be provided to confirm to system administrators that there have been no losses of data at any point in the system and that there have been no unauthorized changes to, or destruction of, data.

2.13.3 The system shall keep track of user activity and store all user activities in the chain of custody.

2.13.4 Viewing, search and enhancement usage shall not alter the original recorded data.

2.13.5 The DVRS shall include an embedded means to authenticate and validate images, recordings and data integrity so that the recorded audio and video shall be legally defensible in prosecuting offenders and settling legal claims.

2.14 G-Force Sensor

2.14.1 The DVR shall include a built-in 3-axis accelerometer capable of triggering an event when a predetermined g-force is exceeded. The sensor must, at a minimum, tag the SSD drive and stamp the recorded video with correct notification information when acceleration, deceleration and vehicle roll exceed programmed parameters. Proposers shall explain how their G-force sensor operates, how its parameters may be periodically adjusted and how it integrates into their proposed DVR.

2.14.2 The G-Force data shall be stored to the DVRs hard disk and as metadata on downloaded video clips.

3 SYSTEM UPGRADES

3.1.1 The DVRS operating system shall be the current and stable version of the operating system for the equipment and components proposed.

3.1.2 Software shall contain version control numbers, and features shall be included to identify the software version on each device.

3.1.3 The DVRS shall be capable of expansion and/or upgrade as a means of extending the life expectancy of the overall system.

3.1.4 All DVR software and firmware shall be upgradeable without having to remove any DVR unit from its host vehicle.

4 SOFTWARE LICENSES

4.1 The proposer shall fully explain any software licenses required for the purchase and operation of any part of the proposed DVRS. This shall include any per unit costs, the terms and conditions of use, and any upgrade costs. These costs shall be delineated and included in the proposed pricing.

5 MAINTENANCE AGREEMENT

5.1 MTA may be interested in purchasing a maintenance agreement as part of the cost of the proposed system. Proposers shall include pricing options for their maintenance agreement in their price proposal. Proposers shall provide an explanation of the coverage provided by their maintenance agreement, including response time and plan for providing parts and labor. Proposers shall also explain how the agreement provides for software patches and version upgrades during the span of the agreement.

6 ADDITIONAL CONDITION OF CONTRACT

6.1 SYSTEM DOCUMENTATION

6.1.1 The Contractor shall provide documentation as needed and as detailed immediately below for the following functions: overall administration and troubleshooting of the system, software and technical administration, and a user guide from the viewpoint of the user of the proposed system.

6.1.2 The Contractor shall supply four (4) complete sets of systems operations and maintenance manuals for each type or model of equipment purchased. The manuals will cover all hardware and software.

6.1.3 All copies provided shall be in both hard copy and electronic formats.

6.1.4 MTA shall review the documentation, diagrams and manuals for completeness and clarity. If MTA determines additional information is required, the Contractor will supply the requested information to MTA in the format specified by MTA.

7 WARRANTY

7.1 MTA’s intention is to have the Contractor train MTA personnel to be able to perform base-level/rudimentary servicing of the DVRS.

7.2 However, the Contractor will provide, at a minimum, a five (5) -year warranty for the system; (from the date of MTA’s final acceptance of the work initially required for installation of the DVRS). The warranty shall include, at least all equipment, parts and service, as well as all critical software updates and any related hardware updates as necessary for continued proper operation of the system. MTA will be responsible for the removal, out-going freight and re-installation of the equipment.