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 CS@wheelsup.com 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

  • Enabled check box: allows customers to enable or disable the integration.

  • Username & Password: Unique key and secret provided by Pulsar. If invalid credentials are entered, an error occurs advising the user that they are incorrect.

Minimum and maximum thresholds for the fatigue scores are also set from the integration page to be used when checking a crew member's legality for conducting any trips they are assigned to.

Personnel Tab

The personnel tab contains all active personnel in your account. The drop down column pulls results back directly from the Pulsar API and lists any personnel that are in your Pulsar account.

If the crew member is already mapped then their name is removed from the drop down list

NOTE: If a personnel member mapping needs to be removed, select the NA option, it clears the mapping and adds the name back to the drop down menu again. When NA is selected, all data for that user is deleted in Pulsar.

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 as seen above 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

    • Related Articles

    • Integrations

      In this area of Global Settings, you are able to connect the ARGUS, Avinode, FlightSafety International , ForeFlight, Pulsar Fatigue Meter, QuickBooks online, and Wyvern Integrations. If you do not have one of these integrations available in your ...

    • Integrations: QuickBooks Online

      The version must be Plus. The integration does not support Essentials or Simple Start. Setup Checklist: Authenticate Provide applicable users access Map cash account, expense class, expense location, invoice class, invoice location and designate ...

    • ForeFlight Integration Setup

      The article covers the setup and settings for the Avianis<>ForeFlight integration. To learn more about the integration functionality please reference the ForeFlight Integration Feature article. ForeFlight Integration Requirements The ...

    • PNRGo Integration Setup & Functions

      PNRGo Integration PNRGo is a 3rd party service provider which facilitates legal communication between a carrier and national authorities. It supports business and charter operators to comply with PNR, API, eu-LISA and sanctions. Find more ...

    • Charter Flight Support Integration Setup & Features

      Charter Flight Support ("CFS") provides AOG recovery sourcing and financial support for charter flights; learn more on their website. CFS Integration Setup Take the following steps to setup the Charter Flight Support integration: Engage CFS. Avianis ...