📢 Phase-out - Announcement for Common Connector Configurator.

Dear All,

We would like to inform you that the Common Connector Configurator (CCC) will be officially phased out on , 30th June 2026.

Successor Solution

The Common Configurator Management App will replace the Common Connector Configurator as the recommended solution moving forward.

Why Transition to the Common Configurator Management App

Centralized Management

• Configure data connectivity from a single, centralized interface within IEM
• Efficiently manage sessions for configured edge devices
• Support for additional connectors beyond SIMATIC S7 and OPC UA

Resource Optimization

• Reduced application footprint on edge devices
• Improved device performance through fewer dependent applications

Enhanced Flexibility

• Continued support for device-level configuration where required
• Seamless integration with existing infrastructure
• Support for data connectivity across all edge device types, including ARM devices

Migration Strategy

To ensure a smooth and safe transition, please follow these steps:

1. Export configurations (SIMATIC S7 Connector / OPC UA Connector) from CCC
2. Install the Common Configurator Management App (CC‑M) on IEM
3. Upgrade the connector versions to 2.4.0 or higher for the OPC UA Connector and 2.3.0 or higher for the SIMATIC S7 Connector (if currently using older versions). Note: Only these versions and later are supported in CC‑M.
4. Import the exported configuration into CC‑M
5. Validate the imported configuration and deployment
6. Uninstall the Common Connector Configurator (CCC) from IEM
7. Migration complete

Important Notes – Coexistence with Common Configurator on IED

• The Common Configurator Management App (CC‑M) does not automatically synchronize with configurations on the Common Configurator on IED (device-level).
• Configuration deployments are not merged:
  • A deployment from CC‑M (IEM) will overwrite configurations on the edge device
  • A deployment from Common Configurator on IED may overwrite centrally managed configurations
• Recommendations:
  • Clearly define whether configuration is managed centrally (IEM) or locally (IED)
  • Avoid parallel configuration changes from both systems to prevent conflicts or data loss

Breaking Changes – SIMATIC S7 Connector

The following applies if you are using:

• A version of the S7 Connector earlier than 2.2.1
• Secure PLC communication with self-signed TLS certificates, and
• The certificate was not configured under Optimized S7 Connection

Impact After Upgrade (2.3.0 or later)

• PLC connection will fail
• Data will not be published

Resolution

• Configure the required certificate in the Common Configurator Management App
• Redeploy the project to restore secure communication and resume data flow

Thank you for your continued support.