NetWorms Yacht
AV/IT
Menu

Independent AV/IT engineer for 35–70m yachts

AV/IT engineering services for yachts

I help Chief Engineers and ETOs diagnose faults, complete controlled repairs and small refit scopes, and leave the relevant system information with the crew.

The work can cover network connectivity, AV, CCTV, local automation, remote access and the electrical or computing infrastructure supporting those systems.

Discuss a service request View services
Direct contactYou work with the engineer carrying out the scope.
Current onboard areaGenova, Savona, Loano, Imperia, San Remo
Service planningScope, access and timing agreed before attendance.
Engineer working on antenna and connectivity equipment aboard a yacht in a marina.

Services

Technical support across connected onboard systems

A service request can begin with a specific fault, an incomplete handover, a planned change or a small refit requirement.

Connectivity

Network and connectivity engineering

Diagnosis, configuration and verification for onboard LAN, Wi-Fi, WAN and satellite connectivity.

  • Wi-Fi and VLAN fault isolation
  • Multi-WAN and failover verification
  • Starlink and upstream integration
  • Wireless surveys and coverage review

AV & control

AV, CCTV and automation support

Fault diagnosis and integration work for AV-over-IP, media, CCTV and local control systems.

  • AV-over-IP path diagnosis
  • CCTV and service displays
  • Local automation resilience
  • Endpoint and controller lifecycle review

Security

Network security and remote access

Review of vendor access, system accounts, network separation and access ownership.

  • Remote-access inventory
  • Network separation review
  • Credential and account ownership
  • Post-work access closure

Handover

Technical documentation and handover

Electronic system records, recovery information and configuration custody prepared for the completed scope.

  • As-built and dependency maps
  • Device and service inventory
  • Recovery and stop-boundary sheets
  • Configuration backup register
Service details and scope boundaries

For Chief Engineers and ETOs

When independent AV/IT support is useful

A network symptom may begin with power, switching, routing, a controller, an endpoint or an external service. I can follow the evidence across those layers and coordinate the work as one technical scope.

  • A recurring fault has already passed between several vendors.
  • The crew needs an independent assessment before approving replacement.
  • A short yard or port window requires preparation before onboard work begins.
  • The system works, but its topology, backups or recovery process are unclear.

Ways to engage

Available engagement formats

If the cause is still unknown, a diagnostic visit can establish the facts needed for a reliable repair proposal.

01

Remote evidence review

A disciplined first look at the symptom, current state and available evidence.

Typical result: A clearer fault boundary and the next useful test.

02

Onboard diagnostic visit

A bounded investigation when the system is unknown or the fault crosses layers.

Typical result: Observed facts, priorities and a defensible remediation scope.

03

Defined remediation

Controlled repair or configuration work with a known acceptance test.

Typical result: A verified known-good state and a clear change record.

04

Compact refit scope

Focused modernisation sized around the vessel’s real work window.

Typical result: A maintainable system without replacing equipment that still earns its place.

How the work is managed

A documented process for live systems

The exact level of control depends on the risk and scope, but the working sequence remains consistent.

  1. 01Review the request

    Define the affected service, current operational impact, available evidence and access window.

  2. 02Record the current state

    Capture relevant configuration, dependencies, versions and behaviour before intervention.

  3. 03Diagnose and agree the work

    Isolate the cause and confirm the change, expected result, acceptance test and recovery plan.

  4. 04Complete and hand over

    Verify the service in operation and provide the relevant record, backup and recovery information.

Read the working method
Tablet showing an electronic system topology and device inventory in front of a yacht cabinet.
Illustrative technical scenario

Handover

Documentation suited to the completed scope

The handover may include an as-built view, device and service inventory, dependency notes, configuration backup register, approved recovery steps and a record of the accepted system state.

The aim is to give the onboard team enough information to identify the affected area, carry out permitted recovery actions and escalate with useful evidence.

View the handover standard