P17214: Smart Mountain Bike Suspension
/public/

Problem Definition

Table of Contents

Team Vision for Problem Definition Phase

At the end of this phase, our team planned to have a complete and thorough understanding of the problem. We completed a finalized problem statement and a complete list of customer and engineering requirements. We also wanted to do some research to help us move forward into the System Design Phase.

Project Summary

In competitive mountain biking situations, suspension aids the rider in absorbing variations in the terrain, though undamped suspension movement on smooth surfaces robs the rider of power. To adjust the suspension and save energy in either condition, the rider must either remove their hands from the bars, limiting control, or use a remote system with both solutions requiring mental energy needed for the event.

Current remote suspension damping controls for mountain biking applications rely on cable actuated systems or the use of electronic servos with limited or no autonomous capabilities. The only commercially available electronic system that affords autonomous operation is capable of operating the rear shock absorber alone due to hardware delays preventing the front suspension from actuating on accelerometer input alone. The proposed solution would allow for remote operation of the front and rear suspension with autonomous operation for both through the use of forward facing terrain sensors.

A live one page summary of the problem can be found here.

Stakeholders

  1. Mountain bike rider
  2. Shop that sells the system
  3. Maintenance technician
  4. MSD Team

Use Cases

Scenario 1

Casual Rider

Casual Rider

Scenario 2

Competitive Rider

Competitive Rider

Scenario 3

Tuning autonomous mode

Tuning autonomous mode

Scenario 4

Failure in system

Failure in system

Project Goals and Key Deliverables

Customer Interviews

A list of interview questions used to elicit the specific needs of the customer and mountain bike riders is listed below.

  1. What do you want to happen when the battery dies?
  2. How do you want the battery to be replaced?
  3. How do you want it to switch in to manual mode?
  4. What is a favorable interface for the system?
  5. How much interaction do you want to have with the system before, during, and after riding?
  6. Do you want automatic mode customization and if so how/when (before race? after race? On stand?)?
  7. How much maintenance are you expecting to do?
  8. How important is data logging and what kind of data do you want?
  9. App? How high of a priority is a mobile app for this system?
  10. How would you like the controls to integrate with the cockpit setup? (tactile feedback)
  11. Are there times when you wouldn’t trust the auto mode?

The below customer requirements were created from customer interviews with Brian Venderbosch and David Marshall

Customer Requirements (Needs)

A table of customer requirements is shown below. The customer requirements table is used to take the outcomes from the customer interview and to put these needs into a list of priority items.

Table of customer requirements

Table of customer requirements

A link to the live document can be found here

Engineering Requirements (Metrics & Specifications)

The Engineering Requirements were created from the Customer Requirements. These requirements are specific and have measurable values that are testable. These will be used to assist in the design of the final product.

A Table of Engineering requirements

A Table of Engineering requirements

A link to the live document can be found here

Constraints

Benchmarking

The table shown below demonstrates the capabilities and features of both current and coming products which aim to provide similar resolutions to the problem.

A benchmarking of competitive products

A benchmarking of competitive products

A live version of the document can be found here.

House of Quality

House of Quality

House of Quality

The live House of Quality document can be found here

Risk Assessment

The table shown below demonstrates the potential risk and severity applicable to the project

A table of risk assessments and likelihood

A table of risk assessments and likelihood

A live version of the document can be found here.

Design Review Materials

This presentation was given February 9th 2017.

Plans for next phase

Future Plans

Gantt Chart

Gantt Chart

Individual 3 Week Goals

Each member of the team has mapped out their goals and tasks for the next three week phase of the MSD 1 project. Individual plans are listed below

Home | Planning & Execution | Imagine RIT

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

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