Fleet and office · Module 01
Vessel and fleet register
Every vessel, department, position and person in one register, with one access model over all of it.
ISM Code, clause 3
What it is for
The requirement, and the problem
Most of what goes wrong in a ship management system goes wrong here, long before anyone opens a work order. A person exists twice because two offices typed the name differently. A position has no holder because the previous holder signed off and nobody closed the record. A superintendent can read another owner’s vessel because access was granted per user rather than per scope.
NoRemarks keeps one register. A company owns fleets, a fleet owns vessels, a vessel owns departments and positions, and a position is held by a person for a period with both ends recorded. Everything else in the product — a job, a permit, a rest-hour record, a requisition — points into that register rather than repeating it.
How it works
Three steps, on board and ashore
- 1
Add the vessel
IMO number, MMSI, flag and time zone. The IMO check digit is verified as it is typed, and an MMSI cannot belong to two ships.
- 2
Build the organisation
Departments and positions start from a catalogue named the way a Norwegian offshore vessel names them. Rename or remove any of it.
- 3
Give access by scope
A role is granted for the company, a fleet or one vessel, and ended rather than edited, so what was signed under it still says who signed it.
Example with demo data
What it looks like
A working picture of the module with demo data from the Ocean Pioneer — the same ship you find in the demo.
Try the demo — no account, in your browser, with the PIN 1234.
- Vessel home — what the vessel is, where it is, and what is due
- Company, vessels, positions and users under Administration
- Nordvest Offshore AScompany
- PSV fleetfleet
- Ocean PioneerIMO 9456789
- DeckMST · CO · 2O · AB × 6
- EngineCE · 2E · ETO · MO
- CateringChief cook · steward
- Fjord SupporterIMO 9512345
- Ocean PioneerIMO 9456789
- PSV fleetfleet
co:nordvest/fl:psv/vs:ocean-pioneerDelegated to 08.10In detail
What the module does
Scoped access, not per-user lists
A role is granted at a scope — the company, one fleet, or one vessel. Adding a vessel to a fleet gives the fleet superintendent that vessel automatically, and removes the class of mistake where somebody is forgotten on the way out.
Delegation with an end date
A master can hand the review and signature of the rest-hour records to somebody signed on the vessel — the chief officer, for exactly the master’s two weeks ashore — and the authority ends on its own date, with no standing elevated account and nothing to remember to revoke.
Explicit denial that outranks a grant
Some things have to be withheld from a person who otherwise holds the role. A deny policy sits above every grant, so the answer to "can this person do this here" is one function with one result, and the product asks it rather than checking a role name.
The vessel stays in setup until it is ready
A new vessel is not in service until it has a time zone, departments and a named master. The checklist is part of the domain, not a launch procedure somebody follows, so a half-configured vessel cannot quietly start recording statutory work.
IMO and MMSI checked on entry
The IMO number check digit is verified where it is typed. An MMSI is validated and cannot be claimed by two vessels, because the AIS position of the wrong ship on the right page is worse than no position at all.
A hash-chained audit trail per vessel
Every server-side write is recorded with the actor, the device, the time and the previous entry’s SHA-256. The chain is per vessel, so an inspector can be handed one vessel’s history without being handed the fleet’s.
In the app
On the bridge, on deck and in the office
The same records on a phone in a machinery space and on a screen in the office — with no signal, and synchronised when the link returns.
- Users and their roles, given and ended at the company or on one vessel
- The audit log, readable in the product rather than in a database
The decision
No onboarding project
A shipowner can add its own vessel, its own departments and its own people, on a Tuesday afternoon, without us. There is no implementation fee and no consultant in the loop, because a register that only a vendor can change is a register that stops being true about three months in.
The seed catalogues — departments and positions as they are actually named on a Norwegian offshore vessel — are there to start from, and every one of them can be renamed or removed.
Works with
One product, not nineteen
The fleet office
Every vessel on one screen, the certificate matrix across the fleet, the rotation planner and the relief pool.
ISM Code, clause 12Crew and certificates
Who is on board, what each position must hold, and which certificate expires before the crew change.
FOR-2011-12-22-1523Messaging and notices
Person to person, office to fleet, and a notice whose acknowledgements are counted per version in force.
Arbeidsmiljøloven § 9-5
Put one vessel on it for two months
No card and no implementation project. A company adds its own vessel and its own people on its own afternoon — and if it is not for you, you stop, with your data exported first.