MecE 360 Mechanical Design Project Teams & Expectations

MecE 360: Mechanical Design II
Fall 2016 Sept 1 to Dec 7

Project Instructor (PI):
Aleksey Baldygin, Ph.D.
Room: NINT 6-046
Phone: 780 492 4412
Email: baldygin@ualberta.ca
Teaching Assistant for Project:
Brianna Bruni-Bossio
Email: brunibos@ualberta.ca
MecE 360 Design Project: Team Policies and Expectations

Design Project Teams
On Thursday, September 1, 2016 before 8:00 AM, students will receive a survey request on their
study background and interest via a group work teaching software, CATME. Students are required to
provide the input by completing a survey by Friday, September 2, 2016 at 10:00 PM.
Project proposals are to be made available in Appendix below.
On Monday, September 5, 2016, MecE 360 students are to be allocated into teams based on a mixed
metrics of GPA, past course experience, and other factors such as English capability. The team
allocation results will be published via eClass. Design teams of five or six students are expected.
Each team needs to contact the Project Instructor (PI) with a Letter of Intent (LOI)/Bidding letter with
the desired project (first come first serve) via eClass by Thursday, September, 8, 2016 at 5:00 PM.
Each group should discuss their project choice carefully.
Project allocation result will be published by Friday, September, 9, 2016 at 5:00 PM via eClass.
Teamwork is an important evaluation aspect for MecE 360. If you run into any major issue, please
seek help; your group advisors and I shall support your teamwork throughout the course.
Your team will have a number of responsibilities as it completes project assignments. Below are some
suggestions and comments, which are not mandatory since groups may have differing dynamics.
Agree on a common meeting time and what each member should have done before the meeting
(readings, taking the first cut at some or all of the assigned work, etc.)
Do the required individual preparation.
Coordinator checks with other team members before the meeting to remind them of when and where
they will meet and what they are supposed to do.
Consult with your instructor if a conflict arises that can't be worked through by the team.
Reports 1 is not marked, but feedback may be provided by instructor. Groups will provide feedback to
one another, and this feedback will be assessed by the instructor.
Instructor: J.D. Hogan

Project Instructor: A.Baldygin
Rev.: Sep. 6, 2016

Project Assessment Breakdown with Due Dates & Mark Allocation (/100):
Deliverables
Individual Background Survey via CATME
Project Selection/Letter of Intent (LOI)/Bidding Letter
Report 1: Concept report (CR) (peer-assessment feedback)
Report 1: Peer Review Survey via CATME
Report 2: Analysis report (AR) (peer-assessment feedback
and from Project Instructor and/or Instructor)
Report 2: Peer Review Survey via CATME
Electronic Submission of Mid-way Presentation
- Format name: mece360_F16_MWP_07.pdf
or mece360_F16_MWP_07.pptx
Mid-way presentation (Oral Presentation)
- During class: Oct. 31, Nov. 2, and Nov. 4
- During seminars: Nov. 1 and Nov. 3
Electronic Submission of Final Presentations
- Format name: mece360_F16_FP_07.pdf
or mece360_F16_FP_07.pptx
Final Presentation (Oral Presentation)
- During class: Nov. 28, Nov. 30, Dec. 2, Dec. 5, and
Dec. 7
Final report (FR): Detailed Design Report
Problem Definition: 20%
Design Explanation and Choices: 20%
Calculations: 20%
Drawings: 20%
Clarity and Presentation: 10%
Evaluation Effort: 10%
Weight
Y/N
Y/N
Y/N
Y/N
Y/N
Due Time
10:00PM
5:00PM
11:59PM
11:59PM
11:59PM
Due Date
Sept. 2, 2016
Sept. 8, 2016
Oct. 2, 2016
Oct. 10, 2016
Nov. 9, 2016
Y/N
Y/N
11:59PM
11:59PM
Nov. 11, 2016

