You are on page 1of 48

MMAN2100 – 2nd Year Design

School of Mechanical and Manufacturing Engineering

Welcome!

Dr. Jason Held


j.held@unsw.edu.au
jheld6557@gmail.com
Why are we here?

What is design
The process
Example of one design process
What you’re in for
- Goals
- Schedule
- Grading
- Logbook
- Exam
What is design?
What is design?

“Creation of a Plan or Convention to construct an object or a system”


• Flight Software

• Painting

• Hubble Space Telescope

• Dining Room Table

• Brooklyn Bridge

• 4-Pines Brewery
What is a GOOD design?
Good Designs - Functional
Good Designs - Attractive
Good Designs - Simple
Good Designs – Cost effective
Good design? Not until its tested!

Simple

Elegant

Follows design standards

Functional

Fits a market need

But does it work?...


What is a BAD design?
Bad Design – Non-Functional
Bad Designs – functional, but awkward
Bad Design – Functional but unnecessary
Bad Design – Just because
An example of…
Bad Design – Disaster

Designed issue <12 deg C

Freezing O-rings

Wind shear

Fuel leaked onto the strut

Catastrophic failure
The Fix

The Point—

1. Design requirements will conflict

2. Mass, volume, power, time, cost

3. You won’t get it right first go

4. TEST YOUR DESIGNS

5. HONEST REPORTING

6. If you don’t, people can die


The Design Process
What is design?

They all follow the same general process:

• Research
• Conceptualisation
• Feasibility / Requirements scoping
• Conceptual design
• Detailed Design
• Prototype
• Test
• Refinement
• Tooling, Production, Manufacture…
Other Related Methods

SCIENTIFIC METHOD MILITARY METHOD

Form a Question Receive Mission

Hypothesis Mission Analysis

Prediction Course of Action Dev

Testing Wargaming

Analysis Orders Production


Design Methodologies – “Waterfall”

Low complexity

Modular Design

Highly structured

Difficult to change
Design Methodologies – “Spiral”

Typically LARGE projects

Emergent Design

Good for complex jobs

But you can paint


yourself into a corner
Design Methodologies – “V-Model”

Extends Waterfall

User focused

“Dual V” for systems of


systems
Design Methodologies – “Agile”

Small teams

Rapid development

Allows mid-dev change

Role focused

Organised “scrums”
Scrum
Product
Master
Owner
Team
For Example…
For Example – “Request for Proposal”
“Design a bottle that can allow easy consumption of liquids in zero gravity”

Customer has a job request

Or you find a job need

High level design request

Some basic constraints

Integration information

Initial instructions are usually VAGUE


For Example – Research
1. Gather information
2. Ask questions
3. Use available resources for background information
For Example – Conceptualisation
For Example – Feasibility & Requirements

1. A review of surface tension issues and fluid flow science


2. A trade study of the surface tension for over 40-beers on market
3. A trade study of the surface energy for bottle materials
4. Surface tension results from Drop Tower tests

1-g

0-g
For Example – Conceptual Design
For Example – Detailed design

3D CAD (Solidworks)

Simulation testing

Some design iteration here


For Example – the prototype….
For Example – the prototype is….
For Example – more testing
What we’re in for – COURSE OVERVIEW

Project RFPs provided by university research projects

6-person design teams

Tutor is your “customer” and mentor

The best teams will go further towards manufacture

Lectures Tues (2-hr)


Thursday (1-hr)

Tutes (2-hr) Mon/Wed/Fri


What we’re in for – Tutorials

Stay in your enrolled tutorial

Tutes start next week

Labs are available at nights and weekends for assignments

If you have a laptop bring it!

https://www.solidworks.com/sw/resources/solidworks-tutorials.htm
Grading

LATE = 0

Assignments for practice Logbook for process Project for assessment


- Requirements document - Log Standards - Functionality
- Conceptual design - Process - Industry standards
- Detailed design - Attention to detail - Process
- Test results - Data - Simplicity
- And other fun surprises - Analysis - Attractiveness
- Cost effective

I SAY AGAIN…. LATE = ZERO!!!


Logbook

A professional reference
Capture your development process
A legal document, part of intellectual property
Engineers, scientists
Part of your assessment!
Logbook – The Good

The Standard:
1. Hard bound book. No binders
2. Only in ink
3. Keep it organised: Date/titles and
sequential
4. Label everything
5. Clean enough to be duplicated

When to use?
Meetings, brainstorms, sketchings, diagrams, plots, test results, random thoughts…
Searches, epihpanies, calculations, and ANYTHING related to your project
Logbook – The Bad

It’s useful to you, maybe not to others


Wright Brothers logbook
- Pencil (NO!)
- Good content (YES!)
- Hard to read
Logbook – The Ugly

Common mistakes:
1. Information missing
2. No date
3. Missing context: Reasons and
conclusions
4. Using White-out
5. Blank pages, torn out pages
6. Missing labels
The Exam
The Project
Project

Questions about the project:


How is the product to be used?
How much should it cost?
What is the market for the product?
What are the required functions?
Is the design economically feasible?
What are the legal requirements?

You might also like