release notes 10.2 - siemens ag · release notes 10.2.1 operating manual ... 43 5.1 introduction...

COMOS

Release Notes 10.2.1

Operating Manual

03/2017 V 10.2.1A5E37082755-AB

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-ABⓅ 03/2017 Subject to change

Copyright © Siemens AG 2015 - 2017.All rights reserved

Table of contents

1 New functions...............................................................................................................................................7

1.1 COMOS 10.2............................................................................................................................71.1.1 Report......................................................................................................................................71.1.2 P&ID.........................................................................................................................................71.1.3 FEED........................................................................................................................................91.1.4 EI&C.........................................................................................................................................91.1.5 PDMS/E3D Engineering Interface..........................................................................................101.1.6 OpenPlant interface...............................................................................................................111.1.7 COMOS Walkinside...............................................................................................................111.1.8 Maintenance...........................................................................................................................121.1.9 Inspection...............................................................................................................................121.1.10 PQM.......................................................................................................................................121.1.11 Enterprise Server...................................................................................................................121.1.12 COMOS PDI...........................................................................................................................131.1.13 Platform..................................................................................................................................131.1.14 Mobile Solutions.....................................................................................................................151.1.15 Help........................................................................................................................................15

1.2 COMOS 10.2.1.......................................................................................................................151.2.1 Database................................................................................................................................151.2.2 Platform & Basic.....................................................................................................................161.2.3 Report....................................................................................................................................181.2.4 Generic Data Mapper.............................................................................................................181.2.5 EI&C.......................................................................................................................................191.2.6 FEED......................................................................................................................................191.2.7 P&ID.......................................................................................................................................201.2.8 MRO.......................................................................................................................................201.2.9 Mobile Solutions.....................................................................................................................201.2.10 PDMS.....................................................................................................................................211.2.11 PDI.........................................................................................................................................221.2.12 Walkinside .............................................................................................................................221.2.13 Database version...................................................................................................................231.2.14 Release for operating systems and third-party software........................................................23

2 Corrected errors.........................................................................................................................................25

2.1 COMOS 10.2..........................................................................................................................252.1.1 Compressing COMOS data...................................................................................................252.1.2 Change markings in reports...................................................................................................25

2.2 COMOS 10.2.1.......................................................................................................................252.2.1 Behavior of RTF text fields in reports.....................................................................................252.2.2 Administration: Language dependency of attribute-based filters...........................................26

3 Discontinuations.........................................................................................................................................27

3.1 Isometrics: ROHR2 export.....................................................................................................27

3.2 COMOS Mobile DocumentView.............................................................................................27

Release Notes 10.2.1Operating Manual, 03/2017 V 10.2.1, A5E37082755-AB 3

3.3 Sharepoint interface...............................................................................................................27

3.4 COMOS Express/COMOS ME Designer...............................................................................27

3.5 COMOS PlantModeler (CPM)................................................................................................27

3.6 Windows XP and Server 2003...............................................................................................28

3.7 Discontinuations and functional boundaries...........................................................................28

3.8 CVS and NewCVS.................................................................................................................29

3.9 Advance announcement........................................................................................................30

4 Known Issues ............................................................................................................................................31

4.1 "Update assemblies" tool.......................................................................................................31

4.2 Copying AutoLoops................................................................................................................31

4.3 HTML help system.................................................................................................................31

4.4 Context menu in the "QueryView" mode................................................................................32

4.5 Construction of a bypass for pipes with special direction.......................................................32

4.6 Zoom function in redlining documents...................................................................................32

4.7 Installing .Net Framework......................................................................................................33

4.8 Export polyline to AutoCAD....................................................................................................33

4.9 Setup Browser under Microsoft Edge....................................................................................33

4.10 Server naming for XIF and quick start....................................................................................34

4.11 noxieFolder............................................................................................................................34

4.12 New calculation method for *-revisions..................................................................................34

4.13 Administration: Required versions of CLS and RLS..............................................................35

4.14 Administration: Increasing the document version..................................................................35

4.15 Administration: Font for display of attributes..........................................................................35

4.16 Administration: Font for computer names..............................................................................36

4.17 Administration: Copying the base project...............................................................................36

4.18 Administration: Editing the "IsRequest" property on Device..................................................36

4.19 Troubleshooting of excessive GDI resource consumption.....................................................37

4.20 ElementName Z.....................................................................................................................37

4.21 Interfaces: PDI interface.........................................................................................................38

4.22 Interfaces: CDI.......................................................................................................................38

4.23 Interfaces: "Export reports to EMF"........................................................................................38

