P18014: Stand-Up Walker
/public/

Preliminary Detailed Design

Table of Contents

Team Vision for Preliminary Detailed Design Phase

During this phase of the project, the S.T.E.P.S. team aimed to further develop concept sketches and ideas that were formed in the System Level stage. The renderings presented in the last review were analyzed further at the subsystem level in order to capitalize on design flaws there.

It was decided that the most effective way to further develop the subsystems was to design a test prototype and receive direct feedback on each of the ideas. The thought process through this phase is outlined below.

Prototyping, Engineering Analysis, Simulation

Iterative activities to demonstrate feasibility, including assumptions you made in your analyses or simulations. Have you completed sufficient analysis to ensure that your design will satisfy requirements? Have you included all usage scenarios in your modeling?

Feasibility: Prototyping, Analysis, Simulation

Purpose

  1. Confirm that the selected concepts can deliver functionality defined by the System Architecture.
  2. Define the optimal values of the most sensitive design parameters.
  3. Support the evaluation of your team's concepts with quantitative information.
  4. Make decisions about design drivers.

Inputs and Source

  1. Engineering Requirements
  2. Concept Selection
  3. Results of preliminary prototyping, analysis, and simulation

Outputs and Destination

  1. A list of Design Parameters, Quantified Targets, and acceptable tolerances
  2. Sensitivity analysis
  3. Refined concept Selection
  4. Drawings, Schematics, Flow Charts, etc.

Drawings, Schematics, Flow Charts, Simulations

Your team should have completed a significant portion of your detailed design, but it will likely require revision based on feedback at your design review.

Purpose

Define instructions that will enable fabrication of the elements required to build and operate the entire system.

Input and Source

  1. Selected Concepts
  2. Feasibility Models
  3. System design and interface definitions

Output and Destination

  1. Complete hierarchy of design files from system level down to components
  2. Parts list
  3. Software design that specifies coding requirements
  4. Test plans, including expected performance vs. requirement and any applicable test standards (e.g., ASTM)

Bill of Material (BOM)

Purpose

Confirm that all expenses and contingencies are afforded by the project financial allocation
Breakdown of Costs for Test Prototype

Breakdown of Costs for Test Prototype

Structural BOM for Test Model

Structural BOM for Test Model

Live Document of BOM with Costs.

Input and Source

  1. PRP.
  2. Design Files.

Output and Destination

Completed BoM and Budget

Test Plans

Purpose

Demonstrate objectively the degree to which the Engineering Requirements are satisfied
Test Plan for Prototype Model

Test Plan for Prototype Model

The document can be found in PDF form here.

Inputs and Source

  1. Engineering Requirements
  2. Feasibility Models
  3. Test standards (e.g., ASTM). The RIT library maintains an infoguide with links to standards databases, many of which provide industry-standard test procedures for a variety of components and systems.

Outputs and Destination

  1. Report that summarized the degree to which Eng Reqs are satisfied.
  2. Assessment of accuracy of feasibility models.
  3. IRB Submission, if applicable (allow at least 30 days for this to be reviewed - more time is idea, since the IRB outcome may be a request for you to modify your proposed test protocol)

Design and Flowcharts

Risk Assessment

Risk Assessment for PDDR

Risk Assessment for PDDR

Design Review Materials

Preliminary Detailed Design Presentation PowerPoint

Plans for next phase

Schedule for Detailed Design

Schedule for Detailed Design


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