Local data scope
Keep tasks, forms and effective documents required for daily work available onboard.
Do not design for the vessel as if it were an office.
High latency, low bandwidth and complete disconnection are not exceptions at sea. Systems that require constant connectivity push crews toward paper, screenshots and delayed entry.
Faromo keeps required work data locally, queues completed records and synchronizes them in order when connectivity returns. Shore can monitor last sync and pending status.
Scope and core capabilities
Low bandwidth
Prioritize transfers based on core records and attachment status.
Queue visibility
Users clearly see pending, transferred or failed records.
Resume after interruption
Completed work remains queued without loss when the connection drops.
Shore monitoring
Authorized shore teams monitor last synchronization and pending records.
Audit trail
Creation on device, transfer and server processing remain traceable.
Workflow
- Prepare the vessel: Users, tasks and references enter the local scope.
- Work offline: The crew completes maintenance and operational records.
- Monitor status: The state of records in the sync queue remains visible.
- Reconcile with shore: Transferred records update shared data and reporting.
Operational outcomes
- Continue producing operational records during outages.
- Reduce duplicate data entry later.
- Make synchronization status explainable to crew and shore.
- Maintain access to the correct tasks and document versions onboard.
Frequently asked questions
Does offline mode work with no internet at all?
Tasks, forms and documents already in local scope remain available; new shore data waits until connectivity returns.
How are attachments synchronized?
Record and attachment status can be tracked separately, allowing large files to transfer later based on connectivity.
Which devices are supported?
Scope is planned around web and mobile workflows; vessel devices, browsers and connectivity are validated during the pilot.
When does shore see an offline record?
The record transfers when connectivity returns, is accepted by the server and becomes visible ashore according to user permissions.