Planning & Execution
Table of Contents
Project SummaryProject Name: Jib Transfer Bench
Project Number: P13031
Project Time Span: MSD I / MSD II: 2012-2 / 2012-3
Mission Statement: The purpose of the Jib Transfer Bench MSD Project is to implement the fundamentals of engineering to create a device to assist a disabled sailing crew, enhancing both their abilities and quality of life.
Project Description: Last year, a team of engineers in MSD worked with Keith Burhan and Richard Ramos to incorporate Keith's design for a swiveling captain chair into Richard's boat. Richard is a C 4-5 quadriplegic so the design incorporated a chair that could hold him securely and a bicycle adaptation for his hands so that he could steer the boat from the chair.
The person crewing with Richard responsible for trimming the Jib sail, Cindy Walker, has limited use of their legs. Team Paradise, a disabled sailing club, has implemented a Jib transfer bench for paraplegics in one of their sail boats. They have a design for a marine plywood and carbon fiber system capable of providing the support needed to accommodate a paraplegic athlete. This design has potential to be re-engineered by future teams so that it is easier to manufacture and less costly. Peter Goldman has shown an interest in implementing a Jib transfer bench such as this in a boat for his sailing club as well. Both boats considered for implementation of this transfer bench are Sonars.
To trim the jib sail they need to get from the left to the right side of the boat. Because the athletes have limited to no leg or core strength they need to use their arms to move themselves. The distance between the seats on either side of the boat is too great to span without considerable arm strength, so currently the person must travel from one seat, to the floor, and back up onto the other seat. This devise should make it easier for the athletes to get from one side to the other. By easier I mean it should take less force and less time to make the transition.
Intellectual Property ConsiderationsRIT owns all intellectual property for this project.
|Customer Need #||Importance||Description|
|CN1||1||Make it easier (require less force) for the jib trimmer to get from port to starboard|
|CN2||2||Decrease the time for the jib trimmer to get from port to starboard compared to if they have no use of their legs and limited to no core strength|
|CN3||1||Design will be light weight|
|CN4||3||Eliminate the need for the person to make contact with the floor of the boat|
|CN5||1||Provides the user access to jib lines|
|CN6||2||Design is an entirely mechanical solution|
|CN7||1||Design is easy to use|
|CN8||1||Provides support for legs and core|
|CN9||1||Design is easy to install|
|CN10||1||Move between port and starboard|
|CN12||1||Design must ensure safety for user|
|CN13||1||Do not hinder ability to see around the boat|
|CN14||1||Accepts customer's cushion|
(1=high priority 2=medium priority 3=low priority)
The Specifications Excel File is a rolling list of how the Customer Needs correspond to Metrics. For example, a Customer need is that the device must be "a light weight". This document maps that need to an engineering metric with marginal and nominal targets.
Team Norms & Values
Our Team Norms and Values establish the parameters for us to work together and function effectively as a group. Every 3 weeks, we evaluate our performance over the evaluation period. In doing so, we know where everyone stands on the performance and cohesiveness of the group and the overall strength of the team moving forward.
Project Plans & SchedulesMSD I & II: WBS, Gantt charts, schedule, etc
Nick, our resident Industrial Engineer, has been keeping a rolling Project Plan. This is revisited and updated regularly.
Meeting Minutes, Notes, & Actions
A list of all of the team meetings we had during MSD I is compiled here: Meeting List. Every meeting had at least three team members, though most had all in attendance. We met Tuesday and Thursday nights at 6:00 PM during MSD I.
During MSD II, it became increasingly difficult to capture every minute that every person spent on each activity. Much of the work was delegated and handed off to others throughout the days. Multiple team members collaborated on the build, construct, and test phases, making it difficult to accurately total the time spent on each activity.
A rolling Microsoft Word document compiling weekly Team Meeting notes electronically was started during Week 10 of MSD I, and is compiled here. This document encompasses the work performed MSD II Project Execution and Logbook Capture
Future teams should start this during week 1, to accurately capture every task completed with relative ease (as compared to trying to sort it all out at the end of the quarter).
Peer ReviewsMSD I