GSA Contract GS-33F-0018-N

SECTION C – STATEMENT OF WORK

C.1 NORTHROP GRUMMAN PERFORMANCE-BASED WORK STATEMENT FOR eTRAVEL

Preface Similarly, some sections of the Northrop Grum-

This Performance Based Work Statement (PBWS) man proposal have been incorporated. Those sec-
describes the work that Northrop Grumman will tions and any changes made are shown in Table 2.
perform under the eTravel Service (eTS) contract.
Table 2. Proposal Sections and Changes.
The requirements of the contract will be met with
an offering called GovTrip. GovTrip consists of a Northrop Grumman
PBWS Section eTravel Proposal Sections Incorporated
web-based travel system; a set of services for im- 4. Requirements Round 1 Technical Volume, Section 3.0,
plementation, customer support, and training; and Functional Capability.
deliverable products. A chart containing all of the 5. WBS Round 1 Technical Volume, Section 1.2.9,
mandatory and objective requirements that WBS, with section numbers changed for this
GovTrip meets is also included in this section in document.
Table 5. 6. Performance Round 1 Technical Volume, Section 1.3,
Levels Performance Goals, with section numbers
This document contains six major sections: changed for this document; Section 1.2,
Monitoring Performance from Round 1
• Background Management Volume with 1.2.2.1, Metrics
• Scope Review Board and 1.2.2.2, Risk Review Board
inserted.
• Applicable Documents
• Requirements
• Work Breakdown Structure
• Level of Performance.
In order to allow this document to stand alone,
some sections of the eTravel RFP have been in-
corporated. Whenever this was done, the only
changes made were to make the wording more
appropriate for a work statement or to delete some
unnecessary language, such as instructions to bid-
ders. Table 1 shows which RFP sections have been
incorporated and what changes, if any, were made.
Table 1. RFP Sections and Changes.
PBWS Section eTravel RFP Section(s) Incorporated
1. Background RFP C.1 Background and Purpose in its
entirety, with minor wording changes to take
out references to ‘solicitation’ and to the
eTravel Home Page.
3. Applicable The list of document titles in RFP C.5
Documents Applicable Documents and Information, with
descriptions and web addresses removed;
several other documents added.
4. Mandatory Section C is incorporated with minor wording
Requirements changes to delete references to “offerors” and
“contractor,” and to replace “shall” and
“should” with “will.” Some descriptive
paragraphs under main headings not
suggestive of requirements were also deleted.
Appendix A RFP C.4 Definitions incorporated without
change. RFP B.1 Pricing Definitions
incorporated without change.

C-1
 GSA Contract GS-33F-0018-N
BACKGROUND
The electronic travel (eTravel) project is grounded
in the President’s E-Government (E-Gov) initia-
tive and the Administration’s commitment to em-
ploy the latest technology to create a more effi-
cient, citizen-centered Federal Government. The
eTravel project was launched in response to The
President’s Management Agenda. Its mission is to
improve the internal efficiency and effectiveness
of the Federal Government. eTravel is a collabora-
tive, inter-agency initiative whose purpose is to
realize operational efficiencies, cost-savings, and
increased service to the Federal traveler through a
common, automated, and integrated approach to
managing Federal Government travel functions.
A common eTravel solution does not exist in the
Federal Government today. The commercial mar-
ketplace advertises both partial and end-to-end,
web-based travel management products. The Gov-
ernment is looking to industry for innovative ap-
proaches to provide a travel management solution
based upon streamlined business processes and
using the latest web technologies for service deliv-
ery. The goal of the eTravel initiative is to provide
a web-based, end-to-end travel management ser-
vice for use by all Executive Branch departments
and agencies of the Federal Government.
Use of the eTS by Executive Branch agencies is
anticipated to be established by policy and regula-
tion. A number of agencies are expecting to be
early adopters. It is anticipated that 12 of the 24
Federal Enterprise Architecture Business Refer-
ence Model agencies will have fully or partially
implemented the eTS within 27 months after con-
tract award. These 12 agencies represent approxi-
mately 40% of civilian Executive Branch travel
activity.
The goals of the eTravel project include the fol-
lowing:
1) Consolidate travel processes at the Govern-
mentwide level
2) Consolidate data to enable the Government to
fully leverage its travel buying power
3) Provide an integrated, web-based travel man-
agement environment that is customer-centric,
provides self-service, and offers end-to-end
travel services
4) Facilitate and simplify the Federal travel pro-
cess, improve customer service to the Federal
C-2
traveler, and foster superior customer satisfac-
tion;
5) Accelerate reimbursement of travel expenses
to the Federal traveler and to travel charge
card vendors
6) Enable central travel management and make
travel procedures configurable at the depart-
ment, agency, and subordinate organization
levels
7) Minimize or eliminate the Government’s capi-
tal investment as well as Governmentwide op-
erational and maintenance costs
8) Significantly reduce the cost of Federal travel
management to achieve dramatic savings by
avoiding unnecessary duplication of automa-
tion efforts by the various federal agencies
9) Provide Governmentwide, consolidated and
aggregated data to support world class travel
management and afford greater visibility into
Federal travel processes for continued man-
agement improvement and cost savings
10) Leverage commercial and Government travel
management best practices and adopt com-
mercial standards and practices wherever pos-
sible
11) Maximize the use of open architecture stan-
dards, as well as leverage industry standards
and commercially available services and sup-
port items.
The Federal Travel Regulation (FTR), the Foreign
Affairs Manual (FAM), the Joint Federal Travel
Regulations (JFTR), and other applicable travel
regulations and related agency policies establish
the Federal travel process. The eTravel Program
Management Office (PMO) provides central man-
agement of both the eTravel initiative and its asso-
ciated travel process reengineering. The Govern-
ment objective is to establish an efficient,
standardized, and common travel process sup-
ported by the eTS that complies with the FTR and
other applicable travel regulations as may be re-
vised to accommodate information technology
(IT) advances and streamlined travel management
policies and procedures. The eTravel PMO, work-
ing with the Office of Governmentwide Policy,
will drive the regulatory and policy changes re-
quired to achieve its vision of the consolidated,
standardized, and efficient automated travel man-
agement service described herein. The eTravel
 GSA Contract GS-33F-0018-N
PMO also facilitates knowledge sharing and ex-
change of best practices among Federal agencies
in support of their individual efforts. The eTS will
support the implementation of new Federal
eTravel standards and practices.
SCOPE
This PBWS describes how Northrop Grumman
will meet the requirements of the SOO, and what
performance levels will be met. Section 4,
Requirements, identifies the requirements for the
system and services. Requirements are of four
kinds, with a subsection for each:
• Functional requirements: What services are
provided by the system (Section 4.1)
• Other service requirements: Implementation,
customer support, and training (Section 4.2)
• Schedule requirements: When key events will
occur (Section 4.3)
• Deliverable requirements: What products will
also be delivered (Section 4.4).
Section 5 presents the work breakdown structure
(WBS). The WBS is a statement of the work areas
that will be performed to meet the requirements.
The WBS is based on the requirements in the SOO
and Section 4 of this document, and a mapping is
shown.
Section 6 defines the levels of performance that
will be achieved by the system, services, and de-
liverables. Section 6.3, Government Obligations,
is an important section that describes what Gov-
ernment actions are necessary for Northrop Grum-
man to be able to meet the performance goals.
APPLICABLE DOCUMENTS
The following is a list of applicable documents
from RFP C.5 with several documents added:
• eTravel Service Statement of Objectives
• Federal Acquisition Regulation 37.6 Perform-
ance-Based Contracting
• CMMI for Systems Engineering/Software En-
gineering
• DoD Civilian Personnel Per Diem Bulletin
• Draft Federal XML Developer’s Guide
• Electronic and Information Technology Acces-
sibility Standards (36 CFR Part 1194) Imple-
menting Section 508 of the Rehabilitation Act
of 1973 (29 U.S.C. 794d) as Amended by the
Workforce Investment Act of 1998 (P.L. 105-
220)
• Section 508 Law
C-3
• 1998 Amendment to Section 508
• Section 508 Standards
• Guide to the Section 508 Standards for Elec-
tronic and Information Technology
• Web Content Accessibility Guidelines 1.0
• Electronic and Information Technology Acces-
sibility Standards, 36 CFR Part 1194
• eTravel Business Process Flow Diagram
• Notional eTS Operational Architecture
• Federal Information Security Management Act
of 2002
• Federal Travel Regulation
• General Accounting Office (GAO) Policy and
Procedures Manual for Guidance of Federal
Agencies, Title 7, Fiscal Procedures
• GSA CIO-IT Security-01-09, IT Security and
Procedural Guide—Certification and Accredi-
tation, with Addendum 1
• GSA Domestic Per Diem Rates
• GSA Nationwide Travel Management Services
Contract Statement of Work
• GSA Security Order, CIO HB 2100.1A, GSA
Information Technology (IT) Security Policy
• Joint Federal Travel Regulation (JFTR) Vol-
ume 1
• Joint Financial Management Improvement Pro-
gram (JFMIP) Travel System Requirements
• Joint Travel Regulations (JTR), Volume 2
• National Archives and Records Administration
General Records Schedule 9
• National Archives and Records Administration
General Records Schedule 20
• National Institute of Standards and Technology
(NIST) Special Publication 800-26, Security
Self-Assessment Guide for Information Tech-
nology Systems
• NIST Cryptographic Toolkit
• NIST Special Publication 800-18, Guide for
Developing Security Plans for Information
Technology Systems
• Office of Management and Budget (OMB) Cir-
cular No. A-130, Management of Federal In-
formation Resources, including Appendix III,
Security of Federal Automated Information Re-
sources
• Preferred Suppliers List
 GSA Contract GS-33F-0018-N
• Suitability and Personnel Security Handbook,
GSA ADM P 9732.1C
• U.S. Department of State Foreign Affairs Man-
ual (FAM), 6 FAM Volume 100, Travel,
Transportation, and Storage
• U.S. Department of State Standardized Regula-
tions (DSSR)
• Voluntary Product Accessibility Template
(VPAT)
• FEA standards to be published by the FEA Pro-
gram Management Office (FEAPMO).
REQUIREMENTS
This section contains requirements in four catego-
ries. Sections 1-9 contain the functional require-
ments for the web-based system. These sections
will serve as the System Requirements Specifica-
tion against which system testing will be done and
will serve as the basic system requirements man-
agement database. The System Functional Re-
quirements Specification (SFRS) has been en-
closed in a page border for ease of identification. It
is the complete set of functional requirements for
the eTS.
In addition to the functional requirements of the
system, there are three services to be delivered
(implementation, customer support, and training).
The requirements for these services are in Section
4.2. The schedule requirements are in Section 4.3
C-4
and are of two kinds. The first kind is the schedule
requirements for IOC and FOC. The second is the
schedule for agency implementation.
Finally, requirements for deliverables in the form
of documents or reviews are in Section 14-16.
Section 4 contains all of the requirements in the
eTravel PBWS.
REQUIREMENTS DEFINED
Requirements are those essential capabilities and
characteristics which must be met in order to
ensure regulatory compliance and meet minimum
functional requirements. eTS requirements
include mandatory Joint Financial Management
Improvement Program (JFMIP) Travel System
Requirements as may be modified within the
PBWS. They are considered go/no-go criteria;
failure to meet all requirements described herein
will result in an offer being excluded from further
evaluation.
OBJECTIVES DEFINED
Objectives as identified in the RFP as are those
capabilities and characteristics which contribute
significantly and synergistically to the
achievement of the Government’s
eTravel vision. Table 5 contains a listing of all the
objectives and a column indicating if GovTrip has
full or partial solution to those objectives.
 GSA Contract GS-33F-0018-N
eTRAVEL SYSTEM
FUNCTIONAL REQUIREMENTS SPECIFICATION
1.0 Types of Travel
1.1 REQUIREMENTS
The eTS will initially support the following types of
Federal Travel:
1) Temporary Duty (TDY) travel (including foreign
and domestic
2) Local travel
3) Long term TDY and long term local travel
(including foreign and domestic)
4) Invitational travel
5) Non-Federally sponsored travel.
1.2 OBJECTIVES
There are no objectives identified for this section.
2.0 Services
2.1 REQUIREMENTS
Northrop Grumman will meet the following
requirements for eTS services:
1) Northrop Grumman will supply all services and
support capabilities required to host and deploy the
eTS solution to Federal agencies.
2) Northrop Grumman will deliver the eTS via a web-
based, self-service environment, supplemented
with phone, fax, person-to-person, and other
customer support modalities as applicable.
3) Northrop Grumman will determine detailed
specifications necessary to meet the mandatory
requirements and objectives described herein.
4) Contractor services, resources, and capabilities
required under this SOO will include, but may not
be limited to the following:
a) IT services and support capabilities
b) Federal travel process and travel management
expertise
c) Web-based reservation service (online booking
engine)
d) Implementation planning and support for
Federal agencies
e) Training for all eTS user roles
f) Customer support (including eTS functional
support, technical support for related IT
problems, and assistance with travel
arrangements).
C-5
3.0 BASIC CAPABILITIES AND
CHARACTERISTICS
3.1 REQUIREMENTS
The eTS will meet the following requirements for
basic capabilities and characteristics:
1) The eTS will provide a web-based, end-to-end
travel management environment to plan, au-
thorize, arrange, process, and manage official
Federal travel.
2) The eTS will support all Federal travel proc-
esses, including, but not limited to, travel
planning and cost estimating, travel authoriza-
tion, booking of travel reservations and travel
arrangements, filing/processing/approval of
official travel claims, travel reporting and
business intelligence, and travel-related data
exchange.
3) The eTS will present all services, functional-
ity, and user support through a single World
Wide Web (WWW) Uniform Resource Loca-
tor (URL) portal. At its discretion, the Gov-
ernment will provide an appropriate “.gov”
URL for Northrop Grumman’s eTravel portal
or establish a link from another “.gov” web
site to Northrop Grumman’s eTravel portal.
4) The eTS will provide web-based delivery of
services and data exchange with access and
input possible by all users and approving offi-
cials at their official station and remote loca-
tions.
5) The eTS will provide the capability to cen-
trally manage the Federal travel procedures
through a common, configurable, customer-
centric, self-service, web-based environment.
6) The eTS will allow policy updates to be made
in real time and allow travel policy to be ad-
ministered with or without exceptions at the
Federal agencies’ option.
7) The eTS will provide access to and control of
all Government preferred travel suppliers and
negotiated rates for booking travel reserva-
tions.
8) The eTS will maintain the order of precedence
for executing travel steps (i.e., authorization
must precede a voucher,) and adequate separa-
tion of duties (e.g., for trip approval, travel
 GSA Contract GS-33F-0018-N
voucher approval, and travel voucher pay-
ment).
9) The eTS will provide controls to prevent the
creation of duplicate travel documents.
10) The eTS will provide for an audit trail on his-
torical data that identifies input, correction,
amendment, cancellation, and approval.
11) The eTS will provide a standard data in-
put/output to support the exchange of data
with agency business systems (e.g., financial,
human resources, etc.), including the capabil-
ity for near real-time, travel-related transac-
tions (e.g., funds availability checking, trav-
eler profile creation or updates).
12) Northrop Grumman will work and coordinate
with Government subject matter experts and
other travel partners (e.g., the vendor for the
FedTrip™ online reservation system and
TMCs) to integrate and deploy the eTS.
13) The Government shall own all Federal data
generated by and/or stored in the eTS.
14) The eTS will allow Government policies,
business rules, vendor contract parameters,
permissions, and profiles to be updated with-
out the need for programming.
4.0 POLICY COMPLIANCE 4.1
REQUIREMENTS
The eTS will meet the following requirements for
policy compliance:
1) Comply with the FTR and other applicable
Federal travel regulations in effect on the date
of contract award and any subsequent amend-
ments 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 ap-
plicable classes of Federal travelers, and com-
ply with any subsequent amendments thereto
on their effective date unless otherwise speci-
fied 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 marketplace in time to meet the
delivery requirements of this contract.
C-6
4) Comply with the mandatory JFMIP Travel
System Requirements in effect on the date of
contract award and as may be modified herein,
and comply with any subsequent revisions
thereto on their effective date unless otherwise
specified by the Government.
5.0 FUNCTIONAL CAPABILITIES AND
CHARACTERISTICS
5.1 USER ROLES, USE CASES, AND ACCOUNT
ACCESS
5.1.1 Requirements
The eTS will meet the following requirements for
user roles, use cases, and account access:
1) Northrop Grumman will use Attachment 2,
Notional eTravel Service Use Cases, as the
foundation from which user roles, detailed use
cases, and the eTS Concept of Operations
(CONOPS) is developed.
2) Northrop Grumman will determine and ana-
lyze Federal travel requirements in order to es-
tablish the eTS Concept of Operations
(CONOPS), user roles, and use cases.
3) Northrop Grumman will ensure that the eTS
supports establishment of user accounts with
specific permissions and access rights.
4) Northrop Grumman will ensure that the eTS
prevents intentional or inadvertent access to
data and functionality not specifically associ-
ated with particular user roles, accounts, and
related permissions.
5) Northrop Grumman will define data element
access for all user roles to meet role-specific
functionality, Privacy Act, and other security
capabilities and characteristics defined herein.
5.2 ETRAVEL PORTAL
5.2.1 Requirements
The eTS will meet the following requirements for
the eTravel portal:
1) Northrop Grumman will establish an eTravel
web portal that serves as the gateway to the
eTS Federal travel management environment.
2) The eTS portal will provide a configurable
environment that can be used by all eligible
users and provides access to all services and
systems used within the eTS.
3) The eTS portal will provide a search capability
for travel documents and information (e.g., au-
thorizations, vouchers, or regulatory informa-
tion).
 GSA Contract GS-33F-0018-N
4) The eTS portal will display terms of use and
Privacy Act notifications upon access and re-
quire user assent to the terms of use and data
protection responsibilities at time of login in
accordance with Section 7 and Attachment 4.
5) The eTS portal will provide a contract admini-
stration workspace, including a bulletin board
for posting eTS contract documents and mes-
sages to and from Northrop Grumman, GSA,
and Federal agencies. Purposes envisioned in-
clude the posting of messages by Federal
agencies interested in pooling their task order
requirements.
6) The eTS will provide the ability for users to
create and maintain their traveler profiles
online (subject to specific data element per-
missions).
5.3 TRAVELER PROFILES
5.3.1 Requirements
The eTS will meet the following requirements for
traveler profiles:
1) The eTS will provide for entry, retention, up-
dating, and deletion of traveler profiles associ-
ated with and subject to the permissions of
Federal or invitational travelers’ eTS accounts.
2) The eTS will be capable of importing traveler
profiles from agency business systems or other
external data sources in a standard data format
specified by Northrop Grumman (e.g., comma
delimited). Federal agencies will be responsi-
ble for the quality assurance of traveler profile
data provided for import to the eTS. The eTS
vendor will only be responsible for ensuring
the fidelity of traveler profile data imported
into the eTS with the corresponding data pro-
vided by the Federal agencies.
3) The eTS will support the entry of traveler pro-
file data online by all users (including non-
Federal invitational travelers) via the compati-
ble web browsers. Federal agencies will be re-
sponsible for the quality assurance of traveler
profile data entered by the traveler via the web
browser.
4) The eTS will provide access to a Federal
agency’s pertinent traveler profile data ele-
ments required for ticketing and fulfillment
purposes to the TMC(s) under contract to that
agency. Access to specific data will be subject
to Privacy Act and applicable System of Re-
cords protections. The eTS will send a notify-
C-7
cation to the Federal traveler’s affiliated
TMC(s) when his or her profile is modified.
5) The eTS traveler profile will be capable of
entry and retention of the following discrete
data elements:
a) Traveler’s name, Social Security Number
(SSN) and/or other employee identifica-
tion number
b) Agency/organization, position title, and
permanent duty station
c) Office phone, mobile phone, mailing ad-
dress, e-mail address, and payment ad-
dress
d) Possession of a Government Contractor-
issued, individually-billed charge card
e) Applicable accounting data, such as de-
fault funding citations, individual billing
account number(s), central billing account
numbers(s), third party payment account
numbers, bank account numbers, and cor-
responding Electronic Funds Transfer
(EFT) routing data (all of which must be
able to be manually overridden within any
particular travel action)
f) User role designation(s) and system per-
mission level(s) (as established by appro-
priate agency travel administrator, ap-
prover, or coordinator).
5.4 TRAVEL PLANNING AND
AUTHORIZATION
5.4.1 Requirements
The eTS will meet the following requirements for
travel planning and authorization:
1) The travel planning and authorization function
of the eTS will provide the capability to create
travel plans and authorizations, including de-
tailed itineraries and related cost estimates that
may be retained separately or included in the
travel authorization.
2) The eTS will support the processing of various
types of travel authorizations, including
unlimited open, limited open, and trip-by-trip.
3) The eTS will allow the traveler to state the
purpose of their trip in accordance with Ap-
pendix C, FTR 301, “Travel Purpose
Identifier.”
 GSA Contract GS-33F-0018-N
