The NYC Ferry fleet had 38 vessels. Every one of them had functional IT infrastructure. And almost none of it was the same.
Access points were falling off walls. Cables were disorganized. Configurations varied from boat to boat. External cellular antennas were outdated or installed differently on every vessel. When something broke, the team had to first track down which vessel, then figure out that specific boat's setup from scratch. And only one team member had the knowledge to fix most problems, creating a dangerous single point of failure across the entire fleet.
The operation was struggling to meet its 95% uptime KPI required by the city contract. Something had to change.
The Real Problem Wasn't Technical
The instinct in IT is to start with the technology. New access points. Better switches. Faster connections. But the core problem on the NYC Ferry fleet wasn't that the equipment was bad. It was that nothing was consistent.
When every vessel is configured differently, you can't build procedures. You can't train people efficiently. You can't troubleshoot quickly because the first step is always figuring out what you're looking at. And you can't scale, because adding a new vessel means inventing a new setup from scratch.
The consistency problem was creating the knowledge gap, which was creating the single point of failure, which was creating the uptime problem. Fix the root cause and everything downstream gets better.
How We Did It
I led a 15-person team through an 8-month standardization effort covering all 38 vessels. The catch: we had to do it while simultaneously running daily operations. These ferries don't stop sailing because IT needs to rewire a rack.
We started by creating physical installation standards. Exact rack layouts. Exact cable management. Exact AP mounting positions. If you opened the IT closet on any vessel, it should look identical to every other vessel in the fleet.
Then we standardized every configuration. Firewalls. Cisco switches. Netgear switches. NVRs. Access points. Destination route systems. The onboard passenger-facing media displays that show route information and announcements. Every device, every config, every setting, documented and uniform.
Training by Doing
I didn't hand my team a manual and send them out. I worked side by side with them on the first vessels. We did the installations together so they could see the standard being built, ask questions in real time, and understand not just what we were doing but why.
After the first batch, I broke the team into smaller groups to scale the rollout across the fleet. Each group followed the same standard, and I maintained a QA process throughout to make sure nothing drifted. When you're standardizing 38 vessels, the temptation to take shortcuts grows with every boat. The QA process was the guardrail against that.
What Changed
The single point of failure disappeared. Any team member could now walk onto any vessel and troubleshoot effectively because every configuration was identical. The knowledge that used to live in one person's head now lived in the standard itself.
Passenger-facing systems became consistent across the fleet. Route displays, announcements, and media systems all worked the same way on every boat. That matters when you're operating a public transit system with a city contract.
And the number that mattered most: the SVP of operations hit the 95% uptime KPI required by the city contract. That wasn't just an IT win. That was a contractual obligation that the entire operation depended on.
What I Took Away
Standardization before optimization. There's no point improving systems that are all configured differently. Get them consistent first. Then you can improve them all at once.
Work alongside the team. The first vessels matter the most. That's where the standard gets tested, refined, and internalized by the people who will execute it without you.
QA is not optional at scale. 38 vessels across 8 months with 15 people means a lot of hands touching a lot of equipment. Without a quality process, standards erode before the project is even finished.
Eliminate the single point of failure first. The most dangerous thing in any operation is knowledge that exists in only one person. Standardization is how you move that knowledge from a person into a process.
The NYC Ferry standardization became the blueprint for everything that came after. When we later tackled global standardization across 167 vessels and 83 offices, the methodology was born here, on 38 ferries in New York Harbor.