Ω-SAIL reveals the dynamics
info@omegasail.it
At METSTRADE 2026 — RAI Amsterdam, 17–19 November. We are on the floor. Write to us and we will come to your stand.

A new signal for sailing instrumentation

Your instruments show the state of the boat. Ω-SAIL shows where that state is going.

Ω-SAIL reads the standard instrument stream and continuously computes how much usable margin is left on three load paths — and how fast that margin is closing. No new sensors. It runs on board.

81.7%average margin still
available at warning
12–86 sobserved warning
lead time
0additional sensors
required
Kernel output · recorded upwind sequence t+000 s · 10×
100%
WIND
& SAILS
100%
SAIL
& HULL
100%
HULL
& WATER
All three paths within their normal range.

Actual kernel output on a recorded upwind sequence with two gusts, played at ten times real speed. The warning on the sail-and-hull path fires with 75% of its margin still available; the margin then falls to 53%.

Where the gap is

Onboard systems got much better at moving data. What is read on deck is still a set of numbers.

01

Instruments report state

Speed, wind, heel, rig load — every channel is an instantaneous value. Reading a developing situation out of them is work the crew does, in their heads, while sailing.

02

Integration solved access, not reading

Networked instruments, wireless load cells and multifunction displays made the data available everywhere on board. They did not change what the number on the screen means.

03

Nobody publishes the margin

How close a load path is to its limit, and how fast it is getting there, is not a channel that exists on the bus today. That is the channel Ω-SAIL adds.

What it measures

Three load paths, one normalised margin each

Ω-SAIL does not track sensors. It tracks the three relationships a sailing boat is always negotiating, and reports how much room is left in each.

Wind and sails

Is the sail still converting the wind?

Speed is being lost while the wind is there and the boat is not heeling further. The sail plan has stopped turning pressure into drive.

Sail and hull

Is the hull still carrying the power?

Heel builds, the helm loads up and the rudder starts working to hold the line. The boat is going over its balance before anyone on deck calls it overpowered.

Hull and water

Is the hull still holding its line in the water?

The boat is sliding — leeway opens up between heading and track, or sea state is taking more out of the hull than the water is giving back.

Heel is the pivot. The same loss of speed means three different things depending on what heel is doing at that moment. Heel is what separates a sail that has stopped converting from a boat that is overpowered from a hull that is sliding — which is why the attribution is made on heel and not on speed.

What it needs

Standard channels, standard protocols

The minimum set produces a global signal. The recommended set separates the three paths.

MINIMUM
global signal only
  • SOG, COG (GPS)
  • Heading (compass)
  • 1 Hz, timestamped
RECOMMENDED
full three-path output
  • Heel angle (IMU / attitude)
  • AWA + AWS (masthead unit)
  • STW (paddle or ultrasonic log)
OPTIONAL
sharpens the control path
  • Rudder angle (direct, else derived)
  • Leeway, sheet position
  • 1–10 Hz
INTEGRATION
how it sits on board
  • NMEA 2000 · Signal K · B&G FastNet
  • Runs on the boat — no cloud, no link
  • Reports “not measurable” rather than guessing

Sample rate is handled as an interval, not as a count of samples: the same sequence read at 1 Hz and at 10 Hz produces the same lead time.

Evidence

Nine events in one passage

Each row is one developing condition: when the warning fired, how much margin was still available at that moment, how far the condition then went, and when the trend turned.

Warning at Range left at warning Lowest reached Smoothed low Trend reversal
1 290 s78.8%50.4%63.0%+12 s
5 234 s85.6%56.1%66.7%+24 s
5 314 s75.4%57.1%72.1%+34 s
5 496 s78.2%59.7%73.5%+29 s
5 996 s75.5%51.2%69.3%+41 s
7 032 s85.0%59.9%70.0%+86 s
7 399 s85.0%58.4%72.0%+27 s
9 730 s87.6%52.0%70.3%+35 s
13 528 s84.2%65.7%62.5%+16 s
Mean81.7%56.7%68.8%+34 s

Status: software prototype, tested on recorded data. These figures describe the recorded sequences that were processed. They are not universally validated performance values, and nothing here has yet been produced in real time at sea.

The next step is real-time validation on signals acquired directly from onboard instrumentation, with attention to data availability, acquisition frequency, synchronisation and processing latency. That is the work we are at METSTRADE to arrange.

The prototype

One glance, three bars, no reading

The display is diagnostic only. It shows where the margin is going and how fast — never what manoeuvre to make, because that depends on the boat, the sails and the crew's intention.

Ω-SAIL quadrant: three margin bars with icons and percentages
The working view. Bar height is the margin left on that path; the bar below each column carries the trend; the dot marks a path that has just been hit. Icons rather than labels, so it reads in one glance and in any language.
Ω-SAIL passage report: margin trace with warnings and interventions
The passage report. Each triangle is an Ω-SAIL warning, each red dot the moment the crew's correction took effect — so the lead time is measurable after the fact, not claimed. Development build; this screen is still in Italian.

Where it earns its place

Wherever there is nobody spare to watch the trend

Shorthanded and offshore

Solo and doublehanded crews have no one free to watch a number develop. Thirty seconds of notice is the difference between easing a sheet and repairing something.

Autopilots

A pilot today reacts to heading error. A margin that is closing in thirty seconds is a feed-forward input — a channel an anticipating pilot does not currently have.

Performance programmes

A vendor-neutral derived channel that sits alongside load, rig and wind data, and logs where the boat was actually close to its limit rather than where it felt fast.

Charter and training

A visible, objective reason for what the boat is doing — for the student learning to read it, and for the fleet that would rather avoid the damage.

What we are looking for

A partner with instruments on a boat and engineers who know the bus

Ω-SAIL does not replace instrumentation. It increases the value of data the partner's equipment already generates.

What we bring

  • The Ω method and a working software prototype.
  • Development of the phone and tablet application.
  • Processing and analysis of the data collected.
  • Technical management of the trial programme.

What we ask

  • Technical discussion with your onboard network and protocol people.
  • Access to available instrumentation and data.
  • An equipped boat for a limited number of sea trials.
  • Technical support during those trials.
STEP 1Technical discussion
STEP 2Access to onboard signals
STEP 3Real-time sea trials
STEP 4Evaluation of results

Ω-SAIL is designed to be cross-platform. A product first developed and validated inside one partner's technical environment can afterwards run on boats equipped by other manufacturers.

Material

The five slides, and the one-page brief

Ω-SAIL reveals the dynamics — the problem, the boat's data, a single indicator Ω-SAIL uses what the boat already knows — GPS, compass, wind, heel, speed through water Ω-SAIL warns you before you get into trouble — margin curve and lead time How it works — input data, processing, output data The signal that helps you sail better — the app view explained

Contact

If the signal is interesting, the next conversation is a technical one.

Tell us what your instruments publish, at what rate, and on which bus. We will tell you straight away whether Ω-SAIL can read it and what it would produce.

info@omegasail.it

Ω-SAIL — Carpi (MO), Italy