Request for Qualifications for

National Onboard Wi-Fi Installation Project:

RFQ Number 1: Communications Platform,

Including Passenger Wi-Fi
Final version 1.0

March 4, 2010

Amtrak
(National Railroad Passenger Corporation)
60 Massachusetts Avenue, N.E.
Washington, DC 20002
 Table of Contents
1. Purpose of Request for Qualifications (RFQ)..................................................................3
1.1 Selection Process.......................................................................................................3
1.2 Background................................................................................................................4
1.3 The Amtrak Fleet.......................................................................................................4
1.3.1 Northeast Corridor..............................................................................................5
1.3.2 Long Distance Trains..........................................................................................6
1.3.3 Corridor and State Trains....................................................................................7
1.3.4 Contract Commuter Service................................................................................8
1.4 Amtrak Major Mechanical Depots.............................................................................9
2. Desired Capabilities.......................................................................................................10
2.1 Communications Platform.......................................................................................10
2.2 Onboard Passenger Wi-Fi........................................................................................11
3. Deliverables...................................................................................................................11
4. Communications Platform Technical Requirements.....................................................12
4.1 Equipment................................................................................................................12
4.2 Connection to Multiple Cellular Networks..............................................................13
4.3 Onboard Network.....................................................................................................14
4.4 Back-end Monitoring and Reporting System..........................................................14
4.5 Additional Required Features..................................................................................15
4.6 Security....................................................................................................................15
4.7 Availability..............................................................................................................15
5. Onboard Passenger Wi-Fi Technical Requirements......................................................17
5.1 Passenger Usage.......................................................................................................17
6. Clarification Questions..................................................................................................18
7. Appendix 1 - Amtrak Fleet ...........................................................................................20
8. Appendix 2 – Amtrak Train Specifications...................................................................22
8.1 Northeast Regional...................................................................................................22
8.2 Capitol Limited (Washington, DC-Chicago)...........................................................23
9. Appendix 3 – Car Type Descriptions.............................................................................24

List of Attachments

Attachment 1 – Specification for Components to be Installed on High Speed Train Sets

Attachment 2 - Amtrak Car Specification Diagrams
Attachment 3 - Environmental and Operating Conditions

2
1. Purpose of Request for Qualifications (RFQ)
Amtrak is seeking to identify a complete technology solution that will serve as an
onboard communications platform (the “Platform”). The Platform will include a robust,
self-healing, self-configuring onboard network and associated equipment that forms the
foundation to support two primary services: (1) Wi-Fi for passengers and (2) a secure Wi-
Fi channel for Amtrak business needs to support on-board transactions (such as ticketing
or on-board sales). In addition, the system will be capable of supporting automated
onboard electronic informational displays and announcements, content caching and
delivery (e.g., for custom content as well as audio and video entertainment), and other
business services.

Amtrak envisions that the Platform will include at its core a wireless and wired
infrastructure, a communications control unit, and an off-board multi-technology
communications system. The Platform will be supported through a hardened data center
that will be capable of real-time monitoring and reporting on the Platform and related
services.

The established Platform will be used as the basis for an ongoing national standard for all
of the trains in the Amtrak fleet and, at Amtrak Rail Partners’ option, for their fleets as
well. Hereinafter, Amtrak and Rail Partners shall be collectively referred to as Amtrak.

1.1 Selection Process

The selection process includes three elements: two RFQs followed by a National Request
for Proposal (RFP). Amtrak will use the RFQs to select core national technology
standards which will subsequently be procured and implemented through the National
RFP, as follows:

• RFQ 1: Communications Platform, including Passenger Wi-Fi: This first RFQ

seeks responses from vendors for the on-board Communications Platform,
including: (a) onboard train communications network, (b) Wi-Fi for passenger
and business use; and (c) content caching and support for future applications as
noted under RFQ 2. Requirements for RFQ 1 are detailed in Sections 2 and 4.

• RFQ 2: Onboard Train Information Systems (OTIS): The second RFQ, which will
shortly follow the first, will seek qualifications from vendors for OTIS. The
OTIS will utilize the Communications Platform identified in RFQ 1 to support
automated on-board signage and announcements and end-of-car displays.

• RFP for Solutions Implementation: Once the core technologies are identified
through the RFQ process, a national task order RFP will be issued which will
establish master contracts with a series of installers who will, with participation of

3
 the core technology vendors, equip specific trains with the respective
Communications Platform and OTIS systems.

At Amtrak’s option, the RFP phase will include one or two RFPs. If two RFPs are issued,
each RFP will correspond to either RFQ1 or RFQ2. If only one RFP is issued, that RFP
will encompass all features of the proposed on-board technologies. The RFP will result in
a selection of a set of vendors qualified to work on a task-order basis to install, operate
and maintain these systems for Amtrak across the United States.

1.2 Background

In 2009/10, Amtrak procured and installed a Platform providing Wi-Fi on the high speed
Acela Express trains that travel on the Northeast Corridor between Washington, DC and
Boston. It is Amtrak’s desire to expand the Platform beyond the Acela Express trains to
the rest of the Amtrak fleet. For the purposes of this RFQ, participants shall formulate
their proposals based on the 2 example trains below which will serve as a representative
sample of the overall Amtrak fleet:

• Northeast Regional: Single level Amfleet-I cars with service between

Washington, DC and Boston

• Capitol Limited: Bi-level Superliner cars with service between Washington, DC

and Chicago

Detailed information about each train can be found in Appendix 2, and car specification
diagrams can be found in Attachment 2.

1.3 The Amtrak Fleet

This section provides an overview of the Amtrak-owned fleet and relationships with other
Rail Partners. Amtrak is the nation’s intercity passenger railroad and a contract operator
for many commuter and intercity trains across a nationwide rail network serving more
than 500 destinations with over 300 weekday departures on 48 routes in 46 states over
22,000 miles of track. Each weekday the Amtrak system carries 66,000 passengers, of
whom 38 percent are business travelers, 18 percent are commuters, and 44 percent are
leisure travelers.

Amtrak-owned equipment includes Amfleet, Superliner, and other railroad passenger cars
totaling 1,519 units. A detailed description of each car type can be found in Appendix 3.
Amtrak also is the operator for state-supported corridor services in 15 states and for 4
commuter rail agencies. A detailed listing of the number and types of cars in the Amtrak
fleet can be found in Appendix 1.

4
Amtrak cars have been purchased during different time periods and have been modified
to serve different purposes. As a result, cars of the same type might have different
modifications and mechanical arrangements that preclude the same technical solution
from being feasible on every car of the same type.

With the exception of Acela Express, Amtrak trains do not operate with a fixed consist1.
Additionally, it is common for cars of different types to be mixed together in a consist,
and it is possible for cars from one train to be split apart and used on different trains. In
addition, it is also possible for a consist to be split apart in route, and to have different
cars from the original consist travel on separate routes. As such, all components and
systems in the Platform must be able to function under any consist arrangement, and all
Platform equipment installed in the cars in the fleet must be compatible with each other.
The proposed Platform must be able to recognize the assembled consist of a train and be
able to dynamically update itself for consistent uninterrupted operation. For this RFQ
Amtrak requires a wireless connection between cars.

1.3.1 Northeast Corridor

Amtrak owns and operates 363 miles of the 457-mile Northeast Corridor (NEC) between
Washington, DC and Boston (a total of 1,219 track miles). The NEC is home to one of
the busiest and most complex, track structures in the United States with over 1,800 trains
each weekday, including slow freight trains traveling at speeds of 30-50 mph, commuter
trains that travel at speeds up to 125 mph, Amtrak Regional trains that travel at 110 or
125 mph, and Acela Express trains that can reach speeds of 150 mph. Note: Acela
Express trains, which already have installed Wi-Fi equipment, are not included in the
scope of this RFQ or subsequent RFP(s).

1
The term consist is used to describe the group of rail cars which make up a train.
5
1.3.2 Long Distance Trains

Amtrak’s long-distance trains provide an essential transportation service for many

communities and to a significant percentage of the general public. A long-distance train
typically consists of sleepers, coaches, café, a diner and/or a lounge car.
• Long-distance trains travel as far as 2,800 miles and pass through as many as
12 states.
• Amtrak operates 15 long-distance trains over 18,500 route miles serving 39
states and the District of Columbia. These trains provide the only rail
passenger service to 23 states.
• In FY 2008 these trains carried 4.2 million passengers accounting for 2.6
billion passenger miles—42% of Amtrak’s total—and produced ticket
revenues of $415 million.
• The average long-distance train passenger traveled 626 miles in FY08.
• Long-distance trains run primarily on tracks owned and maintained by private
freight railroads.

6
 Amtrak’s Long Distance Trains and the major cities they serve.
• Auto Train - Lorton, VA (Washington, DC) - Sanford, FL (Orlando)
• California Zephyr - Chicago - Denver - Emeryville, CA (San Francisco)
• Capitol Limited - Washington, DC - Pittsburgh – Chicago
• Cardinal / Hoosier State - New York - Washington, DC - Chicago
• City of New Orleans - Chicago - Memphis - New Orleans
• Coast Starlight - Seattle - Portland - Los Angeles
• Crescent - New York - Atlanta - New Orleans
• Empire Builder - Chicago - St. Paul - Portland/Seattle
• Lake Shore Limited - New York/Boston - Albany – Chicago
• Silver Service / Palmetto - New York - Washington, DC - Orlando -
Tampa/Miami
• Southwest Chief - Chicago - Albuquerque - Los Angeles
• Sunset Limited - New Orleans - San Antonio - Los Angeles
• Texas Eagle - Chicago - St. Louis - Dallas - San Antonio - (Los Angeles)

1.3.3 Corridor and State Trains

Amtrak’s corridor services operate over a 6,000-mile route system and serve 23 states,
primarily in the Northeast, Midwest and along the Pacific Coast. Outside the Northeast
Corridor, seven corridors carry over one half million people annually.
These corridors are:
• Capitols—San Jose-Oakland-Sacramento-Auburn
• Cascades—Vancouver-Seattle-Portland-Eugene

7
 • Empire—New York-Albany-Buffalo-Toronto
• Hiawatha—Chicago-Milwaukee
• Keystone—New York-Philadelphia-Harrisburg
• Pacific Surfliner—San Diego-Los Angeles-San Luis Obispo
• San Joaquin—Oakland-Fresno-Bakersfield

The following states contract with Amtrak for the operation of trains that supplement the
national Amtrak network by extending the reach of passenger rail services or provide
additional frequencies on Amtrak routes.
• Illinois: Hiawatha Service (Chicago-Milwaukee), Lincoln Service (Chicago-St.
Louis), Illini & Saluki (Chicago-Carbondale) and Illinois Zephyr & Carl Sandburg
(Chicago-Quincy)
• Maine: Downeaster (Portland-Boston)
• Michigan: Blue Water (Port Huron-East Lansing-Chicago) and Pere Marquette
(Grand Rapids-Chicago)
• Missouri: Missouri River Runner (Kansas City-St. Louis)
• New York: Adirondack (New York City-Montreal, Q.C.)
• North Carolina: Carolinian (Charlotte-New York City) and Piedmont (Raleigh-
Charlotte)
• Oklahoma: Heartland Flyer (Oklahoma City-Fort Worth)
• Pennsylvania: Keystone Corridor Service (Harrisburg-Philadelphia-New York
City)
• Texas: Heartland Flyer (Fort Worth-Oklahoma City)
• Vermont: Ethan Allen Express (Rutland-New York City) and Vermonter (St.
Albans-Washington)
• Washington/Oregon: Amtrak Cascades Service (Eugene-Portland-Seattle-
Vancouver, B.C.)

1.3.4 Contract Commuter Service

Amtrak operates currently provides commuter service for the following state and regional
authorities:

• Caltrain (for the Caltrain Joint Powers Board)

• MARC (Maryland Area Regional Commuter)
• Shore Line East (Connecticut DOT)

