COMOS 10.1.3.0.0 - What's new? · Table of contents 1 Security information ... 8.3.1 Pipe Part Finder ... COMOS as of version 10.1 uses iDB in its default

COMOS

COMOS 10.1.3.0.0 - What's new?

Operating Manual

04/2015A5E32016072-AD

Security information 1

Databases iDB and cDB 2

Using the COMOS help 3

COMOS 10.1.0 4

COMOS 10.1.1 5

COMOS 10.1.2 6

COMOS 10.1.3 7Adjustment-related changes in the cDB 8

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

A5E32016072-ADⓅ 03/2015 Subject to change

Copyright © Siemens AG 2015.All rights reserved

Table of contents

1 Security information......................................................................................................................................7

2 Databases iDB and cDB...............................................................................................................................9

3 Using the COMOS help..............................................................................................................................11

3.1 Copying documentation to the help folder..............................................................................11

3.2 Opening the help....................................................................................................................11

3.3 Using the HTML help.............................................................................................................13

3.4 Displaying the COMOS help system online...........................................................................14

3.5 Using the COMOS help system in My Documentation Manager...........................................16

4 COMOS 10.1.0...........................................................................................................................................19

4.1 Help folder for the cDB and iDB databases...........................................................................19

4.2 COMOS menu when using iDB..............................................................................................19

4.3 COMOS Platform...................................................................................................................214.3.1 Information on rights administration.......................................................................................214.3.2 COMOS Platform...................................................................................................................224.3.3 COMOS glossary...................................................................................................................274.3.4 COMOS Web.........................................................................................................................274.3.4.1 Security information...............................................................................................................274.3.4.2 COMOS Mobile Document Review........................................................................................274.3.5 COMOS Enterprise Server.....................................................................................................284.3.6 COMOS Platform Interfaces..................................................................................................284.3.6.1 Interface to Teamcenter.........................................................................................................28

4.4 COMOS Process....................................................................................................................294.4.1 P&ID.......................................................................................................................................29

4.5 COMOS Automation..............................................................................................................314.5.1 Logical....................................................................................................................................314.5.2 Cabinet Equipment wizard.....................................................................................................31

4.6 COMOS Lifecycle...................................................................................................................324.6.1 3D Integration.........................................................................................................................324.6.2 PQM.......................................................................................................................................33

5 COMOS 10.1.1...........................................................................................................................................35

5.1 COMOS Platform...................................................................................................................355.1.1 COMOS Platform...................................................................................................................355.1.2 COMOS Snapshots................................................................................................................375.1.3 COMOS Platform Interfaces..................................................................................................37

5.2 COMOS Automation..............................................................................................................385.2.1 EI&C.......................................................................................................................................385.2.2 Logical....................................................................................................................................395.2.3 Integrated Engineering...........................................................................................................39

COMOS 10.1.3.0.0 - What's new?Operating Manual, 04/2015, A5E32016072-AD 3

5.3 COMOS Operations...............................................................................................................405.3.1 MRO.......................................................................................................................................405.3.2 Maintenance Administration...................................................................................................41

5.4 COMOS Process....................................................................................................................425.4.1 FEED......................................................................................................................................42

5.5 COMOS Lifecycle...................................................................................................................425.5.1 3D Integration.........................................................................................................................42

6 COMOS 10.1.2...........................................................................................................................................45

6.1 Links in the CHM help............................................................................................................45

6.2 Platform..................................................................................................................................456.2.1 Administration........................................................................................................................45

6.3 COMOS Operations...............................................................................................................466.3.1 MRO.......................................................................................................................................46

6.4 COMOS Process....................................................................................................................476.4.1 PipeSpec Designer................................................................................................................47

6.5 COMOS Lifecycle...................................................................................................................486.5.1 3D Integration.........................................................................................................................486.5.2 COMOS Material Management..............................................................................................486.5.3 COMOS Walkinside Integration.............................................................................................50

7 COMOS 10.1.3...........................................................................................................................................51

7.1 Modified project properties.....................................................................................................51

7.2 Platform..................................................................................................................................527.2.1 Administration........................................................................................................................527.2.2 Report....................................................................................................................................53

7.3 Process..................................................................................................................................547.3.1 Isometrics...............................................................................................................................547.3.2 FEED......................................................................................................................................557.3.3 P&ID.......................................................................................................................................557.3.4 PipeSpec Designer................................................................................................................56

7.4 Automation.............................................................................................................................567.4.1 EI&C.......................................................................................................................................567.4.2 Logical....................................................................................................................................577.4.3 Integrated Engineering...........................................................................................................58

7.5 Operations .............................................................................................................................597.5.1 MRO.......................................................................................................................................597.5.2 Inspection...............................................................................................................................607.5.3 Shutdown...............................................................................................................................60

7.6 Mobile Solutions.....................................................................................................................61

7.7 Lifecycle.................................................................................................................................627.7.1 PQM.......................................................................................................................................627.7.2 3D Integration.........................................................................................................................63

8 Adjustment-related changes in the cDB.....................................................................................................65

8.1 About this chapter..................................................................................................................65

Table of contents

COMOS 10.1.3.0.0 - What's new?4 Operating Manual, 04/2015, A5E32016072-AD

8.2 COMOS 10.1.1.......................................................................................................................658.2.1 COMOS Administration..........................................................................................................658.2.2 COMOS menu when using the cDB.......................................................................................658.2.3 COMOS Web.........................................................................................................................678.2.4 COMOS Material Management..............................................................................................678.2.5 Isometrics...............................................................................................................................708.2.6 PipeSpec Designer................................................................................................................708.2.7 3D Integration.........................................................................................................................718.2.8 P&ID.......................................................................................................................................738.2.9 Troubleshooting during excessive GDI resource consumption with COMOS........................75

8.3 COMOS 10.1.2.......................................................................................................................768.3.1 Pipe Part Finder.....................................................................................................................768.3.2 Logical....................................................................................................................................76

8.4 COMOS 10.1.3.......................................................................................................................778.4.1 COMOS Administration..........................................................................................................778.4.2 3D Integration.........................................................................................................................778.4.3 Isometrics...............................................................................................................................788.4.4 Mobile Solutions.....................................................................................................................788.4.5 FEED......................................................................................................................................798.4.6 EI&C.......................................................................................................................................798.4.7 Integrated Engineering...........................................................................................................858.4.7.1 Creating the Master Version..................................................................................................858.4.7.2 "Y10M00N00031 Assembly updater property assignment"...................................................868.4.7.3 Updating assemblies..............................................................................................................88

Table of contents


Table of contents


Security information 1Siemens provides products and solutions with industrial security functions that support the secure operation of plants, solutions, machines, equipment and/or networks. They are important components in a holistic industrial security concept. With this in mind, Siemens’ products and solutions undergo continuous development. Siemens recommends strongly that you regularly check for product updates.

For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and integrate each component into a holistic, state-of-the-art industrial security concept. Third-party products that may be in use should also be considered. For more information about industrial security, visit http://www.siemens.com/industrialsecurity.

To stay informed about product updates as they occur, sign up for a product-specific newsletter. For more information, visit http://support.automation.siemens.com.


Security information


Databases iDB and cDB 2A new database standard was introduced with COMOS 10.1. It is called "industrial DataBase" or iDB for short and replaces the old database as standard in the COMOS delivery state as of 10.1. The old database called "classic DataBase" or cDB for short is no longer included in the scope of delivery as of COMOS 10.1.1.0.0.

Current helps and product support for iDBDue to the database replacement, COMOS as of version 10.1 uses iDB in its default configuration.

This means all help functions are described assuming that you are using an iDB.

"What's new" also looks at new developments based on the iDB database.

Helps and product support for cDBcDB is no longer supported in the standard scope of delivery as of COMOS 10.1.2.0.0. The helps for COMOS using the cDB were frozen as of version 10.0.2.0.0.

If you continue to use COMOS with a cDB, we recommend that you use the help files included in your initial installation because the current help files are based on iDB and describe COMOS deviating from your system. Contact your Delivery Service for information on how to ensure new functionalities while using a cDB.

See alsoAdjustment-related changes in the cDB (Page 65)


Databases iDB and cDB


Using the COMOS help 33.1 Copying documentation to the help folder

RequirementCOMOS is installed.

Procedure1. Open the directory in which the help files are located in the file explorer.

For example: <COMOS Installation directory>/Help/<Help folder>/<Language folder>.

2. Store your documentation in the help folder.

Note"Help" directory

Documents that are located directly in the "Help" directory are not displayed.

3.2 Opening the help

Overview of the COMOS help The COMOS help consists of the following components:

● COMOS help system:A library with manuals on COMOS

● Individual help files in the formats *.pdf, *.pdx and *.docThe PDF files "COMOS - What's new?" and "COMOS Readme" are supplied with COMOS.

NoteSupplementing the help files

You can integrate your own help files in the COMOS "Help" menu. The files are displayed in the COMOS "Help" menu.

You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Central administration of the help menu".


You can open the COMOS help as follows:

● COMOS help system:

– From COMOS

– Online

– From the file system

● Individual help files:

– From COMOS

– From the file system

NoteReferences to other manuals

If other manuals are referenced in the COMOS help, these manuals also form part of the COMOS help.

Opening the help from COMOS 1. Start COMOS.

2. To open the COMOS help system, select the menu command "Help > COMOS help system".The help system is opened as an HTML help. See also chapter Using the HTML help (Page 13).

3. To open an individual help file, select the command "Help > <File name>" in the menu.

To read the help in a different language, switch the language of the COMOS user interface and call up the help system again.

Opening the help online See also chapter Displaying the COMOS help system online (Page 14).

Opening the help through the file system1. Open the directory in which the help files are located in the file explorer.

For example: <COMOS Installation directory>/Help/<Database>/<Language folder>.

2. Double-click the file "COMOS_HelpSystem_enUS.chm" to start the COMOS help system.The help system is opened as an HTML help. See also chapter Using the HTML help (Page 13).

3. To open a PDF document, double-click the document.

Viewing the PDF helpTo display the COMOS help as PDF files, you require a PDF Reader that is compatible with PDF 1.7 (ISO32000-1:2008 PDF).

Using the COMOS help3.2 Opening the help


3.3 Using the HTML help

RequirementsOperating system: Windows 98 and higher

Procedure1. Open the COMOS help system in COMOS or the file system as HTML help. See also

chapter Opening the help (Page 11).

2. On the "Contents" tab, open the node of a COMOS product family, for example "COMOS Platform".All the manuals that belong to the modules of this product family are displayed.

3. Open a manual and select a chapter. The chapter contents are shown on the right.

4. You have the following options when working with the help system:

– Search:You can search through the entire help system on the "Search" tab.

– Displaying related topics:If related topics are available for the chapter currently displayed, these are listed in the menu bar above the chapter contents: The "Manuals" menu contains related instructions; the "Basic principles" menu contains related basic principles.To change to a chapter, select it.

– Creating Favorites:Select a chapter on the "Contents" tab. Change to the "Favorites" tab and click "Add".

– Toggling between chapters already displayed: You can use the "History" and "Extras" menu and the buttons "Back" and "Forward" to toggle between the chapters already displayed.

Note

If you change from one chapter to a different chapter, for example via the links embedded in the chapters, the Favorites or the "History" menu, the node of the currently open chapter is always displayed on the "Contents" tab.

Using the COMOS help3.3 Using the HTML help


3.4 Displaying the COMOS help system onlineThe COMOS help system is available free of charge and in multiple languages on the Internet:

● Open the following Internet page: COMOS documentation (http://www.siemens.de/comos-dokumentation/)

● In the "Overview", you will find the various product areas of COMOS product family.

● In the "Topics" column, you will find the COMOS Manual Collection or individual help files. The lines contain links to the My Documentation Manager and the SIEMENS Industry Online Support Portal:

Clicking on the icon opens the document in My Documentation Manager (MDM). The range of functions in MDM depends on whether you are logged in:● Without registration/login: View documents● With registration and login: Configure, compile documents, notification

function, etc.See chapter Using the COMOS help system in My Documentation Manag‐er (Page 16).

DE, EN, ZH Link to the document in the available languages in the SIEMENS Industry Online Support Portal:● DE=German● EN=English● ZH=Chinese simplified

COMOS help files in the SIEMENS Industry Online Support PortalThe COMOS help files are also available as PDF files in the Siemens Industry Online Support Portal. In addition, you can display the documents with the My Documentation Manager.

Using the COMOS help3.4 Displaying the COMOS help system online


http://www.siemens.de/comos-dokumentation/

http://www.siemens.de/comos-dokumentation/

To find COMOS help files, proceed as follows:

1. Open the Web page of the Siemens Industry Online Support portal: SIOS (http://support.automation.siemens.com/)

① "Product Support" in the navigation bar② "Index (A-Z)" tab③ "Navigation" tab

2. Click on "Product Support" in the navigation bar.

3. You have three ways to find COMOS help:

– Open the "Navigation" tab and look for COMOS in the product tree. You can find COMOS help under: "Automation technology > Automation systems > Automation software > Plant Engineering Software COMOS"

– Open the "Index A-Z" tab. If you click on "C", you will see the COMOS help files in the list.

– Enter the term "COMOS" in the search box at the top right and click "Search". You can narrow search results by clicking on "Manuals" below "Search area" in the hit list.

4. Select a COMOS help file from the list and click the title.

5. When the selected COMOS help is displayed, you can choose from the following:

– "Displaying and configuring": Opens the document in My Documentation Manager.

– "Download": As PDF file

Using the COMOS help3.4 Displaying the COMOS help system online


http://support.automation.siemens.com/

http://support.automation.siemens.com/

3.5 Using the COMOS help system in My Documentation ManagerMy Documentation Manager is a central online database for SIMATIC and COMOS customer documentation. My Documentation Manager allows you to edit the entire customer documentation, reorganize it and export it into a variety of formats if needed. You can assemble documentation corresponding exactly to your system or configuration from the documents that are available. The notification feature informs you by e-mail when a document in your collection has changed.

Range of functions in My Documentation ManagerThe range of functions depends on whether or not you are logged in:

● Functions without login:

– View customer documentation

– Open help for My Documentation Manager

● Additional functions with login:

– Configuration: Assembly of individual documents in a collection

– Delete, add, move, copy any document in a collection

– Send collection to an e-mail address as a link

– Search and assemble documents in one language and then export them to one of the available languages

– Notification feature is available on all levels: Single page, chapter, manual, collection, etc.

– Export documents, folders and collections as a PDF, XML, or RTF file

Working with My Documentation Manager ● The following section describes how to open the My Documentation Manager : Displaying

the COMOS help system online (Page 14).

● A comprehensive description of working in My Documentation Manager is available in the help: Help on My Documentation Manager (http://www.automation.siemens.com/mdm/_help/de/mdm_reference_manual_de-DE.htm).

Using the COMOS help3.5 Using the COMOS help system in My Documentation Manager


http://www.automation.siemens.com/mdm/_help/de/mdm_reference_manual_de-DE.htm

http://www.automation.siemens.com/mdm/_help/de/mdm_reference_manual_de-DE.htm

Registration and login to My Documentation Manager1. Click "Full scope of functions after login/registration".

The login form for My Documentation Manager opens.

2. Click "Yes, I would like to register now" and fill out the fields in the following windows.



3. Click the Next button, until your login information is completed.

4. You have now successfully registered and can use all the functions of My Documentation Manager .



COMOS 10.1.0 44.1 Help folder for the cDB and iDB databases

OverviewA separate help folder is supplied for the iDB and cDB databases as of COMOS version 10.1. You can see the content of the respective folder in the COMOS "Help" menu depending on the database with which you start COMOS.

Contents of the "Help_iDB" folder● Help system 10.1 (.chm)

● COMOS 10.1 - What's new? (.pdf)

● COMOS 10.1 - Readme (.pdf)

Contents of the "Help_cDB" folder● Help system 10.0.2 (.chm)

– Includes the "PQM Configuration Tools" manualIt covers the following topics: "Advanced PQM functions", "Test plan management"

● COMOS 10.1 Updateinfo classic Database (.pdf)

● "Integrated Engineering" manual (.pdf)

See alsoCopying documentation to the help folder (Page 11)

4.2 COMOS menu when using iDB

RequirementsThe COMOS menu changes depending on the COMOS version and the type of database. This section describes the changes under the following conditions:

● Switching from COMOS 10.0 to COMOS 10.1

● And simultaneously from cDB to iDB


List of unavailable menu commands● Extra > Queries > Queries for base objects > Query: cross-project base objects

● Extra > Queries > Tools > Convert old scripts to script blocks

● Extra > Queries > Tools > Semi-open connections

● Extra > Queries > Queries for DVM > My recent documents

● Extra > Viper 3D Editor > Electrical engineering

● Plugins > Basic > Unit conversion

● Plugins > Basic > Pipe spec mapping

● Plugins > Basic > Material Management Assistant

● Plugins > Basic > Task Management

● Plugins > Basic > PDMS PipeSpec Interface

● Plugins > Maintenance

● Plugins > Mechatronics

● Plugins > Automation > Signal name matching

● Plugins > Automation > IEC to JIC conversion

● Plugins > Automation > PCS7 interfaces > Create templates

● Plugins > Automation > PCS7 interfaces > Import/Export PCS 7

● Plugins > Automation > Interfaces > EPLAN5 data exchange

● Plugins > Automation > Interfaces > Ruplan import

● Plugins > Automation > Interfaces > VNS import

● Administrator > Base data > Import ECAD components

● Administrator > Base data > Pipe specs

● Administrator > Base data > Attribute transfer editor

● Administrator > System > Database adjustments

List of textually changed menu commands● Extra > Queries > Queries for engineering objects > Query: cross-project engineering

objectsChanged to: "Engineering objects query (cross-project)"

● Extra > Queries > Queries for documents > Query: cross-project documentsChanged to: "Query: Documents (cross-project)"

● Extra > Queries > Tools > Wire listChanged to: "Wire list (via connectors)"

● Extra > Queries > Tools > Restore COMOS objectsChanged to: "Restore COMOS objects"

● Extra > Queries > Queries for DVMChanged to: "DVM queries"

COMOS 10.1.04.2 COMOS menu when using iDB


● Extra > Queries > Queries for DVM > Bulk checkin/checkoutChanged to: "Bulk checkin/checkout"Moved to: "Plugins > PQM > DVM queries"

● Extra > Viper 3D EditorChanged to: "3D Review"

● Extra > Viper 3D Editor > 3D PipingChanged to: "3D view"

● Plugins > Basic > PDMS InterfaceChanged to: "PDMS Pipe Spec interface"

● Plugins > Automation > Interfaces > Bulk editing of semi-open connectionsMoved to: "Plugins > Automation"

List of new menu commands● Extra > Queries > Queries for engineering objects > Query: Engineering objects (alternative)

● Extra > Queries > Queries for base objects > Query: Base objects (alternative)

● Extra > Queries > Queries for attributes > Query: Attributes (alternative)

● Extra > Queries > Queries for documents > Query: Documents (alternative)

● Extra > Queries > Queries for connectors > Query: Connectors (alternative)

● Plugins > Basic > PDMS Engineering Interface

● Plugins > Basic > Walkinside object assignment

● Plugins > Basic > Data aggregation

● Plugins > Automation > Interfaces > STEP7 Interface

● Plugins > Automation > Interfaces > Cabinet Equipment wizard

● Administrator > Base data > String rule manager

● Administrator > Base data > Database update

4.3 COMOS Platform

4.3.1 Information on rights administration

Adaptation of the documentation for the topic "Administration of rights and roles"For the version COMOS 10.1, additional information was added to the overall help regarding the maximum number of roles and the maximum number of users.

COMOS 10.1.04.3 COMOS Platform


4.3.2 COMOS Platform

iDB databaseCOMOS is delivered with the new database type "iDB". This documentation describes COMOS used in conjunction with iDB.

Project properties revisedIn prior COMOS versions the project properties were stored in three different sources. Now all project properties are combined and are stored in an XML-like structure. Thus all project properties can be queried using a uniform programming syntax. The project properties are no longer displayed in the interface as tabs. Instead, there is a tree-like structure of categories. All project properties were resorted and supplied with more understandable texts as needed.

Database updateThe "Database update" tool has the following use cases:

● Install iDB database updates Controlled application of the corrections provided by Siemens to your own database.The iDB database updates are cumulative. Update 5 also includes all corrections and updates from updates 1 to 4.

The following workflow is offered for this purpose:

1. Preliminary application of changes to a special working layer called the consolidation layerPreliminary application is possible in one or all of the following project types:

– System project

– Base project

– Template project

2. Isolated check of changes

3. Selection of objects to be applied

4. Application of selected objects to the released area



Classification method changedCOMOS now distinguishes between two types of classification:

● Classification

– Hierarchical classificationDescribes the class structure and therefore the base data structure of a COMOS module.Five hierarchically dependent fields with 1 to 4 characters each.The first layer of hierarchical classification is a three-digit key for the module name (M00 for Basic, M20 for Process, M40 for Automation, and so on). In hierarchical classification, the subsequent layers (2, 3, etc.) can only be set in relation to the layers before them.

– Functional classificationDescribes the cross-module function of an object.Five independent fields with 1 to 4 characters each.You can assign any combination of functional classification keys.

● User classificationIs available for your purposes. The functional classification technique is used in the background.

– Hierarchical user classification

– Functional user classification

For this reason, four basic variants for classifications appear below "@99 > A10":

● Classification key 1: COMOS (hierarchic)

● Classification key 2: COMOS (functional)

● Classification key 3: Customer (hierarchic)

● Classification key 4: Customer (functional)

The hierarchic classification with prefix "Z" is no longer reserved for customer-specific classifications.

LockLock, system flagThe iDB contains system-related objects which must not be changed. There are special lock mechanisms to protect these objects.

● The "Object locking" (system lock or lock-lock) function. This function can only be edited by Siemens employees.

● For reasons of clarity, the "system object" status is also available. This status shows that the object is a system-related object. This status has no other implications. In practice, the "System object" status is often combined with the "Object locking" function.

Script LibraryAll scripts were standardized and stored under a common node. The script blocks are commented and are easy to use or modify. This greatly reduces the effort required for customer-specific modification of the database.



Inheriting queriesConfigure a source query and inherit another query from it, which is in a branch of the structure tree.

To inherit a query, proceed as follows:

1. Select the "System" tab in the properties of a query.

2. Drag&drop the source query from the Navigator onto the "Base object" field in the "Reference" control group.A window opens. You have the following options:

– To change the base object reference and replace your archive settings, click the "Yes" button.

– To change the base object reference but retain your archive settings, click the "No" button.

– To cancel the process without making any changes, click the "Cancel" button.

3. Confirm your entries.

Saving settings for the queriesYou can disable the permission for saving a query in the base query.

When saving is disabled, the following happens:

● Base query: A security prompt appears. After this, saving is possible."Save as" is still permitted.

● Query: The menu command "Save" is disabled."Save as" is still permitted.The "Load from base object" menu command is disabled. Because the archive of the query cannot be saved, the archive of the base query is automatically loaded every time you open the query.

DIN identifierUnit systems are standardized for the different technical areas. To illustrate these standardizations, the "DIN identifier" field is now available. A unit is uniquely identified internationally with a DIN identifier and can be more easily imported or exported. The DIN identifiers are listed in a DIN property list that is available on the Internet.

New option for subelementsNew option "Extend subelements":

Only engineering objects which are subelements (child objects) of the base object can be created in the engineering view. Cross-inherited subelements are also created.



Script access to standard tables: ItemByValue / ItemByXValueThe following functions are now available:

● ItemByValue(0, const CString& searchValue) / ItemByXValue(unsigned long index, const CString& searchValue)Returns the value object for the search value.searchValue: Search valueIndex: Search index for XValueReturn: The object with the value or NULL

Name mask for elementsIf the "Default" value is selected for elements for the "Virtual" setting, text mask for names that is entered in the base object is evaluated.

Extending the "Type" list for connectorsIn the "Type" field for connectors, two new types are available:

● TaskUsed for the definition of engineering tasks

● FEEDConnection for FEED objects (for example, process streams)

Monitoring using IsWorkflowReferenceMonitoring using the prefix "WREFOBS_" has been replaced by monitoring using the "SetWorkflowReference" and "IsWorkflowReference" methods. These properties can be queried at the attribute my means of a script. To do this, create a query and define a new column with the corresponding property. You can then check or edit the property in the query.

New script function GetNLSTextCustomer-specific scripts can now use NLS texts. As a result, all texts and messages (such as a Messagebox) are multilingual.

An NLS text is created with one of these functions:

● GetInternationalTextFromNLSByProjectLanguage

● GetInternationalTextFromNLSByGUILanguage

● GetInternationalTextFromNLSByLanguageID

Dependency of working layers on report templatesReport templates can be customized for each working layer.

Various requirements apply to the function "Working layer-dependent report templates". In particular, all template files must be integrated in COMOS by means of document objects. You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Creating a working layer-dependent template file".



Revision archive: Freely configurable revision printer (HARP)A standard configuration was developed for the freely configurable revision printer. The "HARP.ini" file supplied in the default settings uses the following configuration:

● The OEM PostScript printer driver supplied with Windows

● COMOSHarp.inf

● COMOSHarp.ppd

The HARP standard configuration requires the following PS converter:

● GhostScript

Using the PDF document viewWith the "Multiple Document Preview" plugin, you can view one or more external PDF documents on the working area of the report. You can change and print the placed PDF document in the view, but not edit it.

Logging (TraceListener)The "Trace and debug schema" from .NET Framework 4.5 is supported. You can find the documentation for the associated XML schema on the Internet at Microsoft msdn. Logging is switched on as follows:

Comos.exe.config under <system.diagnostics><sharedListeners>: Comment in "ComosTextWriterTraceListener".

The listener must then be added to the corresponding trace sources: Comos.exe.config under <system.diagnostics><sources>

Object matcher extendedThe object matcher can be opened via the context menu for an object and in this case compares the status of an individual object in various working layers. The consolidation layer is now also supported. In this case, the object is compared with the current delivery status of the object. This option is only available for objects for which a delivery status is available. In all other cases, the shortcut menu "Working layers/Histories > Compare object" is grayed out in the released area. The delivery status of an object is determined by the last iDB database update.

Language relevant to projectThis option specifies which languages are relevant for a project. Once this option has been activated, it is only possible to switch between the project-relevant languages in the "Languages" tab.



GrayboxSelectionModeSelection behavior for modules can be changed using the system attribute (SYS.GrayboxSelectionMode) in the main document.

● GrayboxSelectionMode = 0When you click on an object within the module, the object itself is selected.

● GrayboxSelectionMode = 1 (default)When you click on an object within the module, the entire module is selected. Only the second click selects an individual object.

4.3.3 COMOS glossary

RevisionThe terms in the COMOS glossary were revised. The glossaries of the following manuals were moved to the COMOS glossary:

● PQM

● FEED Operation

4.3.4 COMOS Web

4.3.4.1 Security information

Data securityThe "COMOS Web" manual now includes information on data security.

4.3.4.2 COMOS Mobile Document Review

Saving "COMOS Mobile Document Review" data management in a separate base projectIn the project settings in COMOS, you set the free saving of "COMOS Mobile Document Review" data management in a base project other than S01. Here you will find the new project option "Base project" under the "Web" category.

You can find more information on this topic in the "COMOS Web" manual, keyword "Saving the "COMOS Mobile Document Review" data management in a separate base project".



4.3.5 COMOS Enterprise Server

Release of working layersAt the command line, you can now also configure the release of working layers. The following requirements must be met:

● The working layer exists.

● The linked working layer corresponds to the linked working layer of the working layer above it.

● No users are logged on to the working layer.

If you cancel the release process via the COMOS Enterprise Monitor, the working layer receives the status "Incorrect release".

Deletion of working layersIn the command file, you can now also configure the deletion of working layers. The following requirements must be met:

● The working layer exists.

● No projects or working layers are linked in a working layer in the base project.

● No users are logged on to the working layer.

● No objects are present which prevent deletion.

If you cancel the deletion process via the COMOS Enterprise Monitor, the objects are still in the database, but are no longer visible. Therefore, do not cancel the deletion process.

You can find more information on this topic in the "COMOS Enterprise Server" manual, keyword "Editing working layers".

4.3.6 COMOS Platform Interfaces

4.3.6.1 Interface to Teamcenter

Process Data Interface (PDI)Process Data Interface (PDI) is now available.

ObjectivePipe parts are transferred from COMOS to NX via PDI. The data is transferred via Teamcenter to NX. Teamcenter is the interface for the data transfer between COMOS and NX. Transfer takes place by means of XML files in which information about pipe specs and pipe parts is collected.



Pipe schedules are transferred as PDF. Information about PipeRun and XMpLant is also transferred as an XML file.

Functional scopePDI comprises the following functions:

● Connection between COMOS and NX

● Connection between objects

● Navigation to 3D objects in NX and COMOS objects on the P&ID

● Pipe spec export

● Publishing documents

AdministrationThe configuration file "Comos.PDI.config" is available for the administration of PDI.

Use the "pipepartfamilies.xml" file to assign pipe parts in COMOS to pipe part families in NX. You can edit the "pipepartfamilies.xml" file in COMOS. The following functions are available for this purpose:

● Adding attributes

● Editing attributes

● Deleting attributes

You can find more information on this topic in the "COMOS Platform Interfaces" manual, keyword "Process Data Interface (PDI)".

COMOS Teamcenter interface

Synchronizing attribute valuesYou can synchronize attribute values of Teamcenter forms to the engineering and base data with COMOS attributes. Conversely, you can synchronize attribute values from COMOS engineering to Teamcenter forms. You can find more information on this topic in the "COMOS Platform Interfaces" manual, keyword "Synchronizing attribute values".

4.4 COMOS Process

4.4.1 P&ID

XMpLant exportCOMOS can now also export files based on XMpLant 3.3.3.

COMOS 10.1.04.4 COMOS Process


XMpLant import● For the import, COMOS only supports files with XMpLant Version 3.3.3.

● An administrator can enter the subprogram OnXMpLantImportDone on P&ID objects or on P&ID in the script. Once the XMpLant import is complete, the script is executed for each engineering object. You can find additional information on this topic in the "P&ID Administration" manual, keyword "Creating "OnXMpLantImportDone" on COMOS objects".

● Based on two additional import options, you now have the option to identify changes during a reimport and determine how to handle specific objects.In the "Import and dissolve drawing" window, the following import options were added:

– "Import into new working layer" option

– "Remove not contained objects" option

You can find additional information on this topic in the "P&ID Operation" manual, keyword ""Import and dissolve drawing" window".

PDF importDuring a PDF import, all texts of a PDF are imported into COMOS. COMOS creates objects for each text in a text field in accordance with the rules defined by an administrator.

You can find more information on this topic in the "P&ID Operation" manual, keyword "PDF import".

Important terminology changes

Old designation New designation"Pipe branch" "Pipe section""Standard pipe banner" "Standard pipe label""Equipment" "Equipment"

Script option "SegmentULMode"The "SegmentULMode" script option is now also valid for P&ID. You find more information on this topic in the "COMOS Platform Administration" manual, keyword "Function reference for the options script".



4.5 COMOS Automation

4.5.1 Logical

Initial sequence chainFor function diagrams there is now an object for initial sequence chains: Place the object. An entry step, a transition and a final step are generated and connected on the function diagram and in the Navigator.

Improved operation for sequence chainsWhen you insert a new element in a sequence chain, COMOS checks the sequence chain logic:

● Missing objects are automatically createdExample: When inserting a step, a transition is automatically inserted.

● Violations of the sequence chain logic are marked as inconsistent.Example: If you connect the returning connecting line of a jump with a subsequent step, the connection is marked as inconsistent.

4.5.2 Cabinet Equipment wizardThe wizard for cabinet engineering offers you the following functions:

● Simple detail engineering

● List of the placed elements

● Direct access to all relevant attributes and functions

● Synchronization of all dependent documents

● Automatic 3D consistency check of the placed rail elements

COMOS 10.1.04.5 COMOS Automation


4.6 COMOS Lifecycle

4.6.1 3D Integration

PDMS: New interface "COMOS PDMS Engineering Interface"In addition to the old interface there is now a new interface available. To distinguish between them, the following terminology was defined:

● Old interface: "COMOS PDMS Interface"

● New interface: "COMOS PDMS Engineering Interface"

Fundamental changes to the old interface:

● The user works on the PDMS page and can execute all actions from there.

● With the help of queries, the administrator defines in advance which COMOS objects can be loaded in the interface by a user or user group to read and edit them.

● The new interface offers a tree view of the loaded COMOS objects and additional options for comparing the objects in the two applications with one another.

The interface features the following functions:

● Create individual objects in PDMS

● Create hierarchies in PDMS

● Synchronize and update attributes

● Assign objects to each other in COMOS and PDMS

● Navigate between COMOS and PDMS

You can find additional information on this topic in the "3D Integration Operation" and "3D Integration Administration" manuals, keyword "COMOS PDMS Engineering Interface".

PDMS: Citrix client installation mode (silent mode)Installation in silent mode runs in the background and is controlled by a text file in which the administrator has entered all of the relevant information in advance. You do not need to make any further entries during installation.

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Citrix client (silent mode)".

PDMS: Feedback modeIf feedback mode is enabled, the two applications can bidirectionally make write access to data.If feedback mode is disabled, only COMOS can make write access to data from Walkinside.

COMOS 3D ViewingInstallation of "COMOS Walkinside Integration"

COMOS 10.1.04.6 COMOS Lifecycle


"COMOS Walkinside Integration" is the interface between COMOS and the 3D viewer application, COMOS Walkinside. In order to use COMOS 3D viewing, you must install the interface.

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Installing "COMOS Walkinside Integration"".

Assignment of COMOS objects and Walkinside objects

Using a new plugin, you can now assign objects in order to make navigation possible. In the plugin, create a unique label for every object of a defined quantity of objects on the COMOS page and on the Walkinside page. The label is created with the aid of scripts. The related objects on the COMOS page and the Walkinside page must have the same label.

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Configuring navigation".

Export COMOS objects by means of a query

This function is used to collect certain objects in Walkinside, which are already located in Walkinside and for which you have created an assignment.

Example scenario:

● You want to view only those object in Walkinside which have to be maintained.

● You collect these COMOS objects in a query and export them to Walkinside. In Walkinside, a view of these objects is temporarily displayed.

Important terminology changes

Old designation New designationOriginal PDMS interface (no name) "COMOS PDMS Interface""TaggedItem" class "Device with label" class"Pipe" class "Cable" class"@PDMSMAP" folder "Y00R00033 folder for class/subclass definitions

(PDMS)" objectLocObj Area pipe

4.6.2 PQM

ObjectivePQM (Project Quality Management) imports and administers external documents in COMOS. PQM supports you here as a document management system (DMS) for all important lifecycle phases of your project documents.

Extended PQM functionsThe extended PQM functions are no longer part of this manual.



Test plan managementTest plan management is no longer part of this manual.

"My recent documents" queryThe "My recent documents" query is no longer available.



COMOS 10.1.1 55.1 COMOS Platform

5.1.1 COMOS Platform

Update of the released area (database update)The "Database update" tool has the following use cases:

● Install iDB database updates Controlled application of the corrections provided by Siemens to your own database.The iDB database updates are cumulative. Update 5 also includes all corrections and updates from updates 1 to 4.

● Incrementing the iDB versionControlled application of a new iDB version to your own productive database.

The following workflow is offered for this purpose:

1. Preliminary application of changes to a separate working layer called the consolidation layer.Preliminary application is possible in one or all of the following project types:

– System project

– Base project

– Template project

2. Isolated check of changes

3. Selection of objects to be applied

4. Application of selected objects to the released area

5. Option to return to the previous version

"Snapshot" menu commandMenu bar: "Plugins > Basic > Snapshot"

See also chapter COMOS Snapshots (Page 37).

You can find more information on this topic in the "COMOS Snapshots" manual.

Full text search improved (index update on server)The full text index is updated automatically after the initialization. It is now also possible to control the update by a document server (an operating system service). Requirement: The "Index update on server" project option is activated.


The automatic update occurs in this case at any time upon request by COMOS. Automatic updating requires that the events to be updated have taken place. Events to be updated are:

● Creating and copying of documents

● Saving, printing, or revisioning of documents

Object matcher improved (display with text editor)The "Show" command is available in the context menu. This is used to display the selected script block in the default text editor.

Using numbering ranges in MRONumbering ranges can now be created based on the "Classification" method. This method is applied in the MRO area where it is used to create "ID numbers" of MRO objects.

SBM (Service broker messages)SBM offers a few innovations compared to the predecessor CVS system:

● Broadcast no longer used

● Guaranteed message transmission

● Message transmission can be encrypted

● StationID from previously defined pool

● Bidirectional communication

● Transmission in sent sequence (queue)

The old CVS system can be used in parallel if required.

Base working layersYou can now connect an engineering project to a working layer of the base project.

Exporting projectsThe following options are now available for considering revisions when exporting projects:

Yes / No / Ask every time

Merging objects in the iDBThe mergeMode parameter can now be placed at any level in the iDB with a recursive call using the "A01 Merge" tab.



5.1.2 COMOS Snapshots"COMOS Snapshots" gives you fast access to COMOS data in the form of previously created COMOS queries. To get a quick overview of your previously created Snapshots, start a separate EXE file. You do not need access to COMOS for this. "COMOS Snapshots" opens in a separate window and stands out from COMOS due to its ease of use.

The following functions are available with “COMOS Snapshots”:

● You can create Snapshots manually or automatically as a series.

● Using a Snapshot, you can access large data volumes in just a few seconds.

● You can grant read rights for each Snapshot created.

● You can define a lifetime for each Snapshot to prevent building up a large amount of Snapshot data.

● Navigate from a selected Snapshot for the original query to COMOS.

● Select several row objects from a Snapshot and edit these objects in COMOS.

See alsoCOMOS Platform (Page 35)

5.1.3 COMOS Platform Interfaces

Exporting report levels to PDFYou can export level information as follows:

● Only the levels visible in the report

● All levels

You can show and hide the contents of the levels in the PDF using the navigation window for levels. Levels hidden in the report are also initially hidden in the PDF.

For reports with the same drawing type, the levels are collected under one node.

The following are excluded from the export of levels:

● Levels 200 to 255

● Exports with the "Archiving according to ISO standard in PDF/A-1b format" option

DWG/DXF mapping editorOn the "General" tab, you can select the scheme from the "Picture file naming scheme" list to be used for naming pictures embedded in COMOS when exporting.



5.2 COMOS Automation

5.2.1 EI&C

AutoLoopStartObjectsSortingModeNew variable in the option script of loop diagrams that controls the order in which objects are placed on the loop diagram.

● 1: The objects are placed in the same order that they have in the internal COMOS sorting in the Navigator (ASCII sorting).Default

● 0: The order of placement can deviate from the order that the objects have in the internal COMOS sorting in the Navigator.

Updating device label automaticallyUsing the report script option "UpdateBMKAutomatically", administrators can now control when the shared automatic device label of terminals, plugs, and bridges is updated:

● "0" or option missing: Users update the device label as required using the "Options > Refresh device label" context menu.

● "1": COMOS updates the device label on a running basis as soon as one of the following actions is performed for one of the objects on the report:

– Cut and paste

– Dissolve graybox

– Move

– Move (transform)

– Delete

– Drag&drop

– Assign object

Note

In the case of reports with a large number of objects, this setting can slow down work on the report.

Controlling the search order for references output via text function "Elm...VW"New standard table in base project "Y10 > M00 > A20 > Y10M00N00030 Reference search order"

Requirement: A symbol that uses the text function "Elm..VW" and has elements that are placed on a drawing with a different drawing type is placed on an interactive report.



By means of the "Reference search order" standard table, you control which drawing types are considered for the references determined using "Elm..VW" and the order in which the drawing types are evaluated.

5.2.2 Logical

Moving parts of the sequence chain up or down with the context menuYou can move all sequence chain symbols that are located next to or below a start symbol that you selected. You define the number of grid points by which the objects are moved up or down.

If necessary, the sequence chain is moved so that it spans more than one sheet. COMOS prevents symbols from being pushed together.

Moving or copying sequence chain objects with the mouseYou can use the mouse to cut or copy sequence chain objects on a function diagram and paste them at a different point of the sequence chain.

The sequence chain objects are reconnected automatically.

Navigating between half open partner connections in function diagramsYou can navigate from a half open connection to its half open partner connections and back as follows:

● Using the <Page Up> and <Page Down> keys

● Using the context menu "Connection > Navigate to successor"

● Using the "Navigate to successor" and "Navigate to predecessor" buttons on the toolbar of the report

The counter-connection is selected and zoomed in on. It can be located on the same page of the function diagram, on a different page, or on another function diagram. In the latter case, the other function diagram is opened.

5.2.3 Integrated Engineering

iDBIntegrated Engineering COMOS with PCS 7 is now also available on the iDB.



"Update usages" pluginWith the "Update usages" plugin, you apply changes of the types to the already created instances of equipment modules and control modules. You now have the option of overwriting the existing mapping tables at the instances with the mapping table of the type.

5.3 COMOS Operations

5.3.1 MRO

"History" tabFor Maintenance objects, there is now a uniform "History" tab. It is available for the following Maintenance objects:

● Workpackages

● Partial workpackages

● Events/incidents

● Activities

● Spare parts

● Maintenance plans

● Bulk material

● Shutdown

The basis of the tab is the "@20 > A70 > Y20 > M60 > C10 History" query.

Cost and price managementCosts and prices are now calculated automatically as soon as you change a value on a tab. You can enter planned and actual costs on the following tabs:

● "Calculation workpackage"

● "Calculation activity"

● "Calculation spare part"

You can create hourly rates for qualification types in the following standard table:

"@40 > Y00 > A10 > A90 > Y00N00213 hourly rates"

You can find more information on this topic in the "MRO (Maintenance Repair and Overhaul)" manual, keyword "Cost and price management".

COMOS 10.1.15.3 COMOS Operations


Attributes● Attributes used to specify a time are now available with time unit (e.g., "h").

● Date and time are saved in an attribute.

● Attributes used to specify progress are now available with unit (e.g., "%").

5.3.2 Maintenance Administration

"Maintenance options" menuThe new "Maintenance options" menu can be found under the menu "Plugins > Maintenance > Maintenance options". Here, you can make settings for the plugins and user-specific settings.

New project optionsUnder the "Operations > Maintenance" category in the project properties, you will find a series of new project options. You can find more information on this topic in the "Maintenance Administration" manual, keyword "General project settings".

ID numberID numbers are no longer configured using the "Identity" tab, but rather using the "Administrator > System > Numbering ranges" menu. You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Numbering ranges".

To assign an ID number, use the "Attributes > ID number" tab. The following Maintenance objects contain this tab:

● @20 > C40 > A20 Workpackages

● @20 > C40 > A30 Taskpackages

● @20 > C40 > A70 > A60 Activity

● @20 > C40 > A70 > A70 Material management

● @20 > C40 > A70 > A80 Resources

● @20 > C40 > A90 Commercial objects

● @10 > B10 > A10 > A10 Maintainable object

● @20 > C40 > A50 > A10 Events/incidents



5.4 COMOS Process

5.4.1 FEED

AssembliesAssemblies are now also available for the iDB database.

You can find more information on this topic in the "FEED Administration" manual, keyword "Assemblies".

Converting PFD into P&IDYou can now also convert a PFD into a P&ID in the iDB database.

You can find more information on this topic in the "FEED Operation" manual, keyword "Converting a PFD into a P&ID".

Material balancesYou can now also display material balances in the iDB database.

You can find more information on this topic in the "FEED Operation" manual, keyword "Configuring a material balance".

5.5 COMOS Lifecycle


COMOS PDMS integrationNavigation from a pipe or a pipe section to PDMS

In the COMOS PDMS engineering interface, you can navigate on the P&ID from a pipe or a pipe section to the assigned object in the PDMS tree.

You can find more information on this topic in the "3D Integration Operation" manual, keyword "Navigating to PDMS".

User interface of the COMOS PDMS engineering interface has been revised

You can find more information on this topic in the "3D Integration Operation" manual, keyword "COMOS PDMS engineering interface".

Network communication is available for the COMOS PDMS engineering interface

As of Citrix 6.0, long wait times may occur during file-based communication between client and server. To avoid these wait times, you can set up network communication as an alternative.



You can find more information on this topic in the "3D Integration Administration" manual, keyword "Setting up network mode".

Supported PDMS version

PDMS V12.1 is supported.

3D viewingInstallation of "COMOS Walkinside Integration" is possible via the COMOS Setup browser

You can find more information on this topic in the "3D Integration Administration" manual, keyword "Installing "COMOS Walkinside Integration"".

Object assignment can be run as batch job

You can start the object assignment as a batch job using the Enterprise Server. You do not need a Walkinside installation for this type of object assignment.

You can find more information on this topic in the "3D Integration Administration" manual, keyword "Executing object assignment as batch job".





COMOS 10.1.2 66.1 Links in the CHM help

Links to other manualsIn the CHM help, you can now click on links to other manuals and access the topic concerned directly.

6.2 Platform

6.2.1 Administration

Function enhancements in SearchManagerThe SearchManager is a tool for searching for objects with specific properties in the database. The SearchManager is used for the "database search" function as part of queries. The SearchManager can also be used in script by means of Workset.GetSerchManager.

When SearchManager is used through script, new values are now available for Property.

New values for the parameter "Attribute: Property"

● CR (= creation stamp)

● RS (= revision stamp)

● TYP (= document type)

– 0: normal document

– 1: Document template

– 2: Document master

– 3: Document reference

– 10: Checked out document

– 11: Checked in document

– 14: Exported document


Export and import of working layers larger than 2GBCOMOS now makes a distinction between normal working layers and large working layers automatically:

● Normal working layerAn mdb is exported.

● Large working layer (> 2 GB)A zip file with a cwo suffix is created. This zip file is a container for the file format for large working layers.

COMOS with 4GB supportCOMOS uses only 2GB of RAM by default. When COMOS is installed as usual by means of the setup browser, the link in the Windows start menu initiates the standard version of COMOS.

The following file is now also installed as part of the COMOS installation:

<COMOS-Path>\BIN\comos4g.exeIf you run this exe file, COMOS will be initiated with support for 4GB of RAM. comos.exe and comos4G.exe differ only in the amount of RAM they are able to call on. The COMOS version with support for 4GB of RAM is useful for bulk operations with data.

Configurable background loading during queriesPreviously, background loading of cells was always active and all cells were calculated.

Now, there are the following additional possibilities:

● Background loading is turned on, but it aborts if the value in the field "Limit" is reached.

● Background loading is turned off.

6.3 COMOS Operations

6.3.1 MRO

Lifecyle objectsYou can now configure lifecycle objects. With this new function, you have the option to define any type of structure and to determine which base object should be used for it.



6.4 COMOS Process

6.4.1 PipeSpec Designer

Bolting sets and bolting set groups● Bolting set groups are attachment parts under which bolting sets are sorted.

● Bolting set groups have the following advantages:

– All bolting sets of a connection are sorted under the bolting set group.

– If you remove the connection between two pipe parts, the group and all associated bolting sets are automatically deleted.

– The bolted connection is visible in the Navigator even before the calculation.

You can find more information on this topic in the "PipeSpec Designer" manual, keyword "Bolting set groups".

● The various bolt types are no longer managed in a bolting set. A separate bolting set is created for each bolt type.

Attachment table in pipe specsA new "Attachment table" tab is available in pipe specs. Here you can define which attachment part should be used as standard for which attachment type combinations.

You can find more information on this topic in the "PipeSpec Designer" manual, keyword ""Attachment table" tab".

Information about connections on the "3D geometry" tabThe information about connections on the ""3D geometry" tab" has been distributed across new "Connection <1-n>" tabs, Each connection of a 3D component is described on a separate tab.

You can therefore reuse connection information and do not have to re-enter it for every component.

You can find more information on this topic in the "PipeSpec Designer" manual, keyword ""Connection <1-n>" tab".

Standard tables for pipe parts catalog organized by standard systemIn pipe specs, you no longer work with standards to determine value ranges. All standard-related tables are saved by standard system in various nodes. Depending on the standard system you have selected for a pipe part, other standard tables are used.

As a result of the new logic, the procedure for creating a new standard system has changed.



6.5 COMOS Lifecycle


Import of PDMS pipe specsThe import of PDMS pipe specs has been entirely revised. Data exchange between COMOS and PDMS takes place offline by means of XML files. You start the import with the "PipeSpec Interface" command in the "Plugins > Basic" menu.

You can find additional information on this topic in the "3D Integration Operation" manual, keyword "Import of PDMS to COMOS".

Grouping COMOS objects in the PDMS interfaceIf a user requests COMOS objects in the COMOS PDMS Interface, containers with the names for PDMS SITES and ZONES are created for pipes and equipment based on defined rules. The COMOS objects are sorted under these.

If you do not configure SITE mapping and ZONE mapping, all objects are stored parallel to one another in the COMOS PDMS Interface in the "Scope" area.

If you have only configured one of the two tables or the configurations cannot be evaluated, the objects are created under a "Not categorized" node.

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Using ZONE mapping and SITE mapping".

Canceling the assignment between COMOS objects and PDMS objectsYou can cancel the assignment and thereby delete all references by the objects to one another.

You can find additional information on this topic in the "3D Integration Operation" manual, keyword "Canceling the assignment between COMOS objects and PDMS objects".

6.5.2 COMOS Material Management

T-pieces are created automaticallyIf you carry out the MTO estimation on the basis of an R&I, a T-piece is created in the Navigator and on the material list for each connection between a function line and a branch.

The T-piece has the following properties:

● Nominal diameter 1: Nominal diameter of main pipe Example: "100"

● Nominal size 2: Nominal diameter of the branchExample: "80"



● Type: "TEE"

● MatchCode: "T"

● RKEY: Comprises the type and the values for the nominal diameters.Example: "Tee10080"

Defining units for summationIn order to ensure that imported data is displayed correctly and quantities can be converted accordingly, you can now assign the imported units to the COMOS units.

You can find additional information on this topic in the "COMOS Material Management Administration" manual, keyword "Defining units for summation".

"MTO documents" and "MRP documents" tabs● You no longer open, revise, delete or update document packages on the "Documents" tab.

These functions are now available on the "MTO documents" tab in the document tree accessed via the context menu.For more information on this topic, refer to the "COMOS Material Management Operation" manual, keyword "Managing documents".

● The "MTO documents" tab has been completed revised and is now more user-friendly. You can find additional information on this topic in the "COMOS Material Management Operation" manual, keyword ""MTO documents" tab".

Updating document packagesYou can now update document packages in the Material Management Assistant.

1. Open the "MTO Documents" or "MPR Documents" tab in the Material Management Assistant.

2. Open the context menu of a document package in the "MTO documents" or "MPR documents" control group.

3. Click the "Update <document key>" entry.

Displaying the delta for the amount values between two selected revisionsYou can display the delta for the amount values between any two revisions in a temporary delta document and save it in PDF or CSV format.

You can find additional information on this topic in the "COMOS Material Management Operation" manual, keyword "Displaying the delta for the amount values between two selected revisions".

Displaying the delta for the amount values between the current revision and a released revisionYou can display the delta for the amount values between the current revision and a released revision. The administrator configures the display. If you carry out an update, the columns containing the corresponding information are also displayed in the MTO document.



You can find additional information on this topic in the "COMOS Material Management Administration" manual, keyword "Configuring the display of the delta for the amount values between revisions".

Estimating pipes with different nominal diametersWhen estimating R&I data, the nominal diameters of all pipe parts are now displayed on the "Estimated" tab.

For manual estimation, a matrix with all available nominal diameters is displayed. The fields within the matrix include the quantity of a component with the corresponding nominal diameter combination. You can edit the fields to enter the quantities manually.

Legend for the colored fields:

Color DescriptionGray Nominal diameter combination is not possible because the nominal diameter of

the branch is greater than the main nominal diameter.Blue Nominal diameter combination is possible but the pipe part is not valid in this

combination.Red Nominal diameter combination is possible, but there is already an MTO object

for this nominal diameter combination. The quantity of the existing MTO object is displayed in the field.

White Valid nominal diameter combination.

6.5.3 COMOS Walkinside Integration

"COMOS integration" menuAs far as Walkinside is concerned, there is a new "COMOS integration" menu under which the following entries have been categorized:

● COMOS-Plugin "Configuration"

● COMOS-Plugin "COMOS Auto-Assign"

● "Query results"



COMOS 10.1.3 77.1 Modified project properties

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

● "Operations > PQM" category

– "Standard tables for mapping"Old: not setNew: "Y40 > M65 > A10 > Y40M65N00002"

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


7.2 Platform

7.2.1 Administration

Controlling paste mode by means of scriptThe script option "OverrideCopyMode" ensures that the specified paste mode is used automatically when pasting to interactive reports.

Filtering units at attributeThe option "Filter unit" is available when an attribute is created at the base object. You can use this option to select which units can be selected at the base object and optionally also at the engineering object. This way units loaded from a standard table can be further limited at a specific attribute.

Dongle-free license with COMOS LS Host-IDThe function COMOS LS Host-ID retrieves the various client values. These values are referred to here as "Identifying values". The Host-ID is the sum of the Identifying values. Siemens can use the Host-ID to generate a license file that does not require a dongle.

Integrating Siemens PIA LCP as catalogYou can use the "PIA Life Cycle Portal" catalog in COMOS with an online connection. To do so, you need Microsoft Internet Explorer as of 6.0. The data is swapped by means of XML messages.

Language with SAP LoginThe language of the SAP target system is displayed in the "SAP Login" dialog.

Release check takes locked documents into considerationThe release manager also checks for locked documents and displays the locked documents. The user must then close the documents in the target working layer.

Time stamp in the object historyUse the "History behavior of checked-in objects" to control how missing time stamps "CreationStamp" are handled:

● "Time stamp of the inheritance source"

● "Time stamp of the first non-inherited object in the ownership chain on the engineering side"

COMOS 10.1.37.2 Platform


Supported version with CDIRequirements for the use of the COMOS document interface: Word 2003 / Excel 2003 or later.

Adobe Reader 11Adobe Reader 11 is supported.

NoteDeviating requirements for individual functions

Deviating requirements may exist for individual COMOS interfaces and functions. Such special requirements are documented in the corresponding chapters in the manual.

Microsoft SQL Server 2014Microsoft SQL Server 2014 is supported as database management system for COMOS databases.

Oracle 12Oracle 12 is supported as database management system for COMOS databases.

7.2.2 Report

Change and function expansion of the PDF displayThe internal component to display PDF files was changed to QPDF. This means the following functions have been added by this change:

● Support of CID fontsThis means the following fonts are now displayed:

– Type 0

– Type 1 (Type 1 / MMType1)

– Type 3

– TrueType

– CIDFont (CIDFontType0, CIDFontType2)

● Improved display of hatchings

● Improved display of scaling in PDF file

Dynamic loading of queriesThis function is available for list reports with constant row height.

COMOS 10.1.37.2 Platform


Dynamic loading speeds up the display of a query in a report when a default row is used. To do so, COMOS calculates how many default rows of the same size are required to fill a report page. To display a specific report page, only those row reports that are required for this page are performed.

Dynamic loading is controlled by the following two options:

● "ListLoadMode = 1" option.

● "FirstPage = <page>" option

Exception:

● Grouped queries are not supportedIf a query using the "ListLoadMode = 1" option is loaded on a report, the query must not be grouped.

You can find more information on this topic in the "COMOS Platform Administration" manual, keyword "Row report with object queries and default row".

Zooming in reportZooming with the mouse wheel has been adapted to the Microsoft standard. If you need the old behavior, use the "InvertMouseWheelZoomforReport" option.

"InvertMouseWheelZoomforReport" is a variable in the "Workset.Globals".

Value range:

● 0 = old behavior (DEFAULT!)

● 1 = inverted

7.3 Process

7.3.1 Isometrics

IDF import in iDB possibleThe IDF import is now also possible in the iDB database.

Specifying tolerances for pipesPipes that you imported from an IDF file may be marked as inconsistent in COMOS. Reasons for this could be:

● Inexact alignments

● Inexact lengths

This has the result that pipes are shown as not connected in COMOS.

COMOS 10.1.37.3 Process


You can now remove these inconsistencies by defining a tolerance for distances or lengths. If the deviation is within this tolerance, COMOS can correct the deviation.

You can find more information on this topic in the "Isometrics" manual, keyword "Specifying tolerances for pipes".

Revised geotypesGeotypes have been updated, new geotypes have been added and old geotypes that are not used have been removed.

7.3.2 FEED

Condensation curves - simulation objectYou can import condensation curve data from HYSYS to COMOS. To do so, use the condensation curves simulation object.

Using equipment lists and equipment bars● You have the option to display equipment in an equipment bar on process flow diagrams.

To do so, configure the properties of the report and the base objects for equipment.

● You have the option to display equipment in an equipment list. The equipment list is an evaluating report which lists recursively selected properties of the equipment.

7.3.3 P&ID

Using equipment lists and equipment bars● You have the option to display equipment in an equipment bar on P&ID. To do so, configure

the properties of the report and the base objects for equipment.

● You have the option to display equipment in an equipment list. The equipment list is an evaluating report which lists recursively selected properties of the equipment.

Using pipe lists and pipe bars● You have the option to display pipes in a pipe bar on P&ID. To do so, configure the

properties of the report and the base objects for equipment.

● You have the option to display pipes in a pipe list. The pipe list is an evaluating report which lists recursively selected properties of the pipes in the Navigator.

COMOS 10.1.37.3 Process


Using additional listsYou can create the following additional lists under a plant, a unit or a subunit:

● "PB.002 Machine list"

● "PB.003 Control valve list"

● "PB.005 Special equipment list"

● "PB.006 Conveyance means list"


Values from standard tables can be hidden at attributesYou will find an "Obsolete" column at the standard tables for nominal diameters. Using this column, you can hide entries of the standard table within attributes for newly created objects at which the standard table is stored. These hidden nominal diameters are then no longer offered for selection.

You can create and use the "Obsolete" column at other standard tables.

You can find more information on this topic in the "PipeSpec Designer" manual, keyword "Hiding values from standard tables".

7.4 Automation

7.4.1 EI&C

Siemens PIA LCP You can connect the "PIA Life Cycle Portal" catalog in COMOS with an online connection. The data is swapped by means of XML messages.

"Y00A05557 Placing information" attribute The "Object information" control group exists at the wire and at the shield on the "System data" tab. The control group includes the attribute "Y00A05557 Placing information". The field "Placing information" includes the following information:

Document.Label; Page Nr.; X-Quadrant; Y-Quadrant; X-Coord; Y-Coord

Note: When the same wire is placed multiple times, only the last placing information is saved.

COMOS 10.1.37.4 Automation


Numbering auxiliary contacts by means of a scriptThe auxiliary contacts for the elements of an auxiliary contactor can be continuously numbered by means of a script.

Action linesThe action line on the contact surface is calculated and is not part of the symbols. The action line is displayed when at least two elements (e.g., contacts or NO contacts) are listed in the contact surface.

The display of the action line is in the style of EN 60617-2.

NoteModified display of action lines

When you upgrade COMOS from an older version to an up-to-date version and a database of the type iDB is used, the display of the action lines also changes for documents which have already been revisioned.

Representation of automatic linksCOMOS can now also display links based on EN61082-1.

You set the display at the following position: Project options, "Automation > EI&C references" category, "Reference display" control group, "Reference version" list

You use the reference version to control which reference behavior is to be used.

● "Reference behavior up to COMOS 10.1. SP2"

● "Reference behavior according to EN 61082-1"

Master version of the templateUsing the "Generate version" button, you create a master version on the "Attributes > COMOS system" tab of the type template in the "Assembly Updater" control group.

You then use the "Assembly Updater" plugin to check if there is a difference to the version of the template at the instances and update the usage without structure and property check.

7.4.2 Logical

Parameter values of standard function blocksParameter values of standard function blocks are displayed on the function diagram. The parameter values can be edited on the function diagram. Empty values are displayed with the "#" symbol.

You can find more information on this topic in the "Logical" manual, keyword "Parameter values of standard function blocks".




"Update usages" plugin renamedThe "Update usages" plugin is now called "Assembly updater" and was moved to "Plugins > Automation > Assembly updater" in the menu.

EnumerationsYou can create enumeration types with the "Type configurator" plugin and define values at the enumerations. You can use the enumerations at control modules as well as control functions and exchange them with PCS 7.

Text 0/ Text 1With a control tag of data type BOOL, you can use the attributes Text 0 and Text 1 with the "Type configurator" plugin and exchange them with PCS 7.

Function blocksWith the "Type configurator" plugin, you can use the "Functions" button to open a list of the function blocks, select blocks and set them up as functions. They are participating in the exchange with PCS 7.

Textual references, global data references, block variable references Use the function diagram or the "Connection manager" plugin to create textual references, global data references and block variable references. They are participating in the exchange with PCS 7.

"Connection manager" pluginThe plugin is available in the menu under "Plugins > Automation > PCS 7 interface > Connection manager".

You can use the "Connection manager" plugin to interconnect inputs and outputs. The following interconnections are possible:

● TextualReference

● BlockVariableReference

● GlobalDataReference

Connections can be closed.

AppIDObjects which participate in the data exchange with PCS 7 receive an AppID. This ID is now matched during the data exchange instead of the name. You can rename objects and still match them bidirectionally.



Hardware parametersThe list of hardware parameters which participate in the exchange with PCS 7 has been extended. You find supported attributes in the "Attributes > Extended hardware" tab.

Negation of control tagsNegations of control tags placed on the function diagram are now also participating in the data exchange with PCS 7.

"Import / Export PCS 7" pluginThe filters in the "Import / Export PCS 7" plugin have been extended so that you can also select the new objects from the project and the library.

XML signature during import / exportTo describe the origin and integrity of the XML data, the XML file receives a digital signature during the data exchange. By checking the digital signature, you ensure that the XML file on the transfer medium has not been modified.

Version version of the templateUsing the "Generate version" button you create a master version on the "Attributes > COMOS System" tab of the type template in the "Assembly Updater" control group.

You then use the "Assembly Updater" plugin to check if there is a difference in the version of the template at the instances and update the usage without structure and property check.

7.5 Operations

7.5.1 MRO

Plant systemThe plant system is now available. A plant system helps you to define which items of equipment are logically connected to one another and, consequently, depend on one another during operation.

"Shift management" pluginThe "Shift management" plugin is available in the "Plugins > Maintenance > Resources > Shift management" tab. With the "Shift management" plugin, you can plan and organize production shifts.

COMOS 10.1.37.5 Operations


7.5.2 InspectionThe "Inspection" solution makes the plugins "Inspection" and "Inspection diagram" available.

"Inspection" pluginYou open the "Inspection" plugin with "Plugins > Maintenance > Inspection > Inspection".

The "Inspection" plugin is used to check pressure devices which require monitoring, such as pipes, apparatuses, and vessels. The plugin includes the planning, execution and evaluation of non-destructive material tests. You monitor pressure devices with the help of inspection plans. You create inspection plans directly underneath the pressure device.

"Inspection diagram" pluginYou open the "Inspection diagram" plugin with "Plugins > Maintenance > Inspection > Inspection diagram".

You can use the "Inspection diagram" plugin to graphically display the evaluation of the inspection maintenance plan. You can determine what is displayed in the graphic representation and show a legend. You can export the inspection diagram with the legend.

7.5.3 ShutdownThe "Shutdown" solution gives you access to the following plugins:

● "Shutdown management"

● "Quick edit"

● "Logistics"

PhasesIndividual work packages, such as maintenance or repairs, can cover several of these phases. You define and configure the phases in the "@40 > Y00 > A10 > B10 > Y00N00240 Turnaround phase" standard table.

"Shutdown management" pluginYou open the "Shutdown Management" plugin with "Plugins > Maintenance > Shutdown > Shutdown Management".

A shutdown or turnaround is the planned shutdown of a plant to perform scheduled maintenance. The "Shutdown Management" plugin supports you during preplanning, planning of the actual implementation, implementation, and the subsequent evaluation of shutdowns. The following functions are available:

● Editing shutdown data

● Bulk processing

● Clone shutdown

COMOS 10.1.37.5 Operations


● Evaluating maintenance plans of a shutdown

● Export

● Configuring menu for a shutdown object

"Quick edit" pluginYou open the "Quick edit" plugin with "Plugins > Maintenance > Shutdown > Quick edit".

You can use the "Quick edit" plugin to enter properties for individual nozzles centrally and add nozzle-related activities.

"Logistics" pluginYou open the "Logistics" plugin with "Plugins > Maintenance > Shutdown > Logistics".

The "Logistics" plugin makes the following functions available:

● Creation of deliveries for equipment

● Addition of COMOS objects to deliveries

● Creation of delivery notes

● Initiating transport to a different location

● Checking delivery for completeness

7.6 Mobile Solutions

RedliningThe relining function gives you the option of externally checking documents and uploading the redlining document later.

You can call the redlining of different users for a revision. For redlining to be displayed, at least one redlining must be uploaded.

The "Redlining" column has been added in the revision list; you use to control the redlining function.

ReauthenticationThe administrator can make a setting which requires that users must confirm changes in the task management prior to saving them with their user name and password.

COMOS 10.1.37.6 Mobile Solutions


7.7 Lifecycle

7.7.1 PQMPQM Configuration Tools and the "Document transfer" plugin are now available.

PQM Configuration ToolsPQM Configuration Tools support you in qualification planning and during qualification management. The following functions are available among others:

● Defining the project area of application

● Defining the project phases

● Specifying roles

● Specifying the document catalog

● System-supported creation of document types depending on the engineering phases

● Checking completeness before phase completion

"Document transfer" pluginThen "Document transfer" plugin provides a new user interface which gives you an overview of multiple documents. You can select and deselect these documents in order to process them further together.

The following functions are available in the "Document transfer" plugin for joint processing of documents:

● Copying revisions

● Exporting documents

● Printing documents in files

● Importing documents

● Re-importing documents

COMOS 10.1.37.7 Lifecycle



Exporting COMOS pipe specs to PDMSIn COMOS 10.1.3, you can export COMPOS pipe specs to PDMS with the help of the Generic Data Mapper and the COMOS PDMS Engineering Adapter.

● "Generic Data Mapper" plugin:The Generic Data Mapper is a generic tool that allows you to configure the export of data from one system to another system. In version 10.1.3, you use the Generic Data Mapper to configure the export of pipe specs to PDMS. You access the data schema of the source schema and the target schema in the Generic Data Mapper. You create rules that you use to control the following for any input quantity by assigning schema elements of the source system and the target system:

– Which objects are generated during export from the source system how many times in the target system

– Which attribute values are transferred to the objects in the target system

– How the objects created in the target system are interrelated

You can control the data export very accurately by specifying rules which further specify the objects to be exported.You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Generic Data Mapper" and "Exporting COMOS pipe specs to PDMS".

● COMOS PDMS Engineering Adapter plugin You execute the pipe specs export in the "COMOS PDMS Engineering Adapter". Here you specify the export quantity which is to be exported based on the rules that you have created in the Generic Data Mapper.

PDMS Engineering Interface: Filtering and tagging requested objectsOnce you have loaded objects to the COMOS PDMS Engineering Interface, you can filter or tag these objects according to the following new criteria:

● "What's new"Displays all COMOS objects that are new and therefore do not exist in PDMS.

● "To be assigned"Displays all COMOS objects that exist in PDMS but are not assigned.

● "Assignment is OK"Displays all COMOS objects that have already been assigned to PDMS objects.

● "Assignment is invalid"Displays all COMOS objects that have an invalid assignment.

You can also create your own filters and tag objects according to the filter condition.

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



PDMS Engineering Interface: Creating objects in PDMS in the "Potential owners" windowThe command "Show potential owners" in the context menu of an object in the "Scope" area of the interface opens the "Potential owners" window.

In the past, you could use this window to display potential owners of a selected object. You can now create the object as well as other objects not yet created in PDMS directly in the window. You can also determine at which location in the PDMS tree each object is to be created.

You can find additional information on this topic in the "3D Integration Operation" manual, keyword "Displaying possible owner for an object".

PDMS Engineering Interface: Creating three-stage structure for nozzles and pipe parts in PDMS● Equipment with nozzles:

When you request equipment with nozzles from COMOS in the interface, you can specify that a three-stage structure is automatically created in the interface.

● When working with KKS: for pipe parts, such as valves, for example:When you are working with the KKS labeling system and request pipe parts in the interface which are included in a two-stage structure in COMOS, you can specify that a three-stage structure is automatically created in the interface.

This is made possible with the introduction of an "Owner subclass" attribute in the properties of the "Cable" and "Tagged item" subclasses. In it, you set which other subclass is to be used for the generation of the owner.

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Specifying fixed owner for objects of a subclass".

PDMS Engineering Interface: Tags possible at subclasses, "Owner restriction rules" tab in the "Substring" column

Instead of a string, you can also specify a global or local tag for attribute filters in the "Substring" field.

Exception: You cannot use local tags here which get their value from PDMS.

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Specifying owner restriction rules".



Adjustment-related changes in the cDB 88.1 About this chapter

Deviating functionality for COMOS when using the cDBIf you are working with the cDB, you must make different settings for some functions or the functionality can deviate from the functionality for iDB. Before you use new functions, check in the "cDB" chapter if there are deviations for individual functions regarding procedures or functionalities.

8.2 COMOS 10.1.1

8.2.1 COMOS Administration

Controlling grayboxes with attributeThe following further development was made for the standard database in COMOS 10.0:

"@10 > BAS > 3 > 06 > SYS > GrayboxSelectionMode"

The selection mode of grayboxes can be switched with the help of the attribute on the main document.

● GrayboxSelectionMode = 0 The object itself is selecting by clicking an object within the graybox.

● GrayboxSelectionMode = 1 Default. Compatible with behavior in COMOS 9.2The entire graybox is selecting by clicking an object within the graybox. The required object alone is selected with a second click on the object.

8.2.2 COMOS menu when using the cDB

RequirementsThe COMOS menu changes depending on the COMOS version and the database type. This chapter describes the changes under the following circumstances:

● Change from COMOS 10.0 to COMOS 10.1

● Retaining the cDB


List of unavailable entries● View > Engineering tasks

● Administrator > Base data > Database adjustments

● Extra > Viper 3D Editor > Electrical engineering

● Plugins > Mechatronics > Plant and machine configuration

● Plugins > Mechatronic > Path-time diagram

List of entries with text changes● Extra > Viper 3D Editor

Changed to: "Extra > 3D Test"

● Plugins > Basic > PDMS interfaceChanged to: "PDMS PipeSpec Interface"

● Plugins > Basic > Task ManagementChanged to: "Task management"

● Plugins > Automation > PCS 7 interface > Create templatesChanged to: "Create variants"

● Plugins > Automation > Bulk processing of semi-open connectorsMoved to: "Plugins > Automation > Interfaces > Bulk processing of semi-open connectors"

List of new entries● Administrator > Base data > String rule manager

● Plugins > Basic > PDMS Engineering Interface

● Plugins > Basic > Walkinside object assignment

● Plugins > Basic > Data Aggregation

● Plugins > Automation > PCS 7 interface > Type configurator

● Plugins > Automation > PCS 7 interface > Update usages

● Plugins > Automation > Cabinet Equipment wizard

● Plugins > PQM > DVM queries

● Plugins > Collaboration > COMOS Mobile Document Review > Send

● Plugins > Collaboration > COMOS Mobile Document Review > Outbox

Adjustment-related changes in the cDB8.2 COMOS 10.1.1


8.2.3 COMOS Web

Saving the "COMOS Mobile Document Review" data management in its own base objectYou set the free storage of the "COMOS Mobile Document Review" data management in a base object other than SO1 in the system project. You create the option for setting its own base object yourself.

Procedure1. Open the system project.

2. Under the "@PROPAR Project parameter" node, create a tab with the name "COM002".

3. Create a reference attribute with the name "COM2001" on the "COM002" tab.

4. Switch to the project properties.

5. Select the required base object in the new reference attribute.

6. Restart "COMOS Mobile Document Review".

8.2.4 COMOS Material Management

Detailing pipes with several branch nominal sizesThe Material Management Assistant now offers material with several branch nominal sizes in the "Detailing pipes > Manual Estimation" tab. When an object with several branch nominal sizes is adopted in the "Estimated" tab, these nominal sizes are listed below one another in the "Manual Estimation" tab. If the branch nominal sizes are approved according to the pipe spec definition, you can enter quantities in them.

Capturing unit of objects during CSV importSo far the unit of imported objects has only been captured as character string without function in the "MTO.Unit" attribute. COMOS can now apply the unit in the "Unit" attribute property during import in the "MTO.Quantity" attribute.

The administrator has to adapt a mapping table in the configuration object for this purpose:

1. Open the "Attributes > General" tab in the properties of the configuration object.

2. Enter the units specified in the imported CSV files in the "MTO Unit" column of the "Units for quantity summation" control group.

3. Enter the group of the respective unit to which the value of the "MTO Unit" is to be assigned in the "Unit group" column.You can find additional information on this topic in the "System types properties" manual, keyword "Assigning units".



4. In the "Unit" column enter the respective unit to which the value of the "MTO Unit" is to be assigned.

5. You can find additional information on this topic in the "System types properties" manual, keyword "Assigning units".

Result: A corresponding unit is entered in the properties of the "MTO.Quantity" attribute according to the entries in this table. If you change the unit afterwards in the properties, the value of the quantity is recalculated.

T-pieces are automatically estimatedT-pieces on action lines are automatically detected when estimating material on an P&ID. Nominal size 1 and nominal size 2 are captured, among other values.

Displaying the delta of amounts between the last released revision and the current revisionThis new functionality replaces delta lists.

You can check the latest revision of an MTO document with a released version for deviating amounts. To display the deviations in an MTO document, you must edit the report template of the MTO document in the base project.

1. Define two new columns in the base report in the subreports "MTOContent" and "MTOTitle":

– Column for delta valuesThe deviating amount in the MTO document is specified here.

– Column for the statusHere you specify in the MTO document if a material group was added, removed or if there were no changes.

2. Specify in the script in the report template of the MTO documents how these values are to be determined.ExampleDim DeltaValueDim DeltaStatusDeltaValue = CurrentItem.GetAttributeValue("DeltaValue") DeltaStatus = CurrentItem.GetAttributeValue("DeltaStatus")

Result

When you make a revision, the columns with the corresponding information are output in addition in the MTO document.

Displaying the delta of the amounts between two random revisionsThis new functionality replaces delta lists.

You can check any two released versions of an MTO document or a master document for deviating amounts. The results are saved in a temporary delta document.



Requirement

● The option "User can create delta documents" is activated in the configuration object in the "MTO documents" tab.

● The report template, the CSV delimiter and the export directory were defined in the configuration object in the "Delta documents" tab.

Procedure

1. Open the "MTO Documents" tab in the "Material Management Assistant".

2. Drag-and-drop a document from the "MTO Documents" control group to the "MTO document" field of the "Delta documents" control group.

3. Define which revisions are to be compared.

4. Click the "Create PDF delta" button to save the results in a PDF file.Click the "Create CSV delta" button to save the results in a CSV file.

Note

If the export does not start, the two DLLs "<Name>.dll"; "<Name>.dll" must be added manually to the Windows system folder: the path under 32-bit operating systems is "<Windows directory>\system32", under 64-bit operating systems "<Windows directory>\SysWOW64". The files are provided by COMOS Support, if necessary.

The Visual C++ .NET 2003 runtime libraries are no longer offered as installer by Microsoft.

Result

The file is stored in the directory which the administrator has specified in the configuration object.

Tabs in "Material Management Assistant" were revisedThe "Documents" tab was removed and its contents moved to the "MTO documents" and "MRP documents" tabs.

Authorization settingsThe administrator can specify for select actions if the user may execute these during the creation of MTO documents.

Setting: Configuration object, "MTO documents" tab, "Authorization settings" control group

Updating MTO documentsIn the "MTO documents" tab in the "MTO documents" control group, you can update the documents included in a document package in the context menu of the document package. The update is possible for the following material lists:

● "Estimated MTO"

● "Current MTO"

● "Released MTO"

The current status of the MTO document appears in bold in the context menu.



8.2.5 Isometrics

ROHR2 exportYou can export an isometrics into a file in NTR format which you can import in the ROHR2 application from SIGMA Ingenieurgesellschaft mbH.

Procedure

1. Select an isometrics in the Navigator.

2. Select the "Export > ROHR2..." command in the context menu.The "Export to ROHR2" window opens.

3. Select how the data of the isometrics are to be saved.

– "Without subdirectories" optionThe name of the file is formed from the object names in the structure of the isometrics.

– "With subdirectories" optionThe structure is reproduced in the Navigator through folders. The file is stored in the folder that maps the owner. The file receives the name of the isometrics.

– "In a file" optionThe file is given the name that you have entered in the "File selection" field.

4. Define the storage location and the file name, if necessary, in the "File selection" field.


Result

All relevant data for ROHR2 are exported into an NTR file.


Specifying the fastening partsYou can specify for components which fastening parts are to be used when the components are connected with each other in 3D.

The following has been changed in COMOS for this purpose:

● The attributes "VD13", "VD23", etc. have been renamed to "Attachment type" at the objects in the PPC catalog in the "Attributes > 3D geometry" tab in the "Nominal sizes / connection types main passage" control group. The stored standard table has been expanded by the entries which must be selected to specify the fastening parts.

● A new type of connectors has been defined by which fastening parts can be connected with other objects regardless of pipe connections. The connectors are named "CM<counter>"".

The new function is available for the following objects:

● Lap joint flange

● Union nut



To use the function, proceed as follows:

1. Select one of the newly added entries in the base data of a component in the PPC catalog in the "3D geometry" tab in the "Attachment type" list. The old entries are identified by "(old)".

2. Open a pipe spec with the edited components in the PipeSpec Designer and select the "Fastening table" tab.You see a matrix of all fastening types used within the pipe spec. Fastening parts are already preset in the matrix.

3. You can select other fastening parts for the combinations of mounting types.

Defining new attachment typesTo define new attachment types, edit the standard table "@3D > 01 > BC > 03 Attachment types".

1. Select a name with a ten-digit number. The value in column "Value 1" must match the value in the column "Name".

2. Enter the name of another attachment type in the column "Value 4" which you want to specify as standard counterpart. When two components are connected with these attachment types, no additional fastening part is necessary by default.

Specifying or changing attachment typesOptional: To specify or change the defaults for combinations of attachment types, edit the object "@VIPER > @Q > AttachmentTypes Attachment type combinations".

● Enter additional combinations in the "Attributes > Attachment type information" tab in the "Alternative counter-part attachment types (amendments to default)" which can be connected directly with each other without fastening parts.

● On the "Attributes > Attachment type information" tab in the "Default fastening connections" table specify which type of fastening parts is to be used for which combinations of attachment types by default. COMOS uses the first fastening part of the pipe spec, the type (function code) of which corresponds to the type specified here.


PDMS: New interface "COMOS PDMS Engineering Interface"In addition to the existing interface you now have access to a new interface. The following terminology has been defined to distinguish the two:

● Existing interface: "COMOS PDMS Interface"

● New interface: "COMOS PDMS Engineering Interface"



Major changes to the existing interface:

● The user works on the PDMS page and can execute all actions from there.

● The administrator defines in advance with the help of queries for a user or a user group which COMOS objects they can upload to the interface to read or edit them.

● The new interface offers a tree representation of the loaded COMOS objects and additional options to compare the objects with each other in both applications.

The interface offers the following functionalities:

● Create individual objects in PDMS

● Create hierarchies in PDMS

● Compare and update attributes

● Assign objects in COMOS and PDMS to each other

● Navigate between COMOS and PDMS

Note

If you do not wish for a user to be able to edit the link database from Walkinside, the "Comos.C3DView.AutoAssign.Walkinside" file must be deleted from the "plugins\Application" directory, which is located below the Walkinside installation directory, after the setup.

This removes the COMOS Auto Assign plugin. It is no longer displayed in the Walkinside menu. The navigation between COMOS and Walkinside is still possible.

If you want for the user to administer the link database from Walkinside, select the "Install Comos Auto Assign Administration plugin" option during the setup. If this option is activated, the "Comos Auto Assign" plugin is installed. This option is deselected as default.

PDMS: Installation mode Citrix client (Silent Mode)The installation in Silent Mode takes place in the background and is controlled by a text file in which the administrator has previously entered all relevant information. You cannot make any additional entries during the installation.

PDMS: Feedback modeIf Feedback mode is activated, both applications have bidirectional write access to the data.If Feedback mode is deactivated, only COMOS has write access to Walkinside data.

The Feedback mode is activated by default. To be able to deactivate this mode, an administrator must create an option in the "Attributes > General" tab of the "@PDMSMAP" object. The name of the attribute must be "Y00A00728".

1. To activate Feedback mode, activate the newly created option in the "Attributes > General" tab.

2. To disable Feedback mode, deactivate the newly created option in the "Attributes > General" tab.

COMOS 3D ViewingInstallation of "COMOS Walkinside Integration"



"COMOS Walkinside Integration" is the interface between COMOS and the 3D Viewer application COMOS Walkinside. To use COMOS 3D Viewing, you must install the interface.

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Installing COMOS Walkinside Integration".

Assignment of COMOS objects and Walkinside objects

You can now assign objects by means of a new plugin to enable navigation. You have a unique identification created for a defined amount of objects on the COMOS page and on the Walkinside page in the plugin. You have the identification created with the help of scripts. The related objects on the COMOS page and on the Walkinside page must have the same identification.

You can find additional information on this topic in the "3D Integration Administration" manual, keyword "Configuring navigation".

Exporting COMOS objects with the help of a query

This function collects specific objects which are already in Walkinside and for which you have created an assignment in Walkinside.

Example scenario:

● You only want to view objects in Walkinside which have to be maintained.

● You collect these COMOS objects in a query and export it to Walkinside. A view of these objects is temporarily displayed in Walkinside.

8.2.8 P&ID

XMpLant exportCOMOS can now export files created with XMpLant 3.3.3.

XMpLant import● COMOS supports only files with XMpLant version 3.3.3 for import.

● An administrator can enter the subprogram OnXMpLantImportDone at P&ID objects or at P&ID in the script. As soon as the XMpLant import is complete, the script is executed for each engineering object.

● Due to two additional import options you now have the option to identify changes in case of a reimport and determine the handling of specific objects.The following import options have been added in the "Import and dissolve drawing" window:

– "Import into new working layer" option

– "Remove not contained objects" option

You can find additional information on this topic in the "P&ID Operation" manual, keyword ""Import and dissolve drawing" window".



PDF importAll texts of a PDF are imported into COMOS with a PDF import. COMOS creates new objects for each text in a text field according to rules defined by an administrator.

Prepare the database

1. Create a new base object under the following nodes: "@99 > A20 > M00 > A50 > A30".Class: "Dataset", Subclass: None.

2. Create four list attributes for the object. The attributes must have the following NestedName:

– "Y00T00001.Y00A04652" (Local rules)

– "Y00T00001.Y00A04653" (Local rulesets)

– "Y00T00001.Y00A04654" (Global rules)

– "Y00T00001.Y00A04655" (Global rulesets)

3. Create two columns for each list attribute with the following names:

– "Y00A00147" (Name)

– "Y00A01154" (Data)

Create a ruleset for the PDF import

1. In the COMOS menu, select the command "Administrator > Base data > String rule manager".The string rule manager opens.

2. To create a new ruleset, click "New" in the "Selected ruleset" control group.Enter a name for the ruleset and confirm your entry.

3. To add an existing rule to the rule set, select the rules in the "All rules" area.

4. Click the "Left" button.The rule is entered in the "Rulesets" control group.

5. To create a new rule, click "New" in the "All Rules" control group.See section "Create a rule for the PDF import".

6. Optional: Enter some example text in the "Text" column of the "Preview" control group to check whether the rules of the ruleset recognize the text and therefore whether an import of this text will work.When a rule applies, it is displayed in the "Matching rules" column.

7. Optional: Click the "Save" button.Save the entered text to a CSV file in order to reuse it when you create new rules.


The new ruleset is saved. When the user starts a PDF import, the ruleset is offered for selection in the "Ruleset" list of the preview window.

Create a rule for the PDF import

1. Click the "New" button in the "All rules" control group.

2. In the "Data assignment" area, click "Create empty rule".



3. Click "Edit rule".The "Splitting" window opens.You can find additional information on this topic in the "COMOS Automation Interfaces" manual, keyword "Working with the "Splitting" dialog".

4. Select an item from the "Select an operation" list.

5. Select an item from the "Predefined expressions" list.

6. Define the rules for the selected item in the "Regular expression" field.


8. Drag&drop a base object from the "Data assignment" area to the "Base object" field.Allowed:

– Base objects (CDevice)

– Documents

9. Optional: Click the "Extended rule options" button. Additional information about this topic is available in the "COMOS Automation Interfaces" manual, keyword "Extended rule options".

10.Confirm your entries.

8.2.9 Troubleshooting during excessive GDI resource consumption with COMOS

Problem descriptionCOMOS may consume excessive GDI resources when you use Windows 7 SP1 or Windows Server 2008 with Citrix. Under certain conditions this can result in the user interface or its elements not being displayed correctly in COMOS. This affects mainly queries and evaluating reports.

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

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



8.3 COMOS 10.1.2

8.3.1 Pipe Part Finder

Change for the cDBFilters that begin with "@UserFilter" are no longer required to control the display of structure nodes. All filters that begin with "@UserFilter" are ignored. For the structure nodes to be displayed again at the template pipe specs, delete these filters.

8.3.2 Logical

Moving parts of the sequence chain up or down with the context menuYou can move all sequence chain symbols that are located next to or below a start symbol that you selected. You define the number of grid points by which the objects are moved up or down.

If necessary, the sequence chain is moved so that it spans more than one sheet. COMOS prevents symbols from being pushed together.

Moving or copying sequence chain objects with the mouseYou can use the mouse to cut or copy sequence chain objects on a function diagram and paste them at a different point of the sequence chain.

The sequence chain objects are reconnected automatically.

Navigating between half open partner connections in function diagramsYou can navigate from a half open connection to its half open partner connections and back as follows:

● Using the <Page Up> and <Page Down> keys

● Using the context menu "Connection > Navigate to successor"

● Using the "Navigate to successor" and "Navigate to predecessor" buttons on the toolbar of the report

The counter-connection is selected and zoomed in on. It can be located on the same page of the function diagram, on a different page, or on another function diagram. In the latter case, the other function diagram is opened.



8.4 COMOS 10.1.3

8.4.1 COMOS Administration

Automatically creating elements with multiple stages1. Open the project properties.

2. Activate this option:"Element: Default" under element with "Virtual: Off" permitted"


4. Open the properties of a base object.

5. Create an element on the "Elements" tab.

6. Open the properties of the element.

7. Configure the "System" tab:

– Creation option: "Normal"

– "Virtual" control group: "Off"

8. Optional: Create more elements underneath the element.

– Open the properties of the subordinate element.

– Configure the "System" tab:

– "Virtual" control group: "Default"

The elements are now created with two stages.

The elements are automatically created for the engineering object. Depending on the structure of the elements in the base object, the elements are also created with multiple stages.


Exporting COMOS pipe specs to PDMSA sample mapping file is not available for the cDB for the pipe specs export to PDMS. You must create your own mapping file.

Automatically adding additional hierarchy levelsYou can specify that a hierarchy level is added in the "COMOS objects" area of the PDMS Engineering Interface for COMOS objects which are assigned to a specific subclass and have a two-level structure.



To use this function with the cDB, you must create the "OwnerSubclass" attribute:

1. Open the base object of the subclass "Cable" or "Tagged item".

2. Open the "Attributes > General" tab.

3. Create an attribute with the following properties:

– "Type of display": "Edit field"

– "Description": "Owner subclass"

– "Name": "OwnerSubclass"

– "Type": "Alphanumerical"

– "Standard table": "@3D > 00 > PDMS > 08 > 01 Subclasses"

8.4.3 Isometrics

Specifying tolerances for pipesYou specify the direction tolerance at the following attribute at the pipe: "SYS.DIR0EPS"

You specify the length tolerance at the following attribute at the pipe: "SYS.LENGTHEPS"

Procedure:

1. Create the attributes in the database.The attributes must have the following properties:

– "Name": "DIR0EPS" or "LENGTHEPS".

– "Type of display": "Edit field"

– "Type": "Alphanumeric"

2. Place the attributes at the base object of a pipe on the "Attributes > System data" tab.

3. Enter a value for a direction tolerance in the "DIR0EPS" field.Possible values for the deviation: 0.02 to 0.0000001The value "0.02" corresponds to a deviation of approximately 1° as compared to the main direction.

4. Enter a value for a length tolerance in the "LENGTHEPS" field.Possible values for the deviation: 0.1 mm and over.

8.4.4 Mobile SolutionsIf you want to set the Mobile Solutions dashboard when using the cDB, create a new tab with a link attribute in the project properties of the system project.



Procedure1. Open the system project.

2. Create a new tab with the name "COM002" for the project properties under the "Options" tab.

3. Create a "Mobile Solutions base project" link attribute in the new tab with the name "COM2001".

4. Set a reference to the required base project in the new link attribute.

5. Save your settings.

8.4.5 FEED

Condensation curvesTo work with condensation curves, append the condensation curves simulation project to the database with the HYSYS name "CondensingCurve". The simulation object must be named "CCURVESIM". The tab names are identical to the names of the tabs in the HCSIM simulation object. You adapt the attributes on the "Vapor, Liquids" and "Data light and heavy liquid" tabs to the condensation curve.

Some attributes do not exist in the cDB. You must create these attributes yourself:

● Volume flow of vapor/ gas (Y00A03505)

● Z-factor (vapor) (Y00A05414)

● Z-factor (complete liquid) (Y00A05414AA02)

● Relative density of the light liquid (Y00A05411)

● Z-factor of the light liquid (Y00A05416)

● Relative density of the liquid (Y00A05410)

● Z-factor (liquid) (Y00A05415)

8.4.6 EI&C

Action lines in the style of EN 60617-2Action lines are not part of the symbol but are calculated. Below you will find a description of how to introduce the display of action lines in the style of EN 60617-2 in databases of the type cDB.



Requirement: You have access to a current iDB.

NoteCompatibility break of the display

Do not implement the new display of action lines or the new version of the contact surface if you depend on compatibility within a project.

NoteObject structure of objects in the cDB must match object structure of the iDB

The standard tables and attributes must be inserted in the cDB in the same structure as in the iDB.

The calculation of the display of action lines is complex. Below you will find a description of how to introduce the new display by means of templates in the iDB also in a cDB.

● Standard tablesThese standard tables must be exported from the iDB and imported into the cDB. A change of existing cDB standard tables is complex, and the new functionality cannot be guaranteed due to possible customizing.

– ""Y10 > M41 > A10 > Y10M41N00003"Includes symbol script for contact surface.The iDB-specific symbol type name "Name="M41_P2" must be renamed in the cDB-specific symbol type names "Name="DETAIL".

– ""Y10 > M41 > A10 > Y10M41N00017"Includes symbol script for contact rails.The iDB-specific symbol type name "Name="M41_P2" must be renamed in the cDB-specific symbol type names "Name="DETAIL".

– "@40 > Y00 > A10 C10 > Y00N00471"List for action-line-specific labeling of objects (None/ Contact surface/ Contact rail). The position of the standard table is random because this list is linked by means of the attribute Y00A04618.

● Attribute at MainDeviceExample: at the Power contactorThe attribute, "Showlinkelements" in the original, indicates by means of the stored standard table in which form the elements are displayed:

– Contact surface

– Contact rail

– No display

"Y00T00001 > Y00A04618"

– Attribute includes the link to Y00N00471. The attribute is used at a contact switch, for example.

● Specify the start point of the action line in the symbol script of the MainDevice

– Example: "DrawText p10, "%N WWL0%", 0 ,1"



● Attributes at the elements of the MainDevice

– "Y00T00001 > Y00A03392"Attribute contains the link to "Y10 > M41 > A10 > Y10M41N00017" for contact railsThe attribute is used to select the required symbol script for the display from the linked standard table.

– "Y00T00001 > Y00A03071""Checkbox" type of display, "Search subobject" descriptionYou use the attribute to control whether elements below the elements are to be integrated in the contact surface.

● The following script options are available in the report template for the position of the contact surface:

– SO_ContactMirror_X– SO_ContactMirror_Y

Representation of automatic linksCOMOS can display links in the style of EN61082-1. To do so, you must create a project property as follows:

1. Open the system project.

2. Create the standard table "Link version".Create the following two entries in the standard table:

– Name: "0" , description: "Reference behavior until COMOS 10.1 SP2", value "0"

– Name: "1" , description: "Reference behavior according to EN61082-1", value "1"

3. Select the "@PROPAR" object in the "Base objects" tab.

4. Open the properties of this object and select the "LINK EE/EI&C links"

5. Create the attribute "Link version".

6. Link the attribute "Link version" with the "Link version" standard table.


8. Change to an engineering project. There you set the project property "Link version" to the value "Reference behavior according to EN61082-1".

Saving the wire position at the objectCables, wires and shields can be created as objects in COMOS and placed on a connection. COMOS can save the position of the object on the report at cables, wires and shields. Proceed as follows to do this:

● Create the following attribute at the base object of the wire or the shield:

– Tab "Y00T00001", attribute "Y00A05557"

– Description: "Placing information"

– Mode: Read only

● COMOS automatically writes the following array into the attribute label:



● Document.Label; Page number.; X quadrant; Y quadrant; X coordinate; Y coordinate

● Read the array by means of the script (starting at 0)

For wires, the following applies:

● If a wire is placed multiple times, only one item of placing information is required.

● If a wire is placed on different document types, the placement on a current diagram is preferably output.

● If all placements of a wire are deleted, the "Y00A05557" value is empty.

● The information is updated when the wire is created, moved or deleted on the report.

● The information is updated when the wire is removed at the COMOS connector. This is technically the time when the pointer to the wire is removed at the COMOS connector.

● The information refers to the intersection of the wire symbol in the report with the connection.

For cables, the following applies:

● A cable basically behaves like a wire.

● When a cable is placed multiple times, the information of the last processed placement is saved.

For shields, the following applies:

● The information is updated when the shield is created, moved or deleted on the report.

● The information refers to the point of origin according to the symbol script.

Saving and exchanging values for function parameters

AimThe user can place function blocks on a function diagram. The following operation mode is possible:

● The function blocks are connected with control modules.

● The values of the function parameters are displayed as values of the control module.

● The values can be processed at the control module.

● Unconnected connectors on the control module are displayed by means of the placeholder #.

● The values can be exchanged with PCS 7.

ProcedureThe following requirements must be met to use the operation mode above:

● The function blocks must be created as standard function in PCS 7 with the exception of AND, OR, XOR, NOT.

● ConnectorsFunction blocks in the style of IEC61131-3 are used.Open the properties of a function block connector. Click the "Extended" button. Enter the "LockingValue" entry in the extended properties (free attributes).



● SymbolsThe symbols of the function blocks show "LockingValue" as editable value. To do so, the symbol scripts must be edited as follows:

– Call the function ComosGeoSymbols.DrawingUtilities.DrawEditableTextField4Connector. Example:ConnectorName = ""FI" + cstrg(i+1)CreateObject("ComosGeoSymbols.DrawingUtilities").ComosGeoSymbols.DrawingUtilities.DrawEditableTextField4Connector Me, PARAM, ConnectorName, "LockingValue", 0, (-i)*8

– Display of "LockingValue" as editable value. Example:Dim arrParamArrayDim objConnsGenpArray = Array()inputConNum = CStr(CInt(abs(p4.y/8)) + 1)Set objConnsGen = CreateObject("Comos.SolidBaseUtilities.ConnectorGenerator")If Not objConnsGen Is Nothing Then ReDim arrParamArray(13) Set arrParamArray(0) = PARAM arrParamArray(1) = "FI" arrParamArray(3) = "S" arrParamArray(4) = "inputConNum" arrParamArray(5) = "I" arrParamArray(6) = "ANY_BIT" arrParamArray(8) = "N" arrParamArray(9) = "N" arrParamArray(10) = "?IN:" & inputConNum arrParamArray(12) = "N" arrParamArray(13) = "N" Error = objConnsGen.CreateOrUpdateComosConnectors(arrParamArray)End If

– The last two parameters in the example above determine the position of the text field in relation to the function block. This information is to have the same values as the call DrawText.

● Functional classification

– The functional classification "D020 Editable text field for connectors" exists

– The functional classification "D020 Editable text field for connectors" is set for:Standard functionsControl modules

● ExamplesExamples for function blocks in the style of IEC61131-3:

– "@03 > FUP > D > 01 > AA > AA"

– "@03 > FUP > D > 01 > AA > AB"



The placeholder # at unconnected connectors of the control module can be hidden as follows when printing:

● Options script of the report:HideEmptyInPlaceEditOnPrint = TRUE

Numbering for auxiliary contacts for Siemens contactors

AimOld: The switch blocks are created as elements. When a new switch block is created, the collection of elements is checked and the next available name according to the text mask at the base object is assigned. Example: The first auxiliary switch block contains the label "Position 1", followed by "Position 2" and so on. The label of the contact connectors is based on the label of the switch block.

New: The auxiliary contacts for the elements of an auxiliary contactor can be continuously numbered by means of a script. Area of application: Auxiliary switch blocks as contact adapter for contactors.

1. The switch blocks are initially named in the usual way according to the text mask. The text mask can have any design.

2. The user can then trigger a new assignment of the labels by means of a context menu.

3. The number according to the label may also be applied to the numbers of the connectors, if necessary. Example: Label of the auxiliary switch block "5", label of the connectors "51" and "52".

ProcedureThe following requirements must be met to use the operation mode above:

● Structure of the objectsThe main contacts and the auxiliary switch blocks must be located flat under one common owner.

● Classification

– Switch blocks: Functional classification "AN"

– Main contacts: Hierarchical classification "HA" or "HB"

– Main contacts: Functional classification "MC"

● Attributes

– Tab "Y00T00001", attribute "Y00A03392"



● Script

– The content of the script block "GetConnectorLabel" must be moved to the script block "GetConnectorLabel2". "GetConnectorLabel" must be empty after this work step.

● Context menu

– Implementation of a context menu with the function ELOLib.RelabelContactStructure is called

– Example:Function OnMenuExecute(ID,Context)If ID = "PMID_RenameStructure" Then Set EloLib = Context.ComosObject.Workset.Lib.Elo EloLib.RelabelContactStructure(Context.ComosObject)End IfEnd Function

Process:

RelabelContactStructure collects all elements concerned in two arrays:

● First array: "Y00T00001 > Y00A03392"Takes into account all elements which have set any value at this attribute. The element is labeled as component of a contact surface in this case.For an element to be taken into consideration, the OwnLabel must be numerical or empty. The label of main contacts according to the classification "MC" and "HA"/"HB" is not taken into consideration.

● Second array: Functional classification "AN"This classification permits automatic numbering for auxiliary switch blocks. Each array is sorted according to the Label.

All elements are numbered consecutively according to the following order:

1. Elements directly below MainDevice

2. Elements below the auxiliary switch blocks according to sorting by label

Example:

● "@01 > EIC > 01 > 340 Relay, contactors > H Auxiliary contactor"


8.4.7.1 Creating the Master Version

IntroductionYou have the option to set a version at the template.

You then use the "Assembly Updater" plugin to check if there is a difference in the version of the template at the instances and update the usage without structure and property check. See also chapter Updating assemblies (Page 88).



You can create one version for each COMOS session.

RequirementThe object which serves as template must meet the following criteria:

● The "Y00T00005 COMOS system" tab exists.

● The "Y00A05563 Template version" attribute exists on the "Y00T00005 COMOS system" tab. The attribute is read-only because the value is set by the script. It is only visible at the base object.

● The "Y00A05564 Generate version" button exists on the "Y00T00005 COMOS system" tab. The following script is stored:Sub OnClick()'Event: After pressing the buttonSet ObjicUtils = CreateObject("Comos.IC.Utilities.Utilities")strRes = ObjicUtils.UpdateTemplateVersion(ThisObj.GetSpecOwner)If strRes <> "" Then MsgBox strResEnd IfEnd Sub

Procedure1. Open the properties of the type which serves as template.

2. Select the "COMOS system" tab.

3. Click on the "Generate Version" button in the "Assembly Updater" control group.A window opens.

4. Confirm the query if you want to create a new version.


8.4.7.2 "Y10M00N00031 Assembly updater property assignment"

Area of applicationThis list includes attributes that are matched in the "Assembly updater" plugin in "General" mode and are updated, if necessary.

Node"Standard tables > Y10 > M00 > A20 > Y10M00N00031 Property mapping"

User-defined attributes for the matching● Name (abbreviation: @N)

● Label (abbreviation: @L)



● Description (abbreviation: @D)

● CDevice (abbreviation: @C)

● MappingTableXML (abbreviation: @M)

● BackpointerSpecificationsWithLinkObjectAndName (abbreviation: @BS). Example "@BS:Y00T00093.Y00A00159"

● All attributes (if LinkObjects exist, they are taken; otherwise Values). Example "Y00T00093.Y00A00159"

The abbreviations refer to the VSUI Notation.

Attributes that are always matched● Connector (ConnectedWith, Connector Attribute)

● Backpointer

● DocObjs

● Owner

● Unit

● Location

● Implementation

Structure

Column Description"Name" You enter a name according to the following scheme in this

column: A+ 3 numbers incremented in steps of 10. For ex‐ample: "A010"Default: "A010"

"Description" Enter the description of the object whose attributes are eval‐uated in this column. For example: "Action"Default: "Default"

"Value 1" Enter the hierarchical or functional classification of the base object in this column. User classifications are permitted. For example: "C1: M00.A010.A040"Defaults: "Default"

"Value 2" Enter the attributes of the object that are to be matched. For example: "@N;@L;@D;Y00T00001.Y00A03136"Default: "@N;@L;@D;Y00T00093.Y00A02222;Y00T00093.Y00A02224;SIE0006.SIE0060;SIE0006.COM0002;Y00T00025.Y00A00253;BMK.BMK32_FUE;BMK.BMK32_DET"

The "Assembly updater" plugin first checks whether a classification has been stored for the object in the standard table. If the plugin does not find a classification, it uses the default definition.



ExampleAn example of a filled standard table is available here: Standard tables > Y10 > M00 > A20 > Y10M00N00032 Assembly updater property assignment PCS 7". When you are using the "Assembly updater" plugin in "PCS 7" mode, this standard table is evaluated.

8.4.7.3 Updating assemblies

Initial situationA template that is used in your engineering project has been changed.

AimThe usages derived from the template should incorporate the changes. Important data for the configuration from the old objects can be retained or overwritten in the engineering project. You can save the changes in a working layer.

You have the option to set a version at the template. See also chapter Creating the Master Version (Page 85).

RequirementYou have read rights in the "@Template" node.

Attributes which are to be matched are defined in the "Property mapping" standard table. See also chapter "Y10M00N00031 Assembly updater property assignment" (Page 86).

Using the "Update usages" plugin1. Select the "Plugins > Automation > Assembly updater" command in the menu bar:

2. Select the "General" mode from the list.

3. In the "@Template" node, navigate to the template object - the object under which the template is located.

4. Set the desired start object below which the updated template is located.You may use the project node here.

5. Drag the template object into the "Updated template" field.

6. Select one of the following options from the list:

– To check all structures and properties of the template object, select the entry "Structure and property verification".

– To only check the usages which have a different version than your template, select the entry "Version check".



7. Click the "Update" button.

– The table in the "Usages in projects" control group is filled. You see only the usages that differ from the updated template. If you select the "Show unchanged usages" option, you also see the usages in which there are no deviations.If you are in an engineering project, you can see the usages of the current working layer of the engineering project. If you are in the base project, you can see the usages of all engineering projects that are linked to the current open working layer of the base project. When you run a version check, all instances with a version other than the template are displayed.

– A tree with the template is displayed in the "Structural differences" control group.Nothing is displayed here when you run a version check.

8. Select an entry in the table for the "Usages in projects" control group.

– The template tree in the "Structural differences" control group is colored. The colors indicate how the selected usage deviates from the template. The color requirements of the legend apply here.

– Objects that have not been changed in the usage are not displayed in the template tree. To display them, select the "Show unchanged objects" option.

9. If you select an object in the template tree, details about the change are shown in the "Differences between objects" control group.Select one object after the other in the template tree and verify that you want to update the usage.

10.If you want to update the usage, select the option next to the usage in the "Usages in projects" table.

11.Repeat steps 6 to 8 for the remaining entries in the "Usages in projects" table.

12.Click the "Update" button.A dialog opens.

13.Optional: Select one of the following options:

– Enable the "Create working layer" option and assign a name to the working layer to save the changes in a new working layer.

– Enable the "Overwrite engineering information with the template data" option to overwrite the existing engineering information at the instances.

When you run a version check, the version of the master is written to the instance during the update.

14.Confirm your entries.



