P14317: Gaseous Flow Controller
/public/

Problem Definition

Table of Contents

Your website should document your journey through MSD, so include work-in-progress as well as latest results. Use pdf's for display whenever possible so that information is easily viewable without the need to download files and open applications. (Your EDGE file repository should still contain original files).

Sample categories are listed below, but feel free to change or add nodes to better correspond to your project and your Guide’s expectations.

Project Summary

Upstate NY has an abundance of natural gas which can be used for energy. This natural gas can be used for fueling an automobile or for creating electricity. To capture and harness the opportunities of natural gas for automobiles a gaseous flow controller can be added to vehicles to inexpensively allow them to use natural gas as a form of fuel. This device allows the user to mix gas and air which can combust inside the engine creating power. This controller also has the option to be used for gas control in chemical systems and for monitoring liquids in fluids systems. Prototypes have been created and tested, but have not been practical. The objective of this project is to create a gaseous flow controller that can be used in many different industries, but be durable, cost effective, reliable, and simple to input into existing systems. The projected end result will be a fully functioning prototype that a use air that and complies with given constraints.

Questions

Number Questions Answer
1 What times are you available?
2 If there is a current idea, under what circumstances does the current idea fail?
3 What is our deliverable?
  • Prototype
  • Fully functional
  • Ready for sale
4 What types of data do they want outputted?
  • pre-filtered or pre-processed
5 What actions are going to be simulated?
6 What software are we interfacing with?
  • will the software be able to filter the data to show how it is a finger
7 Who approves the device?
8 Who is in control of the funds?
  • What is our expected budget?
9 Who is the user?
10 What are the hand sizes range?
11 What is the range of communication?
12 Is a battery absolutely necessary?
13 How accurate does it have to be? +/- 2 degrees?
14 Is it 120 Hz because we are trying to match the data rate with the cameras?
15 Why is it 2 lbs for the peripheral components? can it heavier?
16 Where do you want the location of peripheral components? (arms,back,chest)
17 How long do you want for calibration time?
18 What are the operating conditions?
19 Battery Life?
20 What is the operating life?
21 Any other faculty or people we can ask for advice?
22 Does it have to be a glove?

Customer Requirements (Needs)

Customer requirements , including importance. You may also want to include links interview notes here.

Here is the excel file of customer needs.

Engineering Requirements (Specifications)

System-level and function-level requirements that define the intended performance of your system.

Here is the excel file of Engineering Requirements.

Constraints

Factors, usually system-level, that limit your design space (e.g., cost, total weight, total footprint, total power available)

Project Goals and Key Deliverables

Expected end result of the project, what the customer can expect to receive at the end of the project.

Solution Parking Lot

During the Problem Definition phase, you will start coming up with possible solutions. Rather than act on those now, put them in the Solution Parking Lot, and come back to them after your team has fully defined the problem.

Home | Planning & Execution | Problem Definition | Systems Design | Detailed Design | Build, Test, Document | Project Review | Photo Gallery