The AirLink Manager Platform is a powerful browser-based software application that enables users to configure, monitor, and analyze Sierra Wireless gateways and associated applications/accessories (such as Asset Manager WiFi tags).
This topic provides the following information:
Note: If you are upgrading to AMM 2.17+ from an earlier version, you must clear your browser cache upon completing the upgrade.
The AirLink Manager Platform is available as two separate versions of the product. AirLink Manager (AM) and AirLink Mobility Manager (AMM). AM and AMM enables simplified, remote and real-time mass configuration, control and troubleshooting of AirLink routers and gateways, connected infrastructure, connected mobile assets and mission critical applications.
AM is an on-premises network management solution focused on fixed asset deployments and is ideal for applications where cloud-based management is not an option. AMM delivers on-premises or cloud-based network management targeted at customers with mobile assets. AMM displays a virtual dashboard with an up-to-date view of the entire fleet, and delivers a continuous stream of rich, real-time network data, allowing users to observe, track and examine the behavior of hundreds of devices, networks, and connected vehicle parameters as it occurs.
AM and AMM are configuration options on the same robust platform. For ease of documentation, “AMM” is used throughout to describe the features and capabilities of the product. As AM provides a subset of the capabilities in AMM, features that are specific to the AMM are identified. Most screenshots in this document that show a logo, show that of the AMM. Feature availability is dependent on the license purchased.
See AM vs AMM Feature Comparison for more information about the features available in each.
Note: the AMM was formerly known as the oMM in versions prior to 2.15.2; this document references those older versions as “oMM” where applicable
Note: throughout this guide the term MG refers to both oMG and MG90 devices
As of Version 2.15, the AMM supports ALEOS devices in addition to MG devices. The main difference between MG and ALEOS devices with regards to how they work with the AMM is that MG devices have constant two-way communication with an AMM when an Internet connection is available, whereas ALEOS devices only check in with the AMM at schedule intervals (i.e. Heartbeat).
This means that MG devices can transmit data to the AMM in near real-time and commands can be sent from the AMM to the MG device immediately. Each MG device collects operational data in a log (e.g. connection status, data transmitted/received, temperature of the unit, voltage of the vehicle, GPS location data, etc.). The data logs from the gateways are transmitted over a wireless data network to an AMM server. The AMM uses these data logs to present current and historical activity.
By default, ALEOS devices collect data when a device checks in with the AMM, and any commands issued to the ALEOS device (e.g. a schedule software upgrade) will not be initiated until the check in occurs. With the release of AMM 2.16, we have introduced an ALEOS Application Framework (AAF) application called AMMER that provides increased data collection independent of the device check in. This AAF application requires ALEOS 4.8.0 or later, and must be installed on your ALEOS-based AirLink gateways to enable this increased data collection. A number of the reports that have been enabled for ALEOS devices in AMM 2.16 require AMMER to function. To configure ALEOS devices for AMM, see Configuring ALEOS Devices for AMM Servers .
Note: An ALEOS gateway must be rebooted upon the initial installation of AMMER before it will be operational.
Note: The AMM does not support AAF application functions, including application installation, for ALEOS devices running 4.4.x.
The AMM is highly configurable to enable great flexibility between customer situations. Business intelligence-style data presentation and reporting enable users to leverage the large amount of data available from the gateways.
The AMM is available both as a “Hosted” version which is operated by Sierra Wireless, and as a standalone appliance which can be purchased and administered by a customer as an on-premise solution.
In this document an MG device and/or ALEOS gateway is often just referred to as a gateway. The gateway hardware is often installed in a vehicle but it can also be installed in a wide variety of locations to take further advantage of the system’s capabilities. Note that since a gateway is often installed in a vehicle, the term is often also used in place of the word “vehicle”.
A key feature of the AMM is its Management Tunnel, which is a dedicated secure VPN connection between the AMM and the gateways that it communicates with.
AMM uses an OpenVPN server to establish these VPN connections. For fleet sizes larger than 2000, multiple OpenVPN servers are used by the AMM, which are generally configured by Sierra Wireless Support during deployment.
Management Tunnel is supported for both MG and ALEOS devices. For more information see:
The following additional information is also available:
AMM has the following main features: