Integrations
01. Fatigue Risk Management Platform integration
Fatigue poses a large risk to aviation safety and the capability within APM's crewing software to integrate with a Fatigue Risk Management platform offers many benefits to airlines. FRMSc’s FRMS Suite is a platform to identify fatigue scores of both cabin crew (CARE) and flight crew (SAFE), assisting your airline in safe crew management. The model is based on the popular fatigue scale — Samn-Perelli seven-point fatigue scale (SPS).
APM customers with a SAFE and CARE suite license are able to track the fatigue risks to their crew members with the integration of the FRMS Suite of predictive fatigue models with our crewing module; CrewLogic.
02. APM EFB Integration
The APM EFB integration service works with Aviobook Integration services to allow your airline to connect APM with Aviobook, an Electronic Flight Bag tool (EFB). This integration allows your flight dispatchers to save time as the following data is automatically transferred from Aviobook to APM, Flight Schedule including crew composition, Booked PAX figures including Special Service Request data (SSR), a Flight Report for crew members. Additionally, APM automatically communicates instantaneously any crew change or aircraft change done in CrewLogic or SmartOps. Finally, this integration also allows your airline to receive loadsheet information from Aviobook so that within APM such as PAX, payload and fuel to complete sector data will enhance analysis and reporting capability from the APM suite.
There are two Aviobook Integration Services, The first one is called the APM Aviobook Integration Service
The APM Aviobook Integration: service pushes the following information from APM to Aviobook:
- Flight Schedule: Daily export From D+2 to D+6 which is configurable.
- Flight Schedule: For the period from D to D+2, standard ASM messages are sent from APM SmartOps
- Crews assigned on each flight by APMs CrewLogic, including crew roles: Daily export for D+2 which is configurable.
- Crew change: Live data sending from D to D+2 which is configurable.
- Flight report: Two transmissions: at H-10 and H-2; plus a live sending if there is a crew or aircraft change on sector. This is configurable.
- PAX numbers as Expected and/or Booked pax figures: Number of Male Adults, Female Adults, Children, Infants. This data is sent at the same time as the daily flight schedule export
- SSR Data: Daily export at the same time as the Flight Schedule export
The second one is called the Aviobook Ingest: Service this service receives data from Aviobook to APM:
- PAX figures from the Aviobook Loadsheet (Total number, total adults, total children, total infants, total males, total females)
- Payload data from Loadsheet (PAX total weight, Holds distribution, Holds total weight, Loadsheet take-off weight, Loadsheet zero fuel weight)
- Fuel data from Loadsheet (Block fuel, Extra Fuel, Extra Reason, Taxi Fuel, Take Off Fuel, Trip Fuel, Landing Fuel)
03. AMOS integration
APM integrates with the MRO system, AMOS, to ensure your Schedule is updated with any planned maintenance to your aircraft. APM is able to ingest CSV files from AMOS to automatically update the graphical display and insert planned maintenance from the MRO system. This provides users with the reason for maintenance and links it to the aircraft registration. APM also offers an ‘apmAmosSectorExtract’ to import sector information from APM into the AMOS software.
04. APM’s Partner Integration Service (Code Shares and Inventory Systems)
With APM’s Partner Integration Services, airlines using SchedulePlanner can:
- Ingest SSIMs, SSMs and ASMs from partner airlines
- View all marketing flights on a separate schedule Graphical Display and filter by airline if required
- Send necessary messages either Sita or Type B about partner flights to 3rd party systems including Amadeus, airports and handling systems to show codeshare details
- Set specific date ranges for the agreed operational period
- Manage incoming DEI 50s and DEI 10s, and translate outgoing messages to show the operating and marketing airlines
- Ingest MVTs and MVAs regarding partner flights for delays, cancellations and other movement changes.
- View all connections based on your airlines and partners flights on a live map
05. Lido integration API
APM have an integration API exchange with the LIDO flight planning system which is available as an option.
- The development based on IBM MQSeries
- The development based on LIDO API
- The development based on APM V7 and later
The messages available from APM to Lido are:
ASMs for Lido flight planning tool (messages are sent for the next 2 days before operations departure date, but this can be parameterized). The ASM messages are generated and sent automatically without any user intervention.
WAB (Weight and Balance Payload Message) for each sector the message records either the expected or booked passenger numbers by gender, class; and adult, children, infant and then uses an APM weight dictionary to compute weights. Additionally for each sector the freight is entered into the flight sector information window.
The sum of the freight and passenger (possibly including crew members) weight values based on the weight dictionary calculates the total of the payload to transmit in the WAB message to Lido.
WOB (Payload Message): for each commercial segment the message records either the expected or booked passenger numbers by gender, class; and adult, children, infant on commercial segment and then uses an APM weight dictionary to compute weights. Additionally for each commercial segment the freight is entered into the flight sector information window.
The sum of the freight and passenger weight values based on the weight dictionary calculates the total of the payload to transmit in the WOB message to Lido.
CMS message: (Crew data message based on crew information from CrewLogic for crew briefing giving Pilot in Command name, crew code, other crew roles and names plus duty position flight no,date). APM users must be using CrewLogic for this message to include appropriate details. The CMS messages are generated and sent automatically without any user intervention.
FUP: Fuel Price Message (taken from the financial tables in APM Financial systems, by airport fuel price, valid from date valid to). The FUP messages are generated and sent automatically without any user intervention.
MVT/MVA messages: Sent for actual time updates. The MVT/MVA messages are generated and sent automatically without any user intervention.
Posting Message: To MQSeries for various docs from APM to LIDO, for example, GenDec can be sent from the APM system to Lido for flight briefing.
Message from LIDO to APM: APM collect these messages from the MQSeries Lido API with a service scan.
WABi: this message includes ETE, planned trip fuel, estimated block fuel. We use this message in APM to update actual times based on the departure time of the sector, total fuel and planned trip fuel.
Lido Flight Plan Briefing Package: This is available from Lido subject to specification and additional cost.
File Handling & Data Exchange
01. APM Passenger File transformer service
The APM Transformer Service picks up a file in a non-XML format – supplied by a third-party system – from a folder, and transforms them into XML file message structure that is compliant with an APM XML schema.
Specific versions of this transformation service can be developed to deal with particular file formats.
02. APM passenger file ingest service
The APM PAX File ingest Service picks up the transformed files generated by the transformer and ingests the PAX figures into the APM database commercial segments.
03. Crew FRMS Roster File Export
The APM FRMS Roster File Export is a module which generates upon a User request an excel file that can be sent to the ‘FRMS’ system who will calculate the Fatigue Management score in their system, normally before a roster is published. With this process the Fatigue Management score is not indicated within the APM system, the Fatigue Management score is indicated in the FRMS system and therefore using this analysis, the User must make amendments as necessary to the CrewLogic Roster and re-export the file to FRMS to ensure the results comply with Fatigue Management limitations. With this export, compliance to Fatigue Management limitations is the responsibility of the User and the FRMS system. This Export module by APM is a separate executable the User must rent from APM, called ‘FRMS’ Roster Export.
04. Aerobytes File Extract (APM V7 and later)
The Aerobytes File Export is an extract report that can be produced in a CSV file that can be either manually or automatically uploaded into the Aerobytes system in order for Aerobytes to align the data with the flights actually flown and to establish who flew the particular flight. The end user report for the airline is produced by Aerobytes.
For further details refer to the Aerobytes website, www.aerobytes.co.uk
05. The APM File Export Service
The APM file Export Service is an application that enables the User to, Export a CSV file or Standard and Closed Accruals, Export a CSV file of the APM Generic Stats Report Automatically Export GenDecs to a designated address such as a Crew Room or Captain’s email address
Message Processing & IATA Messages
01. APM IATA message decoder
The APM IATA Message Decoder allows the system to receive and transmit specified IATA-compliant Type B messages, plus some ACARS, ARINC and AFIRS messages.
The following is a list of some messages that APM can process, others can be added as required by Customers.
Schedule messages:
- ASM Incoming ASMs are stored in the APM database but do not update the flight program without configuration
- ASM Outgoing ASM’s are generated on demand from SmartOps -NEW, TIM, CON, FLT, CNL, RIN, EQT, RPL (these can also be automatically generated and transmitted through the ASM Export Service).
- SSM Outgoing SSM’s are generated and sent on demand
- SSIM Outgoing SSIMs are generated on demand
Operations messages:
- DIV Outgoing DIV messages are generated on demand
- MVA Incoming MVA messages (ACARS messages converted into MVT equivalent messages) are ingested and automatically update flight sector data
- MVT Outgoing MVT messages are automatically generated on demand
- MVT Incoming MVT messages are ingested and automatically update flight sector data
- MVT SI FOB messages are ingested and automatically update flight sector data
- In addition, APM can ingest some Acars messages if they are converted into XML messages (APM can supply a XML schema for this purpose)
- ACARS A80 Flight Summary Message
- ACARS Aircraft Doors opening and closing messages are ingested and automatically update flight sector data
- RQM Outgoing RQM messages are generated on demand
- AAS Outgoing AAS messages are generated on demand
- ADM Outgoing ADM Aircraft Deployment messages are generated on demand
- ASD Outgoing ASD Aircraft switch and delay message
- FMM Fuel Monitoring Message. Incoming messages are ingested
- Sub charter notification
- FOB Fuel on Board Messages
Slots messages:
- SCR Incoming messages are ingested and update slot data
- SAL Incoming messages are ingested and update slot data
- SCR Outgoing messages are generated on demand
- SHL Incoming messages are ingested and update slot data
- SIR Incoming messages are ingested and update slot data
- SMA Outgoing messages are generated on demand
- SAQ Outgoing messages are generated on demand
Air Traffic Control Messages:
- CFMU Incoming ACK messages are ingested
- CFMU Outgoing CNL messages are generated on demand
- CFMU Incoming DES messages are ingested and update flight data
- CFMU Outgoing DLA messages are generated on demand
- CFMU Outgoing FCM messages are generated on demand
- CFMU Incoming FLS messages are ingested and update flight data
- CFMU Incoming FPL messages are ingested
- CFMU Incoming MAN messages are ingested
- CFMU Incoming REJ messages are ingested
- CFMU Outgoing RFI messages are generated on demand
- CFMU Outgoing RQP messages are generated on demand
- CFMU Incoming SAM messages are ingested and update flight data
- CFMU Incoming SIP messages are ingested and update flight data
- CFMU Incoming SLC messages are ingested and update flight data
- CFMU Outgoing SPA messages are generated on demand
- CFMU Outgoing SRJ messages are generated on demand
- CFMU Incoming SRM messages are ingested and update flight data
- CFMU Outgoing SWM messages are generated on demand
Crew messages:
- APIS Outgoing UK, Bulgaria, Brazil, Canada, Cuba, Denmark, France, Ireland, Jordan, Lebanon, Moldova, Norway, Russia, Saudi Arabia, South Africa, United States and China Flight Crew Manifest are generated on demand by a service. Other ICAO APIS standard messages can be configured on demand.
- SMS to crew members
- GenDec General Declaration
- FCM Flight Crew Manifest
Payload Control:
- CPM Cargo Ingest. Incoming messages are ingested.
- LDM Incoming LDM messages are ingested and update pax data
- SLS Incoming incl Actual Pax F,C,Y, GG (free),B (Baggage),E (Palleted Frt), C (Loose Cargo), M (Mail)
02. APM Integration Message Processor
The APM Integration Message Processor is a service that generates MVT, ASM and SSM messages including NEW, CNL, RIN, TIM, CON, RPL, FLT and EQT messages from the APM system to a third party system for integration purposes.
The Integration Message Processor must be configured within the service itself with all recipient addresses for the third party system, not the addresses as normally set in SmartOps for MVT or ASM’s message transfer.
Once this is done the user needs to take no further action for the integration message recipients as configured within the service itself for the third party.
Users also set the integration period of the message transfer from the APM Integration Message Processor to the third party system. The messages will transmit automatically, unless users elect to use the APM Integration Survey utility, which enables the user to review and edit a message.
The integration message flow can only be transmitted to a defined folder on the customers network and the message can then be collected by a third party software from that folder.
03. FCM Generators for Flight Crew Manifest messages generation (APIS)
This is an automatic flight crew manifest message generator following which the message is sent to the appropriate authority.
04. Message Transport Service
This service lets you retrieve messages from a SITA inbox or an email box and insert them into the APM database. It also allows you to deposit IATA messages generated by the APM system in an out folder and send them via SITA or via email.
Automated Services
01. Crew Engine Service
This service performs all automatic background tasks related to CrewLogic (automatic check & save of rotations following a modification on a flight, automatic verification and repair of crew counters).
02. Crew Passed Qualification Events Update
This service automatically validates all crew re-qualification events for the recurrent check whose "Auto Ack Passed Events" column is checked as soon as the event passes.
03. SSIM import service
This is an interface which can import from a defined folder an SSIM Chapter 7 file, the import populates a schedule scenario with the flights and builds the flight rotations with airports defined in the APM database as schedule stops. It then assigns the rotations to aircraft registrations according to onward flight information (DEI6). The system will then assign the scenario to the Live production schedule.
04. The APM Ops Engine
This service runs all automated background tasks in SmartOps, including a draft Zero Fuel Weight calculation (to be validated by third-party systems).
APM REST API
01. APM REST API
APM has a REST API and publishes documentation for a wide range of real-time endpoints in JSON format, which third-party systems can integrate with. We continue to expand our endpoints to meet your specific needs.
