AgendaAgenda

1.1.First meeting issuesFirst meeting issues

2.2.SafetySafety

3.3.Prototyping & testingPrototyping & testing

4.4.Purchasing Purchasing

5.5.Process, CPM, planProcess, CPM, plan

6.6.Design brief Design brief

1. First meeting issues1. First meeting issues

a) Kick start for good journeya) Kick start for good journey

b) PDP experience 1997 – b) PDP experience 1997 – 20132013

c) Paper workc) Paper work

a) Kick start for good journeya) Kick start for good journeyopen and honestopen and honest

agree on w-o-wagree on w-o-w

schedulingscheduling

communication plancommunication plan

roles discussionroles discussion

what is success?what is success?

b) PDP experience 1997 - 2014b) PDP experience 1997 - 2014

ProactivenessProactiveness

Assumptions<>understandingAssumptions<>understanding

Creativity – courageCreativity – courage

Waiting for somethingWaiting for something

Hands-on Hands-on

TestingTesting

DocumentationDocumentation

Success criteriaSuccess criteria

c) Paper workc) Paper work

Assignment of rightsAssignment of rights

ContractContract

NDANDA

Contact infoContact info

Posters / website Posters / website

2. SAFETY

SAFETY

travel

machines

electricity

explosion

poisonous or harmful materials

fire

psychological

3. PROTOTYPING & TESTING

”somebodys job” = nobodys job

purchasing, manufacturing, “adjustment” = time!

“small tasks” do not exist

Respect other projects & courses at ADF

“silence” = something is badly out of order

CAN DO well together with good attitude

MACHINE & OTHER SHOPS

ADF is THE PDP Place at Aalto University

Benefits of time, expenses, and learning…

But it’s not the only place

Machine Design, Production Engineering

Foundry, Light weight structures

ADDLAB, ELEC, ARTS, CHEM

External

Ask the guys at workshop / ask the sponsor

LACK OF RESOURCES or SKILLS ?

Recruiting of reinforcements

Special work / excercise

Partners in other Schools

Omnia

Polytechnics

Lauttasaaren Lukio

Outsourcing

General philosophy & policy

• Tools – back to place, tell us breakage• Machines - don’t do if you don’t know - ask!• Keeping places in order - others can’t• Close windows and doors & switch of lights• Hot works - only by card owner (also grinding!)• Follow instructions of your safety officer or staff• Painting - only in paint shop (never outside!!!)• Avoid danger - work never alone• Office hours 7:00-15:00• 24/7 trust and responsibility

4. PURCHASING

• Finance officers: to instruct, to monitor, and to clarify• Ask Staff First (Vesku, Kari, David, Martti, Heidi,

Eetu…)• On shelf at ADF (material cave, ele, machineshop)• Allways avoid paying by cash, but…

• M2 invoice• Always save the receipts (or your money is gone)

• Protoshop Oy• Ordering

• but why companies fail to ship and charge

PuuhamiehenkatuPursimiehenkujaBucmeähenkujaPuumeihenkuja

Rule book – consult if you don’t know• Items according to project plan • Services a.t.p.p.• Travel expenses a.t.p.p.• Hospitality expenses – with limitations!• Cash invoice handling by finance officer

Forbidden

Possible costs (or not)

• Missing information• Missing receipt• Wrong address / missing reference• Having sauna, dinner,…• If we have money left ...• Daily allowance (päiväraha)

Most typical problems (or questions)

• Team – Sponsor: TBD• Team – Teaching team: defined in calender• Week 44 first CPM (whole team)• Week 47 second CPM • Week 50 third CPM (with sponsors)• 14th Jan review presentations by all course project teams• Week 08 fourth CPM (2-3 teams together)• Week 12 fifth CPM (manufacturing issues)• Week 16 sixth CPM (final check and instructions)• 13th May project report draft (“as is” – no delay)• 21th May Final presentation day (all teams, 10 min)• 22nd May PDP Gala – the project ends.

5. Process and check points

Project planProject plan

1. Background2. Project objectives, expected deliverables3. Methods 4. Organization5. Work breakdown structure6. Schedule7. Budget8. Communication plan9. Meetings , checks and decision making10.Risk analysis11.Plan for reporting and transfer of results12.Tracking experiences, lessons learned and feedback

• Idea • Process • Work load

PDP of the WEEK

6. DESIGN BRIEF…It’s all about project

communication

MOTIVATIONMOTIVATION

Do things right, do right things – but how?

PDP course book; ideas for doing things right

Design Brief; landscape for doing right things-communication-creativity-new viewpoints-state-of-the-art-all sources and forms of information

PDP 1997-2014 PDP 1997-2014 (201 projects)

Most conflicts, problems and disappointments relate to unsatisfying communicationcommunication-waste of resources-decreasing motivation-unmanageable changes, resulting lack of time-results out of scope

There’s no creativity without limits… Magnus Lindberg, composer

What is Design Brief What is Design Brief (in PDP

context)?-documented description-can be used as part / base of project plan-but it is not the project plan-including:1.Background2.Project type3.Goal setting & expected outcomes

Project type?Project type?

?

?

?

?

Path unknown,

Destination known

Path unknown,

Destination unknown

Path known,

Destination known

Project typeProject type

IDEA exists. Find the technology and way of implementing it.TECHNOLOGY exists. Find new ideas and market for it.TECHNOLOGY exists. Accommodate it into this new product.CONCEPT exists. Get through the PD-process.PRODUCT exists. Improve it for future needs.TECHNICAL PROBLEM exists. Solve it.USABILITY PROBLEM exists. Solve it.BIG GENERAL PROBLEM exists. Solve it.OPEN QUESTION; find answers.FINDING QUESTIONS; getting through the field.

Your project - one of these, mixture or something else?

You don’t know yet…You don’t know yet…

• Existing or emerging technology, competitors, …• Patents or other IPR, …• Market trends, business models, competitive edge, …• Lead users, use cases, hidden needs,…• Stakeholders of the project…• Work breakdown stucture…• Areas of research…• …many other things

Usage of DBUsage of DB

• For new parties, changes on personnel• Goal setting (and adjustment, freeze)• Avoiding misunderstandings• Getting started• Recognizing biggest challenges in advance• Less surprises with prioritization, expectations and

results in project work• When plans change, it’s important to know what

existed at beginning, to understand and reflect the changes

• It’s better to ask (stupid) questions in the beginning

What should be there?What should be there?

1. Background - What is the project context (big picture)?- Why is this project to be done (at PDP)?- How did the idea come up?- What has been done already?

2. Project type & “Known & Unknown" - What do we know about the project type? - Path or Destination or both or neither?

3. Aims- What does the sponsor expect to get, desire to get? - What do we as a team expect?- What are the success criteria?- What to emphasize?- What to avoid, what to skip?

?

?

Meeting rooms• Brainstorm - Audi

• Birch - Airbus

• Audition (2nd) - Wärtsilä

• Kino (base) – Duckter

• Engine - Lindström

• Puuhamaa – KONE

• PDP Room - Unicef

• Stage – Fortum & Stalatube• Kafis – Nest & Norpe• Barn - Konecranes• Library (2nd) – Comnet• Staff Wing - ABB

• Company Plaza (2nd) - Valmet

• Urban Mill (BK3) – GE, Innovamo

• Pool (back yard) – Espoo