MARINE SYSTEMS / TECHNICAL OVERVIEW

From yacht signals
to engineering context.

Yachtrix is being developed as an edge-to-cloud platform for marine SCADA and yacht systems intelligence: a connected operational picture for crews, charter operators, fleet managers and engineering teams.

This overview defines the intended architecture and engineering questions. It is not a released product specification; integrations, hardware and delivery scope require project-level agreement.

1. Establish the integration boundary

Build a yacht equipment inventory covering propulsion, generation, batteries, distribution, tanks, bilge systems, HVAC and environmental sensing. Record which signals are accessible and which remain within vendor-controlled networks.

• NMEA 2000: identify supported PGNs, devices and the intended network connection.
• SAE J1939: confirm available engine parameters, permitted access and any gateway requirements.
• Modbus TCP / RTU: verify register maps, data types, units, scaling and polling constraints.
• Serial and additional interfaces: assess NMEA 0183, electrical I/O and documented vendor interfaces case by case.

2. Design the onboard data layer

Planned edge responsibilities include acquisition, timestamping, signal normalization, data-quality indicators and local buffering. Retention duration and synchronization behavior must be defined against hardware capacity and the yacht’s connectivity profile.

3. Make supervision useful

The intended monitoring scope includes trends, alarm history and diagnostic context. Engineering requirements should distinguish current readings from stale data, define alarm thresholds and hysteresis, and establish how alarms are acknowledged and escalated.

Yachtrix is not presented as a replacement for certified alarm, navigation, protection or emergency systems. Remote actuation and digital switching control are outside the capabilities established here.

4. Work through real operating situations

• Before departure: review supported battery, shore power and tank signals, while keeping physical inspections and prescribed checks in the yacht’s procedures.
• Under way: investigate trends in propulsion, electrical loads and auxiliary systems in their operating context.
• Alongside or unattended: define which changes matter, how connectivity affects notification and how the crew responds.
• During service: use timestamped history and equipment context to guide investigation and validate work.
• Across a fleet: establish consistent signal definitions and yacht-level access before comparing trends.

5. Choose the right deployment scale

Start with a compact edge computer for acquisition and local history. Optional local servers can add storage and processing within the same yacht; more demanding installations may call for paired servers or rack infrastructure. Edge-to-cloud connectivity may be direct or pass through this local layer. Replication, independent power paths and failover must be engineered and tested.

A yacht-management company or sailing-charter operator may choose a shoreside HQ server, a private data-center rack or a hosted environment. Capacity planning should cover signal counts, sampling rates, retention, uplink limits and the number of yachts. No fixed capacity or availability figure is claimed.

6. Connect remote services with purpose

Documented APIs may add weather, forecasts, charter bookings, work orders and other operational services. Agree authorized access, data ownership, licensing, credential management and update limits before implementation. Booking context can help identify service windows; weather context can inform passage reviews.

7. Design security into every layer

The intended design accommodates wired and wireless connectivity, including Ethernet and Wi-Fi, with marina, cellular or satellite uplinks where available. These transport networks complement marine data interfaces; they are not interchangeable protocol layers. Security requirements include authenticated endpoints, encrypted communications, network segmentation, least-privilege access, audit records and controlled updates and recovery.

8. Preserve history and support the fleet

Hosted, private-cloud and company-HQ deployments form the enterprise direction. Define retention, backup integrity, recovery testing, access permissions and support responsibilities around the operation. Charter workflows include handover reviews, reactive fault investigation and proactive maintenance planning. Storage durability and service levels must be established through implementation and validation, not inferred from a diagram.

9. Validate before prediction

Anomaly detection and predictive diagnostics sit on the research roadmap. Their usefulness depends on representative data, known operating modes, failure evidence and measured results. No predictive accuracy or autonomous action is promised.

The long-term vision

“The Yacht Operating System” expresses a possible future: a coherent software layer across the yacht. Today, Yacht Systems Intelligence describes the development direction without implying a released operating system or authority over yacht controls.