Attachment 6 CTO Data Requirements 22DEC10.doc

Attachment 6

Commercial Travel Data Requirements

CTO Data Requirements Document

December 22, 2010

Table of Contents

3I.

Travel Daily

5A.

Auto-Queuing Instructions

51.

Sabre

72.

Worldspan

93.

Galileo

114.

Apollo

145.

Amadeus

166.

Special Characters

17B.

Full Listing of PNR Elements

22C.

Instructions for Additional Required Elements

42II.

Premium Class Travel Validation

46III.

CTO Monthly

I. Travel Daily The Government shall utilize branch/bridge access and live PNR queue transfer to read and capture standard PNR data (i.e. air, car, and lodging) and the data elements provided by the Contractor as outlined in the below requirements.

The following data elements, in addition to those found in a standard PNR, are required. The table in Section 1C outlines those data elements.

All reason codes and class of service codes shall be applied at the segment level. These reason codes (segment level entry examples provided in Section 1C) shall be applied based on the class of service and/or the applicable reason code for each PNR air segment. For example; the traveler is ticketed at a coach fare basis HUAUP; however, the passenger is seated in First Class. Using this example, the contractor shall provide the reason code “F” for those segments where the traveler was seated in First Class.

All PNRs shall be quality checked for accuracy. Data Quality issues will be communicated to the Contractor through non-GDS means. The Contractor will be notified on a daily basis of any records that contained data quality issues in the previous 24 hours. The Contractor will have access to a cumulative list of data quality issues on a real time basis. The Contractor will be expected to resolve any data quality issues with 5 business days of notification of the issue.

With the exception of the following requirements, the Contractor is not required to standardize PNR data placement and is expected to use published GDS passive entry standards for non-bookings within the PNR. However, The Government reserves the right to request the Contractor provide a mapping of PNR data placement and how the data is used for each location under the task order.

Requested GDS entries have been provided in these instructions. These are preferred entries that are used for PNR collection directly from the GDS and may or may not transfer to your back office system. You may elect to use an alternate entry (without modifying the DTMO field identifier, i.e., DTMO5), but must submit the proposed entry to the DTMO for approval prior to implementation.

The DTMO will be tracking non-official travel, to include Leisure In Conjunction with Official Business (LICWO) travel, contractor support and any other non-official travel when airline tickets are issued through a contracted Commercial Travel Office (CTO). In order to include PNRs that are solely non-official itineraries into the Travel Daily workflow, the DTMO is requiring the ability to identify a PNR that is solely a non-official PNR. The following two options are provided:

1. Use the standard GDS customer identifier (i.e., Sabre/Apollo DK, Worldspan CA) field for non-official PNRs using the naming string “UNOFFICIAL”.

2. Understanding the influence of the CTO back office with respect to remark placement, alternatively, the CTO may propose remark placement anywhere in the native portion of the PNR that would again include the naming string “UNOFFICIAL”. Examples could be:

Sabre: 5.UD100*UNOFFICIAL, 5.Z*UD12-UNOFFICIAL Worldspan: 5.Z UNOFFICIAL, 5.UNOFFICIAL The DTMO shall establish a unique alpha identifier for each site under this contract. The unique alpha identifier shall not exceed 30 characters. The Contractor shall submit, via email, a Microsoft Excel spreadsheet to the DTMO COR 5 days after award of the task order. Contractors holding multiple contracts may submit one consolidated spreadsheet. The Excel spreadsheet shall record one row for each site serviced under the contract / task order, to include on-site staffed, subcontractor, and off-site support such as call centers and after hours emergency service. Each site will include the following data elements.

CTO

CTO_ALIAS (DBA)

SUB_CTO (If a sub contractor is used) TRAVEL_AREA (e.g.; DTA 07; TA 060)

START_DATE

END_DATE

AGREEMENT_NUMBER (Contract Number)

DTMO COR

GDS

PCC or SID

SITE_NAME

SITE TYPE (S=Staffed, T = Unstaffed (STP), C = Call Center)

ARC/IATA NUMBER

ADDRESS1

ADDRESS2

CITY

STATE

COUNTRY

POSTAL_CODE

CTO_DAYTIME_PHONE

CTO_EMERGENCY_PHONE

An example Travel Daily Spreadsheet is provided in Attachment 12. The DTMO shall populate the unique alpha identifier and return the spreadsheet to the Contractor within 5 days of receipt.

A. Auto-Queuing Instructions

The following GDS features are supported by the Government:

1. Sabre

These instructions apply to Abacus as well.

Official Website: http://www.sabretravelnetwork.com Support: http://eservices.sabre.com

Branch Access: The Contractor shall establish branch access between the DTMO PCC and each of the Contractor’s PCCs which supports the creation, modification, cancellation, and ticketing of DoD PNRs to include official (i.e. CTO Assist (i.e. Traditional) and DTS) and non-official (i.e. LICWO, Contractor Support, etc.) travel arrangements. . The Contractor shall ensure the branch access includes PCCs designated for on-site staffed offices and off-site support/fulfillment such as call center service, emergency after-hours support, sub-contractor support, virtual agents, quality control, satellite, etc. Additionally, the Contractor shall ensure the branch access provides the Government with capability to view, sweep, and queue place all DoD PNRs. The following Sabre GDS formats assist in these requirements:

· Establishing branch access and creating an automated queue drop requires supervisory access: >SI9

