How Do I – Scheduling AOC PBS On Line Instructions
Crewmember Guide to (AOS) PBS
Table of Contents
Preferential Bidding Preferential Bidding Product Overview Bidding Overview Benefits
Comparison to Traditional Bid Lines System Functions and Descriptions Main
Online Docs View Seniority List Preassigned
User Property: Individual crewmember’s flown block from previous bid month Of Days
Pairings Pairing Properties Line Properties Pre-Built
Reserve Of Days Bid Prioritize Layers View Pairing Set Print Bids Standing Bids View Prev Bids Line Award
Listing of al Preferences General Concepts and Logic
System logic with multiple preferences on the same Layer Optimization Process
Good Bids and Bad Bids.
Bidding Conflicts – System Response Pairing Pool Discussion
Bidding Cases and Bidding Scenarios
Preferential Bidding is a bidding system that allows crewmembers to “build their own lines”. Crewmembers can express a preference for of days, specific pairings, general pairing properties, line characteristics, reserve of – days and pre-built CDO lines. The system uses each crewmember’s requests and their pre-assignments (vacation, training, medical, military leave and carry in pairings, etc.) plus their seniority to build their lines. In PBS crewmembers can construct their work schedules around their personal lives, provided that the pairings are available and their seniority.
The Preferential Bidding System “PBS” is designed using unique global optimization techniques to honor seniority while maximizing crewmember satisfaction. The system produces lines of work that are legal (FAR’s and contractual requirements) and within the minimum – maximum line values. Crew member preferences can, if they so desire, determine of days, pairing purity, turn lines, layover cities, and so on.
Crewmembers bid from a web based system that is easy to use. The PBS web site is located by logging onto the Compass Corporate site, then into Crew Member information and then by selecting the PBS option. The first page displays basic information about the crewmember (base, seniority and qualifications), bidding times and total number of line holders. On the left hand side of the page is a list of hyperlinks (see System Functions and Description for al links) (note: a hyperlink is a link to move to another page, one click on the link and the system will move to the desired function), which the crewmember clicks on to move to each function.
For example, when you click on Off Days, the system shows a calendar for the bid period. The calendar displays al pre-assigned activities. By clicking on specific dates, the crewmembers can bid specific of days. By clicking on the Pairings hyperlink, the crewmembers can bid specific pairings. General bids are made by clicking on the Pairing Properties and Line Properties hyperlinks.
Al inputs (bids, pre-assignments, carry-ins and the current month pairings) are collected in a database and then passed to the PBS optimizer to run. The awarded lines of work are generated and then passed back to the database. The lines of work are then loaded to CrewTrac and posted to the web site for crew review.
When the awarded lines are loaded to the web site the crewmembers will see an easy to read line format. The line award is in a calendar format and the pairings in their line are displayed just below the line, al on one screen. By clicking on the Show/Hide Your Bids link at the top of the page, crewmembers to quickly compare their awarded line to their bids.
PBS bidding logic requires crewmembers to enter their preferences into the system. By clicking on the Prioritize Layers hyperlink, a crewmember can then express which of these preferences are his/her 1st choice, 2nd choice, 3rd …etc., by either checking or un-checking the specific preference in an easy to use table. These checked “choices” present layers of preferences. The system will build lines based on the preferences checked in the layers.
The system uses layer one first (preferences with the highest priority) when constructing lines. If the system can build a legal line with layer one preferences, it will. If not, the system will retain the pairings that were granted and move on to the second layer. The system will search for the pairings that fit the checked preferences in the priority 2 layer and assign those pairings to the line. The system will continue to consider additional layers until a legal line is produced.
The system moves from layer 1 to layer 2 to layer 3 and so on … when one of the following situations has happened:
Senior crew members have taken your desired pairings, or You have asked for pairings that are not in the pairing pool, or Your bids conflict with pre-assigned activities, or
Your bids cannot meet the target line value, or
Your preferred of days cannot not be granted because of required coverage.
If the system has processed al layers and the line is still not complete, then the system will assign additional pairings to the line in order to bring it up to a legal value.
The greatest benefit to crewmembers is that they can tailor their work schedules to their personal needs. Additionally:
PBS will reduce the conflict caused by integration.
In traditional bid lines there may be no line you want, an example was the number one pilot who wanted weekends of and Thanksgiving Of , but the hard line did not exist. A line like that would be easy to build in PBS.
Flying a line with a mix of pairings. Some people tell us that they don’t like to land in the same airport all month.
Bidding specific days off. You need the third Thursday of because your significant other tells you so.
Other benefits are from the technology: ease of use and speed of bidding, ability to bid from anywhere in the world that has web access, plus the ability to submit standing bids.
Comparison to Traditional Bid Lines
PBS offers flexibility that the crewmembers never had with traditional bid lines. In PBS crewmembers can mix the types of flying to suit their individual desires; turns with two and three day trips, or things that are different like stand-ups with four day trips, things that would never be done in bid lines. Special of days or large blocks of off days would be constructed in your line when you want them. The key is individual schedules: avoid that particular city, layover in this city or fly a particular pairing. PBS tailors crew’s schedules for individual crewmembers, their seniority and the parings available in their bid package.
System Functions and Descriptions
Note that “Main” is highlighted in yellow (indicating where you are) in the left hand list of hyperlinks (functions). At this stage you can click on any of the links to go directly to that function.
The main page displays the following information: Crew Member’s Name
Crew Member’s Employee ID
Last login date and time, this login date and time Base
Seniority in the Company Seniority in the Bid Package
(The absolute seniority out of all active bidders and its relative seniority percentage) Crew Qualifications (positions)
Attribute Other Info
Current Bid Package Information:
Name of the specific bid package Description of the bidders Package Bidding times
Total number of line holders.
The Message Board is a place where the PBS Administrator/Crew Planner post messages for a specific Bid Package. It provides a way so that the Administrator can broadcast information. For each bid month, each Bid Package may have its own message, or the same as the other bases, or no message.
Clicking on the Online Docs link takes the user to the online Crew Member Guide to PBS. This guide describes all of the preferences and provides bidding suggestions as well as an overview of PBS. Close this page to return to the “Main” page.
View Seniority List
Clicking on the View Sen List link you will see all the bidders in your base/category. The page displays employee number, name, seniority and seniority in Bid Package. If a line is shaded and there is an NA in the last column, then that crewmember is “not available”.
Clicking on the Preassigned link displays al pre-assignments on a calendar and at the bottom of the page shows the total credit and block of the pre-assignments. This includes carry-ins, vacation, training, military leave, company business, etc. Place the cursor over a pre-assignment and a window shows the dates, credit and block of that pre-assignment.
By double clicking on the pre-assignment, the system displays a pop-up window, which shows pairing ID number, start date, end date, credit, block, and pay, and report and release times. There are also two buttons; “Delete Bid” and “Back”. By clicking the “Back “ button, you return to the calendar. It is strongly recommended to check your pre-assigned activities every month, to ensure that the information is valid. Incorrect information of a pre-assignment may negatively impact the line award.
User Property: Individual crewmember’s flown block from previous bid month
When a bid month covers more than one calendar month (using February as an example: 20080130- 20080301), or less than a calendar month (March: e.g. 20080302-20080331), the system needs to subtract the flown block time value awarded in the prior bid month from its associated calendar month, and figure out what the remaining available block time for the current bid month would be.
There are three cases as a result of bid months that do not match with the full calendar months: They are February, March and September.
- February bid month is from 31st to March 1st and January bid month is between Jan. 1st to Jan. 30th. When awarding a line to a crewmember for his/her February bid month, the available block time for Jan. 31st depends on the total block time awarded in the January bid month. Hence,
The available block time for Jan. 31st = Maximum allowed block time for January calendar month – Total block time awarded to January bid month.
- March bid month is from March 2nd to March 31st and the February bid month is from 31st to March 1st.
The available block time for March bid month = Maximum allowed block time for March calendar month – Total block time awarded to March 1st.
- September bid month is from August 31st to September
Approaching the end of the year, the total block time flown in the year may limit crewmembers’ available block time for November and December.
By clicking on the Off Days link, the system displays a calendar of the bid month. The calendar extends 6 days back into the previous month and 6 days into the next month so that you can see the scheduled activities that do not occur in the current bid month. These scheduled activities may impact the way you bid and/or your legalities. This calendar is for bidding the days of you want. You can do this by clicking on the individual day, or by clicking on a day-of-week at the top of the calendar if you want al of those days of (for example al Saturdays).
When you first open the Of -Days screen, the calendar will show your pre-assignments and directly below the calendar is a heading “Additional General Bids”. This is where all of your already made General Bids will be listed.
Note: Clicking Saturday and/or Sunday at the top of the calendar week, requests the system to award you ALL Saturdays and/or Sundays off. It is an al or nothing bid. By clicking INDIVIDUAL Saturdays and/or Sundays off , the system will attempt to reward you any, and as many requested of – days it can. This is true for any days of the week requested off.
The letters “OFF none” (clicked on a single day before prioritizing this off-day bid), “OFF1” (single day of at layer 1 after prioritizing this off -day bid) or “OFFW1” (al day-of-week of at layer 1 after prioritizing this of -day bid) will show on the day or series of days of that you selected. To undo a requested of day, you may click on the day-of letters (“OFF1”). Click on delete bid, and that specific bid will be deleted; this window also provides the bidder the ability to set layers for this specific of day and to save those layers.
The ‘Clear All Off Days’ button on the bottom left portion of the screen gives you the ability to clear al of the selected Of Days in one step.
The ‘View Layer’ drop down box gives you the ability to view the requested days of by Layer. There is more on the Layer concept in the Prioritize Layers section of this document.
When the cursor is placed over a date (the actual number) it will change from an arrow to a hand and the date will be highlighted in yellow, this indicates the date is active to bid. You can bid of -days 4 days into the following month, (thus the Arrow to Hand activation). This is to avoid carry-out pairings operating on your selected off -days in the month. Note: You must bid these same desired of -days in the following bid month, if you so desire.
Strategy: The bidding strategy for days off is almost always based on a combination of your seniority and your objectives. One should request al the days of that you would like to have. Then, in the Prioritize Layers section, you can tell the system which are most important to you by making all of your of day choices a Layer One selection.
- The system recognizes the day-of bids that are prioritized in different layers and awards of days by the available of days (according to the of -day bids) in each Therefore, the off -day bids in the first layer are the most wanted of days, and the off -day bids in the second layer are second to the most, and so on.
- When pairing on-date bids co-exist but conflict with the of -day bids, the pairing-on date bids trump the of -day However, the off -day bids in each layer are still recognized by the system and set the importance for them by layer.
- Al non-pairing on-date bids co-existing with off -day bids in the same layer would be restricted by the of -day bids, e., pairings that conflict with the off -day bids in that layer are excluded from this pairing pool.
- The system awards your of days by considering your of -day bids from Layer One to the last
Note: By clicking on Saturday Of you tell the system that you want al Saturdays off . If the system cannot satisfy your request, it will try your next layer, and then the next. Assuming that you have clicked Saturdays of in all layers, the system will finally have to fill if your line is still incomplete. At that point your Saturday bid is no longer considered.
If you want the maximum weekend days of that are available at your seniority and you do not care which ones they are then bid “Max Weekend Days Off”, as described in Line Properties.
To review and/or select specific pairings, click on the Pairings link on the left side menu. The system shows multiple displays on the right side screen:
- A calendar on the top portion of the screen;
- A pairing search engine (a table in the middle of the screen for entering search criteria);
- Search results (Pairings), which will appear after you have clicked “search” at the bottom of the
The calendar displays the off days and pre-assignments (inherited from previous steps) as well as the specific pairings that are bid (dated pairings appear in the calendar and non-dated pairings appear below the calendar). Note: Bids for pairing properties and line properties do not appear below the pairing calendar.
There is also a “View Layer” function for reviewing specific pairing bids by layer after using the Prioritize Layers function. At the bottom of the calendar there are two buttons, “Clear Al Specific Pairing ID Bids” and “Clear Search Criteria”. Click on “Clear Al Specific Pairing ID Bids” to remove al specific pairing bids. Likewise, by clicking on “Clear Search Criteria” all of the entered search criteria will be removed.
The pairing search engine is a tool for finding pairings. This search engine allows you to define specific search criteria, search al the pairings in your bid package (base, city, report/release time, etc.), and then display them. Notice that after entering your criteria there is a button on the bottom of the table labeled, “Search”. Click “Search”, if no pairings are found a “No Pairings” message shows in the lower left of the screen, otherwise the defined pairings are displayed below the table. On top of the result, it shows how many pairings were found and how often they operate.
The search results display the located pairings in the print format, which includes; flight number, departure – arrival cities and times, etc. Also, included is a calendar showing the days that pairing operates. On the left side of the pairing display is a window, labeled “on date” and in the window is “Bid Pair ID” with dates below (in year, month, day format). To bid a specific pairing, click on the date desired and then click on “choose” (the pairing ID is just below choose) above the window. You will see that the selected pairing is displayed on the desired day on the calendar.
The following criteria can be used to search the pairings that are in your bid package:
Match pairing ID as – By entering a complete pairing ID (for example, M7115), the search function will display that pairing on the bottom of the screen.
Match starting day as – By clicking on a calendar day (a specific date) in the calendar icon on the right, the system will display that date in the input box and display al pairings that start on that date. By clicking on the day of week in the main calendar, the system will display the day of week in the input box (i.e., Mon, Tue, Wed … Sun) and al the pairings that start on that weekday.
Or you may enter the date (following YYYYMMDD format) in the input field or enter Mon, Tue, Wed, Thu, Fri, Sat, or Sun and click search. The search displays al the pairings that start on that date or weekday consistent with your other criteria.
If you want to bid one of the pairings that starts on a specific date, click on the date in the window on the left hand side and click choose. That pairing ID will appear on the calendar on the date selected. If you want to bid one of the pairings that operates on the weekday selected, click on Bid Mon (assuming Monday was selected) in the left hand side window and then click choose. In the area under the calendar, “Pairing ID on weekday (layer1, pair id: actual pairing id number, Mon)” will be displayed. Click on the hyperlink Prioritize Layers and you will note that the pairing on date and pairing on weekday are listed under the pairings section followed by the specific pairing ID number and date or weekday. Also, one pairing is counted on the chart when pairing on date is bid and (in our case we bid a pairing that operated on four Mondays) four pairings are counted from the bid pairing on weekday.
The following three criteria work together to locate pairings that meet the combined requirements of layover city, date and length of layover. Enter your desired combinations and click search. The system will locate the pairings that meet your criteria. If you want to fly any of these pairings you must bid them specifically (bid each pairing ID on the desired day).
Match layover city at – The drop down list shows al the layover cities in the current month pairing set. Click on a city code and click search and the system will locate al the pairings with at least one layover in that city. In addition, you may enter and select a specific layover date and/or enter and select the minimum layover time. The search and make bids work with “Match layover city at” when it is used individual y and when it is used with ‘on day’.
- On day – If used individual y, the system will search for those pairings that have a layover that starts on the date You may specify the date using the calendar or enter YYYYMMDD format.
- With layover time at least – You can specify minimum layover time using a drop down As noted above, this criterion was designed to work with layover city on day. If you use this criterion alone to do a search the system will find pairings that have one or more layovers that meet your setting. Note: not all layovers are required to meet the criterion.
Pairing length (days) from – Pairing trip length is in duty days. You may specify one day trips, also known as turns, (for example, from ‘1’ to ‘1’) or 2 day trips (from ‘2’ to ‘2’), or 3 day trips (from ‘3’ to’3’) or 4 day trips (from ‘4’ to ‘4’), you may also specify two and three day trips (from ‘2’ to ‘3’) or al trips (from “1’ to “4’). The trip lengths displayed are the actual lengths found in the particular bid package. If there are only two and four day trips in the bid then only 2 and 4 would be displayed. If you only enter a lower value the search will assume the maximum length for the upper value, likewise if you only enter an upper length value the search will assume a minimum value for the lower. Note: Duty Day – This definition of day extends between 00:01 to 24:00.
Report between – This choice allows you to specify the reporting time of the selected trips. Select the time window (I want to report between Time A and Time B) from the drop down list of actual report times. When bidding, it is recommended to start Layer 1 with a narrower report-between window and expand the window in subsequent Layers. Be sure to check and see if there are pairings that match your report-between interval request.
Release between – This choice allows you to specify the release time of the selected trips. The time windows work the same as report between. Also, check this request to be sure that pairings exist.
Average credit per duty period – The drop down windows provide actual values for average credit per duty period. By selecting values “from” “to” the system will search for all pairings whose average credit meets your specified range. You need to enter both “from” and “to” values in order for the search to work. Average credit per duty period is calculated by taking the credit value of the pairing and dividing by the number of duty periods.
Min connection (Turn) – This choice allows you to search for pairings that have a minimum connection time of the specified value or greater. Using the drop down window specify your desired connection (Turn) time, the search will find pairings that have connection (Turn) times that are al equal to or greater than the value you selected.
Max connection (Turn) – This choice allows you to search for pairings that have a maximum connection time of the specified value or less. Using the drop down window specify your desired connection (Turn) time, the search will find pairings which have connection (Turn) times that are al equal to or less than the value you selected.
Min layover – This choice allows you to search for pairings that have a minimum layover time. Using the drop down window specify your desired layover time, the search will find pairings that have layover times that are al equal to or greater than the value you selected.
Max layover – This choice allows you to search for pairings that have a maximum layover time. Using the drop down window specify your desired layover time, the search will find pairings which have layover times that are al equal to or less than the value you selected.
Max landings per duty period – This preference allows you to search for pairings that have the specified number of landing per duty period or less. Al duty periods within the pairing will meet this criterion. The drop down window shows the actual number of landings in the current month’s pairings.
Max TAFB- credit ratio – This choice allows you to search for pairings that have a TAFB credit ratio equal to or less than the specified value. TAFB credit ratio is the ‘time away from base’ divided by the ‘credit hours’ of a pairing. Stronger turn trips that have a TAFB value of 12:00 and credit value of 6:00 have a TABF credit ratio of 2. A four-day pairing that has a TAFB value of 70:00 and credit value of 20:00 has a TAFB credit ratio of 3.5.The lower the ratio the more credit for less time away from base. The drop down window shows the actual TAFB – Credit ratios for the current month’s pairings.
Pairing type – If you click on the blank above the choices the system will search al pairings. Currently, one can only bid for regular pairings. Although the “Continuous Duty Only” (CDO) is shown on the list as the second open, crewmembers must access the Pre-Built link in order to bid for pre-built CDO lines.
Please note that when you search for CDO trips, the system displays all CDO trips for your reference only, and is not for bidding.
After the search criteria have been entered, click on the “Search” button to start searching. The search result is displayed on the bottom portion of the screen. If the system cannot find any pairings that match your criteria, it will show “no pairings found” on the bottom left corner of the inquiry table.
Search Result: The pairings that were found are displayed on the bottom portion of the screen.
You may decide to select (bid) some of the specific pairings shown. Click on the preferred pairing’s date you want to bid in the left side list under ‘on date’. Then click on choose above the window. The pairing number is just below choose. The selected pairing will show up on the calendar on the specified date.
To select multiple pairings, depress the ‘shift’ key and click on the dates desired, then click choose, the pairing will be displayed on the calendar on the dates selected. Use the shift key when you want pairings that are in a row, like five turns in a row. Use the ‘control’ key if you want to select multiple occurrences, like every Monday. Again, click.
To bid a specific pairing ID (one pairing on al days it operates), first search for the pairings of interest,
then click “Bid pair ID” in the window on the left and then click choose. The system will display your pairing ID bids below the calendar and place it in prioritize layers.
Note: When using the search engine, if you select turns and either a layover city or any layover time it will show no pairings found. If you select turns and two day trips with layover criteria only two day trips will be displayed.
Specific pairings bid on specific dates survive al conflicts except pre-assignments. When you bid a pairing on a date it will overrule an off day bid on the same date; it will survive a conflict with a report between bid that is more constraining, a conflicting pairing length bid, etc. all. When specific pairing ID’s are bid without dates, they will survive al conflicts except of days and pre-assignments.
When specific pairings are bid along with general preferences (any turns or any 2-day trip) on the same layer, they are seen by the system as of equal importance. For example, if such a bid were made on layer 1, then al bids would be classed as P1’s and the line might contain any combination of the specific pairings, turns and two-day trips. We suggest that if you really want the specific pairings only, then bid them on layer 1 and bid the more general bids on layer 2 and so on.
When bidding pairing ID’s on a date and pairing ID’s and pairing length of 1 on the same layer, they will all be included into the pairing pool and marked as P1’s. In this case you could also condition the pairing lengths with report time, layovers, etc. If one were to bid pairing ID’s on a date and then only bid conditioning preferences such as report time or layover, then the pairings that satisfy those conditioning preferences plus the pairings on date will be included in the pairing pool.
When you click on the Pairing Properties link on the left side menu, the system displays:
- A calendar displaying pre-assignments and al the previously selected of -days date specific properties and date specific pairings,
- Immediately below the calendar is a title ”Additional General Bids” where al general bids will be listed,
- And below is a list of preferences to bid for pairing
Once again, above the calendar is a “View Layer” button and additional y a “Clear Al Checkmarks” button. The “Clear Al Checkmarks” button provides the bidder an easy method to remove the checkmarks from the entire calendar. The checkmarks allow the bidder to bid selected pairing properties (pairing length, report time, release time and layover city) on specific days.
Just below the calendar is a line saying “Additional General Bids”. Each time you bid a pairing property preference it will be listed here. The chosen General Bid will be followed by a message, “Layer None”. This is to inform the bidder that although they have chosen Pairings, Pairing Properties or Line Properties, no Layer has been selected. When one of these choices has been selected by checking a Layer, that Layer number, (e.g. Layer 1,3,5), alerts the bidder what Layer that preference has been selected in. Uncheck the preference in Layer 1 and 5, the message would read Layer 3.
For each of the preferred pairing properties, first click on the bidding button next to the preference, then you may click on a Bid button to save the bid or Clear Bid button to delete al related Bids.
Note: Bidding Pairings and Pairing Properties tell the system which pairings to use to build your line. When your bids go from specific to more general there will be more pairings on each successive layer for the system to choose from.
Listed below are all the Pairing Properties that you can bid as preferences. Notice that the search criteria in the Pairing section are in fact pairing property preferences.
For each of the pairing properties, you may click on a Bid button to save it or Clear Bid button to delete al related Bids.
Minimum Average Credit per duty period. When you click on this preference, the system will show a field that allows you to select pairings of a specified average credit per duty period. The values are preset from 3:45 to 7:30 in 00:15 increments.
Pairing Length. This preference allows you to specify the length of pairings in duty days you want to fly. When this preference is clicked, a drop down window appears, click on the 1, 2, 3, 4, or 5 to determine desired trip length. You may specify one-day or turn trips, also known as a turn, or 2-day trips or a 3-day trips or 4-day trips. If you want to bid 2 and 3-day trips, bid twice, first the 2’s and then the 3’s. Any trip that releases after midnight would be counted as an additional day.
Pairing Length on Date. When this preference is clicked, a drop down window appears, click on the 1, 2, 3, 4, or 5 to determine desired trip length. Then click on the small box in the calendar for the dates you want these trips, and then click “Bid on Checked Dates”. Note that the preferred pairing lengths appear on the selected dates in the calendar.
Deadhead Preference. This preference instructs the system that you want to either prefer or avoid deadheads. The default is no preference.
Report Between. This preference allows you to specify the reporting time of your trips. Select the time window (I want to report between Time A and Time B) from the drop down lists of hours and minutes. When bidding, it is recommended to start Layer 1 with a narrow Report time window and expand the window in subsequent Layers.
Report Between On Date. Similar to the Pairing Length on Date preference, you check the dates you want to report according to the report time window specified. Check your desired date, enter your desired times and then click on “Bid On Checked Dates”.
Release Between. This Preference allows you to specify the desirable release time window. Use the same way as Report.
Release Between On Date. Similar to the Report between on Date Preference, you can check the dates you want to release according to the release time window specified.
Layover at City. This preference allows the crewmember to Bid for or Avoid pairings that have a layover in a specific city. The cities are in a drop down window. Note that the pairing satisfies this preference if it lays over once in the requested city. Actual cities are shown in the drop down window based on the current month’s pairings.
Layover at City on Date. This preference allows you to request pairings that contain layovers in a specific city on a specific date. Check the calendar as with other dated preferences. The calendar is marked with “LAY city-code” on the dates checked. Actual cities are displayed.
Min Connection (Turn) Time Preference. This preference allows you to request pairings that have connection times no less than the time specified. Use the drop down window to bid hours and minutes.
Max Connection (Turn) Time Preference. This preference allows you to request pairings that have connection (sit) times no greater than the time specified. Use the drop down window to bid hours and minutes.
Min Layover Time Preference. This preference allows you to request layovers equal to or greater than the layover time specified. Use the drop down window to bid hours and minutes.
Max Layover Time Preference. This preference allows you to request layovers equal to or less than the layover time specified. Use the drop down window to bid hours and minutes.
Max Landings Per Duty Period. This preference allows you to request a specified number of landings or less within each duty period. Click on the drop up window and select the desired number of landings and click bid.
Landing At City Preference. This preference lets crewmembers specify a city where he/she prefers or intends to avoid any landings at that city. Enter the city code in the window and click “Bid Prefer” or “Bid Avoid”. Use the city codes that are displayed in the pairing print under the pairing search. Remember, this preference will include al pairings into your pool that do not land at the specified city unless you have also provided other constraints on the specific layer. It is possible that a crewmember may enter an incorrect city code to the input field. To prevent further problems caused by the incorrect city code to his/her line award, the system blocks this incorrect bid from being applied to the current bids.
The system validates all values that are entered by crewmembers, not the ones that could be chosen from dropdown lists, to ensure that al values are meaningful. An incorrect value in a bid causes the system to post an error message in red color to warn the crewmember that a specific bid has incorrect information. If the crewmember would like to keep this bid, he/she should go back and correct the value he/she had entered. Otherwise, the system would just ignore the incorrect bid.
When you click on the Line Properties link you will see the calendar with all inherited requested days off , any specific pairings that you requested, any date specific Pairing Properties you may have requested, and your pre-assignments.
The above preferences selected from Pairings and Pairing Properties choose the pairings to be used when the system builds your line. The Line Properties either constrain the line or determine if the line is feasible.
Each preference has a bidding button. These bidding preferences allow you to specify your desired line characteristics.
Listed below are the Line Property Preferences:
Min. Number of Days Off. This preference states that you want a minimum number of days of in the bid month. This constraint tells the system that if it cannot build a legal line at the existing layer with the bid number of days of or more, then move to the next layer and try again. Click on the preference and enter a number (between 11 and 20) in the window and click bid. To waive the minimum off days for the month, one must enter a number that is less than the contractual minimum off days. For instance, entering ‘10’ or ‘9’ as the minimum of days and bid for it, the crewmember has elected to waive the minimum 11 days of and the system may award this line with less than 11 days of .
Target Line Credit Range. This preference states that you want a desired range of values for your line. The number entered should be a whole number. For example: Enter 90 95, not 90:00 to 95:00. Enter your desired lower value and higher value, and then click “Bid”. Note: this preference sets the line feasibility, if the system cannot satisfy this feasibility requirement, it moves to the next layer.
More on “Target Line Credit Range”
The graphs below illustrate how PBS handles “Target Line Credit Range” bids that are out of range for a regular E75 crewmember (where the actual line credit range is between 75:00 and 100:00):
Established credit value: 75:00 to 95:00 hours
(1) Bidder 1 bids all layers 70:00 to 80:00 hours
PBS Solves at (L1,L2, …LN) 75:00 to 80:00 hour range used
Established credit value: 75:00 to 95:00 hours
(2) Bidder 2 bids al layers 80:00 to 110:00 PBS
Solves at (L1,L2, …LN) 80:00 to 95:00 hour range used
Established credit value: 75:00 to 95:00 hours
(3) Bidder 3 bids all layers 100:00 to 120:00
PBS Solves at (LN) 75:00 to 95:00 hour range used
In the first two examples above (Bidders1 & 2) the system will use the one legal line value and set the other to either the line minimum or line maximum. The system will solve at the layer that can be satisfied by the pairings that have been bid. Hence the award could be al P1’s and solve in layer 1 or layer 2, and so on.
In example 3, the system will solve in layer LN because the system cannot satisfy the bid, it will use the pairings that were bid in each layer when it solves in LN. Hence the award could have al P1’s or a combination of P1’s & P2’s or P1’s & P2’s & P3’s, etc. … depending on the bid and seniority.
Additionally, there are two kinds of credit range boundaries set in the system:
Regular line holders – When a crewmember bids a credit range exceeding the system default range, the bid exceeding the boundary (either lower bound or upper bound) will be reset according to the system default to either the minimum or maximum.
Part Timers for flight attendants – The mechanism is the same as the regular line holders. The system will always build a line within the range that has been bid, the only exception that may occur if it is impossible to build the line to the requested range and then a line could be lower.
Min Off Days Between Work Blocks. This preference sets the minimum number of days of between work blocks. The default is “two days” of . Click on the preference, click on the drop down list, click on the desired number (1 to 9) and click bid.
A work block can be a single pairing or pairings that work back to back. But once an of day takes place, a work block is ended.
Note that this preference is a line constraint that instructs the system to only use two days of by default. You may bid one-day of in any layer and the subsequent layers will be set as one-day of. You need to bid three or more days of on the first layer if you want your line to be built with more of days between work blocks.
Also, if you want to fly a high value line, you will need to bid “1”. When using this preference, bid the more constraining bid in layer 1 and again relax in subsequent layers. For example, bid “Min Of Days between Work Blocks” 3 on layer 1 and then 2 on layer 2, and then maybe 1 on layer 4. If one were to bid layer 1 as 1 of and layer 2 as 2 of ; the system honors the line legalities of the first layer. So in this case at layer one a partial line is built and there is a single day of between work blocks, the system in layer two will hold the P1 pairings and as a result ignore “Min Of Days between Work Blocks” of two in layer two.
Note: Trip Mix in a Work Block and Commutable Work Block are special case preferences. In these two cases:
· Work Block has a special definition. Work Block must be two pairings back to back (no days off in between) and their sum must be four days or more. These work blocks will be preceded by and followed by off days.
- Trip Mix in a Work Block will be counted in the matched pairing For example, when 3×1 is bid all one day trips and all three day trips are included in the count displayed in the chart. Commutable Work Block bids will show all pairings in the matched pairing chart.
Trip Mix In A Work Block. This preference allows you to create work blocks that contain trips of the specified lengths. The system will use the trip lengths only in the order that you specified in the selection box. Click on the preference and select your trip mix in the drop down window and click bid. There is a limit of two choices per layer.
Commutable Work Block. This preference allows you to request that your work block begins after a specified time and ends prior to a specified time. Click on the preference and select hours and minutes for report and hours and minutes for release, then click bid. Commutability is possible only when there are pairings that can be back-to-backed as commutable work blocks. Note: There is a limit of one choice per layer.
Do not bid pairing length or pairing ID on date on the same layer with trip mix in a work block or with commutable work block. If you do, the work block bids will be ignored.
- You can bid pairing ID and commutable work block on the same layer, which will create work blocks that utilize the pairings specified (the pairings need to fulfil the report and release requirements stated in the commutable bid).
- Bidding trip mix and commutable work block on the same layer produces work blocks with only the trip mix
- Bidding commutable work blocks with a specified layover will produce work blocks composed of only pairings with that
- Bid four-day trips with report and release times on one layer then commutable work block on a following
Cadence Preference. This preference states that you want your work blocks to start on the same weekday. For example: any four-day pairings as long as they all start on Tuesdays. This is a line constraint and if it is not satisfied the system will move to the next layer. If you bid two specific pairings that start on different days of the week, this preference forces the system to move to the next layer if it cannot fil around them to make the starting days the same. This preference does not consider carry-in pairings. It looks at the current month. It is always recommended to un-check this preference from your last layer to ease the constraints.
Work Block Size. This preference provides the ability to bid the desired size of work blocks. Click on the preference and click on the drop down list next to “low” and click on the smallest size of work blocks desired (1 – 6 days), click on the drop down list next to “high” and click on the largest size work block desired (1 –6 days) and click bid. As an example, your preference maybe a low of “3” and a high of “5”; the system would build no work blocks smaller than 3 days and none larger than 5 days. Remember, don’t bid one of the work block bids (Trip Mix or Commutable Work Block) and also bid size of 1-3. This causes a conflict because they are by definition four-day combinations. Doing so will push the bidder to the next layer, maybe LN.
Max Weekend Days Off. This preference instructs the system to arrange your selected pairings in a manner that maximizes the number of weekend days you have of. In this preference the system scores three individual Saturdays of higher than a weekend of (one Saturday and one Sunday), 3 vs. 2.
Note: In some cases the pairings that have been specified may only be available on weekends. If this is the case and the system can build a legal line it will, even though there are no weekend days of .
Waive Training Credit. This preference allows a crewmember to waive the total credit of her/his pre-assigned training in this bid month. The credit is waived in an Al or None manner. For instance, a crewmember has got 12 hours of training credit for the training events on 4th, 8th, and 10th. By making this bid, she/he will waive the total 12 hours of training credit.
Waive Virtual Credit. This preference lets crewmembers to waive vacation credit by an increment of 2 hours and 30 minutes (2:30), or to the maximum vacation credit he/she has got for this month. When the preference is chosen, a dropdown list box presents the valid credit values to be waived, with an increment of 2:30 credit hours. Once the value is chosen, the crewmember may click on the Bid button to submit this bid and check this bid later in the Prioritize Layer page. As an example, if a crewmember has got 4 vacation days, total of 12 credit hours for this month. When she/he bids for waiving 12:30 credit hours, the system will waive the eligible 12 credit hours.
Clear Award/Partial Line. With this preference, the crewmember can instruct the system to create a complete line that utilizes his or her choices from the layers leading up to the Clear Award/Partial Line preference. If a complete line cannot be awarded based on this first layer(s), the system will conduct a final optimization in this first layer(s) and consider al the available pairings in its pools as a last resort before restarting from the layer designated by the Clear Award/Partial Line preference. The resulting line award from the final optimization would still maximize the crewmember’s requests by layers. If the system is forced to employ the Clear Award/Partial Line preference because a line cannot be completed from the first layer(s) through the crewmember’s choices or through the final optimization, the system automatically discards al preferences specified in the first layer(s) and begins a new line awarding process on the layer designated by the Clear Award/Partial Line preference. This preference provides for an “al or nothing” form of bidding practice. There is no limit for the number of layers being set with this preference.
Clarification of Line Properties
There are four Line Properties that need clarification:
- Min Of Days Between Work Blocks
- Work Block Size
- Target Line Credit Range
- Number of Days Of
Properties 1 & 2 must be bid in Layer 1, otherwise the system will read the defaults: “2 days off” between work blocks and work block size of “1 to 6 days”. Once values have been bid the bidder can only bid more relaxed values for these two properties on subsequent layers. If the bidder skips bidding the work block size on a layer the system will adopt the default.
A bid of one of for Min Off Days between Work Blocks on any layer will result in one of on al subsequent layers unless “Clear Al” is used.
If they skip Min Of Days Between Work Blocks and the previous bid was three or more of then the system will use the default (two off ).
Property 3: The system will use the entire window of credit range (the range set by the company), if there is no bid. Once a range is bid the subsequent layers should bid wider ranges. If not the system will use the wider range; for ex. L2 the range is 75 to 80 hours and L3 is 85 to 90 hours, the system will use 75 to 90 hours in L3. Unless “Clear Award” is used.
Property 4: If there is no bid the system will solve to satisfy the existing bids, ensuring 10 or 11 of days. Once Min. Number of Days Of has been bid the subsequent bids must request same/fewer of days, the system will operate on the smallest of all of the previous bid values.
Click on the Pre-Built link and a list of the pre-built CDO lines will be displayed. Pre-Built lines are bid in a set to be put in layers.
Warning: If you have any pre-assigned activities other than carry-in trip in your bid month, you WILL NOT be awarded any Pre-Built line
There are 3 ways to bid for a Pre-Built line:
- You can click on Append Pre-Built Line Number to append your Pre-Built lines
- You can also use the drop down window to select your desired Pre-Built line. Select the line and click “Append” and the line will appear in the bidding
- At the bottom of the page there is an input box where you can type in the line number(s) of the Pre-Built you want to If you want to bid more than one Pre-Built, the line numbers must be separated by only a comma with no spaces.
Note: The maximum amount of Pre-Built in a set is 12.
You can hover your mouse pointer over Pre-Built pairing number to view detail information of the pairing. After you are satisfy with your Pre-Built set click on Bid. Use the Prioritize Layers link and place the Pre-Built set in the layer you want. You can only bid one Pre-Built set per layer.
Note: Do not layer pre-built set with any other bids and that includes other pre-built set.
The system will award you Pre-Built in the order of the set, so if the order is 0007, 0002, 0003. The system will try to award 0007 Pre-Built line first and 0002 last. If the system cannot award you a Pre-Built line, it will try and award you a regular line, based on the preferences you choose in the next layer.
Reserve Off Days Bid
By clicking on the Reserve link, the system displays two calendars, a targeted reserve crewmember per day chart and a calendar for you to bid your of days. The targeted reserve per day chart is set by company on minimal y how many reserves are required per day. Use the chart to bid your reserve of day accordingly. The second calendar extends back at least 6 days into the previous month, and 6 days into the next month, so you can see the scheduled activities that do not occur in the current bid month.
These scheduled activities may impact the way you bid and/or your legalities. This calendar is for bidding the reserve days of you want. You can do this by clicking on (M)ust or (P)refer of each individual day.
- Must Off Days are required of If the system can’t satisfy the Off days it will move on to the next layer
- Prefer Off Days are of days that the system will consider but will not move on to next layer if you can’t get Instead the system will try to maximize the number of off days you requested.
To delete your of day bid just click on corresponding M or P again. Note: Must and Prefer Off Days cannot co-exist with each other
The Prioritize Layers is an extremely important function. This is where a crewmember instructs the system which of your preferences is your first choice, second choice and so on.
Click on the Prioritize Layers link and you will see a screen with a “Matched Pairing Chart” on top followed by a box with your pre-assignments, a box with tools, a box showing reserve, a box showing the of days you bid, a box with the pairings & pairing properties you bid and a box with the line properties you bid. If you did not bid a category then there will not be a corresponding box.
At the very top of the screen there is a button to “Delete User Bids”. Use this if you want to clear al of your existing bids. Your absolute seniority and relative seniority in the bid package are also displayed.
The Matched Pairing Chart shows how many pairings are available to you based on your of days, pairings and pairing and line property bids. The line properties when bid alone will show 100% of the pairings available (except for “Trip Mix in a Work Block” which will add all of the pairings bid i.e., 1×3 includes al the 1 day and 3 day trips).
As you check and uncheck preferences in the table below the chart, click on “save layers”, the chart will recalculate and display the new number of pairings available. The chart displays are cumulative (layer 2 shows the pairings available from the preferences of layer 2 plus the pairings from layer 1), unless you have checked a “Clear Award/Partial Line”. The bars in the chart are color coded; green for the pairings selected, yellow if the next layer has not changed red if the number of pairings that have been reduced in the following layer and blue is for the layers with no bids.
Your pre-assignments are shown next, followed by a box of tools. The tools are: check/clear all used to check all preferences in a layer or clear all checks in a layer; invert layer checkboxes if you wanted to bid the exact opposite; and copy from previous layer used to copy al checks from one layer to the next. The tools are for your convenience.
The following boxes show reserve, of days, pairing & pairing property preferences and line property preferences you bid. To direct the system, check all but your first choices. Then place a check in layer two for your second choices, check layer three for third choices and so on. Then click “Save layers”, the chart will calculate and display the number of pairings available to you based on your choices (layers 1, layers 2, and so on). It is important to increase the number of pairings available in your subsequent layers.
The “Save layers” button is located at the bottom left of the screen. Remember to save layers each time you change the checks in your layers. (We have implemented a function for Internet Explorer V6 and above that initiates a popup if you go to another function without saving, it asks you if you want to save.)
Strategy for using the prioritize layers: Start by bidding the days you want of and then bid the type of flying you want. In your case you are senior and want weekends of and there are four specific days you also want off. You like three day trips and you like to start in the morning but not too early. Click into the Of Days screen and click on al of the days you want off . Then click on Pairing Properties and click on Pairing Length. Select three-day trips and click bid. Then click Report Between and set your report time window, say between 08:00 and 12:00. Click bid. Repeat the Report Between bid, this time open
the time window, say 07:00 to 12:00. And repeat again, opening the window, say to 07:00 to 13:00. Now go to prioritized layers. Remove the checks on the second two Report Between. Check the middle one on layer 2 and the widest one on layer 3. No checks on any Report Between on layer 4. Now decide which of the of days are most important to you. Place checks in layers 2, 3, & 4 next to them. The other of days check layers 2 & 3 if mid importance. The least important only check layer 1. Now check next to the three day trip in layers 2, 3, & 4.
This strategy starts by asking for it all, but then gives the system more options at each layer, while it continues to hold onto what is most important to the bidder.
There are seven layers to express your preferences; we highly recommend that each crew member uses at least three to four layers.
Don’t skip a layer.
When a blue bar appears on the bar chart in a Layer, no Pairings have been selected. When one skips a layer, the system considers al of the pairings that are still available before the skipped layer, and builds a line at that layer. The system will create a Pairing pool for the blue bar Layer, which adds al of the available Pairings for that bidder to the Pairing pools in that Layer. It will optimize a solution including the unchecked Layer, and treats it as if it was a checked Layer. There is a special case: if the system cannot build a complete line and there was a subsequent reserve bid, it would use the reserve bid.
Warning messages will appear below the matched pairing chart when specific incompatible bids are made. These messages are to alert crewmembers that they have made a bad bid and that they need to change their bid. The following warnings will appear:
- Cannot have trip mix and pairing length bids on the same layer, Cannot have trip mix and pairing ID on date bids on the same layer, Cannot have more than two trip mix bids on the same layer,
- Cannot have commutable work block and pairing length bids on the same layer, Cannot have commutable work block and pairing ID on date bids on the same layer, Cannot have multiple commutable work block bids on the same layer,
- Cannot have prefer and avoid deadheads on the same layer,
- Fly with bid should not co-exist with any other bids (except “min of days between work blocks”),
- Cannot have multiple groups of reserve line bids on the same layer, Reserve bid should not co-exist with any other
- Red Bar: “Cannot Display Bar (Query Limit Exceeded)”
In this last case a Red Bar appears. In exceptional cases, the requested Pairings may exceed the capacity of the web to display the number of Pairings in the bar chart. In that case, a red bar with an inserted note, “cannot display bar (query limit exceeded)”. Al of the Pairings requested will be in that layer, but will not be shown with a green bar. Al of the Pairings in that layer can be viewed from the View Pairing Set hyperlink function.
View Pairing Set
By clicking on the View Pairing Set link you can see which pairings are available to you based upon your preferences and by each layer. The lists of pairings shown available are those in that particular layer. The pairing count is not cumulative.
Each layer shows the pairings that have been defined by the checks in “Prioritized layers” for that layer, so if you check a pairing ID on date on three layers it will appear in each of those layers.
At the top of the screen there is a drop down window labeled Viewing Layer, click on the layer number you are interested in viewing. You view one layer at a time.
The table shows al the pairings available in the layer selected. Displayed are the day of week and date, followed by the pairing number that operates on that date. In parenthesis after the pairing number is the length of the pairing.
To simply view the pairings place the cursor over the pairing to be viewed (for older browsers you will need to click on the pairing number to view).
To view and remove the pairing from the pairing set, click on the date.
And then click on the message “Click here to remove pairing ### on date” at the top of the individual pairing. Click on the ‘Bring Back Al Removed Pairings’ button to bring back all the pairings that was removed. This provides a method to remove specific pairings from the pool of available pairings.
To return to layer 1 click on View Pairing Set on the left side menu, to return to the same layer click on the View Set button on top of the page. Each layer shows the pairings that have been defined by the checks in “Prioritize Layers” for that layer.
Clicking on the Print Bids link provides you a print function for al of your bids. The printout shows you the Preferences you selected from each category and the Layers that were selected for each Preference. The page starts with Username, Open period and Bid Package Information, followed by a listing of the bid categories that are used. The first category is pre-assigned activities, then reserve, of days, pairing and line properties. Each category contains the preferences bid, the bid is printed followed by a set of parenthesis containing its bid code (this code is mainly used for internal reference), followed by the layers that have been checked and then depending on the preference either date, weekday, value of credit or city or time, etc. If a category has not been bid it will not appear in the print.
By clicking on the Standing Bids link, you will see a set of preferences that are al unrelated to specific calendar dates, and unrelated to specific pairings. When no preferences are entered a “No Bids” message shows at the bottom of the preference list. Make a bid and the “No Bids” message will go away and a set of prioritized layers will be displayed. Enter your checkmarks on the appropriate layers and click “Save layers”. This is your method of defining choices within the Standing Bids.
At the bottom left there is the option to “Add Standing Bid into Current Bids”. Click this if you want to start your current bid by using your standing bid as a beginning point. Note, if there is an existing current bid your standing bid will be added to it. The “Replace Standing Bid with Current Bids” option will
replace your existing standing bid with your current bid. There is also a “Clear Standing Bid” button. Click this if you want to start your standing bid over. The Standing Bid function allows you to enter a bid that remains in the system. If you do not bid in the current bid month the system will use your Standing Bid.
Everyone needs to enter a Standing Bid!
The Standing Bids screen is composed of a list of General Preferences and a Prioritize Layer function. Please note that since the Standing Bids can be used for any month al references to any dates have been removed from this function.
Below is listed al of the available preferences for standing bids, the only one that is different is “Day of Week Of”, all others are described in pairing, line properties and reserve.
- Day-of-Week This Preference allows you to request the day of the week of . Click the preference and select your desired day of and click Bid.
· Minimum Average Credit per duty period
- Pairing Length
- Deadhead Preference
- Report Between
- Release Between
- Layover at City
- Min Connection (Turn) Time Preference
- Max Connection (Turn) Time Preference
- Min Layover Time
- Max Layover Time Preference
- Max landings per duty period
- Landing at City Preference
- Number of Days Off
- Target Line Credit Range
- Min Off Days Between Work Blocks
- Trip Mix In A Work Block
- Commutable Work Block
- Cadence Preference
- Work Block Size
- Max Weekend Days Off
- Waive Training Credit
- Waive Virtual Credit
- Clear Award/Partial Line
What happens when the crewmember enters an incorrect value to his/her standing bids?
It is possible that a crewmember may enter incorrect information to his/her Standing Bid. Examples are: city that is not a destination in the schedule for this equipment, or the crewmember entered an equipment
code that he/she is not qualified to fly. To prevent further problems caused by the incorrect information in one’s Standing Bid to his/her line award, the system blocks the incorrect information from being applied to the current bids.
When the crewmember clicks on the button “Add Standing Bid into Current Bids”, the system validates al standing bids to ensure that al values are meaningful. An incorrect value in the Standing Bid causes the system to post an error message in red color to warn the crewmember that a specific bid has incorrect information. If the crewmember would like to keep that bid, he/she should go back and correct the bid. Otherwise, the system would just apply valid bids to the current bids, and ignore the incorrect ones.
View Prev Bids
By clicking on the View Prev Bids link you are able to see your previous month’s bid. A calendar appears showing the specific of days and specific pairings that were bid. There is also a listing of your general bids. Additional y, your award and the related pairings are displayed. Select the specific bid package from your dropdown window. At the bottom of the calendar appears a button “Add these Previous Bids into Current Bid”. You may click on this button to add your previous bids from that displayed month into your current bid. Again, any bid that is Pairing specific or Date specific will not be incorporated into your Current Bid.
LINE 20 PAY 88:49 2| 3 4 5 6 7 | 8 9| 10 11 12 13 14 |15 16| 17 18 19 20 21 |22 23| 24 25 26 27 28 |29 30| 31 1 2 3 4 TAFB 283:06 SU| MO TU WE TH FR |SA SU| MO TU WE TH FR |SA SU| MO TU WE TH FR |SA SU| MO TU WE TH FR |SA SU| MO TU WE TH FR
L2 CR. 88:49 7114| 7164 | | 7107 | | 7118 | 7118 7184 | | OFF 14 DH 0:00 MSP * * YXE CLE AUS LSE MSP * * AUS MSO MSP * * V V * * MSP * * MSP * * AUS MSO BNA AUS MSP
PRIORITY P1 P1 P2 P2 P2 P1
DTY 135:26 BLK 87:38 7114=/0615/1350/0555, 7164=/1242/2148/2726, 7107=/0615/2140/1722, 7118=/0835/1758/0742, 7184=/1820/1034/2131
By clicking on the Line Award link you will be able to review your line award, including al pre- assignments, and a print image of al of the pairings that make up your line.
This link immediately displays the awarded calendar line and if you want to review your bids click on “Show/Hide your bids” at the top of the page to review the bids that you submitted.
Below is an example of the line award that the crewmember will see.
The calendar format shows the calendar day and day of week.
The pairing numbers are shown on the next line. The following line shows “-“s for work days and “*”s for of days, and layover city codes.
Below are pairing codes (P1, P2, P3, … P7, or PN or C1, C2, C3,…C7 or CN). These codes represent the layer from which that pairing was selected. PN means that the system ‘filled’ the line with that pairing.
Below the pairing code is listed the duty, block and the pairing number and the report time, the release time, and the credit value of that pairing.
The last line shows the total Pay, TAFB, L1, Credit (CR.),OFF days and Deadhead Time (DH).
The “L1” that is displayed between TAFB and CR tells the bidder the last layer the system used to construct this line. The layers are labeled as L1, L2, L3, … L7, or LN. LN means that the system went past your last layer in order to build the line. This is extremely important to understanding your award
There are 4 pre-assignment codes in the Line Award. They are C/I (Carry-In), L (Leave), V (Vacation), and T (Training).
C/I is counted as duty and as a working day.
L represents al pre-assigned activities that are not counted as duty and are of days. V represents al vacation days. These days are not counted as duty and are of days.
T represents al pre-assigned activities that are counted as duty and are counted as working days.
Additional Notes on Labeling of Pairings in the Award and Solution Layer:
Pairings are marked as P1, P2 … PN or C1, C2 …CN in the awarded line. The pairings marked with a P indicate the layer (pairing pool) in which the pairing was first bid. If the pairing was not one selected by the bidder it is marked as a PN. When pairings are marked with a C they are pairings that are needed to cover flying. This can occur on holidays or when many pre-assignments (vacation, training or leave) are scheduled on the same day of the month. The system based on seniority will require that an individual fly on a particular day, if there is a pairing in one of their pairing pools that matches this need then the system will use that pairing and will mark it with a C and the pool number the pairing came from. If there are no pairings bid that satisfy the requirement the system will solve in LN and mark the pairing CN.
The lines are marked with an L1, L2 …LN to indicate the system solved in a specific layer. The L number states al conditions were satisfied at that level. An L number before LN means that the line constraints are satisfied using pairings that were bid. When LN appears, it means that the line could not be completed with the bids that were submitted. LN can also be caused by required coverage, when it is a CN. When the system is in LN it does not consider any line properties bid but will use the pairings that have been bid. Hence a completed line can be marked with LN and show P1’s, if there is a PN or CN then the line will always be marked LN.
By clicking on the Print Award link you will be able to print out your line award and a list of the pairings that make up your line. This link displays the awarded calendar line and if you want to review your bids click on “Show/Hide your bids” at the top of the page to review the bids that you submitted.
To print the Award you must scroll to the bottom of the “pairing” page and Click ‘Print This Page’. When the printer dialog box comes up, click “OK”. You will receive a print out at the local printer. To return click “Close This Page” also found at the bottom of the page. Note, if the bids were shown, they will be printed, otherwise the bid print will not be included.
Simply click on the Log Out link to get out of PBS and back to the Corporate Web Page. Everything will be saved.
Always Log Out. It closes your session and saves al bids.
Listing of all Preferences
Bid Off Days
- Specific day of month
- Day of week Pairings
- Pairing ID on a date
- Pairing ID Pairing Properties
- Minimum Average Credit per Duty Period
- Pairing Length
- Pairing Length on Date
- Deadhead Preference
- Report Between
- Report Between on Date
- Release Between
- Release Between on Date
- Layover at City
- Layover at City on Date
- Min Connection (Turn) Time
- Max Connection (Turn) Time
- Min Layover Time
- Max Layover Time
- Max Landings per Duty Period
- Avoid Landing At City Line Properties
- Number of Days off
- Target Line Credit Range
- Min Off Days Between Work Blocks
- Trip Mix In A Work Block
- Commutable Work Block
- Work Block Size
- Max Weekend Days Off
- Waive Training Credit
- Waive Virtual Credit
- Clear Award/Partial Line Reserve
Pre-Built Lines Standing Bids
- Day-of-Week Off
General Concepts and Logic
System logic with multiple preferences on the same Layer
When you place multiple general checked preferences on the same Layer, it is important to understand the logic the system uses in processing the preferences.
When 2 or more preferences are checked on the same Layer the system applies either an ‘or’ logic or an ‘and’ logic. Preferences within a category are ‘or’. Preferences across categories are ‘and’. Some specific examples are listed below.
Or example: If you bid to fly both 3 and 4 day trips (same category) on the same layer, no other preferences checked, the system considers this to be a bid for al 3 day trips, al 4 day trips, ‘or’ any combination of 3 and 4 day trips.
And example: If you bid to fly 4 days and layovers in MSP (two different categories) the system considers this to be a bid for 4 day trips that layover in MSP. Both conditions (4 day trip ‘and’ layover in MSP must be present.
For example: If the checked preferences are:
4 day trip BOS layover MEM layover
The system interprets this as a request for 4 days trips only ‘and’ the 4 day trips being considered must have at least one layover in either PHX ‘or’ SAN.
For example: If the checked preferences are:
- day trip
- day trip BOS layover MEM layover
The system interprets this as a request for 4 ‘or’ 3 day trips only ‘and’ the 4 day or 3 day trips being considered must have at least one layover in either BOS ‘or’ MEM.
For example: If the checked preferences are:
- day trip
- day trip BOS layover MEM layover
1200-2300 Report Between
The system interprets this as a request for 4 ‘or’ 3 day trips only ‘and’ the report time must be between 1200-2300 ‘and’ the 4 day ‘or’ the 3 day trips being considered must have at least one layover in either
BOS ‘or’ MEM.
For example: If the checked preferences are:
- day trip
- day trip
5:00 Min. Credit
1200-2300 Report Between cadence
The system interprets this as a request for 1 (locals) ‘or’ 2 day trips only ‘and’ the 1 (locals) ‘or’ the 2 day trips being considered must have at least 5:00 Min. Credit per duty period ‘and’ the Report Between (report time) must be between 1200-2300 ‘and’ each work block must start on the same day- of-week across the whole month.
If your intent is to fly specific pairings on specific dates or any of the dated preferences, bid those preferences on a layer by themselves. If you combine them with general undated preferences you could receive any combination of those preferences even if the specific dated preferences were available.
The overall optimization process starts after al inputs are loaded to the PBS Line Generator (includes: current month’s pairings, carry-in pairings, pr assignments, line building parameters and crewmember preferences).
The first process is to generate possible lines for every crewmember based on their first choices, layer 1 bids. We can generate as many as 500,000 lines. For small bases we generate all the possible legal lines.
The second step is to score al the generated lines based on which line conflicts the least with lines more junior to them.
The third step is to set aside the least competing line for the most senior crew member, it must be complete and legal. These lines will contain all first choice pairings if they exist in the bid package. The setting aside process is continued until a partial line is reached.
In the fourth step, we are starting with the first partial line. The first thing we do is to look down at al of the pairings below this crewmember (more junior) and search for first choices to complete the line.
Remember we only generated 500,000 lines in the first process, we did not do a completely exhaustive search (actually in small bases we do but in large bases we need to take another look). If we can complete the line with first choices we do and move to the next partial line. If we don’t complete the line we move to the next step.
In the fifth step we fill the partial line with second layer choices, if not complete we fil with third layer choices and so on until we have used all of the choices. The number of the layer that is final y used is printed on the awarded line (it is in the last line of the print between TAFB and Credit).
If the fil does not complete the line we will then optimize at the last layer bid utilizing al of the selected P1’s, P2’s …P7’s and the line properties from the last layer. The process favors the pairings from the highest layers but will in fact exchange an existing P1 for an available P2 or P3…P7 in order to complete the line.
If we still cannot complete the line, we will move to LN and again optimize the pairing set this time holding the line constraints and allow other available pairings into the solution (PN’s).
We use pairings that fit, when there are multiple solution choices we take the one that conflicts the least i.e., the most junior or from open time. If no solution exists we leave a partial line. We continue this process until the last line is built.
Solution feasibility is checked in each optimization process. Before each line is set aside, the system looks down on each calendar day and verifies that there are enough line holders to cover al the flying on that day. If there are enough the line is set aside. If this line holder is needed to cover flying the system looks to see if there is a bid pairing that will fit. If there is it will be marked C#, if no bid pairing is available then a CN will be used. In some cases a line is set aside because there are enough junior line holders to cover the pairings but subsequently when the junior lines are being built the system encounters conflicts caused by legalities and these pairings cannot be covered. These are the pairings that end up in open time.
Good Bids and Bad Bids.
A Good Bid has a number of pairings available appropriate to one’s seniority and there are no logical conflicts in the bid. The bid contains choices in at least three layers. If the bidder is mid-seniority then by layer 3, the bidder should have 50% of the pairings available.
A Bad Bid has no pairings available on layer 1 and no other layers bid. A Bad Bid contains logical conflicts. A Bad Bidder bids only layer 1, unless you are number 1 on the seniority list (but be sure you have made enough selections to build a complete line).
As an example, a bid that is not so good bids 13% available pairings when at 60% of the seniority list. One might get lucky, but bid more choices and give the system more options to build a line of your liking rather than just fil the line.
Bidding Conflicts – System Response Pairing Properties:
Bidding specific pairings on dates will overrule of days. No other bid will overrule of days.
We suggest bidding only specific pairings on layer 1 and then more general bids on layers 2, 3, and so on. This insures that the specific pairings are the only P1’s.
Bid report between. Bidding multiple report times on the same level is allowed. Be sure that the times do not conflict. Bid a report window such as 0500 to 0700 and another window as 0900 to 1200. This example would tell the system to select pairings that did not report during the commute rush (avoid 0701 to 0859). Note that the time windows should not overlap.
Do bid the more constraining report times on layer 1 and relax on the next layers.
Release between behaves the same way.
When you bid a min or max layover time preference the system excludes al turns. Note: the search will exclude the turns but on prioritize layers you will get the turns.
Max TAFB Credit Ratio. Don’t bid multiple ratios on the same layer, the system takes the most constraining one; again relax the ratio on subsequent layers. As the ratio gets larger you are away longer for the same amount of credit.
Min Off Days between Work Blocks. Bid the more constraining bid in layer 1 and again relax in subsequent layers. For example, bid “Min Of Days between Work Blocks” 3 on layer 1 and then 2 on layer 2, and then maybe 1 on layer 4.
If one were to bid layer 1 as 1 of and layer 2 as 2 of; the system honors the line legalities of the first layer. So in this case at layer one a partial line is built and there is a single day of between work blocks, the system in layer two will hold the P1 pairings and as a result ignore “Min Off Days between Work Blocks” of two in layer two.
Target Line Credit Range. Bid a range, the system is trying to find a combination of trips that when added together will satisfy your request. We suggest at least five hours, i.e., 85 to 90. Do not bid a point, for example 85 to 85. There is likely no combination of trips that will hit that exactly.
When bidding “Min. Number of Days of” and “Target Line Credit Range” make the combination doable. For example, if you want lots of days of, maybe 15, then bid a line value that is worth 75 to 80 credit hours. Don’t bid 15 days of and also a line value of 95 to 100 hours. The system at the line properties level is trying to satisfy the 15 day constraint and if it fails will move to your next layer. At the same time it is checking the feasibility of the line based on the requested target line credit range and finds that it is infeasible and will also move to the next layer to try to build a feasible line. When the system cannot do both, the result satisfies neither because the system will move on to LN.
Note: the refined definitions for “Trip Mix In a Work Block” and “Commutable Work Block”. We define these special cases of work block as a combination of two pairings and at least four days, with preceding and succeeding of days. This solves the situation of building combinations of 2,2 followed by a 2. Bidders who want to fly 3 day and 4 day commutable pairings need to bid the pairing length, plus their desired report and release between on different layers.
Pairing Pool Discussion
When bidding in PBS the crewmembers need to think about the pairing pool that is created from their bids. Generally, bids should be designed so that the first layer is most specific, the second layer a bit less specific, the third layer fairly less specific, the fourth layer general and the fifth layer, more general. So in terms of the pairing
pool size, the first layer adds some pairings (specific ones) and each layer adds more pairings. Keep in mind that the system will award as many of the layer one pairings as it can.
Some bids will add pairings while others are conditioning bids and will reduce the number of pairings in the pairing pool. For example: I bid four day trips, all of the four day trips will be in my pairing pool. If I next bid a report time window of say 07:00 to 11:00 on the same layer, this will limit the pairings in my pool to four day trips that report between 07:00 and 11:00.
With this in mind, we should review some of the bidding preferences.
Pairing length: These bids enable the bidder to specify the length of trips that are desired, they can be one day, two day … including all the different lengths available in their base (their bid package).
Conditioning bids: Conditioning bids (such as report, release, avoid landing at city, max landings per duty period, layover at city, connection time … and so on) when bid alone will add al pairings (except CDO’s) that meet the criteria to the pool. So if I bid layover at SFO, al pairings that layover in San Francisco will be added to my pool. Similarly, if I bid avoid landings at ABI, al pairings that don’t land at ABI will be added to my pool. And likewise if I bid weekends of, all pairings that don’t touch weekends will be added to my pool.
On date bids: These are special bids because they will bring into the pool those pairings that meet the specified dated criteria. Bidding “of days” and “on date bids” will not increase the number of pairings in your pool (only those pairings that satisfy your “on date bids” will be included) but the of day bid will reduce your pool if an “on date bid” pairing operated on the specified of day. The exception to this is bid “Pairing ID on Date”.
Bidding “On Date” bids on layer 1 by themselves is strongly recommended!
Bidding Cases and Bidding Scenarios
- How to bid for maximum credit value Use the “Target Line Credit Range” preference. Bid for maximum credit value by setting a high credit range (ex: 95-100 for RJ CAs & FOs) at layer 1. If one of your main objectives is to receive a high credit value line, then keep that range clicked throughout all the subsequent layers.
Note: The Company sets the line credit window for each base, fleet and position.
- How to bid for maximum block time. The system calculates all preferences in terms of credit. The only time block is used is to calculate legalities.
- How to bid for efficient trip/duty rigs
- There are two preferences a crewmember can bid depending on their definition of efficient trip.
- Use “Minimum Average Credit per DP” to bid pairings with a credit value per duty period equal to or greater than your preference. On the other hand if you really want to be “Away From Base” for as little time as possible, then bid the “Max TAFB credit ratio” preference (time away from base divided by credit). This preference looks for trips that are tight (least TAFB for the most credit) not necessarily trips with the highest credit value.
- 4) An accurate description of when & how to use (as well as the functionality) of the Clear
Award Partial Line Preference.
The Clear Award/Partial Line preference is on the first layer after the layer to be cleared. In other words the crew member bids a series of preferences on layer 1. Their thinking is that they want to hold al of pairings on layer 1 to make a legal line, and if that is not possible then they want to throw away those preferences and start over from layer 2, then click Clear Award/Partial Line on layer 2. The Clear Award/Partial Line preference can be applied to multiple layers. If the Clear Award/Partial Line preference is checked on layer 4, the system will throw away al of the bid results and the bid requests from layers 1-3 and start over at layer 4 if the system could not build a legal line out of layer 1-3.
Can “Clear Award/Partial Line ” be used in multiple layers? Yes
An accurate description of when & how to use (as well as the functionality) of the cadence preference. “Cadence” is a preference that is a line property. The system tries to start work blocks on the same weekday. Use this preference when bidding very general, i.e., bid any four day trip worth 5:00 per duty period and cadence. The when is subjective, our thinking is to use it when a regular schedule is important but the actual days of work are not. Note: If you have already bid specific pairings that start on different week days or of days on different week days then cadence is compromised. Because cadence is a line constraint it forces the system to move to the next layer to try to build a complete line when there are conflicting elements.
Why should we bid specific pairings in a dedicated layer and general preferences in a subsequent layer? What other preferences are acceptable in the same layer as the specific pairing? We suggest bidding only specific pairings on layer 1 so that they are the only P1s. This assumes that these are the most important. Bid general preferences in subsequent layers. The why is this makes the specific pairings P1 and they do not have to compete with other P1 pairings. Then continue to bid the of days with the general bids.
Browser back buttons do not work. Yes, we see this too. The browser does not see the entire application. We ask that you do not use the browser back buttons. Use the links on the left hand side of the screens to go the page you want.
Is matched pairing chart always cumulative? Always cumulative until the “Clear Award/Partial Line” preference is used.
Exactly what preferences (both pairing and line properties) does the chart display?
The chart displays pairings available based upon the pairing preferences and line preferences. If Line preferences are bid alone in layers 1 al pairings are available, Trip Mix is the exception.
Remember that the pairing and pairing property preferences determine the pairings available to build your lines. The line properties set line constraints and feasibility.