1 / 87

Seneca College’s Emergency Response and Tickets Presentation

TicketsCAD is a computer-aided dispatch software designed for small emergency response teams. This presentation provides a step-by-step guide for installation, configuration, and user management.

awortham
Download Presentation

Seneca College’s Emergency Response and Tickets Presentation

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. Seneca College’s Emergency Response and Tickets Presentation By: Arzoo Zaheer, Technical Writer

  2. OPEN ISES TEAM

  3. Open ISES Team • Diverse group of volunteers • Mostly American, 1 British , and 1 Canadian (Me) • Creator and Lead Developer • Arnie Shore • Software Developer • Arnie Shore • Andy Harvey • Software Engineer • Kevin Bednar • Senior Technical Writer • Alan Jump • Junior Technical Writer • ArzooZaheer

  4. TICKETS

  5. Purpose • Computer-Aided-Dispatch Software that can be used by any emergency service community located in rural or economically deprived areas.

  6. Who Uses Tickets? • Small Emergency Response teams • Police • Fire department • Emergency medical services (ambulance services) • Tow truck companies • Volunteer teams supporting public safety • 500 downloads per month

  7. INSTALLATION

  8. Installation • Uses the AMP stack (includes apache, MySQL, and php). • Tested and deployed on computers running windows XP, SP2 or later, and various distributions of GNU/Linux. • Complete installation requires less than 100MB. • Should work with all browsers. Still needs to be tested! • Works best with Firefox browser. • To download and install: • Visit http://www.ticketscad.org • Select T2Go_Install_2.20G.exe • Note: Upon successful installation, Tickets will open in Internet Explorer. Copy the URL from IE into Firefox. Make sure IE stays open while you are using Firefox.

  9. CONFIGURATION See pages 11-35 of the TicketsCAD user guide. http://www.ticketscad.org/downloads/Using%20Tickets_12_08_2011.pdf

  10. Config Home Screen

  11. Config Options • Contacts • Edit Settings • Add User • Region • Region Type • Reset Regions • List and Cleanse Allocations • Delete Closed Tickets • Edit Day Colors • Edit Night Colors • Set Default Map • Set GMaps API key • Dumb DB to screen

  12. ConfigOptions • Reset Database • Optimize Database • Edit My Profile • Test: APRS, Instamapper, SMTP Mail, Google, Lattitude, LocateA, Gtrack, Open GTS, Internal Tracker • Add/Edit Notifies • Incident Numbers • Incident types • Units types • Units status   • Facility Status • Facility Types • Captions

  13. Config Options • Signals • Hints • Places • Map Markup • MM Categories • Modules • Modules Configuration • Delete Tickets Module • Add Tickets Module • Constituents • Alarm audio test • ICS 213 • Backup System

  14. Editing Settings

  15. Display Location • Select ConfigEdit Settings. • Edit the following fields to display your geographical location • def area code • def city • def state

  16. Delta Mins Option • The UTC offset is the difference in hours and minutes from the Coordinated Universal Time (UTC). • For example, if you are in the Central Time Zone and you are observing the Daylight Savings Time, the UTC offset is 5 hours. 5*60=300 min. Add 300 to the delta mins field. • Add minutes if west of UTC and subtract if east of UTC. • Time zones and UTC offsets for Canada are found at http://www.timetemperature.com/tzca/time_zone_codes_canada.shtml • If your delta mins setting is correct, then the Run Start time under New will be accurate.

  17. API Key • Not required if you are using Tickets as a stand-alone package on a single computer, not using its mapping functions, or not performing limited reverse lookups. • Google Maps API Key • Provides updated Google Maps in Tickets.   • Assists in the operation of the mapping functions. • Required if you are using a multi-user setup or hosted server. • Generate a key by visiting http://code.google.com/apis/maps/signup.html • Enter this key to thegmapsapi key textbox.

  18. API Key • White Pages API Key • Used in White pages lookup. • The default key that is provided with Tickets does not work if the frequency of White pages lookup is really high. • The limit of lookups is two lookups per second for a given API key. • Generate a key by visiting http://developer.whitepages.com/page • Enter this key to the wp key textbox of Edit Settings.

  19. Setting Default Map

  20. Default Map • Select Set Default Map. • Enter city and province. • Select the lookup tool to populate the rest of the fields and display the location on the map.

  21. Editing User Data

  22. User Data • Select a user from the Users-click to edit pane.

  23. User Data • Enter the desired information such as User ID, Passwords, Level, Region, and Unit.

  24. Adding Users

  25. Adding Users • Select ConfigAdd user. • Enter the required information.

  26. Levels • There are eight levels that can be assigned to the users. • Super • User has complete control of the system including the ability to delete closed tickets from the database, configure the system, and re-initialize the database (i.e. delete all the data). • Admin • User has Super permissions. • Not to be used for day to day operations due to potential of making a mistake that could severely damage the database. • User cannot perform low-level configuration options and database maintenance. • Used by duty supervisors.

  27. Levels • Operator • Assigned to dispatchers. • User can enter or close tickets, change unit and facility status, add facility and status types, but can’t add or remove units. • Make sure to assign a unit to dispatchers who will be logging into from a field unit. • Members • User can view all the information screen. • Unlike the guest account, their logins are monitored and logged. • User can receive email from the system.

  28. Levels • Useful for emergency managers and organizations that monitor activities but don’t have a need for direct dispatch. • Guest • User can view all the information screens but can’t use the system. • Statistics • Used specifically for monitoring system statistics.

  29. Levels • Units • Users can view ticket info on the Situation screen and view all other information screen. • Users can update their own status, enter notes under Action and Patient notes, trigger dispatch actions for additional units on their tickets, access the Call Board bar and change the call progression status.

  30. Critical Config Options

  31. Dump DB to screen • A debugging tool available only to the Super user. • Used in case of significant operating issues. • Allows Super user to dumb contents of the database, and save it as a file that can be sent to the Tickets development team for analysis.

  32. Reset Database • Extremely dangerous! • Available only to the Super user. • Resets Tickets database to a fresh-install state by erasing all stored incident, unit, facility, status, incident and signal data.

  33. Optimize Database • Available only to the Super user. • Examines database for integrity and optimizes it. • Yearly use is recommended. • Use after deleting large numbers of old and closed incidents.

  34. Regions

  35. Region • Region is a functional area within which a relevant department or organization (such as police and fire) is located. • This option is used to: • Assign a specific user to a specific region, which allows the user to dispatch and manage only those units and incidents that are assigned to that region. • Assign supervisors to specific regions, which allows them to view multiple regions for situational awareness. This is helpful especially during a disaster.

  36. Region • Select Region Add new Region entry. • Enter region name and demographical (city, area code, and state/province) and geographical (longitude and latitude) information.

  37. Region • Here is an example of a region table.

  38. Region Categories • Tickets has the following four predefined Region categories: • Category 1: EMS • Regions that are implementing Emergency Management Systems, such as Tickets. • Category 2: Security • Regions that have police stations. • Category 3: Fire • Regions that have Fire Stations. • Category 4: General • Regions that do not implement regional operations.

  39. Region Type • Select Region TypeAdd new Region type entry. • Enter name and description.

  40. Resetting Regions • Select Reset Regions to reset regions to default. • Used to erase all of the newly created region types.

  41. Listing and Cleansing Region Allocations • Diagnostic and repair tool. • Used to delete: • Resources (such as users, units, facilities and tickets) or incidents that are not assigned as a valid Region • Any incidences of double allocations • Accessed only by the Super-Administrator.

  42. Incidents

  43. Incident • Provides information required for: • Proper deployment. • Upgrading the severity level of a situation. • Sending appropriate resources for each incidence type. • Generating reports (done by emergency managers).

  44. Incident Type • Select IncidentTypeAdd new In types entry. • Enter Type (code like ABD for Abdominal pain, Medical Emergency), description, protocol, severity, and other desired information.

  45. Incident Type • Here is an example of a in_types table.

  46. Facilities

  47. Facility Status • Select Facility StatusAdd new Fac status entry. • Enter name (status val), description, group, and other required information.

  48. Facility Type • Select Facility TypeAdd new Fac type entry. • Enter name and description, and select an icon.

  49. Facility Type • Here is an example of a fac_typestable.

  50. Units

More Related