Part 2: the mission

Statement and objectives

Write the mission statement. Then add objectives: primary ones the mission cannot do without, secondary ones, and additional ones. For each, give the need it answers, the measure of success, and what counts as minimum success and as full success. A mission needs at least one primary objective.

This page needs a free account.

Requirements

Add requirements with Add a requirement. Give each its text, the need it comes from, a priority (Must, Should or Could), a way to verify it and the subsystem it is allocated to. You can filter by subsystem. People edit only the requirements of their own subsystems.

Architecture and data flow

Add the elements of the mission: ground sensors, satellites, ground stations and users. Say how many there are and how much data each makes. Then add the links between them with their bit rate and minutes of contact per day. The diagram and the data budget show where a link is too small, for example a LoRa link that cannot carry what the sensors send.

Orbit and lifetime

Set the altitude, the inclination and the constellation pattern (Delta or Star). The orbital lifetime card shows how long a satellite stays up at that altitude, in a quiet sun, an average sun and an active sun. It also gives the highest altitude that keeps the lifetime under a limit, such as 12 months.

Scenarios

Play the operations of the spacecraft through its modes: pointing, power, data and contacts. The scenarios start from the orbit of the mission and are saved in the study.

Phases and reviews

The phases 0, A, B, C, D, E and F and their reviews start from ECSS-M-ST-10C. Edit the names, the outputs and the reviews to fit your programme, and set each phase to Planned, In progress or Done.