4) The eTS will allow for the option of specific
authorization or prior approved travel ar-
rangements as required by FTR 301-2.
5) The eTS will support the routing and approval
of travel and transportation authorization
documents. It will provide Federal agencies
flexibility with regard to the number and lev-
els of approval required for travel authoriza-
tions, including cross-organizational travel.
6) The eTS will allow rejection, correction,
amendment, and cancellation of the travel au-
thorization with appropriate review and ap-
proval controls, including text and code expla-
nation fields. The eTS will provide
notification of rejection, correction, amend-
ment, and cancellation to the traveler, travel
arranger, supervisory approver, and financial
approver as appropriate.
7) The eTS will support the capability to identify
and indicate whether the traveler holds a Gov-
ernment travel charge card based upon data
provided by the employee’s agency. (Note:
This requirement will not be construed to af-
fect the GSA SmartPay® contract or require
GSA SmartPay® contractors to exchange data
with or permit linkage to eTS.)
8) The eTS will support automation of near real-
time funds availability checks, funds commit-
ment/obligation, and the ability to transfer ac-
counting data with agency business systems
within the standard data input/output content.
It will provide the capability to report funds
availability when appropriate (e.g., for specific
TDY trip authorization).
9) The eTS will provide verification that authori-
zation for travel exists;
10) The eTS will provide the capability to process
travel authorizations with split fiscal year
funding and with multiple lines of funding.
11) The eTS will calculate estimated authorized
per diem in accordance with FTR 301-11 (fac-
toring in leave and non-work days, interrupted
travel, reduced per diem rates, and actual ex-
penses) as well as meals and incidental ex-
penses (M&IE) based on the TDY location(s)
and the dates of travel. The eTS will recalcu-
late “should-cost” amounts and perform re-
vised funds availability checks as applicable
for travel plan or itinerary changes.
C-8
12) The eTS will provide the capability to display
to the user and capture within the travel au-
thorization defined notes and messages regard-
ing certification statements, Privacy Act
Statement, standard clauses for required re-
ceipts, supporting documentation require-
ments, justification statements for use of spe-
cial travel arrangements, etc.
13) The eTS will provide the capability to ac-
commodate and incorporate the services of the
TMC(s) under contract to Federal agencies
and their appropriate Commercial Reservation
System(s) (CRS).
14) 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: 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.).
5.5 RESERVATIONS
5.5.1 Requirements
The eTS will be responsible for delivering the res-
ervation services described in this section to order-
ing agencies, whether provided directly by the eTS
vendor or in conjunction with FedTrip and/or
TMCs under contract to Federal agencies. The eTS
will meet the following requirements for
reservations:
1) The eTS provides the capability to make both
self-service and non-self-service reservations
for the following transportation and travel ar-
rangements, at a minimum:
a) Air travel on domestic and international
common carrier flights, including all GSA
City-Pair contract carriers and flights and
published non-contract Government (“me
too”) fares and other discount fares that are
advantageous to the Government
b) Domestic and international car rental res-
ervations with all Military Traffic Man-
agement Command (MTMC) or other
Government preferred sources at or below the
applicable ceiling rate
c) Domestic and international lodging sup-pliers
participating in the Federal Premier Lodging
 GSA Contract GS-33F-0018-N
Program (FPLP) or other Government
preferred sources, including designation and
tracking of the use of Federal Emergency
Management Agency (FEMA) approved
lodging properties
d) Domestic common carrier rail and bus travel
e) Other common carrier travel, e.g., ship
transportation.
2) The eTS self service reservation capability
includes the following:
a) An online booking engine (web-based res-
ervation service) of Northrop Grumman’s
choice that meets s the requirements of
Section 5.6.
b) The capability to accommodate the Fed-
Trip online booking engine on an in-
terim basis through September 30, 2004.
Accommodation of FedTrip is defined
as supporting its use by Federal travelers
and TMCs under contract to Federal agen-
cies as an online booking engine for the
eTS. There is no requirement (or
objective) for the automated integra-tion
of FedTrip with other eTS func-
tionalities. Accommodation may be lim-
ited to travelers reserving travel through
FedTrip and then manually entering
travel arrangement information into eTS
travel planning, authorization, and
voucher functions.
3) The eTS accommodates the services of TMCs
under contract to Federal agencies for non-
self-service reservations.
4) The eTS provides access to all Government
preferred suppliers and rates for transporta-
tion, lodging, and rental car reservations. The
eTS restricts access to Government-only rates
to Federal employees and other authorized us-
ers of those rates.
5) The eTS is capable of modifying and cancel-
ing all such reservations prior to ticket issu-
ance without Government incurrence of a
transaction fee and subject to applicable car-
rier or supplier cancellation provisions.
6) The eTS requires users to identify the appro-
priate FTR exception and provide justification
for the use of all non-preferred or non-
contracted providers, and/or non-U.S. flag air
carriers when booking such reservations.
C-9
5.6 ETS ONLINE BOOKING ENGINE
5.6.1 Requirements
The eTS will meet the following requirements for
its online booking engine:
1) The eTS online booking engine will automati-
cally enforce and monitor compliance to the
appropriate Federal and agency-configured
travel policies during the reservation process
and will control access to all Government ne-
gotiated travel rates (e.g., City-Pair airfares). It
will allow users to override travel policy by
providing the reason for the exception and
provide exception coding and text explanation
capabilities.
2) Northrop Grumman will provide the ability for
Government designated TMC(s) to use the
eTS online booking engine and permit travel
reservations made within the booking engine
to be retrieved in real time by agencies’
TMCs.
3) The eTS online booking engine will provide
estimates of travel costs prior to making an ac-
tual reservation.
4) The eTS online booking engine will provide
published and Government negotiated airfares,
lodging rates, and car rental rates. It will
clearly identify preferred and mandatory travel
suppliers wherever applicable. It will display
Government contracted and Government pre-
ferred travel suppliers first in ascending rate
order and filter out non-compliant choices
based on agency/organizational policy rules
(e.g., preferred suppliers only). Failure to use
Government-negotiated rates will require ap-
propriate justification (with reason/exception
code and text capabilities). Northrop Grum-
man will utilize the reason/exception codes in
Attachment 8 for negotiated airfares and pro-
poses configurable reason/exception codes for
all other travel suppliers.
5) The eTS online booking engine will include
all global commercial airport destinations and
display available airfares for domestic and in-
ternational air travel. It will display alternate
airport/city options for a specific destination.
It will provide appropriate and accurate Gov-
ernment rates under the GSA City-Pair Pro-
gram, published non-contract Government
fares (fare code DG or “me too” fares), and
other discount fares in a real-time environ-
ment. It will support an unlimited number of
 GSA Contract GS-33F-0018-N
City-Pair fares. It will display all applicable
flights, destination information, flight sched-
ules, and other pertinent flight information for
all flights listed. It will clearly display the
availability of appropriate class seating, and
the airfare rules for all available fares. It will
reserve airline travel accommodations for air-
lines listed in Global Distribution Systems
(GDSs) in a real-time 24/7/365 environment.
Failure to use Government-negotiated rates
will require appropriate justification (with rea-
son/exception code and text capabilities).
Northrop Grumman will utilize the rea-
son/exception codes in Attachment 8 for nego-
tiated airfares.
6) The eTS online booking engine will provide
appropriate and accurate Government rates in
a real-time environment for FPLP or other
Government preferred lodging suppliers and
will designate FEMA-approved lodging prop-
erties. It will display FEMA approved lodging
properties ahead of those that are not FEMA
approved. It will reserve lodging accommoda-
tions in a real-time, 24/7/365 environment. It
will require appropriate justification (with rea-
son/exception code and text capabilities) in
accordance with Pub. L. 5 USC 5707a and re-
sulting FTR requirements for failure to use
FEMA approved lodging. Northrop Grumman
will provide configurable reason/exception
codes for all lodging suppliers.
7) The eTS online booking engine will provide
appropriate and accurate rates for domestic
and international car rentals in a real-time en-
vironment for all MTMC or other Government
preferred car rental agencies at or below the
applicable Government ceiling rate. It will re-
serve rental car accommodations in a real-time
24/7/365 environment. Failure to use Gov-
ernment-negotiated rates will require appro-
priate justification (with reason/exception
code and text capabilities). Northrop Grum-
man will propose configurable rea-
son/exception codes for all car rental suppli-
ers.
8) The eTS online booking engine will support
one-way, round-trip, and multiple destination
itineraries. It will verify segment date/time se-
quence during the reservation process to en-
sure logical itineraries and permissible con-
nections. It will consolidate all travel segments
for an itinerary into a single record and create
C-10
all necessary fields in the Passenger Name Re-
cord (PNR) within the GDS(s) and applicable
TMC reporting systems; and
9) The eTS online booking engine will allow us-
ers to modify and/or cancel reservations prior
to ticket issuance without Government incur-
rence of a transaction fee. It will allow the
user to re-price an itinerary after initial crea-
tion when modifications are made, and route
the re-priced itinerary for notification or re-
submit the revised authorization for re-
approval.
5.7 FULFILLMENT
Northrop Grumman will employ expedited agency
TMC incorporation schemes to speed agency
adoption of the eTS and eTS transaction volume
growth. The eTS will also provide ticketing, ful-
fillment, and associated customer support capabili-
ties for Federal travelers. Fulfillment and support
for reservations made online through FedTrip™
and/or the eTS booking engine will be made avail-
able through eTS in addition to the TMCs, subject
to the terms of agencies’ existing TMC contracts.
5.7.1 Requirements
The eTS will meet the following requirements for
fulfillment:
1) The eTS will provide fulfillment services and
associated customer support capabilities for
Federal travel.
2) The eTS will fulfill and support 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 agencies, subject to the
terms of those contracts.
3) The eTS will be capable of accommodating
and incorporating the services of TMCs under
contract/task order to Federal agencies for the
purposes of ticketing and fulfillment as au-
thorized under that contract/task order.
4) The eTS will provide electronic ticketing as
the default option for all common carriers that
support electronic ticket issuance.
5) The eTS will ensure that the corresponding
travel authorization has been approved prior to
ticket issuance with the ability to override this
business rule by allowable exceptions (e.g.,
emergency travel).
 GSA Contract GS-33F-0018-N
) The eTS will be capable of processing and
crediting cancelled or unused tickets and par-
tial fare refunds subject to applicable carrier or
supplier cancellation provisions with attendant
expense and accounting adjustments.
7) The eTS will process allowable credits result-
ing 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 will ensure that credits
and cancellations are accountable to the appli-
cable travel authorization number and billing
account. The eTS will reflect those credits
within all applicable functionalities as well as
in the standard data output provided to inter-
facing agency business systems.
5.8 TRAVEL ADVANCE
5.8.1 Requirements
The eTS will meet the following requirements for
travel advances:
1) If the Government issues a travel advance, the
eTS will support entry, processing, approval,
and the payment and liquidation of Govern-
ment funds. This function must support the
tracking, aging, and control of advances.
2) The eTS will provide the capability to set,
change, and apply established limits on travel
advances in accordance with the FTR, other
applicable travel regulations, and agency poli-
cies.
3) The eTS will provide for limiting the allowed
advance based upon transportation method,
subsistence rates, miscellaneous expenses, and
the traveler’s possession of a Government
Contractor-issued travel charge card.
4) The eTS will make travel advance information
for a particular travel authorization accessible
in travel voucher preparation.
5) The eTS will 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 the traveler. The eTS
will also provide the capability not to liquidate
the advance when the traveler has been author-
ized a “retained” travel advance in accordance
with FTR Part 301-51.
6) The eTS will provide for automatic aging of
outstanding travel advances based on the au-
C-11
thorized end of trip date and generate follow-
up notices to the travelers and approvers con-
cerning delinquent advances that may affect
payroll offsets or other means of collection.
7) The eTS will support the reporting of delin-
quent travel advances as taxable income
through the inclusion of appropriate data ele-
ments in the standard data output.
8) The eTS will allow for and support the prepa-
ration and authorization of emergency travel
advances.
9) With regard to payment and liquidation func-
tionalities for travel advances, the eTS will
only be responsible for making pertinent in-
formation available to agency business sys-
tems (e.g., financial and payroll systems)
within its data exchange and application inte-
gration capabilities.
5.9 TRAVEL VOUCHERS
5.9.1 Requirements
The eTS will meet the following requirements for
travel vouchers:
1) The eTS will provide for the preparation,
submission, and routing of TDY travel vouch-
ers to claim reimbursable expenses for official
travel. The eTS will provide Federal agencies
flexibility with regard to the number and lev-
els of approval required for travel vouchers,
including cross-organizational travel. It will
allow for special routing and approval levels
for vouchers for certain classes/conditions of
travel as required by FTR 301-2.
2) The eTS will provide a tracking system that
will allow travelers, approvers, payment of-
fices, etc., to determine the status of any
voucher/claim in process within the permis-
sions granted to the user.
3) The eTS will pre-populate appropriate data
fields of the voucher based on information
contained within eTS from sources such as the
travel authorization (including any cash ad-
vance provided to the traveler when applica-
ble), traveler profile, etc. The eTS will permit
the user to manually override and edit any ac-
counting data passed automatically to the
voucher.
4) The eTS will provide the capability to create
and modify travel vouchers before final ap-
proval. It will provide routing of vouchers to
the approving official upon submission by the
 GSA Contract GS-33F-0018-N
traveler. It will permit the approving official to
deny and remand the voucher back to the trav-
eler or approve it and forward it for payment.
It will require the approving official to specify
a reason for denial (by means of configurable
codes and text) for all vouchers denied.
5) The eTS will allow for entry of the date of
departure from, and return to, the official duty
station or any other place when travel begins,
ends, or requires overnight lodging in order to
calculate reimbursable expenses and allow-
ances.
6) The eTS will support identification, documen-
tation, and claims for reimbursement of all
modes of transportation (including bus and
ship) authorized by the FTR and other appli-
cable travel regulations.
7) The eTS will 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 loca-
tion(s) and date(s) of travel. The eTS will pro-
vide the personal vehicle mileage rate in effect
on the date(s) and calculate mileage allow-
ance. The eTS will allow the manual entry of
approved or official subsistence rates, mileage
allowance, etc., if not available within the
eTS.
8) The eTS will compute the M&IE allowance
rates based on travel completed and meals
provided in accordance with FTR 301-11. The
eTS will use the following M&IE allowance
rates based on travel completed:
a) More than 12 hours but less than 24: 75%
of the applicable M&IE rate
b) 24 hours or more, on:
i) Day of departure: 75% of the applica-
ble M&IE rate
ii) Full days of travel: 100% of the appli-
cable M&IE rate
iii) Last day of travel: 75 percent of the
applicable M&IE rate.
9) The eTS will process amended vouchers and
reclaim vouchers with appropriate review and
approval controls. It will provide the capabil-
ity to update related functionalities within
eTS. It will allow for special routing and ap-
C-12
proval levels for certain classes/conditions of
travel as required by FTR Chapter 301.
10) The eTS will permit multiple vouchers sub-
mitted against a single authorization for ap-
propriate travel types (e.g., open travel au-
thorizations). It will process partial/interim
vouchers against a travel authorization to ex-
pedite liquidation related to travel obligations.
It will provide a clear and unambiguous final
voucher indicator for the final claim submitted
against an open travel authorization.
11) The eTS will provide the capability to display
defined messages to the user regarding:
a) Required receipts for lodging and author-
ized expenses incurred over $75
b) Requirements for supporting documenta-
tion, justifications, and certification state-
ments in accordance with the FTR and
other applicable travel regulations.
12) Northrop Grumman will provide the capability
and procedures with appropriate messages to
guide the user through the process for the sur-
render and handling of unused, partially used,
or downgraded/exchanged tickets, refund cer-
tificates, etc.
13) The eTS will provide for configurable system-
generated notices when claims and supporting
information have not been submitted in accor-
dance with suspense dates, internal policies,
and procedures established by the agencies.
14) The eTS will support payment of travel claims
by means of its data exchange and application
integration capability. It will support a split
disbursement mechanism within the standard
data output that allows the traveler to desig-
nate applicable amounts to be paid directly to
a Government travel charge card vendor
and/or reimbursed to the traveler. It will also
support recovery of funds owed to the Gov-
ernment as a result of travel through offset of
the traveler’s salary, retirement credit, or other
payment owed to the employee within the
standard data output.
15) The eTS will provide for matching of travel
vouchers with the travel authorizations.
16) The eTS will provide agencies and subordi-
nate organizations the capability to set sam-
pling parameters for their travel vouchers for
audits, information requirements, or other pur-
 GSA Contract GS-33F-0018-N
poses based on criteria determined by the
agency. These parameters may include ran-
dom sampling, cost thresholds, travel type,
traveler identity, etc. (Statistical sampling re-
quirements are contained in the GAO Policy
and Procedures Manual for Guidance of Fed-
eral Agencies, Title 7, Fiscal Procedures.)
5.10 LOCAL TRAVEL VOUCHERS
5.10.1 Requirements
The eTS will meet the following requirements for
local travel vouchers:
1) The eTS will provide the capability for users
to prepare, submit, and route a local travel
voucher for approval and payment.
2) The eTS will compute local mileage allow-
ances using the approved mileage rate in effect
on the date(s) of travel.
3) The eTS will support funds availability
checks, commitment/obligation, and payment
of local travel claims within its data exchange
and application integration capabilities.
5.11 TRAVEL RECEIPTS
The eTravel program, working with the Office of
Governmentwide Policy, will be pursuing and co-
ordinating revisions to Federal policy to support
changes in the requirements for submission and
retention of travel receipts whereby travelers will
be authorized to submit electronic images of re-
ceipts with travel vouchers for reimbursement.
5.11.1 Requirements
The eTS will meet the following requirement for
travel receipts:
1) The eTS will provide a means to associate
hard copy travel receipts (and/or travel receipt
images if that capability is provided) with the
corresponding travel voucher submitted for re-
imbursement.
5.12 NON-FEDERALLY SPONSORED TRAVEL
5.12.1 Requirements
The eTS will meet the following requirements for
non-Federally sponsored travel:
1) The eTS will provide the capability to author-
ize and report the acceptance of payment or
payment-in-kind from non-Federal sources to
defray in whole or in part the cost of travel or
related expenses of Federal employees in ac-
cordance with FTR Chapter 304
2) The eTS will provide a mechanism to ensure
that non-Federally sponsored travel is admin-
C-13
istratively approved by the agency designated
official(s) prior to final approval of the travel
authorization
3) The eTS will provide the capability to indicate
the amounts and entitlements to be paid by the
Government and those to be paid by the spon-
soring organization. For example, if the Gov-
ernment authorizes payment of the traveler’s
MI&E and the sponsoring organization is pay-
ing for the hotel and airfare (services-in-kind),
then this arrangement must be clearly identi-
fied on the travel authorization.
4) The eTS will display estimated amounts where
actual amounts are not known.
5.13 LEISURE TRAVEL
Northrop Grumman will include the functionality
for planning, booking, and fulfilling leisure (per-
sonal) travel conducted in conjunction with offi-
cial travel within the eTS.
5.13.1 Requirements
1) Northrop Grumman will ensure that the leisure
travel functionality is provided at no cost to
the Government as reflected in per-transaction
fees, separately priced line items, etc., include-
ing any related costs for development, mainte-
nance, operation, or customer support.
2) The eTS will ensure that travelers cannot book
City-Pair or other Government-negotiated
fares not authorized for personal use when
making leisure travel reservations.
3) The eTS will ensure that leisure travel ex-
penses are not claimed for Government reim-
bursement and that a method for direct pay-
ment by the traveler for leisure travel expenses
is provided.
5.14 ACCOUNTING CAPABILITIES
5.14.1 Requirements
The eTS will meet the following requirements for
accounting capabilities:
1) Accuracy of eTS computations will be in strict
accordance with Chapter 301 of the FTR and
Sections 920 and 925 of the DSSR. The eTS
will use official per diem rates and mileage
rates in effect on the date(s) of travel for the
appropriate TDY location(s) and type(s) of
travel by default. Per Diem rates will be based
upon TDY location as opposed to airport
codes. The eTS will allow the use of actual
expenses and conference rates in lieu of or in
 GSA Contract GS-33F-0018-N
combination with per Diem rates, when
authorized.
2) The eTS will support near-real-time funds cer-
tification and commitment/obligation within
its standard data exchange and application in-
tegration capabilities.
3) The eTS will generate, record, store, and re-
port financial accounting data related to travel
authorizations, travel advances, and travel
vouchers in the standard data output.
4) The eTS will support split disbursements, i.e.,
allow the agency and/or traveler to designate
applicable expenses to be paid directly to indi-
vidually billed accounts or be reimbursed to
the traveler.
5) The eTS will provide the ability to cite multi-
ple funding sources in travel authorizations
and vouchers. It will allow agencies to estab-
lish default funding citations and payment
modalities for various travel services such as
airfare, lodging, or rental car.
6) The eTS will support the reporting of expenses
for same-day trips of more than 12 hours but
less than 24 hours with no lodging in the stan-
dard data output for interfaces to agency pay-
roll systems for inclusion in the employee’s
Form W-2, Wage and Tax Statement.
7) The eTS will track travel advances authorized
against reimbursable expenses after final
voucher submittal and report the amount due
to or owed by the traveler within the standard
data output.
8) The eTS will accommodate non-Federally
sponsored travel including acceptance of pay-
ment and payment-in-kind from non-Federal
sources with appropriate authorization re-
quirements.
5.15 ROUTING, WORKFLOW,
NOTIFICATIONS, AND SYSTEM MESSAGES
5.15.1 Requirements
The eTS will meet the following requirement for
routing, workflow, notifications, and system
messages:
1) The eTS will provide the capability to main-
tain the order of precedence for executing each
travel step (i.e., authorization must precede a
voucher) and the capability to override and
change the order of precedence of the process-
ing steps to handle unusual travel demands.
C-14
5.16 SYSTEM ADMINISTRATION
5.16.1 Requirements
The eTS will meet the following requirements for
system administration:
1) The eTS system administration capability will
permit and provide for centralized control of
Governmentwide features and business rules
as well as support the management of config-
urable business rules and travel functions by
departments, agencies, or subordinate organi-
zations.
2) The eTS will provide the following system
administration capabilities at the Govern-
mentwide and department/agency/subordinate
organization levels, as applicable:
a) User account administration, including
user roles, permissions, access controls,
and security (including eAuthentication
Gateway assurance level)
b) Traveler profile administration, including
the ability to add/modify/delete user pro-
files and add agency-specific data ele-
ments
c) Scheduling of actions, events, and re-
quirements on a recurring basis, including,
but not limited to, daily, weekly, bi-
weekly, monthly, quarterly, and annual
schedules
d) Creation and maintenance of messages to
be displayed to users regarding general
system information (including access and
Privacy Act statements), announcements,
etc.
e) Creation and maintenance of routing lists
and workflows, including the designation
of approving officials
f) Capability to establish and secure applica-
tion of digital signatures
g) Ability to backup and recover travel trans-
actions
h) Provide for gathering and analyzing usage
statistics
i) Ability to add/modify/delete per diem
rates (M&IE allowances and lodging
rates) by locality in accordance with ap-
plicable Federal regulations
j) Ability to add/modify/delete air carriers,
destinations, and airfares
 GSA Contract GS-33F-0018-N
