---
sourceDocument: Australia Operational Technology Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/operational-technology

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Operational Technology Management

ft:clusterId :

    - optm

bundleId :

    - optm

workflow :

    - Technology


---

# Basic OT Change Model playbook

# Basic OT Change Model playbook {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Basic OT Change Model playbook

The Basic Operational Technology (OT) Change Model playbook outlines the stages and tasks required to process an OT change request that does not require approvals.
This structured approach guides ServiceNow customers through capturing change details, planning, implementing, and closing OT changes efficiently and accurately.
Show full answer Show less  

## Initiate

In the Initiate stage, customers capture essential information about the requested change and assign responsibility. Key tasks include:

* **Describe the change:** Provide a brief and detailed description, specify the change category and site, and define watch and work notes notification lists.
* **Capture risk:** Set priority based on impact and urgency, assess the risk level, and evaluate the impact on industrial processes.
* **Assign the change:** Identify the user requesting the change, assign an OT-type group to manage it, and designate the specific user responsible. Note that changing the assignment group clears the assigned user field.

## Plan

This stage focuses on comprehensive preparation for the change, involving six key tasks:

* **Add a justification:** State the reason the change is necessary.
* **Add implementation plan:** Detail how the change will be executed.
* **Add risk and impact analysis:** Document any risks and impacts related to the change.
* **Add backout plan:** Outline steps to reverse the change if needed.
* **Add test plan:** Describe how to test the change after implementation.
* **Schedule the change:** Set planned start and end dates, optionally using the Scheduling Assistant to select available downtime slots automatically.

## Implement

During the Implement stage, customers perform the actual change on targeted OT devices. Upon completion, they mark the stage as complete, signaling the successful execution of the change.

## Close

After the change is successfully implemented, the Close stage allows customers to finalize the change record by specifying a close code and adding any relevant closing notes. This ensures clear documentation of the closure reason and additional context.  
Learn about the Basic Operational Technology (OT) Change Model playbook stages that an OT change without approvals must go through until it's completed.

## Initiate {#basic-ot-change-model__section_yvv_ygh_2xb}

The Initiate stage of an OT change request lets you capture the details of the requested change and assign the change as necessary. This stage has three tasks.{#basic-ot-change-model__table_yf4_ptm_2xb__entry__2}

| Field | Description |
|-|-|
| Short description | Brief description of the change. |
| Description | Details of the change. |
| Category | Type of change. |
| Site | Site where the change takes place. |
| Watch list | Users who receive notifications about this change when comments are added. |
| Work notes list | Users who receive notifications about this change when work notes are added. |
[Table 1. Describe the change]

{#basic-ot-change-model__table_yf4_ptm_2xb}{#basic-ot-change-model__table_ybq_t5m_2xb__entry__2}

| Field | Description |
|-|-|
| Priority | Impact and urgency to identify how quickly the change should be addressed. |
| Risk | Amount of risk that the change poses. |
| Impact | Measure of the effect that a change has on your industrial processes. |
[Table 2. Capture risk]

{#basic-ot-change-model__table_ybq_t5m_2xb}{#basic-ot-change-model__table_npn_55m_2xb__entry__2}

| Field | Description |
|-|-|
| Requested by | User who requests the change. |
| Assignment group | Assigned group that works on the change. The assignment group can be any group with the type OT. |
| Assigned to | User who works on this change. If the assignment group changes, the Assigned to field is cleared. |
[Table 3. Assign the change]

{#basic-ot-change-model__table_npn_55m_2xb}

## Plan {#basic-ot-change-model__section_fd3_zgh_2xb}

The Plan stage of an OT Change request lets you add a justification for the change, an implementation plan, a
risk and impact plan, a backout plan, a test plan, and a time to schedule the change. This stage has six tasks.
{#basic-ot-change-model__table_jpd_kxm_2xb__entry__2}

| Field | Description |
|-|-|
| Justification | Reason why the change must take place. |
[Table 4. Add a justification]

{#basic-ot-change-model__table_jpd_kxm_2xb} {#basic-ot-change-model__table_exq_kxm_2xb__entry__2}

| Field | Description |
|-|-|
| Implementation plan | Details of how to implement the requested change. |
[Table 5. Add implementation plan]

{#basic-ot-change-model__table_exq_kxm_2xb} {#basic-ot-change-model__table_cxg_lxm_2xb__entry__2}

| Field | Description |
|-|-|
| Risk and impact analysis | Details of any risk and impact factors that are related to this change. |
[Table 6. Add risk and impact analysis]

{#basic-ot-change-model__table_cxg_lxm_2xb} {#basic-ot-change-model__table_zlb_mxm_2xb__entry__2}

| Field | Description |
|-|-|
| Backout plan | Details of how to reverse the change in place if necessary. |
[Table 7. Add backout plan]

{#basic-ot-change-model__table_zlb_mxm_2xb} {#basic-ot-change-model__table_a3s_mxm_2xb__entry__2}

| Field | Description |
|-|-|
| Test plan | Details of how to test the implemented change. |
[Table 8. Add test plan]

{#basic-ot-change-model__table_a3s_mxm_2xb} {#basic-ot-change-model__table_edj_nxm_2xb__entry__2}

| Field | Description |
|-|-|
| Planned start date | Date that the change takes place. Note: You can also choose an available downtime slot on the calendar by selecting the Scheduling Assistant button to fill in the planned start date field automatically. |
| Planned end date | Date that the change ends. Note: You can also choose an available downtime slot on the calendar by selecting the Scheduling Assistant button to fill in the planned end date field automatically. |
[Table 9. Schedule the change]

{#basic-ot-change-model__table_edj_nxm_2xb}

## Implement {#basic-ot-change-model__section_g25_jhh_2xb}

The Implement stage of an OT change request provides the details of the following task. You can mark this stage as complete when it's finished.

Perform the change
:   Mark as complete when the change is performed on the targeted OT devices and completed.

## Close {#basic-ot-change-model__section_bqr_lhh_2xb}

The Close stage lets you close the change record after the change is completed.{#basic-ot-change-model__table_lft_lkn_2xb__entry__2}

| Field | Description |
|-|-|
| Close code | Reason that the change record was closed. |
| Close notes | Additional details about closing the change record. |
[Table 10. Close the change record]

{#basic-ot-change-model__table_lft_lkn_2xb}