· To open Sabre Branch Access: >W/TAAXXXX‡BEZ7C (XXXX denotes CTO PCC) Note: If utilizing Global Branch Access, the Contractor shall ensure the Government has access in accordance with the requirements above. If Global Security products are used – additional permissions should be included for the viewership by the Government PCC.

Queue Placement: The Contractor shall utilize Sabre’s automated queue drop functionality to queue place all newly created, modified, cancelled, and ticketed PNRs to a designated queue in the Government’s PCC. The automated queue drop functionality places PNRs on a designated queue after End Transaction (ET). This eliminates the need to remember to queue a PNR each time a PNR is created, modified, cancelled, and ticketed.

To activate a new queue or assign the functionality to an existing queue:

· Update your Sabre TJR to include the designated queue to auto-queue all created, modified, cancelled, and ticketed PNR activity: >W/KQPA‡200 (200-assumed queue)

· All records using this queue feature will be placed on the PCC in which the TJR is associated. Turn on queue forward for this queue to the assigned government PCC/queue combination.

Passive Segments: The Contractor shall utilize the following Sabre standard formats when entering passive segments into DoD PNRs:

1. Air

Manual Entry: 0UA1192Y19JUNDENBWIYK1

Sabre Response: 1 UA1192Y 19JUN 5 DENBWI YK1/E

2. Hotel Manual Entry: 0HHTHIGK1JFKIN07JUL-OUT08JUL/ HIHOLIDAYINN/DBLB/65.00USD/G/SI-¤1900 VAN WYKE‡S OZONE PARK NY 10405 ‡FONE 212-555-1957¤ REQUESTED SUITE/CF-62FE77

Sabre Response: 1 HHT HI 07JUL T GK1 JFK/OUT08JUL/HI HOLIDAY NN/DBLB/65.00U SD/G/SI-¤1900 VAN WYKE‡S OZONE PARK NY 10405‡FONE 212-555-1957¤ REQUESTED SUITE/CF-62FE77-

3. Car

Manual Entry: 0CARZEGK1LAX24JUN-26JUN/ECAR/CF-123456

Sabre Response: 1 CAR ZE 24JUN W GK1 LAX/26JUN/ECAR/CF-123456-

4. Rail

Manual Entry: 0RAL2VGK1MIAATL3AUG-LV-9A/AR-3P/NA-TRAIN 66/SI-CF

Sabre Response: 1 RAL 2V 03AUG M GK1 MIAATL/LV-9A/AR-3P/NA-TRAIN 66/SI-CF

2. Worldspan

Official Website: http://www.worldspan.com/ Support: http://support.worldspan.com

Bridge Access: The Contractor shall establish bridge access between the DTMO SID(s) and each of the Contractor’s SIDs which supports the creation, modification, cancellation, and ticketing, of DoD PNRs to include official (i.e. CTO Assist (i.e. Traditional) and DTS) and non-official (i.e. LICWO, Contractor Support, etc.) travel arrangements. The Contractor shall ensure the bridge access includes SIDs designated for on-site staffed offices and off-site support/fulfillment such as call center service, emergency after-hours support, sub-contractor support, virtual agents, quality control, etc. Additionally, the Contractor shall ensure the bridge access provides the Government with capability to view, sweep, and queue place all DoD PNRs. The following Worldspan GDS formats, meet these requirements:

· To establish Worldspan Bridge Access:

1. >KYAOU0

2. Grant permissions by changing the N to Y next to the following areas:

· ACCESS PNRS (Y)

· ACCESS QUEUES (Y)

· ALLOW QEP/QEM (Y)

Queue Placement: The Contractor shall utilize Worldspan QTRAC functionality to queue place all newly created, modified, cancelled, and ticketed PNRs to a designated queue in the Government’s SID. QTRAC places PNRs on a designated queue after End Transaction (ET). This eliminates the need to remember to queue a PNR each time a PNR is created, modified, cancelled, and ticketed. Any queue and category may be used for QTRAC except system placed queues.

To activate a new queue or assign the functionality to an existing queue: (EXAMPLE ONLY)

1. Ensure you have no other queue assigned: >QTX

2. Assign QTRAC to an existing queue: >QT/45*C0

3. Remember to assign the queue if using a new queue number: >QD/45*C0

4. All newly created, modified or cancelled PNR activity would be placed on queue 45 within your SID. All PNRs from this queue will need to be forwarded to the government SID/queue combination for collection. This queue will have the queue forward setup during the implementation process and will not require manual queue forward programmatics. Please refer to your helpdesk for assistance on establishing this functionality.

Passive Segments: The Contractor shall utilize the following Worldspan standard formats when entering passive segments into DoD PNRs:

1. Air

Manual Entry: 0UA1192Y19JUNDENBWIMK1

Worldspan Response: 1 UA 116Y 15JUN LAXORD MK1 100P 659P /O E

2. Hotel

Manual Entry: HN@MK*MOB10JAN12JAN2/C-QI/H-QUALITY INN AIRPORT/R-A2DRAC/SI-@123 MAIN STREET$ANYTOWN USA 12345$PHONE 123-123-1234@/RT-USD9900/RD-DELUXE ROOM WITH KING BED/CF-231/BC-R Worldspan Response: 1 HTL 1P MK01 MOB IN10JAN OUT12JAN -QI QUALTY INN AIRPORT/NP-2/R-A2DRAC/RT-USD 99.00/RD-DELUXE ROOM WITH KING BED/BS-1P/BC-R/SI-@123 MAIN STREET$ANYTOWN USA 12345$PHONE 123-123-1234@/CF-231

