Fleet and vessel management
A shore-side record of vessels and the organization around them: which vessel is which, how it sits in the company, and the operational context a coordinator should not have to rebuild from calls and spreadsheets.
SoftMarin
SoftMarin is being built so a maritime company, its vessels, and the people who run the work can share one operational picture — including when the vessel is not continuously online.
Maritime work is split across a shore office and vessels that move. The records those groups depend on — people, equipment, stores, safety tasks, training, and reports — are often kept in separate files. SoftMarin’s vision is to connect that work in one product, with a deliberate path for data between ship and shore.
The intended users are maritime companies, vessel teams, and the shore staff who coordinate them. This page describes that intent. It does not name customers or claim that a fleet is already running the product in production.
Each area below is part of the product being engineered. None of them is presented here as generally available or commercially proven. Current status of a module is confirmed directly with MYSWARE.
A shore-side record of vessels and the organization around them: which vessel is which, how it sits in the company, and the operational context a coordinator should not have to rebuild from calls and spreadsheets.
People, assignments, and the documents attached to them. The aim is a clear view of who is assigned where, and which records are approaching a date that matters.
Plans tied to equipment, with calendar or running-hour rules and a history that is still readable after the job is closed.
Safety routines and compliance tasks treated as tracked work, so an obligation is visible before it is only a file in a folder.
Parts and stores held against a vessel: what is on board, what has been used, and what has been requested.
Training requirements and completed records kept with the person they belong to, so a gap can be seen before it becomes a finding.
Operational reports drawn from the records the team already keeps, instead of rebuilt by hand for each period.
A defined exchange between vessel and office, including how data waits when the link is down and how it catches up when the link returns.
Desktop software for essential vessel-side work that does not assume a continuous connection. Synchronization is a separate, deliberate step.
Ship-to-shore synchronization is a design requirement, not a slogan. The product has to say what happens when the link is absent, what is stored on board, and how the two sides converge when the link returns.
Offline-capable desktop operations exist so essential vessel-side work does not wait on a continuous connection. The desktop is part of the same product thinking as the shore-side web application, not a separate export of a spreadsheet.
SoftMarin is in active development. This website distinguishes production use from the development scope by declining to claim production use.
There is no published launch date, customer count, or compliance certificate on this page. softmarin.com is the product website. Questions about a module belong on the contact form or at admin@mysware.com.