Built in Ålesund, for the vessels around it
This is not a general-purpose platform with a maritime skin on it. It was written for offshore support vessels on the Norwegian shelf and the coastal fleet around them, and the decisions show it.
How it is built
Regulations first, then the rules, then the screens
Every module in this product started as a reading of what the law, the class society or the charterer actually requires — the section number, the wording, the threshold — followed by a domain package that encodes it with tests, followed by screens.
It is slower than starting with the screens. It is the reason the drill module answers the 25 per cent departure question instead of sending a reminder, and the reason the permit module cannot be signed out of order.
What we refused
Four things this product will not do
- Read the crew’s messages. No permission grants it, at any level, including ours. A test asserts the absence so it cannot be added by accident.
- Lock a bridge over an invoice. A lapsed subscription stops growth and nothing else. Recording and reading never stop.
- Hide a rest-hour breach behind a rounding rule. A clean-looking month is worth nothing to a shipowner whose master is explaining it to a port state inspector.
- Hold your data hostage. Export everything, any time, without asking us. A customer who cannot leave has stopped being asked whether the product is any good.
Language
English by default, Norwegian throughout
A Norwegian vessel with a Filipino crew needs both, on the same screen, switched per person rather than per company. Every string in the product exists in both languages and a test keeps the two catalogues in step, so a screen cannot ship with half a translation.
The statutory forms — the KS-0300 record of hours of rest, the oil record book print — reproduce their official wording in the language the inspector is reading.