Start with the right scope.
Map the requirements, define an initial product area and agree on a practical route from preparation to pilot.
Explore the approachShip management software
Vessel. Shore.One connected platform.
Technical management, procurement and vessel operations.
One connected direction for your entire fleet.
One platform. Different responsibilities. Technical teams Marine operations Procurement teams Ship managers
The connected maritime platformA complete view.
A complete view.
Not another disconnected system.
Follow the work from equipment and maintenance to purchasing, delivery and vessel records.
Keep every asset, job and decision connected.
Bring equipment, planned maintenance, defects and work orders into a structured technical record — from the engine room to the technical office.
Explore maintenance
OneMarisProduct previewMaintenance overview
WORKSPACEDue this week24
In progress08
Awaiting review03
| Recent work | Assigned to | Status |
|---|---|---|
| Main engine · 500-hour service | Engine team | In progress |
| Cooling system · Condition review | Chief engineer | For review |
| Deck machinery · Planned inspection | Deck team | Scheduled |
| Generator No. 2 · Filter renewal | Engine team | Completed |
Connected records · Assigned responsibilities · Activity history
Product scope & availability
Technical ManagementAssets, maintenance & work orders
Procurement & InventoryPurchasing, delivery & stock
Vessel OperationsVessel and operational records
HSEQ & ComplianceIncidents, audits & corrective actions
Crew ManagementPeople, qualifications & rotations
Drydock & ProjectsProjects, quotations & progress
Performance & EmissionsVoyage data, fuel & emissions
Fleet IntelligenceCross-vessel views & reporting
Technical Management, Procurement & Inventory and Vessel Operations form the core of the platform; the other areas describe the product direction. Contact OneMaris to confirm scope and availability for your operation.
From vessel to shoreDifferent responsibilities.
Different responsibilities.
One operational picture.
Keep the maintenance finding with the requisition, the delivery with the order, and the next action with its owner.
On boardWhere the work happens
The connected recordContext travels with the work
AshoreWhere teams support and decide
01
Clear ownership
Know who is responsible for the next step.
02
Connected context
Keep the original requirement in view.
03
Documented handovers
Retain the evidence behind an action.
04
A wider perspective
Follow a summary back to its source.
The implementation approachBuilt around your operation.
Built around your operation.
Not the other way around.
The starting point is your workflow: the people involved, the records they rely on and the decisions they need to make.
Data & integrationYour records.
Your records.
Their relationships intact.
A proposed migration approach that considers asset structures, work histories and the context behind the data.
Data & integration approachConnected from the source
Technical recordsAssets · Jobs · Supporting documents
Purchasing contextRequirements · Orders · Receipts
PrepareValidateConnect
People & adoptionDesigned for the team
Designed for the team
doing the work.
Role-based guidance and a phased implementation direction, shaped around the realities of ship and shore.
Training & adoption approach01 / UNDERSTAND
Map the workflow.
Identify the people, information and operational handovers.
02 / PREPARE
Start with a pilot.
Define responsibilities, prepare the records and test the scope.
03 / DEVELOP
Build on experience.
Use practical feedback to shape the next step.
Implementation, migration and support are scoped with your team.
ONEMARIS PERSPECTIVESThe work behind
The work behind
every voyage.
People, decisions and the information between them. A closer look at the work that connects vessel and shore.
Discover the platformTalk to OneMarisLet’s map
Let’s map
the way forward.
Tell us about your fleet and priorities.
Vessel. Shore. One platform.A more connected maritime operation.
OneMaris AI
Understand operational records faster. Keep the decision with your people.
OneMaris AI is designed as a controlled assistance layer over platform records: search, summaries and explanations for the records a user is already permitted to see. Actions that change records stay with the user and the platform’s permission rules.
Capabilities on this page describe the product direction, not a released feature set. Availability is confirmed with OneMaris.
Controlled assistance modelSuggests.
Suggests.
Does not change records without your approval.
Reads permitted records, proposes summaries and drafts, and leaves every action to an authorised user.
Product directionNatural-language search Record summaries Technical assistance Procurement assistance Document understanding Controlled drafts
What the assistance layer is designed to do.
Reach the right record without knowing its number.
Questions are written in everyday language; search is designed to run only within the records the user may access and to group results by module.
See a long history in a few lines.
Summaries are designed to be built from the work orders, counter readings, defects and stock movements linked to a record, with the source records kept visible.
Ask about maintenance history instead of searching for it.
Questions are answered in the context of a piece of equipment, with references to the related work orders, defects and stock movements.
Understand quotations beyond the price.
Quotations against the same requirement are summarised side by side. The selection decision remains with the user; the assistant does not choose a supplier.
Read a document next to the record it may belong to.
Context extracted from an uploaded document is proposed against a possibly related record. Linking is a user decision; document content does not update a record on its own.
Prepare a draft before any action.
A draft is not the record itself: the user reads it, edits it and, where authorised, confirms it. No record is created without that confirmation.
Control modelGrounded Permission-aware Human-controlled Traceable
Four principles behind every answer.
Answers relate back to platform records.
Each response is designed to reference the records it was built from, so it can be checked at the source.
The assistant is not above the permission model.
It is not designed as an administrative authority independent of the application’s roles and scopes. Records outside the user’s scope must not become visible through it.
Steps that require an action stay with the user.
Reading, searching, summarising and comparing are separate from drafting, reviewing, approving and executing. The second group passes through an authorised user.
Suggestion and action are kept apart.
In a record’s history, an assistant suggestion and a user action are designed to appear as separate events. Submissions are recorded in the user’s name; the assistant does not submit records.
BoundariesMaritime decision boundary Technical judgement Commercial rules Access scope See our approach
What OneMaris AI does not do.
AI does not replace the master’s or officer’s operational decision.
Engineering judgement, navigational decisions and safety decisions are not delegated to an autonomous layer.
Suggestions do not replace technical decisions or maker instructions.
Summaries do not replace the source records; the related records should be reviewed for detail.
No direct link between the assistant and a purchase order.
Quotation comparison ends in a recommendation for user review. Approval and issue follow the platform’s commercial rules and approval flows.
Example scopes are configured per installation.
Which modules an assistant may read follows the role definition of the installation; no default scope is promised here.
Understand operational data faster. The decision stays yours.
OneMaris AI is designed as a controlled operations assistant that makes records easier to find and understand.