Introduction
N-PBS 24.1 Enhancements
N-PBS 24.1 Enhancements
We estimate that this will take 3 minutes to complete.
Detailed Explanation
S-69448 - ALL - Quick Stat Additions
For all customers, we added two statistics to the Quick Stat window below the Average Line Value (ALV):
- Run Converged: Yes/No
- # of Passes
S-80044 - ALL - Add Midnight Offset to Pairing Domicle Rest with Table Rule
The MidnightOffSet parameter for the DomicileRestWithTable Rule is now available.
The MidnightOffset parameter affects the ends of activities (including both pairings and working absences) and is specified in minutes.
Any activity that ends at or before 00:00 plus the midnight offset, and starts on an earlier day, is treated as ending on the previous day. This does not count as work for the "next day".
Example: A setting of 120 minutes causes any activity (starting on the previous day) and ending at or before 02:00, to be treated as ending on the previous day.
Note: All customers can set their MidnightOffset value, if they choose to use this parameter. Otherwise, the value should remain at zero.
S-72491 - JZA - Credit Carry In - Proration Change
We configured JZA with the ability to modify the proration for Credit Carry In days in PairingDomicileRestWithTable and ReserveTotalDaysOff Rules.
For Credit Carry In days that do not have any of the codes C1, C2, C3, C4, or C5, the existing functionality remains unchanged. The number of Credit Carry In days is added to:
- the number of prorating days used for searching in the proration table.
- the minimum number of days off required.
Example:
- The period has 30 days.
- The user has seven Credit Carry In days.
- The Proration table maps zero prorating days to ten days off.
- The Proration table maps 7 prorating days to 8 days off.
In this case, the user requires a minimum of 15 days off in the period, calculated as follows:
- The number of prorating days is 7 (because Credit Carry In days add to prorating days).
- The Proration table maps seven prorating days to 8 days off.
- The user requires a minimum of 15 days off (i.e. 8 returned from the table, plus the 7 Credit Carry In days).
Thus, the user requires 7 days off, which correspond to the 7 Credit Carry In days, and then within the remaining 23 days off they require the prorated number of days off (which is 8).
S-72491 - JZA - Credit Carry In - Proration Change Cont'd
Conversely, for Credit Carry In days that do have one of the codes C1,C2,C3,C4, or C5; the number of Credit Carry In days is:
- not added to the number of prorating days used for searching in the Proration table.
- still added to the minimum number of days off required.
Note: The equivalent adjustments are made to the Reserve Proration.
S-78284 - ASAP - Add X Minutes Off In Y Rule with Waive Bid
For ASAP, we added the rule X Minutes Off in Y Minutes from Beginning Of FDP Rule.
By configuring the waive bid, the Federal Aviation Rules (FAR) takes effect.
- X-Minutes = 1860
- Y-Minutes = 10080
- In-Base = True
- LookBackFromTrainingAbsences = False
Also, a new Waive Bid 30 Hour Rest Away From Base has been added.
S-78331 - ASH - Add RestBeforeAndAfterPairings to Configuration
For ASH, we added Add RestBeforeAndAfterPairings to ASH Configuration to all three rule sets.
Also, we have removed Pairing-DomesticHomeRest from all rule sets.
S-78783 - SCX - Improve error message for missing previous duty for
AIMS Absences & History (Job 147 import)
We have improved the error messages for AIMS Absences & History (Job 147) import. Prior to this, several cases were not covered by the error messages.
Error messages added include:
- No prior duty found:
- Duty Report Date, Duty Report Time - empty values
- Duty Debrief Date, Duty Debrief Time - values entered
- No duties found:
- Duty Report Date, Duty Report Time, Duty Debrief Date, Duty Debrief Time - empty values
- Unable to convert...:
- Duty Report Date, Duty Report Time, Duty Debrief Date, Duty Debrief Time, Actual Date of Departure, Actual Time of Departure, Actual Date of Arrival, Actual Time of Arrival - wrong value format
Note: Error messages were created according to the pattern: Pairing Start Line Number + EID (Employee ID) + Pairing Number + field name
Example: Pairing Start Line number 12455, EID 1234, Pairing number 999; Unable to convert Duty Release Date 12/1
S-80730 - ASAP - I5 Update with Qualifications and Restrictions
For ASAP, we enhanced the I5 import to be able to read and apply the appropriate restrictions listed below:
- If a pilot has the Crew Pairing restriction, then the “Green” attribute is applied to the pilot.
- If a pilot has the High Minimums restriction, then RDB is added as a location restriction.
- If a pilot has the ADAK restriction, then ADK is added as a location restriction.
Note: Green restriction or Location restriction are removed if they already exist on a pilot’s profile, but a newly uploaded I5 does not include that same restriction.
