P19305 Preliminary Detailed Design

Team Vision for Preliminary Detailed Design Phase

Over the Preliminary Detailed Design Phase, Team 19305 will complete the initial rendering of the electric longboard's folding mechanism, submit our grant application to IEEE, maintain open communication and utilize consultation with our guides, and develop expectations for our detailed design phase. Additionally, the initial parts list and BOM will be created and verified by the team. Updates to necessary documentation, criteria, etc. will be made as necessary and preparation for the detailed design will begin.

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

Between now and the end of the semester, your team will continue to add detail to your design, which will require more detailed analysis and prototyping to answer feasibility questions. Consider:

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

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.

Instructions

1. Instructions and EXAMPLE must be deleted before the Preliminary Detailed Design Review AND Identify an owner for this document.
2. This document will be inspected at all project reviews during MSD1.
3. At the subsystem design level, feasibility analysis and prototyping may still be relatively coarse. First order analysis, estimation, and rough physical mockups are to be expected. Detailed analysis on critical subsystems or components may be complete.
4. Select the concepts that are expected to be most sensitive and/or problematic. These are usually concepts that will not be satisfied by COTS components.
5. Define the transfer function that converts the concept/subsystem inputs into the desired outputs as a function of specific design parameters. This can be done via theoretical analysis or empirical prototyping. it is often useful for two or more team members to work together so that the work is checked and a clear understanding of these models is captured. Get help here from SMEs who should be able to alert your team to potential difficulties and possible solutions.
6. Use the models to quantitatively specify the design parameter targets and acceptable ranges.
7. Confirm that the concepts selected and the designs anticipated will generate the desired performance.
8. 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. 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 (TEAM)

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.

Instructions

1. Instructions and EXAMPLE must be deleted before the Detailed Design 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. Define all geometries of interfaced subsystems
4. Define detailed fabrication instructions for all unique parts.
5. Call out all purchased parts
6. Develop a software design that reflects operating flow charts and timing diagrams
7. Adhere to all required design standards.
8. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

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 (DEIRDRE)
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) (DEIRDRE)

Purpose

Confirm that all expenses and contingencies are afforded by the project financial allocation

Instructions

1. Instructions and EXAMPLE must be deleted before the first Detailed Design 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. Define all components to be fabricated or purchased.
4. Define all other purchases to enable completion of the project, including operating supplies, with contingencies.
5. Complete BoM template.
6. Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.

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

Instructions

1. Complete test plans specifying the data to be collected, instrumentation to be used, testing procedures and personnel who will conduct the tests.
2. Plans should use data collected to define the accuracy of models generated during feasibility analysis.
3. If your team's testing will involve human subjects, you must review the RIT Human Subjects Research Office "Protecting Human Subjects" page for details on securing approval for work with human subjects

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

This section should continue to be updated from your systems level design documentation.

Risk Assessment (TANVIR)

• Risk Category	Risk	Cause	Effect	Risk Prevention	Contingency Plan	Likelihood	Severity	Importance	Owner(s)
  Technical	Failure of Force Sensors	Damage to sensing surface or blocked transmission of force to sensing surface	Complete loss of motor control/unexpected motor response	Thoroughly test force sensor installation	Use remote to control motors	3	9	27	Matthew G.
  Technical	Control system causing unexpected outputs (malfunction)	Incorrect inputs were put in the system	Incorrect Outputs/System Failure	Have at least one other team member monitoring the inputs made to the system	Have a micro-controller system expert look over the system	1	9	9	Matthew G.
  Technical	Electronic components protection	Exposure to external environmental factors (water,rocks, etc.)	Damage to the battery and other components	Ensure proper location and protection of electrical components.	Have a guide for a particular environment that must	1	3	3	Kristin O.
  Technical	Product failure or part malfunctions	Miscalculations during design process	A non-functioning product	Mechanical Design Leads must be consulting each other	Consult with Mechanical Engineering Professor.	3	9	27	Tanvir M. Connor F. Erik L.
  Safety	Pinch points in the mechanism	Folding Mechanism	Damage to hands and fingers of riders.	Proper outlined guide for Hand Placement	Wear protection gloves	1	3	3	Tanvir M. Connor F. Erik L.
  Safety	Motor failure	Low resistance and Electrical overload	Corrosion of the motor shafts, bearings, and rotors	Determine the full specifications for what type of motor we are looking for	Invest in a High quality motor	3	9	27	Deirdre A. Matthew G.
  Safety	Stability failure	Trucks don't work as designed	Danger to the rider of falling and hurting themselves	Conduct tests of trucks over full range of speeds with differing loads	Find trucks that are stable	3	9	27	Tanvir M. Connor F.
  Safety	Overall integrity of collapsible parts	Weak focal point	Collapsible mechanism does not have a long life span and the board is damaged after few uses	Determine the best and most applicable collapsible mechanism.	Hinge system	1	9	9	Tanvir M. Connor F. Erik L.
  Resource	Lack of additional funding (Budget)	Not keeping track of spending	Unable to finish design or a low quality product	Proper documentation of spending	Cut costs where necessary	3	3	9	Deirdre A.
  Resource	Customer manufacturer quality and accuracy risk	Bad quality deliver	Low quality product	Make sure to order from reputable manufacturers.	Change suppliers	1	9	9	All
  Resource	Lack of experienced riders to test prototypes or data collection	Lack of exposure to longboard riding	Lack of essential knowledge on the design of the longboard	Have a team meeting for instruction on how to ride the longboard	Interview experienced riders	1	1	1	Erik L.
  Resource	Team Members Being Absent	Exceptional Circumstances (Sickness, etc.)	Falling behind on deadlines and not being able to create longboard.	Make sure at least one person on the team has a good understanding of what the abstentee was doing,	Assign the another person the absentee's task depending on how important the task is.	3	3	9	All
  Technical	Folding Mechanism Roadblock	Complexity in Design and Material Scarcity	Can't integrate all essential parts and can't proceed with the design.	We build a functioning prototype without a folding mechanism (mule).	We design a different folding mechanism into our mule based on hinges.	9	9	81	All
  Resource	Not Being Able to Design PCB Board	Lack of experience with PCB design.	Non-functioning PCB.	Try to find a professor to help verify.	Buy VESC.	3	9	27	Matthew G.

Design Review Materials (KRISTIN)

Include links to:

• Pre-read
• Presentation and/or handouts
• Notes from review
• Action Items

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 

• As a team, where do you want to be in three weeks at your next review?

• As an individual on the team, what are you doing to help your team achieve these goals? (Use the individual 3-week plan template attached to this page for this)