Questions shipowners ask

Approval of an electronic record book is granted by the flag administration to a shipowner, not to a vendor, and it is a conversation between the two of them. What we provide is a record built to the requirements it will be judged against — entries that cannot be altered after signature, corrections made as new entries, a true copy that prints in the statutory layout — and the documentation of how it works, for that conversation.

Everything continues. Jobs are closed, permits are raised and signed, rest hours are recorded and reviewed, the oil record book is written, defects are reported with photographs. All of it queues in a durable outbox on the device.

When the link comes back the device sends what it did and pulls what it missed. Nothing is lost and nothing is silently rejected on arrival, because the rules that would reject it already ran on the device a week earlier.

Yes. Components, jobs, intervals and history come in as ordinary rows — there is no second-class imported data and no reconciliation project afterwards. What takes the time is not the import; it is deciding which of the eleven thousand jobs in the old system are real.

Both, and it is the same code. It installs from the browser to a home screen and runs full-screen with no address bar, and it is packaged for the App Store and Google Play for companies whose device management requires that.

A role is granted at a scope — the company, a fleet, or a single vessel — and the product asks whether this person may do this thing here, rather than what their title is. Delegations expire by themselves and explicit denials outrank grants.

One thing nobody can see, at any level: another person’s messages.

Purchasing produces orders, receipts and landed totals, and everything is exportable in a machine-readable form. A direct integration is a conversation about your specific system; we would rather build one properly than list a hundred logos.

A live feed, bound to your vessel by MMSI, with the MMSI validated and refused if another vessel already claims it. Every screen that shows a position also shows how old it is — live, delayed, stale, or no recent position — because a position shown without its age invites somebody to act on a four-hour-old fix as though it were now.

Email, answered by the people who wrote the code. There is no first line reading from a script, because a chief engineer describing a maintenance interval problem at 02:00 should not have to get past somebody who does not know what a running hour is.