Oct. 30, 2016
15%
N/A
N/A
Y/N
11:59PM
Nov 27, 2016
15%
N/A
N/A
60%
5:00PM
Dec. 9, 2016
This progressive marking scheme is intended to credit design teams who apply and demonstrate knowledge gained during the
course of the project. That is, marks are earned as we proceed through the design process. Generally, differential grading of
individual members on a team submission is not done; but on rare occasions it may be invoked if a team has serious issues of
group dynamics. Numerical marks are scaled to a letter grade.
Late elements are subject to penalty. For Y/N elements, no marks are allocated for grading; however, failing to submit an
element will incur a 5% course mark deduction for each missed element.
Group Formation
Early in the course, students will complete a background survey as a part of team formation. The team
forming method is based on the CATME software program, which is a licensed teaching tool. Please watch
this video for support logging in.
http://info.catme.org/catme-student-videos/
On Thursday, September 1, 2016, students will receive a survey request on their study background and
interest. You are required to complete the on-line background survey by 10:00 PM on Friday, September
2
Rev.: Sep. 6, 2016

2, 2016. All information must be entered accurately. Input will be checked for quality assurance; and
any incorrect information may be investigated as an academic integrity issue.
You will be assigned to a group of five or six students on a combined and balanced basis of mixed GPAs,
English competence and project preference. This is intended to provide a more uniform learning
environment so that every group and their members have the best chance of having a fruitful learning
experience and further excel with outstanding teamwork.
During the first group meeting, a group charter should be developed to specify your expectations and
commitments to your peers based on the given template which is available on eClass.
Off-line team meetings and work sessions should be conducted. Sharing and challenging ideas, posing
questions and active engagement are essential elements of successful engineering design; not only here,
within the safe confines of University, but also out in the industrial hinterland!
Project Selection
Team project assignments will be available by Monday, September, 5 2016. You will need to organize your
first group meeting as soon as possible. Your teamwork starts then, and is evaluated accordingly by your
peers in each phase submission.
Project proposals are available below in Appendix. Each group will submit a letter of intent (LOI)/Bidding
letter by Thursday, September 8, 2016 at 5:00 PM with desired project (first come first serve) via eClass.
The final project allocation results will be published on the eClass course site by on Friday, September 9,
2016 at 5:00PM. At this point, you will begin meeting with your Project Instructor (PI).
NOTE: An equal number of bids per project will be accepted (1). Bids will be accepted on a first
come first served basis. Bids that are refused will have to bid for a different project.
Group Involvement
Please note that individual grades can differ between team members depending on engagement, project
effort, contribution, accountability, technical competence, and leadership demonstrated. Team members
must commit to work together. If there are issues with working together, it is vital that the group work to
resolve the issue. Group advisor and the course instructor are resources to facilitate conflict resolution. It is
always better to identify problems early and work to resolve them honestly, and without blame.
As you will find out, group work isn't always easy. Team members sometimes cannot prepare for or attend
group sessions because of other responsibilities, and conflicts often result from differing skill levels and
work ethics. When teams work and communicate well, however, the benefits more than compensate for the
difficulties. One way to improve the chances that a team will work well is to agree beforehand on what
everyone on the team expects from everyone else.

Rev.: Sep. 6, 2016

Evaluation Performance (Peer Review Survey via CATME)
Soon after each phase submission, each team member will attest for their peers and own teamwork
performance with specific input items. On-line peer review survey will be conducted via the CATME online tool after each phase submission to substantiate the score determination based on those evaluated
teamwork factors. As with other unmarked submissions, failing to provide timely online feedback each time
will cost 5% of the total course marks per occurrence.
Additional Information
DO NOT USE PLANETARY GEARS OR WORM GEARS in the design. The analysis is different than
what we learn in class, and it just creates confusion. Try to keep your gear system simple.
Application for mixer or grinder could be different from the proposed below. It can be any scale/any
application (e.g. grinder for the shark meat or oil sands, plastic waste at the recycling facility). Randy
Reichardt (the Librarian) is here to help you find relevant standards/literature for your specific case, if you
chose one.
Critical elements for design and analysis:
Motor selection
Gears
Bearings
Shafts
Connections
General casing (no calculations but must be part of drawings)
Fits
Full set of correct engineering drawings
Suppliers:
Here is a list of suppliers for critical components of the project:
QTC Gears: http://qtcgears.com/
Gear Finder: http://qtcgears.com/tools/gearfinder/
Schaeffler/FAG: http://www.schaeffler.ca/content.schaeffler.us/en/index.jsp
Bearing Selection Tool: http://medias.ina.de/medias//hp?lang=en
SDP/SI Gears: http://www.sdp-si.com/
McMaster-Carr: http://www.mcmaster.com/
Notes: QTC and FAG are the two that are primarily used as they are the primary suppliers of metric gears
and bearings, hence are your primary source for the project. SDP/SI has some unique systems (planetary
gear sets, etc.), while McMaster-Carr is just a generally useful source for stock parts with CAD parts
available.

