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

Event-Driven Automation


Event-Driven Automation 

Event-Driven Automation 

We estimate that this will take 3 minutes to complete.

Detailed Explanation 

Event-Driven Automation 

Building on N-Flight Planning’s time-based automation, the application now also handles event-based triggers.
The currently supported events are aircraft change, captain change, zero-fuel weight change, and ETD change.
Event-based triggers become active after the first successful compute of the flight,
whether manual or through time-based automation.

 Let's go through the process. 

Interaction 1 Click the Name input field.

Interaction 2 Enter NAVBLUE into the Name field.

In this example, we will use NAVBLUE as an automation name. You can use a name that suits your particular automation.

Interaction 1 Click the Use Profile button.

Interaction 1 Click the Add button.

Use this Add option for Event Triggered Automations. 

For an Event, select the event that will trigger the automation. There are four options:

  • Aircraft Changed
  • Captain Changed
  • ETD Changed
  • ZFW Changed.


Aircraft and Captain change events have identical options, as displayed above.


ETD and ZFW change events add the ability to change the their values by time and weight respectively. For each of these, you can select the value change based on a qualifier, and the condition since the last instance of the event. 

Interaction 1 Click the Flight Package has been sent radio button.


The Conditions radio buttons have three settings:

- a check indicates a true condition,
- an X indicates a false condition,
- blank indicates an ignored condition.

 Cycle through these options by clicking the appropriate radio button as often as needed.

Interaction 1 Click the Flight Package has been sent radio button.


Select the option again to cycle through. 

Interaction 1 Click the Action dropdown button.


By crossing out Flight Package has been sent, you indicate that this automation only applies to aircraft changes wherein a flight package has not been sent. In this example, the system ignores whether or not the ACARS or ATC are sent. 

Interaction 1 Click the Compute and Send list item.

Interaction 1 Click the Save button.

In the event of an aircraft change, this automation recomputes and sends the new flight computation, provided the initial flight plan package has not been sent.

Clicking Save saves the automation event to the Automation Events list; clicking Cancel closes the Add Automation Event dialog without saving the information entered. 

The newly-created Event Triggered Automation displays in this window. 


Did you find it helpful? Yes No

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