|
Background |
The small satellite design philosophy is
different from that employed in large-scale
satellite programs. Small satellite designs have
tighter constraints in both volume and mass
compared to larger satellite. The limited volume
adds design constraints and limits the
possibility of adding complex spacecraft (S/C)
systems as required for larger platforms.
Subsystems are designed or procured according to
their low volume, ease of integration, low mass,
and power consumption, rather than on their
reliability. Furthermore, redundant systems are
often bulky and not included unless they are
absolutely necessary. Trade-offs in design
practices do not always lead to a more reliable
S/C, but the lower cost approach generally
allows a higher tolerance for risk and
reliability trade-offs. Simpler system designs
allow for much shorter development times. The
design characteristics of small satellites make
them particularly attractive as an initial
option for building space capability within a
nation.
Even though small satellites are generally
considered to be less complex, cheaper, and
faster to develop, there are many programmatic
considerations that need to be understood and
addressed. This tutorial will help participant
understand the principal considerations needed
to develop a small satellite program.
There are many decisions and trade-offs to
consider for creating a mission. It is important
to ensure that attention is given to all phases
of the mission: concept exploration, detailed
development, production and deployment,
operations and support, and the end-of-mission
life. |
|
|
|
|
About |
|
|
|
Key Features |
 |
Introduction to the CubeSat
Standard |
|
|
Critical CubeSat characteristics |
|
|
Strategies for successful
CubeSat development |
|
|
CubeSat launch Process |
|
|
Organizers |
 |
|
|
|
|
