Our tkUIPL client with workflows deeply integrated with Siemens COMOS, tkUIPL's ability to leverage PlantSight is severely compromised by the non-functional legacy connector.

Our current manual Excel-based workarounds is inefficient, error-prone, and unsustainable.

A robust, automated connector is the most critical technical requirement for the success of our digital twin strategy and will deliver substantial benefits in efficiency, data quality, and project execution.

A dedicated COMOS connector is not just a technical fix; it is a fundamental enabler of business value across the project lifecycle.

How it should work

From a user's perspective, the connector should be an integrated and intuitive part of the PlantSight portal, designed for robustness and ease of use.

1. Connection Setup: Within the PlantSight "Data Acquisition" portal, there should be a new, clearly labeled "COMOS Connector" option. Configuration should be straightforward, requiring only the necessary server details, database name, and credentials to establish a connection.

2. Flexible Data Mapping Interface:

• Provide an intuitive UI to map COMOS object types, layers, and attributes to the corresponding classes and properties in the PlantSight schema.

• This interface must be flexible enough to handle tkUIPL's custom COMOS attributes and project-specific configurations.

• Allow mapping profiles to be saved and reused across projects.

3. Granular Data Scope Selection: Users must be able to select precisely what data to synchronize. For example, the ability to select specific engineering disciplines (e.g., P&ID, Electrical), project units, or even specific drawing sets for an import job. This prevents irrelevant data from cluttering the model.

4. Automated & On-Demand Synchronization:

• On-Demand: A simple "Sync Now" button is essential for triggering immediate updates after significant design milestones or revisions.

5. Transparent Logging and Change Management:

• Detailed Logs: Provide clear, accessible logs for every job, detailing what was created, updated, or deleted. Error messages must be descriptive and actionable.

• Changeset Visualization: Each synchronization should create a changeset in PlantSight, allowing users to easily visualize and review what has changed from the previous version. This is critical for auditing and impact analysis.