Concept demo Illustrative data · not a live system · English-only scope
—

—

My applications

Action needed

Expected calls · next 72 h

002

Pre-Arrival Notification Report

Draft
1 Vessel & voyage
✓ from registry
✓ from registry
✓ from registry
2 Cargo & dangerous goods
Vessel arriving empty (in ballast)
Dangerous goods on board
3 Documents & certificates

Standing certificates are attached automatically from the vessel's certificate vault. Only voyage-specific documents are requested.

    4 Services required this call
    Pilotage & berthing assistance (Form 003)
    Tug assistance (Form 004)
    Waste collection (Form 009)
    Ready to submit — the Port Authority is notified by email.

    Live rule check

    —

    Checked against Port Rules & Regulations Rev 01 as you type.

    Flag, don't block. Findings are recorded and shown to the Harbour Master with the application — they never prevent submission. Any rule can be set to hard-block by configuration.

    Certificate vault

    —

      All applications

      ReferenceFormVesselETAStatusDocument

      Vessel registry

      Particulars entered once, reused on every form
      VesselIMOTypeLOACertificates

      Why this matters

      The Pre-Arrival Notification in the Rules asks for roughly 25 items, most of them standing vessel particulars and certificates that never change between calls.

      Held once in the registry, they are attached automatically to every application. The agent fills only what is genuinely voyage-specific — and the system warns before a certificate expires rather than after a vessel is refused.

      ~25
      items on the paper form
      9
      asked online — the rest are reused

      Application queue

      Ordered by ETA
      RefFormVesselAgentETAStatus

      Issued documents register

      Every approval, sealed and retrievable
      ReferenceDocumentVesselApproved byIssued

      Licensed bunker & STS operators

      Maintained by QSM · drives form validation
      OperatorLicenceScopeValid toStatus

      Registered agents

      CompanyUsersStatus

      Reference data, not code

      Licensed operators, vessel classes, approval roles and the rule parameters themselves are administered from these screens. When the Rules move from Rev 01 to Rev 02 — new notice periods, new required certificates — the change is configuration, not a software release.

      0 documents

      Revision and status shown on every record

      Verify an issued document

      Anyone holding a Shinas Port document — a terminal, customs, a master, a broker — can confirm it is genuine. No account required.

      Legal basis

      Oman's Electronic Transactions Law (Royal Decree 39/2025) gives an electronic signature the same effect as a handwritten one where the system identifies the signer, keeps signing under their control, and preserves the integrity of the document.

      Each issued document therefore carries the approver's identity and designation, the moment of approval, a unique reference, and a cryptographic integrity seal — with the full audit trail retained behind it.

      If a qualified signature is ever mandated, Oman's national PKI (THEQA / TAM) can be added without changing this workflow.

      01 / 08

      —

      —