3. Car

Manual Entry: CRN@MKLAX13MAY17MAY/CZI/VECAR

Worldspan Response: 1 CCR ZI MK01 LAX 13MAY 17MAY ECAR /BS-1P/CF-

3. Galileo

Official Website: http://www.travelport.com/ Support: http://support.galileo.com/sgc/

Branch Access: The Contractor shall establish branch access between the DTMO PCC and each of the Contractors PCCs which supports the creation, modification, cancellation, and ticketing, of DoD PNRs to include official (i.e. CTO Assist (i.e. Traditional) and DTS) and non-official (i.e. LICWO, Contractor Support, etc.) travel arrangements. The Contractor shall ensure the branch access includes PCCs designated for on-site staffed offices and off-site support/fulfillment such as call center service, emergency after-hours support, sub-contractor support, virtual agents, quality control, etc. Additionally, the Contractor shall ensure the branch access provides the Government with capability to view, sweep, and queue place all DoD PNRs.

· To Establish Galileo Branch Access: PAPERA/7P29/203

Note: 203 is the active agreement for the appropriate level of PNR access

Passive Segments: The Contractor shall utilize the following Galileo standard formats when entering passive segments into DoD PNRs:

1. Air

Manual Entry: 0UA1192Y19JUNDENBWIBK1

Galileo Response: 1 UA 1192Y 19JUN DENBWI BK1 100P 659P TU

2. Hotel

Manual Entry: 0HHLRABK1NBO10NOV-18NOV12345A1Q-1/RT-USD55.00/CF-1234567 Galileo Result: 1 HHL CY HK1 LAX 16JUN-17JUN 1NT 95695 COURTYARD CENTURY 1APNL00 –1/RG-USD149.00/AGT99999992/G-TPSTVIXXXXXXXXX8000EXP0111/NM-WHITE SHANNON/CF-99385040*

3. Car

Manual Entry: 0CCRQSBK1CDG27NOV-28NOVSCAR/ARR-0900/DT-1700/AC-EUR

Galileo Result: 5 CAR QS BK1 CDG 27NOV – 28NOV SCAR/BS9999992/ARR-0900/DT-1700/AC-EUR

4. Apollo

Official Website: http://www.travelport.com/ Support: http://support.galileo.com/sgc/

Branch Access: The Contractor shall establish branch access between the DTMO PCC and each of the Contractors PCCs which supports the creation, modification, cancellation, and ticketing, of DoD PNRs to include official (i.e. CTO Assist (i.e. Traditional) and DTS) and non-official (i.e. LICWO, Contractor Support, etc.) travel arrangements. The Contractor shall ensure the branch access includes PCCs designated for on-site staffed offices and off-site support/fulfillment such as call center service, emergency after-hours support, sub-contractor support, virtual agents, quality control, etc. Additionally, the Contractor shall ensure the branch access provides the Government with capability to view, sweep, and queue place all DoD PNRs.

· To Establish Apollo Branch Access: PAPERA/138V/203

Note: 203 is the active agreement for the appropriate level of PNR access

Queue Placement: The Contractor shall utilize Apollo’s default queue drop functionality to queue place all newly created, modified, cancelled, and ticketed PNRs to a designated queue in the Government’s PCC. Default queue drop places PNRs on a designated queue after End Transaction (ET). This eliminates the need to remember to queue a PNR each time a PNR is created, modified, cancelled, and ticketed.

To establish an auto queue drop:

1. Contact the Apollo Help Desk (800) 762-3490.

2. Advise that you wish to establish a programmatic queue – default queue within your PCC.

3. Advise that you wish to have all newly created, modified, cancelled, and ticketed PNRs queued to the default queue/PCC combination.

4. Review your queue structure to determine the most suitable default queue. Please do not use pre-assigned programmatic queues such as:

Queue Number: Assigned For:

0 Urgent (confirmations within 24 hours) 1 General (advance confirmations) 2 Seat (alternate seat comment) 9 TAW (moved using ORB) 10 TAU (current day ticketing) 12 TL (tickler follow-up) 15 Group (C/ PNRs and GPNRs) 17 Waitlist Confirmations 18 Schedule Change (1 - 14 days from advice date) 19 Schedule Change (all travel dates) 20 Schedule Change (15 - 30 days from advice date) 22 Schedule Change (travel 31+ days from advice date) 33 Stored Pricing default 71 Interrupted Airline service 80 Waitlist Confirmations - discount fares 84 Schedule Change on UA flights with discount fares that are protected on full fares Passive Segments: The Contractor shall utilize the following Apollo standard formats when entering passive segments into DoD PNRs:

1. Air

Manual Entry: 0UA1192Y19JUNDENBWIBK1

Apollo Result: 1 UA 1192Y 19JUN DENBWI BK1 100P 659P TU

2. Hotel

Manual Entry: 0HTLZZHK1ABQ20MAY-OUT22MAY/W-HOLIDAY INN#5151 SAN FRANCISCO RD NE#ALBUQUERQUE#NM#87171#505 333-3333/**FREE FORM*** Apollo Result: 1 HTL ZZ HK1 ABQ 20MAY-OUT22MAY /W-HOLIDAY INN#5151 SAN FRANCSICO RD NE#ALBUQUERQUE#NM#87171#505 333-3333/CF-393838

3. Car

Manual Entry: 0CARZEHK1LAX5MAR-7MARICAR/CF-123456

Apollo Result: 1 CAR ZE HK1 LAX 05MAR - 06MAR ICAR/BS-XXXXXXXX/CF-12345

