One Platform. Infinite Workflows.
W1 was not engineered for an industry. It was engineered for a way of working — and that is what keeps taking it into rooms that share almost nothing else.
Every AV installation looks different. A television studio, a corporate auditorium and a vessel bridge share almost nothing at first glance — different rooms, different operators, different signals, different budgets.
And yet the same platform keeps being specified across all three. Not because they share an industry. Because they share a workflow challenge.
This case study is the story of how the W1 platform was engineered around that challenge, and how three completely different environments arrived at the same conclusion by starting from the same question: how do our operators actually work?
At Craltech we don't start a project by choosing the products an installation needs. We start by understanding how the people who will use it work. Everything else follows from there.
Flexibility the Operator Defines
A classic KVM over IP system builds its multiview at the source: fixed quads, presets defined by an engineer, changes that require a ticket to the control room. The operator adapts to the system.
W1 inverts that. The multiview lives on the operator's own screen, built by drag-and-drop, saved as personal presets, switched with a single gesture. The interaction itself matters less than the shift it represents: layout ownership moves from the engineer to the operator.
One real deployment illustrates this particularly well. A television production studio inside a major financial institution, with more than twenty W1 endpoints spread across operator workstations and overview displays. What made the platform the natural choice was not the endpoint count. It was that every operator can shape their own canvas as the production evolves — without waiting for anyone.
In a room where the content changes minute by minute, layouts owned by the operator stop being a convenience. They become the difference between the system supporting the work and the work supporting the system.
An Architecture that Fits the Building
Point-to-point AV distribution has a limit. It works while the room is fixed, and stops working the moment a lectern is moved or an office is repurposed. Modern buildings do both.
W1 was designed around this. The platform runs on the standard managed Gigabit Ethernet already installed in the building — no proprietary fabric, no 10G upgrade, no separate cable per source and per screen. On almost every project this turns the infrastructure question into a much shorter one: use what is already there.
Making the controller optional was a similar decision. Simple rooms do not need one, so simple rooms do not have one. That removes a layer of hardware, licensing and single points of failure from installations where it would only get in the way.
This principle shapes a series of corporate auditoriums where any lectern connects through any wall socket, the receiver sits behind the display, and the existing Ethernet handles the rest. A later phase adds automatic standby — the connected conferencing equipment powers down when no signal is present. One small line in a specification. In daily use, it changes how the room feels, what it costs to run, and how long the hardware in it lasts.
Reliability Shaped by the Operator's Day
A platform is only as reliable as it feels to the operator at three in the morning. That is not a metric that fits neatly into a datasheet, but it is often the requirement that decides the specification without ever being written down.
On the bridge of a commercial fishing vessel, the operators are not IT specialists. They are captains, mates and crew, working long shifts in demanding conditions. What matters to them is not what the platform can do in theory. It is how quickly a familiar layout comes back after a restart, a source change or a signal loss.
That shaped the deployment. Layouts stay familiar for crews already used to existing bridge video walls. The interface lives on the operator's own screen, so there is no separate user station to fail or replace. Reliability is measured over years, not weeks. And the feedback loop is short: the people standing at the bridge influence the next iteration of the platform for this market, in both retrofit and new-build hulls.
The objective is not to replace what already works. It is to give the same operators something simpler, more predictable and easier to trust in the day-to-day.
The Common Thread
Three environments that share almost nothing on paper. And yet, when each of them described the system they were looking for, they used remarkably similar language.
Operators wanted the freedom to organise their own workspace. They wanted workflows that stayed familiar, shift after shift. They wanted an infrastructure that could evolve without a rebuild — and systems that stayed simple when the room itself was simple. Above all, they wanted technology that stepped into the background instead of asking for attention.
None of that reads like a feature list, because it isn't one. It is the way people describe technology they trust. Every engineering decision behind the W1 platform was made in answer to something on that list.
One Architecture. One Ecosystem.
A traditional KVM over IP system is a stack — separate encoders, decoders, matrix, user stations, management. Every layer is something to specify, stock, wire and maintain.
W1 collapses that stack into one symmetric endpoint. The same box works as transmitter or receiver, in copper or fibre, on the switches already in the building. Video, audio and KVM travel together. Operators work from a menu on their own screen. A single control PC configures the system once, and stays out of the way afterwards.
The practical effect is subtle but real. A single W1 catalogue covers a broadcast studio, a corporate auditorium and a vessel bridge without changing hardware category. For the integrator, that is one less SKU list, one less training path, one less line in the stock room. For the operator, the system in front of them behaves the same way it did in the last room.
What Each Deployment Teaches
Each deployment feeds the next. The broadcast studio confirmed how quickly per-operator layouts become essential once a team grows past a handful of workstations. The corporate auditorium sharpened the standby and power-management path. The marine environment is shaping the on-screen interface for operators who never think of themselves as users of a KVM system.
None of these projects arrived asking for the same thing. All of them arrived asking for a platform that could adapt. That is what continues to shape the W1 roadmap — not more features, but fewer moments where the system has to ask the operator for attention.
Conclusion
W1 is not defined by the industries it ends up in. It is defined by the way people work — and by the decision to put them in front of the technology, not behind it.
Every deployment teaches something new. Every operator adds another perspective. And every conversation with an integrator refines what the next version of W1 needs to do — and, just as often, what it needs to stop doing. That is how the platform continues to evolve: not around a plan drawn in advance, but around the way real installations behave once the doors open and the shifts begin.
Adapt the technology to the operator. Not the operator to the technology.
More Case Studies
Related Products
