Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development #19

Merged
merged 3 commits into from
Nov 16, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions _project-managers/pm-encourage-team.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
title: Encourage your team
layout: default
lang: en
---

# Encourage your team
{: .no_toc }


## Get to know your members

## Organise social events for your team
8 changes: 8 additions & 0 deletions _project-managers/pm-freq-coord.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
title: Organise Frequency Coordination
layout: default
lang: en
---

# Organise Frequency Coordination
{: .no_toc }
8 changes: 8 additions & 0 deletions _project-managers/pm-frr.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
title: Organise Flight Readiness Review
layout: default
lang: en
---

# Organise Flight Readiness Review
{: .no_toc }
40 changes: 16 additions & 24 deletions _project-managers/pm-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,47 +29,39 @@ Some of the responsibilities of a project manager include:
- Building a team: Choosing team members with the right skill set and leading them effectively


## How-tos
## How-to
{:toc}

### Manage your team
{:toc}

- [Make a satellite schedule]({{site.url}}/pm/guide/)
- [Organise weekly meetings]({{site.url}}/pm/guide/)
- [Organise sub-team meetings]({{site.url}}/pm/guide/)
- [Organise social events for your team]({{site.url}}/pm/guide/)
- [Plan satellite lifecycle]({{site.url}}/project-managers/pm-lifecycle-plan)
- [Organise meetings]({{site.url}}/project-managers/pm-org-meetings)
- [Encourage your team]({{site.url}}/project-managers/pm-encourage-team)


### Documentation Management
{:toc}

- [Choose a DMS]({{/_project-managers/pm-choose-a-dms.md}})
- [File/ Folder Naming Conventions]({{/_project-managers/pm-naming-conventionsl}})
- [Organise sub-team meetings]({{site.url}}/pm/guide/)
- [Choose a DMS]({{site.url}}/project-managers/pm-choose-a-dms)
- [File/ Folder Naming Conventions]({{site.url}}/project-managers/pm-naming-conventions)

### Risk Management
{:toc}
- [Make a satellite schedule]({{site.url}}/pm/guide/)
- [Organise weekly meetings]({{site.url}}/pm/guide/)
- [Organise sub-team meetings]({{site.url}}/pm/guide/)
Project managers have several risk management tasks, including:
Identifying risks: The first step in the risk management process, this involves finding events that could impact the project.
Analyzing risks: Using risk analysis methods to prepare for and react to risks.
Developing a risk management plan: A document that identifies, prioritizes, and documents risks, and outlines how to deal with them.
Creating a risk response plan: Developing strategies to address risks and reduce their impact on the project.
Keeping a risk register: A document that tracks risks before they escalate, making it easier to find solutions.
Communicating risks: Communicating the right risk to the right person at the right level.
Monitoring risks: Staying vigilant to prevent obstacles and threats from escalating.
Taking corrective action: Taking action as needed.
Risk management is an important competency for project managers, as it helps teams prepare for any outcome.
- [Identify and analyze risks]({{site.url}}/project-managers/pm-identify-analyze-risks)
- [Develop a risk management plan]({{site.url}}/project-managers/pm-risk-mgmt-plan)
- [Communicate and Monitor risks]({{site.url}}/project-managers/pm-monitor-risk)


### Prepare for milestones
{:toc}

- [Make requirement list for MDR]({{site.url}})
- [Make requirement list for PDR]({{site.url}})
- [Make requirement list for CDR]({{site.url}})
- [Make requirement list for MDR]({{site.url}}/project-managers/pm-mdr-reqs)
- [Make requirement list for PDR]({{site.url}}/project-managers/pm-pdr-reqs)
- [Make requirement list for CDR]({{site.url}}/project-managers/pm-cdr-reqs)
- [Organise Frequency Coordination]({{site.url}}/project-managers/pm-freq-coord)
- [Organise Safety Review]({{site.url}}/project-managers/pm-safety-review)
- [Organise Flight Readiness Review]({{site.url}}/project-managers/pm-frr)

### Project Management Tools and Techniques
{:toc}
Expand Down
17 changes: 17 additions & 0 deletions _project-managers/pm-identify-analyze-risks.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: Identify and analyze risks
layout: default
lang: en
---

