Mission Analysis » History » Version 1

Muguerza, Joaquin, 12/15/2014 05:41 PM

1 1 Muguerza, Joaquin
h1. Mission Analysis
2 1 Muguerza, Joaquin
3 1 Muguerza, Joaquin
4 1 Muguerza, Joaquin
{{>toc}} 
5 1 Muguerza, Joaquin
6 1 Muguerza, Joaquin
Since the beginnings of space exploration, space missions have been and continue to be the apex of human engineering capabilities. Their high costs and the impossibility of repair once launched, make it necessary to plan ahead for every possible events and environments susceptibles of disturbing the mission. The resulting systems used to achieve the desired objectives considering all possible adversities have an elevated grade of complexity, with numerous subsystems interacting with each others. In order to increase the chance of success, systems engineering techniques are implemented throughout all the phases of the mission.
7 1 Muguerza, Joaquin
8 1 Muguerza, Joaquin
9 1 Muguerza, Joaquin
h2. Systems Engineering
10 1 Muguerza, Joaquin
11 1 Muguerza, Joaquin
*Systems engineering* (SE) is the science of developing a system capable of meeting requirements within often opposed constraints. The main task is to find a safe and balanced design in the face of opposing interests and multiple conflicting requirements. In other words, system engineering is about balancing organizational and technical interactions in complex systems.
12 1 Muguerza, Joaquin
13 1 Muguerza, Joaquin
Hence, it is about tradeoffs, compromises and generalists rather than specialists in a complex system development process.
14 1 Muguerza, Joaquin
15 1 Muguerza, Joaquin
The processes of the SE engine are used to develop and realize the end products. These set of technical processes are classified in three groups: system design, product realisation and technical management.
16 1 Muguerza, Joaquin
17 1 Muguerza, Joaquin
System design processes are related to the definition of the mission objectives, the generation of technical requirements, and the corresponding translation from technical requirements into a design solution.
18 1 Muguerza, Joaquin
19 1 Muguerza, Joaquin
Product realisation processes are used to create the design solution for each product and to verify, validate, and transition up to the next hierarchical level products that satisfy their previously defined design requirements.
20 1 Muguerza, Joaquin
21 1 Muguerza, Joaquin
The technical management processes are used to establish plans for the project, which would be used to monitor progress, to control technical execution of tasks and, finally, to produce useful information which would help to make decisions.
22 1 Muguerza, Joaquin
23 1 Muguerza, Joaquin
The mission analysis and definition in this project have been realized following the recommendations presented by the NASA, in the book _“NASA Systems Engineering Handbook”, Revision 3_.[1]
24 1 Muguerza, Joaquin
25 1 Muguerza, Joaquin
From a practical and factual point of view, taking into account the project objectives, there is no need for a complex system engineering approach. However, some basic project planning and control is needed.
26 1 Muguerza, Joaquin
Although many system engineering tasks will be trivial or useless in our Cubesat project, as it was previously explained, it is of interest, from an academic point of view, to have an approach to this field since we are working with a small spacecraft system.
27 1 Muguerza, Joaquin
28 1 Muguerza, Joaquin
h2. Stakeholder Expectations Definition
29 1 Muguerza, Joaquin
30 1 Muguerza, Joaquin
h3. In general
31 1 Muguerza, Joaquin
32 1 Muguerza, Joaquin
The first stage of the System Design, its main purpose is to identify who the stakeholders are (people or groups with interests in the mission) and their intentions for the project. A definition process is suggested for complex missions, where many stakeholders may be present, each with different expectations for the project. 
33 1 Muguerza, Joaquin
34 1 Muguerza, Joaquin
With this information, a set of high-level requirements is obtained, following the information path depicted below: 
35 1 Muguerza, Joaquin
36 1 Muguerza, Joaquin
p=. !flow.png!
37 1 Muguerza, Joaquin
_Product flow for stakeholder expectations, from the NASA Systems Engineering Handbook_
38 1 Muguerza, Joaquin
39 1 Muguerza, Joaquin
Where : 
40 1 Muguerza, Joaquin
* The *Mission Authority* is the entity in charge of the mission
41 1 Muguerza, Joaquin
* The *Mission Objectives* are defined from the needs, wants, desires, capabilities and constraints from the stakeholders.
42 1 Muguerza, Joaquin
* The *Operational Objectives* specify how the mission has to be operated in order to achieve its objectives.
43 1 Muguerza, Joaquin
* The *Success Criteria* defines when the mission is considered as successful.
44 1 Muguerza, Joaquin
* The *Design Drivers* consist of important constraints such as the launch date, duration, orbit, that may guide the design of the mission.
45 1 Muguerza, Joaquin
46 1 Muguerza, Joaquin
The output of this stage are a set of high-level requirements, that will be the input of the technical requirements definition process. 
47 1 Muguerza, Joaquin
48 1 Muguerza, Joaquin
h3. The Cubesat project
49 1 Muguerza, Joaquin
50 1 Muguerza, Joaquin
In the case of our cubesat project, the stakeholder expectations definition is considerably simple.
51 1 Muguerza, Joaquin
The sole stakeholder in the project is the SatCom lab, and more precisely, its director, the group of students currently working on the CubeSat, and future users of the platform. The desires: to set ground for future Cubesat projects, and to develop a proof-of-concept of a simple Cubesat mission.
52 1 Muguerza, Joaquin
53 1 Muguerza, Joaquin
Following the above mentioned flow chart, the key points used for defining the top-level requirements are presented below.
54 1 Muguerza, Joaquin
55 1 Muguerza, Joaquin
56 1 Muguerza, Joaquin
57 1 Muguerza, Joaquin
*Mission authority*
58 1 Muguerza, Joaquin
Laurent Franck, director of the SatCom lab.
59 1 Muguerza, Joaquin
60 1 Muguerza, Joaquin
*Mission objectives*
61 1 Muguerza, Joaquin
Develop a prototype of a Cubesat mission, capable of communicating with ground.
62 1 Muguerza, Joaquin
63 1 Muguerza, Joaquin
*Operational objectives*
64 1 Muguerza, Joaquin
* Integrate and test the Cubesat with its payload
65 1 Muguerza, Joaquin
* Get the Cubesat into a LEO orbit
66 1 Muguerza, Joaquin
* Establish a communication with ground
67 1 Muguerza, Joaquin
* Download telemetry from the satellite, to obtain its position
68 1 Muguerza, Joaquin
69 1 Muguerza, Joaquin
*Success criteria*
70 1 Muguerza, Joaquin
The definition of success varies between Cubesat missions. However, it has been noted, that when communications are already established, the success rate is incredibly high. Therefore, we consider a successful mission if a communication link can be established.
71 1 Muguerza, Joaquin
72 1 Muguerza, Joaquin
*Design drivers*
73 1 Muguerza, Joaquin
	Not specified for this simple project.
74 1 Muguerza, Joaquin
75 1 Muguerza, Joaquin
The mission end to end architecture is depicted in the following diagram:
76 1 Muguerza, Joaquin
77 1 Muguerza, Joaquin
p=. !oparchitecture.png!  
78 1 Muguerza, Joaquin
79 1 Muguerza, Joaquin
80 1 Muguerza, Joaquin
81 1 Muguerza, Joaquin
h2. References
82 1 Muguerza, Joaquin
83 1 Muguerza, Joaquin
[1] "NASA Systems Engineering Handbook":https://acc.dau.mil/adl/en-US/263346/file/40975/NASA-SP-2007-6105-Rev-1-Final-31Dec2007.pdf