QLF08_LaBel.pdf - 第23页
IC and Component Selection for Space Sy stems – Presented by Kenneth A . LaBel 23 The Risk T rade Space – Considerations for Device Selection (Incomplete) • Cost and Schedule – Procurement – NRE – Maintenance – Qualifica…
IC and Component Selection for Space Systems – Presented by Kenneth A. LaBel
22
Understanding Risk
• Risk for a mission falls in to the same topic areas as parts
selection
– Technical, programmatic, and reliability
• Technical risks
– Relate to the circuit designs not being able to meet mission
criteria such as jitter related to a long dwell time of a telescope
on an object
• Programmatic risks
– Relate to a mission missing a launch window or exceeding a
budgetary cost cap which can lead to mission cancellation
• Reliability risks
– Relate to mission meeting its lifetime and performance goals
without premature failures or unexpected anomalies
• Each mission must determine its priorities among the three
risk types
IC and Component Selection for Space Systems – Presented by Kenneth A. LaBel
23
The Risk Trade Space –
Considerations for Device Selection (Incomplete)
• Cost and Schedule
– Procurement
– NRE
– Maintenance
– Qualification and test
• Performance
– Bandwidth/density
– SWaP
– System function and
criticality
– Other mission constraints
(ex., reconfigurability)
• System Complexity
– Secondary ICs (and all
their associated
challenges)
– Software, etc…
• Design Environment and
Tools
– Existing infrastructure and
heritage
– Simulation tools
• System operating factors
– Operate-through for single
events
– Survival-through for portions
of the natural environment
– Data operation (example,
95% data coverage)
• Radiation and Reliability
– SEE rates
– Lifetime (TID, thermal,
reliability,…)
– “Upscreening”
• System Validation and
Verification
IC and Component Selection for Space Systems – Presented by Kenneth A. LaBel
24
Systems Engineering and Risk
• The determination of acceptability for
device usage is a complex trade space
– There is often more than one answer that’s
acceptable
• A more omnidirectional approach is taken
to evaluate the various risks
– Each of the three factors may be assigned
weighted priorities
• The systems engineer is often the “person in the
middle” evaluating the technical/reliability risks and
working with management to determine acceptable
risk levels