Airside Sync Data Sheet¶
The latest version of this data sheet is also available as a PDF download.
Client Specifications¶
The Airside Sync client is the user-facing application running on a mobile device or desktop computer.
Device Requirements¶
Mobile¶
Phones are tablets are supported. Tablet devices are recommended for an improved user experience.
iPad and iPhone devices running iOS 15.0 or newer
Android tables and phones running Android 11.0 or newer
Desktop¶
Chrome or Edge browsers on Windows 10 or newer
Safari, Chrome, or Edge browsers on macOS 11.0 or newer
Network Requirements¶
The Airside Sync client (mobile or desktop) requires an Internet connection with the ability to make unfiltered connections to the Airside Sync cloud service on port 443/TCP (HTTPS). WiFi or 4G (LTE) or better is recommended.
Protocols used:
HTTP/2 over TLS (Transport Layer Security) version 1.3
gRPC streaming
External Interfaces & Integrations¶
WiFi or cellular data connection required
Device-integrated GPS required for location-based services
MD30 Interface to Vaisala Mobile Detector MD30
over Bluetooth (Android only)
over TCP via gateway [1] (iOS and Android)
UMB to Lufft Mobile Advanced Road Weather Information Sensor (MARWIS)
over Bluetooth (Android only)
over TCP via gateway [1] (iOS and Android)
Supported Languages¶
The Airside Sync user interface is available in the following languages: Chinese, Dutch, English, French, German, Latvian, Romanian, Spanish, and Swedish.
Server Specifications¶
The Airside Sync server is the central component of the Airside Sync, generally provided as a cloud service.
Integration Protocols¶
REST API over HTTPS¶
Airside Sync provides an open API where clients may access historical data, update assessments, publish reports, etc. For the latest full specifications, please see https://api.safe-sky.net/v1/openapi.html.
SNOWTAM over AFTN¶
Airside Sync can send AFTN messages directly, without a specific integration with the aerodrome. Messages are delivered similar to any other external AFTN message.
Safe Sky AFTN address:
KEWRXAAS
Safe Sky AFTN network partner: ARINC AviNet
Alternatively, Airside Sync can connect to an aerodrome-provided AFTN-over-IP gateway using either of the following protocols:
GWDI AFTN Message Switch TCP/IP Protocol for Message Exchange (TCP/IP-ICD-1.2 18 June 2002)
Frequentis smartMessenger AFTN over TCP/IP (ISD001_2_0004_2.2_ICD_AFTN_TCP_IP)
AMQP over TLS (AMQPS)¶
Airside Sync can publish reports on an AMQP message bus, conforming to the AMQP Messaging Service Binding of the SWIM-TI Yellow Profile.
Client mode supported – end user connects to Safe Sky AMQP server
Server mode supported – Safe Sky connects to end-user AMQP server
SNOWTAM, RCR and ATIS transmitted as text and JSON
SNOWTAM transmitted as AIXM 5.1
Email, SMS, and Fax¶
Airside sync can publish SNOWTAM, RCR and ATIS messages over email, SMS and fax.
SNOWTAM, RCR and ATIS as plain text email, SMS, and fax
SNOWTAM and RCR as PDF email attachment
ATIS in voice synthesized format (MP3 or WAV) email attachment
OpenID Connect¶
Airside Sync uses standards-based OpenID Connect for authentication and authorisation. When deployed with the Airside Sync cloud service, the authentication provider is Microsoft Azure (Azure Active Directory B2C).
Airside Sync supports SSO from external OpenID Connect-conformant authentication systems [2].
METAR¶
Airside Sync automatically import the latest METAR for each client aerodrome.
RWIS¶
Airside Sync supports automatic import of runway weather data from the Vaisala Road & Runway Weather Station RWS200 system.
Hosting Locations¶
The Airside Sync cloud service hosting is provided by Microsoft Azure. Customer data is located in the following Azure data centers, depending on the customer location:
Customer region |
Azure DC |
Location |
---|---|---|
EU & the UK |
“West Europe” |
The Netherlands |
Americas |
“East US” |
Virginia, USA |
Asia Pacific |
“Southeast Asia” |
Singapore |