Attachment_1_TMC_CTO_Data_Requirements_V4.2.1_2017_05_11.pdf

Version 4.2.1 11 MAY 2017

Defense Travel Management Office 1

Travel Management Company Data Requirements

DEFENSE TRAVEL

MANAGEMENT OFFICE

Version 4.2.1 11 MAY 2017

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 2

Table of Contents

Table of Contents

1. TRAVEL DAILY

2. DATA QUALITY

3. CUSTOMER NUMBER LIST (DK/CA)

4. SITE IDENTIFIER

5. RECORD RETENTION

6. TESTING

7. AUTO-QUEUING INSTRUCTIONS

7.1. SABRE

7.2. WORLDSPAN

8. SPECIAL CHARACTERS

9. INSTRUCTIONS FOR ADDITIONAL REQUIRED ELEMENTS

10. OTHER THAN ECONOMY/COACH CLASS TRANSPORTATION (OTECCT) VALIDATION

11. COMMERCIAL TRAVEL INFORMATION MANAGEMENT (CTIM) FILE

11.1. GENERAL FILE PREPARATION AND SUBMISSION INSTRUCTIONS

11.2. FILE PROCESSING REPORTS (FPR) AND DATA CORRECTIONS

11.3. CTIM MONTHLY FILE FORMAT

APPENDICES

Appendix A – DK List

Appendix B – CTO Site Listing

Appendix C – Exchange Ticket Scenarios for Contractor Monthly Data File Reporting

Appendix C.1 – Example of Even Exchange Reporting

Appendix C.2 – Example of Exchange with Add Collect Reporting

Appendix C.3 – Example of Exchange with Refund Reporting

Appendix C.4 – Example of Partial Exchange Reporting

Appendix D – CTO Error Report Examples

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 3

1. 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, etc.) and the additional data elements provided by the contractor.

The contractor shall:

• Establish auto-queuing in accordance with Section 7 below

− Queue DoD PNRs upon processing refunds after contract expiration

• Provide additional data elements in accordance with Section 9 below

− Data required “at the time of booking” shall be entered during the booking/quality control process and prior to end transaction

− Data required “prior to ticketing” may be entered prior to or at ticketing as long as the data is present in the PNR prior to ending transaction

− Leave field blank if the data capture requirements aren’t applicable − Update applicable fields upon processing PNR changes

2. DATA QUALITY

All PNRs will be checked for data quality.

The contractor shall:

• Establish an email address to receive data quality error notifications

• Receive email containing records with data errors

• Correct data errors in the passenger name record (PNR)

• Queue place corrected PNR within five business days of notification

3. CUSTOMER NUMBER LIST (DK/CA)

The contractor shall:

• Provide an Excel spreadsheet NLT five business days prior to contract start date containing the following:

- Listing of all DKs/CAs

- DK/CA descriptive name

- Traveler type (official, leisure, LICWO, contractor, etc.)

- Provide the COR with updates to DK/CA listing five business days prior to implementing changes

An example DK/CA list is provided in Appendix A – DK List

4. SITE IDENTIFIER

The government will assign unique identifiers for each site listed in Attachment 3, Site Data Sheets. The site ID listing and other site specific information will be provided to the contractor within five business days after award.

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 4

• Review the site ID listing

• Provide the COR with acknowledgement or corrections as required NLT 15 business days prior to contract start date

• Provide the COR with updates to site ID listing five business days prior to implementing changes

An example is provided in Appendix B – CTO Site Listing.

5. RECORD RETENTION

The Contractor shall ensure that PNRs are retained in the GDS for a minimum of six months after the last date of travel in the PNR.

6. TESTING

The contractor shall:

• Participate in Travel Daily testing NLT 7 days prior to contract start date

• Prepare and queue one test PNR for each site PCC

• Test PNRs shall include all additional data reporting elements as required in Section 9

7. AUTO-QUEUING INSTRUCTIONS

The following GDS features are supported by the Government:

7.1. SABRE

These instructions apply to Abacus as well.

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

Feature Government Supported

Pseudo City Code EZ7C

Processing Type Web Services

DTMO Queue Assignment The queue will be assigned during the implementation process.

Automated Itinerary Segments Supported

Active/Automated Air, Hotel, Car

Passive itinerary Segments Supported Passive/Sabre Standard for Air, Hotel & Car http://www.sabretravelnetwork.com/ http://eservices.sabre.com/

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 5

Scans/Hit Charges All costs for scans and hits are born by the Government

Access Type Branch

Branch Access

The Contractor shall establish branch access between the above PCC and each of the Contractor’s PCCs to view, sweep, and queue place all DoD PNRs.

Queue Placement

The Contractor shall:

• Utilize Sabre’s automated queue drop functionality to queue place all newly created, ticketed, cancelled, refunded or otherwise modified PNRs to a designated queue in the Government’s PCC

• Ensure PNR refund data is queued immediately upon processing refunds when the PNR is in queue or when initiating refunds via the electronic ticket record (ETR.)

Passive Segments

• Utilize Sabre standard formats for air, car, and rail

• For lodging, use the following format:

0HHTAAGK1WASIN10AUG-OUT12AUG/MCMARRIOTT/GOVT/ 89.00USD/ G/SI-[]101MAIN

STREET#ARLINGTON VIRGINIA 12345#FONE 800-555-1212/CF-12345678

7.2. WORLDSPAN

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

Feature Government Supported

Subscriber Identifications (SIDs) OU0

Processing Type Web Services

DTMO Queue Assignment The queue will be assigned during the implementation process.

Automated Itinerary Segments Supported

Active/Automated Air, Hotel, Car

Passive itinerary Segments Supported Passive/Worldspan Standard for Air, Hotel & Car http://www.worldspan.com/ http://support.worldspan.com/

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 6

Scans/Hit Charges All costs for scans and hits are born by the Government. No SID emulation is performed by DTMO to read PNR information.

