Release Notes 10.2 Release Notes 10.2.3 Operating Manual 05/2018 V 10.2.3 A5E37082755-AD Licenses 1 New functions 2 Corrected errors or changed behavior 3 Discontinuations 4 Known

COMOS

Release Notes 10.2.3

Operating Manual

05/2018 V 10.2.3A5E37082755-AD

Licenses 1

New functions 2Corrected errors or changed behavior 3

Discontinuations 4

Known Issues 5

Changes following deadline 6

Legal informationWarning notice system

This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger.

DANGERindicates that death or severe personal injury will result if proper precautions are not taken.

WARNINGindicates that death or severe personal injury may result if proper precautions are not taken.

CAUTIONindicates that minor personal injury can result if proper precautions are not taken.

NOTICEindicates that property damage can result if proper precautions are not taken.If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.

Qualified PersonnelThe product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems.

Proper use of Siemens productsNote the following:

WARNINGSiemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed.

TrademarksAll names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of LiabilityWe have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AGDivision Process Industries and DrivesPostfach 48 4890026 NÜRNBERGGERMANY

A5E37082755-ADⓅ 05/2018 Subject to change

Copyright © Siemens AG 2015 - 2018.All rights reserved

Table of contents

1 Licenses.......................................................................................................................................................7

1.1 As of Version 10.2.1.................................................................................................................7

1.2 As of Version 10.2.2.................................................................................................................7

2 New functions...............................................................................................................................................9

2.1 Release for operating systems and third-party software..........................................................9

2.2 COMOS 10.2............................................................................................................................92.2.1 Report......................................................................................................................................92.2.2 P&ID.......................................................................................................................................102.2.3 FEED......................................................................................................................................112.2.4 EI&C.......................................................................................................................................112.2.5 PDMS/E3D Engineering Interface..........................................................................................132.2.6 OpenPlant interface...............................................................................................................132.2.7 COMOS Walkinside...............................................................................................................132.2.8 Maintenance...........................................................................................................................142.2.9 Inspection...............................................................................................................................142.2.10 PQM.......................................................................................................................................152.2.11 Enterprise Server...................................................................................................................152.2.12 COMOS PDI...........................................................................................................................152.2.13 Platform..................................................................................................................................162.2.14 Mobile Solutions.....................................................................................................................172.2.15 Help........................................................................................................................................17

2.3 COMOS 10.2.1.......................................................................................................................182.3.1 Database................................................................................................................................182.3.2 Platform & Basic.....................................................................................................................192.3.3 Report....................................................................................................................................202.3.4 Generic Data Mapper.............................................................................................................212.3.5 EI&C.......................................................................................................................................212.3.6 FEED......................................................................................................................................222.3.7 P&ID.......................................................................................................................................222.3.8 MRO.......................................................................................................................................222.3.9 Mobile Solutions.....................................................................................................................232.3.10 PDMS.....................................................................................................................................232.3.11 PDI.........................................................................................................................................242.3.12 Walkinside .............................................................................................................................252.3.13 Database version...................................................................................................................26

2.4 COMOS 10.2.2.......................................................................................................................262.4.1 Frame setup...........................................................................................................................262.4.2 Kernel.....................................................................................................................................262.4.3 Platform..................................................................................................................................272.4.4 Administration: New index clusters........................................................................................282.4.5 Mobile Solutions.....................................................................................................................282.4.6 PDMS.....................................................................................................................................282.4.7 Operations..............................................................................................................................29

Release Notes 10.2.3Operating Manual, 05/2018 V 10.2.3, A5E37082755-AD 3

2.4.8 3D Integration.........................................................................................................................292.4.9 Automation.............................................................................................................................302.4.10 Report....................................................................................................................................302.4.11 Database................................................................................................................................312.4.12 P&ID.......................................................................................................................................322.4.13 FEED......................................................................................................................................33

2.5 COMOS 10.2.3.......................................................................................................................332.5.1 Platform..................................................................................................................................332.5.2 COMOS Mobile Solutions......................................................................................................342.5.3 P&ID.......................................................................................................................................342.5.4 EI&C.......................................................................................................................................342.5.5 Process Data Interface to Teamcenter/NX............................................................................34

3 Corrected errors or changed behavior........................................................................................................35

3.1 COMOS 10.2.3.......................................................................................................................353.1.1 Changed behavior of terminal strips in a diagram..................................................................353.1.2 Error list..................................................................................................................................35

3.2 COMOS 10.2.2.......................................................................................................................393.2.1 Text field on a report..............................................................................................................39

3.3 COMOS 10.2.1.......................................................................................................................403.3.1 Behavior of RTF text fields in reports.....................................................................................403.3.2 Administration: Language dependency of attribute-based filters...........................................40

3.4 COMOS 10.2..........................................................................................................................413.4.1 Compressing COMOS data...................................................................................................413.4.2 Change markings in reports...................................................................................................41

4 Discontinuations.........................................................................................................................................43

4.1 Operating system...................................................................................................................43

4.2 LCODBC32.EXE....................................................................................................................43

4.3 Isometrics: ROHR2 export.....................................................................................................43

4.4 COMOS Mobile DocumentView.............................................................................................44

4.5 Sharepoint interface...............................................................................................................44

4.6 CVS and NewCVS.................................................................................................................44

4.7 COMOS.dll.............................................................................................................................45

4.8 Discontinuations and functional limitations as of COMOS 10.2.0..........................................45

4.9 COMOS PlantModeler (CPM) as of COMOS 10.2.0..............................................................47

4.10 Discontinuation of "Export reports to EMF" as of COMOS 10.2.0.........................................47

4.11 COMOS Express/COMOS ME Designer as of COMOS 10.2.0.............................................47

4.12 P&ID.......................................................................................................................................48

4.13 FEED......................................................................................................................................48

5 Known Issues ............................................................................................................................................49

5.1 As of 10.2.3............................................................................................................................495.1.1 Revision with COMOS HARP................................................................................................49

Table of contents

Release Notes 10.2.34 Operating Manual, 05/2018 V 10.2.3, A5E37082755-AD

5.1.2 Problems occur with incorrect values in specifications using the mode “values in XML”.......495.1.3 Net login method causes incorrect display on reports...........................................................495.1.4 Mobile Solutions.....................................................................................................................505.1.5 Installation of service packs via the Update Center ..............................................................515.1.6 Contents of the help texts......................................................................................................515.1.7 PDF Docu Pack .....................................................................................................................525.1.8 Installing help in silent mode..................................................................................................52

5.2 As of 10.2.2............................................................................................................................525.2.1 Restrictions for Excel interfaces due to MS security updates................................................525.2.2 Mobile Solutions.....................................................................................................................535.2.3 Operations..............................................................................................................................545.2.4 Basic......................................................................................................................................545.2.5 COMOS Help.........................................................................................................................555.2.6 Frame setup...........................................................................................................................555.2.7 FEED......................................................................................................................................575.2.8 P&ID.......................................................................................................................................57

5.3 Older versions........................................................................................................................575.3.1 Uninstalling HARP printer and COMOS revision printer........................................................575.3.2 Uninstallation of the Teamcenter interface.............................................................................575.3.3 Compressing and repairing the database..............................................................................575.3.4 Copying AutoLoops................................................................................................................585.3.5 HTML help system.................................................................................................................585.3.6 Construction of a bypass for pipes with special direction.......................................................585.3.7 Zoom function in redlining documents...................................................................................595.3.8 Installing .Net Framework......................................................................................................595.3.9 Export polyline to AutoCAD....................................................................................................605.3.10 noxieFolder............................................................................................................................605.3.11 New calculation method for *-revisions..................................................................................605.3.12 Administration: Required versions of CLS and RLS..............................................................615.3.13 Administration: Increasing the document version..................................................................615.3.14 Administration: Font for display of attributes..........................................................................625.3.15 Administration: Copying the base project...............................................................................625.3.16 Administration: Editing the "IsRequest" property on Device..................................................635.3.17 Troubleshooting of excessive GDI resource consumption.....................................................635.3.18 ElementName Z.....................................................................................................................645.3.19 Interfaces: CDI.......................................................................................................................645.3.20 Interfaces: "Export reports to EMF"........................................................................................645.3.21 GSD interface.........................................................................................................................655.3.22 Word export............................................................................................................................655.3.23 Report templates dependent on working layers.....................................................................655.3.24 Shutdown...............................................................................................................................665.3.25 MRO.......................................................................................................................................665.3.26 Integrated Engineering...........................................................................................................665.3.27 Collisions in connection with Updateability function...............................................................67

6 Changes following deadline........................................................................................................................69

6.1 Introduction............................................................................................................................69

6.2 COMOS Platform...................................................................................................................696.2.1 Administration........................................................................................................................696.2.2 Operation...............................................................................................................................726.2.3 Class documentation TcIntegrator_dll....................................................................................73

Table of contents


6.2.4 Report....................................................................................................................................766.2.5 COMOS License Management..............................................................................................76

6.3 COMOS Process....................................................................................................................766.3.1 FEED......................................................................................................................................766.3.2 P&ID.......................................................................................................................................776.3.3 Data Flow Manager................................................................................................................786.3.3.1 Objective and general conditions of the Data Flow Manager.................................................786.3.3.2 Overview of using the Data Flow Manager............................................................................796.3.3.3 Using data break flags and data break objects......................................................................806.3.3.4 Preview of the data flow on the report....................................................................................826.3.3.5 Administration........................................................................................................................846.3.4 Configuring text recognition for AutoCAD drawings...............................................................876.3.4.1 Overview of the AutoCAD text recognition.............................................................................876.3.4.2 Example for an implementation in the iDB.............................................................................906.3.4.3 Class documentation DwgDxfInterface..................................................................................91

6.4 COMOS Lifecycle...................................................................................................................936.4.1 PQM.......................................................................................................................................936.4.2 PDMS/E3D Engineering Interface Navigating........................................................................94

6.5 Mobile Solutions.....................................................................................................................946.5.1 Named user licenses required...............................................................................................94

6.6 iDB.........................................................................................................................................95

Table of contents


Licenses 11.1 As of Version 10.2.1

As of 10.2.1 a new bundle is available:

LifecycleCOMOS WebPQM: COMOS WebPQM is designed for the following main use cases:

● Mobile Document Management

● High performance data access

The main functional highlights are:

● Upload, check in and check out documents via the Web interface

● Read and edit engineering data online via web

● Quick links to COMOS objects and documents

● Compatible with several browsers

● Review and approve documents

● Snapshots of COMOS data with high performance access

Table 1-1 The Product IDs are:

CIS:13590C COMOS WebPQM Client Access, FL (C)CIS:13590G COMOS WebPQM Client Access, FL (G)CIS:13590N COMOS WebPQM Client Access, NU

1.2 As of Version 10.2.2As of 10.2.2 a new bundle is available:

LifecycleCOMOS WebData: With COMOS WebData, 1D and 2D data from different data sources can be easily collected – especially in Brownfield scenarios – and then consolidated and validated with the help of a web GUI.


CIS:15332G COMOS WebData, FL (G)CIS:15332C COMOS WebData, FL (C)CIS:15332N COMOS WebData, NU


COMOS WebMRO is a new bundle for operation customers, available as Floating and Named User.


CIS:13099 COMOS WebMRO Client Access, FloatingCIS:13099N COMOS WebMRO Client Access, Named User

Licenses1.2 As of Version 10.2.2


New functions 22.1 Release for operating systems and third-party software

You can find additional information on this topic in the "Installation and Configuration" manual, keyword "Compatibility matrix".

See also chapter Installing .Net Framework (Page 59).

2.2 COMOS 10.2

2.2.1 Report● Extended shortcut keys available on the report: Ctrl+Z, Ctrl+Y, Ctrl+Arrow left, Ctrl+Arrow

right

● Report templates and scripts now have a separate, consistent uniform management

● Dynamic formatting of texts in memo fields - also across several pages

● The representation for views, printing and exporting can now be set separately for the document levels

● PDF export now supports CID fonts

Revision rectanglesAnalog to the interactive report, it is also possible at evaluating reports for changes compared to a previous revision to be represented by means of a rectangle. This ensures that the difference between inheritance and revision remains recognizable.

Improvement of navigation to intelligently exported PDFsAdditional references for a more intuitive PDF stand-alone navigation:DetailReference, AllMyReferences, ReferenceFromOwner, REFCHAIN, REFMASTER, ObjectReference (including all parameters)


2.2.2 P&ID

Renaming of the XMpLant interface and extension of the functional scope● In conformity with Fiatech XMpLant has been renamed to Proteus.

● For the search (on the basis of the ComponentClass) for existing base objects 10 start nodes can be specified for the Proteus import.

● Attributes are supported at XML Items.

● Proteus import and export use a mapping between COMOS attributes and RDL classes and URIs. On the basis of these references attribute values can be exchanged with the Proteus interface.

● So-called DependentAttributes are supported during a Proteus import and export. Texts and labels thus reference values of GenericAttributes.

Updated interfaces● P&IDs are exported and imported ISO 15926-compatible to Proteus (previously XMpLant)

3.3.3 and 3.6.0

● Design data are imported and exported from F.I.R.S.T. Conval 8 and 9

● Drawings are imported from Autodesk AutoCad file formats 2010 and 2013

● Drawings are imported from Adobe PDF file formats 1.4 and 1.6

Bulk changing of the color setting on the P&ID● The menu entry for the bulk changing of the color setting on the P&ID is now language-

dependent

● The selected color setting is now saved and is also active when the P&ID is not opened. A color legend shows the meaning of the colors in the document.

Miscellaneous● Sheet references for pipes can now be generated more comfortably through a new note-

and-connect technique. This allows existing pipes to be assigned to each other.

● Similarly to the docking of measurement functions to pipes, measurement functions can now also be connected to equipment and if necessary receive a connection piece and a process line.

● The P&ID disposes of a new functionality that checks whether components are drawn between pipes, pipe sections or pipe segments. The constellation on the P&ID is compared with the preset attribute "Cut mode". This means that the observance of the identification rules during planning can be ensured better.

● A new symbol catalog supports the symbols in the style of ISO 10628-2:2012

● It is now possible to hide the flow direction arrow of a pipe on the P&ID.

New functions2.2 COMOS 10.2


● The "Assign line types" plugin has been extended. Process lines can be pre-configured with standard line types and line widths.

● Filtering of units. Solely the relevant units can be selected at unit-specific attributes of the FEED and P&ID catalog tabs.

2.2.3 FEED

Extension of the case manager● The run cases are sorted alphabetically in the case manager user interface

● The case manager optionally takes subobjects into account

Miscellaneous● Limiting value for the molar fraction of imported material components. The user of FEED

simulation imports can specify limiting values for the molar fraction of material components to be imported. If the value drops below the limiting value, components are not imported.

● The Aspen import supports the usage of hierarchy levels in Aspen. The levels are dissolved during importing into a process unit.

● Bulk assignment of simulation objects to COMOS objects. The user interface for the assignment of simulation objects to COMOS planning objects has been extended by a button for bulk assignment.

