Integration: Pulsar Fatigue Meter

Integration: Pulsar Fatigue Meter

This article covers the following

  • What is Pulsar

  • How to configure the integration

  • How to use the integration

What is Pulsar

Pulsar is a software that analyzes crew fatigue levels and warns operators if they are scheduling crew that are too fatigued.

SETUP

This feature is behind a module. If you are a current customer of Pulsar and you would like to integrate with Avianis, please reach out to avianissupport@portside.co to learn more.

Prior to Avianis enabling the module be sure to provide the crew list including Last Name, First Name and Homebase at a minimum to Pulsar.

Once the module is enabled, the integration is available in My Company > Global Settings > Integrations > Pulsar Fatigue Meter. 

Settings Tab

On the settings page the following must be filled out in order to leverage the integration: 

  1. Pulsar Organization ID, API Key, and Webhook Key are all provided by the Pulsar team and will need to be added here. 
  2. As an organization, you will then set the warning and critical thresholds for the fatigue scores to be used when checking a crew member's legality for conducting any trips they are assigned to.
  3. Additionally, you will need to set which personnel event categories within Avianis will calculate to Pulsar events titled 'On With Rest'. 


Notes
If invalid credentials are entered, an error occurs advising the user that they are incorrect.

Personnel Tab

The personnel tab contains all active personnel in your account. The Employee ID column shows the unique identified for the user named within Pulsar. 

To create a user via the integration you will toggle the enable setting to Yes and click Update. 

If a personnel member needs to be removed, toggle the setting to No, click update and this will remove the user from Pulsar. 


Logging

The last tab within the settings page titled 'Logging' will show users all the data that flows between the two systems. 

USING THE INTEGRATION

After the personnel are mapped to Pulsar, then a sync pushes the following data for each crew member

  • Proposed duty time

  • Actual duty time

  • Flights as they are scheduled based on when the crew is assigned to an event

After a sync, please allow up to 40 seconds for the change to apply in Pulsar.

Pulsar contains several charts and graphs which display the crew member's duty time using an outlined bar and the bars are filled in with solid blocks when flights are scheduled.

If the duty time schedule is proposed duty time, it is replaced once the actual duty record is submitted. If a flight leg is cancelled in Avianis, it is removed from Pulsar.

These charts and graphs can be run for all crew members or you can view one crew member's data at a time like so:

As the data syncs from Avianis, Pulsar then calculates the crew member's Peak Duty Fatigue score. That value then flows back into Avianis for each flight leg that the designated crew member is assigned.

A flag displays in the trip feasibility and tools if a crew member has exceeded the designated thresholds set.

API Call Information

The following data points are included in the in the API call:

personID - this is the GUID that is mapped to the user

  • Bounds:

  • start - proposed duty start time UTC unless an actual duty record exists in that period, in which case it would use oue.StartDate

  • end - proposed duty end time UTC unless an actual duty record exists in that period, in which case it would use oue.EndDate
    duties

  • start - proposed duty start time UTC unless an actual duty record exists in that period, in which case it would use oue.StartDate

  • end - proposed duty end time UTC unless an actual duty record exists in that period, in which case it would use oue.EndDate

Flights - all flights that fall int he duty period above as an array

  • start - ISNULL(fl.ActualDepartureDateUTC,fl.ScheduledDepartureDateUTC)

  • end - ISNULL(fl.ActualArrivalDateUTC,fl.ScheduledArrivalDateUTC)

  • origin

    • ICAO

    • IATA

    • FAA

    • description

    • lat - location latitude (only used for locations)

    • long - location longitude (only used for locations)

  • destination

    • ICAO

    • IATA

    • FAA

    • description - airport Name

    • lat - location latitude (only used for locations)

    • long - location longitude (only used for locations)

  • crewRole - Crew position on the flight leg

  • crewCount

  • isPositioning

  • legNumber

  • tailNumber

  • aircraftType

UpdateType: A new FMS API exists to log results from the request call. The logs store the following data:

  • OrganizationID

  • SystemObjectID

  • SystemObjestRecordID

  • ModuleID

  • Request

  • Response

  • Completed = true