PEPs and PDPs 1 2 3 4 Objectives

PEPs and PDPs 1. 2. 3. 4. Objectives: Understand Project Execution Plan, requirements, and expectations Product Development Teams Developing successful products Understand Product Development Process Engineering Practicum Baltimore Polytechnic Institute M. Scott

Project Execution Plan (PEP) • A communication tool • A document that describes how a project is: – Planned – Monitored – Managed • Include plans pertaining to: – Product purchasing – Product development – Risk Management Engineering Practicum Baltimore Polytechnic Institute M. Scott

Project Execution Plan (PEP) • Other details: – Clearly defines roles, responsibilities, and authorities – Sets procedures concerning quality and reporting – Covers major schedules and budgets of the project and relevant resources – Used to monitor progress and judge team performance – Contract between the team and managers Engineering Practicum Baltimore Polytechnic Institute M. Scott

Project Execution Plan (PEP) • PEP Expectations – Use the outline posted on bpi. edu – Use the document to clearly plan your actions for your design project • Reporting Requirements Next Semester – Bi-weekly individual and group status reports • Due on separate weeks • Group report is a rotating responsibility – Preliminary Design Report for approval – Final Design Report Engineering Practicum Baltimore Polytechnic Institute M. Scott

Due Dates PEP Rough Draft • Monday December 13 PEP Final Draft • Monday December 20 Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Teams • Teams include marketing, finance, design engineering, operations/manufacturing, and quality control Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Teams • Why good teams are effective: – Meeting together is synergistic – Building on strengths, compensating for weaknesses • Expectations – Team members commit to required level of effort to meet schedule, achieve goals, produce the deliverables – Responsibility 1 – do what you said you would do and what your team expects you to do to the best of your ability – Responsibility 2 – provide your technical expertise – Responsibility 3 – to the team • Bring to its attention functional issues that affect performance • Ensure the team maintains the principles, goals, and objectives Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Teams • Sharing Responsibility – The most important team activity for the individual member – Highly effective teams hold themselves mutually accountable – – for the overall success of the product Team members must recognize and understand all of the product features Team members must assess team progress and participate in improving team performance Must cooperate in establishing all of the reporting relationships required to maintain the communication among the team and functional departments Flexibility and cooperation are required for the team structure to be effective Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Teams • Characteristics of good and bad team members – See lecture notes • Why teams sometimes fail: – Deviate from goals and objectives – Do not meet milestones – Team members become alienated – Blaming each other when things go wrong (and they will) Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Teams • Team contract – Set of simple rules necessary to govern the team – Each team member signs and dates it – Example in lecture notes • Team meetings – – – Always attend Use time wisely Start and end on time Keep focused Create specific agenda, stick to it, and create preliminary agenda for next meeting Engineering Practicum Baltimore Polytechnic Institute M. Scott

Required Team Roles – Design Projects • • • Team Leader Documents and notes manager Drawings, pictures, and other visuals Client point of contact (POC) Accounting and Procuring Engineering Practicum Baltimore Polytechnic Institute M. Scott

Due Dates PEP Rough Draft Team Contract, including roles and responsibilities • Monday December 13 PEP Final Draft • Monday December 20 Engineering Practicum Baltimore Polytechnic Institute M. Scott

Developing Successful Products 1. Quality, Performance, Price Is the product: – Attractive – Easy to use – Durable and reliable – Effective and efficient – Meet customer’s needs – Better than competing products Engineering Practicum Baltimore Polytechnic Institute M. Scott

Developing Successful Products 2. Cost Profit = Product Price – Total Product Cost – Materials – Components – Manufacturing – Assembly – Equipment and tooling – Product Development – Maintaining inventory For a new car, $1 billion with additional $500 million for high-volume tooling Engineering Practicum Baltimore Polytechnic Institute M. Scott

Developing Successful Products 3. Development Time – time from kickoff to introduction to market – Development takes time and requires much money Being first on the market: • Product’s market life extended • Increased market share • Higher profit margins • No competition • More time to develop better production methods Engineering Practicum Baltimore Polytechnic Institute M. Scott

Developing Successful Products Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Process (PDP) Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Process (PDP) • Products surround us – How many do you use each day? • Corporations continuously develop product lines – Minor improvements every year or two – Major improvements every four or five years • Corporation success depends on a steady stream of successful products Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Process (PDP) Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Process (PDP) 1. Identify the customer needs. – Convert customer comments to customer needs – Your product should include features that satisfy the customer’s needs 2. Establish the product specifications. – Well-defined design objectives for each product feature or attribute – Numbers and/or specific statements Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Process (PDP) 3. Define alternative concepts for a design that meets the specification. – Define subsystems – Find existing concepts – Generate new concepts – Eliminate wild ideas Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Process (PDP) 4. Select the most suitable concept. 5. Design the subsystems and integrate them. – Form, fit, function, and finish – Design for manufacturing – it is essential that you consider how the parts are to be fabricated – Design for assembly – you must consider the methods and procedures used to construct all subsystems and assemble them to form the complete system (product) • The components must be able to be assembled • The assembly operation should be easy and not require special operator skills • The time required for the assembly should be minimized – Design for maintenance – Design for the environment Engineering Practicum Baltimore Polytechnic Institute M. Scott

