P20101: 3u Cubesat Flight Control

Planning & Execution

Table of Contents

Intellectual Property Considerations

This MSD project is not restricted by any Intellectual Property agreements, either with the customer or any sponsoring entity. All team members involved have agreed to share the rights of intellectual property produced by the project. The customer, SPEX, has also made it known that for ease of use and integration into future CubeSat projects, and to benefit space exploration as a whole, they would like at minimum, the designs for the attitude determination and control system to be made publicly available and Open Source. The team is considering pursuing a Creative Commons license for this application.

Team Setup

This team has adjusted the suggested team member titles to a space-industry standard. The necessary responsibilities are still carried over but disguised under different, more appropriate, titles of a space mission.

Amber Dubill is the principal investigator. She will lead the team as a whole to make sure the milestones are passed efficiently and the team continues toward success. James Parkus is the systems engineer. He will be responsible for ensuring all systems work together and function as intended. He will review all designs and provide feedback. Jarrett Wehle is the primary electrical engineer. He will be responsible for designing and fabricating all the electrical components of the communications and power system. He will also fulfill the role as purchaser for the team. Nick Amatruda is the test engineer. Nick will perform component-level and system-level tests to ensure all mechanisms and subsystems work together in unison. Sarah Wittenauer is the primary mechanical engineer. Sarah will be the lead designer for all mechanical systems and will contribute to the overall function of the Solar Sail deployment. Charles Nystrom is the flight software engineer. Charles will be responsible for fully developing the flight software based on the mission profile and mission requirements.

Team Values and Norms


Each team member is expected to show up within 10 minutes of meeting times. If this is not doable, members need to let the rest of the team know in advance if they are not available for required meeting times. Whenever progress is made, it is expected that the designated team member updates documentation within the week of significant changes.


Each team member is to make meaningful contributions to the project based on their skill set. Members are responsible for thoroughly researching their subject to complete designated tasks. From this, all design decisions should be able to be justified.


To minimize overwriting issues each team member should update the entire team when EDGE website is updated. Team members are responsible for updating all documentation for their designated tasks, ie EDGE repository, EDGE website. Each team member is responsible for double checking other team members work once completed and updated, though all work should be as accurate as possible to begin with.

Ethical and Professional

No plagiarism or cheating of any kind shall take place. All citations and references are accurate and clearly listed. Each team member shall be treated with respect by other members. All communications with customer is professional and formal.

Project Plans & Schedules

Gantt Chart

Gantt Chart

Gantt Chart

Risk Assessment and Growth Curves

Risk Management

Risk Management

Other Team Resources

The planned meeting space for project discussion and design will be the MSD floor. The planned meeting space for electrical discussion, testing, and design will be the 3rd floor MSD EE laboratory. The planned meeting space for mechanical fabrication will be the KGCOE machine shop. All the machining and assembly will be performed on a clean space in the KGCOE machine shop, unless that work in contracted out to another company due to high complexity parts.

The standard CAD program for this team is CREO 5.0. The simulation software will be the student version of ANSYS. The engineering program is MATLAB R2019a.

Meeting Minutes, Notes, & Actions

Meeting Notes are taken each meeting by the Facilitator. Action items are noted in the meeting notes and also placed in our slack at the end of the meeting.

Peer Reviews


Provide feedback that enables improvements in effectiveness and efficiency of individuals and the whole team.


  1. Instructions and EXAMPLE must be deleted before the Problem Definition Review.
  2. Identify an owner for this document.
  3. Each team member will assess each of their team mate per the criteria established in the Values and Norms section.
  4. Each member will acknowledge excellent behaviors of their fellow team members and provide constructive recommendations to improve the team effectiveness and/or efficiency. (plus/delta recommendations)
  5. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

Inputs and Source

  1. Team members.
  2. Template and Example.
  3. Reference doc.
  4. Guide.

Outputs and Destination

Review form that is shared with Guide at the end of each cycle. All peer reviews are done using the myCourses peer2peer tool, and teams will discuss the results with their guide after each phase.


Customer Contact: Mihail Barbosu Contact via: mxbsma@rit.edu

The team will have weekly communication via email and set up design reviews as needed. Customer is required to be at all reviews, which should not be an issue. The project manager/ principal investigator is to be the main point of contact for the customer communication. All team members, plus the guide will be cc'd on all emails. All pre-reads will be sent at least a day before the established review times.

The team will internally communicate via slack. Email is used to update the guide, and to contact any outside resources. The team members should be cc'd on any relevant progress or responses.

Project Reviews

Preparation, notes and actions, etc. Refer to Gate Reviews page, as well.

Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation