Section 5.1: Human Expansion (page 4)

< Space Transport and Engineering Methods

back to page 3

Program Evaluation Criteria

As noted on page 2, we want an objective method to choose among design alternatives, and to evaluate this program or its parts against existing programs. For a complex program such as this we take multiple measurable features or parameters and convert them to a common scale. The features chosen are the ones of value to the ultimate customer, which here is civilization as a whole, and the conversion formulas are according to their relative importance and desirability. Since we cannot ask everyone in the world what they want, we have to act as a proxy for them and make our best estimates of what they would want if they were well informed on this topic. We can draw on outside information to help with this process. Each design alternative will have different actual feature values, and result in different scores when converted to the common scale. Evaluation of the alternatives then amounts to adding all the scores and seeing which one has the highest total. For this step of the Conceptual Design we can only establish what our criteria should be. Devising alternatives and selecting among them will come later.

Identifying Candidate Criteria

Every possible measurable feature or specification could be used as a point of comparison, but this is unfeasible for two reasons: (1) the time and complexity to evaluate all of them for every alternative, and (2) many features are simply undefined at a high level of a program. So we restrict our candidates to those which are the most important, and those which can at least be estimated at a high level. Any feature which is absolutely required for the program is not a point of comparison, since all the valid alternatives must include it. What that leaves us with are parameters which are variable in some way, so that an alternative can do better or worse by that measure. An example of a good measure is cost. Every alternative has an associated cost, which is almost infinitely variable, and so useful for comparisons. Most people will agree that lower cost is better, although they may differ by how much better. The general agreement that cost is important and which direction is better allows setting up a formula to convert particular cost ranges to score values.

We already (page 3) developed our program requirements based on program goals. By designating them as requirements we have indicated they are important, so those are the first places we should look for measurable criteria. Beyond that, we will also look at the same headings we used for the requirements analysis process, and consider civilization needs and desires generally, as we can find them from outside sources.

Program Requirements

Referring to the Program Requirements on page 3, we identify our first set of candidate criteria as follows:

1.0 Objectives:

2.0 Performance:

As a note, performance levels of a complex program are typically a rich area for finding evaluation criteria, since they tend to be variable with design choices.

3.0 Schedule:

4.0 Cost:

5.0 Technical Risk

6.0 Safety

7.0 Sustainability

8.0 Openness

This gives us a good starting list of candidate criteria. In early conceptual design many of the values will be undetermined for a given option. When not enough information is available to make a clear choice, the proper course is to keep multiple options until you have enough information to decide.

Additional Candidate Sources

General Needs and Desires

NOTE: Improvement Needed This section is preliminary, and an opportunity for improvement.

Here are some ideas about general human/civilization needs and desires. The idea is that since civilization as a whole is the "customer" for this program, it is their needs and desires for which we should be designing, and therefore include these types of items in the evaluation criteria. The following items are drawn from online search, and are not yet backed rigorously or empirically. Until better defined, we are not using them as evaluation criteria.

Selecting and Weighting Candidates

Now that we have established a set of candidates, preliminary as it is, the next step is to choose the most important ones, and establish relative scoring weights and conversion formulas. The weight is how much a given criterion contributes to the total score of a given design. The more important that feature or parameter is, the more weight we give it. The conversion formula takes the feature or parameter and converts it to a relative score, usually with a nominal 0 to 100% range, or 0.00 to 1.00 value. The range is arbitrary, as long as it is consistent within a project. We will use the 0 to 100% range. The total score is obtained from the weight x score for each component criterion, then summing all the resulting products.

We want to narrow the list to the most important ones because it takes too much time and effort to evaluate many criteria for every design option. One way to do this is by making some of them fixed requirements, which all options must meet. Another is to simply drop the candidate as not important enough at the top program level. Whatever list of criteria is developed through this process, they should be reviewed by the rest of the program participants and customer as best is possible. Setting criteria and importance is inherently subjective, so it is very important to get agreement and consensus from the right group of subjective humans that these are the right set to use in evaluating the design.

Candidate Discussion

The following discussion gives our reasoning for the conversion from program parameter or feature to a score. We use the same numbering as for the requirements to make them easier to compare. Since not every requirement has corresponding evaluation criteria, there are gaps in the numbering

Environment:
Environment temperature - range of daily high and low across seasons in Kelvin (K).
Water supply - annual rainfall + running water/ice/air moisture flow in meters.
Atmosphere pressure - average value at the location, in kiloPascals (kPa).
Ground pressure - foundation design load in megaPascals (MPa) or exterior water or rock pressure for below-surface construction.
Energy supply - Flux from natural sources in W/m2.
Gravity level - only applies to space, in meters/sec2.
Radiation dose - measured by human biological effect in Sievert/year.
Time and Distance: These are measured from 5th %ile nearest population on Earth.
Ping Time - minimum round trip communication delay, in seconds.
Travel Time - one way normal travel time for humans.
Stay time - average per person stay time per location in years. Increments count linearly from zero.
Transport energy - total potential, kinetic, and frictional energy to reach the location for most efficient cargo method, in megaJoules/kg.

The two criteria we derive are the actual number of distinct new locations the program establishes, and the total number of range steps expanded to by all the parameters combined. The first is measured directly at 1% per location, and the second at 0.5% per range step.

Weighting Discussion

Next we discuss our reasoning for the relative weights of the criteria. We will use a total weight of 100 points for all the criteria together. Our weighting is subjective, based on human opinion as to the importance of design features and parameters. Design alternatives themselves are objective. So other people reviewing the program choices can simply change the scoring and weighting to fit their own opinions on what matters. The design alternatives can remain the same, but a different set of choices would result from the changed evaluation scores.

Most people, all other factors being equal, prefer to get more results relative to the cost or effort expended. Since the ratio of performance to cost can be equally affected by increasing performance or lowering cost, the relative weight of these criteria groups is often set to be equal, and a large part of the total weight. In our list above, the performance type criteria are from 1.2 through 2.6, and the cost type criteria are 4.1 through 4.3. The remaining criteria fall into the technical risk, safety, and sustainability categories. Historically, large complex programs tended to focus on cost and performance, and put relatively small weight on other factors. With feelings of a finite and connected Earth, longer lives, and greater wealth and standards of living, people feel there is more to lose and so place more importance on the possible negatives of a project. We expect this trend to continue in the future, and this will be a long term program, so we will assign 30 points to this group, and divide the other 70 points equally between performance and cost.

Performance Group (35 points)

Scale (1.2) and number of locations (2.1) are the main motivations for a program of human expansion, so we will assign each 7.5 points. There does not seem to be strong reason to give growth, improved technology, quality of life, or resources (2.2-2.4, 2.6) more or less weight among themselves, so we assign 5 points to each.

Cost Group (35 points)

Development (4.1) and new location (4.2) cost seem equally important, but Earth launch cost only applies to space locations, so we give it half the weight. Therefore the weights are 14, 14, and 7 points each.

Technical Risk, Safety, and Sustainability Group (30 points)

We subjectively rate location (6.1) and population (6.2) risk more highly than the remaining factors, and thus give them 7.5 points each. Technical risk (5.1), biosphere security (7.1), and survivability (7.2) then get 5 points each.

Resulting Evaluation Criteria

From the above discussion, we can now make a table of the resulting evaluation criteria to apply to our design options. Note that in some cases scores can go outside 0 to 100% range if the parameter is outside the expected range. Like all parts of the conceptual design, this may get revised by later work.

Criterion Weight (points) Scoring Formula (percent) Notes
1.2 Program Scale (per location) 3.0 ln(average population per location/100) x 25% Population is final design size for location after growth
1.2 Program Scale (total all locations) 4.5 ln(total population all locations/5000)x25% Population is total design size after growth
2.1 Number of locations (count) 3.75 actual count of locations > minimum size @ 1% each Minimum size = final size/years to grow to final size
2.1 Number of locations (range) 3.75 steps in environment, time, and distance range @ 0.5% each 10 parameters and definition of steps from discussion 2.1 above
2.2 Growth (rate/yr) 5.0 (equivalent % annual GDP growth of all locations -2.5%) x 10 internal production valued as if sold at market rates
2.3 Improved Technology (local resources) 1.0 % of local resources from program locations by kg (mass) or Joules (energy)
2.3 Improved Technology (self production) 1.0 % of finished products from program locations by economic value
2.3 Improved Technology (cyclic flow) 1.0 % of location mass flows reused includes propellants, but not production for growth or sale
2.3 Improved Technology (automation) 1.0 % reduction human labor hours relative to current technology
2.3 Improved Technology (autonomy) 1.0 % required labor and control from within locations based on necessary location functions
2.4 Quality of Life (GDP) 5.0 (equivalent GDP - $20,000)/1600 includes value of internal production and labor
2.6 Resources (surplus) 5.0 ln(material & energy output/internal use)/ln(2) x 25% over program life cycle. Clip at -100%
4.1 Total development cost (Earth) 14.0 - S (avg unit cost/total development cost) x 1000% S = 14 x (space/total) development cost
4.1 Total development cost (Space) S (avg unit cost/total development cost) x 100% see above for S
4.2 New Location Cost (Earth) 14.0-S2 [(ln(0.25xUS capital per person/location cost))/ln(2) x 25%]+100% $200K includes land value for US capital. S2 see below
4.2 New Location Cost (Space) S2 [(ln(0.5 US capital per person/location cost))/ln(2) x 25%]+100% S2 = 14 x (people in space/total in program)
4.3 Earth Launch Cost ($/kg) 7.0 log($1600/(LEO transport per total system mass)) x 20% total mass includes local space resources
5.1 Technical Risk Allowance (%) 5.0 (50% - technical uncertainty allowance) x 2 includes performance and design uncertainty
6.1 New Location Risk (relative) 7.5 [ln(0.25x general casualty risk/location risk)/ln(2) x 25%] +100% casualty risk includes life and property
6.2 Population Risk (relative) 7.5 (% reduction to general population risk) x 5 from natural and program causes. Increased risk not allowed.
7.1 Biosphere Security (species-locations) 5.0 [(log(species maintained outside natural range x locations)) - 1] x 20% in vivo or stored, humans are a species
7.2 Survivability (relative) 5.0 (% compensation for critical risks) x 5 includes all civilization level risks
Total 100 Sum partial scores x weight from each line above

continue to page 5

This article is issued from Wikibooks. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.