The system we use loops back multiple times during the runs for 14,000 plus pilots. Once the runs are complete they are sent over to ALPA to audit. ALPA often asks for reruns before approval. If we give up are ability to audit the results I am sure the company will be quite happy to provide a earlier completion date.

 

I guess I don’t understand what the variables are then. What do they change before it is run again? The pairings are already decided so the only thing I can see them changing is the amount of open time allowed, hard lines vs reserve and maybe average line credit.

 

I have seen it where they try and give you more trips or more time. There are multiple outcomes to getting what you asked for.

 

They publish the ALV and the bid window. They can run a solution that has buffers at the high and low end as long as they don't exceed the window. They can limit the number of 'Min credit' and 'Max credit' bids. I'm assuming they can tweak the number of RLLs. And they can adjust the open time constraints as long as they don't exceed PWA limits.

Lots of things to get the "cost" of a run down. Run/evaluate/run/evaluate/run/evaluate/send to ALPA for review/PUBLISH.

 

Remember, the Company can move the threshold line value anywhere within the LCW and that will have varying outcomes. Take a look at the top of your category's Wide Report and see where the threshold line value ended up.

 

I see no reason 717 pilots should wait for 777 pilots' schedule completion, or vice versa? Why can't they be released as they are completed and reviewed by ALPA?

 

Exactly. If there were issues with the 717, they could run everything else first. Then do the 717 when the bid closed. Oh well, the As are out at least.

 

This is just for the curious.

There's a way you can see the trips it is assigning as it makes it's runs. I counted at least 5 runs on the B side. The final run occurring after the union looked it over I'm guessing. What I've seen is, sometimes the last trip or two in the month may change from run to run, but the first part of the month is usually pretty much the same each run. It gives you a very good idea of the exact days off you'll have.

Here is the bad grammar version for those who want to have at it:

They is a way you's guys can see the trips it is assignen as it makes it's runs. I cownted at least 5 runs on the B side. The final run okurring after the union looked it over I'm gessing. What I done saw is, sometimes the last trip or too in the month may change from run two run, but the first part of the munth is usualie pritty much the same each run. It gives you very good eye-dea of the eggsact days off you'ns will have.

 

I'm certainly no expert, but what dobbs said. The threshold is also a big variable they can tweak and rerun. The thresholds are publish in the at big line of gobbledegook on the top line of every page in the wides...just look for the number after the T. The next few digits/numbers will also let you know what run was used, though the naming convention isn't readily apparent. The threshold is also published in the reasons report.

If you want to see how the process work, give the PBS guys or the company a call. They're probably willing to have you down for the bid run and see what all goes on in the background. Like many things in life, it's always informative and enlightening to take a peak under the hood, rather than just sit back and chuck spears.

 

They once released the schedules in batches of two or three runs. It was also much easier to backdoor your schedule early. They did however put out over and over again that schedules were never final until posted in DBMS. Despite the above they were inundated with phone calls and slammed on forums when a category was rerun and schedules changed prior to posting in DBMS. Seemed often to be someone claiming they ran out and spent 10 grand on a vacation they can’t change. They got tired of it. Frankly I am surprised they don’t just wait until 6 PM on the 17th to post them all.