Short definitions written to make sense on their own, and the questions we are asked most about FleetView OS.
The APA is a sum the charterer pays before a yacht charter to cover running costs during the trip, such as fuel, food, drink and berthing.
A cruise file is the FleetView OS record of a single charter or cruise.
The flag state is the country where a vessel is registered.
The ISM Code (International Safety Management Code) is the international standard for the safe operation of ships, made mandatory by SOLAS Chapter IX.
An MMSI (Maritime Mobile Service Identity) is a unique nine-digit number that identifies a vessel's radio equipment.
The MYBA charter agreement is the standard contract for crewed yacht charters, published by MYBA The Worldwide Yachting Association.
P&I (protection and indemnity) insurance covers a vessel owner's liability to third parties, such as injury to crew or guests, damage to other vessels or property, pollution and wreck removal.
A planned maintenance system (PMS) is a schedule of every recurring maintenance job on a vessel, triggered by calendar date or by running hours, with a record of what was done and when.
A refit is a planned period of major work on a yacht, beyond routine maintenance, such as repainting, replacing teak decks, overhauling engines or renewing interiors.
Running hours, also called engine hours, are the total time an engine or generator has operated.
Yacht management is the professional running of a yacht on the owner's behalf.
FleetView OS is the custom management system FleetView Marine builds for each client, around how that operator runs its yacht or fleet. It can include any feature the operation needs; common ones are documents, maintenance, issues, cruise files, crew management, the logbook and finances, and the Fleet Copilot, an AI assistant that answers questions about the fleet and writes a daily brief.
FleetView OS is for yacht managers at management companies and for captains who run a single vessel. Each gets a system built around their work: a manager sees every vessel on one page, a captain sees their own boat, its paperwork and its plan.
Yes. A captain can hold their own account and run one vessel on it, or be given access by the management company that runs the boat.
No. Each FleetView OS is specified and budgeted for one operator, after a discovery meeting and a pilot. Use the contact page to start.
FleetView OS is a web app. It opens in a browser on a desk and on a phone at the dock, with nothing to install.
Your fleet's data is hosted in the European Union.
The Fleet Copilot reads the same vessels, documents, cruises and costs as the rest of your system, so its answers are current and specific to your fleet. It shows which records it consulted. Like any AI assistant it can make mistakes, so anything important is worth checking against the record it cites.
A project runs in five steps: discovery, assessment, pilot, specification and budget, then implementation and onboarding. In discovery we learn how you run your boats and where time is lost. In the assessment we tell you plainly whether a custom system would help; sometimes the better answer is a change of routine or of who does what. In the pilot a working system runs on your yacht or fleet and we work out together what can be automated. Then we set out what your FleetView OS will do and cost, and once you approve, we build it and bring your team onto it. There is no self-serve sign-up.
Every project starts with a conversation about how you run your boats. If new software is not the answer, we will tell you.
Get in touch
