Multi Attribute Front End For Effective: Tradespace Exploration As Space System Design
Multi Attribute Front End For Effective: Tradespace Exploration As Space System Design
Front End for Effective Space System Design
9 October 2009
2LT. John Richmond
Greg O’Neill
Jorge Cañizales Diaz
MATECON
“MultiAttribute Tradespace Exploration with
ConCurrent Design”
• What does it mean?
• Applying a series of decision metrics (attributes)
that consider the integration of all stakeholder
requirements to generate a framework
incorporating all qualified designs and indicating
the most viable candidates.
9 Oct 2009 2
Taxonomy
• MATECON buzzwords
Decision Maker Person who makes decisions that impact a system at any stage
of its lifecycle
Design Variable Designercontrolled quantitative parameter that reflects an
aspect of a concept
Design Vector Set of design variables that, taken together, uniquely define a
design or architecture
Attribute Decision maker perceived metric measuring how well a defined
objective is met
metric space
9 Oct 2009 3
Index
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 4
Index
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 5
Context of MATECON
Selection (MATE).
System Architecture
• Includes aid for Concept Generation
Requirements Definition
Tradespace Exploration
• Plunges forth and back Concept Selection
Human
into Design (CON), to Factors
Design Definition
win accuracy. Multidisciplinary Optimization
9 Oct 2009 6
Context of MATECON
• Inputs:
Requirements
• Important Stakeholders. Definition
• Set of different
System Architecture
Concepts.
Concept Generation
• Outputs:
Tradespace Exploration
• System requirements for Concept Selection
9 Oct 2009 7
Index
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 8
Implementing MATECON
Architecture-level Analysis
True
preference
space Key decision
1a makers
2a User
MAUT
Design-level Analysis
4 Simulation (e.g. X-TOS) Customer
Designlevel Analysis
9 Oct 2009 9
Index
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 10
“MATE” Overview
Stakeholderi Stakeholderi
Single Attribute
System Preference Interview Repeat for each Utility
Stakeholder Formulation
Single Attribute Repeat for each
Utility Interview Stakeholder
Defining the System
Preferences Multi
Corner Point Interview Attribute
Utility
Formulation
Define the System Generate MultiAttribute
Attributes for Utility Functioni
Stakeholderi
Tradespace n
Utility
Attribute Utility
Remote Sensing Mission
Communications Attributes
Satellite
RANK 4 3 1 2
Data Continuity
Revisit Rate Mission Duration LTAN Timing
(System Availability)
Units hour year % minute
Range [24, 1.5] [5,15] [30,100] [240,5]
Utility Form decreasing increasing increasing decreasing
Range [least acceptable value : most realistic, desirable value]
Rank 1 = most important attribute, 4 = least important attribute
2. Outcome of Single Attribute Utility Interview
Attribute Utility
Revisit Rate: Single-Attribute i Function Attribute j
System Availability: Single-Attribute Utility Function
1.0 1.0
0.9 0.9
0.8 0.8
0.7 0.7
Utility
Utility (-)
Utility (-)
0.6 0.6
0.5
Utility
0.5
0.4 0.4
0.3 0.3
0.2 0.2
0.1 0.1
0.0 0.0
30 40 50
0 5 10
Attribute
Revisit
15
i Axis
Rate (hours)
20 25
Attribute j Axis80
60 70
System Availability (%)
90 100
9 Oct 2009 12
Generating Single Attribute Utility Curves: The Lottery
Select the
Select another Calculate the Indifference Select another Preferred
Attribute Value Probability Value
Utility Point Point Situation
(Repeat for at least 7
Attribute Values)
Situation A Situation B
Attributei Attributei
Prob. = 0.5 (@ value) Prob. = P* (@ best value)
OR 0 ≤ P* ≤ 0.5
Method (LEP) Scenario
• Purpose: To provide context for the interviewee when selecting whether they prefer the outcomes of
Situation A or Situation B in the LEP Situation Setup.
• Example Interview Scenario
• Attribute: resolution, Attribute Value: 4 Megapixels, Attribute Range: 17 Megapixels
“A new optical system has been developed for a satellite that provides a higher amount of image
resolution. If this optical system is used there is a chance that it could provide 7 Megapixel images versus
only 4 Megapixel images when using a traditional optical system. However, the new optical system
employs the use of state of the art glass manufacturing so there is a chance that the new optical system
could lead to reduced image resolution (as compared to a traditional optical system). A team of engineers
has studied the issue and determined that this new optical system has a P* chance of providing images
with a 7 Megapixel resolution, or a (1P*) chance of providing images with a 1 Megapixel resolution,
while traditional optical systems will provide images with a 1 Megapixel resolution with a probability of
50%, and a images with a 4 Megapixel resolution with a probability of 50%. Which optical system would
you prefer to use?”
Prob. = 0.5
Prob. = (1P*)
9 Oct 2009 1 Megapixels 1 Megapixels 14
Utility Point Calculation (from LEP
Method Results)
The utility is calculated on a ordinal scale, where the maximum and minimum utility equal 1.0 and 0.0
respectively. Hence, Eqn. 1 becomes:
0 P' 0
U(Xi) = 2 . P'
9 Oct 2009 15
Generating the MultiAttribute
Utility Function
• Constructing the MAUF
(K ⋅ ki ⋅U ( X )i +1)
__ n
1
U(X ) =
K
−1+ ∏
i=1
• Capabilities of the MAUF
• Determine the stakeholder aggregate utility value for a given set of single attribute utility values.
• Implications
• Must have the MAUF in a explicit function form
• Assumptions (in addition to the 4 single attribute utility theory assumptions)
• Preferential Independence: the ranking of preferences over any pair of attributes is independent of all
the other attributes.
• Utility Independence: The utility curve for one attribute is unique, and independent of all the other
attribute utility functions.
9 Oct 2009 16
MultiAttribute Utility Function
Normalization Constant
• Purpose: To ensure consistency between the MAUF and the SUAF’s. That is, ensure that
the MAUF is defined over the same range as the SAUF’s (i.e. [0, 1]).
n
if ∑k i < 1.0 K >0
i =1 then
n
if ∑k i > 1.0 1 < K < 0
i =1 then
n
if ∑k i = 1.0 K =0
i =1 then
9 Oct 2009 17
Index
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 18
(Integrated) Concurrent Engineering
Objective: to enable engineering design, tradestudies, and subsequent decisions to occur in real
time with all design team members and critical stakeholders colocated and an emphasis placed on
stakeholder feedback.
Screen Screen Screen
Reliability
Conference
IA&T Room and
Thermal
Stakeholder Systems Information
Team Engineering Support
Mechanical Door
Team
Lead Kitchen
Printer
Printer
d
de
A/V
cs
ee
ni
Control
sN
Mission Design Laboratory (MDL) Copier
io
Mission
Av
A
NASA Goddard Space Flight Center
n
Ops Flight
sio
Courtesy of Integrated Design Center, NASA Goddard Space Flight Center. Flight Dynamics
ul
op
Used with permission. LVs and Software Administrative
Pr
Cost Attitude and Technical
Concurrent engineering session example: Control
System: satellite
Radiation Support
Stakeholder: external program manager
Orbital
m
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 20
Alternatives to MATE for Tradespace
Exploration (TE)
Utility
Ideal (TOPSIS)
“Traditional” TE
21
Index
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 22
Benefits
9 Oct 2009 23
Benefits
9 Oct 2009 24
Index
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 25
Limitations
9 Oct 2009 26
Limitations
• No HF concerns are Human
Factors
Design Definition
explicitly addressed. Multidisciplinary Optimization
9 Oct 2009 27
Limitations
9 Oct 2009 28
Limitations
9 Oct 2009 29
Index
1. Context of MATECON
2. Implementing MATECON
1. MATE
2. CON
3. Alternatives
4. Benefits
5. Limitations
6. Discussion
9 Oct 2009 30
Discussion Questions
9 Oct 2009 31
Discussion Questions
9 Oct 2009 32
MIT OpenCourseWare
http://ocw.mit.edu
For information about citing these materials or our Terms of Use, visit: http://ocw.mit.edu/terms.