Skip to main content

Categories

How

The Incident Categories feature allows organizations to Getclassify and organize different types of incidents, such as security events, parking violations, or maintenance requests. Its primary purpose is to Categorizehelp toadministrators Createstandardize orreporting Editand dispatching by defining a structured hierarchy of categories and sub-categories. This article is intended for OPS-COM administrators.

Setup and Configuration


This


feature
Clickis managed entirely within the core OPS-COM administrative portal. No configuration is required on the mobile handheld devices, as they will automatically inherit the category lists during their regular synchronization.

Admin Side: Hover over Admin Options, click Incidents, and Categories.


image.png

The Edit Categories and Sub Categories main page will display. To edit Category, select the desired category from the listed items and click the pencil icon to edit.


image.png

 The page will refresh and you will be able to edit your Incident Category. Change the category name and/or details as desired andthen click "Save Incident Category".


image.png


To add a new Incident Category, return to the Edit Categories and Sub Categories. main page, and click "Add New Category" located at the bottom of the page.


image.png


The pageThis will refresh.  Fill out the details for your new Category Name, select whether it's  "In-House", enter the GIS number, and select if you'd like this category included in Reports. Click "Save Incident Category".


image.png


To check a category for Sub-Categories, return toopen the Edit Categories and Sub Categories main page.

Select

Using onethis Feature

Administrators can use this interface to build a custom list of incident types, create granular sub-categories, and define operational rules such as checklist requirements.

Adding a New Category

  1. Scroll to the bottom of the categoriesEdit byCategories clickingand onSub Categories main page.

  2. Click SubAdd New Category.


  3. Enter a descriptive name in the Category Name text field.

  4. image.pngEnable the In-House checkbox if this incident type is handled strictly internally.


  5. Enter a
    GIS

    Thenumber pageif willapplicable refresh,for spatial tracking and youmapping willintegration.

    have
  6. Enable the option to include this category in system reports, if desired.

  7. Click Save Incident Category to finalize and add the new category to the system.

Editing an Existing Category

  1. Locate the specific category in the listed items on the main page.

  2. Click the pencil icon next to the category to open the edit screen.

  3. Update the category name or specific configuration details as needed.

  4. Click Save Incident Category to apply your changes to the database.

Managing Sub-Categories

Sub-categories allow you to break down broad incidents into highly specific events.

  1. Click Sub next to an existing category on the main list to view its associated sub-categories.

  2. Enter a sub-category.

    new


    name

    image.png

    in


    the

    Toprovided text field to add a new sub-category,category.

    enter
  3. Click Required under the namechecklist column if a formal checklist must be completed by the officer when this specific sub-category is selected in the field.

  4. Click Include if you want forthis yourspecific sub-category. Enable the functions you wish to have in this subcategory.

    • If a Checklist is required, click "Required".
    • If it'scategory to be Includedvisible in Reports,statistical click "Include".reports.

    • Once you have finished, click

      Click "Save SubCategory"SubCategory. to add the new sub-category to the parent group.


Best Practices and Considerations

  • Standardize your naming conventions: Organizations should establish a clear and consistent naming convention for all categories and sub-categories. This prevents duplicate entries and ensures dispatchers and field officers can quickly select the correct option during an active, high-stress incident.

  • Utilize checklists for complex incidents: Enable the checklist requirement for sub-categories that involve multi-step procedures or critical safety protocols. This ensures field officers follow standard operating procedures when responding to specific incident types, reducing organizational liability.