Release Notes 10 - support.industry.siemens.com · Topology planning for detailed cabling 1.5 PDMS/E3D Engineering Interface

COMOS

Release Notes 10.2

05/2016 V 10.2A5E37082755-AA

New functions 1

Corrected errors 2

Discontinuations 3

Known Issues 4

Changes following deadline 5

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-AAⓅ 04/2016 Subject to change

Copyright © Siemens AG 2015 - 2016.All rights reserved

Table of contents

1 New functions...............................................................................................................................................5

1.1 Report......................................................................................................................................5

1.2 P&ID.........................................................................................................................................5

1.3 FEED........................................................................................................................................6

1.4 EI&C.........................................................................................................................................7

1.5 PDMS/E3D Engineering Interface............................................................................................8

1.6 OpenPlant interface.................................................................................................................9

1.7 COMOS Walkinside.................................................................................................................9

1.8 Maintenance...........................................................................................................................10

1.9 Inspection...............................................................................................................................10

1.10 PQM.......................................................................................................................................10

1.11 Enterprise Server...................................................................................................................10

1.12 COMOS PDI...........................................................................................................................11

1.13 Platform..................................................................................................................................11

1.14 Mobile Solutions.....................................................................................................................13

1.15 Release for operating systems and third-party software........................................................13

1.16 Help........................................................................................................................................13

2 Corrected errors.........................................................................................................................................15

2.1 Compressing COMOS data...................................................................................................15

2.2 Change markings in reports...................................................................................................15

3 Discontinuations.........................................................................................................................................17

3.1 COMOS Express/COMOS ME Designer...............................................................................17

3.2 COMOS PlantModeler (CPM)................................................................................................17

3.3 Windows XP and Server 2003...............................................................................................17

3.4 Discontinuations and functional boundaries...........................................................................17

3.5 CVS and NewCVS.................................................................................................................19

3.6 Advance announcement........................................................................................................19

4 Known Issues ............................................................................................................................................21

4.1 Setup Browser under Microsoft Edge....................................................................................21

4.2 Server naming for XIF and quick start....................................................................................21

4.3 noxieFolder............................................................................................................................21

Release Notes 10.2Operating Manual, 05/2016 V 10.2, A5E37082755-AA 3

4.4 HTML help system.................................................................................................................22

4.5 Interfaces: "Export reports to EMF"........................................................................................22

4.6 New calculation method for *-revisions..................................................................................22

4.7 Administration: Required versions of CLS and RLS..............................................................23

4.8 Administration: Increasing the document version..................................................................23

4.9 Administration: Font for display of attributes..........................................................................23

4.10 Administration: Font for computer names..............................................................................24

4.11 Administration: Language dependency of attribute-based filters...........................................24

4.12 Administration: Copying the base project...............................................................................25

4.13 Administration: Editing the "IsRequest" property on Device..................................................25

4.14 Troubleshooting of excessive GDI resource consumption.....................................................25

4.15 ElementName Z.....................................................................................................................26

4.16 Interfaces: PDI interface.........................................................................................................26

4.17 Interfaces: CDI.......................................................................................................................26

4.18 Report templates dependent on working layers.....................................................................27

4.19 Add-ins are not displayed.......................................................................................................27

4.20 Report: Insert OLE object.......................................................................................................27

4.21 P&ID: Project properties for pipe spec mapping....................................................................28

4.22 FEED: ChemCad dialog in the background...........................................................................28

4.23 Shutdown...............................................................................................................................29

4.24 MRO.......................................................................................................................................29

4.25 Word export............................................................................................................................29

4.26 Integrated Engineering...........................................................................................................29

5 Changes following deadline........................................................................................................................31

5.1 Introduction............................................................................................................................31

5.2 COMOS Platform...................................................................................................................315.2.1 MS Project and Primavera interface......................................................................................315.2.2 Platform operation..................................................................................................................315.2.3 Platform Administration..........................................................................................................32

5.3 COMOS Automation..............................................................................................................33

5.4 COMOS Process....................................................................................................................335.4.1 Mirroring symbols in the P&ID report.....................................................................................33

5.5 COMOS Lifecycle...................................................................................................................345.5.1 3D Integration Administration.................................................................................................34

5.6 COMOS Operations...............................................................................................................35

Table of contents

Release Notes 10.24 Operating Manual, 05/2016 V 10.2, A5E37082755-AA

New functions 11.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 rectangles

Analog 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)

1.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.

● 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.

1.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

New functions1.3 FEED


Updated interfaces● Simulation data are imported from Aspentech AspenPlus 8.4 and 8.6

