P19464: Water Purification System

Problem Definition

Table of Contents

Problem Definition Documents

Team Vision for Problem Definition Phase

During this phase of our project, the team gathered customer requirements, engineering requirements, and projected risks to highlight critical elements of concern and priorities for the project moving forward. Interviews were had with the customer to confirm needs and gain additional background knowledge into the operating environment and expected use scenarios.

The team succeeded in obtaining the necessary information to hit the ground running during the following phases. This strong foundation will allow a smooth transition into initial design and later on, prototyping and test. Moving forward the team and our customer will be sure to have close interaction to verify all needs and requirements will be met or exceeded.

Project Summary

A water purification system is a device that will autonomously filter or kill harmful bacteria and viruses, leaving safe drinking water for the consumer. This device will be hands free, except in extreme situations / emergency scenarios, and will include a container acting as a reserve allowing the consumer to have access to the clean water immediately.

There are several purification devices currently in use but none of them are autonomous, they do not continuously store water in a reserve, and most of them do not produce enough water to satisfy multiple people with one unit. Systems currently advertised by the Ugandan Water Project are rainwater collection, borehole rehabilitation and the Saywer Filter. Each of these has critical limitations such as dependency of weather conditions, high cost of operation, and manual gathering of water. The water purification system will not be limited by these factors.

The goals of this project are to analyze current water purification systems in use and the patent database to identify opportunities to make a device that is fully autonomous, can operate 24/7, can continuously store water in a reserve and produce a volume to satisfy 3-4 people. The expected result is a functional prototype that can be marketed to charities and ultimately manufactured.

Team Values and Norms

Work done on time:

Excellent is having the work done 1-2 days ahead of planned due date

Expectation is having the work done before meeting or morning of due date

Deficient is rushing to have work completed during the due date or later

Incomplete is not doing work at all

Meeting on time:

Excellent is showing up to a meeting 10-15 minutes early with work prepared

Expectation is showing up 2-5 minutes early allowing time to get notes together

Deficient is rushing in during the start of the meeting or later

Incomplete is not showing up without giving prior notice


Excellent is contributing to group messages frequently and responding to direct messages immediately

Expectation is contributing to group messages when needed and responding to direct messages within hours

Deficient is barely contributing to the group chat and not responding to direct messages

Incomplete is being absent from all communication

Team Player:

Excellent is picking up slack and doing extra work when available while positively encouraging teammates and settling disputes

Expectation is doing required work and treating teammates and their ideas with respect and open-mindedness

Deficient is not completing assigned work, disrespecting teammates and and causing disputes

Incomplete is not participating in the project

Use Cases

Possible use-scenarios (our product should excel in the RED categories)

Possible use-scenarios (our product should excel in the RED categories)

One possible use-scenario of a mission-trip type trip

One possible use-scenario of a mission-trip type trip

Project Goals and Key Deliverables

4 projected project deliverables will be provided to the customer throughout the completion of the system. These deliverables will ensure that the customer is kept up to date with the progress of the project, as well as confirm to the customer that their requirements are being completed. Below, the deliverables and their purposes are outlined.

Water Purity and Cleanliness Test: This deliverable will be provided following the completion of filter testing. Expected customer requirements for pathogen elimination will need to be proven met.

Unit Expected Lifecycle Documentation: This deliverable will be provided after an analysis of the tested lifecycle for components requiring replacement, exchanging, or cleaning during use.

Projected Clean Water Production: This deliverable will be provided following final testing, outlining the total expected production of clean water on a per-day or per-hour basis in varying conditions and circumstances.

Final Deliverable: Following completion of product design, build, and test, a water purification device capable of meeting or exceeding agreed upon customer requirements will be provided.

Customer Requirements (Needs)

public/Problem Definition Documents/CustomerRequirements.png

See our current customer requirements table file here

Engineering Requirements (Metrics & Specifications)

public/Problem Definition Documents/EngineeringRequirements.png

See our current engineering requirements table file here

House of Quality

public/Problem Definition Documents/QFD.png

See our current house of quality table file here

Risk Management

Risk Management Table

See our current risk management table file here

Design Review Materials

Include links to:

It is appropriate for you to send your customer and guide a link to this page in preparation for the review. This will ensure that they know what you will be presenting and how to view all of your work. Any EDGE link should start with http://edge.rit.edu/edge/P1xxxx..... Using "http" instead of "https" will ensure that non-RIT stakeholders can view the content without being prompted for a DCE login and password.

Plans for next phase

9/13/2018 Gantt chart (3 weeks out)

9/13/2018 Gantt chart (3 weeks out)

See our working gantt chart here

Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation