Migration I3 to I4 Satellites

Inmarsat: 3rd Generation Satellites End of Life: Migration to 4th Generation Satellites

A Message From Inmarsat:-

Following the previous I-3 to I-4 migration notice issued in February, please find below an update on the dates for the first migration of services from the Atlantic Ocean Region West (AORW) I-3 satellite to the Americas (AMER) I-4 satellite.

This migration will be performed in two stages:
• Migration of Inmarsat C (to include Aero C and Mini C) services is scheduled to take place on 16 April 2018 at 10:00 UTC.
• Migration of Fleet 77, Swift 64 and Classic Aero services is scheduled to take place on 30 April 2018 – further details will be provided at least four weeks in advance of this date.
Our primary objective is to ensure that the transition process is as seamless as possible for our partners and customers.

The transition of services from the I-3 fleet onto our I-4 constellation will continue throughout 2018 and will take approximately nine months to complete. Our approach is to migrate all services (Inmarsat C, Fleet 77, Swift 64 and Classic Aero), satellite by satellite, as per the schedule shown in the table below.



I3 Pacific Ocean Region (POR; above left) to I4 Asia Pacific (APAC) Migration

Most Australian customers will be using the I3 Pacific Ocean region satellite and will migrate to I4 APAC around June 2018. Those customers around the WA coast may be using IOR as it’s elevation is slightly higher than the POR currently. Once the POR to APAC migration has occurred most customers will just use the APAC satellite as it covers Australia entirely

Due to the move from the I-3 to the I-4 satellites, the coverage areas will change and users will need to ensure that their devices are pointed to the relevant satellite. This process will generally be managed automatically by the terminal without the need for user intervention. However, in some instances, users will need to manually repoint their devices to the appropriate satellite.
• Inmarsat C users should ensure that their local applications (e.g. data reporting) will operate correctly if they are using a different Inmarsat satellite and are advised to contact their applications provider for any support.
Each migration step will cause a short outage of around 30 minutes as services are migrated onto the I-4 satellites. Under supervision of the International Mobile Satellite Organisation (IMSO), the Global Maritime Distress Safety System (GMDSS) and Maritime Safety Services will be closely monitored during the migration. These safety services will be restored first with the highest priority.

Final dates for the transfer of services of the POR, AORE and IOR migrations will be confirmed approximately six weeks prior to the start of each migration to the corresponding satellite.

We will continue to communicate with you throughout the planning and execution phases of the migrations, providing additional details as and when necessary. Alternatively, please visit the website www.inmarsat.com/i3-i4-services-migration for more information and updates. Inmarsat Migration Guide

Due to the move from I-3 to I-4 satellites, the coverage areas will change and users will need to point towards a different satellite, although this will generally be managed by the terminal without user intervention. However, in some instances, users will need to use a different ocean region.

  • Inmarsat-C users should ensure that their local applications (e.g. data reporting) will operate correctly if they are using a different ocean region

The migrations will be performed during normal working hours, when technical specialists are available to provide support.

Inmarsat has been working closely with LESOs since 2015, both in groups and individually. Inmarsat and its LESO partners will undertake a joint campaign to reach out to end-users to ensure they’re aware of the migration and the steps they (the end-users) will need to take.

We are planning to create infographics to explain the migration process; these graphics will show service coverage of each satellite before and after the migration.

We will be communicating to you throughout the migration planning and execution process, providing additional detail as and when this becomes available.

The following Cobham SATCOM products will be affected:

SAILOR Fleet 77, SAILOR Fleet77+

All SAILOR Fleet products have reached their End of Life (EoL) and their service EoL. The SAILOR Fleet 77 are covered by the general service/support terms being six years after last time delivery, however, no later than June 30th, 2017, as previously communicated in partner Briefing “Last Time Buy – SAILOR Fleet77 and SAILOR Fleet33” of May 2nd, 2011.

It is expected that the Fleet 77 will be able to run all services in the I-4 global beam without problems. However, we are not able to create new software for the SAILOR Fleet 77 and if any unforeseen complications are encountered during the I-3 to I-4 migration, new corrective software will not be made available. We encourage our partners to start a dialogue with existing Fleet 77 users in order to explain the potential terminal malfunction. We recommend that the installed based is upgraded to the newer SAILOR FleetBroadband platform.

SAILOR and Thrane & Thrane branded Mini-C and Sat-C Mobile Earth Stations (MES)products

In general the Thrane & Thrane and SAILOR branded Sat-C and mini-C Mobile Earth Stations (MES) products are not affected by the switch from I3 to I4 satellites. The products are fully capable of scanning and the new I4 satellites will replace the old I3 satellites after the scanning is made.

The MES may be located in an area covered by two satellites before the switch. After the switch the same area may only be covered by one satellite.

If the MES is not logged in via the remaining satellite:

  1. Scan and login
    1. All NON-GMDSS versions will automatically initiate an ocean region scan and login through the remaining satellite.
    2. As a matter of regulation all GMDSS versions will NOT automatically initiate an ocean region scan. The user shall initiate a scan from the user interface, which in turn will login through the remaining satellite.
  1. Data reporting
    1. To ensure continuous data reporting a multi ocean Data Network Identifier (DNID) is required, please contact your service provider.
  1. “Allowed ocean” feature (TT3027)
    1. If the MES make use of this feature and is configured to operate via a satellite which is no longer available, it is always possible for the user to force the MES to log in to the remaining satellite, by initiating a scan. This is independent of the MES model and type.

Effected MES units: