Skip to content

Commit 4765d0d

Browse files
committed
link and power budget how to and schedule page
1 parent 7de4cb0 commit 4765d0d

8 files changed

Lines changed: 24 additions & 13 deletions

File tree

_site/about/index.html

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.

_site/index.html

Lines changed: 1 addition & 1 deletion
Large diffs are not rendered by default.
224 KB
Loading

assets/images/schedule-sheets.png

26.8 KB
Loading

com-members/power-budget.md

Lines changed: 0 additions & 7 deletions
This file was deleted.
Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
2-
title: Making a Link Budget
3-
parent: Ground Segment Integration
4-
grand_parent: For COM Team Members
2+
title: How to Make a Link Budget
3+
parent: How-to guides
54
layout: default
65
lang: en
76
---

how-tos/power-budget.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
title: How to Make a Power Budget
3+
parent: How-to guides
4+
layout: default
5+
lang: en
6+
---

how-tos/schedule.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,12 @@ Follow these steps:
3838
- **PDR**: Validate preliminary designs, ensuring alignment with mission requirements.
3939
- **CDR**: Finalize detailed designs for all subsystems.
4040

41+
If you know your expected launch date or when you want the project to be completed, you can identfy the dates of the above milestones to fit to your completion date. You should try not to spend too much time in the ideation phase, as the aim is to devlop a hands-on project, once you start building things will still change.
42+
43+
Once you have your mission in mind, set out to start developing the subsystem requirements to make that mission successful. This will be inthe form of a requirements sheet (if you don't know how to do that, [you can find the tutorial here.]({{site.url}}/how-tos/req-sheet))
44+
45+
Your MDR ideally shouldn't be more than 2 months after identifying your mission.
46+
4147
**Result**: A high-level structure for the schedule is established.
4248

4349
2. **List major project tasks.**
@@ -106,13 +112,20 @@ Here is an example timeline for a CubeSat project:
106112
| Release & operation | Month 14 | |
107113
| Disposal | Month 20+ | |
108114

115+
![schedule-complete](/assets/images/schedule-complete.png)
116+
109117
### Sub-tasks
110118

111119
If the schedule is complex, you can divide it into sub-tasks, such as:
112120

113121
- Assigning responsibilities to subsystem teams.
114-
- Creating detailed schedules for each subsystem.
122+
- Creating detailed schedules for each subsystem. Templates for subsystem schedules can be found here.
115123
- Periodic reviews and updates to the schedule based on progress.
124+
- each subsystem can have their own sheet that details the subsystems tasks under each section,
125+
- you can also have sheets dedicated to the milestone tasks to have a clearer view of what is needed for each milestone.
126+
127+
![schedule-sheets](/assets/images/schedule-sheets.png)
128+
116129

117130
## See also
118131

0 commit comments

Comments
 (0)