Skip to content

Technical Reporting

Forms compliance plus engineering insight.

A vessel files dozens of technical forms a month. Two questions matter: Are they being submitted on time? (compliance) and What do the numbers in them actually tell us? (analysis) Most forms-management systems answer only the first. This pipeline answers both, on every monthly submission, automatically.

submission compliancebearing wear-downscrape-down ironICCPrecurring delays

Two views, one pipeline

Submission view → Is each form in, on time?
Analytical view → What do the filed numbers say?

The submission view catches the forms problem. The analytical view catches the engineering problem. They are independent failure modes: a vessel can have 100% submission rate and still have a wear-down problem buried in the deflection report nobody read.

Submission — lateness buckets

For every required form, the pipeline tracks last submitted date, next due date, and lateness. Three windows are reported: previous month, rolling 12 months, and DOC-wise rollup.

WindowBucket
0–7 days lateAcceptable slip
8–30 days lateConcerning
31+ days lateCompliance gap — escalate
Not submittedBlack box — dependent analyses are blind

Submission rate per vessel per period:

Submission rate % = N_submitted_on_time / N_mandatory × 100

Worked example — MV POSUN

End-of-April submission review:

FormLast submittedStatusNotes
ME performance2026-04-05In Order
AE performance2026-04-08In Order
AE LO consumption2026-03-12Late 18 daysRecurring — late 3 of 6
LO shore analysis2026-02-25Compliance gap35 days late
ME bearing clearance2026-04-15In OrderCrosshead 4 wear at 78% — monitor
ME scrape-down2026-04-15In OrderIron 165 ppm — normal
Paint inventory2026-03-30Late 8 daysRecurring — late 3 of 6
Walkie-talkie inventory2026-04-12In OrderAll 8 units OK

Submission rate: 84% — below the 95% threshold, flagged.

Analytical findings routed to other pipelines:

  • ME crosshead 4 bearing at 78% wear → ME performance and PMS for replacement planning.
  • LO shore analysis 35 days late → blind spot on lube oil for the past month, escalated.

What each form tells us

ME bearing clearance — wear-down analysis

Main bearings, bottom-end bearings, crosshead bearings, thrust-pad clearance — measured against the maker’s wear-down curve:

Wear % = (C_measured − C_new) / (C_condemn − C_new) × 100
Wear %Status
≤ 50%OK
50% to 80%Monitor
80% to 100%Plan replacement
> 100%Condemn — must be replaced
ME scrape-down — iron content and liner wear

Iron content from cylinder oil scrape-down samples, residual BN variation, stuffing-box leakage status. Iron content is a leading indicator of liner / ring-pack wear:

Iron contentInterpretation
< 100 ppmNormal break-in
100 to 250 ppmActive wear, monitor
250 to 500 ppmAccelerated wear, investigate
> 500 ppmSevere — engine inspection required

Stuffing-box leakage logged here cross-references the lube-oil consumption variance form.

All forms covered
FormWhat the analytical layer extracts
ME performanceRunning hours, SFOC, Pmax, Pcomp, exhaust temp, feed rate → routes to ME performance
AE performancePer-AE equivalent → routes to AE performance
ME bearing clearanceWear-down % per bearing position
ME scrape-downIron content, residual BN, stuffing-box status
ME scavenge inspectionFeed rate, lubrication, deposit formation, coating thickness, axial clearance
Deflection (ME and AE)Crankshaft web deflection vs tolerance — major-overhaul flag
Lube oil conditionTBN, water content, viscosity, renewal status → routes to lube oil
Lube oil monthlyROB, consumption, FOC, renewal status
ICCP performanceAft / midship / forward current outputs and reference voltages
Motor conditionMegger readings and current draw on critical motors
Paint inventoryROB vs reorder threshold, drydock prep adequacy
Chemical inventoryWater-treatment and cleaning chemicals vs spec
Walkie-talkie inventoryCount, condition, charging — PSC inspectors check this
Month-end consolidatedRoll-up: every analyzed form, worst findings first
Repeat-delay detection

A form that’s late once is a slip; a form that’s been late three months in a row is a process problem. The pipeline surfaces forms that have failed three or more consecutive periods:

RECURRING LATE SUBMISSIONS
ME deflection → Late 4 of last 6 months
Lube oil shore analysis → Late 5 of last 6 months
Paint inventory → Late 3 of last 6 months

Recurring late submissions usually trace to one of:

  • Form owner rotated off vessel, handover incomplete
  • Form moved into master compliance system but engineers not notified
  • Form depends on a sample or measurement that is itself overdue
  • Form deprecated but not removed from the mandatory list

The first three are recoverable with one conversation.

Submission status — code snapshot
def compute_submission_status(forms, today):
rows = []
for form in forms:
last_submitted = parse_date(form.get("submittedDate"))
next_due = parse_date(form.get("nextDueDate"))
if last_submitted is None:
status = {"text": "Never submitted", "color": "red"}
elif next_due is None:
status = {"text": "In Order", "color": "green"}
else:
days_diff = (next_due - today).days
if days_diff < 0:
if abs(days_diff) <= 7:
status = {"text": f"Late {abs(days_diff)} days", "color": "orange"}
elif abs(days_diff) <= 30:
status = {"text": f"Late {abs(days_diff)} days", "color": "red"}
else:
status = {"text": "Compliance gap", "color": "red"}
elif days_diff <= 14:
status = {"text": f"Due in {days_diff} days", "color": "orange"}
else:
status = {"text": "In Order", "color": "green"}
rows.append({
"form": form["name"],
"last_submitted": last_submitted,
"next_due": next_due,
"status": status,
})
return rows
Escalation triggers
TriggerSeverity
Form 31+ days lateCRITICAL
Safety-critical form (lifesaving, firefighting) overdueCRITICAL
Submission rate below 90%HIGH
Repeat delay across 3+ consecutive periodsHIGH
Compliance gap on lube-oil consumption or shore-analysis formsHIGH
Form analytical finding outside spec (e.g. bearing condemn)per finding