MariOS End-to-End Operations Manual

Sign in and open the workbench

1. Open /login, tenant code demo, sign in with a chartering account.
2. Land on the /home workbench and confirm the role shortcuts and widgets.

Master data check

1. Open the vessel / port / counterparty master data pages; make sure there are usable vessels, load & discharge ports and charterers.
2. If a counterparty's sanctions status is blocked, the charter cannot be activated (compliance gate).

Voyage estimate

1. Go to /estimates and create an estimate: pick vessel and counterparty, fill quantity, freight/lumpsum, commissions, voyage days, bunkers and port costs.
2. Hit Calculate to get TCE; clone scenarios for comparison and sensitivity.
3. If you already have an email or chat thread, use “fill from text” to paste it, parse and check each field before it lands in the form (section 6).
4. When happy, run To CP to generate a draft charter.

Page: /estimates

Charter approval and activation

1. Go to /charters and open the charter created from the estimate.
2. State flow: draft → pending_approval → active (no skipping).
3. Once active, the system can link and generate the voyage (depending on seed and chain configuration).
4. For COA scenarios, record liftings on the charter desk; an approved charter amendment raises a domain event that notifies the related teams and raises a finance review task.

Departure and port calls

1. Sign in with an operations account and open /operations/voyages.
2. Move the voyage to in-progress; add load / discharge port calls (order, ETA, agents…).
3. Enter noon reports (position, speed, ROB, next-port ETA); the system can flag ETA deviation.
4. Register SOF events (e.g. NOR) under the port call — use the local timezone.
5. Work through the Closeout tab of the voyage workspace: port-call ATA/ATD, SOF facts, finalized laytime, settled claims, issued invoices, bunker delivery and the TCE comparison — every gap can be turned into a follow-up task.
6. Completing the voyage emits a voyage.completed event, which shrinks the schedule, raises tasks for the missing items and snapshots the TCE.

Fleet twin

1. Open /twin for fleet situation awareness; run what-if simulations (demo grade).

Laytime and demurrage claims

1. Sign in with demurrage or finance and open /finance.
2. Create a laytime statement: link voyage / port calls, enter allowed time, turnaround, demurrage rate and time slices (including excluded time).
3. After Calculate → Finalize, raise a demurrage claim and run negotiate / settle.

Clause library: 10 standard charter-party clause templates ship in (SHINC, SHEX, WWD, WWDSHEX…); charterer-specific clauses can be saved and are auto-applied at calculation time.

Statements print straight to PDF (with company letterhead) and batch-export to Excel.

Port disbursements, bunkers, invoices

1. Port disbursements: draft PDA → submit → approve → FDA (record variance).
2. Bunker orders: inquire → order → deliver, with ROB conservation checks.
3. Freight invoice: draft → pending → issued → partial receipts until paid → supports GL posting.
4. Issuing an invoice or closing a PDA raises a domain event that auto-creates reconciliation / posting tasks (a failed GL posting degrades to a task — never silent).
5. Review dynamic voyage P&L (estimate vs actual vs variance) and AR aging.

Analytics entry: /analytics

AI assistant (Ctrl+J on any page)

1. Press Ctrl+J on any page to open the assistant and ask e.g. “what's the TCE on this voyage?”, “which invoices are overdue?”.
2. Answers are drawn from the signed-in tenant's data and the knowledge base; without a configured model they fall back to the built-in rules engine and are tagged rules — they are never passed off as AI.
3. The assistant can suggest actions and field values, but it never writes to the ledger — confirm back on the page and save.

MariAI chat (/ai/chat)

1. Open /ai/chat, pick an agent (estimate / voyage / market…) and start a conversation.
2. Agents can call read-only tools against tenant data; expand “tool calls” on a message to see the actual query, so you can check the basis.
3. Conversations can be renamed, archived and deleted (to the recycle bin); with no model configured a banner stays visible, and a fallback reply is flagged underneath the answer.

AI Hub (/settings/ai)

1. Tenant admins configure the model provider and model under /settings/ai, test the connection and set defaults.
2. Review usage and quota; you may also bring your own key (BYO key) — calls made with your own key are not billed against the platform quota.
3. Bind skills to modules and configure agents and the skill catalogue; metering is off by default and can be switched on when needed.

Email review and AI landing (/email/review)

1. Sync mail at /email/review: pick a 7 / 14 / 30-day window and a message cap, and browse per folder (inbox / sent items…).
2. The system classifies by business type and extracts fields (vessel, ports, freight rate, laytime…), bodies are converted to plain text and parsed fields carry their source and confidence.
3. Act per type: fixture recap → estimate and charter drafts, disbursement → PDA draft, invoice → invoice draft; you can also confirm a parse, ignore and remember that sender, or archive to a business record.
4. Drafts are reviewed by a human in “pending drafts” before they land; from the detail view you can also “fill into voyage estimate” and carry the parsed values to the estimate page.

AI fill-in for voyage estimates (three entry points)

1. Available on the estimate page /estimates, in the email detail view and in the voyage workspace.
2. Paste an email / chat thread → parse → a per-field card (value, source llm or rules, confidence); tick and edit before applying.
3. “Apply to form” writes vessel, counterparty, cargo, ports and freight rate into the estimate form — still reviewed by a human before saving.

Routine task hub (/routine)

1. /routine has three tabs: pending drafts / routine tasks / skill templates.
2. Every field of a draft carries its evidence; the four-eyes rule requires a second approver before the draft is written back to business tables (the originator cannot approve alone).
3. Routine tasks define a trigger (event / time window), an action and an owning role; they can be added, edited, deleted and run manually. Skill templates hold reusable action sets.

Domain-event automation and voyage closeout

1. Business milestones emit domain events automatically: voyage completed, lifting fixed / completed, charter amendment, invoice issued, PDA closed, bunker delivered, claim settled, NOR updated, laytime draft created.
2. Handlers materialise these into follow-up tasks + in-app notifications + GL posting attempts; a handler error is recorded but never rolls back the business operation (automation failure must not block the business).
3. Before completing a voyage, check the closeout checklist (voyage workspace → Closeout): port-call ATA/ATD, SOF facts, finalized laytime, settled claims, issued invoices, bunker delivery, TCE comparison — missing items automatically become tasks with an owner role and a due date.
4. Approval chains are processed in /workflows/inbox; approval nodes are defined under System settings → Workflows.

Documents and PDF

1. 14 document templates ship in: invoice, credit note, laytime statement, hire statement, fixture recap, estimate / TCE, PDA, statement of claim, SOF, COA, voyage instruction, statement of account, remittance advice, bunker delivery note.
2. Templates carry the company letterhead and can be customised and previewed at /settings/templates; “Export PDF” on a business record exports directly, statements include the letterhead.
3. Renders can be looked up in the document centre and sent from within the app.

Ship management

1. Sign in with a technical account and open /ship: certificates, PMS work orders, defects and crew snapshots (depth varies by license / integration).

Approval inbox

1. Once charters / invoices go pending, process them in /workflows/inbox.

Dashboards

1. Open /dashboards for the role wall; fullscreen and auto-refresh are supported.
2. Fleet Twin supports what-if simulation; the market panel gives freight and bunker price references.