Using Operational Technology Change Management to optimize your production process

  • Release version: Washingtondc
  • Updated February 7, 2024
  • 2 minutes to read
    • Summarize
    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 Using Operational Technology Change Management to Optimize Your Production Process

    The Operational Technology Change Management application allows teams to collaboratively manage changes to operational technology (OT) devices and industrial equipment. Changes may encompass optimizations, process alterations, or vulnerability fixes, helping to streamline production processes while maintaining the integrity of OT systems.

    Show full answer Show less

    Key Features

    • Separate Management of Change Requests: Manage OT change requests independently from IT change requests, categorized by network type and site.
    • Change Request Examples: Initiatives can include fixing vulnerabilities, addressing equipment malfunctions, or approvals from production heads.
    • Network Type Assignment: When creating OT change requests, they are automatically assigned a Network Type of OT, distinguishing them from IT requests.
    • Change Model States: Two models are available (Basic and Advanced) to guide the change request process, including planning, implementation, and closure.

    Key Outcomes

    By implementing the Operational Technology Change Management application, organizations can expect improved coordination of OT changes, reduced downtime from device disruptions, and enhanced security through timely vulnerability fixes. This structured approach helps ensure that all aspects of a change are thoroughly evaluated and managed, contributing to overall operational efficiency.

    The Operational Technology Change Management application enables your team members to work collaboratively on changes to operational technology (OT) devices or industrial equipment configurations. These changes include any optimizations, alterations in the production process, or vulnerability fixes.

    Operational Technology Change Management overview

    By using the Operational Technology Change Management application, you can manage your OT change requests separately from your Information Technology (IT) change requests. You can separate OT change requests from IT change requests by the network type and you can manage OT change requests per site.

    The following examples show how to apply Operational Technology Change Management to your organization:
    • An OT remediation owner, who's responsible for fixing vulnerabilities on OT devices, wants to initiate a change to fix a group of vulnerabilities.
    • An OT technician, who's responsible for OT configurations and plant engineering activities, wants to execute a change to fix a malfunctioned robotic arm on the industrial floor.
    • A plant head, who's responsible for overall production activity, wants to review and approve a change requested by the engineering team.

    OT change requests

    OT change requests occur when there’s a disruption in service from an OT device on an OT network. In some cases, the OT device may not be known when the change request is created. When you create an OT change request from the Industrial Workspace, the change request is automatically assigned a Network Type of OT. This attribute is used to distinguish an OT change request from an IT change request. This field isn’t displayed by default. For more information about OT devices, see OT device related items and related lists.

    For more information about how to create an OT change request, see Create a change request.

    Separating an IT and OT change

    When the Operational Technology Change Management application is installed on your instance, you can choose a Network Type of IT, OT, or None. New change requests are assigned a Network Type of None by default.

    Operational Technology Change Management model state transitions

    The following tables list the Operational Technology Change Management model state transitions for both the Basic OT Change Model and the Advanced OT Change Model. For more information about the OT Change Models, see Select a change model to fulfill change requests.
    Table 1. States for the Basic OT Change Model
    State Description
    New An OT change request is initiated.
    Plan The OT change request is analyzed with the following criteria:
    • Justification
    • Implementation plan
    • Risk and impact analysis
    • Backout plan
    • Test plan
    • Schedule the change
    Implementation The change is performed on the targeted OT device.
    Closed The change record is closed after the change is completed.
    Canceled The change record is canceled and the change isn’t applied to the OT device.
    Table 2. States for the Advanced OT Change Model
    State Description
    New An OT change request is initiated.
    Plan The OT change request is analyzed with the following criteria:
    • Justification
    • Implementation plan
    • Risk and impact analysis
    • Backout plan
    • Test plan
    • Schedule the change
    Approve The reviewers approve or deny the OT change request.
    Implementation The change is performed on the targeted OT device.
    Post-Implementation Review Add additional OT change tasks if needed and perform the following checks:
    • Electrical check
    • Network check
    • Quality check
    • Safety check
    Closed The change record is closed after the change is completed.
    Canceled The change record is canceled and the change isn’t applied to the OT device.