CREW: General Services Administration: Regarding E-Gov Travel: 1/21/2010 - Vol 1 - 1 Att 15, eTS Trace Ability Matrix

Attachment 15
eTS Traceability Matrix
Proposal
RFP Reference
Reference
C.3.2.1 Types of Travel – Requirements
1. Temporary duty (TDY) travel (including foreign and domestic); 2.1.1.b, Page 1-10
2. Local travel; 2.1.1.c, Page 1-10
3. Long term TDY and long term local travel (including foreign and
2.1.1.d, Page 1-10
domestic);
4. Invitational travel; and 2.1.1.e, Page 1-10
5. Non-Federally sponsored travel. 2.1.1.f, Page 1-10
C.3.3.1 Services – Requirements
1. The Contractor shall supply all services and support capabilities
2.1.2.a, Page 1-10
required to host and deploy the eTS solution to Federal agencies.
2. The Contractor shall deliver the eTS via a web-based, self-service 2.1.2.a, Page 1-10
environment supplemented with phone, fax, person-to-person, and
other customer support modalities as applicable. 2.4.a, Page 1-23
3. The Contractor shall be responsible to determine detailed
specifications necessary to meet or exceed the mandatory 2.1.b, Page 1-8
requirements and objectives described herein;
4. Contractor services, resources, and capabilities required under this
SOO shall include, but may not be limited to:
a) Information technology services and support capabilities; 2.3.a, Page 1-17
b) Federal travel process and Federal travel management 2.1.2.a, Page 1-10
expertise; 2.1.5.e, Page 1-14
c) Web-based reservation service (online booking engine); 2.2.f, Page 1-16
2.1.2.a, Page 1-10
d) Implementation planning and support for Federal agencies;
2-6.1.a, Page 2-18
2.1.2.a, Page 1-10
e) Training for all eTS user roles; and
2.7.a, Page 2-56
f) Customer support (including eTS functional support,
technical support for related IT problems, and assistance with 2.4.2.d, Page 1-28
travel arrangements).
C.6.1.1 Basic Capabilities and Characteristics – Requirements
1. The eTS shall provide a web-based, end-to-end travel management
environment to plan, authorize, arrange, process, and manage official 2.1.3.a, Page 1-11
Federal travel;
2. The eTS shall support all Federal travel processes including, but not
limited to, travel planning and cost estimating, travel authorization, 2.1.3.a, Page 1-11
booking of travel reservations and travel arrangements,
filing/processing/approval of official travel claims, travel reporting 2.1.3.h, Page 1-12
and business intelligence; travel-related data exchange, etc.;
3. The eTS shall present all services, functionality, and user support
through a single World Wide Web (WWW) Uniform Resource
Locator (URL) portal. At its discretion, the Government will provide
2.1.3.b, Page 1-11
an appropriate “.gov” URL for the Contractor’s eTravel portal, or
establish a link from another “.gov” website to the Contractor’s
eTravel portal;
4. The eTS shall provide web-based delivery of services and data
exchange with access and input possible by all users and approving 2.1.3.c, Page 1-11
officials at their official station and remote locations;
eTS Traceability Matrix v2.0 Page 15-1 of 45 7/24/2003

Attachment 15
Proposal
RFP Reference
Reference
5. The eTS shall provide the capability to centrally manage the Federal
travel procedures through a common, configurable, customer-centric, 2.1.3.d, Page 1-11
self-service, web-based environment;
6. The eTS shall allow policy updates to be made in real-time, and allow
travel policy to be administered with or without exceptions at the 2.1.3.j, Page 1-12
Federal agencies’ option;
7. The eTS shall provide access to and control of all Government
preferred travel suppliers and negotiated rates for booking travel 2.1.3.e, Page 1-11
reservations.
8. The eTS shall maintain the order of precedence for executing travel
steps (i.e., authorization must precede a voucher, etc.) and adequate
2.1.3.f, Page 1-11
separation of duties (e.g., for trip approval, travel voucher approval,
and travel voucher payment);
9. The eTS shall provide controls to prevent the creation of duplicate
2.1.3.f, Page 1-11
travel documents;
10. The eTS shall provide for an audit trail on historical data that
2.1.3.f, Page 1-11
identifies input, correction, amendment, cancellation and approval;
11. The eTS shall provide a standard data input/output to support the
exchange of data with agency business systems (e.g., financial, human
resources, etc.), including the capability for near real-time travel- 2.1.3.i, Page 1-12
related transactions (e.g., funds availability checking, traveler profile
creation or updates, etc.); and
12. The eTS Contractor shall be required to work and coordinate with
Government subject matter experts and other travel partners (e.g., the 2.1.3.k, Page 1-12
vendor for the FedTrip™ online reservation system; TMCs; etc.) to 3.5.a, Page 1-37
integrate and deploy the eTS.
13. The Government shall own all federal data generated by and/or stored
2.1.3.b, Page 1-11
in the eTS.
14. The eTS shall allow Government policies, business rules, vendor
contract parameters, permissions, and profiles to be updated without 2.1.3.j, Page 1-12
the need for programming.
C.6.1.2 Basic Capabilities and Characteristics – Objectives (listed in
order of descending importance)
1. The eTS should provide a common, streamlined travel management 2.1.3.a, Page 1-11
service available Governmentwide that automates and fully integrates 2.2.a, Page 1-15
Federal travel management functions; 2.2.d, Page 1-16
2. The eTS should provide a common, consolidated travel process at a
Governmentwide level with configurability at the department, agency, 2.1.3.d, Page 1-11
and subordinate organization levels within the limits allowed by the 2.1.3.j, Page 1-12
applicable travel regulations;
3. The eTS should provide a consistent, web-based, self-service
environment with an intuitive graphical user interface and sufficient
system prompts, clearly understandable dialog boxes, and informative
2.1.3.d, Page 1-11
messages to guide users through logical, sequential processes and
collect all necessary information within all functionalities and
modules;

Attachment 15
Proposal
RFP Reference
Reference
4. The eTS should provide web-based administration of travel policy
with configurable business rules (e.g., Governmentwide, agency level,
2.1.3.d, Page 1-11
executive employee policy, staff employee policy, etc.) for all
applicable functionalities;
5. The eTS should utilize automated routing, workflow, messaging, and 2.1.3.f, Page 1-11
notifications; 2.1.3.g, Page 1-12
6. The eTS should provide comment fields and local fields within all
functionalities to support organization- and agency-specific business 3.3.d, Page 1-34
processes and audit requirements;
7. The eTS should support the use of personal charge/credit cards where 2.2.i, Page 1-16
authorized; 3.8.d, Page 1-42
8. Offerors should take advantage of and use appropriate commercial
standards wherever possible to streamline the acquisition, enhance
2.4.e, Page 1-25
interoperability, and reduce costs provided that all mandatory
requirements stated herein are met or exceeded;
9. Offerors should support establishment of Federal eTravel standards,
incorporating appropriate commercial and government best practices 2.4.e, Page 1-25
into their eTS solutions; and
10. The eTS should provide support for wireless and personal digital
2.1.3.c, Page 1-11
assistant (PDA) devices.
C.6.2.1 Policy Compliance – Requirements
1. Comply with the FTR and other applicable Federal travel regulations
in effect on the date of contract award and any subsequent
2.1.5.b, Page 1-13
amendments thereto on their effective date unless otherwise specified
by the Government;
2. Comply with 6 FAM Volume 100 regulations in effect on the date of
contract award for TDY travel of Foreign Service and other applicable
classes of Federal travelers, and comply with any subsequent 2.1.5.g, Page 1-15
amendments thereto on their effective date unless otherwise specified
by the Government;
3. Meet the accessibility requirements of 36 CFR 1194 specified herein
to the maximum extent possible with supplies, services, techniques, or
assistive technologies that are available in the commercial 2.1.5.f, Page 1-14
marketplace in time to meet the delivery requirements of this
solicitation; and
4. Comply with the mandatory JFMIP Travel System Requirements in
effect on the date of contract award and as may be modified herein,
2.1.5.g, Page 1-15
and comply with any subsequent revisions thereto on their effective
date unless otherwise specified by the Government.
C.6.3.1.1 User Roles, Use Cases and Account Access – Requirements
1. Offerors shall use Attachment 6, Notional eTravel Service Use Cases,
as the foundation from which user roles, detailed use cases, and the 2.3.e, Page 1-18
eTS Concept of Operations (CONOPS) is developed;
2. Offerors shall determine and analyze Federal travel requirements in
order to establish the eTS Concept of Operations (CONOPS), user 2.3.d, Page 1-18
roles, and use cases;
3. Offerors shall ensure that the eTS supports establishment of user
2.3.c, Page 1-17
accounts with specific permissions and access rights; and

Attachment 15
Proposal
RFP Reference
Reference
4. Offerors shall ensure that the eTS prevents intentional or inadvertent
access to data and functionality not specifically associated with 2.3.b, Page 1-17
particular user roles, accounts, and related permissions.
5. Offerors shall define data element access for all user roles to meet
role-specific functionality, Privacy Act, and other security capabilities 2.3.b, Page 1-17
and characteristics defined herein.
C.6.3.1.2 User Roles, Use Cases and Account Access – Objectives
(listed in order of descending importance)
1. Offerors should address all business travel processes outlined in the
eTravel Business Process Flow Diagram (Attachment 1) and Notional 2.3.e, Page 1-18
eTS Operational Architecture (Attachment 2);
2. The eTS should provide the ability to add user accounts and traveler
2.3.c, Page 1-17
profiles limited only by the concurrent user mandatory requirement;
3. Offerors should describe use cases in simple text to facilitate 2.1.3.d, Page 1-11
communication among Government travel subject matter experts who
may not have specialized IT training; and 2.3.d, Page 1-18
4. Offerors may propose additional or alternative user roles and use cases
that provide the most effective standardized eTS model and
functionality across Federal agencies. The Government may limit the
2.3.d, Page 1-18
number of distinct Federal user roles to six at its discretion; offerors
should provide sound justification if more than six Federal user roles
are proposed.
C.6.3.2.1 eTravel Portal – Requirements
1. The Contractor shall establish an eTravel web portal that serves as the
3.1.a, Page 1-31
gateway to the eTS Federal travel management environment;
2. The eTS portal shall provide a configurable environment that can be
used by all eligible users and provides access to all services and 3.1.a, Page 1-31
systems used within the eTS;
3. The eTS portal shall provide a search capability for travel documents
and information (e.g., authorizations, vouchers, regulatory 3.1.a, Page 1-31
information, etc.);
4. The eTS portal shall display terms of use and Privacy Act
notifications upon access and require user assent to the terms of use
3.1.a, Page 1-31
and data protection responsibilities at time of login in accordance with
Section C.6.4.3.3; and
5. The eTS portal shall provide a contract administration workspace
including a bulletin board for posting eTS contract documents and
messages to and from the Contractor, GSA, and Federal agencies. 3.1.b, Page 1-32
Purposes envisioned include the posting of messages by Federal
agencies interested in pooling their task order requirements.
6. The eTS portal shall provide the ability for users to create and
maintain their traveler profiles online (subject to specific data element 3.1.b, Page 1-32
permissions);
C.6.3.2.2 eTravel Portal – Objectives (of equal importance)
1. The eTS should provide a single sign-on to access all eTS
functionality (utilizing the eAuthentication Gateway as subsequently 2.2.c, Page 1-16
described);

Attachment 15
Proposal
RFP Reference
Reference
2. The eTS should deliver functionality proactively, presenting it to the
user as needed and limiting the need to “drill down” to access eTS 3.1.b, Page 1-32
capabilities;
3. The eTS should provide the capability to establish links to
Governmentwide, GSA, and agency-specific travel-related web sites,
documents, and resources. The eTS should provide links from the
eTravel portal to pertinent Federal travel policy and information 3.1.b, Page 1-32
resources (e.g., the FTR, per diem information, etc.). The eTS should
be capable of linking to services and data from other Government
portals and web-based systems; and
4. The eTS should provide the ability for non-Government travelers who
are authorized by a Government sponsor to register on the system and 5.8.a, Page 1-63
route their registration to the appropriate Government representative 3.15.c, Page 1-49
for account approval to support invitational travel.
C.6.3.3.1 Traveler Profiles – Requirements
1. The eTS shall provide for entry, retention, updating and deletion of
traveler profiles associated with and subject to the permissions of 3.2.a, Page 1-33
Federal or invitational travelers’ eTS accounts.
2. The eTS shall be capable of importing traveler profiles from agency
business systems or other external data sources in a standard data
format specified by the Contractor (e.g., comma delimited, etc.).
Federal agencies will be responsible for the quality assurance of
3.2.a, Page 1-33
traveler profile data provided for import to the eTS. The eTS vendor
will only be responsible to assure the fidelity of traveler profile data
imported into the eTS with the corresponding data provided by the
Federal agencies;
3. The eTS shall support the entry of traveler profile data online by all 3.2.a, Page 1-33
users (including non-Federal invitational travelers) via the compatible
web browsers. Federal agencies will be responsible for the quality
assurance of traveler profile data entered by the traveler via the web
browser; and
4. The eTS shall provide access to a Federal agency’s pertinent traveler 3.2.a, Page 1-33
profile data elements required for ticketing and fulfillment purposes to
the TMC(s) under contract to that agency. Access to specific data
shall be subject to Privacy Act and applicable System of Records
protections. The eTS shall send a notification to the Federal traveler’s
affiliated TMC(s) when his or her profile is modified; and
5. The eTS traveler profile shall be capable of entry and retention of the
following discrete data elements:
a) Traveler’s name, Social Security Number (SSN) and/or 3.2.a, Page 1-33
other employee identification number;
b) Agency/organization, position title, and permanent duty 3.2.a, Page 1-33
station;
c) Office phone, mobile phone, mailing address, e-mail 3.2.a, Page 1-33
address, and payment address;
d) Possession of a Government Contractor-issued Individually 3.2.a, Page 1-33
Billed Charge Card

