--- title: Report an OT incident description: Create an Operational Technology \(OT\) incident record to report a deviation from an expected standard of operation. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/operational-technology/operational-technology-incident-management/report-ot-incident.html release: australia product: Operational Technology Incident Management classification: operational-technology-incident-management topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Use, Operational Technology Incident Management, Operational Technology] --- # Report an OT incident 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 ## About this task For a walkthrough of how to report an OT incident, watch this video.\[Omitted video\] Description: Reporting an OT incident in the Industrial Workspace ## Procedure 1. Navigate to the **Industrial Workspace**. 2. Select the **List** \[Omitted image "icon-list.png"\] icon. 3. Under the OT Incidents list module, select one of the following available lists. - Assigned to me - Belong to my sites - All 4. Select **New**. 5. On the form, fill in the following the fields as needed. If you selected an OT 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 may have configured the OT incident form and its fields to adhere to your incident management process. The following table describes the typical OT incident form fields.
| 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. |