● Simulation data are imported from Aspentech HYSYS 8.4 and 8.6

● Design data are imported and exported from Aspentech EDR 7.3 and 8.0

● Simulation data are imported from Schneider Electrics PRO/II 9.2 and 9.3

● Simulation data are imported from Honeywell UniSim Design R430 and R440

● Simulation data are imported from Chemstation ChemCad HYSYS 6.4 and 6.5

● Design data are imported and exported from HTRI 6 and 7

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.

1.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

New functions1.4 EI&C


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

1.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

New functions1.5 PDMS/E3D Engineering Interface


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

1.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

1.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

New functions1.7 COMOS Walkinside


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

1.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

1.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

1.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

1.11 Enterprise Server● Rescission of jobs

● Execution in working layers

New functions1.11 Enterprise Server


● Logging and monitoring of jobs

● Increased data consistency

1.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

1.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.

New functions1.13 Platform


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.

New functions1.13 Platform


Revision of the user interface for working areasImproved usability

1.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

1.15 Release for operating systems and third-party softwareYou can find additional information on this topic in the "Installation" manual, keyword "Compatibility matrix".

1.16 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.

New functions1.16 Help


New functions1.16 Help


Corrected errors 22.1 Compressing COMOS data

The "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.

2.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 errors2.2 Change markings in reports


Discontinuations 33.1 COMOS Express/COMOS ME Designer

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.

3.2 COMOS PlantModeler (CPM)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.

3.3 Windows XP and Server 2003Microsoft 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.

3.4 Discontinuations and functional boundaries

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.

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

Discontinuations3.4 Discontinuations and functional boundaries


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

3.5 CVS and NewCVSNewCVS is no longer supported. CVS3G is used instead.

The option exists to continue using CVS.

3.6 Advance announcement

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.

Discontinuations3.6 Advance announcement


Discontinuations3.6 Advance announcement


Known Issues 44.1 Setup Browser under Microsoft Edge

The installation of COMOS from the DVD does not work when Microsoft Edge is used under Microsoft 10.

Local versions or versions of the Setup Browser downloaded in networks are not affected.

Workaround for installation from the DVD under Windows 10● Start the Setup Browser manually via the Internet Explorer (right-click > Open with > Internet

Explorer).

● Alternatively: Copy the content of the DVD to the computer and start the installation from there.

4.2 Server naming for XIF and quick startThe comos.xif technology only works when the SQL servers are connected according to the following naming.

Launching COMOS via the command line also only works when the SQL servers are connected according to the following naming.PT_SQL_SERVER_*

PT_SQL_SERVER_1

PT_SQL_SERVER_2

PT_SQL_SERVER_3

The same applies to Oracle.

PT_ORACLE_*

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


4.4 HTML help system

Language selectionWhen you open the HTML system, you see a list in which the languages "German", "English" and "Chinese" are offered in the lower section of the window. When you select a different language, the language of the help does not however change.

The language of the help is selected automatically in accordance with the language that you have selected for the COMOS user interface.

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.

4.5 Interfaces: "Export reports to EMF"The function of the "Export reports to EMF" interface is not guaranteed 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.

4.6 New calculation method for *-revisionsThe automatic generation of *-revisions has been developed further *-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.

Known Issues 4.6 New calculation method for *-revisions


4.7 Administration: Required versions of CLS and RLSA 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.

4.8 Administration: Increasing the document versionWhen 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.

4.9 Administration: Font for display of attributesA 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.

Known Issues 4.9 Administration: Font for display of attributes


4.10 Administration: Font for computer namesGeneral condition for the names of COMOS clients:

● Exclusive use of the English character set

● No Asian characters

● No German umlauts

● No French accents

If necessary, change the client name before a computer is used as the COMOS client.

BackgroundThe computer name is a component of the Ick file generated automatically by COMOS. The Ick file communicates information of which user has opened a report for editing to other COMOS clients.

If the computer name contains unsupported letters, the Ick file will be generated but can then no longer be processed by COMOS. Under error conditions, the Ick file must be deleted as follows:

● Alternative 1: Log in as system administrator and delete using a file explorer

● Alternative 2: Log in as COMOS administrator and use the "Synchronize project folder" function

4.11 Administration: Language dependency of attribute-based filters

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.

Known Issues 4.11 Administration: Language dependency of attribute-based filters


4.12 Administration: Copying the base project

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.

4.13 Administration: Editing the "IsRequest" property on DeviceThe "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.

4.14 Troubleshooting of excessive GDI resource consumption

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.

Known Issues 4.14 Troubleshooting of excessive GDI resource consumption


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

4.15 ElementName Z

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.

4.16 Interfaces: PDI interface

Core statementWe are aware of a malfunction in the Process Data Interface (PDI) in interaction with older versions of the Microsoft .Net Framework 4.0. The malfunction occurs during the synchronization of resources and units between COMOS and Teamcenter. The operation started by the user is aborted without an error message. The corresponding window remains open and empty.

To resolve this problem, install the patch KB2858725 offered by Microsoft. You can find this under the following link:

http://support.microsoft.com/kb/2858725 (http://support.microsoft.com/kb/2858725/en-us)

4.17 Interfaces: CDI

CDI exclusionsCDI cannot process DVM documents.

● CDI and DVM save changes at different times.

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

Known Issues 4.17 Interfaces: CDI


http://support.microsoft.com/kb/2858725/en-us

4.18 Report templates dependent on working layersThe "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.

4.19 Add-ins are not displayed

Microsoft Office applicationsNo add-ins for Microsoft Office applications (Word, Excel, PowerPoint and Outlook) are displayed when you are using COMOS with Windows 7. This function will be available once again with a future version of COMOS.

4.20 Report: Insert OLE objectDocuments can be inserted as OLE objects in a report template and an interactive report. The following exceptions apply:

● DVM functions are not supported:

– No DVM documents can be created as OLE objects.

– OLE objects cannot be transferred to DVM documents (no checkout/checkin possible).

● If the OLE object is opened on the report, the associated document is assigned the document type "General document":

– Only the properties of the "General Document" document type are available.

– CDI is not supported.

● When an OLE object is used and processed in different working layers, changes to the OLE object are transferred to other working layers with a delay.

● The display of OLE objects is controlled by the operating system and is thus varies theoretically depending on the client.

Known Issues 4.20 Report: Insert OLE object


4.21 P&ID: Project properties for pipe spec mapping

Modified project propertiesBase project "SO1": The following project properties are supplied for a new database with the modified default:

● "Process engineering > PipeSpec Manager" category

– "Pipe spec"Old: Y00T00003.Y00A00052New: Y00T00135.Y00A00052

– "Nominal diameter for the first connector (input)"Old: Y00T00003.Y00A00744New: Y00T00135.Y00A00744

– "Nominal diameter for other connector (output)"Old: Y00T00003.Y00A00744AA02New: Y00T00135.Y00A00744AA02

These project properties control the following function, among others: "Execute pipe spec mapping via the Navigator". You must enter new values in the project properties to execute the work step "PlugIns > Basic > Pipe spec mapping" in the COMOS menu. The "Pipe spec mapping" tab will remain blank as long as the old project properties are entered.

NOTICE

Database update does not register these new default values

When you execute a database update, the properties described above are not modified. If necessary, you have to adjust the properties to the new default manually.

4.22 FEED: ChemCad dialog in the backgroundIf you open a simulation that contains old methods with ChemCad, more up-to-date calculation methods are offered in a dialog. When you import a ChemCad file that contains old methods into COMOS, the same dialog is opened in the background, but it cannot be operated from COMOS.

You have the possibility of opening this dialog via ChemCad and activating the option, so that this dialog is no longer displayed.

Alternatively open the file in ChemCad and save it unchanged so that you overwrite the old file. The dialog is no longer displayed afterwards.

Known Issues 4.22 FEED: ChemCad dialog in the background


4.23 Shutdown

PlatesPlates are not supported.

4.24 MRO

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.

4.25 Word export

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.

4.26 Integrated Engineering

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.

Known Issues 4.26 Integrated Engineering


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.

Known Issues 4.26 Integrated Engineering


Changes following deadline 55.1 Introduction

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

5.2 COMOS Platform

5.2.1 MS Project and Primavera interfaceContrary to the information provided in the help, it was not possible to release the interface to MS Project and Primavera in the "Network Diagram" plugin, and it was therefore removed from COMOS 10.2.

5.2.2 Platform operation

"Plugins" menu revised"Readme" manual, keyword "Comparison of COMOS menus":

● "Basic > PDMS PipeSpec Interface"Moved to "3D Engineering Adapter > Aveva PDMS/E3D > PDMS/E3D Pipe Specs Import"

● "Basic > PDMS/E3D Engineering Interface"Moved to "3D Engineering Adapter > Aveva PDMS/E3D"

● "PQM > DVM queries > Bulk checkin / checkout"Renamed to "Bulk checkin/checkout"

Orange coloring of placed attributesMin-Max attributes placed on a report are not colored orange if Max is smaller than Min.


5.2.3 Platform Administration