Amtrak also provides maintenance services for the Sounder Commuter Rail system in
Seattle, dispatching and maintenance of way service to the Massachusetts Bay Transit
Authority, dispatching services for the South Florida Regional Transportation Authority's
Tri-Rail operation, and engineering construction management services for the North
County Transit District in San Diego, California.

8
1.4 Amtrak Major Mechanical Depots
All installation and maintenance for the Platform will occur at one of Amtrak’s major
mechanical depots listed below. The depot used for a given task order will be dependant
upon the train specified in the given task and its geographical location. Locations include:

• Albany, NY
• Beech Grove, IN
• Boston, MA
• Chicago, IL
• Ivy City, DC
• Los Angeles, CA
• NY, NY (called Sunnyside, it is about 4 miles from Madison Square Garden)
• Oakland, CA
• Philadelphia, PA
• Seattle, WA
• Wilmington, DE

There are also smaller facilities at Miami, FL, Sanford, FL, and New Haven, CT.

9
2. Desired Capabilities
2.1 Communications Platform

Amtrak desires a Platform that utilizes cellular broadband technology and additional
external sources of broadband (e.g., external Wi-Fi and track side wireless networks) for
train to land connections. The Platform must have the ability to use multiple cellular
carriers and aggregate all carriers’ bandwidth to provide maximum backhaul throughput.

In addition the Platform must operate over the entire length of the train without a physical
wired connection between train cars. The Platform shall utilize wireless standards such
as 802.11(a/n) for inter-car connections. All Platform equipment shall be able to function
under any consist arrangement. The Platform must be able to recognize the assembled
consist of a train and be able to dynamically configure itself for consistent uninterrupted
operation.

The Platform must be updated and monitored via a nationally recognized data center
provider approved by Amtrak or at one of Amtrak’s facilities.

The key business objectives of the Platform are to:

• Provide a platform for an onboard passenger Wi-Fi network; and

• Provide a platform to support future services, such as onboard train information
systems.

The key technical objectives of the Platform are to:

• Use multiple cellular carriers, aggregating all carriers’ bandwidth;

• Integrate and aggregate additional sources of bandwidth, such as external Wi-Fi
and track side wireless networks to supplement network backhaul;
• Provide robust hosting/caching capabilities that can support Amtrak’s
website/content (i.e. steaming audio and video);
• Provide remote monitoring, troubleshooting capabilities, and intelligent reporting;
• Provide modular kits for ease of installation and repair; and
• Support the migration to 4G technologies without replacing the major components
on board (e.g., WiMAX or Long Term Evolution [LTE]).

Amtrak is not committed to a specific solution or technology to achieve the business and
technical objectives. Amtrak mandates that the Platform will use a combination of cost
effective multiple wireless interfaces (e.g., Wi-Fi, Worldwide Interoperability for
Microwave Access [WiMAX], High Speed Packet Access [HSPA], and Evolution Data

10
Optimized [EV-DO]), spectrum bands (cellular, 2.4 GHz, and 5.x2 GHz, and 4G) to
provide maximum throughput, bandwidth, performance, coverage and redundancy.

2.2 Onboard Passenger Wi-Fi

Amtrak desires an onboard passenger Wi-Fi network. The Wi-Fi network must allow
best-efforts access the most common Internet applications, including, but not limited to:
Web browsing, E-mail access, the use of Virtual Private Network (VPN), file (e.g., data,
photos, movies) upload and download, and video and audio streaming.

The key business objectives of the Wi-Fi Network are to:

• Attract new and retain existing passengers with Internet service; and
• Improve passenger satisfaction by providing reliable Wi-Fi Internet access.

The key technical objectives of the Wi-Fi Network are to:

• Provide a single SSID for all on-train passenger Wi-Fi networks;

• Dynamically allocate bandwidth to passengers;
• Provide the ability to manage the bandwidth to selected passengers or cars – such
as first class;
• Provide the ability to filter the type of content allowed (e.g., blacklist URLs,
radio, video and audio streaming); and
• Allow passengers continuous VPN connectivity on a best efforts basis subject to
backhaul availability.