Product Development Process (PDP) 6. Build and test a prototype and then improve it with modifications. 7. Design and build the tooling for production. 8. Produce and distribute the product. 9. Track the product after release developing an awareness of its strengths and weaknesses. Engineering Practicum Baltimore Polytechnic Institute M. Scott

Design Process Design Principles – – Design is the result of a formal, sequential process. Design is mostly driven by profit motive and market. Design is the result of goal-oriented research. Designs must be continually checked, refined, and improved. The Mind’s Eye Note: – Design problems seldom arise in a clearly defined form. – Design requirements sometimes compete with each other. Engineering Practicum Baltimore Polytechnic Institute M. Scott

Design Process Clearly Defined Steps: 1 2 3 4 5 6 7 8 9 10 11 12 Define the problem Identify criteria and specify constraints Brainstorm Research and generate ideas Explore possibilities Select an approach Develop a design proposal Make a model and/or prototype Test and evaluate the design Refine the design Create the final product Communicate processes and results Engineering Practicum Baltimore Polytechnic Institute M. Scott

Design Process Similar steps can be grouped: Engineering Practicum Define the problem Identify criteria and specify constraints Brainstorm Research and generate ideas Explore possibilities Select an approach Develop a design proposal Make a model and/or prototype Test and evaluate the design Refine the design Create the final product Communicate processes and results Baltimore Polytechnic Institute M. Scott

Design Process as you should know it: 1. Define the Problem 2. Brainstorm, Research, Generate Ideas 3. Explore Final Possibilities 4. Develop a Design Proposal 5. Make Model/Prototype 6. Test and Evaluate 7. Refine the Design 8. Communicate the Solution Engineering Practicum Baltimore Polytechnic Institute M. Scott

Engineering Design Traditional design for an RFP: Structural 5 -9 months Electrical Mechanical Thermal … Engineering Practicum Baltimore Polytechnic Institute M. Scott

Engineering Design Current NASA spacecraft design for proposal: Mechanical Electronic Optical Thermal Engineering Practicum Structural Material Biotechnology Fluid 2 Weeks Baltimore Polytechnic Institute M. Scott

Constraints on the Engineering Design Process (A constraint is a limit or restriction) 1. 2. 3. 4. 5. Safety – is the product safe to use/construct? Reliability – will it work consistently over time? Cost – is it affordable? Quality Control – does it meet customer requirements? Environmental Concerns – does it harm the natural or human environment negatively? 6. Manufacturability – can it be made? 7. Maintenance – how easily can it be maintained or upheld? 8. Ergonomics – how efficiently can the human body utilize it? Engineering Practicum Baltimore Polytechnic Institute M. Scott

Materials Lab Report • Individual Mini-Reports due Monday • 10% off if no original report sent by last Wed. • 10% off if no group report sent in by Monday 11/29 Engineering Practicum Baltimore Polytechnic Institute M. Scott

Engineering Practicum Baltimore Polytechnic Institute M. Scott

Due Dates – SDP PEP Rough Draft Team Contract, including roles and responsibilities • Monday December 13 PEP Final Draft • Monday December 20 Engineering Practicum Baltimore Polytechnic Institute M. Scott

SDP: 12/2 Team Mtg. Topics • Team Roles and Responsibilities • Method of Communication; google docs, blackboard, etc. – ACE groups will use “Basecamp” • Split up the PEP Rough Draft Outline, create due dates • Team Contract, including roles and responsibilities Manufacturing Presentation: • Get with 1 partner and meet to discuss communication methods, how work will be divided, when items are due, etc. Toy Design Project: • Get with a different partner and start discussing ideas OUTCOME: Group Leader sends me a summary of all items above Engineering Practicum Baltimore Polytechnic Institute M. Scott

Required Team Roles – Design Projects • • • Team Leader Documents and notes manager Drawings, pictures, and other visuals Client point of contact (POC) Accounting and Procuring Engineering Practicum Baltimore Polytechnic Institute M. Scott

Criteria: 1. Must fit in 12” x 12” cube 2. Portray human interaction with “nature” 3. “Object” must have at least 3 different types of mechanisms 4. Toy can be powered by a crank, push-button, or lever 5. Bonus – utilize an electric motor 2. Proposal Requirements (due end of class Monday December 6): 1. Homogeneous quality 2. Description of toy operation 3. Drawings: 1. Brainstorm sketches 2. Final 3 -view orthographic drawings (rough sizes) 3. Final isometric drawing 4. Extra Credit – draw toy design using Sketchup Baltimore Polytechnic Institute Engineering Practicum M. Scott 1. TOY DESIGN PROJECT