The application update includes the following features:
Operations
Minor/Lap Child Delineation
Ops Dashboard Arrived in Column Ordering
Leg Selection Behavior when Create New Contact in Trip
Change Control by Flight Leg Status
Default Aircraft Regulatory Set
Maintenance
Create Reposition from Job Card
Mismatch Airports on Offline Job Cards
ATA Codes on Discrepancies/Job Cards
Job Card Maintenance Facility
Inactive APU Log Display Update
CAMP Discrepancy Integration
CAMP Discrepancy Integration (ATA Code Updates)
Custom Maintenance Types and Color Customization
Personnel Events
Event Updates
Multi-Day Event Create
Crew Records
Acknowledge Flights on Behalf of Crew
Schedule Board
Removal of Multi-Day Flight Cards
Fleet Resource Templates
Transient Activity in Fixed & Duration View
Display Leg Colors by Trip Type
Order By Option: Event Types or Time
Fixed Width View Based on Airport Local
Moved 'Settings' into 'Filters'
Aircraft Last Known Location Display on Schedule Board
Additional Data on Flight Tooltips
Differentiate Airport and FBO Mismatches
Filtering Data
Scheduling Notes for Crew Resource and Personnel Event Template Option
Create Reposition in Zulu Time
Fit to Card Option
Create Reposition Auto Settings
Usability Improvements
API Updates
Job Card API Endpoints(22.2)
Contacts For Account API 22.4
Personnel Aircraft Assignment Endpoint
URL Redirect With GUID
Additional designations have been added to the contact record, Minor and Lap child. If the lap child designation is applied the feasibility check for passenger quantity excludes them.
The Arrived In column has been updated to display the most recent flight’s arrival at the top of the column rather than the bottom, as it previously did.
When the user attempts to create a new passenger within the trip passenger tab the “Assign to all legs” checkbox will default to "All Legs" as it does when adding an existing passenger to the trip.
A new configuration has been added to allow an operation to apply change control functionality to leg status rather than trip stage. When the account is configured for the leg status option we have expanded the functions to allow for crew communications (coming soon through mobile 3.0). An operation can set for each change control, if the crew is to be briefed only or if an acknowledgment is required.
If BRIEFING is set then the crew is alerted that there is a change to that the value changed (sends to mobile) but are not required to respond and does not impact the Acknowledge status
If ACKNOWLEDGE is set then the crew is required to respond to the change (acknowledge), if the user had acknowledged the flight previously then this resets and the user much acknowledge again after this data has changed
Crew Acknowledge Severity - When there is an outstanding acknowledgment for this flight in this leg status, it displays for feasibility with the provided severity. Critical = red and Warning = Yellow.
Note: To begin leveraging this feature, you will need to change the "Change Controls By" setting found within Operations > Settings > Configuration > Change Controls By. Once toggled to the desired option-click, save.
An update has been made to allow the user to set a default regulatory set by aircraft. This new field is located in the aircraft profile’s overview section and defaults to Empty. Once set, when a trip is created on the aircraft the trip and leg level regulatory set will automatically apply.
Related Article:
The Schedule Board allows a user to create a reposition from a flight event or a maintenance offline event when there is an airport mismatch. The user is able to right-click on the flight event or offline event to expand the available menu options where Create Reposition can be selected.
Note: If an event is hidden on the Schedule Board due to filters, and Create Reposition is selected on the right-click menu on top of the hidden event then the modal could launch using the details from the event card, or a message may display indicating a reposition is not required.
Maintenance offline events are now considered when the Schedule Board shows when there are mismatched airports between the maintenance event and flight legs. When a job card has been created with an offline event, if the airport does not match the previous or next airport (flight event or offline event) in the flight schedule then the flight event displays the mismatched airport red corners on the top right and/or left of the object indicating if the mismatch is for the previous event or the next.
Two new fields have been added to the Discrepancies and Job Cards called ATA Chapter and ATA Code. While neither field is required to save the Discrepancy or Job Card the ATA Code field will be disabled until an ATA Chapter has been entered. These chapters and codes are managed in the background and cannot be edited by the user.
Note: If the account uses the CAMP integration, then the ATA Chapter and ATA Code fields can be entered in CAMP and received from CAMP.
A new field is available on the Aircraft Out of Service form within a job card labeled “Maintenance Facility” that gives the user the option to select the facility the aircraft is having maintenance performed at. The list of available facilities is populated from FBOs and maintenance vendors associated with the airport selected in the form.
Updates have been made to how information is displayed when a flight log has times allocated to an inactive APU or time allocated to multiple APUs. If the user has an APU record that is marked inactive on the aircraft profile but was previously logged on a flight leg then the inactive APU displays under the Components section within a flight log along with the currently active component. Given the trip stage has the flight log enabled the data entry fields for all APUs are enabled allowing the user to add and/or adjust the hours/cycles if needed.
The Maintenance > Integrations page has been updated to show a log multiple times if times are allocated to multiple APU records within the logs table. When the aircraft is selected from the drop-down, if there are any flight logs with positive allocations made on multiple APU records, then an additional log row displays. Each of the duplicate logs is highlighted red allowing the user to quickly identify if there are any issues.
Note: This is only available in Logbook V2.
The integration has been updated to allow operations to set whether to pull discrepancies from CAMP into Avianis for greater visibility to Operations. Discrepancies continue to be managed in CAMP and the information updates accordingly in Avianis.
Users can now create custom Maintenance Types to correspond to aircraft offline events within the Job Card. These new types are located in the main navigation > Maintenance > Configuration > Offline Types. This allows for greater maintenance event reporting. The following fields are available (items with an asterisk are required).
Name (300 Character MAX) *
Maintenance Type (Scheduled, Unscheduled, or Both) *
Description (No Max Characters)
Active Checkbox
Once created these Offline Types can then be added to the Job Card > Aircraft Out of Service section after a Maintenance Type has been selected. An Offline Type is not required to save and can be removed by selecting N/A from the drop-down.
There is now the ability to customize the colors for maintenance cards that display on the Schedule Board within My Company > Profile > Schedule Board > Event Type Colors. When on the Schedule Board, the legend has also been updated to display the MX: Discrepancy, MX: Offline (No Type), and each active Offline Types.
Note: In addition to this new menu option the menu choice “Maintenance Types” has been updated to display as “Inspection Types”.
Related Articles:
The event modal has been updated for a more streamlined creation flow. When creating an event the required fields have changed depending on the selected "Event Type". If a required field has been omitted when creating the event an asterisk will appear next to the missing section.
Note: The Container field is no longer available when creating events within the Schedule Board.
Due to these changes some columns within Dashboard > My Schedule have been updated:
TRIP/SUBJECT has been updated to TRIP/CATEGORY and will display the Event Category outlined in the event
STATUS/CATEGORY has been updated to STATUS/SUBJECT and will display the Event Category outlined in the event
This update allows an operation to map event categories to event types for automation when creating events. Additionally, this update gives the ability to customize the colors by event category which drives the Schedule Board display.
Quickly create multiple events with just a few clicks. The default is a single occurrence, toggle to Multi and add days up to 16, whether consecutive or non-consecutive once saved each multi-day event is created. Once created these events stand independently from each other.
Note: Multi-day events can only be created within the Schedule Board.
Related Articles:
A configuration has been added to allow other personnel to acknowledge flights on behalf of the crew member. Acknowledgments are reflected in the Trip > Crew tab and the Schedule Board flight card.
The Schedule Board can be located directly underneath the Scheduling module from the main navigation here:
If you do not see the option for the Schedule Board within your account please contact your account manager or support via chat or email opsupport@avianis.com.
A new filter has been added to the Schedule Board > Filters > Templates called "Show Flights on Multiple Days". This new setting is only available on the Schedule Board when the user has Show Event Length By Fixed selected. After selecting Fixed from the templates a new field will be displayed called "Show Flights on Multiple Days".
When the user is in the Fixed or Duration view the transient information is displayed. The events are displayed in a gray low capacity and are layered behind the other Schedule Board events. The event will continue to display the airport identifier of the transient location, the date/time of the arrival, and the trip stage from the previous flight.
To include this filter the user would need to access Schedule Board > Filters > Templates > Aircraft.
Flight event colors can now be customized to display within the Schedule Board by Trip Type. These colors can be added within My Company > Profile > Schedule Board tab > Event Type Colors. When the customization is set then the flight card on the Schedule Board displays the assigned color on the first line of text in the flight card. The flight card’s background still uses color customizations for the flight leg status.
A new setting can be found within Schedule Board > Filters > Templates that can allow the user(s) to group the events within the Schedule Board by Time or Type.
When Type is selected, then the scheduled objects with the Schedule Board are stacked vertically, grouped by the event type, and then displayed in chronological order by the departure or start date/time in ascending order within each of the event type groups. The ordering of events when in this view cannot be edited as displayed in the following order:
Job Cards
Discrepancies
Flights
Events
Medical
Qualification
Note: When Time is selected the view will remain in chronological order regardless of event type as it currently does.
All event cards such as flights, personnel events, and maintenance events will display on the day based on airport local and will order based on start date/time.
Moved the setting options to the filter section so all setup and configuration are located in the same area.
Two filters have been added within the Aircraft Template resource within the Schedule Board templates:
The user now has the ability to add the aircraft home base to the aircraft card. Previously this was hard-coded and could not be edited by the user.
The filter for an aircraft "Current Location" has also been added within the Template > Filter options. This value is pulled from the arrival airport field on the first saved flight log prior to the current date/time (UTC).
An update has been made to the tooltip on the Schedule Board so that when the user hovers over the flight leg the Departure and Arrival airport information is displayed as either ICAO (City, State/Province, Country), IATA, or FAA code.
Updated the flight cards to differentiate corner triangles depending on an airport or FBO mismatch.
Red triangle = airport mismatch
Red triangle with white fill = FBO mismatch
The quick search previously located on the Schedule Board has undergone restructuring. A new “Filter” button has replaced the previous button and allows the user to search for specific resources in each timeline view simultaneously and also includes a new option to search for aircraft that are within a set number of NM (nautical miles) of the designated airport.
Note: To find data located within the Schedule Board you can also leverage the CTRL+F function.
Quickly add Scheduling Notes to crew profiles from the Schedule Board. Users with the user role 'Scheduling Manager' are able to add/edit Scheduling Notes.
Add Scheduling Notes to the Personnel Event template option to view on the Schedule Board.
When creating a reposition from the Schedule Board Zulu is now an option. Toggle quickly to Zulu or if 'Display Events In' is set to Zulu, then when creating repositions Zulu will default
Set 'Fit to Card' to yes to have the trip information text fit to the flight card (this is the default). Often times users want to see a large spectrum of time so flight cards get condensed. Set the 'Fit to Card' option to No, so the flight card text overflows the flight card.
Related Articles:
The v2 API endpoint to GET all contacts has been updated to allow the user to pull all contacts that are associated with a specific account.
A new GET endpoint has been created to pull the personnel directly assigned to an aircraft has been added to the v2 API.
A new GET endpoint, GET/connect/v2/Aircraft/{id}/personnel, to pull the personnel that are directly assigned to an aircraft has been added to the v2 API. The results include the following data: PersonnelID (the GUID of the Personnel member) and Position. The call for this API is and uses only the parameter Aircraft GUID ID. It is important to note that the Position can be NULL if the personnel that is assigned does not have a position selected within the aircraft assignment on the personnel profile.
Updates have been made to the Account, Contact, and Deal detail pages so they will load if the ID or GUID is passed into the URL.