3. Deliverables
The Platform proposal submitted by the participants must include a detailed system
design, as well as pricing proposals for: equipment, project management, and operations
and maintenance support. All Participants are required to complete the enclosed Wi-Fi
RFQ Submission Template, Wi-Fi RFQ Pricing Worksheet, Wi-Fi RFQ Equipment
List, and Wi-Fi RFQ Requirement Verification Matrix.

Participants are required to document the proposed design and architecture of their
system for both of the representative trains sets discussed in section 1.2. These
documents shall include a list of materials to be used, software, functionality of each
module, and all the connections between system components. The Participants are not
required to disclose Intellectual Property, but should include sufficient information to
allow Amtrak to understand the Participant’s proposed solution. The specific deliverables
are summarized in the table below.

2
Throughout the document, 5.x GHz refers to any license-exempt band in the
5000 MHz to 6000 MHz spectrum band.

11
 Deliverables in Response to RFQ

Deliverable Description
Name
1. System Design Models and descriptions of the various architectural and technical
aspects of the system, including:
• Physical design and deployment of equipment.
• Location of the equipment for the 3 example train
• Logical design of software functionality, major components
and customizations.
• Communications technologies used
• Informational model describing the handling of data flows,
data quality, quantity, and timeliness.
• System security design.
2. Pricing Participants are required to complete the Wi-Fi RFQ Pricing
Worksheet.
3. Experience and Participants are required to complete the Wi-Fi RFQ Submission
References Template.
4. Equipment List Participants are required to complete the Wi-Fi RFQ Equipment List.
5. Requirements Participants are required to complete the Wi-Fi RFQ Requirement
Verification Verification Matrix.

4. Communications Platform Technical Requirements

4.1 Equipment
All hardware, with the exception of the cellular access router (e.g., antennae,
4.1.1
cabling, UPS, amplifiers, surge protectors) shall be commonly available equipment.
4.1.2 All custom mounting equipment shall be approved by Amtrak.
Externally and internally mounted equipment shall be ruggedized and withstand all
environmental conditions, including conditions of extreme heat and moisture. The
4.1.3
Participants shall meet all requirements as stated in the “Specification for
Components to be Installed on High Speed Train Sets” (Refer to Attachment 1).
The system shall be modular and have the ability to be maintained via a simple
4.1.4
swap and replace program for both upgrades and repair purposes.
Amtrak requires that all antennas communicating with the cell towers be externally
4.1.5
mounted.
4.1.6 Participants shall design a solution that does not require the removal or alteration of

12
 any equipment on Amtrak trains.
All external antennas (e.g., GPS, Satellite, Cellular, WiFi, and WiMax) shall be
securely mounted on the exterior of the trains and be able to withstand the harsh
environment, including but not limited to the following, and as described in
Attachment 3:
• Weather elements of rain, snow, and ice.
• Wind speeds in excess of 300 mph.
• Surviving hits by debris.
4.1.7 • Corrosion caused by diesel exhaust contaminants.
• Interference from overhead electrical catenary.
• Antennas shall fit within Amtrak’s existing clearance envelope. (Amtrak
does not have a standard antenna height, but rather a maximum height that a
carriage may be on a given service route. As such, the selected participant
shall work with Amtrak on antenna design and placement.). The signal
attenuation for the proposed antenna and cable type should provide the
maximum RSSI.
Participants will be required to work with Amtrak Mechanical Department to
4.1.8 ensure that the proposed solution meets all specifications including but not limited
to those for vibration, heat, electrical and radio interference.
The equipment of the proposed solution shall use uninterrupted power to prevent
4.1.9
loss of service.
The equipment of the proposed solution shall conform to the space provided and
4.1.10 should not in any way interfere with or prevent maintenance of other existing train
systems.
The participants shall select and utilize high quality and reliable components,
4.1.11
materials, and proven designs.
The participant shall utilize service-proven hardware in the proposed solution. For
all parts and components, Amtrak prefers those designs that have a documented and
satisfactory operating history. Systems and equipment with a limited service record
4.1.12
will be given consideration by Amtrak, but they must be accompanied by
presentations and engineering data containing sufficient information for Amtrak to
review the merits of the design.

4.2 Connection to Multiple Cellular Networks

The Platform shall be able to use multiple cellular networks concurrently and
4.2.1
maximize throughput over all cellular interfaces.
The Platform shall integrate and aggregate additional sources of bandwidth, such as
4.2.2 off-board Wi-Fi, Wi-MAX and other radio technologies to supplement network
backhaul.
The Platform shall be able to optimize all sources of available bandwidth to provide
4.2.3
maximum throughput and performance.

13
4.3 Onboard Network
All components and systems in the proposed design shall be able to function under
4.3.1 any consist arrangement, and all equipment installed for the onboard network in the
fleet must be self-configuring and self-healing.
The proposed solution shall be able to recognize the given consist of cars and be
4.3.2
able to dynamically update the onboard network.
The onboard network shall operate over the entire length of the train without a
physical connection between cars. Amtrak desires that the solution shall utilize an
4.3.3
approved 802.11(a/n) standard for inter-car links with Amtrak’s priority being the
fastest reliable connection possible.
The Participant’s solution shall optimize the onboard network bandwidth within
4.3.4
each car.
4.3.5 All access point shall be able to dynamically search for the best channel to use.
If Participants are proposing a single CCU design, the Participants shall document
4.3.6
the expected available bandwidth in each car within the consist.
The solution shall support virtual LANs (VLANS) within the onboard network to
4.3.7
separate Amtrak operations and passenger networks.
The solution shall provide for quality of service between the VLANS and must be
4.3.8
able to allocate bandwidth by channel as directed by Amtrak.
Amtrak requires a separate SSID for each virtual network in the on-train Wi-Fi
4.3.9
network.

4.4 Back-end Monitoring and Reporting System

The system shall provide individual passenger usage statistics including but not
limited to:
• Number of network users on the system at any time.
• The maximum, minimum, and the average bandwidth usage by passenger.
4.4.1 • Average length of time a passenger uses the system.
• Geographic location and time of passenger usage.
• Reporting by URL accessed
• Number of passengers who attempt to access black listed sites and a list of
the site sites they attempted to access.
4.4.2 The system shall provide real time remote health monitoring and trouble shooting
of the installed equipment, with the ability to provide reports including but not
limited to:
• Which trains are experiencing problems.
• Total trains with problems.
• GPS location of all trains.
• Health and location of all components.

14
 • Consist mapping.
The system shall be able to provide real time tracking information on system
4.4.3
hardware configuration including air cards, access points, and control units.
The system shall provide automated email or text alerts when problems are
4.4.4
identified. When and which alerts are triggered should be configurable by Amtrak.
4.4.5 The system shall provide spare part tracking by part number.
If a Participant-hosted data center solution is proposed, the data center solution
4.4.6
shall be fully redundant.

4.5 Additional Required Features

The system shall have the ability to expand the storage allocated to caching data
4.5.1
both from internal applications and from Internet derived data
GPS shall be included as part of the solution for the purpose of, but not limited to,
4.5.2 data analysis and geo-fencing. Amtrak shall have the ability to create, update and
delete geo-fences for the purpose of reporting and monitoring train movement.

4.6 Security
The Participants shall provide detailed information on how they intend to provide
4.6.1 end-to-end security for the on-train network to prevent unauthorized changes and
use of the network.
Participant’s proposed design shall incorporate Wi-Fi equipment that supports
4.6.2 versions b/g/n and that is Wi-Fi Certified, with certification that includes
WPA/WPA2 for administrative purposes.

4.7 Availability
All hardware and software components that constituents the Platform whether
4.7.1 installed on the train or within the data center must function at a 99.99% uptime.
This uptime excludes the cellular carrier’s network performance.
The Platform’s train to land communication shall operate without interruption
4.7.2
subject to cellular backhaul availability.
The Platform shall be designed utilizing industry best practices for high-
4.7.3
availability systems.
The Platform shall be modular in design to facilitate ease of installation, repair,
4.7.4
and upgrades.
If the proposed solution requires any system components to be installed within a
4.7.5 non Amtrak data center, the Participants shall ensure that the data center is
compliant with industry standards for security and availability.

