Maritime Communication Glossary
Key terms and concepts in maritime crew communication, explained clearly.
Augmented Communication
A role-based, AI-supported messaging approach that automatically contextualises alerts and incidents for each crew member based on their position, role, and responsibilities. It reduces information overload and accelerates incident resolution. Coined in the context of maritime crew communication by Shipwize.
Autonomous Maritime Messaging
A messaging system that operates independently of external cloud services, internet connectivity, and third-party push notification providers (Google FCM, Apple APNs). All message routing, delivery, and storage happens onboard the vessel.
Autonomous Push Notifications
Push notifications delivered without relying on Google Firebase Cloud Messaging (FCM) or Apple Push Notification Service (APNs). Shipwize implements this using a local Web Push server running onboard, ensuring instant alert delivery without internet.
FCM (Firebase Cloud Messaging)
Google's push notification service used by most mobile apps to deliver notifications on Android devices. FCM requires internet connectivity and creates a dependency on Google's infrastructure — which is problematic for maritime offline environments.
APNs (Apple Push Notification Service)
Apple's push notification infrastructure for iOS and macOS devices. Like Google FCM, APNs requires internet and creates ecosystem dependency. Maritime platforms must provide alternatives for offline push delivery.
GMDSS (Global Maritime Distress and Safety System)
An internationally agreed-upon set of safety procedures, equipment, and communication protocols for ships. GMDSS covers distress alerting, SAR coordination, and maritime safety information broadcasting. Shipwize complements but does not replace GMDSS.
IMO (International Maritime Organization)
A United Nations specialised agency responsible for regulating shipping. IMO sets standards for maritime safety, security, and environmental performance — including communication requirements codified in SOLAS and the ISPS Code.
Incident Journal
A chronological, tamper-evident log of all communications, alerts, actions, and status updates related to a specific onboard incident. Shipwize automatically generates incident journals for compliance with IMO requirements and ISPS Code.
ISPS Code (International Ship and Port Facility Security Code)
A comprehensive set of measures to enhance the security of ships and port facilities. The ISPS Code requires vessels to maintain communication records and incident documentation — a capability provided by Shipwize's incident journaling.
Janus (WebRTC Gateway)
An open-source WebRTC server developed by Meetecho. Shipwize uses Janus as the media relay for real-time voice and video calls onboard, enabling low-latency communication over LAN without cloud dependency.
Keycloak
An open-source identity and access management solution. Shipwize uses Keycloak for Single Sign-On (SSO), crew authentication, and role-based access control — running locally onboard without internet dependency.
Matrix Protocol
An open standard for decentralised, encrypted real-time communication. Shipwize uses Matrix (via Synapse homeserver) as the messaging backbone, ensuring interoperability, end-to-end encryption, and no vendor lock-in.
Offline-First Architecture
A software design approach where the primary operating mode is offline (without internet), and cloud connectivity is optional. For maritime applications, this means all communication, alerting, and data processing happens onboard.
PBX (Private Branch Exchange)
A private telephone network used within an organisation. On ships, PBX systems connect cabin phones, bridge, and crew terminals. Shipwize can integrate with existing PBX via SIP or fully replace legacy PBX hardware.
PWA (Progressive Web App)
A web application that can be installed on mobile devices directly from the browser — no App Store or Play Store required. PWAs support offline functionality via Service Workers. Shipwize is delivered as a PWA, eliminating Apple/Google ecosystem dependency.
Role-Based Communication
A messaging approach where notification delivery, content, and priority are determined by the recipient's role, department, and position within the vessel's organisational hierarchy. Critical for reducing alert fatigue and ensuring relevant information reaches the right crew members.
SIP (Session Initiation Protocol)
A signalling protocol for establishing, modifying, and terminating real-time voice, video, and messaging sessions. SIP is the standard protocol for VoIP telephony. Shipwize integrates with SIP to bridge existing PBX infrastructure.
SOLAS (Safety of Life at Sea)
The most important international treaty concerning the safety of merchant ships. SOLAS mandates specific communication and safety equipment aboard vessels. Shipwize's incident journaling and alert capabilities support SOLAS compliance objectives.
Synapse
The reference homeserver implementation for the Matrix protocol. Shipwize runs a local Synapse instance onboard each vessel as the messaging backbone — handling encrypted messaging, room management, and user presence.
WebRTC (Web Real-Time Communication)
A set of APIs and protocols enabling real-time audio, video, and data communication directly in web browsers. Shipwize uses WebRTC (via Janus gateway) for voice and video calls — all routed locally over the vessel's LAN.
Stay Updated on Maritime Communication
Get expert insights on offline-first ship communication, Augmented Communication, and maritime software trends — delivered to your inbox.
No spam. Unsubscribe anytime.