k) Ability to add/modify/delete lodging sup-
pliers, properties, FEMA approval desig-
nations, and rates
l) Ability to add/modify/delete rental car
suppliers, types, and rates
m) Ability to change POV mileage rates
n) Ability to add/modify/delete agency and
subordinate organization information, in-
cluding standard funding citations and
delegation of approving officials
o) Remote system administration capability
p) Ability to add/modify/delete rail, ship,
and/or bus carriers, destinations, and rates
(if online reservation capabilities for those
common carriers are provided).
6.0 TECHNOLOGY CAPABILITIES AND
CHARACTERISTICS
6.1 REQUIREMENTS
The eTS will meet the following requirements for
technology capabilities and characteristics:
1) Northrop Grumman will monitor the
http://www.feapmo.gov/ site (with principal
concentration on the Business Reference
Model [BRM] and Data and Information Ref-
erence Model [DRM] to remain aware of and
incorporate applicable standards established
for the FEA as a part of ongoing technology
refreshment.
2) The eTS will provide a browser-based user
interface and Federal travel management envi-
ronment accessible via a single URL portal on
the WWW. The portal and web server compo-
nents will be based on J2EE or .Net architec-
tures. The portal will be capable of interoper-
ating with the FirstGov Portal.
3) The eTS will be client platform and operating
system independent, and will be compatible
with the Microsoft Internet Explorer browser
(version 5.5 or later) and with the Netscape
Navigator browser (version 6.x or later).
4) The eTS will not require any client-side appli-
cation software other than one of the specified
web browsers and associated signed plug-ins
that are downloadable-on-demand and meet
the mobile code requirements of this SOO.
The eTS will not require cookies, other than
session cookies, to deliver full client function-
ality.
C-15
5) At full utilization, the eTS will support at least
5,000 concurrent users. The concurrent user
capability during agency adoption and imple-
mentation will be proportionate to this number
based on the adoption targets cited herein.
6) The eTS will provide data exchange and ap-
plication integration capabilities and infra-
structure to permit integration with Govern-
ment business systems, other E-Gov solutions,
and external partners (e.g., state and local
governments or industry). The data exchange
and application integration capabilities will
support:
a) Near-real-time, event-based integration
leveraging industry standard XML vo-
cabularies to maximize interoperability
and minimize the time for business events
to be reflected in all related systems
b) Batch integration and data translation ca-
pabilities for minimally intrusive integra-
tion with existing legacy applications that
are currently limited to existing data for-
mats and file transfer or other batch inter-
face mechanisms.
7.0 SECURITY CAPABILITIES AND
CHARACTERISTICS
7.1 GENERAL SECURITY STANDARDS
7.1.1 Requirements
The eTS will meet the following requirements for
general security standards:
1) The eTS will protect data (in all aspects enu-
merated in this section) as Sensitive But Un-
classified (SBU) information at the “Medium”
sensitivity level (as defined in GSA IT Secu-
rity 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 sys-
tem of records in accordance with the Privacy
Act. At a minimum, Northrop Grumman will:
a) Establish an eTS that is physically secure
b) Ensure that the eTS protects the integrity
of the travel process and the data con-
tained within eTS systems
c) Ensure that all traveler and travel-related
information is treated and protected as
SBU information at the “Medium” sensi-
tivity level
 GSA Contract GS-33F-0018-N
d) Ensure that all eTS data is treated and pro-
tected in accordance with the Privacy Act.
2) Northrop Grumman will explicitly describe
how the security standards of the SOO will be
met, or how the risk associated with these
standards will be mitigated if there is a reason
that the requirement cannot be met.
3) Northrop Grumman will be responsible for IT
security for all systems supporting the eTS
that are connected to a Federal Government
network or operated by Northrop Grumman
for the Federal Government, regardless of
physical location. This requirement will apply
to all IT resources or services in which North-
rop Grumman has physical or electronic ac-
cess to the Federal Government’s sensitive in-
formation that may be contained within the
eTS. The term “information technology (IT)”
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, transla-
tion, transformation, or reception of data or in-
formation. This includes both major applica-
tions 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 Govern-
ment-accessed major application being hosted
on another organization’s general support sys-
tem. Security guidelines pertaining to major
applications and general support systems as
described herein will apply in accordance with
Section 2.3.1 of NIST Special Publication
800-18. Northrop Grumman will provide ade-
quate 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 con-
tained therein. Northrop Grumman will be the
designated custodian for the eTS with respon-
sibilities in accordance with GSA security pol-
icy documented in CIO HB 2100.1A. The eTS
will comply with all pertinent requirements of
OMB Circular No. A-130, Appendix III, NIST
Special Publication 800-26, and other inden-
tured NIST guidance as applicable to major
SBU applications and general support sys-
tems. Incorporation of classified data into the
eTS, which is not a requirement of this SOO,
C-16
will require a new and comprehensive security
risk assessment; and
5) Northrop Grumman will complete the certifi-
cation and accreditation process to obtain Au-
thority 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 Accredi-
tation with Addendum 1. Northrop Grumman
will coordinate with the designated eTS In-
formation System Security Manager (ISSM) to
prepare and submit all documentation neces-
sary to support certification and accreditation
of the eTS by the GSA Designated Approving
Authority (GSA) GSA-DAA. Northrop
Grumman will complete the certification and
accreditation process for each location that is
identified as a potential eTS contingency loca-
tion in the Continuity of Operations and Con-
tingency Plan so that eTS is granted either In-
terim Authority to Operate (IATO) or ATO at
each contingency location.
6) Northrop Grumman will establish the follow-
ing 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
ii) Develop a security plan that addresses
the system rules; training; personnel
controls; incidence response capabil-
ity; 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 and
Contingency Plan whenever signify-
cant modifications are made (and at
least every 3 years).
b) For major applications (the eTS compo-
nents regardless of their physical loca-
tion):
i) Assign responsibility for security
ii) Develop an application security plan
that addresses application rules; spe-
cialized training; personnel security;
contingency planning; technical
 GSA Contract GS-33F-0018-N
controls; information sharing; and
public access controls
iii) Provide for a review of the security
controls and updates to the Security
Plan and Continuity of Operations and
Contingency Plan whenever signify-
cant modifications are made (and at
least every 3 years).
7.1 GENERAL SECURITY STANDARDS
7.1.2 Security Architecture: Key Features
The eTS will meet the following requirements for
the Security Architecture:
1) The principal goals of the security
architecture are to protect eTS from
compromise and provide appropriate security
mechanisms for the types of data processed
by the system. Taking a Defense-in-Depth
(DiD) approach, the network security design
focuses on expected threats and methods of
mitigation. This strategy results in a layered
approach to security so that the failure of one
security system is unlikely to compromise
network resources. The Release 3.2
architecture, which allows only web access to
the eTS application, combines a number of
functional and technical features that enhance
the security posture of eTS:
a. A layered technical security architecture
engineered for DiD, such that compromise
of a single security feature or layer simply
uncovers another layer of defense, rather
than compromising the system as a whole
b. Network security provided at multiple
locations and/or layers: Tier 1 (web), Tier
2 (application), and Tier 3 (database)
c. A technical architecture consistent with
Cisco Systems’ SAFE Blueprint and
standard practices for a DiD approach
accreditation authorities
d. Separation of security responsibilities
between network and systems staff:
network administrators administer packet
filtering and similar network-based
controls, while systems administrators
manage host-based controls, with the
ISSO/ISSM providing overall security
oversight
e. Implementation of packet filtering on
firewalls and routers to limit data transfer
to authorized services and
C-17
source/destination pairs. A Cisco PIX
firewall is implemented at the system’s
perimeter and the Cisco firewall feature
set is installed on all inter-tier routers to
provide isolation and access control
between the three tiers of the eTS
architecture
f. Implementation of standards-based Secure
Sockets Layer (SSL) whereby an SSL-
enabled Apache web server provides the
server portion of the SSL capability, while
the client portion is inherent in the user’s
web browser
g. PKI-based authentication and digital
signature for authentication, authorization
and non-repudiation. The DBsign product
from Gradkell is used to support these
functions. (As noted above, a non-PKI
based authentication and electronic
signature scheme may be implemented if
PKI credentials are not available)
h. 128-bit SSL encryption to ensure
confidentiality and integrity of all eTS
sessions
i. Intrusion detection for availability,
confidentiality, and integrity. Both
network-based and host-based intrusion
detection are implemented using the ISS
Real Secure product suite
j. Host-based security (e.g., Transmission
Control Protocol [TCP] wrappers, Secure
Shell [SSH], password authentication, and
secure configuration of access controls
and services)
k. Application-level access controls to
prevent unauthorized access to sensitive
eTS data based on user roles/permissions
and organization-based access restrictions.
These controls are designed to implement
a least privilege access control policy.
2) Security functionality is a vital capability of
eTS. The client connection passes from the
user’s client desktop through the client’s
LAN to the WAN (Internet). The WAN
routes the connection to the eTS Router.
3) The first layer of security is at the eTS
routers, which perform packet filtering at the
eTS perimeter. Behind the eTS routers are a
set of firewalls that filter all inbound and
 GSA Contract GS-33F-0018-N
outbound traffic based on a rule set that
defines the required hosts and protocols in the
DMZ that need access or connectivity to
external entities. Any packet not matching a
rule defined in the access control list is
denied, discarded, and logged.
4) A typical user first connects to the eTS Web
Portal where they can view the latest
information and can download any required
software for eTS (if authorized by the local
security policy). If the user’s browser does
not contain the necessary digital signing
client, the user will be prompted to download
the client or contact a system administrator to
install the client. The Web Portal also
provides links to the eTS application. The
link forwards the user to the eTS internal web
server, to which the client connects via an
SSL connection. During the establishment of
the SSL session, the server presents its
eAuthentication PKI server certificate to the
client. This allows the client to verify the
server’s identity before accepting the
connection. After validating the server’s
certificate, the user is able to connect to the
application via the Tier 1 web server using
SSL.
5) When the eTS application receives the
connection request, it sends an authentication
request to the DBsign client over the
established SSL connection. After receiving
the authentication response from the client,
the application forwards the response to the
DBsign application for validation. When
validated, the user is able to log in to the
application.
6) The eTS application software provides an
additional layer of access control. Each eTS
user must have an active account in the eTS
database, established by an individual
authorized to perform eTS administration
functions. As part of the account
establishment process, the user’s profile and
permissions are defined. Together, the profile
and the permissions define which modules of
the eTS software the individual is authorized
to execute, the individual’s role in the system
(traveler, approver, etc.), the individual’s
membership in groups and organizations, and
the scope of data to which the user has
access. Based on these, the application limits
the user’s access to the minimal set of data
C-18
and functions required to perform their job
responsibilities, and no more.
7) At various points during processing, a digital
signature may be needed (e.g., when an
authorizing official approves a travel
authorization or voucher). At that time, the
application initiates the digital signature
request to the client. The user signs the
document using the DBsign client and his/her
PKI certificate, and the DBsign server
transfers the resulting signature back to the
system for validation. Validated signatures
are stored with the document for non-
repudiation and integrity verification.
8) Security for other data exchange with
external systems (e.g., connections to the
GDSs) is achieved via point-to-point
Permanent Virtual Circuits (PVCs)
established over private frame relay networks
or via encrypted virtual private networks
(VPNs), to ensure the confidentiality of the
data transmitted.
9) In addition to the various network- and
application-level security controls described
above, security is enforced on individual
components in the eTS architecture through a
combination of operating system security
controls, supporting tools, and ongoing risk
management and mitigation. All systems are
configured in compliance with best industry
practice and Government (Defense
Information Systems Agency [DISA] and the
National Security Agency [NSA]) Security
Technical Implementation Guidelines
(STIGs) to provide a secure baseline for eTS
operations. Controls implemented and
configured in compliance with the STIGs and
comparable industry guidance include
features such as user account management,
password authentication, auditing, authorized
services, and file/directory permissions.
Supporting tools that supplement the basic
operating system controls include TCP
wrappers to control use of TCP services,
Tripwire to monitor changes to critical files
and directories, SSH to secure remote system
administrator connections to individual host
platforms, and various configuration
management tools that ensure that approved
configurations are properly implemented and
maintained. To ensure that the strong eTS
security posture is maintained over time,
 GSA Contract GS-33F-0018-N
Northrop Grumman constantly monitors
vendor, government (e.g., NIST ICAT,
DoDCERT, FedCIRC), and industry (e.g.,
CERT, Bugtraq, XForce) security advisories.
Working within the eTS configuration
management process, Northrop Grumman
will evaluate the applicability of these
advisories to the eTS environment and apply
those patches and configuration changes
needed to eliminate or mitigate the identified
vulnerabilities within the eTS environment.
7.2 ACCESS AND AUTHENTICATION
7.2.1 Requirements
The eTS will meet the following requirements for
access and authentication:
1) The eTS will provide access to data only on a
role-related “need to know” basis by default.
The eTS will restrict personnel access to those
with a need-to-know in strict accordance with
their roles and permissions (e.g., system ad-
ministrator, travel approvers, financial ana-
lyst). Agencies will determine who within
their organizations has the need to know spe-
cific information about the travelers and travel
within their agency and how that data will be
accessed based on the results of a sensitivity
assessment. They will assign user roles ac-
cordingly;
2) The eTS will interface with and authenticate
eTS user credentials via the eAuthentication
Initial Operating Capability (IOC) Gateway by
the time of eTS IOC task order completion.
Northrop Grumman will refresh technology as
necessary to integrate with and authenticate
eTS user credentials via the Full Operating
Capability (FOC) Gateway at the time of de-
ployment of the FOC Gateway (tentatively
scheduled for deployment by April 2004). A
default authentication level and associated re-
quirements for the eTS will be identified by
the GSA Contracting Officer at the time of the
contract award based on the results of a Gov-
ernment Risk Assessment. The Government
shall provide the Entrust or Entegrity Policy
Enforcement Point (PEP) software modules as
Government Furnished Equipment so that
Northrop Grumman can integrate its eTS solu-
tion with the eAuthentication IOC Gateway.
Northrop Grumman will administer any cre-
dentials they have issued for the duration of
any contract awarded as a result of this pro-
posal. If an agency chooses to procure creden-
C-19
tials from an eTS vendor, such credentials will
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 authentic-
cation 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 Sup-
plemental 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 creden-
tials from an eAuthentication PMO-approved
credential provider.
3) The eTS will provide digital signature capabil-
ity for the traveler, and reviewing and approv-
ing official that satisfies requirements in the
Federal Information Processing Standards
Publication 186, Digital Signature Standard,
issued by the NIST.
4) The eTS will display the following banner at
time of login on all eTS systems (both public
and private) operated by Northrop Grumman
prior to allowing anyone access to the system:
****************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 penal-
ties. Users will not access other users’ or system
files without proper authority. Absence of access
controls IS NOT authorization for access! Infor-
mation systems and equipment related to the
eTravel Service are intended for communication,
transmission, processing, and storage of U.S. Gov-
ernment information. These systems and equip-
ment are subject to monitoring by law enforce-
ment and authorized officials. Monitoring may
result in the acquisition, recording, and analysis of
all data being communicated, transmitted, proc-
essed, or stored in this system by law enforcement
and authorized officials. Use of this system consti-
tutes consent to such monitoring.
****************WARNING*************
5) The eTS will display the following banner at
time of login on all eTS systems that contain
Privacy Act information operated by Northrop
 GSA Contract GS-33F-0018-N
Grumman prior to allowing anyone access to
the system. 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 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 will include adequate safeguards to
restrict data access by department, agency,
subordinate organization, and user.
7.3 WEB BROWSER SECURITY
7.3.1 Requirements
The eTS will meet the following requirement for
web browser security:
1) The eTS will not employ mobile code within
its web content that may harbor malicious con-
tent and therefore be blocked by Federal fire-
walls, consequently denying functionality to
users. Mobile code technology, explicitly pro-
hibited in delivering eTS functionality, in-
cludes, 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.
7.4 DATA SECURITY
7.4.1 Requirements
The eTS will meet the following requirements for
data security:
1) The eTS will protect data (in all aspects enu-
merated in Section 5) at the “Medium” level
for SBU data in accordance with the security
standards cited herein.
2) All financial, privacy, and other sensitive data
transmitted by eTS via the Internet will em-
ploy a minimum of 128-bit encryption that has
been validated by the Cryptographic Module
Validation Program against NIST Federal In-
formation Processing Standards (FIPS) 140-2.
Refer to NIST Special Publication 800-21,
Guideline for Implementing Cryptography in
the Federal Government, and the NIST Cryp-
tographic Toolkit for detailed information.
(Agency requirements that exceed these stan-
C-20
dards will be handled on a case-by-case ba-
sis.).
3) The eTS will protect Federal travel-related
information against disruption, theft, exploita-
tion, and inadvertent disclosure.
7.5 PERSONNEL AND PHYSICAL SECURITY
7.5.1 Requirements
The eTS will meet the following requirements for
personnel and physical security:
1) Northrop Grumman will restrict personnel
access to the eTS to those with 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 will be secured as a Gen-
eral Support System in accordance with NIST
800-18 and the CIO HBA 2100.1A and will be
staffed by an appropriate mix of Level 5 staff
and Level 6 supervisory personnel. Northrop
Grumman will be responsible for the cost of
personnel background checks.
7.6 SUPPLEMENTAL SECURITY SERVICES
While authentication, authorization, and protection
levels for the eTS are intended to meet most Fed-
eral agencies’ requirements, agency-specific secu-
rity policies may require enhanced eTS security
features. Consequently, supplemental eTS security
services may be required.
7.6.1 Requirements
Northrop Grumman will meet the following man-
datory requirement for supplemental security ser-
vices:
1) Northorp Grumman has offered separately
priced supplemental security services to ad-
dress agency-specific security requirements
that augment eTS security standards without
price or functional impact to the basic eTS
services and transactions. These services will
include security risk analysis, enhanced secu-
rity for access and transmission, etc. Certain
agency-specific security requirements, how-
ever, (e.g., the handling of classified data) may
have to be implemented downstream as poten-
tial enhancements or changes to the eTS due
to overall cost and service impact.
7.7 GOVERNMENT ACCESS
7.7.1 REQUIREMENTS
The eTS will meet the following requirement for
Government access:
 GSA Contract GS-33F-0018-N
1) Northrop Grumman will afford the
Government and duly designated Government
support contractors’ access to Northrop
Grumman’s and subcontractors’ facilities,
installations, operations, documentation,
databases, and personnel used in performance
of the eTS contract. Access will be provided to
the extent required to carry out a program of
security inspection (to include vulnerability
testing and risk analysis), 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
IT systems operated on behalf of the GSA, and
in order to preserve evidence of computer
crime if committed.
7.8 SUBCONTRACTOR SECURITY
7.8.1 Requirements
The eTS will meet the following requirement for
subcontractor security:
1) Northrop Grumman will incorporate the
security requirements of the contract in all
subcontracts that support the eTS.
8.0 ELECTRONIC AND INFORMATION
TECHNOLOGY ACCESSIBILITY
The goal for the eTS is to provide equivalent
access to Electronic and Information Technology
(EIT) resources to all users regardless of
disabilities.
8.1 REQUIREMENTS
The eTS will meet the following requirements for
accessibility:
1) The eTS will meet applicable accessibility
standards of 36 CFR 1194 that can be met
with supplies, services, or assistive
technologies that are available in the
commercial marketplace.
9.0 DATA, INTEGRATION, AND
INFORMATION MANAGEMENT
9.1 BUSINESS DATA WAREHOUSE
9.1.1 Requirements
The eTS will meet the following requirements for
a business data warehouse:
1) Northrop Grumman will establish an eTS
business data warehouse to support aggregated
C-21
and consolidated Federal travel information
storage, management, reporting, and business
intelligence.
2) Northrop Grumman will develop all appropri-
ate information models and conduct the analy-
ses and studies required to define detailed data
warehouse requirements. This information will
be documented in Northrop Grumman’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. Northrop Grum-
man will be responsible for managing and pro-
tecting the data in accordance with this solici-
tation and resultant security provisions of the
contract. All eTS data will be protected under
the Privacy Act, and Northrop Grumman will
not use any eTS data for any purpose other
than that specified herein.
4) The business data warehouse will be capable
of importing and exporting Federal travel data
within the scope of the Government SOO that
may be provided from/to external data
sources, e.g., agency business systems or other
Federal travel partner and supplier systems.
5) In addition to the requirements of the continu-
ity of services clause included in this solicita-
tion and any resulting contract, Northrop
Grumman will meet the following data transi-
tion requirements for the eTS:
a) When Northrop Grumman 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) that will not be immediately
succeeded by another such task order from
that agency, Northrop Grumman will
prepare for the transition of that agency’s
data in accordance with Northrop
Grumman’s eTS Data Management Plan.
Upon expiration or termination of the task
order, Northrop Grumman will not permit
further transactions and will transfer all
applicable transactional eTS data for that
agency within operational databases to the
business
 GSA Contract GS-33F-0018-N

Table 3. Considerations for completing the VPAT.

Section 1194.21, Software
Applications and Operating
Systems
Section 1194.22, Web-Based
Internet Information and
Applications
Section 1194.23,
Telecommunications Products
Section 1194.24, Video and Multi-
media Products
Section 1194.25, Self-Contained,
Closed Products
Section 1194.26, Desktop and
Portable Computers
Section 1194.31, Functional
Performance Criteria
Section 1194.41, Information,
Documentation, and Support
Section 508 Requirements for The eTS
All criteria apply for elements of the eTS that are non-browser- based, including, but not limited to, plug-
ins, Java applets, downloaded content, and administrative and management software.
All criteria will apply for web-based elements of the eTS. Criteria (d) means that pages that refer to style
sheets will “degrade gracefully” if the user chooses to disable style sheet support, although eTS users are
required to use a modern browser that supports Cascading Style Sheets (CSS).
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) will also apply.
Criteria (c), (d), and (e) will apply for multimedia training products provided as part of the eTS.
If kiosks or other self-contained, closed products are proposed as part of the eTS, then all criteria listed in
Section 1194.25 will apply to those products.
Contract requirements for the eTS do not include desktop and portable computers, so these criteria are
not applicable.
All criteria in Section 1194.31 will 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
facilitation (as defined in Section 1194.5).
All criteria for end-user support documentation and services will apply.

data warehouse. This will be accom- to the Government. Upon confirmation

plished within 5 business days after expi- from the COR that the Government has
ration or termination of the task order. For received, reviewed, and found the
all transactions that have not been com- transferred data to be acceptable, Northrop
pleted by that time (in-process transac- Grumman will delete said data from its
tions), Northrop Grumman will ensure that transactional databases, business data
all information needed to resume the warehouse, and any backup/archival
transaction is provided. Once the systems or media in a manner that renders
transactional data has been transferred to the data irretrievable in whole or in part.
the business data warehouse, Northrop
b) When Northrop Grumman becomes aware
Grumman will electronically transfer
of the upcoming expiration or termination
and/or provide on durable electronic
of any ordering period under the master
media (e.g., CD-ROM) all traveler
contract that is not immediately succeeded
profiles, reportable configuration records,
by the execution of an optional ordering
travel records, associated files, and other
period, Northrop Grumman will prepare
data identified or referenced in the
for the transition of Government eTS data
Government SOO that are associated with
in accordance with Northrop Grumman’s
that agency and contained in Northrop
eTS Data Management Plan. Upon expira-
Grumman’s business data warehouse to
tion or termination of the ordering period,
the Government within 10 business days
Northrop Grumman will not permit further
after expiration or termination. Data will
transactions and will transfer all applica-
be provided in accordance with Northrop
ble transactional eTS data to the business
Grumman’s eTS Data Management Plan
data warehouse. This will be accom-
as well as the indexing requirements
plished within 10 business days after con-
described in this PBWS. All in-process
tract expiration or termination. For all
transactions will be specifically identified
transactions that have not been completed
to facilitate eTS transition and travel
by that time (in-process transactions),
management by the Government. The
Northrop Grumman will ensure that all in-
Contracting Officer’s Representative
formation needed to resume the trans-
(COR) will provide details regarding
action is provided. Once all transactional
transfer of data and/or delivery of media

C-22
 GSA Contract GS-33F-0018-N
data has been transferred to the business
data warehouse, Northrop Grumman will
electronically transfer and/or provide on
durable electronic media (e.g., CD-ROM)
all traveler profiles, reportable configura-
tion records, travel records, associated
files, and other data identified or refer-
enced in the SOO and contained within
Northrop Grumman’s business data ware-
house to the Government within 20 busi-
ness days after expiration or termination.
Data will be provided in accordance with
Northrop Grumman’s Data Management
Plan as well as the indexing requirements
described in this PBWS. All in-process
transactions will be specifically identified
by agency to facilitate eTS transition and
travel management by the Government.
The 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, re-viewed, and found the
transferred data to be acceptable, Northrop
Grumman will 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.
9.2 DATA EXCHANGE
9.2.1 Requirements
The eTS will meet the following requirements for
data exchange:
1) The eTS will support two-way exchange of
Federal travel data with agency business sys-
tems in both near-real-time and batch modes
as described within this section. The eTS will
be capable of two-way transactional data ex-
change with external systems to support busi-
ness requirements such as funds availability
checks and payment actions.
2) Data exchange will support EDI, UDF, and
XML formats, as well as other industry stan-
dard methods, and the capability to translate
between these formats.
3) The eTS will provide an Enterprise Applica-
tion Integration (EAI) capability and infra-
structure to support near-real-time and batch
integration with the business systems of Fed-
eral agencies, as well as with commercial sys-
tems that may be required.
C-23
4) The eTS EAI platform will perform all neces-
sary format translations for inbound and out-
bound data exchange. Costs associated with
establishing, operating, and maintaining the
eTS EAI capability will be included in and
spread across the Authorization and Voucher
Services fees (CLINs 0003, 0021, 0041, and
0061).
5) Northrop Grumman will establish a standard
data input for the eTS. The standard data input
will be capable of accepting transactional data
(e.g., accounting data, charge card postings,
funds availability checking, and funds certifi-
cation) and “static” data (e.g., traveler profiles,
and lines of accounting) from agency business
systems and/or other external commercial data
sources in a format defined by Northrop
Grumman in the eTS Data Exchange Specifi-
cation.
6) Northrop Grumman will establish a standard
data output for the eTS with the following ca-
pabilities and characteristics:
a) The eTS will capture and make available
in its standard data output the data ele-
ments identified in Chapter 301, Appendix
C, of the FTR as well as additional finan-
cial and accounting data elements speci-
fied herein.
b) The standard data output will draw upon
the entire dictionary of data elements that
are exportable from the eTS and the busi-
ness data warehouse for exchange be-
tween its EAI platform and the agencies’
business systems. Data elements include
traveler identification, commercial
transportation information, travel expense
information, and accounting and certifi-
cation data. These data elements vary in
form and format and are integral to both
travel and accounting transactions. North-
rop Grumman will define the data schema
and format(s) for the standard data output.
Data formats will 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 will interface include financial,
payroll, and human resources systems.
c) Northrop Grumman will provide the
capability to modify or expand the data
 GSA Contract GS-33F-0018-N
elements contained within the standard
data output over the life of the contract.
d) The eTS standard data output will contain
the data necessary to support the
functionalities listed below:
i) Funds availability checking
ii) Credits resulting from cancellation,
unused tickets, and other refunds
iii) Payment, tax reporting, and
liquidation of travel advances
iv) Reporting amount due to or owed by
the traveler after final voucher
submittal and repayment of funds to
offset traveler indebtedness
v) Maintaining standard data elements
specified in the FTR to generate
standard and ad hoc reports
vi) Transactional interfaces between the
eTS and agencies’ business systems,
including the generation of accounting
transactions as needed, update of
funds control and the standard general
ledger, and generation of disburse-
ment actions by EFT or other means
vii) GSA reports that require the data
elements identified in Attachment 7.
7) Northrop Grumman will make the data ele-
ments with sequence numbers 1 through 279
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:
a) Standard data elements related to manda-
tory requirements for the eTS will be in-
cluded in the standard data input or output.
(b) Only standard data elements related to
objectives proposed in this eTS solution
will be included in the standard data input
or output.
9.3 INTEGRATION SUPPORT
Northrop Grumman will not be responsible under
this contract to establish mappings to specific
agency legacy systems and their data elements.
External system owners will be responsible for
developing the detailed data mapping between
their data formats and the eTS standardized data
input/output and for implementing their side of the
C-24
interface using the eTS application integration
platform, services, and data provided.
9.3.1 Requirements
Northrop Grumman will meet the following
requirements for integration support:
1) Northrop Grumman will develop and deliver a
specification that defines requirements for data
exchange with the eTS, including standard
data input and standard data output. The speci-
fication will include all information necessary
for Federal agencies to establish Integration
Agreements and interfaces with the eTS using
the eTS EAI platform. The specification will
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.
2) Northrop Grumman will establish and main-
tain the EAI platform and infrastructure, in-
cluding flexible scheduling, transport, routing,
and format translation services (inbound and
outbound), and provide licenses for Federal
agency access and use (if required).
3) Northrop Grumman will coordinate with
Federal and GSA-authorized commercial
external system owners to facilitate the
establishment of Integration Agreements and
interfaces that facilitate data exchange,
mapping, translation, transport, and scheduling
requirements to support Federal travel
management functions within the scope of the
eTS.
4) Northrop Grumman will execute data
exchange and translation between the eTS and
external systems in accordance with
established Integration Agreements.
9.4 QUERIES AND REPORTS
9.4.1 Requirements
The eTS will meet the following requirements for
queries and reports:
1) The eTS will provide the capability to
generate all reports required by the FTR
Section 300-70 and Chapter 304 for travel
management and agency reporting.
2) The eTS will make travel data available to the
GSA for oversight in accordance with FTR
300-70, Agency Reporting Requirements, and
any other specific information GSA may
require for a reporting period.
 GSA Contract GS-33F-0018-N
3) The eTS will provide query and reporting
capability through the web browser and be
capable of executing queries on all travel data
elements within the eTS. It will provide for ad
hoc and standing/stored queries. It will also
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 traveler levels
according to user roles and permissions. The
eTS will 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. It will 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 will support the creation, formatting,
generation, printing, storage, and electronic
transmittal of custom reports to meet agency
requirements and make both standard and
agency-defined custom reports available
through the web browser.
5) The eTS will maintain transaction data and
standard data elements identified in FTR
Chapter 301, Appendix C, to generate
standard and ad hoc reports and capture
activity in future time frames.
6) The eTS will track and report travel obligation
and liquidation information based on Office of
Management and Budget (OMB) and GSA
defined travel purposes.
7) The eTS will provide the capability to run on-
demand analysis reports and download data to
spreadsheets or other analytical tools.
8) The eTS will provide the specific GSA Travel
Management Reports defined in Attachment 8.
9.4.3 Custom Report Development
9.4.3.1 Requirements
Northrop Grumman will provide separately priced
services for the development of custom reports to
support agency-specific travel management
reporting requirements.
9.5 BUSINESS INTELLIGENCE
9.5.1 Requirements
Northrop Grumman will meet the following
requirement for business intelligence:
C-25
1) Northrop Grumman will establish a robust
business intelligence capability for the eTS to
enable and drive effective Federal travel
policy, management, and procurement.
9.6 RECORDS RETENTION AND ARCHIVING
9.6.1 Requirements
The eTS will meet the following requirements for
records retention and archiving:
1) The eTS will comply with records retention
requirements established by the National
Archives and Records Act and IRS regulations
as applicable.
2) The eTS will 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 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 will apply.
3) The eTS will be Government fiscal year
compliant (October 1 through the following
September 30) for dating and retention of
records.
4) Northrop Grumman will develop and
implement a records retention and archiving
scheme to meet these requirements. The
records retention and archiving scheme will be
documented in Northrop Grumman’s eTS
Data Management Plan.
10.0 Other Service Requirements
In addition to the system functional requirements
in the previous section, Northrop Grumman will
deliver three categories of service:
implementation, customer support, and training.
10.1 Standard Implementation Services
10.1.1 Requirements
Northrop Grumman will meet the following
requirements for standard implementation
services:
1) Northrop Grumman will provide
implementation support services required to
establish agency-standard configuration and
operational readiness in coordination with
each agency placing a task order for eTS
Reservation and Fulfillment Services and/or
eTS Authorization and Voucher Services
under this contract.
 GSA Contract GS-33F-0018-N
2) Northrop Grumman will identify and provide
an implementation team for each
adopting/ordering agency and provide initial
and ongoing account management for each
agency.
3) Northrop Grumman will 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 process,
and key implementation and integration issues
that the agency may face.
4) Northrop Grumman will load all agency-
specific data (e.g., traveler profiles, funding
citations) provided by the agency that may be
imported by automated means. Northrop
Grumman will specify data formats for the
upload of agency data.
5) Northrop Grumman will establish agency
specific billing parameters and procedures.
6) Northrop Grumman will identify online, role-
based training and training curricula available
to the agency for each of the agency’s user
roles. Instructor-led courses will accommodate
at least 25 students per class, will be scheduled
at the ordering agency’s convenience, and will
not be conducted more than 30 days prior to
implementation 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. Northrop
Grumman will for provide computers and
Internet access for classes conducted at
contractor-specified facilities.
7) Northrop Grumman will 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 will 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
C-26
eTS, providing training opportunities for
at least 150 users in a minimum of 6
classes. Agencies will 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.
iii) Provide at least 480 work-hours of
dedicated implementation support with up
to three implementation con-sultants 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 each user role identified in the
eTS, providing training opportunities for
at least 450 users in a minimum of 18
classes. Agencies will have the option of
selecting the specific user role classes to
be repeated if the number of classes
offered exceeds three times the number of
eTS user roles employed by the agency.
iii) Provide at least 960 work-hours of
dedicated implementation support with up
to 6 implementation consult-ants in a
period not to exceed 90 calendar days
from task order award.
c) Standard Implementation Service Level C:
i) Load up to 5,000 user profiles.
ii) Conduct at least 6 instructor-led training
classes for each user role identified in the
eTS, providing training opportunities for
at least 900 users in a minimum of 36
classes. Agencies will have the option of
selecting the specific user role classes to
be repeated if the number of classes
offered exceeds six times the number of
eTS user roles employed by the agency.
iii) Provide at least 1,440 work-hours of
dedicated implementation support with up
to nine implementation consultants in a
period not to exceed 120 calendar days
from task order award.
d) Large scale implementations:
i) Standard implementation services for up to
120,000 users at large agencies that may
wish to procure agency-wide
implementation on single task order.
8) Northrop Grumman will 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 internal
business systems. Northrop Grumman will
 GSA Contract GS-33F-0018-N
support the establishment and testing of
agency interfaces to the eTS EAI platform.
9) Following the dedicated implementation
support period described above, Northrop
Grumman will provide continuing priority
implementation support during the subsequent
2 months of an agency’s eTS roll-out. This
will consist of technical and functional support
for a weekly conference call between
Northrop Grumman, the eTravel PMO, and
the agency to discuss and mitigate roll-out
issues. Northrop Grumman will also support a
monthly conference call with agency and
eTravel PMO through the agency’s sixth
month of deployment.
10) Northrop Grumman will document the agency
standard configuration (e.g., standard process
and work flows, business rules, audits)
established for the eTS during implementation
activities at that agency in an eTS
Implementation Report.
11.0 Customer Support (C.6.9)
11.1 Requirements (C.6.9.1)
Northrop Grumman will meet the following man-
datory requirements for customer support:
1) Northrop Grumman will provide basic cus-
tomer support (e.g., 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 Fri-
day (excluding Federal holidays). Customer
support will meet all requirements specified
herein for functional and technical support, the
price for which is included in the applicable
transaction fees. Northrop Grumman will
expand customer support as the eTS is imple-
mented by Government agencies that are
located OCONUS, in U.S. territories, and in
foreign countries.
2) Basic customer support will consist of on-line
and phone-in Help Desk support with single
“focal points” that direct users to the appropri-
ate type of support (e.g., technical, software,
travel arrangements) 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 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
will accommodate collect calls for overseas
C-27
customers. Northrop Grumman will route
online and phone-in support requests quickly
and efficiently to the appropriate eTS func-
tional, technical, and travel arrangement
assistance.
3) Northrop Grumman will provide travel ar-
rangement support for travelers and travel ar-
rangers and system administration support to
travel administrators and travel coordinators.
Northrop Grumman will provide toll free,
24/7/365 emergency travel arrangement sup-
port via telephone with voice and facsimile
service. Collect calls will be accepted to sup-
port international travelers.
4) Technical support will consist of user role
specific technical support for all user roles
identified. Technical support provided will
help users quickly determine if technical prob-
lems encountered are due to eTS or local
agency network/IT issues. (Northrop Grum-
man will not be responsible for resolving local
agency network/IT issues.) Northrop Grum-
man will also provide system administration
support to travel administrators and travel
coordinators.
5) The eTS will support the submittal of online
and phone-in trouble tickets and provide trou-
ble ticket tracking identifiers that enable the
user to track problem resolution online or by
phone.
6) Northrop Grumman will offer multi-tiered
customer support options with increasing lev-
els of customer service for agencies’ selection
appropriate to their specific needs and in ac-
cordance with task orders that they establish.
Northrop Grumman will 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 tech-
nical support, and the price for which is
included in the applicable transaction fees
b) Separately priced on-site reservation and
fulfillment services
c) Separately priced customer support ser-
vices above and beyond those provided
under subparagraph a) above. Supplemen-
tal customer support services may be per-
 GSA Contract GS-33F-0018-N
formed remotely or on-site at Federal
agencies. This tier of customer support is
not intended to include the on-site
reservation and 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).
12.0 Training
12.1 Requirements
Northrop Grumman will meet the following
requirements for training:
1) Northrop Grumman will provide eTS training
in a variety of forms (e.g., computer-based
tutorials via the eTravel portal, instructor-led
classes, and train-the-trainer curriculum) for
each user role.
2) Northrop Grumman will provide online
computer-based training for all eTS user roles
available via the eTravel portal and presented
via a compatible web browser.
3) Northrop Grumman will develop, conduct, and
provide instructor-led and train-the-trainer
course curriculum that may be used by North-
rop Grumman or the Government for all eTS
user roles. Northrop Grumman will
incorporate hands-on eTS interaction within
instructor-led classes.
4) Northrop Grumman will provide eTS training
environments for all user roles that provide a
realistic experience.
5) Northrop Grumman will establish training
scenarios that include walkthroughs of travel
and administration functions and actions that
Federal employees will encounter within the
eTS applicable to the user role(s) being
trained.
6) Northrop Grumman will provide training on
eTS business intelligence, business data ware-
house, and reporting capabilities for federal
managers.
7) Northrop Grumman will offer separately
priced supplemental training services as
specified below:
a) Northrop Grumman will offer supplemen-
tal instructor-led training for all user roles
at CONUS and OCONUS locations.
C-28
b) Supplemental training classes will ac-
commodate at least 25 students per class
and may be conducted at Government-
specified or contractor-specified facilities,
depending upon the preference of the or-
dering agency. Northrop Grumman will be
responsible for providing computers and
Internet access for classes conducted at
contractor-specified facilities.
c) Unless otherwise specified by the ordering
agency, supplemental training will not be
conducted more than 30 days prior to
implementation and use of eTS by the
users trained.
13.0 Schedule Requirements
Northrop Grumman will activate the IOC system
when the contract is awarded. GSA testing will
begin at that time. Northrop Grumman will con-
duct an IOC implementation at the first ordering
agency, which will consist of 400 users and 800
voucher transactions, of which at least 300 will be
ticketed transactions. FOC will be when the sys-
tem has successfully passed testing, and ATO is
granted. The schedule requirements for IOC and
FOC, and the business data warehouse are in Sec-
tion 13.1
Section 13.2 contains the schedule for implemen-
tation at the agencies.
Section 13.3 contains the schedule for adding
unmet objectives to the IOC system.
13.1 IOC, FOC, and Data Warehouse Schedule
Northrop Grumman will establish eTS IOC at the
first ordering agency during the initial task order
placed under the contract. Northrop Grumman will
be prepared to begin the initial task order within
30 calendar days after contract award and will es-
tablish eTS IOC at the ordering agency no later
than 105 calendar days from the date of task order
award.
Northrop Grumman will establish eTS FOC on or
before December 31, 2003. The Contracting Offi-
cer or his designated representative will notify
Northrop Grumman and Federal agencies within 5
business days once the eTS is determined by the
Government to have achieved FOC and is ap-
proved for task order placement. Full operational
capability is defined in the following:
1) The eTS meeting all requirements specified
within Northrop Grumman’s PBWS
 GSA Contract GS-33F-0018-N

2) The eTS having passed all Independent
Verification and Validation (IV&V) tests,
including remediation and retest as required
3) Northrop Grumman having achieved ATO for
the eTS from the GSA DAA
4) The eTS being available for Governmentwide
adoption.
The Government will be prepared to begin IV&V
testing immediately upon contract award. All
IV&V testing will be conducted by a single Gov-
ernment designee. The Government will support
concurrent IV&V testing in the event that multiple
contracts are awarded. Northrop Grumman may
request that the Government conduct IV&V test-
ing in a phased approach provided the phases cor-
respond with logical functional or technical eTS
“modules.” Northrop Grumman will notify the
COR for scheduling of IV&V testing, which will
be conducted remotely or at Northrop Grumman’s
facility, at the discretion of the Government.
If ordered, Northrop Grumman will establish its
business data warehouse and related capabilities
within 90 days after the date of task order award.
13.2 AGENCY IMPLEMENTATION SCHEDULE
Use of the eTS by Federal Executive Branch
civilian agencies is anticipated to be directed by
policy and regulation. At full adoption and
utilization by civilian agencies, the volume of
travel transactions for the eTS is expected to be
3.5 million vouchered transactions annually.
Current data suggests that 75% of voucher
transactions are for TDY travel while 25% are for
local travel. Of TDY travel vouchers, an estimated
60% require either traditional or online travel
arrangement services, while 40% do not.
Furthermore, it is estimated that 95% of TDY
travel requiring travel arrangement services
include air and/or rail ticketing. The remaining 5%
require travel arrangement services for lodging
and/or car rental only.
Adoption targets for the eTS in terms of online
booking engine reservations and online vouchers
are summarized in Table 4. The numbers are
derived from travel charge card and TMC contract
data and represent Government estimates of
Federal travel transactions. A travel charge card
performance summary and historical travel spend
information is available on the GSA SmartPay®
web site at http://www.gsa.gov/Portal/content/
pubs_content.jsp?contentOID=119196&contentTy
pe=1008. Links to applicable transaction data for
TMC services under GSA’s master contracts are
available on the web at http://apps.fss.gsa.gov/
transtrav/taskorders/taskOrders.cfm. These
numbers represent anticipated transaction targets
that Northrop Grumman will be expected to
handle, but they do not represent any guarantee of
business or transaction volume.
13.3 SCHEDULE FOR UNMET OBJECTIVES
The IOC version of the system will meet all
requirements and some objective requirements.
Northrop Grumman will provide technical
refreshment of the service and system in
accordance with commercial best practice.
Table 5 shows which objectives will be included
in the IOC version of GovTrip.