15
16
5. Onboard Passenger Wi-Fi Technical Requirements

5.1 Passenger Usage

The Wi-Fi network shall allow best efforts access to the most common Internet
applications, including, but not limited to: Web browsing, Email access, Virtual
5.1.1
Private Network (VPN) access, file (e.g., data, photos, movies) upload and
download, and video and audio streaming.
The onboard passenger Wi-Fi network shall operate over the entire length of the
train. Amtrak desires that the solution shall utilize an approved 802.11b/g/(n)
5.1.2
standard for passenger access points with Amtrak’s priority being the fastest
reliable connection possible.
Internet access shall be available to passengers on a best-efforts basis. As a
result, Amtrak does not anticipate the need for real-time customer support
service, but passengers have to be able to provide feedback, send in questions,
5.1.3
and, where warranted, receive answers. The Participants shall provide this
level of customer support and use the feedback provided by passengers to
improve service.
The system shall support a minimum of 20 simultaneous users per passenger
5.1.4
car.
The system shall allow passengers continuous VPN connectivity on a best
5.1.6
efforts basis subject to backhaul availability.
The Onboard Wi-Fi network shall provide the ability to filter the type of
5.1.7
content allowed (e.g., blacklist URLs, radio, video and audio streaming).
The system shall adhere to industry standards for Wi-Fi. The system shall
5.1.8
provide WPA2 security as an option to be used at Amtrak’s discretion.
There shall be dynamic allocation of bandwidth to passengers so that as more
5.1.9
users are added bandwidth is allocated equally to them.
To provide a satisfactory user experience, available network resources have to
be fairly shared among all connected passengers. The Participants solution shall
5.1.10
actively manage passenger access by implementing fair-usage policies agreed to
by Amtrak on an ongoing basis.

17
6. Clarification Questions
To assess responses from Participants, Amtrak requires detailed information about the
solutions proposed and how they will meet the requirements defined in the RFQ. To this
end, Amtrak requires Participants to provide specific answers to questions listed in the
rest of this section.

Cellular Network Connectivity

1. What are your plans for the cellular links? Which operators will provide
access?
2. How many cellular cards do you plan to install on a single train set? Will
they operate concurrently? Please describe how you plan to optimize network
performance, given the bandwidth limitations of cellular networks.
3. If multiple networks do not operate concurrently, how is network selection
done? On which parameters is the choice based? How frequently can a change be
made?
4. If multiple networks operate concurrently, how is the overall traffic from
the network allocated to different networks? How frequently can a change be made
in the allocation? Is the traffic from the train assigned to different networks at the
packet, service flow, session, or virtual network level? Or is a different criterion
used? Can you assign different traffic types to different networks (e.g., block video
traffic from passenger free Internet access over the cellular network but allow it
over a network used for Amtrak business purposes)?
5. If multiple networks operate concurrently, what is the network overhead
required to operate such networks? What is the impact on performance (e.g.,
increase in latency, dropped connections) from the overhead imposed by your
solution? Does your solution require additional data processing, equipment, and/or
software in a data center?
6. What type of relationship do you expect to establish with mobile operators
to ensure that you can rely on a good connection over the cellular network (i.e.,
that your account is not throttled and has no strict bandwidth limitations) at an
affordable price? Can you secure contracts with unlimited bandwidth allowances?
Virtual Networks
7. Will your solution support multiple virtual networks? Will it be able to
segregate traffic into multiple completely insulated networks? (i.e., Operational
applications and passenger Internet traffic)?
8. Will your solution be able to provide the necessary security levels to
protect Operational applications? Can you dynamically change the capacity
allocation among virtual networks?
18
Performance and Service Requirements:
9. What are the maximum latency, jitter, and packet losses for your solution?
Will the Wireless Network successfully and reliably support video and audio
applications, as well as Internet-based applications such as Skype, Hulu and
YouTube?
10. What amount of bandwidth does your proposed Wireless Network provide?
What are your upgrade roadmap and the corresponding performance
improvements?
11. What do you see as potential bandwidth bottlenecks in the Wireless
Network? How can they be addressed?
12. Among the list of applications that the Wireless Network is expected to
support, are there any applications that may not run consistently or as expected? If
so, why and what remedies are available?
13. What level of customer support are you able to offer to passengers? What
level of customer support do you recommend? What channels will passengers have
to submit queries and receive answers (e.g., phone, email, mail) and what are your
commitments in terms of addressing requests (e.g., time it takes to reply to queries,
process used to address issues raised)? How will you forward the information from
users to Amtrak? How will this information be used to improve services?
14. If you have any existing on-train network deployments with rail operators
that support applications such as selling tickets or authorizing credit cards over the
network using dedicated mobile devices, how does your network meet the credit
card industry security requirements (United States or abroad) along each
component of the network infrastructure (including the Wi-Fi in-train network)?
Other
15. Network operations: How will you monitor the performance of the
Wireless Network? What metrics will you able to provide to Amtrak? What
network management software tools will you use? Do you have a network
management and monitoring tool that will be available to Amtrak? What
functionality will it support?
16. Web-based monitoring system: What will be the data base structure? How
many trains can each instance of the database can support? What server hardware
is required?
17. What is the licensing structure for the system? How many licenses will be
required?
18. Data Center: How many data centers will be required to support the
national system? How close does a data center need to be to a given train line to
effectively support the system?