Rev.: Sep. 6, 2016

Project Selection/Letter of Intent (LOI)/Bidding Letter (Y/N)
Recommended effort: 1.5 hrs/person.
Each group is required to submit a standard, one-page, business-format letter addressed to the course
instructor. This letter must:
Identify all design team members
Given and family names (formatting: FAMILY, Given)
Student identification number
Signatures of all group members, engineering contractors (EC) accepting the projects/bids
Contain company name
Group member contact email addresses, email of one contact speaking for the group (that is,
ualberta.ca email addresses, not personal email addresses, formatting: example.user@ualberta.ca)
Indicate acceptance of IP ownership provisions specified by the client. Please note that your
acceptance of these provisions is binding and cannot be renegotiated at the end of term.
Affiliates: It is imperative that the group use components from MECE360 Inc. affiliates QTC Gears and
FAG bearings, if required in the latter case, as cost will be minimized.
MECE360 Inc. does not have a motor provider; the group must specify their own motors for the
applications.
Throughout the bidding process it is mandatory that each engineering contractor discusses project
requirements with MECE360 Inc. ECs should base their submission on existing applications and adhere
to any and all safety standards. MECE360 Inc. will set aside 7 hours/week to meet with groups bi-weekly.
Block off meetings for the term based on following schedule; first com first serve. Signup sheets are
available online on Google.Drive: http://goo.gl/tCrCMh . MECE360 Inc. may have administrative
meetings and may need to reschedule meetings; ECs will be advised by email if that is the case.
Other bidding requirements from MECE360 Inc. which are given in the following:
Bid requirements:
All reports must be submitted electronically as a single PDF document.
Submission are done via the course website. To access the website, go to http://www.ualberta.ca,
then in the top right corner click on eClass. Using your user CCID and password, login to eClass.
In your Course List, select MEC E 360.
Name format, e.g. group 7: mece360_F16_LOI_07.pdf

Rev.: Sep. 6, 2016

Report 1: Concept report (CR) (Y/N)
Recommended effort: 15 hrs/person, with an estimated range between 12-20 hr./person.
Report requirements: The report body must be 1000 words max, not including figure text, tables, charts,
graphs, etc. Dumping a lot of extra detail into cryptic charts and tables is not a sign of clear thinking.
Show the word count for the report body at the end of the table of content.
Report #1 recommended structure:
Abstract
Table of content
List of figures and tables
1. Introduction
Discuss what is expected of you
Discuss current existing designs
Legal/standard requirements
2. Design methodology
brainstorming,
decision matrices,
Gantt chart
Specifications
Assumptions
Design selection process
Design sketches
3. References
4. Appendix
Any additional info
Report submission:
All calculations submitted using MathCAD files converted to PDF or scanned clean hand
calculations converted to PDF
Name format, e.g. group 7: mece360_F16_CR_07.pdf

Rev.: Sep. 6, 2016

Report 2: Analysis report (AR) (Y/N)
Recommended effort: 25 hrs/person, with an estimated range between 20-30 hrs/person.
graphs, etc. Dumping a lot of extra detail into cryptic charts and tables is not a sign of clear thinking.
Show the word count for the report body at the end of the table of content.
Report #2 recommended structure:
Abstract
Table of content
1. Introduction
2. Completed Analysis
FBDs
Critical elements to analyse
Results of analysis
3. References
4. Appendix
All analysis use MathCAD or scan of legible and structured hand written analysis
Schematic/3D model
Any additional info
Report submission:
Name format, e.g. group 7: mece360_F16_AR_07.pdf

Rev.: Sep. 6, 2016

Final report (FR): Detailed Design Report (60%)
Recommended effort: 30 hrs/person, with an estimated range between 25-45 hrs/person.
graphs, etc. Dumping a lot of extra detail into cryptic charts and tables is not a sign of clear thinking. Show
the word count for the report body at the end of the table of content.
The detailed design report is intended to convey the essential elements of the final design. This report should
provide an overview of how the device or system functions and how it satisfies client requirements and
design specifications. Include succinct descriptions of key systems and/or subsystems and explain their
function within the context of the overall design. Liberal use of graphics, schematics, 3D models and
drawings will aid in conveying design intent and should be included within the report.
Final Report:
Abstract
Table of content
1. Introduction
Report #1 tweaked to sound like a final report
2. Design methodology
Report #1 tweaked to sound like a final report
3. Analysis (report + additional analysis)
FBDs
Critical elements to analyse
Results of analysis
5. Discuss design and compare to specification
6. Conclusion
7. References
8. Appendix
All analysis use MathCAD or neatly hand written scanned images
Engineering drawings
o Detailed drawings for 5 major components (Shafts, Supports, etc.) and all necessary
Assembly drawings
Any additional info
Report submission:
Name format, e.g. group 7: mece360_F16_FR_07.pdf
8
Rev.: Sep. 6, 2016

Technical Report Writing Introduction
An engineering report is a direct reflection of its writer's ability and knowledge of the subject. A well
written report cannot cover up a poorly executed effort; however, a poorly written report can seriously
damage an excellent piece of engineering work.
All engineers must master the art of effective communication, of which report writing is an important
part. Fortunately, it is a skill that can be learned and practice is the best learning tool. The personal effort
you make at improving your report writing is well worth it and the writing skills you master will greatly
help you in your professional career. The points that follow provide some guidelines for effective
technical report writing.
1. Always have in mind a specific reader, real or imagined, when you are writing a report. Assume that
the reader is intelligent but uninformed about the particular details you are discussing.
2. Although it seems like extra work, an outline will always save time by helping to organize your
thoughts. The result will be a report that not only effectively presents the material but also takes less time
to write.
3. Before starting to write, decide the exact purpose of your report, and make sure that every word, every
sentence and every paragraph makes a contribution to this purpose and makes it at the appropriate time.
The report should reflect a sound understanding of the presented material and should be as objective as
possible. Subjective materials such as personal opinions, suggestions or complaints are best stated in the
covering letter or letter of transmittal.
4. Use language that is simple, accurate and familiar. Highly technical terms or jargon make it very
difficult for the reader to understand what you are trying to say. If highly technical terms cannot be
avoided then they must be defined in simple terms so that the reader can understand them. Keep sentences
short, especially when dealing with complex material. Point form can be effective, but should be used
sparingly.
5. At the beginning of every section of your report check your writing according to the following
principle: "First tell the reader what you are going to say, then actually tell the reader what you want to
say, and finally tell the reader what you have just said." A report should not be a mystery story. Don't
keep the reader in suspense by leaving essential details until the end. Phrases such as it will be shown
later that .. " and "this manufacturing error will be shown to be the key to the poor performance.." are
useful in tying the various parts of the report together.
6. State all the important points explicitly; don't leave it to the reader to try and guess what it is you are
trying to say. It may be obvious to you what the results or conclusions of your analysis or experiment are
but it is probably not so obvious to the reader.

Rev.: Sep. 6, 2016

7. Use the third person, passive voice. Personal pronouns, (I, me, you, us, and we), should not appear.
Passive voice is used because reports usually deal with something done in the past. For example, use "The
voltmeter was calibrated." instead of We calibrated the voltmeter.". The choice of using past or present
tense is often a matter of personal choice. Rules that work well are:
a. If the event relates specifically to something which has been completed, use the past tense. For
example, "The meter reading fluctuated between .. ".
b. If you are stating something that should be true today as well during your experiment, then use the
present tense. For example, "Jets spread rapidly as they mix with their surroundings" .
8. Never force the reader to search back and forth through the report in order to find information. It never
hurts to repeat information to help the reader understand the point you are trying to make. For example,
Use: "The 40% increase in CO with the vents closed indicates that there was insufficient air for complete
combustion. This is the predominant reason for the drop in efficiency from 82% to 68%."
Not: "The value of 12% CO with the vents closed can be compared to the data with the vents open to
show how the position affects efficiency."
9. If you are having trouble with a sentence it is likely that you are trying to tie together two unrelated
ideas. Stop for a moment and think about what it is you are trying to say. You may find that a number of
shorter sentences conveys the information more clearly and makes the passage more readable.
Parts of a Complete Report

a) Covering Letter - this business letter explains the nature of the attached report. It will briefly define
the problem being considered and give the results of your group's effort. Final report only
b) Abstract - this is a one page summary of the project which should include a brief description of the
design problem, your solution strategy, your predicted performance and your test day result.
c) Table of Contents, List of Figures and Drawings, List of Tables - every section in your report
should have a number and title. Every figure and table should also have a number and title. Make lists of
these with page numbers for ease of reference. Tables and figures in any Appendices must also be
included in your lists. (MS word does this automatically if you set your headings)
d) Description of Final Design - Present your final solution to this design problem - in particular, how it
deviates from the chosen design presented in your progress report. You are required to indicate how your
device achieves previously stated design objectives. A complete set of design drawings (computer
generated) are required for your device as built. These drawings must be complete in the sense that it
should be possible to give these drawings to someone else to manufacture an identical device to the one
that you have built. Each group member MUST contribute to the preparation of these drawings. Every
drawing MUST have a title block indicating (at the very least) the drawing number and title and who it
was created by. All drawings are normally placed in an Appendix.
e) Results - the results of the insurance run and test day are compared to the predicted performance. What
are the reasons for the differences, if any, between the actual and predicted performance? This is an
extremely important part of the report as it will indicate if you understand how your device works (or
doesnt) and the assumptions that you made in coming up with your predicted performance.
Rev.: Sep. 6, 2016
10

f) Discussion - this section considers the difficulties encountered during the design, fabrication and
testing of your device (Trials and Tribulations) and how these difficulties were overcome. Also include
an updated copy of your time management chart and a brief discussion of how well you followed it.
g) Conclusions - briefly summarize the project, your solution and your results.
h) Appendices - for example: design drawings, progress report. Each Appendix must have a number and
title and be referred to in the body of the report.
i) Figures - figures should be numbered in order and called in the text. Figure captions appear at the
bottom of the figure (see Figure 1), usually centered, in bold and in 10 point font. Always include units in
graphs (see Figure 2).
Figure 1: Mould and mandrel assembly
Figure 2: Stress-strain diagram. (a) elastic and preliminary yielding, (b) plastic deformation without necking, and (c)
plastic deformation with necking and specimen failure. Note that all units MUST be given

Rev.: Sep. 6, 2016
11

j) Tables - table captions are bold, centered, in 100 point font and found above the table. Tables can have
formatting or no formatting as seen in Table 1 and Table 2, respectively. Again, all units should be
present.
Table 1: Experimental material properties
Material
Epon 825/Ancamine 1482
Kevlar/epoxy composite
Em (GPa)
3.5
E11 (GPa)
79.7
E22 (GPa)
5.9
Gm (GPa)
1.3
G12 (GPa)
2.3
m
0.35
12
0.33
Table 2: Range of target rigidity required for proposed braided catheter

Characteristic
Target range
Flexural
12.6 - 94.5 (10-3 Nm2)
Torsional
17-1400 (10-3 Nm2)
Axial
39.4 - 147 (kN)
k) References - sources used in a report (book, journal article, report, website, your friend/neighbour/dog,
etc) must be cited in the reference section and in the text where the information was used. References
should always be at the end of the paper in the order they appeared in the paper.
In the paper, reference numbers should appear in brackets []. If text was taken word for word, or
paraphrased, quotation marks should be used before and after; often the text is also placed as an individual
paragraph in the text with 0.5 indent on both sides as shown in the following text.
Example: Petrescue and Lalibert [1] noted that for the CANCOM 2005 conference, the following
reference formats shall be used:
For a book, the format is:
Hibbeler, R. C., Engineering Mechanics Statics and Dynamics, Maxwell Macmillian
Canada, Inc., (1992).
For a journal article, the format is:
Hergenrother, P. M., Development of Composites, Adhesives and Sealants for HighSpeed Commercial Airplanes. SAMPE Journal, 36(1), 30-41 (2000).
For a conference paper, the format is:
Taheri, F. and Hassan, M., Rational Procedure for Designing a Hybrid FibreReinforced Plastic Mast presented at the 3rd Canadian International Composites
Conference, Montreal, P.Q., August 21-24, 2001.
For an unpublished report, the format is:
Margarit, K. L. and F. Y. Sanford, Basic Technology of Intelligent Systems, Fourth
Progress Report, Department of Smart Materials, Virginia Polytechnic Institute and
State University, Blacksburg, March 1993.
References:
1. http://www.cancom2005.ca/participants/authors/paper.php, Petrescue, L. and Lalibert, J., Paper
Format Guidelines for CANCOM 2005, pp. 3, 2004.
Rev.: Sep. 6, 2016
12

