P14551: Multi-Process 3-D Printer Group Members: Jeremy Bennett Austin Chacosky Matt Demm Nick Hensel Chad Rossi Customer: Dr. Dennis Cormier Guide: John Kaemmerlen

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenario Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Chad

Team Introduction Jeremy Bennet, EE Austin Chacosky, ISE Matt Demm, ME Nick Hensel, ME/EE Chad Rossi, ISE, Project Lead Speaker: ---

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenario Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Matt

Brief History of 3D Printing 1984- Charles Hull invents stereolithogrpaphy 1992- First SLA 3-D Printer produced by 3-D Systems Late 1980’s-1990 FDM developed and commercialized 2005- RepRap Project launches. Domestic 3-D printing begins. 2013-The Mutli Prototyping Lab demonstrates multi-process printing 2009- FDM Patents expire, Makerbot launches DIY FDM Kit 2014-Laser Sintering Patents Expire http://www.designboom.com/technology/3d-printing-patents-expiring-in-2014-will-see-market-erupt/ http://en.wikipedia.org/wiki/3D_printing http://individual.troweprice.com/retailCommon/applications/brandjournalism/3DPrint/3D_Printing_Infographic.pdf Speaker: Matt

Open Source & 3-D Printing Open source licenses allow hobbyists to afford 3-D printers. RepRap, Makerbot, Fab@Home, etc. These printers are single process, usually FDM. http://en.wikipedia.org/wiki/3D_printing http://www.fabathome.org/ http://reprap.org/wiki/RepRap http://www.makerbot.com/ Speaker: Matt

Benchmark System: Multi-Process 3-D Printing Currently under development Proprietary Large Size Uses Modular Process Heads Expensive (~$150,000) http://rapidprototypingmachine.com/ http://www.uqast.com/index.php?s=products&channel=nationalnano&product_uname=multi-proto-lab Speaker: Matt

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenario Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Austin

P14551 Problem Statement Current State: Desired State (Short Term): Multi-process printers are expensive, controlled intellectual property Single Process printers require multiple machines to produce complex parts. Desired State (Short Term): Prototype printer to demonstrate concept Easily extensible for future development Desired State (Long Term): A fully functional, open source, multi-process printer. Constraints Must fit on a lab bench Open Source Design (System and Software) Final Cost <$5,000 Speaker: Austin

Key Project Goals and Deliverables Project Goals (Short Term) Develop a robust system architecture that supports extensibility. Build a prototype multi-process 3-D printer with basic functionality. Project Goals (Long Term) Fully operational, open source, inexpensive multi-process printer accessible to hobbyists. Deliverables (Short Term) Extensive design, test, and support documentation for future teams Functional prototype unit to be built upon. Deliverables (Long Term) Fully open source published design. Fully operational multi-process printer. Speaker: Austin

P14551 Stakeholders Speaker: Austin MSD Team Dr. Dennis Cormier Client 3-D Printing Hobbyists Competitors Speaker: Austin

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenario Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Chad

Customer Needs and Requirements Description Importance Category Comments/Status Uses software available to hobbyists (free or inexpensive) 9 Software   Ease of manufacturing/kittable Manufacturability Universal Interface for Tool Heads Ease of use Able to fit on a lab bench 3 Total system cost between $2000 and $5000 Cost Develop an easy to use GUI 1 Outside project scope Utilize existing hardware components available at RIT E-stops and other safety sensors Safety At least two (1 Additive and 1 Subtractive) process Performance Automated Tool Loading Motion Control Subsystems (X,Y,Z Motion) System Enclosure Robust system architecture Speaker: Chad

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenario Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Nick

Use Scenario Speaker: Nick

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenario Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Nick

Engineering Requirements Importance Source Function Engr. Requirement (metric) Unit of Measure Marginal Value Ideal Value 9 CR1 Cost Cost of System Operating Software USD   3 CR3 Performance Useability Time % Up Time low high Tool Change Time Seconds CR4 Enclosure Dimensions (LxWxH) Feet CR2, CR5 System Cost 5000 2000 1 CR7 Quantity of Recycled Parts CR3,CR9 Quantity of Implemented Additive Processes Quantity of Implemented Subtractive Processes CR11 Manipulable (Print/Remove) Part Volume Inches^3 12"x8"x8" CR12 Safety Ability to physically interact with parts during operation User Score Very Hard Impossible X/Y Print Resolution Inch or mm CR13 Ease of Use Development Extensibility (Improvement by Future MSD Teams) CR8 System halt on physical intervention Boolean FALSE TRUE CR6 Intuitive Interface Speaker: Nick

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenario Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Austin

Relationship Matrix Speaker: Austin

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenarios Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Jeremy

General Project Plan Speaker: Jeremy

Descriptive Project Plan Speaker: Jeremy

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenarios Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Jeremy

Functional Decomposition Speaker: Jeremy

Agenda Team Introduction Project Background Problem Statement/Definition Customer Needs and Requirements Use Scenarios Engineering Requirements Relationship Matrix Project Plan Functional Decomposition Team Norms and Values Speaker: Matt

Team Norms and Values Speaker: Matt

Questions?