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