Keeping vessel data reliable at fleet scale takes ongoing operational work. The operating model defines how much of that work sits with you, and how much sits with us.
Beyond capturing and standardising the data, vessel data infrastructure needs ongoing operational work to stay reliable: monitoring data health, investigating root causes, taking action to resolve. We call this the vessel data Function. You run it independently, you run it with full visibility from us, or we run it. Under every model, who does what is explicit.
The Foundation is deployed and delivers standardised vessel data into the Raa Labs cloud. The customer receives the data through Raa Labs' APIs and runs the vessel data Function independently using their own tools and processes.
Raa Labs: Platform service health, software maintenance, correction of platform-side faults, onboard software lifecycle management under RaaEDGE.
Customer: Monitoring data health, discovering issues, investigating vessel silence and root causes, coordinating with OEMs, crew, and vendors.
Right for you if you already have the internal tooling and teams to monitor vessel data health independently.
Everything in Self-Governed, plus Raa Labs deploys monitoring infrastructure, data quality models, and alerting across all contextualised signals. Full visibility into data health through the Raa Labs Portal. Fleet overview showing every connected vessel. Signal-level data quality indicators. Alerting when data streams degrade or stop. You see exactly what is happening across the fleet, and you decide how to act.
Raa Labs adds: Signal-level data health monitoring, fleet-wide health views, alerting for data interruption or degradation, data quality indicators, data access governance, API management.
Customer: Acting on what the monitoring surfaces. Investigation, coordination, and restoration of data streams.
Right for you if you want to know whether your vessel data is reliable across the fleet, across time, and have the visibility to manage it.
Everything in Governed, plus Raa Labs operates the vessel data Function within an agreed scope. We detect issues, investigate root causes, and coordinate with all parties. Case management through closure.
Raa Labs adds: Detection, investigation, coordination with crew, customer IT, OEM vendors, connectivity providers. Structured follow-through toward data stream restoration. SLA-backed response and case management.
Customer: Signals outside the assured scope remain visible through Governed monitoring. You decide whether to act or expand the scope.
Right for you if you want vessel data reliability operated as a dedicated function rather than a side responsibility.
Different vessels in the same fleet can operate under different models. Models can change as your internal capability matures or your fleet shape changes.
| Capability | Self-Governed | Governed | Assured |
|---|---|---|---|
| Foundation and platform | |||
| Data ingestion, standardisation, delivery | ✓ | ✓ | ✓ |
| API access (contextualised and uncontextualised) | ✓ | ✓ | ✓ |
| Portal: visibility into your data foundation | ✓ | ✓ | ✓ |
| Data availability (integration level) | ✓ | ✓ | ✓ |
| Platform service health | ✓ | ✓ | ✓ |
| Correction of platform-side faults | ✓ | ✓ | ✓ |
| Foundation software lifecycle management | ✓ | ✓ | ✓ |
| Visibility and governance | |||
| Connection and streaming status | · | ✓ | ✓ |
| Latency (buffering) | · | ✓ | ✓ |
| Data availability (signal level) | · | ✓ | ✓ |
| Data health monitoring | · | ✓ | ✓ |
| Alerting for data health | · | ✓ | ✓ |
| Controlled data sharing with token-based access | · | ✓ | ✓ |
| Action and accountability | |||
| Investigation of data loss or degradation | · | · | ✓ |
| Coordination with crew, IT, OEMs, vendors | · | · | ✓ |
| SLA-backed response and case management | · | · | ✓ |
Platform service health is backed by defined targets for all customers. Assured adds time-based commitments for detection and response.
Raa Labs implements vessel data infrastructure across large and diverse fleets. Different vessel types, different onboard systems, different IT environments, different OEM landscapes. The implementation process is standardised and repeatable. The configuration adapts to each vessel's setup within that process. Timelines shorten when multiple vessels are implemented in parallel.
Alignment on objectives, data scope, vessel priorities. Joint project team. Architecture and target systems defined.
RaaEDGE: hardware or virtual instance per vessel, crew-assisted installation, connectors deployed remotely. Cloud Connect: API integration configured at cloud level, no onboard work.
Tag mapping and contextualisation. Data structure, quality, and frequency verified.
The Function operates under the chosen model. Platform health monitoring runs continuously. Governed adds alerting. Assured adds action.
Multiple vessels can be implemented in parallel, with full visibility into where each vessel stands in the process. The operating model is defined before implementation begins and can be adjusted later.