# Identify and analyze risks
{: .no_toc }


Project managers have several risk management tasks, including:

## Identifying risks:
The first step in the risk management process, this involves finding events that could impact the project.

## Analyzing risks:
Using risk analysis methods to prepare for and react to risks.
11 changes: 11 additions & 0 deletions _project-managers/pm-lifecycle-plan.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
title: Plan satellite lifecycle
layout: default
lang: en
---

# Plan satellite lifecycle
{: .no_toc }


## Make Satellite Schedule
24 changes: 23 additions & 1 deletion _project-managers/pm-mdr-reqs.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,26 @@ lang: en
---

# Make requirement list for MDR
{: .no_toc }
{: .no_toc }

Each subsystem needs to understannd what they are required to present at each milestone review.

The Mission Definition Review is the first milestone in your satellite's lifecycle.

As the name implies, this review is to identify the main mission(s) of the satellite and how capable each subsystem is of achieving it.

Let's go through what each subsystem needs to present

### OBC


### BPB


### EPS


### COM


### Mission
19 changes: 19 additions & 0 deletions _project-managers/pm-monitor-risk.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: Communicate and Monitor risks
layout: default
lang: en
---

# Communicate and Monitor risks
{: .no_toc }


## Communicating risks:
Communicating the right risk to the right person at the right level.

## Monitoring risks:
Staying vigilant to prevent obstacles and threats from escalating.

## Taking corrective action:
Taking action as needed.
Risk management is an important competency for project managers, as it helps teams prepare for any outcome.
14 changes: 14 additions & 0 deletions _project-managers/pm-org-meetings.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
title: Organise meetings
layout: default
lang: en
---

# Organise meetings
{: .no_toc }


## Organise weekly team meetings


## Organise sub-team meetings
18 changes: 18 additions & 0 deletions _project-managers/pm-risk-mgmt-plan.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
title: Develop a risk management plan
layout: default
lang: en
---

# Develop a risk management plan
{: .no_toc }


Developing a risk management plan:
A document that identifies, prioritizes, and documents risks, and outlines how to deal with them.

## Creating a risk response plan:
Developing strategies to address risks and reduce their impact on the project.

## Keeping a risk register:
A document that tracks risks before they escalate, making it easier to find solutions.
8 changes: 8 additions & 0 deletions _project-managers/pm-safety-review.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
title: Organise Safety Review
layout: default
lang: en
---

# Organise Safety Review
{: .no_toc }
25 changes: 13 additions & 12 deletions _resources/glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,10 @@ lang: en

# Glossary

# {If you need more information about how to fill in this template, read the accompanying [Glossary template guide](https://gitlab.com/tgdp/templates/-/blob/main/glossary/guide_glossary.md).}

# {This template includes boilerplate text that you can customize, use as-is, or completely replace with your own text. This text is indicated in {curly brackets}. Make sure you replace the placeholders with your own text.}