Table 4. Adoption Targets for Online Booking Engine Reservations and Vouchers.
Online Booking
No. Estimated eTS Online Engine
of Voucher Vouchers Reservations
eTS Milestone Fiscal Year Time Frame Agencies Transactions Target Target *
IOC** FY03 - 04 Jul 2003 – Nov 2003 1 800 100% 40%***
1 FY04 Dec 2003 – Sep 2004 7 751,000 50% 60%***
2 FY05 Oct 2004 – Sep 2005 12 1,395,000 65% 60%
3 FY06 Oct 2005 – Sep 2006 24 3,330,000 80% 60%
4 FY07 Oct 2006 – Sep 2007 All 3,500,000 95% 65%
5 FY08 out Oct 2007 and beyond All 3,500,000 100% 70%
• Online booking engine reservation targets apply to number of TDY vouchers requiring reservations and fulfillment.
** IOC adoption targets apply to each contract awardees. Remaining adoption targets represent total civilian Executive Branch travel
estimates.
*** Online booking engine transaction targets for FY03 and FY04 include FedTripTM and eTS booking engine transactions. Online booking
engine targets for FY05 and beyond represent eTS booking engine targets only because the FedTripTM contract expires in FY04.

C-29
 GSA Contract GS-33F-0018-N

Table 5. Method for Providing Requirements. We are proposing to meet all of the requirements and many of the objectives by
IOC. (Legend ●Complete ◐Partial)
ALL REQUIREMENTS IOC
●
IOC
C.6.1 Basic Capabilities and Characteristics
1) Provide a common, streamlined travel management service available Governmentwide that automates and fully integrates Federal travel management ◐
functions
2) Provide a common, consolidated travel process at a Governmentwide level with configurability at the department, agency, and subordinate organization ●
levels within the limits allowed by the applicable travel regulations
3) Provide a consistent, web-based, self-service environment with an intuitive graphical user interface and sufficient information to guide users through logical,
sequential processes and collect all necessary information
●
4) Provide web-based administration of travel policy with configurable business rules (e.g., Governmentwide, agency level, executive employee policy, staff ◐
employee policy, etc.) for all applicable functionalities
5) Utilize automated routing, workflow, messaging, and notifications ●
6) Provide comment fields and local fields within all functionalities to support organization- and agency-specific business processes and audit requirements ●
7) Support the use of personal charge/credit cards where authorized ●
8) Take advantage of and use appropriate commercial standards wherever possible to streamline the acquisition, enhance interoperability, and reduce costs ●
provided that all requirements are met ed
9) Support establishment of Federal eTravel standards, incorporating appropriate best practices ●
10) Provide support for wireless and personal digital assistant (PDA) devices. ◐
C.6.3.1 User Roles, Use Cases, and Account Access
1) Address all business travel processes outlined in the eTravel Business Process Flow Diagram (Attachment 1) and Notional eTS Operational Architecture
(Attachment 2)
●
2) Provide the ability to add user accounts and traveler profiles limited only by the concurrent user requirement ●
3) Describe use cases in simple text to facilitate communication among Government travel subject matter experts ●
4) Propose additional or alternative user roles and use cases that provide the most effective standardized eTS model and functionality across Federal agencies ●
C.6.3.2 eTravel Portal
1) Provide a single sign-on to access all eTS functionality (utilizing the eAuthentication Gateway as subsequently described) ●
2) Deliver functionality proactively, presenting it to the user as needed and limiting the need to “drill down” to access eTS capabilities ●
3) Establish links to Governmentwide, GSA, and agency-specific, travel-related web sites, documents, and resources. Be capable of linking to services and data ●
from other Government portals and web-based systems
4) Provide the ability for non-Government travelers to register on the system and route their registration to the appropriate Government representative for
account approval to support invitational travel.
●
C.6.3.3 Traveler Profiles
1) Traveler profile data within the eTS should be used to pre-populate applicable data to the maximum extent possible within travel actions of all types (e.g., ●
travel authorizations, reservation records, etc.)
2) Traveler profile should provide for entry and retention of the traveler’s default transportation and accommodation requirements and preferences and travel
program affiliations.
●
C.6.3.4 Travel Planning and Authorization
1) Provide the capability to authorize travel for multiple travelers on the same authorization ◐
2) Allow for processing an annual unlimited open travel authorization without recording an estimated obligation amount for each trip prior to travel ◐
3) Support the identification and documentation of all modes of transportation (including rail, bus, ship) authorized by the FTR and other applicable travel ◐
regulations
4) Identify clearly trip legs or segments in the travel plan, itinerary, and on-screen, and identify “no cost” trip segments (i.e., where personal leave is taken during ◐
TDY travel)
5) Support the capability to associate eTS travel authorization with the activation and deactivation of Government Contractor-issued Individually Billed Travel
Charge Cards.
●

C-30
 GSA Contract GS-33F-0018-N

Table 5. Method for Providing Requirements and Objectives (continued). We are proposing to meet all of the requirements,
and many of the objectives by IOC. (Legend ●Complete ◐Partial)
ALL REQUIREMENTS IOC
●
IOC
C.6.3.5 Reservations
1) Propose expedited agency TMC accommodation schemes to facilitate adoption of the eTS and speed eTS transaction volume growth ●
2) Provide non-self service reservation capabilities that meet the requirements for Travel Agent Services/Travel Management Center
Services for reservations specified in the GSA Travel Services Solutions contract
●
3) Provide access to as many domestic and international Government rate and non-Government rate lodging sources as possible ●
4) Take advantage of promotional and spot discount lodging rates to the maximum extent possible ◐
5) Support the passing of pertinent reservation data from the TMCs FedTrip and the eTS online booking engine to associated travel actions
(e.g. travel authorizations, vouchers) within the eTS.
◐
C.6.3.6 eTS Online Booking Engine
1) 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 Government, including the capability to display fare comparisons from multiple fare sources (i.e., City
●
Pair fares vs. other fares), alternate airports
2) Be capable of reserving airline travel accommodations for airlines not listed in GDSs in a real-time 24/7/365 environment ◐
3) Allow TMC reporting systems and TMC created PNRs to be retrieved and/or viewed through the eTS online booking engine. It should
work with any TMC mid-office system(s) to meet file finishing requirements
●
4) Provide the ability to change the traveler’s itinerary and reservations online after ticket issuance ●
5) Encode and decode airline and city/airport codes for the traveler ●
6) Provide graphical seat maps and the capability to reserve seat assignments where commercially available ●
7) Provide the ability to make self service international air travel reservations that comply with applicable regulations ●
8) Support the creation, storage, and shared use of standard individual and shared trip templates
9) Provide appropriate and accurate Government rates for domestic rail travel and reservation of rail travel accommodations in a real-time
24/7/365 environment; provide domestic rail schedules with published and negotiated fares, seats, and destination information.
10) Provide the ability to automatically identify and communicate exceptions to travel policy to multiple recipients (e.g., traveler, approvers) ●
11) Provide the traveler or travel arranger with access to the traveler’s previous trip itineraries ●
12) Be able to reserve ship and bus transportation if commercially available ◐
13) Be able to book shuttle services to and from airports ◐
14) Be able to designate frequent or loyal traveler program account number(s) in reservations. ●
C.6.3.7 Fulfillment
1) Propose expedited agency TMC incorporation schemes to speed agency adoption of the eTS and eTS transaction volume growth ●
2) Provide fulfillment capabilities that meet requirements for Travel Agent Services/Travel Management Center Services for reservations ●
specified in the GSA Travel Services Solutions contract
C.6.3.9 Travel Vouchers
1) Provide for electronic notification to travelers of payments made by disbursing offices or for disallowance of a claim for an expense, ◐
allowing for agency flexibility in defining such message content
2) Provide the capability to enter the “Direct Billed” amount for costs such as OPAC billings by the Department of State for employees
stationed overseas, 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) Be able to accept and post Government travel charge card transactions to a Federal traveler’s eTS account to support voucher
processing, allowing travelers to assign posted travel card charges to the appropriate voucher(s)
●
4) Generate, retain, and attach cost estimates and comparisons to the appropriate travel voucher to support constructive cost travel claims ●
5) Provide for matching of centrally issued tickets with the appropriate travel authorizations and/or vouchers. ●
C.6.3.10 Local Travel Vouchers
1) Provide for electronic notification to travelers of payments made by disbursing offices or for disallowance of a claim for an expense, ◐
allowing for agency flexibility in defining such message content
2) Provide the capability to accept and post Government travel charge card transactions to a traveler’s eTS account to support voucher ●
processing and allow travelers to assign travel card charges to the appropriate voucher(s).

C-31
 GSA Contract GS-33F-0018-N

Table 5. Method for Providing Requirements and Objectives (continued). We are proposing to meet all of the requirements,
and many of the objectives by IOC. (Legend ●Complete ◐Partial)
ALL REQUIREMENTS IOC
●
IOC
C.6.3.11 Travel Receipts
1) Support submittal and storage of electronic images of receipts that comply with applicable Internal Revenue Service (IRS) electronic receipt
requirements
●
2) Include the capability to submit electronic images of Federal travelers’ expense receipts by upload via browser-based functionality and by
facsimile for electronic attachment to the appropriate travel voucher. Receipt images should be stored, indexed to, or associated with the
●
applicable voucher
3) Support agency-specific policy regarding receipt retention and provide guidance about that policy to the traveler when preparing a voucher. ●
C.6.3.12 Non-Federally Sponsored Travel
1) Support special authorizations and the capture of ethics documentation that may be required by Federal agencies ●
C.6.3.14 Accounting Capabilities
1) Provide the capability to accept and post Government travel charge card transactions to a Federal traveler’s eTS account to support
voucher processing
●
2) Be Government fiscal year compliant (October 1 through the following September 30) for dating, indexing, and tracking of accounting ◐
functions
3) 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 currency fluctuations.
●
C.6.3.15 Routing, Workflow, Notifications, and System Messages
1) 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 should require the documentation
◐
of the reason for rejection in text and/or configurable code
2) 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 contain hyperlinks to permit the user to access the related eTS travel action directly from the
◐
message (with appropriate user authentication required)
3) Support cross-organizational travel and provide cross-agency routing and workflow, leveraging existing (compatible) agency E-Mail systems
and the eTS application integration capabilities to the greatest extent possible
●
4) Support conditional routing and notifications as configured by agencies and subordinate organizations ◐
5) Provide the capability to post messages within specific travel action functionalities and display Governmentwide, agency-specific, and
organization-specific messages to users regarding general information
●
6) Provide various eTS notifications and messages. ●
C.6.3.16 System Administration
1) Provide the capability to add or modify “HELP” files, “HELP” screens, and other “HELP” facilities to meet specific requirements of Federal
agencies
●
2) Provide the ability to add/modify/delete agency- and organization-specific data fields related to particular travel functionalities within the eTS. ●
C.6.4 Technology Capabilities and Characteristics
1) Provide a solution with minimum bandwidth and latency requirements for optimal web-based performance and response times across
Federal agencies and networks
●
2) Describe strategy and capability to scale from 5,000 to 10,000 concurrent eTS users ●
3) Application integration capabilities should include flexible transport, routing, scheduling, and data translation services based on ●
message/integration brokering and XML Web Services architectures
4) The application server component should be based on J2EE or .Net architectures ●
5) The portal and web server should be deployed on a UNIX or Windows 2000 or later operating system platform ●
6) The operational database platform(s) 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 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 version
releases, upgrades, or other changes
●
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
●
9) Support handling and viewing of electronic receipt images in TIFF, PDF, other common image formats, and the IRS-compliant electronic
receipt image format used if that capability is supported (see Section 5.11).
●

C-32
 GSA Contract GS-33F-0018-N

Table 5. Method for Providing Requirements and Objectives (continued). We are proposing to meet all of the
requirements, and many of the objectives by IOC. (Legend ●Complete ◐Partial)
ALL REQUIREMENTS IOC
●
IOC
C.6.5.1 General Security Standards
1) Agency-specific and possibly data-specific configurable security is 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 Access and Authentication
1) Prior to availability of the final eAuthentication Gateway, 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 Password authentication level if the interim eAuthentication Gateway and Federal credential providers are not used.
2) Display contact information for the eTS ISSO (to be provided at the time of contract award) in the initial portal screen and in all help screens ●
3) Contain 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.
C.6.5.3 Web Browser Security
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.
C.6.5.5 Personnel and Physical Security
1) Accommodate agency-specific personnel security requirements, including but not limited to ensuring that all contractor personnel meet applicable
agency security and/or clearance requirements. The Contractor may propose staff with other security clearances as long as their clearances meet the
●
levels stated herein
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 FISMA, and NIST requirements, with a specific emphasis on rules of behavior.
●
C.6.6 Electronic and Information Technology Accessibility
1) Section 508 objectives in Section 9.0 ◐
2) Be prepared to provide improved or additional accessibility through the continued application of Web Content Accessibility Guidelines, evolving ●
commercial assistive technologies, etc.
C.6.7.1 Business Data Warehouse
1) Capture and contain all travel transaction data elements from eTS systems associated with or required to fulfill the traveler profile (see Section 5.3), *Will be
travel receipt images if included in eTS capabilities (see Section 5.11), query and reporting (see Section 9.4), business intelligence (see Section 9.5), met when
and data exchange requirements (see Section 9.2). Travel data should be indexed in accordance with the requirements of Sections 5.11 (if applicable), Business
9.4, and 9.6. Data captured and stored should also include, but may not be limited to, detailed travel itinerary and voucher information such as: Data
a) Purpose of travel
b) Exception codes and justifications for not using and/or preferred travel suppliers Warehouse
c) Flight information (carrier, fare basis codes, class of service, etc.); and Travel cost information for transportation, lodging, and rental cars, CLIN is
with taxes and fees paid and tax and fee types separately identified. awarded.
d) Travel cost information for transportation, lodging, and rental cars, with taxes and fees paid and tax and fee types separately identified
2) Be physically and logically separated from operational databases used in support of the eTS. ●

C-33
 GSA Contract GS-33F-0018-N

Table 5. Method for Providing Requirements and Objectives (continued). We are proposing to meet all of the
requirements, and many of the objectives by IOC. (Legend ●Complete ◐Partial)
ALL REQUIREMENTS IOC
●
IOC
C.6.7.2 Data Exchange
1) Be able to accommodate legacy systems based on older technologies as well as the latest emerging data standards (e.g., XML Schema,
Web Services involving SOAP messages for remote procedure calls, message brokers)
●
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 information usability over time.
●
3) Comply with Federal XML guidelines as described in the Draft Federal XML Developer’s Guide for XML Schema and XML instance
documents created and transmitted
●
4) Support the capability to associate eTS travel authorization to activation and deactivation of Government Contractor-issued Individually Billed
Travel Charge Cards (see Section 5.4).
●
5) Standard data elements for eTS data exchange adhere to the names and characteristics identified in Attachment 14B with the following
considerations:
●
a) Data element naming 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
b) Standard data element names provided in Attachment 14B are used unless alternate names conforming to ISO 11179 are proposed.
These data element names are based on 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
c) Specific data elements to support invitational travel orders were not captured in the list provided as Attachment 14B. 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 orders were not captured in the list provided as Attachment 14A. 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) are important to Federal travel management, although not necessarily required for exchange with
●
agency business systems. These data elements are incorporated as they relate to the proposed objectives included in their respective eTS
solution.
C.6.7.4 Queries and Reports
1) Provide robust query and analysis tools, such as OLAP ●
2) In addition to the required reports specified above, provide the following standard reports:
e) Total spend for travel and transportation of employees and invitational travelers
●
f) Average costs and duration of trips
g) Amount of official travel by purpose(s)
h) All instances in which the agency authorized/approved the use of first-class transportation accommodations as well as utilization of
first class travel and accommodations
i) 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.5 Business Intelligence
1) Directly support the business analysis and management functions listed below at the Governmentwide, department, agency, and subordinate
organization levels (as applicable):
●
j) Budget management
k) Real-time spend analysis
l) Preferred supplier utilization and spend
m) Federal travel trend analysis
n) Regulatory compliance and regulatory exception analysis and reporting
o) eTS Contractor performance

2) Business intelligence functionalities should be accessible via the eTravel portal ●

C.6.7.6 Records Retention and Archiving
1) Provide online access to detailed transaction information for a minimum period of 36 months, and permit access to archived detailed
transaction information for a period of 6 years and 3 months ●
2) Archive all data to durable media (e.g., CD-ROM) prior to purging from the eTS and/or the business data warehouse ●
3) 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 media (e.g., CD-ROM). ●

C-34
 GSA Contract GS-33F-0018-N

Table 5. Method for Providing Requirements and Objectives (concluded). We are proposing to meet all of the
requirements, and many of the objectives by IOC. (Legend ●Complete ◐Partial)
ALL REQUIREMENTS IOC
●
IOC
C.6.8.1 Standard Implementation Services
1) Establish and support operational readiness of the ordering agencies, by meeting agency-specific configuration objectives at each
agency:
●
p) Basic business rules and exception procedures
q) Approval and routing chains
r) Agency-specific supplier designations
s) Agency-specific messages and warnings
t) Electronic upload of all traveler profile information provided by the agency with establishment of user accounts and permission
levels for the travelers
u) Incorporation of existing TMC services and establishment of an eTS Integration Agreement for the agency.
C.6.9 Customer Support
1) Provide concise context sensitive online “help” files to assist users in basic eTS functionalities and troubleshooting. In addition to menu
entries, consistently display a Help button or link on every screen to access context sensitive help files and additional user support resources
●
C.7 Performance Measures
1) Meets s the desire outcomes summarized in the below table. These objectives are of equal importance to the Government ●
No. Performance Measure Desired Outcome
I. Service Delivery
a.) Initial Operational Capability (IOC) implementation. < 105 days
b.) Full Operational Capability (FOC) achievement with 2500 vouchers & Before
1000 ticketed transactions. December 1, 2003
Exceed transaction and voucher
c.) Rate of eTS adoption.
targets in Section 13.2
II. Technical
a.) eTS availability or up time (including scheduled eTS down time but not
> 98.00%
including Federal agency network outages).
Maintained to industry best
b.) Technology refreshment.
practices
Establish business data warehouse,
c.) Support of Federal travel management business intelligence and
Data Exchange Specification, and
integration of eTS with agency business systems.
EAI capability ahead of schedule.
Adopt or extend travel industry
d.) Use of XML Schema and related XML technology for eTS data exchange
standard XML Schema and
and integration with agency business systems.
technology.
Meet or beat industry standards for
e.) Online response time. point of presence response time for
comparable online services.
Rapid attainment of GSA Authority
f.) Robust protection of eTS data.
to Operate in order to support FOC.
Meet applicable accessibility
g.) Leveraging of assertive technology to maximize eTS accessibility. requirements of 36 CFR Part 1194
with commercially available tools.
III. Customer Satisfaction
a.) Intuitive eTS user interface and process flows. Qualitative measure.*
b.) Quality of eTS user experience. Qualitative measure.*
c.) Time needed to complete online travel transaction. Qualitative measure.*

C-35
 GSA Contract GS-33F-0018-N

No. Performance Measure Desired Outcome

IV. Self Service Transactions
Maximize end to end, self service transactions including international self 70:30 ratio of self service to non-
service reservations. self service reservations.
V. Customer Support and Training
a.) Percent of user problems resolved during first customer support call (on a
> 95%
semi-annual basis).
b.) Customer support call wait time (semi-annual average). < 5 minutes
c.) Average time between user contact with customer support agent and
resolution of problem (not including agency network outages or problems < 1 hour
requiring software changes.)
d.) Effectiveness of computer- or web-based training. Qualitative measure.*
e.) Effectiveness of instructor-led training Qualitative measure.*
VI. Implementation
a.) Ease of eTS configuration for approval, routing, business rules, user
Qualitative measure.*
accounts, etc.
b.) Accommodation and integration of TMC and FedTrip™ services. Qualitative measure.*

* Qualitative measures for desired outcomes should be based on independent customer surveys administered by
the eTravel PMO. Desired outcomes represent ratings of 4 or better on a scale of 1 to 5 where 1 is the lowest
rating and 5 is the highest rating.

14.0 Deliverable Requirements tract requirements. Northrop Grumman will

The deliverables listed in this section are required
to support management of the eTS. Except as de-
fined below, content and format of deliverables are
the responsibility of Northrop Grumman. Unless
otherwise specified, the Government will have 10
working days from the date of receipt to review
and provide comment back to Northrop Grumman
2) Monthly Status Report and eTS Metrics:
for all deliverables. Northrop Grumman will have
10 working days to provide revised deliverables
that address all Government comments. All docu-
ment deliverables will be provided in hard copy
(four copies) and electronically to the COR for
Government review and distribution. Electronic
copies of documents will be compatible with
Microsoft Office 2000 applications and Microsoft
Project 2000 as applicable. Deliverables 8-17
listed below will be updated and resubmitted
whenever significant changes are made, and
within 30 days after exercise of any optional
ordering period.
1) Kickoff Meeting: Northrop Grumman will
plan and host a kickoff meeting for the eTS
project within 10 calendar days after contract
award. The purpose of the meeting will be to
ensure a common understanding of program
priorities, milestones, deliverables, and con-
provide the Government with an agenda for
the meeting at least 2 working days before the
meeting and deliver meeting minutes that
document all substantive topics and issues dis-
cussed within 7 calendar days after the
meeting.
Northrop Grumman will deliver a Monthly
Status Report and Performance Metrics by the
tenth calendar day of the month beginning the
month after contract award. The status report
will summarize key accomplishments and con-
tractor performance against management and
implementation objectives, program mile-
stones, service level agreements, etc. Actual
and/or anticipated schedule slippage and revi-
sions to the risk analysis and management plan
will also be reported. This document will also
identify key actions required to resolve any
deficiencies reported. The eTS metrics will
report agreed-upon monthly eTS utilization
and performance metrics (target and actual)
proposed by Northrop Grumman and agreed to
by the Government. Metrics will also include
monthly Help Desk and trouble ticket metrics

C-36
 GSA Contract GS-33F-0018-N
necessary to assess eTS service quality, and
quarterly metrics to assess user satisfaction.
3) Quarterly Program Reviews (QPRs): Northrop
Grumman will conduct QPRs in order to re-
port eTS status and performance to the COR,
the eTravel PMO, and the Contracting Officer.
At a minimum, Northrop Grumman will report
the following information: eTS progress and
performance; functional, technology, and
organizational problems encountered; lessons
learned; risk analysis and mitigation strategy
updates; and any resultant changes to its eTS
Program Management Plan. Northrop Grum-
man will prepare a QPR presentation and pro-
vide a copy to the Government for review at
least 15 calendar days before each scheduled
QPR. The Government will provide comments
to the presentation within 7 calendar days after
conduct of the QPR, after which Northrop
Grumman will have 15 calendar days to
deliver minutes for the QPR and address all
Government comments in writing.
4) Semi-Annual Performance Incentive Reviews:
Northrop Grumman will report eTS contract
performance and achievement of eTS service
level agreement objectives twice annually at
performance incentive reviews scheduled by
the Contracting Officer. Northrop Grumman
6) eTS Implementation Report: Northrop Grum-
will present any and all information it deems
relevant for the Government’s consideration in
determining the performance incentive for the
applicable performance period. Performance
incentive reviews may be scheduled in
conjunction with QPRs.
5) eTS IOC: An IOC implementation will be
conducted by Northrop Grumman under the
first task order placed with each awardee. IOC
will include at least 400 users (including all
user roles identified in the CONOPS), and will
consist of the first 800 eTS voucher trans-
actions of which at least 300 will be ticketed
transactions. IOC will include the establish-
ment of eTS data exchange capabilities. At a
minimum, an IATO will be established during
IOC to permit web-based delivery of eTS ser-
vices. Northrop Grumman will deliver an eTS
IOC Report within 15 calendar days after
completion of the IOC effort. The report will
detail the results of the eTS IOC implementa-
tion, including functional, technology, and or-
ganizational problems encountered; how the
problems were resolved or whether resolution
C-37
is still pending; implementation lessons
learned; any proposed changes in Northrop
Grumman’s eTS approach or delivery of ser-
vices; and documentation of eTS configuration
for the ordering agency. Agency configuration
information will be readily separable from any
proprietary information contained within the
report, and will include traveler profiles and
all agency-specific business rules and policies
established in the eTS during IOC implemen-
tation. In addition to the mandatory customer
support and training requirements, Northrop
Grumman will provide the following mini-
mum services:
a) Create traveler profiles for all users in-
volved and establish all classes of user
role accounts and permissions
b) Establish agency and/or subordinate or-
ganization configuration, including basic
business rules and exception procedures,
approval and routing chains, agency-
specific supplier designations, and
agency-specific messages and warnings
c) Incorporate existing TMC services
d) Train all agency users involved in the IOC
effort.
man will prepare and deliver an eTS Imple-
mentation Report under each task order that
includes CLIN 0006, 0023, 0043, and 0063
Standard Implementation Services. This report
will document the agency-specific eTS con-
figuration established during implementation
activities at that agency. The report will
clearly identify the department, agency, or
subordinate organization(s) to which it ap-
plies. It will capture all configurable eTS para-
meters established by Northrop Grumman
during implementation and include a detailed
listing of all data and documents provided to
Northrop Grumman by the agency to support
implementation. At a minimum, the report will
include basic business rules and exception
procedures; static approval and routing chains;
agency-specific supplier designations; agency-
specific standard messages and warnings; user
account and user summaries; procedures for
the incorporation of existing TMC services;
and the eTS Integration Agreement established
for the agency if applicable. eTS Implemen-
tation Reports will be delivered within 30 days
 GSA Contract GS-33F-0018-N
after completion of Standard Implementation
activities at any agency.
7) Redacted eTS Proposal: Northrop Grumman
will deliver an electronic copy of its successful
Round 1 and Round 2 proposals with all in-
formation considered proprietary by Northrop
Grumman stricken within 30 calendar days af-
ter contract award. The electronic format will
permit the Government to review stricken text
in order to achieve concurrence between the
Government and Northrop Grumman as to the
specific text to be stricken for public release.
8) Program Management Plan: Northrop Grum-
man will deliver an eTS Program Management
Plan within 30 calendar days after contract
award. The Program Management Plan must
summarize and demonstrate Northrop Grum-
man’s disciplined program management
methodology; identify team organization, key
personnel, and responsibilities; depict a WBS
and program schedule (with key milestones,
deliverables, and a baseline); and include a
risk analysis and management plan that identi-
fies major risks and associated mitigation
strategies for the eTS. The Program Manage-
ment Plan will clearly identify required Gov-
ernment actions, suspense dates, and schedule
impacts if suspense dates are not met. The
Program Management Plan will also describe
Northrop Grumman’s technology refreshment
policy for the eTS.
9) Implementation Plan: Northrop Grumman will
deliver an eTS Implementation Plan within 60
calendar days after contract award. The plan
will document Northrop Grumman’s eTS im-
plementation approach across Federal agen-
cies, including prioritization of efforts, agency
collaboration and support options, and detailed
implementation plans and activities for a given
agency. The Implementation Plan will clearly
identify required Government actions, sus-
pense dates, and schedule impacts if suspense
dates are not met.
10) eTS Operational Architecture: Northrop
Grumman will deliver an eTS Operational Ar-
chitecture document within 30 calendar days
after contract award. It will describe the eTS
technical environment, including applications,
operating systems and platforms, databases,
data stores, user interfaces, network/Internet
connectivity, and data flows. It will also iden-
C-38
tify linkages between users, service compo-
nents, and travel resources.
11) Configuration Management Plan: Northrop
Grumman will deliver an eTS Configuration
Management Plan within 60 calendar days
after contract award. It will describe Northrop
Grumman’s disciplined methodology for soft-
ware/documentation version control and up-
grade procedures for the eTS. This plan will
also identify the standards with which North-
rop Grumman complies for system configura-
tion management.
12) User Support and Training Plan: Northrop
Grumman will deliver an eTS Customer
Support Plan within 60 calendar days after
contract award. It will summarize eTS
customer support mechanisms, including
online help, phone-in support and help desk
procedures, technical and application support,
travel arrangement support, quality improve-
ment measures, event management/escalation
processes, etc. The plan will also summarize
supplemental customer support services
offered and define the tiered levels of support
offered. Standard and supplemental eTS
training will also be described, including
computer-based training, instructor-led train-
ing, and train-the-trainer curricula.
13) Data Management Plan: Northrop Grumman
will deliver an eTS Data Management Plan
within 90 calendar days after contract award.
This plan will describe the data model for the
business data warehouse and establish man-
agement procedures for the data contained
therein. It will describe how Northrop Grum-
man will manage data retention and archiving
in accordance with the requirements of this
PBWS and the standards cited herein. The
plan will fully define and govern the data
model for the business data warehouse and
address data import/export mapping, formats,
capabilities, and procedures as well as the data
transition requirements of this PBWS. The
data model will include logical schema of the
database(s) and related data dictionaries to
support data sharing within the Federal enter-
prise.
14) Data Exchange Specification: Northrop Grum-
man will deliver an eTS Data Exchange Speci-
fication within 90 days after contract award.
The specification will define the requirements
 GSA Contract GS-33F-0018-N
for data exchange with the eTS, including
standard data input and standard data output.
The specification will include all information
necessary for Federal agencies to establish In-
terface Agreements and interfaces with the
eTS using the eTS EAI platform. This deliver-
able will also include a mapping of data ele-
ments within the business data warehouse (or
other eTS data source) available for exchange
and integration, including a complete list of
data elements, functional data element de-
scriptions, field characteristics, data types,
schema, and a representation of these data
elements in EDI, XML, UDF, or other
industry standard Internet-enabled data
formats. The specification will define the
processes and procedures for data exchange
(inbound and outbound), including, at a
minimum, data transmission and scheduling
options, security and access requirements and
options and format translation capabilities.
15) Continuity of Operations and Contingency
Plan: Northrop Grumman will deliver a
Continuity of Operations and Contingency
Plan within 120 days after contract award.
This plan will be based on the guidelines
presented in NIST Special Publication 800-34.
It will address issues such as emergency
response procedures, backup operations,
recovery actions, roles and responsibilities,
and points of contact. It will also summarize
eTS service level agreements and detail how
Northrop Grumman will manage events that
may interrupt the use of eTS.
16) Security Plan: Northrop Grumman will deliver
an eTS Security Plan that complies with the
guidelines and template of NIST Special
Publication 800-18 within 60 calendar days
after contract award. This plan will detail how
C-39
the eTS will manage user authentication and
role-based access controls (e.g., traveler vs.
approver vs. TMC); the audit capabilities of
the eTS (e.g., whether it can be determined
who booked/approved travel and details of
itinerary); how data will be secured and
encrypted for storage and transmission
(including pin/password data); and how data
integrity and validity will be maintained (e.g.,
nonrepudiation). The plan will also describe
Northrop Grumman’s approach for obtaining
timely GSA certification and accreditation of
eTS, including documentation to be submitted.
17) XML Schema: Northrop Grumman will
deliver a zip file containing all XML Schemas
used in the eTS, including a list or spreadsheet
that indicates which schema were developed
by Northrop Grumman and which were
adopted from industry standardization efforts.
The XML Schema will be delivered within 90
days after contract award. All XML Schemas
developed by Northrop Grumman will follow
the recommendations established in the Draft
Federal XML Developer’s Guide. It is desired
that Northrop Grumman include examples of
XML instances that reference individual XML
Schema. The eTS XML Schema are required
to support anticipated FEAPMO submission
requirements related to the DRM, and to
facilitate standardization of electronic travel
data elements in the travel industry.
15.0 Work Breakdown Structure
This section describes what work will be
performed to meet the requirements in Section 4.
The WBS is performance-based and is mapped to
the requirements in Section 5.2. The WBS for eTS
is based on the requirements and objectives of this
PBWS.
 GSA Contract GS-33F-0018-N

Figure 5-1. The Performance-Based WBS for eTS. The WBS for eTS divides the work on the project into more manageable
elements. Each element has associated performance indicators and standards of performance.
15.1 WBS Categories
Figure 5-1 shows the elements in the WBS. There
are eight main categories of work:
• Program Management
− Ensuring delivery of all requirements and
objectives in accordance with RFP and
contract
− Providing management interface to GSA
and agencies Managing the performance
metrics collection and reporting
− Providing integration and security in
accordance with the RFP and contract
− Performing QA and risk assessment
− Managing the contract deliverables to ensure
quality and meet the schedules in Section
14, Deliverable Requirements
• IOC System
− Activating an IOC system that incorporates
all requirements and the pro-posed
objectives and is ready for use by the IOC
agency by July 2003
− Operating and maintaining the IOC system
− Supporting the IV&V contractor so FOC
dates can be met
− Performing Self Service Fulfillment and
integration at the IOC agency
• FOC System
− Activating an FOC system that incorporates
all requirements and agreed-upon objectives
and is available for agency-wide
implementation by December 31, 2003
− Operating and maintaining the FOC system
− Performing upgrades to the system to sup-
port workload as new agencies are added
− Performing technology refreshment in
accordance with the Technology
Refreshment section of the Program
Management Plan
− Performing Self Service Fulfillment and
integration at agencies
• Implementation
− Performing standard implementation ser-
vices in accordance with the requirements in
this PBWS.

C-40
 GSA Contract GS-33F-0018-N

• Non-Self-Service Reservations and Fulfillment • Business Data Warehouse

− Delivering the travel agent services provided − Implement and operate the business data
(both mandatory and CLIN 0007 task order) warehouse in accordance with the
by subcontractor Rosenbluth International requirements of this PBWS.
− Travel customer support agent assisted Each element in the WBS has at least one
reservations and fulfillment performance indicator and associated performance
• Training standards for those indicators. The standards
chosen are measurable and attainable; in the
− Meeting performance measures and
aggregate, they measure our success in achieving
requirements for both standard training and
the goals and objectives of the eTravel program.
task orders for supplemental training
The specific performance indicators and standards
services (CLIN 0010) and providing
are discussed in detail in Section 16.
sufficient training resources to support the
implementation schedule in this PBWS. 15.2 Cross Reference to the Contract Line Items
• Customer Support The WBS serves other important management
functions, including providing the structure under
− Operate the eTS Help Desk in accordance
which Northrop Grumman will capture program
with the requirements and objectives
costs from purchasing activities and time reports.
(performed by subcontractor Rosenbluth
The WBS elements relate to the price proposal as
International for travel and Northrop
shown in Table 6. The table shows the CLINs and
Grumman for technical support)
the distribution of WBS elements among the
CLINs.
Table 6. Cross Reference Between the WBS and the Contract Line Items. The eTS WBS is based on the requirements and
objectives of the SOO.
BASE PERIOD (36 MONTHS)
CLIN WBS & RFP Reference Comments
0001 eTS IOC WBS 1.1-1.9 Program Management eTS IOC
WBS 2.1 Activate the IOC System
WBS 2.2 IOC Production Readiness Verification
WBS 2.3 Operate & Maintain IOC System
WBS 2.4 Support IV&V
WBS 2.5 Self-Service Fulfillment
WBS 2.6 Integration Support
WBS 4.0 Implementation
WBS 6.1 Standard Training
WBS 7.1 Standard Customer Support

SOW Types of Travel

SOW Services
SOW-C.6.6 Basic Capabilities
SOW Data, Integration, and Information Management
SOW Implementation
SOW Customer Support
SOW Training
SOW IV&V Testing
SOW Deliverables
0002 eTS Reservation and
Fulfillment Services

C-41
 GSA Contract GS-33F-0018-N

Table 6. Cross Reference Between the WBS and the Contract Line Items (continued). The eTS WBS is based on the
following requirements .
BASE PERIOD (36 MONTHS)
CLIN WBS & RFP Reference Comments
0002AA Self-Service Domestic WBS 1.1-1.9 Program Management • Activate an FOC system that meets all
or International Travel WBS 3.1 Activate the FOC System requirements and all agreed-upon
with Air and/or Rail WBS 3.2 FOC Production Readiness Verification objectives
WBS 3.3 Operate & Maintain FOC System • Voucher processing is under CLIN 0003
WBS 3.4 Workload Growth Upgrades • Program management and system
WBS 3.5 Technology Refreshment operation from the end of IOC through the
WBS 3.6 Self-Service Fulfillment base period
WBS 3.7 Integration support • Labor for WBS 1.11 Risk Management
WBS 4.0 Implementation from ASI
WBS 5.1 Standard Reservations and Fulfillment • Some labor for WBS 3.1 and 3.3 from
subcontractor IDC
WBS 6.1 Standard Training
• Self-service reservations & fulfillment by
WBS 7.1 Standard Customer Support
GovTrip system includes TRX booking
engine
SOW Types of Travel
• Standard training at each agency
SOW Services
• Standard customer support help desk,
SOW -C.6.6 Basic Capabilities travel help by subcontractor Rosenbluth
SOW Data, Integration, and Information Management International, and technical help by
SOW Implementation Northrop Grumman
SOW Customer Support • All other subcontractors perform their
SOW Training designated roles
SOW eTS FOC
SOW Deliverables
0002AB Self-Service Domestic WBS 1.1-1.9 Program Management • Activate an FOC system that meets all
or International Travel WBS 3.1 Activate the FOC System requirements and all agreed-upon
without Air and/or WBS 3.2 FOC Production Readiness Verification objectives
Rail(Lodging and/or WBS 3.3 Operate & Maintain FOC System • Voucher processing is under CLIN 0003
Rental Car Only) WBS 3.4 Workload Growth Upgrades • Program management and system
WBS 3.5 Technology Refreshment operation from the end of IOC through the
WBS 3.6 Self-Service Fulfillment base period
WBS 3.7 Integration support • Labor for WBS 1.11 Risk Management
WBS 4.0 Implementation from ASI
WBS 5.1 Standard Reservations and Fulfillment • Some labor for WBS 3.1 and 3.3 from
subcontractor IDC
WBS 6.1 Standard Training
• Self-service reservations & fulfillment by
WBS 7.1 Standard Customer Support
GovTrip system includes TRX booking
engine
SOW Types of Travel
• Standard training at each agency
SOW Services
• Standard customer support help desk,
SOW -C.6.6 Basic Capabilities travel help by subcontractor Rosenbluth
SOW Data, Integration, and Information Management International, and technical help by
SOW Implementation Northrop Grumman
SOW Customer Support • All other subcontractors perform their
SOW Training designated roles
SOW eTS FOC
SOW Deliverables
0002AC Non-Self-Service WBS 5.0 Non-Self-Service Reservations and Fulfillment Performed by subcontractor Rosenbluth
Domestic Travel with SOW.5 Resolutions International
Air and/or Rail SOW Fulfillment
0002AD Non-Self-Service WBS 5.0 Non-Self-Service Reservations and Fulfillment Performed by subcontractor Rosenbluth
International Travel with SOW Resolutions International
Air and/or Rail SOW Fulfillment

C-42
 GSA Contract GS-33F-0018-N

Table 6. Cross Reference Between the WBS and the Contract Line Items (continued). The eTS WBS is based on the
following requirements .
BASE PERIOD (36 MONTHS)
CLIN WBS & RFP Reference Comments
0002AE Non-Self-Service WBS 5.0 Non-Self-Service Reservations and Fulfillment Performed by subcontractor Rosenbluth
Domestic or SOW Resolutions International
International Travel SOW Fulfillment
without Air and/or Rail
(Lodging and/or Car
Rental Only)
0002AF Self-Service Domestic WBS 1.1-1.9 Program Management • Activate an FOC system that meets all
or International Travel WBS 3.1 Activate the FOC System requirements and all agreed-upon
Reservation only with WBS 3.2 FOC Production Readiness Verification objectives
Air and/or Rail WBS 3.3 Operate & Maintain FOC System • Voucher processing is under CLIN 0003
WBS 3.4 Workload Growth Upgrades • Program management and system
WBS 3.5 Technology Refreshment operation from the end of IOC through the
WBS 3.6 Self-Service Fulfillment base period
WBS 3.7 Integration support • Labor for WBS 1.11 Risk Management
WBS 4.0 Implementation from ASI
WBS 5.1 Standard Reservations and Fulfillment • Some labor for WBS 3.1 and 3.3 from
subcontractor IDC
WBS 6.1 Standard Training
• Self-service reservations & fulfillment by
WBS 7.1 Standard Customer Support
GovTrip system includes TRX booking
SOW Types of Travel engine
SOW Services • Standard training at each agency
SOW -C.6.6 Basic Capabilities • Standard customer support help desk,
travel help by subcontractor Rosenbluth
SOW Data, Integration, and Information Management
International, and technical help by
SOW Implementation Northrop Grumman
SOW Customer Support
• All other subcontractors perform their
SOW Training designated roles
SOW eTS FOC
SOW Deliverables
0002AG Self-Service Domestic WBS 1.1-1.9 Program Management • Activate an FOC system that meets all
or International Travel WBS 3.1 Activate the FOC System requirements and all agreed-upon
Reservation Only WBS 3.2 FOC Production Readiness Verification objectives
Without Air and/or Rail WBS 3.3 Operate & Maintain FOC System • Voucher processing is under CLIN 0003
(Lodging and/or Rental WBS 3.4 Workload Growth Upgrades • Program management and system
Car Only) operation from the end of IOC through the
WBS 3.5 Technology Refreshment
WBS 3.6 Self-Service Fulfillment base period
WBS 3.7 Integration support • Labor for WBS 1.11 Risk Management
WBS 4.0 Implementation from ASI
WBS 5.1 Standard Reservations and Fulfillment • Some labor for WBS 3.1 and 3.3 from
subcontractor IDC
WBS 6.1 Standard Training
• Self-service reservations & fulfillment by
WBS 7.1 Standard Customer Support
GovTrip system includes TRX booking
engine
SOW Types of Travel
• Standard training at each agency
SOW Services
• Standard customer support help desk,
SOW C.6.6 Basic Capabilities travel help by subcontractor Rosenbluth
SOW Data, Integration, and Information Management International, and technical help by
SOW Implementation Northrop Grumman
SOW Customer Support • All other subcontractors perform their
SOW Training designated roles
SOW eTS FOC
SOW Deliverables
0003 eTS Authorization and
Voucher Services
0003AA Local Authorization WBS 3.3 Operate and Maintain FOC System (local Basic GovTrip system and Gelco voucher
and/or Voucher voucher processing part only) processing subsystem
SOW Voucher Processing

