|
|
| (20 intermediate revisions by one user not shown) |
| Line 3: |
Line 3: |
| | SUNY University at Buffalo's Introduction to Mechanical Engineering course consists of a semester long project involving the reverse engineering of a consumer product. Our group was assigned a 1994 Honda Engine from a CBR 600 F2 bike. The project consists of five separate gates which consist of planning, dissection, analysis, explanation, and delivery. | | SUNY University at Buffalo's Introduction to Mechanical Engineering course consists of a semester long project involving the reverse engineering of a consumer product. Our group was assigned a 1994 Honda Engine from a CBR 600 F2 bike. The project consists of five separate gates which consist of planning, dissection, analysis, explanation, and delivery. |
| | | | |
| − | == Gate 1: Planning == | + | ==[[Executive Summary]]== |
| | | | |
| − | == '''Project Management: Request for Proposal''' == | + | == [[Gate 1: Product Archeology]] == |
| | | | |
| − | '''Management Proposal'''
| + | == [[Gate 2: Dissection]]== |
| − | To accomplish our task in an appropriate amount of time, we have decided to meet twice a week, on Tuesdays and Thursdays at 5 PM. Meetings in which we will be dissecting the engine will be held in Furnas 621, and meetings in which we are compiling work will be held at a point which will be determined by the group that week. In the event that we underestimate the amount of time needed to complete a gate, extra meetings will be scheduled by our Communication Liaison, in order to meet our deadline.
| + | |
| | | | |
| − | '''Roles and responsibilities'''
| + | == [[Gate 3: Analysis]] == |
| | | | |
| − | 1. Dale Higgins: Project Manager- Lead team meetings, provide members with updates on project, make sure deadlines are met, divide work on gates between members
| |
| | | | |
| − | 2. Prince Joseph: Communication Liaison- Keep members in contact, contact instructor about project complications, schedule extra group meetings if necessary
| + | == [[Gate 4: Explanation]] == |
| | | | |
| − | 3. Nate Sutorius: Technical Expert- Compiles extra research/information about the product, assists members technical issues, adds additional information to entries
| |
| | | | |
| − | 4. Ryan Grace: Site Manager- Regulates and makes necessary changes to wiki, checks all parts for accuracy, compiles and enters appropriate information
| + | == [[Gate 5: Delivery]] == |
| − | | + | |
| − | 5. Peter Hubert: Documenter- Takes relevant notes/pictures of the disassembly and assembly processes, compiles information from meetings for the wiki, asserts assumptions made during meetings with fact checking
| + | |
| − | | + | |
| − | '''Group conflicts'''
| + | |
| − | | + | |
| − | All conflicts resulting between group members will be resolved as group, as this project is a summation of our collective work. Small issues such as member’s responsibilities and work will be settled by the project manager. If the manager alone cannot settle an argument, an abrupt group meeting will be called to mediate the issue. Conflicts in this setting will be settled by a majority rule, unless a solution cannot be met. In any case such as, the issue will be brought to the instructor.
| + | |
| − |
| + | |
| − | '''Work Proposal'''
| + | |
| − | | + | |
| − | The process of disassembly is going to take place over multiple group meetings, as we are simultaneously analyzing each part of the engine, and also we need to take note of the engine at each state, since we will need to efficiently put the parts back together. The dissection will need to be very carefully done, as the engine has become worn in some parts from past projects groups, and also some minor pieces (nut and screws) are missing. The placement of these minor pieces will be crucial, as the engine should appear as it did when it was first given to us, so we will need to take that into account.
| + | |
| − | | + | |
| − | Our group should not have a problem with the dissection process, but our lack of knowledge of combustion engines would be our only significant shortcoming. Although a few of our group’s members are well versed in engines, some of us do not have that advantage. Too meet this challenge, we plan to do outside research to become more accustomed with our product, and as the project progresses, we will begin to pick up on the subtleties of such an engine. Any extra questions we have will be referred to our Technical Expert, who has the most sufficient knowledge of combustion engines, and will prove to be a great asset. All things considered, with the appropriate tools and a sufficient amount of work, this project should prove to be an interesting and enlightening learning experience.
| + | |
| − | | + | |
| − | The following tools are what we decided from our first analysis would be necessary to effectively dissect this engine. They are as follows:
| + | |
| − | | + | |
| − | • Wrench set
| + | |
| − | | + | |
| − | • Screwdriver set
| + | |
| − | | + | |
| − | • Allen key set
| + | |
| − | | + | |
| − | • Hex ocular socket
| + | |
| − | | + | |
| − | • Camera
| + | |
| − | | + | |
| − | • Plastics bags
| + | |
| − | | + | |
| − | '''Disassembly Process'''
| + | |
| − | | + | |
| − | Since we have not yet fully analyzed the engine, we can only speculate as to what components are on the inside. However, from what we could see, we can develop a rough idea of how we will dissect the product. We will obviously begin at the top and move down to the base of the engine, but more specifically, we disassemble in the following order:
| + | |
| − | | + | |
| − | 1. Air box
| + | |
| − | | + | |
| − | 2. Carburetors
| + | |
| − | | + | |
| − | 3. Spark Plugs
| + | |
| − | | + | |
| − | 4. Detach Head
| + | |
| − | | + | |
| − | 5. Top half of engine block
| + | |
| − | | + | |
| − | 6. Crankshaft cover
| + | |
| − | | + | |
| − | 7. Bottom of engine block
| + | |
| − | | + | |
| − | 8. Oil reservoir
| + | |
| − | | + | |
| − | | + | |
| − | '''Contact Info'''
| + | |
| − | Ryan Grace- ryangrac@buffalo.edu
| + | |
| − | | + | |
| − | Dale Higgins- dalehigg@buffalo.edu
| + | |
| − | | + | |
| − | Peter Hubert- peterhub@buffalo.edu
| + | |
| − | | + | |
| − | Nate Sutorius- nathansu@buffalo.edu
| + | |
| − | | + | |
| − | Prince Joseph- princejo@buffalo.edu
| + | |
| − | | + | |
| − | '''Product Archaeology: Preparation and Initial Assessment'''
| + | |
| − | | + | |
| − | Development Profile:
| + | |
| − | | + | |
| − | Usage Profile:
| + | |
| − | | + | |
| − | == Gate 2: Dissection==
| + | |
| − | | + | |
| − | | + | |
| − | == Gate 3: Analysis ==
| + | |
| − | | + | |
| − | | + | |
| − | == Gate 4: Explanation ==
| + | |
| − | | + | |
| − | | + | |
| − | == Gate 5: Delivery == | + | |
SUNY University at Buffalo's Introduction to Mechanical Engineering course consists of a semester long project involving the reverse engineering of a consumer product. Our group was assigned a 1994 Honda Engine from a CBR 600 F2 bike. The project consists of five separate gates which consist of planning, dissection, analysis, explanation, and delivery.