MECE360 Inc., a production firm, was recently awarded contracts to produce new equipment for various
applications. MECE360 Inc. requires engineering contractors (EC) to bid on the projects.
Project #1: Ferraro Inc. Innovative Meat Grinder/Pasta Maker

Objective
Design a meat grinder/pasta maker. The clear need for humans to start making their food from scratch is
critical as exemplified by sanitation problems at large-scale food producers.
Scope of Work
Define design specifications through conversation with customer

Prepare three design concepts by creative brainstorming
Select design concept through consultation with customer
Prepare detailed design calculations and analysis
Prepare assembly and parts drawings suitable for manufacture
Review detailed design drawings for manufacturability
Preliminary Design Specifications (can be flexible)
Single-speed
120 volt (or greater if desired)
Define your own limiting speed and torque
Deliverables
Dimensioned and toleranced assembly and parts manufacturing drawings

Engineering report
Project Sponsor
Name: MECE360 Inc.
Company: University of Alberta
Office: DICE 10-227
Email: jdhogan@ualberta.ca
Meeting Time
Engineering companies and client must meet biweekly for 15 minutes at a predetermined meeting time.
Intellectual Property Ownership

Design IP will remain the property of the Company

Rev.: Sep. 6, 2016
13

Project #2: Kitchengizmo Inc. Single-speed Hand-held Blender
Objective
Design a hand-held blender suitable for heavy-duty professional kitchen work
Scope of Work
Define design specifications through conversation with customer

Prepare three design concepts by creative brainstorming
Select design concept through consultation with customer
Prepare detailed design calculations and analysis
Prepare assembly and parts drawings suitable for manufacture
Review detailed design drawings for manufacturability
Preliminary Design Specifications (can be flexible)
Single-speed
120 volt (or greater if desired)
Define your own limiting speed and torque (e.g., 300 rpm and 4.8 Nm for commercial blender)
Deliverables
Dimensioned and toleranced assembly and parts manufacturing drawings

Engineering report
Project Sponsor
Name: MECE360 Inc.
Company: University of Alberta
Office: DICE 10-227
Email: jdhogan@ualberta.ca
Meeting Time
Engineering companies and client must meet biweekly for 15 minutes at a predetermined meeting time.
Intellectual Property Ownership

Design IP will remain the property of the Company

Rev.: Sep. 6, 2016
14

MecE 360 Mechanical Design Project Teams & Expectations

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

MecE 360 Mechanical Design Project Teams & Expectations

Caricato da

Copyright:

Formati disponibili

MecE 360: Mechanical Design II

Fall 2016 Sept 1 to Dec 7

MecE 360 Design Project: Team Policies and Expectations

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

Nov. 11, 2016

Nov 27, 2016

MecE 360: Mechanical Design II

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

MecE 360: Mechanical Design II

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

Parts of a Complete Report

MecE 360: Mechanical Design II

Figure 1: Mould and mandrel assembly

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

Table 2: Range of target rigidity required for proposed braided catheter

MecE 360: Mechanical Design II

Project #1: Ferraro Inc. Innovative Meat Grinder/Pasta Maker

Define design specifications through conversation with customer

Preliminary Design Specifications (can be flexible)

Dimensioned and toleranced assembly and parts manufacturing drawings

Intellectual Property Ownership

Instructor: J.D. Hogan

MecE 360: Mechanical Design II

Define design specifications through conversation with customer

Preliminary Design Specifications (can be flexible)

Dimensioned and toleranced assembly and parts manufacturing drawings

Intellectual Property Ownership

Instructor: J.D. Hogan

Potrebbero piacerti anche