Play 46 · Trade, logistics and hardware
Your ships wait at anchor long enough to foul
A six-step play for an underwater hull cleaning service. It starts from MarineCadastre AIS, stacks USCG PSIX on top, and ends in a message to the vessel operator's technical manager that is useful before anyone replies.
Installs this workflow, five project tables and a draft campaign. Source access and any external outputs are checked before research.
- Category
- Trade, logistics and hardware
- Sources
- 2
- Steps
- 6
The workflow
- TriggerMarineCadastre AISHistorical anchorage durations by vessel
- Evidence
- ArtifactWhat you hand overA per-vessel anchorage history and a cleaning schedule timed to the wait.
- ContactGliderFinds the vessel operator's technical manager, with a verified work email and a phone
- MessageSend itFrom your own mailboxes, evidence attached
Why it earns attention
A hull that sits at anchor in warm water fouls quickly and burns more fuel on the next leg. The wait at anchor is free time to clean it, and AIS history shows how long it is.
The play in six steps
- 01
Measure time at anchor
MarineCadastre AIS- What you pull
- AIS positions at the port's anchorage over the last year: vessel, arrival, departure and days at anchor.
- Why it matters
- Long waits in warm water are when fouling builds. The history shows which vessels wait the most.
ExampleLong Beach anchorage · 6 vessels from one operator · average 9 days per call
- 02
Find the operator
USCG PSIX- What you pull
- Vessel records: name, type, size, owner and operator.
- Why it matters
- The operator decides on hull cleaning and pays the fuel bill.
Example6 bulk carriers · same operator · built 2011 to 2016
- 03
Build the cleaning schedule
Your artifact- What you build
- Each vessel's anchorage history and a cleaning slot during its typical wait, with the fuel cost of a fouled hull as context.
- Why it works
- It fits the work into time that is already lost, which is the easiest yes.
Example6 vessels · next expected calls · cleaning during the wait · no off-hire
- 04
Check before you send
Check the port's rules on in-water cleaning and capture of debris; some ports restrict it. Confirm current operators, since vessels change hands.
- 05
Find the vessel operator's technical manager in Glider
Glider- Search for
- Technical superintendentTechnical managerFleet managerMarine superintendent
- Why them
- The technical superintendent owns hull condition and fuel performance.
- What you get
- A work email and a direct phone, with the email verified before it goes into a sequence.
- 06
Send the evidence, then run the first test
To: the vessel operator's technical managerEvery line comes from a step above Your six bulk carriers2 averaged nine days at anchor per Long Beach call over the last year.1 Fouling builds fast in warm water at anchor and costs fuel on the next leg, so I put together the per-vessel history and a cleaning schedule we can run during the wait, with no off-hire.3 Want to see it?
- Facts from the data (the number is the step)
- What you built for them
- One small ask
- Why it works
- It turns lost waiting time into something useful, using data about their own ships.
- First test
- Five operators with long average anchorage at one port.
- Success looks like
- One cleaning contract out of ten operators.
The sample message is hypothetical and its numbers are illustrative. Verify every claim, date and rule before sending.
Sources used
The two sources this play names. Each links to the other plays that use it.
Related plays
All 63 GTM playsRun this play with Glider.
Deploy the full workflow into a project. Conway checks your scope and source access, builds the evidence, and prepares outreach for review.