"Your research and presentation proved to be a great investment."
Free For: Innovation Subscribers
- Summary
- Contents
Publication Summary
The passenger name record (PNR) has been the backbone of travel planning ever since automated travel reservations have been in existence. Born on highperformance legacy computer systems, the PNR became the core computer file for documenting and provisioning a travel reservation, effectively serving as the purchase and delivery order for travel. Because of its legacy roots when computing and communications were much more expensive than today, the PNR is concise and cryptic. Processes were built around the PNR to ensure the party delivering the travel service (e.g., the airline or hotel) received all needed
information. Similarly, processes and business logic were put into place for service providers to advise global distribution systems (GDSs) and travel agents (TAs) when there was a problem delivering a reserved service (e.g., an airline schedule change).
Table of Contents
11 Pages
Introduction
Trip Centric or Passenger Centric?
PNR Structure
SuperPNR to the Rescue
Complex Booking Scenario
Building a SuperPNR Repository
Operating a SuperPNR Repository
Alternatives
Third-\302\255Party Tools
TripIt
Conclusion
References
Sources of Further Information
Glossary
Appendix 1: PNR Example
