1. The calendar of survival
Andy Weir’s The Martian is full of calculations about time. How many sols of food remain, how long until the next launch window, how many hours of work fit into a day. The hero does not get to choose his deadlines; they are set by orbital mechanics, inventory, and the patience of distant decision-makers. A space programme is like that. The desktop cannot be willed into orbit. It must be developed, tested, licensed, integrated, launched, and commissioned on a calendar that is partly chosen and partly imposed.
Entry 292 closed the insurance and liability arc. This entry opens the program timeline arc.
2. Why timeline is a design variable
Time is not neutral. A longer timeline allows more testing, more heritage, and lower risk. A shorter timeline may capture a market opportunity or respond to a competitor, but it compresses margins. The programme must decide:
- When must the first unit fly?
- What must it prove?
- How much risk is acceptable to meet that date?
- What can be deferred to later units?
These questions shape the design. A platform that must fly in two years cannot afford a three-year technology development programme.
3. The standard spacecraft development phases
Most spacecraft programmes pass through similar phases:
- Concept study: define the mission, identify stakeholders, assess feasibility.
- Preliminary design: select architecture, make rough-order cost estimates, identify risks.
- Critical design: freeze interfaces, complete analyses, prepare for manufacturing.
- Manufacturing and assembly: build the hardware, procure components, conduct inspections.
- Qualification and acceptance: test the unit, fix findings, demonstrate readiness.
- Launch campaign: integrate with the launch vehicle, obtain final approvals, launch.
- Commissioning: establish operations, verify performance, begin service.
Each phase has entry and exit criteria. Moving backward is expensive; moving forward with unresolved issues is risky.
4. Regulatory and procurement timelines
The technical timeline is only part of the calendar. Other long-lead items include:
- Launch booking and rideshare integration.
- Spectrum coordination and licensing.
- Remote sensing license application.
- Export classification and compliance.
- Insurance placement.
- Major component procurement.
- Facility and cleanroom scheduling.
- Customer contract negotiation.
These run in parallel with design and manufacturing but have their own deadlines. A delay in spectrum coordination can delay a launch as surely as a delay in hardware delivery.
5. The first desktop milestone
For the desktop, the first major milestone is a working platform in orbit that demonstrates the core value proposition. This is not the final product. It is the minimum credible object that proves the concept. The timeline to this milestone determines:
- How much funding is needed before revenue.
- How many iterations can be flown before scale.
- Whether the programme can respond to market changes.
- When customers can be asked to commit.
A credible timeline is one of the most valuable outputs of early planning.
6. Contingency and margin
No plan survives contact with reality. Good timelines include margin for:
- Test failures and rework.
- Supplier delays.
- Regulatory questions.
- Launch slips.
- Weather and range constraints.
The amount of margin reflects the programme’s risk tolerance. A venture-backed startup may run with less margin than a government mission. Both must be honest about what they are assuming.
What this changes
- Program timeline is a design and business variable, not just a schedule.
- Spacecraft development follows concept, preliminary design, critical design, manufacturing, qualification, launch, and commissioning.
- Regulatory, procurement, and customer timelines run in parallel with technical work.
- The first desktop milestone is the minimum credible orbital demonstration.
- Margin and contingency must be budgeted explicitly.
- The next entry will cover development phases and decision gates in more detail.