Administering databases: Database updateUsers with status "Rights for database update" now have the following additional navigation commands in the selection layer.

● "Navigate > Base object in base project"

● "Navigate > Template in base project"

Interfaces: "Export reports to EMF"The "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.

Class documentation COMOS.dll"GetResources" function: The Registry key "MaxGDIRessourceCount" or "MaxGDIResourceCount" respectively is no longer supported.

Supported third-party software● Successful system test for AutoCAD 2014

● Successful system test for PDMS 12.1.2

● Successful system test for OpenPlant Modeler 8i

● Successful system test for AspenPlus 11.1

● Successful system test for HYSYS 8.8

● Successful system test for PRO/II 9.2

● Successful system test for UniSim Design R440 Build 5

● Successful system test for ChemCad 6.5.6.7502

● Successful system test for Promax 3.0.9065.0

● Successful system test for NOW / Proteus (previously XMpLant) 3.6.0

● Successful system test for eCl@ss based on BMECat 9.0 Advanced

● Successful Test System for PDFlib 9.0.2

Index update on the serverThe following option has been removed:

Project properties, category "General settings > Full text index": "Index update on the server"

Changes following deadline5.2 COMOS Platform


Other third-party software● AutoVue 19.2

● Pro II 9.3

5.3 COMOS Automation

5.4 COMOS Process

5.4.1 Mirroring symbols in the P&ID report

Mirroring symbolsThe P&ID reports have function for mirroring symbols. The function in P&ID is independent of the function for mirroring symbols in ET reports.

Old:

● Special handling of rotated symbols

● Basic symbols shortcut menu: "Mirror symbol vertically" / "Mirror symbol horizontally"

● Rotated symbols: Shortcut menu "Mirror symbol at main axis" / "Mirror symbol at minor axis"

New:

● No special handling of rotated symbols

● Shortcut menu: "Mirror horizontally" / "Mirror vertically"

The mirroring function in P&ID reports is always related to the baseline of the report.

Changes following deadline5.4 COMOS Process


5.5 COMOS Lifecycle

5.5.1 3D Integration Administration

Server Directory Service (SDS): Extensions of the configuration filesWhen you define the security settings for communication via configuration files, you have to extend the configuration files.

Note

The configuration files cannot be used without the extensions.

Affected chapters in the manual "3D Integration Administration":

● Chapter Specifying the security settings for communication with the SDS via the service configuration file.

● Chapter Specifying the security settings for communication between COMOS and PDMS/E3D via configuration file.

Extensions:

● "receieveTimeout" attribute in the "binding" elementExample: receiveTimeout="1.00:00:00">You can change the value.If a PDMS/E3D instance does not send a query to COMOS within the period specified here, the connection is disconnected automatically. Example: If a user starts PDMS/E3D and connects to COMOS, the connection is disconnected automatically if the user does not carry out any action in the interface within the specified period.If you do not define the security options via configuration files, the timeout amounts to 1 day.

● "reliableSesssion" element <reliableSession enabled="true"/>The "reliableSession" element activates a reliable connection session.

NoteDo not change the "true" value

The value of the "reliableSession" element must always be "true".

If you do not define the security options via configuration files, a reliable connection session is activated by default.

Example of the netTcpBinding element in the configuration file for COMOS and PDMS/E3D with the specified extensions:

<netTcpBinding>

Changes following deadline5.5 COMOS Lifecycle


<binding name="MessageSystem.MessengerService.Binding" maxReceivedMessageSize="2147483647"receiveTimeout="1.00:00:00"> <readerQuotas maxStringContentLength="2147483647"/> </binding> <reliableSession enabled="true"/> </netTcpBinding>

Example of the netTcpBinding element in the configuration file for the SDS with the specified extensions:

<netTcpBinding> <binding name="MessageSystem.ServerDirectoryService.Binding" receiveTimeout="1.00:00:00"/> <reliableSession enabled="true"/> </netTcpBinding>

Server Directory Service: Working in multiple networksIn the example of the network configuration file of COMOS, the correct IP address of the "Address" attribute is as follows: 126.128.1.53

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Working in multiple networks".

Server Directory Service: Specifying WCF security options for the SDSIf you specify security options for the SDS in the registry, follow these steps:

1. Create a "SOFTWARE\INNOTEC \COMOS\ServerDirectoryService" under "HKEY_LOCAL_MACHINE".

2. Create a "WcfSecurityOptions" value of the type string.

3. Specify the security options. Separate the security options with "|".

5.6 COMOS Operations

Changes following deadline5.6 COMOS Operations


Changes following deadline5.6 COMOS Operations
