Using noon reports
How the master files the day and how the shore approves a report that failed yesterday’s checks.
The noon report is the ship’s daily account of position, speed, distance, fuel and the weather. The master on board speaks it or types it. The superintendent ashore approves the reports that the checks have flagged. Emissions, the voyage module and finance all read these figures later. They do not keep a second copy of the fuel.
Dashboard and pages
Noon reports is http://localhost:4400/app/noon . A 14-day grid shows whether each vessel reported. Flagged reports wait for approval. The page also shows how many minutes after noon the report arrived, and by which channel. Each row has the position, speed, distance, fuel used, fuel and lube remaining, wind and sea, how it was reported, and any check that failed against yesterday.
Voice agent is http://localhost:4400/app/noon/voice . It shows a spoken report, the form filled from it, and the questions the agent asked about gaps. Integrations is http://localhost:4400/app/integrations/noon .
http://localhost:4400/app/noon/port-calls only redirects to the port module. Shipment files and containers are cargo, not noon.
Workflows
Approve needs publish (noon.approve). The button is Approve. It accepts the day’s figures after the checks against yesterday. The approver and the time are pinned by the database. In the demo, Kaan Erdem and Maren Holt have publish on noon. Ravi Menon and Capt. Erdem Yılmaz have edit, so they can work the report and cannot approve it. Watchkeeper has edit and cannot approve either. view is enough to read the grid.
Shared records
Fuel used and remaining on board start here. The emissions ledger, the voyage result and the finance OPEX chart read them. The port call used to be listed on this page. It is now the port module’s record. Cargo files hang off that call, not off the noon report.
What the demo simulates
The voice agent is a prepared demo. No LiveKit call is made. Weather from Stormglass is not fetched. The numbers are generated, including the January fuel spike from heavy weather in the demo story.
Integrations
LiveKit, WhatsApp and Stormglass are mocks. See Connections and the module reference.