1 / 32

SCID Master Control

SCID Master Control. Handheld Device ( Walkie ). Data Protocol (Talkie). Master Control ( Managie ). Outline. Goals Major Functional Components Hardware Software Interfaces Database Graphical User Interface Algorithms Risks. Goals.

zaza
Download Presentation

SCID Master Control

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SCID Master Control Handheld Device (Walkie) Data Protocol (Talkie) Master Control (Managie) SCID Design Details Presentation

  2. Outline Goals Major Functional Components Hardware Software Interfaces Database Graphical User Interface Algorithms Risks SCID Design Details Presentation

  3. 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 SCID Design Details Presentation

  4. Major Functional Components SCID Design Details Presentation

  5. Major Functional Components SCID Design Details Presentation

  6. Hardware SCID Design Details Presentation

  7. Software SCID Design Details Presentation

  8. 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 SCID Design Details Presentation

  9. Software – Database Schema SCID Design Details Presentation

  10. Software – Entity Relationship SCID Design Details Presentation

  11. Software – Database Access Control Matrix SCID Design Details Presentation

  12. Software - GUI SCID Design Details Presentation

  13. Software - GUI SCID Design Details Presentation

  14. GUI - Login SCID Design Details Presentation

  15. GUI – Administrator Main Screen SCID Design Details Presentation

  16. GUI – Data View SCID Design Details Presentation

  17. GUI – Map Display SCID Design Details Presentation

  18. GUI – Add Data SCID Design Details Presentation

  19. GUI – Add User SCID Design Details Presentation

  20. GUI – Send Message SCID Design Details Presentation

  21. GUI - Alert SCID Design Details Presentation

  22. Software - Algorithms SCID Design Details Presentation

  23. 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 SCID Design Details Presentation

  24. 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. SCID Design Details Presentation

  25. 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. SCID Design Details Presentation

  26. 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. SCID Design Details Presentation

  27. 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. SCID Design Details Presentation

  28. 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. SCID Design Details Presentation

  29. 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. SCID Design Details Presentation

  30. 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. SCID Design Details Presentation

  31. 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. SCID Design Details Presentation

  32. References FEMA. Disaster Emergency Communications Division. FEMA, 17 Aug 2012. Web. 10 Feb 2014, <http://www.fema.gov/disaster-emergency-communications-division/ >. 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.

More Related