If I look at route details for a given flight, I get a breakdown of connecting PAX from/to own/external feeders.
Is there a way to drill down on this ?
ie. If I see that there are 52 pax that are connecting from my own flights, how could I find out which flights they are connecting from ? This info would help me a lot planning schedules etc.
I was planning on asking if we could add a feature to allow us to see exactly which flights our connecting PAX were taking. This would help route management immensely.
In addition to its usefulness, realism would also be increased. Airlines obviously know which PAX are taking which flights and to what final destinations within their own network.
At the moment we can not provide you this statistic. It is often wished, but the information is only available for a part of a second during the demand calculation and especially at the larger airports we have some millions of connetions for booking. Storing the detailed information about transfer passenger would blow up the processing time and the system would not be able to handle it (server performance). And no - faster server will not help ;)
The demand is calculated based on a mathematical formula and certain source data. This historical source data will be available at least for some time after the demand calculations are done. Key question: are there random elements in the calculation ? If not then can't we simply redo the calculation and come up with the same results ?
ie. On demand, when we want to examine this data, we would simply redo the math from the data that is still stored and come up with the same results.
or
Re-do the math separately in the background for reporting purposes only. That way the demand calculation itself would not be effected, and the connection data would be available, albeit a bit later but that would be perfectly ok as it is meant for business analysis anyway.
I assume the recalculation would not even have to be 100% accurate with the original calculations. It would still give the indication needed for network planning.
Thank you for your thoughts, we have them too, but currently there is no chance for this. We would love to have these data too, but the performance of the server is not allowing us to do so. There are 12 years of sometimes hurting experiences ;)
Regarding this matter And as i am new in the game i have another question... How can we see witch companys are giving feed back on our Interlining ?? As an example if you have 2 interline agreements in France is there any way to see from the external feeders who is giving the passengers ??
Regarding this matter And as i am new in the game i have another question... How can we see witch companys are giving feed back on our Interlining ?? As an example if you have 2 interline agreements in France is there any way to see from the external feeders who is giving the passengers ??
Unfortunately there is no possibility to know from which airline external passengers are coming from unless you have just one interlining partner.
As far as I understand, the demand calculation is only calculating the flights that originate from that particular airport. Each airport has a specific time that it's demand calculation would go through. So if Airport A has a demand calculation time at 01:00, all you'd have to do is check all your routes that could possibly start at Airport A. If there's an increase on one flight, even if it's between two different airports (say Airport B and Airport C), and neither B or C had demand calculations between 01:00 and when you checked, then you'd know they originate from Airport A and take a particular route. Knowing the transfer times and arrival and departure times of your planes, you could eventually reconstruct the passenger's entire "ticket".
I am bringing this up again as I had a new idea on how to possibly gain access to this data.
Would a feature work, where I could tag a flight for analysis. For example if B is my hub, I could tag a flight from A to B for analysis so that when A computes the demand, the information on which flights the A PAX are connecting to at B would be saved.
In order to save server resources, I would be able to tag only one or two flights at a time, and the tag would be automagically removed after A has computed.