PWO Marine ERP · Solution

Vessel management ERP system—every ship's data in one controlled database

From registry and equipment to work orders, port calls, and vessel P&L—scoped by vessel, rolled up for the fleet.

Last updated: November 2026

Jump to section

ERP modules scoped to each vessel

Vessel master & identity

  • Vessel record: name, IMO, type, flag, operational status
  • Links to all child records (equipment, stores, assignments, voyages)
  • Compliance matrix per vessel for statutory and class-related certificates

Technical asset structure

  • Equipment hierarchy and function masters
  • Equipment types, categories, BOM/spares
  • Runtime and meter readings; optional IoT tag linkage
  • Technical documents attached to equipment

Maintenance (PMS) on the vessel

  • Job plans tied to vessel equipment
  • Work orders filtered by vessel in Kanban workspace
  • Maintenance history and work log entries per ship
  • Service requests raised onboard or from shore

Stores & procurement per vessel

  • Vessel-specific inventory locations and warehouses
  • PR/PO/GRN with vessel dimension on lines
  • Critical stock visibility in reports and AI answers

Crew on board

  • Assignments and roster for the vessel
  • Rest-hour records under MLC rules
  • Crew certificates relevant to posting

Operations timeline

  • Active and historical voyages and port calls
  • Noon reports linked to voyage
  • SOF and operational documents

Finance at vessel level

  • Vessel P&L and allocation views (with finance:view)
  • AP/AR documents can reference vessel context
  • Charter revenue/cost alignment where configured

Why "ERP" matters for vessel management

A CMMS-only tool tracks maintenance. A vessel ERP also connects procurement spend to maintenance jobs, crew cost and rest compliance to operations, charter utilization to financial reporting, safety incidents and PTW to audit evidence, and documents and manuals to equipment tags.

That integration reduces re-keying and gives auditors a single chain of evidence from event → work order → parts → invoice → journal.

Governance, approvals & audit

  • Role-based permissions (finance, payroll, QHSE, IoT, AI admin, chat)
  • Approval workflows and approval inbox for procurement and finance
  • Enterprise attachments on invoices and journals
  • System monitoring: user activity, event logs (Enterprise tier)
  • Audit readiness module for findings, CAPA, evidence packs

Vessel context in AI

Chat accepts vesselId, equipmentId, and workOrderId so answers stay ship-specific. MCP tools accept optional vessel scope. Finance and payroll facts respect JWT permissions.

  • “Open critical work orders on this vessel”
  • “Certificates expiring in 90 days for this fleet”
  • “Charter contracts active for this ship”

Deployment & scale

ModelDescription
SaaSMulti-tenant cloud, per-vessel subscription
EnterpriseSSO (SAML/OIDC), private cloud/on-prem, tailored MSA
EdgeOptional IoT gateway agent per vessel for telemetry

Scale by license

Add vessels by license count; fleet calculator shows monthly total on the pricing page.

Related maritime software solutions

Frequently asked questions

What is a vessel management ERP?

An ERP that models each ship as an operational and financial entity within a shared fleet database.

How is this different from fleet management software?

Fleet management emphasizes rollup visibility; vessel ERP emphasizes per-ship transactional depth—both exist in PWO Marine ERP.

Can one user access all vessels?

Yes, if permissions allow; data is still filtered by tenant and role.

Multi-currency finance?

FX rates and sync supported in finance suite (tiered features).

Vessel acquisition accounting?

Vessel acquisition module in finance for capex scenarios.

Equipment import from Excel?

Equipment management import for instances, spares, and PMS plan import paths.

Separate DB per vessel?

No—logical isolation by vessel_id in a secure multi-tenant Postgres schema.

API access?

REST API and MCP for integrations; Enterprise emphasizes custom integration queue.

Offline on vessel?

Crew mobile offline for defined workflows; core ERP is web-first.

Implementation time?

Depends on vessel count and masters; onboarding SLAs: 1/2/5 days by plan tier.

See vessel ERP in action

Walk through with your vessel types, superintendent workflows, and compliance context in about 30 minutes.

PWO Marine ERP supports maritime operations and compliance workflows; statutory obligations remain with the company DPA, master, and flag/class requirements. AIS and AI outputs are decision support only. Features vary by subscription tier.