RemoteAccess

Not every source in a control room is a physical box in the equipment room. Virtualised applications run on servers, yet they need to be accessible at the workplace — in the same source list, under the same rights management.

That is exactly what the RemoteAccess CPUs do: they occupy a port on the matrix system and provide a virtual machine there. This is how hybrid installations of physical and virtual computers are built.

Important for planning: access to a virtual source behaves differently from a KVM connection to a physical computer. Latency is higher and perceptible, and the image is not pixel-perfect. For monitoring, administration and occasional intervention, this is the right route; where delay-free operation and exact image reproduction matter, a physical computer with a computer module remains the right choice.

The variant follows your matrix world:

• RemoteAccess-CPU for dedicated matrix systems
• RemoteAccess-IP-CPU for KVM-over-IP matrix systems

Both are available for CAT cable as well as multimode and singlemode fibre. The UG variants additionally transmit HID devices — keyboard, mouse and comparable input devices. Smart cards and mass storage are not included.

The RemoteAccess-GATE is a standalone device that sits between your KVM system and the network world. GATE stands for "Global Access to Enterprise": it makes your KVM installation reachable for users who are not in the building — for on-call duty, distributed sites or manufacturer support.

Access runs through a web or software client. No additional hardware is required at the remote workplace.

The RemoteAccess-Workplace is the optional hardware counterpart. It becomes worthwhile where several RemoteAccess GATEs are in use: it consolidates the connections at a fixed workplace and adds multiviewer functionality, so several sources can be shown on one monitor at the same time. For occasional access by a single user, the client is enough.

Both terms involve a network, but they mean different things:

KVM over IP is the transmission route within your installation. The network replaces dedicated matrix hardware; operation remains that of a local workplace.

RemoteAccess-GATE is the route outward. It is not about how signals travel inside the system, but about who can reach it, and from where.

A KVM-over-IP system therefore does not need RemoteAccess, and a dedicated system can use it. The two decisions are independent of each other.

• I want to access my control room while travelling. Which product do I need?
  The RemoteAccess-GATE. Access runs through a web or software client, with no additional hardware required. The RemoteAccess CPUs do not provide this — they work in the other direction and bring virtual sources in.
• When do I need the RemoteAccess-Workplace?
  When several RemoteAccess GATEs are in use, or when several sources need to be visible simultaneously at a fixed workplace. For individual access, the client is enough.
• Do I need a KVM-over-IP system in order to use virtual machines?
  No. Dedicated matrix systems use the RemoteAccess-CPU, IP matrix systems the RemoteAccess-IP-CPU. Both worlds can integrate virtual sources.
• Can operators tell a virtual source from a physical one?
  Yes. Latency is higher than on a KVM connection to a physical computer, and the image is not pixel-perfect. In terms of operating logic, however, the virtual machine is a source like any other.
• Can I use USB devices on a virtual source?
  The UG variants transmit HID devices such as keyboard and mouse. Smart cards and mass storage are not supported on virtual sources; for those you need GenericUSB on a physical computer module.
• How many ports does a RemoteAccess-CPU occupy?
  One — like a computer module for a physical computer. It counts accordingly in your port or licence planning.