Information that never lands in one place
Figures arrive by email, spreadsheet and message, in whatever format the sender preferred that day. Every status check starts with reassembly, and every reassembly is a chance to transcribe a number wrongly.
Pattern 01 · Maritime operations
When the operational picture arrives in pieces.
Route, performance and daily reporting spread across disconnected inputs, so nobody sees the whole position without assembling it by hand first.
A single validated intake
Normalise the inputs into one schema-validated record at the point of arrival. Unreadable fields get flagged rather than guessed, and the extraction keeps its confidence so a human reviews the uncertain ones instead of all of them.
Decisions stop waiting on assembly
The operational view is current without anyone building it, and questions about where a figure came from have an answer with a lineage attached.
Principles
How I keep it honest.
Flag, don't guess
A field the parser could not read is reported as unreadable. Silently inventing a plausible number is the worst possible outcome in operational reporting.
Validate at the edge
Physical sanity checks catch transposed digits early - a distance and a speed that imply a seven-hour day is a typo, not a voyage.
Keep the original
The raw input is retained alongside the structured record, so any extraction can be audited against what was actually sent.
Next step
Get in touch