C-43
 GSA Contract GS-33F-0018-N

Table 6. Cross Reference Between the WBS and the Contract Line Items (continued). The eTS WBS is based on the
following requirements.
BASE PERIOD (36 MONTHS)
CLIN WBS & RFP Reference Comments
0003AB TDY Authorization WBS 3.3 Operate and Maintain FOC System (TDY Basic GovTrip system and Gelco voucher
and/or Voucher voucher processing part only) processing subsystem
SOW Local Travel Vouchers
0004 Paper Ticket Issuance
and Delivery
0004AA Paper Ticket with U.S. WBS 5.3 Paper Tickets Provided by subcontractor Rosenbluth
Mail Delivery International
0004AB Paper Ticket with WBS 5.3 Paper Tickets Provided by subcontractor Rosenbluth
Express Delivery International
0004AC Paper Ticket with WBS 5.3 Paper Tickets Provided by subcontractor Rosenbluth
Courier Delivery International
0005 Business Data WBS 8.0 Business Data Warehouse Establish and operate Business Data
Warehouse SOW Business Data Warehouse Warehouse
SOW Business Data Warehouse
0006 Standard WBS 4.1 Standard Implementation Services Deliver standard implementation services to
Implementation SOW Implementation Services each ordering agency
Services
0007 On-Site Reservation WBS 5.2 On-Site Reservations and Fulfillment Provided by subcontractor Rosenbluth
and Fulfillment Services SOW Reservations International—as specified in task order
SOW Fulfillment
0008 Other
0008AA Travel
0008AB Reserved
0008AC Reserved
0009 Supplemental WBS 7.2 Supplemental Customer Support Services As specified in task order
Customer Support SOW Customer Support
Services
0010 Supplemental Training WBS 6.2 Supplemental Training Services C.6.10 As specified in task order
Services
0011 Supplemental Security WBS 1.5 Supplemental Security Services As specified in task order
Services SOW Security Capabilities and Characteristics
0012 Custom Report WBS 1.8 Custom Reports As specified in task order
Development SOW Custom Report Development

16.0 Level of Performance
The WBS provides the foundation for our PBWS
and our overall approach to performance manage-
ment. The elements of the WBS define the work.
In order for the project to be truly performance-
based, we must have a management process to
ensure that each WBS element produces a quality
output.
To accomplish this, each element of the WBS has
one or more performance indicators and a per-
formance goal for each indicator. A performance
indicator is a statement of the outcome being
measured, and a performance goal is the desired
standard of performance for that outcome. For ex-
ample, “the percentage of help desk calls closed in
less than 30 minutes” would be a performance in-
dicator, and “95%” would be the performance goal
for that indicator. Closing 95% or more help desk
calls in under 30 minutes means we are perform-
ing at an acceptable quality level.
16.1 Performance Levels
Proposed performance goals for eTS are listed in
Table 7. Each element in the WBS is listed, and
each has at least one performance indicator and
performance goal. The value shown for a goal is
the acceptable quality level for that indicator. The
goals are either (a) service delivery, (b) customer
satisfaction, (c) ratio of self-service transactions,
(d) customer support and training, (e) technical, or
(f) management goals that measure the accom-
plishment of management objectives.
The eTS quality assurance (QA) organization
collects the metrics shown in the table—the actual

C-44
 GSA Contract GS-33F-0018-N

performance of each indicator—on a monthly
basis. They then perform the following:
• Enter the metric data in Excel spreadsheets
• Plot the trend curves over time
• Plot correlations of certain indicators, such as
the increase in the number of users-versus-
system response time
• Report to the project team on the status of all
metrics.
Management reviews metrics monthly. The review
consists of evaluating current indicator metrics to
determine if goals are being achieved and if trends
for any indicator show possible risks. They also
assign actions from earlier performance review
meetings.
Performance metrics are the basis on which the
risk analysis process is conducted. The qualitative
and quantitative performance measure values
collected by the QA team are the means we use to
determine whether a risk needs mitigation.
Finally, the performance goals also determine the
course of eTS incentive payments. The incentive
plan will focus on the metrics. The GSA and
Northrop Grumman will use the outcome
measures described here to determine the size of
the incentive payment.

Table 7. Proposed Performance Goals. Our performance goals for all elements of the WBS ensure quality performance of the
eTS.
Performance Goal
WBS Task Performance Indicator Acceptable Quality Level Type
1.0 Program Management
1.1 Program Control Delivery of all Requirements IAW contract M
1.2 GSA Interface Qualitative N/A M
1.3 Agency Interface and Marketing Customer satisfaction surveys > 3 average SD
Number of simultaneous agencies 2 < Number < 4
implementing eTS
Rate of eTS adoption Exceed transaction and voucher targets SD
as shown in Section 13.2
1.4 Program Metrics Metrics collected and reported monthly 100% M
1.5 Security (standard and task Standard time operating under formal 100% SD
order) certification
Robust protection of eTS data Rapid attainment of GSA Authority to T
ATO
1.6 Quality Assurance QA product audits For each C-10 Deliverable SD
QA process audits Once per year for each process
1.7 Risk Management Risk Management Plan Program Management Plan 30 days SD
after contract award
Conduct risk assessments Weekly SD
1.8 Custom Report Development As requested in task orders As requested in task orders N/A
1.9 Deliverables In accordance with Section 14 ± 3 days SD
2.0 IOC System
2.1 Activate IOC System IOC implementation < 105 days after task order SD
2.2 Production Readiness Ready for production July 2003 IOC <105 days after task order SD
Verification
2.3 Operate/Maintain IOC System System availability > 98.00% T
Online response time* < 8 minutes *** T
Use of XML Schema and related XML Adopt or extend travel industry standard T
technology for data exchange and
integration
2.4 Support IV&V Qualitative N/A N/A
2.5 Self-Service Fulfillment Qualitative N/A N/A
2.6 Integration Support Agency prep time (from task order < 60 days I
issuance to first trip)
3.0 FOC System
3.1 Activate FOC System FOC achievement with 2,500 vouchers and ± 20 days SD
1,000 ticketed transactions before
December 1, 2003

C-45
 GSA Contract GS-33F-0018-N

Protection of eTS data Rapid attainment of GSA Authority to T

ATO
Leverage assistive technology for Meet 36 CFR Part 1194 with T
accessibility commercially available tools
* Northrop Grumman standard response test, run during peak business hours
** Based on customer surveys administered by the eTS PMO
*** Exceed industry standards
Type of performance measure (RFP Section C.7):
● SD=Service Delivery ● CS=Customer Satisfaction ● SST=Self Service Transaction ● CS&T=Customer Support & Training
● I=Implementation ● M=Management ● N/A=Not Applicable ● T=Technical

Table 7. Proposed Performance Goals (continued). Our performance goals for all elements of the WBS ensure quality
performance of the eTS.
Performance Goal
WBS Task Performance Indicator Acceptable Quality Level Type
3.0 FOC System (continued)
3.2 Production Readiness Ready for production December 2003 ± 20 days SD
Verification
3.3 Operate and Maintain FOC System availability > 98.00% T
System
Online response time* < 8 minutes *** T
Use of XML Schema and related XML Adopt or extend travel industry standard
technology for data exchange and
integration
3.4 Workload Growth Upgrades Before availability or response time exceed Always implemented before availability T
acceptable quality level or response time begins to exceed
acceptable quality level
3.5 Technology Refreshment To best industry standards and before Always implemented before availability T
availability or response time exceed or response time begins to exceed
acceptable quality level acceptable quality level
3.6 Self-Service Fulfillment Intuitive eTS user interface and process Qualitative measure ** CS
flows
Quality of eTS user experience Qualitative measure ** CS
Time needed to complete online travel Qualitative measure ** CS
transaction
Ratio of self-service to non-self-service 70:30 ratio SST
reservations
Ease of configuration for approval, routing, Qualitative measure ** I
etc.
Accommodation and integration of TMCs Qualitative measure ** I
and FedTrip
3.7 Integration Support Agency prep time (from task order < 60 days I
issuance to first trip)
4.0 Implementation
4.1 Standard Implementation Agency prep time (from task order 45 days I
issuance to first trip)
Agency satisfaction with implementation Score of 3 or better on exit survey I
work
Agency roll-out in accordance with Section ± 20% SD
13.2
4.2 Implementation Services Task As specified in task order As specified in task order N/A
Orders
5.0 Non-Self-Service Reservation and Fulfillment
5.1 Standard Non-Self-Service Quality of eTS user experience Qualitative measure ** CS
Reservation and Fulfillment
Services
Accommodation and integration of TMCs Qualitative measure ** I
and FedTrip

C-46
 GSA Contract GS-33F-0018-N

5.2 On-Site Reservation and As specified in task order As specified in task order N/A
Fulfillment Task Orders
* Northrop Grumman standard response test, run during peak business hours
** Based on customer surveys administered by the eTS PMO
*** Exceed industry standards
Type of performance measure (RFP Section C.7):
● SD=Service Delivery ● CS=Customer Satisfaction ● SST=Self Service Transaction ● CS&T=Customer Support & Training
● I=Implementation ● M=Management ● N/A=Not Applicable ● T=Technical
Table 7. Proposed Performance Goals (concluded). Our performance goals for all elements of the WBS ensure quality
performance of the eTS.
Performance Goal
WBS Task Performance Indicator Acceptable Quality Level Type
6.0 Training
6.1 Standard Training Effectiveness of computer- or web-based Qualitative measure ** CS&T
training
Effectiveness of instructor-led training Qualitative measure ** CS&T
6.2 Training Task Orders As specified in task order As specified in task order N/A
7.0 Customer Support
7.1 Standard Customer Support Probability of busy signal < 2% CS&T
Percent of user problems resolved during > 95% CS&T
first call
Customer support call wait time (semi- < 5 minutes CS&T
annual average)
Average resolution time < 1 hour CS&T
7.2 Supplemental Customer As specified in task order As specified in task order N/A
Support Task Orders
8.0 Business Data Warehouse Number of requirements met 100% T
Completion of data warehouse relative to ± 10 days SD
task order proposal date
* Northrop Grumman standard response test, run during peak business hours
** Based on customer surveys administered by the eTS PMO
*** Exceed industry standards
Type of performance measure (RFP Section C.7):
● SD=Service Delivery ● CS=Customer Satisfaction ● SST=Self Service Transaction ● CS&T=Customer Support & Training
● I=Implementation ● M=Management ● N/A=Not Applicable ● T=Technical

16.2 Quality Assurance Surveillance Plan
QA and metrics management roles are augmented
by two review boards (a Metrics Review Board
[MRB] and a Risk Review Board [RRB]) to
maintain proper focus on analysis and control of
performance measures. The MRB and the RRB
work together to ensure that any early indicators
identified in the performance metrics are quickly
analyzed and that those deemed to be program
risks are sent to the RRB (Figure 2).

C-47
 GSA Contract GS-33F-0018-N
Figure 2. Quality Assurance Surveillance Method. Our products use a metrics-based method to monitor and improve
performance.
16.2.1 Metrics Review Board
A MRB meets monthly to assess status toward
achieving performance objectives, reviews and
reports trends, and recommends corrective action.
The MRB includes members from each of the
functional activities and is chaired by the
program’s Metrics Manager, who is skilled in
quantitative techniques for continuously
improving processes. The MRB determines the
impact of problematic trends and develops action
plans for MRB members to implement or follow
up. The MRB and the RRB work together to
ensure quick response to negative trends or early
indicators identified in the performance metrics.
The MRB ensures that action plans are initiated,
and program risks are passed to the RRB for
reporting and action. The status of action plans are
a permanent item on each MRB meeting agenda.
The metrics collected on the program will be
maintained in the Metrics Database, which
contains the following attributes for each metric:
• Metric name, purpose and detailed description,
base measurement, and calculations
• Analysis
• Actual vs. Plan
• Test/Verification Method
• Threshold levels.
The performance goals are set in the Performance-
Based Management Plan (PBMP). The MRB
reviews metrics for compliance, and early warning
C-48
indicators (those allowing early analysis and
proactive monitoring) are presented to the metrics
coordinator to ensure that all performance
measures are satisfied. The GovTrip Liaison
Manager will also provide the MRB with metrics
collected from Users Group feedback posted to the
GovTrip portal.
When metrics indicate trends that may result in
problems, the MRB determines the impact of the
trends and develops action plans for MRB
members to implement or follow up. More
difficult trends are elevated to the RRB as risks.
The status of action plans will be a permanent item
on each MRB meeting agenda.
Monthly Program Reviews address the metrics and
the number and status of open action items
(including incomplete action plans). We will use
our management portal to make metrics accessible
to both management and customers.
16.2.2 Risk Review Board
A Risk Manager will identify, analyze, plan, track,
and control risks. Following our corporate best
practices, a RRB is established to capture
identified risks and their associated mitigation
plans and status in accordance with a published
eTS Risk Management Plan. The DPM chairs the
RRB with membership from the PMSO and
functional activities. The Risk Manager also
manages the risk database and serves as the RRB
secretary. The RRB meets at least monthly to
 GSA Contract GS-33F-0018-N
identify new risks and reevaluate ongoing risks,
assign responsibility for developing risk mitigation
plans, determine if mitigation is effective, and
control risk until it is properly resolved. The DPM
will provide the GSA PMO monthly risk status
and advisory reports. In addition, the GSA PMO
may direct the RRB, through the PM, to analyze
potential risks identified by GSA.
The RRB monitors, mitigates, and tracks closure
of identified program performance risks. An im-
portant part of any risk mitigation strategy is de-
termining the root cause of the problem. We use
cause-and-effect diagrams and statistical hypothe-
sis tests to determine and validate the root causes
of problems. Error Modes and Effects Analysis
(EMEA) tools identify and document actions taken
to mitigate risks resulting from weaknesses in
processes. Process-oriented metrics are added to
the Metrics Database to ensure that the gains
resulting from risk mitigation activities continue.
16.2.3 Performance Plan
At the initiation of the contract, the PBMP is es-
tablished. This plan documents each performance
goal and metric, with associated thresholds, data
collection, and reporting methods. The PBMP is
based upon the performance goals and measures
identified in the RFP and augmented by those to
be further defined in the proposal. Functional re-
sponsibilities for the data collection, analysis, re-
porting, and corrective action are defined and allo-
cated in the PBMP.
Each PBMP measure, whether explicitly identified
or derived by Northrop Grumman, will be a sepa-
rate section of the performance plan. For each sec-
tion, the objective, measure, and functional or-
ganization roles and responsibilities will be
identified. Any dependencies on other personnel
or tasks are flagged, and progress or status is re-
viewed in the monthly MRB meetings. As de-
scribed earlier, the MRB creates an action plan for
any measure that significantly deviates from plan
or triggers an early warning indicator.
Quantitative and qualitative performance measures
will be used for eTS. An example of a quantitative
performance measure is the eTS threshold for
system availability of 98%. Our current system’s
actual availability was 99.57% from January 2002
through July 2003 as shown Figure 3.
C-49
Figure 3. Threshold of System Availability. Our system’s
availability exceeds 98%.
Qualitative objectives require measurement and
monitoring of subjective metrics, such as the
“travel experience.” Qualitative metrics require the
same decomposition, monitoring, and
measurement approaches as quantitative metrics.
The Metrics Manager and MRB conduct periodic
evaluations of the assumptions and dependencies
that underlie all metrics used on the program. For
example, surveys of customer satisfaction using
the metric “time to complete an online travel
transaction” require definition of a representative
travel transaction and an acceptable time for
completion. Our current travel service conducts
hourly tests of the time it takes to complete a
representative online travel transaction ensuring
the performance and throughput of the system is
meeting processing goals. From October 2002
through January 2003, Northrop Grumman
completed the tests in less than 6 minutes 95% of
the time. This ensures that the throughput of the
system is sufficient for the workload demands of
the users. This measure, along with qualitative
customer survey data, will be used to determine
acceptable user satisfaction.
16.3 Government Obligations
In order for Northrop Grumman to meet certain
performance goals, it is necessary for the
Government (GSA or an agency) to provide
certain information or perform certain actions. In
those cases, which are identified in Table 8,
Northrop Grumman can only be responsible for
meeting the performance goal if the Government
performs its part on time.

Table 8. Government Obligations. In order for Northrop Grumman to meet certain performance goals, the Government must
perform its part on time.
WBS Element
• WBS 2.0 IOC System
• WBS 4.0 Implementation
• WBS 6.0 Training
• WBS 7.0 Customer Support
• WBS 2.0 IOC System
• WBS 4.0 Implementation
• WBS 6.0 Training
• WBS 7.0 Customer Support
• WBS 2.0 IOC System
• WBS 2.4 Support IV&V
• WBS 3.0 FOC System
• WBS 4.0 Implementation
• WBS 3.0 FOC System
• WBS 4.0 Implementation
• WBS 6.0 Training
• WBS 7.0 Customer Support
• WBS 8.0 Business Data Warehouse
• WBS 2.0 IOC System
• WBS 4.0 Implementation
• WBS 5.0 Non-Self-Service Reservations
and Fulfillment
• WBS 1.5 Security
• WBS 2.0 IOC System
• WBS 3.0 FOC System
GSA Contract GS-33F-0018-N
Government Obligations
IOC-agency data shall be provided to Northrop Grumman in accordance with the schedule
negotiated in the task order award.
Provide the data and personnel necessary to maintain the schedule negotiated in the task
order
Agency-specific IV&V will be accommodated on a T&M basis during the Implementation
Phase.
All agency-specific information shall be provided to Northrop Grumman at time specified in the
task order and must be consistent with the eTravel Service common process and compatible
with the functionality of GovTrip as delivered. The agency shall also provide the following
during the specified time periods:
• Agency and/or subordinate organization configuration, basic business rules and exception
procedures, approval and routing chains, agency-specific supplier designations, and
agency-specific messages and warnings
• Users and managers involved in implementation and training shall be available in
accordance with the GovTrip task order schedule
• Traveler profiles for all users involved in implementation, including the establishment of all
classes of user role accounts and permissions
• Provide access to existing TMC/TSS services
Agency-selected TMC must be capable of interfacing and integrating with the GovTrip System
in accordance with the schedule established in the task order.
Policy Enforcement Point (PEP) software modules from Entrust and/or Entegrity
C-50
 GSA Contract GS-33F-0018-N

Table 8. Government Obligations (continued). In order for Northrop Grumman to meet certain performance goals, the
Government must perform its part on time.

WBS Element Government Obligations

• WBS 2.0 IOC System The IOC agency will complete the web-based Training Site Survey at task order award.
• WBS 6.0 Training

• WBS 6.0 Training
• WBS 2.0 IOC System
• WBS 2.0 IOC System
• WBS 5.0 Non-Self Service Reservations
and Fulfillment
• WBS 5.1 Standard Reservations and
Fulfillment
• WBS 5.2 On-Site Reservation and
Fulfillment Services
• WBS 5.3 Paper Tickets
• WBS 1.2 GSA Interface
• WBS 2.0 IOC System
• WBS 4.0 Implementation
• WBS 6.0 Training
• WBS 7.0 Customer Support
• WBS 8.0 Business Data Warehouse
If an Agency requests on-site training in its task order, the Agency will provide the following
facilities and equipment at Government training sites or such facilities as agreed upon in the
task order:
1. A climate-controlled classroom of sufficient size (approximately 1650-1700 square feet) to
accommodate 25 students and the Northrop Grumman instructors (2) and associated
equipment, tables and chairs.
2. Classroom should be able to be secured during non-training hours in order to provide
physical security for training equipment.
3. Access to the training facility/classroom for prior to and after the conduct of the training
classes to conduct equipment setup, connectivity testing and tear down.
4. Training room will be located on the first floor of the building or have an elevator available
for movement of equipment to other floors.
5. Electric power outlets 110Vs – minimum of 5 in the room.
6. 16 – 2.5’ x 8’ tables or equivalents (or computer-desks, other type tables).
7. 29 chairs (25 students, 2 instructors, 2 visitors).
8. White screen (for large screen projection) approximately 5’ x 7’ (or flat white wall area).
9. Access to active Internet portal for connection to GovTrip training environment.
10. Single phone line (with commercial access) connection available in the classroom
400 users to include all roles required in the Northrop Grumman CONOPS
800 eTS voucher transactions of which at least 300 shall be ticketed transactions
Required IOC data elements necessary for eTS data exchange capabilities within the time
specified in the task order, preferably within15 days of IOC task order award, to Northrop
Grumman to allow Northrop Grumman to establish eTS data exchange capabilities
• All agency-specific business rules and policies that are compatible with the functionality of
GovTrip as delivered
• Traveler profiles for all users involved in IOC including the establishment of all classes of
user role accounts and permissions
• Agency and/or subordinate organization configuration basic business rules and exception
procedures, approval and routing chains, agency-specific supplier designations, and
agency-specific messages and warnings
• Access to existing TMC services and future TSS services

• WBS 6.0 Training The IOC Agency will agree, in its task order, to make available accordance with the GovTrip
Training schedule all agency users involved in the IOC effort

C-51
 GSA Contract GS-33F-0018-N

