P14417: B9 Particle Filter Dan Anderson Thomas Heberle Perry Hosmer Karina Roundtree Kelly Stover.

Slides:



Advertisements
Similar presentations
B2B Advertising.
Advertisements

CE 370 Filtration.
The Software Project Management Discipline Succes software projects require careful planning and good use of iterative approaches. Understanding risks.
Improving Executive Engagement Project Leaders Group Adrian Boyd, 7 th June 2011.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
P14417: B9 Particle Filter Cycle 3: System Integration and Testing Dan Anderson Thomas Heberle Perry Hosmer Karina Roundtree Kelly Stover.
Project Management Lecture Developing the Project Plan.
AN OVERVIEW BY JAMIE STARKE The Role of Prototyping.
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
API Design CPSC 315 – Programming Studio Fall 2008 Follows Kernighan and Pike, The Practice of Programming and Joshua Bloch’s Library-Centric Software.
Quality Function Deployment
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
New Product Development Chapter Eight. Copyright ©2011 Pearson Education, Inc., Publishing as Prentice Hall 8-2 Key Learning Points Why new products are.
WP Inc. Case STUDY 3.1 Problem Solving Jonathan Stanley & Kari Eddings
Survival Analysis for Risk-Ranking of ESP System Performance Teddy Petrou, Rice University August 17, 2005.
Narbeh dereghishian - edgardo garcia - ana montenegro - calvin ting - kevin tjho.
Particle and Fluoride Pre-Filter for B9 Plastics Dan Charles – Chemical Engineer John Markidis – Mechanical Engineering Israel Powell – Chemical Engineering.
Victoria E. Aldridge, Pharm.D. JUSTIFICATION OF CLINICAL STAFFING Victoria E. Aldridge, Pharm.D.
IT Project Management Cheng Li, Ph.D. August 2003.
Detailed Design Review: Pre-Filter P13418
Managerial Accounting: An Introduction To Concepts, Methods, And Uses Chapter 11 Profit Center Performance Evaluation Maher, Stickney and Weil.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 23Slide 1 Chapter 23 Software Cost Estimation.
Process Analysis Agenda  Multiple methods & perspectives There are lots of ways to map processes  Useful in many situations not just HRIS design  Preparation.
P14417: B9 Plastics - Particle Filter Detailed Design Review Dan Anderson / Thomas Heberle / Perry Hosmer / Karina Roundtree / Kelly Stover December 10,
Lecture 31 Introduction to System Development Life Cycle - Part 2.
P14417: B9 Particle Filter Introduction & Background Results Daniel Anderson, Thomas Heberle, Perry Hosmer, Karina Roundtree and Kelly Stover Design and.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Software Project Management
P14417: B9 Plastics - Particle Filter Subsystem Design Dan Anderson / Thomas Heberle / Perry Hosmer / Karina Roundtree / Kelly Stover October 29, 2013.
1 Local Readiness Team Lead Kick-Off Meeting May 16, 2007.
P14417: B9 Plastics - Particle Filter Problem Definition
Module 2: Creating a Plan for Network Security. Overview Introduction to Security Policies Designing Security by Using a Framework Creating a Security.
Maricopa Priorities Update Spring Agenda Overview Strategic Directions Implementation process Categorized Recommendations Preliminary Timeline.
Ethics of Software Testing Thomas LaToza CS 210 Final Presentation 12 / 2 / 2002.
What’s Coming…. Today (2/16) Update and review a sample final presentation (20’) Group Presentations- milestones and resource requirements (50’) Work Sessions.
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
Formulating a Simulation Project Proposal Chapter3.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
3/30/04 16:14 1 Lessons Learned CERES Data Management Presented to GIST 21 “If the 3 laws of climate are calibrate, calibrate, calibrate, then the 3 laws.
Chapter 3 Strategic Information Systems Planning.
Introducing Project Management Update December 2011.
1 Getting Started : Purposes of IS Strategic Planning.
CS5103 Software Engineering Lecture 02 More on Software Process Models.
Lecture 4 – XP and Agile 17/9/15. Plan-driven and agile development Plan-driven development A plan-driven approach to software engineering is based around.
Requirements / Specifications. 01/18/10CS-499G2 Requirements Determine what the customer needs (wants) the software to do  What are requirements?  An.
5 - 1 The Cost Modeling Process Chapter Introduction What makes a good cost model? – Good Statistics – Quality Data – Relevant Data – Analogous.
Definitions of GIS Works with geographic information Performs data input, management, manipulation/analysis, and output functions Composed of hardware,
Topic 6 Managing stage boundaries
Project Management in a Nutshell Tips to Keep Your Project on Track Ceilyn Boyd & Cathy Conroy Programs, Projects & Operational Planning 16 September.
Managing Challenging Projects Presented to the class of: Dr. Jane Mackay M.J. Neely School of Business.
January 2013 Action Plan Skills Building: Module 4 Implementing and Evaluating the Action Plan.
Executive Review: Glowcap Project FabG2 Team: Gordana Delic, Ian Warman, Iker Chocarro, Karen Lee Presented: 7/29/2010.
Risk management. Definition and Aim  Risk management is examine systematically all risks and react on them, taking into account all the effects of.
MISSION What conditions must be met to ensure that the digital world of work is humane? EntriesTotalBalance Data Protection High and safe standards of.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Zeosorb - The Clean Solution. AMAZING REVOLUTION!! LATEST STATE OF THE ART 3 IN 1 SOLUTIONS Zeosorb FOR YOUR WATER FILTERATION UNITS.
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
P14417: B9 Plastics - Particle Filter System Design
Business System Development
Project Management The Roles and Responsibilities of a Project Manager
Rapid Application Development
Methodologies By Akinola Soyinka.
New Product Development
The Role of Prototyping
Usability Techniques Lecture 13.
Mohr Separations Research, Inc.
P14417: B9 Plastics - Particle Filter Detailed Design Review
Time Scheduling and Project management
Presentation transcript:

P14417: B9 Particle Filter Dan Anderson Thomas Heberle Perry Hosmer Karina Roundtree Kelly Stover

Agenda Design Overview Requirements Summary Competitive Advantage Process Improvements Next Iteration: Design Improvements Project Planning Lessons Learned

Design Overview

Requirements Summary RequirementMetricUnitsMarginalTargetActualResult Easy to clean / rechargeTime to cleanMinutes<10< O Has a minimal start-up period.Time elapseds (seconds)<30<10 1 O Usable by a family of 5, for 2-5 years w/out full replacement Mean Time To Failure Number of Uses >730>3650 Brush: 800 Bucket Assembly: Infinite Life Mesh: Infinite life O Removes Particles (turbidity/total suspended solids), assist UV TRANSMISSION TurbidityNTU O Does not negatively affect the taste of the water Percent of people with no negative affect %>50%>75% 63.50% O Overnight use scenarioFlowrate lpm (liters per min.) O Easy to clean / recharge # of Tools Req'd for (dis)assembly by end user -<2<1 1 O Lightweight for transportProduct Weight LBs (Pounds) <10< O Inexpensive ShippingRelative shipping volume- < volume of initial design 1/2 Initial (via nesting) O Operates using only energy available naturally (gravity, human power, etc.) Binary (Yes/No)--Yes O Filter is inexpensiveCost to produce$ (dollars)<25<20 $17.90 O Requires no consumables for operation, except for very cheap & locally available materials (salt, soap, sand, etc.) Operating Cost$ (dollars)<20 $- O No hazardous releasesBinary (Yes/No)--No O Legend X Doesn't meet specification Δ Undetermined O Meets specification

Competitive Advantage Simple design - minimal parts required Easy to use Durable Minimal Cleaning necessary - minimizes chances of getting contaminated Commonly found parts Reusable

Process Improvements Largest gap was in expectation for flow rate. May have been avoided through better communication with customer, specifically  More contact with customer  Making sure we obtained approval from the right people  Clearly stating what we are doing and ensuring the customer approves

Next Iteration: Possible Design Improvements Placing the mesh at an angle to increase flow rate (more surface area, less clogging) Induce pressure in the system to increase flow rate (e.g. plunger) Increase the diameter of the mesh openings. Add more holes on the underside of the lid. Implementing pre-filter with larger pore size. (Layered system) Increase hydrostatic pressure with higher volume of water. * Design considerations made with budget consideration.

Project Planning Flowrate testing was the largest source of error when planning. o It was difficult to estimate how long testing would take. o Even with 3 Prototypes, testing was often delayed. Water collection was the main factor in this delay o Water sources were frozen more than anticipated. o Collecting water before finalizing our design would have beneficial; regardless of the design we knew we’d eventually need it for testing. Action items weren’t always 100% correlated to the project plan. o The 2 nd semester of MSD was a big improvement in this respect.

Lessons Learned Communication: External (customer) and internal (project team) communication should be more frequent and consistent. Have written agreements for decisions and goals. Planning: Plans constantly change and evolve. Tasks like testing and exercising the system will often take longer than anticipated and may introduce issues that further extend timelines. Risks: Discover as many risks as you can. Make sure you account for a myriad of possibilities, from very likely situations to those you’d never expect to occur. Execution: Teamwork is essential. Share roles, don’t get locked down into one, as the project will benefit from different perspectives and input.

Questions / Feedback?