5. Amadeus

Official Website: http://www.amadeus.com Support: http://support.amadeus.com

BWI1S212S

BWI1S216C

BWI1S217U

BWI1S213J

Note: the Contractor shall received the applicable Government office ID upon implementation

Branch Access: The Contractor shall establish branch access between the DTMO Office ID and each of the Contractors Office ID’s which supports the creation, modification, cancellation, and ticketing, of DoD PNRs to include official (i.e. CTO Assist (i.e. Traditional) and DTS) and non-official (i.e. LICWO, Contractor Support, etc.) travel arrangements. The Contractor shall ensure the branch access includes Office ID’s designated for on-site staffed offices and off-site support/fulfillment such as call center service, emergency after-hours support, sub-contractor support, virtual agents, quality control, etc. Additionally, the Contractor shall ensure the branch access provides the Government with capability to view, sweep, and queue place all DoD PNRs.

· To Establish Amadeus Branch Access: EOU-BWI1S212D-PNOB/PNGB/CPRB/QUEB/RMOB

Note: PBOB, PNGB, CPRB, QUEB, RMOB provide the appropriate PNR access from an active Amadeus queue. All Amadeus queues shall be activated after branch access is established within the DTMO Office ID.

Passive Segments: The Contractor shall utilize the following Apollo standard formats when entering passive segments into DoD PNRs:

1. Air

Manual Entry: SSUA1192Y12OCT09DENBWIGK1/17251815/ABC123 Amadeus Result: 1 UA1192 Y 12OCT 1 DENBWI GK1 525P 615P ABC123

2. Hotel

Manual Entry: HU1AHK1SFO1SEP-2SEP/SAVOY HOTEL/CF-123456 Amadeus Result: 1 HTL 1A HK1 SFO 01SEP-03SEP/SAVOY HOTEL/CF-123456

3. Car

Manual Entry: 11ACSZELAX17JUN-2/ARR-1500/RT-6P/VT-SCAR/RQ-EUR150/CF-393983

Amadeus Result: 1 CCR ZE HK1 LAX 17JUN 19JUN SCAR/BS-XXXXXXX/ARR-03PM /RQ-EUR150/RT-06PM/CF-133344

6. Special Characters

The Government supports the following characters and translations:

Note: additional characters/translations may be added upon request

B. Full Listing of PNR Elements

This section is a listing of all elements expected in a DoD PNR, to include standard elements (highlighted in green) as well as the additional required elements outlined in Section B (highlighted in light blue). These elements are sorted by the applicable topic to which they pertain. The section of the PNR they are found in is listed in the final column.

C. Instructions for Additional Required Elements

(1)

Class of Service Code Based on inventory class, enter the code from the table below which describes the class of service booked for each air segment.

Element Capture: All transactions. At the fare basis level in the tariff, the Reservation Booking Designator (RBD) defines the cabin of service for the fare basis ticketed.

Code

Class Booked / Ticketed Reason

F

First Class

Generally the highest class of accommodation offered by the airlines in terms of cost and amenities and termed "first class" by the airline and any reservation system B

Business Class

A premium class of accommodation offered by the airlines that is higher than coach and lower than first class in both cost and amenities C

Coach

The basic class of accommodations offered to travelers regardless of fare paid. Also referred to as "tourist" or "economy class".

H

Charter

Negotiated rate to lease an aircraft or other mode of transport such as bus for the use of a group.

GDS Entries

Segment Level ~ Data to be Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO1- S1*F/S2*C/S3*F/S4*C

(Example: S1 First, S2 Coach, S3 First, S4 Coach)

Worldspan

5/DTMO/1- S1*F/S2*C/S3*F/S4*C

Apollo

[]:5DTMO1- S1*F/S2*C/S3*F/S4*C

Galileo

NP.DTMO1- S1*F/S2*C/S3*F/S4*C

RX DTMO1-S1*F/S2*C/S3*F/S4*C

(2)

Reason Code for Premium Class Travel

Must be provided when the class of service code provided is first (F) or business (B) (see field 1) When premium class travel has been booked, enter the appropriate reason code from the table below for each premium class segment.

Only enter the code on the segment(s) to which it applies.

For DTS PNRs, when the Contractor receives a request for CTO assistance to book premium class travel; the Contractor shall obtain the applicable reason code from the traveler or authorized Government Official upon receipt of the request or prior to ticketing.

Element Capture: Required if a Premium Class Travel segment is present in the PNR.

References in description refer to Joint Travel Regulations Volume 2, Chapter 2, Section 3: Commercial Air Transportation (C2204 page C2E3-1, Change 518 12/1/08)

Code

Premium Class Use Reason Code

A

Lower Class Not Available in Time (B.3.a & B.4.a.)

B

Medical (B.3.b & B.4.b.)

C

Security (B.3.c & B.4.c.)

D

Mission (B.3.d & B.4.d.)

E

Only first class provided (if highest class of service is First) / Only business class provided (if highest class of service is Business) (B.3.e & B.4.e.)

F

Non-Federal funding source (must be used in conjunction with A - E) (B.3.f. & B.4.f.)

G

Congressional Travel (must be used in conjunction with A - E) (B.3.g. & B.4.j.)

H

(Business Class Only) Foreign flag coach not adequate (B.4.g.)

I

(Business Class Only) Over 14 hours (B.4.i.)

J

(Business Class Only) Required by foreign government regulations, MOU/MOA/SOFA (B.4.k.)

K

(Business Class Only) Use of business class results in an overall savings on the trip (B.4.h.)

L

Traveler used a frequent flyer upgrade to pay the difference between YCA/lowest unrestricted coach fare and premium class travel M

Traveler self-paid the difference between YCA/lowest unrestricted coach fare and premium class travel

N

Premium class is lower than YCA and/or lower than lowest unrestricted coach fare

O

GDS/Airline automatic upgrade

GDS Entries

Segment Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO2-S1*M/S3*M

(Example: Segments 1 & 3 are premium due to medical)

Worldspan

5/DTMO/2- S1*M/S3*M

Apollo

[]:5DTMO2- S1*M/S3*M

Galileo

NP.DTMO2- S1*M/S3*M

RX DTMO2-S1*M/S3*M

(3)

YCA Fare

1. Enter the _CA fare for the Origin / Destination (O/D), exclusive of taxes and fees.

2. If travel is in a market where there is no contract city pair fare awarded, enter 0000.00.

Enter dollar amount in 0000.00 format. Left justify.

Element Capture: Traditional/PNR Touch Only

GDS Entries

Calculation Based on Origin/Destination ~ Data as of Time of Booking, accounting for any changes in the segments during the trip lifecycle. In the example below, S1 is a connection, $0 value.

Sabre

5.S*UD55-DTMO3-S1*00.00/S2*350.00/S4*450.00

(Example: S1 = 00.00, S2 = 350.00, S4 = 450.00)

Worldspan

5/DTMO/3-S1*00.00/S2*350.00/S4*450.00

Apollo

[]:5DTMO3-S1*00.00/S2*350.00/S4*450.00

Galileo

NP.DTMO3-S1*00.00/S2*350.00/S4*450.00

RX DTMO3-S1*00.00/S2*350.00/S4*450.00

(4)

Lowest Published

Available

Unrestricted Coach Fare

1. Enter the lowest published unrestricted coach fare available for the Origin / Destination (O/D), exclusive of taxes and fees.

2. If segment is the first part of a thru-fare, enter 0.00.

3. If no unrestricted coach fare in this market, leave blank.

Enter dollar amount in 0000.00 format. Left justify.

Element Capture: Traditional/PNR Touch Only

GDS Entries

Calculation Based on Origin/Destination ~ Data as of Time of Booking, accounting for any changes in the segments during the trip lifecycle. In the example below, S1 is a connection, $0 value.

Sabre

5.S*UD55-DTMO4-S1*00.00/S2*350.00/S4*450.00

(Example: S1 = 00.00, S2 = 350.00, S4 = 450.00)

Worldspan

5/DTMO/4-S1*00.00/S2*350.00/S4*450.00

Apollo

[]:5DTMO4-S1*00.00/S2*350.00/S4*450.00

Galileo

NP.DTMO4-S1*00.00/S2*350.00/S4*450.00

RX DTMO4-S1*00.00/S2*350.00/S4*450.00

(5)

Lowest Published Available Unrestricted Fare Basis Enter the fare basis of the lowest published unrestricted coach fare used.

If no unrestricted coach fare in this market, leave blank.

Element Capture: Traditional/PNR Touch Only

GDS Entries

Based on Origin/Destination ~ Data as of Time of Booking, accounting for any changes in the segments during the trip lifecycle.

Sabre

5.S*UD55-DTMO5-S1*HUA/S2*YL/S4*HUA

Worldspan

5/DTMO/5-S1*HUA/S2*YL/S4*HUA

Apollo

[]:5DTMO5-S1*HUA/S2*YL/S4*HUA

Galileo

NP.DTMO5-S1*HUA/S2*YL/S4*HUA

RX DTMO5-S1*HUA/S2*YL/S4*HUA

(6)

Traveler Acceptance of Lowest Fare When a traveler is booked on a non-GSA City Pair, enter the code to indicate if the traveler accepted the lowest fare offered or not.

A ‘Y’/’N’ indicator identifying if the traveler accepted the lower fare offered by the CTO.

Element Capture: Traditional/PNR Touch Only

GDS Entries

Segment Level ~ Data as of Time of Booking, accounting for any changes in the segments during the trip lifecycle.

Sabre

5.S*UD55-DTMO6-S1*Y/S2*Y/S3*N

Worldspan

5/DTMO/6-S1*Y/S2*Y/S3*N

Apollo

[]:5DTMO6-S1*Y/S2*Y/S3*N

Galileo

NP.DTMO6-S1*Y/S2*Y/S3*N

RX DTMO6-S1*Y/S2*Y/S3*N

(8)

Hotel Rate Code Enter alpha code to indicate hotel rate category from the chart below.

NOTE: Enter the rate code booked, not the rate code searched for. If agent searches for "ALL," do not enter ALL as the rate code, enter the rate code that was selected and booked Element Capture: Traditional/PNR Touch Only

Code

Standard Rate Category

V

Convention

COR

Corporate

FAM

Family Plan

GOV

Government

MIL

Military

PRO

Promotional

SCR

Senior Citizen

TOR

Tour Package

WKD

Weekend

RAC

Regular Hotel Rate

XVU

FedRooms Rate

USN

Navy Elite Rate

AAA

AAA Rate GDS Entries

Hotel Segment Level ~ Data to be Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO8-S1*GOV/S2*RAC/S3*MIL

Worldspan

5/DTMO/8- S1*GOV/S2*RAC/S3*MIL

Apollo

[]:5DTMO8- S1*GOV/S2*RAC/S3*MIL

