System Engineering, Economics and Managerial Decision-Making

Introduction and Context

A satellite venture is not merely a spacecraft-development project. It is a socio-technical and economic system involving mission objectives, orbital resources, spectrum, ground infrastructure, launch services, user terminals, regulation, finance, insurance, operations, and end-of-life obligations. Technical excellence alone does not guarantee commercial success. A satellite may meet its design specification and still fail because demand was overestimated, capacity was poorly priced, deployment was delayed, or the operating model was not resilient to launch and in-orbit risks.

System engineering provides the discipline for converting stakeholder needs into verifiable requirements and an integrated architecture. Economics determines whether the architecture creates value over its life cycle. Managerial decision-making connects both by allocating scarce resources under uncertainty. This chapter presents an integrated approach to evaluating satellite ventures using requirements engineering, trade studies, risk registers, lifecycle costing, capacity forecasting, business models, procurement, insurance, governance, and performance analytics.

Learning Objectives

After studying this chapter, the reader should be able to:

1. Translate strategic objectives into traceable satellite-system requirements.

2. Conduct technical, economic, and programmatic trade studies.

3. Construct and prioritize a satellite-project risk register.

4. Estimate life-cycle cost, revenue, cash flow, and investment measures.

5. Forecast capacity demand and assess utilization and service quality.

6. Compare satellite business and procurement models.

7. Design suitable governance, insurance, and performance-management arrangements.

8. Make defensible decisions when technical and commercial information is uncertain.

1. Satellite Ventures as Integrated Systems

The system boundary should include all elements necessary to deliver the intended service. For a communications satellite, these commonly include:

• the space segment: spacecraft bus, payload, propulsion, power, thermal control, attitude control, and flight software;
• the launch segment: launch vehicle, launch-site services, integration, and deployment;
• the ground segment: gateways, network operations centres, tracking and control, antennas, terrestrial backhaul, and cybersecurity;
• the user segment: terminals, antennas, modems, customer-premises equipment, and installation services;
• the institutional environment: spectrum and orbital filings, licences, export controls, safety rules, insurance, financing, and contractual commitments.

The system must also be considered across its life cycle: concept, design, manufacturing, testing, launch, commissioning, routine operations, anomaly recovery, replenishment, and disposal. Decisions made during concept design strongly influence later cost and performance. For example, choosing a highly flexible payload may increase manufacturing cost but reduce the risk of capacity becoming obsolete.

A useful distinction is between mission success and venture success. Mission success concerns technical outcomes such as orbital insertion, payload availability, coverage, and link performance. Venture success additionally requires sufficient paying demand, acceptable cash flow, regulatory compliance, controllable risk, and a credible return for investors or public stakeholders.

2. Requirements Engineering and Traceability

Requirements engineering begins with stakeholder needs and ends with verified system behaviour. A sound requirements hierarchy is:

1. Strategic requirements: the purpose of the venture, target markets, policy goals, or national-service obligations.

2. Service requirements: coverage, availability, latency, throughput, geographic access, service continuity, and pricing constraints.

3. System requirements: payload capacity, antenna performance, power, pointing accuracy, ground-network interfaces, cybersecurity, and lifetime.

4. Subsystem requirements: detailed allocations to payload, bus, software, ground, and user equipment.

5. Verification requirements: test, analysis, inspection, or demonstration methods and acceptance criteria.

A good requirement is necessary, unambiguous, singular, feasible, traceable, and verifiable. “The system shall provide reliable service” is weak because “reliable” is undefined. “The network shall provide 99.5% monthly service availability in the defined coverage area, excluding scheduled maintenance” is more useful, provided availability and exclusions are precisely specified.

A requirements traceability matrix links each stakeholder need to system requirements, design elements, verification evidence, and acceptance status. Traceability supports change control and exposes orphan requirements—requirements with no design allocation or verification method.

Requirements should also be classified as:

