MarshaOS: The Operating System for Gulf Towage and Pilotage

Towage and pilotage billing in Gulf ports runs on a calendar most off-the-shelf software was never built for. The work week doesn't run Monday through Friday — it runs around a Friday-Saturday weekend, with surcharges that shift depending on it. Some charge triggers follow the Hijri calendar, not the Gregorian one most systems default to. And every port — Jebel Ali, Port Rashid, Hamriyah, Fujairah, Ajman — has its own variations on the same underlying rules.

MarshaOS is the OS Series' first entry into marine services — built by Xamun and delivered by BlastAsia — and it's built around a principle that matters more in this sector than most: billing accuracy and operational judgment are two different problems, and conflating them is where marine software tends to go wrong.

Two Minds, Not One

MarshaOS runs on what its team calls a "two minds" architecture. A deterministic billing engine handles everything that touches money — charge calculation, surcharge application, invoicing — using fixed, auditable rules with no AI judgment involved. Alongside it, a separate probabilistic advisory layer helps with dispatch planning, fleet allocation, and scheduling optimization — the kind of decisions that benefit from pattern recognition and recommendation. Critically, the advisory layer never sets or touches a price. It can suggest a better tug assignment; it cannot decide what that assignment costs.

This split exists because marine billing disputes are expensive and slow to resolve, and a rules engine that can drift based on a model's judgment call is a liability in a way that a bad dispatch suggestion isn't. Keeping pricing deterministic means every invoice traces back to a fixed rule, not a probability.

Built for Five Dubai Ports From Day One

MarshaOS shipped with five Dubai-area ports seeded into the system at launch: Jebel Ali, Port Rashid, Hamriyah, Fujairah, and Ajman. Each port's charge structure, surcharge schedule, and operational quirks are configured individually rather than forced into a single generic template — a towage job at Jebel Ali and one at Fujairah can have meaningfully different rate logic, and the system reflects that instead of averaging it away.

Charge-Trigger Automation That Understands the Local Calendar

The billing engine's charge triggers automatically account for the Hijri calendar alongside the Gregorian one, and apply Friday-Saturday weekend surcharges without a human having to remember which jobs fall on which day. For a fleet running vessel movements around the clock, this removes one of the most common sources of billing disputes: a surcharge that should have applied and didn't, or one that shouldn't have and did.

Every charge, once calculated, posts to SAP S/4HANA idempotently — meaning a charge can be resubmitted or reprocessed without creating a duplicate entry, which matters in operations where connectivity or timing issues can otherwise cause a job to bill twice.

Credit Control and Advisory Dispatch

On the commercial side, MarshaOS includes agent credit control, tracking exposure per shipping agent so a port operator isn't extending unlimited credit to a counterparty that's already over its limit.

On the operational side, the advisory layer runs a dispatch and fleet Gantt view with conflict detection — surfacing scheduling conflicts before they become a tug double-booked for two jobs at once — alongside a live geofenced execution map that shows vessel and tug positions against port boundaries in real time.

Built for the People Doing the Work, Not Just the Back Office

Captains, pilots, and customers each get their own mobile app rather than a single interface stretched to serve everyone. A captain checking a job assignment needs a different view than a customer tracking a vessel's ETA, and MarshaOS treats those as distinct products rather than permission levels on one screen.

The entire system — billing engine, advisory layer, and mobile apps — runs with full Arabic RTL support, not as a translated afterthought but as a first-class layout, which matters for a system meant to be used daily by Gulf-based operations teams.

Delivered Through BlastAsia's Engagement Models

MarshaOS is built by Xamun through the Xamun Software Factory and delivered by BlastAsia through its Turnkey or xDD engagement models, with port-specific configuration handled as part of onboarding rather than a generic one-size-fits-all setup.

For port authorities and marine services operators running towage and pilotage in the Gulf, the case for MarshaOS comes down to the same idea that runs through the rest of the OS Series: the rules that are supposed to be fixed — pricing, surcharges, billing — should actually be fixed, deterministic and auditable, while the decisions that benefit from judgment — dispatch, scheduling — get a system smart enough to help without being trusted to set a price.

If you're running marine operations in a Gulf port and want to see how MarshaOS handles your specific charge structure and fleet size, let's talk through your operation.