Attachment 15
Proposal
RFP Reference
Reference
e) Applicable accounting data such as default funding 3.2.a, Page 1-33
citations, individual billing account number(s), central billing
account numbers(s), third party payment account numbers,
bank account numbers, and corresponding Electronic Funds
Transfer (EFT) routing data (all of which must be able to be
manually overridden within any particular travel action); and
f) User role designation(s) and system permission level(s) (as 3.2.a, Page 1-33
established by appropriate agency travel administrator,
approver, or coordinator).
C.6.3.3.2 Traveler Profiles – Objectives (listed in order of descending
importance)
1. Traveler profile data within the eTS should be used to pre-populate
applicable data to the maximum extent possible within travel actions 3.2.b, Page 1-33
of all types (e.g., travel authorizations, reservation records, etc.); and
2. 3.2.b, Page 1-33
The eTS traveler profile should provide for entry and retention of the 3.4.a, Page 1-36
traveler’s default transportation and accommodation requirements and
3.5.d, Page 1-37
preferences (e.g., rental car class, seating preferences, ticketing
preferences, etc.) and travel program affiliations. 3.5.e, Page 1-37
3.2.a, Page 1-33
C.6.3.4.1 Travel Planning and Authorization – Requirements
1. The travel planning and authorization function of the eTS shall
provide the capability to create travel plans and authorizations,
3.3.c, Page 1-34
including detailed itineraries and related cost estimates that may be
retained separately or included in the travel authorization;
2. The eTS shall support the processing of various types of travel
authorizations including unlimited open, limited open, and trip-by- 3.3.a, Page 1-33
trip;
3. The eTS shall require the traveler to state the purpose of their trip in
3.3.c, Page 1-34
accordance with Appendix C, FTR 301, "Travel Purpose Identifier".
4. The eTS shall allow for the option of specific authorization or prior
3.3.a, Page 1-33
approved travel arrangements as required by FTR 301-2;
5. The eTS shall support the routing and approval of travel and
transportation authorization documents. It shall provide Federal
agencies flexibility with regard to the number and levels of approval 3.3.f, Page 1-35
required for travel authorizations, including cross-organizational
travel
6. The eTS shall allow rejection, correction, amendment, and
cancellation of the travel authorization with appropriate review and
approval controls, including text and code explanation fields. The
3.3.f, Page 1-35
eTS shall provide notification of rejection, correction, amendment,
and cancellation to the traveler, travel arranger, supervisory approver,
and financial approver as appropriate;
7. The eTS shall support the capability to identify whether the traveler
holds a Government travel charge card based upon data provided by
the employee’s agency. (Note: This requirement shall not be
3.3.c, Page 1-34
construed to affect the GSA SmartPay® contract or require GSA
SmartPay® contractors to exchange data with or permit linkage to
eTS.);

Attachment 15
Proposal
RFP Reference
Reference
8. The eTS shall support automation of near real-time funds availability
checks, funds commitment/obligation, and the ability to transfer
accounting data with agency business systems within the standard data
3.3.f, Page 1-35
input/output content. It shall provide the capability to report funds
availability when appropriate (e.g., for specific TDY trip
authorization);
9. The eTS shall provide verification that authorization for travel exists
3.3.f, Page 1-35
and that funds are available;
10. The eTS shall provide the capability to process travel authorizations
3.3.e, Page 1-34
with split fiscal year funding and with multiple lines of funding;
11. The eTS shall calculate estimated authorized per diem (factoring in
leave and non-work days, interrupted travel, reduced per diem rates,
and actual expenses) as well as meals and incidental expenses (M&IE)
3.3.c, Page 1-34
based on the TDY location(s) and the dates of travel. The eTS shall
recalculate “should cost” amounts and perform revised funds
availability checks as applicable for travel plan or itinerary changes;
12. The eTS shall provide the capability to display to the user and capture
within the travel authorization defined notes and messages regarding
certification statements, Privacy Act Statement, standard clauses for
3.3.a, Page 1-33
required receipts, supporting documentation requirements,
justification statements for use of special travel arrangements, etc.;
and
13. The eTS shall provide the capability to accommodate and incorporate
the services of the TMC(s) under contract to Federal agencies and 3.6.a, Page 1-39
their appropriate Commercial Reservation System(s) (CRS).
C.6.3.4.2 Travel Planning and Authorization – Objectives (of equal
importance)
1. The eTS should provide the capability to authorize travel for multiple
N/A
travelers on the same authorization;
2. The eTS should allow for processing an annual unlimited open travel 3.3.g, Page 1-35
authorization without recording an estimated obligation amount for
each trip prior to travel; 3.3.a, Page 1-33
3. The eTS should support the identification and documentation of all 3.3.h, Page 1-35
modes of transportation (including rail, bus, ship, etc.) authorized by
the FTR and other applicable travel regulations; 3.3.c, Page 1-33
4. The eTS should clearly identify trip legs or segments in the travel 3.3.h, Page 1-35
plan, itinerary, and on-screen, and identify “no cost” trip segments
(i.e., where personal leave is taken during TDY travel); and 3.3.c, Page 1-34
5. The eTS should support the capability to associate eTS travel
authorization with the activation and deactivation of Government
Contractor-issued Individually Billed Travel Charge Cards (Note: 3.7.c, Page 1-40
Activation/deactivation of the travel charge cards will be the
3.7.d, Page 1-40
responsibility of the Federal agencies. Furthermore, this objective
shall not be construed to affect the GSA SmartPay® contract or 3.3.h, Page 1-35
require GSA SmartPay® contractors to exchange data with or permit
linkage to eTS.).
C.6.3.5.1 Reservations – Requirements

Attachment 15
Proposal
RFP Reference
Reference
1. The eTS shall provide the capability to make both self service and
non-self service reservations for the following transportation and
travel arrangements, at a minimum:
a) Air travel on domestic and international common carrier
flights, including all GSA City-Pair contract carriers and
flights as well as published non-contract Government (“me 3.4.a, Page 1-36
too”) fares and other discount fares which are advantageous to
the Government;
b) Domestic and international car rental reservations with all
Military Traffic Management Command (MTMC) or other
3.4.b, Page 1-36
Government preferred sources at or below the applicable
ceiling rate;
c) Domestic and international lodging suppliers participating
in the Federal Premier Lodging Program (FPLP) or other
Government preferred sources, including designation and 3.4.a, Page 1-36
tracking of the use of Federal Emergency Management
Agency (FEMA) approved lodging properties;
d) Domestic common carrier rail and bus travel; and 3.4.b, Page 1-36
e) Other common carrier travel, e.g., ship transportation; 3.4.b, Page 1-36
2. The eTS self service reservation capability shall include:
a) An online booking engine (web-based reservation service)
of the Contractor’s choice that meets or exceeds the 3.5.a, Page 1-37
mandatory requirements of Section C.6.3.6.1;
b) The capability to accommodate the FedTrip™ online
booking engine on an interim basis through September 30,
2004. Accommodation of FedTrip™ is defined as supporting
its use by Federal travelers and TMCs under contract to
Federal agencies as an online booking engine for the eTS.
There is no mandatory requirement (or objective) for the 3.4.c, Page 1-37
automated integration of FedTrip™ with other eTS
functionalities. Accommodation may be limited to travelers
reserving travel through FedTrip™ and then manually entering
travel arrangement information into eTS travel planning,
authorization, and voucher functions;
3. The eTS shall be capable of accommodating the services of TMCs
3.4.a, Page 1-36
under contract to Federal agencies for non-self services reservations.
4. The eTS shall provide access to all Government preferred suppliers
and rates for transportation, lodging, and rental car reservations. The
3.4.a, Page 1-36
eTS shall restrict access to Government-only rates to Federal
employees and other authorized users of those rates;
5. The eTS shall be capable of modifying and canceling all such
reservations prior to ticket issuance without Government incurrence of
3.4.b, Page 1-36
a transaction fee (as defined in Section B of this solicitation) and
subject to applicable carrier or supplier cancellation provisions;
6. The eTS shall require the user to identify the appropriate FTR
exception and provide justification for the use of all non-preferred or
3.4.b, Page 1-36
non-contracted providers, and/or non-U.S. flag air carriers when
booking such reservations.

Attachment 15
Proposal
RFP Reference
Reference
C.6.3.5.2 Reservations – Objectives (listed in order of descending
importance)
1. Offerors should propose expedited agency TMC accommodation
schemes to facilitate adoption of the eTS and speed eTS transaction 3.4.a, Page 1-36
volume growth;
2. The eTS Contractor is not required to provide traditional TMC
reservation services. In order to achieve the eTravel vision of a
unified travel management service, and to permit Federal agencies to
obtain complete end-to-end travel management services from an eTS
vendor, the eTS offering should provide non-self service reservation
capabilities that meet the requirements for Travel Agent 3.4.a, Page 1-36
Services/Travel Management Center Services for reservations
specified in the GSA Travel Services Solutions solicitation
(Solicitation No. FBGT-VH-030001-B available at
http://www.eps.gov/spg/GSA/FSS/FBG/FBGT-VH-030001-
B/listing.html);
3. The eTS should provide access to as many domestic and international 3.4.a, Page 1-36
lodging sources as possible; 3.4.d, Page 1-37
4. The eTS should take advantage of promotional and spot discount
3.4.d, Page 1-37
lodging rates to the maximum extent possible; and
5. The eTS should support the integration and passing of pertinent
reservation data from the TMCs under contract to Federal agencies 3.2.a, Page 1-33
and from the eTS online booking engine to associated travel actions 3.4.a, Page 1-36
(e.g., travel authorizations, vouchers, etc.) within the eTS.
C6.3.6.1 eTS Online Booking Engine – Requirements
1. The eTS online booking engine shall automatically enforce and

monitor compliance to the appropriate Federal and agency-configured
travel policies during the reservation process. and shall control access
to all Government negotiated travel rates (e.g., City-Pair airfares, etc.). 3.5.b, Page 1-37
It shall allow users to override travel policy by providing the reason
for the exception and provide exception coding and text explanation
capabilities;
2. The Contractor shall provide the ability for Government designated
TMC(s) to use the eTS online booking engine and permit travel
3.5.c, Page 1-37
reservations made within the booking engine to be retrieved in real
time by agencies’ TMCs;
3. The eTS online booking engine shall provide estimates of travel costs
3.5.c, Page 1-37
prior to making an actual reservation;

Attachment 15
Proposal
RFP Reference
Reference
4. The eTS online booking engine shall provide published and
Government negotiated airfares, lodging rates, and car rental rates. It
shall clearly identify preferred and mandatory travel suppliers
wherever applicable. It shall display Government contracted and
Government preferred travel suppliers first in ascending rate order and
filter out non-compliant choices based on agency/organizational
3.5.d, Page 1-37
policy rules (e.g., preferred suppliers only). Failure to use
Government-negotiated rates shall require appropriate justification
(with reason/exception code and text capabilities). The Offeror shall
utilize the reason/exception codes in Attachment 7 for negotiated
airfares and shall propose configurable reason/exception codes for all
other travel suppliers.
5. The eTS online booking engine shall include all global commercial
airport destinations and display available airfares for domestic and
international air travel. It shall display alternate airport/city options
for a specific destination. It shall provide appropriate and accurate
Government rates under the GSA City-Pair Program, published non-
contract Government fares (fare code DG or “me too” fares), and
other discount fares in a real-time environment. It shall support an
unlimited number of City-Pair fares. It shall display all applicable
flights, destination information, flight schedules, and other pertinent 3.5.e, Page 1-37
flight information for all flights listed. It shall clearly display the
availability of appropriate class seating and the airfare rules for all
available fares. It shall reserve airline travel accommodations for
airlines listed in GDSs in a real-time 24/7/365 environment Failure to
use Government-negotiated rates shall require appropriate justification
(with reason/exception code and text capabilities). The Offeror shall
utilize the reason/exception codes in Attachment 7 for negotiated
airfares
6. The eTS online booking engine shall provide appropriate and accurate
Government rates in a real-time environment for FPLP or other
Government preferred lodging suppliers and shall designate FEMA
approved lodging properties. It shall display FEMA approved lodging
properties ahead of those which are not FEMA approved. It shall
reserve lodging accommodations in a real-time 24/7/365 environment. 3.5.f, Page 1-38
It shall require appropriate justification (with reason/exception code
and text capabilities) in accordance with Pub. L. 5 USC 5707a and
resulting FTR requirements for failure to use FEMA approved
lodging. The Offeror shall propose configurable reason/exception
codes for lodging suppliers;
7. The eTS online booking engine shall provide appropriate and accurate
rates for domestic and international car rentals in a real-time
environment for all MTMC or other Government preferred car rental
agencies at or below the applicable Government ceiling rate. It shall
reserve rental car accommodations in a real-time 24/7/365 3.5.e, Page 1-37
environment Failure to use Government-negotiated rates shall require
appropriate justification (with reason/exception code and text
capabilities). The Offeror shall propose configurable reason/exception
codes for all car rentals suppliers;

Attachment 15
Proposal
RFP Reference
Reference
8. The eTS online booking engine shall support one-way, round-trip, and
multiple destination itineraries. It shall verify segment date/time
sequence during the reservation process to ensure logical itineraries
and permissible connections. It shall consolidate all travel segments 3.5.g, Page 1-38
for an itinerary into a single record, and shall creates all necessary
fields in the Passenger Name Record (PNR) within the GDS(s) and
applicable TMC reporting systems;
9. The eTS online booking engine shall allow users to modify and/or
cancel reservations prior to ticket issuance without Government
incurrence of a transaction fee (as defined in Section B of this
solicitation). It shall allow the user to re-price an itinerary after initial 3.5.h, Page 1-38
creation when modifications are made, and route the re-priced
itinerary for notification or resubmit the revised authorization for re-
approval;
C.6.3.6.2 eTS Booking Engine – Objectives (listed in order of
descending importance)
1. The eTS online booking engine should provide the ability to compare
carrier fares as well as rental car and lodging rates to support selection
of the itinerary, carrier, and/or vendor(s) most advantageous to the
3.5.i, Page 1-38
Government. This should include the capability to display fare
comparisons from multiple fare sources (i.e., City Pair fares vs. other
fares), alternate airports, etc;
2. The eTS online booking engine should be capable of reserving airline
travel accommodations for airlines not listed in GDSs in a real-time 3.5.i, Page 1-38
24/7/365 environment;
3. The Contractor should allow TMC reporting systems and TMC
created PNRs to be retrieved and/or viewed through the eTS online 3.5.j, Page 1-38
booking engine. It should work with any TMC mid-office system(s) 3.5.g, Page 1-38
to meet file finishing requirements;
4. The eTS should provide the ability to change the traveler’s itinerary
3.5.k, Page 1-38
and reservations online after ticket issuance;
5. The eTS online booking engine should encode and decode airline and
3.5.k, Page 1-38
city/airport codes for the traveler;
6. The eTS online booking engine should provide graphical seat maps 3.5.k, Page 1-38
and the capability to reserve seat assignments where commercially
available;
7. The eTS should provide the ability to make self service international 3.5.k, Page 1-38
air travel reservations that comply with all applicable regulations;
8. The eTS should support the creation, storage, and shared use of 3.5.k, Page 1-38
standard individual and shared trip templates;
9. The eTS online booking engine should provide appropriate and
accurate Government rates for domestic rail travel and reservation of
rail travel accommodations in a real-time 24/7/365 environment. It
3.5.l, Page 1-38
should provide domestic rail schedules with published and negotiated
fares, seats, and destination information. Rail travel should be based
upon departure and destination cities rather than airport codes;
10. The eTS should provide the ability to automatically identify and
communicate exceptions to travel policy to multiple recipients (e.g., 3.5.m, Page 1-39
traveler, approvers, etc.);

Attachment 15
Proposal
RFP Reference
Reference
11. The eTS should provide the traveler or travel arranger with access to
3.5.k, Page 1-38
the traveler’s previous trip itineraries;
12. The eTS should have the ability to reserve ship and bus transportation
3.5.n, Page 1-39
if commercially available;
13. The eTS should have the ability to book shuttle services to and from
3.5.n, Page 1-39
airports; and
14. The eTS should have the ability to designate frequent or loyal traveler
3.5.n, Page 1-39
program account number(s) in reservations.
C.6.3.7.1 Fulfillment – Requirements
1. The eTS shall provide fulfillment services and associated customer
support capabilities for Federal travel; 3.6.a, Page 1-39
2. The eTS shall be capable of fulfilling and supporting self service

reservations made through the eTS online booking engine and/or the
FedTrip™ online booking engine. Alternately, these self service
reservations may be fulfilled by TMCs under contract to Federal 3.6.a, Page 1-39
agencies, subject to the terms of those contracts;
3. The eTS shall be capable of accommodating the fulfillment services of

3.6.a, Page 1-39
TMCs under contract to Federal agencies;
4. The eTS shall provide electronic ticketing as the default option for all
3.6.b, Page 1-39
common carriers that support electronic ticket issuance;
5. The eTS shall ensure that the corresponding travel authorization has
been approved prior to ticket issuance with the ability to override this 3.6.b, Page 1-39
business rule by allowable exceptions (e.g., emergency travel);
6. The eTS shall be capable of processing and crediting cancelled or
unused tickets and partial fare refunds subject to applicable carrier or
3.6.c, Page 1-39
supplier cancellation provisions with attendant expense and
accounting adjustments; and
7. The eTS shall process allowable credits resulting from the
cancellation of electronic tickets, the turn-in of unused paper tickets,
or partial fare refund transactions promptly and within the time limit
generally accepted as industry best practice. The eTS shall ensure that
3.6.c, Page 1-39
credits and cancellations are accountable to the applicable travel
authorization number and billing account. The eTS shall reflect those
credits within all applicable functionalities as well as in the standard
data output provided to interfacing agency business systems.
C.6.3.7.2 Fulfillment – Objectives (listed in order of descending
importance)
1. Offerors should propose expedited agency TMC incorporation schemes
to speed agency adoption of the eTS and eTS transaction volume 2.1.3.k, Page 1-12
growth; and

Attachment 15
Proposal
RFP Reference
Reference
2. The eTS Contractor is not required to provide traditional TMC
fulfillment services. In order to achieve the eTravel vision of a unified
travel management service, and to permit Federal agencies to obtain
complete end-to-end travel management services from an eTS vendor,
the eTS offering should provide fulfillment capabilities that meet
3.6.a, Page 1-39
requirements for Travel Agent Services/Travel Management Center
Services for reservations specified in the GSA Travel Services
Solutions solicitation (Solicitation No. FBGT-VH-030001-B available
at http://www.eps.gov/spg/GSA/FSS/FBG/FBGT-VH-030001-
B/listing.html).
C.6.3.8.1 Travel Advance – Requirements
1. If the Government issues a travel advance, the eTS shall support entry,
processing, approval, as well as the payment and liquidation of
3.7.b, Page 1-40
Government funds. This function must support the tracking, aging,
and control of advances;
2. The eTS shall provide the capability to set, change, and apply
established limits on travel advances in accordance with the FTR, 3.7.c, Page 1-40
other applicable travel regulations, and agency policies;
3. The eTS shall provide for limiting the allowed advance based upon
transportation method, subsistence rates, miscellaneous expenses, and
3.7.c, Page 1-40
the traveler’s possession of a Government Contractor-issued travel
charge card;
4. The eTS shall make travel advance information for a particular travel
3.7.e, Page 1-41
authorization accessible in travel voucher preparation;
5. The eTS shall support integrated issuance and control of travel
advances with the travel voucher payment process to ensure that the
advance is liquidated or collected prior to the issuance of a payment to
3.7.e, Page 1-41
the traveler. The eTS shall also provide the capability not to liquidate
the advance when the traveler has been authorized a “retained” travel
advance in accordance with FTR Part 301-51;
6. The eTS shall provide for automatic aging of outstanding travel
advances based on the authorized end of trip date and generate follow-
3.7.b, Page 1-40
up notices to the travelers and approvers concerning delinquent
advances that may affect payroll offsets or other means of collection;
7. The eTS shall support the reporting of delinquent travel advances as
taxable income through the inclusion of appropriate data elements in 3.7.b, Page 1-40
the standard data output;
8. The eTS shall allow for and support the preparation and authorization
3.7.c, Page 1-40
of emergency travel advances; and
9. With regard to payment and liquidation functionalities for travel
advances, the eTS shall only be responsible for making pertinent
information available to agency business systems (e.g., financial and 3.7.b, Page 1-40
payroll systems) within its data exchange and application integration
capabilities.
C.6.3.9.1 Travel Vouchers – Requirements

Attachment 15
Proposal
RFP Reference
Reference
1. The eTS shall provide for the preparation, submission, and routing of
TDY travel vouchers to claim reimbursable expenses for official
travel. The eTS shall provide Federal agencies flexibility with regard
to the number and levels of approval required for travel vouchers, 3.8.c, Page 1-42
including cross-organizational travel. It shall allow for special routing
and approval levels for vouchers for certain classes/conditions of
travel as required by FTR 301-2;
2. The eTS shall provide a tracking system that will allow travelers,
approvers, payment offices, etc., to determine the status of any 3.8.d, Page 1-42
voucher/claim in process within the permissions granted to the user;
3. The eTS shall pre-populate appropriate data fields of the voucher
based on information contained within eTS from sources such as the
travel authorization (including any cash advance provided to the
3.8.a, Page 1-41
traveler when applicable), traveler profile, etc. The eTS shall permit
the user to manually override and edit any accounting data passed
automatically to the voucher;
4. The eTS shall provide the capability to create and modify travel
vouchers before final approval. It shall provide routing of vouchers to
the approving official upon submission by the traveler. It shall permit
the approving official to deny and remand the voucher back to the 3.8.c, Page 1-42
traveler, or approve it and forward it for payment. It shall require the
approving official to specify a reason for denial (by means of
configurable codes and text) for all vouchers denied;
5. The eTS shall allow for entry of the date of departure from, and return
to, the official duty station or any other place when travel begins,
3.8.a, Page 1-41
ends, or requires overnight lodging in order to calculate reimbursable
expenses and allowances;
6. The eTS shall support identification, documentation, and claims for
reimbursement of all modes of transportation (including bus, ship, 3.8.a, Page 1-41
etc.) authorized by the FTR and other applicable travel regulations;
7. The eTS shall calculate authorized per diem amounts adjusting for
leave and non-work days, interrupted travel, reduced per diem rates,
and actual expenses using appropriate per diem rates in effect for the
TDY location(s) and date(s) of travel. The eTS shall provide the
3.8.a, Page 1-41
personal vehicle mileage rate in effect on the date(s) and calculate
mileage allowance. The eTS shall allow the manual entry of approved
or official subsistence rates, mileage allowance, etc., if not available
within the eTS;
8. The eTS shall compute the M&IE allowance rates based on travel
completed and meals provided in accordance with FTR 301-11. The
M&IE shall be based on the rates below for the first and last days of
travel and any full days in between::
a) More than 12 hours but less than 24: 75% of the applicable
3.8.b, Page 1-42
M&IE rate
b) 24 hours or more, on:
i) Day of departure: 75% of the applicable M&IE rate; 3.8.b, Page 1-42
ii) Full days of travel: 100% of the applicable M&IE rate; 3.8.b, Page 1-42
iii) Last day of travel: 75% of the applicable M&IE rate; 3.8.b, Page 1-42

Attachment 15
Proposal
RFP Reference
Reference
9. The eTS shall process amended and reclaim vouchers with appropriate
review and approval controls, and provide the capability to update
related functionalities within eTS. It shall allow for special routing 3.8.c, Page 1-42
and approval levels for certain classes/conditions of travel as required
by FTR Chapter 301;
10. The eTS shall permit multiple vouchers submitted against a single
authorization for appropriate travel types (e.g., open travel
authorizations). It shall process partial/interim vouchers against a
travel authorization to expedite liquidation related to travel 3.8.f, Page 1-43
obligations. It shall provide a clear and unambiguous final voucher
indicator for the final claim submitted against an open travel
authorization;
11. The eTS shall provide the capability to display defined messages to
the user regarding:
a) Required receipts for lodging and authorized expenses
3.8.a, Page 1-41
incurred over $75; and
b) Requirements for supporting documentation, justifications,
and certification statements in accordance with the FTR and 3.8.a, Page 1-41
other applicable travel regulations.
12. The Contractor shall provide the capability and procedures with
appropriate messages to guide the user through the process for the
3.8.d, Page 1-42
surrender and handling of unused, partially used, or
downgraded/exchanged tickets; refund certificates, etc;
13. The eTS shall provide for configurable system-generated notices when
claims and supporting information have not been submitted in
3.8.a, Page 1-41
accordance with suspense dates, internal policies, and procedures
established by the agencies;
14. The eTS shall support payment of travel claims by means of its data
exchange and application integration capability. It shall support
within the standard data output a split disbursement mechanism that
allows the traveler to designate applicable amounts to be paid directly
to a Government travel charge card vendor and/or reimbursed to the 3.8.d, Page 1-42
traveler. It shall support within the standard data output recovery of
funds owed to the Government as a result of travel through offset of
the traveler’s salary, retirement credit, or other payment owed to the
employee;
15. The eTS shall provide for matching of travel vouchers with the travel
authorizations and provide for audit of the claim in accordance with
3.8.e, Page 1-43
the FTR and 6 FAM Volume 100 for temporary duty travel of all
civilian agency government travelers as applicable;
16. The eTS shall provide agencies and subordinate organizations the
capability to set sampling parameters for their travel vouchers for
audits, information requirements, or other purposes based on criteria
determined by the agency. These parameters may include random
3.8.a, Page 1-41
sampling, cost thresholds, travel type, traveler identity, etc.
(Statistical sampling requirements are contained in the GAO Policy
and Procedures Manual for Guidance of Federal Agencies, Title 7,
Fiscal Procedures.)
C.6.3.9.2 Travel Vouchers – Objectives (of equal importance)

Attachment 15
Proposal
RFP Reference
Reference
1. The eTS should provide for electronic notification to travelers of 3.3.f, Page 1-35
payments made by disbursing offices or for disallowance of a claim
3.5.m, Page 1-39
for an expense. It should allow for agency flexibility in defining such
message content; 3.9.c, Page 1-44
2. The eTS should provide the capability to enter the “Direct Billed”
amount for costs such as Online Payment and Collection (OPAC)
billings by the Department of State for employees stationed overseas,
2.2.h, Page 1-16
and for lodging, airline, and car rentals that are billed directly to the
agency for payment, but not included in the calculation of payment to
the traveler;
3. The eTS should provide the capability to accept and post Government
travel charge card transactions to a Federal traveler’s eTS account to
support voucher processing. It should allow travelers to assign posted
travel card charges to the appropriate voucher(s). (Note: This shall
not be construed to affect the GSA SmartPay® contract or require
GSA SmartPay® contractors to exchange data with or permit linkage
to the eTS. Federal agencies may post charge card transactions to the 3.13.h, Page 1-47
eTS directly or may authorize their charge card contractors to share
those transactions with the eTS if that service is supported without
additional cost to the Government and without adverse impact to the
GSA SmartPay® contract.) The eTS should support the designation
of personal expense amounts included in posted transactions to
prevent Government reimbursement for those expenses;
4. 2.1.3.f, Page 1-11
The eTS should generate, retain, and attach cost estimates and 2.1.3.g, Page 1-12
comparisons to the appropriate travel voucher to support constructive
cost travel claims; 3.3.c, Page 1-34
3.5.c, Page 1-37
5. 3.7.b, Page 1-40
The eTS should provide for matching of centrally issued passenger
3.13.f, Page 1-47
tickets with the appropriate travel authorizations and/or vouchers.
3.6.b, Page 1-39
C.6.3.10.1 Local Travel Vouchers – Requirements
1. The eTS shall provide the capability for users to prepare, submit, and
3.9.b, Page 1-43
route a local travel voucher for approval and payment;
2. The eTS shall compute local mileage allowances using the approved
3.9.a, Page 1-43
mileage rate in effect on the date(s) of travel; and
3. The eTS shall support funds availability checks,
commitment/obligation, and payment of local travel claims within its 3.9.b, Page 1-43
data exchange and application integration capabilities.
C.6.3.10.2 Local Travel Vouchers – Objectives (of equal importance)
1. The eTS should provide for electronic notification to travelers of
payments made by disbursing offices or for disallowance of a claim 3.7.b, Page 1-40
for an expense. It should allow for agency flexibility in defining such 3.9.c, Page 1-44
message content;

