[Top] | [Previous] | [Next]

5.2.2 Planning Platform Distribution

Figure 14 indicates a notional functional distribution for a planning workstation. Since the benchmarks indicated that a high-end workstation is capable of handling the load for any single planning application, each planning workstation will be able to run any planning application.

Figure 14. Planning platform distribution.

In contrast to the Commanding and Telemetry applications, there is no need to distribute this functionality across platforms. This is not meant to imply that a single workstation can handle all these applications simultaneously, but rather a single workstation can handle any one application's performance requirements. It is left to the operational concept to ensure that enough planning workstations or servers are available and sufficient computer power is available when a time-critical planning function must be performed.

Clearly, for the Orbit Determination and Attitude Determination functions one can extend the performance benchmarks in a linear fashion if data for multiple vehicles are processed in separate, but concurrent estimation procedures. The problem of concurrent orbit estimation of multiple vehicle states is very complex and difficult to analyze thoroughly. For each mission area, an analysis of needed computer power should be performed.

In addition, Figure 14 should not be interpreted to mean that distribution of these functions cannot or should not be accomplished. On the contrary, distribution of a function such as processing tracking data to a separate workstation or server makes a great deal of sense, especially if a high-fidelity ionospheric model is incorporated at some point.

The service layer components are also indicated as resident on this platform. It is expected that a single workstation will handle all DBMS, HCI, and other support, in addition to single application instantiation. For the most stringent performance requirements this will require a high-end workstation platform. If that performance level is not needed, there is no reason why applications cannot run on a smaller (but binary compatible) platform.

It should be noted that, in the platform distribution diagrams, assignment of functions to platforms does not imply any restrictions regarding where the executable is stored on disk. These allocations are simply meant to indicate a reasonable and workable execution-time arrangement. Network file sharing and DBMS software will ensure that all data (including executables) is available to all platforms.