19
7. Appendix 1 - Amtrak Fleet

20
21
8. Appendix 2 – Amtrak Train Specifications
Amtrak requires that Participants submit a detailed design proposal for each train listed below. Detailed specifications for each car
can be found in Attachment 2.

8.1 Northeast Regional

The typical Northeast Regional consist usually includes 8 cars (see detailed table below) and operates between Boston and
Washington, DC.

Car Type Number of Wi-Fi Required Passenger

cars (Y/N) Capacity
Amfleet-I “Capstone” Business Class Coach 1 Y 64
Amfleet-I Coach (ADA) 2 Y 76
Amfleet-I All-Table Dinette 1 Y 56
Amfleet-I Coach (ADA) 4 Y 76
Note: The equipment is listed in the order that it is most often used in the consist.

22
8.2 Capitol Limited (Washington, DC-Chicago)
The typical Capitol Limited consist usually includes 9 cars (see detailed table below) and operates between Washington, DC and
Chicago.

Car Type Number of Wi-Fi Required Passenger

cars (Y/N) Capacity
Heritage Baggage Car 1 N n/a
Superliner Transition Dorm 1 Y 35
Superliner Sleeper 2 Y 44
Superliner Diner 1 Y 72
Superliner Sightseer Lounge 1 Y 70
Superliner Baggage Coach 1 Y 62
Superliner Coach 2 Y 74
Note: The equipment is listed in the order that it is most often used in the consist.

23
9. Appendix 3 – Car Type Descriptions
Superliner

The Superliner is a bi-level passenger car used by Amtrak on long haul trains operating
outside of the Northeast Corridor. The initial cars were built by Pullman-Standard in the
late 1970s and a second order was built in the mid 1990s by Bombardier Transportation.
As delivered, the cars came in various configurations, including coach, diner, and sleeper.

Amfleet

The Amfleet series of intercity railroad passenger cars was built by the Budd Company in
two phases during the late 1970s and early 1980s. Today, Amfleet cars are used
extensively throughout the Amtrak system outside the western United States.

The cars were built in two phases from 1975-78, and 1981-83. A total of 492 Amfleet I
cars (406 coaches and 86 cafes) were built, and are generally used for corridor services.
A total 150 Amfleet II cars (125 coaches and 25 lounges) were built, and are generally
used for long distance services. Amfleet cars were constructed in varying layouts
including coach, business class, and dining cars.

24