Attachment 15
Proposal
RFP Reference
Reference
support voucher processing. It should allow travelers to assign posted
travel card charges to the appropriate voucher(s). (Note: This shall
not be construed to affect the GSA SmartPay® contract or require
GSA SmartPay® contractors to exchange data with or permit linkage
to the eTS. Federal agencies may post charge card transactions to the 3.9.c, Page 1-44
eTS directly or may authorize their charge card contractors to share
those transactions with the eTS if that service is supported without
GSA SmartPay® contract.) The eTS should support the designation
of personal expense amounts included in posted transactions to
prevent Government reimbursement for those expenses.
C.6.3.11.1 Travel Receipts – Requirements
1. The eTS shall provide a means to associate hard copy travel receipts
(and/or travel receipt images if that capability is provided) with the 3.10.a, Page 1-44
corresponding travel voucher submitted for reimbursement.
C.6.3.11.2 Travel Receipts – Objectives (of equal importance)
1. The eTS should support submittal and storage of electronic images of
receipts that comply with applicable Internal Revenue Service (IRS) 4.5.a, Page 1-58
electronic receipt requirements;
2. The eTS electronic image support should include the capability to
submit electronic images of Federal travelers’ expense receipts by
upload via browser-based functionality and by facsimile for electronic 3.10.a, Page 1-44
attachment to the appropriate travel voucher. Receipt images should
be stored, indexed to, or associated with the applicable voucher; and
3. The eTS should support agency-specific policy regarding receipt
retention and provide guidance about that policy to the traveler when 3.10.a, Page 1-44
preparing a voucher.
C.6.3.12.1 Non-Federally Sponsored Travel – Requirements
1. The eTS shall provide the capability to authorize and report the
acceptance of payment or payment in-kind from non-federal sources
3.11.a, Page 1-44
to defray in whole or in part the cost of travel or related expenses of
Federal employees in accordance with FTR Chapter 304;
2. The eTS shall provide a mechanism to assure that non-federally
sponsored travel is administratively approved by the agency
3.11.b, Page 1-44
designated official(s) prior to final approval of the travel
authorization;
3. The eTS shall provide the capability to indicate the amounts and
entitlements to be paid by the Government and those to be paid by the
sponsoring organization. For example, if the Government authorizes
payment of the traveler’s meals and incidental expenses and the 3.11.a, Page 1-44
sponsoring organization is paying for the hotel and airfare (services
in-kind), then this arrangement must be clearly identified on the travel
authorization; and
4. The eTS shall display estimated amounts where actual amounts are
3.11.a, Page 1-44
not known.
C.6.3.12.2 Non-Federally Sponsored Travel – Objectives

Attachment 15
Proposal
RFP Reference
Reference
1. The eTS should support special authorizations and the capture of
3.13.h, Page 1-47
ethics documentation that may be required by Federal agencies.
C.6.3.13.1 Leisure Travel (If Functionality Is Provided) –
Requirements
1. The Contractor shall ensure that the leisure travel functionality is
provided at no cost to the Government as reflected in per-transaction
3.12.a, Page 1-44
fees, separately priced line items, etc., including any related costs for
development, maintenance, operation, customer support, etc.;
2. The eTS shall ensure that travelers cannot book City-Pair or other
Government-negotiated fares not authorized for personal use when 3.12.a, Page 1-44
making leisure travel reservations; and
3. The eTS shall ensure that leisure travel expenses are not claimed for
Government reimbursement, and that a method for direct payment by 3.12.a, Page 1-44
the traveler for leisure travel expenses is provided.
C.6.3.14.1 Accounting Capabilities – Requirements
1. Accuracy of eTS computations shall be in strict accordance with
Chapter 301 of the FTR and Sections 920 and 925 of the DSSR. The
eTS shall by default use official per diem rates and mileage rates in
effect on the date(s) of travel for the appropriate TDY location(s) and
3.13.b, Page 1-45
type(s) of travel. Per diem rates shall be based upon TDY location as
opposed to airport codes. The eTS shall allow the use of actual
expenses and conference rates in lieu of or in combination with per
diem rates, when authorized.
2. The eTS shall support near real-time funds certification and
commitment/obligation within its standard data exchange and 3.13.d, Page 1-46
application integration capabilities;
3. The eTS shall generate, record, store, and report financial accounting
data related to travel authorizations, travel advances, and travel 3.13.a, Page 1-45
vouchers in the standard data output;
4. The eTS shall support split disbursements, i.e., allow the agency
and/or traveler to designate applicable expenses to be paid directly to 3.13.f, Page 1-47
individually billed accounts or be reimbursed to the traveler;
5. The eTS shall provide the ability to cite multiple funding sources in
travel authorizations and vouchers. It shall allow agencies to establish
3.13.g, Page 1-47
default funding citations and payment modalities for various travel
services such as airfare, lodging, or rental car;
6. The eTS shall support the reporting of expenses for same day trips of
more than 12 hours but less than 24 hours with no lodging in the
3.13.f, Page 1-47
standard data output for interfaces to agency payroll systems for
inclusion in the employee’s Form W-2, Wage and Tax Statement;
7. The eTS shall track travel advances authorized against reimbursable
expenses after final voucher submittal and report the amount due to or 3.13.f, Page 1-47
owed by the traveler within the standard data output; and
8. The eTS shall accommodate non-Federally sponsored travel including
acceptance of payment and payment in-kind from non-Federal sources 3.13.h, Page 1-47
with appropriate authorization requirements.
C.6.3.14.2 Accounting Capabilities – Objectives (of equal importance)

Attachment 15
Proposal
RFP Reference
Reference
support voucher processing. (Note: This objective shall not be
construed to affect the GSA SmartPay® contract or require GSA
SmartPay® contractors to exchange data with or permit linkage to the
3.13.h, Page 1-47
eTS. Federal agencies may post charge card transactions to the eTS
directly or may authorize their charge card contractors to share those
transactions with the eTS if that service is supported without
GSA SmartPay® contract.);
2. The eTS should be Government fiscal year compliant (October 1
through the following September 30) for dating, indexing, and 3.13.i, Page 1-47
tracking of accounting functions; and
3. The eTS should have the ability to perform foreign currency
conversions at Government-approved conversion rates on the effective
date(s) of conversion, and should be able to account for foreign
3.13.i, Page 1-47
currency fluctuations. Examples of Government approved conversion
rates are those identified on Government travel charge card invoices
or other exchange rate publications to be determined prior to award.
C.6.3.15.1 Routing, Workflow, Notifications and System Messages –
Requirements
1. The eTS shall provide the capability to maintain the order of
precedence for executing each travel step (i.e., authorization must
precede a voucher, etc.), and the capability to override and change the 3.14.a, Page 1-47
order of precedence of the processing steps to handle unusual travel
demands.
C.6.3.15.2 Routing, Workflow, Notifications, and System Messages –
Objectives (of equal importance)
1. The eTS should provide electronic routing and workflow of travel
actions and notifications to the desktops of eTS users for information,
coordination, review, and approval/rejection based on agency or
subordinate organization policy and criteria. All rejection actions 3.14.b, Page 1-48
should require the documentation of the reason for rejection in text
and/or configurable code, and the reason for rejection should be
included in notifications of rejection provided to eTS users;
2. The eTS should create and forward messages to the traveler and/or
other designated recipients for information or action via SMTP,
MIME, or SMIME compliant E-Mail systems. Messages should
3.14.b, Page 1-48
contain hyperlinks to permit the user to access the related eTS travel
action directly from the message (with appropriate user authentication
required);
3. The eTS should support cross-organizational travel and provide cross- 3.8.e, Page 1-43
agency routing and workflow, leveraging existing (compatible)
4.4.b, Page 1-57
agency E-Mail systems and the eTS application integration
capabilities to the greatest extent possible; 3.14.b, Page 1-48

Attachment 15
Proposal
RFP Reference
Reference
4. The eTS should support conditional routing and notifications as
configured by agencies and subordinate organizations. This includes
the ability to manually or automatically (according to configurable
agency business rules) delegate approval actions to other users in the
3.15.d, Page 1-50
event of absence or routing delays. It also includes the ability to route
travel actions for approvals based on specific characteristics such as
international travel, conferences, request for actual expenses, specific
funding citations, etc;
5. The eTS should provide the capability to post messages within
specific travel action functionalities and display Governmentwide, 3.15.f, Page 1-51
agency-specific, and organization-specific messages to users 3.3.d, Page 1-34
regarding general information; and
6. eTS notifications and messages should include, but may not be limited
to, the following:
a) Pending travel action approvals;
b) Travel authorization or voucher approved or rejected;
c) Confirmation of reservations (made by traveler or travel
arranger in traveler’s name);
d) Confirmation of ticket issuance;
e) Timed reminders for overdue voucher;
f) Timed reminders for approval actions; 3.14.b, Page 1-48
g) Travel reimbursement made to account;
h) Travel advance deposited to account;
i) Split disbursement payments credited to account(s);
j) Defined messages regarding statements, justifications,
certifications, reasons codes, etc.; and
k) Informative messages, warnings, and dialog boxes to guide
users in the proper use of eTS functionalities.
C.6.3.16.1 System Administration – Requirements

1. The eTS system administration capability shall permit and provide for
centralized control of Governmentwide features and business rules as
well as support the management of configurable business rules and 3.15.a, Page 1-49
travel functions by departments, agencies, or subordinate
organizations;
2. The eTS shall provide the following system administration capabilities
at the Governmentwide and department/agency/subordinate
organization levels, as applicable:
a) User account administration including user roles, 3.15.a, Page 1-49
permissions, access controls, and security (including 3.15.c, Page 1-49
eAuthentication Gateway assurance level); 2.2.c, Page 1-16
b) Traveler profile administration including the ability to
add/modify/delete user profiles and add agency-specific data 3.15.e, Page 1-50
elements;
c) Scheduling of actions, events, and requirements on a 3.15.e, Page 1-50
recurring basis, including, but not necessarily limited to, daily,
weekly, biweekly, monthly, quarterly, and annual schedules;

Attachment 15
Proposal
RFP Reference
Reference
d) Creation and maintenance of messages to be displayed to 3.15.e, Page 1-50
users regarding general system information (including access
and Privacy Act statements), announcements, etc.;
e) Creation and maintenance of routing lists and workflows 3.15.e, Page 1-50
including the designation of approving officials;
f) Capability to establish and secure application of digital 3.15.e, Page 1-50
signatures;
g) Ability to backup and recover travel transactions; 3.15.e, Page 1-50
h) Provide for gathering and analyzing usage statistics; 3.15.e, Page 1-50
i) Ability to add/modify/delete per diem rates (M&IE 3.15.e, Page 1-50
allowances and lodging rates) by locality in accordance with
applicable Federal regulations;
j) Ability to add/modify/delete air carriers, destinations, and 3.15.e, Page 1-50
airfares;
k) Ability to add/modify/delete lodging suppliers, properties, 3.15.e, Page 1-50
FEMA approval designations, and rates;
l) Ability to add/modify/delete rental car suppliers, types, and 3.15.e, Page 1-50
rates;
m) Ability to change POV mileage rates; 3.15.e, Page 1-50
n) Ability to add/modify/delete agency and subordinate 3.15.e, Page 1-50
organization information including standard funding citations,
delegation of approving officials, etc.;
o) Remote system administration capability; and 3.15.e, Page 1-50
p) Ability to add/modify/delete rail, ship, and/or bus carriers, 3.15.e, Page 1-50
destinations, and rates (if online reservation capabilities for
those common carriers are provided).
C.6.3.16.2 System Administration – Objectives (of equal importance)
1. The eTS should provide the capability to add or modify “HELP” files,
“HELP” screens, and other “HELP” facilities to meet specific N/A
requirements of Federal agencies; and
2. The eTS should provide the ability to add/modify/delete agency- and
organization-specific data fields related to particular travel 3.15.a, Page 1-49
functionalities within the eTS.
C.6.4.1 Technology Capabilities and Characteristics – Requirements
1. The Contractor shall monitor the http://www.feapmo.gov/ site (with
principal concentration on the BRM and DRM) to remain aware of
2.4.g, Page 1-25
and incorporate applicable standards established for the FEA as a part
of ongoing technology refreshment.
2. The eTS shall provide a browser-based user interface and Federal
travel management environment accessible via a single Uniform
2.4.a, Page 1-23
Resource Locator (URL) portal on the World Wide Web. The portal
shall be capable of interoperating with the FirstGov Portal;
3. The eTS shall be client platform and operating system independent,
and shall be compatible with the Microsoft Internet Explorer browser
2.4.a, Page 1-23
(version 5.5 or later) and with the Netscape Navigator browser
(version 7.x or later);

