Plan the network.
Around the fleet.

Maritime connectivity links a vessel to shore through satellite, cellular or a combination of access technologies. A useful design also defines which applications can use those links, how traffic is prioritised and who manages the environment.

Begin with the work the network must carry. A vessel’s office applications, crew internet access and remote IT support may have different needs. Record those differences before selecting a terminal or service plan.

Where you operate

Trade routes, ports, time offshore and expected changes to the operating area.

What needs a connection

Business applications, voice, crew access and remote maintenance. Identify which activities can wait and which need an agreed fallback.

What is already on board

Terminals, routing equipment, network layout, contracts and the systems you intend to retain.

How does Starlink fit alongside VSAT?

Starlink is a LEO satellite access option in One Net’s connectivity portfolio. Review it against the vessel’s routes, installation requirements, expected traffic and available service terms. An existing VSAT connection may retain a role in the same design; the decision should follow the operating requirements and contracts rather than a blanket replacement rule.

What does SD-WAN add?

SD-WAN applies routing policies across the available connections. Access technology provides a path; routing policy determines how the network uses it. Agree the application priorities and the conditions under which traffic should move to another path.

What should happen when a link is unavailable?

Write down the traffic that should continue, the alternative connection it may use and any usage constraints. Validate the agreed behaviour during commissioning. A second connection alone does not establish what every application will experience during a change of path.

How should crew and business traffic be treated?

Define separate access policies, permitted uses and priorities. Review the network boundaries as well as bandwidth: traffic allocation and security controls are related decisions, but they serve different purposes.

Consider a vessel with an existing VSAT connection, business applications and crew internet access. The operator wants to assess adding Starlink while retaining shore-based IT support.

1. Assess the current environment

   Map the installed equipment and network boundaries. Review routes, contracts and the applications using the current connection.

2. Define the intended change

   Assign a proposed role to the new link. Identify which traffic may use it, how crew access should be handled and what remains on the existing service.

3. Agree the acceptance checks

   Document checks for application access, traffic policies, alternative-path behaviour and authorised remote support. Agree who witnesses and accepts the results.

4. Hand over the operating plan

   Record the installed configuration, support contacts, change responsibilities and information the shore team needs to oversee the vessel.

The outcome of this process is a defined scope and acceptance plan. Performance, installation feasibility and service commitments require assessment of the actual vessel.

Provide a summary of your fleet or vessel types, operating routes, current equipment and contracts. Explain what is not working today, the applications affected and your preferred installation opportunity.

What determines the proposal?

The access services and hardware, integration with retained infrastructure, installation scope and the work to be managed after deployment. Ask for assumptions, exclusions, recurring charges and acceptance criteria to be stated clearly.

What happens after an enquiry?

Your enquiry goes through One Net’s existing official contact form. Use the first conversation to establish the technical scope, the information needed for assessment and the appropriate next step. Existing customers seeking help should use the separate support route.