● Extension of the ChemCad import. Values for Cp/Cv, pH-value and latent heat are now also imported from ChemCad.

● The user interface for the component grouping has been extended by a functionality that allows individual components to be removed from a group.

2.2.4 EI&C

Dynamic connector assignment● Uniform user interface with user guidance, consistency check and status window

● Available for all electrical devices

Generic Excel import● Use of templates; definition using drag-and-drop

● Expanded templates to cover many applications

● Use of engineering objects possible



● Efficient integration of supplier data and inheritances

● No programming effort required for the use of rules

Loop Assistant for industrial plants● Easy integration of inherited and supplied data from industrial plant projects

● Import of pre-configured Excel templates

● Integration of inherited loop lists

● Rule definition via drag&drop

● Templates do not have to be fixed

● Usable with or without templates

GSD interface● Integration of object libraries from the automation

● Use of standardized GSD format for Profibus PA, HART and Foundation Fieldbus

● Workflow support from object selection to assignment

● Web download possible

SIMIT interface● Integration of SIMIT component interface descriptions according to COMOS

● Mapping for customer data model

● Export based on COMOS P&ID Report

● Fast and efficient creation of simulation models

● Direct integration with PCS 7 automation solution

Marshalling designer● Newly designed user interface

● Visualizes connection paths

● Better feedback for bulk functionalities

● Topology planning for detailed cabling



2.2.5 PDMS/E3D Engineering Interface

New user interface for representing and for interactive editing of a working area from the 3D model● Representation of the objects of the working area in a tree view

● Determining of inconsistencies between COMOS and 3D model. In particular reference to objects missing in COMOS

● Interactive creation of missing objects in COMOS

● Navigation between COMOS, PDMS/E3D and the working area

Extended communication between COMOS and PDMS/E3D● The network administration of the communication is much simpler and more efficient

● Several COMOS and PDMS/E3D instances can communicate with each other independently of each other

● Functions for supporting the SIEMENS security guidelines for network communication have been included

2.2.6 OpenPlant interface

Bentley COMOS Collaboration● Creating of Bentley i-models from COMOS P&ID graphics and process data

● User-configurable data export

● Data access to write-protected COMOS data in OpenPlant for 3D purposes

● Synchronizing of 2D and 3D contents with respect to data consistency

2.2.7 COMOS Walkinside

Oculus Rift● COMOS Walkinside HMD Support based on Oculus Rift 0.5 SDK

Status queries● Receive status queries from Walkinside

● Execute status queries and display the results with color highlighting in Walkinside



● Enables the review of all available status queries directly in Walkinside (engineering, order assignment, maintenance)

● Loading of status from the CSV directly into the 3D model

Quick search● Color marking of all quick search results

● Exclusive display of quick search results

SmartPlant 3D ● New builder in COMOS Walkinside - Creation of Walkinside projects based on SP3D data

● SAT and XML extracts from SP3D

● Geometry and attributes and system hierarchy

2.2.8 Maintenance

Usability improvements● Configurable life cycle structure nodes

● Easily configurable data handover and direct navigation from engineering object to operation object

"Network Diagram" plugin● Planning of dependencies in network diagrams

● Transparent visualization of sequences for identification of definition gaps

2.2.9 Inspection● Configurable user interface for input of test data in 3rd party software

● Export of test data series to an Excel file

● Validation of the reimported values



2.2.10 PQM

Document transfer tool: "Document transfer" plugin● Selection via drag&drop

● Export of documents with options: Revision or version, with or without checkout, as .zip or folder

● Print to a file with index or single document

2.2.11 Enterprise Server● Rescission of jobs

● Execution in working layers

● Logging and monitoring of jobs

● Increased data consistency

2.2.12 COMOS PDI

Integrated document management● Synchronizing of document metadata between COMOS and Teamcenter

● Searching for documents in Teamcenter

● Initiating document revision process in Teamcenter

● Transferring of delivery packages

Integrated change management● Creating of change request in COMOS and starting of the change order workflow

● Creating of change order in TC and confirm change order

● Report COMOS change order status to TC

● Changing of the change order in COMOS



2.2.13 Platform

UpdateabilityThis function and the associated user interface have been revised completely. By using a configured and correspondingly prepared iDB, future updates and service packs can be deployed based on individual customer requirements.

It is possible to import only the new and adapted objects needed for the new functionalities.

In addition, existing objects can be updated if the delivery includes corresponding contents.

Object historyTime of all available information for an object and can be used as a change history.

Registration with 4GB support / COMOS4G.execomos4G.exe is no longer being delivered.

comos.exe now always supports the address range up to 4 GB.

Enterprise Server with 4 GB support Enterprise Server now supports the address range up to 4 GB. The following components have been adapted for this purpose:

Comos.EnterpriseServer.Process.exe

ComosMotionXServerManager.exe

CVS3GRedesign of CVS. Release only for SQL databases

References to MSXML 5 replaced The third-party component MSXML is supplied in the following versions:

● Up to and including COMOS 10.1 SP3: MSXML 5

● COMOS 10.2 and later: MSXML 6

If the existence of MSXML 5 is explicitly requested and used as part of customizing, customers must install MSXML 5 themselves later or adapt the customizing.

MSXML 6 is backward compatible. If MSXML is used only generally within the framework of COMOS, there are no known compatibility problems.

Further development of the administration of unitsIt can now be specified for an attribute how it behaves at a change of the unit system.



To use this function, the database version must be increased.

eCl@ss Support of eCl@ss 9.0 advanced (+), extended functions such as user-specific mappings, document import, creation of requirements

SQL Windows authenticationBased on Windows NT authentication Safe and stable technology

Version-dependent licensingComos 10.2 requires new license files. These licenses are available only to new customers and customers with active maintenance agreements.

Customers without ME&S do not have access to new functionalities.

Expansion of ODBC data sourcesExtension of permissible database connections. Increased efficiency for admins.

Revision of the user interface for working areasImproved usability

2.2.14 Mobile Solutions● Support of new service module eSign

● PDF signing without COMOS client in COMOS Web (WEBPQM license required)

● Adoption of COMOS Redlining functions in COMOS Web

● Drop-down navigation aid at bottom in the navigator including display of the object path

2.2.15 HelpHelp has been converted to HTML5 in Version 10.2.

Help thus has a new look and can be displayed on all platforms and operating systems.

This also lays the foundation for the future. The HTML5 technology enables new ideas to be linked in the future.



2.3 COMOS 10.2.1

2.3.1 Database

Script management toolScript search in the database

Script export

Script import

Path search in scripts

@30 Structure toolBulk operations for adding elements, documents and tabs for @30 objects.

Query-based configuration of bulk operations.

Hardcoding managementConfigurable entry points for the software.

Central location for future SystemFullName hardcodings

Hardcoding management for scripting

Attribute toolRule-based attribute import / export

Rule-based tab import / export

Rule-based creation of individual attributes and tabs

Working layer releaseImproved performance for working layer release

Significantly faster release of large working layers

New functions2.3 COMOS 10.2.1


2.3.2 Platform & Basic

COMOS Basic● Office 2013

● QueryViewThe "QueryView" display is a variant of the object browser and replaces the "Alternative" mode in the query. In "QueryView" display mode, a query can be scrolled faster vertically.

eCl@ss interfaceWalkinside supports eCl@ss 9.0 Advanced. You have the option of defining requirements and selecting the manufacturer device. Assignments can be individually defined. Manufacturer information and documents can be imported. The information of the requirement objects are retained. Product data are write-protected to ensure the reliability of the information.

The data import is independent of vendors with this interface. The device data comparison is easier to perform.

eCl@ss connector management● Mapping of the connectors is now possible.

● Additional connectors can now be created when importing.

● Information about the connectors is transferred from the eCl@ss data to COMOS

COMOS iDB● iDB script editing

The script editing exports and imports iDB script blocks. These functions enable you to edit the script blocks outside COMOS. In addition, script editing offers an overview of how script blocks are used in the COMOS projects.

● iDB @30 Attribute toolThe structure in the "@30" node is put together by means of cross-inheritance. The base object "@30 Tool" supports editing of the child objects by means of bulk processing:

– With the "@30 Tool", elements, tabs, documents and similar object components can be assigned in bulk and thereby added.

– With the "@30 Tool", selected properties of the assigned elements can be edited.

● iDB hardcoding managementThis function allows you to use hardcoding in script or source code without having to tolerate the usual disadvantages of hardcoding: You can move or rename base data without having to adapt the script or the source code.The hardcoding is combined with reference attributes for this.

● iDB import of attributes and tabsThis function enables you to edit the attributes catalog and the tabs catalog in bulk based on an external Excel workbook.



Having the full-text index updated by the server You can control the indexing of the full-text index with index updater services that you install on a server.

You install the service for each database on the server that is to be indexed by the server. You install, start and stop services using the "COMOS Full-text Index Service Configurator".

An index updater service monitors all projects of a database during runtime. Indexing takes place as soon as an event occurs that requires an update of the index.

The updated index is available immediately to all users of the database.

The service has the following advantages:

● Improved performance

● The workload at the client end is minimized

● Improved user-friendliness

2.3.3 Report

User settings (report)● Paging behavior

● Rotation angle

● Reverse mouse wheel zoom direction

● User-specific or managed by the administrator

RTF re-engineeringThis means, scaling corrected according to the resolution in relation to the output medium/device.

Performance improvementsStabilization and performance were improved, particularly on the P&ID.



2.3.4 Generic Data Mapper

Importing a consistency report from OpenPlantA status check of the engineering data between 3D and 2D engineering is performed on the object and attribute level. The consistency status is shown in an interface. You can resolve 3D-2D inconsistencies individually or in bulk for each object. The mapping between the Bentley EC scheme and COMOS can be configured.

Find discrepancies between the 3D and 2D process designs. The interface allows you to evaluate the differences and decide whether and where the differences are resolved. This enables you to keep your design consistent over the duration of a project. In addition, you can accomplish smaller tasks such as the modernization or the redesign of an individual plant.

Status display of the componentsA status view shows the individual components, which components are available or not available in COMOS and whether the components are inconsistent or consistent on the attribute level. You navigate to COMOS or COMOD P&ID from the components. The consistencies of the attributes are displayed in a separate window. You can choose if you want to update individual, a selection of or all inconsistencies.

Keep your 2D 3D project aspects consistent and reduce the work required to update your documentation by updating your data with one click.

2.3.5 EI&C

"Update Assemblies" pluginThe "Update Assemblies" plugin supports the administration and versioning of templates. You have the option of assigning the user rights separately for this plugin. Documents and data are updated in such a way that only the changes in the template can be updated. The changes are analyzed in detail. The versioning concept allows you to make changes without influencing the use of the actual template version.

All instance-specific changes can be retained this way. Incomplete work and released versions of a template can be clearly separated. There is a separate release process including rights management for new versions of the template.

New concept for connectionsThe information of the connection and the connection properties are stored separately. If there is a device change and rewiring, the connection properties are retained. A collision check is performed when connections are joined. A defined, transparent behavior for the processes such as joining and cutting. The performance for queries and bulk processing operations has been improved. You can easily find information about wires and cables of the connection. COMOS provides extensive feedback.

This new approach makes EI&C detail engineering easier for you. Detailed collision analysis and enhanced user guidance for bulk processing operations also support you.



Bulk processing for connector mappingsA tool allows you to select multiple connector mappings. The graphical mapping of changes is made using "Memorize" - "Apply". You use the same tool for all devices.

Bulk processing is more efficient for you to use. Once applied, changes you can be simply reapplied.

2.3.6 FEED

Export to Bentley PlantWiseConfigurable mapping between PFD and PlantWise objects, including main attributes and electrical connection

2.3.7 P&ID

Support of ISA 5.1 / 5.3 / 5.5 standardsNew P&ID object library with symbols according to ISA standard including:

● Equipment

● Machines

● Instrumentation

● Line types for signal lines

● Drawings, data sheets and lists

2.3.8 MRO

Project management toolkit● Managing the scope of projects (adding, removing, editing activities)

● Managing different types of relationships between activities (creating, removing)

● Showing activities and relationships in the network diagram and the Gantt chart

Advantages:

● Fully integrated project management

● Direct connection between digital image and project management



2.3.9 Mobile Solutions

Web task managementNew web app for managing a large number of tasks.

● Personalized view of task data via queries

● Editing task queries online

● Viewing and editing tasks, creating new tasks

● Included in WebPQM and WebMRO products

New architectureMicroservices and SOA

Query2ExcelExporting queries to Excel

Usability● Choose between COMOS tree and drill-down tree

● Easy editing of dashboard charts

● Copying dashboards

● Improved splinter handling

2.3.10 PDMS

Status classesSix status classes

Tessellation of the objects in the workspace

Attribute update in succession

DetectFiltering/marking per status class: Filtering & Marking

Tessellation according to status class: Overall status check

Status classes are symbols

Own, inherited and mixed status symbols

Status display in COMOS



Display of the status class: Quick Check

Automatic updating of attributes optional

ReportInconsistency report per status class: Filtering & Marking

Overall inconsistency report: Overall status check

Inconsistency report in HTML format

Layout definition with .xslt

DisconnectResolve inconsistency per status class: Filtering & Marking

Update attributes for all objects: Update attributes for all

Update attributes individually

2.3.11 PDI

Freely configurable integration toolkit● Import and export, create, delete and change multi-level object structures such as material

lists, unit, location and document structures

● Import and export, create, delete and change items or parts

● Create documents and revisions

● Synchronizing documents

● Start workflows and complete workflow tasks

Advantages:

● More flexibility

● Quick configuration

● Easily adaptable to customer-specific



2.3.12 Walkinside

COMOS Walkinside Server - loading multiple online projectsYou have the option of selecting and loading multiple projects. You can save and edit the group of projects for future use. You have the same options as for attached projects in the Walkinside Viewer.

The Walkinside server allows you to divide a large model into smaller pieces so that you can concentrate on the essentials. The function is coordinated with other solutions, such as AVEVA: NET, which also require disassembly.

Oculus Rift supportWalkinside supports the official client version 1.

You can go with the trend and use an immersive HMD device at conferences and events as well as at VIP demonstrations.

Light EditorYou use the Light Editor to select and load multiple projects. You are already familiar with the user interface and options from the Incident Editor.

You can choose between three different light sources:

● Spot light

● Point light

● Directional light - global light

The Light Editor is based on an easy-to-use user interface, so no scripting is required.

You can create night scenarios with light and switch the lights on and off within the scenarios. As a trainer, you can publish global light for the participants of a multi-user training session without requiring developer skills.

Point cloud supportWalkinside supports the use of Bentley Pointools based ASCII (XYZRGBI) Point Cloud. You can measure between points and geometrics. You can create redlines, incidents and lights at point clouds.

Integrate point clouds and geometrics to perform a visual consistency check and mark inconsistencies with redlines. Create HSE scenarios based on point cloud or hybrid projects. Use the dedicated Builder for Point Cloud.

ContextCapture supportWalkinside supports the use of Bentley ContextCapture based OBJ. Walk through your newly designed brownfields and create redlines, lights and incidents.



You have the possibility to walk through your brownfield project with an avatar and perform full collision detection. Mark inconsistencies with redlines. Create HSE scenarios based on point cloud or hybrid projects. Use the dedicated Builder for OBJ.

Builder for DWF(x)Walkinside supports the AutoDesk exchange format, CAD hierarchies and databases. The main goal is models based on Navisworks.

Navisworks projects are supported in order to reuse existing 3D projects for training and in business operations. You have the option of loading BIM-based projects.

2.3.13 Database versionCOMOS 10.2.1 with new database version: iDB Version 19

Interaction: The new "Connection objects in ET reports" function requires iDB version 19.

2.4 COMOS 10.2.2

2.4.1 Frame setupA new frame setup is supplied with COMOS 10.2.2. This is used to install or remove all the components of the COMOS Suite. The frame setup thus replaces the setup browser.

In order to start the frame setup open the setup.exe with administrator rights.

Side-by-side installationssxs installations are also new with COMOS 10.2.2. COMOS is thus always installed in the same version side-by-side. The applies for main versions and service packs.

This means that existing versions are no longer overwritten and remain in the file system. If necessary, they have to be removed manually.

2.4.2 Kernel

Archiving of COMOS projectsCOMOS projects can be archived very easily including the base project and system project.

The archive exists in the form of a 7z file and can be restored at any time.

The size of the archive is only limited by the available hard disk memory.



Performance and availability of MS SQL Server databasesThe indexing was optimized for SQL Server databases.

This results in a performance increase of up to 20% when loading COMOS objects from the database.

In addition locking of the database is now only carried out on the dataset level.

This significantly improves the availability of the database during large transactions, in particular when enabling working layers or when deleting large systems.

Restriction of object rightsObject rights can be restricted as needed using a customizing interface.

For example, it is possible to restrict rights depending on workflows and object status so that only certain users or user groups are granted rights.

Global CollaborationCOMOS now provides new SQL Server scripts and triggers that support SQL Server replication mechanisms.

COMOS SQL Server databases can now be replicated with SQL Server standard tools over multiple locations with only minor restrictions.

Workset.SaveAllThe performance of Workset.SaveAll has been significantly improved if there are only a few objects that need to be saved and if the local COMOS Cache contains many objects.

2.4.3 Platform● Change of units in queries

● Navigation assistant with script functions for mapping

● Management of link objects

● Dynamic background color management for specifications in tabs

● Configurable view of the document properties

● Update of the compatibility matrix



2.4.4 Administration: New index clusters

NoteSQL Server: Change of indexing for databases that were delivered or created before COMOS 10.2.2

COMOS 10.2.2 uses optimized indexes with which the performance of the database access is improved.

When an administrator first opens an older database with COMOS 10.2.2 or higher, COMOS detects the obsolete indexing and automatically updates the indexes.

The duration of the update depends on the size of the database and the SQL server hardware used.

Examples:● 40 GB: Between 15 and 30 minutes● 400 GB: 6 hours

During the update, the database cannot be used in production.


● Realizing shorter runtimes for Brownfield projects with the new Data Loading Portal for COMOS Web

– Simple bulk import of structures, objects and attributes

– Automatic generation of document links from AutoCAD files

● New PDF eSign functionality

● Quick decisions: Custom Actions allow linking of complex decisions to one click

– With a single click, revisions are approved, eSign is carried out, attribute values such as the task status or editor are set, etc.

2.4.6 PDMSUntagged Items:

Objects in PDMS/E3D no longer need names to exchange data.

In PDMS/E3D, objects can now also be created over the interface for which IsNamed=False applies.

The same applies for the import of PMDS/E3D objects to COMOS. The PDMS/E3D objects do not need a name to be imported to COMOS.



2.4.7 OperationsBidirectional data exchange to MS Project/Primavera

From the PM Chart, the Scope project can be exported to a PM XML file that can be read into Microsoft Project and Primavera. Modified PM XML files can be read back into the PM Chart and synchronized and harmonized with the data existing in COMOS.

New functions in the PDI Toolkit:

● GetUID for existing relations

● Synchronizing of unit-specific attributes

● TC value list (LOV)

● Teamcenter document import

● Deleting TC objects (objects, folders, datasets)

2.4.8 3D Integration

Extension of possibilities to create object structures with the "Generic Data Mapper"The new functionality allows for free configuration of object structures which are to be created through export to a target application, for example, Bentley OpenPlant Modeler.

This is effected through the assignment of relations between the components in Mapping. In the process, a single object can be in relation to multiple other objects - which allows the creation of random tree structures in the context of the options of the target application.

The introduction of the mapping elements "MAPPED" and "ANY" in this context allows for the definition of generally applicable structure mapping rules - which significantly reduces the time required for the configuration of an interface configuration.

Completion of the Bentley OpenPlant export / import interfaceThe functionality of the export / import interface between COMOS and Bentley OpenPlant Modeler has been extended significantly to complete the communication in the design cycle. The extensions are presented in more detail below.The comparison data made available by Bentley from the OpenPlant Modeler 3D system are now shown in a much more differentiated status view. This allows for easy identification of differences between the two engineering systems.Engineering elements that already exist in both applications - COMOS and OpenPlant Modeler - but that do not have an assignment to each other can now be associated with each other in COMOS.This ensures that the engineering status is kept consistent and that the objects in the 3D model can be identified and, if necessary, updated after a renewed export.Engineering components that were created in the 3D model planning without an available COMOS object reference can now be generated later by means of the interface in COMOS. This allows for process engineers to very easily take into account supplements of the 3D engineer in COMOS.



In order to use the newly added functionalities, a "Linkage database" is required in which the link information is stored.

This completes the information flow between COMOS and OpenPlant Modeler. Engineering information can be exchanged between the two applications during the entire engineering cycle.

2.4.9 Automation● Improvements in auto routing

● Improvements GSD Interpreter

– Special case fail-safe modules

– Special case manufacturer-specific identifiers

– Evaluation of default modules

● Updating assemblies:

– Release of the function for productive use

– Selective document update

● Connection information

– Extended behavior of the connection information on the circuit diagram when connection objects are used

– Change document type, document- or connection-related

– Display of additional information

● Edit connector assignment:

– Zoom into the symbol preview

– Reset the zoom via icon in the toolbar

– Move the symbol preview

2.4.10 Report

COMOS revision printerUnlike in COMOS HARP, the conversion of PostScript to PDF/ TIFF is initiated automatically. This provides the following advantages:

● Printer can print all printable documents such as Adobe PDF

● Printer can be used for printing and revision

● The COMOS printer is installed with a separate setup.



DWG/DXF Mapping Editor● Redesigned user interface.

● Font mapping implemented

● Configuration wizard. All line types, fonts and colors that are available in the report are automatically applied for the configuration.

Transaction-secured handlingReports that were changed within an UndoState can be either stored or rejected at the end of the transaction in a controlled manner. Mode has to be activated explicitly.

* RevisionAny * Revision is output immediately in the report header/footer. Additional evaluation is not necessary anymore.

Color of the revision rectangleCan be set in project option

Changes in working layers ("eagle eye")The format is not modal anymore.

OLE objectsComprehensive revision for NetworkLogin support, update for external changes. For users without matching application the last status is available as a picture.

2.4.11 Database

iDB● Replacement of the SystemFullName hard coding in scripts and in the COMOS software

through the hard coding function

● Higher-performance attribute search

● Complete transition to a centralized icon system



● Additional symbols in accordance with the American JIC (Joint Industrial Council) standard at electrical engineering objects.

● JIC device symbols:COMOS 10.2.2 provides an extensive symbol library in the database for manual creation of JIC circuit diagrams. Note that these symbols and report templates currently only allow manual creation in engineering. Automatisms such as contact surfaces are not fully supported.

2.4.12 P&ID

User friendly control of the data flow on the P&ID with the data flow manager: ● Smart: Graphical preview of the data flow on the P&ID through usage of the property tree

allows faster engineering

● Simply administered:

● Global rules for interruption of the data flow can be created

● Can be activated via project option

– Transparent: Interrupted attributes are displayed at the interruption flags

– Consistent: Inconsistencies are graphically highlighted

Proteus export● Supports the newest scheme version 4.0.1

● Supports instrumentation

● New graphic user interface for the export

● Export settings can be pre-configured

● Exporting multiple documents without opening them

Signal display according to IEC 62424Signals can be represented and connected on the P&ID following the standard IEC 62424

Symbols from current standards are available in the project specificationThe context menu offers the use of symbols from the current international standards ISO 10628 and IEC 62424.

Updated interfaces● P&IDs are exported ISO 15926-compatible into the formats Proteus 4.0.1 and 3.6.0

● P&IDs are imported ISO 15926-compatible from the formats Proteus 3.6.0 and 3.3.3



● Design data are imported and exported from F.I.R.S.T. Conval 8 and 9

● Drawings are imported from Autodesk AutoCad file formats 2010 and 2013

2.4.13 FEED

Updated interfaces● Simulation import from Aspen Plus supports versions 8.8 and 9

● Simulation import from Aspen HYSYS supports versions 8.8 and 9

● Simulation import from PRO/II supports versions 9.4 and 10.1

● Simulation import from UniSim supports versions R440 and R451

● Simulation import from ProMax supports version 4.0

● Simulation import from ChemCAD supports versions 6.5 and 7.0

● Process data for the calculation of heat exchangers are exported to Aspen EDR V8.8 and V9, and the design data calculated there are imported

Process data for the calculation of heat exchangers are exported to HTRI V7.2 and V7.3, and the design data calculated there are imported

ProMax import The ProMax import has been extended: All phases in the material flows, column trays and components are now imported.

2.5 COMOS 10.2.3

2.5.1 Platform

ExportDB adaptation● ExportDB now supports more than 4 database connections – similar to the login in COMOS

itself.

● The user interface has been adapted and improved in terms of the workflow.

System monitor● The values for MaxLoadedObjects have been adapted to current operating systems.

● The user interface has been adapted.



2.5.2 COMOS Mobile Solutions● COMOS Web Server: New graphical user interface for easy configuration of the IIS

(COMOS Application Server Configurator)

● COMOS Web: Visualization of new and changed objects in the Navigator of the Projects app (working layer display)

● COMOS Web: Integrated PDF Viewer for iOS and Android tablets

● COMOS Web: PDF eSign in the Projects app

2.5.3 P&ID

AutoCAD text recognition for intelligent import of plant information (CAD)● Detection of single texts of an AutoCAD file as a text block

● Saving the AutoCAD text block information as a COMOS engineering object

● Link the generated engineering objects to the report with placed AutoCAD file. Navigation in both directions possible.

2.5.4 EI&C● Improved performance when checking in templates

● New report option for pre-defined lengths of cable symbols

2.5.5 Process Data Interface to Teamcenter/NX

Single Sign-OnYou can log into Teamcenter in COMOS 10.2.3 with Single Sign-On via COMOS. Various authentication methods are supported:

● PKI (for example smartcards)

● Two-factor authentication (for example one-time password)

● Domain-based authentication (for example NTLM)

These can be configured on the SSO server. The requirements for configuring the SSO server for the Teamcenter login can be found in the Teamcenter Administrator Manual.

The settings for the log on with Single Sign-On are carried out in the project properties in the "Teamcenter interface" category. If you do not configure Single Sign-On, you can log on as usual with user name and password.



Corrected errors or changed behavior 33.1 COMOS 10.2.3

3.1.1 Changed behavior of terminal strips in a diagramAs part of error rectification, the user interface and behavior for terminal strips was changed as follows:

The "Save" button was removed from the toolbar and the selected configuration for the view in the tab is saved automatically.

This change only applies when using connection objects.

Note

Please note: The selected configuration has a direct effect on the representation in the terminal diagram and is saved for the specific user.

3.1.2 Error listThe following list is only available in English.

ID TAC No. Component Description2516301 TAC=8979962 Automation Wrong wire information after implementation of potential rails2640827 Automation CM block and function block are overlapping each other2674800 TAC=9035771 Automation GSD Import on ABB_082D file not working1426953 TAC=7474128 Automation Cable application generates inconsistent line1705618 TAC=7705956 Automation Multiple selections can be placed despite blocking2404519 TAC=8934280 Automation The line information is lost after implementation2499921 TAC=8973523 Automation Error while distorting forced wiring2501890 TAC=8973469 Automation Fault at auxiliary circuit connections at parallel routed lines2516244 TAC=8979969 Automation Malfunction of cable core assignment at implementation log. Poten‐

tial2614677 Automation Docking connection is not created in expected time2633217 Automation Oblique connection after segment routing2634091 Automation No routing of dynamic connectors after changing base connection

via grab2640214 Automation UNDO after Rotate object with cable2657144 Automation Slant connection on function diagram and circuit diagram2657404 Automation Routing


2664449 Automation Cascade connection, move the line connection2664456 Automation Multi-pole cascade connections2749355 TAC=9062851 Automation Identification frame does not work in the COMOS Version 10.2.2.0.0

right2751641 TAC=8360973 Automation Error at polygons: Point 2. No new polygon can be created2782545 TAC=9077647 Automation Faulty evaluation of connection-dependent objects2481827 TAC=8967002 Automation eTask execution fails2533519 TAC=8961132 Automation SI0280B5.GSE: Standard telegram channels cannot be implemen‐

ted2725072 TAC=9052490 Automation CMDT06754 - Problem with dynamic blocks in function engineering2830983 TAC=8365477 Automation DEL Key shall only delete objects as in 9.2 and not additionally syn‐

chronize2751667 TAC=8360975 Automation Error at polygons: Point 3. Display error in the toolbar2782725 TAC=9059356 Automation Engineering task undo does not undo everything2800966 TAC=9081409 Automation Optional connection is not displayed correctly2830913 TAC=9080191 Automation Problem placing signals2658506 Platform eCl@ss / GDM: Predicates don't work with MultiLanguageStrings or

NULL values2751544 TAC=9060467 Automation Error at polygons: Point 1. Layout with 10.2.22620307 Mobile Solutions Task ID cannot be synchronized to an attribute of a COMOS task

object2465435 TAC=8954639 Mobile Solutions Plan end Date showing as 30.Dec.1899 for the very low priority task2637398 TAC=9027962 Mobile Solutions Error message when entering values for texts in number fields2677832 TAC=9023742 Mobile Solutions No picture display on chapter cards2705570 TAC=8991966 Mobile Solutions WEBPQM - Query inside the form has freezed (gray) scrollbar2295093 TAC=8854709 P&ID/Feed CMDT06108 - Problems with copying2539009 TAC=8990947 P&ID/Feed COMOS FEED Log Window for Aspen simulations is different be‐

tween two iDBs2539042 TAC=8990986 P&ID/Feed Converting PFD to PID deletes the original PFD drawing2584709 TAC=9004807 P&ID/Feed Create PFD step does not set HC links for air cooler and fired heater,

etc.2589928 TAC=9011641 P&ID/Feed Pro II Import: CurrentPseudoProds Import Log Message2590893 TAC=9012652 P&ID/Feed Case management does not work on subobjects2633973 P&ID/Feed Data missing in HYSYS import2635380 P&ID/Feed FEED PROMAX :- Attribute pressure increase value doesn't import

for 4Glycol Pump simulation object.2663452 TAC=9031798 P&ID/Feed KKS did not appear in 10.22705366 TAC=9043903 P&ID/Feed Import DGN produce COMOS crash (10.2 upwards and integration

1080)1934714 TAC=7822687 P&ID/Feed Navigating between pipe sections listed on two schemes2757097 TAC=8361530 P&ID/Feed DWG import problem with dynamic blocks2380679 TAC=8917457 P&ID/Feed KSS stream selection does not contain streams from Process Units2630036 PDMS Engineer‐

ing InterfacePDMS_1022: E3D crashes when right clicking on a particular object

2636098 TAC=8355694 PDMS Engineer‐ing Interface

Too much information displayed for process lines

Corrected errors or changed behavior3.1 COMOS 10.2.3


2775365 TAC=8362390 PDMS Engineer‐ing Interface

PDMS crashes when interface is not started in COMOS

2130449 TAC=7946671 Platform Slow down the response of the COMOS2332762 TAC=8891844 Platform Tab type in one line and @.NET User Control error2344453 TAC=8893583 Platform Definition of working areas using special characters and lower case

letters2380676 TAC=8899012 Platform Change at inherited GetDisplayValue script causes COMOS to

freeze2519472 TAC=8979014 Platform Mapping table - no reset of write protection2698049 TAC=9041029 Platform Use of range attributes in bulk processing dialog not possible2774771 TAC=9072047 Platform Conversion in queries still does not function2777625 TAC=8362576 Platform RLS client functionality defect in COMOS 10.2.21989733 TAC=7875731 Platform Database services - Headings in msg box or action buttons inter‐

changed2003635 TAC=7885868 Platform CopyAll from local template will not create Tpl pointers2023440 TAC=7885910 Platform Error with report template NOXIE import on SQL DB2204288 TAC=8007534 Platform Changed parameters for UpdateDocumentGroup and UpdateDocu‐

mentGroupForScript2206727 TAC=7999246 Platform COMOS 10.2.1 - "Create revision on change" does not work2448624 Platform ReportToExcel: COMOS Document tool will be defective after export

to Excel2466133 TAC=8961297 Platform Working layer enable in BTSC cannot be carried out2492169 TAC=8969828 Platform Attribute cannot be edited after blocking of the owner on the planning

page2535462 TAC=8982132 Platform Problems in the working layer release process2569026 TAC=8352441 Platform COMOS 10.2.2 PreRelease 114 (100 and higher) crashes when you

try to close it2583713 Platform Compatible fix for RQ2554625 and RQ1823835, XREF Novartis2737232 TAC=9056773 Platform Incorrect indexing of the DB during the changeover from 10.1 to

10.2.2949852 Platform SR= 1-3174215758 Runntime error1146082 Platform SR= 1-3501361866 Screen 2 remains minimized or is no longer

connected1490623 TAC=7547340 Platform Selection from combo box in queries is not case-sensitive.2495241 TAC=8971957 Platform Check for defined length for attribute values not performed2574168 TAC=8352848 Platform ODBC connections are not displayed when description is missing2589269 TAC=8988565 Platform Bulk translation query does not extract attributes on 10.1.3.7.0 ver‐

sion2750777 TAC=9063917 Platform No progress bar at the bottom of the taskbar2807110 TAC=8364112 Platform Bulk translator no longer displays attributes2438409 TAC=8948167 Platform SR= 1-4904311106 Database version is displayed incorrectly after

ExportDB2469691 TAC=8963752 Platform No identification of standard tables with duplicate names in working

layer2561861 TAC=8972704 Platform LCK-files are placed in different folders2618435 TAC=9006947 Platform Naming of working layers not obeying proper rules2662565 TAC=9033131 Platform Wrong display of linked date attribute



2696019 TAC=9029196 Platform The "Modification of name/identification" function does not work2783291 TAC=9076086 Platform Deactivation of script execution within script events results in kernel

error2813928 TAC=9088955 Platform Error message 'Object without cache entry' with attribute value defi‐

nition via script2824667 TAC=9077305 Platform Search manager also does not find objects under the start object2834082 TAC=9093085 Platform Performance problems with queries in BWN4-L22236803 TAC=8801047 Operations COMOS 10.1.3.5 does not close Excel.exe after closing Heat Curve

document2459600 TAC=8956271 Operations MRO resource management bug2535460 TAC=8943503 Operations Problems with CDI (INC2311691)2572620 PQM PQM: UI control can no longer be identified with Ranorex2327751 TAC=8835935 PQM Check-in of dwg file failed2435446 TAC=8344751 PQM 2. CAD Check-In of external documents is failing1202467 TAC=7259501 Report Line feed at vertical texts on report templates2133401 TAC=7781231 Report Display omitted list lines2288893 TAC=8338573 Report Issues related on the *revisions (issue 2)2405058 TAC=8935110 Report Content-based revision does not function2410523 TAC=8935192 Report Problem when printing different formats (A3/A4)2445511 TAC=8952958 Report Problem when setting the angle of an report object to zero2462000 TAC=8959251 Report Resubmitted AutoCAD Export ByLayer function is no longer working2467113 TAC=8936194 Report Performance problems with Windows 10 Client and Print2Me printer

as default2483898 TAC=8967165 Report PDF Export - Textbox option "Fit text" is not recognized by PDF

Export2537011 TAC=8988414 Report COMOS 10.1.3.7.0 - Revision monitoring not working2561645 TAC=8992216 Report Editable report field min/nom/max value (data sheets) --> inherited

values2561862 TAC=8997707 Report Licenses are checked out even if reports are opened read-only2567152 TAC=9001723 Report Licenses (Detail-ET) are checked out even if reports are opened

read-only2587721 Report COMOS printer: Queue File is always locked in Windows 20162599194 TAC=9002722 Report New CRPs cannot be generated via NetLogin2600628 TAC=8957235 Report Error at enable revision2619012 Report Final adaptations for Setup to comply with Open Source Licenses2635379 Report Background color filling for rectangle is not working2658767 Report New ini file is not opening automatically on "Save as" action2660361 Report Printed pdf page size is different when COMOS report printed with

AutoSelect setting2666257 Report Symbols BG color with hatching is not working.2680887 Report COMOS revision printer: iTX issue in cDB2709230 TAC=9045104 Report PDF bookmarks are mixed2717955 TAC=9050525 Report Color of revision rectangles2736872 TAC=8359886 Report Layers seem to be turned on in the DXF though they are set as OFF

in COMOS 10.2



2741884 TAC=8360324 Report The ComosRevisonPrinter is displayed incorrectly in the selection of the project options

2774442 TAC=9069843 Report Document tools don't work with COMOS Revision Printer2775787 TAC=9069966 Report PDF Export - Erroneous behavior related to ReportPicture scaling

setting949978 Report SR= 1-2383579464 9.1 Excel Refresh on Report950002 Report SR= 1-2952062994 No more size adjustment950565 Report SR= 1-1810356984 Drawpicture with .wmf file2445777 TAC=8918060 Report COMOS Revision has values revised that has been never saved2565766 TAC=8986041 Report EMF files display wrong on documents.2569413 TAC=9001796 Report Grab points missing when we use the PSV template in Comos 10.22615074 TAC=8540610 Report COMOS will stop working when opening one PID diagram2756094 TAC=9066110 Report Navigation from documents to attributes partly not possible2756432 TAC=9060848 Report Missing objects on P&ID with COMOS 10.2.22772706 TAC=9064359 Report Revision Printer connection with Ghostscript and redmon2786860 TAC=9078295 Report Comos Revision Printer revisioniert nur bei einem Anwender2797180 TAC=9080320 Report Document paging (successor predecessor) malfunction2831026 TAC=9093653 Report Objects set to invisible are displayed in an interactive report2600471 TAC=9015481 Teamcenter in‐

terfacePDI: Create workflow for material revision aborts with error message

2554872 TAC=8994658 Teamcenter In‐terface

PDI: relation not returned by Types.GetRelationTypes()


PDI: GetPropertyDatabaseValues() returns exception text


PDI: incorporate fix for error "impossible to set BOM line items"

2090028 TAC=7922891 Walkinside inte‐gration

Context menu "COMOS 3D Viewing" not visible

3.2 COMOS 10.2.2

3.2.1 Text field on a reportText fields on reports have automatic line breaks, depending on the setting.

As of COMOS 10.2.2 the following applies: Special characters, such as the hyphen, are placed before the line break.

This behavior is applied after the COMOS 10.2.2 installation to all text fields with automatic line breaks. This may change the presentation of text even without prompting.



3.3 COMOS 10.2.1

3.3.1 Behavior of RTF text fields in reportsThe representation of RTF text fields has been improved. As a consequence of this improvement, RTF text fields create different page breaks depending on the context condition.

Evaluating reports with RTF text fields may be changed by switching to COMOS 10.2.1 at the next update. These reports then also have new * revisions depending on the setting.

You can find additional information on this topic in the "Administration" manual, keyword "Placing rich text box".

3.3.2 Administration: Language dependency of attribute-based filters

TroubleshootingThe following error was corrected. In line with the previous version, which means existing filter attributes can be read and written with the previous problems and new filter attributes are correctly created and also read.

To solve this problem manually in your database, delete the filter attributes and edit them again.

Loss of filter setting at the change of languageFilters for units or selection list values can be set up for the attribute. The system-internal attributes @UnitNameFilter and @StdValFilter are used for this. You can find additional information on this topic in the "Administration" manual, keyword "Filtering the units at the attribute" and keyword "Filtering the selection list values at the attribute".

A language change also switches off the filters is some cases. All information of the engineering objects is retained. The only effect is that the units and selection list values are available to the user again unfiltered.

You have the following options:

● Apply the filter in the primary language. This makes the entry valid for all languages. Do not edit the other languages after this, to ensure that the entry in the primary language remains valid.

● Enter the same filters in all languages when preparing the filters.

● Replace the filter after the language change.



3.4 COMOS 10.2

3.4.1 Compressing COMOS dataThe "Compress COMOS data" function worked in blocks of 1000s in the past. 1000 data records are always deleted.

The block size for this function has been changed to 50,000. This has resulted in notable improvements of the performance of this function.

It is now also possible to configure the value. To this purpose the following entry has to be carried out in the LC_SETTINGS table:

Property name: BLOCK_SIZE_FOR_COMPRESS_DATABASE. The value then has to be a natural number.

3.4.2 Change markings in reportsAn error that prevented updating of the revision index has been corrected. This error caused change markings to be missing in the report.

The index is now also updated when the report is temporarily set to read-only during a background backup.

Corrected errors or changed behavior3.4 COMOS 10.2


Corrected errors or changed behavior3.4 COMOS 10.2


Discontinuations 44.1 Operating system

ID TAC ID

● Microsoft XP and Microsoft Server 2003 are no longer supported as of COMOS 10.2.This is a result of Microsoft's discontinuation of Extended Support.

● Windows Server 2008 R2 will be supported to the full extent for the last time with COMOS 10.2.2.The COMOS version in which the support of Windows Server 2008 R2 will be revoked completely had not yet been specified at the time of writing.

4.2 LCODBC32.EXE

ID TAC ID

The LCODBC32.EXE file has been removed from the scope of delivery. This means that SQL statements to the SQL database only still work if you use SQL Management Studio.

The following licenses are affected:

COMOS Platform

CIS:10355C

CIS:10355G

CIS:10355H

CIS:10355N

CIS:10355S

CIS:10355Z

4.3 Isometrics: ROHR2 export

ID TAC ID


Export to "ROHR2" is no longer available as of 10.2.1 in iDB and cDB.

4.4 COMOS Mobile DocumentView

ID TAC ID

COMOS Mobile DocumentView (SharePoint interface) is no longer available in COMOS 10.2.1.

The products "COMOS WebView" and "Mobile Document Review" are available for similar applications.

4.5 Sharepoint interface

COMOS DocumentView

ID TAC ID

The Mobile Solutions SharePoint interface is no longer offered or supported by COMOS 10.2.1.

If you have installed the SharePoint interface as part of an earlier COMOS version, you can obtain maintenance and care with the following service packs (10.2.1).

4.6 CVS and NewCVS

ID TAC ID

NewCVS is no longer supported. CVS3G is used instead.

The option exists to continue using CVS.

Discontinuations4.6 CVS and NewCVS


4.7 COMOS.dll

ID TAC ID

Workset: LogoCad() as Boolean

This property returns the status as to whether COMOS was started by LogoCAD.

The shared architecture of LogoCAD and COMOS is no longer supported. The LogoCad property must not be used any longer and will be removed in a future version of COMOS.

4.8 Discontinuations and functional limitations as of COMOS 10.2.0

ID TAC ID

General distinctions for customer-specific customizing

Interfaces and 3rd party components● The use of COMOS is only for approved interfaces and 3rd party components. This is also

valid for the COMOS classes and COMOS libraries: Only classes and libraries expressly approved for use are permitted to be used for custom COMOS extensions, scripts or programs. You can find more information in the online help.

Discontinuations and functional limits 10.2.0

COMOS ICA ClientCOMOS ICA Client is discontinued as Citrix client for the next version. The software will no longer be provided and the user documentation will no longer be supplied.

Recommendation: Use the ICA client of a third-party manufacturer for COMOS 10.2 because the COMOS ICA Client for COMOS 10.2 has only limited functional capability.

French localization:● As of Version 10.2 the French localization is no longer part of the scope of delivery:

– The user interface can no longer be switched over to French.

– New and changed objects in the iDB no longer have a French text.In the course of a database update, objects can also lose their French localization in the customer database.

– Customer-specific data retains the French translation.

– As usual, customers can carry out a database localization in French themselves.

Discontinuations4.8 Discontinuations and functional limitations as of COMOS 10.2.0


P&ID - discontinuation of supported third-party software versions● Starting with version 10.2 the older versions of the following third-party software versions

listed below are no longer supported:

– PDF Import Adobe <8

– XMpLant Import and Export <3.3.3

– Conval Import and Conval Export <8

– Autocad (DXF/DWG) Import <2007

– Microstation (DGN) Import <7

– PDS 2D Import <7

FEED - discontinuation of supported third-party software versions● Starting with version 10.2 the EbsilonProfessional import is no longer supported.

– In addition, starting with version 10.2 the older versions of the following third-party software are no longer supported:

– AspenPlus Import <7.3

– PRO/II Import <8.3

– AspenHYSYS Import <7.3

– UniSim Design Import <R400

– ChemCad Import <6.1

– ProMAx Import <3.2

– HTRI Import and Export <6

– AspenEDR Import and Export <7.3

Previous discontinuations and functional limitations to be separately noted

License server● The "SetLicPath.exe" file is no longer used.

If you wish to use a different computer than before for the license server, you must set the new server name on each client using the "<COMOS installation path>\config\Comos.LicenseLib.config" tool.

Printer driver of the revision archive● The following printer drivers are no longer available:

– Adobe Distiller

– Adobe PDF Writer

Discontinuations4.8 Discontinuations and functional limitations as of COMOS 10.2.0


4.9 COMOS PlantModeler (CPM) as of COMOS 10.2.0

ID TAC ID

The COMOS PlantModeler module is no longer offered or supported as of COMOS 10.2.

As regards content, this method has been replaced by an interface to the openPLANT Modeler, the openPLANT Engineering Adapter.

The Engineering Adapter differs functionally in its use of .idgn files for transferring data between 2D and 3D.

The data exchange is performed offline, in contrast to the PlantModeler.

Currently, the Engineering Adapter includes export of COMOS P&ID and process data to openPLANT.

4.10 Discontinuation of "Export reports to EMF" as of COMOS 10.2.0

ID TAC ID

Exporting reports to EMFThe "Export reports to EMF" interface is available for the last time in COMOS 10.2. The Windows 7 and Windows 10 operating systems do not correctly support the "emf" file format. A correction by Siemens is not possible because the file format "emf" is controlled by Microsoft. The function will therefore be discontinued with a subsequent service pack.

4.11 COMOS Express/COMOS ME Designer as of COMOS 10.2.0

ID TAC ID

The COMOS Express and COMOS ME Designer modules are no longer offered or supported as of COMOS 10.2.

No successor products are planned.

As regards content, intelligent template management for modular plant design has been provided by the last few versions in the form of engineering objects. If you have any questions, please contact your local sales or service representative. They will be happy to help and explain the possibilities of the latest technology.

Discontinuations4.11 COMOS Express/COMOS ME Designer as of COMOS 10.2.0


4.12 P&ID

Third-party softwareAs of version 10.2.2 the older versions of the following third-party software versions listed below are no longer supported:

● PDF Import Adobe <8

● Proteus Import <3.3.3

● Proteus Export <3.6.0

● Conval Import and Conval Export <8

● AutoCAD (DXF/DWG) Import <2007

● Microstation (DGN) Import <7

PDS 2D Import <7

Base object switch in functionsIn the cDB standard database, it was possible to switch the base object of a function in the P&ID report by changing the function code. This function required that "neutral function objects" were available in the database that only became a specific function by the editing of the function code.

Which the switch to the iDB this workflow is no longer supported. The iDB does not offer any "neutral function objects". This also means that there is no base object switch.

For reasons of compatibility, this function is still supported in COMOS 10.2.x for databases that were created based on the cDB standard database.

4.13 FEEDAs of version 10.2.2 the older versions of the following third-party software versions listed below are no longer supported:

● AspenPlus Import <8.8

● AspenHYSYS Import <8.8

● AspenEDR Import and Export <8.8

● PRO/II Import <9.4

● PRO/II Import 10.0 (see Known Issues)

● UniSim Design Import <R450

● ChemCad Import <6.5

● ProMAx Import <3.2

HTRI Import and Export <7.2

Discontinuations4.13 FEED


Known Issues 55.1 As of 10.2.3

5.1.1 Revision with COMOS HARPCOMOS HARP only supports the following COMOS document formats:

Excel, Excel 200, AutoCad drawing, Powerpoint, Powerpoint 2007, Word and Word 2007

To create revisions of all other printable document formats, use the COMOS revision printer, Adobe PDF or PDF Factory.

5.1.2 Problems occur with incorrect values in specifications using the mode “values in XML”.

In combination with XML specifications, incorrect values may occur under certain circumstances.

This may be the case if the CML specifications have been stored on the root page and are directly located under a document.

On account of an error (existing as from COMOS 10.1.3), the values have been stored at an incorrect location. This has been corrected, which has the effect that current COMOS versions can no longer find the old values.

In order to correct incorrect values, use the kernel functionality "Workset.RunDatabaseMaintenance 8192, [StartObject]" (DatabaseMaintenanceOptionFixXmlSpecValueLocation = 8192). Enter a start object to search for the specifications to be corrected. Try to select a start object with a very deep hierarchy to shorten the conversion runtime. If you are not sure where affected specifications may be located, enter the root project as start project. All working layers included in the project are automatically processed during the conversion process.

5.1.3 Net login method causes incorrect display on reportsWhen using the net login method, OLE objects are displayed very small after being placed on the report.

To be able to use OLE objects on the report as normal, enlarge them.



References to Mobile OperationsThe "Mobile Solutions" manual contains jump markers and references to the "Mobile Operations” manual.

This product is not included in the scope of delivery of version 10.2.3. Therefore, the manual has been removed and the references became invalid.

Example scripts for synchronization of activities and work packagesThe scripts shown in this manual for synchronization of work packages and activities are incorrect: "Mobile Solutions" manual, keyword "Creating a script for synchronization of COMOS with COMOS Web".

The following example scripts are correct.

Example script for work packagestaskType = "Mobile Operations Workpackage"

Set serviceClient = CreateObject("Comos.TM.Services.ComClient.TasksServiceClientCOM")

If Not serviceClient Is Nothing Then

Set dict = serviceClient.CreateTaskPatchCollection()

dict.SetField "Name", "ComosSync_" & Device.Name & " " & Device.Description

dict.SetField "TaskType", taskType ' additional inital values for TaskFields can be added

id = serviceClient.CreateTask(dict)

If id > 0 Then

serviceClient.SetSyncForTask id, Device

Project.Workset.Lib.Output "Created new Web-Task <#" & id & "> of type " & taskType

End If

End If

Example script for activitiesparentTaskId = ID des Task

taskType = "Mobile Operations Activity"

Set serviceClient = CreateObject("Comos.TM.Services.ComClient.TasksServiceClientCOM")

If Not serviceClient Is Nothing Then

Set dict = serviceClient.CreateTaskPatchCollection()

dict.SetField "Name", "ComosSync_" & Device.Name & " " & Device.Description

dict.SetField "TaskType", taskType



'additional inital values for TaskFields can be added

dict.AddLink "Hierarchical", 1, parentTaskId

'additional inital values for TaskFields can be added

id = serviceClient.CreateTask(dict)

If id > 0 Then

serviceClient.SetSyncForTask id, Device

Project.Workset.Lib.Output "Created new Web-Task <#" & id & "> of type " & taskType

End If

End If

5.1.5 Installation of service packs via the Update Center

New project options are missing after installation of a service pack via the Update CenteriDB project options are managed in the file, projectsettings.xml. This file is located in the Config sudirectory of the installed COMOS version.

When installing a service pack via the Update Center, the files of the existing Config directory are applied to the new installation and not the new files from the Config directory of the new service pack.

As a result, the options supplied with the new service pack for the first time are not visible in the user interface.

To remedy the problem, you can manually copy the projectsettings.xml file from the new service pack to the Config directory of the installed COMOS version. If you have added features to the projectsettings.xml file, you must integrate your entries once again in the new projectsettings.xml file.

5.1.6 Contents of the help textsWith COMOS 10.2.3 there was a conversion in the development process that was designed to make it more agile.

For technical reasons, this affects the help texts supplied. This means that not all manuals will be updated for each version any longer, just the content that has a direct relation to a new development or error rectification.

For this reason, all contents that are supplied with the software will continue to be documented. There may however still be manuals that contain outdated context information or references to information that no longer exists.



Corrections to information from the manuals

Manual/chapter SIPS topic ID Revision options: Specify revision archive (specify print format)

50349922571 Removed (outdated):All necessary components for this (fixed initialization file, Postscript printer driver, Redirection Monitor, Ghostscript) are provided in the COMOS in‐stallation package. The COMOS revision printer can therefore be used without additional management.

5.1.7 PDF Docu Pack Adobe has changed the security settings for PDF files. As a result, you cannot currently use the full text search (.pdx) from network resources. As a workaround, we recommend that you copy and use the Docu Pack locally.

5.1.8 Installing help in silent modeCurrently, help is not automatically installed when using the COMOS Silent installation.

Workaround:

1. Open a DOS box as a Windows administrator

2. Navigate to the directory that contains the setup of the corresponding help.

3. Now use the following call in the DOS box:Setup.exe /s /l1033/v"/qn 1033 is the language code for English. 1031 = German, 1032 = Chinese

5.2 As of 10.2.2

5.2.1 Restrictions for Excel interfaces due to MS security updatesAfter installation of the following Microsoft Windows security updates (October 2017), some Excel interfaces are no longer working with COMOS.

● KB4041676 on Windows 10 & Windows Server 2016

● KB4041681 on Windows 7 & Windows Server 2008R2

● KB4041693 on Windows 8.1 & Windows Server 2012R2



This affects central functions for opening and creating Excel files.

In COMOS, this affects, for example, export of a query to Excel (xls) or the standard import from Excel.

Correction in updates since 14 November 2017Microsoft has solved the problems caused by its most recent security updates. The restrictions no longer apply in COMOS with the latest security updates (as of 14 Nov. 2017).

You can find more information on the Microsoft support pages:

Windows 7 Update Info: https://support.microsoft.com/de-de/help/4048960/windows-7-update-kb4048960

Windows 10 Update Info: https://support.microsoft.com/en-us/help/4048954/windows-10-update-kb4048954

Windows Server 2012 Update Info: https://support.microsoft.com/de-de/help/4048962/windows-server-2012-update-kb4048962

Windows Server 2016 Update Info: https://support.microsoft.com/de-de/help/4048953/windows-10-update-kb4048953


eSign signatures are not displayed in the Redlining editor in Mobile SolutionsWhen you have signed a revision with "eSign in PDF" and then open the revision in the Redlining editor, the signature is not shown. If you save a redlining of the revision nonetheless, the signature is deleted.

You can find additional information on the redlining editor in the "Mobile Solutions" manual, keyword "Creating redlinings in COMOS Web".

Faulty display with minimized user interfacesContext bars and the navigator in the "Projects" tile are displayed incorrectly if parts of the user interface are minimized. This can happen if the user interface is opened on a small screen or if you reduce sections by moving splitters.

Redlining PDF does not work on the iPadRedlining PDF can currently not be saved on an iPad and thus cannot be used on an iPad.

Login in iPad App "Mobile Document Review" not possible if password contains "@"You can not log into the "Mobile Document Review" iPad app, if the password contains the character "@". If you use the app, create an app without that character.



Redlining● Tablet: Touch does not work correctly on tablet (Windows tablet with Edge browser)

● Tablet: Freehand drawing aborts at the first two points and then functions properly thereafter.

● Changing size of freehand drawing (PEN) does not work

5.2.3 OperationsResources (persons or material) are not supported with bidirectional data exchange between MS Project / Primavera.

Only qualifications and qualification requirements are currently supported.

Data exchange with MS ProjectWhen a task which has no duration is imported from COMOS to MS Project, and qualifications have been assigned (with zero man hours) to the task, MS Project converts this task into a milestone. This is the standard behavior of Microsoft Project and can most likely not be altered

As a work-around remove the qualifications. Then the task is also imported as a task without duration.

5.2.4 Basic

Defective configuration of a document base objectIf the properties of a document are incomplete or empty, follow these steps:

1. Switch to the base project.

2. Open the properties of the associated document base object.

3. Select the "Configuration" tab.

4. Apply any entry from the "Default components" list to the "Current components" list.Save the base object.This step internally creates a new configuration.

5. Remove all entries from the "Current components" list.Save the base object.This step resets the configuration to the factory state.

6. Edit the configuration as desired.Save the base object.

Effect on performance for devices with touch inputTouch-enabled devices are tablets or touch monitors, for example.

The following applies to this device class:



If the "Script" tab is displayed in the properties of an attribute, performance may drop.

5.2.5 COMOS HelpThe COMOS Help currently cannot be opened using Microsoft Edge as a browser.

This is due to Active-X controls, which are no longer allowed in Edge.

Use another approved browser. We recommend Internet Explorer 11.

5.2.6 Frame setup

TerminologyThe terms "COMOS Suite" and "Frame setup" have not yet been included consistently in the COMOS documentation. The terms previously used such as "COMOS Portfolio" and "Setup Browser" will be replaced in future updates.

Comparison of the "Frame setup" and "UpdateCenter"COMOS 10.2.2 can be installed as follows:

1. Starting the Setup.exe of the COMOS frame setupYou can find additional information on this topic in the "Installation and Configuration" manual, keyword "Installing COMOS with the installation wizard".

2. Using the UpdateCenterUpdating of COMOS 10.2.0 and COMOS 10.2.1 is supported.You can find additional information on this topic in the "Installation and Configuration" manual, keyword "Installing COMOS updates".

Both types of installation have specific advantages and disadvantages.

Installation by means of the Setup.exe of the COMOS frame setup● The COMOS frame setup also makes additional components available, for example,

Redistributable files.If the requirements of the compatibility matrix are observed, an installation by means of the COMOS frame setup is executable without further administration.

● The new COMOS version is entered in the registry.If additional software is offered in COMOS frame setup that runs together with COMOS Version 10.2.2, this software can be installed as well in one step.The additional software can be listed in the COMOS frame setup in the "COMOS Main" group of the "AddOns" group.

● The current documentation can be installed optionally as well.



● The installation of COMOS 10.2.2 is carried out parallel to the existing COMOS version. Both versions are executable.

● The COMOS frame setup also updates the UpdateCenter.The two versions of the UpdateCenter differ as follows:

– UpdateCenter for COMOS 10.2.0 / COMOS 10.2.1: Allows only updates on the basic installation COMOS 10.2.Updating of COMOS 10.2.0 and COMOS 10.2.1 to COMOS Version 10.2.2 is supported.

– UpdateCenter for COMOS 10.2.2: Allows updates for COMOS 10.2.2

Installation by means of UpdateCenter● The installation can be carried out without having administrator rights on the client.

● The installation adopts customized configurations of the COMOS version that is to be updated.

● If the COMOS installation instructions were observed, the following applies:The update is offered instead of the predecessor version on the client. Users do not have any selection option.

● The current documentation is installed automatically.

● The operating system environment is not updated automatically.Whether the operating system environment is prepared accordingly depends on the customized environment. The older the COMOS version that is to be updated, the higher the likelihood that additional Redistributable files may be required. In this case COMOS 10.2.2 signals which files are required during the start by means of the message "COMOS: Installation error".

● The registry remains unchanged, so that the entry of the predecessor version remains active.As a result, the desktop link is retained.

Additional information● If the installation is carried out by means of the UpdateCenter, and installation by means

of the COMOS frame setup is started in a second step, the following applies:The existing installation of the Service Pack update via the UpdateCenter is not recognized by COMOS frame setup because the UpdateCenter does not make any changes in the registry.

Teamcenter interfaceWhen a query is issued for existing installations the component "Teamcenter Client and Server", abbreviated: TCCS, can currently not be taken into consideration for technical reasons. Whether TCCS includes a pre-installation is therefore not displayed correctly.



