License information 2 3 COMOS Standards in COMOS 4 … · This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to

COMOS

Readme 10.2.3

Readme

04/2018 V 10.2.3A5E39893283-AB

Important information 1

License information 2

Security information 3Directives, Norms and Standards in COMOS 4

Web links 5

iDB vs cDB 6

Using the COMOS help 7

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

A5E39893283-ABⓅ 04/2018 Subject to change

Copyright © Siemens AG 2014 - 2018.All rights reserved

Table of contents

1 Important information....................................................................................................................................5

2 License information......................................................................................................................................7

2.1 COMOS License User Manager..............................................................................................7

2.2 COMOS Remote License Service............................................................................................7

2.3 COMOS License Management ...............................................................................................7

2.4 COMOS License Server Monitor..............................................................................................7

2.5 License types...........................................................................................................................82.5.1 License types...........................................................................................................................82.5.2 Standalone license...................................................................................................................82.5.3 Named User license.................................................................................................................92.5.4 Floating license......................................................................................................................102.5.5 Node-Locked-License............................................................................................................10

3 Security information....................................................................................................................................11

4 Directives, Norms and Standards in COMOS............................................................................................13

5 Web links ...................................................................................................................................................15

6 iDB vs cDB.................................................................................................................................................17

6.1 Databases iDB and cDB........................................................................................................17

6.2 Comparison of COMOS menus.............................................................................................17

6.3 Comparison of COMOS project properties............................................................................25

6.4 Comparison of connector type names...................................................................................37

6.5 Administration: Merging objects in the cDB...........................................................................41

6.6 Soft deleted flag in the cDB....................................................................................................42

7 Using the COMOS help..............................................................................................................................43

7.1 Help on COMOS....................................................................................................................43

7.2 Copying documentation to the help folder..............................................................................44

7.3 Working with the COMOS help system..................................................................................44

7.4 Displaying the COMOS help system online...........................................................................45

Readme 10.2.3Readme, 04/2018 V 10.2.3, A5E39893283-AB 3

Table of contents

Readme 10.2.34 Readme, 04/2018 V 10.2.3, A5E39893283-AB

Important information 1Readme and Release Notes

This readme is installed by COMOS Setup. It contains general information and links to the documents available on the Internet.

Additional information on the use of COMOS is available in the Release Notes (known issues, bug fixes, phase-outs).To keep the information up-to-date, the latest Release Notes are only available on the Internet. You can find the latest version of the Release Notes at the following address:

