Technical services

AV/IT service scopes for live yacht systems

A request can begin with an unresolved fault, a defined change, a compact refit requirement or a documentation gap.

The first step is to establish the affected service, the operational consequence and the evidence already available. From there, the work is scoped around diagnosis, controlled intervention and an accepted handover state.

Discuss a service request

Where to begin

Start with the operational situation

The service route should follow what is known today. It does not need to assume the final repair before the evidence supports it.

01 Fault diagnosis

Cross-system diagnosis and recovery

For faults that are intermittent, poorly documented or moving between vendors without a clear technical owner.

Existing onboard rack equipment inspected during a fault investigation.
Onboard fault investigation

Useful when

  • The affected service crosses power, network, controller and endpoint layers
  • A recurring fault has survived previous resets, swaps or remote sessions
  • The current state is not documented well enough to approve a repair
  • The crew needs an independent view before committing to replacement

Work may include

  • Capture the before-state, symptom and operational impact
  • Test dependencies in a controlled sequence
  • Separate root cause, contributing conditions and unrelated defects
  • Agree and verify a bounded repair or the evidence needed for the next specialist
Discuss this service

02 Connectivity

Networks, Wi-Fi and upstream connectivity

Diagnosis, configuration and integration across the onboard LAN, wireless coverage and available internet paths.

Existing yacht network rack with patching, switches and connected equipment.
Existing rack and network infrastructure

Useful when

  • Guest or crew connectivity is inconsistent between areas
  • WAN failover behaves differently from the intended design
  • Starlink or another upstream service must join the existing network cleanly
  • A refit change affects VLANs, switching, firewall rules or wireless coverage

Work may include

  • Wired and wireless surveys, switch-path tracing and VLAN review
  • Router, firewall, DHCP, DNS and policy verification
  • Multi-WAN, load-sharing and failover testing
  • Starlink network integration, including existing antenna systems and downstream services
Discuss this service

03 AV and communications

AV, CCTV and crew communication systems

Integration and fault work for media endpoints, AV-over-IP paths, CCTV recording and practical intercom requirements.

Engineer seated upright while testing CCTV and intercom equipment in a compact yacht technical space.
Illustrative technical scenario

Useful when

  • A display, source or room works intermittently or only through one control path
  • Camera streams, NVR recording or crew monitoring displays are incomplete
  • An intercom must work at the required location and reach the right crew devices
  • AV or CCTV work is being delayed by unclear network dependencies

Work may include

  • Signal-path and endpoint diagnosis for AV and control
  • AV-over-IP multicast, switching and receiver checks
  • Camera, NVR, storage and additional display integration
  • Intercom mounting, network, audio/video and mobile-answering integration
Discuss this service

04 Local control

Interior automation and local control

Focused work on local automation where the vessel needs predictable operation, understandable dependencies and supportable control.

Local wall-mounted control display installed in a yacht crew area.
Local crew-area control display

Useful when

  • Lighting, shades, climate or scenes no longer behave consistently
  • A local controller must continue operating without cloud access
  • Guest tablets or room controls need a defined, maintainable integration
  • A compact upgrade must coexist with retained equipment

Work may include

  • Loxone configuration, integration and fault diagnosis
  • Controller, sensor, network and power-dependency review
  • Scene, schedule and user-interface adjustments
  • Integration with relevant AV, network and room systems
Discuss this service

05 Infrastructure

Onboard compute, storage and backup

Support for the compact computers, servers and storage systems that sit behind AV, CCTV, files and vessel services.

Existing onboard compute and network rack with connected cabling and equipment.
Existing onboard infrastructure

Useful when

  • NAS, shared storage or media services are slow, full or unreliable
  • A compact server or PC needs repair, replacement or balanced specification
  • RAID health, backup coverage or recovery ownership is unclear
  • Power, cooling, storage and application symptoms are being treated separately

Work may include

  • NAS, file-share, media-storage and RAID assessment
  • Compact server and PC assembly or lifecycle replacement
  • UPS, storage, network and thermal-dependency checks
  • Backup verification and practical recovery planning
Discuss this service

06 Security and access

Network security and remote access review

A practical review of who can reach onboard systems, through which path, and who retains control after the work is complete.

Rugged tablet showing an unreadable remote-access register beside yacht technical equipment.
Illustrative technical scenario

Useful when

  • Vendor access has accumulated without a current owner or register
  • Guest, crew, technical and public-facing services are not clearly separated
  • Credentials or remote tools were inherited from previous support arrangements
  • A refit introduces new connected equipment or external support paths

Work may include

  • Remote-access, account and exposed-service inventory
  • Segmentation, firewall and trust-boundary review
  • Credential custody and administrative ownership checks
  • Removal or closure of temporary post-work access
Discuss this service

07 Handover

Technical documentation and crew handover

Electronic records sized to the completed work and the information the crew needs to identify, recover and escalate a fault.

Rugged tablet showing an unreadable electronic system diagram and device inventory.
Illustrative technical scenario

Useful when

  • The system works but its topology, backups or support boundaries are unclear
  • A refit or repair has changed dependencies without updating the records
  • Crew turnover risks losing configuration and recovery knowledge
  • Multiple vendor documents do not describe the installed system as a whole

Work may include

  • As-built and dependency diagrams
  • Device, service and relevant software inventory
  • Configuration backup and change registers
  • Approved recovery, stop-boundary and escalation notes
Discuss this service

Before work begins

A proposal defines the technical and commercial boundary

The exact detail depends on the risk and available evidence, but the decision points remain explicit.

Deliverables
What will be inspected, changed, tested and handed over.
Access
Required spaces, system access, work windows and authorised contacts.
Assumptions
The known state, available records and dependencies outside the scope.
Acceptance
How the completed service will be verified in normal operation.

Service enquiry

Describe the affected service and current operational impact

A broad location, available window and redacted symptom are enough for the first review. Vessel identity, credentials and exact live location are not required.

Prepare a service enquiry