HomeMy WebLinkAboutRFP - 7381 ADVANCED TRAVELER INFORMATION SYSTEMRFP 7381 Advanced Traveler Information System Page 1 of 143
REQUEST FOR PROPOSAL
7381 ADVANCED TRAVELER INFORMATION SYSTEM (ATIS)
The City of Fort Collins is requesting proposals from qualified firms for the proposed
ATIS project which is a comprehensive Intelligent Transportation System (ITS) solution
consisting of several subprojects with a primary goal to increase ridership. The primary
subproject system is the back office Computer Aided Dispatch (CAD) and Automatic
Vehicle Location (AVL) system.
Written proposals, five (5) copies, will be received at the City of Fort Collins' Purchasing
Division, 215 North Mason St., 2nd floor, Fort Collins, Colorado 80524. Proposals will
be received before 3:00 p.m. (our clock), June 1, 2012 and referenced as
Proposal No. 7381. If delivered, they are to be sent to 215 North Mason Street, 2nd
Floor, Fort Collins, Colorado 80524. If mailed, the address is P.O. Box 580, Fort
Collins, 80522-0580.
A call-in pre-bid conference call will be held on Monday April 30, 2012 at 9:00 a.m. our
clock. Dial in from your phone: (970) 416-2300 – Conference ID: 9398.
The City has an overall DBE goal of 9.9%. There is no specific contract goal for this
project but the City encourages bids from DBE firms in this project.
NOTE: The ATIS procurement and the cost and source of funding is contingent
on the Federal Transit Administration executing the Project Construction Grant
Agreement for the MAX BRT Project.
Questions concerning the scope of the project should be directed to Project Manager,
Dean Erickson at (970) 224-6105 or derickson@fcgov.com.
Questions regarding bid submittal or process should be directed to Ed Bonnette, CPM,
CPPB, Buyer, at (970) 416-2247 or ebonnette@fcgov.com.
A copy of the Proposal may be obtained as follows:
1. Download the Proposal/Bid from the BuySpeed Webpage,
www.fcgov.com/eprocurement
The City of Fort Collins is subject to public information laws, which permit access to
most records and documents. Proprietary information in your response must be clearly
identified and will be protected to the extent legally permissible. Proposals may not be
marked ‘Proprietary’ in their entirety. Information considered proprietary is limited to
material treated as confidential in the normal conduct of business, trade secrets,
Financial Services
Purchasing Division
215 N. Mason St. 2nd Floor
PO Box 580
Fort Collins, CO 80522
970.221.6775
970.221.6707
fcgov.com/purchasing
RFP 7381 Advanced Traveler Information System Page 2 of 143
discount information, and individual product or service pricing. Summary price
information may not be designated as proprietary as such information may be carried
forward into other public documents. All provisions of any contract resulting from this
request for proposal will be public information.
Sales Prohibited/Conflict of Interest: No officer, employee, or member of City Council,
shall have a financial interest in the sale to the City of any real or personal property,
equipment, material, supplies or services where such officer or employee exercises
directly or indirectly any decision-making authority concerning such sale or any
supervisory authority over the services to be rendered. This rule also applies to
subcontracts with the City. Soliciting or accepting any gift, gratuity favor, entertainment,
kickback or any items of monetary value from any person who has or is seeking to do
business with the City of Fort Collins is prohibited.
Collusive or sham proposals: Any proposal deemed to be collusive or a sham proposal
will be rejected and reported to authorities as such. Your authorized signature of this
proposal assures that such proposal is genuine and is not a collusive or sham proposal.
The City of Fort Collins reserves the right to reject any and all proposals and to waive
any irregularities or informalities.
Sincerely,
James B. O'Neill II, CPPO, FNIGP
Director of Purchasing & Risk Management
RFP 7381 Advanced Traveler Information System Page 3 of 143
RFP 7381
Advanced Traveler Information System
(ATIS)
Table of Contents
1.0 DEFINITIONS
2.0 SCOPE
2.1 Project Background
2.2 ATIS Goals
2.3 System Operators and Users
2.3.1 Fixed Route Operations
2.3.2 Fleet Services
2.3.3 Transfort Dispatch/Scheduling
2.3.4 Information Technology
2.3.5 Marketing and Advertising
2.4 ATIS Project Scope
2.5 ATIS System Procurement
2.5.1 Standards
2.6 Contract Deliverables Requirements List
3.0 ATIS COMPONENTS
3.1 Computer Aided Dispatch (CAD)
3.1.1 Automatic Vehicle Location (AVL)
3.1.1.1 Real-time Prediction Accuracy
3.1.1.2 AVL Data Accuracy and System Reliability
3.1.2 Dispatch Workstations
3.1.2.1 User Interface Configuration
3.1.3 Schedule Adherence
3.1.4 Route Adherence
3.1.5 ATIS System Time
3.1.6 Data Messaging
3.1.7 Textual and Tabular Displays
3.1.8 Map Display
3.1.9 Emergency Alarm
3.1.10 Historical Data (Playback Mode)
3.1.11 Scenarios
3.2 Google Transit Feed Specification (GTFS)
3.3 AVL Data Export
3.4 Trapeze Software Interface
4.0 VEHICLE SYSTEMS
4.1 On-Board Computer System (OCS)
4.1.1 Data Transfer
4.2 Mobile Data Terminal
4.2.1 Text Messaging
4.2.2 Transfer Requests
4.3 Automatic Passenger Counter (APC)
RFP 7381 Advanced Traveler Information System Page 4 of 143
4.4 Automatic Announcements (AA)
4.4.1 In Vehicle System
4.4.2 Transit Centers
4.4.3 Platforms and Stops
5.0 PASSENGER INFORMATION SYSTEMS
5.1 Interactive Voice Response (IVR)
5.2 Information Displays and Paging Systems.
5.3 Internet Information (Web Site)
5.4 Mobile Device Applications and Web Site
5.5 Mobile SMS/Email
6.0 ATIS TECHNICAL INFORMATION
6.1 Data information and Ownership
6.2 Data Analysis and Report Generation
6.3 Database Information
6.4 Technical Overview
6.5 Data Communications
6.6 Operating Environment
6.7 Software
6.7.1 Software Requirements
6.7.2 Definitions
6.7.3 Licensing Model
6.8 Protocols
6.9 Anti-Virus
6.10 Security
6.11 Upgrade Tools
6.12 Maintenance and Support
7.0 PROJECT MANAGEMENT
7.1 Contract Management
7.2 Project Management Plan
7.2.1 Progress Reviews, Schedules and Project Control
7.2.2 Weekly Conference Calls
7.2.3 Monthly Progress Status Updates
7.3 Initial Activities Meeting
7.4 Design and Configuration Control
7.4.1 Design Principles and Reviews
7.4.2 Preliminary Design Review
7.4.3 Final Design Review
8.0 TRAINING
8.1 Transfort - Furnished Training Related Items
8.2 Use of Actual Equipment as Training Aids
8.3 Training Program Plan
8.3.1 Description
8.3.2 Training Delivery Schedule
8.3.3 Contractor’s Training Experience
RFP 7381 Advanced Traveler Information System Page 5 of 143
8.3.4 Training Courses
8.3.5 Train-the-Trainers
8.3.6 Training Materials
8.4 Vehicle Equipment Training and Maintenance Module
9.0 SAFETY REQUIREMENTS
10.0 SUBMITTAL REQUIREMENTS
TABLE LISTING
Table 1 ATIS Software, Project Management and Support Costs
Table 2 In Vehicle Systems
Table 3 MAX BRT Platforms / Stops
Table 4 Transit Centers
Table 5 Training and Implementation
Table 6 Submittal Checklist
Table 7 Transit Vehicles
Table 8 Supervisor and Maintenance Vehicles
RFP 7381 Advanced Traveler Information System Page 6 of 143
1.0 DEFINITIONS
Acceptance Testing: A formal process of proving to Transfort that all Work, or a
specified portion thereof, under Contract has been completed to the specification
requirements and submitted to Transfort for approval.
Acceptance: Written documentation attesting to the act of an authorized
representative of Transfort, by which all Work or specified portion thereof, under the
Contract has been identified as complete to the specification requirements.
Alarm: An audible and/or visual indication of a faulty condition.
Approved/Approval: Written approval by the Project Manager unless contract
document specifically states otherwise.
Assembly: A combination of subassemblies or components that form a subset of
equipment.
Audit: An examination of records or accounts to verify accuracy and status.
Authentication: A technique to confirm the identity of a computer system.
Baseline Design: The design of the Advanced Traveler Information System or any of
its assemblies, components, devices, systems, subsystems, or materials that has
received both drawing approval and First Article approval by Transfort. All design
modifications made past the establishment of the design baseline shall be considered
design changes.
Contractor(s) Drawings: Items such as detail drawings, graphs, diagrams, and
sketches which are prepared by the Contractor to detail its work.
Contractor Quality Assurance/Quality Control: The quality assurance and control
program established and maintained by the Contractor that ensures compliance with the
Contract requirements.
Calculation: Numerical computations based on actual field conditions performed to
demonstrate compliance with the Technical Specification.
Contract Deliverables Requirements List (CDRL): List of all Contract Deliverables.
Certified Inspection Reports: Reports signed by the Contractor inspector(s) attesting
that items inspected meet the specification requirements other than any exceptions
included in the report. The Contractor shall also have inspection reports that are
certified as true by the Contractor Project Manager.
RFP 7381 Advanced Traveler Information System Page 7 of 143
Certified Test Reports: Reports of test signed by a qualified professional or Transfort
employee attesting that tests were performed in accordance with the test method
specified. The test results reported are accurate, and that items tested meet or fail to
meet the stated minimum requirements.
Comment: Written critiques of the Contractor’s submittals to Transfort.
Commercially Available: All Contractor supplied equipment, subsystems, assemblies
and/or components that do not require any modifications to meet the functional and
performance requirements of this Contract and that are available from more than two
sources.
Component: A piece or part of an Assembly such as a mechanical part, electrical part,
or support structure that is combined with other components to form an Assembly.
Contracting Administrator: An official of Transfort authorized and empowered to
execute contracts, modifications, and agreements on behalf of Transfort.
Days Working: Those calendar days during which regular business is conducted,
excluding Saturdays and Sundays and all Authority-observed federal, state, and
municipal holidays.
Design baseline: See Baseline Design.
Equal: Whenever the words “equal” or “approved equal” are used in connection with
make or quality of material or equipment in these Contract Documents, the Contracting
Officer’s decision as to whether any material or equipment proposed is equal to that
specified shall be binding and final on both the Contractor and Transfort.
Equipment: All equipment required to be furnished by the Contractor under the
Contract, including, but not limited to vehicle logic units, mobile display terminals,
mobile radios, radio consoles, base stations, displays, display controllers, the
management hardware and software, and all related and appurtenant items.
Failure: The inability of a component, assembly or a piece of equipment to function as
designed and/or specified.
Failure Rate: The frequency of failure, expressed as failures per unit of time (in hours).
First Article: The first one of any production component of the Advanced Traveler
Information System equipment that is produced. The Technical Specification provides
that production components not be manufactured prior to drawing approval, so the First
Article shall have been made to approve drawings.
First Article Testing: The process of testing under the supervision of Transfort or
Transfort’s representative an initial part, assembly, subassembly, subsystem, system or
RFP 7381 Advanced Traveler Information System Page 8 of 143
material, manufactured or assembled by either the Contractor or sub contractors. The
first article inspection shall be completed prior to the first article testing.
Indicated: As used in the Technical Specification, “Indicated” shall be understood to
mean “as shown in the Technical Specification Drawings,” or “as described in the
Technical Specification.”
Inspection: Examining, analyzing, or sampling products or workmanship, including
appropriate raw materials, components, and subassemblies, to determine conformance
to stated requirements.
Installation Inspection and Testing: Inspection that takes place after all installation
activities are complete. Installation test is the process of confirming that the equipment
functions at the same level as prior to shipping.
Maintainability: The ability of the Automatic Vehicle Location and Real-time
Information Equipment to be maintained by maintenance staff, including equipment and
components that require maintenance.
Module and/or Modular: A standardized, interchangeable, self-contained unit(s),
designed to facilitate maintenance, repair(s), and extensions.
Off-line: Not connected to a telephone or other communications network.
On-line: Connected to a telephone or other communications network.
Product Data: Illustrations, standard schedules, performance charts, instructions,
brochures, diagrams, instructions, warnings, and other information furnished by the
Contractor to illustrate or explain the fabrication, assembly, installation, maintenance, or
operation of materials, equipment, or some portion of the work.
Production baseline: The design and fabrication specifications of the Advanced
Traveler Information System equipment or any of its components, subassemblies or
materials of which the First Article Testing has been approved by Transfort. Any
modifications made to production units after the production baseline has been
established will be considered a design/construction change.
Production Inspection and Testing: The Inspection activities that occur during the
production process of the Advanced Traveler Information System equipment and testing
activities that occur prior to shipment of the equipment to Transfort’s work site.
Proof (used as suffix): Apparatus is designated as dustproof, waterproof, etc., when
so constructed, protected, or treated that its successful operation is not interfered with
when subjected to the specified material or condition.
RFP 7381 Advanced Traveler Information System Page 9 of 143
Quality Assurance Audit: Audit performed by Transfort or its representative to ensure
the elements of the Contractor’s Quality Assurance plan are being followed.
Quality Control Inspection and Tests: Inspections and tests performed for the
purpose of monitoring the quality of products and performance of the Contractor.
Reliability: The probability of performing a specified function without failure and within
design parameters for the period of time under actual service conditions.
Service Proven: Identical or near identical equipment which has demonstrated
successful operation in a transit industry environment similar to that anticipated for
Transfort.
Shop Drawings: Drawings or sketches prepared by the Contractor for use in its
manufacturing facility, assembly facility, or shop to fabricate, assemble, and/or install
parts of the Advanced Traveler Information System equipment, whether manufactured
from raw materials or purchased from others in a ready-to-use condition.
Specialized shop-level test equipment: Diagnostic and test equipment furnished by
the Contractor for the purpose of testing, troubleshooting, and calibrating electrical,
mechanical, and electromechanical components of Advanced Traveler Information
System in a shop environment. Such equipment is not intended for use in the field.
State: The State of Colorado.
Subassembly/Subsystem: Two or more components combined into a unit for
convenience in assembling or servicing equipment. A subsystem comprises functional
elements interconnected within a system to perform a specific function, such as a
display, display controller, or control system.
System: When used alone, all Advanced Traveler Information System equipment, data
processing system, and computer equipment to be procured under this Contract.
Tamperproof: Items are designated as tamperproof when they cannot be easily
loosened, opened, or penetrated by hand or with commonly available tools such as a
flat blade or Phillips screwdriver or pliers.
Tight (used as suffix): Apparatus or enclosures are designated as watertight, dust-
tight, etc., when so constructed that the enclosing case will exclude the specified
material and is manufactured and rated according to an industry standard such as
NEMA.
Time-out: When a prescribed amount of time has elapsed during which a specified
action has not occurred.
RFP 7381 Advanced Traveler Information System Page 10 of 143
Upgrades: Performance improvements or enhancements to hardware, software, or
firmware. Upgrades include both hardware and software, as long as fit, form, and
function can be complied with. Upgrades that require design changes necessitate a
change order.
Work Site: The area identified as Transfort Right of Way necessary for the installation
of the equipment being provided under the contract.
2.0 SCOPE
This section outlines System Goals and Objectives and the minimum functional
requirements that shall be obligated and deliverable by the successful Contractor of this
RFP. Please fill out all requested information and explanations in the scope of work and
appendices.
2.1 Project Background
The City of Fort Collins initiated the fixed route Transfort bus system in July of 1974.
Service began with 4 buses on 3 routes. Service was provided mainly in the downtown
area.
Today the Transfort bus system is comprised of 35 buses and 19 routes which provide
service throughout the city limits and areas of Larimer and Boulder Counties. A regional
route called Flex serves as a connection to surrounding communities.
In 2011, Transfort had an average ridership of 7,000 each service day with an annual
total of 2,156,775 passenger trips. In 2011, Transfort provided 995,858 revenue miles
and 77,356 revenue hours. Transfort hours of revenue operation varies by route, but
generally run Monday through Saturday from 6:30 a.m. to 6:30 p.m.
Transfort currently has over 460 bus stops and 2 transit centers. Construction is
expected to be complete on a 3rd transit center in the fall of 2013. Transfort employs 68
fixed route bus operators and 25 administrative staff.
The MAX Bus Rapid Transit service which is projected to begin in spring of 2014 will
have 20 platforms or stops. Construction is slated to start summer of 2012.
Publicly available transit information is contained in mostly traditional static displays,
represented by brochures, wall maps, vehicle maps, and web sites. These traditional
methods of communicating to riders and potential riders have been available and in use
for some time. These traditional communication methods are difficult for new riders and
are seldom referenced by regular riders. The ATIS project will fundamentally change
the interaction and availability of information about the bus routes and where the buses
are in near real-time.
The proposed ATIS project is a comprehensive Intelligent Transportation System (ITS)
solution which consists of several subprojects with a primary goal to increase ridership.
RFP 7381 Advanced Traveler Information System Page 11 of 143
Each of the subprojects complements each other to combine for a substantial impact for
the Transfort rider. Communication infrastructure systems are already in place and will
be leveraged to provide near real-time bus arrival information to the general public. The
primary subproject system is the back office Computer Aided Dispatch (CAD) and
Automatic Vehicle Location (AVL) system. The data provided by the on-board systems
will be used by a central database system and transferred to various application
systems. The projects and there order of implementation coincides with both technical
logic as well as a management derived priority list.
NOTE: The ATIS procurement and the cost and source of funding is contingent
on the Federal Transit Administration executing the Project Construction Grant
Agreement for the MAX BRT Project.
2.2 ATIS Goals
Transfort seeks a system that automates data entry and business processes to the
maximum extent possible with minimal customization. The Contractor shall supply,
license, install, integrate and implement ATIS equipment on all Transfort fixed route
vehicles to provide continuous real-time data of the location for buses.
Promote rider safety and system security: The new system should increase rider
safety by providing reliable data communications throughout the Transfort
service area. ATIS should be designed to be both physically and electronically
secure.
Facilitate prompt customer communication: There is a need to improve customer
information systems to provide quicker response to real‐time information needs
and share data updates with Transfort’s customers.
Provide improved customer information: The new system needs to provide a
broad range of multimedia capabilities to create attention‐getting displays that
increase the variety of customer information without distracting from the
important messages that need to be conveyed in a timely manner.
ATIS will include a Mobile Data Terminal (MDT) installed on each vehicle to
serve as the interface between the vehicle operator and the dispatch center and
between the vehicle operator and other integrated onboard systems.
The proposed system will include all hardware, software, and services necessary
to accomplish the supply, installation, integration, documentation, testing,
training, and startup of the complete system.
Promote open design for information provided by external systems: ATIS must
integrate data and communication systems including Trapeze FX, Trapeze OPS,
and In Motion Technologies Onboard Mobile Gateways to provide accurate and
timely reporting of scheduling and system performance.
RFP 7381 Advanced Traveler Information System Page 12 of 143
Enable centralized control: ATIS needs centralized monitoring, control, error
status reporting, and the data repository to assist operations staff and system
administrators in managing ATIS.
Design of ATIS will be based upon user definable parameters wherever possible.
These parameter values shall be used by all applications throughout ATIS. Types
of configuration parameters shall include vehicles, operators, fleets, divisions,
data messaging, communication settings, system settings and operational
thresholds
The transit component of ATIS will be capable of integrating with Automated
Passenger Counter (APC), Automatic Announcement (AA), and other ITS
components. Transit operations reporting will be integrated within ATIS. The
traveler information component of ATIS will be capable of integrating with the
City web site using accepted internet communications and development
standards and protocols.
The priority for this procurement is to acquire a real-time information system with
a reliable basic CAD and provide the foundation for future smart bus systems as
noted above. Optional subsystems are also detailed within this specification.
The ATIS project will provide a distributed architecture design with centralized
control for all vehicle equipment, dispatch stations, display signs and web
applications. The architecture will rely on Transfort’s data network to connect a
centralized data store with real‐time information software for displays at remote
locations and displayed on the Transfort website.
ATIS will be designed to interface with existing and future onboard systems using
commonly accepted interface and communications industry standards.
ATIS will be designed to interface with existing and future back office systems
using commonly accepted industry communications protocols, programming, and
data access standards.
ATIS will be scalable and easily expandable to other transit stations, transit
stops, and municipal locations for an equitable distribution of customer and
employee information resources.
ATIS will have the ability to override digital sign information and will support the
remote stop and starting of displays and controllers.
ATIS will support real‐time monitoring of system servers, displays, and display
controllers for diagnostic maintenance purposes.
ATIS administrators will have the capability to either remotely, or at a central
server, monitor or integrate all components of the ATIS system. The ATIS system
RFP 7381 Advanced Traveler Information System Page 13 of 143
will provide automated notification of any equipment malfunctions, failures, or
abnormal conditions.
2.3 System Operators and Users
The Transfort organizations are committed to supporting real time information delivery
to the public in order to improve operational efficiency, support customer information
needs, and capture information that will lead to improving the Transfort transit system.
ATIS will touch several departments within the City and groups within Transfort. The
following department and group descriptions describe their relationship to ATIS.
2.3.1 Fixed Route Operations
This internal group is responsible for the delivery of fixed route services by the bus
operators as scheduled or dictated by field conditions, or as directed by dispatchers and
supervisors. This department is responsible for providing street supervision,
dispatching, incident management, making vehicle assignments, and bus operator
management in support of Transfort performance goals.
2.3.2 Fleet Services
This City department is responsible for the transit maintenance functions, and is
responsible for maintaining buses, demand response vehicles, and support vehicles to
meet the delivery of daily vehicle requirements. Fleet Services also troubleshoots and
maintains several ITS components within the Transit fleet such as Mobile Data
Computers, Fareboxes and Mobile Video Systems.
2.3.3 Transfort Dispatch/Scheduling
This internal group is responsible for creating and maintaining Transfort fixed route
services in the Trapeze FX and Blockbuster software applications. This includes bus
stop administration, trip building, blocking and building bus operator rosters.
2.3.4 Information Technology
This City department sets the agency information and transportation technology
standards and policies. It oversees the development and implementation of new
systems that are used to run the Transfort's business applications including the Trapeze
scheduling and operations systems, and all data network infrastructure. This
department also manages all of the day‐to‐day information system related functions.
2.3.5 Marketing and Advertising
This group is responsible for managing the printed materials related to Transfort
services, content management of the Transfort web site, managing Transfort advertising
programs, and coordinating marketing campaigns.
2.4 ATIS Project Scope
Transfort seeks an Advanced Traveler Information System to improve planning,
operations and customer service of Transfort services. ATIS will improve traveler
satisfaction by providing real‐time information onboard, at bus stops and transit facilities,
RFP 7381 Advanced Traveler Information System Page 14 of 143
and through internet technologies. The fully integrated ATIS solution will be capable of
supporting real‐time information delivery for Transfort customers. The solution provided
will be an event driven system integrated with existing Transfort software. CAD
functions shall be integrated that prioritize, display, and archive the real‐time vehicle
events. As part of this contract the Contractor will install software and hardware in
multiple locations, including in desktop computers, in virtual servers, in vehicles and in
transit centers. Integration with existing variable message signs and paging systems at
platforms and stops along the Bus Rapid Transit system under construction will be
required. The map shown below in Figure 1 shows the approximate location of the
transit facilities and the BRT stations and stops to be serviced by the ATIS System.
.
Figure 1 Transfort Transit Facilities
RFP 7381 Advanced Traveler Information System Page 15 of 143
2.5 ATIS System Procurement
ATIS technologies to be procured through this solicitation include automatic
announcement (AA), automated passenger counters (APC), automatic vehicle location
(AVL), computer-aided dispatch (CAD); Interactive Voice Response (IVR), integration of
real time arrival information with passenger information displays and internet
technologies.
Transfort seeks a system that automates data entry and business processes to the
maximum extent possible. The Contractor shall supply, license, install, integrate and
implement ATIS equipment on all Transfort buses, supervisor and maintenance vehicles
to provide continuous real time data of the location for buses, supervisor and
maintenance vehicles. The system shall include a Mobile Data Terminal installed on
each vehicle to serve as the interface between the vehicle operator and the dispatch
center and between the vehicle operator and other integrated onboard systems.
The intention of this request for proposal and its scope of work layout are to give
each proposal a fair and equitable review and comparison. There are extensive
responses and cost breakdowns requested.
The costs summary sheet in Appendix A to be filled in is a critical piece of the
proposal. Please complete to the best of your ability to ensure full consideration
of your proposed system. The ongoing support costs are considered critical to the
selection process.
The proposed system summary in Appendix B is provided as an aide to ensure you
have completed all of the areas requiring a response. A complete proposed system
summary will be considered critical to the selection process.
Proposers shall describe the appropriate system architecture for the ATIS system. This
architecture shall represent a fully integrated collection of distinct systems, subsystems,
and components linked by standard, non-proprietary, or third party supported data
communications protocols. Provide diagrams as necessary to convey your proposed
solution. A detailed technical response is requested in section 6.4.
2.5.1 Standards
Current and future deployments of ATIS technologies require that the system
components be capable of interfacing with on-board technologies via a Vehicle Area
Network. The Contractor shall utilize the following standards for the Vehicle Area
Network: SAE J1708/J1587 or SAE J1939 Standards. The Contractor shall prove that
the Transfort project is compatible with these standards. To the best degree possible,
the system(s) delivered as part of this project must be in compliance with nationally
relevant standards such as the National Transportation Communications for ITS
Protocol (NTCIP) and the Transit Communications Interface Profiles (TCIP). The
proposed system must also conform to the Colorado Department of Transportation
Information Required
RFP 7381 Advanced Traveler Information System Page 16 of 143
Region 4 ITS Plan. All equipment will meet all Local, State, and Federal regulations for
safety and environmental control.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
2.6 Contract Deliverables Requirements List
The Contract Deliverables Requirements List describes contract deliverables. The
deliverables will need to meet the criteria set forth under each section and will need to
meet the schedule and milestones as outlined in the agreed upon CDRL 701, “Project
Management Plan”.
Contract
Deliverables
Requirements
List
CDRL Description
601 Technical Overview
602
Software Design and
Documentation
603 Commercial Software List
701 Project Management Plan
702 Project Schedule
703 Monthly Progress Reports
704
Preliminary Design Review
Package
705 Final Design Review Package
807 Training Program Plan
808 Training Materials
Information Required
3.0 ATIS COMPONENTS
This section details the individual ATIS components starting with the CAD system with
its many unique characteristics. This is followed by the AVL technology requirements
and then the Dispatch application parameters. The external interfaces including GTFS,
AVL data, and Trapeze Software follow the desktop applications. The next areas are
the vehicle systems consisting of hardware and software to be installed on the transit
and support vehicles.
3.1 Computer Aided Dispatch (CAD)
CAD technology is the foundation for accurate bus arrival information to be displayed.
The CAD software shall include all necessary tools to enhance the dispatchers’ ability to
RFP 7381 Advanced Traveler Information System Page 17 of 143
monitor and manage the transit fleet. The software shall utilize a user-friendly graphical
interface that includes mapping capabilities and displaying of messages, events, and
alarms as well as other functionality needed for the efficient management of the fleet.
CAD will provide data for the downstream data systems such as Automatic
Announcements, Interactive Voice Response, Message Notification systems and Mobile
Applications. The software shall be capable of displaying the AVL software in tabular
format. At a minimum, the tabular display shall provide the capability to display
windows that contain the following information:
1. Vehicle, Run, Route, Block and Operator information synchronized with data
generated from Transfort Trapeze modules
2. Vehicles / Operators currently logged into the system
3. Vehicles not logged into The ATIS System
4. Vehicles that have not logged a successful wheelchair lift/ramp cycle
5. Early, On Time and Late vehicles with different colors
6. Off route vehicles
7. Characteristics of vehicles that have actuated a silent alarm condition.
8. Passenger Count Information
9. Transfer protection requests between vehicles
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.1 Automatic Vehicle Location (AVL)
The Automatic Vehicle Location (AVL) subsystem shall provide location using an
onboard Global Positioning Satellite (GPS) receiver as required reaching location
accuracy within ten (10) meters location of actual vehicle location to support ATIS
throughout the Transfort service area. Vehicle location shall be determined by a
navigation algorithm that collects inputs from multiple sources and calculates a solution
based on the reported reliability and weighting of each input device. The location
determination device(s) shall automatically calibrate and require no operator or
maintenance personnel intervention for daily usage.
The GPS system shall have a cold acquisition time of no more than two (2) minutes,
warm acquisition time of no more than fifteen (15) seconds and update the current
position at least every five (5) seconds. The GPS system shall include multi-path
rejection capabilities to help eliminate inaccurate signals caused by reflections off of
buildings or other structures. Vehicle location shall be transmitted at least twice every
one (1) minute to ATIS for display and storage purposes and every fifteen (15) seconds
during an Emergency Alarm.
GPS delay time from location acquisition to formatting for transmission shall not exceed
one (1) second. The GPS system shall store the most recent location to provide as the
“last known good” location in the event that location reporting is interrupted. Location
messages transmitted to dispatch shall indicate messages status as current or “last
known good”.
RFP 7381 Advanced Traveler Information System Page 18 of 143
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.1.1 Real-time Prediction Accuracy
Transfort considers ATIS accuracy to be of the utmost importance. As such, accuracy
and repeatability of results shall play a prominent part in system testing. The Contractor
shall confirm accuracy requirements are met during Functional System Testing.
Transfort’s "real-time" arrival prediction accuracy goals are as follows:
85% of all predictions within 60 seconds of predicted arrival time
95% of all predictions within 90 seconds of predicted arrival time
99% of all predictions within 120 seconds of predicted arrival time
The Contractor shall clearly state in their response to this RFP their ability to meet
specified “real-time” arrival prediction goals and/or actual location and schedule
accuracy and precision that the RTIS will provide.
When real-time information is unavailable to serve a customer request for information
due to a communications failure ATIS shall revert to providing schedule information
clearly identified as schedule information until such time that the communications with
the vehicle(s) is reestablished. A failure to receive vehicle update messages for five
polling cycles shall constitute a communications failure.
Accuracy shall remain consistent during changing conditions such as morning and
afternoon pull-out, transition to off-peak operation, etc.
The system shall indicate the vehicle is “Arriving” (or other equivalent message) to
arrive if the real-time arrival prediction is one (1) minute or less.
The system shall process last minute corrections (“clear-down”) to electronic message
signs to reflect reality, e.g. the bus is due, has arrived, or has just departed. In no case
shall the system indicate that the bus is due to arrive as it is departing the stop. Clear-
down would take precedence over predicted arrival and departure times.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.1.2 AVL Data Accuracy and System Reliability
Data accuracy and reliability shall fall within the following ranges:
Overall reliability of AVL hardware and software (excluding on-board vehicle
hardware) system is expected to be 98% or better (System and all components
are fully functional at least 98% of the time);
Overall reliability of AVL on-board bus hardware is expected to be 95% reliable,
(based on a peak pull-out of 30 buses, we expect no more than 1 bus would
have non-functioning AVL hardware);
RFP 7381 Advanced Traveler Information System Page 19 of 143
Vehicle location information is expected to be 98% accurate based on a GPS
accuracy of +/- 30 feet or less;
Schedule Adherence information is expected to be 95% reliable based on a +/- of
two (2) minutes;
Real-time information system is expected to be 95% reliable based on a +/- of
two and a half (2.5) minutes;
Any hardware component with a failure rate in excess of 10% or greater during
the first twelve (12) months of the original warranty will be considered as a 100%
failure.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.2 Dispatch Workstations
A dispatch workstation will be the central organizing area for daily operations. The
dispatcher workstation will use four 22” LCD screens for display purposes. Dispatchers
monitor vehicle communications and initiate actions according to the real-time
information provided by these displays. Transfort will provide dispatch workstations that
meet the software minimum specs as requested in Section 6.4 Technical Overiview.
3.1.2.1 User Interface Configuration
The map, textual, and tabular displays shall be designed such that functionality based
upon access rights and permissions are either hidden or clearly identifiable as not
accessible. The map, textual, and tabular displays shall be designed such that
unavailable functionality based upon access rights and permissions does not impede
ease of navigation within and between applications.
The system administrator shall have the ability to configure profiles to be used for
different classes of users through defined groups. The profiles shall permit the
administrator to define access rights to applications as well as functions within
applications. The system administrator shall be able to set permissions including any
combination of read, write, change, and delete to applications and functions within
applications.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.3 Schedule Adherence
ATIS shall monitor Schedule Adherence by comparing real schedule versus the
published schedule for all vehicles logged on. Schedule adherence data shall be stored
and include parameters for analysis such as, but not limited to, vehicles, routes, time
points, block/runs, and Operator ID. Both the time of arrival and departure at all
scheduled time points shall be accurately recorded and stored. It shall be noted that
Transfort maintains multiple schedules for Weekday, Saturday, Sunday and maintains
different schedules for schooldays, early out’s etc.
RFP 7381 Advanced Traveler Information System Page 20 of 143
Based on AVL and the stored run and/or block logon, the on-board system shall
constantly calculate the schedule adherence and present it to the vehicle operator.
Schedule adherence shall be reported to ATIS via the cellular data network with every
location update. Adherence tracking shall support multiple patterns per route and
accurately report adherence for route and blocking techniques including route
interlining, mid-trip and end-of-line layovers, revenue deadheads, and non-revenue
deadheads.
Transfort shall be responsible for providing the schedule data from the Trapeze FX and
Trapeze Blockbuster software for use by ATIS. The Contractor shall perform any stop
and route geo-surveys required using Contractor supplied tools and include a
designated Transfort employee in the process. The Contractor shall provide adequate
training prior to the start of this activity in accordance with the project schedule for the
Transfort designated employee. The Contractor supplied tools for route/schedule
maintenance shall be delivered to Transfort as a part of this process.
Provide information concerning the geo-survey tools in the space provided below.
Real-time (predictive to the next time point) schedule adherence shall be displayed for
dispatchers and made available to the real-time customer information applications. In
real-time, ATIS shall be capable of identifying vehicles that are predicted to be running
early by more than a predefined number of minutes or late by more than a predefined
number of minutes at the next scheduled time point on both graphical and tabular
displays. Schedule adherence parameters shall be able to be set differently by route
with separate early and late user supplied values.
The onboard MDT display shall be configurable to either inhibit display or display the
predicted status relative to schedule shown in one minute increments. If the MDT
display is configured in the display mode the schedule adherence display will be shown
to the Operator regardless of dispatcher selectable parameters. Schedule adherence
from the vehicle shall be calculated, transmitted, and stored regardless of the onboard
display setting.
ATIS shall support multiple service types such as school in, school out, early school
dismissal, Weekday, Saturday, Sunday, and holiday to accommodate service variations
at the route and trip level. Each schedule day shall permit assignment of multiple
service types.
Schedule deviations for bus arrivals and departures at time points shall be recorded at
the time when it occurs and independent of the poll rate. Information shall include:
1. Vehicle number
2. Operator number
3. Route number
4. Block number
RFP 7381 Advanced Traveler Information System Page 21 of 143
5. Run number
6. Direction
7. Geographic location
8. Date and time
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.4 Route Adherence
The onboard ATIS solutions shall provide off-route status to the Operator and transmit a
notification to be displayed at the dispatch workstation. The off-route notification shall
identify and display the name of the next stop when a vehicle is further than a pre-
defined distance from the assigned route. The off-route distance value shall be a user
definable parameter. The Contractor shall identify whether the off-route distance is the
total distance traveled from the assigned route or a deviation from the corridor of travel.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.5 ATIS System Time
The ATIS system time shall be based on GPS time. The ATIS system shall display
Mountain Time and provide automatic correction for daylight savings time. If a vehicle’s
GPS is not operating ATIS shall provide GPS time updates. GPS time shall be
accessible for use throughout Transfort’s data network. Time on all ATIS components
shall never be more than five (5) seconds different from GPS time. The MDT shall
display time consistent with all other ATIS components throughout the Transfort data
network in a user specified format derived from the GPS sub-system.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.6 Data Messaging
ATIS shall enable dispatchers to transmit text messages to an individual vehicle, a
group of vehicles, a specific route, fleet, or all vehicles, an operator name, or operator
ID. Text messages shall either be keyed in as free-form text or selected from a pre-
defined text message list (canned). Text length shall support at least 256 characters.
Pre-defined text messages shall be user definable.
The dispatcher shall have the option to require an operator acknowledgement or
response upon viewing the text message and shall be able to monitor the status of text
message acknowledgements or responses. ATIS shall enable dispatchers to send any
Information Required
RFP 7381 Advanced Traveler Information System Page 22 of 143
text messages designated as store-and-forward. Store-and-forward message duration
shall be defined by a user defined time period.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.7 Textual and Tabular Displays
Configurable multiple message queues for Data Messages, Schedule/Headway
Adherence, Request to Talk, Emergency Alarms, text messages, maintenance alarms,
system health, and other event messages shall be provided. Dynamic column filter and
sorting shall be provided. The following tabular displays shall be provided:
1. Canned and ad hoc text messaging to the MDT or onboard vehicle displays with
store and forward capability
2. Emergency alarm listen in, audible alarms, and downgrade capabilities
3. Schedule and route information by block and/or run including real time status
4. Pull-in and Pull-out status from garage(s) for late and missed pull-ins and pull-
outs
5. Capability for dispatchers to log in operators with optional requirement for
operator acknowledgement
6. Off route monitoring including both off route and back on route notification
7. Display of operator generated transfers requests and capability to intervene in
the transfer process as operationally required
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.8 Map Display
The ATIS map display shall be compatible with ESRI shape files and map layers that
can be shared by all Transfort GIS enabled systems including Trapeze FX, trip
planners, GIS tools and applications, and other public web based real-time information
systems. The Contractor shall discuss map compatibility within their proposal. Transfort
desires that the GIS solution be capable of supporting existing industry interface
standards and provide the architecture to support future interface standards.
The Map Display shall have the following characteristics:
1. Continuous refreshed real-time location of all vehicle location updates
2. Filtered map views based upon parameters such as vehicles by user definable
groups, route, line group and login status
3. Options to display different vehicle icon labels including vehicle number,
adherence, route, driver, and run per map view
4. Quick find tool to locate vehicles and routes
5. Automated focus and continuous vehicle tracking during Emergency Alarm
condition
RFP 7381 Advanced Traveler Information System Page 23 of 143
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.9 Emergency Alarm (EA)
When a dispatcher receives an EA the following events shall occur, in sequence:
An audio alarm is triggered and the vehicle is continuously traced on the AVL work
station map display in a separate window. The refresh rate for location reporting shall
be at least every fifteen (15) seconds.
An emergency alarm acknowledgment message is sent and discreetly displayed on the
Mobile Data Terminal (MDT).
A Dispatcher responds to the emergency by listening in on the vehicle audio through a
microphone integrated into the MDT or installed within the Operator work area.
Emergency Alarms shall have the highest priority of all data messages. The EA event
shall be transparent to anyone on the vehicle except the driver.
The EA circuitry shall incorporate power-on-self-test features with the capability to
detect open and short circuit conditions. The EA switch shall be a normally open switch
to guard against accidental activation due to vibration, and shall be designed to
preclude accidental activation by the operator (i.e. within a collar).
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.10 Historical Data (Playback Mode)
ATIS users shall have quick and easy access to an historical event display or Playback
application accessible agency-wide. The historical event display shall playback all
pertinent historical messages (e.g., messages sent and received by: vehicle mobile data
terminal and dispatch). The display shall be by a sequence of events on a geographic
map. Playback of these events shall include the capability to perform the following
functions:
1. Allow selection by vehicle(s), route(s), fleet(s), or run(s) for specific time frames
through a query action window.
2. Configurable speed of replay for moving forward and backward through events
3. Graphical representation of event data on the ATIS system map
4. Selectable display of map layers including but not limited to stops, streets,
routes, points of interest, and geographical attributes
5. Text display of attributes of each vehicle event message including messages
related to other onboard systems
6. Step forward, step backward and pause the historical display of events
RFP 7381 Advanced Traveler Information System Page 24 of 143
7. Zoom, move, center, and fit to window views within the map window
8. Measuring distance tool
9. Vehicle label by number, adherence, route, driver, run, and block
10. Locate vehicles, routes, intersections or objects
11. Display route traces
12. Date and time messages are logged
13. Print the historical display
Automatic query for a selected vehicle in the real-time CAD system shall be available
for dispatcher playback of all historical messages for a user-defined period of time prior
to the current incident time for the dispatcher to assess the current conditions leading
up to an event.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.1.11 Scenarios
Please provide responses on the following five questions on how your proposed ATIS
solution will handle each of the following scenarios:
1. What the dispatcher will need to do?
2. What will public information systems display?
3. How is the route schedule adherence affected?
4. How all work time components are affected?
5. How will work incidents and collisions be synchronized between your system and
our system of record?
A. While on route 5 driver A in bus X gets into a collision. We need to take driver A
in bus X off of the work for 2 hours. During this time the first hour of said time will
need to be cancelled. Driver B in bus Y is able to drive the last hour of route 5
work cancelled off of driver A.
B. Bus X is running 20 minutes down. Bus Y is going to start X’s work on time while
bus X sits out one loop.
C. Route X is in need of an additional unplanned trailer due to a capacity overload.
We have an additional bus Z that is out in the field and is assigned to provide the
unplanned trailer.
D. Temporarily closed stops and line configuration changes due to short term (same
day 6am to 11am) detours.
E. Temporarily closed stops and line configuration changes due to longer term
(traversing 14 days) detours.
Information Required
RFP 7381 Advanced Traveler Information System Page 25 of 143
3.2 Google Transit Feed Specification (GTFS)
The Contractor shall provide an export that meets the Google Transit Feed Specification
(GTFS) for Transfort to make available to Google. The intention is to use the Google
based trip planning system in lieu of purchasing an independent trip planning system.
The ATIS website shall link to the Google trip planning system and appear as a single
seamless system.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.3 AVL Data Export
The Contractor shall provide a fully integrated AVL data export capable of providing
real‐time information that enhances both en‐route and pre‐trip planning for Transfort
customers and Transfort personnel. As part of this contract the Contractor shall
integrate all VMS and paging systems to support displays and sound systems at
Transfort specified locations, a new web site application that displays real‐time arrival
and departure information using both maps and textual displays.
The Contractor shall provide an open source application programming interface that
includes real‐time vehicle location updates for access by developers of web sites or
mobile devices.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
3.4 Trapeze Software Interface
The CAD software shall have an interface to Trapeze software that allows for seamless
synchronization of payroll information as well as incident management. Incidents may
be managed in either Trapeze Software or the CAD solution, however, the interface will
ensure that data is reflected in both solutions “on save”. Trapeze OPS will remain
system of record for most items and lookup data such as employees, vehicles, incident
types and investigation action types will be derived from Trapeze Software. The
interface between OPS and the CAD system shall operate in an automated and virtually
real-time fashion. Transfort updates scheduling based on special circumstances such
as Holiday Service, and other special events. Schedule changes are typically exported
three times annually from Trapeze. Daily vehicle and operator changes are made in
Trapeze OPS. Please refer to Appendix F, the Trapeze Software Interface
Specification. Please include in the cost summary the cost for managing, developing,
and implementing this interface.
Trapeze contact information:
Mr. Curtis Maxwell, Trapeze 5800 Explorer Drive 5th Floor Missasauga, Ontario
L4W5L4
RFP 7381 Advanced Traveler Information System Page 26 of 143
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.0 VEHICLE SYSTEMS
Vehicle systems will consist of onboard computers and operator consoles, VMS signs,
integrated paging systems and automatic passenger counter systems. The integration
of the Onboard Mobile Gateway will be considered a critical component of the received
proposal.
4.1 On-board Computer System (OCS)
The On-board ATIS subsystem shall include an OCS as a central processing unit,
including memory, input and output capabilities, data storage and system software
residing on each vehicle. The OCS shall be the center of the on-board components,
integrating the data communications for the information level applications included in
this specification.
The OCS shall be capable of real time updates and messaging to and from the vehicle.
The OCS shall meet communication requirements for wireless network, as well as
interfaces for current and future onboard ITS systems. Provided interfaces shall include
RS232, RS485 with busy line, TTL, SAE J1708, SAE J1939, USB, Ethernet, TCP/IP,
discrete inputs and outputs, odometer, spare I/O pins, audio inputs and outputs.
The OCS shall meet environmental and vibration standards (MIL-STD-810D, NEMA-4)
as well as appropriate electromagnetic immunity standards (SAE 1455) and protect
against surge, and reverse polarity. The OCS shall be of proven design and easy to
install and replace.
In case the cellular data network is not available, all on-board functions with the
exception of vehicle location and schedule adherence reporting to the central system
shall be functioning. Event data will be stored locally until the communication link is
restored. Data storage capacity shall be sufficient to store at least five operating days
worth of event messages in the case where data communications are disrupted and
event messages are stored locally.
Sufficient data storage capacity shall be included to store the complete current route
schedules, pending route schedules, five days of operating data, and associated
announcement files with 50% spare capacity for long-term growth. Configuration
settings related specifically to the vehicle shall be stored in the vehicle’s configuration
module installed in the vehicle such that the OCS unit can be swapped out and the
unique vehicle information automatically associated with the replacement OCS. Each
OCS shall have a unique IP address for purposes of participating in the vehicle network
and for remote monitoring.
RFP 7381 Advanced Traveler Information System Page 27 of 143
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.1.1 Data Transfer
The On-board equipment shall be capable of sending real-time AVL data and APC data
wirelessly using cellular technology as well as via Wi-Fi technology (802.11 b/g/n), at
the Transfort Facilities. Further, the wireless data transfer for both the AVL and APC
systems shall not require any human intervention, input, or monitoring for its daily
operation. Yet, the Contractor shall supply a means to transfer data by manual
methods using a portable device such as a laptop or other form of manual data retrieval.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.2 Mobile Data Terminal
The Mobile Data Terminal (MDT) shall be connected to the OCS. The MDT shall
provide visual messages and beep tone signals to the operator, if so configured by a
system administrator of Transfort. The MDT shall be capable as serving as the single
point of logon for the ATIS system and its subcomponents. The logon shall also capture
the employee number and run and/or block number that can be shared with other future
systems through industry standard interfaces and communication protocols.
The MDT shall be a color graphical screen capable of displaying fonts of variable size.
The MDT shall be designed with appropriate functional buttons capable of controlling
other onboard ITS systems (e.g. fareboxes, head signs, card readers) including numeric
input. There is no preference to touch-screen or hard key user interface. For a hard key
user interface the MDT buttons shall provide tactile feedback for positive recognition of
signal processing. For a touch-screen user interface the virtual keys shall not require
additional cleaning and provide positive recognition of signal processing.
The MDT shall provide contrast and brightness controls to provide for clear and easy
viewing in day, night, or high glare conditions. The MDT shall be easy to install and
replace, be durable and meet SAE ruggedness standards. The MDT shall be capable of
providing status and setup capabilities to the system administrator of all integrated
onboard systems including GPS, communications network and other on-board
integrated ITS systems such as but not limited to Automatic Passenger Counters,
Headway Signs and Fareboxes.
The MDT shall display the bus’ actual progress related to schedule and route
adherence. The MDT shall display vehicle status including data transmission, pending
messages, and communication mode. The MDT shall be capable of providing unique
aural tones to identify incoming messages to keep the operator’s attention on the road
while driving. The MDT shall be capable of providing onboard information and interface
to onboard systems during operation of the vehicle including:
RFP 7381 Advanced Traveler Information System Page 28 of 143
1. Logon
2. Emergency Alarm
3. Data Messaging
4. Transfer Assistance and Notification
5. Schedule Adherence
6. Trip/Schedule Status
7. Current Route and Direction
8. Maintenance Mode
9. Current GPS Time
10. Fare Box Control (priced separately)
11. Head sign Control (Priced separately
12. Map Display (Priced separately)
When the power is turned on, the MDT software shall automatically perform a power-
on-self test, followed by configuring and initializing the MDT to the user-specified default
values. The MDT shall be self-restarting and shall not become unresponsive and
require manual restarts to continue operations. The MDT shutdown process will be
controlled by the MDT software and shall only be possible when the ignition is in the off
position. A user specified shutdown delay shall be provided to continue operations and
to initiate the shutdown procedure that shall automatically close all files, save values,
and send a shutdown message.
Wheelchair lifts and ramps shall be monitored and data recorded for each cycle. If a
wheelchair lift or ramp is not cycled prior to leaving a garage/storage area at startup,
after the vehicle has moved a user configurable predefined distance then the MDT shall
display a warning to the operator and transmit the warning to the central ATIS system
for storage and display at the dispatcher work station.
The MDT shall display a warning if a logon has not occurred after a vehicle is moved a
user configurable predefined distance. This warning shall be transmitted to the ATIS
system for storage and display at the dispatcher workstation. A logon process shall be
provided for maintenance purposes to enable a vehicle to be moved through-out a
facility for servicing and maintenance purposes without triggering alarms.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.2.1 Text Messaging
The MDT shall allow the operator to send a message to dispatch from a set of pre-
defined messages. Messages shall be capable of being grouped into categories for
quick selection. Message categories and message text shall be user definable. The
MDT shall support the display of text messages longer than can fit on one line of the
display. A minimum of twenty-four (24) messages shall be supported.
The MDT shall store multiple messages received from dispatch and indicate those text
messages that are unread. A distinct aural tone and visual notice shall alert the
RFP 7381 Advanced Traveler Information System Page 29 of 143
Operator of an arriving data message to be read when the vehicle is not in motion. A
text message shall support a required Operator imitated acknowledgement message
back to dispatch once the driver has viewed a message if flagged by dispatch as
requiring Operator acknowledgement. Text messages shall be either deleted or saved
by the Operator after viewing. Storage for saved text messages shall support a
minimum of eight (8) stored messages.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.2.2 Transfer Requests
ATIS shall provide an automated process to protect the transfer of passengers at
designated transfer points designed primarily for transit centers, hubs and major
transfer points. An Operator may select a time point along their trip and be presented
with intersecting routes to “hold” after receiving a customer request for a transfer. Upon
selection ATIS shall evaluate the request and either approve or deny the request based
upon allowable parameters. The parameter values that define allowable hold times shall
be user definable.
The sending vehicle shall receive notification of the ATIS decision and if the request is
approved the target vehicle shall receive a hold notification indicating the location and
route to complete the transfer. The transfer process shall not require dispatcher
intervention. However, the dispatcher shall have the capability to review transfer
requests and intervene as appropriate.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.3 Automatic Passenger Counter (APC)
APC systems will be installed on board each transit revenue vehicle and have the
passenger counts stored on board and or transferred to the data center. The data will
be used to provide the Federal Transit Administration ridership data instead of the
current extrapolated data from handheld devices.
APC collection equipment shall be installed at vehicle door entries. The equipment will
enable complete ridership data collection, storage and transfer. APC data transfer will
be enabled to occur automatically through the wireless infrastructure. The equipment
shall not require any human input or monitoring for its daily operation. In addition, the
Contractor shall also supply a means to transfer data by manual methods using a
portable data storage device such as a laptop or other form of manual data retrieval.
The computer used for processing and analyzing the data must be able to accept and
process the manually transferred data.
Please provide your percentage of accuracy for the APC system you are proposing and
method for verification.
RFP 7381 Advanced Traveler Information System Page 30 of 143
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.4 Automatic Announcements (AA)
Automatic announcement systems consist of three main areas:
In Vehicle Systems
Transit Centers
Platforms and Stops
4.4.1 In Vehicle Systems
In vehicle systems will consist of Contractor installed Variable Message Sign (VMS)
mounted to the ceiling and integration with the existing onboard paging system. There
will be two VMS on forty (40) foot length and smaller buses and three VMS on sixty (60)
foot length buses. The exact location for the VMS to be installed will be approved by
Transfort prior to installation. The bus manufacturer and paging system types are noted
in Appendix C Vehicles. Provide a description of how your integration with the in
vehicle systems will take place, as well as any software or hardware requirements.
The AA shall announce and display information determined by Transfort staff as the
vehicle passes through geo-fences created by the proposed system. The
announcements and displays must meet ADA requirements. Canned messages and
dynamic messages generated from the CAD system will be playable over the AA in
each vehicle. Details concerning cost and quantities must be filled out in the Appendix
A - Cost Summary sheet. Details of existing vehicle equipment are located in Appendix
C – Transit Vehicles.
Information Required
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.4.2 Transit Centers
Transit Center AA will consist of integration of existing paging systems and VMS at
each transit center. The PA systems are currently used for static automatic
announcements through a software application on a Windows XP desktop. Provide a
description of how your integration with the Transit centers will take place, as well as
any software or hardware requirements. The AA shall announce and display
information determined in collaboration with Transfort staff as the vehicle passes
through geo-fences created by the proposed system. The announcements and displays
must meet ADA requirements. Canned messages and dynamic messages generated
from the CAD system will be playable over the AA in each vehicle. Details concerning
cost and quantities must be filled out in the Appendix A - Cost Summary sheet. Details
of current equipment are in Appendix D - Transit Centers
RFP 7381 Advanced Traveler Information System Page 31 of 143
Information Required
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
4.4.3 Platforms and Stops
Platforms and stops AA will consist of VMS and paging system along the Mason
Corridor BRT line. The AA shall announce and display information determined in
collaboration with Transfort staff as the vehicle passes through geo-fences created by
the proposed system. The announcements and displays must meet ADA requirements.
Canned messages and dynamic messages generated from the CAD system will be
playable over the AA to each platform or stop.
All VMS and paging systems are being installed by the General Contractor building the
MAX BRT line. Integration into those devices will be required as part of this project.
Provide a description of how your integration with the Platforms and Stops will take
place, as well as any software or hardware requirements. Details concerning
equipment and quantities are detailed in Appendix E – MAX BRT Platforms and Stops.
Information Required
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
5.0 PASSENGER INFORMATION SYSTEMS
Passenger information systems consist of external facing or public facing ATIS systems:
An interactive voice response system for telecommunication callers.
A series of information displays such as variable message signs (LED) and
digital signage systems (LCD) and paging systems.
An internet information web site with a mobile ready version
Mobile device application and development
Mobile SMS/Email component
5.1 Interactive Voice Response (IVR)
The Contractor shall provide an IVR system with the characteristics below. Riders can
contact the Transfort IVR system using telephones from home, office or cell phones
RFP 7381 Advanced Traveler Information System Page 32 of 143
from the street to receive update information about bus’s location. The IVR system will
receive the location, time and status of the fixed route buses from the CAD system.
The IVR system shall provide for user supplied numeric bus stop identification for
automated delivery of bus stop level real-time and schedule information. The IVR
system shall incorporate Transfort’s bus stop numeric identification system. Using the
unique stop identification number the IVR system shall provide the most current
information related to all routes and vehicles providing service at that stop location.
The IVR system shall interface with ATIS for service bulletins, scheduled, and real-time
bus information.
The IVR shall be capable of providing computer Telephony Integration. Transfort has a
Cisco VOIP phone system that will be used for the IVR system. The IVR shall include
technology integrated with the input from touch-tones phones and not use voice
activated interaction.
The IVR shall provide management tools for authorized Transfort personnel to configure
the system without experiencing system down-time. Reports shall be available to
monitor usage statistics.
The IVR will be used in conjunction with two dial in phone lines and a phone tree that
will roll over the third line to a customer service representative.
Please provide information concerning your IVR solution, such as features, software
and hardware requirements.
Information Required
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
5.2 Information Displays and Paging Systems
The following list identifies the locations in Transfort’s operating area that are the
primary candidates for real-time traveler information displays and are provided for sizing
of the ATIS design:
South Transit Center
1. Will consist of Eleven (11) bus bay Variable Message Displays (LED) (displays
will be purchased and installed by the MAX Bus Rapid Transit General
Contractor) – Outdoor
2. Will consist of Two (2) 40” LCD displays using a digital signage software
(displays will be purchased and installed by the MAX Bus Rapid Transit General
Contractor)
RFP 7381 Advanced Traveler Information System Page 33 of 143
3. Will consist of bus bay specific paging system and internal paging system
(paging system will be purchased and installed by the MAX Bus Rapid Transit
General Contractor)
Downtown Transit Center
1. Consists of an existing 40” LCD display using Four Winds Interactive digital
signage software.
2. Consists of existing internal and external paging system
Colorado State University Transit Center
1. Consists of an existing 40” LCD display using Four Winds Interactive digital
signage software.
2. Consists of an existing 46” LCD display using Four Winds Interactive digital
signage software.
3. Consists of existing internal and external paging system
MAX Bus Rapid Transit Stops and Platforms
1. Will consist of thirty seven (37) Variable Message Displays (LED) (displays will
be purchased and installed by the MAX Bus Rapid Transit General Contractor) –
Outdoor
2. Will consist of Stop and Platform specific paging system (paging system will be
purchased and installed by the MAX Bus Rapid Transit General Contractor)
The Contractor shall provide input to existing or planned LED and LCD signs and
paging systems. Information provided to the signs and paging systems shall include
scheduled and real-time transit vehicle arrival / departure information, text messages,
vehicle location, bay assignments, maps, and other multi-media content. Layout
capabilities shall be user definable and capable of supporting alternate purposes other
than transit scheduling notification including multimedia capabilities.
A user interface shall provide easy setup, configuration, diagnostic, and messaging
status at each Passenger Information Display location. Displays shall be capable of
showing multiple routes, ATIS system time, ad hoc messages, sponsor advertising, and
scheduled messages. A system administrator user interface shall provide diagnostic
information, messaging status, setup, configuration, and messaging capabilities for all
locations.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
5.3 Internet Information (Web Site)
The Contractor shall provide a dynamic geographical view of Transfort’s system routes,
stops, and vehicles with up-to-date real time information using web services. An easy to
use web interface for route and stop information, scheduled departure times, next
estimated arrival and departure times shall be provided.
RFP 7381 Advanced Traveler Information System Page 34 of 143
Information from the web services shall be published to personal computers, cell
phones, personal internet enable devices, and other wireless devices. Customers shall
be able to place subscriptions to real-time alerts for routes, stops, system wide alerts,
and specific trips that will be published by the Transfort web service prior to a
configurable period of time to the event’s occurrence.
Options that are user definable shall be provided that integrate the real-time display of
information into the look and feel of the existing Transfort web site. Such options should
include graphics, logos, backgrounds, page layout, and icons. Map displays shall
include configurable colors, routes, map layers, backgrounds and refresh rates.
The web site application shall permit the user to enter a stop id and select a route and
direction. The system will then display the arrival times of the next two buses. The
application shall also permit the user to identify one or more routes on a map display. All
vehicles on the route(s) shall be displayed at the last known location if communications
with the vehicle are active otherwise scheduled locations shall be displayed and clearly
labeled as scheduled. Each vehicle shall display route, direction, next time point, and
bus ID when the cursor is placed or clicked on the vehicle. The map shall display bus
stops on the route(s) when the zoom level is close enough to support this level of detail.
Each stop shall provide the street location, route(s) and direction(s) served, and unique
bus stop ID when the cursor is placed or clicked on the stop.
The web site application shall permit the user to identify a route, direction, and stop to
display the next two scheduled buses and their real-time estimated time of arrival for
that stop. When the real-time estimated time of arrival is unknown the web site will
clearly state that the scheduled time only is being provided.
All web services configurations, applications and public facing information shall be
approved by a City of Fort Collins representative prior to design and deployment.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
5.4 Mobile Device Applications and Web Site
The Contractor shall provide a mobile application in support of the Iphone and Droid
operating systems on smart phones. The application will be developed and maintained
by the Contractor and made available on the ATIS website and other mobile app
websites. The contractor will coordinate content and features with Transfort prior to
release to the general public.
1. Plan your itinerary using the Google Trip Planner.
2. Find fare, safety rules and help information.
3. Get latest news and rider alerts.
4. The mobile app allows customers to locate the nearest lines and stations based
on the smart phone’s GPS capabilities.
RFP 7381 Advanced Traveler Information System Page 35 of 143
5. The application is integrated with Google Maps, displaying the nearest stations
and lines based on your smart phone’s GPS location. Platforms, stops or transit
centers are represented with a pin and a popup displaying the Line information.
6. Ability to register or change your transit alerts.
The mobile ready version of the ATIS web site shall be developed and made available
for use on mobile devices. The Contractor will coordinate content and features prior to
release to the general public. In addition to the requirements listed above, the mobile
ready version will also require:
1. The mobile web site allows customers to locate the nearest lines and stations
based on their interest.
2. The mobile web site integrated with Google Maps, displaying the stations and
lines based on your interest. Platforms, stops or transit centers are represented
with icons or other designated symbols.
The Contractor shall provide an open source application programming interface that
includes real‐time vehicle location updates for access by developers of mobile devices.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
5.5 Mobile SMS/Email
The proposed ATIS solution will include the capability for passengers to access rider
alert information, real-time and schedule time information via SMS and email
messaging. At a minimum, the system will allow passengers to subscribe to SMS and
email messages as described earlier in this section. Subscriptions will allow
passengers to receive this information in the following manner:
Real-time arrival information
Real-time rider alerts
At a minimum, the proposed solutions will also include the capability for passengers to
receive these updates using the following context:
Day of week
Time of day
Route
Bus stop
The proposed ATIS solution will include the ability to deliver default schedule
information and/or canned messages with alerts when the system is unable to calculate
a prediction to send via SMS or email.
RFP 7381 Advanced Traveler Information System Page 36 of 143
The system will allow passengers to place subscriptions to SMS and email messaging
through a public facing website. The system will also allow passengers to request real-
time arrival, real-time rider alert and scheduling arrival information by entering a stop
number via a mobile application.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.0 ATIS TECHNICAL INFORMATION
City of Fort Collins (CFC) standard network equipment uses the latest technology and
innovation. The following are the existing technologies utilized:
Cisco Networks and VPN
Microsoft Windows Server 2008 R2
VMWARE Virtual Server
Left Hand Storage Area Networks
COMMVault Backup solutions
HP Hardware
The Cisco network utilizing gigabit fiber optic WAN connectivity will be available for use
at all transit locations by the proposed ATIS solution. An integrated solution will utilize
existing CFC server and storage area network infrastructure.
The integrated solution submitted will be evaluated utilizing CFC virtual server and SAN
environment. The virtual server and storage array will be provided according to the
Contractor’s requirements as listed in the proposal. The support model will be mixed
support with the hardware and operating system software supported by the CFC
Information Technology department and the application software supported by the
Contractor.
The transit facilities are geographically distributed across the city as shown in Figure 1
Transfort Transit Facilities in Section 2.4. The Contractor shall provide an innovative
and optimized solution for the transit facilities use of the network based ATIS Solution.
Details must be provided regarding the version, features and capabilities of the
proposed ATIS software. The recommended solution shall need to meet CFC
Information Technology standards for software.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
RFP 7381 Advanced Traveler Information System Page 37 of 143
6.1 Data information and Ownership
The ATIS solution shall have sufficient capacity to store the real-time data from the
buses for at least five (5) 24-hour periods of data for all routes covered. Real-time data
shall be archived on a daily basis. Database shall be capable of keeping ATIS data,
standard reports, and other related information for a minimum period of one (1) year in a
single standard database. In addition, back up and retrieval procedures shall be in
place to be able to use archived data as needed. Data must be indexed by date and
time in which the data was collected.
All data generated and used by the ATIS system shall remain the property and for the
exclusive use of Transfort and the City of Fort Collins with no limitations on any or all
aspects of the data.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.2 Data Analysis and Report Generation
The Contractor shall perform all data processing and report generation from data
collected until all accuracy testing and relevant Transfort staff training have been
successfully completed. The reports will be submitted in hard copy and electronic
format by the Contractor to Transfort within five (5) calendar days from the last date that
data was collected from the ATIS. Hardcopy and electronic reports will be produced for
Weekday, Saturday, and Sunday service. The report formats submitted are subject to
approval by Transfort and will include the following:
Summary of all events observed for each vehicle and route assignment.
Summary of events by Geographic Location.
Schedule adherence utilizing specified parameters that can be adjusted over
time, for early, on-time, and late bus arrivals from designated stops or time points
along a route.
Running times by end-user specified route segment, time interval, and direction
of travel.
Deadhead Running Times.
Schedule Adherence statistics: median, average, standard deviation, percentiles,
etc.
On-Time performance summaries at different levels of detail, including system-
wide, route, and time point levels.
Summary of all samples observed for each vehicle and route assignment.
NTD Report – Defined by Title 49 USC 5335.
Trip reports by route with stops in sequential order, including ID, description,
Boarding, Alighting, Loads, Distance, and Passenger Miles.
Boarding, Alighting, and Load profiles by route, day of the week, month of year,
stop location and time of day (variables are end-user specified).
Vehicle loads by time of day (end-user specified intervals).
RFP 7381 Advanced Traveler Information System Page 38 of 143
Bus loads by end-user specified route segment, time interval and direction of
travel.
Passenger Activity by stop, segment, route, and time period.
Location specific passenger activity (end-user selected location).
Dwell times.
Report on type of errors and adjustments.
Time used in wheelchair lift operation (i.e., lowering, raising, and total time).
(optional)
Wheel-chair lift usage by route by day and direction of travel. (optional)
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.3 Database Information
The Contractor shall provide network access to the raw database as well as standard
reports for staff assigned to work with the data from the ATIS system. The database
shall be able to be accessed, using standard ODBC protocols. Transfort currently
utilizes Microsoft SQL 2008 R2 as its enterprise database.
Data Storage shall make use of the existing Transfort hardware and software as much
as possible. The ATIS software is to be installed at the City of Fort Collins’s main data
center with oversight and approval of the Project Manager assigned to this project.
6.4 Technical Overview
A technical overview of all proposed hardware and software must include:
1. Network diagrams
2. Hardware diagrams and software process flow diagrams
3. Optimum and minimum requirements for:
a. Client viewing computer configurations for desktop and mobile access
b. Network requirements
c. Server requirements
d. Storage requirements
e. Back-up requirements
f. Monitoring requirements
The technical overview submittal shall be provided as (CDRL 601, "Technical
Overview").
Information provided?
6.5 Data Communications
Data transfer from the transit vehicles’ to the Transfort data center is currently
provisioned using a Cisco wireless solution. Data currently being transferred involves
recorded and live video and smart card data from onboard smart card readers. All data
RFP 7381 Advanced Traveler Information System Page 39 of 143
transfer operations are automated and do not require intervention by Transfort
personnel.
6.6 Operating Environment
ATIS shall be able to operate, without degradation in performance, under the following
environmental conditions:
Humidity range of 20% to 100%
Temperature range of 20° F to 150° F
Direct or Indirect Sunlight
Transfort requires that any system proposed must allow for 50% fleet growth
ability within the specified limits of the proposal during the life of ATIS.
The ATIS solution must be able to provide a vehicle location determination
anywhere in Larimer County and Boulder County and up to 10 miles inside the
adjoining counties. Provided appropriate Cellular coverage is available.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.7 Software
The Contractor shall grant Transfort the right to use all software and firmware used in
the equipment provided under the Contract as follows:
For Commercially Available Software, the Contractor shall provide a license for
each copy used in the equipment as well as the distribution media. The
Contractor shall provide for version updates of these applications during the
warranty period as required to be compatible with the Contractor’s system.
For Contractor Proprietary Software, the Contractor shall establish an escrow
account with a third party, acceptable to Transfort, for a period of no less than ten
years, in which the same data as for the Project Specific Software will be
deposited. The Contractor shall pay all initial and future costs related to the
escrow account. The data shall immediately be obtainable and usable by
Transfort should the Contractor agree to release the data; should the Contractor
fail to satisfactorily respond to or support a written request for modification of the
software by Transfort in a reasonable amount of time during the term of the
active escrow agreement; or, the term of the escrow has expired within a
mutually agreed Software License agreement. The Contractor shall notify
Transfort’s current Project Manager of the intended closure of the escrow
account. This notification must be made a minimum of 60 days prior to the
closure.
For software required for Transfort ATIS operations, the Contractor shall grant
Transfort a royalty-free right to use the software. Transfort will have the right to
modify all project-specific software settings and parameters that configure
Transfort’s application, including:
RFP 7381 Advanced Traveler Information System Page 40 of 143
Operating data (machine numbers, network numbers, and
up/download parameters)
Display and voice text and graphics
Other configurable parameters as described in this document.
The software and users manual together with the training shall ensure that Transfort
personnel are able to modify the above listed parameters without system interruption of
more than thirty minutes.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.7.1 Software Requirements
The Contractor shall furnish all software fully debugged and documented.
The Contractor shall work with Transfort to develop the Software Design and
Documentation CDRL 602. At the Preliminary and Final design reviews (PDR, FDR),
the Contractor shall provide for Transfort approval of the full up-to-date documentation,
including flow diagrams, data structures, parameter tables, restoration plans, full
restoration procedures, and all other design and development documentation, with each
software package (CDRL 602, “Software Design and Documentation”). Such
documentation shall be accompanied by a functional description of the software as
applicable to Transfort’s ATIS system.
A list of commercially available software to be employed in the system, including a
description of the capabilities and proposed functionality of such software shall be
submitted to Transfort for review at PDR and approval at the FDR (CDRL 603,
“Commercial Software List”).
All software documentation and licenses shall be provided by the date of delivery of the
first equipment. Updated versions of such documentation, reflecting any prior changes
made in the system, shall be provided within 21 days of any applicable system change.
Final versions of such documentation shall be provided at the end of the warranty
period.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.7.2 Definitions
Commercially Available Software: Any software or firmware product that is
commercially available from software developers, distributors or retailers (i.e.
DOS, Windows, Word, Lotus and Excel).
Proprietary Software: Any software or firmware product developed and
copyrighted by the Contractor or any of its Subcontractors, but not commercially
RFP 7381 Advanced Traveler Information System Page 41 of 143
available, and which is used by the Contractor in any way as part of the
Contractor’s development effort or end product.
Project Specific Software: Any software or firmware product that contains any
element of characteristic design feature or coding developed by the Contractor or
any one of its Subcontractors in whole or in part specifically for or use in
conjunction with equipment delivered under this Contract.
6.7.3 Licensing Model
Please provide information concerning your licensing model and how it relates to
number of vehicles, number of workstations, number of personnel or a combination of
these or other items. Refer to the following information to understand the Transfort
inventory and staffing resources.
Provide information detailing your licensing methodology taking into account that
TransFort currently has the following staff and vehicles:
Up to fifty (50) vehicles
Up to eighty (80) bus operators
Up to six (6) Dispatchers
Up to five (10) Supervisors
Up to two (2) Technical staff
Please provide a breakdown in the Appendix A Cost Summary sheet for all licensing
costs. Please use the sample number of users, vehicles and employees for your
calculations.
Information provided?
6.8 Protocols
ATIS must include the ability to send an email via an email server to anyone, or any
group, based upon an event. Please confirm use of protocols or methods of
communications such as ICMP, SMTP, SMS, paging, etc. The events must include, but
not necessarily limited to, the following:
1. System Event
2. Generated Alarm
3. Any Filter Alarm
4. Any Input Alarm
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.9 Anti-Virus
The VMS shall be compatible with the leading brands of anti-virus software in order to
detect and deactivate malicious software that may attempt to attack the system.
RFP 7381 Advanced Traveler Information System Page 42 of 143
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.10 Security
The option to set up ATIS in advanced security mode shall enable both IT and security
managers to collectively integrate the unit into existing Microsoft Windows networks
without compromising the existing security protocols.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
6.11 Upgrade Tools
Proposals shall provide complete details addressing the following:
1. What is the history of upgrade frequency?
2. What happens to customized tables and fields when an upgrade occurs?
3. How much technical and end-user training is generally required for software
upgrades?
4. How upgrades are applied, i.e. remotely, on-site, etc.?
5. How are patches and fixes deployed and applied?
6. Will you update the Trapeze Software Interface after your upgrade?
Information provided?
6.12 Maintenance and Support
Proposals shall provide complete details addressing the following minimum
requirements:
1. Maintenance coverage for routine services on a periodic basis, including software
updates, patches, and upgrades.
2. Emergency response service with a guaranteed response time, location of dispatch
by responding party and process to be followed for the following events:
a. System outage
b. Network control and monitoring center outage
3. Period of maintenance coverage (i.e., number of hours or days of maintenance
coverage)
4. Equipment replacement procedures (onsite and depot parts repair and replacement)
5. Describe response procedure for:
a. Escalation calls
b. First-time response to service calls
6. Provide breakdown report of all maintenance costs for all equipment, software,
network response and services beginning at the end of the warranty periods and
extending for a period of five years.
RFP 7381 Advanced Traveler Information System Page 43 of 143
a. ATIS software and hardware shall have a minimum of one year warranty and
then have a yearly service contract.
b. The one year warranty time period shall begin 30 (thirty) days after the Go
Live week has been completed.
7. The Contractor shall have the ability to connect remotely to ATIS to provide needed
support. The remote connectivity will be through approved City of Fort Collins VPN
security software.
8. Communication between the awarded vendor and the City of Fort Collins
representative shall be on an ongoing basis. Advanced notification shall occur when
any work is to be performed remotely or on site at any City facility or station / stop.
9. Suggest optional maintenance service plans and reasons for recommendation
Information provided?
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
RFP 7381 Advanced Traveler Information System Page 44 of 143
7.0 PROJECT MANAGEMENT
This section defines the management program that is required to provide a process of
planning, scheduling, design review, controlling, and reporting.
7.1 Contract Management
A Project Manager shall be designated by the Contractor to manage the work of this
Contract. Formal communication shall be between the Contractor’s Project Manager
and the Transfort Project Manager. Change of the Project Manager after Contract
Acceptance shall only be permissible with Transfort’s written approval.
7.2 Project Management Plan
The Contractor shall submit a Management Plan that describes the organization,
controls, planning, and schedules (CDRL 701, “Project Management Plan”). The Plan
shall be submitted no more than 30 days following the Notice to Proceed and shall be
subject to Transfort’s review and approval. The plan shall include the following:
1. An organization chart identifying managers for all organization departments of
the Contractor and Subcontractors
2. The methodology to control program schedule
3. A master program schedule, emphasizing key milestones and events
4. A schedule for the items of design and manufacture that require approval
5. A configuration management plan for all submittals and subsequent revisions
6. A subcontractor management and communications plan outlining the
Contractor’s methods and procedures for organizing and communicating with
subcontractors. This shall include an outline of activities to be performed by DBE
firms, an identification of the portion of the Contract revenues to be allocated to
such firms for these activities, and the means of encouraging, tracking and
controlling DBE participation throughout the duration of the Contract.
7. Procedures and processes to be followed for the replacement of any DBE
subcontractors throughout the duration of the Contract.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
7.2.1 Progress Reviews, Schedules and Project Control
Progress reviews shall be held on a monthly basis at Transfort’s facilities, as
appropriate. Other meetings may be scheduled as necessary.
The Contractor shall prepare and maintain a detailed progress schedule, which shall be
the Contractor's working schedule and shall be used to plan, organize, and execute the
work; record and report actual performance and progress; and forecast remaining work.
The Contractor must fully comply with the schedule submission requirements specified
herein to ensure the timely processing of progress payments. Work shall be scheduled
so that any specified intermediate milestone dates and completion dates are met. The
Contract schedule shall be submitted within 30 days of the Notice to Proceed.
RFP 7381 Advanced Traveler Information System Page 45 of 143
The Contractor shall submit to Transfort a progress schedule addressing Contract
activities for the period from Notice to Proceed to completion of the warranty period
(CDRL 702, “Project Schedule”). Activities shall also include the design reviews.
Critical path method analysis shall be used to approve the baseline schedule of key
milestones and events. One hard copy and one electronic copy in an approved software
package shall be presented. The hard copy of the progress schedule may be in the form
of a Gantt bar chart. In preparation of the progress schedule, the Contractor may
propose, for Transfort’s approval, alternative dates if the specified dates are not
consistent with their sequence of work. This schedule shall be updated on a monthly
basis according to the status of events and presented to Transfort at the status review
meeting.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
7.2.4 Weekly Conference Calls
The Contractor shall participate in weekly conference calls with the Transfort Project
Manager, other Transfort staff and outside consultants as determined by Transfort
Project Manager.
The agenda for these meetings will be to discuss the most current status of and plans
related to all identified issues. Transfort reserves the right to identify for discussion any
additional issues beyond those identified.
A status report shall be issued to Transfort at least two days prior to each conference
call, including
1. Agenda for the upcoming conference call highlighting key discussion items;
2. Updated action item list with the updates incorporating the discussions of the
previous bi-weekly conference call as well as other subsequent developments
since the previous action item list release.
The Contractor shall be represented in these conference calls by at minimum their
designated Project Manager, as well as any additional Contractor staff necessary to
properly address the current issues and project status.
Transfort will be represented by their designated implementation management
representatives.
The call-in procedures for the conference call will be arranged by the Contractor. The
Contractor shall submit minutes within two days of each conference call.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
RFP 7381 Advanced Traveler Information System Page 46 of 143
7.2.5 Monthly Progress Status Updates
The Contractor shall submit to Transfort monthly progress reports comparing actual
progress with planned progress (CDRL 703, “Monthly Progress Reports”). Special
reports may be requested and topical reviews held to address problem areas. Progress
reports shall also include:
A summary of completed, pending and upcoming Contractor and Transfort activities
during the previous and the next two reporting periods, along with required
completion dates
The status of unresolved Contract questions and change requests
A description of current and anticipated project problem areas and steps to be taken
to resolve each problem
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
7.3 Initial Activities Meeting
The initial activities meeting shall take place no later than 20 days after NTP. Transfort
personnel will be introduced to the Contractor’s management team at Transfort’s
facilities. Formal channels of communication and procedures, in accordance with
Transfort’s Standard Operating Procedures, shall be established for agreed-upon letter
and meeting numbering, etc. During these meetings, the Contractor shall present the
project control methodology and convey the plans for the initial activities prior to formal
progress reporting.
The objectives of the initial activities meeting shall be to familiarize Transfort with the
Contractor’s intended design and procurement activities, resolve external interfaces,
and provide the basis for proceeding to PDR. The initial activities meeting shall cover
the following:
1. Schedule review
2. Confirm Contractor’s management team and the scope of for each subcontractor
3. Provide a functional block diagram of the system and equipment
4. Provide narrative descriptions of the major subsystems proposed by the
Contractor, including identification of components supplied by Subcontractors for
each equipment type
5. Provide preliminary device layouts
6. Identify all interfaces between the major subsystems, provide a schedule, and
identify responsibilities for completion of detailed definition of the interfaces
7. Confirm that the Contractor is familiar with the intended operations and
maintenance environment
8. Provide outline and format of customer interface messages
9. Provide physical dimensions of each equipment type
10. Identify power and other facility requirements for each equipment type
11. Identify information needs and decisions required from Transfort
RFP 7381 Advanced Traveler Information System Page 47 of 143
12. Provide description of problem tracking, resolution and reporting process.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
7.4 Design and Configuration Control
The Contractor’s program for design and configuration control shall meet the
requirements in the following subsections.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
7.4.1 Design Principles and Reviews
Commonly accepted industrial design principles shall be employed throughout the
design and manufacturing processes. Design calculations, layouts, and other
documentation summarizing the human factors engineering considerations shall be
submitted during the design reviews. Industrial design aspects of ATIS system shall be
reviewed during the scheduled design review meetings.
A formal design review process shall be conducted to evaluate the progress and
technical, functional and programmatic adequacy of the design in accordance with the
performance requirements of the Contract. In addition to formal design reviews, informal
meetings to address key issues shall be held as needed. Prior to each review, a design
review package shall be submitted that includes items required for the review. Design
review packages shall be provided at least 15 days before a design review meeting.
Design reviews shall consist of the following key activities:
1. Design review package will be reviewed by Transfort staff.
2. An Issues List will be created as a result of the review and will be provided to the
Contractor at least ten days prior to the scheduled design review meeting.
3. The design review meeting, or series of meetings, will be held between
Contractor and Transfort staff where the Contractor shall explain their design and
Transfort shall confirm the requirements. When possible, issues will be resolved
during the design review meetings.
4. Issues not resolved during the meetings will be identified and documented.
Transfort will determine the appropriate action to close the issue, giving
consideration to where the project is in the overall design review process. This
may require resubmission of design review items.
5. The submittal will be approved, upon Transfort’s determination that there are no
open issues.
The Contractor shall conduct a Preliminary Design Review and a Final Design Review.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
RFP 7381 Advanced Traveler Information System Page 48 of 143
7.4.2 Preliminary Design Review
The objective of the PDR is to review the progress of the project and evaluate
specification compliance of the completed work and/or work in progress. The PDR shall
cover the following:
1. Schedule compliance review and discussion of variances or delays
2. Provide all PDR items indicated in the CDRL List
3. Detailed technical descriptions of ATIS system major components
4. Detailed interface descriptions, including mounting arrangements and installation
methods
5. Single-line power diagrams and functional block diagrams for each device,
including a functional overview
6. Detailed network diagram including all wiring and communications interfaces
7. List of special tools and DTE
8. Design of access control for the following:
9. Equipment
10. Software menus
11. Software system-level flow charts
12. Software data backup and recovery procedures
13. Software version and configuration control system
14. Draft Engineering Drawings
The Contractor is encouraged to categorize the PDR information into logical topics.
Ideally, the formal PDR meetings should be limited to confirmation of previously
reviewed, commented on, and approved-in-principle submittals and resolution of open
items.
The specific submittals shall be provided prior to PDR (CDRL 704, "PDR Package").
Each drawing submittal shall include a CD with the drawings in electronic format (.pdf)
and one reproducible on regular paper, developed using Microsoft Visio Professional
2007 files.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
7.4.3 Final Design Review
The FDR shall be conducted when detailed design is complete and production drawings
are ready for release. The objective of the FDR is to determine whether the detailed
design will satisfy the design requirements established in the Contract. Data submitted
for the PDR shall be updated to a level of detail consistent with the completed design
and submitted for the FDR. The FDR shall cover the following:
1. Schedule compliance review and discussion of variances or delays
2. Provide all FDR Items indicated in the CDRL List
3. Latest revisions of the drawings and documentation submitted for the PDR
RFP 7381 Advanced Traveler Information System Page 49 of 143
4. Assembly drawings down to the lowest replacement unit level
5. Electrical schematic drawings, down to the individual signal or wire level, for each
electrical circuit
6. Software documentation consisting of structured data flow diagrams with
software module descriptions (or elemental process descriptions) in structured
narrative format. Input and output data definitions
7. Program parameters
8. Error handling routines
9. Data dictionary
10. Final Engineering Drawings
The Contractor may establish suitable confidentiality agreements.
The specific submittals shall be provided prior to FDR (CDRL 705, "FDR Package").
Each drawing submittal shall include a CD with the drawings in electronic format (.pdf)
and one reproducible on regular paper, developed using Microsoft Visio Professional
2007 files.
For the purposes of change control, the design baseline shall be established at the
FDR. The Contractor shall submit to Transfort for approval changes beyond FDR that
affect the design characteristics agreed to at FDR.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
8.0 TRAINING
The Contractor shall provide a program to educate, train, and teach personnel in all
details of the installed equipment to the subsystem and component level, as required to
enable personnel to operate, service, and maintain the equipment satisfactorily.
Classroom sizes shall allow all trainees to have one-on-one training with equipment and
software.
The Contractor’s training program shall include classroom training given by the
Contractor’s staff. The Contractor shall provide a minimum of 60 hours of classroom
training. These hours shall include training for operations, maintenance, IT, and
marketing functions. The training shall be designed to be delivered by an instructor in
the classroom and, when appropriate, in the field or shop when actual equipment is
used. Classroom presentations may be videotaped for use as a training tool in
subsequent training sessions.
The Contractor’s program shall include formal and informal instruction, models,
manuals, diagrams, and component catalogs. All materials used in the programs, such
as models, manuals, mock-ups, and drawings, shall be of durable construction and shall
RFP 7381 Advanced Traveler Information System Page 50 of 143
become the property of Transfort. Training materials shall be updated as required
during the course of instruction.
The Contractor shall assume that Transfort staff does not have knowledge of any ATIS
features. However, the Contractor may assume that personnel have the basic skills
pertinent to their crafts. Throughout the contracted maintenance term, the Contractor
shall provide course updates of any type as needed.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
8.1 Transfort - Furnished Training Related Items
Transfort will furnish the training-related items listed in the following subsections. The
Contractor must submit requirements for such Transfort-supplied items to Transfort at
least three (3) weeks prior to scheduled start of training.
Space for classroom lectures and practical training on equipment will be furnished by
Transfort. The location and class times will be set by Transfort.
Use of training equipment such as projectors, screens or DVD players, and similar
equipment will be furnished by Transfort.
8.2 Use of Actual Equipment as Training Aids
The Contractor may use actual equipment or spare parts furnished under the Contract
for use as training aids in lieu of mock-ups and for demonstration of and practical
exercises in adjusting, testing, disassembly, and assembly of equipment. However, the
Contractor shall be responsible for ensuring that such parts are not damaged or
modified in any way. In addition, these parts must pass re-inspection and acceptance
tests after return to Transfort.
8.3 Training Program Plan
The Contractor shall submit a Training Program Plan in accordance with the criteria
outlined below (CDRL 807, “Training Program Plan”). In addition, Transfort staff or its
representatives shall have the right to request and receive instruction regarding the
operations and maintenance of all provided equipment, from the Contractor, at any time
as part of the training process.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
8.3.1 Description
A narrative description that documents the design for training Transfort staff shall be
developed. Transfort staff to be trained includes operations managers, dispatch
operators, shift supervisors, drivers, repair personnel, IT, marketing specialists, and
trainers. The description for each training program shall include the following:
RFP 7381 Advanced Traveler Information System Page 51 of 143
1. Performance objectives that state the expected behavior, the conditions under
which performance will occur, and the measures and standards to be applied
2. The sequence of learning activities
3. An outline of the content
4. Learning strategies to be used (e.g., classroom presentation, hands-on practice,
paper and pencil exercises, etc.)
5. Methods and criteria for evaluating performance, including an objective grading
system to report progress of trainees during the training
6. Resources required, such as equipment, shop space, projectors, screens, etc.
7. Approximate hours required for training, including classroom and hands-on
instruction.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
8.3.2 Training Delivery Schedule
A schedule based on the number of hours of instruction shall be developed. The training
delivery schedule shall include the following information:
1. Title of the program
2. General description of the program
3. Intended audience
4. Size of the audience
5. Transfort facilities required (e.g., classroom size)
6. Sequence of classroom and hands-on instruction and estimated hours required
for both
7. Number of sessions
8. Any other information that will facilitate planning for and delivery of the training
programs.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
8.3.3 Contractor’s Training Experience
A brief statement of the experience of the Contractor’s department having prime
responsibility for preparation and implementation of the programs and qualification of
the assigned personnel shall be included. Contractor Trainers shall consist of field
experienced personnel who have hands on knowledge of the provided system.
Resumes of all trainers shall be provided to Transfort no later than 60 days prior to
training commencement. Transfort reserves the right to request changes in the
proposed training staff with no extra expense to Transfort.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
RFP 7381 Advanced Traveler Information System Page 52 of 143
8.3.4 Training Courses
The Contractor shall provide a series of courses designed to train operators,
dispatchers, operations supervisors, customer service representatives, system
administrators, maintenance, and IT personnel on the ATIS operations and simple
maintenance. The Contractor shall provide Transfort a course description of each
course as part of the training program deliverable. All provided training courses shall be
accompanied by training manuals, guides, training aids, student and instructor
workbooks, and operator and maintenance manuals. All training classes will be
scheduled by Transfort and will not take place before the CAD systems are installed on
site.
A plan for training Transfort trainers to deliver the training shall be included. It shall
describe the Contractor’s approach, resources and hours required, and any training aids
that might be included.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
8.3.5 Training Materials
The Contractor shall submit the training materials required for each course discussed in
the Training Program Plan in accordance with the following requirements. The
Contractor shall provide a list of training materials required for each course discussed in
the Training Program Plan. The Contractor shall reflect all changes and revisions to the
installed ATIS systems in all training materials, whether supplied to Transfort personnel,
or used in Contractor-conducted training courses. At a minimum the following training
materials shall be provided for each course in sufficient quantities:
Instructor guides, including the following:
1. Course agenda and objectives
2. Resources and facilities required for the course
3. Detailed lesson plans or outlined presentations and discussion guides
4. Pre- and post-training assignments
5. Instructions for using any audiovisual support and equipment
6. Student handouts
7. Operational ATIS equipment
Two copies of draft training materials shall be submitted (CDRL 808, "Training
Materials") at FDR. Final training materials shall be submitted 20 days before classes
are scheduled to begin for Transfort approval.
The above deliverables shall be in addition to a master copy of each final version that
shall be furnished to Transfort.
RFP 7381 Advanced Traveler Information System Page 53 of 143
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
8.4 Vehicle Equipment Training and Maintenance Module
The Contractor shall supply one (1) portable ATIS module, or “bus-in-a-box” for a
training period of one month before go-live and one month after go-live, that can be
used for training simulation and system maintenance purposes (see Training Section).
The “bus-in-a-box” shall be designed and constructed to be portable and include all
ATIS vehicle equipment. The “bus-in-a-box” shall be able to communicate with the
central system and operate like any other ATIS equipped vehicle using simulated
motion through any run/block file loaded after a successful logon.
Dispatcher Communications and Computer Aided Dispatch
The Computer Aided Dispatch (CAD) subsystem shall provide the ability to:
Monitor vehicle location, status, schedule adherence
Aid in the early restoration of service disruptions through Computer Aided Service
Restoration (CASR)
Record and store operational data, analyze data, and provide management reports.
The CAD subsystem shall capture and store real-time data for historical reporting,
planning and analysis, playback of data for dispute resolution, and data and voice
communications management.
The ATIS system shall provide the capability for dynamic dispatcher assignments based
upon fleet, route, and transportation mode or vehicle type. Distribution of un-assigned
vehicle calls shall be assigned to logged-in dispatchers. The capability to configure all
dispatcher consoles to see emergency alarms shall be provided.
The CAD software shall enable Dispatchers to set pre-approved display preferences
including font size, map options, and window layout and retain those preferences upon
subsequent dispatcher logon.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
9.0 SAFETY REQUIREMENTS
The ATIS system equipment will be placed in revenue service on Transfort’s transit
vehicles and may, depending on the ATIS technology used, be visible to the public
during its operation. Should it be visible to the public, it shall be designed to maintain a
pleasing appearance over the course of its operational life, and shall not have sharp
edges that could cause harm to the riding public or their possessions, either directly or
indirectly.
RFP 7381 Advanced Traveler Information System Page 54 of 143
The ATIS equipment shall be installed so as to not interfere in any way with the
movement of passengers or the driver’s operation of the vehicle.
All ATIS equipment, which is located in the interior of a bus, shall be placed so that it is
easily accessible for maintenance and completely out of the flow of passengers. It shall
not be possible for unauthorized persons, including bus operators, to see or interfere
with any controls, plugs, connectors or wiring. Access to on-board equipment shall be
via opening locks, unfastening interior panels, or opening compartment access doors of
the bus by authorized personnel. With the exception of the MDT, the ATIS system
equipment shall be almost undetectable and tamper resistant.
There shall be no exposed control pads, indicator lights, or electrical connections visible
to Transfort operators or the riding public. The Contractor shall be responsible to
provide suitable locked storage containers for tools, materials, and equipment used in
the installation of the ATIS system. Transfort will not assume responsibility for the
security of these items.
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
10.0 SUBMITTAL REQUIREMENTS
The City’s intent is to choose the most qualified firm based upon approach, methods,
qualifications and experience, availability, and general cost estimate. Once a firm is
selected, a detailed scope of services will be developed. Of prime importance is the
firm’s flexibility in responding to requests by City staff during the process.
The final scope of services will identify a project schedule, tasks, deliverables, and
expected expenditures by task. The scope will also indicate respective
responsibilities of the selected firm and City staff.
All respondents are required to include the following information in the submittal as a
minimum. Respondents are to number and name each section as follows:
1. Methods and Approach - Describe your expected or recommended approach and
tasks. Describe the anticipated interaction with the City. Provide an outline of
your anticipated schedule for completing project tasks.
2. Deliverables - Provide a list and description of expected deliverables, tools, or
other items that you will use to provide services and outcomes of your approach.
All respondents are required to complete the Criteria Checkoffs shown below
each section of the RFP, and note any exceptions or enhancements, as part of
their proposal submittal:
RFP 7381 Advanced Traveler Information System Page 55 of 143
Proposed system meets criteria (choose one) Yes No With Exceptions
Please describe any exceptions or enhancements
Also, all respondents are required to complete all applicable tables in Appendix A
and B as part of their proposal submittal.
3. Qualifications and Experience - Provide relevant information regarding previous
experience related to developing a similar Project:
• Names and location of similar projects.
• Name, address, and phone number of public agency reference(s) overseeing
the Project.
• Samples (preferably three via a web link or “pdf” files) of similar Projects.
4. List of Project Personnel - This list should include the identification of the contact
person with primary responsibility for this contract, the personnel proposed for
this contract, and any supervisory personnel, including partners and/or
subcontractors, and their individual areas of responsibility. A résumé for each
professional and technical person assigned to the contract, including partners
and/or subcontractors, shall be submitted. The résumés shall include at least
three references from previous assignments.
5. Organization Chart/Proposed Project Team - An organization chart containing
the names of all key personnel and subcontractors with titles and their specific
task assignment for this contract shall be provided in this section.
6. Availability – Describe the availability of project personnel to participate in this
project in the context of the firm’s other commitments.
7. Estimated Hours by Task - Provide estimated hours for each proposed or
optional task, including the time required for meetings, conference calls, etc.
8. Schedule of Rates and Cost by Task - Provide a schedule of rates and an
anticipated cost of each task identified in the section “Scope of Work
Considerations” or for tasks that are recommended as part of this Project.
RFP 7381 Advanced Traveler Information System Page 56 of 143
Vendor Statement:
I have read and understand the specifications and requirements for this RFP and
I agree to comply with such specifications and requirements. I further agree that
the method of award is acceptable to my company. I also agree to complete
SERVICES AGREEMENT with the City of Fort Collins within 30 days of notice of
award. If contract is not completed and signed within 30 days, City reserves the
right to cancel and award to the next highest rated firm.
NOTE: VENDOR STATEMENT IS TO BE SIGNED & RETURNED WITH YOUR
PROPOSAL. VENDOR IS TO ALSO INCLUDE THE REQUIRED INSURANCE
CERTIFICATE NAMING THE CITY OF FORT COLLINS AS AN ADDITIONAL
INSURED.
FIRM NAME:
ADDRESS:
EMAIL ADDRESS: PHONE:
BIDDER’S NAME:
SIGNATURE:
PRIMARY SERVICES ISSUES CONTACT:
TELEPHONE: FAX:
EMAIL:
CELL: EMERGENCY:
BACKUP:
Compensation and Contract Process
1. After contract award, progress invoices shall be billed in quarterly installments,
subject to review and approval by the City’s Project Manager. City payment
terms will be Net 30 Days from receipt of invoice.
2. The City reserves the right to award directly as a result of the written proposals.
The City may or may not opt to conduct oral interviews.
3. The selected Contractor shall be expected to sign the City’s standard Services
Agreement prior to commencing Services (see sample attached to this
Proposal).
RFP 7381 Advanced Traveler Information System Page 57 of 143
Review and Assessment
Proposers will be evaluated on the following criteria. These criteria will be the basis for
review of the written proposals and any optional interview session. The rating scale
shall be from 1 to 5, with 1 being a poor rating, 3 being an average rating, and 5 being
an outstanding rating.
WEIGHTING
FACTOR QUALIFICATION STANDARD
2.0 Scope of Proposal
Does the proposal show an understanding of
the project objective, methodology to be used
and results that are desired from the project?
2.0 Assigned
Personnel
Do the persons who will be working on the
project have the necessary skills? Are
sufficient people of the requisite skills assigned
to the project?
1.0 Availability
Can the work be completed in the necessary
time? Can the target start and completion
dates be met? Are other qualified personnel
available to assist in meeting the project
schedule if required? Is the project team
available to attend meetings as required by the
Scope of Work?
1.0 Motivation Is the firm interested and are they capable of
doing the work in the required time frame?
2.0 Cost and Work
Hours
Do the proposed cost and work hours compare
favorably with the Project Manager's estimate?
Are the work hours presented reasonable for
the effort required in each project task or
phase?
2.0 Firm Capability
Does the firm have the support capabilities the
assigned personnel require? Has the firm
done previous projects of this type and scope?
RFP 7381 Advanced Traveler Information System Page 58 of 143
Reference Evaluation (Top Ranked Firm)
The Project Manager will check references using the following criteria. The evaluation
rankings will be labeled Satisfactory/Unsatisfactory.
QUALIFICATION STANDARD
Overall Performance
Would you hire this Professional again?
Did they show the skills required by this
project?
Timetable
Was the original Scope of Work
completed within the specified time?
Were interim deadlines met in a timely
manner?
Completeness
Was the Professional responsive to
client needs; did the Professional
anticipate problems? Were problems
solved quickly and effectively?
Budget Was the original Scope of Work
completed within the project budget?
Job Knowledge If a study, did it meet the Scope of
Work?
PLEASE GO TO www.fcgov.com/purchasing TO REGISTER IN OUR E-
PROCUREMENT SYSTEM FOR FUTURE BID OPPORTUNITIES! BE SURE TO
SELECT ALL APPROPRIATE COMMODITY CODES.
COMMODITY CODES USED FOR THIS RFP:
550-90 Transportation Systems, Intelligent (An automated information system which
provides traffic management, communications, and analysis of data as a minimum
920-32 Intelligent Transportation System Software (To Include Design, Development, and
Maintenance Services)
Services Agreement
Page 59 of 143
FEDERAL TRANSIT ADMINISTRATION
Federally Required and Other Model Contract Clauses
1. NO GOVERNMENT OBLIGATION TO THIRD PARTIES
No Obligation by the Federal Government.
(1) The Purchaser and Contractor acknowledge and agree that, notwithstanding any
concurrence by the Federal Government in or approval of the solicitation or award of the
underlying contract, absent the express written consent by the Federal Government, the Federal
Government is not a party to this contract and shall not be subject to any obligations or liabilities
to the Purchaser, Contractor, or any other party (whether or not a party to that contract)
pertaining to any matter resulting from the underlying contract.
(2) The Contractor agrees to include the above clause in each subcontract financed in whole or
in part with Federal assistance provided by FTA. It is further agreed that the clause shall not be
modified, except to identify the subcontractor who will be subject to its provisions.
2. PROGRAM FRAUD AND FALSE OR FRAUDULENT STATEMENTS AND RELATED
ACTS
Program Fraud and False or Fraudulent Statements or Related Acts.
(1) The Contractor acknowledges that the provisions of the Program Fraud Civil Remedies Act
of 1986, as amended, 31 U.S.C. § 3801 et seq. and U.S. DOT regulations, "Program Fraud Civil
Remedies," 49 C.F.R. Part 31, apply to its actions pertaining to this Project. Upon execution of
the underlying contract, the Contractor certifies or affirms the truthfulness and accuracy of any
statement it has made, it makes, it may make, or causes to be made, pertaining to the
underlying contract or the FTA assisted project for which this contract work is being performed.
In addition to other penalties that may be applicable, the Contractor further acknowledges that if
it makes, or causes to be made, a false, fictitious, or fraudulent claim, statement, submission, or
certification, the Federal Government reserves the right to impose the penalties of the Program
Fraud Civil
Remedies Act of 1986 on the Contractor to the extent the Federal Government deems
appropriate.
(2) The Contractor also acknowledges that if it makes, or causes to be made, a false, fictitious,
or fraudulent claim, statement, submission, or certification to the Federal Government under a
contract connected with a project that is financed in whole or in part with Federal assistance
originally awarded by FTA under the authority of 49 U.S.C. § 5307, the Government reserves
the right to impose the penalties of 18 U.S.C. § 1001 and 49 U.S.C. § 5307(n)(1) on the
Contractor, to the extent the Federal Government deems appropriate.
(3) The Contractor agrees to include the above two clauses in each subcontract financed in
whole or in part with Federal assistance provided by FTA. It is further agreed that the clauses
shall not be modified, except to identify the subcontractor who will be subject to the provisions.
3. ACCESS TO RECORDS AND REPORTS
Access to Records - The following access to records requirements apply to this Contract:
Services Agreement
Page 60 of 143
A. Where the Purchaser is not a State but a local government and is the FTA Recipient or a
subgrantee of the FTA Recipient in accordance with 49 C.F.R. 18.36(i), the Contractor
agrees to provide the Purchaser, the FTA Administrator, the Comptroller General of the
United States or any of their authorized representatives access to any books,
documents, papers and records of the Contractor which are directly pertinent to this
contract for the purposes of making audits, examinations, excerpts and transcriptions.
Contractor also agrees, pursuant to 49 C.F.R. 633.17 to provide the FTA Administrator
or his authorized representatives including any PMO Contractor access to Contractor's
records and construction sites pertaining to a major capital project, defined at 49 U.S.C.
5302(a)1, which is receiving federal financial assistance through the programs described
at 49 U.S.C. 5307, 5309 or 5311.
B. The Contractor agrees to permit any of the foregoing parties to reproduce by any means
whatsoever or to copy excerpts and transcriptions as reasonably needed.
C. The Contractor agrees to maintain all books, records, accounts and reports required
under this contract for a period of not less than three years after the date of termination
or expiration of this contract, except in the event of litigation or settlement of claims
arising from the performance of this contract, in which case Contractor agrees to
maintain same until the Purchaser, the FTA Administrator, the Comptroller General, or
any of their duly authorized representatives, have disposed of all such litigation, appeals,
claims or exceptions related thereto. Reference 49 CFR 18.39(i)(11).
D. FTA does not require the inclusion of these requirements in subcontracts.
Requirements for Access to Records and Reports by Types of Contract
Contract
Characteristics
Operatio
nal
Service
Contract
Turnkey Constructio
n
Architectural
Engineering
Acquisition
of Rolling
Stock
Professional
Services
I State Grantees
a. Contracts below
SAT ($100,000)
b. Contracts above
$100,000/Capital
Projects
None
None
unless1
non-
competiti
ve award
Those
imposed on
state pass
thru to
Contractor
None
Yes, if non-
competitive
award or if
Services Agreement
Page 61 of 143
Sources of Authority: 1 49 USC 5325 (a) 2 49 CFR 633.17 3 18 CFR 18.36 (i)
4. FEDERAL CHANGES
Federal Changes - Contractor shall at all times comply with all applicable FTA regulations,
policies, procedures and directives, including without limitation those listed directly or by
reference in the Master Agreement between Purchaser and FTA, as they may be amended or
promulgated from time to time during the term of this contract. Contractor's failure to so comply
shall constitute a material breach of this contract.
5. TERMINATION
a. Termination for Convenience (General Provision) The City may terminate
this contract, in whole or in part, at any time by written notice to the Contractor when it is in the
Government's best interest. The Contractor shall be paid its costs, including contract close-out
costs, and profit on work performed up to the time of termination. The Contractor shall promptly
submit its termination claim to the City to be paid the Contractor. If the Contractor has any
property in its possession belonging to the City, the Contractor will account for the same, and
dispose of it in the manner the City directs.
b. Termination for Default [Breach or Cause] (General Provision) If the Contractor
does not deliver supplies in accordance with the contract delivery schedule, or, if the contract is
for services, the Contractor fails to perform in the manner called for in the contract, or if the
Contractor fails to comply with any other provisions of the contract, the City may terminate this
contract for default. Termination shall be effected by serving a notice of termination on the
contractor setting forth the manner in which the Contractor is in default. The contractor will only
be paid the contract price for supplies delivered and accepted, or services performed in
accordance with the manner of performance set forth in the contract.
If it is later determined by the City that the Contractor had an excusable reason for not
performing, such as a strike, fire, or flood, events which are not the fault of or are beyond the
control of the Contractor, the City, after setting up a new delivery of performance schedule, may
allow the Contractor to continue work, or treat the termination as a termination for convenience.
c. Opportunity to Cure (General Provision) The City in its sole discretion may, in the
case of a termination for breach or default, allow the Contractor [an appropriately short period of
time] in which to cure the defect. In such case, the notice of termination will state the time
period in which cure is permitted and other appropriate conditions
If Contractor fails to remedy to the City’s satisfaction the breach or default of any of the terms,
covenants, or conditions of this Contract within [ten (10) days] after receipt by Contractor of
written notice from the City setting forth the nature of said breach or default, the City shall have
the right to terminate the Contract without any further obligation to Contractor. Any such
termination for default shall not in any way operate to preclude the City from also pursuing all
available remedies against Contractor and its sureties for said breach or default.
d. Waiver of Remedies for any Breach In the event that the City elects to waive its
remedies for any breach by Contractor of any covenant, term or condition of this Contract, such
waiver by the City shall not limit the City’s remedies for any succeeding breach of that or of any
other term, covenant, or condition of this Contract.
Services Agreement
Page 62 of 143
6. CIVIL RIGHTS REQUIREMENTS
Civil Rights - The following requirements apply to the underlying contract:
(1) Nondiscrimination - In accordance with Title VI of the Civil Rights Act, as amended, 42
U.S.C. § 2000d, section 303 of the Age Discrimination Act of 1975, as amended, 42 U.S.C. §
6102, section 202 of the Americans with Disabilities Act of 1990, 42 U.S.C. § 12132, and
Federal transit law at 49 U.S.C. § 5332, the Contractor agrees that it will not discriminate
against any employee or applicant for employment because of race, color, creed, national
origin, sex, age, or disability. In addition, the Contractor agrees to comply with applicable
Federal implementing regulations and other implementing requirements FTA may issue.
(2) Equal Employment Opportunity - The following equal employment opportunity requirements
apply to the underlying contract:
(a) Race, Color, Creed, National Origin, Sex - In accordance with Title VII of the Civil
Rights Act, as amended, 42 U.S.C. § 2000e, and Federal transit laws at 49 U.S.C. §
5332, the Contractor agrees to comply with all applicable equal employment opportunity
requirements of U.S. Department of Labor (U.S. DOL) regulations, "Office of Federal
Contract Compliance Programs, Equal Employment Opportunity, Department of Labor,"
41 C.F.R. Parts 60 et seq., (which implement Executive Order No. 11246, "Equal
Employment Opportunity," as amended by Executive Order No. 11375, "Amending
Executive Order 11246 Relating to Equal Employment Opportunity," 42 U.S.C. § 2000e
note), and with any applicable Federal statutes, executive orders, regulations, and
Federal policies that may in the future affect construction activities undertaken in the
course of the Project. The Contractor agrees to take affirmative action to ensure that
applicants are employed, and that employees are treated during employment, without
regard to their race, color, creed, national origin, sex, or age. Such action shall include,
but not be limited to, the following: employment, upgrading, demotion or transfer,
recruitment or recruitment advertising, layoff or termination; rates of pay or other forms
of compensation; and selection for training, including apprenticeship. In addition, the
Contractor agrees to comply with any implementing requirements FTA may issue.
(b) Age - In accordance with section 4 of the Age Discrimination in Employment Act of
1967, as amended, 29 U.S.C. § § 623 and Federal transit law at 49 U.S.C. § 5332, the
Contractor agrees to refrain from discrimination against present and prospective
employees for reason of age. In addition, the Contractor agrees to comply with any
implementing requirements FTA may issue.
(c) Disabilities - In accordance with section 102 of the Americans with Disabilities Act, as
amended, 42 U.S.C. § 12112, the Contractor agrees that it will comply with the
requirements of U.S. Equal Employment Opportunity Commission, "Regulations to
Implement the Equal Employment Provisions of the Americans with Disabilities Act," 29
C.F.R. Part 1630, pertaining to employment of persons with disabilities. In addition, the
Contractor agrees to comply with any implementing requirements FTA may issue.
(3) The Contractor also agrees to include these requirements in each subcontract financed in
whole or in part with Federal assistance provided by FTA, modified only if necessary to identify
the affected parties.
Services Agreement
Page 63 of 143
7. DISADVANTAGED BUSINESS ENTERPRISE (DBE)
a. This contract is subject to the requirements of Title 49, Code of Federal Regulations,
Part 26, Participation by Disadvantaged Business Enterprises in Department of
Transportation Financial Assistance Programs. The national goal for participation of
Disadvantaged Business Enterprises (DBE) is 10%. The City has an overall DBE goal
of 9.9%.
There is no specific contract goal for this project but the City encourages bids from DBE
firms in this project.
b. The contractor shall not discriminate on the basis of race, color, national origin, or sex
in the performance of this contract. The contractor shall carry out applicable
requirements of 49 CFR Part 26 in the award and administration of this DOT-assisted
contract. Failure by the contractor to carry out these requirements is a material breach
of this contract, which may result in the termination of this contract or such other remedy
as City of Fort Collins deems appropriate. Each subcontract the contractor signs with
a subcontractor must include the assurance in this paragraph (see 49 CFR 26.13(b)).
The successful bidder/offeror will be required to report its DBE participation obtained
through race-neutral means throughout the period of performance.
d. The contractor is required to pay its subcontractors performing work related to this
contract for satisfactory performance of that work no later than 30 days after the
contractor’s receipt of payment for that work from the City of Fort Collins. In addition, it
is required to return any retainage payments to those subcontractors within 30
days after incremental acceptance of the subcontractor’s work by the City of Fort
Collins and contractor’s receipt of the partial retainage payment related to the
subcontractor’s work.
e. The contractor must promptly notify City of Fort Collins whenever a DBE
subcontractor performing work related to this contract is terminated or fails to complete
its work, and must make good faith efforts to engage another DBE subcontractor to
perform at least the same amount of work. The contractor may not terminate any DBE
subcontractor and perform that work through its own forces or those of an affiliate
without prior written consent of City of Fort Collins.
8. INCORPORATION OF FEDERAL TRANSIT ADMINISTRATION (FTA) TERMS
Incorporation of Federal Transit Administration (FTA) Terms - The preceding provisions include,
in part, certain Standard Terms and Conditions required by DOT, whether or not expressly set
forth in the preceding contract provisions. All contractual provisions required by DOT, as set
forth in FTA Circular 4220.1E, are hereby incorporated by reference. Anything to the contrary
herein notwithstanding, all FTA mandated terms shall be deemed to control in the event of a
conflict with other provisions contained in this Agreement. The Contractor shall not perform any
act, fail to perform any act, or refuse to comply with any (name of grantee) requests which
would cause (name of grantee) to be in violation of the FTA terms and conditions.
Services Agreement
Page 64 of 143
9. GOVERNMENT-WIDE DEBARMENT AND SUSPENSION (NONPROCUREMENT)
Background and Applicability
In conjunction with the Office of Management and Budget and other affected Federal agencies,
DOT published an update to 49 CFR Part 29 on November 26, 2003. This government-wide
regulation implements Executive Order 12549, Debarment and Suspension, Executive Order
12689, Debarment and Suspension, and 31 U.S.C. 6101 note (Section 2455, Public Law 103-
355, 108 Stat. 3327).
The provisions of Part 29 apply to all grantee contracts and subcontracts at any level expected
to equal or exceed $25,000 as well as any contract or subcontract (at any level) for Federally
required auditing services. 49 CFR 29.220(b). This represents a change from prior practice in
that the dollar threshold for application of these rules has been lowered from $100,000 to
$25,000. These are contracts and subcontracts referred to in the regulation as “covered
transactions.”
Grantees, contractors, and subcontractors (at any level) that enter into covered transactions are
required to verify that the entity (as well as its principals and affiliates) they propose to contract
or subcontract with is not excluded or disqualified. They do this by (a) Checking the Excluded
Parties List System, (b) Collecting a certification from that person, or (c) Adding a clause or
condition to the contract or subcontract. This represents a change from prior practice in that
certification is still acceptable but is no longer required. 49 CFR 29.300.
Grantees, contractors, and subcontractors who enter into covered transactions also must
require the entities they contract with to comply with 49 CFR 29, subpart C and include this
requirement in their own subsequent covered transactions (i.e., the requirement flows down to
subcontracts at all levels).
Clause Language
The following clause language is suggested, not mandatory. It incorporates the optional method
of verifying that contractors are not excluded or disqualified by certification.
Suspension and Debarment
This contract is a covered transaction for purposes of 49 CFR Part 29. As such, the
contractor is required to verify that none of the contractor, its principals, as defined at 49
CFR 29.995, or affiliates, as defined at 49 CFR 29.905, are excluded or disqualified as
defined at 49 CFR 29.940 and 29.945.
The contractor is required to comply with 49 CFR 29, Subpart C and must include the
requirement to comply with 49 CFR 29, Subpart C in any lower tier covered transaction it
enters into.
By signing and submitting its bid or proposal, the bidder or proposer certifies as follows:
The certification in this clause is a material representation of fact relied upon by {insert agency
name}. If it is later determined that the bidder or proposer knowingly rendered an erroneous
certification, in addition to remedies available to {insert agency name}, the Federal Government
may pursue available remedies, including but not limited to suspension and/or debarment. The
bidder or proposer agrees to comply with the requirements of 49 CFR 29, Subpart C while this
offer is valid and throughout the period of any contract that may arise from this offer. The bidder
Services Agreement
Page 65 of 143
or proposer further agrees to include a provision requiring such compliance in its lower tier
covered transactions.
10. BREACHES AND DISPUTE RESOLUTION
Disputes - Disputes arising in the performance of this Contract which are not resolved by
agreement of the parties shall be decided in writing by the authorized representative of City's
[title of employee]. This decision shall be final and conclusive unless within [ten (10)] days from
the date of receipt of its copy, the Contractor mails or otherwise furnishes a written appeal to the
[title of employee]. In connection with any such appeal, the Contractor shall be afforded an
opportunity to be heard and to offer evidence in support of its position. The decision of the [title
of employee] shall be binding upon the Contractor and the Contractor shall abide be the
decision.
Performance During Dispute - Unless otherwise directed by City, Contractor shall continue
performance under this Contract while matters in dispute are being resolved.
Claims for Damages - Should either party to the Contract suffer injury or damage to person or
property because of any act or omission of the party or of any of his employees, agents or
others for whose acts he is legally liable, a claim for damages therefor shall be made in writing
to such other party within a reasonable time after the first observance of such injury of damage.
Remedies - Unless this contract provides otherwise, all claims, counterclaims, disputes and
other matters in question between the City and the Contractor arising out of or relating to this
agreement or its breach will be decided by arbitration if the parties mutually agree, or in a court
of competent jurisdiction within the State in which the City is located.
Rights and Remedies - The duties and obligations imposed by the Contract Documents and
the rights and remedies available thereunder shall be in addition to and not a limitation of any
duties, obligations, rights and remedies otherwise imposed or available by law. No action or
failure to act by the City, (Architect) or Contractor shall constitute a waiver of any right or duty
afforded any of them under the Contract, nor shall any such action or failure to act constitute an
approval of or acquiescence in any breach thereunder, except as may be specifically agreed in
writing.
11. LOBBYING
Modifications have been made to the Clause pursuant to Section 10 of the Lobbying Disclosure
Act of 1995, P.L. 104-65 [to be codified at 2 U.S.C. § 1601, et seq.]
- Lobbying Certification and Disclosure of Lobbying Activities for third party contractors are
mandated by 31 U.S.C. 1352(b)(5), as amended by Section 10 of the Lobbying Disclosure Act
of 1995, and DOT implementing regulation, "New Restrictions on Lobbying," at 49 CFR §
20.110(d)
- Language in Lobbying Certification is mandated by 49 CFR Part 19, Appendix A, Section 7,
which provides that contractors file the certification required by 49 CFR Part 20, Appendix A.
Modifications have been made to the Lobbying Certification pursuant to Section 10 of the
Lobbying Disclosure Act of 1995.
Services Agreement
Page 66 of 143
- Use of "Disclosure of Lobbying Activities," Standard Form-LLL set forth in Appendix B of 49
CFR Part 20, as amended by "Government wide Guidance For New Restrictions on Lobbying,"
61 Fed. Reg. 1413 (1/19/96) is mandated by 49 CFR Part 20, Appendix A.
Byrd Anti-Lobbying Amendment, 31 U.S.C. 1352, as amended by the Lobbying Disclosure
Act of 1995, P.L. 104-65 [to be codified at 2 U.S.C. § 1601, et seq.] - Contractors who apply
or bid for an award of $100,000 or more shall file the certification required by 49 CFR part 20,
"New Restrictions on Lobbying." Each tier certifies to the tier above that it will not and has not
used Federal appropriated funds to pay any person or organization for influencing or attempting
to influence an officer or employee of any agency, a member of Congress, officer or employee
of Congress, or an employee of a member of Congress in connection with obtaining any Federal
contract, grant or any other award covered by 31 U.S.C. 1352. Each tier shall also disclose the
name of any registrant under the Lobbying Disclosure Act of 1995 who has made lobbying
contacts on its behalf with non-Federal funds with respect to that Federal contract, grant or
award covered by 31 U.S.C. 1352. Such disclosures are forwarded from tier to tier up to the
recipient.
APPENDIX A, 49 CFR PART 20--CERTIFICATION REGARDING LOBBYING
Certification for Contracts, Grants, Loans, and Cooperative Agreements
(To be submitted with each bid or offer exceeding $100,000)
The undersigned [Contractor] certifies, to the best of his or her knowledge and belief, that:
(1) No Federal appropriated funds have been paid or will be paid, by or on behalf of the
undersigned, to any person for influencing or attempting to influence an officer or employee of
an agency, a Member of Congress, an officer or employee of Congress, or an employee of a
Member of Congress in connection with the awarding of any Federal contract, the making of any
Federal grant, the making of any Federal loan, the entering into of any cooperative agreement,
and the extension, continuation, renewal, amendment, or modification of any Federal contract,
grant, loan, or cooperative agreement.
(2) If any funds other than Federal appropriated funds have been paid or will be paid to any
person for making lobbying contacts to an officer or employee of any agency, a Member of
Congress, an officer or employee of Congress, or an employee of a Member of Congress in
connection with this Federal contract, grant, loan, or cooperative agreement, the undersigned
shall complete and submit Standard Form--LLL, "Disclosure Form to Report Lobbying," in
accordance with its instructions [as amended by "Government wide Guidance for New
Restrictions on Lobbying," 61 Fed. Reg. 1413 (1/19/96). Note: Language in paragraph (2)
herein has been modified in accordance with Section 10 of the Lobbying Disclosure Act of 1995
(P.L. 104-65, to be codified at 2 U.S.C. 1601, et seq.)]
(3) The undersigned shall require that the language of this certification be included in the award
documents for all subawards at all tiers (including subcontracts, subgrants, and contracts under
grants, loans, and cooperative agreements) and that all subrecipients shall certify and disclose
accordingly.
This certification is a material representation of fact upon which reliance was placed when this
transaction was made or entered into. Submission of this certification is a prerequisite for
making or entering into this transaction imposed by 31, U.S.C. § 1352 (as amended by the
Lobbying Disclosure Act of 1995). Any person who fails to file the required certification shall be
Services Agreement
Page 67 of 143
subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such
failure.
[Note: Pursuant to 31 U.S.C. § 1352(c)(1)-(2)(A), any person who makes a prohibited
expenditure or fails to file or amend a required certification or disclosure form shall be subject to
a civil penalty of not less than $10,000 and not more than $100,000 for each such expenditure
or failure.]
The Contractor, ___________________, certifies or affirms the truthfulness and accuracy of
each statement of its certification and disclosure, if any. In addition, the Contractor understands
and agrees that the provisions of 31 U.S.C. A 3801, et seq., apply to this certification and
disclosure, if any.
__________________________ Signature of Contractor's Authorized Official
__________________________ Name and Title of Contractor's Authorized Official
___________________________ Date
12. CLEAN AIR
Clean Air –
(1) The Contractor agrees to comply with all applicable standards, orders or regulations
issued pursuant to the Clean Air Act, as amended, 42 U.S.C. §§ 7401 et seq. The
Contractor agrees to report each violation to the Purchaser and understands and agrees
that the Purchaser will, in turn, report each violation as required to assure notification to FTA
and the appropriate EPA Regional Office.
(2) The Contractor also agrees to include these requirements in each subcontract exceeding
$100,000 financed in whole or in part with Federal assistance provided by FTA.
13. CLEAN WATER REQUIREMENTS
Clean Water - (1) The Contractor agrees to comply with all applicable standards, orders or
regulations issued pursuant to the Federal Water Pollution Control Act, as amended, 33 U.S.C.
1251 et seq. The Contractor agrees to report each violation to the Purchaser and understands
and agrees that the Purchaser will, in turn, report each violation as required to assure
notification to FTA and the appropriate EPA Regional Office.
(2) The Contractor also agrees to include these requirements in each subcontract exceeding
$100,000 financed in whole or in part with Federal assistance provided by FTA.
14. CARGO PREFERENCE REQUIREMENTS
Cargo Preference - Use of United States-Flag Vessels - The contractor agrees: a. to use
privately owned United States-Flag commercial vessels to ship at least 50 percent of the gross
tonnage (computed separately for dry bulk carriers, dry cargo liners, and tankers) involved,
whenever shipping any equipment, material, or commodities pursuant to the underlying contract
to the extent such vessels are available at fair and reasonable rates for United States-Flag
commercial vessels; b. to furnish within 20 working days following the date of loading for
shipments originating within the United States or within 30 working days following the date of
leading for shipments originating outside the United States, a legible copy of a rated, "on-board"
Services Agreement
Page 68 of 143
commercial ocean bill-of -lading in English for each shipment of cargo described in the
preceding paragraph to the Division of National Cargo, Office of Market Development, Maritime
Administration, Washington, DC 20590 and to the FTA recipient (through the contractor in the
case of a subcontractor's bill-of-lading.) c. to include these requirements in all subcontracts
issued pursuant to this contract when the subcontract may involve the transport of equipment,
material, or commodities by ocean vessel.
15. FLY AMERICA REQUIREMENTS
The Contractor agrees to comply with 49 U.S.C. 40118 (the “Fly America” Act) in accordance
with the General Services Administration’s regulations at 41 CFR Part 301-10, which provide
that recipients and subrecipients of Federal funds and their contractors are required to use U.S.
Flag air carriers for U.S Government-financed international air travel and transportation of their
personal effects or property, to the extent such service is available, unless travel by foreign air
carrier is a matter of necessity, as defined by the Fly America Act. The Contractor shall submit,
if a foreign air carrier was used, an appropriate certification or memorandum adequately
explaining why service by a U.S. flag air carrier was not available or why it was necessary to
use a foreign air carrier and shall, in any event, provide a certificate of compliance with the Fly
America requirements. The Contractor agrees to include the requirements of this section in all
subcontracts that may involve international air transportation.
16. CONTRACT WORK HOURS AND SAFETY STANDARDS ACT
Background and Application
The Contract Work Hours and Safety Standards Act is codified at 40 USC 3701, et seq. The
Act applies to grantee contracts and subcontracts “financed at least in part by loans or grants
from … the [Federal] Government.” 40 USC 3701(b)(1)(B)(iii) and (b)(2), 29 CFR 5.2(h), 49
CFR 18.36(i)(6). Although the original Act required its application in any construction contract
over $2,000 or non-construction contract to which the Act applied over $2,500 (and language to
that effect is still found in 49 CFR 18.36(i)(6)), the Act no longer applies to any “contract in an
amount that is not greater than $100,000.” 40 USC 3701(b)(3) (A)(iii).
The Act applies to construction contracts and, in very limited circumstances, non-construction
projects that employ “laborers or mechanics on a public work.” These non-construction
applications do not generally apply to transit procurements because transit procurements (to
include rail cars and buses) are deemed “commercial items.” 40 USC 3707, 41 USC 403 (12).
A grantee that contemplates entering into a contract to procure a developmental or unique item
should consult counsel to determine if the Act applies to that procurement and that additional
language required by 29 CFR 5.5(c) must be added to the basic clause below.
The clause language is drawn directly from 29 CFR 5.5(b) and any deviation from the model
clause below should be coordinated with counsel to ensure the Act’s requirements are satisfied.
Clause Language Contract Work Hours and Safety Standards
(1) Overtime requirements - No contractor or subcontractor contracting for any part of the
contract work which may require or involve the employment of laborers or mechanics shall
require or permit any such laborer or mechanic in any workweek in which he or she is employed
on such work to work in excess of forty hours in such workweek unless such laborer or
mechanic receives compensation at a rate not less than one and one-half times the basic rate of
pay for all hours worked in excess of forty hours in such workweek.
Services Agreement
Page 69 of 143
(2) Violation; liability for unpaid wages; liquidated damages - In the event of any violation of
the clause set forth in paragraph (1) of this section the contractor and any subcontractor
responsible therefore- shall be liable for the unpaid wages. In addition, such contractor and
subcontractor shall be liable to the United States for liquidated damages. Such liquidated
damages shall be computed with respect to each individual laborer or mechanic, including
watchmen and guards, employed in violation of the clause set forth in paragraph (1) of this
section, in the sum of $10 for each calendar day on which such individual was required or
permitted to work in excess of the standard workweek of forty hours without payment of the
overtime wages required by the clause set forth in paragraph (1) of this section.
(3) Withholding for unpaid wages and liquidated damages - The (write in the name of the
grantee) shall upon its own action or upon written request of an authorized representative of the
Department of Labor withhold or cause to be withheld, from any moneys payable on account of
work performed by the contractor or subcontractor under any such contract or any other Federal
contract with the same prime contractor, or any other federally-assisted contract subject to the
Contract Work Hours and Safety Standards Act, which is held by the same prime contractor,
such sums as may be determined to be necessary to satisfy any liabilities of such contractor or
subcontractor for unpaid wages and liquidated damages as provided in the clause set forth in
paragraph (2) of this section.
(4) Subcontracts - The contractor or subcontractor shall insert in any subcontracts the clauses
set forth in paragraphs (1) through (4) of this section and also a clause requiring the
subcontractors to include these clauses in any lower tier subcontracts. The prime contractor
shall be responsible for compliance by any subcontractor or lower tier subcontractor with the
clauses set forth in paragraphs (1) through (4) of this section.
17. ENERGY CONSERVATION REQUIREMENTS
Energy Conservation - The contractor agrees to comply with mandatory standards and
policies relating to energy efficiency which are contained in the state energy conservation plan
issued in compliance with the Energy Policy and Conservation Act.
18. RECYCLED PRODUCTS
Recovered Materials - The contractor agrees to comply with all the requirements of Section
6002 of the Resource Conservation and Recovery Act (RCRA), as amended (42 U.S.C. 6962),
including but not limited to the regulatory provisions of 40 CFR Part 247, and Executive Order
12873, as they apply to the procurement of the items designated in Subpart B of 40 CFR Part
247.
19. CONFORMANCE WITH ITS NATIONAL ARCHITECTURE
To the extent applicable, the Contractor agrees to conform to the National Intelligent
Transportation Systems (ITS) Architecture and Standards as required by SAFETEA-LU §
5307(c), 23 U.S.C. § 512 note, and follow the provisions of FTA Notice, “FTA National ITS
Architecture Policy on Transit Projects,” 66 Fed. Reg. 1455 et seq., January 8, 2001, and any
other implementing directives FTA may issue at a later date, except to the extent FTA
determines otherwise in writing.
Services Agreement
Page 70 of 143
20. ADA ACCESS
Accessibility. Facilities to be used in public transportation service must comply with 42 U.S.C.
Sections 12101 et seq. and DOT regulations, “Transportation Services for Individuals with
Disabilities (ADA),” 49 CFR Part 37; and Joint ATBCB/DOT regulations, “Americans with
Disabilities (ADA) Accessibility Specifications for Transportation Vehicles,” 36 CFR Part 1192
and 49 CFR Part 38. Notably, DOT incorporated by reference the ATBCB’s “Americans with
Disabilities Act Accessibility Guidelines” (ADAAG), revised July 2004, which include accessibility
guidelines for buildings and facilities, and are incorporated into Appendix A to 49 CFR Part 37.
DOT also added specific provisions to Appendix A modifying the ADAAG, with the result that
buildings and facilities must comply with both the ADAAG and amendments thereto in Appendix
A to 49 CFR Part 37.
21. CITY OF FORT COLLINS BID PROTEST PROCEDURES
The City of Fort Collins has a protest procedure, covering any phase of solicitation or award,
including but not limited to specification or award. The protest procedures are available from
the Purchasing Department, City of Fort Collins, 215 N. Mason, Street, 2nd Floor, P. O. Box
580, Fort Collins, CO. 80522. You may also request a copy of the procedures by emailing:
Purchasing@fcgov.com or calling 970-221-6775.
Services Agreement
Page 71 of 143
SERVICES AGREEMENT
THIS AGREEMENT made and entered into the day and year set forth below by and
between THE CITY OF FORT COLLINS, COLORADO, a Municipal Corporation, hereinafter
referred to as the "City" and , hereinafter referred to as "Service Provider".
WITNESSETH:
In consideration of the mutual covenants and obligations herein expressed, it is agreed
by and between the parties hereto as follows:
1. Scope of Services. The Service Provider agrees to provide services in
accordance with the scope of services attached hereto as Exhibit "A", consisting of
( ) page and incorporated herein by this reference.
2. The Work Schedule. [Optional] The services to be performed pursuant to this
Agreement shall be performed in accordance with the Work Schedule attached hereto as
Exhibit "B", consisting of ( ) page , and incorporated herein by this reference.
3. Time of Commencement and Completion of Services. The services to be
performed pursuant to this Agreement shall be initiated within ( ) days following
execution of this Agreement. Services shall be completed no later than . Time is of the
essence. Any extensions of the time limit set forth above must be agreed upon in a writing
signed by the parties.
4. Contract Period. [Option 1] This Agreement shall commence upon the date of
execution shown on the signature page of this Agreement and shall continue in full force and
effect for one (1) year, unless sooner terminated as herein provided. In addition, at the option of
the City, the Agreement may be extended for an additional period of one (1) year at the rates
provided with written notice to the Professional mailed no later than ninety (90) days prior to
contract end.
5. Contract Period. [Option 2] This Agreement shall commence , 200 ,
and shall continue in full force and effect until , 200 , unless sooner terminated as
Services Agreement
Page 72 of 143
herein provided. In addition, at the option of the City, the Agreement may be extended for
additional one year periods not to exceed ( ) additional one year periods.
Renewals and pricing changes shall be negotiated by and agreed to by both parties. The
Denver Boulder Greeley CPIU published by the Colorado State Planning and Budget Office will
be used as a guide. Written notice of renewal shall be provided to the Service Provider and
mailed no later than ninety (90) days prior to contract end.
6. Delay. If either party is prevented in whole or in part from performing its
obligations by unforeseeable causes beyond its reasonable control and without its fault or
negligence, then the party so prevented shall be excused from whatever performance is
prevented by such cause. To the extent that the performance is actually prevented, the Service
Provider must provide written notice to the City of such condition within fifteen (15) days from
the onset of such condition. [Early Termination clause here as an option
7. Early Termination by City/Notice. Notwithstanding the time periods contained
herein, the City may terminate this Agreement at any time without cause by providing written
notice of termination to the Service Provider. Such notice shall be delivered at least fifteen (15)
days prior to the termination date contained in said notice unless otherwise agreed in writing by
the parties. All notices provided under this Agreement shall be effective when mailed, postage
prepaid and sent to the following addresses:
City:
City of Fort Collins
Attn: Purchasing
PO Box 580
Fort Collins, CO 80522
Copy to:
City of Fort Collins
Attn:
PO Box 580
Fort Collins, CO 80522
Service Provider:
In the event of early termination by the City, the Service Provider shall be paid for services
rendered to the date of termination, subject only to the satisfactory performance of the Service
Provider's obligations under this Agreement. Such payment shall be the Service Provider's sole
right and remedy for such termination.
8. Contract Sum. The City shall pay the Service provider for the performance of this
Services Agreement
Page 73 of 143
Contract, subject to additions and deletions provided herein, per the attached Exhibit " ",
consisting of page , and incorporated herein by this reference.
9. City Representative. The City will designate, prior to commencement of the
work, its representative who shall make, within the scope of his or her authority, all necessary
and proper decisions with reference to the services provided under this agreement. All requests
concerning this agreement shall be directed to the City Representative.
10. Independent Service provider. The services to be performed by Service Provider
are those of an independent service provider and not of an employee of the City of Fort Collins.
The City shall not be responsible for withholding any portion of Service Provider's compensation
hereunder for the payment of FICA, Workmen's Compensation or other taxes or benefits or for
any other purpose.
11. Personal Services. It is understood that the City enters into the Agreement
based on the special abilities of the Service Provider and that this Agreement shall be
considered as an agreement for personal services. Accordingly, the Service Provider shall
neither assign any responsibilities nor delegate any duties arising under the Agreement without
the prior written consent of the City.
12. Acceptance Not Waiver. The City's approval or acceptance of, or payment for
any of the services shall not be construed to operate as a waiver of any rights or benefits
provided to the City under this Agreement or cause of action arising out of performance of this
Agreement.
13. Warranty.
a. Service Provider warrants that all work performed hereunder shall be
performed with the highest degree of competence and care in accordance with accepted
standards for work of a similar nature.
Services Agreement
Page 74 of 143
b. Unless otherwise provided in the Agreement, all materials and equipment
incorporated into any work shall be new and, where not specified, of the most suitable grade of
their respective kinds for their intended use, and all workmanship shall be acceptable to City.
c. Service Provider warrants all equipment, materials, labor and other work,
provided under this Agreement, except City-furnished materials, equipment and labor, against
defects and nonconformances in design, materials and workmanship/workwomanship for a
period beginning with the start of the work and ending twelve (12) months from and after final
acceptance under the Agreement, regardless whether the same were furnished or performed by
Service Provider or by any of its subcontractors of any tier. Upon receipt of written notice from
City of any such defect or nonconformances, the affected item or part thereof shall be
redesigned, repaired or replaced by Service Provider in a manner and at a time acceptable to
City.
14. Default. Each and every term and condition hereof shall be deemed to be a
material element of this Agreement. In the event either party should fail or refuse to perform
according to the terms of this agreement, such party may be declared in default thereof.
15. Remedies. In the event a party has been declared in default, such defaulting
party shall be allowed a period of ten (10) days within which to cure said default. In the event
the default remains uncorrected, the party declaring default may elect to (a) terminate the
Agreement and seek damages; (b) treat the Agreement as continuing and require specific
performance; or (c) avail himself of any other remedy at law or equity. If the non-defaulting party
commences legal or equitable actions against the defaulting party, the defaulting party shall be
liable to the non-defaulting party for the non-defaulting party's reasonable attorney fees and
costs incurred because of the default.
16. Binding Effect. This writing, together with the exhibits hereto, constitutes the
entire agreement between the parties and shall be binding upon said parties, their officers,
employees, agents and assigns and shall inure to the benefit of the respective survivors, heirs,
Services Agreement
Page 75 of 143
personal representatives, successors and assigns of said parties.
17. Indemnity/Insurance.
a. The Service Provider agrees to indemnify and save harmless the City, its
officers, agents and employees against and from any and all actions, suits, claims, demands or
liability of any character whatsoever brought or asserted for injuries to or death of any person or
persons, or damages to property arising out of, result from or occurring in connection with the
performance of any service hereunder.
b. The Service Provider shall take all necessary precautions in performing the
work hereunder to prevent injury to persons and property.
c. Without limiting any of the Service Provider's obligations hereunder, the
Service Provider shall provide and maintain insurance coverage naming the City as an
additional insured under this Agreement of the type and with the limits specified within Exhibit
, consisting of one (1) page, attached hereto and incorporated herein by this reference.
The Service Provider before commencing services hereunder, shall deliver to the City's Director
of Purchasing and Risk Management, P. O. Box 580 Fort Collins, Colorado 80522 one copy of
a certificate evidencing the insurance coverage required from an insurance company acceptable
to the City.
18. Entire Agreement. This Agreement, along with all Exhibits and other documents
incorporated herein, shall constitute the entire Agreement of the parties. Covenants or
representations not contained in this Agreement shall not be binding on the parties.
19. Law/Severability. The laws of the State of Colorado shall govern the construction
interpretation, execution and enforcement of this Agreement. In the event any provision of this
Agreement shall be held invalid or unenforceable by any court of competent jurisdiction, such
holding shall not invalidate or render unenforceable any other provision of this Agreement.
20. Prohibition Against Employing Illegal Aliens. Pursuant to Section 8-17.5-101,
C.R.S., et. seq., Service Provider represents and agrees that:
Services Agreement
Page 76 of 143
a. As of the date of this Agreement:
1. Service Provider does not knowingly employ or contract with an illegal
alien who will perform work under this Agreement; and
2. Service Provider will participate in either the e-Verify program created
in
Public Law 208, 104th Congress, as amended, and expanded in Public Law 156, 108th
Congress, as amended, administered by the United States Department of Homeland Security
(the “e-Verify Program”) or the Department Program (the “Department Program”), an
employment verification program established pursuant to Section 8-17.5-102(5)(c) C.R.S. in
order to confirm the employment eligibility of all newly hired employees to perform work under
this Agreement.
b. Service Provider shall not knowingly employ or contract with an illegal alien to
perform work under this Agreement or knowingly enter into a contract with a subcontractor that
knowingly employs or contracts with an illegal alien to perform work under this Agreement.
c. Service Provider is prohibited from using the e-Verify Program or Department
Program procedures to undertake pre-employment screening of job applicants while this
Agreement is being performed.
d. If Service Provider obtains actual knowledge that a subcontractor performing
work under this Agreement knowingly employs or contracts with an illegal alien, Service
Provider shall:
1. Notify such subcontractor and the City within three days that Service Provider
has actual knowledge that the subcontractor is employing or contracting with an illegal alien;
and
2. Terminate the subcontract with the subcontractor if within three days of
receiving the notice required pursuant to this section the subcontractor does not cease
employing or contracting with the illegal alien; except that Service Provider shall not terminate
Services Agreement
Page 77 of 143
the contract with the subcontractor if during such three days the subcontractor provides
information to establish that the subcontractor has not knowingly employed or contracted with
an illegal alien.
e. Service Provider shall comply with any reasonable request by the Colorado
Department of Labor and Employment (the “Department”) made in the course of an
investigation that the Department undertakes or is undertaking pursuant to the authority
established in Subsection 8-17.5-102 (5), C.R.S.
f. If Service Provider violates any provision of this Agreement pertaining to the
duties imposed by Subsection 8-17.5-102, C.R.S. the City may terminate this Agreement. If this
Agreement is so terminated, Service Provider shall be liable for actual and consequential
damages to the City arising out of Service Provider’s violation of Subsection 8-17.5-102, C.R.S.
g. The City will notify the Office of the Secretary of State if Service Provider
violates this provision of this Agreement and the City terminates the Agreement for such breach.
21. Special Provisions. [Optional] Special provisions or conditions relating to the
services to be performed pursuant to this Agreement are set forth in Exhibit " ", consisting
of ( ) pages, attached hereto and incorporated herein by this reference.
Services Agreement
Page 78 of 143
CITY OF FORT COLLINS, COLORADO
a municipal corporation
By:_______________________________
James B. O'Neill II, CPPO, FNIGP
Director of Purchasing and Risk Management
Date:_____________________________
ATTEST:
_________________________________
City Clerk
APPROVED AS TO FORM:
________________________________
Assistant City Attorney
By:_______________________________
__________________________________
PRINT NAME
__________________________________
CORPORATE PRESIDENT OR VICE PRESIDENT
Date:_____________________________
ATTEST: (Corporate Seal)
_____________________________
CORPORATE SECRETARY
RFP 7381 Advanced Traveler Information System Page 79 of 143
EXHIBIT “ ”
INSURANCE REQUIREMENTS
1. The Service Provider will provide, from insurance companies acceptable to the City, the
insurance coverage designated hereinafter and pay all costs. Before commencing work under
this bid, the Service Provider shall furnish the City with certificates of insurance showing the
type, amount, class of operations covered, effective dates and date of expiration of policies, and
containing substantially the following statement:
"The insurance evidenced by this Certificate will not be cancelled or materially altered,
except after ten (10) days written notice has been received by the City of Fort Collins."
In case of the breach of any provision of the Insurance Requirements, the City, at its option,
may take out and maintain, at the expense of the Service Provider, such insurance as the City
may deem proper and may deduct the cost of such insurance from any monies which may be
due or become due the Service Provider under this Agreement. The City, its officers, agents
and employees shall be named as additional insureds on the Service Provider's general liability
and automobile liability insurance policies for any claims arising out of work performed under
this Agreement.
2. Insurance coverages shall be as follows:
A. Workers' Compensation & Employer's Liability. The Service Provider shall
maintain during the life of this Agreement for all of the Service Provider's employees
engaged in work performed under this agreement:
1. Workers' Compensation insurance with statutory limits as required by
Colorado law.
2. Employer's Liability insurance with limits of $100,000 per accident,
$500,000 disease aggregate, and $100,000 disease each employee.
B. Commercial General & Vehicle Liability. The Service Provider shall maintain
during the life of this Agreement such commercial general liability and automobile liability
insurance as will provide coverage for damage claims of personal injury, including
accidental death, as well as for claims for property damage, which may arise directly or
indirectly from the performance of work under this Agreement. Coverage for property
damage shall be on a "broad form" basis. The amount of insurance for each coverage,
Commercial General and Vehicle, shall not be less than $500,000 combined single limits
for bodily injury and property damage.
In the event any work is performed by a subcontractor, the Service Provider shall be
responsible for any liability directly or indirectly arising out of the work performed under
this Agreement by a subcontractor, which liability is not covered by the subcontractor's
insurance.
Services Agreement
Page 80 of 143
Appendix A
COST PROPOSAL SUMMARY
Contractors shall submit their price proposals on the following form. Note that units
and/or quantities shall include the numbers specified in previous sections, and shall
include spares as determined by the Contractor for effective system operation.
Transfort is exempt from federal excise, federal transportation and state sales tax and
such taxes shall not be included in price quotations.
The price breakdown in the attached table shall include the total cost to provide the
system(s). Proposers should use additional lines, or clarify entries so that all costs are
included. For example, the prices for hardware should include brackets, fasteners,
cable, and housings. The intent is to determine the total cost of the base system and
each of the options.
It is understood that the prices detailed on the Cost Proposal constitutes the proposers
total price for completing the work described in the RFP. Transfort will not incur other
additional costs for any additional equipment, services, shipping, handling or
installation.
The Contractor will identify all computer and network requirements; however Transfort
will procure such items independent of this contract. Examples of such equipment
include dispatcher and administrator workstations, printers, switches, routers, etc.
The prices in the Cost Proposal may be modified by the proposer during the
procurement in response to Transfort’s request for a Best and Final Offer.
Services Agreement
Page 81 of 143
Appendix A Cost Summary Sheet
Table 9 ATIS Software, Project Management and Support Costs
ATIS Software
Product:
Site License
(Unlimited Users,
Vehicles,
Employees)
Number of
Users
Number of
Vehicles
Number of
Employees
Assume these values ------------------------ 20 40 100
License Costs:
Computer Aided
Dispatch
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
Map Update (Larimer and
Boulder County,
Colorado)
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
Google Transit Feed
Specification
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
AVL Data Export
Services Agreement
Page 82 of 143
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
Trapeze Interface
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
Automatic
Announcements (AA)
AA Vehicles
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
AA Transit Centers
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
AA Platforms and Stops
Project Management
Costs
Support Costs
Year 2
Services Agreement
Page 83 of 143
Year 3
Year 4
Year 5
Passenger Information
Displays
Interactive Voice
Response
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
Information displays and
paging systems
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
Internet Information
(Web Site)
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
Mobile Applications and
Web Site
Project Management
Costs
Support Costs
Year 2
Year 3
Services Agreement
Page 84 of 143
Year 4
Year 5
Digital Signage Interface
Project Management
Costs
Support Costs
Year 2
Year 3
Year 4
Year 5
Totals Section
Total Software Costs
Total Year 2 Support
Costs
Total Year 3 Support
Costs
Total Year 4 Support
Costs
Total Year 5 Support
Costs
Total Support Costs
Grand Total Costs
Services Agreement
Page 85 of 143
Table 10 In Vehicle Systems
NABI 35
Foot
Buses
NABI 40
Foot Buses
Gillig 35
Foot
Buses
Gillig 40
Foot Buses
Eldorado
30 Foot
Bus
Pool
Vehicles
VMS LED
Signs
Quantity
Costs
Manufacturer
Support
Costs
Year 2
Year 3
Year 4
Year 5
Paging
System
Integration
Quantity
Costs
Manufacturer
Support
Costs
Year 2
Year 3
Year 4
Year 5
APC
Devices
Quantity
Costs
Manufacturer
Support
Costs
Year 2
Year 3
Year 4
Year 5
On-board
Computer
Unit
Quantity
Services Agreement
Page 86 of 143
Costs
Manufacturer
Support
Costs
Year 2
Year 3
Year 4
Year 5
Mobile Data
Terminal
Quantity
Costs
Manufacturer
Support
Costs
Year 2
Year 3
Year 4
Year 5
Headway
Sign
Integration
Cost
Manufacturer
Support
Costs
Year 2
Year 3
Year 4
Year 5
GFI Genfare
Cents-a-Bill
Integration
Cost
Support
Costs
Year 2
Year 3
Year 4
Year 5
Services Agreement
Page 87 of 143
Mechanical System Integration
Wheelchair
ramp
deployment
Cost
Support
Costs
Year 2
Year 3
Year 4
Year 5
Engine
Monitoring
Cost
Support
Costs
Year 2
Year 3
Year 4
Year 5
Totals
Section
Support
Costs
Total Year 2
Support
Costs
Total Year 3
Support
Costs
Total Year 4
Support
Costs
Total Year 5
Support
Costs
Grand Total
In Vehicle
Costs
Services Agreement
Page 88 of 143
Table 11 MAX BRT Platforms / Stops
ID
Number
Station Variable Message Sign
Display System QTY
Costs for
VMS
Integration
Paging
System
Zones
Costs for
Paging
Integration
1 South Transit Center Monument Sign 1 N/A N/A
2 South Transit Center Pull - Ins 11 11
3 Harmony Station - Northbound and
Southbound 2 1
4 Troutman Station - Northbound and
Southbound 2 1
5 Horsetooth Station - Northbound and
Southbound 2 1
6 Swallow Northbound Stop 1 1
7 Swallow Southbound Stop 1 1
8 Drake Station - Northbound and
Southbound 2 1
9 Bay Farm Northbound Stop 1 1
10 Bay Farm Southbound Stop 1 1
11 Prospect Station - Northbound and
Southbound 2 1
12 University Station - Northbound and
Southbound 2 1
13 Laurel Northbound Stop 1 1
14 Laurel Southbound Stop 1 1
15 Mulberry Northbound Stop 1 1
16 Mulberry Southbound Stop 1 1
17 Olive Northbound Stop 1 1
18 Olive Southbound Stop 1 1
19 Mountain Northbound Stop 1 1
20 Mountain Southbound Stop 1 1
21 Downtown Transit Center Stop 1 1
Subtotal 37 30
Support
Costs 1 1
Year 2 1 1
Year 3 1 1
Year 4 1 1
Year 5 1 1
Grand Total MAX BRT Costs
Services Agreement
Page 89 of 143
Table 12 Transit Centers
Transit Centers
Variable Message Signs
LED Signs
Integration into
paging system
Downtown Transit Center
CSU Transit Center
South Transit Center
CSU Transit Center
Support Costs
Year 2
Year 3
Year 4
Year 5
Grand Total Transit Center
Costs
Table 13 Training and Implementation
Training & Implementation
Length, (Hours/ Days)
of on site training
Remote
Training Cost
Dispatch Training
System Administration
Training
Go Live' Training
Refresher Training ( one year
after go live)
Length, (Hours/ Days)
of on site training
Remote
Training Cost
Grand Total Training and
Implementation Costs
Services Agreement
Page 90 of 143
APPENDIX B – Proposed System Summary
Table 14 Submittal Checklist
Summary Checklist
Check the appropriate shaded box for
each section listed
CDRL
provided
Information
provided Yes No
With
Exceptions
2.4 ATIS System Procurement
2.4.1 Standards
2.5 Contract Deliverables Requirements
List
3.0 ATIS Components
3.1 Computer Aided Dispatch (CAD)
3.1.1.1 Real-time Prediction Accuracy
3.1.1.2 AVL Data Accuracy and System
Reliability
3.1.2 Dispatch Workstations
3.1.2.1 User Interface Configuration
3.1.3 Schedule Adherence
3.1.4 Route Adherence
3.1.5 ATIS System Time
3.1.6 Data Messaging
3.1.7 Textual and Tabular Displays
3.1.8 Map Display
3.1.9 Emergency Alarm
3.1.10 Historical Data (Playback Mode)
3.1.11 Scenarios
3.2 Google Transit Feed Specification
(GTFS)
3.3 AVL Data Export
3.4 Trapeze Software Interface
4.0 Vehicle Systems
4.1 On-Board Computer System (OCS)
4.1.1 Data Transfer
4.2 Mobile Data Terminal
4.2.1 Text Messaging
4.2.2 Transfer Requests
4.3 Automatic Passenger Counter (APC)
4.4 Automatic Announcements (AA)
4.4.1 In Vehicle System
4.4.2 Transit Centers
4.4.3 Platforms and Stops
Services Agreement
Page 91 of 143
5.0 Passenger Information Systems
5.1 Interactive Voice Response (IVR)
5.2 Information Displays and Paging
Systems.
5.3 Internet Information (Web Site)
5.4 Mobile Device Applications and Web
Site
5.5 Mobile SMS/Email
6.0 ATIS Technical Information
6.1 Data information and Ownership
6.2 Data Analysis and Report Generation
6.3 Database Information
6.4 Technical Overview
6.5 Data Communications
6.6 Operating Environment
6.7 Software
6.7.1 Software Requirements
6.7.2 Definitions
6.7.3 Licensing Model
6.8 Protocols
6.9 Anti-Virus
6.10 Security
6.11 Upgrade Tools
6.12 Maintenance and Support
7.0 PROJECT MANAGEMENT
7.1 Contract Management
7.2 Project Management Plan
7.2.1 Progress Reviews, Schedules and
Project Control
7.2.2 Weekly Conference Calls
7.2.3 Monthly Progress Status Updates
7.3 Initial Activities Meeting
7.4 Design and Configuration Control
7.4.1 Design Principles and Reviews
7.4.2 Preliminary Design Review
7.4.3 Final Design Review
8.0 Training
8.1 Transfort - Furnished Training Related
Items
Services Agreement
Page 92 of 143
8.2 Use of Actual Equipment as Training
Aids
8.3 Training Program Plan
8.3.1 Description
8.3.2 Training Delivery Schedule
8.3.3 Contractor’s Training Experience
8.3.4 Training Courses
8.3.5 Train-the-Trainers
8.3.6 Training Materials
8.4 Vehicle Equipment Training and
Maintenance Module
9.0 Safety Requirements
RFP 7381 Advanced Traveler Information System Page 93 of 143
APPENDIX C – Transit Vehicles
Table 15 Transit Vehicles
Destination Network Fare
Collection
Unit YR-Make-Model VIN Status Engine Transmission Lift/
Ramp Signs
PA
System Seats Length Type Mfg/Model
29 1993 GILLIG PHANTOM 15GCB1214
P1084887 Active
Cummins
L10
VOITH G3-3
speed
Lift-
Lift-U
LU 0-
51-12
Luminator Mobile
Page 36 35' J-1708
GFI
Centsabill
30 1993 GILLIG PHANTOM 15GCB1216
P1084888 Active
Cummins
L10
VOITH G3-3
speed
Lift-
Lift-U
LU 0-
51-12
Luminator Mobile
Page 36 35' J-1708
GFI
Centsabill
31 1993 GILLIG PHANTOM 15GCB1218
P1084889 Active
Cummins
L10
VOITH G3-3
speed
Lift-
Lift-U
LU 0-
51-12
Luminator Mobile
Page 36 35' J-1708
GFI
Centsabill
39 1997 GILLIG PHANTOM 15GCB2119
V1087482 Active
Cummins
M11
Allison B400R-
5 speed
Lift-
Lift-U
LU 0-
Services Agreement
Page 94 of 143
43 1997 GILLIG PHANTOM 15GCD2113
V1087486 Active
Cummins
M11
Allison B400R-
5 speed
Lift-
Lift-U
LU 0-
51-03
Luminator Mobile
Page 42 40’ J-1708
GFI
Centsabill
45 1998 GILLIG PHANTOM 15GCB2112
W1088958 Active
Cummins
M11
Allison B400R-
6 speed
Lift-
Lift-U
LU 0-
51-12
Luminator Mobile
Page 36 35’ J-1708
GFI
Centsabill
46 1998 GILLIG PHANTOM 15GCB2114
W1088959 Active
Cummins
M11
Allison B400R-
6 speed
Lift-
Lift-U
LU 0-
51-12
Luminator Mobile
Page 36 35’ J-1708
GFI
Centsabill
47 1998 GILLIG PHANTOM 15GCB2110
W1088960 Active
Cummins
M11
Allison B400R-
6 speed
Lift-
Lift-U
LU 0-
51-12
Luminator Mobile
Page 36 35’ J-1708
GFI
Centsabill
48 1998 GILLIG PHANTOM 15GCB2113
W1089259 Active
Services Agreement
Page 95 of 143
54 2001 GILLIG LOW
FLOOR
15GGE1813
11090428 Active
Cummins
ISC
Allison B300R-
5 speed
Ramp
-Lift-U
LU-6-
03-02
Luminator
LED
Mobile
Page 27 29’ J-1708
GFI
Centsabill
55 2006 ELDORADO BUS
LOWFLOOR
1N9MNA8G
36C084056 Active
John
Deere
Allison B300R-
5 speed
Ramp
-
Eldor
ado
Luminator
LED
Mobile
Page 32 28’ J-1939
GFI
Centsabill
60 2008 NABI
35LFW3510.01
1N90351048
A140271 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-6-
03-02
Luminator
LED REI 30 35’ J-1939
GFI
Centsabill
61 2008 NABI
35LFW3510.01
1N90351068
A140272 Active
Cummins
Services Agreement
Page 96 of 143
66 2009 NABI 40' BUS 1N94045219
A140259 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40' J-1939
GFI
Centsabill
67 2009 NABI 40' BUS 1N94045289
A140260 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40' J-1939
GFI
Centsabill
68 2009 NABI 40' BUS 1N940452X
9A140261 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40' J-1939
GFI
Centsabill
69 2009 NABI 40' BUS 1N94045219
A140262 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
Services Agreement
Page 97 of 143
75 2011 NABI 40' BUS 1N9404534
BA140318 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40' J-1939
GFI
Centsabill
76 2011 NABI 40' BUS 1N9404536
BA140319 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40' J-1939
GFI
Centsabill
77 2011 NABI 35' BUS 1N9351025
BA140337 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 30 35' J-1939
GFI
Centsabill
78 2011 NABI 35' BUS 1N9351027
BA140338 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
Services Agreement
Page 98 of 143
82 2013 NABI 35’ BUS TBD on order
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 30 35’ J-1939
GFI
Centsabill
83 2013 NABI 35’ BUS TBD on order
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 30 35’ J-1939
GFI
Centsabill
84 2013 NABI 35’ BUS TBD on order
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 30 35’ J-1939
GFI
Centsabill
85 2013 NABI 35’ BUS TBD on order
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 30 35’ J-1939
Services Agreement
Page 99 of 143
91 2014 NABI 60' ARTIC
BRT ROUTE TBD on order
Cummins
ISL-G
330hp
Allison B500R-
6 speed TBD
Luminator
LED TBD 44 60' J-1939 TBD
93 2014 NABI 60' ARTIC
ROUTE BUS TBD on order
Cummins
ISL-G
330hp
Allison B500R-
6 speed TBD
Luminator
LED TBD 44 60' J-1939 TBD
Services Agreement
Page 100 of 143
Table 16 Supervisor and Maintenance Vehicles
20000 M0960 1998 CHEVROLET BLAZER
20001 M0960 1998 CHEVROLET BLAZER
20002 M0960 2008
DODGE GRAND
CARAVAN
2608 M0960 2000 FORD FLATBED F350
2630 M0960 1998
CHEVROLET ASTRO
VAN
2682 M0960 1999 CHEVROLET VAN
Existing Vehicle Equipment
The equipment listed below is currently installed onboard the transit vehicles and will
need to be considered when integration of ATIS technologies is undertaken.
GFI Genfare Farebox
Cents-a-Bill
Magnetic Stripe Reader
GPS cables installed
Headway signs
Illuminator
Twin Vision
Paging Systems
Mobile page
REI
Moxa Network Switch
8 port ruggedized unmanaged network switch
Onboard Mobile Gateway (OMG) Inmotion Technologies
GPS exports both NEMA and TAIP, will also import TAIP
WIFI local
WIFI backhaul
Cellular – AT&T APN
Verint Digital Video Recorder
Mdvr6s
6 cameras
G-Force Sensor
Services Agreement
Page 101 of 143
Appendix D – Transit Centers
Transfort Maintenance Facility (TMF)
6570 Portner Road
Downtown Transit Center (DTC)
250 North Mason Street
Existing Displays
40’ LCD Samsung display internal
Dell Optiplex 620 computer running Windows XP Pro
Digital signage currently using Four Winds Interactive software
Existing paging equipment
TOA 900 series II Amplifier A-912MK2
Internal and external speakers on a 70 volt line
Volume controls and microphones
Dell Optiplex 280 computer running windows XP pro
Automatic announcements currently using BMS Business Music System
Colorado State University Transit Center (CTC)
North End of the Lory Student Center, lower level
Existing Displays
40” LCD Samsung display internal
46” LCD Samsung display internal
(2) Dell Optiplex 620 computers running Windows XP Pro
Digital signage currently using Four Winds Interactive software
Existing paging equipment
TOA 900 series II Amplifier A-912MK2
TOA Integrated Amplifier
Crown Integrated Amplifier
CSVX 9620 Amplifier
Internal and external speakers on a 70 volt line
Volume controls and microphones
Dell Optiplex 620 computer running windows XP pro
Automatic announcements currently using BMS Business Music System
South Transit Center (STC)
Fossil Blvd - Construction to start 2012
Services Agreement
Page 102 of 143
Appendix E – Platforms and Stops
MAX Bus Rapid Transit construction specs
Including the systems that ATIS will be integrating with after construction is complete.
The following specs are representative of the MAX BRT bid now publicly available
including any addendums. Please refer to the City of Fort Collins Purchasing website
for the latest information. http://www.fcgov.com/purchasing/
Services Agreement
Page 103 of 143
Services Agreement
Page 104 of 143
Services Agreement
Page 105 of 143
Services Agreement
Page 106 of 143
Services Agreement
Page 107 of 143
Services Agreement
Page 108 of 143
Services Agreement
Page 109 of 143
Services Agreement
Page 110 of 143
Services Agreement
Page 111 of 143
Services Agreement
Page 112 of 143
Services Agreement
Page 113 of 143
Services Agreement
Page 114 of 143
Services Agreement
Page 115 of 143
Services Agreement
Page 116 of 143
Services Agreement
Page 117 of 143
Services Agreement
Page 118 of 143
Services Agreement
Page 119 of 143
Services Agreement
Page 120 of 143
Services Agreement
Page 121 of 143
Services Agreement
Page 122 of 143
Services Agreement
Page 123 of 143
Services Agreement
Page 124 of 143
Services Agreement
Page 125 of 143
Services Agreement
Page 126 of 143
Services Agreement
Page 127 of 143
Services Agreement
Page 128 of 143
Services Agreement
Page 129 of 143
Services Agreement
Page 130 of 143
Services Agreement
Page 131 of 143
Services Agreement
Page 132 of 143
Services Agreement
Page 133 of 143
Services Agreement
Page 134 of 143
Services Agreement
Page 135 of 143
Services Agreement
Page 136 of 143
Services Agreement
Page 137 of 143
Services Agreement
Page 138 of 143
Services Agreement
Page 139 of 143
Services Agreement
Page 140 of 143
Services Agreement
Page 141 of 143
Appendix F – Trapeze Software Interface Specification
Transfort uses software to meet scheduling, automated payroll, personnel, asset and
incident management needs. The following is a list of operational data characteristics
that are used in the current software environment. While a comprehensive, custom
interface to Transfort’s scheduling software is not required, Transfort seeks solutions
that will minimize duplication of efforts or data conflicts with the current software
environment.
The following table illustrates some examples of operational data characteristics which
may contain relational information to any CAD solution. Examples of data fields are
provided for proposers to make an assessment of any duplicate or conflicting data.
This appendix is supplied to aid in your response to section 3.4. Responses should be
noted in section 3.4.
Services Agreement
Page 142 of 143
Software
Component Data Label
Sample
Data
Presumed System of
Record
Fixed Route
Scheduling Block Number 15
Current Scheduling
Software
Bus Stop Latitude 40171889 CAD Solution
Bus Stop Longitude
-
105103934 CAD Solution
Bus Stop ID 1175
Current Scheduling
Software
Run Number 5665
Current Scheduling
Software
Stop Times 97140
Current Scheduling
Software
Stored in Seconds from
Midnight
Time Points 97140
Current Scheduling
Software
Stored in Seconds from
Midnight
Operations Vehicle Assignments
--Split Vehicle Blocks, new
dailyblockid created with new
vehicle. ----
Current Scheduling
Software
Times in Operational
software and CAD should
match ---- " "
VehicleNumbers 2675
Current Scheduling
Software
VehicleId 42
Current Scheduling
Software
Work Assignments
--Split work assignments,
new workid created. Times
in Operational ----
Current Scheduling
Software
software and CAD should
match ---- " "
EmployeeId 17
Current Scheduling
Software
Incident Management
EmployeeId 17
Services Agreement
Page 143 of 143
Midnight
SignInTime 83280
Current Scheduling
Software
ReportTime 600
Current Scheduling
Software
PrepTime 900
Current Scheduling
Software
TravelTime 13800
Current Scheduling
Software
StartTime 43600
Current Scheduling
Software
EndTime 65400
Current Scheduling
Software
WaitTime 600
Current Scheduling
Software
PlatformTime 28980
Current Scheduling
Software
FinishTime 900
Current Scheduling
Software
ClearTime 600
Current Scheduling
Software
SignOffTime 97740
Current Scheduling
Software
Current Scheduling
Software
IncidentTypeId 66
Current Scheduling
Software
Incident Description
ROUTE
ERROR
Current Scheduling
Software
IncidentId 157
Current Scheduling
Software
Work Time Components
Stored in Seconds from
GFI
Centsabill
86 2014 NABI 60’ ARTIC
BRT ROUTE TBD on order
Cummins
ISL-G
330hp
Allison B500R-
6 speed TBD
Luminator
LED TBD 44 60’ J-1939 TBD
87 2014 NABI 60’ ARTIC
BRT ROUTE TBD on order
Cummins
ISL-G
330hp
Allison B500R-
6 speed TBD
Luminator
LED TBD 44 60’ J-1939 TBD
88 2014 NABI 60’ ARTIC
BRT ROUTE TBD on order
Cummins
ISL-G
330hp
Allison B500R-
6 speed TBD
Luminator
LED TBD 44 60’ J-1939 TBD
89 2014 NABI 60’ ARTIC
BRT ROUTE TBD on order
Cummins
ISL-G
330hp
Allison B500R-
6 speed TBD
Luminator
LED TBD 44 60’ J-1939 TBD
90 2014 NABI 60’ ARTIC
BRT ROUTE TBD on order
Cummins
ISL-G
330hp
Allison B500R-
6 speed TBD
Luminator
LED TBD 44 60’ J-1939 TBD
11-
06-02
Luminator
LED REI 30 35' J-1939
GFI
Centsabill
79 2013 NABI 35' BUS TBD on order
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 30 35' J-1939
GFI
Centsabill
80 2013 NABI 35' BUS TBD on order
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 30 35' J-1939
GFI
Centsabill
81 2013 NABI 35' BUS TBD on order
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 30 35' J-1939
GFI
Centsabill
11-
06-02
Luminator
LED REI 36 40' J-1939
GFI
Centsabill
72 2009 INTERNATL 3200 4DRASAAL4
9H042758 Active
IHC
Maxforce
DT-366
Allison B300-5
speed
Lift-
Braun
Vista
Twin Vision 25 26' J-1939 GFI
Centsabill
73 2011 NABI 40' BUS 1N9404530
BA140316 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40' J-1939
GFI
Centsabill
74 2011 NABI 40' BUS 1N9404532
BA140317 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40' J-1939
GFI
Centsabill
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-6-
03-02
Luminator
LED REI 30 35’ J-1939
GFI
Centsabill
62 2008 NABI
35LFW3510.01
1N90351088
A140273 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-6-
03-02
Luminator
LED REI 30 35’ J-1939
GFI
Centsabill
63 2009 NABI 40’ BUS 1N94045009
A140137 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40’ J-1939
GFI
Centsabill
64 2009 NABI 40’ BUS 1N94045289
A140257 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40’ J-1939
GFI
Centsabill
65 2009 NABI 40’ BUS 1N940452X
9A140258 Active
Cummins
ISL-G
280hp
Allison B400R-
6 speed
Ramp
-Lift-U
LU-
11-
06-02
Luminator
LED REI 36 40’ J-1939
GFI
Centsabill
Cummins
M11
Allison B400R-
6 speed
Lift-
Lift-U
LU 0-
51-12
Luminator Mobile
Page 36 35’ J-1708
GFI
Centsabill
49 2001 GILLIG LOW
FLOOR
15GGE1814
11090423 Active
Cummins
ISC
Allison B300R-
5 speed
Ramp
-Lift-U
LU-6-
03-02
Luminator
LED
Mobile
Page 27 29’ J-1708
GFI
Centsabill
50 2001 GILLIG LOW
FLOOR
15GGE1816
11090424 Active
Cummins
ISC
Allison B300R-
5 speed
Ramp
-Lift-U
LU-6-
03-02
Luminator
LED
Mobile
Page 27 29’ J-1708
GFI
Centsabill
51 2001 GILLIG LOW
FLOOR
15GGE1818
11090425 Active
Cummins
ISC
Allison B300R-
5 speed
Ramp
-Lift-U
LU-6-
03-02
Luminator
LED
Mobile
Page 27 29’ J-1708
GFI
Centsabill
53 2001 GILLIG LOW
FLOOR
15GGE1811
11090427 Active
Cummins
ISC
Allison B300R-
5 speed
Ramp
-Lift-U
LU-6-
03-02
Luminator
LED
Mobile
Page 27 29’ J-1708
GFI
Centsabill
51-03
Luminator Mobile
Page 36 35' J-1708
GFI
Centsabill
40 1997 GILLIG PHANTOM 15GCB2110
V1087483 Active
Cummins
M11
Allison B400R-
5 speed
Lift-
Lift-U
LU 0-
51-03
Luminator Mobile
Page 36 35' J-1708
GFI
Centsabill
41 1997 GILLIG PHANTOM 15GCB2112
V1087484 Active
Cummins
M11
Allison B400R-
5 speed
Lift-
Lift-U
LU 0-
51-03
Luminator Mobile
Page 36 35' J-1708
GFI
Centsabill
42 1997 GILLIG PHANTOM 15GCB2114
V1087485 Active
Cummins
M11
Allison B400R-
5 speed
Lift-
Lift-U
LU 0-
51-03
Luminator Mobile
Page 36 35' J-1708
GFI
Centsabill
funded thru2
5307/5309/5
311
None
None unless
non-
competitive
award
None
None unless
non-
competitive
award
None
None unless
non-
competitive
award
II Non State
Grantees
a. Contracts below
SAT ($100,000)
b. Contracts above
$100,000/Capital
Projects
Yes3
Yes3
Those
imposed on
non-state
Grantee
pass thru to
Contractor
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes