Data and security
The office has its own tenant; no other office can see the data, and the database enforces that too. Daily backups with a media archive, a monthly restore drill. If the pilot ends, everything is handed over as Excel and PDF.
MarOps · Pilot programme
One office, thirty days, Excel retired.
For a shipowner's office of four to eight people running one to five dry-bulk vessels on Excel and WhatsApp. Certificate dates live in someone's head, laytime is recalculated by hand for every dispute, voyage profit shows up weeks late.
By day thirty the office does three things in MarOps and does not go back to Excel: certificate tracking, port calls and laytime, noon reports and voyage results. If not, your data is exported and you lose nothing.
Week by week
Four weeks, one working day of setup.
| Week | The office | Oktay | Outcome |
|---|---|---|---|
| 0 · Setup, 1 day | Sends the current crew-list and certificate spreadsheets; provides the vessel list (IMO, flag, MMSI). | Opens the tenant, imports the spreadsheets, checks the flag rules, creates the users. | The fleet's real alerts on the Today screen. |
| 1 · Certificates | Opens the Today screen each morning; closes, snoozes or renews the alerts. | Fixes any wrong threshold in the rule table, not in code. | At least one certificate the spreadsheet had missed. |
| 2 · Port call and laytime | Opens the active voyage and port call, enters the SOF in real time, produces the first laytime statement. | Checks the same SOF against the Excel calculation side by side. | A statement ready to send to the charterer. |
| 3 · Noon and DA | Pastes the master's noon email, reviews the ROB reconciliation; enters the agent's DA proforma and final. | Reads the deviations together, opens the AIS map. | Voyage bunker and port costs. |
| 4 · Result and decision | Completes the voyage result, looks at the performance and emissions screens. | Repeats the measurement, runs the closing call. | Continue, extend or stop. |
Rhythm: one 30-minute call a week; questions in between by WhatsApp, answered the same day.
Success metrics
Measured on day one in Excel, on day thirty in MarOps.
Three operations are timed with a stopwatch on the first day and repeated on the last. The thresholds are written down now and not moved later.
| # | Metric | How it is measured | Threshold |
|---|---|---|---|
| 1 | Port call entry time | One SOF (10–15 events) entered end to end, in seconds | MarOps ≤ half of Excel |
| 2 | Certificate alerts caught | Alerts MarOps raised that the spreadsheet had missed | ≥ 1 |
| 3 | Laytime statements | Statements produced and compared with the Excel calculation | ≥ 2, within 1 hour |
| 4 | Noon report coverage | Reports entered ÷ days at sea | ≥ 90% |
| 5 | Morning routine | The office starts the day on the Today screen instead of Excel (observed in week 4) | 4 of 5 working days |
| 6 | Voyage result delay | Days between the end of the voyage and the profit being visible | ≤ 2 days |
Bonus: the performance or CII screen used as evidence in a charter party discussion.
The day-30 decision
Continue: founding office plan, 39 USD per vessel per month, fixed for 12 months, no setup fee.
Extend: 15 more days on the same terms, only if a single metric fell short.
Stop: data exported, account closed, no charge.