Maritime operations software, built to your workflow.
Vessel operators, port terminals and marine service companies use Genwright to replace the binders, spreadsheets and half-fitting packages holding their operations together. Describe the workflow; get production software on a governed platform in weeks.
Common starting points in maritime operations.
Why maritime operations end up running on binders and spreadsheets
Packaged maritime software is built for the average operator. Very few operators are average.
A coastwise tug and barge operator, a chemical tanker owner, a container terminal and an offshore support vessel company all carry recordkeeping obligations, but almost nothing else in common. Fleet management packages are priced and shaped for deep-sea tonnage. Terminal operating systems assume container volumes most facilities never reach. Maintenance software assumes shoreside connectivity that a vessel three days out does not have.
So the gaps get filled the way gaps always get filled: a spreadsheet on the superintendent's laptop, a WhatsApp group with the masters, a binder in the ship's office, and a week of assembly work every time an auditor or a charterer asks a question the systems cannot answer.
The expensive part is rarely the software. It is the superintendent spending three days assembling an audit pack that should already exist, and the demurrage claim that cannot be defended because nobody can prove when the move happened.
Common first builds in maritime and port operations
Each of these is a scoped starting point, not a product. Genwright builds them against your job codes, your vessel classes and your management system.
Planned maintenance and defects
Equipment registers by vessel and class, jobs scheduled on running hours or calendar interval, defect reporting from the engine room, spares consumption, and overdue escalation to the superintendent ashore.
Safety management evidence
Drills, inspections, non-conformities, corrective actions and certificate expiry — recorded once, attributable to a person and a time, and assembled into an audit pack on demand rather than on request.
Gate, yard and move history
Gate-in and gate-out capture, yard position, damage photographs and a dwell clock that starts when the box actually moves — with a time-stamped history exportable per container for billing disputes.
Voyage and port call operations
Port call checklists, agent instructions, bunker records, statement of facts capture and delay coding, held in one place instead of across email, spreadsheets and a shared drive.
Crew and certification tracking
Crew records, certificate and endorsement expiry, rest hour records, and joiner/leaver movements — with alerts that fire before a certificate lapses rather than after the inspector finds it.
Marine services job management
For repair yards, launch services, surveyors and marine contractors: job intake, scheduling against vessel availability, field capture of work performed, photographs, and billing-ready records.
Three maritime realities Genwright is built around
The link goes down
Crew record work when it happens. The application holds entries locally and synchronizes when connectivity returns, preserving the original timestamp and author rather than the sync time.
Every record may be examined
The platform enforces an audit trail on every record: who created it, who changed it, when, and what the previous value was. It is not an optional module and cannot be switched off per application.
Shore and ship see different things
Master, chief engineer, designated person ashore, superintendent, charterer and auditor each need a different view. Role-based access and row-level security are configured per role, not bolted on later.
Genwright supplies complete, attributable, exportable records. Your safety management system defines what evidence your flag state, class society and charterers require. We build to your requirements; we do not assert that any application is certified against a standard on your behalf.
From a superintendent's description to a vessel in production
- STEP 01
Describe one workflow
Start with the workflow that generates the most manual assembly work — usually maintenance, defects or audit evidence.
- STEP 02
Build in the Studio
Records, roles, onboard forms and escalations are configured against your job codes and vessel classes, then reviewed with the people who will use them.
- STEP 03
Pass pre-flight
Data model, permissions, audit coverage and offline behavior are inspected before anything goes aboard.
- STEP 04
Launch one vessel, then the fleet
Prove it on one vessel or one terminal for a full cycle. Roll out from a workflow that has already carried real load.
Maritime questions we are asked most
Can Genwright replace a planned maintenance system on a vessel?
Yes, for operators whose maintenance workflow does not fit a packaged PMS. Genwright builds equipment registers, job schedules by running hours or calendar interval, defect records, spares consumption and overdue escalation, configured to the operator's own job codes and vessel classes rather than a vendor's template.
Does Genwright work on vessels without reliable connectivity?
Yes. Field capture is offline-tolerant: crew enter records onboard and the application synchronizes when the link returns. Each entry carries its own timestamp and author, so the shoreside record reflects when work was actually done rather than when the connection came back.
Will the records satisfy a Port State Control or class inspection?
Genwright produces complete, time-stamped, attributable records with an enforced audit trail and export to PDF or spreadsheet. Whether a given record set satisfies a specific inspection depends on your management system and flag state requirements. Genwright supplies the evidence; your safety management system defines what evidence is required.
Can Genwright exchange data with our existing systems?
Yes. Applications built on the Knomatic platform can read from and write to external systems over documented interfaces, which is how most operators connect accounting, payroll, telematics or an existing ERP. Integration scope is agreed during scoping because it is usually the part that determines the timeline.
How long does a maritime pilot take?
A typical first build covers two to three workflows on one vessel class or one terminal and runs about four weeks from kickoff to pre-flight review. Fleet-wide rollout follows once the workflow is proven aboard, usually vessel by vessel rather than all at once.
What does it cost to run across a fleet?
Genwright is priced on a platform footprint that scales with deployed users or units under management, not per application and not per field user. Adding a second and third workflow to an existing deployment does not multiply the platform fee.
Bring the workflow that costs you the most time ashore.
A scoping call is a working session with someone who understands vessel and terminal operations. Describe what your superintendents currently assemble by hand, and you will leave knowing what a first build covers and what it costs.