Introduction
Event-Driven Automation
In this topic, we will review 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 handles event-based triggers as well.
The currently supported events include aircraft change, captain change, zero-fuel weight change, and ETD change.
Event-based triggers activate after the first successful computation of the flight,
whether done manually or through time-based automation.
Let's go through the process.
Click the Name input field.
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.
Click the Use Profile button.
Click the Add button.
For an Event, select the event that will trigger the automation. There are five options:
- Aircraft Changed
- Captain Changed
- ETD Changed
- ZFW Changed
- Weather Degraded.
Aircraft, and Captain change events have identical options, as displayed above.
ETD, and ZFW change events add the ability to change 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.
Weather Degraded option allows users to set an event based on when weather conditions exceed the thresholds set in the Weather Profile, under the Alert Profiles menu.
HINT
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.
Click the Flight Package has been sent radio button.
HINT
Select the option again to cycle through.
Click the Flight Package has been sent radio button.
Click the Action dropdown button.
HINT
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.
Click the Compute and Send list item.
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.