• hard constraints, such as regulatory limits or a launch-vehicle mass limit;
• performance objectives, such as throughput or latency targets;
• commercial assumptions, such as subscriber numbers or willingness to pay; and
• design margins, which protect against uncertainty.

Confusing assumptions with requirements is dangerous. A forecast that 100,000 customers will subscribe is not a physical requirement; it is a business assumption that must be tested through market research and sensitivity analysis.

Verification and validation

Verification asks, “Was the system built correctly against its specification?” Validation asks, “Does the system solve the stakeholder’s actual problem?” A payload can pass laboratory tests and still be commercially invalid if its capacity, beam geography, or terminal cost does not match customer needs. Verification evidence should be planned from the outset, since late discovery of untestable requirements causes delay and dispute.

3. Architecture and Trade Studies

A trade study compares feasible alternatives against explicitly stated criteria. Typical alternatives include different orbital regimes, frequency bands, payload architectures, satellite sizes, launch strategies, ground-network designs, and ownership models.

The process should include:

1. define the decision and “do nothing” or baseline option;

2. establish constraints and evaluation criteria;

3. generate technically feasible alternatives;

4. model performance, cost, schedule, risk, and commercial consequences;

5. apply stakeholder weightings transparently;

6. perform sensitivity and uncertainty analysis;

7. document the recommendation and unresolved assumptions.

A simple weighted-score model is

\[

S_j=\sum_{i=1}^{n} w_i r_{ij},

\]

where \(S_j\) is the score of alternative \(j\), \(w_i\) is the normalized importance weight for criterion \(i\), and \(r_{ij}\) is the normalized rating of alternative \(j\) on criterion \(i\). The model is applicable when criteria can be meaningfully normalized and treated as additive. It should not conceal a fatal constraint: an alternative that violates a licensing or safety requirement must be rejected rather than rescued by high scores elsewhere.

For financial alternatives, net present value is commonly used:

\[

NPV=\sum_{t=0}^{T}\frac{CF_t}{(1+r)^t},

\]

where \(CF_t\) is net cash flow in period \(t\), \(r\) is the discount rate per period, and \(T\) is the analysis horizon. The initial investment is normally represented by a negative \(CF_0\). NPV is meaningful only when cash flows, inflation treatment, tax assumptions, currency, and discount rate are internally consistent. Nominal cash flows require a nominal discount rate; real cash flows require a real discount rate.

Trade studies should include non-financial attributes. A lower-cost design may have lower radiation tolerance, greater dependence on a single supplier, or inadequate replenishment flexibility. Conversely, a technically superior design may be unattractive if its additional capacity cannot be sold.

4. Risk, Uncertainty, and Decision Quality

A risk is an uncertain event or condition that can affect objectives. It differs from an issue, which has already occurred, and from an assumption, which is accepted temporarily for planning. Satellite risk categories include:

• technical: payload underperformance, software defects, radiation damage, or propulsion failure;
• launch and deployment: launch delay, launch failure, separation anomaly, or orbital injection error;
• regulatory: licensing delay, spectrum conflict, export restriction, or debris-compliance failure;
• market: weak demand, price erosion, customer concentration, or disruptive competition;
• financial: interest-rate, currency, refinancing, and liquidity risk;
• supply chain: component obsolescence, counterfeit parts, sole-source dependence, or factory delay;
• operational and cyber: command compromise, ground-station outage, jamming, collision, or human error; and
• environmental and social: debris generation, radio-frequency interference, and unsafe disposal.

A risk register should record a unique identifier, cause, event, consequence, owner, probability, impact, trigger, response, residual exposure, and review date. Qualitative probability-impact matrices are useful for early screening but can create false precision. Where data permit, quantitative analysis is preferable.

For a discrete risk with probability \(p\) and monetary consequence \(C\), the expected monetary impact is

\[

EMI=pC.

\]

This is an average over repeated comparable situations, not a prediction of the actual loss in one project. It is inappropriate to use EMI alone when consequences are catastrophic, probabilities are poorly known, or risks are strongly correlated. Monte Carlo simulation can model uncertain cost, schedule, demand, and failure variables, but its output is only as credible as the distributions and dependencies supplied.

