Manual Basic en

COMOS Training Basic
Working with the module Platform
Unrestricted Siemens AG 2015 All rights reserved. siemens.com/comos

Contents (1)
COMOS projects and user interface

Basic definitions and design of the software
Working with the user interface
Navigator and tabs
Working with the Navigator and the context menu
COMOS objects
Creating a project with structures and engineering projects
Editing attribute values
Basics for queries
Creating a query and editing a hit list
Unrestricted Siemens AG 2015 All rights reserved.

2 COMOS Plant Engineering Software
Contents (2)
Queries and bulk processing

Grouping a hit list
Bulk processing of attributes
Documents and lists
Tab Documents
Working with data sheets
Interfaces
Data exchange via XML
Import of a data table
Working layers
Functionalities and handling
Contents (3)
Training units at a glance: COMOS Basic
Working layers
Interfaces
Documents and lists
Basics for queries
COMOS objects
Navigator and tabs
Learning target(s) of this training unit:
Basic definitions and design of the software

The COMOS database with base project and engineering projects
Working with the user interface
Creating a new project by copying
Note: The following figures show examples and concepts

and are not always intended to represent concrete
system configurations.
COMOS overview
COMOS Process COMOS Automation COMOS Operations COMOS Lifecycle
FEED EI&C MRO PQM
P&ID (EE, I&C, Cabinet Layout) Shutdown 3 D Integration
PipeSpec Manager Logical Portable & Direct Walkinside
PipeSpec Designer Int. Eng. (SIMATIC PCS 7) Inspection
Isometrics Fluidics
COMOS Platform COMOS Basic

COMOS Administration
COMOS Enterprise Server

View/WebView

COMOS Platform
Is the basis for all other COMOS software solutions und provides all basic
functionalities for them. Examples:
Object-oriented data management (component object server)
Working layer technology
Generating data sheets
User administration
Export and import of data
Export of COMOS data sheets to Word documents

Basic design of the system

COMOS user interface
The COMOS software is the
graphical user interface for
the COMOS database. COMOS database Document
directory
COMOS engineering projects P1 P2 P3 ...

(P) are based on the
SO1
base project (SO1).
@COMOSSYSTEM
Templates
User
er administration
administratio

Opening the database
For opening the following entries are required:

'DWDEDVH& PGE
Type of database 8VHUQDPH#6(783
Path to database 8QLYHUVDODFFHVV

'HIDXOWDFFHVV
User name
$OWHUQDWLYHDFFHVV
NOTE: COMOS distinguishes between three types of user names, that

can be assigned to different rights.

Opening and creating a project
After opening the data base the user can open up or copy an existing engineering
project. Or can create a new one via the context menu.
click
Context menu
New or Copy
Properties of projects
3URMHFW Context menu
Via the context menu and the
command Properties the basic, global 3URSHUWLHV
settings and definitions of an
3URMHFW%DVLF
engineering projects can be displayed
and entered. *HQHUDO/LQNV2SWLRQV/DQJXDJH&DVHYDULDQWV)XOOWH[WLQGH[
For doing so, several tabs are available 1DPH 3URMHFW

(1)
'HVFULSWLRQ %DVLF
in the working area.
'HVFULSWLRQ
'HVFULSWLRQ
7\SH(QJLQHHULQJSURMHFW

Viewing rights
3URMHFW Context menu
Via the context menu of the
engineering project and the 5LJKWV
command Rights the users and their

rights can be displayed or modified.
For each object, the corresponding

object rights can be displayed via the Following
keys Ctrl + A. dialogs

Design and layout of the interface

Menu- & function bars
The COMOS user interface contains:
Adjustable windows
Tabs Navigator Working area
Bars.
The graphic shows the main areas and

the terms, which are used throughout the
Detail window
training and the documentation. (of the Navigator)
Status bar
Working with the COMOS user interface
Many steps / operations in COMOS can be carried out via the mouse cursor and
the methods:
Dragging objects: With the mouse cursor and left mouse button pressed
(called drag&drop in the following)
Context menu: Clicking the right mouse button. Can be carried out on
objects, blank area (Navigator, working areas) or frames /
cells (e.g. in tables or hit lists)

Tearing off
3URMHFW $8QLW
Any structure node can be displayed 3ODQW 76XEXQLW
(in addition) in a separate tab in the $8QLW 76XEXQLW
Navigator. $8QLW
$8QLW
76XEXQLW
In COMOS, this drag&drop-method is
76XEXQLW
called tear off.
Drag&Drop
This additional tab can also be Context menu

deleted. 8QLWV/RFDWLRQV'RFXP%DVHREM 8QLWV/RFDWLRQV'RFXP%DVHREM$8QLW
'HOHWHWDE

Dividing windows
3URMHFW 3URMHFW 3URMHFW
Windows in the Navigator and in the 3ODQW 3ODQW #
$8QLW $8QLW
working areas can be divided / sub-

divided.

For doing so, the docking indicator

must be used.
Drag&Drop
One benefit: Objects can be copied
between tabs via the mouse cursor.

Notes:

Navigator and tabs
Handling and configuration of the Navigator

Working with the context menu within the COMOS user interface
Searching within the Navigator

Navigator and tabs
Functions of the Navigator
Fundamental features and functions in the Navigator are:
Displaying engineering objects in a hierarchical structure

Objects can be displayed in different areas of the Navigator
Creating new objects
Displaying connections / references between objects
Contains functions for searching and navigating
Working in the Navigator only via context menu or drag&drop
Switching between projects
Switching between released area and working layers
Navigator and tabs
Tabs in the Navigator
In the basic set up, the upper part of the 8QLWV/RFDWLRQV'RFXPHQWV%DVHREMHFWV

Navigator is subdivided into four tabs.
Units: Contains function-related structures / objects

Locations: Contains location-related structures / objects (not relevant
for this training)
Documents: Optional: Provides a grouped document structure, can
contain references to external / internal documents
Base objects: Displays the global / system wide base objects. Optional:
Can contain local base objects.
.
Navigator and tabs
1HZ
The context menu in COMOS 'HOHWH
&XW
&RS\
Enables the creation of 3DVWH
0RYH
New structuring objects
&RS\VWUXFWXUH
3DVWHOLQN
New engineering objects
1DYLJDWH
COMOS internal documents. 3ULQW

:RUNLQJOD\HUV+LVWRU\
Provides specific commands / menus. 6HDUFK

3URSHUWLHV
Serves (for example) for setting the Navigator. 1DYLJDWRUVHWWLQJV

6WDWXVGLVSOD\
Can be configured individually by a COMOS administrator. :RUNLQJOD\HUGLVSOD\PRGH
+LVWRU\GLVSOD\
/HJHQG

(Examples)
Navigator and tabs
Navigate in the context menu
%9HVVHO
Context menu
Allows switching to other objects or other
projects. 1DYLJDWH %DVHREMHFWLQEDVHSURMHFW
(1) 'RFXPHQWVEHORZ
The command is available for all objects
and at many positions within the user
interface.

The navigation targets, which show up Context menu
1DYLJDWH $WWULEXWH
(1), are depending on the objects and its
/LQNVRXUFHV
connections/properties. (1) ,QKHULWDQFHVRXUFHV

Navigator and tabs
Text search in the Navigator
The context menu of all objects in the Navigator contains the command
Search, which allows searching for text strings below a desired object.
6HDUFK
3ULQW
context menu :RUNLQJOD\HUV+LVWRU\
6HDUFK2SWLRQV
3ODQW
$8QLW
6HDUFK
6HDUFKEHORZ $7(TXLSPHQW6WDUW
76XEXQLW &RQWDLQHGWH[WSXPS
(TXLSPHQW
6HDUFKFRPSOHWHG
6HDUFKLQ1DYLJDWRUWH[W
5HODWLYHQDPH 'HVFULSWLRQ 7H[W

3 /LTXLGSXPS 3/LTXLGSXPS
3 /LTXLGSXPS 3/LTXLGSXPS

Navigator and tabs
The window Navigator settings
Contains the following control groups:
Display Controls the display of the pieces of information in the

Navigator
General Contains options for sorting and for the behavior of objects in
the Navigator
Tabs Tabs in the Navigator can be activated / de-activated. Also,
pre-defined views can be selected from lists.

Navigator and tabs
Navigator settings
3URMHFW 1DYLJDWRUVHWWLQJV
Are called up via the context
'LVSOD\
menu of the Navigator. Context menu 7RS%RWWRP2II (1)
/LQHOD\RXW
Influence the display of objects 0RGLI\
in the areas of the Navigator 0DLQWHQDQFH

1DYLJDWRUVHWWLQJV 7LPH
via the options: Top, bottom,
$FFHVVRU\
off (1). &RQQHFWRU
$WWULEXWH
Remain the same when re- 'RFXPHQW
starting COMOS (because 8QLWV/RFDWLRQ'RFXP%DVHREM

'RF2EM
they are saved in the user

profile).
Navigator and tabs
Notes:

COMOS objects
Creating a new engineering project with units and location structure

Creating new engineering objects with different methods
Attributes and tabs of engineering objects
Editing attribute values
Handling and functionality of instances and inheritance

COMOS objects
Engineering project in COMOS

3URMHFW
3ODQW
Has the following hierarchical structure in the
$8QLW
Units tab: 76XEXQLW
&DWIROGHU$
%9HVVHO
Project &DWIROGHU%
Unit structure containing
Plant
Unit
Subunit
8QLWV/RF'RFXPHQWV%DVHREMHFWV
Category folders with engineering objects
(Symbolic)

COMOS objects
Engineering project in COMOS

3URMHFW
:)DFWRU\
Has the following hierarchical structure in *%XLOGLQJ
))ORRU
the Locations tab:
55RRPFRQWUROFHQWHU
Project 6&DELQHW
))XVHSROH
Location structure containing
Factory
Building
Floor
Room (or sub location) 8QLWV/RF'RFXPHQWV%DVHREMHFWV
Cabinet
Engineering objects (Symbolic)

COMOS objects
References between unit and location structure
Create a logical connection and enables navigation between structures / tabs.

For this, corresponding pointers / references are set in the properties of objects
(1) and displayed in the Navigator (2).
:+76XEXQLW (1)
:)DFWRU\
Drag&Drop
*%XLOGLQJ 7 /DEHO
1DPH
/)LHOGORFDWLRQ
'HVFULSWLRQ 6XEXQLW )ROGHU
:+76XEXQLW (2)
$OLDV 1RWVHW
/RFDWLRQ :/)LHOGORFDWLRQ

