What a fleet manager's morning actually looks like with real-time risk data

It's 0730. You manage a mixed fleet of tankers and bulkers — five vessels, spread across the Indian Ocean, Med, and Southeast Asia. Your phone buzzed overnight with three chokepoint alerts: Malacca Strait disrupted (disruption score 40), Suez Canal elevated (disruption 30), Strait of Hormuz elevated. You open ArcNautical.

This isn't a hypothetical. I'm going to walk through exactly what a fleet manager sees and does in the first hour of using the platform, using real data from the live system. Every screenshot below is from the actual app, taken today.

---

0730 — The dashboard: what happened overnight

The first thing you see is the global intelligence map. The colored clusters tell you where things are happening right now — green for routine monitoring, amber for elevated, red for active threats. The right panel shows chokepoint status at a glance.

The status ticker across the top is already telling you things: IDJKT → JPTYO risk 35, IDJKT → USSDD risk 43, Malacca Strait 6/9. That last number — 6 out of 9 risk signals active at Malacca — is why it's flagged as disrupted.

You also see 1 piracy incident in the last 7 days and 369 active NAVWARNs globally. One piracy incident in a week might sound low. But you need to know where it was relative to your vessels.

0740 — Fleet positions: where is everyone

You click "Fleet" in the sidebar. Five vessels, shown on the map with their current AIS positions.

The red shaded areas on the map are JWC (Joint War Committee) listed areas — the zones where hull and war risk premiums apply. If any of your five vessels is inside one of those zones, or approaching one, you want to know before your insurer calls you.

The fleet list on the left shows each vessel with its current position, heading, speed, and — critically — its real-time risk context. You can export the whole thing to CSV for your morning briefing email to ops.

0750 — A vessel is approaching the Gulf of Aden

One of your tankers is scheduled to transit from Fujairah to Djibouti. The charterer wants a departure confirmation by 0900. Before you confirm, you need to know what's waiting en route.

You open the Voyage Scorer. Fujairah (AEFJR) to Djibouti (DJJIB). Tanker, laden, 14 knots, VLSFO. Hit "Score Route."

The results come back in under two seconds. Here's what you're looking at:

Risk score 38 out of 100 — MODERATE. Not great, not terrible. But the signal breakdown tells the real story.

What's driving the score

The risk exposure panel on the right breaks the composite score into its individual signals:

JWC at 100 means the route passes directly through a listed area — specifically the Gulf of Aden and Red Sea. That's binary: you're either in the zone or you're not, and this route is. That JWC score is the reason your insurer will charge additional premium for this transit.

Sanctions at 48 is because the route passes near Iran, Yemen, and Somalia — all sanctioned jurisdictions. The scoring engine checks proximity to these countries along the actual route geometry, not just the origin and destination.

0800 — The CII problem nobody talks about

The voyage scored a CII rating of D. For a laden tanker at 14 knots burning VLSFO, that's 1,173.9 MT of CO₂ over 2,222 nautical miles. Under the IMO's tightening schedule (MEPC.354(78)), a D rating in 2026 means this vessel is in the second-worst band. One more notch and it's an E — the "must take corrective action" tier.

A fleet manager isn't just thinking about piracy and war risk. CII compliance affects your commercial viability. Charterers increasingly want C-rated or better vessels. If your fleet is averaging D, you're losing fixtures to competitors with newer, slower, more efficient ships.

The route that's cheapest on fuel isn't always cheapest on risk premium. The route with the lowest risk score isn't always CII-compliant. Fleet management is optimization across all three.

0815 — Checking the alert pipeline

You switch to the Alerts page. This is where you configure what the platform watches for on your behalf.

Alert types you'd typically configure for a five-vessel fleet:

Alert Type	Trigger	Why It Matters
JWC zone entry	Vessel AIS position inside listed area	War risk premium notification to insurer
Piracy proximity	New incident within 200nm of active voyage	Crew and ISPS officer need immediate briefing
AIS dark event	Vessel stops transmitting for >4 hours	Possible equipment failure, sanctions evasion, or distress
Chokepoint disruption	Strait risk score exceeds threshold	Rerouting decision may be needed
NAVWARN on route	New navigational warning along planned voyage	Master needs updated passage plan

Alerts push to your dashboard, email, or webhook. If you use Slack or Teams, the webhook integration means your ops channel gets a message the moment something triggers. No one has to be watching the screen.

0830 — Live tracking: the vessel you're worried about

Your Fujairah tanker isn't the only vessel in a sensitive area. You switch to Live Track to see all five positions on a single map.

The tracking view does something that a raw AIS feed doesn't: it overlays every threat layer on the same map. JWC zones, active piracy incidents, navigational warnings, conflict event clusters. You're not just seeing where your vessels are — you're seeing what's around them.

You can export all positions to CSV (there's a button for that), filter by fleet, or click into any vessel for its full dossier — ownership chain, detention history, class records, the works.

0845 — The decision

Back to that Fujairah–Djibouti transit. Risk score 38 is moderate. The JWC signal is maxed out — unavoidable for this route. Piracy is low (score 8, only one incident in 7 days). Weather looks manageable (score 19). The sanctions exposure is the one that needs a second look, because the AI briefing flagged proximity to Iran and Yemen.

You have 5 route advisories available (the "Route Advisory (5)" tab). These are alternative waypoint suggestions — hug the Omani coast tighter, take the IRTC corridor, adjust the Bab el-Mandeb approach angle. Each advisory re-scores the route so you can compare.

Your decision: proceed with departure, notify your P&I club of the JWC transit, brief the master on the AI risk summary, and set up a piracy proximity alert at 150nm. Total time from login to decision: about an hour.

---

What this looks like without the platform

The same morning, without ArcNautical:

• Check IMB piracy map in one browser tab. No integration with your vessel positions.
• Open NGA warnings list. Search manually for your route area. 369 active warnings — good luck finding the relevant ones.
• Email your broker to ask about current JWC listed area boundaries. Wait for a reply.
• Open a weather service in another tab. Estimate fuel consumption with a spreadsheet formula.
• Call the CII consultant to check if this voyage keeps you in compliance.
• Manually write the risk assessment for your ops report.

That's a three-hour morning. And you're still the integration layer — the person stitching together six data sources in your head and hoping you didn't miss something.

---

If you manage a fleet and your morning looks anything like the "without" version above, I'd genuinely like to hear about it. What's the most time-consuming part of your daily risk workflow? What data source do you wish talked to the others?