Risk responses include avoidance, reduction, transfer, acceptance, and exploitation of opportunity. Insurance transfers selected financial consequences but does not eliminate technical or reputational damage. A risk owner must have authority and resources to act; assigning a risk without ownership is administrative rather than managerial control.

5. Life-Cycle Costing and Economic Evaluation

Life-cycle cost includes non-recurring and recurring expenditure from concept through disposal. A representative structure is:

\[

LCC=C_{concept}+C_{design}+C_{manufacture}+C_{launch}+C_{ground}+C_{insurance}+C_{operations}+C_{decommissioning},

\]

where each term is measured on a consistent accounting basis. This identity is a cost classification framework, not a valuation formula; financing costs, taxes, contingencies, and escalation must be treated explicitly rather than hidden in a category.

Important cost distinctions include:

• non-recurring engineering versus recurring production cost;
• fixed cost versus usage-dependent variable cost;
• committed cost versus avoidable cost;
• cash cost versus accounting depreciation; and
• sunk cost versus relevant future cost.

Sunk costs should not determine a future choice, although contractual liabilities must be recognized. Life-cycle analysis should include replacement or replenishment. A satellite with a fifteen-year design life may not be economically superior if its technology becomes commercially obsolete after six years.

Revenue models may be based on capacity leases, managed services, retail subscriptions, government contracts, data sales, hosted payloads, or blended arrangements. The analyst should model customer acquisition, terminal subsidies, churn, service credits, bad debt, and revenue recognition rather than treating all contracted capacity as immediate cash.

Useful measures include NPV, internal rate of return, payback period, profitability index, break-even utilization, and debt-service coverage. NPV is generally preferable for mutually exclusive investments because it measures value in monetary terms and respects the timing of cash flows. Internal rate of return can be misleading where cash flows change sign more than once or where projects differ greatly in scale.

Capacity economics

For a service with nominal capacity \(K\), utilized capacity \(U\), and total serviceable capacity \(K_s\), utilization is commonly defined as

\[

\eta=\frac{U}{K_s},

\]

provided \(U\) and \(K_s\) are measured in the same units and time interval. Capacity may be expressed in MHz, transponder equivalents, Gbit/s, beam-hours, or subscriber-equivalent busy-hour throughput. Nominal payload capacity is not necessarily saleable capacity because of coverage, interference, gateway, power, regulatory, and quality-of-service constraints.

Demand forecasts should distinguish addressable market, qualified prospects, contracted demand, active users, and busy-hour traffic. Scenarios—conservative, central, and high-growth—are more informative than a single-point forecast. Forecast uncertainty should be propagated into fleet size, ground infrastructure, financing, and replenishment decisions.

6. Business Models and Strategic Positioning

Satellite ventures use different value propositions and revenue mechanisms:

• capacity wholesale sells transponders, beams, or throughput to telecommunications operators and broadcasters;
• managed connectivity sells an end-to-end service including terminals, network management, and support;
• direct-to-user service earns recurring subscription revenue but requires substantial distribution and customer-support capability;
• government or institutional service relies on procurement contracts and may prioritize resilience or sovereignty over lowest price;
• hosted payload and infrastructure-as-a-service share spacecraft resources among multiple customers; and
• data or analytics models monetize imagery, sensing, timing, or derived information rather than raw space capacity.

Business-model analysis should examine customer segments, value proposition, channels, key partners, resources, activities, cost structure, and revenue streams. Strategic differentiation may arise from coverage, latency, resilience, terminal affordability, service integration, regulatory access, or data quality. A technically impressive constellation can fail if customer switching costs are low and terrestrial substitutes are improving rapidly.

Real options thinking is useful where uncertainty is high. A staged deployment, pilot service, hosted payload, or option to expand may have value because it postpones irreversible expenditure until market information improves. Staging can, however, increase unit cost and delay network effects. The value of flexibility must be compared with the cost of delay and incomplete coverage.

7. Procurement, Contracting, and Supply-Chain Strategy

Procurement strategy determines what the venture owns, buys, leases, or partners for. Options include turnkey procurement, split procurement of bus and payload, build-operate-transfer arrangements, public-private partnerships, hosted payloads, and rideshare launches.

A procurement statement of work should define interfaces, technical baselines, deliverables, verification evidence, acceptance criteria, schedule milestones, data rights, cybersecurity obligations, spares, training, and support. Contract incentives should reflect controllable outcomes. Fixed-price contracting can transfer cost risk but may encourage conservative pricing, claims, or reduced flexibility. Cost-plus contracting supports uncertain development but places greater cost-control responsibility on the buyer. Milestone payments should be tied to objective evidence rather than calendar dates alone.

Interface control is especially important when multiple suppliers provide spacecraft, payload, launch, ground, and user systems. Configuration management prevents unauthorized changes from invalidating qualification evidence. Supplier due diligence should assess financial health, quality systems, export constraints, production capacity, component provenance, and recovery plans.

Make-or-buy decisions should consider total cost, intellectual property, strategic autonomy, schedule, learning value, and supplier dependence. Lowest purchase price is not equivalent to lowest risk-adjusted life-cycle cost.

8. Insurance, Financing, and Risk Allocation

Space insurance may cover launch, in-orbit failure, third-party liability, or specialized risks, subject to policy terms, exclusions, deductibles, and proof of loss. Insurance underwriting depends on design heritage, qualification evidence, launch vehicle history, mission profile, redundancy, operations, and claims experience. Insurance should be integrated into architecture and financing decisions, not purchased as an afterthought.

Financing may involve equity, project debt, export credit, government support, anchor-customer prepayments, or blended finance. Debt increases financial leverage and imposes repayment obligations even when utilization is below forecast. Covenants may require minimum cash balances, insurance, performance reporting, or restrictions on additional borrowing.

Risk allocation should place each risk with the party best able to control or diversify it. A launch provider may control launch execution, while the satellite manufacturer controls manufacturing quality and the operator controls mission operations. Contractual transfer is effective only when the counterparty has adequate resources and the contract is enforceable. Excessive transfer can increase price and produce adversarial behaviour.

9. Project Governance and Decision Gates

Governance establishes who decides, on what evidence, and with what accountability. A suitable structure may include a sponsoring board, programme director, systems-engineering authority, commercial lead, safety and compliance authority, independent assurance, and risk committee. Technical authority should be sufficiently independent to reject unsafe or unverifiable designs.

Stage gates commonly occur at mission concept, preliminary design, critical design, manufacturing readiness, launch readiness, in-orbit acceptance, and service entry. Each gate should have entry criteria, required evidence, decision rights, approved tolerances, and explicit outcomes: proceed, proceed with conditions, rework, defer, or terminate.

Earned value management can compare planned, performed, and actual work. If budgeted cost of work scheduled is \(BCWS\), budgeted cost of work performed is \(BCWP\), and actual cost of work performed is \(ACWP\), then:

\[

SV=BCWP-BCWS, \qquad CV=BCWP-ACWP.

\]

Schedule variance \(SV\) and cost variance \(CV\) are expressed in budgetary cost units in this formulation. Positive values indicate more performed work than scheduled or lower actual cost than budgeted, respectively. These measures do not by themselves prove that the project will finish on time; schedule performance should also be assessed using network logic and milestone forecasts. Index forms are \(SPI=BCWP/BCWS\) and \(CPI=BCWP/ACWP\), when the denominators are non-zero.

Governance must manage change rather than suppress it. A change-control board should evaluate changes for technical effect, cost, schedule, safety, regulatory status, cybersecurity, and commercial value. “Launch at any cost” is not a governance strategy; it is an unmanaged risk posture.

10. Performance Analytics and Continuous Learning

