We introduced our KVM switch solution in 2006. The objective was to get rid of the different keyboard/mouse combinations we had on our desk. We chose not to switch the video since the operators did not want important data hidden from their view. The other problem was that some of the video signals exceeded the capabilities of the KVM switch. So the KVM switch was actually degraded to just a KM switch.

The constant use of the KVM to switch between the applications, keeping track of the mouse and keyboard input focus, was driving me crazy. It didn't really improve the operator efficiency, because in reality we took the keyboard and mouse with us to go and sit in front of the monitor(s) we were focusing on at the moment. I once even initiated an operation on a field device by accident because somehow the mouse was connected to a different application than what I thought.

To make matters worse, the applications started requiring multiple high resolution monitors for displaying the data. Adding additional screens per application, meant our work area grew larger, and we had to constantly roll back and forth on our office chairs to do our job - always taking that keyboard and mouse with us. One day, a colleague threw out his KVM switch and re-installed the multiple keyboard/mouse combinations that were removed over two years ago. It didn't take long for us to follow his example. And there we were revisiting the past by using a dedicated keyboard and mouse for each application server.

Do you remember what came after that for your organization? Keep an eye on my blog: I'll tell you the rest of my story in my next post.

distributed by