Satellite Functions

When completed, the following will be an allocation of the functions of a satellite to subsystems. The subsystems and functions have been abstracted at the top level from the ECS-1 communications satellite (Garner and Jones, 1990). The set of functions, denoted by {}, are, thus, representative of a typical satellite, however, they need to be expanded to include all satellites. A similar approach needs to be applied to launch vehicles and space stations in order to cover the current spectrum of space operations.

Communication System

Satellite Segment

Telemetry, Tracking, and Command Subsystem

{encode information}

{perform tracking}

{receive telecommand}

{decode telecommand}

{execute telecommand}

Power Supply Subsystem

{supply power}

Pyrotechnic Subsystem

{fire pyrotechnics}

Attitude and Orbital Control Subsystem

{determine altitude}

{control altitude}

Thermal Control Subsystem

{provide thermal_environment}

Communications Payload

{perform mission}

Apogee Boost Motor Subsystem

{attain orbit}

Subsystem Interfacing Subsystem

{interface subsystems}

Structural Subsystem

{maintain spatial_orientation}

Satellite Integration

{integrate subsystems}

Ground Segment

Satellite Health Control Subsystem

{maintain satellite_health}

Flight Dynamics Subsystem

{maintain flight_dynamics}

Trend Analysis Subsystem

{determine trends}

Structural Subsystem

{maintain spatial_orientation}

Ground Integration

{integrate subsystems}

Note that the functions are derived from the existing system. Once abstracted, they may be allocated to a new system which may be configured quite differently. Note also that a function may be allocated either to the satellite segement, to the ground segment, or to both.

The question arises "Why is there a ground segement? Can't we have a completely autonomous spacecraft?" The answers to these questions provide the real world constraints upon the configuration of the system. Since constraints drive cost, these answers also illuminate important cost drivers.

Since Garner and Jones (1990) provided many functions which cannot be easily allocated to the ECS-1 configuration, the following is an implementation independent listing of functions derived from Garner and Jones (1990). These functions have not been grouped by similarity and near redundancy has not been resolved. The list is under construction and, hence, incomplete.

{construct system}

{test system}

{operate system}

{support system}

{build spacecraft}

{verify spacecraft}

{test spacecraft}

{launch spacecraft}

{make fully_operational_system}

{maintain fully_operational_system}

{operate in_flight_spacecraft}

{control in_flight_spacecraft}

{verify Earth_segment}

{test Earth_segment}

{modify space_segment}

{verify Earth_segment_space_segement_interface}

{define communication_system_programme}

{design communication_system_programme}

{control roll_pitch_yaw}

{stabilize platform}

{manoeuver spacecraft}

{separate_from_launch_vehicle spacecraft}

{manoeuver_into_operational_orbit spacecraft}

{stabilize satellite_spin}

{attain orbital_position}

{control satellite_attitude}

{deploy solar_array}

{configure communication_system}

{establish communication_links}

{point communications_antenna}

{transmit telemetry_signal}

{track orbital_position}

{determine orbital_position}

{maintain orbital_position}

{receive telecommands}

{decode telecommands}

{execute telecommands}

{interface_satellite_to ground_support_facilities}

{}

Bibliographies

Satellite Function Bibliography

---

References

• Garner, J. T. and M. Jones (1990). Satellite Operations: Systems Approach to Design and Control, Ellis Horwood Limited, Chichester, UK.

---

To Design for Competitive Advantage

---

Originated on 951212 | Improved on 951212
Author Ed Dean | Curator Al Motley