Access Type Bridge

Bridge Access

The Contractor shall establish bridge access between the above government supported SID and each of the Contractor’s SIDs to view, sweep, and queue place all DoD PNRs.

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

• Ensure PNR refund data is queued immediately upon processing refunds when the PNR is in queue or when initiating refunds via the electronic ticket record (ETR)

Passive Segments

• Utilize the Worldspan standard format for air, car, and rail

• Process lodging using the following format:

Manual Entry: HN@MK*MIA25OCT28OCT1/C-QI/H-QUALITY INN/R-A2DRAC/SI-123

MAIN STREET$MIAMI FL12345$PHONE 703-456-9876@/RT-USD 9900/RD-DELUXE

ROOM/CF-444444

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 7

8. SPECIAL CHARACTERS

The Government supports the following characters and translations:

Note: additional characters/translations may be added upon request

Character Translated to

AT @

at @ U _ u _ &#164 @

(A) @

(a) @ *27 ' *2D - *4 ' *40 @ *5F _ *6 _ *8 @

.AT. @

.at. @

.UN. _

.un. _

/AT/ @

/at/ @ \u00A4 @ \u00A4\u00A4- _ \u00A4\u00A4U _ Blank Space _

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 8

9. INSTRUCTIONS FOR ADDITIONAL REQUIRED ELEMENTS

Field ID Description

CLASS OF SERVICE CODE

Enter code from the table below.

Data Capture Requirements:

• All PNR’s with air, bus, rail and water reservations

• All air, bus, and rail segments

• Prior to ticketing

Code Description 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 airlines and reservation systems.

B Business Class A premium class of accommodation offered by the airlines that is generally 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.

Data Entry Format Examples (S1 First, S2 Coach, S3 First, S4 Coach):

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

Worldspan 5.Z DTMO1- S1*F/S2*C/S3*F/S4*C

REASON CODE FOR OTHER THAN ECONOMY/COACH CLASS TRANSPORTATION (OTECCT)

Data Capture Requirements:

• All PNRs with OTECCT reservations

• All OTECCT segments

• At time of booking for reason codes N and O below

• Prior to ticketing for all other reason codes

References in description refer to the Joint Travel Regulations, Appendix H3A

Code Description

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.)

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 9

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 (e.g. Leisure, LICWO, Contractor Travel, etc.)

N Premium class is lower than YCA and/or lower than lowest unrestricted coach fare (e.g. GDS auto-priced premium as the lowest applicable unrestricted fare)

O Airline automatic upgrade (e.g. “UP” fares)

Data Entry Format Examples (Segments 1 & 3 are OTECCT due to medical):

Sabre 5.S*UD55-DTMO2-S1*B/S3*B

Worldspan 5.Z DTMO2- S1*B/S3*B

COMPARISON FARE

Enter the comparison fare in accordance with the instructions below.

Data Capture Requirements:

− All PNRs with OTECCT reservations − Ticket level o Enter comparison fare in the last segment associated with each stored fare

− At the time of booking

Example #1:

Booked/Ticketed Fare

1 UA 594Y 20SEP S DCADEN SS1 412P 609P

2 UA 565F 25SEP F DENDCA SS1 955A 322P

BASE FARE TAXES/FEES/CHARGES TOTAL

1- USD1826.97 165.23XT USD1992.20GVT

XT 137.03US 8.00ZP 11.20AY 9.00XF

1826.97 165.23 1992.20TTL

GVT-01 YCADCA FUA2F

Comparison Fare

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 10

1 UA 594Y 20SEP S DCADEN SS1 412P 609P

2 UA 565Y 25SEP F DENDCA SS1 955A 322P

BASE FARE TAXES/FEES/CHARGES TOTAL

1- USD401.86 58.34XT USD460.20GVT

XT 30.14US 8.00ZP 11.20AY 9.00XF

401.86 58.34 460.20TTL

GVT-01 YCADCA

United was the contract carrier for the origin/destination; therefore, the round trip YCA inclusive of taxes and fees (460.20) shall be used as the comparison fare.

Example #2:

Booked/Ticketed Fare

1 UA 989Y 20SEP S IADFRA SS1 525P 720A 21SEP

2 LH 326Y 24SEP Q FRAVCE NN1 1230P 145P

3 UA9058J 29SEP T VCEFRA*SS1 1030A 1155A

4 UA8827J 29SEP T FRAIAD*SS1 115P 355P

WPPGVT‡XR«

BASE FARE TAXES/FEES/CHARGES TOTAL

1- USD7650.00 634.00XT USD8284.00GVT

XT 428.00YQ 35.40US 5.50YC 7.00XY

5.00XA 5.60AY 18.40DE 53.40RA

47.30OY 1.80EX 9.60IT 4.30VT

7.30HB 0.90MJ 4.50XF

7650.00 634.00 8284.00TTL

GVT-01 YCA Y77 JXR1

Comparison Fare:

1 UA 989Y 20SEP S IADFRA SS1 525P 720A 21SEP

2 LH 326Y 24SEP Q FRAVCE NN1 1230P 145P

3 UA9058Y 29SEP T VCEFRA*SS1 1030A 1155A

4 UA8827Y 29SEP T FRAIAD*SS1 115P 355P

WPPGVT‡XR«

BASE FARE TAXES/FEES/CHARGES TOTAL

1- USD3649.00 464.00XT USD4113.00GVT

XT 258.00YQ 35.40US 5.50YC 7.00XY

5.00XA 5.60AY 18.40DE 53.40RA

47.30OY 1.80EX 9.60IT 4.30VT

7.30HB 0.90MJ 4.50XF

3649.00 464.00 4113.00TTL

GVT-01 YCA Y77 YDG

The comparison fare for this example includes a contract fare, unrestricted economy class fare, and a discount government fare (4113.00).

