Attachment_6_PNR_Validation_Configuration_Worksheet_Final_16April18.pdf

TMC DoD OBT PNR Configuration

2 Defense Travel Management Office

DEFENSE TRAVEL

MANAGEMENT OFFICE

Travel Management Company

Passenger Name Record Validation (TMC PNR Validation)

Requirement:

A Travel Management Company (TMC) submitting a proposal for acquisition must complete a TMC Passenger Name Record (PNR) validation configuration worksheet to be eligible for contract award. The TMC shall submit a PNR validation configuration worksheet containing all Pseudo City Codes (PCCs), the Airline Reporting Corporation (ARC)/International Air Transport Association (IATA) number and contact information.

Under a joint venture, if parties have different PCCs, ARC/ IATA numbers and contact information, a separate PNR validation worksheet must be submitted. It is not necessary to participate in a PNR Validation if the TMC is submitting a PCC currently connected to the Department of Defense (DoD) Online Booking Tool (OBT).

Background:

The PNR validation is a process that confirms the DoD OBT’s ability to exchange a PNR with the TMC and provides the TMC an example of an actual PNR that will be delivered from the DoD OBT.

Additionally, the process assures the DoD OBT can send a PNR to the TMC on a specified queue and sweep the PNR from the TMC outbound queue back into the DoD OBT.

This process validates the technical aspects of TMC connectivity and provides the TMC the experience transmitting data with DoD OBT.

TMC PNR Validation Procedure:

1. The attached configuration worksheet contains the technical requirements for the DoD OBT to deliver a PNR to the TMC.

2. Complete the configuration worksheet, making sure to specify the preferred Global Distribution System (GDS), PCC, five (5) queues and the company profile listed in the GDS.

3. Send the completed configuration worksheet to:

dodhra.mc-alex.dtmo.list.contracting@mail.mil to schedule the validation test. It may take up to thirty calendar (30) days to schedule the validation.

4. Set up branch access within the preferred GDS (Sabre or Worldspan).

5. Receive a DoD OBT PNR in your requested queue.

6. Place the test DoD OBT PNR on the specified outbound queue for the DoD OBT to sweep.

7. Verify with the DoD OBT the PNR was received.

8. Print the validated DoD OBT test PNR, saving a copy for your records.

Deadline: Offerors shall submit the PNR configuration worksheet prior to the proposal due date.

Offerors shall be deemed to have satisfied this requirement when the Government receives confirmation that the PNR validation has occurred in accordance with the above procedures.

Any questions regarding the worksheet, contact DTMO Movement Management Branch (MMB) at 571-372-1300.

mailto:dodhra.mc-alex.dtmo.list.contracting@mail.mi

3 Defense Travel Management Office

DEFENSE TRAVEL

MANAGEMENT OFFICE

TMC DoD OBT PNR Configuration Worksheet

This worksheet contains the necessary information to begin your DoD OBT connectivity process that will allow DoD OBT to automate applicable data with your PCC.

TMC:

Joint Venture TMC: (if applicable) Name:

Address 1:

Address 2:

City / State / Zip Code:

ARC/IATA Number:

Solicitation Number:

TMC will support (site/sites):

TMC POC:

Telephone:

Email:

Alternate POC:

Telephone:

Email:

If submitting under a Joint Venture (select yes or no)?

Yes ☐ No ☐

Authorized Name and Title Signature Date

4 Defense Travel Management Office

1. GDS used to support this contract (check all that apply):

Sabre ☐ Worldspan ☐

2. Pseudo City Codes (PCC) and GDS Queues:

• Include minimum of one PCC/OFFICE ID for each GDS identified above.

• Identify the five queues for each PCC/OFFICE ID.

• When more than one PCC/OFFICE ID is identified for a GDS, identify the queues associated with each PCC/OFFICE ID and the DoD sites/locations.

PCC/OFFICE ID Ticketing Queue Cancellation Queue Inbound Queue Polling/Outbound

Queue Urgent Queue

Explanation of Queues Used in DoD OBT:

• Ticketing queue – Approved DoD OBT PNRs will be placed on this queue three (3) business days prior to travel.

• Cancellation queue – Authorizations cancelled in DoD OBT PNRs will be placed on this queue.

• Inbound queue – Any new/changed DoD OBT PNRs will be placed on this queue.

• Polling/Outbound queue – Outbound queue for TMC’s to return PNRs to DoD OBT.

• Urgent queue – Any new/changed DoD OBT PNRs within three (3) business days prior to travel or if earlier ticketing is required will be placed on this queue.

3. Company Profile set up to support DoD OBT:

Each PCC/OFFICE ID listed in Item number 2 above must be associated with a Company Profile, as identified below: (Sabre – Profile; Worldspan – 2nd level Worldfile)

PCC/OFFICE ID User File /Company Profile Name

5 Defense Travel Management Office

4. Quality Control Applications:

NO quality control applications are to be attached to a DoD OBT profile or PCC/OFFICE ID that requires a mandatory field prior to ending a PNR.

Examples to check if you have mandatory edits turned on

Sabre – Flex edits (W/K*TJRALL)

Worldspan – Worldfile edits

5. Required PCC/OFFICE ID Settings for DoD OBT

• Sabre:

Automatic hotel description Off (HIP¤AUTOHOD)

12‐Hour Clock On

• Worldspan:

Worldspan (AIR Table)

12‐Hour Clock On (DEF/A)

Hotel Property Code turned On (H/L)

PowerShopper On

Note: PNR will require the PI stored

6. Remark Qualifiers:

The following table identifies the “alpha qualifiers” to be used to identify traveler record information for air, car, hotel, personal and any additional information.

The “DoD OBT‐to‐TMC Qualifiers” are preset by the DoD OBT and cannot be changed.

Remark Subject

OBT to TMC Qualifier (pre‐set) TMC to OBT Qualifier

Air W E

Car X D

Hotel Y G

Personal P P

Change A

6 Defense Travel Management Office

GDS Branch Access Procedures

Worldspan:

KYApseudo

Template appears, tab and change N to Y in the following fields:

Access PNRs Access Queues Allow

QEP/QEM

Access Profiles Emulation Enter

Display Branches KY*

Emulation format:

4@Epseudo End Emulation:

4@EOFF

Sabre:

SI9

W/TAATMCPCC#AOBTPCC

W/TAATMCPCC#BOBTPCC

Delete Branch Access

Worldspan:

KY* ‐ lists all branched PCCs

KYDpseudo being deleted

Sabre:

SI*9

W/TADour pcc#B pcc to be deleted

W/TADour pcc#A pcc to be deleted