P15221: Baja SAE DAQ
/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 editable files).

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

You may want to consider using the Problem Definition Documents directory to store this information. Some templates are available there for your use.

Project Summary

Currently the RIT BAJA SAE team has a data acquisition system that collects various vehicle parameters, however it has multiple drawbacks. The system has failed to last the duration of an endurance race, which can last up to 4.5 hours, nor has it been able to gather all data accurately and consistently.

The goal of this project is to provide the customer with a fully functional data acquisition system that will capture, store, and retrieve BAJA performance and reliability parameters while being easily integrated into the chassis. The expected end state of this project is to provide the RIT BAJA team a packaged system that can survive the long endurance races as well as being a solid base that can be build upon in years to come. The system must reliably report speed data to the driver while periodically transmit data to the engineers for real-time diagnostics.

Project Goals and Key Deliverables

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

Customer Requirements (Needs)

Customer requirements, including importance. You may also want to include links interview notes here. Have you sought input from all the relevant stakeholders? Have you confirmed this list of requirements with your customer? Are all your customer requirements being addressed by a measurable, testable engineering requirement or constraint?

Engineering Requirements (Metrics & Specifications)

System-level and function-level requirements that define the intended performance of your system. Are your engineering requirements measurable and testable? Can they all be traced back to customer requirements?

Constraints

Factors, usually system-level, that limit your design space (e.g., cost, total weight, total footprint, total power available). Are your constraints measurable and testable, and can they be traced back to customer requirements? Have you considered economic, environmental, social, political, ethical, health and safety, manufacturability, and sustainability constraints, for example?

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 | Publications & Presentations | Photo Gallery