The second important data in the system is passenger information for each flights. The preparation of the PNRGOV message is dependent on this data and can be blocked for individual sending if the passenger list is not completed.
Getting data from Leon
If you use the Leon software, all you need is to prepare the user to whom PnrGo will connect to your flight database. It should have the following permissions:
PnrGo will track your flights every 5 minutes and take all of passengers for flights classified as a PNR. The data collected for each passenger are:
- first name and last name
- date of birth
- travel document: number, country and expiration date
Please note Leon is processing only PASSPORTS at the moment, but passengers are able to travel with ID CARD as well. The issue is requested to Leon, but it takes a while for them to prepare a solution. At the moment PnrGo has implemented a workaround to use a notes (description) field on passport record. You can define one of below scenario for you:
- Skip recognizing ID CARDs at all.
- Treat passport as ID CARD, when ANY note is added.
- Treat passport as ID CARD, when SPECIFIC phrases are added on the note field.
Managing passengers manually
PnrGo allows you to manage passengers manually. You can add, edit and remove PNRs and Passengers using user interface. You can also import them from XLS, XLSX or CSV file as well. You can read more about these actions in User Interface section.
Receiving PAXLST from DCS systems
The most effective and reliable way to get the passengers' data is to get them after check-in from the DCS system. PnrGo offers two methods of integration: via the PAXLST standard, sent via TypeB or email. Data received in this form have priority over others. To configure the PAXLST reception, all you need to do is instruct the handlers about the preferred pushing method. Details of the implementation and data format are described in a separate document.