Industrial Core plugin

The Industrial Core plugin contains the class mappings needed for the Operational Technology (OT) certified Service Graph Connectors.

Industrial Core plugin overview

The Industrial Core plugin [sn_ot_core] introduces foundational capabilities to support OT-specific data models and the site based licensing requirements for OT. The plugin is required as a dependency by all products in the Operational Technology Management solution. The dependency can be a direct dependency or a dependency through a base product. For example, the Operational Technology Manager application is a dependency. For the Operational Technology Vulnerability Response application, the Industrial Core plugin isn't added as a dependency because Operational Technology Manager is a direct dependency for Operational Technology Vulnerability Response.

Note:

All partner applications integrating with the OT functionality must declare a dependency on the Industrial Core plugin. This ensures consistent handling of licensing and future model enhancements.

Industrial Core plugin features

The following table summarizes the features for the Industrial Core plugin.

Table 1. Plugin features

Feature	Description
OT Class Mapping Template [ot_class_mapping_template]	The Industrial Core plugin introduces a configuration template to manage class mappings through a user-accessible table part of the OT Service Graph Connectors. This configuration template replaces the prior script-based approach. While the OT Class Mapping Template is currently optional, adopting this method is recommended as it allows you to view, manage, and override class mappings directly in the UI and provides a greater transparency and flexibility. Note: Partners can extend the OT Class Mapping Template table in the scope of their application to capture the class mappings specific to the integration. With the OT Class Mapping template, you can also define an OT device naming strategy per class by using the Allow Custom Device Naming and Device Naming Strategy fields. For more information about how to implement the device naming strategy, see Create and use an OT device naming strategy. For more information about the OT Class Mapping Template and its available fields, see the OT Class Mapping Template section in Operational Technology (OT) extension classes. For more information about reviewing class mappings for the Service Graph Connector for Microsoft Excel, see Review class mappings.
OT Device Network Connection [sn_ot_device_network_connection]	The OT Device Network Connection [sn_ot_device_network_connection] table references the CI relationships [cmdb_rel_ci] table, and identifies device-to-device connections in CI relationships for OT devices. Note: This data is populated with the available OT integrations and cannot be manually created. For more information about the OT Device Network Connection data model, see Operational Technology (OT) extension classes.
OT Site Map [sn_ot_site_map]	The OT Site Map [sn_ot_site_map] table is used to assign metadata information to OT devices and contains the following fields. Approval group Assigned to Change group Company ISA assignment site Location Managed by Managed by group Owned by Site description Site name Network type Support group Active Supported by
OT Discovered Subnet [sn_ot_discovered_subnet]	The OT Discovered Subnet [sn_ot_discovered_subnet] table contains the discovered subnets used for OT subnet mapping and contains the following fields. CIDR Discovered managed network Site
OT Activity [sn_ot_activity]	The OT Activity [sn_ot_activity] table captures the following activities that occur on the OT device: Addition, update, or retiring of a configuration item Addition of an IP address
OT Backup Job Execution History [ot_backup_history_and_comparison_log]	The Backup Job Execution History [ot_backup_history_and_comparison_log] class creates a history of records for all backup executions. It compares the history of records for all backup executions.
OT Automation Repo [ot_automation_repo]	The OT Automation Repo [ot_automation_repo] class acts as a repository to store all configuration changes you want to perform on an OT entity.
OT Automation Repo Device M2M [ot_automation_repo_device_m2m]	The OT Automation Repo Device M2M [ot_automation_repo_device_m2m] class acts a reference to the OT Automation Repo and the OT Entity table.
OT AutomationCommit [ot_automation_commit]	OT AutomationCommit [ot_automation_commit] class acts as a reference to the changes you have committed to a project.

• Create and use an OT device naming strategy
  Create and use the Operational Technology (OT) device naming strategy to create unique names for your OT devices.