Table 8. Government Obligations (concluded). In order for Northrop Grumman to meet certain performance goals, the
Government must perform its part on time.

WBS Element Government Obligations

• WBS 1.0 Program Management Government comments on all deliverables are due to Northrop Grumman within ten (10) days
• WBS 1.9 Deliverables of delivery

• WBS 2.0 IOC System Agency eTS transition manager, travel manager, coordinators, administrators, and other
• WBS 4.0 Implementation necessary personnel will be available to make timely decisions in accordance with the
• WBS 6.0 Training schedule specified in the task order

• WBS 2.0 IOC System Agency supports the implementation schedule and process with required information and data
• WBS 4.0 Implementation in accordance with the schedule specified in the task order
• WBS 6.0 Training

• WBS 2.0 IOC System If the agency selects a TMC other than Northrop Grumman’s, then the TMC must be capable
• WBS 4.0 Implementation of interfacing and integrating with the GovTrip System to the level specified and in accordance
• WBS 5.0 Non-Self-Service Reservations with the schedule established in the task order.
and Fulfillment
• WBS 5.1 Standard Reservations and
Fulfillment
• WBS 5.2 On-Site Reservations and
Fulfillment
• WBS 7.0 Customer Support
• WBS 2.0 IOC System Agency’s that require on-site implementation personnel will, at the task order level, agree to
• WBS 3.0 FOC System provide any on-site implementation personnel with access to the facility, and be provided
• WBS 4.0 Implementation typical office support (desk, chair, phone, utilities, meeting area, and access to a fax and
• WBS 6.0 Training copier)

• WBS 4.0 Implementation Government comments on the Implementation Report are due to Northrop Grumman within
ten (10) days of delivery
• WBS 2.0 IOC System The agency is responsible for translation of the EAI standard eTS output to their legacy
• WBS 4.0 Implementation automation systems

• WBS 6.0 Training Agency travelers shall make a good faith effort to use the on-line help tools and web-based
• WBS 7.0 Customer Support training prior to placing calls to the help desk and the agency maintains a sustain -training
program.

APPENDIX A
DEFINITIONS

Amended Voucher: An amended voucher is a re-
vised version of a voucher already prepared and/or
submitted, but not yet paid. The amended voucher
is substituted for the original voucher and only the
amount claimed on the amended voucher, if proper
and correct, is paid.
Blanket Travel Authorization: A continuing
travel authorization issued to a traveler who regu-
larly and frequently makes trips away from his/her
official duty station within certain geographical
limits over a specified period of time (normally 1
year or less) in the performance of assigned duties.
Includes unlimited-open and limited-open travel
authorizations as defined in the FTR.
Business Reference Model (BRM): A function-
driven framework for describing the business op-
erations of the Federal Government independent of
the agencies that performs them. It comprises 24
specific agencies in the context of the business
operations that it describes. Federal agencies iden-
tified in the BRM and their mappings to the busi-
ness operations may be found on the web at
http://www.feapmo.gov/resources/
fea_brm_agency_mappings_rev_1.pdf.

C-52
 GSA Contract GS-33F-0018-N
Common Carrier: Private sector suppliers of air,
rail, ship, or bus transportation.
Configurability: The capacity to accommodate
variations to processes, business rules, routing,
approvals, feature access, system messages, etc.,
within the limits of specified requirements and
objectives without the need for programming
changes in automated systems. A configurable
solution must provide a user interface that enables
administrators to configure agency-specific details
without the need for programming knowledge.
Continental United States (CONUS): The 48 con-
tiguous States and the District of Columbia.
Digital Signature: A secure electronic signature
that uses encryption and passwords to authenticate
and protect the integrity of the signature of the
party who signed a message or document. A digi-
tal signature is one type of the more broadly de-
fined electronic signatures that can be used to au-
thenticate the identity of the sender of a message
or the signer of a document, and to ensure that the
original content of the message or document that
has been sent is unchanged. Digital signatures are
easily transportable, cannot be imitated by some-
one else, and can be automatically time-stamped.
They are also used to detect unauthorized modify-
cations to data and provide nonrepudiation; i.e.,
the ability to prove to a third party that a specific
signatory generated the signature on a message,
document, or transaction.
Direct Billed: Negotiated agreement with a travel
supplier (e.g., lodging provider, airline, and/or car
rental agency) who agrees to bill directly to an
agency for payment. These expenses will not be
claimed for reimbursement on the employee’s
travel voucher. Also includes Online Payment and
Collection (OPAC) billings from other Federal
agencies, such as Department of State for TDY
travel of employees stationed overseas.
eAuthentication Gateway: The Electronic Authen-
tication (eAuthentication) Gateway is a Federal
web service or component that will provide valida-
tion for multiple forms of identification creden-
tials, including public key infrastructure (PKI) -
based certificates for access to online Government
information systems for both citizens and Federal
employees. It will provide authentication and veri-
fication for all E-Gov initiatives. The eAuthentica-
tion Gateway will provide a common way to de-
termine and validate “trusted” credentials,
including common rules for agreements between
C-53
the Gateway, agencies, and credential providers.
An interim eAuthentication Gateway is in opera-
tion and is expected to be available for use with
the eTS at the time of the eTS contract award. The
interface to the interim Gateway is documented in
the eAuthentication Concept of Operations
(CONOPS) which may be found at
http://www.cio.gov/eauthentication. The final
eAuthentication Gateway will be based on open
system standard security protocols and is expected
to be operational in September 2003, with inter-
face standards/specifications published on the
website 60 to 90 days earlier.
Electronic Data Interchange (EDI): A common
method of electronic exchange of routine business
transactions across networks within and between
government and industry. EDI data is formatted in
standardized transaction sets established standards
committees that work to include appropriate trans-
actions within the EDI body of standards. EDI
transactions include documents such as purchase
orders, invoices, inquiries, planning, acknowl-
edgements, pricing, order status, scheduling, test
results, shipping and receiving, payments,
financial reporting, etc.
Electronic Signature: An electronic sound,
symbol, or process used to sign an electronic
transaction. Examples of electronic signature
technologies include Personal Identification
Numbers (PINs), user identities and passwords,
digital signatures, digitized signatures, and
hardware or biometric tokens. Some of the
government documents citied herein use the terms
“electronic signature” and “digital signature”
interchangeably. In security terminology, however,
electronic signature is more broadly defined than
digital signature. All digital signatures are
electronic signatures, but the reverse is not true. The
eTS requires a digital signature to support
encryption, non-repudiation, data integrity, etc.
Consequently, for the purposes of this PBWS and
the eTS, the term “electronic signature” shall be
taken to mean “digital signature” as defined herein.
Enterprise Application Integration (EAI): A
process and set of functionalities to provide the
unrestricted sharing of data and business processes
throughout systems or data sources within an
enterprise. Simply stated, EAI platforms schedule,
translate, and move data between systems in
accordance with business rules established within
the platform. EAI streamlines processes and
 GSA Contract GS-33F-0018-N
interfaces to keep all the elements of an information
enterprise interconnected.
Full Operational Capability (FOC): The point at
which eTS end-to-end travel management
functionality has been established and is
operationally available for Governmentwide
adoption. It includes meeting all requirements
specified within this PBWS and all other eTS
requirements incorporated in the Contractor’s
Performance Based Work Statement (PBWS),
having passed all IV&V tests including remediation
and retest as required, and having been granted
Authority to Operate from the GSA Designated
Approving Authority (DAA).
General Support Systems: An interconnected set of
information resources under the same direct
management control which shares common
functionality. For example, a Local Area Network
(LAN) including smart terminals that supports a
branch office, an agency-wide backbone, a
communications network, a departmental data
processing center including its operating system
and utilities, a tactical radio network, or a shared
information processing service organization.
Normally, the purpose of a general support system
is to provide processing or communications
support.
Global Distribution System: A computer
reservation service/system (CRS), typically owned
jointly by airlines or travel suppliers, that includes
reservation databases for a large number of
international airlines, rail carriers, lodging
providers, rental car agencies, etc. GDSs are used
by travel agencies and Travel Management
Centers (TMCs) to reserve worldwide travel
accommodations for their customers.
Government Contractor-issued Individually
Billed Charge Card: Also referred to as an
individually billed account,. This is a charge card
issued under a Government contract to authorize
Federal employees to pay for official travel and
transportation expenses for which the charge card
contractor bills the employee directly. Official
travel expenses charged to an individually billed
account are claimed for reimbursement or split
disbursement by the traveler. Split disbursement
payments are made directly to the charge card
contractor.
Government Contractor-issued Centrally Billed
Charge Card/Account: Also referred to as a
centrally billed account. This is a charge card or
C-54
account issued under a Government contract and
established by an agency/organization to pay for
official travel expenses across the agency/
organization, which may be a card/cardless account.
Official travel expenses charged to a centrally billed
account are not claimed for reimbursement by the
traveler. Payments are made directly to the charge
card contractor by the agency/organization.
Government Transportation Request (GTR)
(Standard Form 1169): A Government document
used to procure common carrier transportation
services. The document obligates the Government
to pay for transportation services provided.
Official transportation acquired via GTR is not
claimed for reimbursement by the traveler.
Payment is made directly to the carrier or its agent.
Refer to FTR 300-3.1.
Integration Agreement: Also referred to as an
Interface Agreement. This document formalizes an
agreement between the eTS Contractor and a
Federal agency about the parameters of inbound
and outbound data exchange between the agency’s
business systems and the eTS. It addresses data
format(s), translation, scheduling, access, testing,
transmission, security requirements,
responsibilities, points of contact, etc., associated
with eTS data exchange.
Invitational Travel: Authorized travel of
individuals either employed not employed (under
5 U.S.C. 5703) intermittently in the Government
service as consultants or experts and paid on a
daily “when actually employed” basis and for
individuals serving without pay or at $1 a year
when they are acting in a capacity that is directly
related to, or in connection with, official activities
of the Government. Travel allowances authorized
for such persons are the same as those normally
authorized for employees in connection with TDY
travel.
Initial Operational Capability (IOC): IOC
represents the first step in demonstrating
operational capability of the eTS. It is a limited
duration implementation at the first ordering
agency for each awardee that facilitates the
establishment of eTS Full Operational Capability.
As defined herein, IOC involves a specified
minimum number of travelers and transactions,
specific implementation and operational support
activities, eTS configuration requirements, and the
establishment of data exchange capabilities.
 GSA Contract GS-33F-0018-N
Local Travel: Travel within the vicinity (as defined
by departmental or agency regulations) of an
employee’s designated official duty station for
which taxi fares, mass transit fares, privately owned
vehicle (POV) mileage, and other miscellaneous
expenses incurred while performing official
business not in conjunction with TDY travel may
be claimed.
Major Applications: A use of information and
information technology to satisfy a specific set of
user requirements that requires special management
attention to security due to the risk and magnitude
of harm resulting from the loss, misuse or
unauthorized access to or modification of the
information in the application. All applications
require some level of security, and adequate
security for most of them should be provided by
security of the general support systems in which
they operate. However, certain applications,
because of the nature of the information in them,
require special management oversight and should
be treated as major.
Mobile Code: A software that is transmitted across
a network from a remote source to a local system
and is then executed on that local system (PC,
PDA, mobile phone, etc.), often without explicit
action or permission on the part of the user.
Mobile code differs from traditional software in
that it need not be installed or executed explicitly
by the user. Mobile code is sometimes referred to
as downloadable code or active content.
Non-Federally Sponsored Travel: Payment from
a non-Federal source for travel, subsistence, and
related expenses with respect to the attendance of
a Government employee in a travel status and/or
the accompanying spouse of such employee when
applicable at a meeting or similar function relating
to the official duties of the employee. Refer to
FTR Chapter 304.
Non-Federal Source: Any person or entity other
than the Government of the United States. The term
includes any individual, private or commercial
entity, nonprofit organization or association or
international or multinational organization
(irrespective of whether an agency holds
membership in the organization or association), or
foreign, state, or local government (including the
government of the District of Columbia). Refer to
FTR Chapter 304.
Non-Self Service Transaction: As used in this
contract, it is one in which the services of a
C-55
customer support agent are used explicitly for
making and/or fulfilling travel arrangements. The
use of eTS customer support services for technical
support or assistance in completing self service
actions shall not constitute a non-self service
transaction.
Official Duty Station: The official duty station of
an employee or invitational traveler (see FTR §
301-1.2) is the location of the employee’s or
invitational traveler’s permanent work assignment.
The geographic limits of the official duty station as
defined in the FTR are provided below. Agencies
may, however, define a radius broader than the
official station in which per diem or actual expenses
will not be authorized.
1) For an employee:
a) The corporate limits of the city or town
where stationed or if not in an incorpo-
rated city or town; and
b) The reservation, station, or other estab-
lished area (including established subdivi-
sions of large reservations) having definite
boundaries where the employee is
stationed.
2) For an invitational traveler:
a) The corporate limits of the city or town
where the home or principal place of
business exists or if not in an incorporated
city or town; and
b) The reservation, station, or other
established area (including established
subdivisions of large reservations) having
definite boundaries where the home or
principal place of business is located.
Operational Security (OPSEC): A process
designed to disrupt or defeat the ability of an
adversary to exploit sensitive departmental
activities or information and to prevent the
inadvertent disclosure of such information.
Outside the Continental United States
(OCONUS): Any location outside the 48
contiguous States and the District of Columbia.
Passenger Name Record (PNR): A file in a
Global Distribution System or Computerized
Reservation System that contains all the pertinent
information relating to a specific reservation.
 GSA Contract GS-33F-0018-N
Per Diem Allowance: A daily payment for
lodging, meals, and related incidental expenses
used instead of reimbursement for actual expenses.
Permanent Change of Station (PCS): The
relocation of an employee to a new official station
or post of duty for permanent duty.
Post of Duty: An official station outside CONUS.
Prompt Payment: As it relates to reimbursing
employees for travel expenses, Section 301-52.17
of the Federal Travel Regulation states that
agencies are required to reimburse employees
within 30 calendar days after a proper travel claim
is submitted to the agency’s designated approving
office or an interest penalty is owed. As it relates to
reimbursing contractors for services performed, the
Prompt Payment Act at 31 U.S.C. 3903 governs.
Reclaim Voucher: A second or subsequent voucher
submitted by a traveler seeking reimbursement of
an expense previously denied or suspended. The
reclaim voucher must be accompanied by an
itemization of expenses, required receipts (provided
that an agency does not already have a copy(s)), a
statement signed by the traveler, or other evidence
of the validity and correctness of the amount
claimed.
Self Service Transaction: Travel reservations and
fulfillment are initiated and completed online; i.e.,
without direct contact between the traveler or
travel arranger with a customer support agent for
the explicit purpose of making and/or fulfilling
travel arrangements.
Split Disbursement: Allocation of payment for
reimbursable travel expenses where the traveler
designates applicable amounts to be disbursed to
multiple accounts, e.g., a Government contractor
issued individually or centrally billed charge card,
a GTR, and/or directly to the traveler.
Standard Data Output: As used in this PBWS,
standard data output refers to travel information in
EDI, UDF, XML, or other Internet standards-
based data formats, made available by the eTS for
exchange with other Government or commercial
business systems.
Supplemental Voucher: A second or subsequent
voucher submitted by a traveler to claim
reimbursement of expenses not previously claimed
for a trip for which reimbursement has already
been made or claimed. Itemization of expenses or
C-56
receipts is required as they would be if the
expenses were claimed on the original voucher.
Temporary Change of Station (TCS): The
relocation of an employee to a new official station
for a temporary period (not less than 6 months, nor
more than 30 months) while the employee is
performing a long-term assignment and subsequent
return of the employee to the previous official
station upon completion of that assignment.
Temporary Duty (TDY) Travel: Travel at a place,
away from an employee’s official duty station,
where the employee is authorized to travel.
Temporary Duty (TDY) Location: A place, away
from an employee’s official duty station, where
the employee is authorized to travel.
Travel Advance: Prepayment for estimated cash
transaction travel expenses paid to an employee.
Travel Authorization: Written approval to travel
on official business. There are three basic types of
travel authorizations:
1) Unlimited Open—An authorization allowing
an employee to travel for any official purpose
without further authorization.
2) Limited Open—An authorization allowing an
employee to travel on official business without
further authorization under certain specific
conditions, i.e., travel to specific geographic
area(s) for specific purpose(s), subject to trip
cost ceilings, or for specific periods of time.
3) Trip-by-trip—An authorization allowing an
individual or group of individuals to take one
or more specific official business trips, which
must include specific purpose, itinerary, and
estimated costs.
Travel Planning: The process of researching
flight and rail schedules, lodging alternatives, and
other travel arrangements for the purpose of
establishing a tentative travel itinerary, travel cost
estimate, travel plan, etc., to support the planning
and authorization of official Federal travel. It does
not include the booking of travel reservations and
does not generate a transaction fee in accordance
with Section B of this contract.
Traveler Profile: A record of information about a
traveler provided by Federal agencies and/or their
employees that contains basic identifying
elements, including, but not limited to, the
traveler’s name, e-mail address, agency name,
 GSA Contract GS-33F-0018-N
work address, phone numbers, charge card
information (name(s), number(s), and expiration
date(s) of cards), accounting information, travel
preferences, passport and/or visa numbers,
frequent traveler memberships, etc.
Travel Management Center (TMC): A company
under contract with an agency to arrange travel
services for Federal employees on official travel,
including tickets and transportation, and
reservation of accommodations.
Travel Voucher: A digitally signed claim for
reimbursement of expenses incurred in the
performance of official travel.
Temporary Duty (TDY) Travel Voucher: Claim
for expenses incurred in connection with travel
away from an employee’s official duty station,
where the employee is authorized to travel.
Local Travel Voucher: Claim for expenses,
including taxi and mass transit fares, privately
owned vehicle (POV) mileage and other
miscellaneous expenses incurred while performing
official business within the vicinity of an
employee’s designated post of duty, not connected
with TDY travel.
User Defined File (UDF): A file format defined
by the military as part of the Federal
Implementation Guideline for Electronic Data
Interchange (EDI). The format defines EDI
transaction sets that comply with the American
National Standards Institute (ANSI) Accredited
Standards Committee (ASC) X12. Examples of
transactions sets are 810 (invoice), 820 (payment
order), and 810T (travel invoice).
Web Portal: A web site that offers a broad array of
resources, services, and content (e.g., e-mail,
forums, search engines, links, etc.) and which
typically can be personalized to the viewers
preferences. A web portal is commonly referred to
simply as a portal.
PRICING DEFINITIONS
eTravel Service (eTS): The services and support
involved in providing an integrated, web-based,
end-to-end travel management service for use by
Executive Branch departments and agencies of the
Federal Government and other authorized users.
Initial Operational Capability (IOC): Represents
the first step in demonstrating operational
capability of the eTS. It is a limited duration
implementation at the first ordering agency for
each awardees that facilitates the establishment of
C-57
eTS Full Operational Capability. As defined
herein, IOC involves a specified minimum number
of travelers and transactions, specific
implementation and operational support activities,
eTS configuration requirements, and the
establishment of data exchange capabilities.
Non-Self Service Transaction: Where the services
of a customer support agent are used explicitly for
making and/or fulfilling travel arrangements. The
use of eTS customer support services for technical
support or assistance in completing self service
actions shall not constitute a non-self service
transaction.
Task Order: An order for services placed against
any contract resulting from the solicitation
#FBGT-CD-030001-N. For the purposes of this
contract, the terms “task order” and “delivery
order” shall be considered synonymous.
Transaction A - Air and/or Rail Ticket with or
without Lodging and/or Car Rental Reservations:
Transaction A fee applies for all arrangements and
reservations related to one itinerary for which an
air or rail ticket is issued. The fee includes making
and changing arrangements (air/rail, lodging,
and/or car rental) for one or multiple locations.
The fee may only be charged at time of ticket
issuance and is not required to be refunded if the
travel is subsequently cancelled. The transaction
fee covers the processing of refunds or credits for
unused tickets. An additional transaction fee may
be incurred if changes in the itinerary require the
issuance of a new ticket. The contractor shall not
charge a fee for cancellations made prior to
issuance of tickets. Activities that do not result in
the issuance of a ticket (e.g., research of travel
arrangements, changes to existing arrangements
prior to ticket issuance, air and/or rail reservations
for which tickets are not issued, etc.) shall not be
considered Type A transactions.
Transaction B - Lodging and/or Car Rental
Reservations: Transaction B fee applies for all
arrangements and reservations related to one
itinerary for which an air or rail ticket is not
issued. The fee includes making and changing
lodging and/or car rental arrangements for one or
multiple locations when air or rail transportation is
not included in the itinerary. Research of travel
arrangements and activities that result in changes
to or cancellation of lodging and/or car rental
reservations prior to the check-in or pickup date
shall not be considered Type B transactions.
 GSA Contract GS-33F-0018-N

Travel Voucher: A digitally signed claim for
reimbursement of expenses incurred in the
performance of official travel. For the purposes of
pricing, the travel voucher includes travel planning
authorization (see Section 5.4), travel advance (see
Section 5.8), and travel voucher (see Section 5.9)
functionalities described in this contract.
Local Travel Voucher: Claim for expenses,
including taxi and mass transit fares, privately
owned vehicle (POV) mileage, and other
miscellaneous expenses incurred while performing
official business within the vicinity of an
employee’s designated post of duty, not connected
with TDY travel.
Paper Ticket: A paper instrument that identifies
the transportation to which the traveler is entitled.
For the purposes of this contract, paper ticket
refers to all physical documents (e.g., flight
coupon, passenger receipt, detailed itinerary, etc.)
related to a single travel itinerary.

C-58