Operational Technology Version Control data model for Backup Management

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read
  • In Operational Technology (OT) Backup Management, you can develop multiple scripts or programs to automate the data backup process of OT devices. The Version Control data model enables you to maintain a record of all the backup scripts or programs you develop for an OT entity.

    The following class tables are interconnected and collectively form the Version Control data model for Operational Technology (OT) Backup Management data model.

    Use the OT Automation Repo (sn_ot_automation_repo) class as a repository to store all configuration changes you want to perform on an OT entity. The following attributes are available in the class:
    Attribute Description
    Project Last Updated Date and time of the most recent changes to the project.
    Comments Additional information provided by the OT engineer.
    Is multiple edits enabled Select Yes or No to enable multiple edits to the project.
    Days since current state Number of days that have passed since the project has been in the present status.
    Latest version Current version of the OT device the project is assigned to.
    Project State Status of the project.
    Use the OT Automation Repo Device M2M (sn_ot_automation_repo_device_m2m) class as a reference to the OT Automation repository and the OT Entity table. The following attributes are available in the class:
    Attribute Description
    Automation Repo The repository where all project modifications and configurations are stored.
    OT Entity The OT Entity to which the project has been assigned.
    Use the OT AutomationCommit (sn_ot_automation_commit) class as a reference to the changes you have committed to a project. The following attributes are available in the class:
    Attribute Description
    Automation Version The version of the script or the program committed for the OT entity.