R. I. T Mechanical Engineering Technology Roadmapping Design Project Management Rochester Institute...

transcript

R . I . TMechanical Engineering

Technology Roadmapping

Design Project Management

Rochester Institute of TechnologyMechanical Engineering Department

Rochester, NY USA

Session Objectives

• Motivation• Examples• Suggestions• Work time

***Warning***

Extremely superficial overview of complex material ahead. Proceed with caution.

Session Objectives

Why Develop a Roadmap?

• For complex and/or long-term projects• Forces you to consider order of implementation• Build a case for funding initial projects• Make effective use of time• Demonstrate that you have an end goal

Boeing

• Five focus areas for underwater robotics work:• Communication

• Navigation

• Payloads and Sensors

• Power

• Autonomy

• Customer seeking multiple project ideas in each area• short-term and long-term solutions

Air Quality Monitor

• Single core idea with lots of potential applications…• Wearable

• Indoors with cookstove

• Outdoors to monitor city data

• Monitor other types of emissions

• …And a corresponding need for a test chamber

Who else is here…?

• Test rigs:• PMTR – develop 1, 10, 20? Classroom demo, student

lab, or research quality?

• Garlock – build up increased functionality, parallel development to different test standards

• Baja, FSAE:• Long-term vision for the car, develop risky advances in

parallel with traditional improvements

Session Objectives

Example 1

• “A familiar technology family”• Credit to Dr. Hensel for assembling this

• Note how easy this looks in hindsight – the real challenge is to PLAN this!

FunctionDisparate

Analog Technologies

Discrete Products

Products integrated into Modules

Fully Integrated Products

Appointment Management

Paper Planner Calendar

PDA - Palm Pilot1996

PDAPhoneEmailTextFaxWebBlackberry, 2002

AppleiPhone3GJuly 11, 2008

PhoneKeyboardCameraMultimediaText MessagingEmailVoicemailWeb BrowsingWi-fiAssisted GPS

First iPhone ModelUSA IntroductionJune 2007

2007 Time Magazine“Invention of the Year”

Mobile Telephony

Analog Cell PhoneMay 1979

Digital Cell Phone Camera Phone

Still Image

Capture

View From the Window at Le Gras (1826), Nicéphore Niépce.

KodakBrownie(1900)

FairchildSemiconductor100 x 100 CCD (1974)

PositioningPaper Maps, Sextant ca. 1890

FoucaultGyroscopeca. 1882

TransitSatellite1959

GarminETrex2000

MusicEdisonCylinderPhonographca. 1899

SONY Walkman TPS-l2July 1, 1979

Phillips& SONY Compact Disc 1982

Apple iPodClassic2001

Capture

Kodak Super 8 Film(1965)

Kodak Ektasound130(1974-77)

JVCVHS1976

DVDVideoRentals1997

Electronic Messaging

MorseTelegraph1837

FultographImageReceiver1929

Fax Machinew/ SingleLine CCD

OlympiaFlexwriter 1962

Brief History - Familiar Technology Family

We observe that products move from highly modular designs to highly integrated designs, over time, as the core technologies mature.

We want to reproduce that product development experience for our students, to helpImprove the understanding of set based concurrent engineering, and modern product innovation!

FunctionDisparate

Analog Technologies

Discrete Products

Mobile Telephony

Still Image

Capture

KodakBrownie(1900)

GarminETrex2000

Capture

JVCVHS1976

DVDVideoRentals1997

MorseTelegraph1837

During the early generations of product evolution,we observe that products Improve in capability.

They become Faster,Better,Cheaper,Safer, Smaller, and Lighter.

FunctionDisparate

Analog Technologies

Discrete Products

Mobile Telephony

Still Image

Capture

KodakBrownie(1900)

GarminETrex2000

Capture

JVCVHS1976

DVDVideoRentals1997

MorseTelegraph1837

Subsequentgenerations of products begin tomerge technologiesand integrate two products into one.

FunctionDisparate

Analog Technologies

Discrete Products

Mobile Telephony

Still Image

Capture

KodakBrownie(1900)

GarminETrex2000

Capture

JVCVHS1976

DVDVideoRentals1997

MorseTelegraph1837

R11005 – Land Vehicle for Education

R10003 - WOCCS

R10006 – Sustainable Energy Systems

Session Objectives

Things to consider

• Need for each project• Platform to be used for future development?

• System to which other systems can be compared?

• Customer priority or bonus feature?

• Level of risk with each project• Risky ≠ Bad

• Safe ≠ Good

• Balance

More things to consider

• System architecture• How to modularize system

• Common interfaces? (think USB)

• It’s not personal• It’s not likely that your roadmap will play out exactly as

you define it

• View it as a starting point to give the project direction

Session Objectives

R. I. T Mechanical Engineering Technology Roadmapping Design Project Management Rochester Institute...

Documents