Attachment 8_PNR Validation Process 15Dec10.doc

DOC document 31 KB Posted

Attached to
DTMO Commericial Travel Services Federal contract opportunity
Solicitation number
H98210-10-R-0006
Issued by
Defense Human Resources Activity

About this file

Attachment 8 PNR Validation

View the file

Other files for this federal contract opportunity

Other files attached to DTMO Commericial Travel Services, newest first.
File Type Posted
Wayne County North Carolina.pdf PDF
H98210-10-R-0006 Amend 4.doc DOC document
Bay County Florida.pdf PDF
Pima County Arizona.pdf PDF
ST.CLAIR COUNTY IL 05-2310.pdf PDF
KERN COUNTY CA 05-2044.pdf PDF
Curry County New Mexico.pdf PDF
Lowndes County Mississippi.pdf PDF
Orleans Parish Louisiana.pdf PDF
FRANKLIN COUNTY TN 05-2492.pdf PDF
YORK COUNTY 05-2544.pdf PDF
SUMTER COUNTY 05-2476.pdf PDF
OTERO COUNTY NM 05-2512.pdf PDF
Shelby County Tennessee.pdf PDF
TOOELE COUNTY UT 05-2532.pdf PDF
Montana Statewide.pdf PDF
Val Verde County Texas.pdf PDF
CLARK COUNTY NV 05-2332.pdf PDF
SOLANO COUNTY CA 05-2070.pdf PDF
Maricopa County Arizona.pdf PDF
PIERCE COUNTY WA 05-2568.pdf PDF
HOUSTON COUNTY GA 05-2140.pdf PDF
San Bernardino County California.pdf PDF
OKLAHOMA COUNTY OK 05-2432.pdf PDF
HILLSBOROUGH COUNTY FL 05-2126.pdf PDF
KENT COUNTY DE 05-2098.pdf PDF
MIDDELSEX COUNTY MA 05-2256.pdf PDF
Jackson County Oklahoma.pdf PDF
City Pair Information SBS Top 10 Origin Destinations.xlsx XLSX spreadsheet
H98210-10-R-0006 MOD 2.doc DOC document
Attachment 2_SBTA 4_Contract Requirements_30 Mar 11.docx DOCX document
Attachment_10_PNR_Data_Elements_30 Mar 11.docx DOCX document
Attachment 4_SBTA 4_Site Data Sheet_31 March 2011.docx DOCX document
Attachment 7_Part 2 Army Reconciliation Process_15 Dec 10.doc DOC document
Attachment 10_PNR Data Element121510.doc DOC document
Attachment 3_SBTA2_workloadsheet_122010.xls XLS spreadsheet
Attachment 4_SBTA 6_Site Data Sheet_21 Oct 10.doc DOC document
Attachment 12_Example Travel Daily PNR Spreadsheet122210.xls XLS spreadsheet
Attachment 1_Definitions and Acronyms_22 Dec.doc DOC document
Attachment 2_SBTA 2_Contract Requirements_ 7 Mar 11.docx DOCX document
Attachment 2_SBTA 4_Contract Requirements_7 Mar 11.docx DOCX document
Attachment 4_SBTA 2_Site Data Sheet_21 Oct 10.doc DOC document
Attachment 4_SBTA 5_Site Data Sheet.doc DOC document
Attachment 9_DD 254.pdf PDF
Attachment 6 CTO Data Requirements 22DEC10.doc DOC document
Attachment 2_SBTA 1_Contract Requirements_7 Mar 11.docx DOCX document
Attachment 4_SBTA 1_Site Data Sheet.doc DOC document
Attachment 3_SBTA1_workloadsheet_122010.xls XLS spreadsheet
Attachment 2_SBTA 6_Contract Requirements_7 Mar 11.docx DOCX document
Attachment 13_DTS PNR Format Instructions.doc DOC document
Show all 50

DTMO Commericial Travel Services has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Attachment 8

PNR Validation Process

Commercial Travel Office

Passenger Name Record Validation

(CTO PNR Validation)

Requirement:

A commercial travel office (CTO) submitting a proposal for the follow-on CTO acquisition must complete a CTO PNR Validation configuration worksheet to be eligible for contract award. However, it is not necessary to participate in a PNR Validation if the CTO is using a Pseudo City Code (PCC) that is currently connected to DTS. Under a joint venture, if all parties have different PCCs, Airline Reporting Corporation (ARC)/International Air Transport Association (IATA) numbers and contact information, a worksheet would be required for each CTO and participation in the PNR validation would be required if one or both CTOs PCC isn’t currently connected to DTS.

Background:

The PNR validation is a process that confirms the Defense Travel System’s (DTS) ability to exchange a passenger name record (PNR) with the commercial travel office (CTO) and provides the CTO an example of an actual PNR that will be delivered from DTS.

Additionally, it assures DTS can send a PNR to the CTO on a specified queue and then sweep the PNR from the CTO outbound queue back into DTS.

This process validates the technical aspects of CTO connectivity and provides the CTO the experience transmitting data with DTS.

CTO PNR VAlidation PROCEDURE

1.

Contact dtmocontracting@dtmo.pentagon.mil to request the configuration worksheet. The worksheet lists the technical requirements for DTS to deliver a PNR to the CTO. The worksheet will be sent directly to the person requesting the validation.

2.

Complete the configuration worksheet, making sure to specify the preferred GDS, Pseudo City Code, 4 queues, 2 terminal addresses, and the company profile as listed in the GDS.

3. Return the configuration worksheet to dtmocontracting@dtmo.pentagon.mil. If you have questions regarding the worksheet, contact Kim Shine at 703-696-8039 or Susan Buckalew at 703-696-7374.

4.

Email DTMO contracting to schedule the validation test (This request may be included with Step 3). It may take 2 to 3 weeks to set up the validation and less than a day to complete it.

5.

Set up branch access within the agreed GDS.

6.

Receive a DTS PNR in your requested queue.

7.

Place the observed DTS PNR on the specified outbound queue for DTS to sweep.

8. Verify with DTS that the PNR was received

9. Print the validated PNR, saving a copy for your records.

Deadline: Offerors shall complete this procedure no later than thirty (15) days 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 procedure.

File details come from the government source that posted it. Updated .