| Term | {Optional} Abbreviation | Definition
| Term | Acronym | Definition
| --- | --- | --- |
| Attitude Determination and Control System |ADCS| |
| Attitude Determination and Control System | ADCS | A system that uses sensors and actuators to determine and control the orientation of a vehicle, such as a spacecraft. ADCS is essential when the orientation of a vehicle is important for its mission, such as for observation or communications.
|
| Automatic Packet Reporting System | APRS | The Automatic Packet Reporting System or APRS for short is an amateur radio-based system for real-time digital communications of information.
| BIRDS | |The BIRDS project is the Joint Global Multi-Nations Satellite project. It ws created by the Kyushu Institute of Technology (Kyutech) to help countries build their satellites.
| Bus | | A satellite bus is the main body and structural component of a satellite, in which the payload and all scientific instruments are held
Expand All @@ -24,17 +21,21 @@ lang: en
| Mission Definition Review | MDR | Mission Definition Review or MDR involves assessing the primary objectives and feasibility of the satellite. It is done by evaluating the mission's definition, system design, and other important aspects
| Systems Tool Kit | STK | Systems Tool Kit (STK) is a modeling software used by engineers and scientists to analyze and simulate real-world problems, related to satellites, spacecraft, and aircraft
| Gaussian Minimum Shift keying | GMSK | The GMSK is a modulation technique used in satellite communications systems. It carries just 1 bit per symbol. |
| QSL Card | | A QSL card is a written confirmation of radiocommunication involving a one-way reception of a signal (from an AM radio, FM radio or television), between two amateur radios, or the reception of a two-way radiocommunication by a third-party listener |
| QSL Card | The term “QSL” comes from the international Q code and means “I confirm receipt of your transmission”. | A QSL card is a written confirmation of radiocommunication involving a one-way reception of a signal (from an AM radio, FM radio or television), between two amateur radios, or the reception of a two-way radiocommunication by a third-party listener |
| Two-Line Element | TLE | A Two-Line Element (TLE) is a standardised format used to describe the orbit of a satellite
| DNST| |
| PNST| |
| PNST| Post-graduate study on Nano-Satellite Technologies. | More information can be found [here]
| DLP feasibility | |
| Satellite Beacon | | A satellite beacon is a distinct and identifiable signal transmitted by a satellite to indicate its presence or provide essential tracking information.
| On-Board Computer |OBC| An On-Board Computer (OBC) is a satellite's central processing unit that runs the satellite's software and controls its vital functions. It is the brain of the satellite.
| Electrical Power System |EPS| An electrical power system (EPS) is a satellite subsystem that manages the satellie and supplies other systems in the satellite with the necessary electrical power to operate effectively. The EPS is a critical component especially in small satelites such as theluding CubeSats
| Preliminary Design Review | PDR |
| Flight Model Testing | FMT | Flight Model testing ivolves subjecting the satellite, known as Flight Model to undergo several rogorous tests. It is done to verify that the satellite's design and construction meet all the functional and environmental requirements for flight.
| C& DHS| | |
| EM | | |
| FM | | |
|Command and Data Handling System | CDHS| This is another name for the OBC based on the tasks the system performs. |
| Engineering Model | EM | An engineering model (EM) of a satellite is a model that is built to verify the electrical functionality and interfaces of a spacecraft before the flight model is built. It is representative of the flight model in terms of form, fit, and function, but it doesn't have the same level of redundancy as the flight model. An EM can be built at a fraction of the cost of a flight model because it doesn't need to undergo the same lengthy and expensive environmental tests.Once the design passes the PDR, the EM is built. |
| Flight Model | FM | A satellite's flight model (FM) is the final version of the satellite that is built to be deployed into space. It is the result of a series of testing, validation, and refinement processes that begin with the engineering model (EM) and qualification model (QM). Once the design passes the CDR, the FM is built. The FM is built to the highest standards of precision and reliability. However, testing it to the limits may cause micro-cracks in the structure, so it is not tested as rigorously as the QM.|
| Structural and Thermal Model | STM | The Structural and Thermal Model (STM) of a satellite is a model built during the development phase of a spacecraft that is used to test the satellite's subsystems and ensure they are compatible with the launcher and ground systems. The STM is built alongside the Engineering Model (EM) during Phase C of the development process. Both models are subjected to rigorous tests to replicate the conditions of launch. |



-----------
[here]: https://www.unoosa.org/oosa/en/ourwork/access2space4all/PNST/PNST_Index.html
18 changes: 11 additions & 7 deletions index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ If you would want to contribute to, or work with the [BIRDS] community in order
These phases create a structured pathway from conceptualization to launch, with each review and testing stage serving as a critical checkpoint. The **Mission Definition Review** sets the scope, the **Preliminary Design Review** checks the initial design feasibility, the **Critical Design Review** finalizes the detailed design, and **Flight Model Testing** ensures that the satellite is robust and mission-ready. This structured approach helps in mitigating risks, ensuring quality, and promoting mission success.

