PRODUCT Progress Update 2 v2023
docx
keyboard_arrow_up
School
Oregon State University, Corvallis *
*We aren’t endorsed by this school
Course
498
Subject
Industrial Engineering
Date
Jun 2, 2024
Type
docx
Pages
3
Uploaded by UltraValor2353
[Project name here]
Progress Update # 2
[Team member names]
[Student 1 name]
[Student 2 name]
[Student 3 name]
2023
[Insert OSU or Team Logo as watermark or include a photo of the team or project]
[Insert Team Number Here]
[Insert Team Name Here]
1 Design Changes
[
Discuss how the design has been altered BETWEEN Progress Update #1 and now
and describe all problems encountered. For design changes, include applicable simulations, engineering calculations, revised part drawings or other design specifications (probably in appendices) as necessary. Include details
for ALL iterations of the design, including failed iterations or any minor proof of concepts you may have elected to create. All changes in the design must include the motivation behind the change and the decision process regarding how to make the change. Provide all justifications that the decisions made thus far will produce successful results.]
[Teams may elect to organize the information in the following format, but are not required to.]
1.1 Design Iteration 1: Change in [subsystem/component] discussion
[Briefly describe what the original design was and the change made for this particular component or subsystem. Provide pictorial evidence of the differences if applicable] 2 Standards, Codes, and Regulations
[Provide a summary and table of any and all standards and codes of practice that apply to this project. A table of the standards should be similar to the table below. Provide a discussion of how these standards affect your project in detail. You may reference the list you created last term, but this section must be
more detailed and thorough now that your team is nearly done with designing the system.]
2.1 Standards applied to project
[Provide a table of standards similar to the table below.]
Standard
Number or
Code
Title of Standard
How it applied to Project
ASNI/AAMI HE 74:2001
Human Factors Design Process for Medical Devices
Helped in the design of how the device interfaces with the user in a safe manner.
3 Risk Analysis and Mitigation
3.1 Potential Failures Identified Fall Term
[Review your previous FMEA from last term and add any and all new potential failures that were brought
about by the design changes this term. Highlight these new/changed potential failures in the FMEA. Provide the shortened FMEA here, then include the full FMEA in the appendix. Include an introduction here then discuss the critical failures shown in the shortened FMEA.]
3.2 Risk Mitigation
[Discuss how your team took the list of potential failures in the previous section and designed their 2
[Insert Team Number Here]
[Insert Team Name Here]
system to mitigate these failures. Provide design evidence that the major critical failures have a low likelihood of occurring. Also provide discussion regarding any trade-offs in risk mitigation that occurred (i.e. were any risks harder to mitigate when trying to mitigate another? Were any new risks created during
the design process?).]
4 ES Proofs
[Use this section to discuss the Engineering Specification proofs run by the team. ES Proofs MUST be detailed enough to completely describe how each Engineering Specification is proven to be satisfied (including what program or equations were used, how the test was completed, etc.). Each team must include proofs that verify the system in reliable and robust (i.e. can withstand numerous uses, withstand external forces such as drops or impacts, etc.).]
[Each Engineering Specification must have its own subsection as shown to clearly describe how your team DID
meet the ESs. This document must outline definitively how each ES was
completed.] 4.1 ES Proof: Reliability [
required section]
[Provide concrete proof that your system is reliable in its operation through video documentation or equivalent. Reliability is related to continuous and consistent performance in operation.]
4.2 ES Proof: Robust [
required section]
[Provide concrete proof that your system is robust in its design through video or equivalent documentation. Robustness is based on higher quality design that won’t break or be damaged easily.]
4.3 ES Proof #1 – [State Engineering Specification #1 here]
[Describe how your team can prove that this ES has been satisfied in your design. Clearly outline the program, software, and/or equations that were used to prove the ESs has been met.] 4.4 ES Proof #2 – [State Engineering Specification #2 here]
[
Insert enough subsection headers and content into this section to clearly outline every Engineering specification.]
3
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help