FleetView

Context & Problem

A naval operations center tracks dozens of ships at once, and a late or missing update can cause real problems. The tools they use today scatter everything. Hull status sits in one system, readiness scores in another, fault logs somewhere else again. Commanders need one trusted screen that flags urgent problems right away, one that still lets them open a single ship for the details without losing sight of the rest of the fleet. Closing that gap is the problem I set out to solve.

Process

I designed this for two users. A fleet commander needs to see status and progress reports within 30 seconds. A watch officer needs to dig into a single vessel's faults and other issues. Other naval dashboards either crammed too much onto one screen or hid the information that mattered. I wanted to reveal status in stages instead. You start with the whole fleet, filter down by ship type, then open a single ship for the full story. A bar along the bottom keeps the key readings in view the whole time, and I reused the same progress bars, charts, and filter chips on both screens, so nothing feels unfamiliar as you move between them.

Final Design

Scroll to see the full page ↓

Scroll to see the full page ↓

Outcome

When I tested the finished prototype, both of my main users could do their jobs fast. A commander scanning for trouble spotted the offline ship and the struggling one in about eight seconds. A watch officer could reach a ship's GPS fault and clear the alert in three taps. What people responded to most was how the app handles problems. Every state, whether a ship is offline, in maintenance, or running degraded, has its own clear look and its own next step: Recall, Dispatch, or Acknowledge. Reviewers pointed to that as what set it apart from the tools already out there.