RFP_Attachment_H_-_Data_Sources_Inclusive_of_Amendment_1.pdf

QMAC-CY-140001-N

Attachment H – Data Sources – Page 1

ATTACHMENT – H - Data Sources

Introduction

The Contractor shall import, aggregate, standardize, and store data from multiple source types which include, but are not limited to: TMC data, ETS2 data, ARC data, charge card data (SmartPay), supplier direct data (air, car, hotel), benchmark data, reference data, and TMIS 1.0 data archives. This attachment provides the Contractor with a description and the corresponding specifications (when available) for each data source listed above.

The estimates provided herein are estimates only, and are based on history where available. They are not guarantees of future volume under this effort.

Many, but not all, of the data sources are under contract with the Federal Government. As a result, this acquisition could cause an organizational conflict of interest because performance of TMIS 2.0 requires use of potentially proprietary information from other travel related contractors to perform the work on this contract. Unfettered use of this information could confer an unfair competitive advantage to the TMIS contractor. As a result, please reference Section H for the Conflict of Interest clause that will apply to this effort.

1. Travel Management Center (TMC) Data

A TMC or travel agency provides the final booking and ticketing service. TMC data is travel reservation and/or ticketed data. TMC data is also referred to as PNR (Passenger Name Record) data.

It is expected that the feed will be received from 20-30 TMCs weekly. TMIS 1.0 currently receives data feeds from 22 TMCs. These TMCs utilize 7 different commercial back-office systems which are, Agresso (42%), Decision Source (<1%), GlobalMax (<1%), Globalware (2%), Glory (32%), TRAMS (24%), Travcom (<1%). The Figures in parenthesis are the approximate % of transactions currently received from each back office system, and is subject to change.

This data may also be received from other sources such as ETS. The Contractor may propose an alternative source for this reservation data providing that the data quality meets or enhances the level received via standard TMC feeds, for example, better refund and exchange data.

The format of feed is currently CSV/text delimited/Excel files. The format of the data feed varies among TMCs. The data feed may consist of multiple data files, e.g. air reservation, hotel reservation, invoice files.

Estimated annual PNR volume for the current TMCs is 2.5 – 3.0 million, based on FY12 and FY13 PNRs processed.

Each PNR record may contain over 100 data elements.

2. E-Gov Travel Service 2 (ETS2) Voucher Data

Attachment H – Data Sources – Page 2

ETS2 is an secure web-based end-to-end travel management service that includes: travel planning, travel reservation, authorization, vouchering, and reporting. ETS2 is used by civilian federal agencies.

There are two vendors providing ETS2 services, and hence up to two feeds are expected. The format of the feeds would be different from each ETS2 vendor.

The format of the data feed is expected to be CSV/excel and/or XML. The expected frequency of ETS2 data feed is weekly.

It is estimated that ETS2 will process approximately 2.0 – 2.5 million vouchers per year. ETS2 contractors are required to collect at least 457 data elements that may all be incorporated into ETS2 Voucher data.

It is expected that only approximately 200 of these data elements will be needed for reporting.

3. Airline Reporting Corporation (ARC) Data

ARC (www.arccorp.com) provides settlement services for U.S. flag carriers and many international carriers, but not for all carriers. For example, Southwest airlines is a large carrier that does not use ARC.

The ARC data feed only covers air and some rail travel. This data feed includes ticket sales for virtually all official government travel.

There is a single data feed. The expected frequency of ARC data feed is monthly.

The format of data feed is currently CSV/excel files.

The annual transaction volume is expected to be in the range of 3.5 – 4.5 million. The number of data elements per record is expected to be over 20.

4. Charge Card Data (GSA SmartPay)

GSA SmartPay (SP) is the Government’s charge card program. There are two types of travel charge card accounts, known as Centrally Billed Account (CBA), and Individually Billed Account (IBA). Like ARC data, this data feed includes SP travel transactions for all branches of government.

There are currently three (3) banks (Citibank, JPMorgan Chase, and US Bank) providing SP card services to the Government. The Contractor will import a single SP data feed directly from the SP PMO. The format of the data feed may vary among banks.

The format of SP data feed generally is CSV/text delimited/excel files. The expected frequency of SP data feed is Daily.

Estimated annual transaction volume for SP data feed is about 9.0 million, and each transaction is expected to have up to 100 data elements.

5. Supplier Direct Data

Travel Service Suppliers (such as airlines, hotels, rental car companies etc.) are another source of travel data. This data provides detailed and/or supplemental information on the service transaction that the supplier delivered to the traveler. Additional information is expected to be available with the service suppliers. For example, an airline could provide details on ancillary services purchased; a hotel could http://www.arccorp.com/

Attachment H – Data Sources – Page 3 provide detailed folio data for a stay; a car rental company could provide data on type of vehicle (size, fuel type etc), mileage, additional charges such as GPS rental etc.

It is expected that supplier direct data will be provided in industry standard formats (e.g. csv, text delimited, xml), however, data elements will differ among industry and suppliers. The Government intends to order supplier data by industry type (e.g. air, hotel, rental car). When proposing a price for this CLIN, the Offeror should propose a price based on their commercial experience.

6. Reference Data

Reference data is needed for analyzing trends and measuring policy and program performance. For example, Government per diem rates are compared against actual lodging expenses to determine variances to per diem. Reference data is available from public sources, both government and commercial.

GSA will provide access to annual lodging per-diem rates table, as well as airline City-Pair Program contract fares. This data is also publically available on GSA website, www.gsa.gov.

The Contractor is expected to collect and maintain other reference data such as airlines class of service codes (which change frequently by individual airline), airline fare basis codes, mileage information between a city-pair, city-county/urban area, hotel chain rollup, geographic city/state/country rollup, city name normalization, hotel name normalization, hotel property to parent rollup, car class rollup, car rental city rollup (varies by vendor), airport to city rollup, etc.

In addition, the Government will provide summary benchmark data on air, lodging, and rental car average rates to be integrated into TMIS 2.0.

Reference data will require periodic updates, the frequency of which will depend on the particular data set.

7. TMIS 1.0 Data Archives

TMIS 1.0 Data Archives refers to the data extract of current and expiring MIS service. This extract will include TMC feed for civilian agencies starting from FY08 till present.

There will be a single, one-time data delivery from the Government.

The format of TMIS 1.0 archive will be CSV/excel files.

The expected number of records is in the range of 21.0 – 25.0 million, and total number of data elements is approximately 200 per record.

http://www.gsa.gov/