Introduction 

Automation Action Configuration Options 

In this topic, we will review the options available to create Automation Actions. 

We estimate that this will take 7 minutes to complete.

Detailed Explanation 

Automation Functionality and Configuration

This module provides detailed information pertaining to the N-Flight Planning Automation functions, the establishment of Automation Profiles, and the configuration of Automation Actions.
 

ATTENTION 

These functions require configuration by a Level 3 Support team. Please contact NAVBLUE Support for more information about these functions. 

Automation Action Configuration - Automation Attributes 

N-Flight Planning Automation Functionality is based upon automation actions, which occur at customer determined times. The customer can configure many attributes for a single action, and many actions can be employed in an Automation Profile. To begin, you will need to establish Automation Actions. This is done via the Automation Action Configuration Document, pictured to the right. You can assign a unique name to the action you want to create, and then select the attributes that will makeup that action. Each individual action will require its own form.

Available Attributes include:

 Save Results

• Automated calculations can save their results just like a user-initiated calculation within the NFP application, or discard the results, and simply report problems to the user.

     
 IFPS Check

• Should calculated flight plans be validated with the Eurocontrol IFPS system and tested for adherence? (This is only performed if we detect the flight entering IFPS airspace)
  
  

IFPS Retry

• If IFPS validation fails, should the system query CFMU for a compliant route?

     
 IFPS Exception

• If IFPS validation is performed and fails, should automation be halted for the flight in question?

   
 RAIM Check

• Should calculated flight plans be validated for RAIM compliance.

 RAIM Exception

Automation Action Configuration - Automation Attributes 

MTTA Retry

• If routes exist for a given city-pair but route analysis fails to provide a viable route, should the system try to find its own optimum route?

Route Analysis Exception

• The system generates an automation exception if any route viewed by the Route Analysis fails to pass the rules check.

 Lock User Inputs

• The system must only use a user provided route from a previous compute. Removes Route Analysis. The automated calculation must use the route from a previous compute.

 Lock Original Flight Levels

• Future automated calculations must use the same route and associated altitude profile as the last calculation. Ensuring the previous ATC filing remains valid.

     
 Max Routes

• Configuration of the route count limit to consider when choosing the best route to calculate.  The default value is three routes.

     
 Optimization Method

• Set the automation optimization method to a value other than the default.

     
 Warnings Cause Exceptions

• Should flight plan calculations that yield warnings result in automation being halted?

Warning Overrides

• Any specified warning codes will be treated in the opposite manner as the setting directly above. I.e. If all warnings cause exceptions, these will not, and vice versa.

 Transmission Type

• Which type of message transmission should be performed.

     
 Transmission Layout

• An optional override package name, as shown in the NFP reports page. If absent, the default will be used. Applies only for “Flight Papers” type transmissions.

 ACARS Format

• An optional override ACARS format number to use. If absent, the default will be used. Applies only for “ACARS” type transmissions.

 Addresses

• Optional override of destinations for the transmission. If absent, the defaults will be used.
   

ATC CHG

• If enabled, after an initial Flight Plan has been filed, the system will transmit a CHG message when an automated ATC send is executed.

Automation Action Configuration - Automation Profiles

The following section of the module provides an interactive walk-through of the Automation Profile configuration. This assumes that Automation Attributes have already been configured into Automation Actions.  

 The Automation Profile is a grouping of one or more Automation Actions, configured for execution based on a specific time relative to Estimated Time of Departure.

Click the ALC dropdown button.

Click the CZQ list item.

Click the Name dropdown button.

Click the Long range list item.

Click the Use Profile button.

This automation profile has only one scheduled Automation Action. It runs the "Compute and Save" action 24 hours before the ETD. 

Let's switch to a different automation profile. 

Click the Name dropdown button.

Click the Default list item.

Click the Use Profile button.

The "Default" Automation Profile used in this example has five Automation Actions, or Automation Events.

They perform a "Test Compute" three hours before the ETD, then a "Save Compute" five minutes later. With two hours before ETD there is a "Compute and Send". 15 minutes later the "Send Flight Package" action is performed. Finally, with one hour before ETD the "Send ATC" action is peformed.

It is possible to Add, Edit, and Delete actions using these buttons.

Let's add a new Automation Action to the default profile. 

Click the Add button.

Click the Sched. time input field.

Enter 00:45 into the Sched. time field.

Click the Action dropdown button.

Click the Send ACARS list item.

Click the Save button.

Click the Save button.

SUCCESS 

Congratulations! You have successfully modified the default automation profile.