COMOS objects
Methods for creating an object

1HZ
'HOHWH
Via the context menu by &XW
&RS\
New 3DVWH
0RYH
Copy and Paste
1HZ
New|New object from list (one or several objects) 1HZREMHFWIURPOLVW
Via the Static new menu from the menu bar

An object can be copied in the Navigator using the 9LHZ$GPLQLVWUDWRU
mouse cursor and a drag&drop-method. %DFN

)DYRULWHV
6WDWLF1HZPHQX

COMOS objects
Objects in COMOS
Have properties and attributes, which are organized by tabs.

Are differentiated according to base objects and engineering objects.
Are assigned to a class.
Properties and attributes can be

Inherited / passed (attributes can also be linked).
Retrieved, changed and exported.
Displayed, printed, exported via lists and data sheets.

COMOS objects
Properties of objects
Calling up properties: Via context menu or double clicking.

Display as a tab (1) in the working area.
Besides name, description, label it contains further tabs.
Context menu %9HVVHO

(1)

3URSHUWLHV
1DPH % /DEHO
%9HVVHO 'HVFULSWLRQ 9HVVHO )ROGHU
,PSOHPHQWDWLRQ 1RWVHW
Alternative:
*HQHUDO$WWULEXWHV(OHPHQWV&RQQHFWRUV6WDWXV
Double clicking

COMOS objects
Attributes of an object (1)

:3URGXFWLRQ
3&6
(3) 6DIHW\UHTXLUHPHQWV
The pieces of information, which describe and (QYLURQPHQWDOFRQGLWLRQV
3URFHVVWHPSHUDWXUH0LQ0D[
define an object (1), are represented, displayed (2) (QYLURQPHQWDOFRQGLWLRQV
and saved by attributes (2). &OLPDWHFODVV
Attributes are grouped and organized via tabs

(3).
Tabs and attributes are displayed in the
Navigator and in the working area (after calling
up the properties of an object).

COMOS objects
Editing attributes
Text color blue

Highlight own changes within the last 48 hours
Text color red

Highlight changes made by another COMOS
user within the last 48 hours
Text color black

No changes within the last 48 hours

COMOS objects
Attribute links
Dynamic:
The link source passes its associated attribute Context menu
values directly to the linked objects.
Static:
The user decides whether a value of the
source is passed to the linked object.
Differences are highlighted in color on the linked
object (standard color: orange).
(depending on the configuration of the system and attributes)

COMOS objects
Inheritance
A fundamental concept of object-oriented programming.

Attribute, attribute values and values of properties can be inherited
hierarchically within base objects and between base and engineering objects.
Inherited attribute values
Are shown in italics
Cannot be deleted
Can be overwritten (= checked in).
Is indicated in the Navigator by icon inserts (for the COMOS administrator).

COMOS objects
Example for instances of a base object

M
Motor
Voltage: 230V
Engineering objects
M
Motor M1
Inherited / passed Voltage: 230V
M
Motor M2
Inherited / passed & checked in Voltage: 380V

COMOS objects
Notes:

Basics for queries
Functionality and handling of queries

Saving queries
Editing hit lists

Basics for queries
Creating / opening a query in an engineering project
Queries for engineering objects can be called up at different positions in the

user interface:
From the menu bar Extra | Query |

From the function bar Query |
Via the context menu of the node @Queries
(depending on system configuration)

Basics for queries
Saving a query in a engineering project
Queries (as objects) can be saved at many positions (but not at any) within the
unit or location structure in the Navigator.
Possible saving positions can be unit or subunit nodes or a dedicated query

folder.
When saving a query, Name and Description should be filled with
meaningful values (according to the individual needs).

Basics for queries
Terms / Definitions
A query is displayed as a tab in the working area with the following layout:
#4XHULHV43XPSV
#4XHULHV43XPSV Saving position and name of query
&ODVVHV
&ODVVHV (TXLSPHQW
(TXLSPHQW
Function bar
6WDUWREMHFWV
6WDUWREMHFWV :$76XEXQLW
:$76XEXQLW
%DVHREMHFWV
%DVHREMHFWV #__9HVVHOZLWKFRQLFDOKHDG
#__9HVVHOZLWKFRQLFDOKHDG
Query parameters
/DEHO
/DEHO 'HVFULSWLRQ
'HVFULSWLRQ
&
& 9HVVHOZLWKFRQLFDOKHDG
9HVVHOZLWKFRQLFDOKHDG Hit list / result list
&
9HVVHOZLWKFRQLFDOKHDG
&
9HVVHOZLWKFRQLFDOKHDG

Basics for queries
Configuring a query (1)
The object type (to be retrieved) (= engineering object) (1) must be dragged to
the field Base object(s) (2). Multiple-object-setting is possible.
#4XHULHV43XPSV Automatically set
:3ODQW
$8QLW
76XEXQLW &ODVVHV (TXLSPHQW
)ROGHU 6WDUWREMHFWV

(1) &9HVVHOZLWKFRQLFDOKHDG

%DVHREMHFWV (2) #__9HVVHOZLWKFRQLFDOKHDG
/DEHO 'HVFULSWLRQ
& %HKOWHUPLWJHZOEWHQ%GHQ

Basics for queries
Configuring a query (2)
The desired start object (=structure node) (1) must be dragged to the field of the
same name (2). Multiple-object-setting is possible.
#4XHULHV43XPSV
:3ODQW
$8QLW

(1) 76XEXQLW &ODVVHV (TXLSPHQW
)ROGHU 6WDUWREMHFWV (2) :$76XEXQLW
&9HVVHOZLWKFRQLFDOKHDG
%DVHREMHFWV #__9HVVHOZLWKFRQLFDOKHDG

/DEHO 'HVFULSWLRQ

Basics for queries
Function bar
The working area of a query contains the

commands (1) (2) (3) (4) (5) (6) (7)
Navigate
Update (1) Scriptblock Action
Save/Load (2) Search at once / search
Print (3) Search technique
Export (4) Start object(s)
and other specific commands and menus (5) 'Folder' filter
that expand or limit the hit list. (6) Placing filter
(7) Options
Basics for queries
Properties of a column Context menu

/DEHO 'HVFULSWLRQ
As each object, the columns of a hit list & 9HVVHOZLWKFRQLFDOKHDG
have properties, which can be called up via & 1HZ %HKOWHUPLWFRQLFDOKHDG
'HOHWH
the context menu.
3URSHUWLHV
The properties are displayed in a separate
New window
window with six tabs.
With tabs:
General
Object evaluation
Value calculation
Object by value
Extras
Languages
Basics for queries
Configuring a hit list Context menu

/DEHO 'HVFULSWLRQ (1)
Via the context menu of the (shaded) & 9HVVHOZLWKFRQLFDOKHDG
headline a new column can be inserted & 1HZ *HQHUDO
%HKOWHUPLWJHZOEWHQ%GHQ
(2)
'HOHWH 3URMHFW
into the hit list (1). 7LPHVWDPS
3URSHUWLHV
Via New (2) the contents for new 2ZQHU
8QLW
columns and further menus are offered. /RFDWLRQ
Via Attributes (3) the available and %DVHREMHFW

,PSOHPHQWDWLRQ
(2)
insertable attributes of the retrieved objects
5HTXHVW
can be displayed and selected. 6WDWXV
(3)
(3) $WWULEXWHV
5RZVWDWLVWLF

Basics for queries
Exporting / importing a hit list
A hit list can be exported in via different formats / types of files. They can be
selected via the function bar of the query and the button Export data (1).
Importing external data is done via the function Standard import (2) from the
COMOS menu bar.
([WUD3OXJLQV+HOS
06([FHO %XONSURFHVVLQJ
06$FFHVV 4XHU\
7H[WILOH 6WDQGDUGLPSRUW
(2) $FFHVV([FHO;0/5HLPSRUW
(1)
;0/ILOH

Basics for queries
Notes:

Editing, grouping, sorting hit lists

The command and dialog Sorting/Filter
Functionality and handling of bulk processing

Sorting hit lists

:HLJKW
A hit list can be sorted via the Auto- $XWR6RUW:HLJKW $XWRILOWHU:HLJKW
buttons (1) in the headline of each column, DVFHQGLQJ

(1)
GHVFHQGLQJ
similar to table calculation. This sorting
QRQH
cannot be saved.
Context menu
8QLW 'HVFULSWLRQ
For sorting, (multi level) grouping and :$7 9HVVHOZLWKFRQLFDOKHDG
:$7 9HVVHOZLWKFRQLFDOKHDG
filtering for all columns, the command 6RUW
:$79HVVHOZLWKFRQLFDOKHDG
)LOWHU
Sorting / Filter (2) and its options are (2)
6RUWLQJ)LOWHU (2)
available via the context menu.

Sorting and grouping hit lists
Per column, the kind of sorting and grouping can be defined by this method:
Column from the Ascending Alphabetic Yes

hit list (=Attribute) Descending Alphanumeric No
Numeric
0 = Off
6RUWLQJ)LOWHU
1 = Grouping by identical contents , first
6RUWLQJ level

2 = Grouping within the first level by
identical contents
&ROXPQ 6HTXHQFH6RUWLQJW\SH&DVHVHQVL*URXSLQJ

Tab Bulk processing

Navigator Tab Bulk processing
The tab Bulk processing Area Query Area Editing
is subdivided into two parts (1) (2)
(1,2).
Tabs or single attributes of

objects can be dragged from
the Navigator to the area
Editing, as indicated.

Bulk processing
(1-3)
Bulk processing is a tool for
changing information within in a
defined set of objects (1-4). (4)
The set of objects is defined (by a
query) in the left section of the
window.
The information to be changed is
(A)
entered in the right section of the
window (A), the Explosion group
for example.
Workflow for bulk processing
1. Retrieving the objects, which shall be modified, via a query.
2. Getting the attribute, which shall be modified, to the area Editing (via
drag&drop).
3. Marking the engineering objects, which shall be modified, in the hit list.
4. Entering the desired attribute value and confirming with Apply.
NOTE: This method makes sense only for equal or similar objects.

Notes:

Documents and lists
Configuring the tab Documents

Importing / embedding an external file
Working with data sheets

Documents and lists
Tab Documents in the Navigator (1)
Via the context menu and New a folder structure with a topic-related sorting
/ grouping can be created below the project node.
It only contains document references. The original document objects are
located in the unit and location structures.
3URMHFW
#1DPH6\VWHP'RFXPHQWVWUXFWXUH'&&&RGH
$%0DQDJHPHQWGRFXPHQWV
$&&RQWUDFWXDODQGQRQWHFKQLFDOGRFXPHQWV
$44XDOLW\PDQDJHPHQWGRFXPHQWVDQGVDIHW\GHVFULELQJGRFXPHQWV
($'RFXPHQWDWLRQGHVFULELQJGRFXPHQWV


Documents and lists
Tab Documents in the Navigator (2)
Workflow for setting up the tab and the references:
Setting the field Standard (@NameSystem) to Document group hierarchy

in the project properties.
Creating the node @NameSystemDCC via the context menu (of the
COMOS project) and New (in the tab Documents in the Navigator).
Carrying out Create references via the context menu of the
@NameSystem-node.

Documents and lists
COMOS internal and external documents
With basic functionalities, lists / data sheets can be created and managed,
also external files can be handled.
COMOS internal documents External files

Order list *.docx
Consumer list *.xlsx
Pump data sheets *.pdf
Motor list *.tif
Terminal plan, *.jpg,
(Lists and data sheets) (external file formats)
Documents and lists
Embedding an external file

%9HVVHO
External files can be embedded from the '%GDWDVKHHWYHVVHO
desktop into the Navigator via drag&drop,
as indicated. (PC desktop)
When doing so, the user has to decide:
Create copy or Create reference. %9HVVHO
'%GDWDVKHHWYHVVHO
0DQXDO
NOTE: The Navigator setting for
documents (top/bottom) needs
to be considered. 8QLWV/RF'RFXPHQWV%DVHREMHFWV

Documents and lists
Characteristics and features
COMOS internal documents
Display object information (example: data sheets) and relations between

objects (example: cabinet layout document).
Are based on document / report templates, which are located in the base
project.
Can be modified, re-designed and created by a COMOS administrator.
Can be managed by versions and can be fixed / frozen by conversion into a
non-edit format (.tiff or .pdf).

Documents and lists
Methods for creating documents
A document can be created

Automatically in the Navigator, when the related engineering object is
created.
Via the context menu of an object (example: Vessel list for a subunit).
These settings can be influenced / modified by a COMOS administrator.
Via New | General | New document and selecting an existing report
template.

Documents and lists
Data sheets in COMOS
Are available Ready-for-use as templates in

COMOS.
Can be individually configured / modified by a
COMOS administrator.
Can be edited (in the sense of attribute values)
inside and outside of COMOS.
Can be printed.
Can be exported / re-imported.

Documents and lists
Attributes in data sheets
Attribute values can be edited in data sheets (if the data sheets and fields
are prepared for this).
The field of an attribute has a context menu, which allows navigating and
displaying the attribute properties. (depending on the system configuration)
Context menu To the attribute

3URFHVVGDWD
object
1DYLJDWH
,QOHW
$OORZRSHUDWLRQWHPS 3URSHUWLHV
Displaying the
properties of the
data sheet (excerpt)
attribute

Documents and lists
Notes:

Interfaces
Ex- / importing structures and objects via XML format

Basic handling of the plugin Generic Excel import

Interfaces
Data exchange
COMOS provides many options for exchanging data through import/export. They
are available as standard features, plugins or via XML connectors in the software.
Examples:
Import/export of COMOS projects in XML format (separate plugin)

Generic import of Excel spreadsheets (separate plugin)
Import of external simulation data
SIMATIC PCS 7 interface

Interfaces
Examples for applications and formats
XML
SAP
Simulation data for COMOS FEED
3D-Visualization (external supplier)
COMOS Walkinside
SIMATIC PCS 7
pdf
CAD
Text editor / Table calculation
Interfaces
XML data exchange: Principle
The exported COMOS project data (objects and structures) can be imported into
another project (1) in the same database or into another database (2).
COMOS database A COMOS database B

(1)
XML file (2)

exporting
Interfaces
XML data exchange: Plugin 1DWLYHREMHFW;0/LPSRUWH[SRUW

Exporting (1) / importing (2) 2SWLRQV
COMOS project data (in total or (1)2ZQSURSHUWLHVRQO\

([SRUW :LWKRZQHULQIR
,PSRUW(2)8SGDWH :LWKRZQHULQIR
parts of them) is done via the

plugin Native Object XML- ,PSRUW([SRUW;0/ILOH

Import/Export (short: NOXIE).
'RFXPHQWGLUHFWRU\

Objects / structure nodes, which
'UDJ'URSDQREMHFWWRH[SRUW
shall be exported, must be
2EMHFWVWRH[SRUW
explicitly defined (3). (3)
:$

Interfaces
XML data exchange: Options
Own properties only For export, only checked in, no passed data will
be considered.
With owner info When exporting / importing, the owner objects of

the structure will be additionally processed and
included.
Update Only objects / data, which were modified, will be

imported. Timestamps will be updated.

Interfaces
Generic Excel import: Features
Data import from Excel spreadsheets to

COMOS, without scripting or programming
skills
Manual data processing before the import

and use of definable rules while importing
Result: Structures, engineering objects,

attribute values in COMOS

Interfaces
Generic Excel import: Interface

(1)
(1) Import settings:
Used to define the import file and the COMOS
start object (example: engineering project)
(2)
(2) Import data:
Provides a tabular preview (of the first line of the (3)
import data) in COMOS
(3) Data assignment:
Enables the assignment of rules and COMOS
base objects
(4) Start of the import (4)
Interfaces
Generic Excel import: Data assignment and editing rules

(2) (3) (4)
(1)
(5) (6)
(1) Set pointer to base object

(2) Remove base object
(3) Edit rule
(4) Delete rule
(5) Advanced rule options
(6) Copy rule

Interfaces
Generic Excel import: Splitting by delimiters
The contents of a data set can be split into several parts by specifying a
delimiter.
NOTE:
The context menu (right mouse button) can only be
called up in the upper section. Then followed by the
Split into rules-command.

Interfaces
Generic Excel Import: regular expressions
Disassembly of text-based information (known as parsing).

Example: Filter screens 5 m particles.
Expression Output Description

sc\w* screens first occurrence string with sc
\w F first occurrence alphanum. character
\d 5 first occurrence numeric character
\w{9} particles first alphanum. string, 9 characters
\d \w* \w* 5 m particles More than one alphanum. strings
[^F] ilter Ignore character
5 5 m Any character
Interfaces
Notes:

Working layers
Functionalities and creation of working layers

Working with working layers

Working layers
Working with working layers
Working layers are overlapping views of an engineering project, where you

can work without changing the shared database in the project.
For example they enable:
Creation of design drafts

Documentation the various project versions or variants
Parallel engineering of sub tasks by several users.

Working layers
Creating working layers
Working layers (WL) can be

Created in a hierarchical order. WL 1
Merging / releasing is possible only in
WL 1.1
the respective hierarchically arranged
working layer one level above.
Created with equal priority below the

WL 1
released area or with equal priority
within a hierarchy level. WL 2

Working layers
Releasing working layers
Released area of the

engineering project
Working layer
(Engineer A, version X)
Result after merging

(= Release of the working
layer in the released area)
Working layers
Examples
A current engineering can be processed and extended in parallel and

independently by several engineers.
Released area: Current engineering status
Engineer 1: Specifying the pumps in subunit A
Engineer 2: Creating all P&ID for subunit A
Engineer 3: Creating and specifying new subunit B

Working layers
Examples
For a given current project status, project variants (and also sub-variants) can
be engineered.
Released area: As-built-status of the plant
Reconstruction variant A
Reconstruction variant A, alternative
Reconstruction variant B

Working layers
Working layers in the working area

7RWDORYHUYLHZ/LVW
Working layers are displayed (in two

3ODQWSURMHFW
tabs) in the working area in the lower
$65HFRQVWUXFWLRQYDULDQW$
part of the tab Open project $65HFRQVWUXFWLRQYDULDQW$DOWHUQDWLYH
$65HFRQVWUXFWLRQYDULDQW%
Creating a new working layer is done

7RWDORYHUYLHZ/LVW
via the command of the same name
via the context menu of the project or 3ODQWSURMHFW
Context menu
of the desired working layer.
1HZ :RUNLQJOD\HU

Working layers
Functions in the context menu Context menu in the Navigator

1DYLJDWRUVHWWLQJV
The working layer display mode (1) 6WDWXVGLVSOD\

:RUNLQJOD\HUGLVSOD\PRGH
(1) can be activated / de-
activated via the context menu of
Context menu of an object
the Navigator.
Print
Working layer/History Restore
(2)
Functions and features related to Search Accept collisions
Rights Object history
working layers (2) can be called
Properties Compare object
up via the context menu of an Refresh Object status
object. Recalculate the working layer display mode

Check in to current working layer
Release-relevant
Working layers
Switching between working layers

3URMHFW%DVLF
:/5HFRQVWUXFWYDULDQW%OLQNHGWR5HOHDVHGDUHD

As soon as a working layer was opened 5HFHQWZRUNLQJOD\HUV

up once (via the tab Open project), :/5HFRQVWUXFWYDULDQW%OLQNHGWR5HOHDVHGDUHD
:/5HFRQVWUXFWYDULDQW$OLQNHGWR5HOHDVHGDUHD
name and description appear in the 5HOHDVHGDUHDOLQNHGWR5HOHDVHGDUHD

header part of the Navigator, in addition 2WKHUZRUNLQJOD\HUV

to the released area.

By this, a quick und simple switching
between working layers and released

area is possible. 8QLWV/RF'RFXPHQWV%DVHREMHFWV

Working layers
Notes:

COMOS Training Center
Siemens Industry Software GmbH

COMOS Training Center
Kruppstrae 16
45128 Essen
Phone: +49 201 31937-157

Fax: +49 201 31937-187
training.de.comos@siemens.com
www.siemens.com/comos
This document is published for training purpose only and is subject to change without notice.
Siemens Industry Software accepts no liability with respect to its content.
Any kind of distribution or reproduction of this document, utilization and communication of its content is not permitted,
unless otherwise expressly agreed. Any violation may lead to claims for compensation.
A2S00000112 / 2.0 / e

Industry
Tutorial
This document is published for training purpose only and is subject to change
without notice.
Any kind of distribution or reproduction of this document, utilization and

communication of its content is not permitted, unless otherwise expressly
agreed. Any violation may lead to claims for compensation.
A2S00000401/2.0/ei 2015 Siemens Industry Automation. All rights reserved.

Contents
1. Introduction ....................................................................................................................... 2
2 Description of the task....................................................................................................... 3
2.1 Creating an examplary project by copying ................................................................. 3
2.2 Adjusting and getting to know the project properties ................................................. 3
2.3 Adjusting and changing windows ............................................................................... 4
2.4 The menu Help ........................................................................................................ 5
2.5 The menu File.......................................................................................................... 5
3 Solution ............................................................................................................................. 6
1. Introduction
This tutorial intends to convey the working with COMOS projects and the handling of the
COMOS user interface.
You will
Copy an existing engineering project (from the standard delivery package of the
software)
Change the project properties and get to know some further properties
Adjust the size of the windows and sub-divide them
Move / drag objects with mouse cursor (drag&drop-method)
Open the help system and change the language of the user interface.
Be sure to read all of the information and notes in a chapter and then try to independently
carry out the tasks step-by-step. The steps of the tutorial built along a sequence, so (in most
cases) you cannot skip one.
If you need help, use the figures in chapter 3 or talk to the trainer.
The screenshots presented in this document are for reference use only.
COMOS projects and user interface 2/9

A2S00000401/2.0/ei
2 Description of the task
2.1 Creating an examplary project by copying

Open your COMOS database with your universal access.
Execute Open project.
In the tab Open project, activate the setting Engineering and select the project iDB_P01.
Via the context menu (of the selected project) execute the commands Copy and Paste.
De-activate the two options With revisions and With working layers, which are offered in
the dialog. Take care, how your copy is named and where it appears in the listing.
2.2 Adjusting and getting to know the project properties

Open the copied project by double clicking, so that it is displayed in the Navigator.
There, select/mark the project node and open the properties via the context menu.
In the working area, the properties of the project are displayed in several tabs / areas, which
you shall watch or modify.
Categories / Group Pay attention or execute:
Project data / General Change the name to 00_Training and the description to
Basic.
Confirm your entries by Apply (button, bottom, right side).
Project data / Links Take a look at the entries in the fields Project structure and
Base data. In each line, click on the -button.
How many base projects does your COMOS project have?
Languages Check if all checkboxes are set in English. If not, change the
language to English.
Confirm your entries by OK.
For preparing the next step, expand the project node and the node Plant (general) in the
Navigator.

A2S00000401/2.0/ei
2.3 Adjusting and changing windows
Get familiar with user interface and the adjustment of windows and areas.
1) Move / arrange the areas within the user interface as indicated by the arrows in the figure:
2) The top, right corner you will find three small buttons, which you probably know from other
Windows applications:
Exit program
Full screen on / off
Minimize
Switch to Full screen off and try to make the COMOS window smaller as indicated in the
figure:
Try to grab the entire COMOS window (in the header area, a bit to the right) with the
mouse cursor and to move it within your desktop screen.
3) Click (and hold) and drag the object P1 Plant (general) from the Navigator to the right, to
the working area. The mouse cursor is displayed as a circle with a line.
Move the mouse cursor to the upper part of the working area, until the cursor display will
change (white square with black arrow). Then, drop the object.
In the following, this method is called drag&drop.
Repeat this procedure with the object H1 supply base material. Now, you have two tabs
being displayed in the working area.

A2S00000401/2.0/ei
4) Place the mouse cursor on the flag of the tab P1 Plant (general). Click it and drag it
downwards until a cross-like element (docking indicator) is displayed.
Drag the mouse cursor on the lower part of the docking indicator, so that this part will
be displayed with colored shadow. Release the mouse button. Take a look, how the
working area is now divided.
Undo this setting:
Grab the tab Plant and drag it upwards, until the docking indicator is displayed.
Move the cursor to the center / middle of the docking indicator and drop it.
2.4 The menu Help

From the menu bar, open the menu Help and access / read the information regarding
COMOS version and database. For doing so, choose the corresponding commands.
Open the COMOS help system by the command of the same name.
Click the tabs Content, Index and Search (one by one) in the help system in order to get
an overview.
Close the help system.
2.5 The menu File

Open the menu File and execute the command Languages. Change the language (e.g. to
German) and confirm your entry. What happens?
Expand the nodes of your project in the Navigator.
What language is displayed?
You have checked the language in one of the previous steps. Can you explain the difference
of the two setting options?

A2S00000401/2.0/ei
3 Solution
The following figures show a sample solution:
Fig.1: Copying the existing, delivered project via the context menu (chap.2.1)
Fig.2: Opening the properties of the new engineering project (chap.2.2)
Fig.3: Entering / changing name and description (chap.2.2)

A2S00000401/2.0/ei
Fig.4: Language settings of the project (three checkboxes can be switched) (chap.2.2)
Fig.5: The expanded project structure in the Navigator (tab Units) (chap.2.2)
Fig.6: Dragging the object Plant (general) to the working area via drag&drop (chap.2.3)
Fig.7: The object Plant (general) is displayed as a tab in the working area (chap.2.3)

A2S00000401/2.0/ei
Fig.8: The tab is virtually placed on the lower arrow of the docking indicator (chap.2.3)
Fig.9: The working area is sub-divided horizontally into two areas (chap.2.3)

A2S00000401/2.0/ei
Fig.10: Calling up the help system and information related to the used software (chap.2.3)
Fig.11: Calling up language setting from the menu bar and changing it in a separate window (chap.2.3)

A2S00000401/2.0/ei
Industry
Tutorial
Handling the Navigator
without notice.


Contents
1. Introduction ....................................................................................................................... 2
2.1 The command Navigate .......................................................................................... 3
2.2 Search text in the Navigator ....................................................................................... 3
2.3 Navigator settings ...................................................................................................... 4
2.4 Setting up favorites .................................................................................................... 4
3 Solution ............................................................................................................................. 5
1. Introduction
This tutorial intends to convey the working with the COMOS Navigator.
You will
Use the commands Navigate and Search
Adjust settings for the display mode of the Navigator
Define and save favorites.
carry out the tasks step-by-step. The steps of the tutorial are built along a sequence, so (in
most cases) you cannot skip one.
Precondition
It is required, that you have processed
Tutorial COMOS projects and user interface
in advance and have the data / objects available.
Handling the Navigator 2/7

A2S00000395/2.0/ei
Open the COMOS database with your universal access and engineering project from the
previous tutorial.
2.1 The command Navigate

This step covers the principle handling and the purpose of the command Navigate, which
can be executed via the context menu at several positions and objects.
Open the context menu of an engineering object like a pump in unit H3.T1.
Navigate to the base object. What is the active / activated tab in the Navigator now?
You are active in what project?
Change back to your original object.
Navigate to the base object in base project. What is the active / activated tab in the
Navigator now? What project is opened now?
Test the other navigation possibilities.
2.2 Search text in the Navigator

This step covers the principle handling of the command Search and the corresponding
window. Execute the next step in your engineering project.
Open the context menu of the unit H3 and execute the command Search.
Adjust the options as follows:
Type of search: Search in Navigator text
Case-sensitive: activated
With pattern matching: de-activated
Search for the text pump (with small p). Does the result meet your expectation?
Deactivate Case-sensitive and search again
Search for texts, which contain the string position. Does the result meet your
expectation?
Adjust the options as follows:

Type of search: Database-based search
Supported objects: Engineering objects, attributes
Supported properties: Name, value
Search for the text 50. Interpret the search result.

Delete Name from the supported properties.
Again, search for the text 50. Interpret the search result.

A2S00000395/2.0/ei
2.3 Navigator settings
This step imparts the principle function of the dialog / window Navigator settings.
Expand the structure in the Navigator, so that an engineering object like vessel or pump is
displayed. Try to find out how and where tabs and attributes are displayed.
Adjust the Navigator display mode in such a way, that attribute are displayed at bottom
und documents at top. Take a look at the change of display in the Navigator. Is the
display mode as expected?
Adjust the Navigator display mode in such a way, that connectors are displayed at top.
Take a look at the change of display in the Navigator.
Adjust the Navigator display mode in such a way, that the display of documents is off,
Take a look at the change of display in the Navigator. Where are documents displayed
now?
Hide the tab Base data.
For the next steps of the tutorial, select Bottom for attributes, documents and connectors
and make the tab Base data visible.
2.4 Setting up favorites

This step imparts the principle handling of the tab Favorites.
Make the tab visible by executing the command Favorites from the menu View.
In this tab, place two engineering objects (for example a vessel from H3.T2 and a pump
from H4.T1).
Change to the engineering project (iDB_P01), which served as the copy template for
your project, and place an engineering object (for example a 2-way shut-off valve from
H4.T1) from the unit structure in the favorites-tab.
Change back to your training project, for doing so, use the header part of the Navigator.
Activate and switch between the options Current and All in the tab Favorites. What is
the difference between both views?
Finally, close the tab Favorites.

A2S00000395/2.0/ei
3 Solution
Fig.1: Calling up Navigate and the navigation targets (chap.2.1)
Fig.2: Searching for pump in the Navigator text (chap.2.2)

A2S00000395/2.0/ei
Fig.3: The Navigator settings as specified (chap.2.2)
Fig.4: The setting for hiding the tab Base data (chap.2.3)

A2S00000395/2.0/ei
Fig.5: Two objects were defined as favorites (chap.2.2)
Fig.6: All shows the favorites throughout all projects (chap.2.2)

A2S00000395/2.0/ei
Industry
Tutorial
Creating a COMOS project and objects
without notice.


Contents
1 Introduction .................................................................................................................. 2
2 Description of the task.................................................................................................. 3
2.1 Creating an engineering project ............................................................................ 3
2.2 Creating a unit structure........................................................................................ 3
2.3 Creating a location structure ................................................................................. 4
2.4 Linking unit and location structure ........................................................................ 4
2.5 Using different methods for creating objects ......................................................... 4
2.6 Editing attribute values .......................................................................................... 5
3 Solution ........................................................................................................................ 6
1 Introduction
This tutorial intends to convey the creation of a unit and location structure.
You will
Create a new engineering project
Create unit and location structures and link them
Create engineering objects via four methods
Edit attribute values (updating, copying).
perform the tasks step-by-step. The steps of the tutorial are built along a sequence, so (in
Creating a COMOS project and objects 2/9

A2S00000389/2.0/ei
2.1 Creating an engineering project

Your default access should not contain any administration rights.
Open the COMOS database with your default access.
Create a new project with:

Property / attribute Value / setting Categories / Group
Name 00_Basic Project data / General
Description (as you decide) Project data / General
Type Engineering project Project data / General
Project structure A10 Project Project data / Links
presetting, general
example.
Project language English Language
NOTE: Use the context menu for processing the next steps.
2.2 Creating a unit structure

In the tab Units create a hierarchical structure and enter the following labels and
descriptions (leave the names as they are):
Object in context menu Name (set by Label Description

system)
A10 Plant (general) A10 WT Water treatment

A10 Unit A10 PR Pre cleaning
A11 MT Main treatment
A12 FI Final cleaning
Below MT
A10 Subunit A10 AT Aeration tank
Activate the option Sort alphabetically in the Navigator settings and note the changes in the
display.
Then de-activate this option so that the objects are again sorted by name in the Navigator.

A2S00000389/2.0/ei
2.3 Creating a location structure
In the tab Locations create a hierarchical structure and enter the following labels and
descriptions (leave the names as they are):
Object in context menu Name (set Label Description

by system)
B30 Plant 0 S1 Site water treatment

A10 Building L001 CO Control office
A10 Floor, level G001 R Roof level
A10 Floor, level G002 3 Third floor
A10 Floor, level G003 2 Second floor
A10 Floor, level G004 1 First floor, basement
Below 2
A10 Room R001 C001 Control center
Below the factory
A20 Field location O001 O001 Field West
Activate the option Sort alphabetically in the Navigator settings and note the changes in the
display.
Then de-activate this option so that the objects are again sorted by name in the Navigator.
2.4 Linking unit and location structure

Open the properties of the subunit Aeration tank and set a pointer / link to the field location
via drag&drop.
Take a look how the link is displayed in the tabs Units and Locations.
Call up the command Navigate in the context menu of the subunit Aeration tank. Check, if
the field location is offered as a navigation target.
2.5 Using different methods for creating objects

In the next steps you shall create new objects below the given objects and shall use the
following creation methods:
New from the context menu
Drag&drop in the Navigator
New | General | New object from list from the context menu and the
option Create N
Static new menu (from the menu View).

A2S00000389/2.0/ei
Below the folder Machines
Two general pumps shall be created:
Open the context menu of the A20 Machines-folder-object.
Create a Pump, general via the command New | A10 Pumps.
Leave name and description as they are.
Create a second general pump by using the drag&drop-method: Grab the existing
pump with the mouse cursor, drag it on the Machines-folder-object and drop it. Was a
second pump created?
Three Mechanical couplings and two Gears shall be created, which can be found under
A20 Machines | A80 Drives:
Open the context menu of the Machines-folder-object.
Select New| General | New object from list, so that the corresponding window opens up.
Select / mark the object Mechanical coupling, open its context menu and execute the
command Create N. Enter the given quantity and confirm by clicking the green button.
Do you find the new objects in the Navigator?
Repeat this procedure for the gears.
Close the window New object from list via Close (not via Create).
Below the room

Three cabinets shall be created:
In the Navigator, select / mark the room and (from the menu View ) call up the static new
menu, which will be opened up as a new tab in the detail window of the Navigator.
Select the desired / specified object and enter the given quantity.
Start the process by clicking the green button.
Does the desired result show up in the Navigator? If yes, close the tab Static new menu.
2.6 Editing attribute values

Copying attribute values between tabs:
Open the properties of one of the pumps and enter these values in the tab Process
data:
Medium = Water / Steam and ambient temperature = 40; 80; 140.
Click Apply. At a blank position open the context menu and execute the command
Copy tab data.
Open the properties of the other pump. In the tab Process data, insert the copied
values by using the corresponding command.

A2S00000389/2.0/ei
3 Solution
Fig.1: Calling up Open project from the menu File (chap. 2.1)
Fig.2: The general project settings (chap. 2.1)
Fig.3: Links to the specified project structure and the base data (chap. 2.1)

A2S00000389/2.0/ei
Fig.4: De-activated Navigator setting Sort alphabetically (chap. 2.1)
Fig.5: Unit structure as specified (chap. 2.2)
Fig.6: Location structure as specified (chap. 2.3)
Fig.7: Linking the subunit with the field location via drag&drop (chap. 2.4)

A2S00000389/2.0/ei
Fig.8: Creating new objects from a list (chap. 2.5)
Fig.9: Creating objects via the static new menu (chap. 2.5)

A2S00000389/2.0/ei
Fig.10: Copying attribute values from a tab (chap. 2.6)
Fig.11: Inserting copied attribute values in a tab (chap. 2.6)

A2S00000389/2.0/ei
Industry
Tutorial
Creating and editing a query
without notice.


Contents
1 Introduction ....................................................................................................................... 2
2.1 Getting started ........................................................................................................... 3
2.2 Creating and saving a new, empty query ................................................................... 3
2.3 Configuring the query................................................................................................. 3
2.4 Modifying and editing ................................................................................................. 4
2.5 External editing and import ........................................................................................ 5
3 Solution ............................................................................................................................. 6
1 Introduction
This tutorial intends to convey the principle working with queries.
You will
Create a query in an engineering project
Configure the query
Extend the hit list and edit attribute values
Export data, edit them externally and import them.
Creating and editing a query 2/8

A2S00000397/2.0/ei
Precondition:
If you have processed the tutorial Creating a COMOS project and objects, you can use the
existing data and objects.
If not, you need the following objects:
An engineering project with unit structure (factory, unit, at least one subunit) in the tab
Units.
Five Pumps, general below the category folder A20 Machines.
2.1 Getting started

Open the COMOS database with your default access and your engineering project.
In the tab Units create two further subunits by copying the existing one twice. Leave
names, labels and descriptions as they are.
Below the project, create a new node New unit and rename it to @Q (name) and
Query folder (description).
2.2 Creating and saving a new, empty query

A Query: Engineering objects shall be call up, created and saved:
Identify the positions, where you can call up the given kind of query. Decide, what option
you like to use.
Open up Query: Engineering objects and save it below your query folder.
Enter Q1 and General pump listing for name and description.
2.3 Configuring the query

The query, which you have created and saved, shall retrieve and display all general pumps
from the first and third subunit:
Open the query Q1.
At first, drag the object, which shall be retrieved, into the corresponding field. Then drag
it in the field Class. Which class is shown?
Drag the two desired subunits into the field Start object. For doing so, it is required to
mark both objects in the Navigator and drag them in one step into the field. Does a hit list
appear? If not, click the Search-button. How many columns does the hit list contain?
How many hits (=displayed objects) do you expect and does the displayed result meet
your expectation?
If the query shall cover all subunits, what would be the appropriate start object?
Save the query, but do not close it.

A2S00000397/2.0/ei
2.4 Modifying and editing
New columns shall be inserted and the sequence shall be modified:
With the help of the row object, insert the following columns:
Number
Owner
Net weight (from the detail design data)
Voltage (from the detail design data)
If needed, re-arrange the columns, so that the hit list has this sequence (from left to
right):
Number
Owner
Label
Description
Net weight
Voltage
The values for the columns Net weight and Voltage shall be entered and the display shall
be modified:
For all pumps of one subunit enter 230 V for the voltage. The pumps from the other
subunit shall have a voltage of 380 V.
For the 230 V-pumps, enter the weight 80 kg (each). Try the mark all fields and to
enter the value only once.
For the 380 V-pumps, enter the weight 120 kg (each).
Split the column Net weight into value and unit. Note, how the hit list is changed.
NOTE: In order to undo the splitting, you must delete the column Unit. Open the
properties of the column Net weight and select DisplayValue in the tab
Value calculation. (Do not carry out!)
Make sure, that the units cannot be edited via the hit list by setting the corresponding
option via the properties of the column accordingly.
Change the headline / description of the column Net weight to Net weight (empty) by
editing the properties of the column accordingly.
Make sure, that the attribute values are passed over. Save the query, but do not close it.

A2S00000397/2.0/ei
2.5 External editing and import
The hit list shall be exported and then re-imported into COMOS.
Export your hit list into an Excel file by using the corresponding function from the function
bar. Choose a saving location and give Pump list as file name, so that you can find the
file easily.
Close the query.
In the Excel file, change the weight to 150 for two pumps from each subunit. Save
the file.
NOTE: Be aware, that before the import the COMOS software may look for files with
xlsx extension, according to your COMOS and Windows environment. In this
case, change the Windows dialog accordingly.
From the menu Extra, call up the command Standard import.

Select the file to be imported and use the Search-button for getting a preview of the
Excel data. Can you identify the modified values? Start the import by clicking the green
hook-button (in the function bar). Answer / confirm the following dialogs.
After the import, take a look at the messages in the status column.
Open the query Q1 and run it. Does the hit list show the values for the weight as
expected? If yes, close the query and exit COMOS.

A2S00000397/2.0/ei
3 Solution
The following figures show a sample solution, with the objects from the tutorial Creating a
COMOS project and objects.
Fig.1: Unit structure with pumps and the query folder as specified (chap.2.1)
Fig.2: The saved query (chap. 2.2)
Fig.3: The specified and required entries for the query (chap. 2.3)

A2S00000397/2.0/ei
Fig.4: Inserting a column via the context menu, example Number (chap. 2.4)
Fig.5: New columns were inserted and arranged (chap. 2.4)

A2S00000397/2.0/ei
Fig.6: Command for separating value and unit (chap. 2.4)
Fig.7: The configured hit list as specified (chap. 2.4)
Fig.8: In the import preview, the modified values can be identified (chap. 2.5)
Fig.9: Button for starting the import (chap. 2.5)

A2S00000397/2.0/ei
Industry
Tutorial
Grouping and bulk processing
without notice.

A2S00000399 /2.0/ei 2015 Siemens Industry Automation. All rights reserved.

Contents
1 Introduction ....................................................................................................................... 2
2.1 Getting started and creating a query .......................................................................... 3
2.2 Configuring the query................................................................................................. 3
2.3 Entering attribute values by bulk processing ............................................................. 4
2.4 Grouping the hit list .................................................................................................... 5
3 Solution ............................................................................................................................. 6
1 Introduction
This tutorial intends to convey the editing of a hit list and the use of bulk processing.
You will
Create a query in an engineering project
Add columns to the hit list
Use the method Bulk processing
Group the hit list by subunits and object types.
NOTE: Opening a COMOS database, opening COMOS projects and working with the
context menu are supposed to be well-known and are not part of this
document.
Grouping and bulk processing 2/8

A2S00000399 /2.0/ei
Precondition:
If you have processed the tutorial Creating and editing a query, you can use the existing
data and objects, but add some pumps (see below).
If not, you need the following objects:
An engineering project with unit structure (factory, unit, three subunits) and a query-
folder in the tab Units.
In each subunit, five Pumps, general and three Rotary pumps below the category
folder A20 Machines.
2.1 Getting started and creating a query

Open the COMOS database with your default access and your engineering project.
Make sure, that the precondition is fulfilled. How many pumps do you have in your unit
structure?
A Query: Engineering objects shall be called up, created and saved:

Identify the positions, where you can call up the given kind of query. Decide, what option
you like to use.
Open up Query: Engineering objects and save it below your query folder. Enter Q2
and Pump list, grouped for name and description.
2.2 Configuring the query

Your query shall retrieve and display the general and rotary pumps of all subunits:
Open the query Q2.
Drag one of the pump types into the field Base object and in the field class, in doing
so the class will be filled with Device. Press the keys Ctrl + Shift and drag the second
pump type into the base object field. Confirm this procedure with Add.
Decide what object of the unit structure fits best as the start object. Drag this object into
the field Start object.
Does a hit list appear? If no, click the Search- button. Use the status bar in order to
check the number of hits. Does it correlate with your expectation?
Insert the column Net weight (from detail design data)
NOTE: If you have processed the previous tutorial, most of the liquid pumps have
(different) values for the weight. In case some general pumps have no
values, enter values like 80 kg or 120 kg or 150 kg, so that all general
pumps have a weight value.
Do not enter any values for the rotary pumps, this will be done later.

A2S00000399 /2.0/ei
Arrange the columns, so that you have this sequence of (from left to right):
Unit
Description
Label
Net weight
Save and close the query.
2.3 Entering attribute values by bulk processing

Via bulk processing the attribute Net weight of all rotary pumps shall be filled with values:
Open Bulk processing: Engineering objects from the menu Extra.
Retrieve all rotary pumps of the unit.
Note, how the user interface of the working area has changed. In the right part an
interface for editing is displayed.
In the Navigator, search und find the position of the tab Detail design data, which
contains the attribute Net weight.
Drag this tab from the Navigator to the empty area of the tab General, which is part of
the working / editing area of the bulk processing.
Mark all rotary pumps in the hit list (shift-key pressed + click on first line and shift-key
pressed + click on last line).
In the working / editing area of the bulk processing, enter 60 kg for the attribute Net
weight.
Click Apply and OK.
By using the query Q2 Pump list, grouped, make sure that the values were entered and
saved.

A2S00000399 /2.0/ei
2.4 Grouping the hit list
The hit list shall be grouped twofold and sorted by Net weight.
Open the query Q2. Check and ensure that all pumps have a value for the weight.
Insert a column Count in subtable and place it on the right side of Unit. Again, insert a
column Count in subtable and place it on the right side of Description.
Open the context menu of the column Unit and execute the command Sorting / filter.
A window of the same name opens up. Within the control group Sorting, enter these
settings (leave all other settings unmodified):
Unit ascending, alphabetic first grouping

Description ascending, alphabetic second grouping
Net weight ascending, numerical sorting no grouping
For applying these settings, close the window by OK.
Check, if the current hit list meets your settings and expectations:
Is the twofold, hierarchical grouping visible and expandable?
Are the values for Count in subtable visible and plausible?
Is the sorting by weight in accordance to your setting?
If you can always answer with yes, the task is completely done.
If you can answer everything with "Yes", the task is solved.
Save your query and exit.

A2S00000399 /2.0/ei
3 Solution
The following figures show a sample solution, with the objects from the tutorial Creating a
COMOS project and objects.
Fig.1: Object and structure as specified: Three subunits with 24 pumps (chap. 2.1)
Fig.2: Object Rotary pump is added as the second base object (chap.2.2)
Fig.3: The hit list with the column Weight(chap. 2.2)

A2S00000399 /2.0/ei
Fig.4: The hit list for the rotary pumps for the bulk processing (chap. 2.3)
Fig.5: The tab is brought to the editing area of the bulk processing via drag&drop (chap. 2.3)
Fig.6: The two columns Sub count are inserted (chap. 2.3)

A2S00000399 /2.0/ei
Fig.7: The settings for grouping and sorting (chap. 2.4)
Fig.8: The completely configured hit list of the query (chap. 2.4)

A2S00000399 /2.0/ei
Industry
Tutorial
Working with documents
without notice.


Contents
1 Introduction ....................................................................................................................... 2
2.1 Importing an external file ............................................................................................ 3
2.2 Setting up the tab Documents ................................................................................. 3
2.3 Editing an attribute value in a data sheet ................................................................... 4
2.4 Creating a new document with a report template ...................................................... 4
3 Solution ............................................................................................................................. 5
1 Introduction
The tutorial intends to convey the working with external files and with COMOS internal
documents.
You will
Import an external file into the Navigator
Set up the tab Documents
Edit an attribute value in a data sheet
Create a new document with an existing report template.
Precondition:
It is supposed, that you have processed the tutorial Creating a COMOS project and objects
and that you have the objects / data in your system.
Also, it is required, that you have a pdf file as an object symbol on your desktop.
Working with documents 2/7

A2S00000393/2.0/ei
2.1 Importing an external file

A pdf file shall be imported below an arbitrary pump as a document (copy):
Open the COMOS database with your default account and your engineering project.
Adjust the COMOS window in such a way, so that you can also access the PC user
interface and your pdf file.
Extend the unit structure in the Navigator in such a way, so that a pump object is visible.
(Before you do the next step, keep in mind how your Navigator is set up: Documents at
top or bottom?).
Via drag&drop insert the pdf file to the pump. Answer / confirm the dialog window as
specified in the first line of this chapter. Is the file visible in the Navigator? If yes, can you
open it?
2.2 Setting up the tab Documents

The tab shall be filled with a document structure and with references:
Open the project properties and change to the control group Automatic referencing of
documents (located at General settings | Documents). In the field Default
(@NameSystem), enter the value Document group hierarchy. Click OK.
Change to the project node in the tab Documents in the Navigator. Below the project
node, create the object @NameSystem.
From the menu Extra, open Query: Documents. Execute it in order to check, if
references already exist. Use the project as the start object.
Ensure, that references are created in the document structure. For doing so, use the
corresponding command in the context menu of the object @NameSystem.
Again, execute Query: Documents in order to check, if references exist.
NOTE: There can be two reasons, if no hit list appears: There are no documents
in the unit and location structure or your settings are not correct. Try to find
the reason and to fix it. Otherwise talk to the trainer.
Change to the pump of chap.2.1 and create a data sheet via New. Compare the
displayed information of the data sheet and the pdf file in the Navigator. What do you
observe?
Open the properties of the imported pdf file. Enter FE.001 (as name) and
Manual_external (as description). Note, what happens in the Navigator, when you
confirm your entries. Navigate from the file to the reference document by using the
command of the same name from the context menu.

A2S00000393/2.0/ei
2.3 Editing an attribute value in a data sheet
An attribute value shall be entered in a data sheet and the context menu shall be used:
Open a data sheet, which you have created before.
Enter a numeric value into a suitable field (example: Operating temp max = 60C).
Save and close the data sheet. Check, if the entered attribute value is visible in the
Navigator and saved.
2.4 Creating a new document with a report template

A new document shall be created and linked to an existing report template:
Open the context menu of a subunit and execute the command New | General | New
document.
Note the value in the field Name. Select the report template PLT list under E | EC |
EC_A10 . Note, which name is set by the system. Enter Material list training as
description.
Confirm your entry. Note, what happens in the Navigator. Is the document visible? Was a
reference document created in the document structure? If yes, what is the reason?
Open the properties of the new document. Change the name to EA.001 and confirm
your entry. Does the display of the document change in the Navigator? If yes, what is the
reason?

A2S00000393/2.0/ei
3 Solution
The following figures show a sample solution.
Fig.1: Selecting the import mode when embedding a file via drag&drop (chap. 2.1)
Fig.2: The external file is embedded / imported below the pump (chap. 2.1)
Fig.3: The field Standard must be filled with the value as indicated (chap. 2.2)
Fig.4: Creating the @NameSystem-node in the tab Documents (chap. 2.2)
Fig.5: Configuring the document query (chap. 2.2)

A2S00000393/2.0/ei
Fig.6: Creating references below the node @NameSystem (chap. 2.2)
Fig.7: Document query with hit list (chap. 2.2)
Fig.8: The data sheet contains a reference, file does not (chap. 2.2)
Fig.9: The file contains a reference to the document structure by the name PZA.001 (chap. 2.2)

A2S00000393/2.0/ei
Fig.10: Entering an attribute value in a data sheet (chap. 2.3)
Fig.11: Selecting the report template (chap. 2.4)
Fig.12: The new document has a DCC-code-conform name and a reference (chap. 2.4)
Fig.13: The new document (reference) is displayed in the document structure (chap. 2.4)
Fig.14: The name is not in accordance to the DCC code, so no reference exist (chap. 2.4)

A2S00000393/2.0/ei
Industry
Tutorial
Working with interfaces
without notice.


Contents
1 Introduction ....................................................................................................................... 2
2.1 Exporting into an XML file .......................................................................................... 3
2.2 Importing from an XML file ......................................................................................... 3
2.3 XML export / import with owner information ............................................................... 3
2.4 Working with generic Excel import ............................................................................. 4
3 Solution ............................................................................................................................. 6
1 Introduction
The tutorial intends to convey methods for exporting / importing data and the working with
two plugins.
You will:
Use the function for ex- / import via XML
Import data for a unit structure from a data table.
perform the tasks step-by-step. The steps of the tutorial are built along a sequence, so (in
Precondition: You can use the unit structure of the water treatment from the previous
tutorials. Otherwise, you need an engineering project with a plant, at least
one unit, one or several subunits.
Working with interfaces 2/8

A2S00000391/2.0/ei
2.1 Exporting into an XML file

Open your engineering project 00_Basic.
Open Native object XML export import from the menu bar and the menu Plugins.
The task is to export a unit (including subunits) into an XML file.
Define the object you want to export. Leave the export options de-activated.
Define a saving location and a filename.
Start the export.
2.2 Importing from an XML file

For testing purpose, create a new engineering project 00_Basic_Import with a unit
structure, which only contains the plant WF Water facility.
Open Native object XML export import from the menu bar and the menu Plugins.
The task is to import the XML file from the previous step and insert it below the plant.
Enter the required settings. Leave the import options de-activated.

Start the import.
Do all expected objects show up in the Navigator? If yes, the import was successful.
For preparing the next step, delete all objects below the project node.
2.3 XML export / import with owner information

Open your engineering project 00_Basic.
Open Native object XML export import.
The task is to export the unit with owner information into an XML file.
Define the object you want to export and activate the corresponding export option.
Define a saving location and a filename (you can also overwrite your existing XML file).
Start the export.
Open your existing engineering project for the import test.

The task is to import the XML file with owner information and insert it below the project
node.
Enter the root object and activate the corresponding import option.
Start the import.
Do all expected objects show up in the Navigator? Could you observe the effect when using
With owner information?

A2S00000391/2.0/ei
2.4 Working with generic Excel import
Preparation
You can use one of the engineering projects, which you have created during this tutorial.
Delete all objects (tab Units) and create a plant (A40 Plant) with name WT and
description Water treatment below the project node.
It is required, that you have an Excel file with some training data.
If it is not supplied by the trainer, you have to create and save the file. Layout and contents of
the table:
Unit / subunit Unit / label Unit / Subunit / label Subunit /
description description
H1.T1 PT1 Pre treatment R Rough
H1.T2 PT1 Pre treatment F Fine
H2.T1 MT1 Main treatment AT Aeration tank
H3.T1 FT1 Final treatment BC Biological
cleaning
Configuration of the import

Open the plugin Generic Excel import from the menu Plugins | Automation.
Enter the filename of your Excel file in the field of the same name and define, that data
should be read from table 1 and from line 2.
Define the node Water treatment as start object.
In order to have a preview of the import data, click on the button Load work sheet.
Do you see all columns, the headlines and the data of the second line in the area Import
data? If no, repeat the step 2.4 and make sure, that your settings are correct.
The editing of the import data has this goal:

From the first column, a structure containing units and subunits shall be created.
For the unit and subunit objects, the values for name and description shall be taken from
the other columns.

A2S00000391/2.0/ei
In the area Data assignment, enter these settings and definitions for line A (=first column):
Split the contents of the column by sub rules and by using . (dot) as the delimiter.
Drag the base object A10 Unit, which you find in the Navigator of the area Data
assignment below A10 Plant (general), into the first rule of line A as the first base
object (preview value H1).
If there is a sub rule, which contains the complete string in the preview, delete this sub
rule. In total you must create and edit two sub rules.
In the same way, set the base object for the sub unit.
In the area Data assignment, enter these settings and definitions for line B (=second
column):
Create an empty rule.

As the base object, set the object A10 unit.
Via the button Extended rule options, set the target properties to Label.
Repeat the last step for line C and set the target properties to Description.
Repeat the last steps for the lines D and E in order to set the target properties of the
subunits.
Open the preview. Does it meet your expectations?

If yes, ensure, that the two options on the right side of the button Import are de-activated.
Start the import.
Are objects created in the Navigator? If yes, how many units and subunits do you count?

A2S00000391/2.0/ei
3 Solution
Fig.1: Settings for the export, export object defined via drag&drop (chap.2.1)
Fig.2: Settings for the import, start object defined via drag&drop (chap.2.2)
Fig.3: The imported unit with its subunits (chap.2.2)

A2S00000391/2.0/ei
Fig.4: Settings for the import with owner information (chap.2.3)
Fig.5: The imported unit with its subunits and owner (= Water treatment) (chap.2.3)
Fig.6: Generic Excel import: Settings and preview (chap.2.4)
Fig.7: Splitting line A (= first column) into rules (chap.2.4)

A2S00000391/2.0/ei
Fig.8: Setting the base objects for the two sub rules via drag&drop (chap.2.4)
Fig.9: Setting the target properties for line B (here: Label) (chap. 2.4)
Fig.10: The preview with the data from one line before the import (chap.2.4)
Fig.11: The complete unit structure in the Navigator after the import (chap.2.4)

A2S00000391/2.0/ei
Industry
Tutorial
Working layers in COMOS
without notice. Siemens Industry Software accepts no liability with respect to its
content.

communication of its content is not permitted, unless otherwise expressly agreed.
Any violation may lead to claims for compensation.
Contents
1 Introduction ....................................................................................................................... 2
2.1 Creating a project with several working layers ........................................................... 3
2.2 Creating objects in the released area ........................................................................ 3
2.3 Modifying an attribute in working layer A ................................................................... 3
2.4 Releasing the working layer B ................................................................................... 3
2.5 Checking and accepting collisions ............................................................................. 3
2.6 Working in working layer A.01 ................................................................................... 4
2.7 Releasing of two working layers ................................................................................ 4
3 Solution ............................................................................................................................. 5
1 Introduction
This tutorial intends to convey the handling of working layers in an engineering project.
You will
Create a project with several working layers
Create, delete, restore objects in the released area and within the working layers
Release working layers.
Working layers in COMOS 2/8

A2S00000387/2.0/ei
2.1 Creating a project with several working layers

Create an engineering project with the name 00_Training working layer. Select Project
presetting, general example in the category General settings | Project data.
In the tab Open project, create working layers (WL) and follow this naming convention and
this hierarchical scheme:
00_Training working layer
Layer A
Layer A.01
Layer B
2.2 Creating objects in the released area

In the Navigator (tab Units) and in the released area, create one general plant A40 Plant
(name = 0, description = Training), one unit and one subunit.
Below the folder A10 Equipment and via the path A60 Filter, create a liquid filter. In the
tab Design data, enter the value 1000 for the attribute Empty weight.
2.3 Modifying an attribute in working layer A

Open the working layer A and change the empty weight to 1500 (tab Design data).
Switch to the Working layer display mode and expand the structure. Are there any objects
displayed in a colored tone? Does this meet your expectation?
Compare your structure and objects with figure 2 in chapter 3.
If your display differs from the figure, repeat the previous steps.
2.4 Releasing the working layer B

Open the working layer B and change the empty weight to 2000.
Release the working layer B to the released area. In the released area, check the attribute
Empty weight.
Which value do you expect?
2.5 Checking and accepting collisions

Open the working layer A.
Check, if collisions exist. Dont forget to switch to the Working layer display mode.
If collisions exist, accept them by using the corresponding command. Note, that the detected
/ identified values will not be changed.

A2S00000387/2.0/ei
2.6 Working in working layer A.01
Deleting in working layers
Open the working layer A.01
For the attribute Material (in the design data, tab Vessel), enter a value from the selection
list.
Delete the filter object.
Activate the Working layer display mode, make the deleted object visible and open its
context menu.
Undo the deletion by using the command of the same name.
Deactivate the Working layer display mode and open the properties of the filter. Which
value is displayed for the material?
Delete the filter object.
Activate the Working layer display mode, make the deleted object visible and open its
context menu.
Undo the deletion by using the command Restore | with subobjects.
Deactivate the Working layer display mode and open the properties of the filter. Which
value is displayed for the material?
Explain the difference between the two commands.
Comparing objects
For the attribute Diameter (in the design data, control group Vessel), enter 8000. Click
Apply.
Execute Compare object from the context menu of the filter object. Is it required to switch to
the Working layer display mode for doing so?
Release relevance for objects

Change the description of the subunit as you desire and, afterwards, set the subunit to non
release relevant.
Note the icon insert.
NOTE: Such objects will not be considered when the working layer is released to a
higher level. Release relevance can also be defined on attribute level.
2.7 Releasing of two working layers

Release the working layer A.01. Check the result in working layer A.
Release the working layer A. Check the result in the released area.

A2S00000387/2.0/ei
3 Solution
The following figures represent a sample solution.
Fig.1: Creating a project with several working layers (chap.2.1)
Fig.2: Working layer display mode is activated (chap.2.3)
Fig.3: Releasing working layer B (chap.2.4)

A2S00000387/2.0/ei
Fig.4: Checking and accepting collisions in working layer A (chap.2.5)
Fig.5: Undoing the deletion in a working layer (chap.2.6)

A2S00000387/2.0/ei
Fig.6: Value of the attribute Material after undo deletion (chap.2.6)
Fig.7: Restoring the object in a working layer (chap.2.6)
Fig.8: Value of the attribute Material after restore with subobjects (chap.2.6)

A2S00000387/2.0/ei
Fig.9: Result of the object comparison (chap.2.6)
Fig.10: Indication in the Navigator that the subunit was set to non release relevant (chap.2.6)
Fig.11: The filter object in the released area after releasing the working layers (chap.2.7)

A2S00000387/2.0/ei
Industry
Training Handout
Icon inserts
without notice. Siemens Industry Software accepts no liability with respect to its
content.

communication of its content is not permitted, unless otherwise expressly agreed.
Any violation may lead to claims for compensation.
A2S00000151/1.0 2015 Siemens Industry Automation. All rights reserved.

User-related icon inserts
1. A small orange triangle ( ) in the bottom right corner of the icon signifies that this is
not a real device but a device request.
2. A small blue square ( ) in the bottom left corner of the icon signifies that this is not an
independent object but a link.
3. If the selection For all placed objects/Only for placed elements is active, the icons
of placed objects/elements contain a pink checkmark ( ) in the top right corner of
the icon.
Example of placed elements: Terminal strip elements or vessel nozzles.
4. Icons of locally created base objects are signified by means of a cyan insert ( ) in the
top right corner.
5. In the directory of the documents tab, reports created in either the location or unit
view are signified by means of a black arrow on an orange background ( ) in the
bottom left corner of the icon.
6. On the document tab, referenced documents in either the location or unit view are
signified by means of a black arrow on a white background in the bottom left corner of
the icon ( ). The black arrow is pointing to the upper right. See also chapter 9.
7. Working layers: An object identified as non-release-relevant is signified by means of

an orange insert ( ) in the top left area of the object icon.
8. An orange double-angle insert ( ) signifies that a new object pointer may be set in a
query for an object.
Administrator-related icon inserts
9. If information (= objects) on the base object side is inherited from a superordinate

object to a subordinate object, this is signified by a black arrow ( ) in the top left
corner of the icon. The black arrow is pointing to the lower right. See also chapter 6.
Example: Attribute tabs.
10. If information has been checked into an inherited object, this is signified by a white
arrow ( ) in the top left corner of the icon.
Example: A default value is entered in any attribute of an inherited tab.
Icon inserts 2/2

A2S00000151/1.0

Manual Basic en

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Manual Basic en

Enviado por

Direitos autorais:

Formatos disponíveis

COMOS Training Basic

Working with the module Platform

Unrestricted Siemens AG 2015 All rights reserved. siemens.com/comos

COMOS projects and user interface

Unrestricted Siemens AG 2015 All rights reserved.

Queries and bulk processing

Training units at a glance: COMOS Basic

Learning target(s) of this training unit:

Basic definitions and design of the software

Note: The following figures show examples and concepts

COMOS Platform COMOS Basic

COMOS Enterprise Server

Unrestricted Siemens AG 2015 All rights reserved.

Unrestricted Siemens AG 2015 All rights reserved.

Basic design of the system

COMOS engineering projects P1 P2 P3 ...

Unrestricted Siemens AG 2015 All rights reserved.

Opening the database

For opening the following entries are required:

Type of database 8VHUQDPH#6(783

Path to database 8QLYHUVDODFFHVV

NOTE: COMOS distinguishes between three types of user names, that

Unrestricted Siemens AG 2015 All rights reserved.

Opening and creating a project

For doing so, several tabs are available 1DPH 3URMHFW

Unrestricted Siemens AG 2015 All rights reserved.

command Rights the users and their

For each object, the corresponding

Unrestricted Siemens AG 2015 All rights reserved.

Design and layout of the interface

The graphic shows the main areas and

Working with the COMOS user interface

Unrestricted Siemens AG 2015 All rights reserved.

(in addition) in a separate tab in the $8QLW 76XEXQLW

This additional tab can also be Context menu

Unrestricted Siemens AG 2015 All rights reserved.

Windows in the Navigator and in the 3ODQW 3ODQW #

For doing so, the docking indicator

Unrestricted Siemens AG 2015 All rights reserved.

Unrestricted Siemens AG 2015 All rights reserved.

Learning target(s) of this training unit:

Handling and configuration of the Navigator

Unrestricted Siemens AG 2015 All rights reserved.

Functions of the Navigator

Fundamental features and functions in the Navigator are:

Displaying engineering objects in a hierarchical structure

Tabs in the Navigator

In the basic set up, the upper part of the 8QLWV/RFDWLRQV'RFXPHQWV%DVHREMHFWV

Units: Contains function-related structures / objects

COMOS internal documents. 3ULQW

Provides specific commands / menus. 6HDUFK

Serves (for example) for setting the Navigator. 1DYLJDWRUVHWWLQJV

Unrestricted Siemens AG 2015 All rights reserved.

Navigate in the context menu

Unrestricted Siemens AG 2015 All rights reserved.

Text search in the Navigator

5HODWLYHQDPH 'HVFULSWLRQ 7H[W

Unrestricted Siemens AG 2015 All rights reserved.

The window Navigator settings

Contains the following control groups:

Display Controls the display of the pieces of information in the

Unrestricted Siemens AG 2015 All rights reserved.

in the areas of the Navigator 0DLQWHQDQFH

(in addition) in a separate tab in the $8QLW 76XEXQLW

Windows in the Navigator and in the 3ODQW 3ODQW #

starting COMOS (because 8QLWV/RFDWLRQ'RFXP%DVHREM

Context menu %9HVVHO

%9HVVHO 'HVFULSWLRQ 9HVVHO )ROGHU