4.24 MS Project and Primavera interface......................................................................................38

4.25 GSD interface.........................................................................................................................38

4.26 Word export............................................................................................................................39

4.27 Report templates dependent on working layers.....................................................................39

Table of contents

Release Notes 10.2.14 Operating Manual, 03/2017 V 10.2.1, A5E37082755-AB

4.28 Add-ins are not displayed.......................................................................................................39

4.29 Report: Insert OLE object.......................................................................................................39

4.30 Shutdown...............................................................................................................................40

4.31 MRO.......................................................................................................................................40

4.32 Integrated Engineering...........................................................................................................40

4.33 Collisions in connection with Updateability function...............................................................41

5 Changes following deadline........................................................................................................................43

5.1 Introduction............................................................................................................................43

5.2 COMOS Platform...................................................................................................................435.2.1 Installation..............................................................................................................................435.2.2 Administration........................................................................................................................445.2.3 iDB.........................................................................................................................................455.2.4 Class documentation..............................................................................................................45

5.3 COMOS Automation..............................................................................................................46

5.4 COMOS Process....................................................................................................................465.4.1 P&ID.......................................................................................................................................46

5.5 COMOS Lifecycle...................................................................................................................465.5.1 Start the PDMS/E3D interface...............................................................................................46

5.6 COMOS Operations...............................................................................................................475.6.1 "Critical path" button removed................................................................................................47

Table of contents


Table of contents


New functions 11.1 COMOS 10.2

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

New functions1.1 COMOS 10.2


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

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

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



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



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.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.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.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.1.11 Enterprise Server● Rescission of jobs

● Execution in working layers



● Logging and monitoring of jobs

● Increased data consistency

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



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

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

1.2 COMOS 10.2.1

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

New functions1.2 COMOS 10.2.1


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

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



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

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



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

1.2.6 FEED

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



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

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

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

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

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

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

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

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



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



Corrected errors 22.1 COMOS 10.2

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

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

2.2 COMOS 10.2.1

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


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

Corrected errors2.2 COMOS 10.2.1


Discontinuations 33.1 Isometrics: ROHR2 export

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

3.2 COMOS Mobile DocumentViewCOMOS 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.

3.3 Sharepoint interface

COMOS DocumentViewThe 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).

3.4 COMOS Express/COMOS ME DesignerThe 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.5 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.6 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.7 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.

Discontinuations3.6 Windows XP and Server 2003


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

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

Discontinuations3.8 CVS and NewCVS


The option exists to continue using CVS.

3.9 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.9 Advance announcement


Known Issues 44.1 "Update assemblies" tool

This functionality is not released for productive use.

4.2 Copying AutoLoopsThe 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.

4.3 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.4 Context menu in the "QueryView" mode

Requirement● A query has the "Row oriented (ByRow)" setting in the options.

● Calculated columns are added to the query. You drag, for example, an attribute from the Navigator to a column header in the query. A new column is created as a result; it is calculated depending on the selected column.

● The query is opened in "QueryView" mode.

RestrictionThe following context menus are not available:

● "Navigate"

● "Properties"

A patch is available from COMOS Support upon request.

4.5 Construction of a bypass for pipes with special directionWhen 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.

4.6 Zoom function in redlining documentsIf 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.

Known Issues 4.4 Context menu in the "QueryView" mode


4.7 Installing .Net Framework

.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 Installation (Page 43).

4.8 Export polyline to AutoCAD

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.

4.9 Setup Browser under Microsoft EdgeThe installation of COMOS from the DVD does not work when Microsoft Edge is used under Microsoft 10.

Known Issues 4.7 Installing .Net Framework


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.10 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.11 noxieFolderWith Drag&Drop or the manufacturer devices selection, an object (noxieFolderForBackupAndRestore) is created in the Elements tab, which is sometimes not necessary.

4.12 New calculation method for *-revisionsThe 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

Known Issues 4.10 Server naming for XIF and quick start


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.

4.13 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.14 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.15 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.13 Administration: Required versions of CLS and RLS


4.16 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.17 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.18 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.

Known Issues 4.16 Administration: Font for computer names


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

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

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

Known Issues 4.19 Troubleshooting of excessive GDI resource consumption


4.21 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.22 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.

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

4.24 MS Project and Primavera interfaceContrary to the information provided in the help, the interface to MS Project and Primavera is not contained in the "Project Management Charts" plugin in COMOS 10.2.1.

4.25 GSD interfaceThe 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).

Known Issues 4.21 Interfaces: PDI interface


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

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