− Segment 1 (IAD-FRA) was booked/ticketed on the contract carrier (YCA) − Segment 2 (FRA-VCE) was booked/ticketed between an origin/destination with no contract city pair award. The fare was booked/ticketed at the lowest

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 11 available unrestricted economy class fare (Y77) − Segments 3 & 4 (VCE-IAD) were booked/ticketed on the non-contract carrier − The lowest available unrestricted economy fare for the non-contract carrier was a discount government fare (YDG).

Data Entry Format Examples:

Sabre 5.S*UD55-DTMO3- S2*460.20 (Using example #1 from above)

Worldspan 5/DTMO/3-S4*4113.00 (Using example #2 from above)

4 FARE RESTRICTION INDICATOR

Data Capture Requirements:

• All PNR’s with air or rail reservations

• All air and rail segments

• At time of booking

R Fully Refundable Fare N Non-Refundable Fare P Refundable Fare with Penalty

Data Entry Format Examples:

Sabre 5.S*UD55-DTMO4-S1*N/S2*N/S3*N/S4*N

Worldspan 5/DTMO/4-S1*N/S2*N/S3*N/S4*N

5 RESTRICTED FARE COMPARISON

Data Capture Requirements:

− All PNRs with restricted fares (any fare other than fully refundable) − Ticket level o Enter comparison fare in the last segment associated with each restricted fare stored

− At the time of booking

Example #1:

Booked/Ticketed Fare

1 UA 594O 20SEP O FRATPA SS1 412P 609P

2 UA 565O 25SEP O TPAFRA SS1 955A 322P

BASE FARE TAXES/FEES/CHARGES TOTAL

1- USD300.76 386.76XT USD687.57ADT

XT 35.60US 317.00YR 5.50YC

7.00XY 3.96XA 11.20AY 10.20DE

37.70RA 46.60OY 12.00XF

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 12

300.76 386.76 687.57TTL

ADT-01 OKADPM0N

Comparison Fare

1 UA 594Y 20SEP Y FRATPA SS1 412P 609P

2 UA 565Y 25SEP Y FRATPA SS1 955A 322P

BASE FARE TAXES/FEES/CHARGES TOTAL

1- USD1446.00 169.76XT USD1615.76GVT

XT 35.60US 5.50YC 7.00XY 3.96XA

11.20AY 10.20DE 37.70RA 46.60OY

1446.00 169.76 1615.76TTL

GVT-01 YCA

United was the contract carrier for the origin/destination; therefore, the round trip YCA inclusive of taxes and fees (1615.76) shall be used as the comparison fare.

Example #2:

Booked/Ticketed Fare

1 AZ1745O 27SEP O FCOCTA SS1 105P 220P

2 AZ1730X 30SEP X CTAFCO SS1 115P 235P

BASE FARE EQUIV AMT TAXES/FEES/CHARGES TOTAL

1- EUR71.00 USD80.00 86.20XT USD166.20ADT

XT 22.40YR 4.80EX 29.30IT 6.10VT

15.70HB 2.10MJ 5.80FN

71.00 80.00 86.20 166.20TTL

ADT-01 OOWLGNB1 XOWLGNB1

Comparison Fare

1 AZ1745M 27SEP M FCOCTA SS1 105P 220P

2 AZ1730M 30SEP M CTAFCO SS1 115P 235P

BASE FARE EQUIV AMT TAXES/FEES/CHARGES TOTAL

1- EUR630.00 USD708.00 86.20XT USD794.20ADT

XT 22.40YR 4.80EX 29.30IT 6.10VT

15.70HB 2.10MJ 5.80FN

630.00 708.00 86.20 794.20TTL

ADT-01 MOWFLN1

Travel for this example wasn’t ticketed on the city pair carrier; therefore, the lowest unrestricted fare inclusive of taxes and fees (794.20) shall be used as the comparison fare.

Data Entry Format Examples:

Sabre 5.S*UD55-DTMO5-S2*1615.76 (Using example #1 from above)

Worldspan 5/DTMO/5-S2*794.20 (Using example #2 from above)

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 13

6 This field is not used

7 USE/NON-USE OF DOD PREFERRED COMMERCIAL LODGING

Enter code from the table below.

Data Capture Requirements:

• Applicable to CTO/TMC created PNRs

• All segments where DoD Preferred Lodging is applicable

• At booking

Code Description L0 DoD Preferred Commercial Lodging used L1 Too Far Away L2 Mission Requirements L3 Lower Rate Available L4 Personal Choice/Limited Reimbursement L5 DoD Lodging (AKA On-Base Housing) used L6 Lodging with Family or Friends L7 Conference or Event L8 Contract Lodging L9 Rental Housing Used L10 Exempt IAW JTR L11A DoD Preferred Commercial Lodging not available

Data Entry Format Examples (booked lower rate available at non-preferred property):

Sabre 5.S*UD55-DTMO7- S3*L3

Worldspan 5.Z DTMO7- S1*L3

LODGING RATE CODE

Data Capture Requirements:

• Applicable to CTO/TMC created PNRs with lodging reservations

• All lodging segments

• At booking

AAA AAA Rate

SCR Senior Citizen

COR Corporate

TOR Tour Package

FAM Family Plan

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 14

GOV Government

V Convention

MIL Military

WKD Weekend

PRO Promotional

XVL

DoD Preferred Commercial Lodging

RAC Regular Hotel Rate

XVU FedRooms Rate

DoD DoD Lodging

Data Entry Format Examples (DoD Preferred Commercial Lodging booked):

Sabre 5.S*UD55-DTMO8-S3*XVL

Worldspan 5.Z DTMO8- S3*XVL

USE/NON-USE OF DOD LODGING

Data Capture Requirements:

• Applicable to CTO/TMC created PNR’s o If DoD lodging arrangements are required by the CTO/TMC contract

• All segments where DoD lodging is applicable

• At booking

Code Description H0 DoD Lodging Booked

H1 No rooms available. Non-Availability (NA) Confirmation Number issued.

H2 Exempted by order issuing agency.

H3 DoD Lodging not offered at location.

Data Entry Format Examples (No rooms available CTO/TMC received NA Confirmation):

Sabre 5.S*UD55-DTMO9-S3*H1

Worldspan 5.Z DTMO9-S3*H1

10 TRAVEL AUTHORIZATION NUMBER

Provide the travel authorization/order number.

Data Capture Requirements:

• All PNRs

• At PNR level

• Prior to ticketing

Data Entry Format Examples:

Sabre 5.S*UD55-DTMO10-TA010112

Worldspan 5.Z DTMO10-TA010112

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 15

11 DOD COMPONENT

Data Capture Requirements:

• Applicable to CTO/TMC created PNRs and DTS PNRs with OTECCT

• At PNR level

• Prior to ticketing

Note: DTS provides the DoD component in the PNR General Remarks field.

Code Description

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

Data Entry Format Examples (traveler is Army):

Sabre 5.S*UD55-DTMO11-A

Worldspan 5.Z DTMO11-A

12 TRAVEL PURPOSE IDENTIFIER

Data Capture Requirements:

• Applicable to CTO/TMC created PNRs and DTS PNRs with OTECCT

• PNR level

• Prior to ticketing

Note: DTS provides the DoD component in the PNR General Remarks field.

Code Description 0 Site visit 1 Information Meeting 2 Training attendance – receiving training 3 To give speech or presentation 4 Conference attendance – observe/no formal role in conference 5 Relocation – transfer from one permanent duty station to another (PCS) accompanied by dependents 6 Relocation – transfer from one permanent duty station to another (PCS) not accompanied by dependents 7 Relocation – transfer from one permanent duty station to

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 16 another (PCS) unaccompanied dependents (without military or civilian) principal

8 Entitlement travel 9 Between tours of duty travel 10 Special missions travel 11 Emergency travel 12 Other travel

Data Entry Format Examples (travel purpose is training):

Sabre 5.S*UD55-DTMO12-2

Worldspan 5.Z DTMO12-2

TRAVELER’S GOVERNMENT E-MAIL ADDRESS

Provide the traveler’s Government e-mail address.

Data Capture Requirements:

• Applicable to all CTO/TMC created PNRs and DTS PNRs with OTECCT

• PNR level

• Prior to ticketing

Data Entry Format Examples:

Sabre 5.S*UD55-DTMO13-joe.c.traveler.mil@mail.mil

Worldspan 5.Z DTMO13- joe.c.traveler.mil@mail.mil

SITE IDENTIFIER

Provide the government assigned Site Identifier.

Data Capture Requirements:

• All PNR’s

• PNR level

• At booking

Data Entry Format Examples:

Sabre 5.S*UD55-DTMO14-12345

Worldspan 5.Z DTMO14-12345

USE/NON-USE OF CONTRACT AIR

Enter reason code from the table below.

Data Capture Requirements:

• Applicable to all PNRs with air reservations

• All air segments

• Prior to ticketing

Note: DTS passes the applicable reason code in the PNR W (Air) Remarks Field.

Code Description 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

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 17 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 No longer used.

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

C7A Traveler refused contract fare because: Airport specified.

C7B Traveler refused contract fare because: Carrier specified.

C7C Traveler refused contract fare because: Routing specified.

C7D Traveler refused contract fare because: Time specified.

C7E Traveler refused contract fare because: 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.

Data Entry Format Examples (contract carrier used for all four air segments):

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

16 This field is not used 17 This field is not used 18 This field is not used 19 This field is not used 20 This field is not used 21 This field is not used

DoD LODGING NON-AVAILABILITY (NA) CONFIRMATION NUMBER Enter NA confirmation number that is provided by the facility if reported “H1” in Field 9 – Reason Codes for Use/Non-Use of DoD Lodging.

Data Capture Requirements:

• Applicable to CTO/TMC created PNR’s o If DoD lodging arrangements are required by the CTO/TMC contract

• All segments where DoD lodging is applicable and wasn’t available

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 18

Data Entry Format Example:

Sabre 5.S*UD55-DTMO22-S3*16AL222222222222

Worldspan 5.Z DTMO22- S3*16AL222222222222

23 This field is not used.

24 This field is not used.

25 AIR/RAIL COST BY LEG/SEGMENT

Enter airline/rail leg/segment cost using the linear fare construction from the GDS pricing.

Data Capture Requirements:

• All PNR’s with air/rail reservations

• All air/rail segments o For through fares with multiple segments − Enter base fare in the last segment associated to the fare − Enter 0.00 for preceding segments associated to the fare

Pricing Example:

Data Entry Format Examples (based on the pricing example above):

Sabre 5.S*UD55-DTMO25- S1*504.19/S2*157.21/S3*0.00/S4*422.33/S5*0.00/S6*419.53

Worldspan 5.Z DTMO25- S1*504.19/S2*157.21/S3*0.00/S4*422.33/S5*0.00/S6*419.53

TOTAL TRANSPORTATION COST

Enter the total airline, bus, rail, or water ticket cost.

Data Capture Requirements:

• All PNR’s with air, bus, rail, and water reservations

• Ticket level o Enter the total air, bus (individual), rail, and water cost in the last segment associated with each ticket o For bus charters, enter the total cost for the charter

Pricing Example from GDS for air:

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 19

Sabre 5.S*UD55-DTMO26-S6*1667.20

Worldspan 5.Z DTMO26-S6*1667.20

TOTAL BASE AIR/RAIL FARE COST

Enter the total airline base fare.

Data Capture Requirements:

• All PNR’s with air/rail reservations

• Ticket level o Enter the total base air/rail cost in the last segment associated with each ticket

Pricing Example:

Sabre 5.S*UD55-DTMO27-S6*1503.26

Worldspan 5.Z DTMO27-S6*1503.26

28 This field is not used 29 This field is not used

RANK/GRADE OF TRAVELER

Enter the traveler’s military rank or civilian grade code from the table below.

• Applicable to CTO/TMC created PNRs and DTS PNRs with OTECCT

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 20

• Ticket level

DTS passes the traveler’s rank/grade in the PNR (P) Remarks field.

Code Description E1 – E9 Military Enlisted O1 – O9 Military Officer GS1 – GS15 General Schedule (GS) Employees SES1 – SES3 Senior Executive Service NG Non-Government Traveler

Data Entry Format Examples(Traveler’s rank is O2):

Sabre 5.S*UD55-DTMO30-O2

Worldspan 5.Z DTMO30-O2

TRAVELER TYPE

Enter the code from the table below.

Data Capture Requirements:

• Applicable to CTO/TMC created PNRs and DTS PNRs with OTECCT

• Ticket level

• Prior to ticketing

DTS passes the traveler’s rank/grade in the PNR (P) Remarks field.

A Accession Travel (Recruit)

K Contractor/Cost Charge Travel

C Civilian Government Employee

O Military Officer

D Dependent of Military Officer

P Dependent Student

E Military Enlisted

R Human Remains

F Prisoner

S Sponsor

G Dependent of Military Enlisted

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

H Dependent of Civilian Employee

W Warrant Officer

I Invitational

Data Entry Format Examples (traveler is a Military Officer):

Sabre 5.S*UD55-DTMO31-O

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 21

Worldspan 5.Z DTMO31-O

32 ORIGIN/DESTINATION (O/D) INDICATOR

Enter the code in accordance with the instructions below.

Data Capture Requirements:

• All PNR’s with air and rail reservations

• All air and rail segments

• Enter “D” if the segment is for travel between the O/D with no connections.

• For multiple segments/connections for travel between the O/D o Enter “T” in the outbound/connecting segments preceding the destination o Enter “D” in the destination segment

• Prior to ticketing

Example:

Outbound - O/D is DCA to TUS with connections in ATL and DFW.

Return - O/D is TUS to DCA with connection in ATL.

Segment Travel Date Start Finish Fare Basis

O/D Destination Indicator

01 30SEP DCA ATL KCADCA T

02 30SEP ATL DFW LCA T

03 30SEP DFW TUS HCA D

04 14JAN TUS ATL YCA T

05 14JAN ATL DCA YCA D

Data Entry Format Examples (based on the example above):

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

Worldspan 5.Z DTMO32- S1*T/S2*T/S3*D/S4*T/S5*D

33 LOWEST PUBLISHED AVAILABLE RESTRICTED ECONOMY/COACH FARE

Enter the lowest available published restricted economy/coach class fare inclusive of taxes and fees.

Data Capture Requirements:

• All PNR’s

• Enter fare in the last segment associated with each stored fare

• At booking

Example:

Booked Fare

1 AA 175Y 18OCT S*DCADFW SS1 659A 927A

2 AA2472Y 18OCT S DFWSAN*SS1 1035A 1139A

3 AA2491Y 24OCT J*SANDFW SS1 920A 220P

4 AA2239Y 24OCT J DFWDCA*SS1 310P 713P

WPPGVT‡XR«

BASE FARE TAXES/FEES/CHARGES TOTAL

1- USD1588.84 164.36XT USD1753.20GVT

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 22

XT 119.16US 16.00ZP 11.20AY 18.00XF

1588.84 164.36 1753.20TTL

GVT-01 YCADCA YCA YCADCA

Comparison Fare

1 AA 175 N 18OCT S DCA DFW 0659A 0927A

1 AA 2472 V 18OCT S DFW SAN 1035A 1139A

2 AA 2491 S 24OCT J SAN DFW 0920A 0220P

2 AA 2239 S 24OCT J DFW DCA 0310P 0713P 738

1ADT 598.20 598.20

TOTAL FARE - USD 598.20

Data Entry Format Examples (Using the example above):

Sabre 5.S*UD55-DTMO33-S4*598.20

Worldspan 5.Z DTMO33-S4*598.20

34 This field is not used.

CTO TICKET TRANSACTION TYPE

Data Capture Requirements:

• All PNR’s

• Enter the code in the last segment of the ticket

N Original Ticket E Exchange Ticket (value of original ticket exchanged for a new ticket) S Reissued Ticket (Original ticket is refunded and new ticket is issued)

Data Entry Format Examples (new issued ticket with four segments):

Sabre 5.S*UD55-DTMO35- S4*N

Worldspan 5.Z DTMO35- S4*N

36 TRANSACTION FEE RECORD

Enter transaction fee data followed by the applicable codes from the tables below.

Data Capture Requirements:

• All PNR’s o If transaction fee is issued at the point of sale

• PNR level

• Enter the transaction fee number and amount followed by the applicable

Transaction Fee Type Code from Table 1 o If Transaction Fee Type code “CA” (CTO Assist) applies, enter applicable codes from Table 2 and 3 below

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 23 o Additional Codes from Tables 2 and 3 not required for all other Transaction Fee Type Codes

• Separate each data element with a slash (/)

• Upon fee issuance and prior to end transaction

Table 1. TRANSACTION FEE TYPE

AM AMC Patriot Express BT Bus Individual CV Bus Charter CT DoD Contractor Travel CA CTO Assist *Requires entry of codes from Tables 2 and 3 below CR CTO Assist Non-Air/Rail

DT DTS

HR Human Remains

LI LICWO

MD Military Working Dog PT Pet Travel

Table 2. TRANSACTION FEE RESERVATION TYPE

1 Air 2 Rail 3 Car 4 Commercial Lodging 5 DoD Lodging

Table 3. TRANSACTION FEE JUSTIFICATION CODE

A Traveler Requested Assistance via DTS (does not apply to reservations that cannot be booked/ticketed in the contractor's chosen GDS but can be in another GDS).

B Traveler/Government Representative requested assistance via phone, email, fax, or in person resulting in the CTO/TMC’s modifying the DTS PNR.

C Industry Driven (e.g. TSA Secure Flight Data not passed to DTS PNR).

D COR Initiated (e.g. temporary workarounds due to DTS system problem as specified in the PWS).

E Government Travel Charge Card Declined (may only be used with

RESERVATION TYPE 1(Air) or 2 (Rail).

T CTO/TMC created PNR (reservations made as a result of a request made in person, or via phone, email, or fax.).

TR CTO/TMC created PNR (arranged through Transportation Office).

Data Entry Format Examples:

Example 1 - DTS transaction.

Example 2 – CTO Assist transaction, traveler requested assistance with air via DTS.

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 24

Remark Entry Order

Transaction Fee Number/Transaction Fee Amount/Transaction Fee Type/ Transaction Fee Reservation Type/Transaction Fee Justification

Sabre 5.S*UD55-DTMO36-8901234567890/5.00/DT

5.S*UD55-DTMO36-8900987654321/10.00/CA/1/A

Worldspan 5.Z DTMO36-8901234567890/5.00/DT

5.Z DTMO36-8901234567890/10.00/CA/1/A

37 COUNT OF BUS PASSENGERS

Enter 1 for individual bus passengers.

For charters, enter the total number of bus passengers.

Data Capture Requirements:

• All PNRs with bus reservations

• All bus segments

Data Entry Format Examples (example of charter with 26 passengers):

Sabre 5.S*UD55-DTMO37-S1*26

Worldspan 5.Z DTMO37- S1*26

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 25

10. OTHER THAN ECONOMY/COACH CLASS TRANSPORTATION (OTECCT) VALIDATION

The contractor shall support the government’s validation process for all OTECCT by taking the following actions:

• Receive records containing OTECCT segments via email to the address designated by the contractor

• Review records for completeness and accuracy

• Correct missing and erroneous data via the PNR as required

OTECCT Validation analysis shall be submitted to the Government 5 business days after receipt of the email.

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 26

11. COMMERCIAL TRAVEL INFORMATION MANAGEMENT (CTIM) FILE

11.1. GENERAL FILE PREPARATION AND SUBMISSION INSTRUCTIONS

• Provide data on all travel arrangements to include, but not limited to, air, rail, bus, rental vehicle, and lodging arrangements

• Provide a single file per contract

• Provide files for all tickets/invoices issued during the reporting period

• Reporting period is the 1st calendar day of the month through the last calendar day of the month

• Report travel at the segment level, providing data for all segments in the PNR

• Report transaction fee data on the final segment of the ticket to which the fee applies

• Report all tickets issued (original issues, voids, refunds, exchanges, and reissues)

• Left justify values that do not fill the entire field length, do not front fill with a zero(s)

(except as noted)

• Provide files for twelve months after contract expiration

• Use the following file naming convention:

- V06_YYYYMM_###_CONTRACTOR_NAME.TXT

o V06 is internal reference used by DTMO, do not modify o YYYY is the four-digit calendar year o MM format is the two digit month. If the reporting month is January through September, front fill the month with a zero e.g. 01 represents January.

o ### is a unique contract identifier that the government will provide after contract award. If the contract identifier contains fewer than 3 digits, front fill with zeros.

o Example: ABC Travel’s file for activity ticketed/invoiced in October 2015 with a contract ID of 23 would be named V06_201510_023_ABC

TRAVEL.TXT

- Note: Erroneously named files may be rejected and considered undelivered

• Submit data files via the DTMO’s Secure Communications Portal (SCP)

• Register authorized personnel for access to the SCP at:

https://www.dodtvl.com/Passport

• Direct questions regarding access, instructions formatting, and transmissions to:

dodhra.mc-alex.dtmo.mbx.CTIM@mail.mil https://www.dodtvl.com/Passport mailto:dodhra.mc-alex.dtmo.mbx.CTIM@mail.mil

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 27

11.2. FILE PROCESSING REPORTS (FPR) AND DATA CORRECTIONS

• Receive one FPR for each CTIM file and each CTIM corrections file submitted

• Receive FPRs via the contractor’s designated email address

• The FPR will provide data quality statistics and instructions for correcting errors

• The FPR will provide the name of the error file to be downloaded

• Download the error file from the SCP when the FPR indicates data errors

• Not modify the error file name

• Edit the spreadsheet; overwriting the bad data with corrected information

• Submit corrected files via the SCP on the 15th calendar day of the month or 7 calendar days after receiving the FPR, whichever comes later

See Appendix D for sample Error Reports and data corrections.

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 28

11.3. CTIM MONTHLY FILE FORMAT

Field Position Length Field Name/Description

1 1 to 8 8 PREPARING OFFICE

Enter the International Air Transport Association (IATA) code of the ticketing office.

Data Capture Requirements:

• All PNR’s

2 9 to 16 8 TRANSPORTATION CHARGES Enter base fare for each leg/segment using the linear fare construction from the GDS pricing for air and rail. For bus transportation enter the base fare provided by the bus carrier.

Data Capture Requirements:

• All PNR’s with air, bus, rail, and water reservations

• All air, bus, rail, and water segments o For through fares with multiple segments − Enter base fare in the last segment associated to the fare − Enter 0.00 for preceding segments associated to the fare

• Enter positive numbers for refunds

• For ticket exchanges:

o Original ticket, enter the value of segment(s) being exchanged o New ticket, enter the value of the segments o Do not enter the add/collect or refund amount

See Appendix C for various exchange transactions reporting scenarios.

Example – Air Transaction:

Fare Basis Origin Destination Trans. Charges

YDGDCA DCA ORD 504.19 X

YCA ORD OMA 157.21 O

YCA OMA CLT 0.00 X

YCA CLT FAY 422.33 O

YCAIAD FAY CLT 0.00 X

YCAIAD CLT IAD 419.53 O

3 17 to 23 7 TAXES AND MISCELLANEOUS CHARGES

Enter the total taxes and other miscellaneous charges for the ticket in the last segment of the ticket.

Data Capture Requirements:

• All PNR’s with air, bus, rail, and water reservations

• All air, bus, rail, and water segments

4 24 to 24 1 MODE OF TRAVEL Enter code from the list below

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 29

• All PNR’s

A Air

B Bus

R Rail

W Water (Cruise/Ferry/Water Taxi)

O No Transportation Arrangements (i.e. car/hotel only)

5 25 to 27 3 ORIGIN AIRPORT/RAIL/BUS STATION CODE If an airport, bus, rail, or water station code exists, enter the three letter code.

Data Capture Requirements:

• All PNRs with air, bus, or rail reservations

• All air, bus, and rail segments

6 28 to 47 20 ORIGIN CITY If no airport, bus, rail, or water station code exists, enter the origin city.

Data Capture Requirements:

• All PNR’s with air, bus, or rail reservations

• All air, bus, and rail segments

• If the origin city name exceeds the 20 character limit, enter the first 20 characters 7 48 to 49 2 ORIGIN STATE

If ORIGIN CITY is populated, enter the origin state code in accordance with the instructions below.

Data Capture Requirements:

• All PNR’s with air, bus, rail, or water reservations

• All air, bus, rail, and water segments

• For domestic, use the standard two alpha character state codes

• For international, use the two alpha International Standards

Organization (ISO) code 8 50 to 52 3 DESTINATION AIRPORT/RAIL STATION CODE

If an airport, bus, rail, or water station code exists, enter the three letter code.

Data Capture Requirements:

• All PNRs with air, bus, rail, or water reservations

• All air, bus, rail, and water segments

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 30

9 53 to 72 20 DESTINATION CITY If no airport, bus, rail, or water station code exists, enter the destination city.

Data Capture Requirements:

• All PNR’s with air, bus, rail, or water reservations

• All air, bus, rail, and water segments

• If the destination city name exceeds the 20 character limit, enter the first 20 characters 10 73 to 74 2 DESTINATION STATE

If DESTINATION CITY is populated, enter the destination state in accordance with the below instructions.

Data Capture Requirements:

• All PNR’s with air, bus, rail, or water reservations

• All air, bus, rail, and water segments

• For domestic, use the standard two alpha character state codes

• For international, use the two alpha International Standards

Organization (ISO) code 11 75 to 94 20 FARE BASIS

Enter the complete fare basis code.

Data Capture Requirements:

• All PNR’s with air and rail reservations

• All air and rail segments

12 95 to 98 4 BOOKED AIR/RAIL/BUS CARRIER Enter the air, bus, or rail, or water code for the carrier booked.

Data Capture Requirements:

• All PNR’s with air, bus, rail, and water reservations

• All air, bus, rail and water segments

• For air/rail, use standard carrier codes

• For bus and water, use the Standard Carrier Alpha Code (SCAC)

Example: AA 1234 operated by US Airways shall be reported as AA.

13 99 to 102 4 FLIGHT/TRAIN/BUS NUMBER Enter the bus, flight, or train number.

Data Capture Requirements:

• All PNR’s with air, bus or rail reservations

• All air and rail segments

14 103 to 115 13 TICKET NUMBER Enter the airline or rail ticket number.

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 31

• All PNR’s with air or rail reservations

• All air rail segments

• For non-GDS issued tickets, provide the ticket number issued by the air/rail carrier

• For conjunctive tickets enter the first ticket number on all segments

• Enter the PNR locator if the airline does not generate a ticket number

Examples:

1. American Airlines (AA) validated ticket 1234567890 will be entered as 0011234567890

2. Conjunctive tickets 0161234567895 / 896 validated on United

Airlines will be entered as 0161234567895 15 116 to 116 1 ROUND TRIP INDICATOR

Enter the round trip indicator code.

Data Capture Requirements:

• All PNR’s with air and rail reservations

• Enter “R” for the destination segment

• For round-trip tickets, enter “R” for the destination segment and the first segment of the return Routing Connection Round Trip Indicator

JAX – ATL X

ATL – DCA O R

DCA – HSV O R

HSV – JAX O

16 117 to 123 7 RENTAL CAR RATE AMOUNT Enter rental car rate booked.

Data Capture Requirements:

• All PNR’s with car reservations

• All car segments

17 124 to 124 1 RENTAL CAR RATE TYPE Enter code from the table below.

Data Capture Requirements:

• All PNR’s with car reservations

• All car segments

• Code entered should be consistent with the amount entered in the

RENTAL CAR RATE AMOUNT

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 32

H Hourly D Daily W Weekly M Monthly

18 125 to 127 3 RENTAL CAR PICKUP LOCATION If pickup location is at an airport, enter the airport code.

Enter the city code for non-airport pickup locations.

Data Capture Requirements:

• All PNR’s with car reservations

• All car segments

19 128 to 130 3 RENTAL CAR DROP-OFF LOCATION If drop-off location is at an airport, enter the airport code.

Enter the city code for non-airport drop-off locations.

Data Capture Requirements:

• All PNR’s with car reservations

• All car segments

20 131 to 132 2 RENTAL CAR VENDOR CODE Enter vendor code for the rental car company.

Data Capture Requirements:

• All PNR’s with car reservations

• All car segments

21 133 to 133 1 RENTAL CAR VEHICLE TYPE Enter code from the table below.

Data Capture Requirements:

• All PNR’s with car reservations

• All car segments

Code Description M Mini N Mini Elite E Economy H Economy Elite C Compact D Compact Elite I Intermediate J Intermediate Elite K Standard R Standard Elite F Full Size G Full Size Elite O SUV (all sizes)

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 33

P Premium U Premium Elite L Luxury V Van/Minivan W Luxury Elite Y Oversize

22 134 to 134 1 SEGMENT SEQUENCE DESIGNATOR Enter the segment sequence designator.

Data Capture Requirements:

• All PNR’s with air and rail reservations

• All air and rail segments

• Designate the segment sequence in order of travel o The first segment shall begin with A and continue in an unbroken sequence

• Maintain the segment sequence designator for all subsequent reporting including refunds and exchanges

Examples:

Recording sale of a ticket

Origin Destination Segment Sequence Designator

JAX ATL A

ATL LAX B

LAX IAD C

1. Recording partial refund of a ticket

Origin Destination Segment Sequence Designator

LAX IAD C

23 135 to 135 1 DOD COMPONENT

Data Capture Requirements:

• Applicable to CTO/TMC created PNR’s Code Description 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

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 34

24 136 to 138 3 LODGING CITY CODE If an airport or city code exists, enter the three letter code.

Data Capture Requirements:

• All PNRs with lodging reservations

• All lodging segments

25 139 to 158 20 LODGING CITY If no airport or city code exists, enter the lodging city name.

Data Capture Requirements:

• All PNRs with lodging reservations

• All lodging segments

• If the lodging city name exceeds the 20 character limit, enter the first 20 characters 26 159 to 160 2 LODGING STATE

If LODGING CITY is populated; enter the lodging state code in accordance with the instructions below.

Data Capture Requirements:

• All PNRs with lodging reservations

• All lodging segments

• For domestic, use the standard two alpha character state codes

• For international, use the two alpha International Standards

Organization (ISO) code 27 161 to 162 2 LODGING VENDOR CODE

Enter lodging vendor code.

Data Capture Requirements:

• All PNR’s with lodging reservations

• All lodging segments

28 163 to 169 7 LODGING CHARGE Enter the daily lodging rate.

Data Capture Requirements:

• All PNR’s with lodging reservations

• All lodging segments

29 170 to 172 3 LODGING RATE CODE Enter code from the table below.

Data Capture Requirements:

• All PNR’s with lodging reservations

• All lodging segments

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 35

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 XVL DoD Preferred Lodging AAA AAA Rate DoD DoD Lodging

30 173 to 175 3 REASON CODES FOR USE/NON-USE OF CRAF CARRIER

Data Capture Requirements:

• Applicable to CTO/TMC created PNR’s with air reservations

• All air segments

Code Description R0 CRAF carrier used R1 Destination not serviced by CRAF carrier R2 Did not meet mission requirements.

R3 Seat not available.

Traveler refused CRAF carrier because:

R4A Airport specified R4B Carrier specified R4C Routing specified R4D Time specified R4E Personal reasons.

31 176 to 178 3 REASON CODES FOR USE/NON-USE OF CONTRACT AIR Enter code from table below.

Data Capture Requirements:

• Applicable to all PNRs with air reservations

• All air segments

Note: DTS passes the applicable reason code in the PNR W (Air) Remarks Field.

Code Description C0 Contract Fare Used.

C1 Scheduled contract fare flights are not available in time to

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 36 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 No longer used 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

32 179 to 180 2 REASON CODES FOR NON-USE OF AMC AIRLIFT ON INTERNATIONAL

TRAVEL

Enter code from the table below.

Data Capture Requirements:

• Applicable to CTO/TMC created PNRs with international air segments o If reason code is provided by the government or CTO/TMC is required to book AMC/PE per contract

Code Description A1 Destination not serviced by AMC A2 Did not meet mission requirements A3 Seat not available

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 37

33 181 to 182 2 REASON CODE FOR OTHER THAN ECONOMY/COACH CLASS

TRANSPORTATION (OTECCT)

Enter code from the table below.

Data Capture Requirements:

• All PNRs with OTECCT reservations

• All segments with OTECCT

References in description refer to the Joint Travel Regulations, Appendix H3A

Code Description

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 (e.g. Leisure, LICWO, Contractor Travel, etc.)

N Premium class is lower than YCA and/or lower than lowest unrestricted coach fare (e.g. GDS auto-priced premium as the lowest applicable unrestricted fare)

O Airline automatic upgrade (e.g. “UP” fares)

34 183 to 184 2 REASON CODES FOR USE/NON-USE OF DOD LODGING

Data Capture Requirements:

• Applicable to CTO/TMC created PNR’s o If DoD lodging arrangements are required by the CTO/TMC contract

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defense Travel Management Office 38

• All segments where DoD lodging is applicable Code Description H0 DoD Lodging used H1 No rooms available. Non-Availability (NA)

Confirmation Number issued.

H2 Exempted by order issuing agency.

H3 DoD lodging not offered at location.

35 185 to 204 20 NON-AVAILABILITY (NA) CONFIRMATION NUMBER Enter NA confirmation number if reported “H1” in REASON CODES FOR

USE/NON-USE OF DOD LODGING.

Data Capture Requirements:

• Applicable to CTO/TMC created PNR’s o If DoD lodging arrangements are required by the CTO/TMC contract

• All segments where DoD lodging is applicable and wasn’t available

36 205 to 208 4 NON-USE OF DOD PREFERRED COMMERCIAL LODGING Enter code from table below.

Data Capture Requirements:

• Applicable to CTO/TMC created PNR’s

• All segments where DoD Preferred Lodging is applicable

Code Description L1 Too Far Away L2 Mission Requirements L3 Lower Rate Available L4 Personal Choice/Limited Reimbursement L5 DoD Lodging (AKA On-Base Housing) used L6 Lodging with Family or Friends L7 Conference or Event L8 Contract Lodging L9 Rental Housing Used L10 Exempt IAW JTR L11A DoD Preferred Commercial Lodging not available

37 209 to 217 9 DEPARTURE DATE OF TRAVEL Enter departure date for each segment.

Data Capture Requirements:

• All PNR’s 38 218 to 226 9 ARRIVAL DATE OF TRAVEL

Enter arrival date for each segment.

Travel Management Office Data Requirements Version 4.2.1 11 MAY 2017

Defen…