Skywest
#5093
Think of a CN as Company Needs and a PN as Pilot Needs. Basically PBS was unable to complete the pilot’s line within the 7 layers PBS allows a pilot to bid. If PBS cannot complete a pilot’s line within those 7 layers the system will select a pairing for them from the available pairing pool to complete his or her line. This is absolutely what you DO NOT want to have happen because if you allow the system to move past layer 7 you’ve now given complete control of your bid to PBS which will assign whatever pairings it so chooses in order to formula a solution.
Piedmonster has fallen prey to a very common mindset. He/She (sucks not knowing a posters sex) thinks he's/she's "very good with PBS" when in actuality he/she is not and does not understand the system at all. Because of his/her inability to bid properly more JR pilots to him/her are getting far better lines. Much like PerpetualFlyer stating.
Hopefully understands what I'm posting, digs deeper into the Online Docs and re-evaluates his/her approach. If Peidmonster doesn't he'll/she'll continue to get crap lines and those behind him/her benefit.
Piedmonster has fallen prey to a very common mindset. He/She (sucks not knowing a posters sex) thinks he's/she's "very good with PBS" when in actuality he/she is not and does not understand the system at all. Because of his/her inability to bid properly more JR pilots to him/her are getting far better lines. Much like PerpetualFlyer stating.
Hopefully understands what I'm posting, digs deeper into the Online Docs and re-evaluates his/her approach. If Peidmonster doesn't he'll/she'll continue to get crap lines and those behind him/her benefit.
Last edited by MatchPoint; 05-19-2014 at 01:07 PM.
#5095
Gets Weekends Off
Joined APC: Sep 2008
Position: B767
Posts: 1,901
I was trying to help one of our FAs today with her bid... Or rather, help her understand it. She needed a specific day off, and bid for it in EVERY layer!! She also really wanted a specific pairing, and bid for that in 1-5 as well. So 1-5 were all the same 2% of pairings, and she "opened it up" for 6-7 by deselecting the desired pairing. Her entire month was garbage CNs, and despite my explaining why it happened she just couldn't understand it. She's been here longer than me!
#5096
#5097
I was trying to help one of our FAs today with her bid... Or rather, help her understand it. She needed a specific day off, and bid for it in EVERY layer!! She also really wanted a specific pairing, and bid for that in 1-5 as well. So 1-5 were all the same 2% of pairings, and she "opened it up" for 6-7 by deselecting the desired pairing. Her entire month was garbage CNs, and despite my explaining why it happened she just couldn't understand it. She's been here longer than me!
#5098
Gets Weekends Off
Joined APC: Apr 2009
Position: CL-65 / Gear Wrangler
Posts: 321
I am an expert at PBS, you need to understand a CN means the company screwed you and a PN means you screwed yourself!!!
Trying to get too restrictive for your seniority (weekends off, 22+hr commutable trips, etc.) and not properly opening up your bid by layer 7 is the most common way people screw themselves. The key to PBS is understanding how each parameter works in relation to each other both within a layer and as the system moves through each subsequent layer. My advice is to learn as much as you can about the defaults and properties because certain pairing and line properties WILL result in conflicts further restricting your line and causing it to move past layer 7 forcing PNs upon you.
Again a PN means you screwed yourself by not properly opening up your bid by layer 7 and a CN means the company screwed you by assigning a pairing they needed covered and you just happened to be the most JR crewmember it was legal to force the pairing upon.
Trying to get too restrictive for your seniority (weekends off, 22+hr commutable trips, etc.) and not properly opening up your bid by layer 7 is the most common way people screw themselves. The key to PBS is understanding how each parameter works in relation to each other both within a layer and as the system moves through each subsequent layer. My advice is to learn as much as you can about the defaults and properties because certain pairing and line properties WILL result in conflicts further restricting your line and causing it to move past layer 7 forcing PNs upon you.
Again a PN means you screwed yourself by not properly opening up your bid by layer 7 and a CN means the company screwed you by assigning a pairing they needed covered and you just happened to be the most JR crewmember it was legal to force the pairing upon.
Same bid as the past 5 months, every month has come out vastly different.
I don't bid hardly anything restrictive.
1: CDOs; 5h+ cdt/dp
2: locals, 2 days; 5h+ cdt/dp; 12hrs off between pairings
3: 3 days; 5h+ cdt/dp; try to finish at this layer; waive min cdt.; 12hrs off between pairings
4: 4 days; 5h+ cdt/dp; waive min cdt.; 12hrs off between pairings
5: CDOs, locals, 2 days (no restrictions)
6: 3days, 4 days (no restrictions)
7: no restrictions...
Also, by layer 4, 60%, and layer 5, 75% of all trips fit.
I bid 55%, so by no stretch should I have gotten PN trips all over my schedule.
And the PNs happen after the last layer awarded trip, which was a P5, so it had nothing to do with the layer 3 "try to finish"
Since I only bid by trip length and credit, with no other pairing properties selected. (no weekends off, trip mix, commutable blocks, days, nights, etc. None of that AT ALL)
So, I'm awfully curious how I restricted PBS' too much, or how the simple system was just too much for my lack of common sense or brain to handle.
Now tell me Mr. Expert, how I F'd myself.
Considering this is the same bid I've used for months, and can't get a single month to look similar to another. I haven't seen a PN in a year on my schedule. And only one or 2 CNs in the past year. Now the opposite.
I've been bidding with this POS PBS software for 3 years, and only 2x have I gotten such a POS schedule. One month, everyone was getting hosed. This month, as you assert, I screwed myself...
Last edited by Piedmonster; 05-19-2014 at 01:27 PM.
#5099
Yes, please explain how I screwed myself...
Same bid as the past 5 months, every month has come out vastly different.
I don't bid hardly anything restrictive.
1: CDOs; 5h+ cdt/dp
2: locals, 2 days; 5h+ cdt/dp; 12hrs off between pairings
3: 3 days; 5h+ cdt/dp; try to finish at this layer; waive min cdt.; 12hrs off between pairings
4: 4 days; 5h+ cdt/dp; waive min cdt.; 12hrs off between pairings
5: CDOs, locals, 2 days (no restrictions)
6: 3days, 4 days (no restrictions)
7: no restrictions...
Also, by layer 4, 60%, and layer 5, 75% of all trips fit.
I bid 55%, so by no stretch should I have gotten PN trips all over my schedule.
And the PNs happen after the last layer awarded trip, which was a P5, so it had nothing to do with the layer 3 "try to finish"
Since I only bid by trip length and credit, with no other pairing properties selected. (no weekends off, trip mix, commutable blocks, days, nights, etc. None of that AT ALL)
So, I'm awfully curious how I restricted PBS' too much, or how the simple system was just too much for my lack of common sense or brain to handle.
Now tell me Mr. Expert, how I F'd myself.
Considering this is the same bid I've used for months, and can't get a single month to look similar to another. I haven't seen a PN in a year on my schedule. And only one or 2 CNs in the past year. Now the opposite.
I've been bidding with this POS PBS software for 3 years, and only 2x have I gotten such a POS schedule. One month, everyone was getting hosed. This month, as you assert, I screwed myself...
Same bid as the past 5 months, every month has come out vastly different.
I don't bid hardly anything restrictive.
1: CDOs; 5h+ cdt/dp
2: locals, 2 days; 5h+ cdt/dp; 12hrs off between pairings
3: 3 days; 5h+ cdt/dp; try to finish at this layer; waive min cdt.; 12hrs off between pairings
4: 4 days; 5h+ cdt/dp; waive min cdt.; 12hrs off between pairings
5: CDOs, locals, 2 days (no restrictions)
6: 3days, 4 days (no restrictions)
7: no restrictions...
Also, by layer 4, 60%, and layer 5, 75% of all trips fit.
I bid 55%, so by no stretch should I have gotten PN trips all over my schedule.
And the PNs happen after the last layer awarded trip, which was a P5, so it had nothing to do with the layer 3 "try to finish"
Since I only bid by trip length and credit, with no other pairing properties selected. (no weekends off, trip mix, commutable blocks, days, nights, etc. None of that AT ALL)
So, I'm awfully curious how I restricted PBS' too much, or how the simple system was just too much for my lack of common sense or brain to handle.
Now tell me Mr. Expert, how I F'd myself.
Considering this is the same bid I've used for months, and can't get a single month to look similar to another. I haven't seen a PN in a year on my schedule. And only one or 2 CNs in the past year. Now the opposite.
I've been bidding with this POS PBS software for 3 years, and only 2x have I gotten such a POS schedule. One month, everyone was getting hosed. This month, as you assert, I screwed myself...
#5100
Yes, please explain how I screwed myself...
Same bid as the past 5 months, every month has come out vastly different.
I don't bid hardly anything restrictive.
1: CDOs; 5h+ cdt/dp
2: locals, 2 days; 5h+ cdt/dp; 12hrs off between pairings
3: 3 days; 5h+ cdt/dp; try to finish at this layer; waive min cdt.; 12hrs off between pairings
4: 4 days; 5h+ cdt/dp; waive min cdt.; 12hrs off between pairings
5: CDOs, locals, 2 days (no restrictions)
6: 3days, 4 days (no restrictions)
7: no restrictions...
also, by layer 5 I had 75% of all trips fit. By layer 4, 60%.
I bid 55%, so by no stretch should I have gotten PN trips all over my schedule.
Especially since I only bid by trip length and credit, with no other pairing properties selected.
I'm awfully curious how I restricted PBS' too much, or how the simple system was too much for my lack of common sense or brain.
That's it. Now tell me Mr. Expert, how I F'd myself. Considering this is the same bid I've used for months, and can't get a single month to look similar to another. I haven't seen a PN in a year on my schedule. And only one or 2 CNs in the past year. Now the opposite.
I've been bidding with this POS PBS software for 3 years, and only 2x have I gotten such a POS schedule. One month, everyone was getting hosed.
This month, as you assert, I screwed myself...
Same bid as the past 5 months, every month has come out vastly different.
I don't bid hardly anything restrictive.
1: CDOs; 5h+ cdt/dp
2: locals, 2 days; 5h+ cdt/dp; 12hrs off between pairings
3: 3 days; 5h+ cdt/dp; try to finish at this layer; waive min cdt.; 12hrs off between pairings
4: 4 days; 5h+ cdt/dp; waive min cdt.; 12hrs off between pairings
5: CDOs, locals, 2 days (no restrictions)
6: 3days, 4 days (no restrictions)
7: no restrictions...
also, by layer 5 I had 75% of all trips fit. By layer 4, 60%.
I bid 55%, so by no stretch should I have gotten PN trips all over my schedule.
Especially since I only bid by trip length and credit, with no other pairing properties selected.
I'm awfully curious how I restricted PBS' too much, or how the simple system was too much for my lack of common sense or brain.
That's it. Now tell me Mr. Expert, how I F'd myself. Considering this is the same bid I've used for months, and can't get a single month to look similar to another. I haven't seen a PN in a year on my schedule. And only one or 2 CNs in the past year. Now the opposite.
I've been bidding with this POS PBS software for 3 years, and only 2x have I gotten such a POS schedule. One month, everyone was getting hosed.
This month, as you assert, I screwed myself...
There is a possibility PBS made an error on a more senior pilots award creating an error in the pairings available to you in your pairing pool but you should still have been able to complete your solution without any PNs. Again, PNs mean you made the error. Without reading your “reason report” I’m thinking what happened is PBS could not create a solution with the pairing pool available to you by layer 3. You bid "try to finish by the layer" but only in layer 3, since your line wasn’t full of P/L1-3s it means it could not create a solution from the pairings that were available to you in those layers. So the computer retained what it awarded you in layers 1-3 but those pairings restricted PBS in later layers from creating a solution with what remained. In order words, for June, you were unable to hold a line full of what you're bidding for in layers 1-3 and those pairings conflicted with what you could hold in the following layers. In order to relax this restriction you need to bid “try to finish by this layer” in other layers as well as adjust your approach a bit.
If I could see your complete award with the reason report I could paint a clear picture but I’m certain this is what happened. You were somewhat stabbing at a line without understanding how the layers work together as they moved from start to completion of a solution.
Last edited by MatchPoint; 05-19-2014 at 02:05 PM.
Thread
Thread Starter
Forum
Replies
Last Post