Drebin Rescuing Firefighters in Distress FPR

1. Drebin Rescuing Firefighters in Distress FPR Team Ganz: Jonathan Bruso Michael Carney Daniel Fortin James Schafer

2. Outline • Background Motivation • System Requirements • Video • Users • System Components • Drebin System Installer • Tracking Software • Incident Commander Interface • Demo

3. Background and Motivation: Firefighters lives are endangered when going into burning buildings Many firefighter have recently perished after becoming lost or unconscious in a burning building Worcester, MA 1999 (six killed) Bronx, NY 2006 (one killed) Charleston, SC 2007 (nine killed) A system that can track firefighters in a building could aid in tracking and rescuing firefighters in distress

4. System Requirements: Dynamically display firefighters position on a visual blueprint of the building Allow for the toggling of the path for each firefighter Critical System, must be able to detect and recover from error quickly User Friendly

5. VIDEO DEMO!!!!!

6. Users • Firefighter • Carries RFID Reader and PDA • System Installers • Creating building blueprint using Drebin System Installer • Responsible for placement of tags and system calibration • Require average computer skills • Incident Commanders • Exposed to Drebin Visual Display • Features automated and require little computer knowledge

7. Our Design (1 reader and Multiple Tags): Tracking Done Using Active RFID Technology

8. Overall Design • Total System Software: 14,696 Lines of Code • Drebin System Installer • Tracking Software • Incident Commander Interface

9. Overall Design • Drebin System Installer : 3,793 Lines of Code • Tracking Software • Incident Commander Interface

10. Drebin System Installer Features Used to design the floor layout of a building Wall Creation Blueprint generation Save/load Functionality Tags placed on blueprint System calibrated for individual environments Room and Hallway Identification

11. Drebin System Installer Evolution • Current • CDR

12. Main Software Features: • Blueprint Analysis • Search for tags located: • Inside rooms • Inside hallways • Doorway tags • Room, Doorway, Hallway Connection • Find triangular orientation of tags • Required for trilateration

13. Overall Design • Drebin System Installer • Tracking Software : 6,610 Lines of Code • Incident Commander Interface

14. Tracking Software and Algorithms: Current status • Goal: Hallway and Room Tracking / Identification • Uses blueprint and tag layout created with Drebin System Installer • Signal Strength to Distance • Alternative: Trilateration • Signal Strength to Distance through walls • High Accuracy Required for Distance Computation • Zone Analysis

15. Current Zone Algorithm • Two Tracking Modes • Both use signal strength to distance conversion • Threshold for within 10 feet of each tag • Signal strength to distance conversion within 10-35 ft • Both use created Blueprint • Hallway Tags • Room Tags • Transitional Tags

16. Hallway • Tags Placement: • Every 30 feet down hallways • Region Between Hallway Tags calculated • Uses Signal Strength to Distance conversion

17. Room • Rooms in Blueprints are zones • Tags Placement: • Middle of room • Within 5 feet of each doorway inside room • Transition detection determined by signal strength (10 feet threshold ) • Entrance through doorway • Entrance from Hallways

18. Tracking Software • Drebin System Installer • Tracking Software • Incident Commander Interface : 3,239 Lines of Code

19. Incident Commander Interface • Created after CDR • Uses Zone Analysis Data from Tracking Algorithm to display current position on Blueprint created using Drebin System Installer

20. Main Software Features: • Wireless Communication • Bluetooth connects to one PDA / Laptop • Data gathered and sent via WIFI to second Laptop • Second Laptop executes Tracking Software

21. Path Display: • 745 Lines of Code • Path Construction and Replay • Traversed route calculated based of zones • Path save / load functionality • Replay • Toggle to specific point in time • Animate

22. Path Animation

23. Final Demo: • Incident Commander Interface located on projector • Group member walks with Laptop / Reader throughout building • Reader Zone displayed on Incident Commander Interface • Path Animation

24. Engineering techniques and tools Microsoft Visual Studio 2008 to design Drebin system to design Blueprint Designer C# programming Microsoft SQL Server Microsoft Office Suite for engineering documents and data analysis MATLAB

25. Application of courses Databases/Programming Designing tools with object oriented programming Database design and management C# learned outside of class Computer Systems Lab I/II Serial interfaced communication with RFID Reader Mathematics Statistical analysis Trilateration algorithm Software Engineering Reliability, requirement specification etc..

26. Team Roles, technical and administrative Jon Bruso Computer Systems Engineering Trilateration and distance calculation algorithm, Incident commander GUI, Blueprint Generator, Serial communication with reader, Incident Commander Interface, Hallway and Room Tracking Algorithm, Team Manager Mike Carney Computer Systems Engineering Trilateration Implementation, Room Zone Analysis, Room Display Dan Fortin Electrical Engineering Trilateration research, Statistical analysis, Testing Plan James Schafer Computer Systems Engineering Logarithmic model experimentation, Trilateration algorithm testing, Documents coordinator, Path Animation, Wireless Communication, Marcus Blueprint Creation

27. Outside sources and references • M220 RFID Reader Users Manual • Used to design serial interface for reader • Indoor Positioning via Three Different RF Technologies • Algorithms for signal strength to distance conversion • RADAR: An In-Building RFbased Tracking • From research.microsoft.com • Algorithms for signal strength to distance conversion