Attachment 1 - USFK PNR Validation Worksheet (REV)_Clean_2026-08-05.docx

CUI

Attachment 1 - PNR Validation Worksheet V2.7 August 2026 Attachment 1 – United States Forces Korea (USFK) Travel Management Company Passenger Name Record Validation Configuration Worksheet August 2026 – V2.7 Background:

The Passenger Name Record (PNR) Validation Configuration is a process that confirms the Department of Defense Online Booking Tool (DoD OBT) has the ability to exchange a PNR with the Travel Management Company (TMC) and provides the TMC with an example of an actual PNR that is delivered from the DoD OBT. Additionally, the process assures that the DoD OBT can send a PNR to the TMC on a specified queue and can 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 of exchanging data with the DoD OBT. The current DoD OBT only supports Sabre and Worldspan Global Distribution System (GDS).

Requirements:

A TMC submitting a proposal for an acquisition must submit a completed TMC PNR Validation Configuration Worksheet. The TMC must “PASS” the PNR Validation to be eligible to bid on the contract and be eligible for contract award. The PNR Validation Configuration Worksheet must contain the GDS, all Pseudo City Codes (PCCs)/Site Identification Codes (SIDs), the Airline Reporting Corporation (ARC)/International Air Transport Association (IATA) Numbers, Queue Assignments, Company Profiles/Worldfiles and contact information on or before: hh:mm am/pm Month, Day, Year (to be added by the Contracting Officer specific to each solicitation) Under a joint venture or subcontractor, if parties have different PCCs/SIDs, ARC/IATA Numbers, Queue Assignments, Company Profiles/Worldfiles and contact information, each TMC must submit a separate TMC PNR Validation Configuration Worksheet.

The TMC is required to submit a PNR Validation Configuration Worksheet, as a notification of intent to the Government. The TMC shall submit the PNR Validation Configuration Worksheet, irrespective of whether the TMC intends to use the same PCC/SID/Queue Assignments/Company Profiles/Worldfiles already connected to the DoD OBT.

For GDS submissions, all travel fulfillment operations, ticketing, and Pseudo City Codes (PCCs) must reside exclusively on the standard Global Host (Example: Sabre GDS Code 1S, Worldspan 1P).Configuration changes (e.g., Company Profiles/Worldfiles, Queue Assignments) to the current connection of a PCC/SID, shall be identified in Table 2. The PCC/SID submitted herein, whether for a prime or sub-contractor, shall remain the same and cannot be revised between the PNR Validation Configuration Worksheet submission date and the service start date of the contract. Any request for changes must be submitted to the Contracting Officer (CO) for approval.

In the event there are multiple PCCs/SIDs submitted, the Government reserves the right to conduct a random sampling during the PNR Validation testing process.

The TMC shall be deemed to have satisfied this requirement when the TMC submits a copy of the validated DoD OBT test PNR to the Contracting Officer, (CO) in accordance with the validation procedures.

TMC PNR Validation Procedures:

Fill out and complete Table 1.

Fill out and complete Table 2 and Table 3 of the TMC PNR Validation Configuration Worksheet, making sure to specify the GDS, PCCs/SIDs, five (5) different Queue Assignments and the Company Profiles/Worldfiles.

Sign and date the PNR Validation Configuration Worksheet.

Submit the completed TMC PNR Validation Configuration Worksheet by:

(CO to add hh:mm am/pm Month, Day, Year) to (CO to add their email address).

Open Branch/Bridge access within the GDS (Sabre or Worldspan).

Receive a DoD OBT test PNR in the queues identified in Table 2.

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

Receive verification the test PNR was received in the DoD OBT.

Submit a copy of the validated DoD OBT test PNR to the Contracting Officer, (CO) at:

(CO to add their email address).

Table 1.

No Yes

10. If submitting under a Joint Venture or Subcontractor (select yes or no)?Sabre Worldspan

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

Pseudo City Codes (PCC) / Site Identification Codes (SID) and GDS Queue Assignments:

Include a minimum of one (1) PCC/SID for the GDS identified above.

Identify the five (5) different Queue Assignments for each PCC/SID in Table 2.

Identify the Queue Assignment Numbers associated with each PCC/SID in Table 2.

(No categories for Worldspan or prefatory codes for Sabre shall be listed, list only the queue numbers).

Table 2.

Sabre: ABC1 Worldspan: 1AB (Example)

*Modify Table 2 with additional rows as needed to satisfy the requirement.

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

Company Profiles / Worldfiles set up to support DoD OBT:

Each PCC/SID listed in Table 3 must be associated with a Company Profile/Worldfile, as identified in the examples below:

(Sabre – Profile; Worldspan – 2nd level Worldfile) A Company Profile/Worldfile MUST be provided for each site/location associated with the PCC.

Examples:

Dashes must be included in Sabre profiles

No spaces or dashes in Worldspan Worldfiles

Identify characters that can be misinterpreted (i.e., number 0 for letter O, number 1 for letter l etc.). If the PCC/SID or Company Profile/Worldfile Name used by the TMC contains an ambiguous character, specify this in the comments column below.

Table 3.

Worldspan Worldfile Name Comments

Sabre: ABC1 Worldspan: 1AB

-ABC1-HAPPYTOWN

HAPPYTOWN

ABC1 (number 1) 1AB (number 1)

*Modify Table 3 with additional rows as needed to satisfy the requirement.

Quality Control Applications:

NO quality control applications are to be attached to a DoD OBT profile or PCC/SID 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 Required PCC/SID Settings for DoD OBT:

Note: PNR will require the PI stored Remark Qualifiers:

Table 4. identifies the “alpha qualifiers” to be used to identify traveler record information for air, car, hotel, personal, change and any additional information.

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

Table 4.

(pre‐set) TMC to DoD OBT Qualifier

GDS Open Branch/Bridge Access Procedures:

Sabre:

SI9

W/TAATMCPCC#AOBTPCC

W/TAATMCPCC#BOBTPCC

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

Delete Branch/Bridge Access Procedures:

W/TADour pcc#B pcc to be deleted W/TADour pcc#A pcc to be deleted

Worldspan:

KY* ‐ lists all branched PCCs KYDpseudo being deleted

Authorized Name and Title (Printed)

Signature

Date

Department of Defense | Defense Human Resources Activity

image1.png image2.png