Originally Posted by
simons1
It isn't rocket science, but there are data protection requirements and legacy systems involved and if a batch of data went astray people would be straight on here to complain.
There must be millions of these transactions every year, 99.9% will go smoothly but inevitably there will be occasional issues. I saw mention of a typhoon on the cross posted thread, perhaps some IRROPS issue affected this one.
Oh come on, I work in the mobile telecoms field and our data processing is orders of magnitude greater than the airlines' ... yet somehow we manage to comply with data protection across mutliple global jurisdictions AND bill customers correctly 99.999% of the time...
The core Oneworld data exchange requirement is not even rich, it's something like:
{FAMILY NAME}
{GIVEN NAMES}
{FQTV}
{ORIGINATING AIRPORT}
{ORIGINATING DATE}
{ORIGINATING DEP TIME UTC}
{DESTINATION AIRPORT}
{DESTINATION DATE}
{DESTINATION ARR TIME UTC}
{CARRIER}
{CABIN FLOWN}
and if QR fly about 32m pax in 2017 (per their Annual Report) then that's a maximum less than 100k rows of data a day - I meam, honestly, the work experience moppet could manage it on a spreadsheet
None of which means that getting data out of legacy systems is a doddle - it certainly isn't. But this is not a dynamic real-time request building reports on the fly: it's a bog-standard scehduled batch job, hence "not rocket science" !!!