Plan space station module development with a Gantt chart. Covers SRR, PDR, CDR, AIT, launch, docking, and ECLSS activation for ISS and commercial programs.
Space station module development is one of the longest and most demanding engineering programs a team can undertake. From initial requirements definition to first crew occupancy, a single pressurized module typically spans eight to fourteen years of coordinated effort across government agencies, prime contractors, and international partners. A Gantt chart is indispensable for managing that timeline — it makes the critical path visible, enforces milestone discipline, and gives program managers the situational awareness needed to protect schedule across thousands of interdependent tasks.
Space programs fail at interfaces. The hardware is rarely the problem; the schedule slippage happens when one phase hands off to the next without a clear, time-boxed commitment. A Gantt chart forces every phase — requirements definition, design reviews, manufacturing, testing, launch preparation, and on-orbit commissioning — onto a single visual timeline. NASA program managers, ESA project leads, and commercial operators at Axiom Space and Vast all depend on integrated master schedules built on exactly this logic. The Gantt format maps directly to how NASA structures its acquisition: sequential design reviews gated by documented evidence, with explicit hold points before proceeding.
Every module program begins with requirements. For ISS partner modules, NASA, ESA, and JAXA each maintain Interface Control Documents (ICDs) governing the Common Berthing Mechanism (CBM) or International Docking Standard (IDS), power interfaces, data interfaces, and ECLSS integration boundaries. Commercial station programs — Axiom Station, Starlab (Voyager/Airbus with Hilton as the hospitality partner), and Haven-2 (Vast) — must satisfy both NASA visiting vehicle requirements and their own private customer requirements for research facilities, habitation standards, and on-orbit services.
On your Gantt chart, this phase includes: customer and stakeholder requirements workshops, heritage review from ISS module programs (Node 3, Leonardo PMM), ConOps (Concept of Operations) development, draft system requirements document, and review/approval cycles with NASA's Mission Integration and Operations Directorate. Schedule this phase conservatively — requirements documents that skip stakeholder review cycles are the single leading cause of costly design changes in Phase 3.
SRR is the first NASA Technical Authority gate. The program demonstrates that requirements are complete, consistent, and traceable to mission objectives. TRL (Technology Readiness Level) assessments begin here; critical technologies must reach TRL 4 (validated in laboratory environment) before SRR closes. On the Gantt chart, SRR appears as a diamond milestone with a two-week review window and a formal closure action item burn-down period.
PDR is the transition from requirements to design. The program presents the selected architecture — module diameter, length, hatch locations, rack layout, ECLSS concept (closed-loop vs. open-loop water recovery, CO₂ removal system selection), electrical power system topology (solar array size, battery sizing for eclipse operations). Long-lead procurement planning begins at PDR: pressure vessel forgings, primary structure aluminum billets, and ECLSS hardware components have lead times of 24–36 months and must be ordered before CDR.
CDR closes the design. Every drawing is at revision status "for fabrication." The program demonstrates that the design meets all requirements through analysis, simulation, and subsystem test data. TRL 6 (prototype demonstrated in relevant environment) is required for all critical technologies at CDR. After CDR, engineering changes are extremely expensive — each change must be assessed against structural, thermal, and ECLSS system models and reverified.
Manufacturing overlaps with the tail end of CDR preparation. Key Gantt chart tasks include:
Long-lead items appear as predecessor tasks on the Gantt chart with explicit delivery milestones. Missing a long-lead delivery date by even two months can cascade into a six-month schedule slip because the integration sequence cannot begin without all structural components present.
AIT is the most schedule-dense phase. The flight article is assembled in a cleanroom facility (Class 10,000 or better) and subjected to a full environmental test campaign designed to simulate the launch environment:
Each test is its own Gantt subtask with setup, test conduct, data review, and anomaly resolution periods. Anomalies discovered in testing drive replanning: a failed component requires root cause analysis, corrective action, and retest — budget at least 20% schedule margin in the AIT phase.
Once AIT is complete and all nonconformances are closed, the module is packaged for launch. Manifesting on Falcon Heavy, SLS, or New Glenn determines the fairing envelope, mass limit, and structural interface. Launch site operations include: transport to launch site, receiving inspection, fit-check with launch vehicle, final closeouts, propellant loading (if the module carries propulsion for orbit adjustment), and pad operations. On the Gantt chart, this phase ends at the launch milestone diamond.
Post-launch milestones: launch confirmed, orbit insertion confirmed, module activation (initial power-up), rendezvous and proximity operations, docking or berthing confirmed, vestibule pressurization and leak check, hatch opening, ECLSS activation (O₂ generation, CO₂ removal, water recovery checkout), first crew occupancy. Commercial station programs (Axiom, Vast) add a business operations milestone: first commercial research payload activation.
| Milestone | Typical Program Month |
|---|---|
| SRR Complete | 22 |
| PDR Complete | 48 |
| Long-Lead Procurement Complete | 54 |
| CDR Complete | 72 |
| Flight Article Delivery to Launch Site | 120 |
| Launch | 126 |
| Docking Confirmed | 127 |
| ECLSS Activated | 129 |
| Habitable Volume Certified | 132 |
| First Crew Occupancy | 134 |
Axiom Station is taking a phased approach: Axiom Module 1 (AxM-1) attached to ISS Node 2 forward port provides early on-orbit heritage while the full station architecture matures. The transition from ISS-attached to independent station operations (post-2030) creates a unique dual-timeline challenge: the ISS attachment schedule is driven by NASA's ISS transition timeline, while the independent station schedule is driven by Axiom's own financing and customer commitments.
Starlab, developed by Voyager Space and Airbus with Hilton as the hospitality and interior design partner, targets a single-launch large-diameter station. The Hilton partnership introduces hospitality design requirements — crew quarters, lighting design, materials selection — as formal design inputs alongside NASA's human factors requirements.
Haven-2 (Vast) leverages SpaceX Starship's large payload volume to enable a more spacious module architecture. The CLPS (Commercial Lunar Payload Services) program context adds lunar surface delivery missions to adjacent project timelines — teams working across both LEO station and lunar surface programs need integrated Gantt charts that show resource conflicts between programs sharing engineering staff.
Start with the TRL gate review calendar as anchors: SRR at TRL 4, PDR at TRL 5, CDR at TRL 6, launch at TRL 9. Work backward from a target launch date. Identify all long-lead items and plot their procurement start dates as early as possible — these are non-negotiable schedule drivers. Build in 15–20% margin in manufacturing and AIT phases. Use dependencies aggressively: AIT cannot begin until flight article assembly is complete; TVAC cannot begin until acoustic testing is cleared. A well-constructed Gantt chart for space station module development will contain 400–800 tasks and span a ten-year timeline — but the investment in building it pays for itself the first time it surfaces a critical path conflict before it becomes a program delay.