Skip to content
Snippets Groups Projects
Commit d075a13d authored by Lorenzo Cucchi's avatar Lorenzo Cucchi
Browse files

handbook

parent 49b3fda4
Branches
No related tags found
No related merge requests found
Show whitespace changes
Inline Side-by-side
Showing
with 309 additions and 0 deletions
handbook/Handbook.md 0 → 100644
+ 309
− 0
View file @ d075a13d
---
subtitle: '[]{#_riouzcua7lt7 .anchor}**A practical guide to Skyward**'
title: |
[]{#_ywuer3526kmk .anchor}
[]{#_ulgpnrm28v0g .anchor}
[]{#_k8n46wqe8q0d .anchor}
[]{#_glqy2z2mmanm .anchor}
[]{#_kh33m1oz7wp .anchor}**The New Skywarder Handbook**
---
**Authors:** Matteo Colombo, Alberto Boffi
**Editor:** Matteo Colombo, Alberto Boffi, Alberto Nidasio
**Changelog**
=============
| **Date** | **Author** | **Notes** |
|------------|-----------------|-------------------------------------|
| 2021/09/26 | Matteo Colombo | Document creation |
| 2021/09/29 | Alberto Boffi | Added 'Active projects' paragraph and edited Slack channel list|
| 2022/03/30 | Alberto Nidasio | Document update for 2022/03 recruitment |
| 2022/10/16 | Alberto Nidasio | Document update for 2022/09 recruitment |
| 2023/04/01 | Lorenzo Cucchi | Document update for 2023/03 recruitment added Jira section. |
**Index**
=========
[**Changelog**](#changelog)
[**Index**](#index)
[**Introduction**](#introduction)
> [Document scope](#document-scope)
[**The association**](#the-association)
> [Active projects](#active-projects)
>
> [Just completed projects](#just-completed-projects)
>
> [Organizational chart](#organizational-chart)
>
> [Past projects: a remainder for the future](#past-projects-a-remainder-for-the-future)
[**The working tools**](#the-working-tools)
> [Slack](#slack)
>
> [Google Drive](#google-drive)
>
> [Online meetings: Slack / Webex](#online-meetings-slack-webex)
>
> [In presence work](#in-presence-work)
>
> [Google Calendar](#google-calendar)
>
> [Jira](#jira)
**Introduction**
================
***Document scope***
--------------------
This document was created to be an informal guide to the Skyward world
and to help new recruits to better integrate into the association. The
organization chart, work tools, work organization, an overview of past
and future projects and much more are contained here.
**The association**
===================
*Active projects*
-----------------
Currently, Skyward has one project under his belt: Gemini.
Gemini is an hybrid motor rocket currently in development that will
participate in the 2023 EuRoC competition in the H3-s category (Hybrid
3000m SRAD).
*Just completed projects*
-------------------------
During mid october the Pyxis project was concluded, a rocket with a
solid COTS motor. Two almost exact copies of it exists. The first was
launched in Roccaraso (AQ) during september 2022 with a smaller motor.
The second, with a more powerful motor, participated in the 2022 EuRoC
edition in the S3-c category (Solid 3000m COTS).
Before Pyxis, during 2021, the Lynx project, a COTS solid-engine rocket
of which two nearly identical copies exist. The first was launched in
Roccaraso (AQ) in September 2021, with a smaller engine. The second,
with a more powerful engine, participated in the EuRoC 2021 competition
in the S3-c category and won first place in its category and second
overall prize. In addition, Skyward also won the \"Team award\" for the
strong sporting spirit and excellent teamwork shown throughout the
competition.
*Organizational chart*
----------------------
![](media/image1.png){width="6.340277777777778in"
height="1.532557961504812in"}
Skyward is an association of the Politecnico di Milano, which however
remains independent from the Department of Aerospace Sciences and
Technologies (with pros and cons). The structure is the classic one of
an association: under the President there are the Vice President, the
Secretary, the Treasury and the Board of Directors, made up of the Heads
of Departments. The Directive Council (DC) deals with relations with the
Polytechnic, the association\'s finances, human resources. The head of
department must be the point of reference for each member to contact for
any problems.
At the technical level, the projects are managed by a Project Manager
(for Gemini, rocket for EuRoC 2023, Davide Rosato) who leads the
technical meeting (RT), formed by the team leaders of each department
(IPTL - Integrated Project Team Leader).
The IPTs (Integrated Project Teams) and IPTLs for Gemini are:
- \[STR\] Structures (Edoardo Nistri)
- \[ELC\] Electronics (Vincenzo Tirolese)
- \[SWD\] Software Development (Matteo Pignataro)
- \[GNC\] Guidance Navigation and Control (Marco Marchesi)
- \[RCS\] Recovery (Davide Perani)
- \[PRF\] Parafoil (Alessio Derobertis)
- \[MSA\] Mission Analysis (Riccardo Cadamuro)
- \[AER\] Aerodynamics (Lorenzo Cucchi)
- \[ASD\] Aeroelasticity Structural Dynamics (Letizia Montesano)
- \[R&D\] Research & Development (Tommaso Pansieri)
- \[RPS\] Rocket Propulsion System (Paolo Gnata)
- \[GSE\] Groud Segment Equipment (Alessandro Staffolani)
The work of each IPT cannot be separated from that of the other IPTs,
and it is therefore essential that all team members know the managers of
the other teams and know who to contact in order to resolve
inter-departmental technical issues.
*Past projects: a remainder for the future*
-------------------------------------------
After the first two successful launches, the old Skyward members decided
to design a large drone capable of bringing a rocket up, and then
launching it. At the same time, the development of a huge hybrid engine
began.
After years of development, all these projects have been canceled,
mainly for logistical and legal problems, but leaving a heavy legacy: a
lot of money (partly from the Polytechnic) spent without achieving the
objectives, and a bad image for the association.
In recent years with the launches of Hermes V0 and V1 and especially
with the Lynx project, the name of Skyward has been painstakingly
rehabilitated in the eyes of the Polytechnic, even if the road is still
long. Participating in the European competition, supporting oneself
through sponsors, showing a serious organization, cultivating
relationships with the DAER: this is the right path, undertaken in the
last two year and to be followed in future ones, following ambitious but
feasible and sustainable projects.
**The working tools**
=====================
This paragraph describes the main work tools used by the association. It
is important that all members adapt and use these tools 100% in order to
make intra and inter departmental collaboration as simple and effective
as possible.
*Slack*
-------
Slack is the association carried online. It is divided into channels,
which can be public or private. Each member can subscribe to public
channels freely, or be invited to private ones. Single or group chats
are also available. However, once created, the latter cannot be extended
to include other people, so the advice is to only use chats between two
members. Another note is that private channels cannot be made public,
while the opposite is allowed. Furthermore, each message on slack is
actually a thread to which you can reply directly, in this way the
channel remains well organized and it is easy to distinguish the topic
discussed.
**100% of the organization of the teams is on Slack**, in order to
improve traceability (unlike a Whatsapp chat, everything remains on
Slack, also visible by future members) and collaboration with other IPTs
(for members external to ours team it\'s easy to join our channel and
leave a message). It is imperative that members have Slack on all
devices and **enable notifications so they always stay up to date!** It
is also important to have a **profile complete with photo** (where you
can see the face), **telephone number and position held** (written as
Member / IPTL / CD \'3-letter department code\' - \'Project\' (eg. IPTL
STR - Pyxis )), and that they are as active as possible. It is advisable
to enter these channels and periodically check if channels of interest
are created:
| | |
|----------------------------------|---------------------------------|
| General channels | **general**: Topics addressed to the entire association |
| | **gemini general**: Same as |
| | general, but for the |
| | gemini project |
| | **random**: Random messages, non legati ai progetti |
| | **rocketposting**: Messaggi random a tema missilistico) |
| | **viaggio roccaraso**: Where the test launch in Roccaraso is organized |
| Strutture | **dpt structures**: Department channel |
| | **help fem abaqus** |
| | **help solidworks** |
| Avionics | **dpt avionics** |
| | **ipt electronics** |
| | **ipt software development** |
| | **ipt guidance navigation and controlscs helpdesk** |
| Recovery Systems | **dpt recovery system:** Department channel |
| | **ipt parafoil** |
| Aerodynamics and Flight Dynamics | **dpt aerodyamics and flight dynamics:** Department channel |
| | **ipt aerodynamics** |
| | **ipt aeroelasticity flight dynamics** |
| | **ipt mission analysis** |
| Logistics and Media | |
| | **dpt logistics and media:** Department channel |
| Propulsion | **dpt propulsion**: Department channel|
| | **ipt ground segment equipment** |
| | **ipt research and development** |
| | **ipt rocket propulsion system** |
*Google Drive*
--------------
Each Skyward member is equipped with an \@skywarder.eu account managed
by Google, and can therefore access the entire suite of Google services,
such as Drive, as well as other services such as Slack and GitLab. All
the material used during the development of the missile, the
documentation, the reports, the accounts, the scripts, EVERYTHING must
be CREATED (documents, sheets, presentations) or uploaded (images, pdf,
scripts) to Drive. **Saving material in your personal space makes
information retrieval difficult and is strongly discouraged**. Again, it
is essential to use Drive so that the documents can be consulted by
everyone, and for compatibility reasons **it is FORBIDDEN to upload
Word, Excel, PowerPoint files**: they must be created directly on Drive
using the Google counterpart of the aforementioned programs, and using
the templates made available.
The material of the association is mainly contained in
[[this]{.underline}](https://drive.google.com/drive/folders/0B41AbAqKq4Jnd0FVQklnSFF0aWs?resourcekey=0-g22LLUyVbUCdFzA8UvBOpA&usp=sharing)
shared folder, in which there are, among others, one sub-folder per
project and one per department. It is recommended to set shortcuts of
the folders of interest directly in your personal space so as to easily
retrieve the material.
*Online meetings: Slack / Webex*
--------------------------------
Meetings in presence will always be preferred to online meetings, but if
necessary, Slack will be used, if the number of participants is small,
or Webex, so as to be able to connect from the Politecnico classrooms in
case of need. The reference platform is Slack.
*In presence work*
------------------
The most important work tool is face-to-face work. The spaces that the
Politecnico has reserved for us are \"C2\" (a room in building B14 with
an independent entrance which can be accessed after taking the safety
course) and \"B21\" (half, for now, of building B21 , opposite the B14).
As mentioned, it is essential that the members of each team know each
other and know the other departments: Skyward is not individuality. Each
department is fundamental to the realization of the project, and
**collaboration is essential** therefore encouraged. The spaces in
question are completely entrusted to the association, therefore **it is
mandatory to keep the work environment in order by cleaning and
arranging the material used**.
*Google Calendar*
-----------------
There is a Google Calendar shared with the main milestones of the
project, which in any case will also be reported on ClickUp. At the
moment it is not mandatory to use Google Calendar, but it is strongly
recommended as it could be used more and more in the coming months.
*Jira*
------
Jira is the management software for organizing project-level tasks.
During team meetings, tasks for the week will be assigned directly on
Jira. As with Slack, you need to have Jira on all possible devices, even
if the desktop app is far more complete and easier to use. To start use
Jira follow the guide at the following link [[\[GEM\] Jira
Rules]{.underline}](https://docs.google.com/document/d/1UPb-DmakXu2LNDRr1BoRKcyBQgX3yeKqX0JfBHTxlQw/edit?usp=sharing).
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment