Making the Connection

They used to say that the only way to guarantee successful connection between two systems was to make sure the same vendor’s name was on both. That was often true, until QiSOFT developed ProcessLink.

More than 20 years ago (way back in 1987) we developed each interface separately but then we noticed a large number of common functions were used in each one. We then rationalized the common parts into the ProcessLink program and took the unique parts and turned them into individual device drivers (bear with me, this will all make sense in a bit).

Over the years, our efforts led to a system where every single interface, no matter how complex, would be configured and managed in the same way for easy interpretation by the system administrator.

Today, ProcessLink has become the universal power adaptor for device interfaces and is also very similar in use. Just plug it in and see it go to work. ProcessLink is also flexible and can be used to facilitate data transfer between incompatible systems through bi-directional drivers.

But as powerful and useful as ProcessLink was, we determined in 2007 to upgrade the technology once more. This time we introduced the QIS Interface Console that allowed users to see data flow in its raw state, check the status of a link or even inspect the contents of a file, all from the comfort of an office, armchair or hotel room via a basic network connection.

So now, with one click, you can review every aspect of every interface you have configured including current operations, history logs and current status. Not to mention the ability to readily trouble-shoot any issues without having to physically connect to the servers on which ProcessLink runs.

It’s about being connected, not tied down, for a technological solution that enhances decision making while also simplifying everything you do.

Colin Marney
With QiSOFT Since 1987