Intellectual Property Considerations
The intent of this project is to keep as much
information publicly available as possible. Once completed,
the aim of the project is to generate notoriety for
Rochester Institute of Technology in the realm of deep
space technology, and to keep the design open source and
accessible to any research groups, engineers, etc. that
wish to create similar projects in the future.
The team collectively discussed each member's co-op,
in-class, and out-of class experiences, highlighting
strengths and weaknesses throughout the discussion. The
specific roles each team member was assigned are not
exclusive, as teamwork necessitates cooperative effort.
In light of the aforementioned, every team member is held
responsible for knowing what each role is responsible
for, so that the tasks for each role can be done by any
team member in the event of an emergency.
The following is a table of team members, their key
strengths, and their role within the team.
Rapid prototyping, CAD, ergonomics, and conceptual
Jake Van Cuyck
Circuit design, electrical component selection, and
Electrical Engineer and Morale Officer
FEA, CAD, and facilitating team discussions
Co-Team Lead and Mechanical Engineer
Public speaking, leadership, and design for
Team Leader and Mechanical Engineer
Organic design, researching, and human factors
Finance / Purchasing and Biomedical Engineer
CAD, mechanical design, and aerospace systems
Scribe and Mechanical Engineer
Organization and project management
Planner and Industrial Engineering
System integration, circuit design, and wiring
Electrical Engineering Specialist
Notable limitations of our team's skill pool include
little precision manufacturing capabilities and little
Space and Aerospace systems knowledge.
Team Values and Norms
Team values and norms were collectively generated by
the group in an open discussion, and can be viewed below.
When team members feel that violations of the team norms
are being made, they will first and foremost discuss the
issues with each other before bringing the problems to an
outside source such as the team guide or instructors.
Team members will show up within ten minutes of agreed
upon start times, or ten minutes prior for design reviews.
Members should give reasonable notice, within the ten
minute window, for any tardiness, and as far-out as
possible for upcoming absences.
Honesty is the foundation a strong team. All members
are expected to display a strong moral character. Lying,
cheating, or stealing will not be tolerated.
Clear and Consistent Communication
All team members will check messages and emails at
least once a day, and are expected to respond within one
day of receiving a communication from another member.
Communication will be clear, so that all members can
understand the content. Communication with people outside
of the team will be clear and professional. Team members
sending any emails to stakeholders or subject matter
experts will CC team members.
Discussions about the project or team performance will
be constructive and civil in nature. At no point will
anyone make any comments in malice towards an individual or
group. Any problems with the project or the team will
always be followed up with at least one suggested solution
so that the discussion can continue towards an agreed upon
resolution. If a team member is speaking, the rest of the
members will try not to interrupt them.
Below is a flow chart on how the team will handle
change management when it comes to different aspects of
this project. The specific change management document will
be updated and uploaded phase by phase.
Change Management Flow Chart
Risk Assessment and Growth Curves
Below are our Technical, Resource, Safety, and
Environmental Risk Tables. The Risk Matrices and Excel file
can be found on the "Home" page under "Work Breakdown: By
Technical Risks Table
Resource Risks Table
Safety Risks Table
Environmental Risks Table
The chart below contains the group's contacts and
advisers with their skills. The order of the resources
are in the order in which they were approached by the
group for assistance.
Dr. Kathleen Lamkin-Kennard
Our faculty guide, customer, and deployable-soft
Our MSD guide and experienced project and design
Industrial Design adjunct professor and expert in
Human factors, spacecraft Layout, and spacesuit
docking design for NASA
Dr. Cory Stiehl
Systems engineering for advanced life support systems
for manned space program at NASA
Contracting Lead for NASA
Michael Buffalin IV
Director at The Construct @ RIT
Team Communication and Meeting Minutes
- The customer point of contact is Michael Garcia,
Mechanical Engineer and Scribe. The customer is Dr.
Kathleen Lamkin-Kennard. Russell Phelps is the faculty
guide for the team.
- The preferred method of contact between the point
of contact and the costumer is email.
- The expected frequency of communication is 1
email per week.
- The costumer is available for all 5 reviews. Each
review is expected to take on a Monday 2:00pm-4:45pm.
- Michael Garcia will handle costumer communication.
- It is expected that all team members will be
copied on costumer emails.
- Pre-read documentation will be shared with the
costumer via email which will include a link to
- In-team communication will take place Facebook
Messenger. Secondary communication will take place via
- The preferred method of communication is Facebook
- It is expected that the faculty guide will be
included in communication that involves pre-read
documents or that includes information regarding
meetings with him.
- It is expected that all team members will be
copied on in-team messages that include action item
updates, meeting times, and expected work.
Communication regarding combined tasks between
specific team members does not need to shared with
the entire team.
Below is the Master Gantt Chart for the team. It is a
work in progress and will be updated once a phase. The
Excel file can be found on the "Home" page under "Work
Breakdown: By Topic."
Master Schedule - MSD I
Master Schedule - MSD II
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