P16250: Self-Powered Autonomous Aquatic Vehicle

Planning & Execution

Table of Contents

Team Setup

Listing of Team Members
Team Member Current Role(s) Strengths/Interests Relevant Experience/Skills
Erika Bliss Project Manager, Purchasing Coordinator Project Management, Stats- Linear Regressions & Statistical Quality Control Aided a project manager during a project that introduced a new piece of equipment to the production floor
Andy Litzinger Electrical Engineer, POC for customer Hardware, motors, photo-voltaic Project management experience, avid boater
Max Kelley Electrical Engineering Lead Radio communications, embedded systems, robotics Second place winner at ASEE two year college design competition, lead programmer on MCC RoboMagellan
Matthew Haywood Computer Engineering Lead, Electrical Engineer Robotics, embedded systems, CAD, system modelling Taken all robotics classes offered by EE department, successfully built 4 robots
Matt Webster Mechanical Engineering Lead CAD, mechanical system modelling & analysis Taken and currently taking alternative energy classes.
Tyler Malay Mechanical Engineer Mechanical design, Machine shop, CAD Co-op for a company that designs and builds solar powered equipment

Team Values and Norms

Document Owner - Erika
Each team member will be prompt and arrive at the team meetings on time. If an unexpected conflict comes up, the absent team member will preferably send a message in Slack (or message another individual on the team) at least an hour prior to the arranged meeting time. If the team member is running late, he/she has to inform the group at least 30 minutes prior to the meeting. An absent team member should confirm that someone else in the group has received the message.
Each team member will complete their tasks thoroughly and completely, so that the work does not have to be re-done by a peer on the team. If a member does not know how to complete a task, feels overwhelmed, or needs assistance then the member notifies peers, and seeks assistance either from a peer, the faculty guide, a faculty consultant, or another person. Each member must be accountable for their own decisions and take appropriate action when necessary.
Each team member completes their work accurately and in a way that can be easily checked for accuracy by peers and the faculty guide. All work is fully documented and easy to follow.
Professional and Ethical
Each team member gives credit where credit is due. All work completed includes citations to appropriate literature, or sources of assistance. If a team member has gotten assistance from a publication or individual, then that assistance or guidance is fully documented in the reports prepared. Each team member is honest and trustworthy in their dealings with their peers.
Demonstrates the core RIT values of SPIRIT http://www.rit.edu/overview/vision.html
Each team member will contribute an equal share to the success of the project. If a team member is overloaded during a certain week due to other commitments, he/she will make up the workload the following week. Each team member is expected to complete the work in a timely fashion.
Members are expected to attend at least 90% of the meetings. Tangential conversations will be kept to a minimum so that everyone can be actively engaged in the meeting in order to accomplish the meeting goal. Team members will readily provide updates on tasks-in-progress. Each member should be given the chance to provide input, be open with their ideas, and maintain a level of professionalism.
For decisions that require a group setting, trust between members is imperative for issues that involve a person's particular skill set. If this is not an option, a consensus must be reached within the group. As a last resort, a majority vote will determine the outcome of a decision. Conflict within the team will be addressed maturely, and flexibly depending on the situation. If the conflict cannot be handled internally, involvement of the guide will be sought.

Project Plans & Schedules

Tasks will be assigned on Asana. Erika will update the project schedule according so that it will be reflective of Asana.

Project Schedule - Project 2013

Project Schedule for MSD II can be found here below.

MSD II - Project 2013

Change Control Process

Erika will inform all team members when she has received a Change Proposal form and when a decision regarding its change resolution (whether the change has been accepted or rejected) has been made.

Steps consists of:

  1. A change can be generated by anyone on the project team
  2. The requester will fill out a Change Proposal form and hand it to Erika
  3. Erika will update the Change Request Register
  4. The Change Proposal will be reviewed by Erika and the team lead(s) for which the change will impact
  5. The change will either be approved or rejected
  6. If approved, the change will be implemented

The Change Proposal form can be found here.

The Change Request Register can be found here

Issue Management

We will use this spreadsheet to record, track, prioritize, and close project issues.

Idea Management System

We will use this spreadsheet to record, track, prioritize, and close project issues.

Closure Plan

The document that be filled out at the end of MSD II that describes project closure can be found here

Time Accounting System

The spreadsheet that records the actual amount of work applied towards each activity can be found here

Cost Accounting System

The spreadsheet that records the actual cost of each activity can be found here

Other Project Plan Items

The Configuration Management Plan, Communications Plan, and Procurement Plan can be found here.

Purchase ledger can be found here

Risk Assessment and Growth Curves

Initial Risk Assessment

Associated Risks for Self-Powered Autonomous Aquatic Vehicle (SPAAV)
Risk Number Technical Resource Safety Societal/Environmental
Risk 1 Hole in the boat could cause it to sink Lack of water Run-away boat Environmental contamination
Risk 2 Water gets into electrical components Weather prevents prototyping Injury to the team when launching Could become a nuisance to other boaters
Risk 3 Loss of propulsion control Not having enough financial sponsors Electric shock ...
Risk 4 Unable to overcome waves Lack of meeting times Battery explosion ...
Risk 5 Energy harvesting failure ... ... ...

Meeting Minutes, Notes, & Actions


Team Meetings for MSD I
Week Number Date Meeting Notes
MSDI-1 8/27/15 Minutes 8_27
MSDI-2 9/1/15 Minutes 9_1
MSDI-2 9/2/15 Minutes 9_2
MSDI-2 9/3/15 Minutes 9_3
MSDI-3 9/7/15 Minutes 9_7
MSDI-3 9/8/15 Minutes 9_8
MSDI-3 9/9/15 Minutes 9_9
MSDI-4 9/14/15 Minutes 9_14
MSDI-4 9/15/15 Minutes 9_15
MSDI-4 9/16/15 Minutes 9_16
MSDI-4 9/17/15 Minutes 9_17
MSDI-5 9/20/15 Minutes 9_20
MSDI-5 9/22/15 Minutes 9_22
MSDI-5 9/24/15 Minutes 9_24
MSDI-5 9/26/15 Minutes 9_26
MSDI-7 10/4/15 Minutes 10_4
MSDI-7 10/6/15 Minutes 10_6
MSDI-8 10/11/15 Minutes 10_11
MSDI-9 10/18/15 Minutes 10_18
MSDI-9 10/22/15 Minutes 10_22
MSDI-10 10/27/15 Minutes 10_27
MSDI-10 10/29/15 Minutes 10_29
MSDI-11 11/3/15 Minutes 11_3
MSDI-11 11/5/15 Minutes 11_5
MSDI-12 11/10/15 Minutes 11_10
MSDI-12 11/12/15 Minutes 11_12
MSDI-13 11/19/15 Minutes 11_19
MSDI-14 11/24/15 Minutes 11_24
MSDI-15 12/1/15 Minutes 12_1
MSDI-15 12/3/15 Minutes 12_3


Week 7 had a customer update. Week 8 had a demo.
Team Meetings for MSD II
Week Number Date Meeting Notes
MSDII-2 2/2/16 Feb 2 Minutes
MSDII-3 2/9/16 Feb 9 Minutes
MSDII-3 2/11/16 Feb 11 Minutes
MSDII-4 2/18/16 Feb 18 Minutes
MSDII-5 2/23/16 Feb 23 Minutes
MSDII-6 3/1/16 March 1 Minutes
MSDII-9 3/29/16 March 29 Minutes
MSDII-9 3/31/16 March 31 Minutes
MSDII-10 4/5/16 April 5 Minutes
MSDII-10 4/7/16 April 7 Minutes

Individual Project Status Tables

Max Kelley

Andy Litzinger

Matt Haywood

Matt Webster

Tyler Malay

Erika Bliss

Project Reviews

Problem Definition Review

System Level Design Review

Subsystem Level Design Review

Preliminary Detailed Design Review

Detailed Design Review

Home | Planning & Execution | Imagine RIT

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

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