---
sourceDocument: Xanadu Operational Technology Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/operational-technology

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Operational Technology Management

ft:clusterId :

    - optm

bundleId :

    - optm

workflow :

    - Technology


---

# Report an incident

# Report an incident {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create an Operational Technology (OT) incident record to report a deviation from an expected standard of operation.

## Before you begin

Role required: sn_ot_incident_write

## Procedure

1. Navigate to AllIndustrial Workspace.
2. Select an device record or an equipment model entity record.  
   Note:  
   You can also raise an OT incident on the OT Incidents list module.
3. Select the OT Incidents tab.
4. Select New.
5. On the form, fill in the fields.  
   If you selected an device record, the Site and OT device fields are automatically filled in. If you selected an equipment model entity record, the Site and Equipment model entity fields are automatically filled in. If the OT incident is raised from the OT Incidents list module, then none of these fields are automatically filled in.  
   Note:  
   Your organization has configured the incident form and its fields to adhere to its incident management process. The following table describes the typical OT incident form fields.
   {#report-ot-incident__table_jbh_xzy_fwb__entry__2}

   | Field | Description |
   |-|-|
   | Short description | Brief description of the incident. |
   | Description | Detailed explanation of the incident. |
   | Number | Unique system-generated incident number that is prefixed with Operational Technology Incident (OTINC). |
   | Caller | User who contacted the OT engineer with an issue. |
   | Impact | Measure of the effect that an incident has on industrial processes. |
   | Urgency | Measure of how long the resolution can be delayed until an incident has a significant business impact. |
   | State | State of the OT incident. The state moves and tracks incidents through several stages of resolution. |
   | Category | Type of issue. After selecting the category, select the subcategory if applicable. |
   | Subcategory | Type of issue within the selected category. |
   | Watch list | Users who receive notifications about this incident when comments are added. |
   | Work notes list | Users who receive notifications about this incident when work notes are added. |
   | Site | Site where the issue happened. |
   | OT device | Affected OT device at the site. |
   | Equipment model entity | Affected equipment model equipment model entity at the site. |
   | Business impact | More information about the business impact of the OT incident. |
   | Assignment group | Assigned group that works on the incident. The assignment group can be any group with the type OT. |
   | Assigned to | User who works on this incident. If the assignment group changes, the Assigned to field is cleared. You can only select the users that are included in the Assignment group field and have the sn_ot_incident_write role. If the Assignment group field is empty, then any site user with the sn_ot_incident_write role can be selected. |
   | Parent incident | Unique number of the parent incident for this incident record. |
   | Additional comments | More information about the issue as needed. All users that can view incidents can see the additional comments. |
   | Work notes | Information about how to resolve the incident or the steps taken to resolve it, if applicable. |
   [Table 1. Operational Technology incident form]

   {#report-ot-incident__table_jbh_xzy_fwb}
6. Select Save.

## Result

Now, the assignment group and assignee are aware that there's an OT incident that needs to be addressed.

*[\>]: and then