Independent pre-execution authority for maritime operations

Maritime workflows unified.
Reduce operational and financial risk.

Cargo, vetting, maintenance, crewing, certificates and voyage systems each hold part of the picture. XMA resolves that context across your estate and returns ALLOW, CONDITIONAL or DENY, with traceable evidence, before the digital action executes.

PROPOSED ACTION
COMMENCE_LOADING
Cargo Management proposes to begin loading. Allocation appears valid.
CROSS-SYSTEM CONTEXT
XMA AUTHORITY
Evaluating deterministic policy…
·
Resolving authority.
Deterministic decision · traceable evidence
Built to complement the systems already running your fleet.
Fail-closed by design
Traceable decision record
Continuously valid
Human + machine
Why XMA is different

Existing maritime systems hold the facts. XMA determines whether those facts collectively establish authority to proceed.

Pre-execution

Govern before the originating digital action executes; not after it has already run.

Cross-system

Authority is evaluated across your operational context, not inside one application.

Human + machine

The same authority layer governs human-, application- and agent-initiated actions.

Continuously valid

An ALLOW can be invalidated when the material operational facts it relied on change.

What this looks like in practice

A loading proposal meets the wider picture.

Cargo allocation looks valid on its own. XMA resolves the authority state that lives elsewhere; and finds the condition that changes the answer.

Step 1, Proposal

Cargo Management proposes COMMENCE_LOADING

Within the cargo system, allocation appears valid and the action is ready to proceed.

Step 2, Wider context

XMA resolves the operational estate

Maintenance, vetting, crewing, certificates, terminal and Company SMS authority state are gathered and evaluated together.

Step 3, Authority

A critical maintenance restriction exists

The facts do not collectively establish authority to proceed.

DENY
If the defect arrives after an ALLOW: ALLOW · ACTIVE → INVALIDATED → REASSESSMENT → DENY
Why this matters financially

Stop authority failures before they become operational and financial loss.

Expired certificates, missing evidence and other authority failures can lead to fines, detention and delay. XMA is designed to catch those conditions before the digital workflow proceeds.

Proposed operation

A digital maritime workflow is ready to proceed.

XMA checks authority

Certificate state and required evidence are resolved before execution.

Certificate invalid / expired

The required authority condition is not valid.

DENY before execution

The workflow is stopped before the invalid authority state becomes an operational event.

UK prosecution example

£30,000 fine, plus prosecution costs, after a vessel continued operating for six weeks with an expired Domestic Safety Management certificate.

Source: UK Maritime & Coastguard Agency prosecution report.

Port State Control, 2024

90,381inspections
2,708detentions
~3%detention rate
Source: International Maritime Organization.
Fines Detention Port delay Off-hire Remediation Contractual claims Cargo incidents Insurance consequences
Designed to complement

XMA doesn't replace your systems of record. It reads across them.

Reads the estate, owns none of it

XMA does not need to become the system of record for the underlying operational data. Your existing platforms keep holding the facts; XMA determines whether, together, they permit the action.

Cargo Management Maintenance Vetting Crewing Certificates Voyage / Port Company SMS
Design partner pilot

Start in shadow / advisory mode

Run against selected workflows to validate authority dependencies, integration feasibility, human approval boundaries and measurable operational-assurance value, before production enforcement.

No physical machinery control.

Could a digital operation proceed while a required authority condition exists somewhere else in your organisation?

Let's find out. Start a design-partner pilot in advisory mode against your own workflows.