5.2.7 FEEDThe version 10.0 of PRO/II does not provide 2D coordinates for the equipment. Therefore automatic placement of the equipment does not work. This error was fixed by SimSci in the PRO/II version 10.1.

5.2.8 P&ID

Special features of reducersReducers have the following attributes:

● "Design data" tab: "Nominal diameter 1" and "Nominal diameter 2"

The following applies on P&ID reports: The reducer is automatically rotated, if necessary, to perfectly match the existing nominal diameters of the pipe and the components. For technical reasons, the attributes "Nominal diameter 1" and "Nominal diameter 2" are also swapped in this case. This means the larger nominal diameter can be entered in "Nominal diameter 1" as well as "Nominal diameter 2".

The following applies to isometric reports and pipe spec mapping: "Nominal diameter 1" always contains the larger nominal diameter.

If the "P&ID" module is used together with one of the "Isometrics" or "Pipe spec mapping" modules, you must ensure that the larger nominal diameter is entered in "Nominal diameter 1" for all reducers.

5.3 Older versions

5.3.1 Uninstalling HARP printer and COMOS revision printerThe uninstallation can currently not be implemented through the Frame setup. Uninstall the printers manually.

5.3.2 Uninstallation of the Teamcenter interfaceThe uninstallation can currently not be implemented through the Frame setup. Uninstall the interface manually.

5.3.3 Compressing and repairing the database

ID TAC ID1619144

Known Issues 5.3 Older versions


COMOS menu: "Administrator > System > Data maintenance (support)": "Database services: Compress this database"

This function is currently not available.

5.3.4 Copying AutoLoops

ID TAC ID

The current version of the iDB database has the "OnSaveDone" script at the base object of the AutoLoop document. This script can unnecessarily initiate a query regarding the insertion location of copied objects.

The script can become effective as follows:

● You create a new database based on the iDB supplied as part of COMOS 10.2.1.

● You apply the content of the iDB supplied as part of COMOS 10.2.1 to your database by means of a database update.

When the script becomes effective, an error can be triggered when an AutoLoop is included in the copy set. An AutoLoop can become part of a copy set as follows:

● You copy a branch in the Navigator in which an Autoloop document is created.

● You copy objects to a report that are connected to an AutoLoop.

5.3.5 HTML help system

Displaying blocked contentsWhen you open the help system, it is possible that a button "Display blocked content" is displayed in the lower section of the window. This button result from the security settings of your operating systems.

If you do not confirm the prompt, it is hidden again after a few seconds and no content is displayed in the help system. In order to view the content open the help system again and confirm the prompt.

5.3.6 Construction of a bypass for pipes with special direction

ID TAC ID



When the pipe is aligned in special direction and you create a bypass with the connector tool, the T-pieces are not created automatically.

Proceed as follows:

● Place the two T-pieces in the pipe manually.

● Select the bypass in the connector tool.

● Connect the two T-pieces.

5.3.7 Zoom function in redlining documents

ID TAC ID

If a zoom greater than 300% is selected in a redlining document, the document content is no longer displayed.

This behavior occurs in all situations in which a document can be zoomed.

5.3.8 Installing .Net Framework

ID TAC ID

.Net Framework on Windows 10Delivery state of Windows 10:

● .Net Framework 4.5 installed

● .Net Framework 3.5 not installed

COMOS requires .NET Framework 3.5 to be installed and activated. A limited compatible successor version of .NET framework is not enough.

Before installing COMOS on Windows 10, check if .NET Framework is installed on Windows and is activated. Also install and activate .NET Framework 3.5, if this version is not available.

.NET Framework on Windows Server 2012 R2If the installation is not successful, install and activate NET Framework 4.6.1.

Requirement: Windows hotfix KB2919355 is installed.



Change following deadlinePlease also into account the change following the deadline on this topic.

See chapter AUTOHOTSPOT.

5.3.9 Export polyline to AutoCAD

ID TAC ID

Intelligent COMOS lines cannot be generated in AutoCADCOMOS has connecting lines that automatically create a polyline (a parallel double line) when drawing. Example:

Shell connections in P&ID:

● A main line is created for the connection when drawing

● A secondary line is created for the shell when drawing

When exporting to AutoCAD, the polyline is transferred as a line marking instead of a graphic. Because AutoCAD has no polylines, the parallel double line cannot be transferred to AutoCAD with a single line marking.

Check the result in AutoCAD if the export contains polylines.

5.3.10 noxieFolder

ID TAC ID

With Drag&Drop or the manufacturer devices selection, an object (noxieFolderForBackupAndRestore) is created in the Elements tab, which is sometimes not necessary.

5.3.11 New calculation method for *-revisions

ID TAC ID



The automatic generation of *-revisions has been developed further as of COMOS 10.2. *-revisions are now additionally generated automatically.

● Let an attribute with the example name "Test" be given.

● The Value or XValue of the "Test" attribute is displayed in a report.

● The Value/XValue is set by one of the two following methods:

– Properties of the attribute, "Link" tab: "Value > Fully dynamic": Value/XValue was changed at the source attributeor

– Property is inherited from the master data: Value/XValue was changed at the attribute of the base object

In older COMOS versions no *-revision was generated because the "Test" attribute is unchanged from the view of the object model. Now a *-revision is generated, because the Value/XValue has changed on the report from the user point of view.

5.3.12 Administration: Required versions of CLS and RLS

ID TAC ID

A modified license check is used as of COMOS 10.2. The following therefore applies in COMOS 10.2 and later:

● You must use a license server 2.0 or higher.

● You must use RLS 3.9 or higher.

5.3.13 Administration: Increasing the document version

ID TAC ID

When switching to COMOS 10.2, Siemens recommends increment the document version as soon as possible. Incrementing the document version activates new background technology for generation of the Report.LID. The older version Report.LID is retained, but all the new Report.LID are then generated according to the new technology. The Report.LID identifies the elements placed on the reports.

Technical backgroundWhen the document version is incremented, you can no longer access the database of old COMOS clients. Therefore, there may be reasons specific to your company for delaying the incrementation of the document until a later date.



The old technology for generating the Report.LID has a limited number range. If the old technology is used over a longer period of time, it is possible that duplicate Report.LID will be generated. This can lead to follow-up errors.

5.3.14 Administration: Font for display of attributes

ID TAC ID

A font can be set for attributes as follows:

1. Properties of the base object, "Attributes" tab

2. Activate "Design mode"

3. Select attribute

4. "Properties > Display of the attribute" shortcut menu

5. "Properties of attribute title" group "Font/color" option

Do not use fonts with Unicode characters (e.g. Asian font names)

BackgroundIf an Access mdb is used in COMOS, attributes with Unicode fonts can initially be created. However, this type of project can no longer be transferred to MS SQL or Oracle.

5.3.15 Administration: Copying the base project

ID TAC ID

Adaptation of absolute file nameIf a base project is being copied using Copy&Paste, the following applies:

● Check whether hierarchically generated documents are correct. Hierarchically generated documents are created, for example, when a row report is integrated in a report template or when headers and footers are generated using a subreport.

Background:

The path information in absolute file names is adapted during the copy operation. If some document parts (headers, footers) are displayed incorrectly in the copy of the base project, this is due to unadapted path information in the corresponding report template. To correct this, check the file name or the file name of the undisplayed document parts in your report template.



5.3.16 Administration: Editing the "IsRequest" property on Device

ID TAC ID

The "IsRequest" property in older COMOS versions was set exclusively on the CDevice. The following options were provided:

● Editing the "IsRequest" property per script on the CDevice

● Properties of a CDevice, "System settings" tab: "Request" option.

The Device inherits the "Request" option and the "IsRequest" property from the CDevice. The property could not be edited with either the COMOS interface or per script on the Device. That is why a script line such as the following line has no effect up till now: Device.IsRequest = Device.CDevice.IsRequestAs of COMOS 10.2: The "IsRequest" property can be edited on the Device. This means these and similar constructions as exemplified by the script line above take effect with the change to COMOS 10.2. Company-specific scripts should be checked for the existence of such artifacts that were ineffective in the past.

The "Request" option continues to be available in the interface only for CDevice.

5.3.17 Troubleshooting of excessive GDI resource consumption

ID TAC ID

Problem descriptionCOMOS may use too many GDI resources on different operating systems. This causes an incorrect display of the user interface or individual elements of the user interface in COMOS under certain conditions. This affects mainly queries and evaluating reports.

In Task Manager of the operating system, you see that the number of GDI objects has reached or exceeded 10,000.

TroubleshootingMicrosoft provides the hotfix KB2719248. Install this hotfix if you observe GDI resource consumption by COMOS that is too high.



5.3.18 ElementName Z

ID TAC ID

Inheritance of object to parent device

NoteDo not use Z as object name.

When an object with the name Z is created below a device, the installation/3D data are applied to the device.

This is also the case when the object name is changed to Z.

Example: A varistor is created below an auxiliary contactor. It is renamed to Z. Different assembly data is entered for the varistor. This data is now also applied to the auxiliary contactor.

Functionality is tied to this naming process.

5.3.19 Interfaces: CDI

ID TAC ID

CDI exclusionsCDI cannot process DVM documents.

● CDI and DVM save changes at different times.

● CDI and DVM use a different hierarchy when accessing documents.

5.3.20 Interfaces: "Export reports to EMF"

ID TAC ID

The function of the "Export reports to EMF" interface is not guaranteed as of COMOS 10.2. The Windows 7 and Windows 10 operating systems do not correctly support the "emf" file format. A correction by Siemens is not possible because the file format "emf" is controlled by Microsoft.



5.3.21 GSD interface

ID TAC ID

The GSD interface evaluates text information as it is stored in the GSD file. For some GSD files it is possible that the module name, for example, has leading or trailing spaces that are applied in COMOS.

During data exchange with other systems problems can arise if the spaces are filtered by the system. In SIMATIC PCS 7 this results in a replacement of the modules not being possible (for example: PA139720.GSD).

Recommendation: As a workaround, delete the respective space in the COMOS object property.

5.3.22 Word export

ID TAC ID

Export reports to WordExporting reports to Word is designed only for one or a maximum of two pages.

This function is not enabled for larger reports and pages numbering more than two in Word.

5.3.23 Report templates dependent on working layers

ID TAC ID

The "Report templates depending on working layers" function is available if an iDB type database is used.

You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Creating a working layer-dependent template file in COMOS".

When a cDB is used, the full range of functions is not available.



5.3.24 Shutdown

ID TAC ID

PlatesPlates are not supported.

5.3.25 MRO

ID TAC ID

Sending e-mails via Maintenance DemonSending e-mails via Maintenance Demon in connection with the Enterprise Server is only possible via SMTP.

"Direct" pluginIncidentals and the corresponding "Incidentals" option are not currently supported.

5.3.26 Integrated Engineering

ID TAC ID

Reengineering of control modules including functions or standard functionsWhen you import a new control module that includes two functions or standard functions of the same type from PCS 7 and would then like to reengineer it, start by first importing and reengineering the control module and then the functions or standard functions.

"Assembly Updater" pluginWhen you update instances with the "Assembly Updater" plugin, the instances receive a new system ID. For renamed objects to be recognized again during data exchange, synchronize the ID with PCS 7.



Closing referencesWhen references are closed, the project name is not considered. If you use identical hierarchy levels in two projects and wish to close a reference across projects, the reference may not be closed correctly in certain circumstances.

5.3.27 Collisions in connection with Updateability function

ID TAC ID

If Siemens objects are checked in in the released area using the "Check in to current working layer" function and are then not changed in Customizing, collisions are wrongly shown when these exact objects are imported again via Updateability.





Changes following deadline 66.1 Introduction

In this chapter, deviations from the supplied user documentation are listed.

6.2 COMOS Platform

6.2.1 Administration

The new interface for "ExportDB" / "ExportDB" supports more than 4 ODBC connectionsThe following applies for the "ExportDB.exe" program in the "\BIN" directory in the COMOS root directory:

● The user interface is now customized more strongly to the workflow and is more intuitive.The new interface focuses more on the effect of the "Include working layers in export" option. This option influences which projects are offered for the export and which data are exported.

– Activated: The working layers are exported.When you select this option, all working layers are exported for all selected projects. Note: You have to activate the option to export a project in which the released area is connected to a base project working layer.

– Deactivated: Only the released area is exported.The list only includes projects that do not use working layers and for which the released area of the project references the released area of the base project.

● In the case of incomplete data the "Next" button is blocked.

● Any name suffixes are supported for the SQL instance. Therefore more than 4 instances are now offered.


System monitorThe following applies to the "Extra > Monitoring > System monitor" tool:

● "Maximum no. of loaded objects"The value selected for "Maximum no. of loaded objects" determines from what point the cache is to be emptied. The recommended limit for the maximum number of objects to be loaded depends on the amount of free memory available.Default:

– Default value: 500,000

Select one of the following two options:

– Select an entry in the list.

or

– Click in the field and enter a value.Minimum permitted value: 100 000Maximum permitted value: 3 000 000.

When the value is set for the first time, the default value "500.000" is set.

If a value below the minimum value of "100.000" is set at the COMOS start, the minimum value is set.

Function exclusions for Network LoginThe "Network Login" function is not designed to work simultaneously with two databases.

Therefore, for example, ExportDB is not supported in combination with "Network Login".

Interaction with user rights in the file systemCOMOS data must not be placed in folders with the "Hidden" property.

Archiving a project● The archive container has been changed from Zip to 7z.

During archiving a window of the 7z container appears several times. Do not close this window manually.

● COMOS must not be launched from a directory addressed via UNC (uniform naming convention).

Classifications

NoteNo different classifications per working layer

Classifications have to be unique within a project. You may not use different classifications for the same base objects or engineering objects derived from these in different working layers.

Changes following deadline6.2 COMOS Platform


Technical backgroundThe following functions are available to transfer classifications to engineering objects:

● Administrator > Update Classification > Current project

● Administrator > Update Classification > All projects

● Administrator > System > Data maintenance (support) > DB utilities

● Administrator > System > Data maintenance (support) > Project utility

When the classifications for a project are updated the transferred classification applies for all working layers of this project.

Technically, therefore, base working layers can be generated with different classifications, but the classification update results in all working layers having the same classification on the engineering side. This results in a deviation between the classification on the engineering side and the classification on the associated base working layer. This status is impermissible.

Starting the Enterprise Server with AssemblyImplement a memory management in your assembly file.

Example: System.Threading.Thread.CurrentThread.Join(100);

Particular aspect in the project property "No evaluation of rights for object display"The project property "No evaluation of rights for object display" can reduce the number of displayed objects in an object query.

In COMOS versions before 10.2.2 there was an interaction with a property in the object query:

● Context menu in the column header of the query: Options: "Administration" tab: "Extended" mode:"Table" row: ActionScript, extended object"

If the line "Table: ActionScript, extended object" was set to "Disable", the following applied: The project properties were not evaluated. This interaction prevented the activated project property from reducing the number of displayed objects.

As of COMOS 10.2.2 the following applies: There is no interaction anymore.

Installation of the "KernelExtension" interfaceName template for KernelExtension:Comos.Kernel.Extension.<name>.dllExamples:

● Permitted: "Comos.Kernel.Extension.ExampleExtension.dll"

● Not permitted: "Comos.Kernel.Extension.dll"

The components have to be stored directly in the "\bin\custom\extensions\kernel" folder. Subfolders are not permissible.



"Load from file" menu for queriesIf the "Load from file" menu is not available, contrary to the other settings, you also grant the user the function right "Base data".

Triggered script blocks when using "Move"The "Move" context menu command is available in COMOS if the context menu command "Copy" or "Cut" has been used before. The "Move" context menu command itself consists of a combination of the two context menu commands "Cut" and "Paste".

This results in the following conceivable workflows:

● "Copy" context menu command + "Move" context menu commandTriggered script blocks: "CanBeCopied" + "CanBeCut", "IsPaste..Allowed", "AfterPaste..."

● "Cut" context menu command + "Move" context menu command"CanBeCut" is omitted in the "Move" context menu command in this case and is therefore only triggered once.Triggered script blocks: "CanBeCut" + "IsPaste..Allowed", "AfterPaste..."

6.2.2 Operation

Queries: Run mode "Simple"● "Find" button

– The button is visible when the "Search at once" option is disabled in the "Extended" run mode.

– The button is invisible when the "Search at once" option is enabled in the "Extended" run mode.

● "Start object(s)" field

– The field is visible when the following option is enabled in the "Extended" run mode: Context menu in the "Options" column header: "Input layout" tab: "IncludeMainObject" row to "Visible"

– The field is invisible when the following option is enabled in the "Extended" run mode. Context menu in the "Options" column header: "Input layout" tab: "IncludeMainObject" row: "Visible" disabled

● User input at a query with the "Database search" propertyQueries with the "Database search" property can have the following setting:"User can enter value" or "User must enter value"In both cases an additional field for the user input is displayed in the "Simple" mode.



6.2.3 Class documentation TcIntegrator_dllThe following information supplements the documentation for "Class documentation TcIntegrator_dll".

"Query" classThe "Query" class is available on the TcHandler. It provides functionality for querying objects.

public static class Query { public static KDictionary Objects(string typeName, string objectName, string scope = "WSO_scope_All"); public static KDictionary ObjectsByName(string objectName, string scope = "WSO_scope_All"); public static KDictionary ObjectsByType(string typeName, string scope = "WSO_scope_All"); }

ObjectsReturns objects based on their type and name

typeName: Specifies the name of one or more types. Objects of this type are returned. "*" can be used as a wildcard, for example "Item*" returns objects of the types "Item", "ItemRevision" as well as "Item Master Form", etc. Queries with only "*" can sometimes take a long time, because very many objects are queried. See also "GetTcType".

objectName: Specifies the name of one or more objects. "*" can be used as a wildcard. Queries with only "*" or ""can sometimes take a long time, because very many objects are queried.

Scope: Scope of the search within Teamcenter. WSO_scope_All = Entire database. WSO_search_Approved = Object must have at least the "Approved" status.

A KDictionary with identification key is returned from Teamcenter and a text describing the object, referred to as Object_string the Teamcenter.

Example:

Set test = a.workset.getctisession.tchandler.query.objects("Item", "Test")Output test.countFor i = 1 To test.count Output i & ": " & test.key(i) & " - " & test.item(i)Next



ObjectsByNameLike Objects with typeName = "*", searches for all objects by the name, regardless of type. Queries with only "*" or "" can sometimes take a long time, because all objects are queried.

Example:

Set test = a.workset.getctisession.tchandler.query.objectsbyname("Test")Output test.countFor i = 1 To test.count Output i & ": " & test.key(i) & " - " & test.item(i)Next

ObjectsByTypeLike Objects with objectName = "*", searches for all objects by the type, regardless of name. Queries with only "*" can sometimes take a long time, because all objects are queried.

Example:

Set test = a.workset.getctisession.tchandler.query.objectsbytype("Item")Output test.countFor i = 1 To test.count Output i & ": " & test.key(i) & " - " & test.item(i)Next

Update to the "Classification" chapterThe current content of the chapter is as follows.

"Classification" class The class contains functions for querying classification information from Teamcenter.

public static class Classification { public static string AddClassInComos(IComosBaseObject tcObject, IComosBaseObject tcClass); public static string ExportClassAttributeValues(IComosBaseObject tcObject, string classId = null);



public static string ExportClassificationInfo(IComosBaseObject tcObject, string classID = null); public static string ImportClassAttributeValues(IComosBaseObject tcObject, string classId = null); public static string ImportClassificationInfo(IComosBaseObject tcObject); public static string ImportTcUoM(IComosBaseObject stdTableTcUom = null, string stdTableRootPath = "", string stdTableName = "", string tcUoMClassId = "", string additionalUomAttributes = "", string separator = ";"); public static string RemoveClassInComos(IComosBaseObject tcObject, IComosBaseObject tcClass); }

AddClassInComos and RemoveClassInComosAdds or removes the classification information for a COMOS object.

The parameters in both cases are:

tcObject: A COMOS object to which an object is assigned in Teamcenter

tcClass: A COMOS object under "@20 | B60 | M06 | Y30 | A10 | A20 Teamcenter classification" that represents a Teamcenter classification.

ExportClassificationInfoTransfers the classification information created in COMOS to Teamcenter.

ImportClassificationInfoQueries information for an object previously classified in Teamcenter.

ExportClassAttributeValuesTransfers the values of the classification attributes for a COMOS object that is connected to a classified object in Teamcenter.

ImportClassAttributeValuesQueries the values for all classification attributes for a COMOS object that is connected to a classified object in Teamcenter.

ImportTcUoMImports measuring units from Teamcenter and writes them to a dedicated standard table in COMOS.



6.2.4 Report

Deleting objects under a document on the diagramIn order to only graphically delete components under a document the option can now be activated at the base object on the "System data" tab via the attribute Y00T00001.Y00A07334.

To this purpose the value of the attribute has to be set to 1. Then only these are removed when the graphics is deleted. The database object is retained under the document.

Objects can be graphically deleted by using the <Del> key or per shortcut menu. In the shortcut menu you then have the choice whether the object is to be deleted only on the diagram or also from the database.

6.2.5 COMOS License ManagementThe information about the supplied versions of the following components is outdated in the manuals:

Installation Version in manual Delivered versionCOMOS LS 2.0.5 2.0.7COMOS LS Monitor 1.7.2 1.7.3COMOS RLS 3.9 3.10

6.3 COMOS Process

6.3.1 FEED

Multiple import of a design caseChapter 8.4 of the "FEED Operation" manual describes how an additional design case is imported.

To import the same design case multiple times, proceed as follows:

1. Create an additional "SIMCASE002 simulation case" SIMCASE object in the "A10 Simulation data" folder.

2. In the context menu of the "SIMCASE002 simulation case" object, create the "ASPEN XML simulation import" object.

3. Open the properties of the "ASXI001 Aspen XML simulation import" object.

4. Select the "Import options" tab.

5. Activate the "Update connection on 2nd import" option.

Changes following deadline6.3 COMOS Process


6. Import the design case as usual.The assignment between the imported information and the generated COMOS objects is based on the SIMCASE and the name.

7. Edit the additional steps as usual.

If inconsistencies are visible on the report, proceed as follows to remove the inconsistencies:

1. Open the report of the "Process flow diagram" type.

2. Select the process stream.

3. In the context menu, select the command "Options > Accept connections from drawing".

Affected manual chapters:

● "FEED Operation" manual, chapter 7.4 "Creating a simulation case (SIMCASE)"

● "FEED Operation" manual, new chapter 8.5 "Importing a design case multiple times"

6.3.2 P&ID

Using the symbol bar to create a measurement functionIf you want to use the automatic docking of measurement functions at vessels, press the "<Ctrl>" key additionally when selecting the measurement function.

"Proteus export" category: "File name pattern""Schema file directory"

Determines the schema file. The Proteus schema is read from this file.

Permitted placeholders:

● ${AliasFullLabel}● ${Description}● ${FullLabel}● ${FullName}● ${Label}● ${Name}● ${PathFullName}● ${SystemUID}Replacement of special characters:

● < > : / \ | ? *● ASCII control characters (char)0 to (char)31

are replaced with

● _



Multiple blank characters are permitted.

Example:

● ${PathFullName} . ${Name} ${Description}Default:

● ${FullName} (${SystemUID})

6.3.3 Data Flow Manager

6.3.3.1 Objective and general conditions of the Data Flow Manager

Basic principle of the Data Flow Manager● Automatic data flow

In the default state, all attribute values are transferred to connected components and pipes

● Controlled interruptionData flow events interrupt the data flow

● PreviewThe potential data flow is displayed on the report before values are changed.

● Supported report types: P&ID flow diagrams

DefinitionData break events are:

● Data break rules

– Purpose: Rules defined in a central standard table for interrupting the data flow. A data break rule can affect any number of reports.

● "Data flow break flag"

– Terminology: For reasons of legibility, the abbreviated term data break flag is used in this chapter instead of "Data flow break flag".If we are talking specifically about the object in the database, we use the object name "Data flow break flag".

– Purpose: A graphical object on the report to interrupt the flow of data starting at a single point. A data break flag has no connectors of its own.

● "Data flow break object"

– Terminology: For reasons of legibility, the abbreviated term data break object is used in this chapter instead of "Data flow break object".If we are talking specifically about the object in the database, we use the object name "Data flow break object".

– Purpose: A COMOS engineering object for interrupting the flow of data starting at a single point of a pipe. A data break object has connectors of its own.



AlternativesThe Data Flow Manager is an alternative to the "Update devices" tool.

See alsoOverview of using the Data Flow Manager (Page 79)

6.3.3.2 Overview of using the Data Flow Manager

Requirement● You are familiar with the objective and general conditions of the Data Flow Manager.

See section Objective and general conditions of the Data Flow Manager (Page 78).

● The administration has been performed.See section Administration (Page 84).

● A P&ID report has been opened.

Procedure1. Place P&ID objects as usual and connect the components using pipes.

COMOS also supports the approach of connecting components directly.

2. Place data break flags and data break objects.For more, see section Using data break flags and data break objects (Page 80).

3. Select an object on the P&ID.The correspondingly prepared attributes of the selected object are displayed in the properties tree.Ensure that the "Attribute filter" mode is set in the properties tree.

4. Select the input field of an attribute in the property tree.The P&ID highlights all objects that will receive the new value of the selected attribute.For more, see section Preview of the data flow on the report (Page 82).

5. Enter the attribute value.

6. Click the "Apply" button in the properties tree.

NoteApplying attributes individually

In the properties tree, confirm each edited attribute (i.e. each edited line) individually with "Apply".

The preview of the data flow of the attribute value available before applying only symbolizes one data flow. If multiple attributes are edited at the same time, only one of the attribute values has a valid preview.

ResultThe value is transferred to the color-coded objects.



6.3.3.3 Using data break flags and data break objects

Requirement● You are familiar with the use of the Data Flow Manager.

See section Overview of using the Data Flow Manager (Page 79).

● You cannot override the general data break rules.See section Administration (Page 84) for more on this.

You further restrict the data flow on the P&ID with data break flags and data break objects.

Using a data break flag1. Select the data break flag in the base data.

"@30 > M00 > A50 > A15 > A80 > A30 >B70 Data flow break flag"

2. Drag the data break flag from the base data onto a component.The Data Flow Manager requires that the data break flag be created in the same step on the report and be connected to a component.The "Data Flow Manager: Break attributes" window appears.

3. Edit the "Data Flow Manager: Break attributes" window.See "Determining break attributes" in the following section.

4. Confirm your entries.The data break flag is displayed.

5. After placement, the data break flag can be moved on the P&ID without having to open the "Data Flow Manager: Break attributes" window again.

6. Optional: In the context menu of the object to which the data break flag belongs, select the command "Options > Edit break attributes".The "Data Flow Manager: Break attributes" window appears.

Using a data break object1. Select the data break object in the base data.

"@30 > M00 > A50 > A15 > A80 > A30 >B70 Data flow break pipe"

2. Drag the data break object from the base data onto a pipe.Alternatively: Drag the data break object onto the report and onto a pipe only as a second step.The "Data Flow Manager: Break attributes" window appears.



3. Edit the "Data Flow Manager: Break attributes" window.See "Determining break attributes" in the following section.

4. Confirm your entries.The data break object is displayed.

5. After placing it on a pipe, the data break object can be moved on the P&ID without having to open the "Data Flow Manager: Break attributes" window again.The pipe is re-routed when the data break object is moved.

6. Optional: In the context menu of the data break object, select the command "Options > Edit break attributes".The "Data Flow Manager: Break attributes" window appears.



Determining break attributes1. The "Data Flow Manager: Break attributes" was called according to the workflow described

above.

The base object determines which attributes are offered in this window.

– Data break flag: The VSIU attribute of the component to which the data break flag belongs determines the attributes offered.

– Data break objects: The VSIU attribute of the data break object determines the attributes offered.

See also chapter Preparing base data for the Data Flow Manager (Page 85).

2. Select the attributes for which the data flow should be interrupted.If a break flag has been set for an attribute:

– If the data flow for an attribute is interrupted, an additional diamond appears on the report.

– If the interruption of the data flow is canceled, the diamond disappears.

– For administration of the break labels, see chapter Preparing labels for the data flow break attribute (Page 86).

6.3.3.4 Preview of the data flow on the report

Requirement● You are familiar with the use of the Data Flow Manager.

See section Overview of using the Data Flow Manager (Page 79).

Basic principle of the previewThe color representation of the objects described below symbolizes the potential changes.



The values are not changed until the value entry is confirmed.

Passing the attribute value without competing value at the target object● Pink

– Attribute value is passed by the Data Flow Manager

– There is no competing value at the target object

Passing the attribute value with competing value at the target object● Orange

– Attribute value is passed by the Data Flow Manager

– There is a competing value at the target object. The competing value is overwritten.

All other states● The target retains its original color

– Attribute value is not passed



6.3.3.5 Administration

Overview of the administration of the Data Flow Manager

Overview● Check the project properties.

See section Enabling the Data Flow Manager in the project properties (Page 84).

● Check the report options.See section Requirements for the report administration (Page 84).

● Edit the general data break rules.See section Preparing general rules for a data flow break (Page 85).

● Edit the base data.See section Preparing base data for the Data Flow Manager (Page 85).

● Optional: Edit the display of break labels.See section Preparing labels for the data flow break attribute (Page 86).

Enabling the Data Flow Manager in the project properties

Requirement● You are familiar with the overview of the administration.

See section Overview of the administration of the Data Flow Manager (Page 84).

Procedure1. Open the project properties.

2. Select the category "Process engineering > Attribute synchronization tool".

3. Select the entry "Data flow manager".

4. Confirm your entries.

Requirements for the report administration



EnableVSUI2The option script of the report template for P&ID contains the "EnableVSUI2 = TRUE" variable. If the value is set to "True", the properties tree is displayed automatically when you open the report.



