CS-FL-00-0102 FlightLink Services Operator Onboarding - Rev5 - AVN - Rev1

FlightLink Services Operator Onboarding
Operator course CS-FL-00-0102

Revision 5
April 2020
Agenda
 Chapter 1: introduction
 Chapter 2: onboarding process
 Chapter 3: hardware and software requirements
 Chapter 4: schedule
2 Revision 6, April 2020 FlightLink Administration

Introduction
Chapter 1

Introduction
• In this section:
– Meeting objective
– FlightLink services
– FlightLink infrastructure

Introduction
Meeting objective
At the end of this information session, you will be able to compile all information required to
setup the FlightLink Services for your A220 aircraft
5 Revision 5, April 2020 FlightLink Services Operator Onboarding

Introduction
FlightLink services
Baseline Subscription-based
Health Field Loadable Aircraft Data Real-Time Analytics

Management Unit Software Management Monitoring (under development)
(HMU) (FLS) (DM) (RTM)
• Data Recording • Manage LSAP & FLS • Secured ground wireless • Get active faults • Analyze aircraft and
• Transmission to ground transmission transmitted by ACARS® fleet data
• Manage, store, deliver • Integrated troubleshooting • Provide basic or
aircraft data • Track aircraft flying advanced services

Introduction
FlightLink infrastructure
FlightLink
AIRCOM Operator
Database Web Portal
Server File End Users
Processing &
Distribution
Solution
File Receiver Operator IT
Infrastructure
FlightLink Provides Turn-Key Solution with Minimal Operator Infrastructure

Revision 5, April 2020 FlightLink Services Operator Onboarding
7
Onboarding Process
Chapter 2

Onboarding Process
– Operator’s inputs
– Focal points
– Access control
– Ground connectivity
– Business-to-business connection
– Data delivery settings
– Data retention requirements
– ACARS settings

Onboarding Process
Overview
• The FlightLink operator onboarding steps are summarized as follows:
Information Admin Operator’s System

Startup Kit Training
Session Training Inputs Setup
• Details of the FlightLink onboarding are documented in the

FlightLink Onboarding Guide, available on the A220 portal

Onboarding Process
Operator’s Inputs
• The following operator information is required:
– Contact focal points
– Users information
– Cellular/Wi-Fi information
– Business-to-business (B2B) connection information
– Data delivery requirements
– Data retention requirements
– ACARS® information
• Customer shall formalize these customer inputs and requirements in the FlightLink Onboarding Form

Onboarding Process
Contact focal points
• Main FlightLink focal • Main IT/ACARS focal
– Coordinate operator activities – Set-up the B2B connection
– Gather required information – Manage IT infrastructure
– Define and track schedule – Manage Wi-Fi/cellular aspects
– Report issues to Airbus Canada – Set-up ACARS routing
– Appoint staff to be trained
• Data Management Administrator

• FlightLink Delegated Administrator – Approve data delivery requests
– Manage operator’s users access – Control HMU configuration
– Assign FlightLink roles to users – Manage aircraft to HMU assignation
• Client Administrator • Real-Time Monitoring Administrator

– Approve operator’s users Universal Registration (P&W) – Assign aircraft/subfleets to operator’s users
– Manage operator’s exclusion rules
Operator to provide contact information for main focal points

Onboarding Process
FlightLink infrastructure
FlightLink
d AIRCOM a Operator
Database Web Portal
Server File End Users
Processing &
Distribution
b Solution c
File Receiver Operator IT
Infrastructure
FlightLink Provides Turn-Key Solution with Minimal Operator Infrastructure

Revision 5, April 2020 FlightLink Services Operator Onboarding
13
Onboarding Process
Summary of Infrastructure Requirements
BASELINE SERVICES
Infrastructure FLS/LSAP HMU Configuration Data Management Real-Time Monitoring
Internet access and LSAP and FLS download from Access via iflybombardier.com Access via iflybombardier.com Access via iflybombardier.com
a certified web browser iflybombardier.com portal portal portal portal
Wi-Fi and/or Cellular Data Not applicable Not applicable Data plan Not applicable
b Service Provider SIM Card as required(2)
Business-to-Business AS2 for automated LSAP Not applicable AS2 or SFTP for automated Not applicable
c Connection delivery (optional) data delivery
AS2 for wireless FLS upload(1)
Storage Space As required, for storage of As required, for storage of raw Storage of converted data files Not applicable
c LSAP and FLS and converted data files
ACARS Data Service Not applicable Optional, for reception of Optional, for reception of Data Service Provider and
d Provider ACARS data files ACARS data files AIRCOM server
1. Availability date to be confirmed; applies to Data Management Tier 1 and Tier 2 customers
2. Applies to Data Management Tier 0 and Tier 1 customers, with the Cellular Ground Connectivity option installed

Onboarding Process
a. Access control
• Operator must appoint a FlightLink Delegated Administrator and a Client Administrator who will manage
accesses for all the operator’s end users
• The following components have their own registration processes running in parallel:
1. A220 customer portal: FlightLink Delegated Administrator assigns FlightLink roles to operator’s user and manages
accesses to all FlightLink services, including LSAP
2. “Universal Registration”: Client Administrator validates users registration to eFAST™ (Data Management and HMU
configuration functionality); users must submit their Universal Registration to Pratt & Whitney
• The same person may have both FlightLink Delegated Administrator and P&W Client Admin roles (recommended, but not required)
A220 Portal
all FlightLink
eFAST™ roles Services roles
Operator to provide contact information for Delegated Admin & Client Admin
Onboarding Process
a. Web browsers
• Below is the list of browsers that are currently supported for FlightLink web applications
Browser Version Supported
Google™ Chrome™ 49 to 74 
Mozilla® Firefox® 44 to 66 
Microsoft® 10 
Internet Explorer® 11 

Onboarding Process
b. Ground connectivity
• As a prerequisite to the Data Management service, the aircraft must be fitted with at least one of the following
ground connectivity options:
– C23230001 Connectivity, FlightLink, External Wireless LAN
– C23230011 Connectivity, FlightLink, Cellular (3G)
• The operator must subscribe to a data plan with the data service provider(s) of their choice in order for the aircraft to transfer data
via Wi-Fi and/or cellular*
Operator to contract cellular/Wi-Fi data service provider(s)

* A cellular data plan and SIM cards are provided by Airbus Canada for Tier 2 Data
17 Revision 5, April 2020 FlightLink Services Operator Onboarding Management service customers
Onboarding Process
b. Ground connectivity: Wi-Fi infrastructure
• Wireless access points requirements:
– WPA2 authentication
– IEEE 802.11 b/g standard
– Public SSID (not hidden)
Settings at Mirabel Operator’s Settings
Access point make and model Aruba AP 134
Access point antenna type External, directional
Allowed bands g (2.4-2.5 GHz)
Channels 1, 6, 11
Max transmission power (Tx EIRP) 15 dB
Min transmission power (Tx EIRP) 9 dB
Basic data rates 12 Mbps
Transmit data rates 12, 18, 24, 36, 48, 54 Mbps
RSSI threshold None
Station handoff assist None
Dynamic channel assignment Enabled
Operator to share details of planned Wi-Fi infrastructure

Onboarding Process
b. Ground connectivity: Wi-Fi settings
• The following table illustrates the Wi-Fi information the operator needs to provide to Airbus Canada for the initial setup
Parameter Value
Name* myWiFi
Password 123
SSID* operatorwifi-wpa2
Security Key* UY/xLVhE7tCbctaUyIS7
Airport (IATA) ABC Albacete
* mandatory fields
• The Operator remains in full control of these settings in service

• Up to 100 Wi-Fi networks may be defined
Operator to compile Wi-Fi settings

Onboarding Process
b. Ground connectivity: cellular settings
• The following table illustrates the cellular information the operator needs to provide to Airbus Canada for the initial setup
Parameter Value
Name* mySIM
APN* gprs.gsmdsp.com
User abc
Password 123
Country Abcdef
High Cost Offload* (roaming) Yes/No
* mandatory fields
• The Operator remains in full control of these settings in service

• Certified carriers:
– AT&T and VODAFONE are certified carriers; Rogers has been successfully tested in Canada
– Some FlightLink customers are successfully using non-certified carriers
• The operator must purchase and install a SIM card in the aircraft post-delivery**:
– SIM card physical size: “mini” (also called “standard”) 25x15mm
– the aircraft will be broadcasting in the 850, 900, 1800, 1900 and 2100 MHz bands, using 3G technology
Operator to compile cellular settings