Operational analytics should connect engineering telemetry to service and financial outcomes. Relevant indicators include payload availability, network availability, throughput, latency, dropped sessions, energy margin, anomaly recurrence, mean time to detect, mean time to recover, capacity utilization, customer churn, revenue per unit of capacity, operating cost per subscriber, and forecast error.

Indicators require definitions and denominators. For example, availability may be calculated as

\[

A=\frac{T_{service}-T_{unavailable}}{T_{service}},

\]

where both times use the same observation period and exclusions are explicitly defined. Planned maintenance, force majeure, and customer-equipment outages must not be excluded inconsistently. A high aggregate availability can conceal poor performance in a critical region or customer class, so analytics should be segmented.

Dashboards should support decisions rather than merely display data. Leading indicators include unresolved critical defects, supplier slippage, declining test margins, and risk-trigger frequency. Lagging indicators include missed milestones, service credits, and lost revenue. Artificial intelligence can assist anomaly detection, demand forecasting, predictive maintenance, document review, and scenario generation. It must not replace engineering authority where training data are biased, explanations are inadequate, or a false alarm can cause unsafe commanding. Data provenance, model validation, cybersecurity, human oversight, and protection of commercially sensitive information are essential.

11. Illustrative Case: A Regional Broadband Constellation

Background

The following fictional case is illustrative. Meridian Connectivity proposes a regional broadband constellation to serve remote communities and maritime users. The proposed architecture consists of a staged fleet, gateway stations, customer terminals, and a managed-service business model. A government agency may become an anchor customer, but commercial demand is uncertain.

Problem

The engineering team favours a large initial deployment because it provides attractive coverage and lower unit cost. The finance team warns that the deployment requires substantial early capital, while market research supports only gradual adoption. The board must choose between a large deployment, a staged deployment, and a hosted-capacity partnership.

Analysis

The requirements baseline identifies minimum regional coverage, a service-availability target, latency limits, cybersecurity controls, debris-mitigation obligations, and an initial government service commitment. Commercial assumptions are kept separate from technical requirements. The trade study assigns criteria for coverage, five-year NPV, time to service, expansion flexibility, supply-chain risk, and environmental compliance.

The large deployment scores highest in eventual capacity but has the greatest exposure to demand risk and financing pressure. The hosted option has the lowest initial capital requirement but provides less control over coverage and long-term pricing. The staged architecture has slower full-region coverage but allows demand observations after the first deployment.

The risk register identifies launch delay, terminal affordability, gateway permitting, component obsolescence, spectrum coordination, and customer concentration. Mitigations include multiple launch opportunities, a terminal subsidy ceiling, early regulatory engagement, design provisions for software reconfiguration, and a requirement that no single commercial customer represent an excessive proportion of forecast revenue.

Financial analysis uses nominal cash flows and a nominal discount rate. It includes satellite, launch, gateway, insurance, operations, customer acquisition, replacement, taxes, and working capital. Demand is modelled in conservative, central, and high-growth scenarios. The staged option has a lower central-case NPV than the large deployment but a smaller downside loss and a valuable expansion decision after the first service phase.

Approach and outcome

The board selects a staged programme with a contractual government anchor, an option for additional spacecraft, and a gateway partnership. The first gate requires demonstrated terminal affordability, spectrum progress, supplier qualification, and committed financing. Expansion is authorized only if utilization, service quality, and customer acquisition cost fall within predefined ranges.

The decision does not claim that staging maximizes every metric. It deliberately exchanges some scale efficiency for information, flexibility, and liquidity protection. Governance assigns the systems authority control over requirements and the commercial authority responsibility for demand evidence. A quarterly dashboard links technical availability, utilization, cash burn, risk exposure, and customer growth.

Learning points

The case illustrates that architecture and business model are coupled. A capacity decision is also a financing and market decision. Separating requirements from assumptions improves honesty; scenario analysis exposes downside risk; staged investment can be rational under uncertainty; and gates turn a strategic plan into a controlled learning process.

12. Challenges, Limitations, and Professional Practice

Satellite evaluation is limited by sparse failure data, long development cycles, uncertain regulation, correlated risks, proprietary supplier information, and rapid technology change. Financial models can create an illusion of precision when forecasts are speculative. Weighted scores can hide stakeholder disagreement, while NPV can undervalue resilience, sovereignty, scientific benefit, or public-service obligations.

Best practice therefore combines quantitative models with expert judgement and explicit uncertainty. Analysts should document assumptions, use independent reviews, test adverse scenarios, maintain configuration control, and distinguish facts from estimates. Decisions should be reversible where possible, and irreversible commitments should require stronger evidence. Environmental responsibility includes spectrum coordination, orbital-debris prevention, collision avoidance, responsible end-of-life disposal, and consideration of the energy and material footprint of ground infrastructure.

Ethically, operators must protect user data, avoid discriminatory service exclusion where public funds are involved, report anomalies honestly, and resist pressure to conceal weak performance. Regulatory compliance is a minimum condition, not a substitute for responsible engineering. The strongest ventures align technical feasibility, economic value, public legitimacy, and long-term orbital sustainability.

Chapter Summary

Satellite ventures must be managed as integrated technical, commercial, institutional, and life-cycle systems. Requirements engineering converts stakeholder needs into traceable and verifiable specifications, while validation confirms that the service remains relevant to users. Trade studies compare alternatives across performance, cost, schedule, risk, flexibility, and regulatory criteria. Risk registers assign ownership and responses, but quantitative estimates must not disguise uncertainty or correlated consequences.

Life-cycle costing includes development, launch, ground, operations, insurance, replacement, and disposal. NPV and related measures are useful only when cash-flow, inflation, tax, currency, and discount-rate assumptions are consistent. Capacity forecasts should distinguish nominal, serviceable, contracted, and utilized capacity. Business models range from wholesale capacity to managed connectivity, direct service, government contracts, hosted payloads, and data products.

Procurement, contracting, insurance, financing, and governance determine how risk and accountability are distributed. Stage gates, configuration control, independent assurance, and performance analytics support disciplined decisions. Staged deployment and real-options thinking are especially valuable when demand and technology are uncertain. Ultimately, a successful satellite venture balances mission performance, financial resilience, customer value, regulatory legitimacy, and orbital sustainability.

Key Terms

Requirements engineering: Process of eliciting, specifying, allocating, and verifying stakeholder needs.

Traceability: Ability to link a requirement to its origin, design allocation, and verification evidence.

Validation: Confirmation that a system meets its intended operational purpose.

Trade study: Structured comparison of feasible alternatives against defined criteria.

Life-cycle cost: Total relevant cost from concept through disposal or decommissioning.

Net present value: Present value of future net cash flows less the investment represented in the cash-flow series.

Capacity utilization: Used serviceable capacity divided by available serviceable capacity.

Risk register: Controlled record of risks, causes, consequences, owners, triggers, and responses.

Residual risk: Risk remaining after responses have been implemented.

Risk transfer: Allocation of selected financial or operational consequences to another party.

Stage gate: Formal decision point requiring specified evidence before continuation.

Configuration management: Control of approved system baselines and changes.

Earned value management: Method comparing planned value, earned value, and actual cost.

Business model: Structure describing customers, value creation, delivery, partners, costs, and revenue.

Hosted payload: Customer or mission equipment carried on another operator’s spacecraft.

Real option: Value created by retaining the ability to defer, expand, abandon, or modify an investment.

Availability: Proportion of defined service time during which the service is operational.

Anchor customer: Early committed customer supporting initial demand and financing confidence.

Orbital sustainability: Responsible use of space that limits debris, interference, and long-term environmental harm.

Review Questions

Short Answer Questions

1. Distinguish verification from validation in a satellite programme.

2. What information should a risk register contain?

3. Why must nominal cash flows be paired with a nominal discount rate?

4. Define serviceable capacity and explain why it differs from nominal payload capacity.

5. State two advantages of stage-gate governance.

Long Answer Questions

1. Explain how requirements engineering and traceability support technical and commercial success.

