{//% unless portal.user.is_agent %} Tickets
Login Submit a Ticket News {//% endunless %}

N-PBS 22-5 New Features


22-5 New Features 

22-5 New Features 

We estimate that this will take 6 minutes to complete.

Detailed Explanation 

S-65097 - JBU - New Absence Code Flag 


A new absence code flag named "Pre-awarded Reserve Day" is now available to JBU.

Note: This upgrade does not mark any absence codes with this flag. JBU is responsible for marking appropriate absence codes with this flag.

S-63161     - JBU - Pairing - Rest Before and After Absence Rule Flag 


Two new parameters appear in the Pairing-RestBeforeAndAfterAbsences Rule:

  • Work For Duty Only
  • Rest Rules Apply Only.


These are both configured true for all existing configurations except for JBU Cabin. For JBU Cabin, they are configured false.

S-64441     - JBU - Reserve Rest Before and After Absences Rule Flag 


For JBU, three new parameters appear in the Reserve RestBeforeAndAfterAbsences Rule to remain contractually compliant:

  • Work For Duty Only
  • Rest Rules Apply Only
  • Training Only.


For JBU Cabin the parameters are:

  • Work for Duty Only False
  • Rest Rules Apply Only False
  • Training Only True
  • Minutes before 720 (waivable to 660)
  • Minutes after 720 (waivable to 660).


For non-JBU customers, the new parameters are:

  • Work for Duty Only True
  • Rest Rules Apply Only True
  • Training Only False. 

S-62178     - JBU - Base Rest Waive 


The JBU pairing waive now impacts the following rules:     

  • RestBeforeAndAfterAbsences (Minutes after and before)     
  • Pairing - DomesticHomeRest     
  • Pairing-DesignatedOSHomeRest     
  • Pairing -OverseasHomeRest.


There is also a reserve waive which impacts the Reserve RestBeforeAndAfterAbsences Rule. 

S-63322     - JBU - Check Rules During Slide Vacation 


There is a new flag, "Check Slides" which uses the RestBeforeAndAfterAbsences rule.


When this flag is true and when considering slides (within either pairing or reserve bid group), if the RestBeforeAndAfterAbsences rule is present, the system enforces rest using these criteria:

  • In a pairing bid group, enforce the minutes before and minutes after between a slid vacation and pairing, or between a slid vacation and training absence. If the bidder has waived the rule (Waive Base Rest) then the lower value is used.
     Values are taken from the Pairing RestBeforeAndAfterAbsences rule.
  • In a reserve bid group, enforce the minutes before and minutes after between a slid vacation and pairing, or between a slid vacation and training absence. If the bidder has waived the rule (Waive Base Rest), then the lower value is used.
     Values are taken from the Reserve RestBeforeAndAfterAbsences rule. 

S-64850     - JBU - Add Cabin Reserve Waive Bids 


Reserve bid groups (cabin) now have the following bids:

  • Waive Max Days On Up to X
  • X being a range from 7 to 12
  • Waive Min Consecutive Days Off. 

S-63133     - JBU - New Rule - AOffAfterBExtendable 


NJBU Cabin now has a Pairing-AOffAfterBExtendable rule with the following parameters:

  • NumDaysOff: 2
  • MaxDaysOn: 6
  • ExtendedMaxDaysOn: 6
  • LastDayEndBufferMinutes: 121
  • LastDayEndBufferExcludePreAwardedReserveDay: 1 (i.e., true)
  • ExtendedBlockRollingRestMinutes: 1500 (i.e., 25 hours)
  • ExtendedBlockRollingRestNumDays: 7
  • ExtendedBlockRollingRestIncludeLayovers: 1 (i.e., true)

Cabin includes a new waive bid, allowing the user to waive the 2 down to 1 and/or waive the 6 up to any value from 7 to 19.

Note:  When a bidder waives the 6 up to a higher value, they are changing the ExtendedMaxDaysOn  parameter value, not the MaxDaysOn  parameter value. For example, "Waive 2 Off After 6 To 2 Off After 10" changes the parameters from:

  • NumDaysOff: 2
  • MaxDaysOn: 6
  • ExtendedMaxDaysOn: 6


  • NumDaysOff: 2
  • MaxDaysOn: 6
  • ExtendedMaxDaysOn: 10



Details of the new rule Pairing-AOffAfterBExtendable

Pairings occur when the value of the parameter ExtendedMaxDaysOn is equal to the value of MaxDaysOn (e.g., NumDaysOff 2, MaxDaysOn 6, and ExtendedMaxDaysOn 6). In that case, the rule is similar to the other "A Off After B" rule (e.g., 2 off after 6). The basic rule enforces the following:
When a person has working activities touching a given number of consecutive calendar days (B), then they must have the next A days off. For example, "2 off after 6": When a person has working activities touching 6 consecutive calendar days, they must then have the next 2 days off (i.e., days 7 and 8).
Note that this rule does not enforce any off-block requirements if the person does not have B consecutive working days. For example, under "2 off after 6," it is legal for a person to work the sequence "5 on, 1 off, 5 on, 1 off."


Layovers within pairings do not count as days off towards the basic rule. However, they can count for the special rolling rest required within extended blocks depending on the ExtendedBlockRollingRestIncludeLayovers parameter. This is described later.


Working Absences

Working absences are counted towards this rule in two ways:

  • they can contribute days on during the B consecutive days on
  • they can violate the required A consecutive days off

The “Work For Days On Off” flag is used for this rule. That is, working absences are those with absence code with the "Work For Days On Off" flag set to true.
 Note that non-working absences count as rest (days off) for this rule; i.e., this rule completely ignores non-working absences and acts as if they are not present.


Extended Block Functionality

When the ExtendedMaxDaysOn value is higher than the MaxDaysOn value, a block of working days may be extended up to the ExtendedMaxDaysOn. However, their first block of days off (at any point after MaxDaysOn) must still have a length of at least NumDaysOff.

For example, if NumDaysOff  is 2, MaxDaysOn  is 6, and ExtendedMaxDaysOn is 10, then once the person has had 6 consecutive working days (without any days off), their next block of days off must have a length of at least 2 days. It must occur, at the latest, after 10 working days, and there must not be any single days off in the interim range (after the 6 working days, before the 2 consecutive days off).
The Last Day End Buffer treatment continues to apply to the last day in the extended block. For example, when ExtendedMaxDaysOn  is 10, any activity ending on day 10 is subject to the Last Day End Buffer restriction (as described above).

If the parameter ExtendedBlockRollingRestMinutes  is set to a value above zero, then the presence of any extended block (longer than MaxDaysOn) triggers a requirement for a rolling rest. In that case, there must be a rolling rest of at least ExtendedBlockRollingRestMinutes  within any range of calendar days of length ExtendedBlockRollingRestNumDays  which ends on any day within the extended part of the block, after the MaxDaysOn, before the subsequent NumDaysOff  rest.


For example, with parameters NumDaysOff 2, MaxDaysOn 6, ExtendedMaxDaysOn 10, ExtendedBlockRollingRestMinutes 1500 (25 hours), ExtendedBlockRollingRestNumDays 7, then any block above 6 working days must have a rest of 25 hours within each range of 7 days, which ends after day 6 and before the two-day rest (i.e., within the ranges ending on day 7, day 8 (if the working day range is at least 8 days), day 9 (if the working day range is at least 9 days), and day 10 (if the working day range is at least 10 days).


If the parameter ExtendedBlockRollingRestIncludeLayovers is true, then a layover can count as the rolling rest (provided at least ExtendedBlockRollingRestMinutes of the layover occurs within the ExtendedBlockRollingRestNumDays, measured in calendar days using base time zone). 


Last Day End Buffer

When the LastDayEndBufferMinutes parameter has a value greater than zero, any working activity on the last day (that is, day B in a sequence of B consecutive calendar days with work) must end no later than midnight subtracting this number of minutes (for example, LastDayEndBufferMinutes 121 means the activity must end no later than 21:59).

If LastDayEndBufferExcludePreAwardedReserveDay is configured to true, an exception applies to absences with the absence code flag "Pre-awarded Reserve Day" set to true. Those absences are allowed to occur on the last day of a sequence up until midnight.


Pre-Awarded Violations

If there is a violation caused entirely by pre-awarded items, this in itself does not cause the rule to fail (that is, the violation will be ignored). However, the system enforces that a block of NumDaysOff consecutive days of rest must be given before awarding any new item.

 For example: In the case of 2 off after 6, pre-awarded violation of 6 days on, followed by 1 day off, followed by 2 days on (all consisting entirely of pre-awards). The system will enforce that days 10 and 11 must be given as days off, because the person has not yet had the 2 days off they require after the 6 days on. It will not award any new pairings on day 10 or 11.

S-64904     - JBU - Cabin Reserve Output Change 


For Cabin reserve, in any seven day block of work including RS, one of them is changed to R7. For the first seven days, the last RS is marked as R7, and then the system looks forward seven days from that R7 and repeats the process. 


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.