Attachment 15
Proposal
RFP Reference
Reference
4. The eTS shall not require any client-side application software other
than one of the specified web browsers and associated signed plug-ins
that are downloadable-on-demand and meet the mobile code 2.4.a, Page 1-23
requirements of this SOO. The eTS shall not require cookies, other
than session cookies, to deliver full client functionality;
5. At full utilization, the eTS shall support at least 5,000 concurrent
users. The concurrent user capability during agency adoption and
2.4.c, Page 1-24
implementation shall be proportionate to this number based on the
adoption targets cited herein;
6. The eTS shall provide data exchange and application integration
capabilities and infrastructure to permit integration with Government
business systems, other E-Gov solutions, and external partners (e.g., 2.4.b, Page 1-24
state and local governments or industry). The data exchange and
application integration capabilities shall support:
a) Near-real-time, event-based integration leveraging industry
standard XML vocabularies to maximize interoperability and
2.4.b, Page 1-24
minimize the time for business events to be reflected in all
related systems; and
b) Batch integration and data translation capabilities for
minimally intrusive integration with existing legacy
applications that are currently limited to existing data formats 2.4.b, Page 1-24
and file transfer or other batch interface mechanisms.
C.6.4.2 Technology Capabilities and Characteristics – Objectives (of
equal importance)
1. The eTS should provide a solution with minimum bandwidth and
latency requirements for optimal web-based performance and 2.4.c, Page 1-24
response times across Federal agencies and networks;
2. Offerors should describe their strategy and capability to scale from
2.4.c, Page 1-24
5,000 to 10,000 concurrent eTS users;
3. The eTS application integration capabilities should include flexible
transport, routing, scheduling, and data translation services based on 4.1.a, Page 1-52
message/integration brokering and XML Web Services architectures;
4. The application server, web server, and portal components of the
3.c, Page 1-29
eTravel solution should be based on J2EE or .Net architectures;
5. The application server, web server, and portal components of the
eTravel solution should be deployed on a UNIX or Windows 2000 or 2.4.c, Page 1-24
later operating system platform;
6. The operational database platform(s) for the eTS should be based on
either Oracle version 7 or later, or Microsoft SQL Server version 7 or
later. Also any database and application server components should be 2.4.c, Page 1-24
deployed using either a UNIX or Windows 2000 or later operating
system platform;
7. Existing department, agency, and subordinate organization
configurations should not be deleted or adversely impacted by new 3.d, Page 1-30
version releases, upgrades, or other changes to the eTS except where
those changes directly affect specific functionalities or features in the 2.4.j, Page 1-26
existing eTS configuration;

Attachment 15
Proposal
RFP Reference
Reference
8. The technology infrastructure supporting the eTS should be refreshed
in accordance with best commercial practices over the life of the
contract as a part of routine operations and maintenance. Technology
refreshment should maintain robust eTS performance and improve
eTS performance when possible by leveraging cost-effective
technology advances as they become available. Other technology
2.4.g, Page 1-25
refreshment targets include, but may not be limited to, accessibility
features, web form functionality, standardized XML Schema related to
eTravel, etc. Offerors should describe their eTS technology
refreshment strategy in the technical volume of their proposals. The
Contractor should document its eTS technology refreshment policy
within the deliverable Program Management Plan; and
9. The eTS should support handling and viewing of electronic receipt
images in TIFF, PDF, other common image formats used on the
Internet, and the IRS-compliant electronic receipt image format used
if that capability is supported (see Section C.6.3.11). Support for 2.4.j, Page 1-26
proprietary image formats which are not viewable by means of native
capability of the specified web browsers or commonly available
signed “freeware” plug-ins is not required.
C.6.5.1.1 General Security Standards – Requirements
1. The eTS shall protect data (in all aspects enumerated in Section C.6.5)
as Sensitive But Unclassified (SBU) information at the “Medium”
sensitivity level (as defined in GSA IT Security Policy CIO HB
2100.1A and in NIST Special Publication 800-26) and as Privacy Act
data. The GSA will publish the notice to establish the eTS as a
Governmentwide system of records in accordance with the Privacy
Act. At a minimum the Contractor shall:
a) Establish an eTS that is physically secure; 5.2.a, Page 1-59
b) Ensure that the eTS protects the integrity of the travel
5.2.b, Page 1-59
process and the data contained within eTS systems;
c) Ensure that all traveler and travel-related information is
treated and protected as SBU information at the "Medium" 5.2.a, Page 1-59
sensitivity level;
d) Ensure that all eTS data is treated and protected in
5.2.a, Page 1-59
accordance with the Privacy Act.
2. The Contractor shall explicitly describe how the security standards of
this SOO will be met, or how the risk associated with these standards
5.2.d, Page 1-60
will be mitigated if there is a reason that the requirement cannot be
met;

Attachment 15
Proposal
RFP Reference
Reference
3. The Contractor shall be responsible for information technology
security for all systems supporting the eTS that are connected to a
Federal Government network or operated by the Contractor for the
Federal Government, regardless of physical location. This
requirement shall apply to all information technology resources or
services in which the Contractor has physical or electronic access to
the Federal Government’s sensitive information that may be contained
5.2.a, Page 1-59
within the eTS. The term “information technology” as used in this
section means any equipment or interconnected system or subsystem
that is used in the acquisition, storage, manipulation, management,
movement, control, display, switching, interchange, transmission,
translation, transformation, or reception of data or information. This
includes both major applications and general support systems as
defined by OMB Circular A-130;
4. For the purposes of implementing security controls, the eTS is
classified as a Government-accessed major application being hosted
on another organization’s general support system. Security guidelines
pertaining to major applications and general support systems as
described herein shall apply in accordance with Section 2.3.1 of NIST
Special Publication 800-18. The Contractor shall provide adequate
security for both the major application (i.e., the eTS) and the general
support system that hosts it to ensure protection for both the
applications used and the information contained therein. The
5.1.a, Page 1-59
Contractor shall be the designated Custodian for the eTS with
responsibilities in accordance with GSA security policy documented
in CIO HB 2100.1A. The eTS shall comply with all pertinent
requirements of OMB Circular No. A-130, Appendix III, NIST
Special Publication 800-26, and other indentured NIST guidance as
applicable to SBU major applications and general support systems.
Incorporation of classified data into the eTS, which is not a
requirement of this SOO, shall require a new and comprehensive
security risk assessment; and
5. The Contractor shall complete the certification and accreditation
process to obtain Authority To Operate (ATO) in accordance with
GSA Security Order, CIO HB 2100.1A and GSA CIO-IT Security 01-
09, IT Security and Procedural Guide -- Certification and
Accreditation. The Contractor shall coordinate with the designated
eTS Information System Security Manager (ISSM) to prepare and
submit all documentation necessary to support certification and 5.2.f, Page 1-60
accreditation of the eTS by the GSA DAA. The Contractor shall
complete the certification and accreditation process for each location
that is identified as a potential eTS contingency location in the
Continuity of Operations and Contingency Plan so that eTS is granted
either Interim Authority to Operate (IATO) or Authority to Operate
(ATO) at each contingency location;
6. The Contractor shall establish the following minimum controls in
accordance with OMB A-130, Appendix III, as modified herein:
a) For general support systems (the physical location(s) from
where the service is run):
i) Assign responsibility for security; 5.2.d, Page 1-60

Attachment 15
Proposal
RFP Reference
Reference
ii) Develop a security plan that addresses the system rules;
training; personnel controls; incidence response
5.2.d, Page 1-60
capability; continuity of support; technical security; and
system interconnection;
iii) Provide for a review of the security controls and
updates to the Security Plan and Continuity of Operations
5.2.e, Page 1-60
and Contingency Plan whenever significant modifications
are made (but at least every 3 years);
b) For major applications (the eTS components regardless of
their physical location):
i) Assign responsibility for security; 5.2.f, Page 1-60
ii) Develop an application security plan that addresses
application rules; specialized training; personnel security;
5.2.d, Page 1-60
contingency planning; technical controls; information
sharing; and public access controls; and
iii) Provide for a review of the security controls and
updates to the Security Plan and Continuity of Operations
5.2.e, Page 1-60
and Contingency Plan whenever significant modifications
are made (but at least every 3 years).
C.6.5.1.2 General Security Standards – Objectives
1. Data stored within the eTS may vary among low, medium, and high
sensitivity levels across agencies, within agencies, and even within
individual travel actions as seen from different agency perspectives.
Agency-specific and possibly data-specific configurable security is
5.2.c, Page 1-60
desirable, but is anticipated to be cost-prohibitive. Offerors may
propose a configurable security scheme that is more configurable
and scalable if it can be demonstrated to be of greater benefit or
cost-effectiveness to the Government.
C.6.5.2.1 Access and Authentication – Requirements
1. The eTS shall by default provide access to data only on a role-related
“need to know” basis. The eTS shall restrict personnel access to those
with a need-to-know in strict accordance with their roles and
permissions (e.g., system administrator, travel approvers, financial
analyst, etc.). Agencies will determine who within their organizations 5.3.a, Page 1-61
has the need to know specific information about the travelers and
travel within their agency and how that data should be accessed based
on the results of a sensitivity assessment, and will assign user roles
accordingly.