2. Describe a comprehensive trade-study process for selecting between two satellite architectures.

3. Discuss the principal components of satellite life-cycle cost and the limitations of accounting cost alone.

4. Compare wholesale capacity, managed connectivity, and direct-to-user satellite business models.

5. Explain how procurement, insurance, and contracts can allocate—but not eliminate—project risk.

Analytical / Application Questions

1. A proposed constellation has three deployment alternatives: a large initial fleet, a staged fleet, and hosted capacity. Construct a weighted trade-study framework including at least six criteria, justify the weights, and identify which assumptions require sensitivity analysis.

2. Develop a risk register for a regional broadband satellite project containing at least eight risks. Assign owners, triggers, responses, and residual-risk priorities.

3. Design a stage-gate decision plan for the illustrative Meridian Connectivity case. Specify the evidence required before initial deployment and the quantitative and qualitative conditions for expansion.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes validation from verification?

A. Validation checks whether the system solves the intended operational problem; verification checks conformity to specified requirements.

B. Validation is performed only after launch; verification is performed only before manufacturing.

C. Validation measures project profit; verification measures customer satisfaction.

D. Validation assigns risk owners; verification assigns contract prices.

Correct Answer: A. Validation checks whether the system solves the intended operational problem; verification checks conformity to specified requirements.

Question 2

In a weighted-score trade study, what does a normalized criterion weight usually represent?

A. The physical unit of the criterion

B. The relative importance assigned to the criterion

C. The probability that the alternative will fail

D. The supplier's manufacturing cost

Correct Answer: B. The relative importance assigned to the criterion

Question 3

A risk has probability 0.2 and a monetary consequence of $5 million. What is its expected monetary impact?

A. $0.2 million

B. $1 million

C. $5.2 million

D. $25 million

Correct Answer: B. $1 million

Question 4

Which cash-flow treatment is internally consistent for a project analysis?

A. Real cash flows with a nominal discount rate

B. Nominal cash flows with a real discount rate

C. Nominal cash flows with a nominal discount rate

D. Cash flows without any discount rate regardless of timing

Correct Answer: C. Nominal cash flows with a nominal discount rate

Question 5

If serviceable capacity is 100 Gbit/s and utilized capacity is 65 Gbit/s, what is utilization?

A. 35%

B. 65%

C. 100%

D. 165%

Correct Answer: B. 65%

Question 6

Which is an example of a commercial assumption rather than a physical system requirement?

A. The spacecraft shall remain within its allocated orbital regime.

B. The payload shall meet the specified pointing accuracy.

C. The venture shall attract 100,000 paying users in its first year.

D. The ground system shall implement the approved command interface.

Correct Answer: C. The venture shall attract 100,000 paying users in its first year.

Question 7

What is the principal purpose of a stage gate?

A. To guarantee that no project change can ever occur

B. To provide an evidence-based decision point before further commitment

C. To replace all technical testing with financial analysis

D. To transfer every project risk to the launch provider

Correct Answer: B. To provide an evidence-based decision point before further commitment

Question 8

In earned value terminology, if BCWP is $8 million and ACWP is $10 million, what is cost variance?

A. -$2 million

B. $2 million

C. $8 million

D. $18 million

Correct Answer: A. -$2 million

Question 9

Which statement about insurance is most accurate?

A. Insurance eliminates the technical probability of satellite failure.

B. Insurance transfers every consequence of failure without exclusions.

C. Insurance can transfer selected financial consequences but does not remove technical or reputational damage.

D. Insurance makes requirements verification unnecessary.

Correct Answer: C. Insurance can transfer selected financial consequences but does not remove technical or reputational damage.

Question 10

Why can staged deployment be attractive under uncertain demand?

A. It always has the lowest unit cost and fastest full coverage.

B. It permits learning and postpones some irreversible investment.

C. It eliminates the need for regulatory approval.

D. It guarantees higher utilization than a large deployment.

Correct Answer: B. It permits learning and postpones some irreversible investment.