GraphWorX Application Overview

Visualizations allow you to see and interact with runtime processes and system data via a computer's user interface. A GENESIS installation on a Windows operating system includes a desktop client application, called GraphWorX, that you use to configure front-end visualizations and execute operator visualizations. For operating systems other than Windows, visualizations can be run via a web browser or a mobile application.

There are two variants of the GraphWorX application:

  • GraphWorX Configuration (plus Runtime)
  • GraphWorX Runtime-only

GraphWorX Configuration Application

The GraphWorX configuration application is the design environment that you use to build visualizations. It provides the necessary tools and capabilities for you to build and deploy these visualizations via a robust set of graphical features.

The GraphWorX configurator also includes a built-in run-time execution capability for the configured visualizations. While building the visualizations, this built-in run-time capability allows you to quickly and conveniently test that the visualization will behave as intended for operators. Even if your final deployment is intended for the web or a mobile app, the desktop GraphWorX configurator is the tool used to build the visualizations for all platforms.

GraphWorX Runtime Application

Your intended operator deployment may be for a Windows desktop environment, such as a control room scenario where a web or mobile app might not be needed. In that case, we generally recommend that you use the GraphWorX Runtime-only application to execute the visualizations since run-time operators do not need the ability to modify the visualization's configuration.

The GraphWorX Runtime-only application requires fewer operating system resources to run and is therefore preferred for user scenarios where configuration is not needed.

GraphWorX Deployment Considerations

An operator deployment for desktop GraphWorX has some unique advantages and disadvantages when compared to a web or mobile deployment.

  • Advantages of a desktop GraphWorX run-time deployment:

    • It is less resource-demanding for the GENESIS server because more of the application logic executes on each client machine.
    • It provides access to some more advanced features, such as custom scripting and the ability to embed custom .NET controls into visualizations.
    • It has potentially better client performance (faster screen load times and smoother animations).

  • Disadvantages of a desktop GraphWorX run-time deployment:

    • It can only run on a Windows operating system.
    • It must be explicitly installed (and kept updated) on each client machine that is an operator station. In contrast, a web deployment only requires a standard web browser (and the application stays updated on each client automatically).

It is possible to design visualizations to run on both desktop and web or mobile clients. This may be a wise strategy if your project requires support for both types of client platforms. However, you may decide that setting up desktop GraphWorX run-time stations is not necessary for your application deployment if all the client interfaces will be delivered by web browser or mobile client. In this case, you may use GraphWorX to configure the visualizations but use the web browser or mobile app for run-time operational use.