June 1, 2026 · 4 min read
Why cable routing belongs in the cloud
Shipbuilding programs run modern PLM, modern ERP, and modern 3D design — then route cable through a workflow built for one desktop and one engineer at a time. That gap costs real schedule.
Walk through any modern shipbuilding program and you'll see cloud tooling everywhere: document control, scheduling, even the 3D model reviews happen in shared environments. Then you get to cable routing, and suddenly it's one licensed workstation, one engineer with the file open, and everyone else waiting.
This isn't a tooling preference debate. It's a throughput problem with a measurable cost.
The single-seat bottleneck
Cable routing on a typical program is serialized through whoever has the routing seat. Need a route checked? Get in line. Need fifty cables re-routed after a tray change? That's one person's week, and everything downstream of the pull sheet waits.
Cloud-based routing removes the serialization. When routing runs in the browser against one shared database, three engineers can work three zones simultaneously — same project, same live data, no file locks and no "who has the latest export?"
Data integrity is a workflow property
Most routing data problems aren't caused by bad engineers. They're caused by workflows that force data through exports: the routing tool exports to a spreadsheet, the spreadsheet gets emailed, someone edits a copy, and three weeks later the yard is pulling cable against numbers that no longer match the model.
Every export is a fork. Every fork is a future discrepancy.
When the routing platform is the database — when pull sheets and reports generate from live data instead of copies — the fork never happens. That's not a feature, it's an architecture decision, and it's the main reason routing belongs in the cloud rather than on a desktop with an export button.
Design change is the normal case
Routing workflows tend to be designed as if the model is frozen. It never is. Trays move, compartments get rearranged, equipment relocates — and each change invalidates some set of routes that someone has to find and fix.
A cloud platform with live model data can answer "which cables does this change affect?" in seconds, then re-route them in minutes. The desktop workflow answers the same question with an engineer, a spreadsheet, and a couple of days.
What this means for your program
If your routing process involves waiting for a seat, reconciling spreadsheet versions, or dreading model revisions, the problem isn't your team. It's that routing is the last desktop-bound step in an otherwise modern pipeline.
That's the problem Unreal Routing was built to remove.