3.14.20 – PBS: Generic vs. Specific Bidding

Saturday, March 14, 2020

PBS: Generic vs. Specific Bidding

We frequently receive the question on whether to combine specific and generic properties in the same layer or not. As a general rule, it is not advisable to combine bidding specific pairings with generic properties in the same layer, but there are circumstances when it can be used.

The important thing to remember is that when PBS processes your bid it will view all pairings within a single layer as equal.

By adding specific sequences and generic properties for PBS to consider pairings in the same layer, you are telling PBS I am equally ok with any of these trips. Below you will find some examples of bidding these selections and we hope it will help clarify how PBS is viewing your selection during the award process.

As a good rule, if you have questions about what pairings are in your pairing pool, always check your layer tab and the “View Pairing Set”. This will show you all the pairings in your pairing pool by layer. If this does not reflect your bidding strategy, then you can remove individual pairings or adjust your properties accordingly.

Let’s first look at generic bidding. As you know, electing preferences under pairing type are considered generic. Combining different generic properties can narrow the pairings pulled into your pairing pool.

For example:
Bidding IPD in a layer will pull in all trips that are considered IPD – originating all days

Bidding IPD in conjunction with a layover would pull in only IPD trips laying over in that city into your pairing pool– originating all days.

Bidding IPD in conjunction with multiple layovers selected would pull in all IPD trips with layovers in the selected city into your pairing pool– originating all days.


As a reminder, bidding days off will remove any pairings that touch those days off, thereby reducing the number of pairings in your pairing pool.

Let’s take a look at what happens when specific sequences are bid.

For example:
Bidding 3 specific trips in a layer would pull in those three trips and your pairing pool would contain only those three trips (times however many positions are bid) in this example 12 pairings are in layer 1 (3 trips x 4 Positions).

Now let’s add a generic property.

Bidding IPD would also pull in all trips that are considered IPD (times the number of positions) – now the pairing pool changed to 1023.

If the flight attendant only wanted those 3 specific trips to be considered, the addition of the IPD property negated that desire.

A common generic property used is Aircraft type.  By selecting a preference for an aircraft all sequences that contain a working leg on the selected aircraft would be added to the pool and could exponentially increase the pairing pool!

 

Combining Generic & Specific Scenario


There is a scenario where generic and specific selections can be combined.

For example:
Bidding IPD with a layover – let’s say CDG – all trips to CDG would be pulled into the pairing pool – this is the main desire of the flight attendant.

But there are some LHR trips that the flight attendant would also like to consider, just not all of them.  The flight attendant could bid specific pairings and those would be added to the pairing pool of CDG layovers. PBS would now look at the pool of CDG trips with a few selected LHR trips as all being equal within the same layer.

In Unity,

APFA JSIC
pbs@apfa.org

Alin Boswell
Julie Hedrick
Linda Haertling

1004 West Euless Boulevard
Euless, Texas 76040

Phone: (817) 540-0108
Fax: (817) 540-2077

 

Headquarters
M-F: 9:00AM - 5:00PM (CST)

APFA Phone Reps
M-F: 7:00AM - 7:00PM (CST)

After-Hours Live Chat
M-F: 3:00PM - 11:00 PM (CST)
Sat-Sun: 9:00AM - 5:00PM (CST)

APFA Events

SBA Town Hall

November 17 @ 1:00 pm - 2:00 pm