Galileo

NP.DTMO8- S1*GOV/S2*RAC/S3*MIL

RX DTMO8- S1*GOV/S2*RAC/S3*MIL

(9)

Reason Code for Non-Use of Government Quarters Enter alpha numeric code from the table below to indicate reason for non-use of Government quarters.

Element Capture: Traditional/PNR Touch Only Code

Government Quarters Non-Use Reason Code

H1

No rooms available. Certificate of Non-Availability issued.

H2

Exempted by order issuing agency.

H3 Quarters not offered at location.

GDS Entries

Hotel Segment Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO9-S1*H1/S2*H3

Worldspan

5/DTMO/9-S1*H1/S2*H3

Apollo

[]:5DTMO9-S1*H1/S2*H3

Galileo

NP.DTMO9-S1*H1/S2*H3

RX DTMO9-S1*H1/S2*H3

(10)

Travel Authorization Number Enter the travel authorization number. For a DTS transaction, this will be the Travel Authorization Number (TANUM). As an example for a traditional transaction on the DD Form 1610, this will be the Travel Authorization Number (field 22 on the DD form 1610).

Element Capture: All transactions.

GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO10-TA010112

Worldspan

5/DTMO/10-TA010112

Apollo

[]:5DTMO10-TA010112

Galileo

NP.DTMO10-TA010112

RX DTMO10-TA010112

(11)

DoD Component Enter code from the table below to indicate the Department of Defense (DOD) Component of the traveler:

Code

DoD Component

A

Department of the Army

C

Coast Guard

F

Department of the Air Force

J

Joint Staff/Command

N

Department of the Navy

M

United States Marine Corps

X

Other DoD Components

Element Capture: Traditional/PNR Touch Only GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO11-C

Worldspan

5/DTMO/11-C

Apollo

[]:5DTMO11-C

Galileo

NP.DTMO11-C

RX DTMO11-C

(12)

Purpose of Travel Enter code from the table below to indicate the purpose of travel:

Element Capture: Traditional/PNR Touch Only

Code

Description

Site visit

Information meeting

Training attendance - receiving training

To give speech or presentation

Conference attendance - observe/no formal role in conference

Relocation - transfer from one permanent duty station to another (PCS) accompanied by dependents

Relocation - transfer from one permanent duty station to another (PCS) not accompanied by dependents

Relocation - transfer from one permanent duty station to another (PCS) unaccompanied dependents (without military or civilian) principal

Entitlement travel

Between tours of duty travel

Special missions travel

Emergency travel

Other travel

GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO12-2

(Example: purpose is training)

Worldspan

5/DTMO/12-2

Apollo

[]:5DTMO12-2

Galileo

NP.DTMO12-2

RX DTMO12-2

(13) Traveler’s Government

E-Mail Address Enter the traveler’s Government e-mail address.

Note: CTOs should continue to use standard PNR fields for storing email addresses for itinerary distribution. The traveler’s government email address should be the only value provided in the DTMO13 (field 13) entry.

Element Capture: Required for Traditional/PNR Touch Only when standard PNR email address fields do not contain traveler’s government email address.

GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO13-john.doe@us.army.mil

(Example: traveler name is John Doe and has an Army email address)

Worldspan

5/DTMO/13-john.doe@us.army.mil

Apollo

[]:5DTMO13- john.doe@us.army.mil

Galileo

NP.DTMO13- john.doe@us.army.mil

RX DTMO13-john.doe@us.army.mil

(14)

CTO Servicing Location Enter the CTO servicing site/location.

The Contractor shall utilize a unique alpha/numeric identifier defined by the DTMO for each site/location. The unique identifier shall not exceed 30 characters. The Contractor shall utilize the applicable identifier to identify the CTO servicing location. The DTMO shall provide an excel spreadsheet to the Contractor containing each PCC/SID supporting travel services, to include ARC/IATA number, and unique alpha identifier for each site identified under this task order.

Element Capture: All transactions.

See Attachment A for location codes.

GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO14-12345

(Example: the traveler is assigned to Ft. Bragg)

Worldspan

5/DTMO/14-12345

Apollo

[]:5DTMO14-12345

Galileo

NP.DTMO14-12345

RX DTMO14-12345

(15)

Reason Codes for Use/Non-Use of Contract Air Enter the code from the table below for each air segment to indicate use/non-use of the General Services Administration (GSA) contract city pair fare.

Element Capture: All transactions.

Code

Reason

C0

Contract Fare Used.

C1

Scheduled contract fare flights are not available in time to meet mission requirements or use of contract service would require the traveler to incur unnecessary overnight lodging costs that would increase the total cost of the trip.

C2

The contractor's flight schedule is inconsistent with explicit policies of individual Federal departments and agencies where applicable to schedule travel during normal working hours.

C3

A non-contract carrier offers a lower fare available to the general public, the use of which will result in a lower total trip cost to the government to include the combined costs of transportation, lodging, meals, and related expenses.

NOTE: This exception does not apply if the contract carrier(s) offers a comparable fare and has seats available at the fare, or if the lower fare offered by a non-contract carrier is restricted to government and military travelers on official business and may only be purchased with a GTR or government travel card, e.g., YDG, MDG, QDG, VDG, and similar fares.

C4

Seat not available on contract air carrier.

C5

Used contract fare for portion of trip, but not entire trip.

C6

Non-contract fare used on contract carrier (lower fare than CA).

Traveler refused contract fare because:

C7A

Airport specified

C7B

Carrier specified

C7C

Routing specified

C7D

Time specified

C7E

Personal reasons.

C8

No cost ticket (e.g., Frequent Flyer).

C9

FMS.

C10

Rail service available and cost effective.

C11

No contract fare in market.

GDS Entries

Segment Level ~ Data to be Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO15-S1*C0/S2*C0/S3*C0/S4*C0

(Example: traveler is utilizing the contract carrier for all four segments)

Worldspan

5/DTMO/15-S1*C0/S2*C0/S3*C0/S4*C0

Apollo

[]:5DTMO15-S1*C0/S2*C0/S3*C0/S4*C0

Galileo

NP.DTMO15-S1*C0/S2*C0/S3*C0/S4*C0

RX DTMO15-S1*C0/S2*C0/S3*C0/S4*C0

(16)

Transaction Fee Amount If a transaction fee is charged, enter dollar amount of transaction fee using the 0000.00 format; left justify.

If multiple transaction fees are charged, the dollar amount of the transaction fee should be cumulative.

Element Capture: All transactions.

GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO16-0015.00

(Example: $15.00 transaction fee charged)

Worldspan

5/DTMO/16-0015.00

Apollo

[]5DTMO16-0015.00

Galileo

NP.DTMO16-0015.00

RX DTMO16-0015.00

(17)

Transaction Fee Type Enter alpha code from the table below to indicate transaction fee type. Enter the transaction fee code for the trip in the first segment of the trip reported.

Element Capture: All transactions.

Type

Description

E Self Booked (e.g., DTS) B Full Service (e.g., DTS Touch (Small Business Contracts Only)) F Full Service (e.g., CTO Assist (Worldwide CTO Task Orders) / Traditional (Small Business Contracts)) GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO17-F

(Example: full service transaction fee)

Worldspan

5/DTMO/17-F

Apollo

[]:5DTMO17-F

Galileo

NP.DTMO17-F

RX DTMO17-F

(18)

Transaction Fee

Justification If Transaction Fee Type (element 17) value is “B” or “F”, enter the 2-5 character code from the tables below that justifies why a touch transaction fee was charged.

The first character of the field shall identify the reason a fee type is used from the alpha codes identified below.

CTO Fee Justification Alpha Codes Justification Code Justification/Reason A Traveler Requested Assistance – DTS B Non-Auto-booked PNR C Industry Driven D COR Initiated E

CBA

The last four characters shall identify the reservation type(s) that caused the fee type to be used. Up to four characters can be entered, but a minimum of one must be entered.

NOTE: Only Justification Codes 1 and/or 2 should be used with “E” - CBA.

CTO Fee Justification Reservation Types Justification Code Justification/Reason Air Rail Car Lodging For No Touch transactions, the code “NT” should be used.

Element Capture: All transactions.

Example: Traveler requested assistance through DTS with Air and Car reservation – entry would be – ‘A13’ GDS Entries Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO18-B3

Worldspan

5/DTMO/18-B3

Apollo

[]:5DTMO18-B3

Galileo

NP.DTMO18-B3

RX DTMO18-B3

(19)

Contract/ Task Order Number Enter the contract or task order (as it applies to the servicing location) number under which the transaction fee charged is authorized.

Element Capture: All transactions.

GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO19-WQ19001B1014

Worldspan

5/DTMO/19-WQ19001B1014

Apollo

[]:5DTMO19-WQ19001B1014

Galileo

NP.DTMO19-WQ19001B1014

RX DTMO19-WQ19001B1014

(20)

CTO Email Address Enter the email address where Premium Class Travel validation requests for this specific PNR should be directed. The email address can be established by individual CTO location, CTO-wide or any level in between that the CTO chooses. This can either be person or a distribution email. The recipient of this email should have the necessary access/information to address the authorization cycle used with respect to premium class travel.

Element Capture: All transactions.

GDS Entries

Ticket Level ~ Data to be Captured at Time of PNR Creation Sabre

5.S*UD55-DTMO20-travelagent@commercialtravel.com Worldspan

5/DTMO/20-travelagent@commercialtravel.com Apollo

[]:5DTMO20-travelagent@commercialtravel.com Galileo

NP.DTMO20-travelagent@commercialtravel.com

RX DTMO20-travelagent@commercialtravel.com

(21)

Miles Flown Enter the total air miles for each air segment.

Element Capture: All transactions.

GDS Entries

Segment Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO21-S1*850/S2*1150/S3*3549

Worldspan

5/DTMO/21-S1*850/S2*1150/S3*3549

Apollo

[]:5DTMO21-S1*850/S2*1150/S3*3549

Galileo

NP.DTMO21-S1*850/S2*1150/S3*3549

RX DTMO21-S1*850/S2*1150/S3*3549

(23)

Number of PNRs The total number of PNRs associated with the trip this record locator is associated with. Example: Southwest Airlines or other multi-PNR required booking process.

Element Capture: Traditional/PNR Touch Only

GDS Entries

PNR Level ~ Data to be Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO23-2

Worldspan

5/DTMO/23-2

Apollo

[]:5DTMO23-2

Galileo

NP.DTMO23-2

RX DTMO23-2

(24)

Associated Record Locator Provide the primary record locator if this PNR is part of a multi-PNR booking (referencing requirement 23 above).

Element Capture: Traditional/PNR Touch Only

GDS Entries

PNR Level ~ Data Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO24-ZUJDJU

Worldspan

5/DTMO/24-ZUJDJU

Apollo

