# Offline Vessel Software and Synchronization | Faromo

Canonical: https://faromo.com/en/products/offline-synchronization
Language: en

Keep vessel work running without internet and synchronize completed records safely and controllably when connectivity returns.

Modified: 2026-08-16

Reviewed: 2026-08-16

View tasks and record results offline in supported mobile workflows. Records are sent when connectivity returns, and pending items remain visible in the app.

Daily maintenance, checklists and operational records continue when vessel connectivity slows or disappears. If the system depends on online forms, crews fall back to paper and later duplicate data entry.

Faromo addresses this problem with a layered flow—SQLite on mobile, IndexedDB on the web and a tenant-scoped server event history—not a single “offline” switch. A local save, queued transfer and server result are different states, each with its own control point.

## Local task access

Assigned work and required references remain available without connectivity.

## Offline capture

Record results, notes, readings and operational data securely on the device.

## Sync queue

See pending records with order, status and error reason.

## Retry control

Interrupted transfers resume in a controlled way when connectivity returns.

## Record-specific conflict policy

Retain different replay decisions for maintenance, certificates, incidents and append-only log records in event history.

## Shore status

Monitor a registered device’s last sync, cursor progress and stale-device state.

## Workflow

1. Prepare data onboard: Tasks and references become available locally.
2. Work offline: The crew completes daily work without interruption.
3. Manage the queue: Completed records enter the transfer queue.
4. Sync ashore: When connectivity returns, records are validated into the shared state.

## Which modules can work offline?

Coverage is verified by client and action. The native app implements local queues for work orders, noon reports, rest hours, drills, incidents, CAPAs, checklists, logbooks, permits to work and related operational flows; the pilot scope should still be confirmed before purchase.

## What happens if the same record changes in two places?

There is no single generic merge rule. The server applies record-specific policy; replayed, skipped, conflict or rejected outcomes remain in event history for diagnostics.

## Is data lost if synchronization fails?

A failed write remains pending or failed in the local queue and can be retried. Pilot acceptance must still test device loss, logout, attachments and lost-server-response scenarios separately.

## Can shore see the vessel’s last sync?

Yes. Authorized users can monitor a registered device’s last successful pull, last cursor and stale-device state. The count of locally pending records is shown on the device itself.

## Sources

- [Guidelines on Maritime Cyber Risk Management (MSC-FAL.1/Circ.3/Rev.3)](https://wwwcdn.imo.org/localresources/en/OurWork/Security/Documents/MSC-FAL.1-Circ.3-Rev.3.pdf)
- [Maritime cyber risk management](https://www.imo.org/en/ourwork/security/pages/cyber-security.aspx)
- [International Safety Management (ISM) Code](https://www.imo.org/en/ourwork/humanelement/pages/ismcode.aspx)