P18014: Stand-Up Walker
/public/

Systems Design

Table of Contents

Team Vision for System-Level Design Phase

The S.T.E.P.S. team aimed to use our understanding of the problem statement to brainstorm possible solutions and develop concepts and sketches of such. During the Systems Design phase, the team established the subsystems that will exist in our concepts, we developed a morphological diagram in order to explore various methods for each subsystem, and we chose 2 final concepts to move forward with into the next phase.

Functional Decomposition

Purpose

Define the total list of functions and subfunctions, based on the Customer and Engineering Requirements, that must be delivered by the final design. This will establish the need for specific concepts necessary to deliver the overall objectives of the project
Functional Decomposition Diagram

Functional Decomposition Diagram

Inputs and Source

  1. Template and Example.
  2. Project Objectives.
  3. Engineering Requirements.
  4. Benchmarking Data.

Outputs and Destination

  1. Complete list of functions that must be provided in order to satisfy the functional requirements of the entire project.
  2. Engineering Requirements are written to measure how well the functions are performed.
  3. Concepts are generated around functions identified here.

Benchmarking

Purpose

Avoid redundant work by identifying already available solutions and concept options
Benchmarking

Benchmarking

Inputs and Source

  1. PRP.
  2. Project Objective.
  3. Function Decomposition.
  4. Prior MSD EDGE sites.
  5. Customers.
  6. Vendors and users of existing or similar solutions.
  7. Literature search.
  8. Friends and associates.

Output and Destination

  1. List of best available concepts and embodiments.
  2. Criteria used for selection of best.

Concept Development

Purpose

Generate new concept options or combinations that can potentially exceed the benchmark concepts
Ideation Overall

Ideation Overall

Progression 1

Progression 1

Progression 2

Progression 2

Progression 3

Progression 3

Input and Source

  1. Function Decomposition.
  2. Results of Benchmarking.
  3. Analysis and prototyping.

Outputs and Destination

List of multiple viable concept options to provide each function.

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.
Preliminary Feasibility Analysis

Preliminary Feasibility Analysis

Inputs and Source

  1. Engineering Requirements
  2. Concept Selection

Outputs and Destination

  1. A list of Design Parameters, Quantified Targets, and acceptable tolerances
  2. Sensitivity analysis
  3. Concept Selection

Morphological Chart and Concept Selection

Purpose

  1. Develop multiple concept options to deliver the required list of functions.
  2. Ensure that concepts (means) are available to deliver every required function.
  3. Select the optimal set of concepts that can be integrated to meet the project objectives.
Morphological Chart

Morphological Chart

Inputs and Source

  1. Project Objectives.
  2. Engineering Requirements.
  3. Function Decomposition.
  4. Concept Development.
  5. Benchmarking criteria.
  6. System Architecture.

Outputs and Destination

  1. A complete set of concepts that provide all of the functionality required.
  2. Fall back options to substitute for the most risky concepts.

Concept Selection

This consists of two elements:
Pugh Chart Concept Selection

Pugh Chart Concept Selection

Systems Architecture

Purpose

  1. Ensure flow of energy, info, material and structural forces as intended.
  2. Define subsystem functions, envelopes and interfaces.
System Architecture

System Architecture

Inputs and Source

  1. Engineering Requirements.
  2. Functional Decomposition.
  3. Concept Development.

Outputs and Destination

  1. High level description of the total system that support concept selection.
  2. Interface definition for subsystem design.

Designs and Flowcharts

Purpose

Define a high-level view of the elements required to build and operate the entire system
Design Flowcharts

Design Flowcharts

Risk Assessment

Risk Assessment

Risk Assessment

Design Review Materials

Include links to:

Plans for next phase

As a team, we would like to further develop our subsystems into more details while creating a plan for how to test these subsystems. Over the next few weeks, the team will focus on working to brainstorm and building a working and cost effective prototype to model our concept. A plan of the next coming weeks is as follows:
4 week Project Plan

4 week Project Plan


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