Stoor-Sarina-HW5

doc

School

Drexel University *

*We aren’t endorsed by this school

Course

688

Subject

Mechanical Engineering

Date

Apr 3, 2024

Type

doc

Pages

8

Uploaded by ColonelKomodoDragonMaster1085

Report
Homework 5 Chapter 16 1. If you are planning to ship 10 million units and offer a 1 year warranty what is more important, reliability or availability? Reliability is important because the unit should last more than a year and ideally you would not want to have to use the warranty unless there is a one off issue with the product. If the unit that is being shipped is intended to be replaced each year, then availability would be more important because you will have a higher turn around time on the product and greater demand. 3. When identifying architecture alternatives and trying to make a selection should RMA numbers be calculated? Yes, you should calculate RMA numbers when identifying and making a selection on architecture alternatives. This is important for comparing options to make sure you have the most reliable system that is available and can be maintained properly. 4. When working with new technologies with little history what can you do to calculate RMA numbers? You can work backwards with the numbers you aim to get and calculate from them. You can also use FRACAS to get the data to perform the RMA analyses after the system is trialed for a certain period of time. Chapter 17 3. What is the impact of failure in a car if the engine, a tire, the steering, headlight, or suspension fails at high and low speed? Use an IOF table. I am not sure I completely understand the IOF table based off the chapter in the book. I did my best to try to understand the consequences vs possibility of failure. Low Speed: Alternatives Failure Types High IOF Med IOF Low IOF Engine* 6 4 2 Tire 3 3 Steering** 5 3 2 Headlight^ 3 2 1 Suspension 6 5 1 High Speed: Alternatives Failure Types High IOF Med IOF Low IOF Engine* 8 5 3 Tire 5 5 Steering** 8 5 3 Headlight^ 4 3 1 Suspension 8 5 3
*Engine: catch on fire vs stalls. **Steering: loss of power steering vs no steering capability. ^Headlight: day/night. ^^Suspension: shocks/airbag failure vs axle failure Chapter 18 None Chapter 19 - 1. Identify unsafe events associated with your automobile. State how many failures you will accept before any unsafe event surfaces. Create a fault tree and identify the cut sets. Chapter 20 4. What are the fault tolerant elements in your automobile? What are the single points of failure in your automobile? Fault tolerant elements: emergency brake lever if brakes fail, physical key to get in car if fob doesn’t work, spare tire if you get a flat, alternator to charge battery, handheld tire pressure gauge if the sensors go bad. Single point failures: spark plugs, ignition, transmission, battery, fuel pump, steering, burned out lights.
7. Identify systems where checklists can increase the level of fault tolerance. Checking all the components of an HVAC system (i.e. filters, vents, motors, fans, pumps, sensors) Restrooms – checking stock and functionality of components (i.e. paper products, soap; functioning toilets, flush sensors, hand dryers) Vehicle inspection (every 5k miles, checking certain components at 25k, 50k, 75k, 100k miles) Chapter 21 None Chapter 22 5. How do security analysis techniques (threat assessment and penetration) compare to Impact or Failure? Threat assessments and penetration analysis are similar techniques to impact of failure because all three techniques use level criteria to analyze the scenarios. The lower number on each chart represents the highest threat. For your project update the following previous work: 1. Project charter 2. Stakeholder list 3. Divergent stakeholder needs 4. Stakeholder key requirements 5. Context diagram 6. Concept diagram 7. Functional block diagram 8. Functional sequence diagram 9. Operational threads 10. Human Factors considerations 11. Flow charts 12. DFD context diagram, Level 0 and Level 1 13. Characterization of your system functions 14. Architecture allocation 15. HIPO diagrams 16. State diagram 17. System external interfaces and key internal interfaces For your project address the following new elements: 1. Reliability Maintainability Availability 2. Impact of failure 3. FMEA 4. Fault Tree Analysis 5. Fault tolerance 6. Safety, use OpenFTA.exe if appropriate
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
7. Security, use OpenFTA.exe if appropriate Project Name: Solar Traffic Control on Airport Apron Project Charter: The purpose of this project is to develop a solar powered traffic control system on the inner service road of the airport apron to ensure safety for personnel and vehicle traffic and contribute to the overall LEAD goals for the airport. Key Requirements: Timing of lights: o To allow buses to make it fully through the overhang o To ensure buses are not sitting at red lights for extended periods of time Energy Efficiency: o Solar panels to provide power to the traffic light system Stakeholders: Direct Users o American Airlines – Bus Drivers o Airline Employees o Airport Maintenance Indirect Users o Federal Aviation Administration o Airport Sustainability Group o Airport Operations Needs: o American Airlines Buses need to be able to use the inner service road to avoid delays due to planes Buses do not fit under overhangs with two-way traffic o Airline Employees Safety plan for crossing inner service road o Airport Maintenance Accessibility to equipment for servicing in areas that minimize road closures
Human Factor Considerations: Vision/Display o Traffic Light o Digital Walk Sign o Stop Sign o Crosswalk Touch/Tactile o Pedestrian Button Response Time o Timing of light loop o Timing of walk loop
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