Skip to main content

Locations - Sub Locations

Sub-locationsThe inSub OPSCOMLocations allowfeature allows administrators to define more granular areas within a main system location, primarily for detailed incident reporting. ThisIts featureprimary enhancespurpose is to enhance the precision of incident documentation by pinpointing specific spots within a larger location, providing richer context for investigations and analysis. This article is intended for OPS-COM administrators responsible for managing geographic data and incident configurations.

Setup and Configuration

This feature is an administrative tool used to establish specific areas within your predefined physical locations.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the location configuration menus and manage the geographic lists. Ensure your primary locations are already configured before adding sub-locations. Detailed instructions can be found on the Locations page.

Using this Feature

TheAdministrators Managecan Sub-Locationsuse pagethe providesfollowing ainstructions straightforwardto navigate the management interface to addseamlessly andadd, edit, or delete various sub-locations.

Accessing the Management Interface

  1. 1. Hover over System Configuration,Configuration, thenclick Manage Locations,Locations, and clickthen Manage Sub-Locations.

Adding Sub-Sub Locations

  1. Click the Add Sub-Location button.

  2. Enter the name of your new location.sub-location in the provided text field.

  3. The

    Enter a geographic location code in the GIS Number field isif optionalyour andorganization isutilizes used by clients who utilize a geographic location code (GIS maps).maps.

  4. Click the Save Changes button to create the new location.sub-location and refresh the list.

The ManageGIS Sub-LocationsNumber pagefield willis refreshstrictly optional and displayis aonly confirmationrequired messagefor indicatingclients thatwho theutilize Locationan hasexternal beengeographic updatedlocation (code system or added).mapping integration.

Editing Sub-Sub Locations

  1. Locate the Sub-Locationspecific sub-location you wish to modify in the active list.

  2. Click the Edit button next to it.the entry.

  3. Make yourthe necessary updates andto clickthe name or GIS number.

  4. Click the Save Changes. button to apply your updates.

Deleting Sub-Sub Locations

  1. Locate the eligible sub-location you wish to remove from the list.

  2. Click the Delete button next to the entry.

  3. Confirm the action to permanently remove the sub-location from the system.

A sub-location can only be deleted from the system if it is not associated with any existing recordsrecords. (e.g.,Administrators must first ensure that the sub-location is not actively referenced by incidents, violations, or other datasystem wheredata. thisReassigning records to another valid sub-location is referenced).

crucial
    to
  1. prevent data inconsistencies. If a sub-location is eligiblecurrently forin deletion, you will see a Delete button specific to that location 
  2. Clickuse, the Delete button and confirm. This action will permanentlynot removebe the location from the system.
available.

Best Practices &and Considerations

  • DetailAdd for Incident Reporting: Sub-locations are primarilydetail for incident reporting.reporting: UseLeverage themsub-locations to addprovide specific detail that goes beyond the general "Location"location. (e.g.,For example, within a main location like "Mulloy Library"Library," you might havecreate sub-locations for "Reading Room," "South Entrance," and "Loading Dock"). to pinpoint exactly where an incident occurred.

  • ClarityMaintain clarity in Naming:naming: Use clear and concise names for your sub-locationslocations. toDescriptive makenaming ensures incident reports are easily understandable.understandable for all administrators and enforcement officers reviewing the data.

  • Ensure accurate GIS Integration:integration: If your organization uses GIS data, ensure your GIS numbers for sub-locations are accurate and consistent with your mapping systems. Mismatched codes can cause mapping errors or data syncing issues.

  • DataVerify Integrity:data integrity before deletion: Always ensure that a sub-location is not actively referenced by any system records before attempting to delete it. Attempting to force the deletion of an active sub-location can cause critical data conflicts with past incident reports.

Back to top