Online help (https://w3.siemens.com/mcms/industrial-automation-systems-simatic/en/manual-overview/comos-manuals/Pages/Default.aspx)

NoteTopicality of documents available online

Documents that are available online may be more up-to-date than the version of the documents installed by COMOS Setup. The statements in the documents available online therefore take precedence over the statements in the installed documents.

Note

Before you start installing or using COMOS, you must read the information in the latest version of the Release Notes (online).


https://w3.siemens.com/mcms/industrial-automation-systems-simatic/en/manual-overview/comos-manuals/Pages/Default.aspx

https://w3.siemens.com/mcms/industrial-automation-systems-simatic/en/manual-overview/comos-manuals/Pages/Default.aspx

Important information


License information 22.1 COMOS License User Manager

You manage the user licenses with the COMOS License User Manager.

2.2 COMOS Remote License ServiceThe Remote License Service makes a COMOS license that is available on the client available on the Citrix server or terminal server. The Remote License Supplier connects a Microsoft Terminal client or Citrix Terminal client to the Citrix server.

2.3 COMOS License Management

The software that is required for licensing, the registration of licenses, and all related tasks can be found in the 'COMOS License Management' menu.

● COMOS License Server: Here you can find the setup for the license server and the setup for the COMOS License Server Monitor.

● COMOS Remote License Supplier: Here you can find the setup for the COMOS Remote License Supplier to use local licenses on a Citrix server. Alternatively, you can find the setup for the COMOS ICA client.

● COMOS License User Manager: Here you can find the setup for the License User Manager with which you manage the user licenses.

● COMOS License Server Host ID: Here you can find the tool for licensing without dongle.

2.4 COMOS License Server MonitorThe License Server Monitor is used by administrators and super users to start and exit the license server and to manage the licenses in your company network. To do so, the License Server Monitor offers different overviews of licenses that are generally available and those that are currently in use.


2.5 License types

2.5.1 License types

The special license types available for the COMOS software are defined in more detail in this section. We would like to advise you that license types defined in the general agreement that are not expressly listed in this section are still being used. The license types can be offered for individual COMOS software products or for product families. The license type is offered in the LSDA. Unless specified otherwise, customers can install the licensed COMOS server software on one (1) hardware device per license. The COMOS software consists of one or multiple COMOS platform licenses required for the use of a required number and/or combination of additional modules, except defined COMOS packages, that already contain functionalities of the platform and specified modules.

2.5.2 Standalone licenseStandalone licenses are limited in their usage/right of use. The corresponding limitations depend on the respective module (license).

MRO StandaloneThe MRO Standalone license is a license bundle consisting of a Platform and an MRO license. The Platform license is a main module and is always required for an add-on module. When an MRO Standalone license is ordered, the Platform license is automatically supplied in addition to the MRO functionality as a license bundle with the license file.

However, we wish to point out the following scenario:

The MRO Standalone license bundle, which includes a Platform license, may be used with the add-on modules listed here:

● COMOS Shutdown

● COMOS Inspection

● COMOS Portable

● COMOS Direct

● COMOS PQM

● COMOS Enterprise Server

● COMOS SAP Interface

● COMOS Isometrics

● COMOS WebView

● COMOS WebPQM

● COMOS WebMRO

● COMOS Mobile Document Review Client Access

License information2.5 License types


An Operations Upgrade fee is due when the Platform license in the MRO Standalone license bundle is to be used for an add-on module that is not listed here, for example, EI&C, Logical, etc.

PQM StandaloneThe PQM Standalone license is a license bundle consisting of a Platform and a PQM license. The Platform license is a main module and is always required for an add-on module. When an PQM Standalone license is ordered, the Platform license is automatically supplied in addition to the PQM functionality as a license bundle with the license file.

However, we wish to point out the following scenario:

The PQM Standalone license bundle, which includes a Platform license, may be used with the add-on modules listed here:

● COMOS WebView

● COMOS WebPQM

● COMOS WebMRO

● COMOS Mobile Document Review Client Access

An Upgrade fee is due when the Platform license in the PQM Stand-alone license bundle is to be used for an add-on module that is not listed here, for example, EI&C, Logical, etc.

2.5.3 Named User license"Named User" license means that the COMOS software can be exclusively used by a specifically named user. This user is an Authorized User according to the definition in the general agreement. The name entered for the Authorized User can be changed for an additional fee ("Rename Counter Fee"). The Named User license is not limited to a territory but can be used freely by the user in the customer network and within the domain in which the license server is located if the applicable export laws and regulations are being observed. If a customer wants to name a different user for this Named User license, a Rename Counter Fee must be paid to SISW.



2.5.4 Floating license"Floating" license in a concurrent user license according to the definition in the general agreement that is subject to the following additional rules. Each user with a COMOS platform license for the COMOS platform can use a different COMOS module at his or her workstation if this module is available on the license server. As soon as a user releases the COMOS platform license, all module licenses used by the user are being released by the license server and are therefore available to other users with a valid COMOS platform license. The general restriction that the software must not be used outside the customer premises does not apply to the floating licenses of the COMOS software. A floating license can consist of one of the two following types:

1. According to the specification in an LSDA, a "Country Floating" license is limited to the use of a floating license in the country in which the software is first installed in the customer network and within the domain in which the license server is located.

2. "Global Floating" license This license requires a Global Software License Agreement (GSLA). This license can be used freely in all time zones around the globe if the applicable export laws and regulations are being observed.

2.5.5 Node-Locked-LicenseNode-Locked-License means that the usage of the software is limited to an individual work station specified by the customer. In order to implement this limitation, this license type usually has a hardware protection for the hardware or a dongle.



Security information 3Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines, and networks.

In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial security concept. Siemens’ products and solutions only form one element of such a concept.

Customer is responsible to prevent unauthorized access to its plants, systems, machines and networks. Systems, machines and components should only be connected to the enterprise network or the internet if and to the extent necessary and with appropriate security measures (e.g. use of firewalls and network segmentation) in place.

Additionally, Siemens’ guidance on appropriate security measures should be taken into account. For more information about industrial security, please visit:

http://www.siemens.com/industrialsecurity.

Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer’s exposure to cyber threats.

To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed under

http://www.siemens.com/industrialsecurity.


Security information


Directives, Norms and Standards in COMOS 4All references to directives, norms and standards in the software interface and the documentation serve as guides. SIEMENS AG claims no conformity of COMOS to these directives, norms and standards. Rather, we draw attention to the fact that COMOS supports planning in accordance with certain norms and standards. Further standards and norms can be added to the COMOS applications by corresponding customization.The COMOS licensee is always responsible for the licensing of the corresponding norms and standards to the required degree through the authorized licensor.Standards for the nuclear power station sector are expressly excluded and to be obtained independently by the licensee (via VGB PowerTech e.V.).


Directives, Norms and Standards in COMOS


Web links 5Note

Please read through the readme carefully, as it contains important information and additions for COMOS. The statements in this readme file take priority over the COMOS manuals.

● Further information on COMOS is available on the Internet on theCOMOS website (http://www.siemens.com/comos).

● Contact persons for COMOS software solutions in sales and service can be found online atCOMOS contact person (http://www.automation.siemens.com/mcms/plant-engineering-software/en/contact/).

● You can find free electronic documentation on the Internet atCOMOS documentation (http://www.siemens.com/comos-manuals).

● You can find the installation instructions for the documentation supplied with COMOS here:Installing COMOS documentation

● COMOS support page in the Online SupportCOMOS support (https://support.industry.siemens.com/cs/document/109739837/comos-overview?dti=0&lc=en-WW)


http://www.siemens.com/comos

http://www.automation.siemens.com/mcms/plant-engineering-software/en/contact/

http://www.automation.siemens.com/mcms/plant-engineering-software/en/contact/

http://www.siemens.com/comos-manuals

https://support.industry.siemens.com/cs/document/109739837/comos-overview?dti=0&lc=en-WW

https://support.industry.siemens.com/cs/document/109739837/comos-overview?dti=0&lc=en-WW

Web links


iDB vs cDB 66.1 Databases iDB and cDB

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

Software FeaturesAll new software functionality for COMOS version 10.2 and other software deliveries are implemented based on iDB.

A service pack is provided to support existing cDB installations. This will make it possible to subsequently implement special sections of COMOS V 10.2.1 in the cDB.

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.

6.2 Comparison of COMOS menus

ObjectiveThe following table describes the changes in the COMOS menu under the following conditions:

● Use of COMOS 10.2.2

● Switch from cDB to iDB

● Availability of all rights and licenses


Comparison

File (cDB) File (iDB)Unchanged except for:

(-) User settings [New]

View (cDB) View (iDB)Unchanged

Administrator (cDB) Administrator (iDB)Script error handling Script error handlingBase data Standard tables Standard tables

Unit systems Unit systemsDocument types Document typesImport ECAD component [Removed]

Obsolete. Functionality is included upon request by custom‐er within the framework of customization.

Pipe specs Pipe specsAttribute transfer editor [Removed]

Obsolete and discontinued.Bulk processing of report templates Bulk processing of report templatesExtended properties Extended propertiesPermitted connector type combinations Permitted connector type combinationsString rule manager String rule manager

System

Data maintenance (support) Data maintenance (support)User administration User administrationPermissions Permissions(-) Database update [New]Synchronize project folder Synchronize project folderNumbering ranges Numbering ranges

Update classifi‐cation

Update classification Submenu unchanged

Documents (cDB) Documents (iDB)Unchanged

Extra (cDB) Extra (iDB)Bulk processing Bulk processing

Submenu database-dependent

iDB vs cDB6.2 Comparison of COMOS menus


Extra (cDB) Extra (iDB)Queries > Engineering ob‐

jects

Query: Engineering objects Query: Engineering objectsQuery: Engineering objects (short) [Removed]Query: Cross-project engineering objects Query: Engineering objects (cross-project) [Renamed]

Queries > Base objects

Query: Base objects Query: Base objectsQuery: cross-project base objects [Removed]

Obsolete because the new recommendation is to edit base objects for specific projects.

Queries > Attributes

Query: Attributes Query: Attributes

Queries > Documents

Query: Documents Query: DocumentsQuery: Cross-project documents Query: Documents (cross-project) [Renamed]

Queries > Connectors

Query: Connectors Query: Connectors

Queries > Tools

Wire list [Moved]-> "Plugins > Automation > Connection attributes"

Implement requests Implement requestsRestore COMOS objects Restore COMOS objectsConvert old scripts to script blocks [Removed]

cDB-specific repair function for which there is no need in the new structure of the iDB.

Changed devices in a working layer Changed devices in a working layerChanged attributes in a working layer Changed attributes in a working layerHalf-open connectors [Moved]

-> "Plugins > Automation > Bulk processing half-open con‐nections"

Queries > DVM queries

Bulk checkin / checkout [Removed]Duplicate entry. See "Plugins > Project Quality Management > DVM queries > Bulk checkin / checkout"

My most recent documents [Removed]Obsolete and discontinued. The associated @Profile ob‐jects for this were no longer ported to iDB due to a lack of requests.

Standard import Standard importSubmenu unchanged

Translation TranslationSubmenu unchanged

Checking CheckingSubmenu unchanged

Detail DetailSubmenu unchanged

Working layers/Histories

Working layers/HistoriesSubmenu unchanged

3D check 3D checkSubmenu unchanged



Extra (cDB) Extra (iDB)Object matcher Object matcherCross-project copy Cross-project copyReport Designer Report DesignerReimport ReimportRestrict working areas Restrict working areasObject debugger Object debuggerMultiple Document Review Multiple Document ReviewMonitoring Monitoring

Submenu unchanged



Plugins (cDB) Plugins (iDB)Basic Define attribute colors Define attribute colors

Document interface Document interfaceNative object XML import export Native object XML import exportCross-class copy Cross-class copyFull-text search Full-text searchUnit conversion [Temporarily removed]

Functionality is put into operation by a ServicePack for CO‐MOS 10.2.

Error analysis for 3D objects Error analysis for 3D objectsDWG/DXF mapping editor DWG/DXF mapping editorPDMS Pipe Spec Interface [Moved]

-> "CAE Apps > Aveva > PDMS/E3D Pipe spec import"PDMS/E3D Engineering Interface [Moved]

-> "CAE Apps > Submenu"Walkinside object assignment Walkinside object assignmentAssign line types Assign line typesPipe spec mapping Pipe spec mappingJob Management [Removed]

Removed due to functional overlapping with task manage‐ment.

Material Management Wizard Material Management WizardTask management Task managementData aggregation Data aggregationSnapshot SnapshotGeneric Data Mapper Generic Data MapperEngineering adapter configuration[Moved to "CAE Apps"]

[Removed]No you can find these settings in the properties of the project:Category "Process engineering" > "Engineering adapter" > Submenus

Engineering adapter pipe spec export for PDMS[Moved to "CAE Apps"]

[Moved]-> "CAE Apps > Aveva > PDMS Pipe spec export" in iDB as well as cDB

Script processing Script processing



Plugins (cDB) Plugins (iDB)Maintenance General maintenance

General maintenance (Submenu unchanged)

Events EventsShutdown ShutdownResources ResourcesWarehouse management Warehouse management

Warehouse management Warehouse managementGoods receipt Goods receiptGoods issuing [Removed]

Functionality was transferred to: "Warehouse manage‐ment", "Goods receipt"

Logistics LogisticsInspection Inspection3D risk diagram 3D risk diagramObject search Object searchDirect login Direct login(-) Project management charts [New, renamed](-) Maintenance options [New]



Plugins (cDB) Plugins (iDB)Automation Signal name matching [Removed]

Obsolete. Functionality is included upon request by custom‐er within the framework of customization.

Signal/device assignment manager Signal/device assignment managerUpdating macro blocks Updating macro blocksBulk processing of half-open connections Bulk processing of half-open connections Connection attributes [Successor wire list]Generic Excel import Generic Excel importBrownfield Loop Wizard Brownfield Loop Wizard(-) Templates [New]

Template administra‐tion [Moved, renamed]Updating assemblies

[Moved to here]Defining the connection pattern Defining the connection patternIEC to JIC conversion [Removed]

JIC currently not available in the iDB.SPI interface SPI interfacePCS 7 interface [Removed]

PCS 7 interfaceOnly available with "PA Base" license in the iDB.

Interfaces [Removed]Obsolete. Functionality is included upon request by custom‐er within the framework of customization.

Assembly updater Assembly updater [Moved]Loop Document Manager Loop Document ManagerCabinet Equipment Wizard Cabinet Equipment WizardSIMIT interface SIMIT interface [Renamed]

Submenu unchangedGSD GSD

Submenu unchangedMerge UI Merge UI(-) Collision control for connection objects [New]



Plugins (cDB) Plugins (iDB)PQM(Project Quality Management)

Include documents Include documentsFile transfer File transferStart Excel Start ExcelStart Outlook Start OutlookStart PowerPoint Start PowerPointStart Vision Start VisionStart Word Start WordViewer settings Viewer settingsDVM Transmittal [Removed]

Functionality was transferred to: "Document transfer"DVM queries DVM queries

Bulk checkin / checkout Bulk checkin / checkout [Renamed]My most recent documents [Removed]

Obsolete and discontinued. The associated @Profile ob‐jects for this were no longer ported to iDB due to a lack of

requests.(-) Query: Transmittal documents [New]

Document transferTransmittal functionality cannot be per‐formed here. See "DVM Transmittal".

Document transferIncluding "Transmittals".

SAP SAPSubmenu unchanged

Collaboration COMOS Mobile Document Review COMOS Mobile Document ReviewSubmenu unchanged

CAE apps [Re‐named]

CAE apps [Renamed]Engineering adapter configurationContains the "Engineering adapter" cat‐egory with the submenus for Aveva, Pro‐teus and PDMS pipe spec export

[Removed]Not available in the iDB.

Aveva [Renamed] Aveva [Renamed] PDMS/E3D Engineering Interface

PDMS/E3D Pipe spec import [Moved to]PDMS pipe spec export [Moved to here]

Bentley [Renamed] Bentley [Renamed] COMOS P&ID process data import

COMOS P&ID process data exportCOMOS FEED process data export

Proteus [New] Proteus [New] (-) XML Data export [New]

Help (cDB) Help (iDB)Unchanged



6.3 Comparison of COMOS project properties

ObjectiveThe following table describes the changes in the properties of the COMOS project under the following conditions:

● Use of COMOS 10.2

● Switch from cDB to iDB

● Availability of all rights and licenses

Comparison

"General" tab iDB: Category > Subcategory >> Group: Option General settings > Project data >> General

"Links" tab iDB: Category > Subcategory >> Group: Option General settings > Project data >> Links

"Options" tab > "Standard" tab iDB: Category > Subcategory >> Group: Option Prefixes and de‐limiters

General settings > Standard >> Prefixes and delimiters "Prefix and delimiters of the class 'General' depend on use as unit, lo‐cation or document group"

[Renamed]"Objects in the "General" class are given a prefix and delimiter depending on whether they are used as a unit/location/document group"

Always suspend General settings > Standard >> Attribute value

Renamed list [Named]"Exponential notation" list

Static link General settings > Standard >> Static link

Switch at 1st Change from dynamic to static

[Renamed]Change from dynamic to static on first change

Unit system Renamed list [Split into:]

General settings > Standard >> Unit system: Current unit systemGeneral settings > Standard >> Unit system: New unit system

iDB vs cDB6.3 Comparison of COMOS project properties


"Options" tab > "Standard" tab iDB: Category > Subcategory >> Group: Option Display Date/Time in

General settings > Standard >> Display Date/Time in

User/Rights General settings > Standard >> User/Rights

Enable user project [Renamed]Enable user project

No write permission for 'Read-Only Scripts'

[Renamed]No write permission for 'read-only scripts'

Automatic read rights 'Only for one object' to all owners

[Renamed]Read rights 'Only for one object automatically assigned to all owner objects'

Others General settings > Standard >> Other

Use number ranges [Moved]General settings > Numbering ranges: Use number ranges

Elements 'Element: Default' under element

with 'Virtual: Off permitted[Removed]The option was removed from the user interface be‐cause it is always enabled in the iDB.

"Options" tab > "Documents" tab iDB: Category > Subcategory >> Group: Option General General settings > Documents >> General View station: De‐fault action

General settings > Documents >> View station: Default action

Automatic refer‐encing of docu‐ments

General settings > Documents >> Automatic referencing of documents

"Options" tab > "Revision options" tab iDB: Category > Subcategory >> Group: Option Server-side revi‐sions

General settings > Revision options >> Server side revision

Procedure Create PDF file at first step General settings > Revision options >> Settings:

Create PDF file at first step

eSign Enable eSign General settings > Revision options >> Settings:

Enable eSign



"Options" tab > "Revision options" tab iDB: Category > Subcategory >> Group: Option Monitoring General settings > Revision options >> Monitoring Settings Revision archive General settings > Revision options >> Settings:

Revision archive

Revision label editable during the complete revision operation

General settings > Revision options >> Procedure: Revision label editable during the complete revision operation

Revision is possible in checked out state

General settings > Revision options >> Procedure: Revision is possible in checked out state

Report revision comparison method

General settings > Revision options >> Report revision comparison method

Redlining General settings > Revision options >> Redlining Others General settings > Revision options >> Other

"Options" tab > "EE/EI&C options 1" tab iDB: Category > Subcategory >> Group: Option General Automation > EI&C >> General

'_' for empty request values to the device option

[Renamed]Write '_' for empty request values to the device option

Manufacturer device selection

Automation > EI&C >> Manufacturer device selection XML based mode [Removed]

In COMOS 10.2, the selection of manufacturer devices catalogs based on XML and the selection of the CO‐MOS base objects are simultaneously available. Project-wide switching of the selection to only one of the two sources is no longer necessary.

Signal tracking Automation > EI&C >> Signal tracking Device labeling group

Automation > EI&C >> General: Device labeling group



"Options" tab > "EE/EI&C options 2" tab iDB: Category > Subcategory >> Group: Option Settings Automation > EI&C >> Settings

Company logo used [Moved]General settings > Project data >> Customer: Company logo

"Options" tab > "FieldConnect" tab iDB: Category > Subcategory >> Group: Option Comos defaults [Removed]

Obsolete. FieldConnect is discontinued for iDB.

Miscellaneous DCS library Administration Interconnecting diagrams Structures

"Options" tab > "PCS 7 interface" tab iDB: Category > Subcategory >> Group: Option Level 1 - Level 8 Automation > PCS 7 settings >> Plant hierarchy map‐

ping:Level 1 - Level 8

"Options" tab > "EE/EI&C references" tab iDB: Category > Subcategory >> Group: Option Reference dis‐play

Automation > EI&C references >> Reference display Remove document group prefix [Renamed]

Remove document group prefix

Reference behavior [Renamed]Reference behavior

Separators Automation > EI&C references >> Delimiters

Prefix [Renamed]Prefix

Suffix [Renamed]Suffix

Settings Automation > EI&C >> Others Relative output to segments [Renamed]

Relative output to segments



"Options" tab > "Process engineering" tab iDB: Category > Subcategory >> Group: Option Base object for pipe [Removed]

The selection of a pipe branch is technically sufficient. The specification of a pipeline was a collective defini‐tion.

Base object for pipe branch [Moved] [Renamed]Process engineering: Base object for pipe section

Name for implementation [Removed]Obsolete technology for managing 3D data. This tech‐nology is no longer supported in the iDB. See also "On‐ly apply values linked through the GD tab".

Disable automatic generation of COMOS connectors [Removed]This function is no longer supported in the iDB.

Always generate a new name at unit assignment [Removed]This function is no longer supported in the iDB.

Company logo [Removed]Duplicate entry. See category "General settings > Project data"

Source valve actuators Obsolete technology for managing drives. This tech‐nology is no longer supported in the iDB. The drives are defined in the iDB at each symbol as properties that are graphically relevant.

DXF ini file General settings > Documents >> Auto CAD export: DXF ini file

Linking between P&ID and PPC

Process engineering > PipeSpec Manager >> Link P&ID and PPC

Only apply values linked through the GD tab [Removed]

Obsolete technology for managing 3D data. This tech‐nology is no longer supported in the iDB. See also "Name fir implementation".

Consider rotation of *V*:symbol variables Process engineering > PipeSpec Manager >> Link P&ID and PPC:Consider rotation of *V*:symbol variables



"Options" tab > "Maintenance" iDB: Category > Subcategory >> Group: Option Options Settings Workstation [Removed]

Now you can find these settings in the COMOS menu:"Plugins > Maintenance > Maintenance options"

Classes [Removed]This entry belongs to an obsolete maintenance classi‐fication that is no longer supported. See also "Use new classification".Only the COMOS classification "@99 > A10 Classifica‐tion keys" is still used in the iDB.

Plugins [Removed]This function is no longer supported in the iDB.

Identity [Removed]

Is maintenance project Operations > Maintenance >> Options:Is maintenance project

Is shutdown project [Renamed]Operations > Shutdown >> Options:Is a shutdown project option

Used object hierarchy [Removed]This entry belongs to an obsolete maintenance object structure that is no longer supported. See also "Use lifecycle structure".xxx

Use new classification [Removed]The old maintenance classification is no longer suppor‐ted in the iDB. This is why the "Use new classification" option is always enabled and invisible in the iDB. See also "Settings > Classes".Only the COMOS classification "@99 > A10 Classifica‐tion keys" is still used in the iDB.

Use EventManager Operations > Maintenance >> Options:Use EventManager

Company database Operations > Maintenance >> Options:Company database



"Options" tab > "Maintenance" iDB: Category > Subcategory >> Group: Option Extensions Lock maintenance objects Operations > Maintenance >> Expansions:

Lock maintenance objects

Automatically archive completed workpackages

[Renamed]Operations > Maintenance >> Expansions: Automatically archive completed workpackages

Do not reset planned date on work‐package

Operations > Maintenance >> Expansions:Do not reset planned date on workpackage

Cache tour progress [Renamed]Operations > Maintenance >> Expansions: Cache tour progress

Use maintenance navigator text [Renamed]Operations > Maintenance >> Expansions: Use maintenance Navigator text

New workpackages always planned [Renamed]Operations > Maintenance >> Expansions: Plan workpackages per default

Set workpackage label [Renamed]Operations > Maintenance >> Expansions: Set workpackage label

Use lifecycle structure [Removed]The lifecycle structure is standard in the iDB and cannot be disabled; the option was therefore removed. See also "Used object hierarchy". See also "Lifecycle base object full name".

Lifecycle base object full name Operations > Maintenance >> Maintenance base ob‐jects:Lifecycle base object full name

Device compare mode [Renamed]Operations > Maintenance >> Resources:Mode for comparing equipment

Device compare attribute [Renamed]Operations > Maintenance >> Resources:Attribute for attribute comparison

Use new qualification objects [Removed]The new qualification objects are standard in the iDB and cannot be disabled; the option was therefore re‐moved.

Qualification compare mode [Renamed]Operations > Maintenance >> Resources: Mode for comparing qualification

Qualification comparison attribute Operations > Maintenance >> Resources: Qualification comparison attribute



"Options" tab > "Project Quality Management options" tab

iDB: Category > Subcategory >> Group: Option

General Operations > Project Quality Management >> General: Default working directory [Renamed]

Default working folder

Create temporary documents below [Renamed]Create temporary documents below

Configuration FileTrans

Operations > Project Quality Management >> Configuration file transfer: Script user-def. Separators [Renamed]

Script for user-defined delimiter

Standard table for mapping [Renamed]Standard tables for mapping

Selected table for mapping [Renamed]Selected table for mapping

Standard table for MDB [Renamed]Standard tables for MDB

Renamed text field [Removed]The text field belongs to a project-specific selection of authorized persons together with two other attributes (invisible in the user's view). This technology is obso‐lete and no longer supported in the iDB. The persons and roles are managed through the USER project in the iDB.

E-mail options Operations > Project Quality Management >> E-mail options:

E-mail sender [Renamed]E-mail sender

E-mail server (SMTP) [Renamed]E-mail server (SMTP)

Folder base object [Renamed]Folder base object

Container base object [Renamed]Container base object

Version base object [Renamed]Version base object

Directory [Renamed]Folder



"Options" tab > "COMOS" tab iDB: Category > Subcategory >> Group: Option COMOSDB version information [Removed]

You can find this information in the COMOS menu:"Help > COMOS info", "Help > Database info"

Extra project op‐tions

Search setting for base data [Removed]This option was a preparation for performance optimi‐zation that is yet to be implemented. Since the perform‐ance optimization is now being implemented in another way, this option has also been eliminated.

Print job processing in queries General settings > Documents >> General:Individual print jobs

Behavior of elements upon base ob‐ject switch

General settings > COMOS >> Extra project options:Behavior of elements upon base object switch

General data Standard masks General settings > Standard >> Other:

Standard-specific text masks

Document op‐tions

Scrolling General settings > Documents >> Document options:Scrolling

Debug mode Display PIA messages General settings > COMOS >> Debug mode:

Display PIA messages

"Languages" tab iDB: Category > Subcategory >> Group: Option General settings > Languages

"Case variants" tab iDB: Category > Subcategory >> Group: Option Process engineering > Case variants

"Full-text index" tab iDB: Category > Subcategory >> Group: Option General settings > Fulltext index



"Numbering ranges" tab iDB: Category > Subcategory >> Group: Option General settings > Numbering ranges

"PDMS Interface/Construction Assistant" tab iDB: Category > Subcategory >> Group: Option Communica‐tions folder

Edit communications folder [Removed]Process development > PDMS/E3D Engineering Inter‐face >> Project and profile folder:Initialization fileOnly one ini file is still selected in COMOS. The ini file is edited outside COMOS. Several read-only attributes show the key information in the ini file.

Various attributes for displaying the configuration

Project and pro‐file folder

Edit project folder Various attributes for displaying the configuration

Save COMOS interface configuration [Removed]

This function is no longer supported in the iDB.

Activate/Deactivate Process development > PDMS/E3D Engineering Inter‐face >> Status:Interface active

"Project data" tab iDB: Category > Subcategory >> Group: Option Customer [Removed]

Only the following information is included in the project properties in the iDB:General settings > Project data >> Customer:Customer name, Order no., Company logo, Customer logoAll other project data are acquired in the iDB solely through the USER project.

Responsibility Users project

"Project options, general - Base references 2" tab iDB: Category > Subcategory >> Group: Option [Removed]This information manages the basic structures and import objects of the cDB. This information is now meaning‐less for the iDB:● The structuring of the iDB totally different than that of the cDB● All objects are managed in the iDB using classification



"Project options, general - Base references 1" tab iDB: Category > Subcategory >> Group: Option Basic object types [Removed]

This information manages the basic structures and im‐port objects of the cDB. This information is now mean‐ingless for the iDB:● The structuring of the iDB totally different than that

of the cDB● All objects are managed in the iDB using

classification

Types of TS number device collections [Removed]This function was a component of FieldConnect and is no longer supported in the iDB.

Contact object [Removed]Only the following information is included in the project properties in the iDB:General settings > Project data >> Customer:Customer name, Order no., Company logo, Customer logoAll other project data are acquired in the iDB solely through the USER project.

Device types [Removed]This information manages the basic structures and im‐port objects of the cDB. This information is now mean‐ingless for the iDB:● The structuring of the iDB totally different than that


classification

Other base ob‐ject references

Start object TS [Removed]This function was a component of FieldConnect and is no longer supported in the iDB.

NLS path [Removed]The specification has been removed because NLS texts are managed in the iDB exclusively below this path:Standard tables: Y60 NLS tables

Control device types [Removed]This information manages the basic structures and im‐port objects of the cDB. This information is now mean‐ingless for the iDB:● The structuring of the iDB totally different than that


classification



"SysLog" tab iDB: Category > Subcategory >> Group: Option [Removed]This tab belongs to the "FieldConnect" module. FieldConnect is discontinued for iDB.

"Configuration file transfer" tab iDB: Category > Subcategory >> Group: Option Operations > Project Quality Management >> Configuration file transferDuplicates the "Options > Project Quality Management" tab. For details, see the heading "Configuration File‐Trans" in this chapter.

"Viper" tab iDB: Category > Subcategory >> Group: Option Standardization Process engineering > PipeSpec Designer >> Start

node:System depending tables

Pipe spec definition Process engineering > PipeSpec Designer >> Start node:Pipe spec definition

Basic tables, industrial standards Process engineering > PipeSpec Designer >> Start node:Basic tables, industrial standards

"Nominal diameters" standard table [Removed]The nominal diameters are managed in the iDB using attributes that invoke a selection list of nominal sizes. The user can no longer select which standard table is used for nominal diameters, and therefore the project-specific specification of a standard table for nominal diameters has been removed.

Pipe part types Process engineering > PipeSpec Designer >> Start node:Pipe part types

Rating for the raster router [Removed]This function is no longer supported in the iDB.

MTO configuration Process engineering > PipeSpec Designer >> Other:MTO configuration

Default encoding for XML import Process engineering > PipeSpec Designer >> Start node:Default encoding for XML import

Start OpenGL in software mode [Removed]This function is no longer supported in the iDB.



"OPC" tab iDB: Category > Subcategory >> Group: Option Automation > OPC >> OPC settings

"Workflows" tab iDB: Category > Subcategory >> Group: Option General settings > Standard >> Workflows

6.4 Comparison of connector type names

Naming system for connectorsThe name given is neutral and is assigned for each module.

Attention must be paid to the length of the name as the name will be displayed on different plans.

Connectors are generally independent of the drawing type, i.e. a connector may be displayed on different drawing types. In some cases connectors are only displayed on one drawing type or on no drawing type at all.

Structure of the name: 3 or 4 characters (the first two characters are letters; the following characters are figures with consecutive numbering):

Note

The consecutive numbering may have one or two digits.

1. Position 2. Position 3. Position 4. Position NoteLetter Letter Number Number A BasicB BasicC ProcessD ProcessE AutomationF AutomationG OperationsH Operations Z Often used for customer-specific connectors A Free naming within each module

iDB vs cDB6.4 Comparison of connector type names


1. Position 2. Position 3. Position 4. Position NoteLetter Letter Number Number … Free naming within each module Z Free naming within each module 0 1 Consecutive numbering (one or two digits) 0 2 Consecutive numbering (one or two digits) … Consecutive numbering (one or two digits) 0 9 Consecutive numbering (one or two digits) 1 0 Consecutive numbering (one or two digits) … Consecutive numbering (one or two digits)

The first digit is for the purposes of assignment to the 4 higher-level areas in COMOS. The letter "Z" is reserved for customer-specific connectors. The second digit is assigned within an area. After this the number is consecutive (with one or two digits).

Fixed names in the Automation area

ET Multiline EAxxET Singleline EBxxET Bridge internal ECxxET Bridge external EDxxET Reserve EExx – EHxx (4 Reserve)IC Multiline EIxxIC Singleline EKxxIC Reserve ELxx – EOxx (4 Reserve, when J is not used)

Fluid Hydraulic FAxxFluid Pneumatic FBxxFluid Lubrication FCxxFluid Reserve FDxx-FHxx (5 Reserve)Logical FUP input FIxxLogical FUP output FKxxLogical Reserve FLxx

There are more exceptions in the area of automation for connector arrays and PE connectors.

Fixed names in the M20 Process area

Old name New name Note ModuleCX0 CX0 for origin connectors (never used in BaseProject) VIPERCX1 CX1 Viper ComosConnectors VIPERCX2 CX2 Viper ComosConnectors VIPERCX3 CX3 Viper ComosConnectors VIPER



Old name New name Note ModuleCX4 CX4 Viper ComosConnectors VIPERCA1 CA1 for actuator connectors VIPERCA2 CA2 for actuator connectors VIPERCA3 CA3 for actuator connectors VIPERCA4 CA4 for actuator connectors VIPERCAn CAn for actuator connectors VIPERCY1 CY1 for dynamic connectors (never used in BaseProject) VIPERCY2 CY2 for dynamic connectors (never used in BaseProject) VIPERCY3 CY3 for dynamic connectors (never used in BaseProject) VIPERCY4 CY4 for dynamic connectors (never used in BaseProject) VIPERCYn CYn for dynamic connectors (never used in BaseProject) VIPERCP1 CP1 for physical connectors (never used in BaseProject) VIPERCP2 CP2 for physical connectors (never used in BaseProject) VIPERCP3 CP3 for physical connectors (never used in BaseProject) VIPERCP4 CP4 for physical connectors (never used in BaseProject) VIPERCPn CPn for physical connectors (never used in BaseProject) VIPERCM1 CM1 for attachment connectors (for mounting parts like nuts or slip on

flanges)VIPER

CM2 CM2 for attachment connectors (for mounting parts like nuts or slip on flanges)

VIPER


VIPER


VIPER

CMn CMn for attachment connectors (for mounting parts like nuts or slip on flanges)

VIPER

C#1 C#1 for CP/CX in IsoSymbols. VIPERC#2 C#2 for CP/CX in IsoSymbols. VIPERC#3 C#3 for CP/CX in IsoSymbols. VIPERC#4 C#4 for CP/CX in IsoSymbols. VIPERC#n C#n for CP/CX in IsoSymbols. VIPERCX# CX# for connectionTypes in IsoSymbols VIPERCP# CP# for connectionTypes in IsoSymbols VIPERI1 CI1 input connector FEEDO1 CO1 output connector FEEDO2 CO2 output connector FEEDO3 CO3 output connector FEEDO4 CO4 output connector FEED001 CN1 dynamic and/or neutral connector FEED002 CN2 dynamic and/or neutral connector FEED003 CN3 dynamic and/or neutral connector FEED004 CN4 dynamic and/or neutral connector FEEDW CS1 signal line connector FEEDW1 CS2 signal line connector FEED



Old name New name Note ModuleW2 CS3 signal line connector FEEDW3 CS4 signal line connector FEEDW4 CS5 signal line connector FEEDWn CSn signal line connector FEEDI1 DI1 input connector P&IDI2 DI2 input connector P&IDO1 DO1 output connector P&IDO2 DO2 output connector P&ID001 DN1 dynamic and/or neutral connector P&ID002 DN2 dynamic and/or neutral connector P&IDW DS1 signal line connector P&IDW1 DS2 signal line connector P&IDW2 DS3 signal line connector P&IDW3 DS4 signal line connector P&IDW4 DS5 signal line connector P&IDWn DSn signal line connector P&ID

Comparison of names in the old COMOS database and COMOS iDB

Old connector name in DB V10.0 and below New connector name in the COMOS iDBSLI EB01SLO EB02SL1 EB01SL EB01SL1 EB01SL11 EB02CPxx EAxxBI[1] EC[1]BI[2] EC[2]BE[1] ED[1]BE[2] ED[2]I II[3] I[3]I1 I1I2 I2IN1 EA01IN2 EA02O OO[1] O[1]O1 O1O2 O2O3 O3



Old connector name in DB V10.0 and below New connector name in the COMOS iDBOUT1 EA02 or EA03PE EE01

6.5 Administration: Merging objects in the cDB

New standard for "Merge"The new standard for the "Merge" technology specifies that you are required to work with the "MergeMode" tab for assemblies that are copied in.

When assemblies are copied in, the Merge method is called automatically. All new objects are evaluated to determine whether they have the "MergeMode" tab and, if so, whether the "MergeOnTemplateCreate" attribute has been assigned the value "1".

● If so, a search is conducted for the partner that is to be merged with the new object. With subobjects, the search is first carried out through the MatchKey. If this is not successful, a search is carried out for an object with an identical name.If a partner for merging is found, the Merge method is called at the existing object. The new, copied-in object is handed over as slave and the value 256 is used for the mergeMode parameter. To introduce a different behavior, specify it in the "MergeMode" tabs of the assembly.

● When the "MergeMode" tab does not exist, the attributes are not merged but copied. This may result in duplicate tabs.

The following applies to recursive merging: If there are further child objects below an object, these are also merged.

You can find more information on this topic in the "Platform Administration" manual, keywords "Merging objects" and Automatic merging for assemblies".

To change the standard described above, proceed as follows:

● Change the project properties "MergeModeChapterMandatory"This project property is not visible in the cDB. Change the project properties using the object debugger:Set mergeOpt = a.Project.OwnParameters.CreateNewWithName("MergeModeChapterMandatory")mergeOpt.value = "0"When the project is opened again, the changed project property will become effective.

– mergeOpt.value = "0"DeactivatedRecursive merging is deactivated by default. The "MergeMode" tab can be used to include individual objects during recursive merging.

– mergeOpt.value = "1"ActivatedRecursive merging is used by default. The "MergeMode" tab can be used to exclude individual objects from recursive merging.

iDB vs cDB6.5 Administration: Merging objects in the cDB


6.6 Soft deleted flag in the cDB● cDB: "Soft deleting" an object also has an impact on subsequent working layers: existing

instances in subsequent working layers are also deleted (soft-deleted).

● iDB: Instances remain unchanged in subsequent working layers.

iDB vs cDB6.6 Soft deleted flag in the cDB


Using the COMOS help 77.1 Help on COMOS

Software requirementsHelp has been converted to HTML5 as of COMOS Version 10.2. You need an HTML5-enabled browser.

The following browsers have been tested and approved:

● Windows 7 with Internet Explorer 10

● Windows 7 with Internet Explorer 11

● Windows 10 with Internet Explorer 11 The help cannot be displayed under MS Edge because the required Active X Plugins do not run.

● Windows Mobile with IE 11

● Windows 7 with Chrome 46

● Windows 7 with Firefox 38

● Apple with Safari (iPad, iPhone)

Overview of the COMOS help 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

Opening the help from COMOS1. Start COMOS.

2. To open the COMOS help system, select the menu command "Help > Help system".

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 onlineSee chapter Displaying the COMOS help system online (Page 45).

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/<Language folder>.

2. To start the COMOS help system, double-click on the file "start.htm". The help system opens.

7.2 Copying documentation to the help folder

RequirementCOMOS is installed.

Permissible data types: .doc / .docx / .txt / .pdf

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

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

2. Save your documentation in the <Language folder>.

Note"Help" directory

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

ResultThe files are displayed in COMOS with the "Help" button.

7.3 Working with the COMOS help system

NavigationThe navigation menu of the COMOS help system consists of a table of contents, a search function and a setup menu.

The table of contents lets you navigate freely through the COMOS manual. The search function offers a precise option to get the required results quickly with the help of specific search operators (see below). The search covers the entire document or the currently open structure.

Using the COMOS help7.3 Working with the COMOS help system


You can use the setup menu to personalize the help system. You can, for example, show section numbers, pin the navigation menu on the left or collapse all content segments.

Search operatorsDefault: An OR search is implemented by default. As a result, the search displays all the topics that contain one of the search strings.

Reduce the hit list by means of the following search operators:

● Multi string (".....")

– When you place the strings in quotation marks, only those topics are displayed that contain all the words in any order.

● Excluding search terms (- .....)

– When you place a hyphen or a minus sign in front of word, the results that include this word are excluded.

7.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.com/comos-manuals)

● 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 SIEMENS Industry Online Support Portal:

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.

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




To find COMOS help files, proceed as follows:

1. Open the Web page of the Siemens Industry Online Support portal: SIOS (https://support.industry.siemens.com/cs/start?lc=en-WW)

① "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:

– "Download": As PDF file

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


https://support.industry.siemens.com/cs/start?lc=en-WW

https://support.industry.siemens.com/cs/start?lc=en-WW