Docs

Deployment and Integration Guide

← Back to documents Screenshot of the Eastar Map offline license evaluation dialog

Introduces onboard, shore-side, and hybrid deployment scenarios, runtime environment requirements, and integration flows using NMEA and WebSocket interfaces.

DeploymentIntegration

The deployment model depends on the scenario: a single vessel values offline availability, fleet management values centralized data, and ship-to-shore collaboration requires both ends to exchange data. The three models can be combined.

Deployment models

ModelScenarioNotes
Onboard deploymentSingle-vessel navigation supportRuns locally offline, with chart data and permits updated aboard
Shore-side deploymentFleet and dispatch managementCentralized management of chart and voyage data for unified maintenance
Hybrid deploymentShip-to-shore collaborationOnboard system works offline and synchronizes with shore after berthing
Screenshot of the authorization status summary in the Eastar credential manager
License type, remaining time, and validation states in the credential manager.

Runtime environment

Interface integration

Implementation flow

  1. Requirement confirmation: agree on vessel type, waters, data format, and warning scope.
  2. Environment preparation: confirm operating system, hardware, and network conditions.
  3. Data import: load chart data and permit files and verify coverage.
  4. Interface joint debugging: validate position input and warning event output.
  5. Trial run and delivery: adjust configuration based on the trial run, then deliver.
Specific environment baselines and interface details follow the project technical proposal agreed by both parties.

Continue Reading