One integrated system that captures vessel data onboard, standardises it across the fleet, and delivers it through APIs. Your analytics, your reporting, your compliance tools, your third parties. One source, any consumer.
Captures vessel data at source. Standardises across vessels and systems. Stores and serves through APIs in the naming schemas your downstream systems require.
Monitors data health, investigates root causes, and takes action to restore data streams. The work that has to happen for a Foundation to stay trustworthy at fleet scale.
The Foundation is what every Raa Labs customer receives. It is the same underlying system across all operating models. What varies is the operational layer on top.
Every signal contextualised against a fleet-wide naming schema. ISO 19848, DNV VIS, JSMEA, or custom naming, served simultaneously from the same Foundation. A signal means the same thing on every vessel.
Stored in a dedicated fleet tenant in the Raa Labs cloud. Measurements, metadata, statistics, and derived values served through structured APIs. Contextualised and uncontextualised signals available. Pull into your data lake, analytics tools, reporting systems, or share with third parties.
Fleet-level visibility into your data foundation. Fleet overview showing connected vessels, data explorer for viewing and comparing raw data, tag library, expected signals overview, and platform service health visibility.
Token-based authentication governs who can reach the API. You decide which systems and people get access to your fleet's data.
Both deliver into the same Raa Labs fleet tenant. A fleet can mix both. The choice is made per vessel based on existing setup and what data you need.
Captures data directly from vessel systems, standardises at the source, delivers to the cloud. Handles signal capture, local processing, buffering during connectivity loss, and secure transmission. OEM-agnostic across all common industrial protocols. Standardisation happens onboard, not just in the cloud. Data buffered locally during connectivity loss, no data lost. Entire software stack managed remotely after physical install, no crew involvement for ongoing operations.
Brings data from existing onboard collectors into the Foundation at the cloud level. No new hardware. No rip and replace. Data from existing collectors is ingested, contextualised, and standardised. Consolidates data from multiple collectors and OEM clouds into one foundation. Raa Labs handles format mapping, signal identification, and contextualisation. Historical data can be backfilled. No onboard installation required.
No lock-in. Change where your data goes and how it is used without changing the foundation underneath.
Capturing data and standardising it is not enough. At fleet scale, things happen. Sensors drift. Onboard systems change. Connectivity varies. OEMs update interfaces. Crew change configurations. Keeping the data dependable over time is its own discipline. We call it the vessel data Function.
Watch every contextualised signal across the fleet. Connection status, latency, data quality, completeness. When something degrades or stops, it is detected, not waited on.
Trace the issue to its root cause. Place it where it belongs: sensor, onboard system, connectivity, platform, OEM. Cross system boundaries. Coordinate with crew, customer IT, OEM vendors, connectivity providers. Investigation is where most of the operational work lives.
Work to restore the data stream. Coordinate the work required, whether it is a configuration change, a sensor replacement, a vendor escalation, or a crew action. Track the case through to closure.
Vessel data does not stay reliable on its own. Signals degrade, connections drop, sensors drift, configurations change. Somebody needs to watch, figure out what went wrong, and get it fixed. This is the vessel data Function. The operating model defines who does it.
Platform service health (ingestion services, processing pipelines, storage, APIs, portal, monitoring infrastructure) is Raa Labs' responsibility regardless of operating model. The choice is about the Function: who monitors data health, who acts on issues, who is accountable for keeping the data trustworthy at fleet scale.
See Our Service