Project: Hypergravity Habitat
Document type: preliminary economic framework
Status: working document for pre-feasibility review
Scope: cost categories, drivers, uncertainty, staged funding logic, and comparison method for candidate infrastructure concepts
This document defines a transparent cost framework for the Hypergravity Habitat project. It does not predict a final project cost and should not be used as a construction estimate.
The purpose is to help reviewers understand:
The central principle is:
At the current stage, cost modelling should support decision-making and feasibility assessment, not create false precision.
The project should use staged and parametric cost modelling.
Costs should be estimated separately for:
Costs should be linked to variables such as radius, guideway length, operating speed, vehicle mass, payload complexity, staffing model, operating hours, maintenance interval, environmental-control requirements, and safety or certification burden.
Every estimate should state source or assumption, unit cost, quantity, uncertainty range, date of estimate, included items, and excluded items.
Capital expenditure includes one-time investment costs such as land, permitting, site preparation, guideway construction, rotating structures, vehicles or payload modules, propulsion, control systems, power infrastructure, buildings, laboratories, environmental control, safety systems, commissioning, project management, and contingency.
Operating expenditure includes recurring costs such as electricity, staff, maintenance, inspections, consumables, laboratory operations, medical support where relevant, data systems, insurance, training, safety readiness, administration, and facility management.
Renewal costs include rail replacement, wheel replacement, bearings, guideway components, power electronics, sensors, HVAC systems, laboratory equipment, software upgrades, and building refurbishment.
End-of-life costs include dismantling, site restoration, disposal, recycling, hazardous-material handling, documentation, and project closure.
A credible funding path should avoid proposing a full facility before smaller evidence-producing stages.
| Stage | Typical output | Cost-model purpose |
|---|---|---|
| Concept refinement | literature review, parameter model | justify research question |
| Simulation | physics, vibration, energy, safety models | identify feasible envelopes |
| Payload demonstrator | instrumented biological or physical payload | verify measurement quality |
| Engineering demonstrator | guideway or rotating rig | test acceleration, vibration, operations |
| Pre-feasibility study | trade study, risk register, partner map | support larger funding decision |
| Larger infrastructure | facility concept | only after prior evidence |
Each stage should include stop/go criteria.
Primary drivers include track length, track quality, earthworks, land, rolling stock, depot and workshop, power supply, control and safety systems, environmental-control modifications, laboratory integration, wheel and rail maintenance, inspections, staff, and downtime management.
Dominant uncertainty: continuous circular operation may produce maintenance patterns that differ from ordinary railway service.
Primary drivers include guideway, levitation and guidance, propulsion, power electronics, control systems, electromagnetic shielding where required, thermal management, specialized vehicles, fallback systems, power demand, specialized maintenance, inspection, cooling, and software support.
Dominant uncertainty: the cost and safety case of a specialized circular long-duration research maglev system are not yet established.
Primary drivers include structure, bearings or support system, drive system, balancing, vibration control, payload modules, safety enclosure, access system, environmental control, inspection, and maintenance.
Dominant uncertainty: scaling from small payload demonstrator to habitat-scale system.
Primary drivers include test rig, sensor package, environmental enclosure, payload containers, data system, control software, safety enclosure, experiment preparation, sample handling, consumables, staff time, and data analysis.
Dominant uncertainty: whether the demonstrator is scientifically sufficient to justify later stages.
Life-cycle cost should include capital expenditure, operating expenditure, renewals, and decommissioning:
LCC = CAPEX + ΣOPEX + ΣRenewals + Decommissioning
A concept with lower initial cost may become expensive if maintenance is high. A concept with high initial cost may become attractive if it significantly reduces vibration, wear, downtime, or operational risk.
Therefore, candidate concepts should not be ranked by construction cost alone.
Funding discussions should connect cost to scientific output.
Possible metrics:
For early stages, “cost per risk retired” may be more useful than cost per participant.
At the current stage, uncertainty is high.
| Cost area | Current confidence | Reason |
|---|---|---|
| small payload demonstrator | medium | scope can be limited |
| literature and modelling | medium-high | mostly staff effort |
| track or guideway length | medium | geometry is calculable |
| track or guideway unit cost | low-medium | site-specific |
| rolling stock refurbishment | low | depends on availability and requirements |
| maglev system cost | low | concept not specified |
| human-rated safety systems | low | governance not defined |
| OPEX | low | maintenance and staffing unknown |
| long-term renewal | low | lifetime assumptions unknown |
All cost estimates should include contingency. The contingency percentage should reflect project maturity and uncertainty.
Future cost models should test sensitivity to radius, target gravity, operating speed, guideway unit cost, vehicle mass, operating hours, electricity price, maintenance interval, staff count, laboratory complexity, safety requirements, downtime tolerance, and contingency percentage.
Sensitivity analysis is important because one or two assumptions may dominate total cost.
| Criterion | Railway | Maglev | Rotating demonstrator | Payload-only rig |
|---|---|---|---|---|
| Initial cost | medium-high | high | low to high | low-medium |
| Cost uncertainty | medium | high | medium | low-medium |
| Maintenance uncertainty | medium-high | high | medium | low |
| Scientific scalability | medium-high | medium-high | medium | low-medium |
| Early feasibility | medium | low-medium | high | high |
| Human-habitat potential | possible | possible | possible but scale-dependent | no |
| Best early role | trade study / instrumented test | advanced trade study | physics and payload demonstrator | first science demonstrator |
This framework should be updated when more data become available.
A proposal-grade funding strategy should begin with modest, reviewable milestones such as literature review, reproducible physics and cost models, biological payload demonstrator design, vibration and acceleration measurement, safety and ethics framework, architecture trade study, and external pre-feasibility review.
The first funding request should probably not be for a full habitat. It should be for a defined feasibility package that produces decision-quality evidence.
Future revisions should gather comparable research-infrastructure costs, rail construction references, maglev guideway references, rotating test-rig costs, laboratory equipment costs, HVAC costs, staffing models, maintenance intervals, power consumption estimates, land and permitting assumptions, insurance costs, safety-compliance costs, and uncertainty ranges.
All sources should be cited and dated.
The cost model should remain staged, transparent, and decision-oriented. The project should avoid premature full-facility cost claims and instead focus on defining the lowest-cost pathway that can verify the research gap, validate the physics model, test measurement quality, and retire key risks.
A credible funding narrative is not “build the habitat immediately”. It is “fund the next evidence-producing step and decide from the results whether the next stage is justified”.
Project: Hypergravity Habitat · Status: exploratory research documentation · License: see repository license and file-level notes