Workstations are physical or virtual computers that run an instance of Runtime. Each instance of Runtime must be associated with a single, unique Workstation. They are where the operator monitors and interacts with Runtime.

A Display Layout is the layout that will be shown on a Runtime Workstation monitor. This can contain items such as Maps, controls, Video Viewers, and more. A Workstation can have multiple Display Layouts assigned, and a layout can be used on multiple Workstations.

A Map is a graphical representation of real-world elements. This is commonly a floor plan or a grid containing asset icons. Maps are where you display your Integrated System assets. A project will typically have many Maps. Navigation controls are used to allow the operator to swap between Maps. To add a Map to a Display Layout, you must add a Map Container.

A Legend is a visual key that explains icons and colors representing system statuses. It consists of a canvas displaying status icons. Each Integrated System has associated status icons in the Legend that represent its range of possible statuses. Legends are especially useful when displayed alongside alarms in Runtime, as they make it easier for users to understand the meaning of the colors and symbols. It is also possible to move the Legend across all Display Layout screens in Runtime.

The Drawing tools can be used in Display Layouts and Maps to add shapes, labels and images. It is recommended to use Drawing tools for items that are expected to change, e.g., labels. The Drawing tools are found in the Drawing pane.

An integrated system is a plug-in component that allows a third-party subsystem to communicate with Runtime. Items from the systems can be added as assets. When these assets are added via Designer, their states can be monitored and have commands issued to them.

Collections give users the ability to group items in a project together. This feature simplifies the configuration required and makes it easier to do edits in the future. Many different types of groups can be created. Users can create custom Collections in the Collections menu located under the Home tab. When a Collection is created, it is accessible in the Asset Selection Browser, via Workflow Commands. This Collection can be defined once and used to perform actions in multiple places. Any updates or changes to that Collection only need to be made in one location, making the process more efficient and easier to manage. Additionally, Collections will dynamically update without the user needing to take additional action.

Alarms are used to alert the operator to a potential issue within a facility. For example, a camera that has lost its connection to Runtime. While Designer projects do come with preset Alarm Types, you can add new ones, or change the existing Alarm Types. Creating different alarm types will assist in providing context surrounding an alarm event which is displayed in the Alarm Grid. Alarm postings may then be used to allow only alarms for certain assets to be displayed based on the Workstation.

A Workflow is used to execute a process. This can be a standard operating procedure, automating system actions, and more. There are two types of Workflows: Interactive and Background.

Version Control allows you to create a repository to track changes to your projects. This is useful for if you need to roll back to a previous version, or to keep track of changes when multiple people are working on the project.

Runtime is where projects created in Designer are run. It connects with integrated systems, runs Workflows, manages alarms, etc. A graphical Runtime can be interacted with by an operator on a Workstation. It can also be run as a service instead.

The Language Manager allows the addition and editing of the text displayed in Runtime. This allows a user to set multiple languages on a project for multilingual operators and localize international projects.

Security enables you to create login requirements for access to Runtime and Designer.

The Logging and Reporting application allows the logging and generation of data about activities in the software. Using this application, system events and user actions can be monitored and archived.

Simulation mode is a way to test your design before going live on Runtime. With the Simulation Client you can change the status of assets, trigger Workflows, create command associations for statuses, and view how it behaves. Simulation allows you to test your configuration without having to connect to real devices.

The OPC Tag Database creates a connection to OPC devices using tags — the representation of the OPC variable or datapoint. It provides OPC client functionality for Runtime. This includes the querying of states and execution of commands either locally or remotely.

Enable external programs and users to connect to the IPFusion event stream and send commands to IPFusion Objects.

The Debug Tools are used to assist in troubleshooting issues with your project. It can connect to Designer, Runtime, and running drivers. The Debug Tools display all logging and debugging messages as you work in the project.

Below are topics which include information for best practices when creating projects.