Composite complexity is determined by scoring the functions complexity and system drivers for each component (command and telemetry), giving the most weight to system drivers. The FireSat example appears to be satisfied with a "simple" system approach with one exception. The high-speed payload data requirement must be addressed to prevent this requirement from becoming the system design driver. The impact must be evaluated for the mission design. Potential solutions include a separate data link, onboard data compression to reduce bandwidth, and additional research to determine if the ISO Mbps requirement is really needed to accomplish the mission.

The reliability requirement specified for FireSat causes a significant impact on the system design and cost To achieve the desired rating, the systems must be configured redundantly and manufactured using Class S parts. This information, its impact and alternatives, should be fed back into the mission design process as early as possible.

Step 5—Estimate Size, Weight, and Power for Each Component The results of steps 3 and 4 may now be used in conjunction with Table 11-29 to obtain an estimate of the system parameters. The "feel" of the system or the desired design margin will determine the selected value within each zone.

TABLE 11-29. Parametric Estimation of C&DH Size, Weight, and Power. Peak command power will vary by command type, duration, and load. Nominal command power will be higher if ACS drivers are required.
0 0

Post a comment