4.26 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.27 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.28 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.29 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.

Known Issues 4.26 Word export


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

4.30 Shutdown

PlatesPlates are not supported.

4.31 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.32 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.

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.30 Shutdown


4.33 Collisions in connection with Updateability functionIf 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.

Known Issues 4.33 Collisions in connection with Updateability function


Known Issues 4.33 Collisions in connection with Updateability function


Changes following deadline 55.1 Introduction

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

5.2 COMOS Platform

5.2.1 Installation

Compatibility matrix: COMOS module involved● COMOS LS 2.0.6

● COMOS LSMonitor 1.7.3

Compatibility matrix: Runtime components of the installationThe following runtime components must be present:

● Runtime of Microsoft Visual C++ 6.0 SP6

● Runtime of Microsoft Visual Basic 6.0 SP6

● Microsoft Visual C++ 2012 x86 Redistributable



● Microsoft .NET Framework 3.5 (needs Internet access)Please check the document "Release Notes 10.2.1" for the latest information about this topic especially when Windows 10 is used.

● Microsoft .NET Framework 4.5.2Note: On some systems also the requirement for the use of Microsoft .NET Framework 4.6.1.

● For specific systems: Microsoft .NET Framework 4.6.1See chapter Installing .Net Framework (Page 33).

The runtime components are automatically included in the installation by default.

Compatibility matrix: Minimum updating of Windows 7COMOS cannot be installed on a basic installation of Windows 7.


If COMOS does have to be installed on a Windows 7 basic installation, at least the following security patches have to be installed:

2999226 Update for Universal C Runtime in Windows

2533623 Microsoft Security Advisory: Insecure library loading could allow remote code execution

Siemens recommends not using such basic installations in productive operation.

Alternative installation: Start the installation from the Windows ExplorerThe following line is added:

Product DirectoryCOMOS Full Text Index Serv‐ice Configurator

"...\Setup-Browser\SetupCallers\<Language>\AddOn-comosFull‐text.html"

COMOS Mobile DocumentViewAll entries on the topic of COMOS Mobile DocumentView are obsolete because the product has been discontinued.

5.2.2 Administration

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. Correction by Siemens is not possible because the file format "emf" is controlled by Microsoft.

Release of working layersThe new technology for release of working layers requires the following database version:

● Version 17 or higherDatabase version 17 was delivered with COMOS 10.1.

This does not only apply to the performance aspect of the new technology but to all other further developments and corrections for the release of working layers.

You can find additional information on this topic in the "Operation" manual, keyword "New release technology for MS SQL servers".

Changes following deadline5.2 COMOS Platform


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

5.2.4 Class documentation

Class documentation COMOS_dll: IComosDWorksetstring GetRelevantOverlayFileNameByFullFileName(string fullFileName, bool write)Supplies the file name that is correct from the point of view of the current working layer for an overlay-relevant file to a full absolute file name. During the search the actual file name is extracted from the full name and is used to find the next suitable name in the current layer chain. If, for example, the specified file does not exist in the current layer, but only in the

Changes following deadline5.2 COMOS Platform


released area, the correct file name for the released area is supplied, regardless of which layer directory was contained in the original absolute file name.

● fullFileNameFull absolute file name of a document in the document directory of the open database. It is not mandatory for the file to already exist.

● write

– FALSE: The file is searched for reading. Therefore only existing files are returned.

– TRUE: The file name is returned matching the current layer so that the file can be modified there.

● Return value

– Full file name matching the specified parameters: Either file name for reading or for writing (creating).

– If the fullFileName parameter does not belong to the document directory of the current database, the specified file name is returned without any change.

5.3 COMOS Automation

5.4 COMOS Process

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

5.5 COMOS Lifecycle

5.5.1 Start the PDMS/E3D interfaceUse the following command lines to start the PDMS/3ED interface in the respective third-party software.

Changes following deadline5.3 COMOS Automation


PDMS E3D Catalog 1.1 Catalog 2.1COMOS PDMS inter‐face

!!ITSetupCOMOS() !!ITSetupCOMOS() !!ITSetupCOMOS() !!SAGLaunchInter‐face()

PDMS/E3D Engineer‐ing Interface

!!SAGLaunchInter‐face()




5.6 COMOS Operations

5.6.1 "Critical path" button removedThe "Critical path" button has been removed from the "Network diagram" tab of the "Project Management Charts" plugin. The critical path can no longer be displayed.

Changes following deadline5.6 COMOS Operations


Changes following deadline5.6 COMOS Operations