20 Revision 5, April 2020 FlightLink Services Operator Onboarding ** A cellular data plan and SIM cards are provided by Airbus Canada for Tier 2 Data
Management service customers
Onboarding Process
c. Business-to-business connection
• A business-to-business connection is required to support the following features:
– Automatic delivery of Data Management data files to the operator’s IT infrastructure
– Optional automatic delivery of LSAP to the operator’s IT infrastructure
• Supported protocols:
Functionality SFTP AS2
Automatic delivery of Data Management data files  

Optional automatic delivery of LSAP  
• Operators are free to select the SFTP/AS2 products they wish as long as they demonstrate reliability and compatibility when
interacting or interfacing with the certified products deployed at CSALP (IBM® DataPower® Gateway); compliance to this
requirement may be demonstrated via trial runs of use cases to be mutually agreed

Onboarding Process
c. Business-to-business connection: AS2
• Drummond group® provides a list of products that are certified for the AS2 protocol
• Non-certified products such as Ipswitch MOVEit™ and mendelson AS2 have been proven to be reliable and protocol abiding to a
level acceptable to Airbus Canada
• Airbus Canada’s partners (operators and suppliers) are free to select the AS2 product they wish as long as it demonstrates
reliability and compatibility when interacting or interfacing with the AS2 certified product deployed at Airbus Canada (IBM®
DataPower® Gateway); compliance to this requirement may be demonstrated via trial runs of some use cases to be defined
Operator to select AS2 solution

Onboarding Process
c. Business-to-business connection: AS2
• The following table shows an example of the AS2 settings needed in order to setup the AS2 B2B connection for the delivery of
FlightLink reports and LSAP (as applicable)
• The AS2 connection requires both parties to exchange certificates
• Airbus Canada’s IT specialists will guide the Operator through this process
Operator Airbus Canada
AS2 Identifier CI XXBAEPROGAS2CI01 / XXBALSAPAS2CI01 CI BAXXEPROGAS2CI01 / BAXXLSAPAS2CI01
PRD XXBAEPROGAS2PRD01 / XXBALSAPAS2PRD01 PRD BAXXEPROGAS2PRD01 / BAXXLSAPAS2PRD01
AS2 Address (URL) CI https://as2test.myairline.com/as2receiver.aspx
N/A (outgoing traffic only)
PRD https://as2.myairline.com/as2receiver.aspx
Connection IP Address Domains and IP addresses from which Operator will receive files:
CI https://as2test.myairline.com 123.456.789.10 CI ci.b2bgw.aero.bombardier.com 207.253.40.23, 207.253.40.97
PRD https://as2.myairline.com 123.456.789.1 PRD b2bgw.aero.bombardier.com 207.253.40.23, 207.253.40.97
AS2 Port HTTPS: 443 or other TBD HTTPS: 443
AS2 Software & Version TBD IBM DataPower XB62 V7
Encryption / Signing 3DES / SHA-256 3DES / SHA-256
Connection timeout 300 seconds 300 seconds
Compression None None
MDN Message Required N/A (incoming traffic only) Synchronous or asynchronous, signed
MDN Response Synchronous or asynchronous TBD, signed N/A (outgoing traffic only)
MDN Receiver IP Address (required for async MDN) N/A (incoming traffic only) CI ci.b2bgw.aero.bombardier.com 207.253.40.23, 207.253.40.97
PRD b2bgw.aero.bombardier.com 207.253.40.23, 207.253.40.97
AS2 Certificates To be exchanged To be exchanged
HTTPS Certificate TBD Obtained from URL
Operator to compile AS2 settings

Onboarding Process
c. Business-to-business connection: SFTP
• The following table shows an example of the SFTP settings needed in order to setup the SFTP B2B connection for the delivery of
FlightLink reports
• The SFTP connection authentication shall be based on usernames and public certificates (or passwords alternatively)
• Airbus Canada’s IT specialists will guide the Operator through this process
Operator Airbus Canada
Connection IP Address IP addresses from which Operator will receive files:
CI 123.456.789.10 CI 207.253.40.23, 207.253.40.97
PRD 123.456.789.1 PRD 207.253.40.23, 207.253.40.97
SFTP Port 22 22
SFTP Software & Version TBD IBM DataPower XB62 V7
SFTP Certificate / Public Key To be exchanged To be exchanged
Operator to compile SFTP settings