[]:5DTMO24-ZUJDJU

Galileo

NP.DTMO24-ZUJDJU

RX DTMO24-ZUJDJU

(25)

Price By Leg Provide the price by leg based on the current pricing of the itinerary. Remember to modify any entries to capture changes in the itinerary and/or pricing. GDS example entries are provided as well as a review of pricing by segment based on using the linear fare construction from the GDS. Pricing for connections should indicate zero, while the actual leg pricing is associated with the final segment in the pricing city pair.

Element Capture: All transactions.

Pricing Example:

GDS Entries

Segment Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO25-S1*157.21/S2*157.21

Worldspan

5/DTMO/25-S1*0.00/S2*157.21/S3*0.00/S4*157.21 (below example) Apollo

[]:5DTMO25-S1*157.21/S2*157.21

Galileo

NP.DTMO25-S1*157.21/S2*157.21

Amadeus

RX DTMO25-S1*157.21/S2*157.21

Pricing Example, with connection pricing:

(26)

Total Air Cost The total air cost of the trip, inclusive of fees, taxes and base fare.

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD26-DTMO17-380.80

Worldspan

5/DTMO/26-380.80

Apollo

[]:5DTMO26-380.80

Galileo

NP.DTMO26-380.80

RX DTMO26-380.80

(27)

Total Air Base Fare The total base air fare of the trip, exclusive of fees and taxes.

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO27-314.42

Worldspan

5/DTMO/27-314.42

Apollo

[]:5DTMO27-314.42

Galileo

NP.DTMO27-314.42

RX DTMO27-314.42

(28)

Approving Official Name The name of the Approving Official (AO) that authorized premium class travel.

Element Capture: Required if a Premium Class Travel segment is present in the PNR.

GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO28-Mark Montgomery Worldspan

5/DTMO/28-Mark Montgomery Apollo

[]:5DTMO28-Mark Montgomery Galileo

NP.DTMO28-Mark Montgomery

RX DTMO28-Mark Montgomery

(29)

Approving Official Email Address The email address of the Approving Official (AO) that authorized premium class travel.

Element Capture: Required if a Premium Class Travel segment is present in the PNR.

GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO29-mark_montgomery@travis.af.mil Worldspan

5/DTMO/29-mark_montgomery@travis.af.mil Apollo

[]:5DTMO29-mark_montgomery@travis.af.mil Galileo

NP.DTMO29-mark_montgomery@travis.af.mil

RX DTMO29-mark_montgomery@travis.af.mil

(30)

Rank/Grade of Traveler The military rank or civilian grade of the traveler. Use standard government and military ranking structure.

E1 - E9 Military Enlisted

O1 – O9 Military Officer

GS1 – GS15 Civilian Government Service

SES1 – SES Level

NG – Non-Government Traveler

Element Capture: Required if a Premium Class Travel segment is present in the PNR.

GDS Entries (i.e., Officer – 1st Lt./LTJG) Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO30-O2

Worldspan

5/DTMO/30-O2

Apollo

[]:5DTMO30-O2

Galileo

NP.DTMO30-O2

RX DTMO30-O2

(31)

Type of Traveler Enter alpha code from the table below to indicate the type of traveler.

Element Capture: Traditional/PNR Touch Only Code

Description

O

Military Officer

E

Military Enlisted

C

Civilian Government Employee

D

Dependent of Military Officer

G

Dependent of Military Enlisted

H

Dependent of Civilian Employee

R

Human Remains

S

Sponsor

T

Team Travel - A movement of 10 or more personnel traveling as a group under the same orders, from the same origin to the same destination

P

Dependent Student

K

Contractor/Cost Charge Travel

I

Invitational

F

Prisoner

A Accession Travel (Recruit) GDS Entries

Ticket Level ~ Data to be Captured Prior to or at Time of Ticketing Sabre

5.S*UD55-DTMO31-O

Worldspan

5/DTMO/31-O

Apollo

[]:5DTMO31-O

Galileo

NP.DTMO31-O

RX DTMO31-O

(32)

Origin / Destination Indicator At the segment level, Enter a “T” if the destination of the city pair is a connection. Enter a “D” if the destination of the city pair is the traveler’s destination. This indicator is independent of pricing.

Example:

Passenger is traveling from Washington to Dallas-Fort Worth. In pricing the trip from WAS to DFW, the agent finds that it is cheaper to break the fare in ATL and AEX.

Element Capture: Traditional/PNR Touch Only

Segment

Travel Date

Start

Finish

GDS O/X

Fare Basis

O/D Destination Indicator

30SEP

DCA

ATL

O

KCADCA

T

30SEP

ATL

AEX

O

BDG

T

30SEP

AEX

DFW

O

HCA

D

14JAN

DFW

LGA

X

YCA

T

14JAN

LGA

DCA

O

YCA

D

GDS Entries

Segment Level ~ Data to be Captured Prior to or at Time of Ticketing

Sabre

5.S*UD55-DTMO32-S1*T/S2*T/S3*D/S4*T/S5*D

Worldspan

5/DTMO/32- S1*T/S2*T/S3*D/S4*T/S5*D

Apollo

[]:5DTMO32- S1*T/S2*T/S3*D/S4*T/S5*D

Galileo

NP.DTMO32- S1*T/S2*T/S3*D/S4*T/S5*D

RX DTMO32- S1*T/S2*T/S3*D/S4*T/S5*D

II. Premium Class Travel Validation The Contractor shall submit a monthly report of all other-than-coach travel.