P17010: GearChair
/public/

Systems Design

Table of Contents

Our System Level Design Review Presentation can be found here.

Team Vision for System-Level Design Phase

Systems Design Unit schedule found here.

Functional Decomposition

Functional Decomposition

The live document can be found here.

Benchmarking

Market Comparison

Pugh Chart

Concept Development

System Decomposition

Morphological Chart

Feasibility: Prototyping, Analysis, Simulation

Width Analysis

Shaft Analysis

Cable Analysis

Speed Testing

Force to Move Testing

Shaft Testing

Cable Testing

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.

Instructions

  1. Instructions and EXAMPLE must be deleted before the System-Level Design Review AND Identify an owner for this document.
  2. This document will be inspected at all project reviews during MSD1.
  3. Begin with the Function Decomposition and identify concepts that can deliver the function and are expected to comply with the project constraints.
  4. Identify the best available solution that the customer could access. These are often earlier projects or commercially available systems that do not fully address the customer's needs. Sometimes these are a mix of elements plus manual that integrate and complete them to approximate a full customer solution.This best existing system will become the datum.
  5. Generate new concepts as well. The team should be considering at least 50 different concepts to cover all of the required functionality. In many cases, 100 is a better target. Try to avoid redundant efforts by teammates BUT don't leave gaps.
  6. Consider the Engineering Requirements and overall project objectives to construct a list of selection criteria. Remember that the concepts must be integrated by the team within the expected system envelope, the project constraints, the available schedule and budget.
  7. Use a systematic selection process, e.g.Pugh, to evaluate, recombine and add new concepts, by comparing them to the datum. Select the best combination of concepts.
  8. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

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:

The real value in this step of the process is not the comparison matrix you generate to compare your concepts, but the analysis and discussion you do to support your evaluation.

Systems Architecture

Purpose

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

Instructions

  1. Instructions and EXAMPLE must be deleted before the System-Level Design Review Identify an owner for this document.
  2. This document will be inspected at all project reviews during MSD1.
  3. Begin with the Function Decomposition. The top level function is provided by the total system. The next level of functionality is generally provided by subsystems. Lower levels of functionality are delivered by sub-subsystems, assemblies and sub assemblies on down to individual parts. System Architecture generally addresses subsystems.
  4. Define the functional system architecture by assessing how material, energy, information and forces are transmitted from the total system inputs to the outputs. Define the condition and timing of these at the subsystem interfaces.
  5. Next describe the physical system by considering how envelopes of the various subsystems (the concepts and expected designs that embody these) and how they will interface with each other.
  6. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

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

Instructions

  1. Instructions and EXAMPLE must be deleted before the next Project Review AND Identify an owner for this document.
  2. This document will be inspected at all project reviews until the system is assembled and debugged.
  3. Identify subsystem interfaces.
  4. Define projected system operation.
  5. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.
  6. Reference: http://edge.rit.edu/edge/P15571/public/Detailed%20Design%20Documents/Data_Flow_Chart_Rev_2_0.pdf
  7. Note: This section should be started during systems design, and continued through detailed design.

Risk Assessment

Have you updated your risk list (started during Problem Definition) to include new items specific to your chosen concept?

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


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