Attachment 15
Proposal
RFP Reference
Reference
2. The eTS shall interface with and authenticate eTS user credentials via
the eAuthentication Initial Operating Capability (IOC) Gateway by the
time of eTS IOC task order completion. The Contractor shall refresh
technology as necessary to integrate with and authenticate eTS user
credentials via the Full Operating Capability (FOC) Gateway
tentatively scheduled for deployment by April 2004. A default
authentication level and associated requirements for the eTS will be
identified by the GSA Contracting Officer at the time of the contract
award based on the results of a Government Risk Assessment. The
Government will provide one of the following Policy Enforcement
Point (PEP) software modules as Government Furnished Equipment
so that the Contractor can integrate its eTS solution with the
eAuthentication IOC Gateway. The IOC PEP vendors approved by
eAuthentication PMO are: Netgrity, Entrust, and Entegrity. Offerors
shall identify which of the approved PEP software modules are
compatible with their eTS offering within their proposal. The
Contractor may issue eAuthentication PMO-approved credentials
which meet or exceed the eTS default authentication level and
associated requirements to eTS users from any Agency which has not
otherwise obtained credentials for its users. If eTS vendor(s) issue 5.3.b, Page 1-61
such credentials, they shall be required to register and integrate their
credential repository with the eAuthentication Gateway in accordance
with the e-Authentication Gateway Interface Specifications (available
at http://www.cio.gov/eauthentication) before issuing credentials to
eTS users. The eTS vendor(s) shall be required to administer any
credentials they have issued for the duration of their eTS contract. If
an agency chooses to procure credentials from an eTS vendor, such
credentials shall be proposed and charged as an additional sub-CLIN
under CLINs 0008, 0025, 0045, and 0065, as applicable, to the
agency’s Task Order. In the event that an agency requires a higher
authentication level than the default eTS level, the agency will
identify the required authentication level to which eTS must be
configured. Any costs associated with a higher level of eTS user
authentication will be proposed and charged to the agency’s task
order under Supplemental Security Services CLINs 0011, 0028, 0048,
and 0068, as applicable. In this case, agencies will be responsible to
ensure that their users obtain the necessary credentials from an
eAuthentication PMO-approved credential provider.
3. The eTS shall provide digital signature capability for the traveler, and
reviewing and approving officials that satisfies requirements in the
5.5.b, Page 1-62
Federal Information Processing Standards Publication 186, Digital
Signature Standard, issued by the NIST;
4. The eTS shall display the following banner at time of login on all eTS
systems (both public and private) operated by the Contractor prior to
allowing anyone access to the system:

Attachment 15
Proposal
RFP Reference
Reference
WARNING
This is a U.S. Federal Government information system that is “FOR
OFFICIAL USE ONLY”. Unauthorized access is a violation of U.S. Law
and may result in criminal or administrative penalties. Users shall not
access other users’ or system files without proper authority. Absence of
access controls IS NOT authorization for access! Information systems and
equipment related to the eTravel Service are intended for communication,
5.3.c, Page 1-61
transmission, processing, and storage of U.S. Government information.
These systems and equipment are subject to monitoring by law enforcement
and authorized officials. Monitoring may result in the acquisition,
recording, and analysis of all data being communicated, transmitted,
processed, or stored in this system by law enforcement and authorized
officials. Use of this system constitutes consent to such monitoring.
WARNING
5. The eTS shall display the following banner at time of login on all eTS
systems that contain Privacy Act information operated by the
Contractor prior to allowing anyone access to the system. Routine
uses language to be appended to the Privacy Act banner will be
provided at the time of contract award:
PRIVACY ACT NOTICE
This system contains information protected under the provisions of the
privacy act of 1974 (Public Law 93-579). Any privacy information
displayed on the screen or printed must be protected from unauthorized 5.3.c, Page 1-61
disclosure. Employees who violate privacy safeguards may be subject to
disciplinary actions, a fine of up to $5,000, or both.
PRIVACY ACT NOTICE
6. The eTS shall include adequate safeguards to restrict data access by
5.3.c, Page 1-61
department, agency, subordinate organization, and user.
C.6.5.2.2 Access and Authentication – Objectives (of equal importance)
1. Prior to availability of the final eAuthentication Gateway, the
Contractor should use the interim eAuthentication Gateway and
credentials from supported Federal credential providers. Alternately,
and with the approval of the GSA Contracting Officer, the Contractor
may fulfill the role of credential provider for eTS at the User ID and 5.3.a, Page 1-61
Password authentication level if the interim eAuthentication Gateway 3.1.a, Page 1-31
and Federal credential providers are not used. A minimum assurance
level for the eTS will be specified by the eTravel PMO promptly after
the final eAuthentication Gateway assurance levels have been defined
and prior to contract award;
2. The eTS should display contact information for the eTS Information 5.3.d, Page 1-61
System Security Officer (ISSO) (to be provided at the time of contract
award) in the initial portal screen and in all help screens; and
3. The eTS should have an agency configurable session timeout feature
(configurable only by an agency eTS administrator) to prevent
inappropriate access and viewing of any material during user absence.
The default timeout shall be 15 minutes of inactivity such that if the
5.3.e, Page 1-61
user has no interaction with eTS for that time, the user will be required
to re-authenticate in order to resume use of the system. Session state
and data entered at the moment of timeout shall be saved to the
maximum extent possible.

Attachment 15
Proposal
RFP Reference
Reference
C.6.5.3.1 Web Browser Security – Requirements
1. The eTS shall not employ mobile code within its web content that may
harbor malicious content and therefore be blocked by Federal
firewalls, consequently denying functionality to users. Mobile code
technology explicitly prohibited in delivering eTS functionality 5.4.a, Page 1-62
includes, but may not be limited to, ActiveX, UNIX Shell Scripts,
Disk Operating System (DOS) Batch Scripts, unsigned Java applets,
or other unsigned Java mobile code.
C.6.5.3.2 Web Browser Security – Objectives
1. Where necessary to provide eTS functionality, certain mobile code
technology may be employed, such as signed Java applets, signed Java
JAR files, JavaScript, JScript, and ECMA-Script. These technologies
5.4.a, Page 1-62
are considered a limited risk and, if employed, shall be addressed in
the eTS Security Plan including compensating controls which mitigate
that risk.
C.6.5.4.1 Data Security – Requirements
1. The eTS shall protect data (in all aspects enumerated in Section C.6.5)
at the “Medium” level for Sensitive But Unclassified (SBU) data in 5.5.a, Page 1-62
accordance with the security standards cited herein;
2. All financial, privacy, and other sensitive data transmitted by eTS via
the Internet shall employ a minimum of 128-bit encryption that has
been validated by the Cryptographic Module Validation Program
against NIST Federal Information Processing Standards (FIPS) 140-2.
Refer to NIST Special Publication 800-21, Guideline for
Implementing Cryptography in the Federal Government, and the 5.5.a, Page 1-62
NIST Cryptographic Toolkit for detailed information. (Agency
requirements that exceed these standards will be handled on a case-
by-case basis.); and
3. The eTS shall protect Federal travel-related information against 5.5.e, Page 1-63
disruption, theft, exploitation, and inadvertent disclosure. 5.5.f, Page 1-63
C.6.5.5.1 Personnel and Physical Security – Requirements
1. The Contractor shall restrict personnel access to the eTS to those with
5.6.a, Page 1-63
a need-to-know.
2. Based on the Privacy Act and guidelines in Suitability and Personnel
Security Handbook, GSA ADM P 9732.1C, the physical site where
the hardware resides shall be secured as a General Support System in
accordance with NIST 800-18 and the CIO HBA 2100.1A, and shall 5.6.b, Page 1-63
be staffed by an appropriate mix of Level 5 staff and Level 6
supervisory personnel. The Contractor shall be responsible for the
cost of personnel background checks.
C.6.5.5.2 Personnel and Physical Security – Objectives (of equal
importance)

Attachment 15
Proposal
RFP Reference
Reference
1. The Contractor should accommodate agency-specific personnel
security requirements, including but not limited to ensuring that all
contractor personnel meet applicable agency security and/or clearance
2.7.a, Page 2-56
requirements. The Contractor may propose staff with other security
clearances as long as their clearances meet or exceed the levels stated
herein; and
2. The Contractor should ensure that its employees performing under this
contract receive annual IT security training in accordance with OMB
Circular A-130, the Federal Information Security Management Act of 2.7.a, Page 2-56
2002 (FISMA), and NIST requirements, with a specific emphasis on
rules of behavior.
C.6.5.6.1 Supplemental Security Services – Requirements
1. Offerors shall propose separately priced supplemental security
services to address agency-specific security requirements that
augment eTS security standards without cost or impact to the basic
eTS services and transactions. These services shall include security
risk analysis, enhanced security for access and transmission, etc. 5.7.a, Page 1-63
Certain agency-specific security requirements, however, (e.g., the
handling of classified data) may have to be implemented downstream
as potential enhancements or changes to the eTS due to overall cost
and service impact.
C.6.5.7.1 Government Access – Requirements
1. The Contractor shall afford the Government and duly designated
Government support contractors access to the Contractor’s and
subcontractors’ facilities, installations, operations, documentation,
databases and personnel used in performance of the eTS contract.
Access shall be provided to the extent required to carry out a program
of security inspection (to include vulnerability testing, risk analysis, 5.8.a, Page 1-63
etc.), investigation, and audit. Such access and activities are required
in order to safeguard against threats and hazards to the integrity,
availability and confidentiality of eTS data, to the function of
information technology systems operated on behalf of the GSA, and in
order to preserve evidence of computer crime if committed.
C.6.5.8.1 Subcontractor Security – Requirements
1. The Contractor shall incorporate the substance of security
requirements of the contract (Section C.6.5) in all subcontracts that 5.9.a, Page 1-64
support the eTS.
C.6.6.1 Electronic and Information Technology Accessibility –
Requirements
1. The eTS shall meet applicable accessibility standards of 36 CFR 1194
that can be met with supplies, services, or assistive technologies that
2.1.4.a, Page 1-8
are available in the commercial marketplace in time to meet the
delivery requirements of this SOO;

Attachment 15
Proposal
RFP Reference
Reference
2. Offerors shall complete and submit a Voluntary Product Accessibility
Template (VPAT) with their proposals to permit the Government to
assess the accessibility of their eTS solution, and to evaluate its degree
of compliance with 36 CFR 1194. The VPAT is intended to capture
the degree of accessibility of EIT resources afforded by means of
commercially available products, services, and technologies. A
VPAT tailored for the eTS is included as Attachment 5. Offerors shall
2.1.4.a, Page 1-13
respond fully to any accessibility requirement for which there is no
Government language modifying the requirement in the “Remarks and
Explanations” column of the VPAT. Offerors shall provide additional
contact information to facilitate more detailed inquiries by the
Government if necessary. Offerors shall take into account the
considerations identified in the summary table in Section C.6.6.2
below in completing the VPAT.
C.6.6.2 Electronic and Information Technology Accessibility –
Objectives (of equal importance)
1. Accessibility objectives for the eTS are summarized as follows:
All criteria apply for elements of the eTS that are non-web browser-
based, including, but not limited to: plug-ins, Java applets,
downloaded content, and administrative and management software.
2.1.4.a, Page 1-13
The contractor shall either build all accessibility features in, or
develop a solution that is compatible with assistive technology.
See Section 1194.21 - Software Applications and Operating Systems.
All criteria shall apply for web-based elements of the eTS. Criteria (d)
means that pages that refer to style sheets should “degrade gracefully”
if the user chooses to disable style sheet support, although eTS users
are required to use a modern browser that supports CSS (Cascading 2.1.4.a, Page 1-13
Style Sheets).
See Section 1194.22 - Web-based internet information and
applications.
Criteria (a), (b), (c), and (d) apply for phone-based support elements
of the eTS. If the vendor’s solution includes special telephone
equipment for the hearing impaired, criteria (f) and (g) shall also 2.1.4.a, Page 1-13
apply.
See Section 1194.23 - Telecommunications Products.
Criteria (c), (d), and (e) shall apply for multi-media training products
provided as part of the eTS. 2.1.4.a, Page 1-13
See Section 1194.24 - Video and Multi-media Products.
If kiosks or other self-contained, closed products are proposed as part
of the eTS, then all criteria listed in Section 1194.25 shall apply to
those products. 2.1.4.a, Page 1-13
Section 1194.25 - Self-Contained, Closed Products.
Contract requirements for the eTS do not include Desktop and
Portable Computers, so these criteria are not applicable. 2.1.4.a, Page 1-13
See Section 1194.26 - Desktop and Portable Computers.

Attachment 15
Proposal
RFP Reference
Reference
All criteria in Section 1194.31 shall apply for technologies that are not
included in any of the above Sections (1194.21-1194.26) or where
eTS meets a particular criterion in those sections through equivalent 2.1.4.a, Page 1-13
facilitation (as defined in Section 1194.5).
Section 1194.31 - Functional Performance Criteria.
All criteria for end-user support documentation and services shall
apply. 2.1.4.a, Page 1-13
Section 1194.41 - Information, Documentation, and Support.
2. During the course of the eTS contract, the Contractor should be
prepared to provide improved or additional accessibility through the
2.1.4.a, Page 1-13
continued application of Web Content Accessibility Guidelines,
evolving commercial assistive technologies, etc.
C.6.7.1.1 Business Data Warehouse – Requirements
1. The Contractor shall establish an eTS business data warehouse to 4.3.a, Page 1-54
support aggregated and consolidated Federal travel information
storage, management, reporting, and business intelligence; 4.3.h, Page 1-56
2. The Contractor shall develop all appropriate information models and
conduct the analyses and studies required to define detailed data 4.3.a, Page 1-54
warehouse requirements. This information shall be documented in the 4.3.g, Page 1-56
Contractor’s eTS Data Management Plan;
3. The data model and all data contained within the eTS business data
warehouse will be owned by the Government. The Contractor shall be
responsible for managing and protecting the data in accordance with
this solicitation and resultant security provisions of the contract. All 4.3.f, Page 1-56
eTS data will be protected under the Privacy Act, and the Contractor
shall not use any eTS data for any purpose other than that specified
herein.
4. The business data warehouse shall be capable of importing and
exporting Federal travel data within the scope of this SOO which may
be provided from/to external data sources, e.g., agency business
systems, other Federal travel partner and supplier systems, etc. The
Government reserves the right to award the CLIN 0005 Business Data 4.3.a, Page 1-54
Warehouse to a single vendor or not to award CLIN 0005 under this
contract. Offerors shall include in their proposals their approach for
the collection and export of travel data elements to an eTS Business
Data Warehouse operated by another entity. (Refer to Section C.10
(13) for additional information.)
5. In addition to the requirements of the continuity of services clause
included in this solicitation and any resulting contract, the Contractor
shall meet the following data transition requirements for the eTS:

Attachment 15
Proposal
RFP Reference
Reference
a) When the Contractor becomes aware of the upcoming
expiration or termination of a task order from a Federal agency
that includes eTS Authorization and Voucher Services (CLINs
0003, 0021, 0041, and 0061) which will not be immediately
succeeded by another such task order from that agency, the
Contractor shall prepare for the transition of that agency’s data
in accordance with the Contractor’s eTS Data Management
Plan. Upon expiration or termination of the task order, the
Contractor shall not permit further transactions and shall
transfer all applicable transactional eTS data for that agency
within operational databases to the business data warehouse.
This shall be accomplished within five business days after
expiration or termination of the task order. For all transactions
that have not been completed by that time (in-process
transactions), the Contractor shall ensure that all information
needed to resume the transaction is provided. Once the
transactional data has been transferred to the business data
warehouse, the Contractor shall electronically transfer and/or
provide on durable electronic media (e.g., CD-ROM) all 4.3.k, Page 1-57
traveler profiles, reportable configuration records, travel
records, associated files, and other data identified or referenced
in this SOO that are associated with that agency and contained
in the Contractor’s business data warehouse to the Government
within ten business days after expiration or termination. Data
shall be provided in accordance with the Contractor’s eTS
Data Management Transition Plan as well as the indexing
requirements of Sections C.6.5.3 and C.6.5.4. All in-process
transactions shall be specifically identified to facilitate eTS
transition and travel management by the Government. The
Contracting Officer’s Representative (COR) will provide
details regarding transfer of data and/or delivery of media to
the Government. Upon confirmation from the COR that the
Government has received, reviewed, and found the transferred
data to be acceptable, the Contractor shall delete said data
from its transactional databases, business data warehouse, and
any backup/archival systems or media in a manner that renders
the data irretrievable in whole or in part;

Attachment 15
Proposal
RFP Reference
Reference
b) When the Contractor becomes aware of the upcoming
expiration or termination of any ordering period under the
master contract that is not immediately succeeded by the
execution of an optional ordering period, the Contractor shall
prepare for the transition of Government eTS data in
accordance with the Contractor’s eTS Data Management Plan.
Upon expiration or termination of the ordering period, the
Contractor shall not permit further transactions and shall
transfer all applicable transactional eTS data to the business
data warehouse. This shall be accomplished within ten
business days after contract expiration or termination. For all
transactions that have not been completed by that time (in-
process transactions), the Contractor shall ensure that all
information needed to resume the transaction is provided.
Once all transactional data has been transferred to the business
data warehouse, the Contractor shall electronically transfer
and/or provide on durable electronic media (e.g., CD-ROM)
all traveler profiles, reportable configuration records, travel 4.3.k, Page 1-57
records, associated files, and other data identified or
referenced in this SOO and contained within the Contractor’s
business data warehouse to the Government within 20
business days after expiration or termination. Data shall be
provided in accordance with the Contractor’s Data
Management Plan as well as the indexing requirements of
Sections C.6.3.11.2 (if applicable), C.6.7.4.1, and C.6.7.6.2.
All in-process transactions shall be specifically identified by
agency to facilitate eTS transition and travel management by
the Government. The Contracting Officer’s Representative
(COR) will provide details regarding transfer of data and/or
delivery of media to the Government. Upon confirmation
from the COR that the Government has received, reviewed,
and found the transferred data to be acceptable, the Contractor
shall delete said data from its transactional databases, business
data warehouse, and any backup/archival systems or media in
a manner that renders the data irretrievable.
C.6.7.1.2 Business Data Warehouse – Objectives (of equal importance)

Attachment 15
Proposal
RFP Reference
Reference
1. The business data warehouse should capture and contain all travel
transaction data elements from eTS systems associated with or required
to fulfill the traveler profile (see Section C.6.3.3), travel receipt images
if included in eTS capabilities (see Section C.6.3.11), query and
reporting (see Section C.6.7.4), business intelligence (see Section
C.6.7.5), and data exchange requirements (see Section C.6.7.2) of this
SOO. Travel data should be indexed in accordance with the
requirements of Sections C.6.3.11.2 (if applicable), C.6.7.4.1, and
C.6.7.6.2. Data captured and stored should also include, but may not
be limited to, detailed travel itinerary and voucher information such as: 4.3.a, Page 1-54
a) Purpose of travel;
b) Exception codes and justifications for not using mandatory
and/or preferred travel suppliers; and
c) Flight information (carrier, fare basis codes, class of service,
etc.); and
d) Travel cost information for transportation, lodging, and
rental cars, with taxes and fees paid and tax and fee types
separately identified.
2. The eTS business data warehouse should be physically and logically
4.3.h, Page 1-56
separated from operational databases used in support of the eTS.
C.6.7.2.1 Data Exchange – Requirements
1. The eTS shall support two-way exchange of Federal travel data with
agency business systems in both near real time and batch modes as
described within this section. The eTS shall be capable of two-way 4.1.a, Page 1-52
transactional data exchange with external systems to support business
requirements such as funds availability checks, payment actions, etc.;
2. Data exchange shall support EDI, UDF, and XML formats as well as
other industry standard methods, and the capability to translate 4.1.d, Page 1-52
between these formats;
3. The eTS shall provide an Enterprise Application Integration (EAI)
capability and infrastructure to support near real time and batch
4.1.a, Page 1-52
integration with the business systems of Federal agencies, as well as
with commercial systems as may be required;
4. The eTS EAI platform shall perform all necessary format translations
for inbound and outbound data exchange. Costs associated with
establishing, operating, and maintaining the eTS EAI capability shall 4.1.d, Page 1-52
be included in and spread across the Authorization and Voucher
Services fees (CLINs 0003, 0021, 0041, and 0061);
5. The Contractor shall establish a standard data input for the eTS. The
standard data input shall be capable of accepting transactional data
(e.g., accounting data, charge card postings, funds availability
checking, funds certification, etc.) and “static” data (e.g., traveler 4.1.f, Page 1-53
profiles, lines of accounting, etc.) from agency business systems
and/or other external commercial data sources in a format defined by
the Contractor in the eTS Data Exchange Specification;
6. The Contractor shall establish a standard data output for the eTS with
the following capabilities and characteristics:

Attachment 15
Proposal
RFP Reference
Reference
a) The eTS shall capture and make available in its standard
data output the data elements identified in Chapter 301,
4.1.f, Page 1-53
Appendix C, of the FTR as well as additional financial and
accounting data elements specified herein;
b) The standard data output shall draw upon the entire
dictionary of data elements that are exportable from the eTS
and the business data warehouse for exchange between its EAI
platform and the agencies’ business systems. Data elements
include traveler identification, commercial transportation
information, travel expense information, and accounting and
certification data. These data elements vary in form and
format and are integral to both travel and accounting 4.1.d, Page 1-52
transactions. The Contractor shall define the data schema and
format(s) for the standard data output. Data formats shall be
flexible enough to facilitate exchange of key travel and
financial information without requiring costly modification to
existing systems. Examples of Government systems with
which eTS shall interface include financial, payroll, and
human resources systems;
c) The Contractor shall provide the capability to modify or
expand the data elements contained within the standard data 4.1.g, Page 1-53
output over the life of the contract;
d) The eTS standard data output shall contain the data
necessary to support the functionalities listed below:
i) Funds availability checking (see Sections C.6.1,
4.1.d, Page 1-52
C.6.3.4, and C.6.3.10);
ii) Credits resulting from cancellation, unused tickets, and
4.1.d, Page 1-52
other refunds (see Section C.6.3.7);
iii) Payment, tax reporting, and liquidation of travel
4.1.d, Page 1-52
advances (see Sections C.6.3.8 and C.6.3.14);
iv) Reporting amount due to or owed by the traveler after
final voucher submittal (see Section C.6.3.14) and
4.1.g, Page 1-53
repayment of funds to offset traveler indebtedness (see
Section C.6.3.9);
v) Maintaining standard data elements specified in the
FTR to generate standard and ad hoc reports (see Section 4.1.g, Page 1-53
C.6.7.4);
vi) Transactional interfaces between the eTS and
agencies’ business systems, including the generation of
accounting transactions as needed, update of funds control
4.1.d, Page 1-52
and the standard general ledger, and generation of
disbursement actions by electronic funds transfer (EFT) or
other means;
vii) GSA reports which require the data elements
4.1.g, Page 1-53
identified in Attachment 7.

Attachment 15
Proposal
RFP Reference
Reference
7. Attachment 14A provides an explanation of Standard data
elements. At a minimum, the Contractor shall make the data
elements with Sequence numbers 1 through 279 identified in
Attachment 14B (those identified as Standard Data Elements for
Exchange) available for input and output to and from the eTS
respectively via the eTS EAI capability subject to the following
conditions: 4.1.a, Page 1-52
a) Standard data elements related to mandatory requirements
for the eTS must be included in the standard data input or
output; and
b) Standard data elements related to objectives which are a
part of your proposed eTS solution must be included in the
standard data input or output.
C.6.7.2.2 Data Exchange – Objectives (of equal importance)
1. The eTS should have the capability to accommodate legacy systems
based on older technologies as well as the latest emerging data
standards (e.g., XML Schema, Web Services involving Simple Object 4.1.d, Page 1-52
Access Protocol (SOAP) messages for remote procedure calls,
message brokers, etc.);
2. The Contractor should establish a standardized data exchange
mechanism that is “loosely coupled” to accommodate sharing of data
with legacy systems while leveraging new standards to improve
4.1.d, Page 1-52
information usability over time. Offerors should note if they will be
transmitting/storing standard XML within their proposed eTS
environment;
3. XML Schema and XML instance documents created and transmitted
by the eTS should comply with Federal XML guidelines as described 4.1.d, Page 1-52
in the Draft Federal XML Developer’s Guide; and
4. The eTS should support the capability to associate eTS travel
authorization to activation and deactivation of Government
Contractor-issued Individually Billed Travel Charge Cards (see
Section C.6.3.4.2). This will be accomplished by including
appropriate data elements in the eTS standard data output to enable
agencies to associate eTS travel authorizations to travel charge card
management through the electronic access systems associated with
2.2, Page 1-15
their respective travel charge cards. Activation/deactivation of the
travel charge cards will be the responsibility of the agency. (Note:
Activation/deactivation of the travel charge cards will be the
responsibility of the Federal agencies. Furthermore, this objective
shall not be construed to affect the GSA SmartPay® contract or
require GSA SmartPay® contractors to exchange data with or permit
linkage to eTS.)

Attachment 15
Proposal
RFP Reference
Reference
5. Attachment 14A provides an explanation of Standard data elements.
Standard data elements for eTS data exchange should adhere to the
names and characteristics identified in Attachment 14B with the
following considerations:
a) Data element naming should follow the guidelines of the
CIO Council’s XML Working Group draft XML Developer’s
Guide, which strongly recommends the use of either business
terms or names that comply with ISO/IEC 11179, Information
Technology - Specification and Standardization of Data
Elements. (See links related to ISO/IEC 11179 at
http://metadata-stds.org/ and http://metadata-
stds.org/document_library.html for additional information.)
General conventions include, but are not limited to, the use of
upper camel case (e.g., “UpperCamelCase”) and lower camel
case (e.g., “lowerCamelCase”) names, minimal use of
acronyms (unless universally known across the government
travel community), avoidance of abbreviations, etc.;
b) Standard data element names provided in Attachment 14B
4.1.d, Page 1-52
should be used unless alternate names conforming to ISO
11179 are proposed. These data element names are based on 4.1.a, Page 1-52
travel management (business) terms and reflect consensus
among a number of Federal agencies. Business terms improve
readability, whereas ISO 11179 conventions facilitate
automated analysis of schema components for harmonization
efforts. If different business terms are proposed for element
names and types, they should represent a consensus among
members of the government travel community.
c) Specific data elements to support invitational travel were
not captured in the list provided as Attachment 14B. Offerors
should propose invitational travel data elements for the eTS
data exchange capability if relevant for exchange with agency
business systems.
d) Specific data elements to support invitational travel were
not captured in the list provided as Attachment 14A. Offerors
should propose invitational travel data elements for the eTS
data exchange capability if relevant for exchange with agency
business systems.
6. Standard data elements with Sequence numbers 280 through 385 in
Attachment 14B (those labeled as Standard Data Elements for Business
Data Warehouse and/or Travel Management) have been identified as
important to Federal travel management, although not necessarily 4.1.a, Page 1-52
required for exchange with agency business systems. Offerors should
incorporate these data elements as they relate to the proposed
objectives included in their respective eTS solution.

Attachment 15
Proposal
RFP Reference
Reference
C.6.7.3.1 Integration Support – Requirements
7. The Contractor shall develop and deliver a specification that defines
requirements for data exchange with the eTS, including standard data
input and standard data output. The specification shall include all
information necessary for Federal agencies to establish Integration
Agreements and interfaces with the eTS using the eTS EAI platform. 4.2.a, Page 1-54
The specification shall include, but not necessarily be limited to, eTS
data exchange requirements and procedures, standard data input and
output data elements, functional data element descriptions, field
characteristics, data types, data schema, etc.;
8. The Contractor shall establish and maintain the EAI platform and
infrastructure including flexible scheduling, transport, routing, and
4.2.a, Page 1-54
format translation services (inbound and outbound) and provide
licenses for Federal agency access and use (if required);
9. The Contractor shall coordinate with Federal and GSA-authorized
commercial external system owners to facilitate the establishment of
Integration Agreements and interfaces that facilitate data exchange,
4.2.a, Page 1-54
mapping, translation, transport, and scheduling requirements to
support Federal travel management functions within the scope of the
eTS; and
10. The Contractor shall execute data exchange and translation between
the eTS and external systems in accordance with established 4.2.a, Page 1-54
Integration Agreements.
C.6.7.4.1 Queries and Reports – Requirements
1. The eTS shall provide the capability to generate all reports required by
the FTR Section 300-70 and Chapter 304 for travel management and 4.4.b, Page 1-57
agency reporting:
2. The eTS shall make travel data available to the GSA for oversight in
accordance with FTR 300-70, Agency Reporting Requirements, and
4.4.b, Page 1-57
any other specific information GSA may require for a reporting
period;
3. The eTS shall provide query and reporting capability through the web
browser and be capable of executing queries on all travel data
elements within the eTS. Provide for ad hoc and standing/stored
queries. Provide the capability to drill down from summary data to
detail data, and have the capability to drill from the Governmentwide
level to department, agency, subordinate organization, and individual
4.4.b, Page 1-57
traveler levels according to user roles and permissions. Allow
information within eTS to be queried by field and viewed online to
present specific data as requested by the user subject to user roles and
permissions. Index travel actions by travel authorization number,
traveler name, traveler SSN or other employee identification number,
travel destination, and dates of travel;
4. The eTS shall support the creation, formatting, generation, printing,
storage, and electronic transmittal of custom reports to meet agency
4.4.b, Page 1-57
requirements, and make both standard and agency-defined custom
reports available through the web browser;

Attachment 15
Proposal
RFP Reference
Reference
5. The eTS shall maintain transaction data and standard data elements
identified in FTR Chapter 301, Appendix C, to generate standard and 4.4.b, Page 1-57
ad hoc reports and capture activity in future time frames;
6. The eTS shall track and report travel obligation and liquidation
4.4.b, Page 1-57
information based on OMB and GSA defined travel purposes;
7. The eTS shall provide the capability to run on-demand analysis
reports and download data to spreadsheets or other analytical tools; 4.4.b, Page 1-57
and
8. The eTS shall provide the specific GSA Travel Management Reports
4.4.b, Page 1-57
defined in Attachment 7.
C.6.7.4.2 Queries and Reports – Objectives (of equal importance)
1. The eTS should provide robust query and analysis tools, such as
N/A
Online Analytical Processing (OLAP); and
2. In addition to the required reports specified above, the eTS should
provide the following standard reports:
a) Total spend for travel and transportation of employees and
invitational travelers;
b) Average costs and duration of trips;
c) Amount of official travel by purpose(s);
d) All instances in which the agency authorized/approved the 4.4.a, Page 1-57
use of first-class transportation accommodations as well as
utilization of first class travel and accommodations; and
e) Exception reports documenting all instances and the
relevant details when travel was authorized, accomplished,
and/or vouchered with exception(s) to applicable travel
regulations and policies.
C.6.7.4.3.1 Custom Report Development – Requirements
1. The Contractor shall provide separately priced services for the
development of custom reports to support agency-specific travel 4.4.c, Page 1-58
management reporting requirements.
C.6.7.5.1 Business Intelligence – Requirements
1. The Contractor shall establish a robust business intelligence 4.3.c, Page 1-55
capability for the eTS to enable and drive effective Federal travel
policy, management, and procurement. 4.3.d, Page 1-55
C.6.7.5.2 Business Intelligence – Objectives (of equal importance)
1. To the extent possible with commercially available tools, the business
intelligence capabilities of the eTS should directly support the business
analysis and management functions listed below at the
Governmentwide, department, agency, and subordinate organization
levels (as applicable):
a) Budget management; 4.4.a, Page 1-57
b) Real-time spend analysis; 4.3.d, Page 1-55
c) Preferred supplier utilization and spend;
d) Federal travel trend analysis;
e) Regulatory compliance and regulatory exception analysis
and reporting; and
f) eTS Contractor performance.

Attachment 15
Proposal
RFP Reference
Reference
2. Business intelligence functionalities should be accessible via the
4.3.d, Page 1-55
eTravel portal.
C.6.7.6.1 Records Retention and Archiving – Requirements
1. The eTS shall comply with records retention requirements established
by the National Archives and Records Act and Internal Revenue 4.5.b, Page 1-58
Service regulations as applicable;
2. The eTS shall prevent the purging of historical records prior to the
proper retention period, and permit purging only of those records
authorized for disposal by the National Archives and Records
4.5.a, Page 1-58
Administration (NARA) per 36 CFR 1228 and 1234. NARA General
Records Schedule 9 for Travel and Transportation Records and
General Records Schedule 20 for Electronic Records shall apply;
3. The eTS shall be Government fiscal year compliant (October 1
through the following September 30) for dating and retention of 4.5.b, Page 1-58
records;
4. The Contractor shall develop and implement a records retention and
archiving scheme to meet these requirements. The records retention
4.5.b, Page 1-58
and archiving scheme shall be documented in the Contractor’s eTS
Data Management Plan.
C.6.7.6.2 Records Retention and Archiving – Objectives (of equal
importance)
1. The eTS should provide online access to detailed transaction
information for a minimum period of 36 months, and permit access to
4.5.b, Page 1-58
archived detailed transaction information for a period of 6 years and 3
months;
2. The eTS should archive all data to durable media (e.g., CD-ROM)
4.5.a, Page 1-58
prior to purging from the eTS and/or the business data warehouse; and
3. The eTS should provide a means for departments, agencies, and
subordinate organizations to archive their travel records by download.
Alternately, the Contractor may supply archived records on durable
4.5.a, Page 1-58
media (e.g., CD-ROM). Archived records should be indexed by travel
authorization number, traveler name, traveler SSN or other employee
identification number, travel destination, and dates of travel.
C.6.8.1.1 Standard Implementation Services – Requirements
1. The Contractor shall provide implementation support services
required to establish agency-standard configuration and operational
readiness in coordination with each agency placing a task order for 2.6.1.a, Page 2-24
eTS Reservation and Fulfillment Services and/or eTS Authorization
and Voucher Services under this contract;
2. The Contractor shall identify and provide an implementation team for
each adopting/ordering agency, and provide initial and ongoing 2.6.1.a, Page 2-24
account management for each agency;
3. The Contractor shall host an agency kickoff or planning meeting for
key travel management personnel to explain eTS configuration
options, assignment of user roles and permissions, the implementation 2.6.1.d, Page 2-25
process, and key implementation and integration issues that the
agency may face;

