{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":36733,"path":"operational-technology/operational-technology-incident-management/define-priority-lookup-rules.md","title":"Define a priority lookup rule for incidents","bundle":null,"doc_type":null,"release":"australia","body":"\n# Define a priority lookup rule for incidents\n\nDefine the impact and urgency of an Operational Technology incident to calculate its priority. You can then use the priority calculation to prioritize your work and to drive service level agreements \\(SLAs\\) in your organization.\n\n## Before you begin\n\nRole required: ot\\_incident\\_admin\n\n## Procedure\n\n1.  Navigate to **All** > **Industrial Workspace Admin** > **Operational Technology Incident Management** > **Priority Lookup Rules**.\n\n2.  Select **New**.\n\n3.  On the form, fill in the fields.\n\n    |Field|Description|\n    |-----|-----------|\n    |Impact|Measure of the effect of an incident on business processes.|\n    |Urgency|Measure how long the resolution can be delayed until an incident has a significant business impact.|\n    |Priority|Option that is based on the impact and urgency. The priority identifies how quickly the OT engineer should address the task.|\n    |Application|Scope of the rules. The scope defines whether the rules are available for all applications or for scoped applications.|\n    |Active|Option to define whether the rule is active or not.|\n    |Order|Order in which the rules appear in the priority lookup list. This field indicates which rule to execute first.|\n\n    **Note:**\n\n    The priority is calculated according to the sample data lookup rules in the following table.\n\n    |Impact|Urgency|Priority|\n    |------|-------|--------|\n    |1 - High|1 - High|1 - Critical|\n    |1 - High|2 - Medium|2 - High|\n    |1 - High|3 - Low|3 - Moderate|\n    |2 - Medium|1 - High|2 - High|\n    |2 - Medium|2 - Medium|3 - Moderate|\n    |2 - Medium|3 - Low|4 - Low|\n    |3 - Low|1 - High|3 - Moderate|\n    |3 - Low|2 - Medium|4 - Low|\n    |3 - Low|3 - Low|5 - Planning|\n\n    By default, the **Priority** field is read-only and must be set by selecting the **Impact** and **Urgency** values. To change how the priority is calculated, you can either alter the priority lookup rules or disable the **Priority is managed by Data Lookup - set as read-only** UI policy and create their own business logic.\n\n4.  Select **Submit**.\n\n\n**Parent Topic:**[Configuring Operational Technology Incident Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/operational-technology/operational-technology-incident-management/configuring-operational-technology-incident-mgt.md)\n\n"}}