Onboarding Process
c. Data storage
• An appropriate storage space is required to support the Operator IT
following:
– Storage of Data Management data files
FlightLink Infrastructure
– Storage of LSAP and FLS
File B2B
Processing & c
• Storage capacity for Data Management data files must be sized Receiver
to accommodate the amount of data expected to be delivered Distribution
from the operator’s A220 fleet, which is variable and depends on Solution
the operator’s data delivery rules and fleet usage; tailored
assessments may be provided upon request
– ROM: 3 to 5 times the size of the data plan, e.g. 15 to 25
GB/aircraft/month for a 5GB data plan
Operator to plan for data storage

Onboarding Process
c. Data routing
• The operator may implement routing rules to end users as required by its operational needs
– All data files are delivered via the business-to-business connection to a single location (“B2B receiver”)
– Routing rules may be based on filenames; file naming convention may be provided upon request
Operator IT Infrastructure
FlightLink
FOQA Operator
File B2B
End User #1
Processing & c Receiver
Distribution
Powerplant Operator
Solution End User #2
Operator to plan for data routing

Onboarding Process
c. Data delivery settings (1/2)
• Airbus Canada will set-up the initial data delivery settings based on a default predefined configuration; the Operator then has the
opportunity to customize the following:
– Output types
ARINC 767 / ASCII Printer

Report Type CSV Other
XML (ARINC 620) (PTR)
ACMF    
ADRF   (1) (1)
AFF, HLEIF, UBMF, VDAR, VFDR, VQAR   ARINC 717(2)
ACMF: Aircraft Condition Monitoring Function UBMF: Usage-Base Monitoring Function
ADRF: Aircraft Data Recording Function VDAR: Virtual Direct Access Recorder
AFF: Aircraft Full Flight, also designated as Engine Diagnostics, Prognostics and VFDR: Virtual Flight Data Recorder
Health Monitoring (DPHM) VQAR: Virtual Quick Access Recorder
HLEIF: High Load Event Indication Function
– Build options(3): Fill/Gaps, De-identification
Operator may specify custom data delivery requirements

(1) ADRF SnapShot reports only
27 Revision 5, April 2020 (1) FlightLink Services Operator Onboarding (2) VFDR only
(3) Data de-identification is available to Tier 1 and Tier 2 Data Management service customers
Onboarding Process
c. Data delivery settings (2/2)
• Airbus Canada will set-up the initial data delivery settings based on a default predefined configuration; the Operator then has the
opportunity to customize the following:
– Delivery location:
– Data files may be sent:
– to the operator’s IT infrastructure via a business-to-business (B2B) connection
– to the Real-Time Monitoring “HMU Reports” page*
– by email: limited to operator’s registered users (file size restrictions may apply)
Conversion and delivery rules will be applied to the specified reports
– Notifications: users may be automatically notified upon delivery of every data file:
– via the A220 customer portal
– by email
Operator may specify custom data delivery requirements

28 Revision 5, April 2020 FlightLink Services Operator Onboarding * Requires a subscription to the Real-Time Monitoring service
Onboarding Process
c. Data retention requirements
Operator is requested to specify data retention period requirements, which will apply to all Data Management reports:
• Raw data active retention: 3 months (Tier 0)
6 months (Tier 1) OR None(1)
2 years (Tier 2)
• Raw data archive(2): 2 years (Tier 0)
3 years (Tier 1) OR None
5 years (Tier 2)
• Converted data: 30 days OR None(1) (not shared)
120 days (shared)
• Notes:
– Raw data is archived at the end of the active retention period, then deleted at the end of the archive period
– Converted data not “Shared with Airframer” is deleted by Airbus Canada after the selected retention period
– Converted data tagged as “Shared with Airframer” is archived by Airbus Canada after 120 days
– Data archived by Airbus Canada may be retained for the life of the aircraft; some data is intended to support life extension and
inspection interval extension programs (usage based lifing)
– Data files delivered to the Real-Time Monitoring service will remain available to the operator for 2 years before being deleted
Operator to specify data retention requirements