You can find additional information on the attribute filters in the properties tree in the "Administration" manual, keyword "Preparing attribute filters".

Preparing general rules for a data flow break



Procedure1. Open the base project.

2. Select the following standard table:"Standard tables > Y10 > M22 > A10 > Y10M22N00013 General rules for data flow break"

3. Edit the standard table according to the following scheme:

– "Name" column: Unique string.Recommendation: Use the iDB-compliant enumeration [A10, A20, ...]

– "Description of the break attribute" column For free use.Recommendation: Enter the "Description" property of the attribute here.

– "Nested name of the break attribute" column: Identification of the attribute according to the scheme "Tab name.Attribute name".

– "Classifications of break objects" column: You use this information to determine which objects are searched and used for the attribute. The classification can be found in the properties of the base objects in the "Classification" tab, "Hierarchical classification" field.If each classification is valid, enter the asterisk "*" as a wildcard.Multiple classifications are separated by semicolons without spaces.

EffectThe Data Flow Manager breaks the data flow for the identified attribute if the target object has the specified classification.

Preparing base data for the Data Flow Manager





Base objectsThe Data Flow Manager considers the following objects:

● "@30 > M00 > A50 > A15 > A80 > A30 >B70 Data flow break flag"The data break flag does not generate an engineering object and has no connectors. The data break flag exists only graphically on the report. The context menu of the data break flag on the report contains the "Navigate >" command. This "Navigate >" command contains a navigation to the engineering object of the component to which the data break flag belongs.

– Attribute "Y00T00001.Y00A02625 VSUI attributes"The attribute remains empty in the base data. Because the data break flag does not generate an engineering object, COMOS uses the VSUI attribute of the component or the pipe section to which the data break flag is assigned.

– Attribute "Y00T00001.Y00A05706 Data flow break"The attribute is only processed by COMOS. The attribute remains empty in the base data. Because the data break flag does not generate an engineering object, COMOS uses the attribute of the same name of the component or pipe section to which the data break flag is assigned.

● "@30 > M00 > A50 > A15 > A80 > A30 >B80 Data flow break object"The data break object generates an engineering object and has connectors of its own. The connectors are automatically attached to the connectors on the segments of the pipe when the data break object is used.

– Attribute "Y00T00001.Y00A02625 VSUI attributes"The attribute is edited in the base data.

– Attribute "Y00T00001.Y00A05706 Data flow break"The attribute is only processed by COMOS. The attribute remains empty in the base data.

Additional information about the attributes● "Y00A02625 VSUI attributes"

The attribute contains the maximum list of attributes that can be offered in the "Data Flow Manager: Break attributes" window. In order for an attribute to actually be offered in the window, it must also be available as a VSUI attribute for the source object.

● "Y00A05706 Data flow break"With engineering objects, the attribute contains the specification about the attributes for which the user has interrupted the data flow in the "Data Flow Manager: Break attributes" window.

Preparing labels for the data flow break attribute





Procedure1. Open the base project.

2. Select the following standard table:"Standard tables > Y10 > M22 > A10 > Y10M22N00014 Labels for data flow break attribute"

3. Edit the standard table according to the following scheme:

– "Name" column: Unique string.Recommendation: Use the iDB-compliant enumeration [A10, A20, ...]

– "Description of the break attribute" column For free use.Recommendation: Enter the "Description" property of the attribute here.

– "Nested name of the break attribute" column: Identification of the attribute according to the scheme "Tab name.Attribute name".

– "Indicator" column: This string is displayed in the flag.

Effect1. The standard table is evaluated when data break flags or data break objects are used.

See section Using data break flags and data break objects (Page 80).

2. COMOS checks whether there is an entry in the standard table above for each affected VSUI attribute.

3. COMOS checks whether an attribute is set for the data flow break in the "Data Flow Manager: Break attributes" window.

4. If a data flow break is set, an additional diamond is created and the text in "Indicator" column is displayed in the diamond.

5. If a data flow break is canceled, the diamond is hidden again.

6.3.4 Configuring text recognition for AutoCAD drawings

6.3.4.1 Overview of the AutoCAD text recognition

Requirement● The licensing conditions are known:

– The function will be technically available for the first time as of COMOS 10.2.3

– The function requires a license as of COMOS 10.3.

ObjectiveThe AutoCAD text recognition requires that an AutoCAD file is placed on a report. In the screenshot below the report is marked with (1).



The AutoCAD text recognition detects individual texts of an AutoCAD file as a concatenated text block. The following elements are created for every concatenated text block:

● In the Navigator: An engineering object whose description includes the text of the text block. This engineering object is called the text block object. In the screenshot below the text block object is marked with (2).

● In the Navigator: An object in which the placement information for the recognized text block is stored. The placement object in the navigator is called DocObj. In the figure below the DocObj is marked with (3).

● On the report: A text block frame. This frame is called BoundingBox in this chapter. In the following figure the BoundingBox is marked with (4).

● When you double-click DocObj, the report opens and zooms onto the BoundingBox.

● The context menu of the BoundingBox contains the context menu "Navigate > Object". With this context menu you can navigate to the text block object:

As a result the AutoCAD text recognition function allows you the navigation between an object in the navigator and a text in a placed AutoCAD file.

The AutoCad file is visible as a background image on the report. The AutoCAD file is not broken up and the texts remain part of the AutoCAD file. Therefore it is not possible to select the texts on the report.

Sequence of the AutoCad text recognition1. The user defines an AutoCad file.

2. The user defines the framework of the text block detection.See chapter Example for an implementation in the iDB (Page 90) for an example.

3. The user defines a COMOS report.

4. The AutoCAD file is placed automatically on the report.

5. The AutoCAD file is checked for the following elements: Blockreference, AutoCADText, MText



6. BlockreferenceA Blockreference creates exactly one COMOS device. The Blockreference includes 1 to n AttributValues.Depending on the option the AttributValues are combined into groups or a separate text block is generated for each AttributValue.The following factors influence which texts are detected as concatenated text blocks:

– The user defines the TextDistanceFactor separately for the X-direction and Y-direction.

– A BoundingBox is created for every individual text: TextDistanceFactor * Text.Height

– Concatenated: At least one corner point of a single text BoundingBox has to lie within the BoundingBox of a different individual text.

7. AutoCADTextEvery AutoCADText includes a single-line TextValue. Multiple items of the AutoCADText type can be combined graphically to one text block.

8. MTextA text block is created for every MText. It is irrelevant whether the MText contains a single-line or multi-line TextValue.

9. A text block frame (BoundingBox) is generated for each text block on the report (Position (4) in the figure.)

10.For every text block one text block object is created in the navigator (Position (2) in the figure):

– Name: Consecutive number

– Description: The summary of the values read from the AutoCAD file (AttributValue, TextValue). The values that are taken into consideration depends on the generated text block.

11.A context menu "Navigation" is provided for the BoundingBox.The navigation references the created text block object.

12.Optional: Moving the DocObjThe DocObj of the BoundingBox is located in the default under the report. The DocObj objects store placing information. You can navigate to the report on which the engineering object is placed via the context menu of the DocObj object. If one moves the DocObj under the engineering objects, the DocObj can be used to move from the engineering object to the text on the report.You can find additional information on this topic in the "Operation" manual, keyword "DocObj objects".

Similar functionsAn AutoCAD import is available in the P&ID module. The AutoCAD import identifies the elements in the AutoCAD files and creates COMOS objects for the elements.

You can find more information on this topic in the "P&ID Operation" manual, keyword "Use AutoCAD import (dwg, dxf) import".



6.3.4.2 Example for an implementation in the iDB

Requirement● You are familiar with the overview of the AutoCad text recognition.

See chapter Overview of the AutoCAD text recognition (Page 87).

User interface (example)



Systematic procedure1. "Merge Block Text", "ConcatenationDelimiter", "Export Invisible Text",

"RecognizeMultiLineTexts", "Text distance factor X", "Text distance factor Y"These attributes do not have a script and a feature. The attributes represent the setting options in the DwgDxfInterface and are evaluated in the further course of the script. If DwgDxfInterface is extended and contains new setting options, add corresponding attributes as required. See chapter Class documentation DwgDxfInterface (Page 91) for the setting options in DwgDxfInterface.

2. "Mapped base object", "Document Template", "Folder", "Document pointer"The DwgDxfInterface function requires three details:

– The AutoCAD file.

– A COMOS engineering object as the starting point for a base object. The base object is required to create the text block objects.

– A COMOS report on which the AutoCAD file is placed.

In which form these three specifications are determined and which additional specifications are determined for further automation depends on the customer DB.

3. The function is triggered via the "Create View" interface. The attribute of this button owns the script with which all other attributes are sampled.In this script the settings for DwgDxfInterface are set on the basis of the sampled attribute values. Subsequently the AutoCAD text recognition is carried out in DwgDxfInterface.

4. "AutoCAD Mapping" is not a component of the AutoCad text recognition. This attribute is an extension of the application and serves to move the generated DocObj to the existing planning objects. This allows existing engineering data to be assigned to the BoundingBox objects on the AutoCAD file. As a result the user can navigate from the engineering objects to the BoundingBox on the AutoCAD file.

6.3.4.3 Class documentation DwgDxfInterface

CallNamespace:Set objDwgDxfInterface = CreateObject("Siemens.Comos.DwgDxfInterface.ComWrapper")Name of the dll:Comos.AutoCadIntegrator.ComWrapper

Variables used in this example● a: AutoCAD file (dwg or dxf)

● b: A COMOS engineering object as the starting point for a base object. The base object is required to create the text block objects.

● c: COMOS Report on which the AutoCAD file is placed



Placing an AutoCad file on the report● objDwgDxfInterface.AutoPlaceAndScaleDwgDxf c, a

This function places and scales the AutoCAD file. The scale factor influences the coordinates during the placement of the DocObj for the text blocks.

This method makes a property AutoPlaceResult available. This property contains the following information:

● objDwgDxfInterface.AutoPlaceAndScaleDwgDxf c, aSet AutoPlaceResult = objDwgDxfInterface.AutoPlaceResultOutput "Placed successful : " & AutoPlaceResult.DocumentPlacedSuccessful Output "ScaleFactorX : " & AutoPlaceResult.ScaleFactorX Output "ScaleFactorY : " & AutoPlaceResult.ScaleFactorYOutput "ScaleFactorOverall: " & AutoPlaceResult.ScaleFactorOverall

Configuration● objDwgDxfInterface.OpenReportAutomatically = true

Optional.Default: TrueDetermines whether the report is opened automatically.

● objDwgDxfInterface.CsvFilename = "C:\text.csv"Optional.Default: Path specification and file name of the AutoCAD file with the file extension ".csv"

● objDwgDxfInterface.ExportTextsToCsvOptional.Is required if CsvFilename is set.

● objDwgDxfInterface.DwgDxfFilename = a.FullFileNameDetermines the AutoCad file to be evaluated.

● objDwgDxfInterface.ConcatenateBlockTexts = trueDefault: TrueDetermines whether all the AttributeValues of a Blockreference are combined into one text block.

● objDwgDxfInterface.ConcatenationDelimiter = "_"Separators of individual texts in the collection of texts (Blockreference, AutoCADText).

● objDwgDxfInterface.ExportInvisibleAttributes = falseDetermines whether invisible AutoCAD attributes are considered.

● objDwgDxfInterface.ExportHeaderLine = falseSupport in troubleshooting.Determines whether the column descriptions are to be included as the first row in the semicolon-separated csv-file.

● objDwgDxfInterface.AutomaticallyRecognizeMultineTexts = trueDetermines whether the single-line AutoCADText elements (IAcadText) are recognized by means of graphical assignment as a concatenated text block.

● objDwgDxfInterface.TextDistanceFactorX = 1Determines the distance in X-direction (mm / pt), until which the AutoCADText is detected as a concatenated text block.



● objDwgDxfInterface.TextDistanceFactorY = 1Determines the distance in Y-direction (mm / pt), until which the AutoCADText is detected as a concatenated text block.

● objDwgDxfInterface.CompareTextHeights = trueOptional.Default: TrueDetermines whether the font size is considered during the detection of text blocks.

● objDwgDxfInterface.CompareTextHeightsToleranceFactor = 1Optional. Default: 0.1Dependency: CompareTextHeightsDetermines the scale factor until which a differently-sized font is considered during the detection of text blocks.

● objDwgDxfInterface.DrawReportObjectBoundary = trueDetermines whether the frame for the concatenated text block is visible when selecting on the report.

Create BoundingBox objects and DocObj● strCsvAllText = objDwgDxfInterface.GetCsvTexts

Base for CreateComosObjectsByCsvLine.

● count = objDwgDxfInterface.CreateComosObjectsByCsvLine(strCsvAllText, b.CDevice, c)Creates BoundingBox, Textblock object and DocObj.The counter is only important in case of faults or checking.

6.4 COMOS Lifecycle

6.4.1 PQM

SQL full-text search and text recognition for navigation● SQL full-text search

COMOS menu, "Plugins > Basic >SQL full-text search"

● Text recognition for navigationNo call available in the current iDB.

Both functions can currently only be commissioned and used with the assistance of project engineers.

Changes following deadline6.4 COMOS Lifecycle


6.4.2 PDMS/E3D Engineering Interface NavigatingThe following information supplements the chapter "PDMS/E3D Engineering Interface", keyword "Navigate", in the "3D Integration Operation" manual.

Extended functionality for navigationAll options described in the documentation for navigating between COMOS and PDMS/E3D remain valid.

For objects that represent pipes and Area Lines in PDMS/E3D, the corresponding navigation commands in the context menu have been expanded to include submenus.

Example:

If you want to navigate from a pipe in a P&ID in COMOS, the navigation destinations are offered as possible or available Area Lines.

6.5 Mobile Solutions

6.5.1 Named user licenses requiredIn this version you can only use Mobile Solutions with named user licenses.

Changes following deadline6.5 Mobile Solutions


6.6 iDB

Attribute import in node "Y30""iDB Administration" manual, chapter "Bulk importing of attributes and tabs", topic "Preparing the "Attributes" Excel sheet for attribute import":

● Structuring variant 5 "Y30 Import"

– Column "Searching area": Enter the value "Y30".

– Column "Naming area": Optional

– "Naming area" defines the node under "Y30" under which the attribute is created.

– Column "Name": Enter the name.

– Column "Owner": Enter the path and name of the customer node (e.g. "Z10"). You cannot create carrier objects for attributes directly below "Y30".

– If "Naming area" is set, the "Owner" node is generated under the "Naming area" node.

– Column "Main attribute": Blank

– Column "iDB structured": Blank

– Optional for structuring variant 5 b: Column "Packaging": Set an "x".

– Column "Special naming (Y30)": Set an "x".

Script processing"iDB Administration" manual, chapter "iDB script processing":

Labeling of the "Script processing" tool.

Attribute import: Modification of the column headers not permittedThe names of the column headers may not be modified in the Excel workbook "A30 Attributes & tabs V1.0".

Changes following deadline6.6 iDB


Changes following deadline6.6 iDB
