The Yacht Refit Network Checklist: What to Confirm Before Equipment Is Ordered

Equipment orders are easier to place than to change. On a yacht refit, the avoidable delays usually appear after hardware has been selected: a switch has insufficient PoE capacity, the only available uplink is the wrong media type, or an access point cannot be mounted where the coverage plan assumed. A short technical check before purchase protects the programme, the installation team and the vessel.

1. Define the network brief

Start with the operating requirement, not a product list. Confirm the areas being served, services expected on each network, internet connections, critical devices, AV or control dependencies, and who will support the system after handover. Record assumptions that still need confirmation, including whether the vessel is alongside, in build, or moving between locations during the refit.

2. Confirm the PoE budget with headroom

List every powered device by switch and use its stated maximum power draw where available. Include access points, cameras, phones, controllers and any PoE-powered converters. Compare the total against the switch’s available PoE budget, then leave sensible headroom for startup demand, future devices and changes on site. Port count alone does not confirm that a switch can power the required endpoints.

3. Map uplinks and fibre or copper runs

Document each inter-rack and deck-to-deck link: origin, destination, route, approximate length, existing cable type, connector type and available termination. Confirm whether the design needs copper, multimode fibre or single-mode fibre, and identify the correct optics or media converters before ordering. It is also worth noting any spare fibres, patch panel capacity and routes that may be difficult to access once work is complete.

4. Check rack space, cooling and power

Confirm usable rack units rather than nominal rack height. Allow for cable management, patching, power distribution, service access and airflow. Check the power feed, outlet type, UPS arrangement and whether the cabinet’s cooling path suits the proposed equipment. A network design that fits on a drawing can still be impractical if it blocks ventilation or leaves no room to dress cables safely.

5. Confirm Wi-Fi coverage and mounting constraints

Review the intended access point locations against the actual build. Ceiling materials, metalwork, bulkheads, service voids and aesthetic restrictions all influence the final placement. Confirm cable routes, mounting method, available clearance and whether an access point must be concealed or placed in a service area. Coverage expectations should be agreed by zone, with particular attention to exterior areas and spaces separated by heavy structure.

6. Verify lead times and delivery location

Check availability before the equipment list is treated as final. Confirm the required delivery date, delivery address, site contact and any yard or marina receiving restrictions. If equipment will be delivered to an integrator, warehouse or vessel, make sure the recipient can receive and store it securely. Where timing is tight, identify which components are critical to first fix, commissioning or handover.

7. Decide what can be configured and tested before dispatch

Pre-configuration is most useful when the network brief, addressing plan and equipment schedule are sufficiently settled. Switch naming, VLANs, management addressing, firmware baselines and access point adoption can often be prepared in advance. Agree the scope of any bench test, what information must be supplied, and what remains to be completed on board. YOT can help validate a requirement, source project equipment and prepare Plug n’ Go configurations where agreed.

When to bring in technical pre-sales

Bring technical pre-sales into the discussion when the equipment list is still being shaped, when uplink or power assumptions are unclear, or when the programme leaves little room for substitutions. Early review is especially helpful where several trades share the same rack space, cable routes or power provision. The aim is not to over-design the system, but to identify the dependencies that can affect ordering and installation.

Final before-order checklist

• Network brief, scope boundaries and key assumptions confirmed.

• PoE budget checked by switch, with headroom included.

• Uplink media, cable runs, connectors and optics confirmed.

• Rack units, cooling, cable management and power verified.

• Wi-Fi locations, mounting constraints and coverage expectations reviewed.

• Lead times, delivery point and receiving arrangements confirmed.

• Pre-configuration and bench-testing scope agreed.

For a requirement review, equipment sourcing or agreed Plug n’ Go preparation, visit fuse.systems or contact sales@yotltd.com.

Frequently asked questions

What should a yacht refit team confirm before ordering network equipment?

Confirm the network brief, PoE requirements, uplink media and routes, usable rack space, power, cooling, Wi-Fi locations, delivery timing and what can be configured before dispatch. Record any assumptions that still need confirmation before equipment is ordered.

How do we size a PoE budget for a refit?

List the maximum power draw of every powered device by switch, including access points, cameras, phones, controllers and converters. Compare each total with the switch’s available PoE budget, then allow headroom for startup demand, future devices and site changes.

When should fibre or higher-speed uplinks be specified?

Specify uplinks after documenting each link’s origin, destination, route, approximate length, existing cable type, connector type and capacity requirements. Use that information to confirm whether copper, multimode fibre or single-mode fibre is appropriate and whether the required optics or converters are available.

What information should be sent for a technical pre-sales check?

Send the operating brief, areas to be served, equipment schedule, expected powered devices, uplink and cable details, rack and power constraints, Wi-Fi locations, delivery requirements, programme timing and the parts of the configuration or testing scope that are already agreed.