1. System Design Review Smart Walker

2. Project Description Project Background Problem Statement Scope Deliverables

3. Work Breakdown

4. Navigation

5. Fall Detection

6. Monitoring User

7. Collect Vitals

8. Room Layout

9. Customer Needs P13041 Customer Needs Customer Need #ImportanceDescriptionComments/Status CN11Functionally unobstrusive to the user CN21Functionally autonomous but independent of locating the user (avoid obstacles) CN31Locate user when in trouble using microphone array independent of autonomy CN41Support user's weight CN51Collect heart rate CN61Collect temperature CN71Collect weight fluctuation of the patient Sensor under seat (not full weight accounted for when sitting) CN81Feedback to a local hub be wireless CN91Measure tendencies of how much user relies on walker for stability (fall "saves", distance traveled, velocity,accel) CN101Meet budget CN111Must meet battery life requirements CN121Allow for ability for live feed data during autonomous navigation CN131Monitoring systems need to not be visible to the user (aesthetically pleasing) CN141Needs to be programmable and have a user interface (for doctor)max/min vitals CN151Detection of the user falling down CN162Collect Body Fat (BMI) Fluctuation CN173Detect smoke in the environment CN183Capable of stability control CN193Alert user if obstacle in path of motion Revision #3 Importance: Sample scale (1=must have, 2=nice to have, 3=preference only), or see Ulrich exhibit 4-8.

10. Specifications Spec. #ImportanceSourceFunction Specification (metric) Unit of Measure Marginal Value Ideal Value Comments/Status S1 CN1 Noise should not exceedDecibels S2 CN1 Walker heightcm 96 S3 CN1 Walker widthcm 62 S4 CN1 Walker depthcm 70 S5 CN1 Walker weightkg2520Stock 8.2 S6 CN2 Time to Successfully Navigate to usermin605 S7 CN10 Meet Budgetdollars2,0008,000 S8 CN2 Use SLAMboolean 1 S9 CN2 Minimum distance to detect obstaclecm 10 S10 CN3 Minimum distance from user when locating with navigationcm S11 CN3 Audibly detect fall within a rangem S12 CN5 Detect heart rate within (Time)s Need to determine how many beats are required to detect S13 CN5 Detect heart rate periodicallys S14 CN6 Temperature accuracy°F S15 CN6 Distance to measure temperaturem S18 CN4 Weight capacitykg 91 S19 CN11 Battery life in passive modedays12 S20 CN11 Battery in active modeminutes 60 S21 CN8 Non-emergency updates to local hubhours 24 S22 CN8 Emergency update to local hubs 5 S23 CN8 Send all last recorded vitals to local hub with in (?sec) of entering emergency modes S24 CN6 Detect temp within (Time)s S25 CN7 Detect weight within (Time)s S26 CN16 Detect BMI within (Time)s S27 CN7 Weight Accuracykg

11. System Design Schematic

12. Software Flow Chart

13. Signal Processing

14. Concept Selection: Walker

15. CS: Obstacle detection

16. CS: Drive

17. Odometry

18. CS:

19. CS: User Weight

20. CS: Wireless Communication

21. CS: Heart Rate Monitoring

22. CS: BMI

23. CS: Temperature

24. Project Plan

25. Risks IDRisk ItemEffectCause Likelihood Severity Importance Action to Minimize Risk Owner 1 Customer fails to deliver promised algorithms Walker will not function seamlessly. Must develop additional testing procedures to prove sub systems work. Will take significant time to prove sub systems 212 Reduce: Under stand what Algorithms are expect to be put in place early 2 Battery is too small to meet specs Fail to meet, S20&21 (battery life) Motor takes more power than predicted, overall weight is heavier, computer draw is high, wifi draw is high 224 Prevent: Use a battery that is overkill and can later be sized down. 3 Unable to detect heart rate when walking via camera Fail to meet CN5 & S13 Currently available technology is not able to work without stationary person. 224 Transfer: Have customer understand that we will put camera in place for use but it is not our job to insure it works in motion 4 Programmin g will not be begun in time A working model will be delayed. Won't meet delivery date 224 Reduce: Ensure that other deliverables are met on schedule 5 Microcontrol ler is not sufficient We essentially have to start from scratch Insufficient knowledge of how to select a microcontroller to meet our needs 133 Reduce: Attend "Which Micro" lecture on Friday 12/21/12 Prevent: Over- compensate computing needs.

26. Risks Con’t 6 Parts that are spec'd will be unavailable Parts with different spec's will delay development of PCB or not be compatible with PCB Rare/ extremely specialized parts 236 Reduce: Spec common parts, Check to see if in stock before adding to BOM, Order Early (week 10) Team 7 Unable to develop a BMI technology for walker use Walker will not be able to detect BMI Under estimating the complexity of the BMI handheld unit 313 Accept: We will not have BMI on the walker James 8 Unable to develop a temperature monitoring technology for walker use Walker will not be able to detect temperature Under estimating the complexity of the Temp Gun 224 Reduce: Look into temp gun tech early and find another solution if not possible Rika 9 A failure during testing causes destruction of another subsystem Walker will be broken, Will have to be rebuilt, could fail to have deliverable in May Poor designing133 Reduce: Design testing procedures so that possible destructive testing is last. Team 10 PCB is not designed or fabricated in time Electronics and wiring of all sensors will be set back. Programming will also be delayed. Poor time management or unexpected issues with fabrication/board itself 236 Reduce: Design carefully in order to prevent any extra emf signals or other common PCB issues. Also, design early and possibly have the design checked by peers/mentors. EE's