(1) Up to 24 hours
29 Revision 5, April 2020 FlightLink Services Operator Onboarding (2) Archive period starts at the end of the active retention period
Onboarding Process
d. ACARS providers and routing schemes
• List of ACARS provider(s)
• Preferred scheme(s) for downlink and uplink messages:
#1 #2
Airbus Airbus
Canada Canada
Operator to confirm ACARS provider(s) and routing scheme

Onboarding Process
d. ACARS message formats
• The following messages must be routed to/from Airbus Canada’s AIRCOM server:
– CFD SMI:
– CAS and INFO
– Fault
– Flight milestones, including ETA: Out, Off, On, In
– Optional:
– HMU reports and uplink commands (TT7/TT8)
• Operator to whitelist Airbus Canada’s AIRCOM server type B address for uplinks
• Operator to share their AOC definition if customized
Operator to share customized AOC definition

Hardware & Software Requirements
Chapter 3

– Hardware
– Software, LSAP
– Software, Data Management

Hardware
• Hardware required to perform LSAP and HMU-related activities are specified in the A220
Airplane Maintenance Publication (AMP)
• LSAP:
– commercial off-the-shelf USB memory device
– optionally: commercial off-the-shelf laptop computer
• HMU-related activities (e.g. manual data download, manual HMU configuration)

– commercial off-the-shelf laptop computer
– optionally: commercial off-the-shelf USB memory device

Software, LSAP
• The A220 Aircraft Network Security Publication (ANSP) recommends that the operator run a
Public Key Infrastructure (PKI) validation on the LSAP before their installation on the aircraft
• The A220 LSAP standalone PKI validator tool is available for download via the
following link (Windows, 32-bit or 64-bit): https://pubextpki.aero.bombardier.com/validatortool/
• A user guide is available on the A220 portal: FlightLink > Documentation > Field Loadable
Software Documentation > Guides
• No other specific software is required to handle A220 LSAP

Software, Data Management
• Data files may be delivered to the operator in formats that require specific software to be
interpreted, in particular:
– ARINC 767 / XML also known as FRED (A647A): most flight data management/analysis
companies offer solutions that are able to ingest this format; Airbus Canada has experience
interfacing with:
– GE Aviation (previously Austin Digital) Event Measurement System (EMS)
– Aerobytes FDM
– Safran Cassiopee FDM
– ARINC 717: VFDR files delivered in this format may be read using an FDR-compatible data
reader such as ROSE
• Other output formats such as CSV, XML, TXT may be ingested by typical spreadsheet and text
applications
• Operators are solely responsible to acquire data interpretation solutions to fit their needs

Schedule
Chapter 4

Schedule
– Onboarding timeline
– Training scope

Schedule
Onboarding timeline
Activity Weeks before Entry Into Service
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Contract signed
Start-up kit
Information session
Operator compiles information

Operator users registration
B2B connection setup
FlightLink services configuration

FlightLink services Go Live
LSAP service Go Live

Preliminary LSAP assigned
Final LSAP assigned
Admin training
Training

Schedule
Training scope
• Training will be provided to the operator as follows:
Topic Applicable Service Type Duration
FlightLink Administration WebEx 2 hours
A220 LSAP Classroom or WebEx 2.5 hours
Introduction to FlightLink Data Management Classroom 4 hours
Data Management and HMU configuration Classroom 8 hours
Real-Time Monitoring Classroom 6 hours
• Classroom courses are planned to be delivered in Mirabel or at the operator’s facilities

Thank you
© Airbus Canada Limited Partnership. All rights reserved. Confidential and proprietary document. This document and all information contained herein is the sole property of Airbus
Canada Limited Partnership. No intellectual property rights are granted by the delivery of this document or the disclosure of its content. No part of this document shall be reproduced or
disclosed in any manner to a third party without the express written consent of Airbus Canada Limited Partnership. This document and its content shall not be used for any purpose other
than that for which it is supplied and any statement made herein do not constitute an offer. AIRBUS, AIRBUS logo and A220 are trademarks or registered trademarks of Airbus SAS.
ACRONYMS
ACARS: Aircraft Communications Addressing and Reporting LSAP: Loadable Software Aircraft Part
System MDN: Message Delivery Notification
AOC: Airline Operational Communication MOQA: Maintenance Operations Quality Assurance
APN: Access Point Name OMS: Onboard Maintenance System
ARINC: Aeronautical Radio INCorporated PKI: Public Key Infrastructure
AS2: Applicability Statement 2 RTM: Real-Time Monitoring
ASCII: American Standard Code for Information Interchange SFTP: Secure File Transfer Protocol
B2B: Business-to-Business SHA: Secure Hashing Algorithm
CAS: Crew Alerting System SMI: Standard Message Identifier
CSV: Coma Separated Values SSID: Service Set IDentifier
FLS: Field Loadable Software TBC: To Be Confirmed
FOQA: Flight Operations Quality Assurance UBM(F): Usage-Base Monitoring (Function)
FRED: Flight Recorder Electronic Documentation URL: Universal Resource Locator
GSM: Global System for Mobile communications USB: Universal Serial Bus
HMU: Health Management Unit VHF: Very High Frequency
IATA: International Air Transport Association Wi-Fi: Wireless Fidelity
IMS: Information Management System WPA: Wi-Fi Protected Access
IT: Information Technologies XML: Extensible Markup Language

