Part 1 of 11
Goals and scope
What the system must achieve, how fast and how accurately, and where on the water its rules apply. Every later design decision traces back to this page.
The use case
SeaTrace AI provides real-time tracking of rented jet skis used by holiday-goers. Most riders are first-timers on a 15 to 60 minute package. They leave from a single dock, ride inside a marked area, and are expected back on time and in one piece.
The operator needs to know at a glance where every unit is, who is on it, how long they have left, and whether anything about its movement looks wrong. Outside rental hours, the same system becomes a security layer that watches for theft and tampering.
The design assumes one or more beach docks, each with its own zones, staff and fleet. Everything is configured per site, so a second beach is a configuration task rather than a new project.
| Users | Dock staff, shift supervisors, operations manager, owner |
| Assets | Jet skis, with optional extension to patrol and rescue boats |
| Typical rental | 15, 30 or 60 minutes, guided or self-ride |
| Operating day | Around 9am to 7pm, with overnight security monitoring |
| Sites | One beach dock at launch, multi-site ready |
Primary outcomes
Three outcomes, each with a measure we commit to tracking from the pilot onwards.
Accurate location
A trustworthy position for every unit through the whole journey: dock, launch corridor, riding zone, beach and back. Drift near the pier is filtered so a parked unit never appears to wander.
Measured by position error against surveyed dock markers, and the share of fixes rejected as noise.
Rental-time monitoring
Who has which unit, when it went out, and when it is due back. Overdue rentals are flagged automatically and the predicted return time helps staff plan the next departure.
Measured by average overrun per rental and minutes of idle time between rentals.
Theft and misuse detection
Geofence breaches, unexpected movement after hours, towing signatures and riding that is far outside the fleet’s norm, each raised to the right person with the evidence attached.
Measured by detection time, and false alerts per unit per day.
Performance targets
Reporting frequency is the main trade-off between detail, data cost and battery. Rather than one fixed interval, the tracker changes its rate with the unit’s state.
Reporting interval by state
| Unit state | Interval | Why |
|---|---|---|
| Riding, on rental | Every 10 seconds | Smooth track on the map and geofence detection inside 30 seconds at riding speed |
| Slow or idle on the water | Every 30 seconds | Enough to spot a breakdown or a rider in difficulty without wasting data |
| At the dock, in hours | Every 5 minutes | Confirms the unit is moored and powered |
| Overnight, parked | Heartbeat every 30 minutes, instant wake on motion | Long backup life, while any movement triggers immediate reporting |
| Alarm active | Every 2 to 5 seconds | Live pursuit view for theft recovery or a safety incident |
Accuracy, latency and reliability
| Measure | Target | Notes |
|---|---|---|
| Horizontal accuracy, open water | 0.5 m or better, 95% of fixes, with QZSS MADOCA-PPP converged; 2 m otherwise | Lets the swim-zone buffer shrink from about 10 m to about 3 m without false alarms |
| Horizontal accuracy, near the pier | 5 m or better, 95% of fixes | Structures and hulls cause multipath; dock snapping removes visible jitter |
| Event to staff alert | 30 seconds or less | From the fix that crosses a boundary to the push notification on a phone |
| Track completeness | 99% of fixes delivered | Store-and-forward backfills any coverage gaps once the link returns |
| Platform availability | 99.5% monthly | Excludes agreed maintenance windows outside operating hours |
| False alerts | Fewer than 0.5 per unit per day | Tuned during the pilot; noisy alerts get ignored, so this matters as much as detection |
Operational boundaries
Every site is described as a set of zones drawn on the chart. Each zone carries its own rules: what is allowed, what triggers a warning, and what is an emergency.
Rental dock
Start and end of every rental. Units here are “at dock”; leaving without a check-out is an alert.
Launch corridor
Marked lane between dock and riding zone, with a slow-speed limit set by the operator.
Riding zone
Where riding is permitted. Leaving it triggers a warning to dock staff.
Swim zone
Buoyed bathing area. Any entry is critical and escalates immediately.
Restricted area
Coral reserve or channel. A warning buffer fires first; entry is critical.
Recovery point
Where broken-down units are towed and staged. Dwell here is expected.
In scope
- Tracker hardware: design, supply, certification support and installation
- Tracking platform: ingestion, geofencing, rental lifecycle, anomaly detection, return-time prediction
- Staff app for Android and iOS: check-out, check-in, live map, alerts
- Control room web dashboard: live map, rental timeline, reports, heatmaps
- Alerts by push notification, WhatsApp and SMS
- Field testing, pilot, fleet rollout, staff training and ongoing support
Out of scope, unless agreed
- Online booking and payment processing (we integrate with an existing system by API or file export)
- A rider-facing app, offered as an optional extension after Phase 4
- Patrol boat equipment beyond fitting a tracker
- Marine licensing applications, which remain the operator’s responsibility; the platform supplies supporting records
Assumptions
Cellular coverage at the site is confirmed during the survey. Jet skis provide a 12 V accessory supply. The operator defines zones with local authority guidance. Staff phones run Android 10 or iOS 15 or later.