Managing Incident Relations

The Managing Incident Relations in OPSCOMfeature allows administrators to define specific types of connections or relationships between individuals involved in an incidentincident, (e.g.,such "as a Witness," "Victim," "Suspect," "or Reporting Party").Party. ThisIts featureprimary purpose is crucial forto accurately documentingdocument complex incident scenarios, ensuringensure all parties are properly identified, and facilitatingfacilitate comprehensive investigations. This article is intended for OPS-COM administrators responsible for configuring incident reporting standards.

Setup and investigation.Configuration

This feature is a core administrative tool used to establish the drop-down options available when documenting individuals involved in an active incident.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the incident configuration menus and manage the list of relations.

Using this Feature

TheAdministrators Relationcan Administrationuse pagethe providesfollowing ainstructions straightforwardto navigate the management interface to seamlessly add andor edit various incident relation types.relations.

Accessing the Management Interface

1. 1. Hover over System Configuration,Configuration, click Incidents, then Incidents, and click Relations.

Adding Relations

1. Locate the empty text box provided at the bottom of the listlist.

   for adding a new relation.
2. Type in

   Enter the desired relationname namefor the connection (e.g., "Witness,"Witness "Victim,"or "Suspect,"Victim) "Reportinginto Party").the text field.

3. Choose a unique color for this type.specific relationship type to visually distinguish it within the system.

4. Click the Insert New button to add the new relation to the list.

Editing Relations

1. Locate the specific relation you wish to modify in the listlist.

   and
click

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

3. Make yourthe changesnecessary andupdates clickto the name or color.

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

---

Best Practices &and Considerations

• ComprehensiveEstablish Definitionscomprehensive definitions:: Define all relevant relationship types that might occur in your incident reportingreporting. toProviding ensurea complete list ensures accurate and completecomprehensive documentation.documentation of any complex scenario your officers might encounter.

• ClearUse Namingclear naming conventions:: Use concise and unambiguous names for relations to avoid confusionadministrative (e.g.,confusion. For instance, clearly establishing the difference between a "Victim" vs.and a "Complainant" ifguarantees theyfield representofficers differentselect rolesthe incorrect yourrole context).during documentation.

• StandardizationEnforce standardization:: Encourage consistent use of defined relations by all personnel involved in incident reportingreporting. toConsistent improveapplication drastically improves overarching data quality and long-term reporting consistency.reliability.

• DataVerify Integritydata integrity before deletion:: Always ensure that a relation is not actively linked to any incident parties before attempting to delete it,it. Attempting to preventforce the removal of an active relation can cause critical data inconsistencies.inconsistencies in historical incident reports.

• ReportingLeverage Valuerelations for reporting value:: Properly categorized relations are essential for generating accurate reportsreports. onThis structured data is highly valuable for analyzing incident demographics and auditing the distinct roles of individuals involved.involved across your property.