## **3. What is in the BIRDS bus?**
<p align="center">
<p>
<img alt="birdsx-ext-assembly" src="/assets/images/birdsx-ext-assembly.png" width="45%">
&nbsp;
<img alt="birdsx-board-layout" src="/assets/images/birdsx-board-layout.png" width="45%">
Expand All @@ -98,27 +98,31 @@ These phases create a structured pathway from conceptualization to launch, with
- **Electrical Power System (EPS)**: Manages power generation, storage, and distribution.
- **Attitude Determination and Control System (ADCS)**: Controls satellite orientation and stability.
- **Communications (COM)**: Oversees data transmission to and from the satellite.
<p align="center">
<center>
<p>
<img alt="birdsx-com" src="/assets/images/birdsx-com.png" width="25%">
</p>
</center>
- **Structure**: Designs and constructs the satellite’s physical frame.
<p align="center">
<p>
<img alt="birdsx-frame" src="/assets/images/birdsx-frame.png" width="45%">
&nbsp;
<img alt="birdsx-board-frame" src="/assets/images/birdsx-board-frame-assembly.png" width="45%">
</p>
- **Payload**: Manages mission-specific instruments or sensors.
- **Backplane (BPB)**: Integrates all the subsystems and allows transfer of power and data to each of them.
<p align="center">
<center>
<p>
<img alt="birdsx-bpb" src="/assets/images/bpb-birdsx.png" width="15%">
</p>
</p>
</center>

## *Organizational Chart*
{: .no_toc }
[![](https://mermaid.ink/img/pako:eNp1kV1vgjAUhv9Kc65cgqaVL-ViiYBxX0wTdrXiRQdVSYCaUrI58b-vMmO2hTXnoud9n5yck_cIqcg4eLApxHu6Y1KhlzCpkH4zGjPFiyJXfI2Gw1vkDxZSNFWGYr4teaVu_uGCQbxnKf-DBZ0X0hU7FIJl65_qnEYsr5Df1Bc57OQ24uUbl8hp0YJGeV3nohqSXsRt0d0VGV-Q-S-EtOiexko2qWok70XGLXqgwTLqNc0WPdJZGMS9rtWiJzpf9Zt2iyK69INeU1_3TP2VvwYDSi5Llmc6j-MZTUDteMkT8PQ34xvWFCqBpDpplDVKxIcqBU-fxA3Q0Wx34G1YUeuu2Wc6lDBnW8nKq8qzXAkZfSfeBW_AnlXgHeEDPOKQke1MiS7sTrFtuwYcwDOJNcLndjIlpoWJczLgUwg9FY8ch0zwBLumPcaOg61u3Gtnnrc6fQFYEbPP?type=png)](https://mermaid.live/edit#pako:eNp1kV1vgjAUhv9Kc65cgqaVL-ViiYBxX0wTdrXiRQdVSYCaUrI58b-vMmO2hTXnoud9n5yck_cIqcg4eLApxHu6Y1KhlzCpkH4zGjPFiyJXfI2Gw1vkDxZSNFWGYr4teaVu_uGCQbxnKf-DBZ0X0hU7FIJl65_qnEYsr5Df1Bc57OQ24uUbl8hp0YJGeV3nohqSXsRt0d0VGV-Q-S-EtOiexko2qWok70XGLXqgwTLqNc0WPdJZGMS9rtWiJzpf9Zt2iyK69INeU1_3TP2VvwYDSi5Llmc6j-MZTUDteMkT8PQ34xvWFCqBpDpplDVKxIcqBU-fxA3Q0Wx34G1YUeuu2Wc6lDBnW8nKq8qzXAkZfSfeBW_AnlXgHeEDPOKQke1MiS7sTrFtuwYcwDOJNcLndjIlpoWJczLgUwg9FY8ch0zwBLumPcaOg61u3Gtnnrc6fQFYEbPP)


## **3. What tools do we use in development?**
## **4. What tools do we use in development?**
- **Software**:
- **Computer Aided Design (CAD) tools for Design**: Fusion 360
- **Simulation Tools**: Thermal desktop, STK for mission analysis
Expand All @@ -131,7 +135,7 @@ These phases create a structured pathway from conceptualization to launch, with
- **Sensing Devices**: Magnetometers, gyroscopes for ADCS
- **Version Control**: Git/ [GitHub]

## **4. [Getting Started Steps]({{site.url}}/get-started){: .btn .btn-purple }**
## [Getting Started]({{site.url}}/get-started){: .btn .btn-purple }

----

Expand Down