The PNRGOV message is designed to comply with Governments’’ Legislation for the provision of PNR data from carriers. There are two technical standards in use: EDIFACT and XML. Both od them are in use, however the EDIFACT is more popular while the XML is newer one. PnrGo implements both of them as well.
Structure of the message
A message always contains the flight leg header and PNRs (reservations). Regular carriers who use booking systems for one flight generate a lot of PNRs. Others who, for example, specialize in charter flights, usually do not sell individual tickets and do not use reservation systems. In this case, all passengers can be treated as a collection for a single PNR.
PnrGo application was designed to support both scenarios, however in most cases (automatic implementation) carriers use the second one. The passenger list usually is taken from external systems as one set, so only one PNR is created. If you want to edit flight manually you can create next PNRs and compose passenger lists as needed.
Depending on the country, the list of submission times may vary. PnrGo has a flexible configuration that allows you to define freely different configurations for individual countries. For example for Poland pushes are defined at -25hrs and ATD (wheels up).
The submissions therefore depend on the STD and ATD times and it is necessary that these times be processed in the system. While the STD time is part of the data in the schedule, ATD time is delivered separately with possible delays or even it could be not received at all. Therefore, in the PnrGo application, the monitoring module analyses every flight and sends warnings in the event of delay. The parameters of delays and the frequency of alerts are configurable.