![]() |
Huh - can't find any update avail and still crashes??
|
https://fxpilot.info/php_uploads/fxpilotLogin.php
For those with an autopilot subscription |
[QUOTE=Overnitefr8;1803414]Company doesn't care who flies the trips. Now they may have something at the bargaining table to offer if we're willing to give up something to get it coded.
Does any suppose The Wolf Pack got gouge on the new Open Time format????? |
Again, in fairness to the company, they did give us a heads up, just not all of the changes were included.
There was an effort to work with us. |
OK, I give up. What is the significance of the blue highlight on certain trips in open time?
MG2 |
My guess is it is pm return to Mem.
|
From what I can tell, blue is afternoon launches, white is a.m launches.
|
Nothing new
Originally Posted by av8rdude
(Post 1803383)
Maybe the new format will now allow a code that a particular pairing is Disputed.
The info is not secret, but it takes some effort to keep up with which pairings are disputed. I would bet some are picked up by honest mistake, which still undermines the dispute process and the efforts of our scheduling improvement team. If there was something like a "DISP" trip type, I bet it would cut down on that happening. It would also eliminate the "excuses" of some who would flout the dispute process just because a certain pairing happens to suit their personal needs in a particular instance. Several years ago I was looking at Open Time and saw those evil Disputed Pairings marked as DSP or DISP or something like that. There was even discussion on APC (if I recall correctly) about it. Shortly thereafter, BAM, it was gone. The crew "view" still doesn't include Disputed Pairings but others (Scheduling, Management, etc.) "view" probably has it in there (and probably) always has. A very simple programming change could make it available to the crews, but of course, that would be helpful to the crews, so that will not happen. |
Originally Posted by Red Letter
(Post 1806410)
Several years ago I was looking at Open Time and saw those evil Disputed Pairings marked as DSP or DISP or something like that. There was even discussion on APC (if I recall correctly) about it. Shortly thereafter, BAM, it was gone.
The crew "view" still doesn't include Disputed Pairings but others (Scheduling, Management, etc.) "view" probably has it in there (and probably) always has. A very simple programming change could make it available to the crews, but of course, that would be helpful to the crews, so that will not happen. The schedulers can absolutely see them. No programming change necessary for us to see them. They just have to turn off the hide function. |
I once proposed at an MEC meeting that "Disputed Pairings" be assigned a "D" code before the number; D386 ... D1763 ... DX254 ...
I was quickly brushed off (by my own union?) and told that Management had absolutely no motivation to do that and that it would NEVER happen!*? How about if we include it in Contract Negotiations? :eek: |
| All times are GMT -8. The time now is 11:59 AM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands