The InControl product is typically configured in one of two ways. The first configuration is as a Control Server. A Control Server handles all of the mission-critical telemetry and command processing tasks. The Control Server also supports telemetry archive, operations log archive, hardware interface to the baseband unit(s) and antenna control unit(s), and data persistence between primary and backup sites. Like all InControl software, the Control Server can be hosted on a Microsoft® Windows® platform or a UNIX platform.

The second configuration of InControl is as a thin client known as a Control or Analyst Workstation. This configuration supports the operator interface functions of satellite command and control solutions. These functions include operations log display, alarm conditions, telemetry data display and analysis, commanding menus and procedures, and overall satellite fleet status. While all Control/Analyst Workstations are configured with identical software, each installation can be customized in order to support unique operational concepts. For example, a satellite operations site may dictate that satellite commanding should only occur from a subset of the operation consoles. InControl can enforce this concept by locking out commanding from all other control clients other than those designated for commanding.

The diagram above shows the major subsystem components that comprise the primary ground configuration of a system and includes all of the necessary telemetry and command processing components to support both ground equipment and satellite control. The system also incorporates an internal level of redundancy using primary and backup system servers and workstations to ensure a high level of system availability.