Attachment 15
Proposal
RFP Reference
Reference
4. The Contractor shall load all agency-specific data (e.g., traveler
profiles, funding citations, etc.) provided by the agency which may be
2.6.1.i, Page 2-26
imported by automated means. The Contractor shall specify data
formats for the upload of agency data;
5. The Contractor shall establish agency specific billing parameters and
2.6.1.i, Page 2-26
procedures;
6. The Contractor shall identify online, role-based training and training
curricula available to the agency for each of the agency’s user roles.
Instructor-led courses shall accommodate at least twenty-five students
per class, and shall be scheduled at the ordering agency’s convenience
and shall be conducted no more than 30 days prior to implementation
2.7.a, Page 2-56
and use of eTS by the users trained. Training classes may be
conducted at a Government-specified or Contractor-specified facility,
depending upon the preference of the ordering agency. The
Contractor shall be responsible for providing computers and Internet
access for classes conducted at Contractor-specified facilities;
7. The Contractor shall provide dedicated implementation support to the
agency eTS migration manager(s), travel manager, travel
coordinator(s), and/or travel administrator(s) as defined for
implementation service levels described below. Support may include
on-site support as determined by the needs of the agency. (Travel
expenses incurred will be paid in accordance with Chapter 301 of the
FTR on a cost reimbursable basis, and should be submitted under
CLINs 0008, 0025, 0045, and 0065:
a) Standard Implementation Service Level A:
i) Load up to 500 user profiles;
ii) Conduct at least one instructor-led training class for
each user role identified in the eTS, providing training
opportunities for at least 150 users in a minimum of six
classes. Agencies shall have the option of selecting the
specific user role classes to be repeated if the number of
classes offered exceeds the number of eTS user roles
employed by the agency. Offeror’s shall propose how 3.8.c, Page 1-42
train-the-trainer classes may be substituted for specific 2.6.1.a, Page 2-24
individual user role classes at the agency’s discretion;
iii) Provide at least 480 work-hours of dedicated
implementation support with up to three implementation
consultants in a period not to exceed 60 calendar days
from task order award.
b) Standard Implementation Service Level B:
i) Load up to 2,000 user profiles;
ii) Conduct at least three instructor-led training classes for
opportunities for at least 450 users in a minimum of 18
classes offered exceeds three times the number of eTS
user roles employed by the agency. Offeror’s shall
propose how train-the-trainer classes may be substituted
for specific individual user role classes at the agency’s

Attachment 15
Proposal
RFP Reference
Reference
discretion;
iii) Provide at least 960 work-hours of dedicated
implementation support with up to six implementation
c) Standard Implementation Service Level C:
i) Load up to 5,000 user profiles;
ii) Conduct at least six instructor-led training classes for
opportunities for at least 900 users in a minimum of 36
classes offered exceeds six times the number of eTS user
roles employed by the agency. Offeror’s shall propose
how train-the-trainer classes may be substituted for
specific individual user role classes at the agency’s
discretion;
iii) Provide at least 1,440 work-hours of dedicated
implementation support with up to nine implementation
d) Large scale implementations:
i) Offerors shall propose their method and pricing for large
scale standard implementation services for up to
120,000 users at large agencies that may wish to procure
agency-wide implementation on single task order. The
description of large scale standard implementation shall
address the loading of user profiles; training for all user
roles and the appropriate combination of computer-
based, instructor-led, and train-the-trainer courses;
dedicated implementation support; timing of
implementation activities; and any other implementation
support which in the experience of the offeror is vital to
successful implementation and adoption of web-based
services. Proposed pricing for large scale
implementations shall indicate how it is scaled based on
the number of users, and is expected to reflect
appropriate volume discounts.
e) Alternative implementation services:
i) Offerors may propose and price an alternative and/or
additional performance-based standard implementation
service scheme as part of any alternate price proposal
submitted.
8. The Contractor shall provide technical support to coordinate with
agency personnel to develop Integration Agreements that establish the
agency’s use of the eTS data exchange capabilities to interface with its
2.6.1.a, Page 2-24
internal business systems. The Contractor shall support the
establishment and testing of agency interfaces to the eTS EAI
platform;

Attachment 15
Proposal
RFP Reference
Reference
9. Following the dedicated implementation support period described
above, the Contractor shall provide continuing priority
implementation support during the subsequent two months of an
agency’s eTS roll-out. This shall consist of technical and functional
support for a weekly conference call between the Contractor, the 7.2.2.c, Page 2-??
eTravel PMO, and the agency to discuss and mitigate roll-out issues.
The Contractor shall also support a monthly conference call with
agency and eTravel PMO through the agency’s sixth month of
deployment; and
10. The Contractor shall document the agency standard configuration
(e.g., standard process and work flows, business rules, audits, etc.)
2.7.3.a, Page 2-60
established for the eTS during implementation activities at that agency
in an eTS Implementation Report.
C.6.8.1.2 Standard Implementation Services – Objectives (of equal
importance)
1. Basic business rules and exception procedures; 2.6.2.k, Page 2-26
2. Approval and routing chains; 2.6.2.i, Page 2-26
3. Agency-specific supplier designations; 2.6.2.i, Page 2-26
4. Agency-specific messages and warnings; 2.6.2.i, Page 2-26
5. Electronic upload of all traveler profile information provided by the
agency with establishment of user accounts and permission levels for 2.6.1.a, Page 2-24
the travelers;
6. Incorporation of existing TMC services; and 2.6.2.e, Page 2-25
7. 4.2.b, Page 1-54
Establishment of an eTS Integration Agreement for the agency.
4.2.c, Page 1-54
C.6.9.1 Customer Support – Requirements
1. The Contractor shall provide basic customer support (i.e., a help desk)
for all user roles established in the eTS from 8:00 A.M. to 9:00 P.M.
Eastern Time, Monday through Friday (excluding Federal holidays).
Customer support shall meet all requirements specified herein for
functional and technical support, the price for which shall be included
in the applicable transaction fees. The Contractor shall expand
customer support as the eTS is implemented by government agencies 2.4.2.a, Page 1-27
that are located OCONUS, in U.S. territories, and in foreign countries.
Offerors shall describe their plan and ability to provide this expanded
customer support, and identify a pricing strategy for the expanded
hours of support if not included in the price for basic customer
support. Pricing for expanded customer support hours will be
negotiated in accordance with the changes clause of the contract;

Attachment 15
Proposal
RFP Reference
Reference
2. Basic customer support shall consist of on-line and phone-in Help
Desk support with single “focal points” that direct users to the
appropriate type of support (e.g., technical, software, travel
arrangements, etc.) required to resolve their questions, issues,
problems, or needs. For online customer support, this means a single
e-mail address, instant messaging address, portal hyperlink, etc. For
2.4.2.a, Page 1-27
phone-in support, this means a single, domestic toll free customer
service phone number and a single, toll free domestic facsimile
number. Phone-in support shall accommodate collect calls for
overseas customers. The Contractor shall route online and phone-in
support requests quickly and efficiently to the appropriate eTS
functional, technical, and travel arrangement assistance;
3. The Contractor shall provide travel arrangement support for travelers
and travel arrangers. Provide system administration support to travel
administrators and travel coordinators. The Contractor shall provide
2.4.2.a, Page 1-27
toll free 24/7/365 emergency travel arrangement support via telephone
with voice and facsimile service. Collect calls shall be accepted in
order to support international travelers;
4. Technical support shall consist of user role specific technical support
for all user roles identified. Technical support provided shall help
users quickly determine if technical problems encountered are due to
eTS or local agency network/IT issues. (The Contractor shall not be 2.4.2.b, Page 1-27
responsible for resolving local agency network/IT issues.) The
Contractor shall also provide system administration support to travel
administrators and travel coordinators;
5. The eTS shall support the submittal of online and phone-in trouble
tickets. Provide trouble ticket tracking identifiers that enable the user 2.4.2.b, Page 1-27
to track problem resolution online or by phone;
6. The Contractor shall offer multi-tiered customer support options with
increasing levels of customer service for agencies’ selection
appropriate to their specific needs and in accordance with task orders
that they establish. The Contractor shall offer the following user
support tiers, and may offer additional tiers of customer support
consistent with commercial best practices:
a) Basic customer support services that meet all requirements
specified in paragraphs 1) through 5) above for functional and 2.4.2.d, Page 1-28
technical support, and the price for which is included in the 2.4.2.e, Page 1-28
applicable transaction fees;
b) Separately priced on-site reservation and fulfillment
2.4.2.c, Page 1-27
services;
c) Separately priced customer support services above and
beyond those provided under subparagraph a) above.
Supplemental customer support services may be performed
remotely or on-site at Federal agencies. This tier of customer
support is not intended to include the on-site reservation and
2.4.2.e, Page 1-28
fulfillment services described in subparagraph b) above
(CLINs 0007, 0024, 0044, 0064), or services provided under
non-self service reservation and fulfillment (CLINs 0002AC,
AD, AE; 0020AC, AD, AE; 0040AC, AD, AE; and 0060AC,
AD, AE).

Attachment 15
Proposal
RFP Reference
Reference
C.6.9.2 Customer Support – Objectives
1. The Contractor should provide concise context sensitive online
“help” files to assist users in basic eTS functionalities and
troubleshooting. In addition to menu entries, the eTS should 2.4.2.a, Page 1-27
consistently display a Help button or link on every screen to access
context sensitive help files and additional user support resources.
C.6.10.1 Training – Requirements
1. The Contractor shall provide eTS training in a variety of forms (e.g.,
computer-based tutorials via the eTravel portal, instructor-led classes, 2.7.a, Page 2-56
train-the-trainer curriculum, etc.) for each user role;
2. The Contractor shall provide online computer-based training for all
eTS user roles available via the eTravel portal and presented via a 2.7.a, Page 2-56
compatible web browser;
3. The Contractor shall develop, conduct, and provide instructor-led and
train-the-trainer course curriculum which may be used by the
Contractor or the Government for all eTS user roles. The Contractor 2.7.a, Page 2-56
shall incorporate hands-on eTS interaction within instructor-led
classes;
4. The Contractor shall provide eTS training environments for all user
2.7.a, Page 2-56
roles that provide a realistic experience;
5. The Contractor shall establish training scenarios that include
walkthroughs of travel and administration functions and actions that
2.7.a, Page 2-56
Federal employees will encounter within the eTS applicable to the
user role(s) being trained;
6. The Contractor shall provide training on eTS business intelligence,
business data warehouse, and reporting capabilities for federal 2.7.a, Page 2-56
managers; and
7. The Contractor shall offer separately priced supplemental training
services as specified below:
a) The Contractor shall offer supplemental instructor-led
2.7.a, Page 2-56
training for all user roles at CONUS and OCONUS locations;
b) Supplemental training classes shall accommodate at least
25 students per class and may be conducted at Government-
specified or Contractor-specified facilities, depending upon the
2.7.a, Page 2-56
preference of the ordering agency. The Contractor shall be
responsible for providing computers and Internet access for
classes conducted at Contractor-specified facilities; and
c) Unless otherwise specified by the ordering agency,
supplemental training shall not be conducted more than 30
2.7.a, Page 2-56
days prior to implementation and use of eTS by the users
trained.
C.7.2 Performance Measures – Objectives
1. The eTS should, to the maximum extent possible, meet or exceed the
desired outcomes summarized in a table on page C-50 of the
7.1, Page 7-1
Solicitation. These objectives are of equal importance to the
Government.

CREW: General Services Administration: Regarding E-Gov Travel: 1/21/2010 - Vol 1 - 1 Att 15, eTS Trace Ability Matrix

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

CREW: General Services Administration: Regarding E-Gov Travel: 1/21/2010 - Vol 1 - 1 Att 15, eTS Trace Ability Matrix

Enviado por

Direitos autorais:

Formatos disponíveis

Attachment 15

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-1 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-2 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-3 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-4 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-5 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-6 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-7 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-8 of 45 7/24/2003

eTS Traceability Matrix

C6.3.6.1 eTS Online Booking Engine – Requirements

1. The eTS online booking engine shall automatically enforce and

eTS Traceability Matrix v2.0 Page 15-9 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-10 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-11 of 45 7/24/2003

eTS Traceability Matrix

2. The eTS shall be capable of fulfilling and supporting self service

3. The eTS shall be capable of accommodating the fulfillment services of

eTS Traceability Matrix v2.0 Page 15-12 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-13 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-14 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-15 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-16 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-17 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-18 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-19 of 45 7/24/2003

eTS Traceability Matrix

C.6.3.16.1 System Administration – Requirements

eTS Traceability Matrix v2.0 Page 15-20 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-21 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-22 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-23 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-24 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-25 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-26 of 45 7/24/2003

eTS Traceability Matrix

eTS Traceability Matrix v2.0 Page 15-27 of 45 7/24/2003

eTS Traceability Matrix

C.6.5.5.1 Personnel and Physical Security – Requirements

eTS Traceability Matrix v2.0 Page 15-28 of 45 7/24/2003