P19224: Biometric Driver Monitoring

Problem Definition

Table of Contents

Team Vision for Problem Definition Phase

The goal of this phase is to ensure that our interpretation of the project aligns with the customer's vision. The project readiness packet was supplied to us, and it was up to us to define requirements using tools like use cases, customer interviews, expert interviews, etc. At the conclusion of this phase, we should have all of the information needed to start producing concept ideas and determining how we are going to achieve these requirements.

Project Summary

The goal of this project is to develop a system to integrate driver vitals and biometrics into the typical data acquisition system of a racing vehicle. The driver is the most important part of a racing vehicle, and if the driver cannot perform adequately, then the quality of the car itself matters little. The tuning of the car is also extremely important. While the driver is expected to give verbal feedback, sometimes not all necessary information is transmitted. To solve these issues, we would develop a method of measuring driver heartrate, body temperature, muscle force, reaction time, and fatigue of the driver based on the metrics overtime. These metrics will be recorded into the current logger on the car to be viewed alongside the data already being collected.

One goal of this would be to allow the team to evaluate the driver’s vitals to interpret when the driver may have experienced an undesirable or surprising reaction of the car. A spike in the heartrate of the driver likely indicates that he/she almost spun, slid, etc. Another goal would be to evaluate driver fitness. Sometimes, laptimes will drop off as the car drives for a longer period of time. There are elements on the car that could cause this, but it can also be from just driver fatigue. These vitals should aid in allowing the people looking over the data to distinguish between these two situations. Along with the goals mentioned above, the metrics can allow optimization and validation of erganomic designs associated with the driver such as (but not limited to) seat shape, steering wheel design, and location of brake and throttle pedals. Having this information can bring “driver feedback” about how the car is feeling and driving to a whole new, competitive level.


These are entities who currently have an interest in our project, or some examples who may show interest in the future or in the completed project.
  1. Driver(s)
  2. Team in the Pit
  3. Engineers (The Team)
  4. Sponsors
  5. Guide
  6. Future Engineers who may work on the project
  7. Other racing teams that may want the same product for their team
  8. Emergency Response Personnel
  9. Design Judges at FSAE Competitions
  10. Racing electronics companies (3rd party companies)

Use Cases

Figure 1: Use Cases

Figure 1: Use Cases

Project Goals and Key Deliverables

The desired end result of this project is a working prototype that transmits all of the signals listed in the PRP over CAN in a usable (filtered) manner.

Necessary deliverables at the end of the project are all relevant project documents, and the prototype, in whatever state it is in at that time.

Customer Requirements (Needs)

Figure 2: Customer Requirements

Figure 2: Customer Requirements

The full document can be viewed here: Customer Requirements

Engineering Requirements (Metrics & Specifications)

Figure 3:Engineering Requirements

Figure 3:Engineering Requirements

The full document can be viewed here: Engineering Requirements


House of Quality

Figure 4:House of Quality

Figure 4:House of Quality

The full document can be viewed here: House of Quality

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

In the next phase, we will begin the process of system-level design. We will complete tasks regarding benchmarking, concept development, and concept selection to move towards our final design and prototype development.

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