2. SCID Master Control 4/22/2014SCID Design Details Presentation1 Handheld Device (Walkie) Master Control (Managie) Data Protocol (Talkie)

3. Outline Goals Major Functional Components Hardware Software Interfaces Database Graphical User Interface Algorithms Risks 4/22/2014SCID Design Details Presentation2

4. Goals Provide an efficient method for agency dispatchers and supervisors to view event, agency, personnel, equipment and device information Allow agency dispatchers and supervisors to send orders and messages to agents in the field in a timely and efficient manner Relay gathered disaster information to agency headquarters and databases located outside the disaster zone 4/22/2014SCID Design Details Presentation3

5. Major Functional Components 4/22/2014SCID Design Details Presentation4

6. Major Functional Components 4/22/2014SCID Design Details Presentation5

7. Hardware 4/22/2014SCID Design Details Presentation6

8. Software 4/22/2014SCID Design Details Presentation7

9. Software – Interfaces Interface with data protocol to receive messages from and send orders to hand- held devices Interface with Internet and agency databases to provide information about the disaster and relief efforts to agencies and organizations outside disaster zone 4/22/2014SCID Design Details Presentation8

10. Software – Database Schema 4/22/2014SCID Design Details Presentation9

11. Software – Entity Relationship 4/22/2014SCID Design Details Presentation10

12. Software – Database Access Control Matrix 4/22/2014SCID Design Details Presentation11 Add New User Add New Moderator Send Alerts/Messages Search/Add/Edit Data Remove Data Compare Data View Data Administrator√√√√√√√ Moderator√X√√√√√ UserXX√√X√√

13. Software - GUI 4/22/2014SCID Design Details Presentation12

14. Software - GUI 4/22/2014SCID Design Details Presentation13

15. GUI - Login 4/22/2014SCID Design Details Presentation14

16. GUI – Administrator Main Screen 4/22/2014SCID Design Details Presentation15

17. GUI – Data View 4/22/2014SCID Design Details Presentation16

18. GUI – Map Display 4/22/2014SCID Design Details Presentation17

19. GUI – Add Data 4/22/2014SCID Design Details Presentation18

20. GUI – Add User 4/22/2014SCID Design Details Presentation19

21. GUI – Send Message 4/22/2014SCID Design Details Presentation20

22. GUI - Alert 4/22/2014SCID Design Details Presentation21

23. Software - Algorithms 4/22/2014SCID Design Details Presentation22

24. Risks Consumer Risks C1 – Single Point of Failure C2 – Failure to Adopt System C3 – Difficult to Use C4 – Device Interchanging Technical Risks T1 – Duplicate Events T2 – Transmission Failure to Outside Disaster Zone T3 – Corrupted Data T4 – Security 4/22/2014SCID Design Details Presentation23

25. Technical Risk 1 – Duplicate Events Probability: 5 Impact: 2 Risk: Two or more alerts may be sent to master control in regards to the same event, causing dispatchers to issue field orders based on incorrect information. Mitigation: Allow users to describe the event in a message and to input coordinates with as much detail as possible to differentiate between events. Train agencies in the importance of using as much detail as possible in their event alerts. 4/22/2014SCID Design Details Presentation24

26. Technical Risk 2 – Transmission Failure to Outside Disaster Zone Probability: 2 Impact: 1 Risk: Transmission of data to agencies and organizations outside the relief zone may be interrupted, lose data, or fail. Mitigation: Use transmission control protocol to ensure receipt of message and resend if not received. 4/22/2014SCID Design Details Presentation25

27. Technical Risk 3 – Corrupted Data Probability: 3 Impact: 4 Risk: Data may be lost or corrupted when it arrives at master control and could disrupt the system if not handled properly. Mitigation: Ensure data is intact and not corrupted before attempting to enter it into the database. Request resending of data if any parts are lost or corrupted. 4/22/2014SCID Design Details Presentation26

28. Technical Risk 4 - Security Probability: 3 Impact: 4 Risk: Master control will store information collected by users in the field, some of which may be sensitive or confidential. Mitigation: Utilize data encryption. Create a secure system that requires users to login to access data. Prevent moderators and users from accessing sensitive information from other agencies besides their own. 4/22/2014SCID Design Details Presentation27

29. Customer Risk 1 – Single Point of Failure Probability: 2 Impact: 5 Risk: Instituting a centralized data storage and control system creates the risk of the system becoming a single point of failure for the SCIDs project should the system fail. Mitigation: Create back-up databases and distribute the data and control structures across the devices for added redundancy. 4/22/2014SCID Design Details Presentation28

30. Customer Risk 2 – Failure to Adopt System Probability: 5 Impact: 5 Risk: Failing to adopt the SCID system leaves the current problems facing disaster relief communications unsolved. Mitigation: Create a functional prototype of the SCID system that relief agencies can use during training to emphasize the benefits of SCIDs over the current communications system. 4/22/2014SCID Design Details Presentation29

31. Customer Risk 3 – Difficult to Use Probability: 3 Impact: 3 Risk: The development of the system may result in a product that is difficult to use and unappealing to target agencies and organizations. Mitigation: Develop the user interface to be simple and easy to use and understand. Train agencies in the use of the system. 4/22/2014SCID Design Details Presentation30

32. Customer Risk 4 – Device Interchanging Probability: 5 Impact: 2 Risk: Relief workers in the field may accidentally or intentionally exchange devices, causing targeted orders or messages to reach the wrong personnel. Mitigation: Create different IDs for devices and personnel to distinguish between the device and the relief worker utilizing it. Allow dispatchers to send orders and messages agency-wide. Train the agencies to emphasize the importance of keeping the device they were assigned. 4/22/2014SCID Design Details Presentation31

33. References 3/27/201432 FEMA. Disaster Emergency Communications Division. FEMA, 17 Aug 2012. Web. 10 Feb 2014,. FEMA. Emergency Support Function Annexes: Introduction. FEMA, 2008. PDF file. FEMA. NEMIS-MT User Manual. FEMA, 2014. PDF file. Gay, Ronald J. An Analysis of Inter-Agency Radio Communications with Emergency Responders. Florida Department of Law Enforcement, n.d. PDF file. National Task Force on Interoperability. Why Can’t we Talk? Working Together To Bridge the Communications Gap To Save Lives. NTFI, 2005. PDF file. FEMA. Disaster Emergency Communications Division. FEMA, 17 Aug 2012. Web. 10 Feb 2014,. FEMA. Emergency Support Function Annexes: Introduction. FEMA, 2008. PDF file. FEMA. NEMIS-MT User Manual. FEMA, 2014. PDF file. Gay, Ronald J. An Analysis of Inter-Agency Radio Communications with Emergency Responders. Florida Department of Law Enforcement, n.d. PDF file. National Task Force on Interoperability. Why Can’t we Talk? Working Together To Bridge the Communications Gap To Save Lives. NTFI, 2005. PDF file.