PWO Marine ERP · Solution

Planned maintenance that stays on schedule — across the fleet

Shore plans. Crew executes. Auto work orders. One audit-ready PMS loop in your ERP.

Calendar and running-hour PM, reusable job plans, Kanban work orders, auto-WO generation, digital execution, and audit-ready reports — integrated with equipment, stores, crew mobile, and AI.

Built for superintendents and vessel engineers who need ISM-aligned traceability, not another spreadsheet.

Last updated: November 2026

Jump to section

The problem

  • PM schedules live in spreadsheets — overdue jobs surface too late
  • Running-hour PM is disconnected from meter readings and runtime logs
  • Work orders are raised after breakdowns, not when the plan says they are due
  • Equipment, BOM/spares, and procedures sit in different tools
  • Drydock scope sits in email and Excel
  • Crew work is on paper or chat — weak audit trail for class and internal audits
  • Result: reactive maintenance, compliance risk, duplicate entry, and crews on paperwork instead of safe operations

The solution: one closed loop

  1. 1

    Equipment register (Technical) → Job plans → Maintenance plans (PMS jobs)

  2. 2

    → Occurrence / scheduler → Work orders (Kanban) → Work log / job cards

  3. 3

    BOM / stores · Service requests / defects · Maintenance history

  4. 4

    Class surveys · Drydock · IoT / CBM (optional)

  5. 5

    Shore plans and monitors. Crew execute on web portal or mobile (offline on Professional+).

  6. 6

    Completions roll schedules forward per tenant policies (planning horizon, missed-WO policy, roll on close).

PMS vs Technical Management

Maintenance (PMS)Technical Management
SidebarMaintenance (PMS)Technical
FocusExecute maintenance: plans, WOs, logsOwn assets: equipment, inspections, drydock
Key routes/maintenance, /work-orders, /maintenance/plans/technical, /equipment, /drydock
AImodule=maintenance, filters pms, manualmodule=technical-management

Shared data model

Both modules use the same equipment register and work order records.

Module map (in-app navigation)

RouteNamePurpose
/maintenanceDashboardKPIs — due plans, open WOs, service requests
/maintenance/plansJob plansPreventive / RH / inspection schedules on equipment
/maintenance/plans/importImportBulk PMS / plan rollout
/job-plansJob plan libraryReusable procedures (linked from WO form)
/work-ordersWork ordersKanban + list workspace, filters, CSV export
/work-logWork logEntries against work orders
/work-log-reportsWork log reportsKPIs, filters, Excel export
/service-requestsService requestsCrew issues → approve → convert to WO
/maintenance/historyMaintenance historyRead-only completions

Core capabilities (detailed)

1Equipment register (foundation — Technical module)

  • Vessel → system → equipment hierarchy with tags, types, categories, function masters
  • Runtime — running hours, AIS-derived runtime where configured
  • BOM / spares on job plans and WOs
  • Import: equipment instances, spares, then PMS plan import

2Job plans

  • Description, checklists, required spares, attachments, labour/tools editors
  • Link to maintenance jobs so every WO carries the same procedure
  • Job Plan PDF for yard/contractor packages
  • Create and edit from maintenance planner UI

3Maintenance plans (PMS jobs & scheduler)

  • Trigger types: calendar, running hours, class survey / inspection-oriented jobs
  • Calendar and list views — overdue, due soon, scheduled
  • PMS scheduler (hourly tick, leader lock in multi-instance deployments)
  • autoGenerateWo — creates WOs when due; at most one open WO per PMS job where configured
  • Catch-up lookback, missed WO policy, PmsCatchUpWorkOrders for planners
  • Roll-forward on completion per tenant rules
  • AI: PMS WO forecast — jobs due soon with autoGenerateWo

4Work order management

  • Kanban board + list view; vessel, equipment, status, priority filters
  • KPI strip; CSV export; saved views via URL params
  • Sources: manual, PMS schedule, inspection, service request, defect, drydock, CBM
  • Digital execution: checklists, photos, labour, measurements
  • Permissions: pms_manage, wo_execute, wo_close, pms:view

5Service requests

  • Crew/shore issues with approval path
  • Convert to WO without re-keying context
  • Dashboard KPIs

6Work log & execution KPIs

  • Structured work log entries per WO
  • Work log reports with filters + Excel export
  • Superintendent audit on who did what and when

7Maintenance history

  • Read-only completed maintenance
  • Trending and audit without altering closed records

8Class surveys & compliance maintenance

  • Survey-oriented jobs alongside statutory/calendar PM
  • Compliance PDF groups: inspection, defect, risk, PTW, audit
  • Pairs with certificate matrix on Fleet

9Drydock (integrated)

  • Drydock plans and work packages
  • WOs linked to drydock plan for yard campaigns
  • Dry dock maintenance report

10Reporting & evidence (25+ PDF types)

  • Job docs: job plan, WO, completion certificate, checklist, spares used, job cost
  • Equipment: maintenance history, running hours, health, calibration, lubrication
  • Compliance: defect, inspection, risk, PTW, audit
  • Fleet & KPI: PMS schedule, overdue, vessel/fleet summary, maintenance KPI, dry dock

Shore + vessel: how teams work together

  1. 1

    Onboard fleet: equipment import → job plans → maintenance plan import

  2. 2

    Daily: maintenance dashboard + scheduler surface due/overdue; auto-WOs per policy

  3. 3

    At sea: crew My Work on portal/mobile — checklists, offline queue (Professional+)

  4. 4

    On sync: shore sees status, work log, rolled next-due dates

  5. 5

    Audit: export vessel/fleet summaries and completion certificates

Integrations

IntegrationBenefit
Crew portal & mobileOffline WO execution; in-app, FCM, SMS when configured
Technical stores / BOMRequired spares on job plans; inventory awareness
Fleet IoT & CBMAnomalies inform or trigger maintenance when enabled
QHSE / SMSDefects, PTW, hazards aligned with maintenance evidence
Compliance notificationsCertificate and maintenance-related reminders
ProcurementPR from stock shortages on jobs (MCP draft PR with confirm)
Marine AILive WO/PMS facts + OEM manual RAG; PMS autopsy on Professional+

AI & MCP for PMS

Tool / factUse
pms_list_work_orders, pms_work_order_kpisOpen backlog and KPIs
pms_jobs_for_equipment, pms_equipment_bomJobs and BOM for equipment
PMS WO forecast (ERP fact)How many WOs scheduler will create
pms_autopsy_work_order, pms_autopsy_vesselDeep operational dossier (Pro+; no financial margins)
Write tools (gated)Create WO, update status, service request, PR — confirm=true

Knowledge pipeline → PMS data

Upload OEM manuals → analyse → extract entities → review → sync equipment, spares, job plans → embed to Qdrant for maintenance-mode chat. Enterprise: PMS manual structured ingest at scale. Import order: equipment instances → spares → PMS plans import.

Who it is for

RoleTypical outcomes
Technical superintendentFleet/vessel KPIs, overdue/upcoming, drydock + class context
Planner (shore)Job plans, imports, catch-up WOs, assignment rules
Master / C/EWOs, checklists, meter readings, work log
Fleet managementFleet PMS summary, maintenance KPI reports
Auditors / class prepCompletion certificates, checklists, PDF catalogue

Business outcomes

MetricBeforeWith PWO PMS
Overdue PM visibilityUnknown until failureDashboard, reports, alerts
Time to create WOsManualAuto from due plans + catch-up
Defect → correctiveAd hocService request → approved WO
Drydock scopeSpreadsheet silosLinked drydock + WOs
Spares readinessGuessworkJob plan parts + BOM/stores
Audit prepRebuild PDFsReport catalogue per job/vessel/fleet

Why PWO — not a standalone CMMS

  • Maritime-native: vessels, class surveys, drydock, fleet KPIs in same ERP as crew, voyage, finance
  • Multi-tenant RBAC: shore vs vessel; vessel-scoped technical permissions
  • Crew-connected: execution syncs to same WOs shore manages
  • Implementation-ready: master data setup docs, import paths, UAT patterns
  • AI-native: live MCP + manuals, not generic chat

Pricing snapshot

PMS is core platform, not a separate SKU—sold per vessel/month. Starter: full PMS loop, work orders, AI + MCP. Professional: mobile offline, CBM (limited), PMS AI autopsy. Enterprise: full CBM, manual ingest, AI Suite, advanced analytics.

View per-vessel pricing

Planned maintenance for real fleet operations

PWO Marine ERP Planned Maintenance System connects job plans, maintenance schedules, and work order execution to the equipment register and BOM used by technical superintendents fleet-wide. A background PMS scheduler evaluates due calendar and running-hour jobs, respects autoGenerateWo and tenant catch-up policies, and generates work orders for planners to assign in a Kanban work order workspace or execute aboard via crew portal and mobile. Service requests feed corrective work without losing vessel context; work logs and maintenance history provide audit-ready trails; 25+ PDF report types support class preparation and management review. Optional Fleet IoT and CBM layers anomaly hints into the same WO model. The Marine AI Assistant in maintenance mode answers with live PMS WO forecasts, open backlog KPIs, equipment-linked manuals, and on higher tiers PMS autopsy reports—always permission-aware and read-only for policy-blocked writes.

PWO Marine ERP supports maintenance workflows aligned with company SMS/ISM processes; class and statutory survey obligations remain with the vessel and recognised organisations. Scheduler behaviour depends on tenant settings and enabled modules. AIS/IoT/AI outputs are decision support.

Related maritime software solutions

Frequently asked questions

What is a planned maintenance system on a ship?

Scheduled maintenance jobs on equipment, executed as traceable work orders with records for audits.

Does PWO support running-hour-based PM?

Yes — maintenance jobs use RH triggers; runtime records meter readings.

How are work orders auto-created?

The PMS scheduler (hourly tick, leader election) creates WOs when jobs are due and autoGenerateWo is enabled, subject to missed-WO and open-WO rules.

What if we missed due dates?

Tenant catch-up lookback and PmsCatchUpWorkOrders support creating missed WOs; policies are configurable.

Can we import an existing PM library?

Yes — maintenance plans import plus equipment/spares import paths.

Kanban vs list for work orders?

/work-orders supports both; filters and export in one workspace.

Can crew work offline?

Yes on Professional+ crew mobile for defined WO workflows.

Is this only preventive maintenance?

No — same WO model covers corrective work from service requests, defects, inspections, CBM.

Does AI create work orders?

MCP can create WOs only with explicit user confirm; default chat is read-only policy.

What is PMS autopsy?

Deep operational dossier for one WO or vessel period—parts, logs, linked requests—not financial margin data.

Relation to class society software?

Supports your survey jobs and evidence export; class systems remain external.

How do I implement?

Demo → vessels → equipment import → job plans → maintenance plans → crew training → go-live.

Put your fleet on a single maintenance record

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.