CS-FL-00-0102 FlightLink Services Operator Onboarding - Rev5 - AVN - Rev1

Uploaded by

Copyright:

Available Formats

You might also like

CS-FL-00-0102 FlightLink Services Operator Onboarding - Rev5 - AVN - Rev1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CS-FL-00-0102 FlightLink Services Operator Onboarding - Rev5 - AVN - Rev1

Uploaded by

Copyright:

Available Formats

FlightLink Services Operator Onboarding

Operator course CS-FL-00-0102

2 Revision 6, April 2020 FlightLink Administration

3 Revision 6, April 2020 FlightLink Administration

4 Revision 6, April 2020 FlightLink Administration

5 Revision 5, April 2020 FlightLink Services Operator Onboarding

Health Field Loadable Aircraft Data Real-Time Analytics

6 Revision 5, April 2020 FlightLink Services Operator Onboarding

FlightLink Provides Turn-Key Solution with Minimal Operator Infrastructure

8 Revision 6, April 2020 FlightLink Administration

9 Revision 6, April 2020 FlightLink Administration

Information Admin Operator’s System

• Details of the FlightLink onboarding are documented in the

10 Revision 5, April 2020 FlightLink Services Operator Onboarding

11 Revision 5, April 2020 FlightLink Services Operator Onboarding

• Data Management Administrator

• Client Administrator • Real-Time Monitoring Administrator

Operator to provide contact information for main focal points

FlightLink Provides Turn-Key Solution with Minimal Operator Infrastructure

14 Revision 5, April 2020 FlightLink Services Operator Onboarding

16 Revision 5, April 2020 FlightLink Services Operator Onboarding

– C23230011 Connectivity, FlightLink, Cellular (3G)

Operator to contract cellular/Wi-Fi data service provider(s)

Operator to share details of planned Wi-Fi infrastructure

• The Operator remains in full control of these settings in service

Operator to compile Wi-Fi settings

• The Operator remains in full control of these settings in service

Operator to compile cellular settings

Functionality SFTP AS2

Automatic delivery of Data Management data files  

21 Revision 5, April 2020 FlightLink Services Operator Onboarding

Operator to select AS2 solution

Operator to compile AS2 settings

Operator to compile SFTP settings

Operator to plan for data storage

Operator to plan for data routing

ARINC 767 / ASCII Printer

– Build options(3): Fill/Gaps, De-identification

Operator may specify custom data delivery requirements

– to the operator’s IT infrastructure via a business-to-business (B2B) connection

– to the Real-Time Monitoring “HMU Reports” page*

– via the A220 customer portal

Operator may specify custom data delivery requirements

Operator to specify data retention requirements

Operator to confirm ACARS provider(s) and routing scheme

Operator to share customized AOC definition

32 Revision 6, April 2020 FlightLink Administration

33 Revision 6, April 2020 FlightLink Administration

• HMU-related activities (e.g. manual data download, manual HMU configuration)

34 Revision 5, April 2020 FlightLink Services Operator Onboarding

• No other specific software is required to handle A220 LSAP

35 Revision 5, April 2020 FlightLink Services Operator Onboarding

36 Revision 5, April 2020 FlightLink Services Operator Onboarding

37 Revision 6, April 2020 FlightLink Administration

38 Revision 6, April 2020 FlightLink Administration

Operator compiles information

B2B connection setup

FlightLink services configuration