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

N-PBS 24.3 New Features

  1. Introduction 

N-PBS 24.3 New Features 

N-PBS 24.3 New Features 

We estimate that this will take 4 minutes to complete.

  1. Detailed Explanation 

S-77442 - JBU - Crew Absence Import from TOPS

We created the ability to import Crew Absences from JBU's TOPS system.

These enhancements include:

  • A TOPS Absences Option in the Import dropdown.
  • A TOPS Absences Column to display the results of the import.

     

After completing development, JBU admin are able to:
1. Login to the Admin UI for JBU.
2. Go to the Period tab.
3. Click the Data button for the selected period.
4. In the Import Files section, click the Import Files dropdown.
5. Select the TOPS ABSENCES option from the dropdown.
6. Click the Choose file button, select a proper .xml file and open it.
7. Click the Import button.

Expected result:

  • The import logs display. 
  • The file is successfully imported.
  • The TOPS ABSENCES Column in the Pairing Data Status table updates (ex.AB/388). To confirm, select Yes.

 

S-77437 - JBU - Pairing Import from TOPS 

For JBU, we created a new functionality to import pairings from JBU's new TOPS system.
 These new features include:

  • A TOPS Pairing Option  in the Import dropdown.
  • A TOPS Pairings Column to show the results of the import.


After completing development JBU admin are able to:
1. Login to the Admin UI for JBU.
2. Go to the Period tab.
3. Click the Data button for the selected period.
4. In the section Import Files, click the Import Files dropdown.
5. Select the TOPS Pairings option from the dropdown.
6. Click the Choose file button. Select a proper .xml file and open it.
7. Click the Import button.

Expected result:

  • The import logs display.
  • The file is successfully imported.
  • The TOPS Pairings column in the Pairing Data Status table updates.
  • The downloaded records can be searched in the Pairings tab.

 

Note

  • The data as BASE, Equipment, position, and crew categories must be configured first. 
  • The TOPS Crew file has to be imported first.

     

S-77437 - JBU - Pairing Import from TOPS cont'd

Error messages
Error messages are specific to the root cause of the error. The error mentions the crewID and the field for which the error occurred. It depends on the squad to frame the failure message, but it is important to mention the crewID and field.
Note: The error messages displays in the Import Files section.

 

S-78996 - JBU - Crew Import from TOPS 

We have enhanced a new integration to import crewmembers from JBU's new TOPS system. 

These new features include:

  • A TOPS Crew Option in the Import Dropdown.
  • A TOPS Crew Column to show the results of the import.
     

After completing development JBU admin are able to:
1. Log to the Admin UI for JBU.
2. Go to the Period tab.
3. Click the Data button for the selected period.
4. In the section Import Files, click the dropdown. Refer to Screen 1.
5. Select the TOPS Crew option from the dropdown.
6. Click the Choose file button. Select a proper .xml file and open it.
7. Click the Import button.
 

Expected result:

  • The import logs displays.
  • The file is successfully imported.
  • The TOPS Crew Column in the Pairing Data Status table updates (ex. E/388). Refer to Screen 2.

     
  • The downloaded records can be searched in the Crew tab.
       

S-83453 - MXY - Redeye Imports 

For MXY, we have enhanced the Redeye Imports to flag certain pairings as Redeyes within the N-OC Pairing Import. Any leg that now touches between 0115 and 0445 is flagged as a Redeye.
Note: A Redeye is any flight that departs in the range [1600, 0445] station local and arrives in the range [0115, 1400] station local.

 

S-81415 - SCX - First Out/Last Out for Reserve and Pairing preferences -
 WebApp and Export 

We created a new functionality to collect First Out/Last Out (FOLO) preferences from employees. SCX can now export preferences from PBS and import them into their CMS with this new function.

 

Scenario:

  1. Bidder logs into the WebApp.
  2. Bidder creates a FOLO bid and submits.
  3. Admin logs into the Admin application and completes a scheduler run. 
  4. Admin exports the FOLO Bid file.0.

 

FOLO Requirements

  • Pilot defines whether they want First Out or Last Out (if the pilot is placed on the reserve), which is used by the company during the day of operation.
  • Both pairing lineholders and Reserve pilots should be able to bid for FOLO.
  • There are instances where a pilot with a pairing line could be assigned to reserve or reserve is embedded in a pairing.

 

S-81415 - SCX - First Out/Last Out for Reserve and Pairing preferences -
 WebApp and Export Cont'd

We created a new group named FOLO Bid. Previously, FOLO was placed 

as an additional bid group below Award Pairings/Reserve.
 

Also, Pilots are now able to bid on First Out or Last Out, in addition to the following reserve periods: 

  • AM 
  • PM 
  • RE  
  • and LC (Long Call).

 

 

Did you find it helpful? Yes No

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