SPPA-T3000 User Guide

Engineering User Guide (1/3)

 Engineering User Guide (1/3) Page: 2 of 313
LKZ:DE AL:N ECCN:4E992

Documenation User Guide

SPPA-T3000 USER GUIDE .............................................................................................................................................. 1

1 GETTING STARTED .............................................................................................................................. 7

1.1 Implementation Example...................................................................................................................... 8

1.2 Logging In .............................................................................................................................................. 9

1.3 Orientation ........................................................................................................................................... 10

1.4 Creating the Project Structure........................................................................................................... 13

1.4.1 Creating Project Nodes ......................................................................................................................... 15
1.4.2 Assigning to a Runtime Container ........................................................................................................ 16
1.4.3 Creating Diagrams ................................................................................................................................ 17

1.5 Working with Diagrams ...................................................................................................................... 19

1.5.1 Automation Functions............................................................................................................................ 19
1.5.2 Working with Function Diagrams .......................................................................................................... 20
1.5.2.1 Opening a Diagram in the Diagram Editor............................................................................................ 20
1.5.2.2 Placing Symbols .................................................................................................................................... 21
1.5.2.3 Making Connections.............................................................................................................................. 24
1.5.2.4 Setting Parameters................................................................................................................................ 26
1.5.3 Working with Plant Displays.................................................................................................................. 29
1.5.3.1 Inserting into the Plant Display Hierarchy............................................................................................. 29
1.5.3.2 Creating Free Graphics ......................................................................................................................... 30
1.5.3.3 Creating Dynamic Elements.................................................................................................................. 33

1.6 Actualizing Changes ........................................................................................................................... 37

1.6.1 Transaction Handling ............................................................................................................................ 37
1.6.2 Status Indication.................................................................................................................................... 39

1.7 Operation Mode ................................................................................................................................... 40

1.7.1 Operating with Plant Displays ............................................................................................................... 41
1.7.2 Forcing Signals...................................................................................................................................... 44

1.8 Deleting the Example .......................................................................................................................... 48

2 PORTAL ................................................................................................................................................ 49

3 WORKBENCH ...................................................................................................................................... 51

3.1 General Layout .................................................................................................................................... 51

3.1.1 Favorites ................................................................................................................................................ 52
3.1.1.1 Adding Favorites ................................................................................................................................... 53
3.1.1.2 Managing Favorites............................................................................................................................... 54
3.1.2 View ....................................................................................................................................................... 56
3.1.2.1 Saving and Deleting the Workspace..................................................................................................... 57
3.1.3 Window.................................................................................................................................................. 58
3.1.4 Dockable Windows................................................................................................................................ 59
3.1.5 Customizing Toolbars............................................................................................................................ 60
3.1.6 Printing from the Workbench................................................................................................................. 61

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 3 of 313
LKZ:DE AL:N ECCN:4E992

3.1.7 Keyboard Shortcuts............................................................................................................................... 62

3.2 Workbench Mode ................................................................................................................................ 64

3.3 Exiting the Workbench ....................................................................................................................... 64

4 PROJECT VIEW ................................................................................................................................... 66

4.1 Starting the View ................................................................................................................................. 66

4.2 General Layout .................................................................................................................................... 66

4.2.1 Tree View .............................................................................................................................................. 67
4.2.1.1 Navigate Up........................................................................................................................................... 69
4.2.2 List View ................................................................................................................................................ 69
4.2.3 Toolbar .................................................................................................................................................. 70
4.2.4 Context Menus ...................................................................................................................................... 70
4.2.5 Drag and Drop ....................................................................................................................................... 70
4.2.6 List View Appearance............................................................................................................................ 71
4.2.7 Saving the View..................................................................................................................................... 73
4.2.8 Selecting Items in the Project View....................................................................................................... 73
4.2.9 Open Containing Folder ........................................................................................................................ 75
4.2.10 Protocol Report Browser ....................................................................................................................... 75
4.2.11 Dialog Exporting .................................................................................................................................... 76
4.2.12 Dialog Printing ....................................................................................................................................... 77
4.2.13 Illegal Characters .................................................................................................................................. 77

4.3 Multi User Operation ........................................................................................................................... 78

4.4 Project Functions ................................................................................................................................ 79

4.4.1 Create New Project Node ..................................................................................................................... 79
4.4.2 Create New Library Node...................................................................................................................... 80
4.4.3 Rename Node ....................................................................................................................................... 81
4.4.4 Delete Node........................................................................................................................................... 83
4.4.5 Project Settings ..................................................................................................................................... 84
4.4.5.1 Setting of Colors.................................................................................................................................... 85
4.4.5.2 Setting of Styles .................................................................................................................................... 86
4.4.5.3 Connector Styles ................................................................................................................................... 87
4.4.5.4 Link Styles ............................................................................................................................................. 89
4.4.5.5 Global Settings ...................................................................................................................................... 90
4.4.5.6 Workbench Settings .............................................................................................................................. 95
4.4.5.7 Operation View Settings........................................................................................................................ 97
4.4.5.8 Diagram Styles .................................................................................................................................... 101
4.4.5.8.1 Calculating the Plant Display Area...................................................................................................... 104
4.4.5.9 Print Connector ................................................................................................................................... 105
4.4.5.10 Symbol Styles...................................................................................................................................... 106
4.4.5.11 ASD Styles .......................................................................................................................................... 108
4.4.5.12 Archive Settings .................................................................................................................................. 111
4.4.5.13 Report Settings.................................................................................................................................... 112
4.4.5.14 VGB Documentation Settings ............................................................................................................. 113
4.4.5.15 Plant Display Hierarchy....................................................................................................................... 115
4.4.5.16 Diagnostic View................................................................................................................................... 116
4.4.5.17 Point View............................................................................................................................................ 117
4.4.5.18 Trends/Curves ..................................................................................................................................... 118
4.4.5.19 Defining Document Types................................................................................................................... 119
4.4.5.19.1 Document Types ................................................................................................................................. 121
4.4.5.20 Inheritance Rules ................................................................................................................................ 122
4.4.5.20.1 Default Rule Inheritance Setting ......................................................................................................... 124
4.4.5.20.1.1 Creating User Defined Rules for Specific Ports.................................................................................. 126
4.4.5.20.2 Creating Type Specific Rules.............................................................................................................. 130
4.4.5.20.2.1 Inheritance Rules Syntax .................................................................................................................... 134
4.4.5.20.3 Inheriting Rule Changes...................................................................................................................... 135

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 4 of 313
LKZ:DE AL:N ECCN:4E992

4.4.6 User Specific Settings ......................................................................................................................... 136

4.4.6.1 Setting of Styles .................................................................................................................................. 136
4.4.6.2 Connector Styles ................................................................................................................................. 137
4.4.6.3 Link Styles ........................................................................................................................................... 138
4.4.6.4 Global Settings .................................................................................................................................... 140
4.4.6.5 Workbench Settings ............................................................................................................................ 144
4.4.6.6 Operation View Settings...................................................................................................................... 145
4.4.6.7 Diagram Styles .................................................................................................................................... 149
4.4.6.8 Print Connector ................................................................................................................................... 152
4.4.6.9 Symbol Styles...................................................................................................................................... 153
4.4.6.10 ASD Styles .......................................................................................................................................... 154
4.4.6.11 Plant Display Hierarchy....................................................................................................................... 156
4.4.6.12 Diagnostic View................................................................................................................................... 156
4.4.6.13 Point View............................................................................................................................................ 157
4.4.6.14 Trends/Curves ..................................................................................................................................... 158
4.4.7 Setting the System Diagram Root....................................................................................................... 159
4.4.8 Project Version Management.............................................................................................................. 161
4.4.8.1 Creating Project Versions ................................................................................................................... 161
4.4.8.2 Comparing Project Versions ............................................................................................................... 162
4.4.9 Assigning Pictograms and Faceplates................................................................................................ 164
4.4.9.1 Adding or Deleting Prototype Assignments ........................................................................................ 165
4.4.9.2 Assigning Ports ................................................................................................................................... 166
4.4.9.2.1 Inheritance Assignment of Pictogram Properties ............................................................................... 168
4.4.9.3 Setting or Deleting the Default Prototype and Automation Function.................................................. 169
4.4.10 User Specific Plant Displays in the Project View................................................................................ 170
4.4.11 Alarm Sounds ...................................................................................................................................... 170
4.4.11.1 Importing and Deleting Sounds........................................................................................................... 171
4.4.11.2 Organizing Sounds.............................................................................................................................. 172
4.4.11.3 Defining Sound Alarm Groups ............................................................................................................ 173
4.4.12 Alarm Printers...................................................................................................................................... 174
4.4.12.1 Defining Print Alarm Groups ............................................................................................................... 174
4.4.12.2 Stopping and Starting Alarm Printing.................................................................................................. 176
4.4.13 Alarm Types ........................................................................................................................................ 177
4.4.13.1 Adding Alarm Types ............................................................................................................................ 177
4.4.13.2 Editing Alarm Types ............................................................................................................................ 179
4.4.13.3 Deleting Alarm Types .......................................................................................................................... 180
4.4.14 Downloading Files from a Server........................................................................................................ 181
4.4.15 Images ................................................................................................................................................. 182
4.4.15.1 Importing Images................................................................................................................................. 182
4.4.15.2 Deleting Images .................................................................................................................................. 183

4.5 Runtime Containers .......................................................................................................................... 183

4.5.1 Types of Runtime Containers.............................................................................................................. 184
4.5.2 Runtime Containers on Servers.......................................................................................................... 185
4.5.2.1 Creating Runtime Containers.............................................................................................................. 185
4.5.2.2 Creating S7 Runtime Containers ........................................................................................................ 187
4.5.2.2.1 Editing the Main Properties ................................................................................................................. 190
4.5.2.2.2 Expert Properties................................................................................................................................. 193
4.5.2.3 Editing Runtime Containers ................................................................................................................ 193
4.5.2.4 Deleting Runtime Containers .............................................................................................................. 195
4.5.2.4.1 Deleting Specialized S7 Runtime Containers ..................................................................................... 196
4.5.2.5 Peer-to-Peer Connections................................................................................................................... 198
4.5.2.5.1 Create New Peer-to-Peer Connections .............................................................................................. 199
4.5.2.5.2 Editing Existing Peer-to-Peer Connections......................................................................................... 200
4.5.2.5.3 Deleting Peer-to-Peer Connections .................................................................................................... 202
4.5.2.6 Starting or Stopping Runtime Containers ........................................................................................... 203
4.5.2.7 Starting or Stopping S7 Stations......................................................................................................... 204
4.5.2.8 Loading an S7 Execution Frame......................................................................................................... 206
4.5.2.9 List S7 Block Versions ........................................................................................................................ 207
4.5.3 Assigning Function Diagrams to Runtime Containers ........................................................................ 209
4.5.4 Setting the Cycle Time ........................................................................................................................ 212
4.5.4.1 Setting the Cycle Time at the Project Node Level .............................................................................. 212
4.5.4.2 Setting the Function Diagram Cycle Time .......................................................................................... 213

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 5 of 313
LKZ:DE AL:N ECCN:4E992

4.5.4.3 Setting the AF Block Cycle Time ........................................................................................................ 214

4.5.4.4 FUM Cycle Time Rules ....................................................................................................................... 215
4.5.5 Execution Sequence ........................................................................................................................... 215
4.5.5.1 Automatic Scheduling.......................................................................................................................... 217
4.5.5.2 Manual Scheduling.............................................................................................................................. 218
4.5.5.2.1 Component Scheduling ....................................................................................................................... 219
4.5.5.2.1.1 Switching Component Scheduling On and Off ................................................................................... 219
4.5.5.2.1.2 Setting Component Scheduling .......................................................................................................... 219
4.5.5.2.1.3 Activating Component Scheduling ...................................................................................................... 222
4.5.5.2.1.4 Modifying Components ....................................................................................................................... 224
4.5.5.2.2 Diagram Scheduling ............................................................................................................................ 224
4.5.5.2.2.1 Setting Diagram Scheduling................................................................................................................ 225
4.5.5.2.2.2 Activating Diagram Scheduling ........................................................................................................... 228
4.5.5.2.2.3 Modifying Diagrams............................................................................................................................. 229
4.5.5.2.2.4 Importing Manually Scheduled Diagrams ........................................................................................... 230
4.5.6 Calculation of System Resources ....................................................................................................... 231
4.5.6.1 Assigning Application Profiles to Runtime Containers ....................................................................... 231
4.5.6.2 Calculate System Resources .............................................................................................................. 231

4.6 Diagram Functions............................................................................................................................ 234

4.6.1 Creating Function Diagrams and Plant Displays ................................................................................ 234
4.6.2 Small Plant Displays............................................................................................................................ 236
4.6.3 Rename Diagram ................................................................................................................................ 237
4.6.3.1 Inheritance for Diagram Renaming ..................................................................................................... 240
4.6.4 Delete Diagram ................................................................................................................................... 241
4.6.5 Open Diagram in Configuration Mode ................................................................................................ 242
4.6.6 Find Diagram ....................................................................................................................................... 243
4.6.7 Find Tag Usages ................................................................................................................................. 245
4.6.8 Find Tag Duplicates ............................................................................................................................ 248
4.6.9 Find Open Function Diagram Connections......................................................................................... 249
4.6.10 Find Open Plant Display Mappings..................................................................................................... 250
4.6.11 Hierarchy Browser............................................................................................................................... 251
4.6.12 Title Block ............................................................................................................................................ 254
4.6.12.1 Editing the Title Block.......................................................................................................................... 256
4.6.13 Copying Diagrams............................................................................................................................... 260
4.6.13.1 A Conceptual Example........................................................................................................................ 263
4.6.13.2 How the Copy and Modify Rules Work ............................................................................................... 264
4.6.13.3 Copy and Modify Preview ................................................................................................................... 268
4.6.13.4 Copy and Modify Rules ....................................................................................................................... 270
4.6.14 Batch Printing ...................................................................................................................................... 272

4.7 Transaction Handling........................................................................................................................ 275

4.7.1 Transaction Handling for Function Diagrams ..................................................................................... 276
4.7.2 Transaction Handling for Plant Displays, User Defined Reports and Point Groups .......................... 278
4.7.3 Commit ................................................................................................................................................ 279
4.7.4 Rollback ............................................................................................................................................... 280
4.7.5 Activate ................................................................................................................................................ 281
4.7.6 Deactivate............................................................................................................................................ 283
4.7.7 Commit or Rollback Last Activation/Deactivation ............................................................................... 285
4.7.8 Recovering Project and Runtime Container Inconsistencies ............................................................. 286

4.8 Online Configuration of SIMATIC S7............................................................................................... 287

4.8.1 Hardware Configuration ...................................................................................................................... 287
4.8.1.1 How to Carry Out an S7 Hardware Configuration .............................................................................. 289
4.8.1.2 Configure S7 Hardware....................................................................................................................... 290
4.8.1.3 Load S7 Hardware .............................................................................................................................. 291
4.8.1.4 Load S7 Connections .......................................................................................................................... 293

4.9 Project Documentation..................................................................................................................... 294

4.9.1 Project Node........................................................................................................................................ 294
4.9.2 Tag Names .......................................................................................................................................... 295
4.9.3 Library Node ........................................................................................................................................ 297

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 6 of 313
LKZ:DE AL:N ECCN:4E992

4.9.4 Uncommitted Changes........................................................................................................................ 298

4.9.5 Forced Ports ........................................................................................................................................ 299
4.9.6 Unactivated Changes .......................................................................................................................... 299
4.9.7 Peer to Peer Connections ................................................................................................................... 300
4.9.8 License Status ..................................................................................................................................... 302
4.9.9 System Settings .................................................................................................................................. 304
4.9.10 Manual Scheduling.............................................................................................................................. 305
4.9.11 Print Alarm Groups.............................................................................................................................. 306
4.9.12 Sound Alarm Groups........................................................................................................................... 307
4.9.13 Hardware Configuration States ........................................................................................................... 308
4.9.14 Failsafe/FM458 Activation States ....................................................................................................... 309
4.9.15 FM458 Operators ................................................................................................................................ 311
4.9.16 Documentation of GSD Files............................................................................................................... 312

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 7 of 313
LKZ:DE AL:N ECCN:4E992

ENGINEERING USER GUIDE

Today, architect engineers, independent power producers, and plant owners have to manage a huge amount of project
data and plant information. To be competitive in the power business it is essential to increase productivity, reduce
project preparation, and maintenance times while minimizing all costs. Collecting, storing, and managing information
for the whole lifetime of a plant is a challenge which can easily be met by SPPA-T3000, due to its built-in data
consistency and integrated engineering

The Engineering Views form the basis for each SPPA-T3000 system. Its intuitive, user friendly graphical interface
allows for immediate and cost effective conversions from technological task definitions to high quality I&C
implementations.

Further key features are:

• Horizontal Integration (product lifecycle)

• Integrated Engineering through close dependency of operation and automation
• Simultaneous work by several users independent of the location and with remote access

The central functions of the engineering are:

• Project View (Project Functions, Project Documentation, Project Administration, Plant Display Hierarch View)
The Project View is the main engineering view from which the project is organized.
The Plant Displays for plant operation are organized in the Plant Display Hierarchy View. Engineers can
monitor and force live signals in Dynamic Function Diagrams.
• Diagram Editor (Function Diagram, Plant Display, Search/Navigation, Integrated Engineering)
The Diagram Editor is accessed via the Project View, this is a graphic tool for producing all diagrams.
• Commissioning functions (Transaction Handling, Online reconfiguration)
Transaction handling is the way in which engineering changes made by the user are saved in and actualized
in the system.
• Spreadsheet engineering
Spreadsheet engineering is a tool that allows the user to extract engineering data from many different
components, and view or edit them in a single spreadsheet.
• Export/Import
A number of functions exist to facilitate the importing and exporting of data to and from SPPA-T3000.
• Logs of engineering changes
The system allows for archiving of configuration changes with user name, date and time. Through this, the
user is provided with the ability to analyze the changes made between two modifications and determine what
was changed, by whom and when. Additionally, the access to the system is tracked.
• Diagram output
Different print formats can be selected to generate the plant documentation. Therefore, the virtual diagram
size will be transformed according to the chosen format. Title block information and page connectors are
generated automatically according to the project settings.

1 Getting Started
What is the Aim of Getting Started?

Getting Started is aimed at new users to become acquainted with engineering in SPPA-T3000. The fundamental
engineering techniques and concepts are not only explained, but also illustrated by means of a practical example of
implementation.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 8 of 313
LKZ:DE AL:N ECCN:4E992

The user is taken step by step through the actions needed to implement the example. The system concepts and
terminology are explained at each step.

The aim of Getting Started is not to describe the complete system or every possibility available, but rather to gain
familiarity with the basic functionality. A full description can be found in the Engineering User Guide.

The implementation example is made for an existing project, and is for a user assigned with the appropriate
rights to perform engineering tasks.

If the implementation example is implemented at a running plant, care must be taken not to interfere with the
normal operation of the plant or the control system.

1.1 Implementation Example

A schematic drawing of the implementation example is shown below:

The plant for the example consists of:

• A water tank.
• A water pump feeding the tank.
• An analog tank level signal with threshold values for stopping the pump, and high and low level Alarms.

In Getting Started the user is shown how to implement this example in SPPA-T3000. The steps followed are:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 9 of 313
LKZ:DE AL:N ECCN:4E992

1. The user logs in and is orientated with the Workbench.

2. Additional project structure is created for the example.
3. A Function Diagram is created, containing the Automation logic.
4. A Plant Display is created, for operation of the plant.
5. The example is actualized (i.e. made to run in the online system).
6. Plant operation using the example is discussed, and a signal value is forced.
7. The example is deleted from the system.

1.2 Logging In
In order to use the system the user has to login. SPPA-T3000 is a web based application and the user logs in on a
Client computer. The Client Computer has a light load, most of the data and software are on the SPPA-T3000 Server.
Access to the system is password protected.

How to Login

If any problems are encountered during the login process, consult the system specialist for the project.

1. Start the Client Computer.

2. Start the Web Browser on the Client Computer.

The user needs the URL of the SPPA-T3000 Server for the project. This URL is available from the
system specialist for the project.

3. Enter the URL of the SPPA-T3000 Server in the address field of the browser. When the server has been
accessed an SPPA-T3000 Portal will appear, which contains the options for running the system.

Click on Login Project to Open Workbench as Application

4. When the Login dialog box appears, enter the User name and Password

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 10 of 313
LKZ:DE AL:N ECCN:4E992

The user must be assigned a User name and a Password by the system specialist.

5. Click on Login.
6. If the Login was successful the Workbench will open.

Users are assigned roles in the system. The role defines the access rights the user has in the system e.g. to
modify logic, or to operate the plant. If the user has been assigned different roles, the Workspace Selection
dialog box will appear. Then the user can select which workspace the Workbench will start up in.

1.3 Orientation
Once the Workbench has been opened the user can orientate him or herself to the workbench layout, learn how to
open and close views in the Workbench, and learn how to use the Operation Mode.

What is Available from the Workbench?

The Workbench is the central or uppermost view in the SPPA-T3000 system, all other views are accessible from the
Workbench. The SPPA-T3000 views cater to the different needs of users e.g. engineers, operators, maintenance staff.
The views are opened as windows in the Workbench Work Area.

The following views can be opened from the Workbench:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 11 of 313
LKZ:DE AL:N ECCN:4E992

• Project View: This is the main view for engineering. The complete project structure is available here, as well
as all the project data.
• The Diagram Editor is opened via the Project View and is used to configure all application software and logic,
as well as the Plant Displays used to operate the plant. The Runtime Container is configured and the user
can implement configuration changes in the running system. Project administration is also done in the Project
View.
• Plant Display Hierarchy View: The structure that the operator uses to navigate between Plant Displays is
defined here.
• Diagnostic View: Displays system information and is used for fault analysis.
• Lifetime Calculation: A system for calculating the lifetime consumption of steam generator components.
• TDY: A system that performs thermodynamic monitoring and diagnostics of the power plant.
• Alarm Sequence Display: All Alarms are displayed and organized in the ASD.
• Prototype Editor: Used to create and edit user defined Pictograms and Faceplates.
• Reports: Used to extract and view historical process information from the archive.

Operation Mode is also selected in the Workbench, in this mode the plant is controlled and monitored.

How Do I Open a View in the Workbench?

• To open the Project View, Plant Display Hierarchy View, Alarm Sequence Display, Diagnostic View etc. click
on Applications on the menu bar, and then click on the view in the drop down menu.
•

• The view will then open in the Work Area.

• As many different views as are required can be opened simultaneously and arranged in the Workbench (an
example of a Workbench with many views open is shown here).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 12 of 313
LKZ:DE AL:N ECCN:4E992

• In the windows toolbar of the Workbench, a button can be seen for each open view. If the views are
overlapping or overlaying each other, click on the button in the windows toolbar to make the view visible.
•

• To start (or stop) Operation Mode click on Mode on the menu bar then click on Operation Mode in the drop
down menu.
•

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 13 of 313
LKZ:DE AL:N ECCN:4E992

The user can close any open view at any stage in the implementation example and also reopen it if required.

• Before proceeding with the implementation example, close all open views in the Workbench and stop
Operation Mode.

1.4 Creating the Project Structure

All elements of the project are structured in the Project Hierarchy. This Project Hierarchy is arranged and viewed in the
Project View.

How to Open the Project View

The user must be logged in and the Workbench must be opened.

• Select the Applications menu from the Workbench menu bar, then Project View from the drop down menu.

The Project View will open in the Workbench.

An example of an open Project View is shown here. The contents of the Project View vary for different projects.

What is in the Project View?

The Project View is divided into two Frames:

• The left hand Frame is the Tree View . The Tree View shows the arrangement of Nodes in the project. The
Nodes are like folders which are used to organize the project, this organization is called the Project Hierarchy.
There are two types of Nodes:
o Project Nodes: These contain all the diagrams that are configured for the project. The contents of
the Project Nodes are project specific.
Project Nodes may also contain other Project Nodes, depending on the design of the Project
Hierarchy. The Project Hierarchy may for example be divided according to plant areas.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 14 of 313
LKZ:DE AL:N ECCN:4E992

Project Nodes have the following representation in the Tree View:

o Library Nodes: These contain all of the functions and elements that can be drawn from, to configure
the project. The contents of the Library Nodes are largely system specific (user defined functions
called Macros are also stored in Library Nodes).
Library Nodes have the following representation in the Tree View:

• The right hand Frame is the List View . The List View shows the contents of the Node selected in the Tree
View. These contents are typically either:
o Other Project Nodes, represented by:

o Function Diagrams: These contain all the logic and functionality that is configured. This includes all
signal input and output, interlocks, calculations and interfaces for operation. Function Diagrams are
represented by:

o Plant Displays: These are pictures or graphic presentations that the operator uses to operate the
plant. They contain all the drives and indicators and normally a graphical representation of the plant
layout. Plant Displays are indicated as:

Creating the Project Structure consists of:

• Creating Project Nodes

• Assigning to a Runtime Container
• Creating Diagrams

Any Project Nodes or diagrams created for the implementation example can be deleted, and the project will be
returned to its original state.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 15 of 313
LKZ:DE AL:N ECCN:4E992

1.4.1 Creating Project Nodes

For the implementation example one Project Node is to be created, called Tank Example. To create a new Project
Node for inclusion in the Project Hierarchy proceed as follows:

The Project View must be open.

1. Select the root Node in the Tree View. This Node will be the parent Node of the new Node that is being
created.

2. Select the Project menu, then New, then Project Node from the drop down menus.
3. A new Project Node is created as DefaultName, under the root Node.

The new Project Node can then be named:

1. Select the DefaultName Node in the Tree view.

2. Select the Project menu, then Rename from the drop down menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 16 of 313
LKZ:DE AL:N ECCN:4E992

3. A cursor will appear at the Node name.

4. Delete the name of the old Node and enter the new name Tank Example, then press Enter.

The Node is renamed as Tank Example.

1.4.2 Assigning to a Runtime Container

The Project Node will be assigned to a Runtime Container. This means that the logic included in Function Diagrams in
the Project Node will be executed in the Runtime Container to which the Project Node has been assigned.

It is possible to assign individual Function Diagrams to a Runtime Container. It is however preferable to assign
the complete Project Node .

To assign the Tank Example Project Node in the implementation example to an Runtime Container proceed as
follows:

The Project View must be open.

1. Select the Tank Example Project Node in the Tree View.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 17 of 313
LKZ:DE AL:N ECCN:4E992

2. Select the Edit menu, then Assign Runtime Container from the drop down menu.
3. The Assign Runtime Container dialog box will appear.

The organization of the Runtime Containers is project specific. Ask the system specialist for the
project to identify the Runtime Container that the implementation example should be assigned to.

4. Select Runtime Container to be assigned from the Runtime Container Assignment drop down list. In the
example above Runtime Container afc 103 is being selected.
5. Click on Save.

The Function Diagrams within the Tank Example Project Node will be assigned to the selected Runtime Container.

1.4.3 Creating Diagrams

For this implementation example a Function Diagram and a Plant Display will be created in the Tank Example
Project Node.

• One Function Diagram named: Tank Logic.

• One Plant Display named: Tank Display

Creating the Function Diagram

The Project View must be open.

1. Select the Tank Example Project Node in the Tree View. The new Function Diagram will be created in this
Node.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 18 of 313
LKZ:DE AL:N ECCN:4E992

2. Select the Project menu, then New, then Function Diagram from the drop down menus.
3. The New Function Diagram dialog box appears.

4. Enter the name of the Function Diagram : Tank Logic, leave the Plant Display field open. (For simplicity,
only a diagram name has been entered, and no designation).
5. Click on OK, the Function Diagram will be created.

Creating the Plant Display

The Project View must be open.

1. Select the Tank Example Project Node in the Tree View. The new Plant Display will be created in this Node.
2. Select the Project menu, then New, then Plant Display from the drop down menus.
3. The New Plant Display dialog box appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 19 of 313
LKZ:DE AL:N ECCN:4E992

4. Enter the name of the Plant Display : Tank Display, leave the Function Diagram field open (For
simplicity, only a diagram name has been entered, and no designation).
5. Click on OK, the Plant Display will be created.

The two diagrams for the implementation example are now created.

1.5 Working with Diagrams

This section explains Function Diagrams and Plant Displays and shows how to configure them using the Diagram
Editor.

First the concept of Automation Functions is explained as this applies to both types of diagrams, and is a central
SPPA-T3000 concept. All the automation logic is created in the Function Diagrams, while the Plant Display pictures
are for plant operation.

Any changes made to diagrams for the implementation example can be deleted, and the project returned to its
original state.

1.5.1 Automation Functions

SPPA-T3000 has a component based software architecture. This means that every Automation Function is a single
component that carries out not only Automation tasks but also the functionality for operating and monitoring, alarming,
engineering and diagnostic purposes.

This concept is represented graphically:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 20 of 313
LKZ:DE AL:N ECCN:4E992

The Automation Function has interfaces not only for connection with other Automation Functions, but also for all other
system functions. There are no separate systems, for example for diagnostics or operating, SPPA-T3000 simply
provides a different view of the same components.

The Automation Functions are provided in the SPPA-T3000 Library for use in projects.

1.5.2 Working with Function Diagrams

Function Diagrams contain all the logic and functionality that must be configured for projects. In the implementation
example the logic is created by:

• Opening the Function Diagram in the Diagram Editor.

• Placing symbols in the diagram.
• Making connections.
• Setting Parameters.

1.5.2.1 Opening a Diagram in the Diagram Editor

The Diagram Editor is a graphic tool which is used for editing Plant Displays and Function Diagrams. All functionality
required for engineering of the Function Diagrams and Plant Displays is available in the Diagram Editor.

To open the Tank Logic Function Diagram in the Diagram Editor, proceed as follows:

The Project View must be open.

1. Select the Tank Example Project Node in the Tree View and then the Tank Logic Function Diagram in the
List View.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 21 of 313
LKZ:DE AL:N ECCN:4E992

2. Select the Edit menu, then Open in Configuration Mode from the drop down menu.
3. The Diagram Editor will now start up, and the Tank Logic Function Diagram will open (The diagram is
empty as nothing has been configured yet).

1.5.2.2 Placing Symbols

The Library is contained in a window which is docked on the left hand side of the Diagram Editor. This library contains
all the Automation Functions, Hardware Proxies and Pictogram symbols (for use in the Plant Displays) which can be
selected and used in the Project.

In order to use Automation Functions in an SPPA-T3000 project, they have to be placed as AF Blocks in Function
Diagrams.

For the implementation example, two AF Blocks are required:

• MOTOR (Controller for motor drives) for controlling the pump. The AF Block provides all the logic, interfaces
and interlocks needed to control the pump.
• ASMON (Analog Signal Monitor) to monitor the tank level signal. The AF Block provides all the logic and
interfaces needed to monitor the analog value and provide limit values.

To place these AF Blocks proceed as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 22 of 313
LKZ:DE AL:N ECCN:4E992

The Tank Logic Function Diagram is open.

Before placing symbols for the implementation example, ensure integrated engineering is switched off.

To check whether integrated engineering is off:

In the Diagram Editor, select Edit then Integrated Engineering from the drop down menu. Integrated
engineering is off when the menu item is unticked.

1. Find the MOTOR AF Block in the Library. This is under Library > Automation > Open Loop Controller.
1. Double click on the Automation Library Node in the Library and the Library Nodes for the
Automation Functions will appear.

2. Double click on the Open Loop Controller Library Node.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 23 of 313
LKZ:DE AL:N ECCN:4E992

2. Select the MOTOR Automation Function, by clicking on it.

3. Simply move the cursor over the empty Tank Logic Function Diagram, the symbol for the AF Block moves
with it.
4. Move the AF Block symbol to the approximate position shown in the example below, and then click again.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 24 of 313
LKZ:DE AL:N ECCN:4E992

The symbol will be placed in the diagram.

• Repeating the above procedure, place an ASMON AF Block in the diagram. The ASMON can be found under
Library > Automation > Conditioning and Monitoring in the Library.
•

1.5.2.3 Making Connections

When the Automation Functions have been placed in the diagram there is a connection required between two of their
Ports. An interlock is required that will cause the pump to trip when the tank level is too high.

A binary limit value signal must be generated in the ASMON AF Block. The ASMON output Q1 (Limit Value 1) will be
used. The parameters for the limit value will be set with the Alarms later.

To realize the interlock the Q1 output Port of the ASMON must be connected to the input Port P1_STOP (Protection 1
Command Stop) of the MOTOR.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 25 of 313
LKZ:DE AL:N ECCN:4E992

To make this connection proceed as follows:

The Tank Logic Function Diagram is open in the Diagram Editor.

1. Click on the Connection (Graphical Interactor) icon on the toolbar.

2. Move the cursor over the ASMON block, the Ports available for connection are highlighted.
3. Click on the Q1 Port of the ASMON block.

When clicking on a Port, click just inside the AF Block on the Port Description.

Do not click on the border of the AF Block.

4. A line is connected to the source Port. As the cursor is moved the line moves with it.

5. Move the cursor to the MOTOR block, the Ports available and suitable for connection are highlighted.
6. Click on the P1_STOP Port.

The connection is made.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 26 of 313
LKZ:DE AL:N ECCN:4E992

1.5.2.4 Setting Parameters

Symbols in Function Diagrams have a number of properties or settings associated with them. These are called
parameters and can be accessed in the parameter mask. The parameter mask is a dialog box which can be opened
and contains all the parameters for a symbol. Parameters are also used for setting alarms.

Alarms are used to warn operating staff about conditions that require their attention. Alarms are configured in the
Function Diagrams, and are viewed by operators in the Operation Mode.

SPPA-T3000 has a number of Alarm Types which indicate Alarm priority (e.g. ALARM or WARNING) or Alarm origin
(e.g. ICALARM). The Alarm text and descriptions can also be defined.

The Alarms to be configured for the implementation example are:

Tag Name Level Alarm Alarm Type Port Name

TANK LEVEL 90% HIHI ALARM Q1
TANK LEVEL 80% HI WARNING Q2
TANK LEVEL 20% LO WARNING Q3

To set the Alarms for the implementation example proceed as follows:

Open the Tank Logic Function Diagram in the Diagram Editor.

1. Select the ASMON AF Block by clicking on it.

2. Click the right mouse button to open the context menu then select Edit from the context menu.
3. The parameter mask for the ASMON AF Block will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 27 of 313
LKZ:DE AL:N ECCN:4E992

If a column is too narrow it can be widened: position the cursor over the column border at the head of
the table, then press the left mouse button and drag the column to the desired width, then release the
mouse button.

4. Ensure that the Parameter Set 1 sheet of the mask is open (if not, open it by clicking on it).
5. Enter the limit values for the three Alarms:
LV1: 90
LV2: 80
LV3: 20

6. Check the signal range (that it corresponds to 0..100%):

UL: 100
LL:0

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 28 of 313
LKZ:DE AL:N ECCN:4E992

7. Check that the limit values are switched on:

LSG1, LSG2, LSG3 are selected
and the upper or lower limit is selected correctly:
HI_LOW1, HI_LOW2 are selected
HI_LOW3 is not selected.

8. Scroll to the bottom of the mask to the parameters for the output Ports, then click on the Alarm column header
to expand the Alarm parameters.

9. Switch the Alarms on by ticking the Alarm column for outputs Q1, Q2, Q3.
10. Ensure that Inheritance is broken by deselecting the check box at the Active Alarm Text and Deactive
Alarm Text columns.

11. Edit the Active Alarm Text and Deactive Alarm Text columns for outputs Q1, Q2, Q3:
Q1: >HIHI and <HIHI
Q2: >HI and <HI
Q3: <LO and >LO

12. Click on Save.

The three Alarms have now been configured.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 29 of 313
LKZ:DE AL:N ECCN:4E992

1.5.3 Working with Plant Displays

Plant Displays are pictures used by operators to monitor and operate the plant. The Plant Displays are configured in
the Diagram Editor and used for operating in the Operation Mode.

Plant Displays are inserted in the Plant Display Hierarchy, this hierarchy is logically organized to allow easy navigation
between Plant Displays.

Plant Displays typically include a schematic representation of the plant layout, this is created using free graphics. The
dynamic elements (representing measurements, drives etc.) are then added.

1.5.3.1 Inserting into the Plant Display Hierarchy

The Plant Display Hierarchy is the organization of the Plant Displays for the Operation Mode. The operator navigates
through the Plant Display Hierarchy to find Plant Displays.

The Plant Display Hierarchy is not the same as the Project Hierarchy, the two are created independently of
each other.

The Plant Display Hierarchy is created by dragging and dropping Plant Displays from the Project View to the Plant
Display Hierarchy View.

To insert the Tank Display Plant Display into the Plant Display Hierarchy proceed as follows:

1. Open the Project View, select the Tank Example Node in the Tree View.
2. To start the Plant Display Hierarchy View: Select the Applications menu from the Workbench menu bar, then
Plant Display Hierarchy View from the drop down menu.
3. The Plant Display Hierarchy View will now open (in engineering mode) in the Workbench.

4. The Plant Display is inserted into the hierarchy by drag and drop:
1. In the List View of the Project View click on the Tank Display Plant Display to select it.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 30 of 313
LKZ:DE AL:N ECCN:4E992

2. Press and hold the left mouse button with the cursor over the Tank Display Plant Display, then
move the cursor to the Plant Display Hierarchy View. The cursor indicates that the item is being
dragged.

3. Still holding the left mouse button, move the cursor to a free area in the Plant Display Hierarchy
View, then release the left mouse button.

The Tank Display Plant Display will appear in the Plant Display Hierarchy.

When complete, close the Plant Display Hierarchy View.

1.5.3.2 Creating Free Graphics

Free Graphics are the static elements in Plant Displays. Free Graphics are used to create schematic representations
of the plant, in this way the operator can easily understand the location and function of drives or measurements that
are displayed in the pictures.

For the implementation example the Free Graphics to be created consist of the tank and its associated pipe work. To
create the Free Graphics proceed as follows:

1. Open the Tank Display Plant Display in the Diagram Editor.

2. Draw the tank:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 31 of 313
LKZ:DE AL:N ECCN:4E992

1. In the Diagram Editor toolbar, click on the Rectangle icon.

2. Move the cursor over the diagram, the cursor appears as a cross.

3. Draw a tank similar to the example in the picture below. Press and hold the left mouse button to
establish a tank corner, then drag the cursor to the opposite corner of the tank, then release the
mouse button.

3. Draw the pipe work:

1. In the Diagram Editor toolbar, click on the Polyline icon.

2. Click once at the starting point of the line, then move the cursor. The line will move with it.

3. Click once on the corner for the line, then double click on the end point. The line will be drawn.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 32 of 313
LKZ:DE AL:N ECCN:4E992

4. Click on the Arrow Polyline icon.

5. Draw the pipe at the tank discharge.

The complete Free Graphic picture is now created.

More elaborate and colorful graphics are easily created, for the purpose of Getting Started a simple example
has been used here.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 33 of 313
LKZ:DE AL:N ECCN:4E992

1.5.3.3 Creating Dynamic Elements

Dynamic elements are used in Plant Displays to provide the operator with live plant information (e.g. motor running
status, temperatures), and to allow the operator to control the plant (e.g. start or stop drives).

Dynamic elements placed in Plant Displays are called Pictograms. Pictograms are contained in their own library. Once
a Pictogram is placed, a process connection must be made to the corresponding AF Block (in a Function Diagram).

For the implementation example, dynamic elements must be placed and connected for:

• The pump
• The tank level indication

Creating the Pump

Placing the Pictogram

The Tank Example Plant Display is open in the Diagram Editor.

Before placing Pictograms for the implementation example, ensure integrated engineering is switched off.

To switch integrated engineering off:

In the Diagram Editor, select Edit then Integrated Engineering from the drop down menu. Integrated
engineering is off when the menu item is unticked.

1. Find the MOTOR_SYM5 Pictogram in the Prototype library. The path to the Pictogram is: Library > Prototypes >
Drives.

2. Place the Pictogram centrally on the line.

Setting the Process Connection

The Pictogram must now be connected to the AF Block for the pump.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 34 of 313
LKZ:DE AL:N ECCN:4E992

1. In the Tank Display Plant Display: Double click on the pump Pictogram, the parameter mask for the
Pictogram will appear.

2. The AF Block to which the process connection is to be made is found using the tag browser.
1. Click on the browse button to the right hand side of the Tag- Name field.

2. The tag browser appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 35 of 313
LKZ:DE AL:N ECCN:4E992

3. Select the Tank Example node by clicking on it.

4. Click on the Start Search button. The tag browser will now search for Automation Functions of the
type MOTOR in the node selected.
5. The results of the search are displayed at the bottom of the tag browser window. The single item in
the list corresponds to the pump in the implementation example.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 36 of 313
LKZ:DE AL:N ECCN:4E992

6. Select the item in the list by clicking on it.

7. Click on Ok.

The combination of Tag Name and Tag Item is unique for every AF Block, therefore the Tag Name
and Tag Item below are an example only.

3. The process connection to the AF Block will now be made. The Tag Name and Tag Item of the AF Block will
appear automatically in the Pictogram parameter mask.

4. Click on Save to save the process connection, otherwise click on Cancel.

Creating the Level Indication

The tank level indication is created in the same way as the pump.

Place the Pictogram for the tank level indicator and make the process connection, as in the picture.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 37 of 313
LKZ:DE AL:N ECCN:4E992

• The Pictogram is ASMON_SYM2 (the path is: Library > Prototypes > Monitoring).
• Connect the Pictogram to the ASMON AF Block in the Tank Logic Function Diagram.

1.6 Actualizing Changes

Once the user has made engineering changes (to Function Diagrams or Plant Displays) these changes must be
actualized in the system. The process of actualizing the changes is called Transaction Handling.

Transaction Handling is different for Function Diagrams and Plant Displays:

• For Function Diagrams, logic that has been changed will start actively running in the system. Symbols in
Function Diagrams have a status indication to show which logic has been actualized.
• For Plant Displays, the changed pictures will become visible to operators in Operation Mode.

1.6.1 Transaction Handling

Transaction Handling involves committing and activating changes in order to actualize the changes in the system. This
is handled differently for Function Diagrams and Plant Displays:

Transaction Handling for Function Diagrams

The process of making changes and performing transaction handling for Function Diagrams is as follows:

• The user makes changes in a Function Diagram (using the Diagram Editor). These changes are reflected in
the Project Container.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 38 of 313
LKZ:DE AL:N ECCN:4E992

• The user commits the changes. This saves the changed configuration in the Project Container.
• The user activates the changes. This starts the execution of the new logic in the Runtime Container.
•

• The user makes the changes permanent by committing the activation.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 39 of 313
LKZ:DE AL:N ECCN:4E992

Transaction Handling for Plant Displays

When committing changed Plant Displays they are saved to the Project Container. Activating changes makes the
changed pictures available in the Operation Mode.

Actualizing the Changes for the Implementation Example

Activating changes makes them immediately effective, there is no waiting time for a transfer of code.

To actualize the changes for the implementation example proceed as follows:

1. Open the Project View and select the Tank Example Project Node in the Tree View.
2. Commit the Function Diagrams and Plant Displays
1. Select the Edit menu, then Commit from the drop down menu.
2. A dialog will appear listing all diagrams to be committed. Click on Commit
3. A dialog box will appear to confirm that the Diagrams have been committed successfully.
3. Activate
1. Select the Tank Example Project Node in the Tree View.
2. Select the Edit menu, then Activate from the drop down menu.
3. A dialog box appears to confirm the Project Node selected. Click on Activate.
4. All committed changes made to Plant Displays and Function Diagrams, made by all users in the
selected Project Node will be activated.
5. A dialog box will appear to confirm that the diagrams have been activated successfully.
4. Commit the Activation
1. Select the Edit menu, then Commit Last Activation/Deactivation from the drop down menu.
2. A dialog box will appear to confirm that the activated diagrams have been committed successfully.

The complete implementation example (Function Diagrams and Plant Display) will now be actualized in the system.

1.6.2 Status Indication

Color is used in Function Diagrams to indicate the status of the symbols. The user can see at a glance which logic is
active and running in the Runtime Container, or which logic is being added or deleted.

The colors used for the status indication can be modified to suit user preference.

Active Symbols

Active symbols are represented with blue border and font.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 40 of 313
LKZ:DE AL:N ECCN:4E992

New Symbols

New symbols which are added to the logic (e.g. new AF Blocks, new connections), and are not yet activated are
represented with black border and font.

Deleted Symbols

Active symbols which have been deleted are represented with a light gray color.

After the changes are activated these deleted symbols disappear.

1.7 Operation Mode

Once the diagrams configured for the implementation example have been actualized they can be viewed in Operation
Mode. In Operation Mode the plant is operated and monitored.

In this section the engineering user is familiarized with the basics of Operation Mode, and shown how to start
Operation Mode and how to operate with Plant Displays. The user is then shown how to force a signal.

Starting Operation Mode

Before starting Operation Mode the user may wish to close the Project View and the Diagram Editor. It may be
confusing when a lot of windows are open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 41 of 313
LKZ:DE AL:N ECCN:4E992

The Workbench is open, click on Mode on the menu bar and then click on Operation Mode in the drop down menu.

The Operation Mode will now start. The Plant Display Hierarchy button and the Common Alarm Indicators will appear
in the menu bar.

An example of a Workbench in Operation Mode is shown here.

For displaying the Plant Display Hierarchy click on the Plant Display Hierarchy icon. The contents of the Plant Display
Hierarchy are different for different projects.

1.7.1 Operating with Plant Displays

The operator operates and monitors the plant with the Plant Displays in Operation Mode. Using the Plant Display
previously configured in the implementation example it is shown how to open the Plant Display and arrange the view,
and how to interpret the elements in the diagram. Then the Faceplates are explained.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 42 of 313
LKZ:DE AL:N ECCN:4E992

How to Open a Plant Display

The Workbench must be in Operation Mode and the Plant Display Hierarchy must be open.

1. In the Plant Display Hierarchy double click on the Tank Display Plant Display.

2. The Tank Display Plant Display will now open in the Workbench (in Operation Mode).

What is in the Plant Display?

The Plant Display shows the picture configured for the implementation example, both the Free Graphics and the
dynamic elements.

The dynamic elements now give the actual status of the plant i.e. the tank level is zero and the pump is off.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 43 of 313
LKZ:DE AL:N ECCN:4E992

How to Open Faceplates

Faceplates can be opened for each Pictogram in the Plant Display. The Faceplate makes a number of functions
available for the dynamic element e.g. starting and stopping pumps.

To open the Faceplate for the pump in the Tank Display proceed as follows:

1. Select the pump Pictogram by clicking on it.

2. Click the right mouse button to open the context menu, select Open Faceplate .

3. The Faceplate for the pump will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 44 of 313
LKZ:DE AL:N ECCN:4E992

The Faceplate consists of a toolbar to access further views (e.g. curves or diagnostics) for the pump, and all functions
necessary to control the pump (e.g. starting or stopping).

1.7.2 Forcing Signals

A function is available to force signals. By using this function the actual value of a signal can be overridden and
replaced by a substitution value set by the user.

The implementation example is used to show how to force a signal via a Dynamic Function Diagram.

Care must be taken when using the forcing signals feature. There may be safety implications e.g. a drive
interlock may be overridden, or some other undesired effect on the control system may take place. Plant
safety protocols must be followed when applying the forcing features.

How to Open a Dynamic Function Diagram

A Dynamic Function Diagram provides a view of a Function Diagram in Operation Mode. All signal values in the
diagram are dynamically displayed. Signals are also forced in Dynamic Function Diagrams.

Proceed as follows:

The Tank Display Plant Display is open in the Workbench in Operation Mode.

1. Open the Faceplate for the tank level indicator (make sure the indicator is selected, and not the tank).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 45 of 313
LKZ:DE AL:N ECCN:4E992

2. In the toolbar of the Faceplate click on the Open Function Diagram icon.

The Dynamic Function Diagram for the Tank Logic Function Diagram will now open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 46 of 313
LKZ:DE AL:N ECCN:4E992

The Dynamic Function Diagram contains all the elements in the Function Diagram. The current signal states are
indicated in the small yellow boxes in the diagram.

How to Force a Signal

1. If not already selected, select the ASMON AF Block by clicking on it (Handles will appear on the symbol).

2. Open the context menu with a right mouse click anywhere in the diagram, then click on Force Ports .
3. A dialog box appears containing all Ports of the ASMON AF Block which can be forced.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 47 of 313
LKZ:DE AL:N ECCN:4E992

4. To force the tank level signal, click on the check box of the IN PORT in the Force column. A tick appears in
the check box. Enter a Force Value of 50.

5. Click on Save. The tank level signal will be forced to 50%.

The forced value of 50% for the tank level can now be seen in the Dynamic Function Diagram, the Faceplate and in
the Plant Display.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 48 of 313
LKZ:DE AL:N ECCN:4E992

1.8 Deleting the Example

The implementation example can be deleted from the project. The project will then be returned to its original state.

To avoid confusion, the user may wish to stop Operation Mode before deleting the implementation example.

To delete the implementation example, proceed as follows:

1. Open the Project View.

2. Select the Tank Example Project Node in the Tree View.

Before deleting the Function Diagrams all logic and symbols contained in them must first be
deactivated.

3. Deactivate the Tank Logic and Tank Display diagrams as follows:

1. Select the Edit menu, then Deactivate from the drop down menu.
2. A dialog box will appear to confirm the deactivation. Click on Deactivate.
3. A dialog box will appear to report on the deactivation, click on OK.
4. Select the Project menu, then Delete from the drop down menu.
5. A dialog box will appear to confirm the deletion. Click on Yes in the dialog box.

The Tank Example node and its contents will be deleted from the Project Hierarchy.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 49 of 313
LKZ:DE AL:N ECCN:4E992

2 Portal
The SPPA-T3000 Portal is the users entry point to the SPPA-T3000 system. The user has to access the Portal and
then login to the system.

The SPPA-T3000 system is running on a server. The user accesses the server by using a Web Browser on a Client
machine. The user has to enter the URL of the server in the Web Browser. This URL is available from the system
specialist.

There are three possibilities for running the SPPA-T3000 system on the Client machine. The system can run either as:

• An Applet: Running in a Web Browser (e.g. using Internet Explorer from Microsoft), OR
• An Application: Running in a similar way to a normal program on a computer, using Webstart from Sun
Microsystems.
• A Multi Unit : Running in a similar way to a normal program on a computer, using Webstart from Sun
Microsystems. This option provides the ability to attach to additional Application Servers in Multi Unit Plant.

The option for running the system may be chosen according to the users preference, or depend on the projects
specific software installation.

SPPA-T3000 users are allocated user names and passwords which are required to login to the system. Users are
assigned Roles as part of the Project Administration which defines the users access rights. Additionally the access
rights of the login session may be restricted if the Thin Client has limited Operator Working Place rights.

How to Login

To login as a Multi Unit read the description on how to login in a Multi Unit Plant.

To login as an applet or application proceed as follows:

The users Client Computer is up and running.

1. Start the Web Browser software on the computer.

2. Enter the URL for the SPPA-T3000 server in the address field of the browser.
3. The SPPA-T3000 Portal will appear, this contains the options for running the system.

Click on Login Project to open the Workbench as either:

o an applet
o an application
o a Multi Unit

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 50 of 313
LKZ:DE AL:N ECCN:4E992

During the first login of the Workbench as an applet or an application, the required files are
downloaded from the Application Server. It may take a couple of minutes for the Login dialog box to
appear. In addition the user will receive security warnings related to the installation of the system.

During the login as an application, the user may be given an option to have an SPPA-T3000 icon
installed on the desktop. For future logins the user can simply double click on this icon to login, and
need not access the SPPA-T3000 Portal.

4. When the Login dialog box appears, enter the User name and Password.

5. Click on Login.
6. The system will check if the User name and Password have been correctly entered.

After a set number of failed attempts, a system alarm is generated.

7. If the user has been assigned different roles, or if the user has previously saved workspaces, the Workspace
Selection dialog box will appear. The user can select which workspace the Workbench will start up in.

1. Select the workspace from the drop down list.

2. Click on OK to continue the logging in process, otherwise click on Cancel to return to the login
dialog box.
8. The user will be logged in to SPPA-T3000 and the Workbench will start up.

The Temporary Supervisor Login function is described separately.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 51 of 313
LKZ:DE AL:N ECCN:4E992

3 Workbench
The Workbench is the central or uppermost view in the SPPA-T3000 system, all other views are accessible from the
Workbench. The SPPA-T3000 views cater to the different needs of users, e.g., engineers, operators, maintenance
staff. The SPPA-T3000 Workbench is used to view the plant status, to perform the operation and monitoring functions
for operation, and also to perform engineering or diagnostic tasks in SPPA-T3000. The views are opened as windows
in the Workbench Work Area.

The following views can be opened from the Workbench:

• Project View: This is the main view for engineering. The complete project structure is available here, as well
as all the project data.
The Diagram Editor is opened via the Project View and is used to configure all application software and logic,
as well as the Plant Displays used to operate the plant. The Runtime Container is configured and the user
can implement configuration changes in the running system. Project administration is also done in the Project
View.
• Function Diagram in Operation Mode: In this view Dynamic Function Diagrams contain live data indicating
current IO port values, e.g., feedbacks and release states.
• Trend: Trend displays are used to display archived or live values of process data in the form of a line chart.
• Plant Display in Operation Mode: In this view Plant Displays represent the plant at various levels of
abstraction in the form of dynamic objects.
• Reports: Used to extract and view historical process information from the archive.
• Diagnostic View: Displays system information and is used for fault analysis.
• Plant Display Hierarchy View: The structure that the operator uses to navigate between Plant Displays is
defined here.
• Alarm Sequence Display: All Alarms are displayed and organized in the ASD.
• Prototype Editor: Used to create and edit user-defined Pictograms and Faceplates.

Via the function Mode the Workbench can be switched between Configuration and Operation Mode . During
Operation Mode the plant is controlled and monitored and the Configuration Mode is for engineering of Plant
Displays, Function Diagrams, Trend Displays, Reports, etc.

3.1 General Layout

The Workbench has the following structure:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 52 of 313
LKZ:DE AL:N ECCN:4E992

• A menu bar with the following drop down menus:

o Applications: From which the Project View, the Plant Display Hierarchy View, the Diagnostic View,
the Lifetime Calculation, the TDY, the Alarm Sequence Displays and the Prototype Editor are
started. The user can also obtain Reports, Login as Temporary Supervisor, or exit from SPPA-T3000
here.
o Favorites: To easily access the users own choice of diagrams.
o View: To configure the toolbars, save the layout, print, or make block information available in
Dynamic Function Diagrams.
o Window: To arrange the Frames within the Work Area.
o Extras: To find diagrams or tags in the Project Hierarchy, tag usages, or notes.
o Mode: To select the Workbench Mode.
o Help
• Toolbars that can be configured by the user in the View menu.
• A Work Area in which the other SPPA-T3000 views are opened. Windows can be docked on the borders of
the Work Area.
• A status bar (at the bottom of the window) indicating:
o The current user.
o The Workbench Mode.
o The Engineering Mode (if the Diagram Editor is open).

3.1.1 Favorites
The favorites function of the Workbench is provided so that users can quickly and easily access their own choice of
diagrams. Each user can create and maintain their own favorite diagrams by:

• Adding favorites
• Managing favorites

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 53 of 313
LKZ:DE AL:N ECCN:4E992

How to Open a Favorite Diagram

Favorite diagrams (Plant Displays or Function Diagrams) can be opened with a single click as follows:

The Workbench is open.

1. Select the Favorites menu.

2. A drop down menu appears containing:
o The menu items for adding and managing favorites.
o The favorite diagrams, these may also be arranged in folders.

3. To open any diagram from the favorites, simply click on it.

The diagram will be opened in either configuration mode or operation mode corresponding to the current
Workbench mode.

3.1.1.1 Adding Favorites

New diagrams can be added to the favorites, also to subordinate favorite folders. New folders can also be created.

To add a new diagram (Plant Display or Function Diagram) to the favorites proceed as follows:

The Workbench is open, and the Project View is open.

1. Select any diagram in the List View of the Project View.

2. Select the Favorites menu, then Add to Favorites from the drop down menu.
3. The Add Favorites dialog box appears, the selected diagram is shown.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 54 of 313
LKZ:DE AL:N ECCN:4E992

4. To add the diagram to the Favorites click on Add, otherwise click on Cancel.

How to Add the Diagram to a Subordinate Folder

The Add Favorites dialog box is open.

1. Click on Add to, the dialog box will be extended.

2. Select the folder to which the diagram is to be added by clicking on it.

3. Click on Add, otherwise click on Cancel.

How to Create a New Folder

The Add Favorites dialog box is open.

1. Click on Add to, the dialog box will be extended.

2. Select the parent folder of the new folder to be created, by clicking on it.
3. Click on New Folder.
4. The Create New Folder dialog box appears.
5. Enter the name of the new folder, then click on Add, otherwise click on Cancel.

The new folder will be created in the favorites, new diagrams can now be added to this folder as described above.

3.1.1.2 Managing Favorites

Functions are available to manage the favorites. Existing diagrams and folders can be deleted, new folders created
and folders can be renamed. The structure of the favorites can also be changed by moving folders and diagrams.

To manage the favorites proceed as follows:

1. Select the Favorites menu, then Manage Favorites from the drop down menu.
2. The Manage Favorites dialog box appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 55 of 313
LKZ:DE AL:N ECCN:4E992

How to Delete Diagrams or Folders

The Manage Favorites dialog box is open.

1. Select the diagram or folder by clicking on it.

2. Click on Delete.
3. Click on Save to delete the diagram or folder, otherwise click on Cancel.

If a folder is deleted, the contents of the folder will also be deleted.

If a User Specific Plant Display is deleted, the Plant Display will not be retrievable.

How to Create New Folders

The Manage Favorites dialog box is open.

1. Select the parent folder of the new folder to be created.

2. Click on New Folder.
3. The Create New Folder dialog box appears.
4. Enter the name of the new folder, then click on Add, otherwise click on Cancel.
5. Click on Save to create the folder, otherwise click on Cancel.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 56 of 313
LKZ:DE AL:N ECCN:4E992

How to Rename Folders

The Manage Favorites dialog box is open.

1. Select the folder to be renamed.

2. Click on Rename.
3. A cursor appears at the selected folder.
4. Edit the folder name as required.
5. Press Enter.
6. Click on Save to rename the folder, otherwise click on Cancel.

How to Move Folders and Diagrams

Folders and diagrams can be moved in the favorites structure using a drag and drop method.

The Manage Favorites dialog box is open.

1. Move the cursor over the folder or diagram.

2. Press and hold the left mouse button. The item will be selected.
3. Holding the left mouse button, drag the item towards the new position. Below the cursor, a small rectangle
appears indicating that the item is being dragged.

4. Position the cursor over the new folder, and release the left mouse button. The item will be moved in the
dialog box.
5. Click on Save to move the folder or diagram, otherwise click on Cancel.

If a folder is moved, the contents of the folder will be moved with it.

3.1.2 View
The View drop down menu has the following menu items:

• Zoom Functions: any diagram open in Operation Mode can be zoomed with the following functions (as
described for diagrams in the Diagram Editor):
o Fit to View
o Zoom by 200%
o Zoom by 50%
o Zoom to Original size
o Pan and Zoom
• Save and Delete Workspace
• Printing Functions: The user has the option to Print Screen or Print Window.
• Toolbars: Allows the user to select which toolbars are visible in the Workbench, and to customize them.
• Block Information Menu Items: The same block information options are available for AF Block and
Connector symbol information for Dynamic Function Diagrams as described in AF Block Information and
Connector Information for diagrams open in configuration mode in the Diagram Editor. The function for
viewing process values at all output Ports is included here.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 57 of 313
LKZ:DE AL:N ECCN:4E992

• The block information menu items are visible when a diagram is open in Operation Mode.

Selecting Toolbars

The Workbench has two toolbars available:

• Default Toolbar: This is the upper toolbar with icons. The icons are shortcuts to menu items and can be
customized by the user.
• Windows Toolbar: This is the lower toolbar which has a button for each open view in the Work Area. Clicking
the button for a view, selects the view and makes it visible.

To make a toolbar visible in the view select it as follows:

The Workbench is open.

1. Select the View menu, then Toolbars from the drop down menu.
2. A further drop down menu appears, the two toolbars are listed in the menu.
3. To select or deselect a menu, click on it in the drop down menu. When a toolbar is selected it has a tick next
to it in the menu.

3.1.2.1 Saving and Deleting the Workspace

Saving and deleting the workspace controls the default layout and content of the Workbench that appears when the
user logs in.

When the workspace has been saved, the next time the user logs in, the Workbench will open again with exactly the
same views open, with all windows and Frames the same size. If the workspace is saved with the Workbench in
Operation Mode, then any diagrams open in Operation Mode will also be saved (i.e. the next time the user logs in, the
diagrams will open again). All other user defined components (e.g. user specific ASDs) and customizations will also be
available.

A user can save as many workspaces as desired, under different names. The user can choose which workspace is to
be used when logging in.

Saving the Workspace

To save the current workspace of the logged in user, proceed as follows:

The Workbench is open.

1. Select the View menu, then Save Workspace from the drop down menu.
2. The Save Workspace dialog box appears.

3. A workspace name can be selected from the Select Profile drop down list.
OR A new workspace name can be entered. The new workspace will be added to the list.
4. Click on Save to save the workspace, otherwise click on Cancel.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 58 of 313
LKZ:DE AL:N ECCN:4E992

Deleting the Workspace

To delete a saved workspace, proceed as follows:

The current workspace (that was chosen at login) cannot be deleted. If this workspace is selected for deletion,
only the settings will be deleted, i.e. an empty Workbench will open when the user logs in with this workspace
again.

The Workbench is open.

1. Select the View menu, then Delete Workspace from the drop down menu.
2. The Delete Workspace dialog box appears.

3. Select the workspace name from the Select Profile drop down list.
4. Click on Delete to delete the workspace , otherwise click on Cancel.
5. A dialog box will for confirmation of the deletion. There are 2 possibilities:
o If it is the current workspace, only the settings can be deleted. Click on Yes to delete the workspace
settings, otherwise click on No.
o If it is not the current workspace, click on Yes to delete the workspace, otherwise click on No.

3.1.3 Window
The items in the Window drop down menu are used to arrange the windows in the Workbench Work Area.

• Define Screen Grid: The screen position for open Faceplates can be assigned (an operators function).
• Arrange Opens a dialog box to select the layout of the open windows. In a multi screen arrangement the user
can select which screen will be arranged. The options available are:
o Tile: divides the Work Area horizontally and vertically.
o Tile Vertically: divides the Work Area vertically.
o Tile Horizontally: divides the Work Area horizontally.
o Cascade: Arranges the windows by overlapping them.
• Maximize to, and Restore from all Screens, and Move Window: Are used for a multi screen arrangement.
The Screen Selection will then also be displayed at the bottom of the menu.
• Open Windows: The open windows are listed. Selecting a window from the list selects the window and
moves it to the top of any other open windows in the Work Area.
• Operation View Windows: The following functions apply to any diagram that is open in the Operation Mode:
o Close All Dynamic Diagrams: All diagrams open in the Operation Mode will be closed.
o Close All Faceplates: All open Faceplates will be closed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 59 of 313
LKZ:DE AL:N ECCN:4E992

3.1.4 Dockable Windows

A dockable window is a window that attaches itself to the Work Area border. Other windows cannot be dragged over
the docked window.

Examples of dockable windows are the Project View, or the Plant Display Hierarchy View.

How to Dock and Undock a Dockable Window :

1. Move the cursor over the window title bar, then press and hold down the left mouse button. Move the window
(by dragging it) towards the Work Area border against which the window is to be docked.

2. When the window is moved close enough to the Work Area border it will disappear and a line will indicate the
eventual border of the docked window.
3. Release the left mouse button, the window will appear, docked against the Work Area border.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 60 of 313
LKZ:DE AL:N ECCN:4E992

Other windows in the same Work Area cannot be dragged over the docked window.

To undock a docked window, click on the title bar and drag the window away from the Work Area border.

3.1.5 Customizing Toolbars

Some toolbars can be customized by the user. In this way any menu item from a particular view can be represented as
an icon on the toolbar of the view.

To customize a toolbar proceed as follows:

The view containing the toolbar is open.

1. Select the View menu, then Toolbars, then Customize from the drop down menus.
2. The Customize Toolbar dialog box appears.
3. The Frame on the right hand side of the dialog box shows which menu items have been selected for the
toolbar. To delete items from the tool bar, click on the item in the right hand Frame, then click on the Delete
button.
4. The Frame on the left hand side of the dialog box shows the menu items that can be included in the toolbar.
The menu items are arranged in folders. To open a folder double click on it and the menu items contained
within it will appear. To add items to the toolbar, click on the item in the left hand Frame, then click on the
Add button.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 61 of 313
LKZ:DE AL:N ECCN:4E992

5. The items in the right hand Frame are displayed in the same sequence upright as they are displayed in the
horizontal Toolbar.
1. To arrange the added icons select one by clicking on it with the mouse.
2. Press the right mouse button.
3. Arrows for moving this item up or down will appear and also one button to delete this icon.
4. Click on the desired button.
5. Repeat this procedure until every icon is in the right place.
6. To confirm any changes which are made, click on Save, otherwise to ignore any changes click on Cancel.

3.1.6 Printing from the Workbench

There are two print functions available from the Workbench, Print Screen and Print Window. Print Screen prints the
entire on-screen image. Print Window prints only a selected window.

Print Screen

To print the entire on-screen image proceed as follows:

The Workbench is open.

1. Select the View menu.

2. From the drop down menu select Print Screen.

In a multi screen configuration select one screen and press on the F12

key.

3. If the Workbench Setting, Print screenshot with print dialog, has not been set a dialog box will appear.
Initiate the print from this dialog box.

The entire on-screen image will be printed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 62 of 313
LKZ:DE AL:N ECCN:4E992

Print Window

The performance of the Workbench may deteriorate momentarily during printing.

To print a single frame in the Workbench proceed as follows:

The Workbench is open.

1. Click on the window within the Workbench that is to be printed.

2. Select the Workbench View menu.
3. From the drop down menu select Print Window.
4. If the Workbench Setting, Print screenshot without print dialog, has not been set a dialog box will appear.
Initiate the print from this dialog box.

Print Window can only print windows opened from the workbench. (For example, the Reference List,
opened from the Diagram Editor, cannot be printed individually with Print Window.)

The image of the selected window will be printed.

The dialog box that opens, after selecting Print Screen or Print Window, is specific to the printer type and the
driver software.

3.1.7 Keyboard Shortcuts

There are several keyboard shortcuts available in the Workbench. The user must be aware of these shortcuts to:

• Improve usability of SPPA-T3000

• Avoid unwanted actions.

Shortcuts with ALT and CTRL

The menus can be accessed via the keyboard using the ALT key. Without pressing any key, the menus appear as
follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 63 of 313
LKZ:DE AL:N ECCN:4E992

When the ALT key is held down, one letter in each menu item is underlined:

To open a specific menu, continue holding down the ALT key and press the corresponding underlined letter on the
keyboard.

The action of pressing and releasing the ALT key before selecting a menu item is not defined.

The CTRL key is used in combination with a letter key to select a menu item. For example, in the Workbench, hold
down the CTRL key and press J to open the Project View :

Using the Esc Key

The behavior of the Esc key is to close a window or dialog box without saving the changes. If some changes have
already been applied (via Apply button), the Esc key closes the window without saving the unapplied changes only.

Using the Space Bar

The Space bar performs the same function as clicking on the button currently with focus. Focus means that the button
is selected (shown as dotted box around text, e.g. No):

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 64 of 313
LKZ:DE AL:N ECCN:4E992

3.2 Workbench Mode

The Workbench is an extremely flexible interface. Operation and engineering activities can both be carried out
simultaneously in the same Workbench. The application of the Workbench is set using the Workbench mode.

The Workbench can be selected in one of two modes:

• Operation Mode: For operating and monitoring the plant. In Operation Mode engineering activities can also
be carried out by users with the appropriate user rights.
• Configuration Mode: For engineering activities. Essentially this means that the Operation Mode is switched
off.

How to Select the Workbench Mode

The Workbench must be open.

• Select the Mode menu, then Operation Mode from the drop down menu.

The Workbench mode will now toggle to either Operation Mode or Configuration Mode.

When the Operation Mode is active the Operation Mode menu item is ticked.

3.3 Exiting the Workbench

Exiting the Workbench also involves logging out of, and ending the SPPA-T3000 session.

If the user has any uncommitted diagrams at the time of logging out, a dialog box appears giving details of the
diagrams and the option to commit them. It is good practice to commit the diagrams, because:

• Other users will not be able to activate the uncommitted diagrams (see Multi User Operation).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 65 of 313
LKZ:DE AL:N ECCN:4E992

• If the server is shut down, the uncommitted changes will be lost.

To Exit from the Workbench proceed as follows:

The Workbench is open, other views may also be open in the Workbench.

1. Select the Applications menu, then Exit from the drop down menu.
2. If uncommitted diagrams exist for the user, a dialog box will appear giving details of the uncommitted
diagrams.

The contents of the dialog box can be saved or printed.

3. To commit the diagrams click on Commit All, otherwise to ignore the function click on Close.
4. A dialog box will appear to confirm the exit from the Workbench. Click on Yes to exit the Workbench,
otherwise click on No.

The standard window close button can also be used to exit the Workbench. But if the Workbench was opened
as an applet, the user will immediately exit the Workbench without seeing any confirmation dialogs.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 66 of 313
LKZ:DE AL:N ECCN:4E992

4 Project View
Good process engineering is a priority for both the plant designer and plant operator. Therefore, a plant must be
technologically structured with the project view and displayed similarly to that of Windows Explorer.

The Project View is the main user interface for Engineering tasks. This includes the configuration and execution of the
engineering data, and the control of user access and the user interface appearance.

The description of the Project View covers:

• Starting the view and the general layout of the View.

• Multi User Operation, where many users can perform engineering tasks on the same project simultaneously.
• Constructing and manipulating the Project Hierarchy nodes, as well as providing functions to control the
appearance of the user interface. These are described in project functions.
• Functions needed to control the way automation tasks are carried out in Runtime Containers.
• Creating and manipulating Function Diagrams and Plant Displays that use diagram functions. The
engineering data is configured in these diagrams.
• Actualizing engineering changes in the system that use the transaction handling functions.
• Drawing project documentation from the system.
• Importing and Exporting data.
• Controlling user access and performing higher level project controls with the project administration functions.

4.1 Starting the View

How to start the Project View:

The user must be logged in and the Workbench must be open.

• Select the Applications menu from the Workbench menu bar, then Project View from the drop down menu.

The Project View will open in the Workbench.

4.2 General Layout

The Project View has the following structure:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 67 of 313
LKZ:DE AL:N ECCN:4E992

• A menu bar with the following drop down menus:

o Project
o Edit
o View
o Versioning
o Extras
o Admin
o Help
• A Toolbar.
• Several context menus are available.
• The Project View consists of two Frames:
o The Tree View in the left hand Frame, containing the Project Nodes in the Project Hierarchy.
o The List View in the right hand Frame, containing the contents of the Project Node selected in the
Tree View. The appearance of the List View contents can be changed by the user.

The technique for selecting items in the Project View is shown, and also the way Project Nodes and diagrams can be
moved in the Project Hierarchy by Drag and Dropping.

4.2.1 Tree View

The Tree View is displayed in the left hand Frame of the Project View. The Tree View shows the arrangement of
Nodes in the Project Hierarchy. The Project Hierarchy contains both Project Nodes and Library Nodes.

Contents of the Tree View

Library Nodes:

This type of Node contains the functions and elements used to configure the project.

Library Nodes may contain the following:

• Other Library Nodes

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 68 of 313
LKZ:DE AL:N ECCN:4E992

• Automation Functions: configured Automation Functions are provided with the system software.
• Hardware Proxies: configured Hardware Proxies are provided with the system software.
• Macros: Macros are freely designed by the user.
• Prototype Nodes: a set of configured Prototypes is provided with the system software. New Prototypes
created by the user can also be added to this set.

Prototype Nodes:

This type of Node contains Prototypes. Prototypes are the dynamic elements used to configure Plant Displays.

Prototype Nodes may contain the following:

• Other Prototype Nodes

• Prototypes

Project Nodes:

This type of Node contains all the diagrams that are configured for the project.

Project Nodes may contain the following:

• Other Project Nodes

• Function Diagrams
• Plant Displays
• User Defined Reports
• Point Group Definitions

Function Diagrams:

Function Diagrams that contain Embedded Macro Logic are displayed in the Tree View.

Tree Structure and Navigation

The Project Nodes are linked together in a tree or hierarchy. There is an uppermost or root Node in each project. All
Nodes and diagrams are contained within this root Node. Nodes which are higher in the hierarchy are called
superordinate Nodes. Nodes lower in the hierarchy are called subordinate Nodes.

Nodes that contain other Nodes have a special representation in the Tree View. Where the subordinate Node
branches off, there is a small square with a + or - sign in it.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 69 of 313
LKZ:DE AL:N ECCN:4E992

To display the sub Nodes within a Node click on the + square. To hide the sub Nodes click on the - square.

A function is also provided to Navigate Up the Project Hierarchy in the Tree View.

The Project Hierarchy

The Project Hierarchy is built by creating Project Nodes in the hierarchy. It is also possible to drag and drop a Project
Node from one place in the hierarchy to another. The Project Nodes can be named after creation, or deleted if
required.

Careful thought should be given to the design of the Project Hierarchy, because the organization of the project is
dependent on it. A popular method is to divide the plant into plant areas and assign Project Nodes for each. Each plant
area can then be divided up further and sub Nodes assigned accordingly.

With a well designed Project Hierarchy it should be easy to understand the project organization and also to navigate
through the hierarchy to find items.

4.2.1.1 Navigate Up
A function is provided to navigate up to the immediate superordinate Node in the Project Hierarchy. To navigate up the
Project Hierarchy in the Tree View proceed as follows:

The Project View is open.

1. Select a Project Node in the Tree View.

2. Select the Edit menu, then Navigate Up from the drop down menu.

The Project Node that is immediately superordinate becomes selected, and its contents appear in the List View.

4.2.2 List View

The List View is diplayed in the right hand window of the Project View. The List View shows:

• the contents of a node selected in the Tree View. This content may include Project Nodes, Function
Diagrams, Plant Displays, Automation Functions, User Defined Reports, Point Group definitions, or may be
empty.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 70 of 313
LKZ:DE AL:N ECCN:4E992

• the Macros contained in a Function Diagram selected in the Tree View.

The appearance of the List View can be selected by the user.

4.2.3 Toolbar
The Project View has one toolbar available, called the Default Toolbar. This toolbar can be customized by the user.

To make the Default Toolbar visible in the view select it as follows:

The Project View is open.

1. Select the View menu, then Toolbars from the drop down menu.
2. A further drop down menu appears with the Default Toolbar in the menu.
3. To select or deselect the toolbar, click on it in the drop down menu. When the toolbar is selected it has a tick
next to it in the menu.

4.2.4 Context Menus

The Project View has several context menus. The menu options available in the context menu depend on which item
has been selected in the Project View.

To open the context menu click the right mouse button after the selection has been made.

There are context menus for the following selections:

• A Project Node.
• A Library Node.
• A Function Diagram.
• A Plant Display.
• A Report Definition.
• A Point Group.
• A Macro in a Library Node.
• An AF or a Proxy in a Library Node.
• In the List View with nothing selected.
• In the List View with multiple items selected.

Should the users access rights prohibit operation of any of the menu items, the menu items will be grayed out.

4.2.5 Drag and Drop

Project Nodes or diagrams can be moved in the Project Hierarchy with the drag and drop method. For example, a
Function Diagram may have been created in the wrong Project Node; to move it to the correct Project Node the user
can simply drag and drop it there in the Project View.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 71 of 313
LKZ:DE AL:N ECCN:4E992

When a Project Node is moved by the drag and drop method, the complete contents of the Project Node are
moved with it.

How to Drag and Drop

The Project View is open.

1. Select the item (Project Node, Function Diagram, Plant Display, Report Definition or Point Group) to be
moved by positioning the cursor over it and pressing and holding the Left Mouse button on the item. The item
can be selected from either the Tree View or List View.

Multiple item selection is possible in the List View.

2. Holding the Left Mouse button, drag the item towards the new Project Node. Below the cursor, a small
rectangle appears indicating that the item is being dragged.

3. Position the cursor over the new Project Node (in either the Tree View or List View) and release the Left
Mouse button.
4. A dialog box appears to confirm the move function.
5. To move the item click Yes, otherwise to cancel the function click on No.

The item will be moved to the new Project Node.

User Access Rights

When nodes or diagrams are moved there may be consequences to user access rights. Many access rights are node
(or plant area) specific, and some users may lose access rights to nodes or diagrams when they are moved. This may
require the adjustment of user rights for the nodes or diagrams in their new location.

In order to prevent the loss of user access to activated diagrams, only users assigned the access right
Define and change user rights can move activated diagrams in cases where users access rights
may be lost.

When moving these diagrams, the user is required to confirm the action before it is carried out.

4.2.6 List View Appearance

The List View appearance can be selected from the following options:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 72 of 313
LKZ:DE AL:N ECCN:4E992

• Large Symbols
•

• Small Symbols
•

• List
•

• Details
•

• The Attributes column can contain:

o S: Indicates a Sound Alarm Group.
o P: Indicates a Print Alarm Group.

When selected as List or Details the contents of the List View can be sorted in ascending or descending order
by clicking on the column title.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 73 of 313
LKZ:DE AL:N ECCN:4E992

To navigate down to a sub Node, double click on the Node in the List View.

Selecting the Appearance

The Project View is open.

1. Select the View menu, then either Large Symbols, Small Symbols, List or Details from the drop down
menu.

Alternatively, select the appearance via the context menu (Right Mouse Click in the List View, with no items
selected).

4.2.7 Saving the View

The Save View option controls the default layout that appears when the user starts the Project View.

The Project View is open.

Proceed as follows:

Select the View Menu, then Save View.

The List View appearance, toolbar settings, and the relative sizes of the Tree View and the List View, are
saved.

The next time the user logs in, the settings that were stored in the session before are available.

4.2.8 Selecting Items in the Project View

When working in the Project View it is often necessary to select items, this is described below:

Selecting in the Tree View

Only single items can be selected in the Tree View. To select an item (e.g. a Project Node) in the Tree View, simply
move the cursor over the item and click the left mouse button. The item acquires a dark blue background which
indicate thats it is selected.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 74 of 313
LKZ:DE AL:N ECCN:4E992

To open up, or expand sub-hierarchies either:

• Click on the small plus symbol in front of the node symbol.

•

• Double Click on the node.

Selecting Items in the List View

To select a single item in the List View, simply move the cursor over the item and click the left mouse button.
Depending on the List View Appearance chosen, the item acquires the following representation:

• Small or Large Symbols: A light blue background.

•

• List or Details: A dark blue background.

•

Multiple items can be selected in the List View, either:

Select a single item, then pressing the CTRL key select more items. OR

Select a single item, then pressing the SHIFT key select another item. Both the items and all the items in
between them will be selected.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 75 of 313
LKZ:DE AL:N ECCN:4E992

Opening Items in the List View

Double click on any item in the List View to open it:

• Double Click on a Project Node to view its contents.

• Double Click on a diagram to open it in the Diagram Editor.

4.2.9 Open Containing Folder

This function provides a method for direct navigation into the Project View. The function is usually available for items in
a list of search results (e.g. from the Find Diagram function). The location in the Project hierarchy will automatically be
found for nodes and diagrams.

To navigate directly to the location of an item in the Project View, proceed as follows:

1. Select the item in the list, by clicking on it.

2. Click the right mouse button to open the context menu.
3. Select Open Containing Folder from the context menu.

The selected item will appear in the List View of the Project View.

The Project View will automatically open, if it is not open already.

4.2.10 Protocol Report Browser

Some of the functions in the Project View will generate a protocol report when they are carried out (e.g. when
importing or exporting Project Nodes and diagrams). These protocol reports are contained in files and normally contain
detailed information about the execution of a function.

In order to simplify the users access to the information, it is viewed using a protocol report browser. The protocol report
browser facilitates navigation through the information in the protocol report, and enables the user to find information
quickly and easily.

Using the Protocol Report Browser

The protocol report browser is divided into three Frames:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 76 of 313
LKZ:DE AL:N ECCN:4E992

• The list of diagrams: This contains a list of all the diagrams in the report.
• The list of modules: This contains a list of all the modules (e.g. AF Blocks, Proxies or Macros) in the report.
The diagram name precedes the modules contained in the diagram.
• The report: This contains all of the information messages contained in the report.

Information is accessed using the browser as follows:

• Click on any diagram in the list, and all the module list will scroll until the modules for that diagram appear.
• Click on any module in the list and the report will scroll until the messages for that module appear.
• Messages are classified as either Info, Warning or Error. Warning and error messages are identified by yellow
and red symbols respectively in the diagram and module lists.

4.2.11 Dialog Exporting

Many dialog boxes contain information that users may wish to save. These dialog boxes are provided with a function
for dialog exporting. When data has been exported from a dialog box, it can be viewed or edited with any appropriate
tool.

To save the contents of a dialog box, proceed as follows:

The dialog box is open.

1. Click on the Export button.

2. A dialog box will appear to choose the destination. The default directory is shown first.

The file will be saved in the selected format.

Possible Formats are:

• HTML

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 77 of 313
LKZ:DE AL:N ECCN:4E992

• CSV
• XLS

4.2.12 Dialog Printing

Many dialog boxes contain information that users may wish to print out. These dialog boxes are provided with a
function for dialog printing.

The performance of the Workbench may diminish momentarily during printing.

The entire contents of the dialog box will be printed out, with the same dimensions as on the screen. Should the
contents be too wide for the paper, the size will be automatically adjusted.

To print out the contents of a dialog box, proceed as follows:

The dialog box is open.

1. Click on the Print button.

2. A dialog box will appear to control and start the printing. This is specific to the system and printer being used.

The contents of the dialog box will be printed out.

The page size can be set via the printer page setup in the Print function in the Project View.

If an Adobe PDF printer is available on the users Thin Client then dialog diagrams can be printed to .pdf file.
Printing to *.pdf files requires several Adobe PDF Printer settings.

4.2.13 Illegal Characters

The names of items contained in the Project Hierarchy may not contain the following characters:

• double quotation marks (")

• single quotation mark (')
• forward slash (/)
• at symbol (@)

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 78 of 313
LKZ:DE AL:N ECCN:4E992

• section symbol (§)

• degree symbol (°)

The items in the Project Hierarchy for which these illegal characters apply include, but are not limited to, the following:

• Function Diagrams
• Plant Displays
• Macros
• Compound Components
• Report Definitions
• Point Groups
• Project Nodes
• Library Nodes
• Prototypes

If the user assigns a name with illegal characters to any of the aforementioned items, the illegal character is
automatically replaced with the underscore symbol (_). This correction will also automatically take place when items
are imported.

Illegal characters are also not permitted in tag names and tag items.

4.3 Multi User Operation

Many users can work in the Project View simultaneously. This multi user access is achieved by the following
measures:

View Updating

Whenever a user makes a change (e.g. creates a new Project Node) the views of all users are updated immediately.
This means that all users see the actual state of the Project View including all changes made by other users.

Committing and Activating Diagrams

Changes made by users are actualized in the system with the transaction handling concept. Multi user operation is
handled in the following way.

• When a user commits diagrams, the changes made by that user only are committed.
• When a user rolls back changes, only the changes made by that user will be rolled back.
• When a user activates diagrams, all changes made by all users in those diagrams must first be committed. All
these changes will then be activated.
• When Function Diagrams have been activated or deactivated, but the activation or deactivation has not yet
been committed, then engineering is locked, and no user may make any changes.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 79 of 313
LKZ:DE AL:N ECCN:4E992

In exceptional circumstances, a user with the appropriate access rights may Commit All or Rollback All
diagrams. With these functions all multi user access measures are overridden, and all diagrams are committed
or rolled back, regardless of which user made changes in the diagrams.

Opening Diagrams

The same diagram can be open in the Diagram Editor of many users simultaneously.

However making changes is subject to certain constraints. These are described in Multi User Operation for the
Diagram Editor.

Manual Diagram Scheduling

When the manual diagram scheduling is edited only one user at a time may make changes to the diagram scheduling
in a Runtime Container. No other users may edit the manual scheduling until the first users changes are committed.

When the manual diagram scheduling for a Runtime Container is activated, all committed changes by all users to the
scheduling will be activated.

4.4 Project Functions

The Project Functions in the Project View are arranged as follows:

• Working with Nodes : Creating Project Nodes or Creating Library Nodes, and Renaming or Deleting Nodes.
• Setting Colors and Styles: Customizing the Look and Feel or making the User Specific Settings.
• Setting the system diagram root: The system diagram root is set as part of the creation of the hierarchy for
the Diagnostic View.
• Project Version Management: Management of different versions of the engineered data for a project.
• Alarms : Configuring and allocating alarm sounds and alarm printers.

4.4.1 Create New Project Node

The Project Hierarchy is built up by creating new Project Nodes which are then placed into the hierarchy.

To create a new Project Node for inclusion in the Project Hierarchy proceed as follows:

The Project View is open.

1. Select a Project Node in the Tree View or List View. This Node will be the parent Node of the new Node that
is being created.
2. Select the Project menu, then New, then Project Node from the drop down menus.
3. A new Project Node is created as DefaultName, under the selected parent Node.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 80 of 313
LKZ:DE AL:N ECCN:4E992

4. To name the Project Node enter the name and press Enter.

Illegal characters are not permitted in the name.

Alternatively, select the function via the Context Menu (Right Mouse Click > Create New Project Node ).

To change the name of a Project Node, use the rename Project Node function.

4.4.2 Create New Library Node

The Library is contained in the Project Hierarchy and contains Library Nodes. Additional Library Nodes may be
required e.g. for Macro functions.

To create a new Library Node for inclusion in the Project Hierarchy proceed as follows:

The Project View is open.

1. Select a Library Node in the Tree View or List View. This Node will be the parent Node of the new Node that
is being created.
2. Select the Project menu, then New, then Library Node from the drop down menus.
3. A new Library Node is created as DefaultAutoLib, under the selected parent Node.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 81 of 313
LKZ:DE AL:N ECCN:4E992

4. To name the Library Node, use the rename Node function.

Alternatively, select the function via the Context Menu (Right Mouse Click > Create New Library Node ).

Illegal characters are not permitted in the name.

4.4.3 Rename Node

A Node is renamed in the Project View. This can be done in three ways:

• In the Tree View

• In the List View as a Symbol
• In the List View as a List

All three methods are described below:

All Nodes immediately subordinate to a parent Node must be uniquely named, or the name will not be
accepted by the system.

Rename from Tree View

The Project View is open.

1. Select the Node to be renamed in the Tree View.

2. Select the Project menu, then Rename from the drop down menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 82 of 313
LKZ:DE AL:N ECCN:4E992

3. A cursor will appear at the Node name.

4. Delete the name of the old Node and enter the new name, then press Enter.

The Node is renamed.

Alternatively select the function via the context menu (Right Mouse Click > Rename), or simply click on a
selected node in the Tree View.

Rename from List View as a Symbol

It is possible to select the List View Appearance. If Small Symbols or Large Symbols are selected a Node is
renamed as follows:

The Project View is open.

1. Select the Node to be renamed in the List View.

2. Select the Project menu, then Rename from the drop down menu.
3. A cursor appears at the node name.

4. Edit the name of the Node, then press Enter.

5. The Node is renamed.

Alternatively select the function via the context menu (Right Mouse Click > Rename), or simply click on a
selected node in the List View.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 83 of 313
LKZ:DE AL:N ECCN:4E992

Rename from List View as a List

It is possible to select the List View Appearance. If List or Details are selected a Node is renamed as follows:

The Project View is open.

1. Select the Node to be renamed in the List View.

2. Select the Project menu, then Rename from the drop down menu.
3. In the Name column the Node name can be edited directly

4. Change the name of the Node, then press Enter.

5. The Node is renamed.

Alternatively select the function via the context menu (Right Mouse Click > Rename), or simply click on a
selected node in the List View.

User Access Rights

When nodes are renamed there may be consequences to user access rights. Many access rights are node (or plant
area) specific, and some users may lose access rights to nodes or diagrams when superordinate nodes are renamed.
This may require the adjustment of user rights for the nodes or diagrams.

In order to prevent the loss of user access to activated diagrams, only users assigned the access right
Define and change user rights can rename nodes in cases where users access rights may be lost.

When renaming these nodes, the user is required to confirm the action before it is carried out.

4.4.4 Delete Node

The Project Hierarchy can be modified by removing a Project Node or Library Node from the hierarchy. When
removing a node the following points are important:

The entire contents of the Node will be simultaneously deleted.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 84 of 313
LKZ:DE AL:N ECCN:4E992

The user deleting the node may have no uncommitted changes in any Function Diagram.

It is possible that individual diagrams contained within the node cannot be deleted (for example, if they contain
uncommitted changes or are active). In these cases the diagrams will remain:

• The diagrams will not be deleted.

• The structure that contains these diagrams (i.e. the nodes) will not be deleted.

How to Delete a Node

To delete a Node from the Project Hierarchy proceed as follows.

The Project View is open.

1. Select the Node to be deleted in the Tree View or List View.

Multiple diagrams or nodes can be selected in the List View to delete them simultaneously.

2. Select the Project menu, then Delete from the drop down menu.
3. A dialog box appears to confirm the delete function.

Deleted nodes cannot be rolled back after they have been deleted.

4. To delete the Node click on Yes, otherwise to cancel the function click on No.

If confirmed, the Node (and its contents) will be deleted.

Alternatively, select the function with the Del key, or via the context menu (Right Mouse Click > Delete).

4.4.5 Project Settings

The appearance of the system is defined by the system settings. These settings or styles can be adjusted for the
project or be user specific.
It is recommended the user defines these settings early in the detailed engineering phase. Later revisions or changes
to existing drawings or layouts can then be avoided.

One of the first activities during the project setup should be to complete or modify the

• colors used to visualize the various conditions such as:

o Alarm / warning / tolerance limits,
o conditions of field devices such as open / closed / running,

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 85 of 313
LKZ:DE AL:N ECCN:4E992

• colors assigned to the different process media such as

o steam, oil, water, air, gas, waste, chemicals etc.
• Furthermore, it is recommended that a basic set of symbols and connections be defined before the actual
Plant Display designs begin.

The defined styles and colors are stored in the Project Container. The profiles contain key/value pairs. Each entry
represents a property.

First the system tries to load a property from the user settings. If the property is not found in the user profile, then the
system will try to load the setting from the project profile. Finally, if the property is also not found in the project profile
the hard coded default value is loaded.

To adjust the project specific settings open the window Project View in the Workbench and select Extras > Project
Settings.

4.4.5.1 Setting of Colors

The SPPA-T3000 system makes extensive use of color in the presentation of information to users. Many of these
colors can be defined and set by the user, and are used in:

• Project and user styles.

• Plant Displays: The colors used for static and dynamic elements in Plant Displays can be set as part of the
engineering.

Colors are defined and set by the user in a color keys table. In this table a key is created for each color that has been
defined. These color keys are then used to set colors for styles and Plant Displays.

The use of keys has the advantage that a reference can be created for any specific property required (e.g. a particular
process condition, like an open indication for a valve), and always used to represent this property. The actual color
defined for this key can be easily changed if required.

How to Set Colors

To open the color settings proceed as follows:

The Project View is open.

1. Select Extras, then Project Settings, then Colors.

2. The table Define Color Keys appears:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 86 of 313
LKZ:DE AL:N ECCN:4E992

• Column Color Key: This value is the reference in the system. To apply a color to an object in a style or a
Plant Display, use this key.
• Column Key Type: Use this value to make groups of colors. For example, the value System is used to group
the colors visualizing system conditions, e.g. Alarms, indicate whether a module is activated (in the Runtime
Container) or deleted, you can visualize binary and analog connections with different colors.
• Drop down list Filter: The colors assigned to a certain Key Type can be filtered.
• Column Color: Displays the color actually assigned to the color key. To change a color, click on the cell. A
sub-window appears to adjust the color.
• Column Reference: The reference color appears identically to the origin color. When the origin color is re-
defined the reference will also change accordingly. When the user changes a color which was defined by a
reference, the reference is deleted.
• Column Description: Entries in this column are optional. The user can provide a short description about the
application of that color.

Changes on the color table

• To add a color key

1. press the button Add. A new row is added at the end of the table.
2. enter a Color Key,
3. assign the color to a existing Key Type or enter a new key type,
4. press the Color button and adjust the color in the sub-window, or
5. choose a color Reference,
6. enter a description for the color.
• To delete a color key
1. click in the row to be deleted
2. click the button Delete.

After the modifications are finished click Save, or click Cancel if the changes are not to be stored in the system.

4.4.5.2 Setting of Styles

To open the style settings select the Project Settings, then Styles.
The Project Settings tree appears:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 87 of 313
LKZ:DE AL:N ECCN:4E992

The styles are grouped into the sections:

• Global Settings, allows adjustment of common properties,

• Diagram Styles, to set styles for diagrams in the Diagram Editor and in printed diagrams.
• Symbol Styles, describes the appearance of the symbols (e.g. AF Blocks) in Function Diagrams,
• Print Connector, to set the styles for the appearance of connectors in printed diagrams,
• Connector Styles, describes the appearance of connectors in the diagrams,
• Link Styles, describes the appearance of links in the diagrams,
• Workbench Settings, allows adjustment of the appearance of the Workbench,
• Operation View Settings, allows adjustment of presettings used for the appearance during the operation
mode.
• Trends/Curves, allows adjustment of presettings used for Trend Displays and XY Curve Displays.
• Plant Display Hierarchy, allows adjustment of presettings used for the appearance of the PDH.
• Diagnostic View, allows adjustment of presettings used for the appearance of the Diagnostic View.
• Point View, allows adjustment of presettings used for the appearance of the Point View.
• ASD Styles, allows adjustment of presettings used for the appearance of the ASD.
• Archive, allows the selection of the Swapping Out Mode of archive data.
• Reports, allows adjustment of presettings used for handling of reports.
• VGB, allows adjustment of presettings used for the creation of VGB compliant Function Diagrams.

Choose one of the above chapters for further details.

4.4.5.3 Connector Styles

After the section Connector Styles is opened in the table Project Settings, you will find the properties which can be
changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 88 of 313
LKZ:DE AL:N ECCN:4E992

To assign a color, click on the drop down list and select the desired color.

Colors refer always to the Color Key as defined in the section Color of the project settings.

Special Features

The property Connector background '...' identical for all states controls whether the connector background changes
according to the AF Block status.
To activate this feature the box has to be checked.

For details about the runtime status refer to Symbol appearance

To accept the changes click Save, or click Cancel to discard the changes.

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 89 of 313
LKZ:DE AL:N ECCN:4E992

4.4.5.4 Link Styles

After the section Link Styles is opened in the table Project Settings, you will find the properties which can be
changed.

To assign a color, just click on the drop down list and select the desired color key.

Colors refer always to the Color Key as defined in the section Color of the project settings.

For details about the runtime status refer to Symbol appearance.

The Link width settings set the line width for links. The first option in the drop down list is a line width that remains
constantly thin, even when zooming. This option may provide unsatisfactory results when printing diagrams.

To accept the changes click Save, or click Cancel to discard the changes.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 90 of 313
LKZ:DE AL:N ECCN:4E992

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.5.5 Global Settings

After the section Global Settings is opened in the table Project Settings, you will find the properties which can be
changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 91 of 313
LKZ:DE AL:N ECCN:4E992

Section Global Settings

The language can be selected for the presentation of the following three components in the system:

• GUI Language
• Library Language
• Help Language

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 92 of 313
LKZ:DE AL:N ECCN:4E992

All of the languages which are available in a project can be selected from the drop down list for each of the
components. When a different language has been selected for any component, it will come into effect immediately.
Some open dialog boxes may retain the old language until they are closed and reopened again.

The SPPA-T3000 language setting also changes the keyboard settings.

In cases where the SPPA-T3000 language setting and the keyboard do not correspond, it is necessary to set
the Keyboard Layout via the computer operating system.

For example, with Windows XP, if SPPA-T3000 is set to English and the keyboard is German: For the Input
Language English, the Keyboard must be set to German. If this setting is not made, some keys on the
keyboard will not work as expected (e.g. typing a y will result in a z being entered).

The drop down list Look and Feel allows the user to adjust the system GUI appearance. The four options: Windows,
Windows Classic, CDE Motiv, Metal, and Extended Look and Feel are available.

To select one of the options:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 93 of 313
LKZ:DE AL:N ECCN:4E992

1. Open the drop down list and select the desired layout
2. Click the button Save, or abort with Cancel

The Extended Look and Feel option enables extensive customizing of the GUI. This option involves the use of the
Pluggable Look and Feel functionality of Java, and is only intended for use by experienced development personnel.
The Pluggable Look and Feel definitions are contained in XML files in the following directory: \SPPA-
T3000\Orion\software\config\apache\plaf. To utilize a definition file:

1. Select the Extended Look and Feel option.

2. An empty field will appear on the right hand side of the selection box.
3. Enter the name of the definition file (excluding the .xml extension)
4. Click the button Save, or abort with Cancel

The Tag separator is used to separate the components of Tags (Tag Name and Tag Item) and Signal Definitions
(Tag Name, Signal Item and Signal Name).

To modify the default setting

1. Place the mouse pointer in the edit field and enter a separator character
2. Click the button Save, or abort with Cancel

If the Use standard browser for URLs flag is set, the URLs such as protocols are opened in the standard browser of
the system. Otherwise a special frame with minimal functionality is opened. This facility should only be used if the
standard browser cannot be used for some reason.

The Workbench Command Port is the port on the Thin Client that is used for links from the Plant Manual to the
system. In cases where more than 1 system are connected together (e.g. Multi Unit), each system must be assigned a
unique Workbench Command Port number. This number is in the range [6000 .. 6016]. The unique number must be
taken into account when making links for the Plant Manual.

Activation Section

If Automatic Activation Preview is selected, then the Preview Activation dialog will always appear when a Function
Diagram is activated from either the Project View or Diagram Editor.

Section Tool Tip Settings

A tip is displayed to inform the user about the possible action of the corresponding item, when the user moves the
cursor above a menu. The tool tip settings allow the adjustment of the behavior of the tip's activation.

• Initial Delay Time is the time which passes until the tip appears.
• Reshow Delay Time is the time which has to pass before a new activation is possible after a previous
activation.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 94 of 313
LKZ:DE AL:N ECCN:4E992

• Dismiss Delay Time specifies how long the tip is displayed after an activation.

To adjust the tool tip behavior:

1. Click in the respective field and enter the desired time value
2. Click the button Save, or abort with Cancel

Section Date and Time Formats

The date and time are displayed in several places in the workbench, in tables and printouts. The format of the date and
time strings can be set here.
Depending on the position a short, medium or long format is displayed.

To adjust the date format:

1. Open the drop down list and select the desired format
2. Optionally select a separator
3. Click the button Save, or abort with Cancel

To accept the changes click Save, or click Cancel to discard the changes. To activate the changes the user
must close the Workbench and login again.

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

Key Words for Notes

Keywords are used in the notepad function. Keywords can be assigned to each Note using the information fields, Inf1,
Inf2, and Inf3. A set of common key words for each information field can be created for the project.

To create the common key words for the project proceed as follows:

1. Click on Inf1.
2. The Edit Key Words Inf 1 dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 95 of 313
LKZ:DE AL:N ECCN:4E992

3. Add a key word as follows:

1. Click beside the last character of one of the keywords. Then press Enter on the keyboard.
2. A blank line will be created. Enter the new key word.
4. To modify a keyword highlight the keyword in the list and enter the modification.
5. Click on Ok to save the changes.
6. Repeat steps 1 to 5 for Inf2 and Inf3.

Temporary Supervisor

The Automatic Logout Time (minutes) sets the time-out of the Temporary Supervisor session when no keyboard or
mouse actions has occurred. The default time is 5 minutes.

Login Monitoring

The Number of Failed Login Attempts to Generate Alarm is set by default as 5 attempts. This applies to both the
Workbench login and the Temporary Supervisor login.

4.4.5.6 Workbench Settings

After the section Workbench is opened in the table Project Settings, you will find the properties which can be
changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 96 of 313
LKZ:DE AL:N ECCN:4E992

Choose a Background Color or Image for the Workbench

The Web Browser header and the taskbar, below the Workbench status bar, can be hidden by selecting Hide
Workbench Frame. When the header is hidden the resize, close and minimize controls will not be available to user.

If the check box Same background color as windows desktop is checked, no other background image or color for
the Workbench is possible. This is the default setting.

To select a different background image or color:

1. remove the check in the check box Same background color as windows desktop,
2. enter the path name where the picture is stored into the editable field Background image and color,
3. select a tiled or a full screen mode for displaying of the picture.
4. Alternatively select a background color from the drop down list.

Colors refer always to the Color Key as defined in the section Color of the project settings.

Windows Toolbar Font

The font and size of the button text in the Workbench windows toolbar is selectable. Prior to selecting a font the
Special windows toolbar font must be selected, then make the settings for the Windows toolbar font.

Print Function Settings

There are two parameters that can be set for the Workbench print functions:

• Print screenshot without print dialog: If this check box is selected then the Workbench menu print
functions are immediately executed after being selected. If the check box is not selected a print dialog box,
specific to the printer and printer driver, will appear after a Workbench print function is selected.
• Ensure high quality for frame screenshots: Select this check box to create higher quality printouts. If this
check box is not selected then the Workbench printouts will generate quicker, but at the expense of some
image quality.

To accept the changes click Save, or click Cancel to discard the changes. To activate the changes the user
must close the Workbench and login again.

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 97 of 313
LKZ:DE AL:N ECCN:4E992

4.4.5.7 Operation View Settings

After the section Operation View is opened in the table Project Settings, you will find the properties which can be
changed.

Section Global Operation Mode Settings

Settings effecting the appearance of the Workbench in Operation Mode and the audible alarms are made in the Global
Operation Mode Settings section.

• Navigation Buttons' Visibility: The navigation buttons in the footer of the Workbench can be switched on or
off.
• Keep ratio in fit to view mode for Plant Display : When the check box is selected the proportions of the
Plant Display will be kept constant when the Workbench view is switched from Original Size to Fit to View.
(i.e. there will be no distortion of the Plant Display .)
• Plant Display Default Display Mode: The Plant Displays can be opened in either Original size, or Fit to
View mode.
• Maximize to all screens initially: For Multi Screen arrangements, the option to maximize Plant Displays to
all screens is set as the default.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 98 of 313
LKZ:DE AL:N ECCN:4E992

• Plant Display Hierarchy Button's Visibility: The Plant Display Hierarchy button in the header of the
Workbench can be switched on or off.
• Audible Alarms Play Mode: The alarm sounds can be set to play continuously until silenced or just once.
• Maximum Number of opened Dynamic Diagrams: The maximum number of open diagrams open in
Operation Mode can be set here. This is the maximum number allowed per client.
• Maximum number of Opened Faceplates : The maximum number of open Faceplates can be set here. This
is the maximum number allowed per client.
• Anti aliasing: If Anti Aliasing is switched on, curves will appear smoother at high resolution but faded at
lower resolution.

Anti aliasing will consume more CPU load.

• Magnifying Glass Size: The height and width, in pixels, of the square magnifying glass can be set here.
• Plant Display Hierarchy Font: The font and size of the text in the Plant Display Hierarchy is selectable. Prior
to selecting a font, Special plant display hierarchy font must be selected.

Section Dynamic Diagram Color

The settings in the Dynamic Diagram Color section are applied to both Dynamic Function Diagrams and Plant
Displays.

• Background color of dynamic diagrams: Available colors are selectable in the drop down list.

Colors refer always to the Color Key as defined in the section Color of the project settings.

• Print with background color: Select this check box to switch on the option to print the Plant Displays and
Dynamic Function Diagrams with the background color. Otherwise, the background area is left blank.
• Background color of associated button for plant displays: The color of the buttons for Plant Displays in
the window toolbar.
• Background color of associated button for function diagrams: The color of the buttons for Function
Diagrams in the window toolbar.

Section Visibilities for Dynamic Function Diagrams

The default symbol appearance options for Dynamic Function Diagrams can be set in Visibilities for dynamic
function diagrams.

• Special function diagram visibilities: Selecting this check box sets the default symbol appearance to the
selected Show... options.
• Show... options: These are the symbol appearance options available in the Workbench View menu. Select
the check box to select the option as default.

Section Visibilities for Dynamic Plant Displays

The Plant Displays can be set to display tag names beside each Pictogram.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 99 of 313
LKZ:DE AL:N ECCN:4E992

• Special dynamic plant display visibilities: Selecting this check box sets the default to the Show Tag Name
for dynamic plant displays setting.

Section Faceplate

Faceplate background color, and minimum width are set in this section.

• Use background color for faceplates: Select this box to set the faceplate background color to the setting in
Background Color of Faceplates . If the check box is empty then the background color is determined by the
operating system settings
• Background color of faceplates: Available colors are selectable in the listbox.
• Use Minimal Width for Faceplates : If not selected the default minimal width is determined by either the
width of Faceplate toolbar or the width of the dynamic symbol. If selected, the faceplate width is determined
by the value entered in the Minimal Width of Faceplates field.

Section ASD Button

The colors of the ASD indicator can be modified in the ASD Button section.

• ASD-button color : The color selected from the listbox will be the button color indicating the presence of
alarms.
• ASD-button flash color: When flashing, the ASD indicator color will alternate between the colors selected for
the ASD-button color and ASD-button flash color .

Section Flash Frequency

The flash frequencies are the speeds at which visual elements related to Alarms will flash (e.g. in the ASD). Visual
elements may flash at a slow or fast speed, depending on alarm and acknowledgement state.

• Slow and Fast: Values are entered in milliseconds. Therefore the higher the value, the slower the flash rate.

Section Frame for Pictograms in Operation Mode

When a faceplate is opened in the operation mode the related Pictogram is surrounded by a border. The section
Frame for Pictograms in Operation Mode allows the adjustment of the settings for this border.

• Operating Box Foreground Color: Available colors for the border are selectable in the listbox.
• Operating Box Border Width: Enter a value for the border width.

Section Process Values

The appearance of the process values on Dynamic Function Diagrams can be configured in this section. These
settings are made in Process Values section.

• Subscription Update Delay (ms) is applied when a user scrolls from one area of a Dynamic Function
Diagram to another. This setting is the delay between the last scrolling action by the user and the update of
the process values. The default is 3000 ms. Decreasing the delay time provides a faster update of the values

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 100 of 313
LKZ:DE AL:N ECCN:4E992

but it also increases the Thin Client CPU load. The load on the S7-CPU providing the values is also
increased.
• Maximum Length of the Value: Enter the desired number of digits to be displayed. The minimum number
that can be entered is 8.
• Background Colors of the process values can be configured to help the operator quickly identify the binary
state or the quality of process values.
o Background Color GOOD - except Binary without Option sets the background color of the
analog values that have GOD status indication.
o Background Color GOOD - Binary 'true' without Option sets the background color of the binary
values that are 'true' and have GOD status indication.
o Background Color GOOD - Binary 'false' without Option sets the background color of the binary
values that are 'false' and have GOD status indication.
o Background Color BAD sets the background color of analog and binary values with BAD status
indication.
o Background Color UNCERTAIN sets the background color of analog and binary values with UNC
status indication.

Section Group Alarm Indicators

The dimensions and the fonts of the group alarms indicators are set in the Group Alarm indicators section.

• ...in workbench header and tree tooltip: The dimensions and fonts of the group alarm indicators in both the
PDH and the Workbench header can be set here.
• ...inside NavigationButton: The dimensions and fonts of the Group Alarm indicators that appear in the Plant
Displays can be set here.

Section Trends

The user can select the background color of the plotting area in the trends and XY curves with the Trend Curve
Background Color setting.

To accept the changes click Save, or click Cancel to discard the changes. To activate the changes it is
necessary to close the Workbench and login again.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 101 of 313
LKZ:DE AL:N ECCN:4E992

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, and then select Reset from the context menu.

4.4.5.8 Diagram Styles

After the section Diagram Styles is opened in the table Project Settings you will find the properties which can be
changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 102 of 313
LKZ:DE AL:N ECCN:4E992

Section Title Block

The design for the title block can be chosen from the Title Block Prototype drop down list. The default title block is
available with the system, but this can be modified using the Prototype Editor and made available for use.

The section SPPA-T3000 Title Block also allows adjusting different fonts to be used in the diagram title block.

• Select the font and size from the drop down lists.

The preview for the current settings is displayed below the options.

Section Diagrams Properties

Within this section, some of the diagram properties are set. These become the default settings for newly created
diagrams.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 103 of 313
LKZ:DE AL:N ECCN:4E992

The background color for Plant Displays and Function Diagrams can be adjusted. To select a color click the small
arrow on the right of the drop down list and choose the setting. Read only diagrams are those for which a user has
read only access rights.

The grid width and height, and some of the settings for AF Block and Connector information can also be made.

Section Print Page Format

The frame size and color for printed diagrams can be set here. The default setting for special print settings for batch
printing can also be set.

Section Editor Page Area

These settings are for the frame appearance that indicates the page size for diagrams in the editor, as described in
Function diagram Page Setup.

For Plant Displays a frame is indicated. The size of this frame for Plant Displays can be set here, and is used as a
guide when designing Plant Displays. The maximum Plant Display size for any particular screen arrangement can be
calculated. It is possible to assign more than one frame to a Plant Display.

The setting Value Column Color is used to select a background color for the input Port fields in the parameter sheet
and Point View.

Section Prototype Editor

The default grid settings for the Prototype Editor can be made.

Section Function Diagram Page Setup Properties

The default settings for Function Diagram drawing pages can be made.

Section Interactors

The default font for interactors with text can be set.

Colors refer always to the Color Key as defined in the section Color of the project settings.

To accept the changes click Save, or click Cancel to discard the changes.

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 104 of 313
LKZ:DE AL:N ECCN:4E992

Section F/FM Engineering

The Enable user influence flag enables the dialog for changing the default options for connections between S7
Runtime Containers and the Specialized Applications

The Enable alarm/archive at read modules flag enables the Archive and Alarm options for these Specialized
Applications.

4.4.5.8.1 Calculating the Plant Display Area

When Plant Displays are open in the Diagram Editor, a guide frame is visible in the diagram. This guide frame is used
when editing Plant Displays, and its size can be set in the diagram styles.

When a Plant Display is open in Operation Mode, there is a maximum display area available on the screen. This
concept is shown in the attached schematic diagram.

The available Plant Display area represents the area that is left on the screen after the area reserved for all menu
bars, toolbars and frames has been subtracted.

It is useful to set the guide frame to equal this maximum size available. Users will then be aware of the Plant Display
area available when editing Plant Displays. The maximum Plant Display area is dependant on a number of factors
(e.g. the screen resolution or the toolbar visibility), and must therefore be calculated to meet the screen configuration
used.

An example is provided below, of how to calculate the maximum Plant Display area.

Calculation Example

This calculation example is provided for the following screen arrangement:

• User logged in with Windows Explorer Web Browser.

• No Windows toolbar visible.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 105 of 313
LKZ:DE AL:N ECCN:4E992

• No windows docked in the Workbench Work Area.

• Screen resolution = 1280 x 1024 pixels.
• Workbench in Operation Mode.
• All Workbench toolbars visible.

The tables below contain the height and width dimensions (in pixels) of all the elements on the display (refer to above
schematic diagram).

Height:

Description Size (Pixels)

a Workbench Title Bar plus Frame 23
b Workbench Menu Bar 30 (in Operation Mode)
21 (not in Operation Mode)
c Workbench Default Toolbar 26
d Workbench Windows Toolbar 22
e Diagram Title Bar plus Frame 27
f Diagram Frame 7
g Workbench Status Bar 27 (with navigation buttons visible)
20 (with navigation buttons not visible)
h Workbench Frame 10
i Offset (to ensure complete diagram is displayed). 2

Width:

Description Size (Pixels)

A Workbench Frame 5
B Diagram Frame 7
C Offset (to ensure complete diagram is displayed). 2

The Plant Display maximum height and width are calculated as follows:

Plant Display maximum height = screen resolution height - (a+b+c+d+e+f+g+h+i)

= 1024 - (23+30+26+22+27+7+27+10+2)
= 850 pixels

Plant Display maximum width = screen resolution width - (A+A+B+B+C)

= 1280 - (5+5+7+7+2)
= 1254 pixels

These dimensions can be set in the Diagram Styles settings:

Editor Page Area: Plant Displays Height and Width.

4.4.5.9 Print Connector

After the section Print Connector is opened in the table Project Settings, the properties which can be changed are
found.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 106 of 313
LKZ:DE AL:N ECCN:4E992

The styles for Print Connectors define the appearance of Connector when a diagram is printed out.

To assign a color, click on the drop down list and select the desired color.

Colors refer always to the Color Key as defined in the section Color of the project settings.

Special Features

• Show Border: determines whether the connector is surrounded by a border or not.

• Draw Color / Font Color: The colors may be defined differently for text and graphic elements.

To accept the changes click Save, or click Cancel to discard the changes.

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.5.10 Symbol Styles

After the section Symbol Styles is opened in the table Project Settings, you will find the properties which can be
changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 107 of 313
LKZ:DE AL:N ECCN:4E992

To assign a color, click on the drop down list and select the desired color.

Colors refer always to the Color Key as defined in the section Color of the project settings.

Special Features

• The property Graphic Style allows a selection of 3 graphic styles for AF Blocks in Function Diagrams. An
example of each is shown below:
o IEC- with Icon

o IEC- without Icon

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 108 of 313
LKZ:DE AL:N ECCN:4E992

o SAMA

• The property Symbol background identical for all states makes the symbol background color remain the
same, irrespective of the AF Block status.
To activate this feature the box has to be checked.
• If Allow break in portname is selected, port names will be written in 2 lines if they are long. This keeps the
symbol size smaller.
• The setting Show Parameters as Ports determines the visibility of Ports and parameter values of AF Blocks
in Function Diagrams.

For details about the AF Block colors refer to symbol appearance

To accept the changes click Save, or click Cancel to discard the changes.

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.5.11 ASD Styles

After the section ASD is opened in the table Project Settings, you will find the properties which can be changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 109 of 313
LKZ:DE AL:N ECCN:4E992

ASD Columns

An ASD has a number of columns visible in its List View. In this sheet the settings can be made to control the default
appearance of the columns in user specific and context related ASDs. The appearance of context related ASDs
opened from Faceplates can also be set.

The ASD styles are applied to any ASD that has not been customized, and saved by the user.

To set the default visibility of columns in the ASD List View (for either chronological, or alarm point view), proceed as
follows:

1. Click on Edit, for either the chronological, or the alarm point view
o Clicking on Edit for Column names in chronological view or Column names in alarm point view
is for setting the appearance of user defined ASDs and context related ASDs, that are opened from
Faceplates.
o Clicking Edit for Column names in faceplate chronological view or Column names in faceplate
alarm point view will open the editor for the context related ASDs accessed from Faceplates only.
2. The Configure Asd Table Columns dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 110 of 313
LKZ:DE AL:N ECCN:4E992

Under Complete Columns on the left hand side, all available columns are shown (columns which are already
selected are grayed out). Under Configured Columns on the right hand side, all columns which have been
selected are shown.
3. To add columns for display:
1. Select the column to be displayed in the Complete Columns list.
2. Click on the Add button.
3. The selected column will appear in the Configured Columns list.

Alternatively, the column can dragged and dropped from the Complete Columns to the Configured
Columns.

4. To remove columns from display:

1. Select the column to be removed in the Configured Columns window, by clicking on it.
2. Click on the Delete button.
3. The selected column will be removed, and will appear in the Complete Columns list.

Multiple columns can be selected for removal using the SHIFT, or CTRL keys.

5. Click on Ok to accept any changes, otherwise click on Cancel.

ASD Table Text Size

To select the size of the text in the ASD table proceed as follows:

1. Tick the Special ASD table font check box.

2. Select a text size in the text size drop down list.

The text size setting will be active the next time any user logs in to SPPA-T3000.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 111 of 313
LKZ:DE AL:N ECCN:4E992

If the Special ASD table font check box is left unticked, then the text size will default to 11.

To accept the changes (for all the project settings) click Save, or click Cancel to discard the changes.

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.5.12 Archive Settings

Archive Settings

After the section Archive is opened in the table Project Settings, the Swapping Out Mode of archive data may be
selected.

The swapping out mode may be performed automatically by the system, or manually by user. Select the required
mode from the Swap out Mode drop down list.

To accept the changes (for all the project settings) click Save, or click Cancel to discard the changes.

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 112 of 313
LKZ:DE AL:N ECCN:4E992

4.4.5.13 Report Settings

After the section Reports is opened in the table Project Settings, some settings that may be made for reports
become available.

SMTP-Configuration

For emailing reports, the following settings are required:

• Mail Server: The IP Address of the mail server that is to be used to send the email messages must be
entered.
• Address of Mail Sender: The address that will appear in the email messages as that of the sender can be
entered.

Remote File System

For saving reports on a remote file system, the following setting is required:

• Remote Filesystem Path: A filesystem path must be entered. The path of a remote file system can be
specified. It is also possible to specify a local path on the Application Server.
o Example 1: //<host name or IP address>/<shared drive or folder>/<path to
folder>/
e.g. Entering //141.73.20.179/d$/Reports/ will save the reports to the folder Reports on a
drive with the shared drive name d$ of the host with IP address 141.73.20.179
o Example 2: <drive on Application Server>:/<path to folder>/
e.g. Entering D:/generated_reports/ will save the reports in the folder generated_reports
on the D: drive of the Application Server.

Save the reports in a folder that both the Application Server and Thin Clients have access to. In many cases
the Thin Clients will not have access to the folders on the Application Server.

Latency

For event triggered reports, the Latency can be set. The latency is the minimum period that will elapse before the
same report is re-triggered. This ensures that the report system will not be overloaded if the trigger signal is toggling
frequently between TRUE and FALSE.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 113 of 313
LKZ:DE AL:N ECCN:4E992

Any individual setting can be changed back to the originally installed setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.5.14 VGB Documentation Settings

After the section VGB is opened in Project Settings, the user will find the properties which can be changed. The
settings on the VGB section support the VGB Documentation features in the project.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 114 of 313
LKZ:DE AL:N ECCN:4E992

Section VGB Support

Settings, determining the user interface to the VGB documentation features, are made in the VGB Support section.

• Enable VGB Support: Selecting the check box will make the VGB features available in the Project View
menu and context menus .
• Automatic diagram generation after Commit: When this Check box is set the dialog to generate Individual
Level Diagrams will automatically appear whenever a user commits an Area Level Diagram.
• Automatic diagram generation after Activate: When this check box is set the dialog to generate Individual
Level Diagrams will automatically appear whenever a user activates an Area Level Diagram.
• Background color associated button for individual level diagrams: This is the color of the buttons in the
Workbench toolbar for the Individual Level Diagrams that are open in the Workbench.

Generated VGB Diagram View Settings

The settings in the Generated VGB diagram view settings section are applied to all generated Individual Level
Diagrams in the project.

• Special generated VGB diagram visibilities: When this check box is selected the visibilities set in the
section are applied to the generated Individual Level Diagrams.
• Show ... options: The user selects AF block information and AF block parameters to appear on the generated
individual level diagrams.
• Source and Destination Connector... options: The user selects the source and destination connector
information to appear on the generated individual level diagrams. The user may want to increase or decrease
the number of lines of connector information depending on the available space on the diagram. This can be a
factor when there are many connectors.

Generated VGB diagram page format

The settings in the Generated VGB diagram page format section allow the user to specify the drawing page size of
the generated Individual Level Diagram.

If a larger page size is selected then more logic can be shown on one page of the generated Function
Diagram.

• Special page format for all generated VGB diagrams: When this setting is selected the Individual Level
Diagrams will be generated using the width and height settings specified in this section. If this setting is not
selected then the page size will be determined by the drawing page settings used for the Area Level Diagram.

To modify the page dimensions proceed as follows:

1. Select Special page format for all generated VGB diagrams.

2. Click on Edit.
3. The Function Diagram - Page Setup dialog will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 115 of 313
LKZ:DE AL:N ECCN:4E992

4. The user has the option to:

o Select a Predefined Size: the height and width will change according to the standard page size
selected.
o Select to enter a Custom Size - the user is free to input the height and width .
5. Click on Save to save the changes.

HTML Page Format

By default one HTML file will contain the Individual Level Diagrams for a single tagname. This default can be changed
with the following settings:

• Split large diagrams: If this check box is selected, multiple HTML files will be generated for a single tagname
if the specified Maximum number of diagram pages on HTML page is exceeded.
• Maximum number of diagram pages on HTML page: The desired maximum number of Function Diagram
pages per HTML file.

Changes to the settings are not automatically incorporated into already existing Individual Level Diagrams.
The user will need to regenerate existing individual level diagrams to incorporate the changes.

4.4.5.15 Plant Display Hierarchy

Plant Display Hierarchy

After Plant Display Hierarchy is selected in the Project Settings tree, the settings that may be made for Plant
Display Hierarchy become available.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 116 of 313
LKZ:DE AL:N ECCN:4E992

Tree View

For adjusting the appearance of the PDH in Operation Mode, select Display designation as identifier to display the
designations given to the Plant Displays instead of using the Plant Display names in the PDH.

Hierarchies

By default the maximum number of partial hierarchies a user can create is 25. This default value can be changed by
entering the desired value.

4.4.5.16 Diagnostic View

Diagnostic View

When Diagnostic View is selected in the Project Settings tree, the appearance of the Diagnostic View can be
adjusted.

The settings allow the user to change the background color of the process values in the Diagnostic View.

Background colors can be used to bring the operators attention to the quality of the process values. Background colors
can also be selected to distinguish types and states of the process values:

• except Binary without Option include:

o analog and float values
o binary values with options. An example of this type of binary input would be the HI_LOW1 Port of the
ASMON. The option High or Low is selected as the input value.
• Binary 'true' without Option are binary values with a value of 1.
• Binary 'false' without Option are binary values with a value of 0.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 117 of 313
LKZ:DE AL:N ECCN:4E992

Colors refer always to the Color Key as defined in the Color section of the project settings.

The default selection is <Depending on Look&Feel>. The background color is determined by Look and
Feel selected Global Settings.

4.4.5.17 Point View

Point View

When Point View is selected in the Project Settings tree, the appearance of the Point View can be adjusted.

The settings allow the user to change the background color of the process values in the Point View.

Background colors can be used to bring the operators attention to the quality of the process values.

Background colors can also be selected to distinguish types and states of the process values:

• except Binary without Option include:

o analog and float values
o binary values used for inputs where input is a selected. An example of this type of binary input would
be the HI_LOW1 Port of the ASMON. High or Low are selected as the input value.
• Binary 'true' without Option are binary values with a value of 1.
• Binary 'false' without Option are binary values with a value of 0.

Colors refer always to the Color Key as defined in the Color section of the project settings.

The default selection is <Depending on Look&Feel>. The background color is determined by Look and
Feel selected Global Settings.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 118 of 313
LKZ:DE AL:N ECCN:4E992

4.4.5.18 Trends/Curves
When Trends/Curves is selected in the Project Settings tree, the appearance for Trend Displays and XY Curve
Displays can be adjusted.

After the settings have been changed they will come into effect the next time a Trend Display or XY Curve Display is
opened (any exceptions are mentioned).

Trend Displays

The following settings can be made.

Trend Curve Background Color: Sets the background color for Trend Displays. Select a color key from the drop
down list. This setting only comes into effect the next time that users log in.

Trend Curve Foreground Color 1 .. Trend Curve Foreground Color 10: Sets the tag color for curves. Select a color
key from the drop down list.

Trend Curve Duration: Sets the duration of curves. Select a time from the drop down time setter.

Trend Curve Interpolation: Switches interpolation on or off. Select the tick box as required.

XY Curve Displays

The following settings can be made.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 119 of 313
LKZ:DE AL:N ECCN:4E992

XY Curve Foreground Color 1 .. XY Curve Foreground Color 5: Sets the Operation Point color. Select a color key
from the drop down list.

XY Curve Background Image: Select a background image from the drop down list.

XY Curve Duration: Sets the duration of XY curves. Select a time from the drop down time setter.

XY Curve Interpolation: Switches interpolation on or off. Select the tick box as required.

Colors refer always to the Color Key as defined in the Color section of the project settings.

4.4.5.19 Defining Document Types

SPPA-T3000 comes with several standard document types defined in the system. The user can tailor the document
types to a specific project by editing the existing definitions , or adding and deleting document types.

Adding or Editing a Document Type

The Project View is open.

1. Select the Extras menu then Project Settings the Document Types from the drop down menus.
2. The Document Types dialog will appear. The document types already defined in the system are listed in the
dialog.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 120 of 313
LKZ:DE AL:N ECCN:4E992

3. The user can perform one of the following functions from this dialog:
1. To add a document document type: click on Add.
2. To edit an existing document type select a document type form the list. Then click on Edit.
4. The Edit Document Type dialog will appear.

5. Enter new information or edit existing information in the following fields:

o Name (DCC): A code assigned to a type of document.
o Description: A description of the document type.
o Subtype of: Document types can be assigned to either Function Diagrams or Plant Displays.
o Default: When this is selected then any diagram, that is created without a document type
assignment, will be assigned this DCC as default. There can only be one default document type for Function
Diagrams and one for Plant Displays. If diagrams without document codes have been imported into the
project, they will automatically assigned the default document types.

Alternatively, to define an existing Document Type as default, select the document type from the list
in the Document Type dialog. Then click on Set Default

o Generated for VGB as: This field is relevant for Function Diagrams and projects where the VGB
documentation functions will be used. If the Function Diagram document type being defined is for an Area
Level Diagram, then generated Individual Level Diagrams will have the DCC selected in this field. The user
will only be able to select DCCs already defined as Individual Level Diagrams.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 121 of 313
LKZ:DE AL:N ECCN:4E992

If the document type being defined is an Individual Level Diagrams , or no diagrams are to be generated, then
select None.
6. Click on OK to accept the changes. Otherwise click on Cancel. The dialog box will close.
7. Click on Save in the Document Types dialog to accept the changes. Otherwise click on Cancel.

If a new document type was added then a new document type will be available to assign to Function Diagrams in the
system. If an existing document type was edited, the changed characteristics in the definition will be active in all
existing Function Diagrams with this document type assignment.

Deleting a Document Type Definition

A document type definition can only be deleted if it is currently not assigned to any Function Diagrams or Plant
Displays.

To delete a document type proceed as follows:

The Project View is open.

1. Select the Extras menu then Project Settings the Document Types from the drop down menus.
2. The Document Types dialog will appear. The document types, already defined in the system, are listed in
the dialog.
3. Click on the document type in the list to delete.
4. Click on Delete.

The document type definition will no longer be available to assign to Function Diagrams or Plant Display.

4.4.5.19.1 Document Types

The document classification code (DCC) is a document type identifier that the user assigns to Function Diagrams and
Plant Displays. The DCC indicates the type of information that is shown on a diagram. In SPPA-T3000 documentation
naming system the DCC is intended to be used with the equipment identifier as the diagram identifier. From the
diagram identifier alone the user will be able to determine what type of information is provided for a given piece of
equipment.

Assigning a DCC to each Function Diagram conforms with VGB documentation guidelines.

The DCC appears in the title block of all printed Function Diagrams and Plant Displays.

The DCC also appears in the detailed List View of the Project View in the Type column.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 122 of 313
LKZ:DE AL:N ECCN:4E992

The user can modify the DCC assignment when editing the diagram title block or through spreadsheet
engineering.

Standard Codes

SPPA-T3000 comes with several IEC 61355 standard document classification codes already defined in the system.
These document type definitions are defined in SPPA-T3000 as follows:

Name (DCC) Description Subtype of Default Generate for VGB as

EFA00 Area Level Diagram Function Diagram yes EFF10
EFF10 Individual Level Diagram Function Diagram none
EFC00 Plant Display Plant Display yes none
EFC01 Topology Diagram Plant Display yes none

Another commonly used DCC system is the KKS documentation standard. Some examples are listed below:

• YFM - Overview function diagrams

• YFR - Detail Level function diagrams

The user is free to customize the document types to fit a specific project.

4.4.5.20 Inheritance Rules

To set the Active Alarm Text and Deactive Alarm Text in the parameter masks of certain Automation Function or
Hardware Proxy the user has the option to:

• enter the text manually, or

• assign an inheritance rule that will create a text expression based on values inherited from the blocks input
ports.

Inheritance rules comprise of standard rules and user defined rules. Standard rules are predefined for each block type
and cannot be modified or deleted. User defined rules can be custom defined and edited for either the entire block or
specific ports.

The inheritance rules for each block are defined in the Inheritance Rules feature found in the Project View. To
configure inheritance rules, proceed as follows:

The Project View is open.

1. Select the Extras menu, then Project Settings, then Inheritance Rules from the drop down menus.
2. The Select AF dialog box will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 123 of 313
LKZ:DE AL:N ECCN:4E992

3. Select the AF to configure from the drop down list.

Although the dialog box uses the term AF , the list will contain both Automation Functions and
Hardware Proxies available for inheritance rules.

4. Click OK to open the Edit Inheritance Rules of... window.

The Inheritance Rules of... window is now open and displays the settings for the selected block. In the Parameter
Set sheet, the default rule inheritance settings can be assigned to each port. Additionally in this sheet, user defined
inheritance rules for specific ports can be created and modified.

In the Type Specific Rules sheet, user defined inheritance rules available for all ports can be created and modified:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 124 of 313
LKZ:DE AL:N ECCN:4E992

4.4.5.20.1 Default Rule Inheritance Setting

The Edit Inheritance Rules of... window opens by default showing the Parameter Set sheet. In this view it is possible
to assign the default rule to each assignable port. The rules available for assignment are:

• Standard rules
• User defined rules as found in the Type Specific Rules sheet
• User defined rules created in the Parameter Set sheet for a specific port.
• No rule (denoted as <No Inheritance>)

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 125 of 313
LKZ:DE AL:N ECCN:4E992

The term default with regards to the inheritance rules is used to denote the relationship that the setting has
with the Active Alarm and Deactive Alarm text.

Whichever inheritance rule is assigned to the port (including the rule <No Inheritance>) becomes the
default setting when the block is placed.

This inheritance of the default rule remains until the default inheritance is broken. Until that occurs, changes to
the default rule setting will be inherited to all existing placed blocks.

To the assign an inheritance rule to a specific port, proceed as follows:

The Parameter Set sheet of the Edit Inheritance Rules of... window is open.

1. Click in the Active Alarm or Deactive Alarm field of the desired port.

Grayed out fields cannot be edited.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 126 of 313
LKZ:DE AL:N ECCN:4E992

2. A drop down list of all available rules will appear:

3. Select the desired rule.

4. To the apply changes without closing the window, click on Apply.
If the block has already been placed in the project, the rule assignment change will be inherited by all existing
blocks where the default inheritance is active.
5. When default rule assignment is complete click on Save to save any unapplied changes and close the
window. Otherwise click on Close to close the window without saving unapplied changes.

If multiple ports have been changed, the Information dialog box might contain a large quantity of
changes.

Clicking Apply after modifying each rule assignment instead of waiting until editing is complete and
using Save will ensure the rule inheritance list is kept small and manageable.

If the user attempts to switch to the Type Specific Rules sheet without applying all changes, a dialog box
appears offering the opportunity to save changes.

4.4.5.20.1.1 Creating User Defined Rules for Specific Ports

User defined inheritance rules can be created for a specific port in the Parameter Set sheet.

The user defined inheritance rules defined here are only applicable for the specific port where it is created and
will not show up in the Type Specific Rules list.

To create user defined inheritance rules available for the entire block, use the Type Specific Rules sheet.

To the create an inheritance rule for a specific port, proceed as follows:

The Parameter Set sheet of the Edit Inheritance Rules of... window is open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 127 of 313
LKZ:DE AL:N ECCN:4E992

1. Right mouse click in the Active Alarm or Deactive Alarm field of the desired port.

The currently displayed rule becomes the base for Copy or Edit operations.

If using one of these two operations, select the desired base rule before using the right mouse button.

Grayed out fields cannot be edited.

2. A context menu will appear with one or more of the following options Delete, Add, Copy, and Edit:

3. Proceed to Add, Copy, or Edit the inheritance rule (see below).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 128 of 313
LKZ:DE AL:N ECCN:4E992

Selecting Delete will delete the rule from the list without additional warning.

4. To the apply changes without closing the window, click on Apply.

If the block has already been placed in the project, the rule change will be inherited by all existing blocks
where the default inheritance is active.
5. When default rule assignment is complete click on Save to save any unapplied changes and close the
window. Otherwise click on Close to close the window without saving unapplied changes.

If multiple ports have been changed, the Information dialog box might contain a large quantity of changes.

Clicking Apply after modifying each rule assignment instead of waiting until editing is complete and using
Save will ensure the rule inheritance list is kept small and manageable.

The inheritance rule is applied to the port.

Standard inheritance rules cannot be edited or deleted.

User defined inheritance rules defined in the Type Specific Rules sheet cannot be deleted or edited via the
context menu.

Add an Inheritance Rule

To add an inheritance rule for a specific port proceed as follows:

The Add Rule dialog box is open:

1. Enter the rule following the rule syntax.

If the rule contains unallowed syntax, the text changes color and the OK button is disabled.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 129 of 313
LKZ:DE AL:N ECCN:4E992

2. Click OK to save. Otherwise click Cancel.

The inheritance rule is applied to the port.

Copy an Inheritance Rule

To copy an existing inheritance rule and use it as the base for a new rule proceed as follows:

The Copy Rule dialog box is open with the base rule:

1. Modify the rule following the rule syntax.

If the rule contains unallowed syntax, the text changes color and the OK button is disabled.

2. Click OK to save. Otherwise click Cancel.

The inheritance rule is applied to the port. The base rule remains in the list.

If no changes to the base rule are made, clicking Ok will open an error message and the operation will be
canceled.

Edit an Inheritance Rule

To edit an inheritance rule for a specific port proceed as follows:

The Edit Rule dialog box is open with the rule to be edited:

1. Edit the rule following the rule syntax.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 130 of 313
LKZ:DE AL:N ECCN:4E992

If the rule contains unallowed syntax, the text changes color and the OK button is disabled.

2. Click OK to save. Otherwise click Cancel.

The inheritance rule is applied to the port. The older version is overwritten.

4.4.5.20.2 Creating Type Specific Rules

User defined Type Specific Rules for Active Alarm and Deactive Alarm text can be created for each block in the Type
Specific Rules sheet of the Edit Inheritance Rules of... window.

The rules created here are available to all applicable ports in the block.

To create user defined inheritance rules available only for specific ports, use the context menu in the
Parameter Set sheet.

To create and edit Type Specific Rules, proceed as follows:

The Edit Inheritance Rules of... window is open.

1. Click on the Type Specific Rules sheet.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 131 of 313
LKZ:DE AL:N ECCN:4E992

The user defined Type Specific Rules will be displayed in the window.

2. Proceed to Delete, Add, Copy or Edit the rules (described below).

3. When rule modification is complete, click on Apply to apply the changes without closing the window.
4. If a rule is deleted or modified which applies to a block already placed in the project, the rule change will be
inherited by all existing blocks where the default inheritance is active.
5. When rule modification is complete click on Save to save any unapplied changes and close the window.
Otherwise click on Close to close the window without saving unapplied changes.

If multiple ports have been changed, the Information dialog box might contain a large quantity of
changes.

Clicking Apply after modifying each rule assignment instead of waiting until editing is complete and
using Save will ensure the rule inheritance list is kept small and manageable.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 132 of 313
LKZ:DE AL:N ECCN:4E992

If the user attempts to switch to the Parameter Set sheet without applying all changes, a dialog box
appears offering the opportunity to save changes.

The Type Specific Rules will be modified.

Delete Inheritance Rule

To delete an existing type specific inheritance rule proceed as follows:

Selecting Delete will delete the rule from the list without additional warning (i.e. no dialog box).

The Type Specific Rules dialog box is open.

1. Select the rule to delete from the list.

2. Click Delete to delete the rule.

The inheritance rule is deleted.

Add Inheritance Rule

To add a type specific inheritance rule proceed as follows:

The Type Specific Rules dialog box is open.

1. Click on Add.
2. The Add Rule dialog box opens:

3. Enter the rule following the rule syntax.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 133 of 313
LKZ:DE AL:N ECCN:4E992

If the rule contains unallowed syntax, the text changes color and the OK button is disabled.

4. Set the check boxes accordingly if the rule is to be Usable as 'Active Alarm' or Usable as 'Deactive Alarm'.
5. Click OK to save. Otherwise click Cancel.

The inheritance rule is added to the list.

Copy Inheritance Rule

To copy an existing type specific inheritance rule proceed as follows:

The Type Specific Rules dialog box is open.

1. Select the base rule to copy from the list.

2. Click on Copy.
3. The Copy Rule dialog box opens:

4. Modify the rule following the rule syntax.

If the rule contains unallowed syntax, the text changes color and the OK button is disabled.

5. Set the check boxes accordingly if the rule is to be Usable as 'Active Alarm' or Usable as 'Deactive Alarm'.
6. Click OK to save. Otherwise click Cancel.

The inheritance rule is added to the list. The base rule remains in the list.

Edit Inheritance Rule

To edit a type specific inheritance rule proceed as follows:

The Type Specific Rules dialog box is open.

1. Select the rule to edit from the list.

2. Click on Edit.
3. The Edit Rule dialog box opens:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 134 of 313
LKZ:DE AL:N ECCN:4E992

4. Edit the rule following the rule syntax.

If the rule contains unallowed syntax, the text changes color and the OK button is disabled.

5. Set the check boxes accordingly if the rule is to be Usable as 'Active Alarm' or Usable as 'Deactive Alarm'.
6. Click OK to save. Otherwise click Cancel.

The inheritance rule is edited in the list. The older version is overwritten.

4.4.5.20.2.1 Inheritance Rules Syntax

An inheritance rule is a concatenation of free text and parameter values. There exist several basic rule formats:

Type Example Example Output

Rule
Format
Text only > max > max
Single Limit [LV1] Limit 100 exceeded
rule exceeded (example with parameter LV1 equal to 100)
using
port
variables
and text
Conditio [HI_LOW2 > 99 %
nal rule ]?> [LV2] (example with parameter HI_LOW2 equal to TRUE, LV2 equal to 99, and EU equal to %)
using [EU]:<
port [LV2] [EU]
variables
and text

Rules are checked for correctness during creation. Invalid rules are not permitted to be saved.

Syntax Rules and Hints

The following are important syntax rules and hints for creating inheritance rule:

• A port variable is of the form [PORTNAME]. The localized port names are displayed and can be used to
create new rules.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 135 of 313
LKZ:DE AL:N ECCN:4E992

• For conditional rules, only binary port variables are allowed.

• The character colon (:) is only allowed for defining a conditional rule. It is not allowed in the rule text.
• The character question mark (?) is not allowed in the condition of a conditional string. But unlike the colon (:),
it can be used in rule text.

4.4.5.20.3 Inheriting Rule Changes

If the block has already been placed in the project, any rule assignment or rule change will be inherited by all existing
blocks where the default rule inheritance is active.

When the user attempts to apply the rule assignment or rule change (via either Apply or Save), the Information
dialog box appears with a list of the changes to the engineering data:

To change the rules and overwrite the existing assignments click Yes, otherwise to cancel the change and retain the
existing assignments click No.

If No is selected, all the rule changes and assignments made since last successful Apply or Save are lost.

The contents of the dialog box can be printed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 136 of 313
LKZ:DE AL:N ECCN:4E992

4.4.6 User Specific Settings

Customizing of the Graphical User Interface (GUI)

Irrespective of project settings, any suitably authorized user can adjust the settings for appearance but the changes
will be restricted to that user's login.
If there is no individual setting available the system uses the project settings.

To adjust the user specific setting open the window Project View and select Extras > User Properties > Styles.

4.4.6.1 Setting of Styles

To open the style settings select the User Properties, then Styles.
The User Properties tree appears:

The styles are grouped into the sections:

• Global Settings, allows the adjustment of common properties,

• Diagram Styles, to set styles for diagrams in the Diagram Editor and in printed diagrams.
• Symbol Styles, describes the appearance of symbols (e.g. AF Blocks) in Function Diagrams,
• Print Connector, to set the styles for the appearance of connectors in printed diagrams,
• Connector Styles, describes the appearance of connectors in the diagrams,
• Link Styles, describes the appearance of links in the diagrams,
• Workbench Settings, allows the adjustment of the appearance of the Workbench,
• Operation View Settings, allows the adjustment of the presettings used for the appearance during the
operation mode.
• Trends/Curves, allows the adjustment of the presettings used for Trend Displays and XY Curve Displays.
• Plant Display Hierarchy, allows adjustment of presettings used for the appearance of the PDH.
• Diagnostic View, allows adjustment of presettings used for the appearance of the Diagnostic View.
• Point View, allows adjustment of presettings used for the appearance of the Point View.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 137 of 313
LKZ:DE AL:N ECCN:4E992

• ASD Styles, allows adjustment of presettings used for the appearance of the ASD.

Choose one of the above chapters for further details.

4.4.6.2 Connector Styles

After the section Connector Styles is opened in the table User Properties, you will find the properties which can be
changed.

To assign a color, click on the drop down list and select the desired color.

Colors refer always to the Color Key as defined in the section Color of the project settings.

Special Features

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 138 of 313
LKZ:DE AL:N ECCN:4E992

• The property Connector background '...' identical for all states controls whether the connector background
changes according to the AF Block status.
To activate this feature the box has to be checked.

For details about the runtime status refer to Symbol appearance

To accept the changes click Save, or click Cancel to discard the changes.

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.6.3 Link Styles

After the section Link Styles is opened in the table User Properties, you will find the properties which can be
changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 139 of 313
LKZ:DE AL:N ECCN:4E992

To assign a color, click on the drop down list and select the desired color key.

Colors refer always to the Color Key as defined in the section Color of the project settings.

For details about the runtime status refer to Symbol appearance.

The Link width settings set the line width for links. The first option in the drop down list is a line width that remains
constantly thin, even when zooming. This option may provide unsatisfactory results when printing diagrams.

To accept the changes click Save, or click Cancel to discard the changes.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 140 of 313
LKZ:DE AL:N ECCN:4E992

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.6.4 Global Settings

After the section Global Settings is opened in the table User Properties, the following properties can be changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 141 of 313
LKZ:DE AL:N ECCN:4E992

Section Global Settings

The language can be selected for the presentation of the following three components in the system:

• GUI Language
• Library Language
• Help Language

All of the languages which are available in a project can be selected from the drop down list for each of the
components. When a different language has been selected for any component, it will come into effect immediately.
Some open dialog boxes may retain the old language until they are closed and reopened again.

The SPPA-T3000 language setting also changes the keyboard settings.

In cases where the SPPA-T3000 language setting and the keyboard do not correspond, it is necessary to set
the Keyboard Layout via the computer operating system.

For example, with Windows XP, if SPPA-T3000 is set to English and the keyboard is German: For the Input
Language English, the Keyboard must be set to German. If this setting is not made, some keys on the
keyboard will not work as expected (e.g. typing a y will result in a z being entered).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 142 of 313
LKZ:DE AL:N ECCN:4E992

The drop down list Look and Feel allows the user to adjust the system GUI appearance. The four options: Windows,
Windows Classic, CDE Motiv, Metal, and Extended Look and Feel are available.

To select one of the options:

1. Open the drop down list and select the desired layout
2. Click the button Save, or abort with Cancel

The Extended Look and Feel option enables extensive customizing of the GUI. This option involves the use of the
Pluggable Look and Feel functionality of Java, and is only intended for use by experienced development personnel.
The Pluggable Look and Feel definitions are contained in XML files in the following directory: \SPPA-
T3000\Orion\software\config\apache\plaf. To utilize a definition file:

1. Select the Extended Look and Feel option.

2. An empty field will appear on the right hand side of the selection box.
3. Enter the name of the definition file (excluding the .xml extension)
4. Click the button Save, or abort with Cancel

If the Use standard browser for URLs flag is set, the URLs such as protocols are opened in the standard browser of
the system. Otherwise a special frame with minimal functionality is opened. This facility should only be used if the
standard browser cannot be used for some reason.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 143 of 313
LKZ:DE AL:N ECCN:4E992

Activation Section

If Automatic Activation Preview is selected, then the Preview Activation dialog will always appear when a Function
Diagram is activated from either the Project View or Diagram Editor.

Section Tooltip Settings

A tip is being displayed to inform the user about the possible action of the corresponding item, when the user moves
the cursor above a menu. The tooltip settings allow the adjustment of the behavior of the tip activation.

• Initial Delay Time is the time which passes until the tip appears.
• Reshow Delay Time is the time which has to pass before a new activation is possible after a previous
activation.
• Dismiss Delay Time specifies how long the tip is displayed after an activation.

To adjust the tooltip behavior:

1. Click in the respective field and enter the desired time value
2. Click the button Save, or abort with Cancel

Section Date and Time Formats

The date and time are displayed in several places in the workbench, in tables and printouts. The format of the date and
time strings can be set here.
Depending on the position a short, medium or long format is displayed.

To adjust the date format:

1. Open the drop down list and select the desired format
2. Optionally select a separator
3. Click the button Save, or abort with Cancel

To accept the changes click Save, or click Cancel to discard the changes. To activate the changes the user
must close the Workbench and login again.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 144 of 313
LKZ:DE AL:N ECCN:4E992

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.6.5 Workbench Settings

After the section Workbench is opened in the table User Properties, you will find the properties which can be
changed.

Choose a Background Color or Image for the Workbench

The Web Browser header and the taskbar, below the Workbench status bar, can be hidden by selecting Hide
Workbench Frame. When the header is hidden the resize, close and minimize controls will not be available to user.

If the check box Same background color as windows desktop is selected, no other background image or color for
the Workbench is possible. This is the default setting.

To select a different background image or color proceed as follows:

1. Remove the check in the check box Same background color as windows desktop,
2. Enter the path name where the picture is stored into the editable field Background image and color,
3. Select a tiled or a full screen mode for displaying of the picture.
4. Alternatively select a background color from the drop down list below.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 145 of 313
LKZ:DE AL:N ECCN:4E992

Colors refer always to the Color Key as defined in the section Color of the project settings.

Windows Toolbar Font

The font and size of the button text in the Workbench windows toolbar are selectable. Prior to selecting a font select
the Special windows toolbar font check box. Then make the settings for the Windows toolbar font.

Print Function Settings

There are two parameters that can be set for the Workbench printing functions:

• Print screenshot without print dialog: If this check box is selected then the Workbench menu print
functions are immediately executed after being selected. If the check box is not selected a print dialog box,
specific to the printer and printer driver, will appear after a Workbench print function is selected.
• Ensure high quality for frame screenshots: Selecting this check box will create higher quality printouts. If
this check box is not selected then the Workbench printouts will generated quicker, but at the expense of
some image quality.

To accept the changes click Save, or click Cancel to discard the changes. To activate the changes the user
must close the Workbench and login again.

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.6.6 Operation View Settings

After the section Operation View is opened in the table User Properties, you will find the properties which can be
changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 146 of 313
LKZ:DE AL:N ECCN:4E992

Section Global Operation Mode Settings

Settings affecting the appearance of the Workbench in Operation Mode and the audible alarms are made in the Global
Operation Mode Settings section.

• Navigation Buttons' Visibility: The navigation buttons in the footer of the Workbench can be switched on or
off.
• Keep ratio in fit to view mode for Plant Display : When the check box is selected the proportions of the
Plant Display will be kept constant when the Workbench view is switched from Original Size to Fit to View,
(i.e. there will be no distortion of the Plant Display.)
• Plant Display Default Display Mode: The Plant Displays can be opened in either Original size, or Fit to
View mode.
• Maximize to all screens initially: For Multi Screen arrangements, the option to maximize Plant Displays to
all screens is set as the default.
• Maximum Number of opened Dynamic Diagrams: The maximum number of open diagrams open in
Operation Mode can be set here. This is the maximum number allowed per client.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 147 of 313
LKZ:DE AL:N ECCN:4E992

• Maximum number of Opened Faceplates : The maximum number of open Faceplates can be set here. This
is the maximum number allowed per client.
• Anti aliasing: If Anti Aliasing is switched on, curves will appear smoother at high resolution but faded at
lower resolution.

Anti aliasing will consume more CPU load.

• Magnifying Glass Size: The height and width, in pixels, of the square magnifying glass can be set here.
• Plant Display Hierarchy Font: The font and size of the text in the Plant Display Hierarchy is selectable. Prior
to selecting a font, Special plant display hierarchy font must be selected.

Section Dynamic Diagram Color

The settings in the Dynamic Diagram Color section are applied to both Dynamic Function Diagrams and Plant
Displays.

• Background color of dynamic diagrams: Available colors are selectable in the drop down list.
• Print with background color: A tick in this check box switches on the option to print the Plant Displays and
Dynamic Function Diagrams with the background color. Otherwise, the background area is left blank.
• Background color of associated button for plant displays: The color of the buttons for Plant Displays in
the window toolbar.
• Background color of associated button for function diagrams: The color of the buttons for Function
Diagrams in the window toolbar.

Section Visibilities for Dynamic Function Diagrams

The default symbol appearance options for Dynamic Function Diagrams can be set in Visibilities for dynamic
function diagrams.

• Special function diagram visibilities: Ticking this check box sets the default symbol appearance to the
selected Show... options.
• Show... options: These are the symbol appearance options available in the Workbench View menu. Tick the
check box to select the option as default.

Section Visibilities for Dynamic Plant Displays

The Plant Displays can be set to display tag names beside each Pictogram.

• Special dynamic plant display visibilities: Ticking this check box sets the default to the Show Tag Name
for dynamic plant displays setting.

Section Faceplate

Faceplate background color, and minimum width are set in this section.

• Use background color for faceplates: A tick in this box sets the faceplate background color to the setting in
Background Color of Faceplates . If the check box is empty then the background color is determined by the
operating system settings
• Background color of faceplates: Available colors are selectable in the drop down list.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 148 of 313
LKZ:DE AL:N ECCN:4E992

• Use Minimal Width for Faceplates : If not selected the default minimal width is determined by either the
width of Faceplate toolbar or the width of the dynamic symbol. If selected, the faceplate width is determined
by the value entered in the Minimal Width of Faceplates field.

Section Frame for Pictograms in Operation Mode

When a faceplate is opened in the operation mode the related Pictogram is surrounded by a border. The section
Frame for Pictograms in Operation Mode allows the adjustment of the settings for this border.

• Operating Box Foreground Color: Available colors for the border are selectable in the drop down list.
• Operating Box Border Width: Enter a value for the border width.

Section Process Values

The appearance of the process values on Dynamic Function Diagrams can be configured in this section. These
settings are made in Process Values section.

• Subscription Update Delay (ms) is applied when a user scrolls from one area of a Dynamic Function
Diagram to another. This setting is the delay between the last scrolling action by the user and the update of
the process values. The default is 3000 ms. Decreasing the delay time provides a faster update of the values
but it also increases the Thin Client CPU load. The load on the S7-CPU providing the values is also
increased.
• Maximum Length of the Value: Enter the desired number of digits to be displayed. The minimum number
that can be entered is 8.
• Background Colors of the process values can be configured to help the operator quickly identify the binary
state or the quality of process values.
o Background Color GOOD - except Binary without Option sets the background color of the
analog values that have GOOD status indication.
o Background Color GOOD - Binary 'true' without Option sets the background color of the binary
values that are 'true' and have GOOD status indication.
o Background Color GOOD - Binary 'false' without Option sets the background color of the binary
values that are 'false' and have GOOD status indication.
o Background Color BAD sets the background color of analog and binary values with BAD status
indication.
o Background Color UNCERTAIN sets the background color of analog and binary values with
uncertain status indication.

Section Group Alarm Indicators

The dimensions and the fonts of the group alarms indicators are set in the Group Alarm indicators section.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 149 of 313
LKZ:DE AL:N ECCN:4E992

• ...in workbench header and tree tooltip: The dimensions and fonts of the group alarm indicators in both the
PDH and the Workbench header can be set here.
• ...inside NavigationButton: The dimensions and fonts of the Group Alarm indicators that appear in the Plant
Displays can be set here.

Section Trends

The user can select the background color of the plotting area in the trends and XY curves with the Trend Curve
Background Color setting.

To accept the changes click Save, or click Cancel to discard the changes. To activate the changes it is
necessary to close the Workbench and login again.

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

4.4.6.7 Diagram Styles

After the section Diagram Styles is opened in the table User Properties you will find the properties which can be
changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 150 of 313
LKZ:DE AL:N ECCN:4E992

Section Title Block

The section SPPA-T3000 Title Block allows adjusting different fonts to be used in the diagram title block.

• Select the font and the size from the drop down list.

The preview for the current settings is displayed below the options.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 151 of 313
LKZ:DE AL:N ECCN:4E992

Plant Display Properties

The background color for Plant Displays can be adjusted.

Select a color click from the drop down list. Read only diagrams are those for which a user has read only access
rights.

Function Diagram Properties

The background color for Function Diagrams can be adjusted.

Select a color click from the drop down list. Read only diagrams are those for which a user has read only access
rights.

Section Print Page Format

The frame size and color for printed diagrams can be set here. The default setting for special print settings for batch
printing can also be set.

Section Editor Page Area

These settings are for the frame appearance that indicates the page size for diagrams in the editor, as described in
Function diagram Page Setup.

For Plant Displays a frame is indicated. The size of this frame for Plant Displays can be set here, and is used as a
guide when designing Plant Displays. The maximum Plant Display size for any particular screen arrangement can be
calculated. It is possible to assign more than one frame to a Plant Display.

The setting Value Column Color is used to select a background color for the input Port fields in the parameter sheet
and Point View.

Colors refer always to the Color Key as defined in the section Color of the project settings.

To accept the changes click Save, or click Cancel to discard the changes.

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 152 of 313
LKZ:DE AL:N ECCN:4E992

4.4.6.8 Print Connector

After the section Print Connector is opened in the table User Properties, you will find the properties which can be
changed.

The styles for Print Connectors define the appearance of a Connector when a diagram is printed out.

To assign a color, click on the drop down list and select the desired color.

Colors refer always to the Color Key as defined in the section Color of the project settings.

Special Features

• Show Border: determines whether the connector is surrounded by a border or not.

• Draw Color / Font Color: The colors can be defined differently for text and graphic elements.

To accept the changes click Save, or click Cancel to discard the changes.

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the context menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 153 of 313
LKZ:DE AL:N ECCN:4E992

4.4.6.9 Symbol Styles

After the section Symbol Styles is opened in the table User Properties, you will find the properties which can be
changed.

To assign a color, click on the drop down list and select the desired color.

Colors refer always to the Color Key as defined in the section Color of the project settings.

Special Features

• The property Graphic Style allows a selection of 3 graphic styles for AF Blocks in Function Diagrams. An
example of each is shown below:
o IEC- with Icon

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 154 of 313
LKZ:DE AL:N ECCN:4E992

o IEC- without Icon

o SAMA

• The property Symbol background identical for all states makes the symbol background color remain the
same, irrespective of the AF Block status.
To activate this feature the box has to be checked.
• If Allow break in portname is selected, port names will be written in 2 lines if they are long. This keeps the
symbol size smaller.
• The setting, Show Parameters as Ports determines the visibility of Ports and parameter values of AF Blocks
in Function Diagrams.

For details about the AF Block status refer to Symbol appearance

To accept the changes click Save, or click Cancel to discard the changes.

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the Context Menu.

4.4.6.10 ASD Styles

After the section ASD is opened in the table User Properties, you will find the properties which can be changed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 155 of 313
LKZ:DE AL:N ECCN:4E992

ASD Table Text Size

To select the size of the text in the ASD table proceed as follows:

1. Select the Special ASD table font check box.

2. Select a text size in the text size drop down list.
3. To accept the changes click Save, or click Cancel to discard the changes.

To apply the Project Settings leave the Special ASD table font check box unselected.

The text size setting will be active the next time the user logs in to SPPA-T3000.

To make all the user specific settings equal to the project settings, press the Reset All button.

Any individual setting can be changed back to the project setting as follows:

Position the cursor over the text that describes the setting.

Click on the right mouse button, then select Reset from the Context Menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 156 of 313
LKZ:DE AL:N ECCN:4E992

4.4.6.11 Plant Display Hierarchy

Plant Display Hierarchy

After Plant Display Hierarchy is selected in the User Properties tree, the settings that may be made for Plant Display
Hierarchy become available.

Tree View

For adjusting the appearance of the PDH in Operation Mode, select Display designation as identifier to display the
designations given to the Plant Displays instead of using the Plant Display names in the PDH.

4.4.6.12 Diagnostic View

Diagnostic View

When Diagnostic View is selected in the User Properties tree, the appearance of the Diagnostic View can be
adjusted.

The settings allow the user to change the background color of the process values in the Diagnostic View.

Background colors can be used to bring the operators attention to the quality of the process values. Different colors
can be selected for GOOD, BAD or UNCERTAIN quality.

Background colors can also be selected to distinguish types and states of the process values:

• except Binary without Option include:

o analog and float values
o binary values with options. An example of this type of binary input would be the HI_LOW1 Port of the
ASMON. The option High or Low is selected as the input value.
• Binary 'true' without Option are binary values with a value of 1.
• Binary 'false' without Option are binary values with a value of 0.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 157 of 313
LKZ:DE AL:N ECCN:4E992

Colors refer always to the Color Key as defined in the section Color of the project settings.

The default selection is <Depending on Look&Feel>. The background color is determined by Look and
Feel selected Global Settings.

4.4.6.13 Point View

Point View

When Point View is selected in the User Properties tree, the appearance of the Point View can be adjusted.

The settings allow the user to change the background color of the process values in the Point View.

Background colors can be used to bring the operators attention to the quality of the process values. Different colors
can be selected for GOOD, BAD or UNCERTAIN quality.

Background colors can also be selected to distinguish types and states of the process values:

• except Binary without Option include:

o analog and float values
o binary values used for inputs where input is a selected. An example of this type of binary input would
be the HI_LOW1 Port of the ASMON. High or Low are selected as the input value.
• Binary 'true' without Option are binary values with a value of 1.
• Binary 'false' without Option are binary values with a value of 0.

Colors refer always to the Color Key as defined in the section Color of the project settings.

The default selection is <Depending on Look&Feel>. The background color is determined by Look and
Feel selected Global Settings.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 158 of 313
LKZ:DE AL:N ECCN:4E992

4.4.6.14 Trends/Curves
When Trends/Curves is selected in the User Properties tree, the appearance for Trend Displays and XY Curve
Displays can be adjusted.

After the settings have been changed they will come into effect the next time a Trend Display or XY Curve Display is
opened by the user (any exceptions are mentioned).

Trend Displays

The following settings can be made.

Trend Curve Background Color: Sets the background color for Trend Displays. Select a color key from the drop
down list. This setting only comes into effect the next time that the user logs in.

Trend Curve Foreground Color 1 .. Trend Curve Foreground Color 10: Sets the tag color for curves. Select a color
key from the drop down list.

Trend Curve Duration: Sets the duration of curves. Select a time from the drop down time setter.

Trend Curve Interpolation: Switches interpolation on or off. Select the tick box as required.

XY Curve Displays

The following settings can be made.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 159 of 313
LKZ:DE AL:N ECCN:4E992

XY Curve Foreground Color 1 .. XY Curve Foreground Color 5: Sets the Operation Point color. Select a color key
from the drop down list.

XY Curve Background Image: Select a background image from the drop down list.

XY Curve Duration: Sets the duration of XY curves. Select a time from the drop down time setter.

XY Curve Interpolation: Switches interpolation on or off. Select the tick box as required.

Colors refer always to the Color Key as defined in the Color section of the project settings.

4.4.7 Setting the System Diagram Root

Setting the system diagram root is required when the diagnostic hierarchy is created. The requirements for, and the
creation of the diagnostic hierarchy are explained below.

The Diagnostic Hierarchy

The diagnostic hierarchy is the arrangement of system components that is visible in the Tree View of the Diagnostic
View. The user navigates through the diagnostic hierarchy to access diagnostic information.

The majority of diagnostic information that the user most frequently wishes to access is information from:

• Proxies: Hardware and Management Proxies provide diagnostic information about IO devices, bus
communication and server components.
• Containers: Containers running on servers provide diagnostic information and have control functionality via
the Diagnostic View.

The diagnostic hierarchy can be designed to provide easy access to this information.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 160 of 313
LKZ:DE AL:N ECCN:4E992

Creating the Diagnostic Hierarchy

A diagnostic hierarchy is created automatically when the system is installed, but only contains all the servers that are
configured for the project. A new diagnostic hierarchy can then be designed, and tailored to meet the requirements of
any specific project.

The diagnostic hierarchy is dependant on the design of the Project Hierarchy. A sub tree within the Project Hierarchy is
selected as the diagnostic hierarchy. This is achieved by setting the system diagram root, as explained below.

In order to make the proxy and container information easily accessible it is recommended to arrange the system
diagrams under the system diagram root in the Project Hierarchy, as follows:

• Group diagrams containing Hardware Proxies and Management Proxies under the system diagram root.
• Create a Project Node for each server that has containers running on it, and group these under the system
diagram root. When the diagnostic hierarchy is viewed in the Diagnostic View, all containers running on the
server will automatically appear.

Nodes representing servers in the Diagnostic View must be named exactly the same as the server name.

This arrangement will result in a Diagnostic Hierarchy as shown graphically here:

Diagrams will not appear twice in the diagnostic hierarchy in the Diagnostic View, i.e. A diagram under the
system diagram root will not appear under the Runtime Container to which it is assigned.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 161 of 313
LKZ:DE AL:N ECCN:4E992

How to Set the System Diagram Root

To set the system diagram root for creation of the diagnostic hierarchy, proceed as follows:

This action is disabled if any operating sessions are open. The list of users in operating mode can be found in
the License Status window.

For setting the System Diagram Root, the Alarm Container must be stopped.

The Project View is open.

1. Select the Project Node to be used for the system diagram root.
2. Select the Edit menu, then Set System Diagram Root from the drop down menu.
3. A dialog box appears to confirm the selection, click on Set Root to set the system diagram root, otherwise
click on Cancel.

The system diagram root will be set and the diagnostic hierarchy updated accordingly.

4.4.8 Project Version Management

The engineered data for an SPPA-T3000 project undergoes many changes during the design, commissioning and
operation of the system. It is often useful (or required) to be able to track new or changed software in a project. A
project version is a record of the complete engineering data for the project, made at any specific point in time.

The following functions are provided for project version management:

• Creating Project Versions

• Comparing Project Versions

4.4.8.1 Creating Project Versions

A project version is in fact a complete backup of the project made at a distinct time. The project version includes:

• All engineered data.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 162 of 313
LKZ:DE AL:N ECCN:4E992

• The complete library (i.e. Automation Functions, Proxies, Macros and Prototypes).

Creating a Project Version is only possible in Configuration Mode.

The project version will include committed data only.

To create a project version proceed as follows:

The Project View is open.

1. Select the Versioning menu, then Create Project Version from the drop down menu.
2. The Create Project Version dialog box appears.

3. Enter a Version Id. This is a mandatory input, and the system will only accept a unique identifier.
4. Enter a Description if required. This is an optional input.
5. To create a project version click on Create, otherwise click on Cancel.

A project version will be created.

Engineering will be locked while the system creates the project version.

4.4.8.2 Comparing Project Versions

Once project versions have been created, it is possible to carry out a comparison of these versions. The system
compares the versions and reports on the differences it finds between them. The comparison is node selective, and
any part of, or the compete project data can be selected for comparison.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 163 of 313
LKZ:DE AL:N ECCN:4E992

Comparisons can only be made with versions from the same project.

Which Data is Compared ?

The version comparison is performed to identify changes which affect the functionality of the engineered data. For this
reason not all data in the project version is compared.

The following data will be compared:

• The Project Hierarchy

• Title block information
• Diagram manual scheduling
• Runtime Container Assignment
• Function Diagram default cycle time
• Component manual scheduling
• AF Block cycle time
• AF blocks, proxies and Macros within Function Diagrams
• Signals and connections
• Parameter settings

The following data will not be compared:

• The contents of Plant Displays

• Any free graphics in Function Diagrams.
• Connector, line or block positions in Function Diagrams.

How to Compare Project Versions

To compare project versions proceed as follows:

The Project View is open.

1. Select the Project Node for which the engineered data is to be compared (select the root node to compare the
entire project).
2. Select the Versioning menu, then Compare Project Versions from the drop down menu.
3. The Compare Project Versions dialog box appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 164 of 313
LKZ:DE AL:N ECCN:4E992

4. The Selected Node is visible.

5. Select the Base Version from the drop down list. This is the version which the Compare Version will be
checked against.

The Current Project Data can be selected as the Base Version. In this case all current data,
irrespective of whether it has been committed or not, will be compared.

6. Select the Compare Version.

7. To start the comparison click on Compare, otherwise click on Cancel.
8. After the comparison is complete, a dialog box will appear containing summary information of errors or
warnings from the operation. To view a report detailing all the differences between the versions, click on the
Open Protocol button to open a protocol report browser, otherwise click on OK.

4.4.9 Assigning Pictograms and Faceplates

Automation Functions, Proxies and Macros provide an operation user interface via Pictograms and Faceplates in Plant
Displays. The relationship between them is established as follows:

• Automation Function, proxy and Macro types are assigned to Prototype types (i.e. Pictograms and
Faceplates).
• The Prototype type properties are mapped individually to Ports of the AF, proxy or Macro type.

Automation Functions and proxies have default assignments and property Mappings which are pre-configured for the
system. Assignments and property Mappings for Macros are configured by the user.

Port assignment may only be changed for Macros and/or custom Prototypes.

How to make Assignments

To assign Pictograms and Faceplates to Automation Functions, proxies or Macros, proceed as follows:

The Project View is open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 165 of 313
LKZ:DE AL:N ECCN:4E992

1. Select the Automation Function, proxy or Macro that is to be assigned from the Library Node.
2. Select the Extras menu, then Assign Pictogram/Faceplate from the drop down menu.
3. The Assign Pictogram/Faceplate dialog box appears.

The Selected AF is the AF, Proxy or Macro that was selected for assignment. The Assigned Prototypes are
the Faceplates and/or Pictograms that have already been assigned to the selected component.
4. The following functions can now be carried out :
o Adding or deleting prototype assignments
o Assigning ports
o Setting or deleting the default prototype and Automation Function
5. Click on Save to save any new assignments, otherwise click on Cancel.

4.4.9.1 Adding or Deleting Prototype Assignments

Assigning an AF, proxy or Macro type to a Prototype type effectively links the two together. For example, if an AF block
has been placed in a Function Diagram, then a corresponding prototype of an assigned type can be placed in a Plant
Display, and the process connection made. Any number of assignments can be made.

The assigned prototype is the Pictogram or Faceplate that is selected when integrated engineering is used.

To add or delete prototype assignments to AFs, proxies or Macros proceed as follows:

The Assign Pictogram/Faceplate dialog box is open.

• To add prototype assignments:

1. Click on Add.
2. A Prototype Browser will appear.
3. Select the prototype to be assigned. This can be either a Pictogram or a Faceplate.
4. Click on Ok to make the assignment, otherwise click on Cancel.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 166 of 313
LKZ:DE AL:N ECCN:4E992

If a Pictogram is assigned it is useful to assign a corresponding Faceplate as well. In this way default
mappings can be made to both the Pictogram and the Faceplate.

• To delete prototype assignments:

1. Select the prototype to be deleted from the assignments by clicking on it.
2. Click on Delete.
3. The assignment will be deleted.

4.4.9.2 Assigning Ports

Once the assignments have been made, the AF, Proxy or Macro type Ports have to be mapped to the corresponding
properties in the Prototype. The mapping defines how the Pictogram or Faceplate indicates or exchanges signals with
the AF, Proxy or Macro (See General Remarks for more information on mapping Ports).

Port assignment can only be changed for Macros and/or custom Prototypes.

If both a Pictogram and a corresponding Faceplate have been assigned, remember to perform the mapping for
both.

To map signals between Ports and properties, proceed as follows:

The Assign Pictogram/Faceplate dialog box is open.

1. Select the Prototype for which the mapping is to be performed.

2. Click on Assign Ports .
3. The Assign AF Ports to Pictogram/Faceplate dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 167 of 313
LKZ:DE AL:N ECCN:4E992

On the left hand side of the dialog box, the component (i.e. AF, proxy or Macro) Ports appear. On the right
hand side the Prototype Properties appear.
4. To create a new mapping by drag and drop, proceed as follows:
1. Select the component Port to be mapped by positioning the cursor over it and pressing and holding
the Left Mouse button.
2. Holding the Left Mouse button, drag the item to the Property to which it is to be mapped.
3. Position the cursor over the AF Port column of the property and release the Left Mouse button.
The mapping will be made, and the name of the component Port will appear in the property
mapping.

Alternatively the user has the option to map the property to the variation min, variation max
or engineering unit of one of the existing Property values. This is performed using the
context menu in the AF Port field.

5. To remove existing mappings proceed as follows:

1. Select the property mapping to be removed by clicking on it.
2. Click on the small arrow.

The mapping will be removed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 168 of 313
LKZ:DE AL:N ECCN:4E992

Click on the large arrow to remove all mappings simultaneously.

Alternatively, the user has the option to remove existing mappings via the context menu:
Right mouse click > Remove or Right mouse click > Remove All.

4.4.9.2.1 Inheritance Assignment of Pictogram Properties

The Prototype properties can not only be mapped individually to Ports of the AF, Proxy or Macro type, but in some
cases also to the variation min, variation max, and engineering unit associated with the port assigned to another
Prototype property.

The same steps apply to the inheritance mapping of individual Faceplate Properties.

To map a Pictogram property in this way, proceed as follows:

1. The Assign AF Ports to Pictogram/Faceplate table is open.

2. Right mouse click in the AF Port field for the property to be assigned:

3. Select the inheritance type (e.g. Use Variation Min...).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 169 of 313
LKZ:DE AL:N ECCN:4E992

4. The Select Property dialog box opens:

5. Select the Prototype Property to use for the mapping from the drop down list. The list contains all the
prototype properties available from the Mapping Details Pictogram table for mapping of the chosen
inheritance type.
6. Click OK to confirm the mapping or Cancel to abort.
7. The mapping is displayed in the Value field.

The selected Prototype Property is mapped to the property associated with the selected port assigned to the other
Property.

4.4.9.3 Setting or Deleting the Default Prototype and Automation

Function
The default Prototypes and Automation Functions are the components which appear as defaults when making process
connections, or appear in the reference list during integrated engineering.

Default Prototypes

To set or delete the default prototype for an Automation Function, proceed as follows:

The Assign Pictogram/Faceplate dialog box is open.

• To set a default prototype:

1. Select the prototype to be set as default.
2. Click on Set Default Prototype .
The appendix (Default Prototype) appears.
• To delete a default setting:
1. Select the prototype with the default to be deleted.
2. Click on Delete Default Prototype .
The appendix (Default Prototype) disappears.

Default Automation Functions

To set or delete the selected AF as the default AF for any of the assigned prototypes, proceed as follows:

The Assign Pictogram/Faceplate dialog box is open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 170 of 313
LKZ:DE AL:N ECCN:4E992

• To set a default Automation Function:

1. Select a prototype from the Assigned Prototypes .
2. Click on Set Default AF .
The appendix (Default AF) appears next to the prototype.
• To delete a default setting proceed as follows:
1. Select the prototype with the default AF to be deleted.
2. Click on Delete Default AF .
The appendix (Default AF) disappears.

A prototype may only have one AF set as default. If a new default is set, the old one is automatically deleted.

4.4.10 User Specific Plant Displays in the Project View

User specific plant displays are provided for operation users who want to make their own Plant Displays using
elements from existing Plant Displays engineered for a project. The representation of user specific plant displays from
an engineering view is described here.

When a user specific plant display is created it is stored under a Project Node that is automatically created with the
users name. All the user specific plant displays belonging to a particular user will be stored under one node.

User specific plant displays can be opened and edited in the Diagram Editor just like any other Plant Display if required
(any changes then have to be committed and activated).

User specific plant displays cannot be deleted or renamed.

4.4.11 Alarm Sounds

Alarm sounds are a component of the Alarm System, and are used to alert users to the presence of Alarms by means
of an audible signal. The configuration and customizing of alarm sounds is very flexible, and is performed by the
engineering user.

Alarm sounds are generated at the thin client computers (where users are logged in), and are played using the
computers own sound system (i.e. sound card and loudspeaker).

Many alarm sounds are available for use. Users can also import sound files if required for the project, or later delete
them. The sounds can then be organized for use in the system.

The allocation of alarm sounds to Alarm Sources is performed by defining Sound Alarm Groups. Using Sound Alarm
Groups, different sounds can be allocated to:

• Different Alarm types (e.g. more critical alarms can be allocated more acute alarm sounds).
• Different areas of the Project Hierarchy (e.g. boiler and turbine alarms can have different sounds).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 171 of 313
LKZ:DE AL:N ECCN:4E992

4.4.11.1 Importing and Deleting Sounds

Several default sounds are made available in the system. It is also possible for users to use other sounds. The sounds
are contained in sound files, and the system will play sounds from a number of sound file formats. The following file
formats are possible:

File Extension Format Description

.wav Windows Wave File
.snd Sound File
.au Audio File
.aif Audio Interchange File
.aifc Audio Interchange File (Compressed)
.aiff Audio Interchange File Format
.wma Windows Media Audio File

Sound files of any length can be imported.

Alarm sounds can be selected to play either once, or continuously via the project settings. When
Continuously is selected the playing of the sound file will be looped by the system.

Importing Sounds

To import sounds to the system proceed as follows:

The Project View is open.

1. Select the Extras menu, then Import, then Sound File from the drop down menus.
2. The Import Sound Files dialog box will open.

3. Enter the path and file name of the sound file to be imported, or click on the browse button to open an Open
dialog box to find the file.
4. Click on Import to import the file, otherwise click on Cancel.
The sound file will be imported and available for use in the project.

The maximum size of a single sound file that can be imported is 5 MB.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 172 of 313
LKZ:DE AL:N ECCN:4E992

Deleting Sounds

Sounds no longer required in the project can be deleted as follows:

The Project View is open.

1. Select the Extras menu, then Delete, then Sound File from the drop down menus.
2. The Delete Sound Files dialog box will appear.

3. Select the file to be deleted from the drop down list.

4. Click on Delete to delete the file, otherwise click on Cancel.

4.4.11.2 Organizing Sounds

The sound files in the system can be organized to enable easy definition of the sound alarm groups. Organization of
the sounds involves:

• Creation of sounds: Allocating names and description to sound files.

• Creating sounds via reference: An existing sound can be used to create new sounds. This is useful when the
same sound is used in different applications. Should the sound need to be changed, the sound file only needs
to be changed once.
• Editing existing sounds.
• Deletion of sounds.

To organize sounds proceed as follows:

The Project View is open.

1. Select the Extras menu, then Project Settings, then Sounds from the drop down menus.
2. The Define Sounds dialog box will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 173 of 313
LKZ:DE AL:N ECCN:4E992

Any sound can be previewed by clicking on the Play arrow for the sound.

3. To create a new sound:

1. Click on Add.
2. Enter a Sound Name and a Description.
3. To allocate a sound either:
Click in the Sound cell and select a sound file from the drop down list. OR
Click in the Reference cell and select a reference sound from the drop down list.
4. To edit an existing sound: click in the cell to be edited, and edit as required.
5. To delete a sound: Click anywhere in the row for the sound, and then click on Delete.
6. Click on Save to save any changes, otherwise click on Cancel.

4.4.11.3 Defining Sound Alarm Groups

The creation of Sound Alarm Groups allows the user to allocate alarm sounds to Alarm Sources.

Sound Alarm Groups can be created for any Project Node in the Project Hierarchy, and are created for a single Alarm
Type only.

All Alarm Sources (of the defined Alarm Type) within sub-nodes of a Sound Alarm Group Project Node will also be
allocated the same alarm sound, except in cases where a subnode is defined as an alarm sound group itself.

How to Define Sound Alarm Groups

To create or edit a Sound Alarm Group for a Project Node in the Project Hierarchy, proceed as follows:

The Project View is open.

1. Select the Project Node in either the Tree View or the List View.
2. Select the Edit menu, then Sound Alarm Groups from the drop down menu.
3. A Define Sound Alarm Groups dialog box will open.

All Alarm Types defined within the Sound Alarm Group are listed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 174 of 313
LKZ:DE AL:N ECCN:4E992

4. To add a new Alarm Type :

1. Click on Add.
2. A new row will be added to the table in the dialog box.
3. Click on the Alarm Type cell, and select the Alarm Type to be defined from the drop down list. Only
the undefined Alarm Types will be listed.
4. Click on the Sound Name cell, and select a sound name from the drop down list.

If no alarm sound is required (i.e. the alarm is to be silent), the option NO_SOUND can be selected
from the Sound Name drop down list.

5. To edit an existing row: Click on the cell to be edited, and edit it as required.
6. To delete a row in the table: Click anywhere in the row to select it, then click on Delete.
7. Click on Save to save the settings, otherwise click on Cancel.

Alternatively, select the function via the context menu: Right mouse click > Edit Sound Alarm Groups .

How Sound Groups are Indicated

When a Project Node has been defined as a Sound Alarm Group, it is indicated in the List View of the Project View
(the List View appearance must be selected to details).

4.4.12 Alarm Printers

Alarm printers are components of the Alarm System, and are used to print out alarms, immediately as they are raised
or gone, in chronological order.

Alarm printers can be connected to thin client computers, and are exclusively used for the purpose of alarm printing.
The printers use continuous paper to facilitate on-line printing.

Alarms can be configured to print out at different alarm printers. This is performed by defining Print Alarm Groups.
Different alarm printers can be allocated to:

• Different areas of the Project Hierarchy (e.g. all boiler alarms on one printer, and all turbine alarms on
another).
• Different Alarm Types (e.g. all system alarms can be sent to a single alarm printer for maintenance
personnel).

Alarm printers can be started and stopped via the Project View.

4.4.12.1 Defining Print Alarm Groups

The creation of Print Alarm Groups allows the user to decide which Alarms will be printed out on a particular alarm
printer.

Print Alarm Groups can be created for any Project Node in the Project Hierarchy. The user can define:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 175 of 313
LKZ:DE AL:N ECCN:4E992

• On which alarm printer the alarms will be printed.

• Which Alarm Types will be printed.

All Alarm Sources (of the defined Alarm Types) in Function Diagrams within the Project Node are allocated to the Print
Alarm Group. All Alarm Sources (of the defined Alarm Types) within sub-nodes of a Print Alarm Group Project Node
will also be allocated to the same Print Alarm Group, except in cases where a sub-node is defined as a Print Alarm
Group itself.

How to Define Print Alarm Groups

To create or edit a Print Alarm Group for an alarm printer, proceed as follows:

An alarm printer must exist before Print Alarm Groups may be defined.

The Project View is open.

1. Select the Project Node in either the Tree View or the List View.
2. Select the Edit menu, then Print Alarm Groups from the drop down menu.
3. A Define Print Alarm Groups dialog box will open.

All alarm printers and Alarm Types defined for the Print Alarm Group are shown.
4. To add a new alarm printer:
1. Click on Add Printer.
2. The Add Alarm Printer dialog box will appear.

3. Select the alarm printer to be added from the drop down list.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 176 of 313
LKZ:DE AL:N ECCN:4E992

4. Click on Add to add the new alarm printer, otherwise click on Cancel.
5. To remove an alarm printer:
1. Select the printer to be removed from the Alarm Printer list.
2. Click on Remove Printer.
6. To add new Alarm Types to a printer:
1. Select the printer from the Alarm Printer list.
2. Click on Add Alarm Type .
3. The Add Alarm Type dialog box will appear.

4. Select the Alarm Types to be allocated to the printers Print Alarm Group, from the drop down list.

All Alarm types can be selected, or the Alarm Types can be selected individually.

5. Click on the Add button to add the Alarm Type, otherwise click on Cancel.
6. The selected Alarm Type will be included in the Alarm Types list.
7. To remove Alarm Types from a printer:
1. Select the printer from the Alarm Printer list.
2. Select the Alarm Type to be deleted from the Alarm Types list.
3. Click on Remove Alarm Type .
8. Click on Save to save the settings, otherwise click on Cancel.

Alternatively, select the function via the context menu: Right mouse click > Edit Print Alarm Groups .

How Print Alarm Groups are Indicated

When a Project Node has been defined as a Print Alarm Group, it is indicated in the List View of the Project View (the
List View appearance must be selected to details).

4.4.12.2 Stopping and Starting Alarm Printing

Alarm printing on a particular alarm printer can be started and stopped via the Project View. The two functions are
described below.

How to Start Alarm Printing

To start alarm printing on an alarm printer proceed as follows:

The Project View is open.

1. Select the Admin menu, then Alarm Printer, then Start Printing from the drop down menus.
2. The Start Alarm Printing dialog box will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 177 of 313
LKZ:DE AL:N ECCN:4E992

3. Select the printer from the Select Alarm Printer drop down list.
4. Click on Start to start printing, otherwise click on Cancel.

The printer will start printing alarms.

How to Stop Alarm Printing

To stop alarm printing on an alarm printer proceed as follows::

The Project View is open.

1. Select the Admin menu, then Alarm Printer, then Stop Printing from the drop down menus.
2. The Stop Alarm Printing dialog box will open.
3. Select the printer from the Select Alarm Printer drop down list.
4. Click on Stop to stop printing, otherwise click on Cancel.

The printer will stop printing alarms.

4.4.13 Alarm Types

Alarms are characterized by an Alarm Type that can be used to indicate the origin or severity of Alarms. The definition
of Alarm Types is very flexible. There are a number of default Alarm Types, but new Alarm Types may also be created,
possibly to meet project specific requirements .

New Alarm Types can be added, and existing Alarm Types can be edited or deleted.

4.4.13.1 Adding Alarm Types

To add a new alarm type for use in the project, proceed as follows:

The Project View is open.

1. Select the Admin menu, then Alarm Types from the drop down menu.
2. The Alarm Types dialog box will open.

The dialog box contains a list of all the defined Alarm Types.
3. Click on the Add button.
4. The New Alarm Type dialog box will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 178 of 313
LKZ:DE AL:N ECCN:4E992

5. The new Alarm Type can be configured by setting the following fields in the dialog box:
o Name: An alarm type name that is used in the system, e.g. in the ASD and in Parameter masks
where the alarm parameters are set. The text should be brief and descriptive.
o Abbreviated Name: An abbreviation of the Name that is used for alarm display, e.g. in the ASD or
group alarm indicators. The text should be very short (ideally only one or two letters).
o Display Group Alarm Indicator: Select the check box to display the Alarm Type in group alarm
indicators.
o Color: This is the background color used for alarm display in the ASD or group alarm indicators. The
color is set via the color key in the drop down list on the right hand side of the field.
o Default Color: The Default Color will replace the Color if the system cannot access the color key
(e.g. if it has been deleted). To set the default color, click on the box on the right hand side of the field. A
dialog box will open, in which the default color can be directly set.
o Flash Color: This is the background color used for flashing alarms. When an alarm flashes, the
background color alternates between the Color and the Flash Color. The color is set via the color key in the
drop down list on the right hand side of the field.
o Default Flash Color: The Default Flash Color will replace the Flash Color if the system cannot
access the color key (e.g. if it has been deleted). To set the default flash color, click on the box on the right
hand side of the field. A dialog box will open, in which the default flash color can be directly set.
o Priority: This is the priority of the Alarm Type. The priority defines the order of importance for the
presentation of Alarm Types, when only one type can be displayed, e.g. in the alarm indicators in the PDH.
The priority is an Integer number equal to, or greater than zero. The type with the lowest number has the
highest priority.
o I&C : This setting determines the position of the alarm display in the group alarm indicators. If
selected, the alarm will be displayed on the side of the I&C alarm indicator.
o Manual Operator Response: If selected a manual operator response is required to clear and
acknowledge the alarm.
6. Click on Apply to add the new Alarm Type to the list in the Alarm Types dialog box, otherwise click on
Cancel.
7. Click on Save in the Alarm Types dialog box to create the new Alarm Type in the system, otherwise click on
Cancel.

The new Alarm Type will be created, and can be assigned at Alarm Sources.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 179 of 313
LKZ:DE AL:N ECCN:4E992

4.4.13.2 Editing Alarm Types

To edit an existing Alarm Type that has been defined in the project, proceed as follows:

The Project View is open.

1. Select the Admin menu, then Alarm Types from the drop down menu.
2. The Alarm Types dialog box will open.

The dialog box contains a list of all the defined Alarm Types.
3. Select the Alarm Type to be edited by clicking on it.
4. Click on the Edit button.
5. The Edit Alarm Type dialog box will open.

6. The selected Alarm Type can be edited by setting the following fields in the dialog box:
o Name: Cannot be edited.
o Abbreviated Name: Cannot be edited.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 180 of 313
LKZ:DE AL:N ECCN:4E992

o Display Group Alarm Indicator: Tick the check box to display the Alarm Type in group alarm
indicators.
o Color: This is the background color used for alarm display in the ASD or group alarm indicators. The
color is set via the color key in the drop down list on the right hand side of the field.
o Default Color: The Default Color will replace the Color if the system cannot access the color key
(e.g. if it has been deleted). To set the default color, click on the box on the right hand side of the field. A
dialog box will open, in which the default color can be directly set.
o Flash Color: This is the background color used for flashing alarms. When an alarm flashes, the
background color alternates between the Color and the Flash Color. The color is set via the color key in the
drop down list on the right hand side of the field.
o Default Flash Color: The Default Flash Color will replace the Flash Color if the system cannot
access the color key (e.g. if it has been deleted). To set the default flash color, click on the box on the right
hand side of the field. A dialog box will open, in which the default flash color can be directly set.
o Priority: This is the priority of the Alarm Type. The priority defines the order of importance for the
presentation of Alarm Types, when only one type can be displayed, e.g. in the alarm indicators in the PDH.
The priority is an Integer number equal to, or greater than zero. The type with the lowest number has the
highest priority.
o I&C : This setting determines the position of the alarm display in the group alarm indicators. If
selected, the alarm will be displayed on the side of the I&C alarm indicator.
o Manual Operator Response: If selected a manual operator response is required to clear and
acknowledge the alarm.
7. Click on Apply to update the changes and return to the Alarm Types dialog box, otherwise click on Cancel.
8. Click on Save in the Alarm Types dialog box to update the edited Alarm Type in the system, otherwise click
on Cancel.

The edited Alarm Type will be updated in the system. Wherever the type has been assigned to an Alarm Source, the
type will be updated.

To make any changes effective for alarms displayed in ASDs, the Alarm Container must be restarted.

4.4.13.3 Deleting Alarm Types

To delete an existing Alarm Type that has been defined in the project, proceed as follows:

An Alarm Type cannot be deleted when it is assigned to any Alarm Source. These assignments must be
removed before the Alarm Type can be deleted.

Default Alarm Types cannot be deleted.

The Project View is open.

1. Select the Admin menu, then Alarm Types from the drop down menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 181 of 313
LKZ:DE AL:N ECCN:4E992

2. The Alarm Types dialog box will open.

The dialog box contains a list of all the defined Alarm Types.
3. Select the Alarm Type to be deleted by clicking on it.
4. Click on the Delete button.
5. The selected Alarm Type will be deleted from the list of Alarm Types in the dialog box.
6. Click on Save in the Alarm Types dialog box to delete the selected Alarm Type in the system, otherwise click
on Cancel.

The edited Alarm Type will be deleted from the system.

4.4.14 Downloading Files from a Server

Sometimes it may be necessary to access files that are stored on an SPPA-T3000 application server (e.g. exported
files or protocol reports). Files can be downloaded from the server at any client computer, and can be stored at any
location that can be accessed by the client computer.

To download files from a server, proceed as follows:

The Project View is open.

1. Select the Extras menu, then File Download from the drop down menu.
2. The Download from server dialog box appears.

3. Select the files to download:

1. Click on the button on the right hand side of the Download file(s) field.
2. The Select the File(s) to Download dialog box will open. All user accessible directories on the
server are available here.
3. Select the file(s) to be downloaded in the dialog box.
4. Select the destination to which the files are to be downloaded.
1. Click on the button on the right hand side of the Destination field.
2. The Select the Destination dialog box will open. All directories accessible to the client computer are
available here.
3. Select the destination in the dialog box.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 182 of 313
LKZ:DE AL:N ECCN:4E992

5. Click on Download to download the files, otherwise click on Cancel.

6. A dialog box opens which indicates the downloads progress. Click on Cancel if required, to abort the
download.

The files will be downloaded from the server to the selected destination.

4.4.15 Images
Images may be imported into, and used within the system. For example, an image of a plant component can be placed
in a Plant Display, if it is of particular use for plant operation.

Images of several different file formats can be imported:

File Extension Format Description

.gif Graphics Interchange Format
.png Portable Network Graphics
.jpg JPEG Compliant
.jif JPEG Compliant
.jpeg Joint Photographic Experts Group

When images are imported, they are stored on the Application Server. When an image is no longer required, it can be
deleted.

4.4.15.1 Importing Images

To import images to the system proceed as follows:

The Project View is open.

1. Select the Extras menu, then Import, then Image from the drop down menus.
2. The Import Image File dialog box will open.

3. Enter the path and file name of the Image File to be imported, or click on the button on the right hand side of
the field, and an Open dialog box will open for browsing, and find the file.
4. Click on Import to import the file, otherwise click on Cancel.

The image file will be imported and becomes available for use in the project.

Size Limits

The maximum size of images that can be imported into the Workbench are as follows:

• 1280 x 1024 pixels for .gif files

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 183 of 313
LKZ:DE AL:N ECCN:4E992

• (1280 x 1024)/4 for .png, .jpg, .jif, .jpeg. The smaller size requirement is due to the way color data is stored in
these file formats.

If a file in .png, .jpg, .jif or .jpeg is too large to import, then try changing the file format to .gif.

4.4.15.2 Deleting Images

Images no longer required in the project can be deleted as follows:

Take care not to delete images that are currently used in the project (e.g. placed in a Plant Display).

The Project View is open.

1. Select the Extras menu, then Delete, then Image from the drop down menus.
2. The Delete Image dialog box will appear.

3. Select the Deletable Image file to be deleted from the drop down list. The user will be informed if no images
are currently stored in the system.
4. Click on Ok to delete the file, otherwise click on Cancel.

The image will be deleted from the system.

4.5 Runtime Containers

Runtime Containers provide the execution environment for all Function Diagrams.

A typical system installation may include many Runtime Containers, depending on the size and requirements of the
project. A Runtime Container is always allocated to an SPPA-T3000 server, on which it runs.

Function Diagrams are assigned to Runtime Containers. The Automation Functions, Management Proxies or
Hardware Proxies contained in the Function Diagrams are all executed in their assigned Runtime Containers.

The cycle time for the execution of all elements within Function Diagrams can be set. All the elements are executed in
a particular execution sequence.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 184 of 313
LKZ:DE AL:N ECCN:4E992

4.5.1 Types of Runtime Containers

There are different types of Runtime Containers available. The selection of the type of Runtime Container to be used
depends on the nature of its application.

The table below provides a summary of the different Runtime Container types:

Type Execution Mode Server Type Executes Comments

S7 Runtime Realtime Automation AFs, S7 Hardware Used for Realtime
Container Server S7-CPU Proxies automation tasks on
an S7-CPU.
Management Non-Realtime Application Management Used for
Container Server Proxies, AFs Management Proxies
on Application
Servers.
OPC Client Non-Realtime Application OPC Client Used for an OPC
Container Server Hardware Proxies, Client interface on an
AFs Application Server.
CM Runtime Realtime Automation Hardware Proxies, Used for CM
Container Server CM AFs communication with
external systems.
Runtime Non-Realtime Application AFs, Modbus Used for Non-
Container Server Proxies Realtime tasks on
Application Servers.
S7 Turbine Realtime FM458-1DP Turbine Control Used for turbine
Control CFC Blocks control.
(FM458)
Runtime
Container
S7 Fail Safe Realtime Automation Fail Safe CFC Used for fail safe
Runtime Server S7-CPU Blocks applications.
Container
Technical Non-Realtime Technology Lifetime Used for the Lifetime
Calculation Server Calculation, TDY Calculations and TDY
Container AFs application.
Plant Monitor Non-Realtime Technology Plant Monitor AFs A type fo Technical
Container Server Calculation Container
used for the Plant
Monitor application.

Analog Number Ranges

The ranges of Integers and Floating Point Numbers are as follows:

Format Server Type Range

Minimum Maximum
Integer Automation Server S7-CPU -231(i.e. -2147483648) +231(i.e. 214748364
31 31
Application Server, Automation Server CM -2 (i.e. -2147483648) +2 (i.e. 214748364
Floating Point Number Automation Server S7-CPU -3.402823E+38 +3.402823E+38
Application Server, Automation Server CM -3.40282347E+38 +3.40282347E+38

Analog Number Accuracy

The floating-point arithmetics on the Application Server and Automation Server CM have an accuracy of 8 decimal
places resulting in a maximum resolution of 1.17549435E-38. However, on the Automation Server S7-CPU, the
accuracy for floating-point arithmetics is limited to 6 decimal places resulting in a lower maximum resolution of
1.175495E-38.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 185 of 313
LKZ:DE AL:N ECCN:4E992

4.5.2 Runtime Containers on Servers

Runtime Containers are allocated to a single Application or an Automation Server. A server may have more than one
Runtime Container allocated to it.

Runtime Containers can execute in a Realtime, or a non-Realtime mode.

• Realtime Runtime Containers are used for automation tasks. Realtime execution ensures that automation
tasks are carried out within a cycle time specified by the user.
• Non-Realtime Runtime Containers are used for functions which do not require continuous strict adherence to
a specific cycle time.

Runtime Containers can be created by users, and existing Runtime Containers can be edited or deleted. When a
Runtime Container has been created, it can be started or stopped by the user.

Management Containers are provided specifically for the execution of Management Proxies. These containers
are created automatically by the system.

4.5.2.1 Creating Runtime Containers

The purpose of a Runtime Container must be considered when it is created. The user should take into account:

• What type of server the Runtime container should be allocated to, i.e. an Automation or an Application server.
• The base cycle time for the Runtime Container. This is the shortest possible cycle time in which all the
components assigned to the Runtime Container will be executed.
• Longer base cycle times allow for more Automation Functions (e.g. for control logic), or proxies to be
executed in a Runtime Container. The base cycle time should be set as long as it is reasonable for the
application.

The creation of Runtime Containers and Management Containers is explained below:

How to Create a Runtime Container

The Project View is open.

1. Select the Admin menu, then Runtime Container , then Create from the drop down menus.
2. The Create New Runtime Container dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 186 of 313
LKZ:DE AL:N ECCN:4E992

The dialog box contains default values in some fields to assist the user.
3. Enter a Container Name, the container names must be unique. All the Runtime Containers in an installation
can be consistently numbered, (e.g. rtc101 ... rtc105).
4. Enter a Container Description, this can be freely edited.
5. Container Id: No entry is required in this field, as the container ID will be allocated automatically.
In some cases it may be required to enter the ID of a previous runtime container, and the configuration of this
old runtime container can be recovered. To enter this ID, first tick the check box in front of the entry.
6. Select a Host Name from the drop down list. Each host in the list is a server that has been configured for the
project.
7. Select a Execution Mode of the Runtime Container from the drop down list. i.e. Realtime or non-Realtime.

Realtime Runtime Containers can only be allocated to S7-CPU Automation Servers or CM

Automation Servers.
Creating S7 Runtime Containers and CM Runtime Containers is described elsewhere.

8. Select the Communication Protocols supported by the Runtime Container. Click on the browse button (on
the right hand side of the field) to open the Communication Protocols rtc window.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 187 of 313
LKZ:DE AL:N ECCN:4E992

Select the protocols. Click on Save to save the selection or click on Cancel to close the window without
saving.
9. Enter a Base Cycle Time for the container, in milliseconds. Typical values for a Runtime Container are in the
range of 16 .. 1000 msec.
10. Enter a Keep Alive Time Time for the container, in milliseconds. The keep alive time is the time period the
Runtime Container uses for monitoring communication with other Runtime Containers. If a break in
communication with another container occurs for a period exceeding the keep alive time, all the signals being
received from this container will acquire a bad quality.
11. Select the Memory Usage from the drop down list. This is used to optimize memory allocation for the
Runtime Container on the server. A Runtime Container with approximately 5000 Automation Functions or
proxies allocated to it is considered a Medium memory usage. Runtime Containers having less than 3000 or
more than 7000 can be selected as Minimum or Maximum, resectively.
12. Select Restart Container on Failure in the check box, if required. A Runtime Container that has Restart
Container enabled, will attempt a restart automatically following a failure. This property is selected according
to the control philosophy of the plant.
13. Click on Create to create the new Runtime Container, or otherwise click on Cancel.

The new Runtime Container will be created, and Function Diagrams can be assigned to it. The new Runtime Container
will also have to be started.

Management Containers

Management Containers are created automatically for each server, and cannot be created by users. One Management
Container is created for each Application Server.

4.5.2.2 Creating S7 Runtime Containers

For every S7-CPU a Runtime Container must be created.

The S7-CPU type corresponds to the type of S7 hardware in the S7-CPU. The following S7-CPU types are supported:

• CPU 414-3
• CPU 414-H
• CPU 414-HPG
• CPU 416-2
• CPU 416-3
• CPU 417-4
• CPU 417-H
• CPU types for fail safe systems
o CPU 417-F
o CPU 417-FH

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 188 of 313
LKZ:DE AL:N ECCN:4E992

• CPU types for turbine control (FM458)

o CPU 414-HPG_FM
o CPU 417-H_FM
• CPU type for fail safe and turbine control
o CPU 417-FH_FM

Fail Safe and Turbine Control

When Runtime Containers are created for either a fail safe or turbine control (FM458) S7-CPU types, two containers
will be simultaneously created:

• One container is created for the fail safe or turbine control functionality. The ID of this container will have the
suffix -F for fail safe, or _FM for turbine control.
• The other is an S7 Runtime Container with which signal exchange with the fail safe or turbine control Runtime
Container can occur.

For the CPU type CPU 417-FH_FM , one S7-CPU includes both fail safe and turbine control functionality. In this case
all three containers will be simultaneously created.

How to Create an S7 Runtime Container

The Project View is open.

1. Select the Admin menu, then Runtime Container , then Create S7 Runtime Container from the drop down
menus.
2. The Create New S7 Runtime Container dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 189 of 313
LKZ:DE AL:N ECCN:4E992

The dialog box contains default values in some fields to assist the user. The dialog box has 2 sheets:
o Main Properties: Contains settings that require user entry.
o Expert Properties: Contains settings that can be viewed but not edited.
3. Edit the parameters in the Main Properties sheet.
4. Define the peer to peer connections for the Runtime Container.
5. Click on Create to create the new Runtime Container, or otherwise click on Cancel.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 190 of 313
LKZ:DE AL:N ECCN:4E992

When an S7 Runtime Container has been created, the Execution Frame must be loaded to the S7 CPU.

If Peer-to-Peer connections have been made, additional steps may be required.

4.5.2.2.1 Editing the Main Properties

In order for and S7 Runtime Container to be created, the following container and CPU type properties must be entered
in the Main Properties sheet:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 191 of 313
LKZ:DE AL:N ECCN:4E992

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 192 of 313
LKZ:DE AL:N ECCN:4E992

The dialog box contains default values in some fields to assist the user.

• Container Name: Must be unique and may contain a maximum of 24 characters (no special characters may
be used). All the Runtime Containers in an installation can be consistently numbered, (e.g. afc701 ... afc705).
• Container Description: Can be freely edited.
• Container Id(= SIMATIC ID): No entry is required in this field, as the container ID will be allocated
automatically. .
• In some cases it may be required to enter the ID of a previous runtime container, and the configuration of this
old runtime container can be recovered. To enter this ID, first tick the check box in front of the entry.
• CPU Type: The S7-CPU type corresponds to the type of S7 hardware being used.
• Peer-to-Peer Sources: Defines the peer to peer connections for the S7-CPU.
• Host Name: The name of the First Application Server. This entry is added automatically and cannot be
changed.
• Application Server First IP Address (Automation Highway): The IP address for the Ethernet card for the
Application Server. The following configurations are possible.
o Single physical bus: Only one IP address for the Application Server is required. Enter either the IP
address, or the text localhost.
o Dual physical bus: Two IP addresses for the Application Server are required. Enter the first of these
addresses.

In a Multi Unit, ensure that the IP address for Application Server of the Local Unit is entered.

• Application Server Second IP Address (Automation Highway): Referring the First IP Address above.
o Single physical bus: The same IP address as for the First IP Address must be entered.
o Dual physical bus: Enter the second of the 2 IP addresses.
• Application Server First Multicast Address: Addresses must be entered to enable multicast
communication with Application Servers. Multicast is required for online upgrades of the Application Server.
The following configurations are possible.
o Single physical bus: Only one Multicast address for the Application Server is required. Enter this
address.
o Dual physical bus: Two Multicast addresses for the Application Server are required. Enter the first of
these addresses.

In a Multi Unit, ensure that the Multicast address for Application Server of the Local Unit is entered.

• Application Server Second Multicast Address: Refer to First Multicast Address above.
o Single physical bus: The same Multicast address as for the First Multicast Address must be entered.
o Dual physical bus: Enter the second of the 2 Multicast addresses.
• First NTP IP Address: The IP address for the Network Time Protocol Server.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 193 of 313
LKZ:DE AL:N ECCN:4E992

• Second NTP IP Address: The second IP address for the Network Time Protocol Server (when 2 are
available).
• First S7-Station IP Address: The first IP Address configured for the S7 CP.
• Second S7-Station IP Address: The second IP Address configured for the S7 CP.
• First Router IP Address: When the NTP server is not in the same network and is connected via a router.
The IP Address for the router must be entered.
• Second Router IP Address: As described for First Router IP Address. This is for the second Router IP
Address (when 2 are available).
• First S7-Station MAC Address: The MAC address assigned to the first S7 CP. This is visible on a label on
the module.
• Second S7-Station MAC Address: The MAC address assigned to the second S7 CP. This is visible on a
label on the module.
• Subnet-Mask: Specifies the Ethernet sub net.
• Base Cycle (ms): Base cycle time for the container, in msec. Typical values for a Runtime Container are in
the range of 16 .. 1000 msec.
• Failsafe Cycle 1 (ms) and Failsafe Cycle 2 (ms): These settings are only visible when a Failsafe Runtime
Container is being created (e.g. CPU type 417-FH). Typically one cycle time is set to a lower value for binary
logic. The other cycle time will be set to a higher value for analog logic.

4.5.2.2.2 Expert Properties

The Expert Properties contains settings used for creating an S7 Runtime Container. The settings can be viewed but
not edited. The settings are described below:

• Telegram Length: The telegram length for communication between the S7 CPU and the Application Server.
• Time Out (ms): The time out (in msec) is the time period the Communication Container uses for monitoring
communication with the S7-CPU when it is expecting a response (e.g. following an operation command). If a
break in communication with the S7-CPU occurs for a period exceeding the S7 time out, all the signals being
received from this S7-CPU will acquire a BAD quality.
• Engineering Channel Time Out (ms): This is the time period the Communication Container uses for
monitoring the communication with the S7-CPU that is used for engineering changes (i.e. when changes are
activated).
• Maximum Forced Ports : The maximum number of Ports (of AFs and proxies running in the S7-CPU) that
can be simultaneously forced.
• Maximum Number of Port Value Subscriptions: The maximum number of dynamic values from the S7-
CPU that can be simultaneously displayed at User Interfaces (excluding alarms and archive values).
• Maximum Count for Acknowledge Alarm Call: The maximum number of alarms that can be automatically
switched into auto acknowledgement mode, per second, from the ASD.
• Lifebeat Time Out (ms): This is the time period the Communication Container uses for monitoring
communication with the S7-CPU. A lifebeat signal that is sent from the S7-CPU for this purpose. Should this
time be exceeded, the Application server assumes that the S7-CPU has stopped and all the signals being
received from this S7-CPU will acquire a BAD quality.

4.5.2.3 Editing Runtime Containers

When a Runtime Container has been created its settings can be edited later, should the need arise.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 194 of 313
LKZ:DE AL:N ECCN:4E992

The Runtime Container will automatically stop and restart after editing, in order to acquire the new settings.

CM Runtime Containers can only be edited in the Administration Console.

In S7 Runtime Containers, only the editing peer-to-peer connections button is enabled.

To edit the settings of an existing Runtime Container proceed as follows:

The Project View is open.

1. Select the Admin menu, then Runtime Container , then Edit from the drop down menus.
2. The Select Runtime Container dialog box will appear.

1. Select the Runtime Container to be edited from the drop down list.
2. Click on Edit to edit the Runtime Container settings, otherwise click on Cancel.
3. The Edit Runtime Container dialog box for the selected container will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 195 of 313
LKZ:DE AL:N ECCN:4E992

4. The Runtime Container Settings can now be edited. These settings are described under creating Runtime
Containers.

Some settings for Management Containers are grayed out, and cannot be edited.

The Base Cycle of Management Containers can be edited. Typical values for a Management
Container are in the range of 500 .. 5000 msec.

5. Click on Save to save the new Runtime Container settings, otherwise click on Cancel.
6. A warning will appear to inform the user that the Runtime Container will be automatically stopped and re-
started in order to acquire the new settings. Click on Ok to go ahead and re-start the Runtime Container,
otherwise click on Cancel to return to the Edit Runtime Container dialog box.

The Runtime Container will be stopped and re-started automatically, and the new settings will come into effect.

4.5.2.4 Deleting Runtime Containers

When a Runtime Container is no longer required, it can be deleted.

To delete an existing Runtime Container proceed as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 196 of 313
LKZ:DE AL:N ECCN:4E992

A Runtime Container must be empty (i.e. have no Function Diagrams assigned to it) before it can be deleted.

No uncommitted changes may exist in the project when a Runtime Container is deleted.

Deleting Failsafe and FM458 containers requires some special steps. These are described in the section
Deleting Spezialized S7 Runtime Containers.

The Project View is open.

1. Select the Admin menu, then Runtime Container , then Delete from the drop down menus.
2. The Delete Runtime Container dialog box will appear.

3. Select the Runtime Container to be deleted from the drop down list.

Management Containers cannot be deleted.

CM Runtime Containers are deleted by removing the host, using the administration console.

4. Click on Delete to delete the Runtime Container, otherwise click on Cancel.

The Runtime Container will be deleted.

4.5.2.4.1 Deleting Specialized S7 Runtime Containers

When a Fail-safe Runtime Container or an FM458 Container is no longer required, it can be deleted.

Deleting Fail-safe and FM458 containers requires some special steps for preparation. Proceed as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 197 of 313
LKZ:DE AL:N ECCN:4E992

A Runtime Container must be empty (i.e. have no Function Diagrams assigned to it) before it can be deleted.

The Project View is open.

Only one user at a time may delete specialized S7 Runtime Containers.

1. Deactivate the Specialized S7 Runtime Container.

2. To empty the Specialized S7 Runtime Container, click on compile and download. For FM-Containers follow
the procedure described in FM 458 Transaction Handling, for Fail-safe it is described in F-System
Transaction Handling.
3. Disconnect the Specialized S7 Runtime Container.
4. Deactivate the corresponding S7 Container.
5. Disconnect this corresponding S7 Container.
6. Deassign the Specialized S7 Runtime Container Node by assigning it to None.

Now the Specialized S7 Runtime Container and its corresponding S7 Container can be deleted.

Proceed as follows:

1. Select the Admin menu, then Runtime Container , then Delete from the drop down menus.
2. The Delete Runtime Container dialog box will appear.

3. Select the Specialized S7 Runtime Container to be deleted from the drop down list.
4. Click on Delete.
5. The Information dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 198 of 313
LKZ:DE AL:N ECCN:4E992

6. Click on Yes. Otherwise click on No.

The Runtime Container will be deleted immediately.
7. Delete the corresponding S7 Container.

The specialized S7 Runtime Container is deleted.

4.5.2.5 Peer-to-Peer Connections

When creating an S7 Runtime Container, the required peer-to-peer connections must be defined. Peer-to-peer
connections are the connections that are made between one S7 Runtime Container and a second Runtime Container
(S7, CM, or Runtime Container). The maximum number of peer-to-peer connections are as follows:

Peer-to-Peer Connections Number Configurable

S7 RTC to S7 RTC 30 Maximum
S7 RTC to CM RTC (Total)
S7 RTC to RTC 1 Maximum
Total 31 Maximum

The frequency of peer-to-peer communication and the amount of signals to be exchanged can be configured and
optimized if required. This feature is of particular interest for very large system installations.

CPU 414-3 and CPU 414-H are restricted to 10+1 peer-to-peer connections.

A maximum of 500 data points (each direction) per S7/S7 and S7/CM peer-to-peer connections.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 199 of 313
LKZ:DE AL:N ECCN:4E992

For S7 to CM peer-to-peer connections, only CPU 417-H, CPU 417-4, CPU 417-F and CPU 414-HPG are
supported.

S7 time stamps are not transferred to other S7 RTCs or CM RTCs.

The process to create peer-to-peer connections, edit parameters of existing peer-to-peer connections, and deleting
peer-to-peer connections are described separately.

Each CM counts towards the limit of the maximum number of S7 per unit.

4.5.2.5.1 Create New Peer-to-Peer Connections

To create the new peer-to-peer connections for an S7 CPU, proceed as follows:

The Create S7 Runtime Container dialog box is open.

1. Click on Edit on the right hand side of the Peer-to-Peer Connections field.
2. The Peer to Peer Connections dialog box will open:

3. The Runtime Containers that may be connected are listed in the dialog box. The following settings can be
made for each S7 Runtime Container:
o Connectable: Tick the box if a peer-to-peer connection is to be made. Any such peer-to-peer
connection is bidirectional.
o Send Cycle (ms): The intervals at which peer-to-peer communication is carried out to the connected
S7 CPU.
o Maximum Signals: The maximum amount of signals that may be sent via the connection.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 200 of 313
LKZ:DE AL:N ECCN:4E992

The contents of the dialog box can be exported or printed.

4. Click on Save to accept the settings, otherwise click on Cancel.

5. A dialog box reports on the progress of the action.
6. The Update S7 Runtime Container Result dialog box will appear. The Open Protocol button will open a
Protocol Report Browser. Click on OK to close the dialog box.

The Function Diagrams with the peer-to-peer connections can now be assigned to Runtime
Containers and activated, but the signals will not be transferred between them.

7. To determine which steps are required to actualize the changes in the S7, open the S7 Hardware
Configuration States dialog box.
8. Typically the S7 Hardware Configuration and Load S7 Connections functions are required. Perform these
tasks.
9. If one of the peer-to-peer partners is a CM RTC, the following steps are required to actualize the changes in
the CM:

Disconnecting or Reconnecting a Runtime Container is not a commonplace activity, and is not

recommended at a running plant.

Refer to the description of implications.

1. Disconnect the CM Runtime Containers.

2. Reconnect the CM Runtime Containers.

The peer-to-peer connections are created and actualized.

Once the peer-to-peer connection between two Runtime Containers has been established, additional Function
Diagrams can be added and activated without additional steps up until the configured maximum signal limit.

4.5.2.5.2 Editing Existing Peer-to-Peer Connections

To edit existing peer-to-peer connections for an S7 CPU, proceed as follows:

The Create S7 Runtime Container dialog box is open.

1. Click on Edit on the right hand side of the Peer-to-Peer Connections field.
2. The Peer to Peer Connections dialog box will open:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 201 of 313
LKZ:DE AL:N ECCN:4E992

3. The following parameters of the connected Runtime Containers can be edited:

o Send Cycle (ms): The intervals at which peer-to-peer communication is carried out to the connected
S7 CPU.
o Maximum Signals: The maximum amount of signals that may be sent via the connection.

Do not select or deselect the Connectable check box. That would create a new or delete an existing
peer-to-peer connection instead. Those processes are described separately.

4. Click in the white fields to edit the parameters. Gray fields are not editable.

The contents of the dialog box can be exported or printed.

5. Click on Save to accept the settings, otherwise click on Cancel.

6. A dialog box reports on the progress of the action.
7. The Update S7 Runtime Container Result dialog box will appear. The Open Protocol button will open a
Protocol Report Browser. Click on OK to close the dialog box.
8. To actualize the changes in the peer-to-peer partners, the affected S7 and CM Runtime Containers must be
disconnected and reconnected:

Disconnecting or Reconnecting a Runtime Container is not a commonplace activity, and is not

recommended at a running plant.

Refer to the description of implications.

1. Disconnect the S7 and CM Runtime Containers.

2. Reconnect the S7 and CM Runtime Containers.

The peer-to-peer connection parameter changes are actualized.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 202 of 313
LKZ:DE AL:N ECCN:4E992

4.5.2.5.3 Deleting Peer-to-Peer Connections

To delete peer-to-peer connections for an S7 CPU, proceed as follows:

Before the peer-to-peer connections can be deleted, the affected function diagrams must be deassigned from
the Runtime Containers. This is done by assigning the diagrams to none.

The Create S7 Runtime Container dialog box is open.

1. Click on Edit on the right hand side of the Peer-to-Peer Connections field.
2. The Peer to Peer Connections dialog box will open:

3. Delete the peer-to-peer connection by deselecting the Connectable check box.

The contents of the dialog box can be exported or printed.

4. Click on Save to accept the settings, otherwise click on Cancel.

5. A dialog box reports on the progress of the action.
6. The Update S7 Runtime Container Result dialog box will appear. The Open Protocol button will open a
Protocol Report Browser. Click on OK to close the dialog box.
7. To determine which steps are required to actualize the changes in the S7, open the S7 Hardware
Configuration States dialog box.
8. Typically the S7 Hardware Configuration and Load S7 Connections functions are required. Perform these
tasks.
9. If one of the peer-to-peer partners is a CM RTC, the following steps are required to actualize the changes in
the CM:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 203 of 313
LKZ:DE AL:N ECCN:4E992

Disconnecting or Reconnecting a Runtime Container is not a commonplace activity, and is not

recommended at a running plant.

Refer to the description of implications.

1. Disconnect the CM Runtime Containers.

2. Reconnect the CM Runtime Containers.

The peer-to-peer connection is deleted.

4.5.2.6 Starting or Stopping Runtime Containers

A Runtime Container can be started or stopped. When a Runtime Container is running, it is executing the Automation
Functions and proxies in the Function Diagrams that are assigned to it. When a Runtime Container is stopped, its is
not executing at all, and all signals leaving the container acquire a BAD quality.

S7 Runtime Containers can't be started or stopped with this function. To start or stop an S7 Runtime Container
use the Start S7 Station or Stop S7 Station functions.

Take any precautions that may be necessary when starting or stopping a Runtime Container. Many functions
may be assigned to the Runtime Container, and these will be stopped or started with the Runtime Container.

Starting a Runtime Container

To start a Runtime Container, proceed as follows:

The Project View is open.

1. Select the Admin menu, then Runtime Container , then Start from the drop down menus.
2. The Start Runtime Container dialog box will open.

3. Select the Runtime Container to be started from the drop down list.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 204 of 313
LKZ:DE AL:N ECCN:4E992

4. Click on Start to start the Runtime Container, otherwise click on Cancel.

The Runtime Container will be started, the status of the Runtime Container can then be viewed in the diagnostic
system.

Stopping a Runtime Container

To stop a Runtime Container, proceed as follows:

The Project View is open.

1. Select the Admin menu, then Runtime Container , and then Stop from the drop down menus.
2. The Stop Runtime Container dialog box will open.

3. Select the Runtime Container to be stopped from the drop down list.
4. Click on Stop to stop the Runtime Container, otherwise click on Cancel.

The Runtime Container will be stopped, the status of the Runtime Container can then be viewed in the diagnostic
system.

A stopped container will remain stopped, even if the SPPA-T3000 system is restarted.

4.5.2.7 Starting or Stopping S7 Stations

An S7 CPU can be started or stopped from the Workbench, by using the functions Start S7 Stations or Stop S7
Stations.

An S7 Runtime Container, in a running S7 CPU, executes the Automation Functions and the S7 Hardware
Proxies in the Function Diagrams that are assigned to it.

In a redundant configuration, the user can start/stop only one of the redundant S7 CPUs at a time. If an S7 Station of a
redundant S7 CPU configuration is stopped, e.g. Master, then the other one, e.g. Slave, will take over. The S7
Runtime Container continues executing, though all the signals referring to the Stopped S7 Station acquire BAD quality.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 205 of 313
LKZ:DE AL:N ECCN:4E992

If the user stops a nonredundant S7 Station, or both S7 Stations of a redundant pair, then the corresponding
S7 Runtime Container will also be stopped. All the signals will acquire BAD quality.

Starting an S7 Station

To start an S7 CPU, proceed as follows:

The Project View is open.

1. Select the Edit menu, then S7, then Start S7 Station from the drop down menus.
2. The Start S7 Station dialog box will open.

3. Select the Runtime Container from the drop down list.

4. In the case of a redundant S7 CPU, select the Rack number from the drop down list.
5. Click on Start to continue, otherwise click on Cancel.
6. A dialog box appears. Click on Yes in order to confirm the start of the S7 CPU.

The S7 CPU located in the selected rack will be started.

The status of the S7 Runtime Container and the quality of the signals leaving the S7 Runtime Container can be viewed
in the Diagnostic View.

Stopping an S7 Station

To stop an S7 CPU, proceed as follows:

The Project View is open.

1. Select the Edit menu, then S7, then Stop S7 Station from the drop down menus.
2. The Stop S7 Station dialog box will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 206 of 313
LKZ:DE AL:N ECCN:4E992

3. Select the Runtime Container from the drop down list.

4. In the case of a redundant S7 CPU, select the Rack number from the drop down list.
5. Click on Stop to continue, otherwise click on Cancel.
6. A dialog box appears. Click on Yes in order to confirm the stop of the S7 CPU.

The S7 CPU located in the selected rack will be stopped.

The status of the S7 Runtime Container and the quality of the signals leaving the S7 Runtime Container can be viewed
in the Diagnostic View.

Alternatively, the Start S7 Station or Stop S7 Station can be handled from the context menu in the S7
Hardware Configuration States Documentation dialog box (Right Mouse Click > Start S7 station or Stop S7
Station).

4.5.2.8 Loading an S7 Execution Frame

When an S7 Runtime Container has been created, the execution frame must be downloaded to the S7 CPU. The
Execution Frame is an S7 program that implements the engineering and communication interfaces of the S7 Runtime
Container.

The S7-CPU will be stopped by execution of Load S7 Execution Frame .

To load the Execution Frame for a CPU, proceed as follows:

The Project View is open.

Only one user at a time may load an Execution Frame.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 207 of 313
LKZ:DE AL:N ECCN:4E992

1. Select Edit, then S7, then Load S7 Execution Frame from the drop down menus.
The Load S7 Execution Frame dialog box will open.

2. Select the Runtime Container to be loaded from the drop down list.
3. Click on Load
The first CPU will be stopped for loading the configuration. If the download was successful, the CPU will
automatically restart. The second CPU will now be stopped and configured and started again.
4. The Load S7 Execution Frame Result box will open.
For further information click on Open Protocol.

If the restart didn't function automatically a disconnect/ reconnect has to be executed.

The Execution Frame is now downloaded into the S7-CPU System.

4.5.2.9 List S7 Block Versions

A list of blocks loaded on each S7 Runtime Container, with version information, can be viewed. The blocks were
loaded into the S7 Runtime Container either through the Load S7 Execution Frame function or through a block
upgrade.

The information provided to support Siemens SPPA-T3000 experts. The block information is not needed
for engineering or operation purposes.

To view a list of the blocks contained in the S7 Runtime Container, proceed as follows:

The Project View is open.

1. Select Edit, then S7, then List S7 Block Versions from the drop down menus.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 208 of 313
LKZ:DE AL:N ECCN:4E992

The List S7 Block Versions dialog box will open.

2. Select the Runtime Container for which the blocks will be listed.
3. Click on List.
The List S7 Block Versions Result dialog will open.

4. Click on Open Protocol. A window with a list of the blocks contained in the selected S7 Runtime Container
will open .

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 209 of 313
LKZ:DE AL:N ECCN:4E992

5. Click on OK of the List S7 Block Versions Result dialog to exit the function.

4.5.3 Assigning Function Diagrams to Runtime Containers

All Function Diagrams must be assigned to Runtime Containers. Runtime Containers provide the execution
environment for the Automation Functions and proxies contained in the Function Diagrams. Since the assignment is
made for each diagram, all the logic within a Function Diagram will be assigned to the same Runtime Container. A
project may consist of several Runtime Containers, and the Function Diagrams should be carefully assigned to them.

Assigning Project Nodes

Project Nodes are also assigned to Runtime Containers. Although Project Nodes contain no logic that will execute in
the Runtime Container, this is useful because of the inheritance functionality in the Project Hierarchy.

• When new Function Diagrams are created, they are automatically assigned to the same Runtime Container
as their superordinate Project Node.
• When a Project Node is assigned to a Runtime Container all subordinate nodes and Function Diagrams are
automatically assigned to the same Runtime Container, except:
o If a subordinate node or diagram has previously been assigned individually, the user is given the
choice to either retain or overwrite this assignment.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 210 of 313
LKZ:DE AL:N ECCN:4E992

Assignment Considerations

It is recommended to assign complete Project Nodes to Runtime Containers rather than individual diagrams. In this
way the assignment is clearer and easier to understand.

Furthermore, if the Project Hierarchy is arranged with the plant areas divided into Project Nodes, then assigning
complete Project Nodes to the Runtime Containers has other advantages:

• Functional Distribution: Reliability is enhanced by assigning functionally dependant controls to the same
Runtime Containers.
• Signal Interchange: Communication is optimized when functionally dependant controls are executed in the
same Runtime Container.

Other factors to consider are:

• If the execution sequence of any logic or Function Diagrams is to be set manually, the logic or Function
Diagrams must all be assigned to the same Runtime Container.
• The execution cycle time required. Each Runtime Container is assigned a base cycle time. If, for instance,
some logic requires a very quick cycle time, it may be beneficial to assign this logic to its own Runtime
Container.

The assignment should be considered early on in the project, since diagrams can only be reassigned to other Runtime
Containers when they are deactivated. It is easier to assign to Runtime Containers early on, than to change the
assignment later.

Management Containers

Function Diagrams containing Management Proxies must be assigned to Management Containers. Each server in an
installation will have one Management Container allocated to it.

Making a Null Assignment

It is possible to make a null assignment, this means that no assignment to any Runtime Container is made. This
assignment may be useful in some situations, for example early on in the engineering phase, before any Runtime
Containers have been created.

When blocks are placed in a Function Diagram that has a null assignment, no checks can be made to ensure that the
block is appropriate for the Runtime Container assignment. Users must therefore ensure that the blocks placed in
these Function Diagrams are all appropriate for an eventual Runtime Container assignment.

How to Assign Project Nodes and Function Diagrams to Runtime Containers

The Project View is open.

When diagrams are assigned to Runtime Containers, they may not contain any uncommitted or active data.

Prior to assigning to the Runtime Container the diagrams must be committed and deactivated.

1. Select the Project Node or diagram to be assigned in the Tree View or List View.
2. Select the Edit menu, then Assign Runtime Container from the drop down menu.
3. The Set Runtime Container Assignment dialog box appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 211 of 313
LKZ:DE AL:N ECCN:4E992

4. Select Runtime Container to be assigned from the Runtime Container Assignment drop down list.

Select <None> from the list to make a Null assignment.

5. To assign to the Runtime Container click on Save, otherwise to leave it unchanged click on Cancel.
If the assignment is being made for a Project Node that contains other nodes or diagrams that have been
previously assigned individually, proceed as follows:
1. A dialog box will appear informing the user which nodes or diagrams have been explicitly assigned
previously.

2. To overwrite the existing assignments click on Yes, to retain these existing assignments click on No,
otherwise click on Cancel to return to the Set Runtime Container Assignment dialog box.

The contents of the dialog box can be printed.

The Project Node or diagram will now be assigned to the Runtime Container.

Alternatively, select the function via the context menu (Right Mouse Click > Assign Runtime Container ).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 212 of 313
LKZ:DE AL:N ECCN:4E992

4.5.4 Setting the Cycle Time

The Automation Functions running in a Runtime Container have time controlled program cycles. This means that an
Automation Function in the control logic will execute regularly at an interval which can be adjusted by the user.

The program cycle in a Runtime Container has a base cycle time configured this is the shortest cycle time possible. In
some applications a fast cycle time is not necessary, for example a temperature control loop may have a very slow
response. In these cases it is possible to assign a longer cycle time to these functions and thereby optimize the overall
cyclic loading of the Runtime Container.

The cycle time need not be the same for all AF Blocks within the same Function Diagram. The cycle time is assigned
as a multiple of the base cycle time.

The cycle time can be set for:

• Project Nodes, or.

• Complete Function Diagrams, or.
• Individual AF Blocks.

Cycle Time Settings

The cycle time set is a multiple of the the base cycle time that was set during the Runtime Container creation. Eight
multiples of the base cycle time can be selected when setting the cycle time, i.e.

Cycle Time = Base Cycle Time * n (where n = 1..8)

The following are exceptions to this rule:

Runtime Container Type Exception

S7 Turbine Control Only 5 multiples are available (i.e. n = 1..5).
(FM458)
S7 Runtime Containers Only 2 multiples are available (i.e. n = 1..2).
CPU 414
S7 Fail Safe Only 2 cycle times can be selected. These are the 2 Fail Safe cycle times which were set
during creation of the Fail Safe Runtime Container.

4.5.4.1 Setting the Cycle Time at the Project Node Level

The cycle time for Project Nodes can be set. Using this function, the cycle times of existing Function Diagrams within
the Node and all subordinate Nodes will not be changed. Instead the default setting for all subsequent Function
Diagrams that are placed in the Node and subordinate Nodes will be set to this cycle time. This function also affects
the creation of all future subordinate Project Nodes (and their Function Diagrams) within the hierarchy.

The cycle time for a Project Node is set as follows:

The Project View is open.

1. Select the Project Node in the Tree View or List View.

2. Select the Edit menu, then Set Cycle Time from the drop down menu.
3. The Set Cycle Time dialog box appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 213 of 313
LKZ:DE AL:N ECCN:4E992

4. To change the cycle time, select the time from the AF Cycle Time (ms) from those available in the drop down
list.
5. To change the cycle time click on Save, otherwise to leave it unchanged click on Cancel.
If the assignment is being made for a Project Node that contains other nodes that have been previously
assigned individually, proceed as follows:
1. A dialog box will appear informing the user which nodes have been explicitly assigned previously.

The contents of the dialog box can be printed.

2. To overwrite the existing assignments click on Yes, to retain these existing assignments click on No,
otherwise click on Cancel to return to the Set Cycle Time dialog box.

The cycle time for the Project Node will be set.

The cycle time of Function Diagrams can be changed individually in the Project View or with spreadsheet
engineering.

4.5.4.2 Setting the Function Diagram Cycle Time

The cycle time for individual Function Diagrams can be set. Using this function, the cycle times of existing AF Blocks
within the diagram will NOT be changed, but the default setting for all subsequent AF Blocks that are placed in the
diagram will be set.

The cycle time for a Function Diagram is set as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 214 of 313
LKZ:DE AL:N ECCN:4E992

The Project View is open.

1. Select the Function Diagram in the Tree View or List View.

2. Select the Edit menu, then Set Cycle Time from the drop down menu.
3. The Set Cycle Time dialog box appears.

4. To change the cycle time, select the time from the AF Cycle Time (ms) from those available drop down list.
5. Click on Save to change the cycle time, otherwise to leave it unchanged click on Cancel.

The cycle time for the Function Diagram will be set.

4.5.4.3 Setting the AF Block Cycle Time

The cycle times for AF Blocks within a Function Diagram can be set. This function can be carried out for either
individual, or multiple AF Blocks.

The cycle time for AF Blocks is set as follows:

A diagram is open in the diagram editor.

1. Select the AF Block/s for which the cycle time is to be set.

2. Select the Edit menu, then Set Cycle Time from the drop down menu.
3. The Set Cycle Time dialog box appears.

4. To change the cycle time, select the time from the AF Cycle Time (ms) from those available in the drop down
list.
5. Click on Save to change the cycle time, otherwise to leave it unchanged click on Cancel.

The cycle time for the AF Block/s will be set.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 215 of 313
LKZ:DE AL:N ECCN:4E992

Alternatively, select the function via the context menu (Right Mouse Click > Set Cycle Time).

4.5.4.4 FUM Cycle Time Rules

The cycle time of each IM616 Hardware Proxy, FUM Hardware Proxy and FUM Automation Function must be set
according to the following rules:

• FUM Automation Functions (e.g. FUM_ASMON, FUM_BSMON) must be assigned in the same cycle time or
in a faster (shorter) cycle time as the FUM Hardware Proxy (e.g. FUM230AT) they are connected to.
• FUM Hardware Proxies (e.g. FUM230AT) must be assigned in the same cycle time or in a faster (shorter)
cycle time as the IM 616 Hardware Proxy (IM616) they are connected to.

All FUM Hardware Proxies and Automation Functions connected to an IM 616 Hardware Proxy must be
assigned to the same S7 Runtime Container.

4.5.5 Execution Sequence

Function Diagrams containing logic components (e.g. Automation Functions and Proxies) are assigned to Runtime
Containers, this logic will be executed in the program cycle of the Runtime Container in a particular sequence or order.
This sequence occurs as follows:

• The Function Diagrams are executed in sequence.

• As each Function Diagram is executed, the logic components within the diagram are processed, in a
particular order also.

Function Diagram Sequence

The Function Diagrams within a Runtime Container are executed in an assigned sequence.

This is represented schematically as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 216 of 313
LKZ:DE AL:N ECCN:4E992

A number of Function Diagrams (1,2,3 .. n) have been allocated to a Runtime Container and are being executed.
The sequence of execution is predetermined, first the Function Diagram 1 is processed. All the logic within the
Function Diagram is processed, when this is complete the sequence moves on to the next Function Diagram.

The order is Function Diagram 2,3 and then all the other Function Diagrams assigned to the Runtime Container are
processed individually until the last Function Diagram n is processed. The cycle then begins at Function Diagram 1
again.

Component Sequence

The components within a Function Diagram are also executed in a particular sequence. This is represented
schematically as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 217 of 313
LKZ:DE AL:N ECCN:4E992

A Function Diagram containing components (e.g. Automation Functions and Proxies) is represented. Each component
in the diagram is executed in an assigned sequence, this sequence is represented here by a number in the block
(blocks 1..6). Once the sequence is complete and all blocks have been processed, the processing of that Function
Diagram will be complete, and the next Function Diagram will then be processed.

The execution sequence within a Function Diagram can be viewed using the Show Sequence Number function in the
Diagram Editor.

Scheduling of the Execution Sequence

The execution sequence of Function Diagrams and components is determined by scheduling. Scheduling can be
performed in two ways:

• Automatic scheduling: This is carried out by the system.

• Manual scheduling: In some cases the user may wish to manually schedule the execution sequence.

Automatic scheduling of the execution sequence is normally sufficient in the majority of cases.

Macros

Macros in Function Diagrams are scheduled in exactly the same way as other components. The only difference is that
Macros are assigned a range of sequence numbers (i.e. one for every component contained in the Macro).

The scheduling of components within a Macro itself is performed in the same way as for an individual Function
Diagram.

4.5.5.1 Automatic Scheduling

The principle of the automatic scheduling of the execution sequence, is that the sequence occurs in the direction of
signal flow. If one AF Block is the source of a signal going to a destination at another AF Block, then the AF Block at
the signal source will be processed before the AF Block at the signal destination.

This principle is shown in the schematic diagram below:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 218 of 313
LKZ:DE AL:N ECCN:4E992

In each case the block sourcing a signal is executed before the block at the signal destination.

The same principle is applied for the automatic scheduling of the Function Diagram sequence (i.e. diagrams with
signal sources for other diagrams are processed first).

4.5.5.2 Manual Scheduling

When is Manual Scheduling Necessary?

Automatic scheduling is sufficient in the majority of cases, and provides efficient and consistent scheduling of diagrams
and components.

In some cases, it is possible that the execution sequence of logic can effect the functioning of that logic.
Interconnected logic can sometimes produce different results, depending on the sequence in which its components are
executed. An example of this problem is with sequential logic i.e. binary logic with some form of internal feedback (or
memory).

It is therefore, sometimes necessary to manually schedule the execution sequence, in order to ensure predictable
operation of logic. This is not normally a commonplace activity, and need only be done if the user considers it is really
necessary.

Hardware and Management Proxies are scheduled automatically by the system. These Proxies cannot be
scheduled manually by the user.

How Manual Scheduling is Implemented

Manual scheduling can be implemented for both types of scheduling:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 219 of 313
LKZ:DE AL:N ECCN:4E992

• Manual component scheduling for manually scheduling the execution sequence of Automation Functions and
Macros within a Function Diagram.
• Manual diagram scheduling for manually scheduling the execution sequence of Function Diagrams within a
Runtime Container.

4.5.5.2.1 Component Scheduling

Manual Component Scheduling is carried out for components within Function Diagrams.

In order for manual component scheduling to be carried out, manual scheduling has to be switched on for the diagram.
The manual scheduling is set using a scheduling table for the diagram. Once scheduling changes have been made,
they have to be activated, and the changes will come into effect.

The manual component scheduling for a diagram can be switched off, in which case automatic scheduling for the
diagram will be reinstated.

4.5.5.2.1.1 Switching Component Scheduling On and Off

Manual scheduling can be switched on or off for a Function Diagram.

• When manual scheduling is switched on, the manual scheduling of all the components within the diagram can
be set by the user.
• When manual scheduling is switched off, the components within the diagram will be automatically scheduled
by the system.

To switch manual scheduling on or off for a Function Diagram, proceed as follows:

The Function diagram is open in the Diagram Editor.

• Select the Extras menu, then Manual Scheduling from the drop down menu.

Manual scheduling for the diagram will now toggle to either on or off.

When manual scheduling is switched on for the diagram, the Manual Scheduling menu item is ticked.

4.5.5.2.1.2 Setting Component Scheduling

The scheduling of components in a Function Diagram is viewed and set using the manual scheduling table.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 220 of 313
LKZ:DE AL:N ECCN:4E992

Manual scheduling has to be switched on for a diagram, before its components can be manually scheduled.

The manual scheduling table is described below, and then the way in which components are scheduled using the
table.

The Manual Scheduling Table

To open the manual scheduling table for a Function Diagram, proceed as follows:

A Function Diagram is open in the Diagram Editor.

1. Select the Extras menu, then Open Scheduling Table from the drop down menu.
2. The Manual Component Scheduling dialog box will open docked on the left hand side of the Diagram Editor
Work Area. The dialog box contains the manual scheduling table for the components in the diagram.

When the dialog box is docked some buttons will not be visible. To make the buttons visible the
dialog box must be undocked in the Diagram Editor.

o The dialog box is split into 2 Frames, the contents of the Frames are identical. The Frames are
designed to facilitate the easy handling of component scheduling, even when the diagram contains many
components.
The upper Frame can be sorted according to any of the columns, by clicking on the column header.
The lower Frame is always sorted in order of the sequence number in the Seq column.
o Each row in the table represents a single component in the diagram. Click on a row to select it, and
the component will be automatically selected in the Function Diagram in the Diagram Editor. If a component
in the diagram is selected, the corresponding row in the table will also be selected automatically.
o The sequence number of each component is shown in the Seq column.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 221 of 313
LKZ:DE AL:N ECCN:4E992

o All components that have been manually scheduled, are indicated by a tick in the box, in the Man
column. This also applies to diagrams that have a scheduling rule assigned as a result of freezing the
diagram.
o When the manual scheduling has been activated, the cell in the Man column will have a blue
background. If the table contains any unactivated changes, the cells have a black background.

If the table contains any unactivated changes, a warning icon appears at the bottom of the dialog box.

The contents of the dialog box can be exported or printed.

Setting the Scheduling

Manual component scheduling can be set using the manual scheduling table. The scheduling of any single component
can be changed, by changing the position of the component in the table. The component is dragged from its current
position in the sequence, and dropped into a new position. Proceed as follows:

The Manual Scheduling Table for the diagram is open.

1. To select the component to be rescheduled, position the cursor over the component in the upper Frame in the
dialog box, then press and hold the left mouse button.

2. Continue to hold the mouse button and drag the component towards its new position in the list in the lower
Frame in the dialog box.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 222 of 313
LKZ:DE AL:N ECCN:4E992

3. With the cursor positioned over the new position, release the mouse button. The dragged component will be
scheduled immediately before this position in the sequence.

Alternatively, the setting can be performed by dragging and dropping components within the lower Frame.

Click on Apply to save the changes, or click on Save to save the changes and close the dialog box. Otherwise click on
Cancel.

The new scheduling has to be activated in order for it to come into effect.

4.5.5.2.1.3 Activating Component Scheduling

Changes which have been made to the manual scheduling of components in a Function Diagram, are implemented in
the system via the transaction handling process.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 223 of 313
LKZ:DE AL:N ECCN:4E992

Prior to activating manual component scheduling, all Function Diagrams must first be committed.

Component scheduling can be activated in two ways:

• All changes can be activated.

• Individual Function Diagrams can be activated.

Activated components have a special appearance in Function Diagrams.

When activating diagrams the changes become active immediately, there is no waiting time for a transfer of
code. Ensure that any necessary precautions have been taken prior to activating e.g. informing operating staff
of the change.

When a user activates changes in a multi-user environment, any scheduling changes committed by other
users will then also be activated.

Activating All Changes

When a Function Diagram is activated (as normal) from the Project View, then any manual component scheduling
contained in the diagram is also activated (along with any other logic changes in the diagram).

Activating Component Scheduling Within Individual Function Diagrams

The manual component scheduling within a diagram can be activated, without activating any other changes. When the
activation is carried out this way, only the manual component scheduling will be activated (and no other changes to
the diagram).

To activate the manual scheduling of components from the Diagram Editor proceed as follows:

A Function Diagram is open in the Diagram Editor.

• Select the Extras menu, then Activate Scheduling from the drop down menu.

The manual scheduling for the Function Diagram will be activated.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 224 of 313
LKZ:DE AL:N ECCN:4E992

Alternatively, the internal diagram scheduling can be activated from the Project View:

Select the Function Diagram in the List View.

Select the Edit menu, then Manual Scheduling, then Activate Internal Diagram Scheduling from the drop
down menu.

Symbol Appearance

Components which have been manually scheduled and activated have a special appearance in the Diagram Editor.
The sequence number of the component will appear with a red frame around it.

4.5.5.2.1.4 Modifying Components

Function Diagrams that are manually scheduled can be freely modified. When components are added to, or deleted
from the diagram the manual scheduling is affected.

Deleting Components

When components are deleted from a manually scheduled Function Diagram, they are simply removed from the
sequence.

For example, in the sequence:

A > B > C > D, component C is deleted.

The new sequence will be:

A > B > D

Adding Components

When new components are added to a manually scheduled Function Diagram, they are scheduled automatically.
These new components can also be manually scheduled if required.

4.5.5.2.2 Diagram Scheduling

Manual Component Scheduling is carried out for diagrams within a Runtime Container. Manual diagram scheduling is
set using a manual scheduling table for the Runtime Container.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 225 of 313
LKZ:DE AL:N ECCN:4E992

Once scheduling changes have been made, the changes must be activated before they will come into effect.

4.5.5.2.2.1 Setting Diagram Scheduling

Diagram scheduling within a Runtime Container is viewed and set using the manual scheduling table. The manual
scheduling table is explained below, and then the way in which diagrams are scheduled using the table.

Opening the Manual Scheduling Table

To open the manual scheduling table for a Runtime Container proceed as follows:

The Project View is open.

1. Select the Edit menu, then Manual Scheduling, then Open Scheduling Table from the drop down menus.
2. The Select Runtime Container dialog box will open.

3. Select the Runtime Container from the drop down list.

4. Manual Scheduling can be switched on or off for the Runtime Container. Switch manual scheduling on by
ticking the Manual Schedule check box, or switch it off if required, by removing the tick.
o When manual scheduling is switched on, the manual scheduling of all the Function Diagrams within
the Runtime Container can be set by the user.
o When manual scheduling is switched off, all the Function Diagrams within the Runtime Container
will be automatically scheduled by the system.
5. Click on Calculate, the dialog box will expand and lists all the Function Diagrams assigned to the Runtime
Container.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 226 of 313
LKZ:DE AL:N ECCN:4E992

• The dialog box is split into 2 Frames, the contents of the Frames are identical. This arrangement is made to
assist with scheduling of containers that contain many diagrams.
• The upper Frame can be sorted according to any of the columns, by clicking on the column header. The lower
Frame is always sorted in order of the sequence number in the Seq column.
• Each row in the table represents 1 diagram in the Runtime Container.
• The sequence number of each diagram is shown in the Seq column.
• All diagrams that have been manually scheduled, are indicated by a tick in the box, in the Man column.
• The background color of the Man cells is:
o Black for diagrams with manual scheduling that has not yet been activated.
o Blue for diagrams for which the displayed manual scheduling has been activated.

Imported diagrams may lose their manual scheduling.

The contents of the dialog box can be exported or printed.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 227 of 313
LKZ:DE AL:N ECCN:4E992

Setting the Scheduling

Manual diagram scheduling can be set using the manual scheduling table. The scheduling of any single diagram can
be changed, by changing the position of the diagram in the table. The diagram is dragged from its current position in
the sequence, and dropped into a new position. Proceed as follows:

The Manual Scheduling Table for the Runtime Container is open.

1. To select the diagram to be rescheduled, position the cursor over the diagram in the upper Frame in the
dialog box, then press and hold the left mouse button.

2. Continue to hold the mouse button and drag the diagram towards its new position in the lower Frame in the
dialog box.

3. With the cursor positioned over the new position, release the mouse button. The dragged diagram will be
scheduled immediately before this position in the sequence.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 228 of 313
LKZ:DE AL:N ECCN:4E992

Alternatively, the setting can be performed by dragging and dropping components within the lower Frame.

Click on Apply to make the changes. Otherwise click on Cancel.

The new scheduling has to be activated in order for it to come into effect.

4.5.5.2.2.2 Activating Diagram Scheduling

Changes which have been made to the manual scheduling of Function Diagrams in a Runtime Container are
implemented in the system via the transaction handling process.

Activation of diagram scheduling has its own menu item, and is not activated along with other changes.

After activating, the changes become active immediately, there is no waiting time for a transfer of code.
Ensure that any necessary precautions have been taken prior to activating e.g. informing operating staff of the
change.

When a user activates changes in a multi-user environment, any scheduling changes committed by other
users will then also be activated.

To activate manual diagram scheduling in a Runtime Container, proceed as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 229 of 313
LKZ:DE AL:N ECCN:4E992

Prior to activating manual diagram scheduling, all Function Diagrams must first be committed.

The Project View is open.

1. Select the Edit menu, then Manual Scheduling, then Activate Diagram Scheduling from the drop down
menus.
2. The Activate manually edited Diagram Scheduling dialog box appears.

3. Select the Runtime Container for which the manual diagram scheduling is to be activated, from the drop down
list.
4. Click on Activate to activate the scheduling, otherwise click on Cancel.

The manual diagram scheduling will now be activated in the Runtime Container.

A dialog box will appear, reporting on the results of the activation.

4.5.5.2.2.3 Modifying Diagrams

After the diagrams in a Runtime Container have been manually scheduled, new diagrams can be created, or existing
diagrams can be deleted.

Deleting Diagrams

When diagrams are deleted from a manually scheduled Runtime Container, they are simply removed from the
sequence. The diagrams which existed before and after the deleted diagram in the sequence will now follow each
other.

For example, in the sequence:

A > B > C > D, diagram C is deleted.

The new sequence will be:

A > B > D

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 230 of 313
LKZ:DE AL:N ECCN:4E992

Adding Diagrams

When new diagrams are added to a manually scheduled Runtime Container, they are scheduled automatically. These
new diagrams can be also be manually scheduled if required.

4.5.5.2.2.4 Importing Manually Scheduled Diagrams

Diagrams which have been manually scheduled can be exported from and imported into projects. When this is done
the diagram scheduling is also exported and imported. Any exported diagrams which have a manually set execution
sequence will retain this manual sequence when they have been imported.

There is, however, a special case that must be considered. This case is when the sequence of diagrams is only
partially imported, and the diagram sequence is interrupted.

Interrupted Sequences

A diagram sequence can be interrupted, an example is shown in the picture below:

In this example, diagrams which have been manually scheduled have been exported out of one project, and imported
into another. The complete manually scheduled sequence has not been copied, and the sequence in the new project
has been interrupted. This results in the following situation after the import:

• Diagrams which have been imported with their manual scheduling intact (i.e. the predecessor in the sequence
has also been imported), will remain manually scheduled.
• Diagrams which have imported which are at interruptions (i.e. the predecessor in the sequence has not been
imported), will no longer have manual scheduling.

Identifying Interrupted Sequences

After the import of Function Diagrams which contain an interrupted sequence a warning will appear. The details of the
warning (and the sequence interruption) can be found by clicking on the Open Protocol button to open a protocol
report browser.

Repairing Interrupted Sequences

Interrupted sequences can be repaired by manually scheduling the diagrams which have lost their manual scheduling
during the import. A new predecessor for these diagrams can be set by the user.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 231 of 313
LKZ:DE AL:N ECCN:4E992

4.5.6 Calculation of System Resources

During engineering, the design engineer has to decide, which Function Diagram should be assigned to which Runtime
Container.

To help with this process a function is provided that gives an overview of the CPU-Load of Runtime Containers. In this
way it is possible to optimize the assignment of Function Diagrams to Runtime Containers, and optimize Automation
Server performance.

4.5.6.1 Assigning Application Profiles to Runtime Containers

For calculating the CPU-Load of a Runtime Container there must be an assigned profile.

S7 Runtime Containers have only the default profile.

Proceed as follows:

The Project View is open

1. Select Extras then Assign Application Profile.

2. The Assign Application Profile to Runtime Container dialog box will appear.

3. Choose the profile from the drop down menu.

4. Click on Save to save the selection, otherwise click on Cancel

4.5.6.2 Calculate System Resources

This Function allows the calculation of the CPU-Load of a Runtime Container. This calculation is possible without
activating those Function Diagrams, which are assigned to the Runtime Container. So there is a possibility to check
the availability of resources and to optimize them.

For calculation proceed as follows:

The Project View is open

1. Select the Extra menu, then Calculate System Resources.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 232 of 313
LKZ:DE AL:N ECCN:4E992

2. The Calculate System Resources Dialog box will appear.

3. Choose the Parameters from the drop down menus.

o Server: The Server on which the Runtime Container is running.

All S7 Runtime Containers are listed under the Primary Server.

o Runtime Container : Choose the name of the Runtime Container

o Hierarchy Levels: The levels of the Hierarchy of the detail list.
o Communication Load: This is a reserved storage of the CPU and normally it is 5% of the CPU-
Load if the selection is Low. Five percent is normally enough and is default. So it is not necessary to change
it.
4. For starting the calculation click on Calculate, otherwise click on Cancel.
5. The Calculation Box will appear.

Note the following:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 233 of 313
LKZ:DE AL:N ECCN:4E992

• Highlighting in the color defined in the color table indicates, that the correct calculation is not possible,
because data related to the Automation Function Type is missing.
• A zero in the Used Mem. (%) field signifies, that there is no memory information for the S7-CPU type
available.
• Number of Peer to Peer Destinations informs of the maximum used peer to peer connections of the
Runtime Container.
• Max number of Peer to Peer Connections per Destinations: gives information of the maximum allowed
peer to peer connections per destination.

The applied performance and the used memory is given in percentage for every assigned Project Node and Function
Diagram: available calculated time of the Runtime Container includes overheads and buffers. If 100% is reached, no
more modules can be configured to run on this Runtime Container.

If the load is too high, an element can be selected from the list by clicking on it and moving it to another Runtime
Container.

Proceed as follows:

1. After selection click on the right mouse button and Change Runtime Container
2. The Reassign Runtime Container and Calculate CPU Load Preview dialog box will appear.
3. Choose a new Runtime Container from the drop down menu.
4. Click on Recalculate or Cancel.

Overview

The Overview sheet gives information of every Runtime Container, assigned to the Server.

The following information is shown:

• Perf.: The total Performance in %.

• The total Used Memory in %.
• Status information

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 234 of 313
LKZ:DE AL:N ECCN:4E992

• Number of the peer to peer connections.

4.6 Diagram Functions

Diagrams contain the engineering data that is configured for the Project. There are four types of diagram:

• Function Diagrams: These diagrams contain all the logic and functionality that is configured. This includes
all signal input and output, interlocks, calculations and interfaces for operation.
• Plant Displays: These are pictures that the operator uses to operate the plant. They contain all the drives
and indicators and normally a graphical representation of the plant layout.
• Report Definitions: These diagrams are report definitions that can be saved and are available for editing if
required. A report definition contains the parameters used to select archived data. The selected data will be
output to a report.
• Point Groups:These diagrams are user defined groups of signals. Point Groups are used in report
definitions.

Diagram Functions refer to the operations, accessible from the Project View, which can be applied to the diagrams.
New diagrams are created in the Project View. The diagrams can then be opened, renamed or deleted. There is a
search function available to find diagrams in the Project Hierarchy.

Function Diagrams and Plant Displays have title blocks. These title blocks contain information pertaining to the
diagram that will be printed out in the diagrams title block.

There are functions available to find open connections in Function Diagrams, and open mappings to Plant Displays.

Diagrams and Project Nodes can be copied and used again. This enables the user to work more efficiently. Diagrams
can also be printed in batches selected by the user.

4.6.1 Creating Function Diagrams and Plant Displays

A new Function Diagram or Plant Display can be created in a Project Node. There is no limit to the number of Function
Diagrams or Plant Displays that can be created in a Node.

When creating a:

• Function Diagram: A corresponding Plant Display can be automatically created at the same time.
• Plant Display: A corresponding Function Diagram can be automatically created at the same time.

When Function Diagrams and Plant Displays are created simultaneously, the diagram assignment between them is
created automatically.

To create new Function Diagrams or Plant Displays for inclusion in a Project Node proceed as follows:

The Project View is open.

1. Select a Project Node in the Tree View or List View. The new Function Diagram or Plant Display will be
created in this Node.
2. Select the Project menu, then New from the first drop down menu, then:
o For a new Function Diagram: Select Function Diagram from the second drop down menu.
o For a new Plant Display: Select Plant Display from the second drop down menu.
3. A dialog box appears for either the new Function Diagram, or Plant Display.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 235 of 313
LKZ:DE AL:N ECCN:4E992

4. Enter the name of the new diagram (this is typically an alphanumeric code) in the uppermost field.

Illegal characters are not permitted in the name.

5. Assign the new diagram a document type in the Diagram Document Type field. The default document type
will be assigned if no document type is selected.
6. If a corresponding diagram is to be created, position the cursor over the middle field and click on it, the name
entered in the uppermost field will be automatically entered here (i.e. the Function Diagram and plant Display
names exactly the same). This name can be edited if required.
The corresponding diagram will be created in the same Project Node. If required, the new diagram can be
created with diagram assignments to and from a diagram that already exists. To create this assignment,
proceed as follows:
1. Click on the button on the right hand side of the middle field.

2. A Hierarchy Browser will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 236 of 313
LKZ:DE AL:N ECCN:4E992

3. Navigate through the Project Hierarchy in the Hierarchy Browser, and select the appropriate
diagram.
4. Click on Ok to copy the name of the selected diagram, or click on Cancel.
5. Assign the new diagram a document type in the Diagram Document Type field. The default
document type will be assigned if no document type is selected.
7. Enter the designation (this is typically a description).
8. Click on OK to create the diagram, otherwise click on Cancel.

A new Function Diagram or Plant Display is created in the selected Node.

Alternatively, select the function via the Context Menu (Right Mouse Click > Create New Function Diagram
or Create New Plant Display ).

4.6.2 Small Plant Displays

A small plant display is a Plant Display that opens with the smallest possible size when it is opened in the Operation
Mode. Plant Displays can be defined as small plant displays, after they have been created.

To set the size type of a Plant Display, proceed as follows:

The Project View is open.

1. Select the Plant Display.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 237 of 313
LKZ:DE AL:N ECCN:4E992

2. Select the Edit menu, then Set Plant Display Type from the drop down menu.
3. The Set Plant Display Type dialog box will open.

4. In the Plant Display Type drop down list, select either:

o Plant Display : For a normal Plant Display that opens to the full size.
o Small Plant Display : For a small plant display.
5. Select the Document Type from the drop down list.
6. Click on Set to save the selected type, otherwise click on Cancel.

The size type of the Plant Display will now be set.

The Plant Display has to be activated to make the changes effective in the Operation Mode.

In the List View of the Project View, the Plant Display will be indicated as a small plant display, in the Type
column.

The Plant Display type can also be set for a Plant Display that is open in the Diagram Editor.

Select the Edit menu, then Set Plant Display Type from the drop down menu.

4.6.3 Rename Diagram

A diagram can be renamed in the Project View. This can be done in three ways:

• In the Tree View

• In the List View as a Symbol
• In the List View as a List

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 238 of 313
LKZ:DE AL:N ECCN:4E992

All three methods are described below:

All diagrams of the same type (e.g. Function Diagrams) immediately subordinate to a parent Node must be
uniquely named, or the name will not be accepted by the system.

Diagrams of differing types (e.g. a Function Diagram and a Plant Display) immediately subordinate to a parent
Node may have the same name.

Changes to the diagram name will be inherited by AFs and signals within the diagram.

The inheritance of the new name may result in the renaming of signals. In this case a message appears, and
the user can confirm whether or not the signals should also be renamed. If the signals are not renamed any
connections made to them will be broken.

Special care must be take when renaming Project Nodes. When Project Nodes are
renamed they are not automatically renamed in the user access rights settings. For
example, if a Project Node that is referred to in the access rights is renamed then another
user may lose access to a set of Plant Displays. For this reason, users with insufficient
rights will not be able to rename a Project Node containing activated Function Diagrams.

Rename from Tree View

The Project View is open.

1. Select the diagram to be renamed in the Tree View.

2. Select the Project menu, then Rename from the drop down menu.
3. A cursor will appear at the diagram name.

4. Delete the name of the old diagram and enter the new name, then press Enter.
5. If the values of AFs or signals within the diagram have been previously manually modified, the Interrupted
inheritance dialog box will appear.
The user is then given the option to overwrite the values or to leave the current values.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 239 of 313
LKZ:DE AL:N ECCN:4E992

The diagram will be renamed.

Alternatively select the function via the context menu (Right Mouse Click > Rename), or click on a selected
diagram in the Tree View.

Rename from List View as a Symbol

It is possible to select the List View Appearance. If Small Symbols or Large Symbols are selected a diagram is
renamed as follows:

The Project View is open.

1. Select the diagram to be renamed in the List View.

2. Select the Project menu, then Rename from the drop down menu.
3. A cursor appears at the diagram name.

4. Change the name of the diagram, then press Enter.

5. If the values of AFs or signals within the diagram have been previously manually modified, the Interrupted
inheritance dialog box will appear.
The user is then given the option to overwrite the values or to leave the current values.

The diagram will be renamed.

Alternatively select the function via the context menu (Right Mouse Click > Rename), or click on a selected
diagram in the List View.

Rename from List View as a List

It is possible to select the List View Appearance. If List or Details are selected a diagram is renamed as follows:

The Project View is open.

1. Select the diagram to be renamed in the List View.

2. Select the Project menu, then Rename from the drop down menu.
3. In the Name column the diagram name can be edited directly

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 240 of 313
LKZ:DE AL:N ECCN:4E992

4. Change the name of the diagram, then press Enter.

5. If the values of AFs or signals within the diagram have been previously manually modified, the Interrupted
inheritance dialog box will appear.
The user is then given the option to overwrite the values or to leave the current values.

The diagram will be renamed.

Alternatively select the function via the context menu (Right Mouse Click > Rename), or click on a selected
diagram in the List View.

Illegal characters are not permitted in the names.

4.6.3.1 Inheritance for Diagram Renaming

During the Function Diagram renaming process, if the values of AFs or signals within the diagram have been
previously manually modified, then the Interrupted inheritance dialog box appears:

To restore inheritance and overwrite the existing assignments click on Yes, to retain these existing assignments click
on No, otherwise click on Cancel to cancel the renaming operation.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 241 of 313
LKZ:DE AL:N ECCN:4E992

The contents of the dialog box can be printed.

If there are closed connections that are using the renamed signals, then clicking Yes in the Interrupted inheritance
dialog box opens Confirmation dialog box. This dialog box confirms if all the corresponding Destination Connectors
should also be changed (i.e. the connection kept closed).
Click Yes to rename the closed destinations, click No retain them, otherwise click on Cancel.

Clicking No will open the connections.

Clicking Yes in the Confirmation dialog box opens Information dialog box informing the results of the renaming
process.
Click OK to close the dialog box.

4.6.4 Delete Diagram

Diagrams can be deleted from a Project Node.

When can Diagrams be deleted?

The following conditions must be met before a user may delete diagrams.

Function Diagrams

Before deleting a Function Diagram:

• The user deleting the diagram may have no uncommitted changes in any Function Diagrams.
• The diagram may not contain any uncommitted changes from other users.
• The diagram may not contain any active elements.

Plant Displays

Before deleting a Plant Display:

• The diagram may not contain any uncommitted changes from other users.
• The diagram must be deactivated.

Report Definitions and Point Groups

Before deleting a Report Definition or Point Group:

• The diagram may not contain any uncommitted changes from other users.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 242 of 313
LKZ:DE AL:N ECCN:4E992

How to Delete a Diagram

To delete diagrams from a Project Node proceed as follows:

The Project View is open.

1. Select the diagram to be deleted from the List View.

Multiple diagrams can be selected in the List View and deleted simultaneously.

2. Select the Project menu, then Delete from the drop down menu.
3. A dialog box appears to confirm the delete function.

Deleted diagrams cannot be rolled back after they have been deleted.

4. To delete the diagram click on Yes, otherwise to cancel the function click on No.

The diagram will be deleted.

Alternatively, select the function with the Del key, or via the Context Menu (Right Mouse Click > Delete).

4.6.5 Open Diagram in Configuration Mode

The following diagrams can be opened in the configuration mode, in their corresponding editors, where the diagrams
can be viewed or modified:

• Function Diagrams and Macros

• Plant Displays
• Report Definitions
• Point Groups

To open diagrams for configuration in the corresponding editor proceed as follows:

The Project View is open.

1. Select the diagram to be opened from the List View.

2. Select the Edit menu, then Open in Configuration Mode from the drop down menu.
3. Depending on the type of diagram being opened the following will appear:
o A Function Diagram or macro will open in the Diagram Editor.
o A Plant Display will open in the Diagram Editor.
o A Report Definition will open the report definition configuration dialog in the Report View.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 243 of 313
LKZ:DE AL:N ECCN:4E992

o A Point Group will open the Point Group definition dialog box.

Alternatively, the function can be selected via the context menu (Right Mouse Click > Open in Configuration
Mode)

The function can also be accessed via context menus from numerous other views and dialog boxes.

4.6.6 Find Diagram

The user may know the name of a diagram, but is unable to locate the item in the Project Hierarchy. The Find Diagram
function is provided to search and find the item, and is also useful for searching for items which conform to a particular
search pattern.

To find a diagram or Project Node in the Project Hierarchy proceed as follows:

Find Diagrams can be selected from either the Workbench or the Project View.

From the Workbench

The Workbench is open.

When starting Extras from the Workbench the whole project will be searched.

1. Select the Extras menu, then Find Diagram from the drop down menu.
2. The Find Diagrams dialog box appears.

See below for a description of the find functions in the dialog box.

From the Project View

The Project View is open.

1. Select the Project Node to be searched, in the Tree View or List View.

To search the entire project simply select the highest Node in the project.

2. Select the Extras menu, then Find Diagram from the drop down menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 244 of 313
LKZ:DE AL:N ECCN:4E992

3. The Find Diagrams dialog box appears.

See below for a description of the find functions in the dialog box.

Alternatively, select the function via the Context Menu (Right Mouse Click > Find Diagrams).

This function can also be accessed via context menus from some other views and dialog boxes.

Functions in the Find Dialog Box

The Find Diagrams dialog box is open.

1. Enter the diagram or Node name in the Search Pattern field.

Wildcard searches can be made as follows:

Enter an asterisk (*), to represent any group of characters, or a blank.

Enter a question mark (?), to represent any single character.

A diagram or Node Id can also be entered in place of diagram or Node name.

The asterisk or question mark cannot be used in the Search Pattern field for a search on an Id
number.

2. Select Match Case if the search is to be case sensitive.

3. Select the Search Type, from either:
o Plant Displays
o Function Diagrams
o Plant Displays and Function Diagrams
o Project Nodes
o Report Definitions
o Point Groups
o AF Types: A search will be made for all Function Diagrams containing the type of AF selected.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 245 of 313
LKZ:DE AL:N ECCN:4E992

o Pictogram Types: A search will be made for all Plant Displays containing the type of Pictogram or
Faceplate selected.
o An asterisk (*) which represents all of the above
4. The field beside Search Type allows the user to select a document type when searching for Plant Displays
and Function Diagrams.
5. The node to be searched is displayed in the Search Node field. The search node can be changed as follows:
1. Click on the button on the right hand side of the Selected Node field.
2. A Hierarchy Browser will open.
3. Select the Project Node, or diagram to be searched in the Hierarchy Browser.
4. Click on Ok to search this node, otherwise click on Cancel.
6. Click on Start Search to initiate the search, otherwise click on Cancel.
7. If diagrams or Nodes are found which match the Search Pattern, they appear in a list in the dialog box.

To sort the search results, click on any column header. The list will be sorted in ascending or
descending order according to the column contents.

8. Any item in the list can be selected and any of the following options selected via the context menu:
o Open Containing Folder
o Open in Operation Mode
o Open in Configuration Mode
9. Click on Cancel to close the window.

The contents of the dialog box can be exported or printed.

4.6.7 Find Tag Usages

The Find Tag Usages function provides a tool for users to establish the usage of Tags in a project. For example:

• The mapping of AF Blocks to Pictograms.

• The destinations of signals in Function Diagrams.
• The assignment of signals to Point Groups.
• The assignment of signals to Report Definitions.

The user can search for tag usages:

• In selected areas of the Project Hierarchy.

• That correspond to certain search criteria.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 246 of 313
LKZ:DE AL:N ECCN:4E992

Opening Find Tag Usages

There are two options for opening the Find Tag Usages dialog box.

From the Workbench

To open Find Tag Usages from the Workbench, proceed as follows:

The Workbench is open.

• Select the Extras menu, then Find Tag Usages from the drop down menu.

The Find Tag Usages dialog box will open.

From the Project View

To open Find Tag Usages from the Project View, proceed as follows:

The Project View is open.

1. Select the Project Node or diagram to be searched in either the List View, or the Tree View.
2. Select the Extras menu, then Find Tag Usages from the drop down menu.

Alternatively, select the function via the Context Menu (Right Mouse Click > Find Tag Usages).

The Find Tag Usages dialog box will open.

Finding Tag Usages

Once the Find Tag Usages dialog box is open, the user can go ahead, and search the Project Hierarchy with specific
search criteria.

1. The Project Node or diagram that will be searched is shown in the Search Node field. The selected node can
be changed as follows:
1. Click on the button on the right hand side of the Search Node field.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 247 of 313
LKZ:DE AL:N ECCN:4E992

2. A Hierarchy Browser will open.

3. Select the Project Node, or diagram to be searched in the Hierarchy Browser.

4. Click on Ok to search this node or diagram, otherwise click on Cancel.

2. Enter the Search Pattern. The fields of the search Pattern are entered as follows:
o Tag Name: Enter the required Tag Name.
o Tag Item: Enter the required Tag Item.
o Signal Name: Enter the required Tag Item (only when searching for signal usages).

Wildcard searches can be made as follows:

Enter an asterisk (*), to represent any number of characters, or a blank.

Enter an question mark (?), to represent any single character.

3. Select the Match Case check box, if the search for the search pattern is to be case sensitive.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 248 of 313
LKZ:DE AL:N ECCN:4E992

4. Select the Search Type from the drop down list (the number of options available depends on whether Find
Signals has been selected).
o Plant Displays
o Function Diagrams
o Point Groups
o Report Definitions
o Plant Displays and Function Diagrams
o Point Groups and Report Definitions
o An asterisk (*) which represents all of the above
5. Select the Find Signals check box if the search is to be made for signal usages.
6. Click on Start Search.
7. The results of the search will appear at the bottom of the dialog box. A message appears if no corresponding
usages are found.

The search results can be exported and printed.

8. Any item in the list can be selected and any of the following options selected via the context menu:
o Open Containing Folder
o Open in Operation Mode: The usage will be automatically selected in the diagram.
o Open in Configuration Mode: The usage will be automatically selected in the diagram.
9. When complete, click on Cancel and the Find Tag Usages dialog box will close.

4.6.8 Find Tag Duplicates

The Find Tag Duplicates function shows the user a list of all tag names that are used on more than one diagram. The
functionality of the control logic is not affected by duplicate tag names. But the documentation would not be in
conformance with VGB documentation guidelines.

To locate tag names that appear on multiple Function Diagrams and Plant Displays proceed as follows:

The Project View is open.

1. Select the Extras menu, then Find Tag Duplicates from the drop down menu.
2. The Find Tag Duplicates dialog box appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 249 of 313
LKZ:DE AL:N ECCN:4E992

3. A list of all the tags appearing on more than one Function Diagram appears under the heading Duplicate
Tags.
4. Select a tag. The Function Diagrams and Plant Displays in which the selected tag appears will be listed under
Diagrams containing the tag .
5. If desired, select a document type in the Document Type Filter. The diagrams listed will only be of the
selected type. The default selection, All, lists the diagrams of all the defined document types.
6. Select a diagram in the Diagrams Containing the Tag field, then click on the Open Diagram button.
7. The selected diagram will open in the Diagram Editor for editing.
8. After modifying and committing the selected diagram the user can click on Refresh in the Find Tag
Duplicates dialog.
9. The list of Diagrams Containing the Tag will update if the duplicate tag no longer exists.
10. Click on Close to exit the dialog.

4.6.9 Find Open Function Diagram Connections

The Find Open Function Diagram Connections function is used to find open connections between Source Connectors
and Destination Connectors. All open Destination Connectors within the selected area of the Project Hierarchy are
listed. Both committed and uncommitted diagrams are searched.

To find open Function Diagram Connections proceed as follows:

The Project View is open.

1. Select the diagram or Project Node to be searched.

2. Select the Extras menu, then Find Open Function Diagram Connections from the drop down menu.

Alternatively, select a diagram or Project Node in the Tree view or List View. Then select the function
via the context menu (Right Mouse Click > Find Open Connections...).

3. The Find Open Function Diagram Connections dialog box appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 250 of 313
LKZ:DE AL:N ECCN:4E992

Each row in the list in the dialog box provides information about a single open Destination Connector.
4. Any item in the list can be selected and any of the following options selected via the context menu:
o Open Containing Folder
o Open in Configuration Mode: The open connection will be automatically selected.
5. The user can make changes on the diagrams in the selected node, then click on Update button to update the
list in the dialog.
6. When complete click on the Ok button.

The contents of the dialog box can be exported or printed.

4.6.10 Find Open Plant Display Mappings

Pictograms and Faceplates in Plant Displays are mapped to AF Blocks in Function Diagrams with Process
Connections. The process connection can be made using :

• Default Mapping: The assignment of all Ports is predefined.

• Special Mapping: Ports can be manually assigned individually.

A project typically requires many process connections which have to be established and maintained. Using the Find
Open Plant Display Mappings function, the user can obtain a list of all default or special mappings which are open.

Open plant display mappings are mappings which are either non-existent or non-functional, and can have the following
states:

Invalid The mapped AF Block does not exist, or no mapping has been assigned.
Offline The mapped AF Block exists but is not active.
Online The mapped AF Block is active but has been deleted. When the deletion is activated the mapping will
Delete become invalid.
Reserved The Pictogram has been placed in Integrated Engineering mode, but the AF Block has not yet been
placed (i.e. still exists in the reference list).
Connectable A Pictogram has been mapped to an existing AF, but the connection is not closed. This might occur if
the mapped AF was deleted then added again.
Remote Unit The mapped AF Block is in a Remote Unit in a Multi Unit arrangement. The mapping cannot be
checked because the user is not logged in to this remote unit.

To find open plant display mappings in a Plant Display or Project Node, proceed as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 251 of 313
LKZ:DE AL:N ECCN:4E992

The Project View is open.

1. Select the Plant Display or Project Node to be checked.

2. Select the Extras menu, then Find Open Plant Display Mappings from the drop down menu.

Alternatively, select a Plant Display in the List View. Then select the function via the context menu
(Right Mouse Click > Find Open Plant Display Mappings ).

3. The Find Open Plant Display Mappings dialog box will appear.

Each row in the list in the dialog box contains details about a single open default or special mapping.
4. Any item in the list can be selected and any of the following options selected via the context menu:
o Open Containing Folder
o Open in Configuration Mode: The Pictogram or Faceplate will be automatically selected.
5. The user can make changes on the diagrams in the selected node, then click on Update button to update the
list in the dialog.
6. If there are any items on the list with the AF State Connectable, clicking on Map will close all of these
connections.

The contents of the dialog box can be exported or printed.

7. When complete click on the Ok button.

4.6.11 Hierarchy Browser

The Hierarchy Browser dialog is a subdialog of different dialog boxes.

It makes it easy to select the required Search Pattern of this main dialog box.

Depending on the main dialog box, only the relevant pattern are available.

To display the sub Nodes within a Node click on the + square.

Select the Project Node, or diagram to be searched in the Hierarchy Browser

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 252 of 313
LKZ:DE AL:N ECCN:4E992

Click on Ok to search this node or diagram, otherwise click on Cancel.

For further explanation see the appropriate documents:

• Creating Function Diagrams and Plant Displays

• Find Diagram
• Find Tag Usages
• Batch Printing
• Copying Diagrams
• Importing Project Nodes or Diagrams
• Importing Hardware Engineering
• Importing Macros and Compound Components
• Exporting Project Nodes or Diagrams
• Exporting Signals
• Call Home Configurator
• Replacing Compound Components
• Navigation Buttons
• Synchronize Database
• Find Tags

In special cases there is a New button available.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 253 of 313
LKZ:DE AL:N ECCN:4E992

Clicking the New button opens the New Function Diagram dialog box for creating a new Function Diagram.

For further explanation see the appropriate documents:

• Connection from an S7 Runtime Container to the FM 458 Runtime Container

• Connection from an FM 458 Runtime Container to the S7 Runtime Container
• Connection from an S7 Runtime Container to the F_System Runtime Container
• Connection from an F_System to the S7 Runtime Container
• Connection from an F_System to another F_System Runtime Container

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 254 of 313
LKZ:DE AL:N ECCN:4E992

4.6.12 Title Block

The title block appears on all printed Function Diagrams and Plant Displays, and contains all information relevant to
the diagrams. For example the Drawing Number, Plant ID Code, the Title and the Creation Date all appear in the title
block. From this information it is possible not only to uniquely identify the diagram, but also for example: to see by
whom it was drawn, on what date, for what plant, and who checked it.

Arrangement of Title Blocks

Much of the title block information may be common to many diagrams e.g. the customer or plant name, and should
only be entered once for all these diagrams. Alternatively, some information is specific to single diagrams only (e.g.
document number), and must be entered individually for each diagram.

Some of the fields in the Title Block can be carried over directly from the data configured for the diagram (e.g.
Document Type).

These requirements are met in the following ways:

• The title block information for Project Nodes and diagrams is edited differently.
• The title block information entered for a Project Node applies to the Node itself and all subordinate Nodes
and diagrams. In this way title block information is entered for whole groups of diagrams.
• The title block information entered for a diagram applies to that particular diagram only.
• Certain fields of the title block are applicable only to Project Nodes or only to diagrams. A field which is
diagram specific cannot be edited at the Project Node, and vice versa.
• Some fields of the title block are entered automatically.

These principles are illustrated in the example below:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 255 of 313
LKZ:DE AL:N ECCN:4E992

There are 2 Project Nodes: PROJECT NODE 1 is superordinate to PROJECT NODE 2, DIAGRAM 1 is contained in
PROJECT NODE 2. The title blocks for each of the Nodes and for the diagram are illustrated, as well as 3 of the fields
i.e. ID CODE, BUYER and DRAWN BY.

The field BUYER can only be edited at a Project Node. In the title block for DIAGRAM 1, BUYER is grayed out and
cannot be edited here. Note how the BUYER for PROJECT NODE 1 is carried through to the subordinate Node
PROJECT NODE 2 and its diagram DIAGRAM 1. For all Nodes and diagrams contained in PROJECT NODE 1 the field
BUYER need only be entered once.

The field DRAWN BY has been entered in PROJECT NODE 1 and carried through to all subordinate Nodes and
diagrams. Note that it is possible to edit this field at the DIAGRAM 1 level also, the field is not grayed out.

The field ID CODE must be entered for each diagram. It is not possible to edit this field at Project Nodes, the field is
grayed out there.

Inheritance of Title Block Information

The following conditions apply for the carrying through or inheritance of the title block information:

• When a new Project Node or diagram is created, it inherits the corresponding title block information from its
superordinate node.
• Any changes to the title block information of a Project Node or diagram will have no effect on the title block
information of superordinate nodes.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 256 of 313
LKZ:DE AL:N ECCN:4E992

• All changes made to a field of the title block of a Project Node will be carried through to all subordinate nodes
and diagrams, except:
o If the corresponding field in the title block of any subordinate node or diagram has previously been
edited individually, the inheritance is interrupted.
The user is then given the option to implement the changes only to the non-interrupted subordinates
or to restore inheritance and overwrite the values.

Accessing and editing the title block is described in Editing the Title Block.

Title Blocks also exist for Point Groups and Report Definitions. These cannot be printed out, but may be useful
for information purposes.

4.6.12.1 Editing the Title Block

The title block contains all information relevant to diagrams and appears on the printed version of the diagrams. For
information on the title block and the way it is arranged in the project see Title Block.

The contents of the title block, and the position of the title block entries in a printed diagram is provided below as well
as the procedure for editing the title block.

Contents of the Title Block

The title block mask has two sheets, one for the title block and one for revisions. The contents of the title block are
shown in the table below:

Sheet Field Character Notes

s
Title Block Name n.a. Automatic entry, equal to the diagram name. Cannot b
the title block.
Location ID-Code 32 Reserved for Diagrams.
Customer 32 Reserved for Project Nodes.
Buyer 32 Reserved for Project Nodes.
Plant Name 32 Reserved for Project Nodes.
Designation 81 Reserved for Diagrams. Automatic entry, equal to the d
designation.

Changes to the diagram name will be inherited by AFs

within the diagram.
Document Type n.a. Automatic entry, equal to the document type assigned
diagram was created. Can be changed.
Drawn By 15 Free.
Checked By 15 Free.
Standard 15 Free.
Creation Date 14 Automatic entry, equal to date and time the diagram or
created. Can be changed.
Special Note 12 Free.
Document Number 12 Reserved for Diagrams.
Drawing Number 28 Free.
Original Number 7 Free.
Created By 30 Reserved for Project Nodes.
Company 20 Reserved for Project Nodes.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 257 of 313
LKZ:DE AL:N ECCN:4E992

Sheet Field Character Notes

s
Year 4 Reserved for Project Nodes.
Revisions Revision Index 7 Free.
Revision Note 9 Free.
Revision Date 10 Free.
Modified by 5 Free.
(n.a. = not applicable)

• The column Characters indicates the maximum number of characters that can be entered. There is no
restriction on the format of the entries (i.e. any combination of numbers or letters can be entered). Those
marked n.a. are not applicable.
• The automatic entries are shown. Some automatic entries are not changeable in the title block.
• Some entries can be inherited from superordinate nodes.
• Some entries are reserved for either Nodes or diagrams.
• The revision information is freely set by the user, and is handled in the same way as the other title block
information. Revision information for the last three revisions can be entered.

Position of the Title Block Entries

The positions of the title block entries in a printed out diagram are shown.

How to Edit the Title Block

The Project View is open.

1. Select the Project Node or diagram in the Tree View or the List View, for which the title block is to be edited.
2. Select the Edit menu, then Title Block from the drop down menu.
3. The dialog box to edit the title block appears, consisting of 2 sheets, one for the title block and one for
revisions.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 258 of 313
LKZ:DE AL:N ECCN:4E992

Grayed out fields differ for nodes or diagrams, these fields are reserved for either nodes or diagrams.

4. The fields of the title block can now be edited.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 259 of 313
LKZ:DE AL:N ECCN:4E992

Dates are edited in the drop down calendar which opens when the pull down arrow is clicked on.

5. Inheritance of title block data is indicated and modified by the check boxes:
o If the check box is selected then...

Inheritance active
o If the user deselects the check box then...

Inheritance disabled
o Modify the text within the field...

Content modified
o Select the check box...

Inheritance restored
6. To apply changes to fields without closing the dialog box, click on Apply.
If the title block data assignment is being made for a Project Node that contains other nodes that have been
previously assigned individually, proceed as follows:
1. A dialog box will appear informing the user which nodes have been explicitly assigned previously.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 260 of 313
LKZ:DE AL:N ECCN:4E992

The contents of the dialog box can be printed.

2.To restore inheritance and overwrite the existing assignments click on Yes, to retain these existing
assignments click on No, otherwise click on Cancel to return to the Edit Title Block Data dialog
box.
7. When editing is complete click on Save or otherwise click on Cancel to cancel the function.

If multiple fields have been changed, the Interrupted inheritance dialog box might contain a large
quantity of changes.

Clicking Apply after modifying each field instead of waiting until editing is complete and using Save
will ensure the Interrupted inheritance list is kept small and manageable.

Alternatively select the function:

Via the context menu (Right Mouse Click > Edit Title Block).

In the Diagram Editor, select the Edit menu, then Edit Title Block from the drop down menu.

In the Diagram Editor, via the context menu (Right Mouse Click > Edit Title Block).

This function can also be accessed via context menus from numerous other views and dialog boxes.

4.6.13 Copying Diagrams

Diagrams and Project Nodes can all be copied and used again. By copying diagrams the user can avoid unnecessary
repetition of the same work, this is particularly useful when implementing redundant plant items.

A conceptual example of a situation where the copying function would be used is provided. This explains the
principles, and the process involved in copying diagrams.

When diagrams are copied:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 261 of 313
LKZ:DE AL:N ECCN:4E992

• The Project Hierarchy (consisting of Project Nodes) can be copied as well as diagrams (i.e. Function
Diagrams, Plant Displays, Report Definitions, and Point Groups).
• The IDs of all components being copied (except in Report Definitions) are modified according to rules set by
the user.

A description follows on how to copy diagrams, and also how to roll back or reverse the action if required.

How to Copy Diagrams

To copy nodes and diagrams in the Project Hierarchy proceed as follows:

The Project View is open.

1. Select the diagram or Project Node to be copied in the Tree View or List View. Only one item may be
selected, if a Project Node is selected the entire contents of the node will be copied.
2. Select the Edit menu, then Copy and Modify from the drop down menu.
3. The Start Copy and Modify dialog box appears.

4. Click on the browse button to the right of the destination folder field to open a hierarchy browser.
1. Select the Project Node into which the items will be copied.
2. Click on OK to accept the selection, otherwise click on Cancel.
5. Click on Copy and Modify to proceed with copying the diagrams, otherwise click on Cancel.

Alternatively the copy and modify operation can be started as follows:

Simultaneously press the CTRL key and drag and drop the selected item to the new Project Node
into which it is to be copied.

To indicate that the dragged item is being copied, a small rectangle with a plus symbol will appear
below the cursor.

6. The Copy and Modify Preview dialog box will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 262 of 313
LKZ:DE AL:N ECCN:4E992

This dialog box provides the opportunity to view, edit and try out the copy and modify rules, and initiate the
copy and modify action if required.
7. After the copy has been carried out, the new items are inserted into the Project Hierarchy. A Copy Modify
Result dialog box may open which provides the following information:

o Tags which had to be changed different to the preview: Any AF Block or signal IDs that have
been changed because they are duplicates of existing IDs in the project.
o Signals which could not be closed although corresponding usages and definitions were
found: The system automatically checks for, and closes any signal connections that may exist between
components in the existing, and copied Function Diagrams. The signals listed here are connections could not
be closed, for example if the existing component is locked by another user.

The contents of the dialog box can be printed.

After the nodes and diagrams have been copied into the target Project Node, they can then be committed or rolled
back as described below.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 263 of 313
LKZ:DE AL:N ECCN:4E992

Rolling Back

After the copied nodes or diagrams have been inserted, the user can remove them (or reverse the action) by using the
Rollback function. Rolling back will remove the selected diagrams, provided that no changes were been committed
after the copy.

Before copying diagrams it is a good idea to commit all diagrams. The project can then later be easily rolled
back to exactly the same state as it was prior to copying diagrams.

4.6.13.1 A Conceptual Example

An example of a simple situation where the copying function would be used is described here. Consider an area of
plant which consists of 2 identical fans. The control logic required for each individual fan is the same, the
representation required in the Plant Displays is also exactly the same.

The following Project Nodes and diagrams are created:

• The superordinate Project Node for FANS.

• The Project Node for FAN A.
• A Function Diagram containing the logic for Fan A, called FD A.
• A Plant Display containing the graphics and control elements for Fan A, called PD A.

The hierarchy for the plant area has been created, and all the engineering for fan A has been completed.

Now the configuration for fan B is required. Rather than creating the nodes and diagrams for fan B individually (as was
done for fan A), it is much easier to copy the configuration over from fan A. This concept is shown below:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 264 of 313
LKZ:DE AL:N ECCN:4E992

The Project Node for fan A and its contents are simply copied over to fan B. The configuration for fan B is exactly the
same as fan A, except that all the IDs have been renamed or modified. All nodes and diagrams and the module and
signal IDs inside them have been changed to apply to fan B.

The modification of the IDs is not done manually, it is performed automatically by the system in accordance with rules
set by the user before copying the diagrams.

4.6.13.2 How the Copy and Modify Rules Work

All nodes, diagrams, items within the diagrams and signals are uniquely identified in the system. No duplicates are
permitted. When copying, or (if required) when importing diagrams, the IDs of all copied components are modified in
order to meet the required engineering configuration. These IDs are converted from the existing IDs of the components
that are being copied or imported. The conversion is performed automatically by the system according to the copy and
modify rules set by the user.

In this section the way in which components are identified is discussed. Then information on setting the copy and
modify rules is provided. Finally the way in which the various types of components are handled during a copy and
modify operation is explained.

Identification of Components

It is important to understand the way in which the various components are identified. The copy and modify rules will
then be applied to these IDs when the new nodes and diagrams are created.

The components are identified as follows:

• Project Nodes are identified by the node name.

• Function Diagrams, Plant Displays, Report Definitions and Point Groups are identified by the diagram name.
• AF Blocks, Macros and Proxies (within Function Diagrams) are identified by the tag which is a combination
of:
o Tag Name, and
o Tag Item

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 265 of 313
LKZ:DE AL:N ECCN:4E992

• Signals are identified by the signal definition which is a combination of:

o Tag Name, and
o Signal Item, and
o Signal Name

Tags and signal definitions are expressed using tag separators to separate their constituents (e.g. 10MAG12.11223 or
10LAC10.44556.OUT).

Setting the Rules

Patterns

The conversion or modification of IDs is done according to patterns which are entered by the user in a table.

The user enters a source ID code (this is the ID the system will try to find), and a destination ID code (this is the ID the
system will replace the source ID code with, if it is found).

Consider the following rule example:

Source ID Code Destination ID Code

10HHL 10HHJ

The system searches the IDs, and every time the ID 10HHL is found, it replaces it with 10HHJ.

When no rule exists to match a particular ID, then the ID will not be replaced (or modified).

Wildcards

The real power of the copy and modify function becomes apparent when using wildcard patterns. The characters for
asterisk (*) and question mark (?) can be used to create wildcard patterns.

* (asterisk) Represents any number of characters, or a blank.

? (question mark) Represents a single character.

Consider the following rule example:

Source ID Code Destination ID Code

10CJC* 50HTC*

Every ID starting with 10CJC will be replaced by 50HTC, the rest of the ID stays unchanged. For example:

10CJC44 becomes 50HTC44

10CJC.4455.OUT becomes 50HTC.4455.OUT
10CJC becomes 50HTC

Or a more complicated example:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 266 of 313
LKZ:DE AL:N ECCN:4E992

Source ID Code Destination ID Code

1*HGM? 8*TOE?

10HGMM becomes 80TOEM

1555HGMU becomes 8555TOEU

However, IDs like 19HGHZZ or 18HGM do not match the source ID code and will not be modified.

For tags and signals, the tag separators form an integral part of the ID code. When copying diagrams,
remember that the included tags and signals will be copied and processed, using the same patterns. If the
user has special requirements (e.g. for specific signals), patterns must be entered specifically for these. Tag
separators can be used in the pattern if necessary (e.g. 10MAG20.*.X*).

Priority

When more than one rule is entered, the user can assign a priority number to each rule. The priority defines the order
in which the rules are applied during the copy and modify operation. The lower the priority number, the higher the rule
priority.

The system searches the IDs using the rules in order of priority. If a rule matches a particular ID, then the ID will be
modified according to the rule and the system will not attempt to modify that ID with any other lower priority rule. For
example if 3 rules with priorities 10,20 and 30 match the ID, then the rule with priority 10 will be applied.

Validity

When the user enters rules they are checked for validity by the system before they are accepted. For a rule to be valid,
all wildcards in the destination ID code must match those in the source ID code, in the same order.

Resolving Duplicates

Duplicate IDs are not permitted. The system automatically resolves any duplicate IDs resulting from a copy and modify
or import operation. The user is informed about any duplicate IDs which the system has had to resolve. The way in
which the duplicates are resolved depends on the type of component being copied. This is described in the section
below.

Handling of the Various Components

Project Nodes

The rules will be applied to the node name. Should the modified node name duplicate any other node immediately
subordinate to the same parent node, the system will resolve the duplication. The modified node will be renamed
automatically. This is done by inserting a number at the start of the modified node name.

Function Diagrams

The rules will be applied to:

• The diagram name: Should the modified diagram name duplicate any other Function Diagram immediately
subordinate to the same node the system will resolve the duplication, and rename the modified diagram name
automatically. This is done by inserting a number at the start of the modified diagram name.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 267 of 313
LKZ:DE AL:N ECCN:4E992

• Tags: Should the modified tag duplicate any other tag in the entire project the system will resolve the
duplication by changing the modified tag item automatically.
• The signal definitions: Should the modified signal definition duplicate any other signal definition in the entire
project, the system will resolve the duplication as follows:
o The tag name and signal item of the modified signal definition are replaced by the tag name and tag
item of the source AF Block or Proxy respectively. Should a duplicate still exist, then:
o The tag name of the modified signal definition is changed further. A number is automatically inserted
at the start of the tag name.

The following are features of modified Function Diagrams:

• All the elements contained in the diagrams are copied.

• The Project Nodes and Function Diagrams are assigned to Runtime Container zero (i.e. no assignment)
when they are inserted. The assignment must then be performed manually.
• The cycle times of all elements in Function Diagrams are copied.
• The title block information is not copied.
• The diagram assignments are copied if they exist between the diagrams that are being simultaneously
copied. Diagram assignments to other diagrams are not copied.

Plant Displays

The rules will be applied to the diagram name. Should the modified diagram name duplicate any other Plant Display
immediately subordinate to the same node the system will resolve the duplication, and rename the modified diagram
name automatically. This is done by inserting a number at the start of the modified diagram name.

When elements in Plant Displays contain process connections to Ports of AF Blocks in Function Diagrams, these
process connections are handled as follows:

• If the process connection is made to an AF Block that is in a Function Diagram that is being copied and
modified simultaneously, the process connection will be made to the modified AF Block in the modified
Function Diagram. Otherwise:
• The modified process connection will simply be modified according to the copy and modify rules.

The diagram assignments are copied if they exist between the diagrams that are being simultaneously copied.
Diagram assignments to other diagrams are not copied.

Point Groups

The rules will be applied to:

• The diagram name: Should the modified diagram name duplicate any other Point Group immediately
subordinate to the same node the system will resolve the duplication, and rename the modified diagram name
automatically. This is done by inserting a number at the start of the modified diagram name.
• Tags: The tag names within the Point Group definition will simply be modified according to the copy and
modify rules.

Report Definitions

The rules will be applied to:

• The diagram name: Should the modified diagram name duplicate any other Report Definitions immediately
subordinate to the same node the system will resolve the duplication, and rename the modified diagram name
automatically. This is done by inserting a number at the start of the modified diagram name.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 268 of 313
LKZ:DE AL:N ECCN:4E992

The tags contained in a Report Definitions will not be effected by the Copy and Modify rules.

4.6.13.3 Copy and Modify Preview

The copy and modify preview dialog box is a virtual control center for copying diagrams. After the user has initiated a
diagram copy function (via drag and drop in the Project View), the Copy and Modify Preview dialog box opens
automatically.

Using the functionality available in the dialog box the user can:

• View or edit the copy and modify rules. The modify rules are explained in How the Copy and Modify Rules
Work.
• Try out the rules and see what the effect is. The rules can be performed on the selected diagrams, and the
results can be viewed without making any actual changes to the project (i.e. just a preview).
• Decide whether or not to go ahead and perform the copy and modify operation.

The use of the Copy and Modify Preview functionality is described below.

Source and Destination Nodes

At the top of the dialog box the Source and the Destination are shown. These were identified in the drag and drop
operation that initiated the diagram copy.

If a single diagram (not a Project Node) is being copied, the diagram name will appear in the Source field.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 269 of 313
LKZ:DE AL:N ECCN:4E992

Modify Rules

The Modify Rules area of the dialog box contains the controls for accessing and applying the copy and modify rules.

Click on Change Rules to open the Copy and Modify Rules dialog box. In this dialog box the rules can be viewed or
edited.

Click on Perform new Rules to apply the copy and modify rules that have been saved. Performing the new rules will
not cause any changes to the project, it allows the user to preview the effect of the rules.

The first time the Copy and Modify Preview dialog box opens after initiating the copy function, the existing
rules will be performed automatically (without clicking on Perform new Rules).

Not Modified Tags and Signals

A list of the Not Modified Tags and Signals is provided in the dialog box. This list contains all the tags and signals for
which the system could find no matching pattern in the copy and modify rules. Since no rule can be applied to these
items the system will resolve the duplicates automatically if the copy and modify operation is carried out. The way in
which duplicates are resolved is discussed How the Copy and Modify Rules Work.

Signals and tags are represented differently in the list. If the item is a tag (e.g. an AF Block or Proxy tag), this tag is
shown in the Tag Name column, and the Signal column is empty. If the item is a signal, then the tag of the source
module (e.g. AF Block) is shown in the Tag Name column, and the signal definition is shown in the Signal column.

When copying diagrams the user normally wants to develop the copy and modify rules to match all the tags
and signals in the diagrams being copied. In this event the Not Modified Tags and Signals list will be empty.

Display Modifications

The Display Modifications area of the dialog box contains the controls to view the effect of the copy and modify rules
on the IDs of individual groups of components (e.g. diagrams or AF Blocks) for which a matching pattern was found.

• Click on the Diagrams button to open a dialog box containing a list that shows how all diagram and node
names will be modified.
•

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 270 of 313
LKZ:DE AL:N ECCN:4E992

• Click on the Tags without items button to open a dialog box containing a list that shows how the tags will be
modified.
•

• A tag consists of a tag name and a tag item, in this list only the tag name is shown. If many tags with the
same tag name (but different tag items) are modified, there will only be a single entry in the list for this tag.
• Click on the Tags with items button to open a dialog box containing a list that shows how the tags will be
modified.
•

• Both the tag name and tag item of all tags are shown in this list.
• Click on the Signals button to open a dialog box containing a list that shows how the signals will be modified.
•

• The components of the signal definition (tag name, signal item and signal name) are shown separated by a
delimiter in the Previous Signal and Modified Signal columns. The delimiter is defined as the Tag
separator in the global settings. The tag of the signal source is shown in the Tag Name column. If the signal
to be changed is an input or output port it will be indicated by I or O respectively, under Type.

The contents of the above dialog boxes can be printed.

Perform Copy and Modify

Click on Perform Copy and Modify to carry out the copy and modify operation and insert the new diagrams, or click
on Cancel to abort the function.

4.6.13.4 Copy and Modify Rules

The copy and modify rules dialog box contains the rules table for the copy and modify function. The rules are
applicable to both copying , and (when required) importing diagrams. In the dialog box the rules can be viewed and
edited. How the Copy and Modify Rules Work contains an explanation of the way the rules are formulated.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 271 of 313
LKZ:DE AL:N ECCN:4E992

The box contains the list of rules which are defined by the user, and the controls to edit them. The rules are saved for
individual users and also for the project.

How to Access the Copy and Modify Rules

To open the copy and modify rules dialog box proceed as follows:

The Project View is open.

• Select the Edit menu, then Edit Rule Table from the drop down menu.

The dialog box will open.

Alternatively, the copy and modify rules dialog box can be opened directly from the Copy and Modify Preview
dialog box when copying diagrams.

How to Edit the Rules

To edit the:

• Priority,
• Source ID Code, or
• Destination ID Code

of an existing rule, double click on the cell in the list. A cursor will appear in the cell and it can be edited. When
complete press Enter or click in another cell. The validity of the rule will be automatically checked.

The rule constituents: Priority, Source ID Code, and Destination ID Code are explained in How the Copy and
Modify Rules Work.

To make a rule active, simply click on the Active check box for that rule.

Click on Insert to insert a new rule into the table, the rule can then be edited. To delete a rule from the table, click on
the rule in the table to select it, then click on Delete.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 272 of 313
LKZ:DE AL:N ECCN:4E992

User and Project Rules

The rules are saved on two levels:

• Project Rules: One set of rules that is accessible by all users in the project.
• User Rules: Rules that are stored for, and accessible only by individual users.

Click on Save User Rules to save the rules in the list for an individual user. The dialog box will then close.

Click on Save Project Rules to save the rules in the list for the project. The dialog box will then close.

Click on Reset User Rules to make the user rules exactly the same as the project rules.

Click on Cancel to ignore any changes made since the dialog box was opened. The dialog box will then close.

4.6.14 Batch Printing

In the Project View a function is provided for diagram printing. The print function provided in the Diagram Editor prints
out single diagrams, whereas the print function in the Project View can be used to print out batches of diagrams.

The user can select which diagrams are to be printed, apply print settings globally to all these diagrams and print them
in a batch.

Selecting a Batch of Diagrams for Printing

Before batch printing, the diagrams to be printed must be selected. To make this selection proceed as follows:

The Project View is open.

1. Select either:
o A Project Node in either the Tree View or List View. If a Project Node is selected, any diagrams
contained in the node can be selected for printing.
o A single diagram (Function Diagram, Plant Display or Macro) in either the Tree View or List View.
2. Select the Project menu, then Print from the drop down menu.
3. The Print Diagrams dialog box will open.

4. The Selected Project-Node can be changed by clicking on the browse button beside the field.
5. Enter the Search Pattern, this can contain a wildcard character (i.e. an asterisk, *). The selected Project
Node or diagram will then be searched for diagram names corresponding to this pattern.
6. Click on Start Search. A list of diagrams that match the search criteria will appear in a list in the dialog box.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 273 of 313
LKZ:DE AL:N ECCN:4E992

7. Any diagram in the list can now be selected for printing. Click on any diagram to select it, or select multiple
diagrams by using the SHIFT or CTRL key.

Batch printing can also be performed for a multiple selection of diagrams in the List View of the Project View.
When this is done, the search is performed automatically, and the diagrams automatically selected in the
search result list.

Diagram Settings

There are various settings that can be made to control the diagram appearance of the printed out diagrams.

To view or adjust the diagram settings, click on Settings. The Function Diagram Print Settings dialog box will
appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 274 of 313
LKZ:DE AL:N ECCN:4E992

When a large batch is sent to a printer, the system splits the batch into a number of individual print jobs. The
Maximum number of diagrams per job can be set. This setting is also important for printing PDF (see below).

When diagrams are printed out, the appearance of:

• Connector Information, AND

• AF Block Information

will be the same as when the diagrams are open in the Diagram Editor.

These settings can be overridden by ticking the Activate special function diagram print settings check box. Then
special settings are enabled for Print Source Connector and Print Destination Connector (corresponding to
Connector Information), and Print Text Fields (corresponding to AF Block Information).

The special settings will then apply globally to all the diagrams being printed out in the batch.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 275 of 313
LKZ:DE AL:N ECCN:4E992

Click on the Page Setup button to bring up a dialog box for printed page setup settings. The contents of this dialog box
are specific to the printer and the printer driver software.

If the lines in the diagrams are not printing out well, then check the link width.

Printing Out

The performance of the Workbench may deteriorate momentarily during printing.

Click on the Print button to bring up a dialog box to print out the selected diagrams. The contents of this dialog box are
specific to the printer and the printer driver software.

Click on Cancel to close the Print Diagrams dialog box.

When printing Plant Displays it may be possible to achieve a higher quality by printing them out individually.

Printing PDF

The performance of the Workbench may deteriorate momentarily during PDF printing.

If an Adobe PDF printer has been added on the users Thin Client then diagrams can be printed to *.pdf files. Printing
to *.pdf files requires several Adobe PDF Printer settings.

A single .pdf file can be generated for each diagram that is printed:
The maximum number of diagrams in each batch must be set to 1. When this is done, the file names will correspond to
the diagram names of the diagrams that are being printed.

4.7 Transaction Handling

Transaction handling is the way in which engineering changes made by the user are saved and actualized in the
system. Engineering changes are any changes made to diagrams visible in the Project View. These include Function
Diagrams, Plant Displays, User Defined Reports and Point Groups. The changes involve new or existing engineering
data. The transaction handling process makes the engineered changes become part of the active logic controlling the
plant, or updates the Plant Displays and Reports used for plant operation.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 276 of 313
LKZ:DE AL:N ECCN:4E992

Transaction handling applies to engineering data in Function Diagrams, Plant Displays, User Defined Reports
and Point Groups, but not to hierarchical structures in the project. Changes to the Project Hierarchy and the
Plant Display Hierarchy become effective immediately, without transaction handling.

In general the transaction handling process takes place as follows:

1. Engineering changes have been made using the applicable editor i.e. Diagram Editor, Report Definition dialog
box, or Point Group Definition dialog box.
2. The changes are committed. This effectively saves the configuration changes to the system.
3. At any stage the user can rollback the changes, this will remove all the changes made.
4. The changes are activated. This starts all the committed changes running in the system.

The diagrams in the Project View can be separated into two groups:

• Function Diagrams
• Diagrams for Operation and Monitoring Functions. These include the Plant Displays, User Defined Reports
and Point Groups.

The way changes are handled is different for each group. The two processes are described.

No Code Generation or Code Transfer

An important advantage of the SPPA-T3000 software architecture is that there is no separate generation and transfer
of code required when actualizing changes. Components placed in diagrams already contain the code necessary to be
executed in the runtime environment.

This means that design changes made in SPPA-T3000 can be actualized very quickly and easily.

4.7.1 Transaction Handling for Function Diagrams

Engineering changes are made using the Diagram Editor and are saved in the Project Container and the applicable
Runtime Container via the transaction handling process. The system components affected by a change in a Function
Diagram are illustrated in the diagram below.

Engineering changes are made by a user working on a thin client computer. The engineering design is updated in the
Project Container, and is saved there when the user commits the data.

When the user activates Automation Functions, the newly committed data in the Project Container is transferred to the
Runtime Container and starts running (i.e. it becomes part of the control logic that actively controls the plant).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 277 of 313
LKZ:DE AL:N ECCN:4E992

Transaction handling for Function Diagrams is carried out in the following order (see attached flow chart, and the step
numbers which are also indicated):

1. The user makes changes to the control logic by adding, modifying, parameterizing, connecting or deleting
logic in Function Diagrams.
2. Once these changes are made the user must commit all Function Diagrams.
o 2.1 At any stage it is possible to rollback all Function Diagrams. All Function Diagrams will then be
returned to the same state as when the last commit or rollback was carried out.
3. Committed Function Diagrams can then be activated, this starts the changes running in the program cycle in
the Runtime Container.
o 3.1 It is also possible to deactivate Function Diagrams, this stops the logic in the diagram from
running in the program cycle in the Runtime Container.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 278 of 313
LKZ:DE AL:N ECCN:4E992

4. After changes have been activated or deactivated in Function Diagrams, the user can make the changes
permanently active by committing the last activation/deactivation, or
o 4.1 revert to the previous state by rolling back the last activation/deactivation.

Logic can also be activated or deactivated as individual components in Function Diagrams.

4.7.2 Transaction Handling for Plant Displays, User Defined

Reports and Point Groups
Transaction handling for the diagrams for operation and monitoring functions (i.e. Plant Displays, Report Definitions
and Point Groups) is a simple process. Changes to these types of diagrams have no influence on Runtime Containers.
Committed changes are saved to the Project Container. Activating these diagrams updates the operating and
monitoring functions.

Transaction Handling for Plant Displays, User Defined Reports and Point Groups is carried out as follows:

1. The user makes changes to the diagram (e.g. adding or deleting Pictograms or Free Graphics on Plant
Displays.)
2. The changes are saved to the Project Container when the user commits the diagram. Before committing the
user can rollback changes to the diagram. This returns the diagrams to the same state as when the most
recent rollback or commit was carried out.
3. The Plant Displays will be updated in Operation Mode when they are activated. When the User Defined
Reports and Point Groups are activated, the changes will be visible in the next Reports that are generated.
o 3.1 It is also possible to deactivate a Plant Display. Only deactivated Plant Displays can be deleted.

With Plant Displays, User Defined Reports and Point Groups there is no function to commit or rollback the last
activation or deactivation.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 279 of 313
LKZ:DE AL:N ECCN:4E992

4.7.3 Commit
For an introduction see transaction handling for Function Diagrams and transaction handling for Plant Displays, User
Defined Reports and Point Groups

To save the diagram changes made by the user proceed as follows:

The Project View is open.

1. Select:
o an individual Plant Display, User Defined Report or Point Group, from the List View
- In this case the selected diagram will be committed in Step 4
or
o a Function Diagram or macro in the Tree View or List View
- In this case all changed Function Diagrams will be committed in Step 4. (Note, Function Diagrams may be
in other Project Nodes in the Project Tree.)
or
o a Project Node in the Tree View or List View
- In this case all changed diagrams within the Project Node, will be committed in Step 4. If a Function
Diagram or macro is included in the selected Project Node, then all changed Function Diagrams will be
committed. (Note, Function Diagrams may be in other Project Nodes in the Project Hierarchy.)
2. In the Project View select the Edit menu, then Commit from the drop down menu.
3. A dialog box appears listing all diagrams to be committed.
4. To commit the diagrams click on Commit. Otherwise to cancel the function, click on Cancel.

A dialog appears reporting the results of the commit.

Function Diagram changes are saved to the Project Container and Runtime Container. Changes to Plant Displays,
User Defined Reports and Point Groups are saved only to the Project Container.

When a user commits changes, only the changes made by that user are actually committed. In a multi-user
environment, that means that each user must commit their own changes.

When any user activates changes, all changes committed by all users are activated. This means that
committed Plant Displays, User Defined Report, Point Group or Function Diagrams may be activated by
another user.

Multiple diagram or Node selection is also possible.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 280 of 313
LKZ:DE AL:N ECCN:4E992

Alternatively,

select the function via the Context Menu (Right Mouse click > Commit).

4.7.4 Rollback
For an introduction see transaction handling for Function Diagrams and transaction handling for Plant Displays, User
Defined Reports and Point Groups

To remove all the changes made by the user from uncommitted diagrams, proceed as follows:

The Project View is open.

1. Select :
o an individual Plant Display, User Defined Report or Point Group, from the List View
- In this case the selected diagram will be rolled back in Step 4.
or
o a Function Diagram or macro in the Tree View or List View
- In this case all changed Function Diagrams will be rolled back in Step 4. (Note, Function Diagrams may be
in other Project Nodes in the Project Tree.)
or
o a Project Node in the Tree View or List View
- In this case all changed diagrams within the Project Node, will be rolled back in Step 4. If a Function
Diagram or macro is included in the selected Project Node, then all changed Function Diagram will be rolled
back. (Note, Function Diagrams may be in other Project Nodes in the Project Tree.)
2. In the Project View select the Edit menu, then Rollback from the drop down menu.
3. A dialog box appears listing the diagrams to be rolled back.
4. To rollback the diagrams click on Rollback. Otherwise to cancel the function click on Cancel.

A dialog box appears reporting the results of the rollback.

All diagram changes are removed. Any new diagrams, that were created but not committed, will also be removed.

When a user rolls back changes in a multi-user environment, only changes made by that user will be rolled
back. No changes made by any other user will be affected.

If a Function Diagram or macro is included in the selected Project Node, then all Function Diagram changes
made by the user will be rolled back. This includes Function Diagram changes in other Project Nodes.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 281 of 313
LKZ:DE AL:N ECCN:4E992

Multiple diagram or Node selection is also possible.

Alternatively, select the function via the Context Menu (Right Mouse click > Rollback ) for all diagram types.

4.7.5 Activate
For an introduction see transaction handling for Function Diagrams and transaction handling for Plant Displays, User
Defined Reports and Point Groups.

Function Diagrams and the diagrams for operation and monitoring functions (i.e. Plant Displays, User Defined Reports
and Point Groups) can be activated simultaneously. However, they are handled differently. First the procedure to
activate diagrams is explained, and the handling of the two groups of diagrams will be explained separately.

How to Activate Diagrams

The Project View is open.

1. Select either:
o an individual diagram (in the List View) to be activated.
or
o a Project Node (In the Tree View or List View) to be activated. In this case all diagrams within the
Project Node will be activated.
2. In the Project View select the Edit menu, then Activate from the drop down menu.
3. A dialog box appears listing the Function Diagrams selected for Activation.

4. Select one of the options for Activate Function Diagram Changes.

o By selecting Only changes at activated AFs the changes of unactivated AFs will not be activated.
For example, if an AF was just added to the Function Diagram, it will not be activated.
o By selecting All, all logic on the Function Diagrams will be activated.
5. The user has the option to:
o click on Activate to activate the diagrams.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 282 of 313
LKZ:DE AL:N ECCN:4E992

If Automatic Activation Preview has been selected in Global Settings then the Preview Activation
dialog will appear, when activating Function Diagrams. After reviewing the list, click on Activate or
Cancel.

o click on Preview to view a list of AF block updates in the Function Diagrams before activating. Then
select OK to close the list. (This option only exists when activating Function Diagrams.)
o click on Cancel

A dialog box will appear, reporting on the results of the activation.

The changes become active immediately, there is no waiting time for a transfer of code. Ensure that any
necessary precautions have been taken prior to activating e.g. informing operating staff of the change.

When a user activates changes in a multi-user environment, any changes committed by other users will then
also be activated.

Activating Function Diagrams

Changes can be activated either as complete diagrams, or as individual elements within Function Diagrams. This
chapter covers the activation of complete diagrams, see Activating AF Blocks for activating individual elements.

Before a Function Diagram is activated the following conditions must be met:

• No uncommitted changes (made by any user) may exist in the diagram.

• The user may have no other uncommitted changes in any other Function Diagram.
• The Function Diagram must be assigned to a Runtime Container.

If two or more Function Diagrams are being activated simultaneously, none will be activated if any uncommitted
changes are present in any of them.

If uncommitted changes exist the Function Diagram will not be activated, and this will be reported in the dialog box.

Function Diagrams assigned to S7 Runtime Containers cannot be activated if any inconsistencies are present.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 283 of 313
LKZ:DE AL:N ECCN:4E992

The activation of S7 Runtime Containers enables a cycle overload check in the SIMATIC S7. This overload
check prevents an S7-CPU stop due to a violation of the guaranteed Base Cycle Time, which is defined during
the creation of the Runtime Container.

There are two possible errors which can occur:

• Overload of the process cycle:

• A possible troubleshooting measure can be to increase the cycle time of several Automation Functions of this
Runtime Container.
• Overload of the S7-CPU program.
• A possible troubleshooting measure can be to activate the affected Automation Functions step by step
instead of the whole Function Diagram.

When viewing the Function Diagrams in the Diagram Editor, activated AF Blocks are indicated with a blue
Frame, as per the AF Block Status Indication.

Manual scheduling of Function Diagrams is activated with a separate function.

Activating Plant Displays, User Defined Reports and Point Groups

When a Plant Display, User Defined Report or Point Group is activated, no uncommitted changes (made by any user)
may exist in the diagram. If uncommitted changes exist, the diagram will not be activated. This will be reported in the
dialog box.

If two or more diagrams are being activated simultaneously, only those with committed changes will be activated.

4.7.6 Deactivate
For an introduction see transaction handling for Function Diagrams and transaction handling for Plant Displays, User
Defined Reports and Point Groups.. Deactivating applies only to Function Diagrams and Plant Displays.

Control logic can be deactivated either as complete Function Diagrams, or as individual elements within Function
Diagrams. This chapter covers the deactivation of complete diagrams, see Deactivating AF Blocks for deactivating
individual elements.

Deactivating Function Diagrams elements removes the Automation Functions from the program cycle in the Runtime
Container (i.e. they stop running). The elements can be activated again later if required.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 284 of 313
LKZ:DE AL:N ECCN:4E992

If a signal is sourced by deactivated logic, then the signal is considered deleted. The input Port of the signal
destination will assume its signal value (as set in the mask), as if there was no connection.

Deactivating a Plant Display will close the Plant Display if it is open in Operation Mode. The user is allowed to delete
deactive Plant Displays.

Before a Diagram is deactivated the following conditions must be met:

• No uncommitted changes (made by any user) may exist in the diagram

• The user may have no other uncommitted changes in any other Function Diagram.

To deactivate Diagrams proceed as follows:

The Project View is open.

1. Select either:
o An Individual Diagram (in the List View) to be deactivated.
o A Project Node (In the Tree View or List View) to be deactivated. In this case all Diagrams within the
Project Node will be deactivated.
2. In the Project View select the Edit menu, then Deactivate from the drop down menu.
3. A dialog box appears to confirm the selection to be deactivated.
4. To deactivate the Diagrams click on Deactivate, otherwise to cancel the function click on Cancel.

A dialog box will appear, reporting on the results of the deactivation.

The deactivation becomes effective immediately, there is no waiting time for a transfer of code. Ensure that
any necessary precautions have been taken prior to deactivating e.g. informing operating staff of the change.

When a user deactivates changes in a multi-user environment, any changes committed and activated by other
users could also be deactivated.

Function Diagrams assigned to S7 Runtime Containers cannot be deactivated if any inconsistencies are
present.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 285 of 313
LKZ:DE AL:N ECCN:4E992

4.7.7 Commit or Rollback Last Activation/Deactivation

For an introduction see Transaction Handling for Function Diagrams.

Committing or rolling back of the last activation or deactivation only applies to Function Diagrams .

After changes have been activated or deactivated the user has the opportunity to decide if the activation or
deactivation should be made permanent. This facility allows for the changes to be observed or tested while they are
actively executing in the Runtime Container.

If the user is satisfied with the results of the changes then the last activation/deactivation can be committed. Otherwise
if the user wants to remove the changes and return the logic in the Runtime Container to its previous state, then the
last activation/deactivation can be rolled back.

After a Function Diagram has been activated or deactivated, all engineering is locked (i.e. no changes can be
made by any user) until the activation or deactivation is either committed or rolled back.

Committing and rolling back the last activation or deactivation are described below:

The functions described below will not be available to the user if the Project Container parameter, AFC
Autocommit, has been enabled in the Administration Console.

Commit Last Activation/Deactivation

The user has activated or deactivated Function Diagrams, and wishes to make the activation or deactivation
permanent.

The Project View is open.

1. Select the Edit menu, then Commit Last Activation/Deactivation from the drop down menu.
2. A dialog box will appear giving the result of the action.

Rollback Last Activation/Deactivation

The user has activated or deactivated Function Diagrams, and wishes to remove the activation or deactivation and
return the logic running in the Runtime Container to its previous state.

The Project View is open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 286 of 313
LKZ:DE AL:N ECCN:4E992

1. Select the Edit menu, then Rollback Last Activation/Deactivation from the drop down menu.
2. A dialog box will appear giving the result of the action.

Alternatively the Commit and Rollback Last Activation/Deactivation functions are available in the Diagram
Editor.

4.7.8 Recovering Project and Runtime Container Inconsistencies

The Runtime Containers and the Project Container should always have consistent data. Sometimes system problems
may arise (e.g. network failures) that result in inconsistencies.

One way to remove the inconsistencies is to completely restart the affected Runtime Container. When a Runtime
Container is restarted, the complete configuration is loaded from the engineering data in the Project Container.
However, a complete restart of a Runtime Container is not normally an option in a running plant since the Runtime
Container has to be stopped first.

Only S7 Runtime Containers can be recovered.

The inconsistencies can be removed without stopping the affected Runtime Containers. It is possible to obtain
information on inconsistencies, or to resolve them where possible.

In the event that the recovery of an S7 Runtime Container is unsuccessful, the Container must be disconnected and
reconnected.

Recover Project Container

To use the Recover Project Container functions proceed as follows:

The Project View is open. All Function Diagrams and Plant Displays must be committed.

1. Select the Extras menu, then Recover Project Container from the drop down menu.
2. The Recover Project Container dialog box will open.
3. Select a Runtime Container from the drop down list.
4. Select the Mode.
The modes are described below:
o Report : A report is created detailing any inconsistencies between the Project and Runtime
Containers. Nothing will be repaired or changed.
o Repair PC RTC : Data in both the Project and Runtime Containers will be changed to resolve
inconsistencies wherever possible. A report is created detailing the changes made and any remaining
inconsistencies.
5. To carry out the selected recovery mode for the selected Runtime Container click on Recover, otherwise to
cancel the function click on Cancel.
6. A dialog box appears giving summary information of the result of the recovery. The errors and warnings give
information about any inconsistencies that still exist.
7. Click on Open Protocol to open a protocol report browser to view detailed information about the recovery,
otherwise click on OK to close the dialog box.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 287 of 313
LKZ:DE AL:N ECCN:4E992

4.8 Online Configuration of SIMATIC S7

SIMATIC S7 is a CPU that is used as an Automation Server in the SPPA-T3000 system. An S7 CPU Automation
Server connects to various devices via:

• PROFIBUS DP - e.g. distributed IO stations, intelligent field devices, Exciter, etc.

• Peer to Peer connections

The configuration of SIMATIC S7 hardware can be carried out online. This includes adding and removing hardware as
well as communication connections.

Full technical information about the S7 System is available in the Equipment Catalog.

S7 engineering must be carried out using the facilities provided in the Workbench. No activities may be carried
out directly using the SIMATIC Manager program on the Application Server.

4.8.1 Hardware Configuration

An S7 CPU provides the platform for a single Realtime Runtime Container. Hardware devices (e.g. SM modules for
signal IO) are represented by Hardware Proxies that are assigned to a Runtime Container. The update of the
Hardware Proxy inside the S7 CPU can be done online. The procedure for carrying out hardware configuration
changes must be performed in a specific sequence.

Hardware Assignment

The Hardware Proxies are assigned to physical hardware. A schematic representation of an S7 system is shown
below:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 288 of 313
LKZ:DE AL:N ECCN:4E992

The S7 CPU acts as the PROFIBUS master, and the stations (e.g. ET200M stations) are the PROFIBUS slaves. A
redundantly configured S7 CPU consists of two racks, numbered Rack 0 and Rack 1. The network can also be
configured nonredundantly.

Each of these components must be assigned an ID during the system design. These IDs are set in the parameter
mask of the Hardware Proxies:

• The Rack number is the ID assigned to each Rack of the PROFIBUS master.
• The Slave number is the ID of the PROFIBUS Slave
• The Slot number defines the position of the IO device on the extension rack

What is Involved in an S7 Hardware Configuration ?

The system performs three tasks for S7 hardware configuration:

• Configure Hardware: The creation of System Data Blocks for the S7 CPU.
• Load Hardware: The loading of System Data Blocks on the S7 CPU.
• Load Connections: The loading of connection System Data Blocks required for a connection to, for example,
a multi unit configuration, or a Black Box connection.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 289 of 313
LKZ:DE AL:N ECCN:4E992

4.8.1.1 How to Carry Out an S7 Hardware Configuration

The three possible scenarios for carrying out an S7 Hardware Configuration are described below.

The activation of Hardware Proxies which have no corresponding SDBs will cause a system fault. To avoid
this situation, it is important to keep to the order described in the descriptions below.

Adding Hardware

To add hardware proceed as follows:

The Project View is open. The new hardware proxies have been placed and their parameters set in the applicable
Function Diagrams.

1. Commit the Function Diagrams.

2. Configure the S7 hardware.
3. Load the S7 hardware.
4. If required, load the S7 connections.
5. Activate the Function Diagrams.

The new hardware configuration will now be online in the system.

Removing Hardware

To remove hardware proceed as follows:

The Project View is open. The Hardware Proxies have been deleted from the Function Diagrams.

1. Commit the changed Function Diagrams, and activate them.

2. Configure the S7 hardware.
3. Load the S7 hardware.
4. If required, load the S7 connections.

The new hardware configuration will now be online in the system.

Replacing Hardware

Replacing hardware is a combination of the two above descriptions:

1. First remove the hardware that is to be replaced,

2. then add the new hardware.

The status of S7 Hardware Proxies (i.e. whether a hardware configuration, loading or connections loading is
required) is indicated by the blocks in Function Diagrams.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 290 of 313
LKZ:DE AL:N ECCN:4E992

4.8.1.2 Configure S7 Hardware

An S7 hardware configuration creates the System Data Blocks which are used in the S7 CPU.

To configure S7 Hardware (and create the S7 System Data Blocks), proceed as follows:

A specific sequence of activities must be followed for hardware configuration.

The Project View is open.

1. Select the Edit Menu, then S7, then S7 Hardware Configuration from the drop down menus.
2. The Configure S7 Hardware dialog box will open.

3. Select the Runtime Container to which the Function Diagrams which contain the proxies are assigned.

Hardware Configuration is carried out individually for Runtime Containers.

4. Click on Configure to carry out the hardware configuration, otherwise click on Cancel.
5. After the hardware configuration is complete, the S7 HW Config Result dialog box will appear.

The Open Protocol Button will open the Protocol Report Browser.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 291 of 313
LKZ:DE AL:N ECCN:4E992

Before proceeding with the hardware configuration, ensure that no errors are reported in the S7 HW
Config Result dialog box.

An error will occur, if a PDM editor is running. This is then reported in the Protocol.

The protocol report will also inform if loading S7 connections is required.

The new hardware configuration will be available and can be loaded.

Alternatively, the S7 Hardware Configuration can be handled from the context menu in the S7 Hardware
Configuration States Documentation dialog box (Right Mouse Click > S7 Hardware Configuration).

4.8.1.3 Load S7 Hardware

Loading S7 hardware causes the System Data Blocks to be loaded to the S7 CPU.

To download these changed SDBs into the S7 CPU System proceed as follows:

The Project View is open. The Hardware Configuration was successful, i.e. there are no errors listed in the Hardware
Configuration Protocol.

A specific sequence of activities must be followed for hardware configuration.

1. Select the Edit Menu, then S7, then Load S7 Hardware from the drop down menus.
2. The Load S7 Hardware dialog box will open.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 292 of 313
LKZ:DE AL:N ECCN:4E992

3. Select the S7 Runtime Container from the drop down menu.

Only S7-Runtime Containers are displayed.

4. Click on Load, otherwise click on Cancel.

5. The Information dialog box will appear. Review the information and follow the instructions carefully before
proceeding.

It is important to follow the instructions, that are provided in the dialogs, about the physical handling
of the hardware. These instructions are hardware specific and are designed to allow uninterrupted
operation of redundant S7 CPUs.

6. Click on Yes to continue loading the S7 hardware.

7. The new configuration will be downloaded into the S7 CPU. A control box will indicate the progress of the
download.
The download for a redundant system occurs as follows: The second CPU becomes the master. The first
CPU stops, and the SDBs are downloaded. The first CPU starts again. The first CPU synchronizes with the
second CPU and becomes master. The same procedure is performed for the second CPU.

The first CPU will be stopped by this process. If the configuration is wrong it can cause a total
communication failure of the S7-CPU System.

8. The Load S7 Hardware Result dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 293 of 313
LKZ:DE AL:N ECCN:4E992

The Open Protocol Button will open a Protocol Report Browser.

The SDBs will be downloaded into the S7 CPU.

Alternatively, the Loading S7 Hardware can be handled from the context menu in the S7 Hardware
Configuration States Documentation dialog box (Right Mouse Click > Load S7 Hardware).

4.8.1.4 Load S7 Connections

Loading S7 hardware causes the download of connection SDBs.

To download these changed SDBs into the S7 CPU System proceed as follows:

The Project View is open. The Hardware Configuration was successful, i.e. there are no errors listed in the Hardware
Configuration Protocol.

A specific sequence of activities must be followed for hardware configuration.

1. Select Edit, then S7, then Load S7 Connections from the drop down menus.
2. The Load S7 Connections dialog box will open.

3. Select the S7 Runtime Container, the Function Diagram is assigned to, which contains the new Hardware
Proxies from the drop down menu.
4. Click on Load, otherwise click on Cancel.
5. the Load S7 Connections Result dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 294 of 313
LKZ:DE AL:N ECCN:4E992

The Open Protocol Button will open a Protocol Report Browser.

6. Click on OK.

The S7 connections will be downloaded to the S7 CPU.

Alternatively, the Load S7 Connections can be handled from the context menu in the S7 Hardware
Configuration States Documentation dialog box (Right Mouse Click > Load S7 Connections).

4.9 Project Documentation

The Project Documentation functions provide the user with summary lists of the project data. These summary lists
help the user evaluate the state of the project.

4.9.1 Project Node

By using this function the user can obtain a list of all the diagrams contained in a Project Node. Some information
about each diagram is included in the list.

To obtain a list of all the diagrams contained within a Project Node and its sub-nodes, proceed as follows:

The Project View is open.

1. Select the Project Node in the Tree View or List View.

2. Select the Extras menu, then Documentation, then Project Node from the drop down menus.
3. The list of diagrams contained in the node appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 295 of 313
LKZ:DE AL:N ECCN:4E992

4. When complete, click on OK to close the window.

The information fields in the list are as follows:

• Diagram-Name, Diagram-Type and Diagram-Designation are all from the title block of the diagram.
• Project-Node is the node that is immediately superordinate to the diagram.
• Revision, Revision Note, Revision Date and Modified By correspond to the Revision Index, the Revision
Note, the Revision Date and Modified By in the title block. The revision information is taken from the last
revision entered in the title block (they are numbered 1,2 and 3).
• Last Change is the date and time of the most recent committed change made in a diagram. These changes
only include those which affect the functioning of logic i.e. changes to AF Blocks, proxies, Macros, Pictograms
and Faceplates.

The user can control the list appearance:

• The column widths can be adjusted.

• The list can be sorted by a particular column.
• Columns can be moved.

The contents of the dialog box can be exported or printed.

4.9.2 Tag Names

By using this function the user can obtain a list of all the tag names contained on a Function Diagram. If a Function
Diagram contains multiple tag names this will be visible on the list. The user can also list the tag names used on a
Macro. The tag names used on all Function Diagrams in a selected Project Node can also be displayed in one list.

To obtain a list of all the tag names contained on selected Function Diagrams or Macros proceed as follows:

The Project View is open.

1. Select the Function Diagram, Macro or Project Node in the Tree View or List View.
2. Select the Extras menu, then Documentation, then Tag Names from the drop down menus.
3. The list of tag names contained in the selected item appears.
o If an individual Function Diagram for Macro was selected the list of tag names appears as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 296 of 313
LKZ:DE AL:N ECCN:4E992

o If the Project Node was selected the list of tag names appears as follows:

4. When complete, click on OK to close the window.

The information fields in the tag name list for a Project Node are as follows:

• Diagram Name from the title block of the Function Diagram.

• Path is the location of the Project Node that is immediately superordinate to the diagram.
• Each Tag Name on a Function in the Project Node is listed.

The user can control the list appearance:

• The column widths can be adjusted.

• The list can be sorted by a particular column.
• Columns can be moved.

The user has the following navigation options when a tag name is selected in the Tag Names dialog boxes:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 297 of 313
LKZ:DE AL:N ECCN:4E992

• From the Context Menu the user can:

o Open in Configuration Mode.
o Open in Operation Mode.
o Open Containing Folder. This is available when viewing the tag names in a Project Node.
• Double click on the tag to open the Function Diagram in the Diagram Editor. The tag will be selected on the
Function Diagram.

The contents of the dialog box can be exported or printed.

4.9.3 Library Node

Using this function the user can obtain a list of all the elements contained in a Library Node (e.g. Automation Functions
or Macros). Some information about each element is included in the list.

To obtain a list of all the elements contained within a Library Node and its sub-nodes, proceed as follows:

The Project View is open.

1. Select the Library Node in the Tree View or List View.

2. Select the Extras menu, then Documentation, then Library Node from the drop down menus.
3. The list of elements contained in the node appears.

4. When complete, click on OK to close the window.

The user can control the list appearance:

• The column widths can be adjusted.

• The list can be sorted by a particular column.
• Columns can be moved.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 298 of 313
LKZ:DE AL:N ECCN:4E992

The contents of the dialog box can be exported or printed.

4.9.4 Uncommitted Changes

Uncommitted changes are:

• Function Diagrams, Plant Displays, Point Groups or Report Definitions in which changes have been made but
the changes have not been committed.
• Function diagrams which have been activated or deactivated, but the activation or deactivation has not been
committed or rolled back.

To find out which diagrams are uncommitted proceed as follows:

The Project View is open.

1. Select the Extras menu, then Documentation, then Uncommitted Changes from the drop down menus.
2. A dialog box appears with the list of uncommitted diagrams and plant displays (should none exist a message
is given).

The list of uncommitted changes contains only the uncommitted diagrams for that user and not for
other users.

The contents of the dialog box can be printed and exported.

3. To commit all the diagrams in the list, click Commit All. Otherwise click on Close.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 299 of 313
LKZ:DE AL:N ECCN:4E992

4.9.5 Forced Ports

Forced Ports are signals which have been overridden so that a substitution value set by the user replaces the actual
value at a signal port. It is important to keep track of which ports have been forced, and also to what value they have
been forced to.

To determine which ports are forced, or to reset a forced port from the list, proceed as follows:

The Project View is open.

1. Select the Extras menu, then Documentation, then Forced Ports from the drop down menus.
2. A dialog box appears with the list of forced ports (should none exist a message is given).

The contents of the dialog box can be exported or printed.

3. To reset a forced Port from the list, proceed as follows:

1. Select the Port to be reset from the list by clicking on it.
Multiple diagrams can be selected by pressing the SHIFT or CTRL key and selecting further items.
2. Click the right mouse button to open the context menu.
3. Click on Reset Forced Port .
4. A dialog box will appear with the results of the reset.
4. When completed click on Ok to close the dialog box.

4.9.6 Unactivated Changes

Unactivated diagrams are those in which changes have been committed but have not been activated. This applies to
Function Diagrams, Report Definitions and Point Groups.

To find out which diagrams are unactivated (by all users) proceed as follows:

The Project View is open.

1. Select the node or diagram to be checked in the Project View.

2. Select the Extras menu, then Documentation, then Unactivated Changes from the drop down menus.
3. A list of unactivated diagrams appears (should none exist a message is given).

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 300 of 313
LKZ:DE AL:N ECCN:4E992

The contents of the dialog box can be printed and exported.

4. Unactivated diagrams in the list can be activated as follows:

1. Select the diagram to be activated by clicking on it.
Multiple diagrams can be selected by pressing the SHIFT or CTRL key and selecting further items.
2. Click on Activate Changes.

Alternatively, activate the diagrams via the context menu. (Right Mouse Click > Activate
Changes).

AF Block updates on Function Diagrams can be previewed, before activation, via the context
menu (Right Mouse Click > Preview Activation).

3. A dialog box will appear giving the results of the activation.

5. When complete click on Close to close the dialog box.

4.9.7 Peer to Peer Connections

The Peer to Peer documentation feature allows the user to perform the following functions:

• Monitor the quantity of signals being exchanged via peer to peer connections between Runtime Containers.
• Be alerted if the configured signal limit is being approached.
• Navigate to the Function Diagrams containing the exchanged signals.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 301 of 313
LKZ:DE AL:N ECCN:4E992

To use the Peer to Peer documentation function, proceed as follows:

The Project View is open.

1. Select the Extras menu, then Documentation, then Peer-to-peer connections from the drop down menus.
2. The Peer-to-peer connections dialog appears.

3. Select the desired Runtime Container to monitor.

4. Enter the Warning Level as a percent of the configured maximum number exchanged signals. If the number
of free signals is below this limit, a warning will appear in the results list.
5. Click on Calculate.
6. A summary of the signals exchanged between the selected Runtime Container and the configured peer to
peer connections will be displayed.

o Connected Container: The list contains the containers with which the selected Runtime Container
has peer to peer connections.
o Active Incoming: This shows the quantity of activated signals being sent from the Connected
Container to the selected Runtime Container .
o Preview Incoming: The function looks at all the signals committed to the Connected Container
that are engineered to be sent to the selected Runtime Container . This quantity includes both activated and
not-activated signals.
o Active Outgoing: This shows the quantity of activated signals being sent from the selected
Runtime Container to the Connected Container.
o Preview Outgoing: The function looks at all the signals committed to the selected Runtime
Container that are engineered to be sent to the Connected Container. This quantity includes both activated
and not-activated signals.
The quantity of Preview Incoming signals, is compared with the Maximum Signals configured for the
Connected Container. Similarly, the quantity of Preview Outgoing signals is compared with the Maximum
Signals configured for the selected Runtime Container . If there are less free signals available, for either the
incoming or outgoing case, than what was specified as the Warning Level, the user is warned by the
background color of the row. The background will be in the system warning color.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 302 of 313
LKZ:DE AL:N ECCN:4E992

7. Details of connections can be viewed as follows:

Select either the Preview Incoming or Preview Outgoing call for a connection, then make a right mouse
click and select Connection Details from the context menu. The signal connections will be listed in the
Connections dialog.

o Source or Destination Path: The location of the Function Diagram in the Project Hierarchy from
where the signal originates (Source), or to where the signal is sent (Destination).
o Source or Destination Module: The tagname of the Automation Function Block from where the
signal originates (Source), or to where the signal is sent (Destination).
o Source or Destination Port : The AF Block port name for the source or destination signal.
o Signal: The signal name.
o State: State of the connection.
8. Select a signal in the list and right mouse click to open the navigation context menu.
9. Select one of the context menu items to perform one of the following navigation options:
o Open the folder, in the Project View, containing the Function Diagram with the source or destination
of the selected signal.
o Open the Function Diagram in the Operation Mode or Configuration Mode with the source or
destination of the selected signal.
10. Click on Ok in the Connections dialog to close the window.
11. Click on Close in the Peer-to-Peer dialog to close the window.

The contents of the dialog boxes can be exported or printed.

4.9.8 License Status

Using this function the user can view the current license status for a project. The license status appears as a list of all
the licensed features that exist for the system, and gives license information about all the features that are licensed for
the project.

To obtain a list of license status information for the project, proceed as follows:

The Project View is open.

1. Select the Extras menu, then Documentation, then License Status from the drop down menus.
2. A list containing the license status appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 303 of 313
LKZ:DE AL:N ECCN:4E992

3. The users of the Engineering Session and Operation Sessions can be viewed as follows:
1. Click on the session in the license list for which the user list is desired.

2. Click on User .
3. A dialog box listing the users currently using the selected session will appear.
4. To update the current status of the licenses, click on Update.
5. When complete, click on OK to close the window.

The Required License Version property at the top indicates the minimum version of the license required.

The information fields in the list are as follows:

• Feature-Name: The individual function that exists and can be licensed.

• Version: The license version.
• Quantity: The maximum amount of times for which a feature is licensed in a project (e.g. maximum number
of views open).
• In Use: The amount of licenses for the feature currently in use at the time of requesting the license status.
• Expiration-Date: The date on which the license for a feature will expire.
• Available: A tick in the box indicates that the project has a license for this particular feature..

The user can control the list appearance:

• The column widths can be adjusted.

• The list can be sorted by a particular column.
• Columns can be moved.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 304 of 313
LKZ:DE AL:N ECCN:4E992

The contents of the both the License Status and the User List dialog boxes can be exported or printed.

4.9.9 System Settings

Using this function the user can monitor the current status of the system. The system settings appear as a list of all the
components that exist for the system along with the limits set for them in the Offline Calculation tool. It also displays
the actual situation of each component so that the user may take specific action to avoid a component running out of
memory.

The Offline Calculation tool defines the maximum size of the system during the installation of the system. It
determines the memory settings required for various components, for e.g., a project container in the system.

To view the system settings, proceed as follows:

The Project View is open.

1. Select the Extras menu, then Documentation, then System Settings from the drop down menus.
2. The System Settings dialog box appears.

3. To update the current status of the system, click on Update.

4. When complete, click on OK to close the window.

The Warning Level (min. % free) property at the top indicates the limit at which a warning should be indicated if the
Current status is close to the Limit/Setting. The default value for this is 10. This default value can be changed by
entering the desired value.

The following information is provided:

• Name: The name of the system component.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 305 of 313
LKZ:DE AL:N ECCN:4E992

• Current: The actual status of the component.

• Limit/Setting: The maximum limit set for the system component via Offline Calculation tool.

The gray fields in the Current column indicate that the current status of the component is not calculated. Only
the maximum limits set for these components is displayed.

The user can control the list appearance:

• The column widths can be adjusted.

• The list can be sorted by a particular column.
• Columns can be moved.

The contents of the System Settings dialog box can be exported or printed.

4.9.10 Manual Scheduling

A project may contain manually scheduled items. These may be either Function diagrams which contain manually
scheduled items, or Runtime Containers in which the diagram execution sequence has been manually scheduled.

To find all the manually scheduled items in a project, proceed as follows:

The Project View is open.

1. Select the Extras menu, then Documentation, then Manual Scheduling from the drop down menus.
2. The Documentation Manual Scheduling dialog box will open. All the manually scheduled items will be
listed.

The following information is provided:

o Name: The name of the Runtime Container (for diagram scheduling), or Function Diagram (for
component scheduling).
o Path: The location of the Function Diagrams in the Project Hierarchy.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 306 of 313
LKZ:DE AL:N ECCN:4E992

o Activated: This field is selected when the item contains any manual scheduling that has been
activated.
o Changed: This field is selected when the item contains any manual scheduling that has been made,
or changed, but not yet activated.
3. The following functions are available via the context menu (select the item in the list by clicking on it, then
click the right mouse button):
o For Runtime Containers: Activate Diagram Scheduling, to activate the manual diagram scheduling
for the Runtime Container.
o For Function Diagrams:
Open in Configuration Mode, to open the Function Diagram in the Diagram Editor.
Activate Internal Diagram Scheduling, to activate the manual scheduling of components within the
Function Diagram.
4. When complete, click on OK to close the dialog box.

The contents of the dialog box can be exported or printed.

4.9.11 Print Alarm Groups

By using this function the user can obtain a list of all the Print Alarm Groups contained in a Project Node. Some
information about each group is included in the list.

To obtain a list, proceed as follows:

The Project View is open.

1. Select the Project Node in the Tree View or List View.

2. Select the Extras menu, then Documentation, then Print Alarm Groups from the drop down menus.
3. The list of the Print Alarm Groups contained in the node appears.

4. When complete, click on OK to close the window.

The information fields in the list are as follows:

• Name: The Name of the Project Node for for which the Print Alarm Group exists.
• Path: The location of the Project Node in the Project Hierarchy.
• Printer: The alarm printer to which the group is allocated.
• Alarm Types : The Alarm Types for which the Print Alarm Group is configured, are selected.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 307 of 313
LKZ:DE AL:N ECCN:4E992

The user can control the list appearance:

• The column widths can be adjusted.

• The list can be sorted by a particular column.
• Columns can be moved.

The contents of the dialog box can be exported or printed.

4.9.12 Sound Alarm Groups

By using this function the user can obtain a list of all the Sound Alarm Groups contained in a Project Node. Some
information about each group is included in the list.

To obtain a list, proceed as follows:

The Project View is open.

1. Select the Project Node in the Tree View or List View.

2. Select the Extras menu, then Documentation, then Sound Alarm Groups from the drop down menus.
3. The list of the Sound Alarm Groups contained in the node appears.

4. When complete, click on OK to close the window.

The information fields in the list are as follows:

• Name: The Name of the Project Node for for which the Sound Alarm Group exists.
• Path: The location of the Project Node in the Project Hierarchy.
• Alarm Types : The Sound that is allocated for each Alarm Type is shown.

The user can control the list appearance:

• The column widths can be adjusted.

• The list can be sorted by a particular column.
• Columns can be moved.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 308 of 313
LKZ:DE AL:N ECCN:4E992

The user has the following option when an item is selected in the list in the dialog box:

• Edit Sound Alarm Group

The contents of the dialog box can be exported or printed.

4.9.13 Hardware Configuration States

This function shows the user if there are any S7 Runtime Containers where hardware configuration tasks have not
been completed. This is relevant wherever Hardware Proxies have been assigned to S7 Runtime Containers. If the
hardware configuration tasks have not been completed then these Hardware Proxies will not be recognized in the
system.

To view the status of the hardware configuration tasks in each S7 Runtime Container to which Hardware Proxies have
been assigned, proceed as follows:

The Project View is open.

1. Select the Extras menu, then Documentation, then S7 Hardware Configuration States from the drop down
menus.
2. A dialog listing the S7 Runtime Containers created in the system appears.

3. The columns show the hardware configuration tasks. A selected field indicates that the user is required to
carry out the task.
4. Select the desired S7 Runtime Container and right mouse click to access the context menu.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 309 of 313
LKZ:DE AL:N ECCN:4E992

5. Select the desired hardware configuration task from the context menu:
o S7 Hardware Configuration
o Load S7 Hardware
o Load S7 Connections
o Start S7 Station
o Stop S7 Station
6. The hardware task will be carried out. A dialog will appear showing the result of the task.

Click on Open Protocol to open a protocol report browser containing detailed information, or click on OK.
7. The status of the task will be updated in the Documentation Hardware Configuration States dialog.
8. Click on OK to close the dialog.

The contents of the dialog box can be exported or printed.

4.9.14 Failsafe/FM458 Activation States

This function shows the user if there are any FM458 Runtime Container where compile or download have not been
completed and for every Failsafe container where compile or download have not been completed. This is relevant
wherever Hardware Proxies have been assigned to S7 Runtime Containers. If these actions have not been completed
then these Hardware Proxies will not be recognized in the system.

To view the status of the actions proceed as follows:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 310 of 313
LKZ:DE AL:N ECCN:4E992

The Project View is open.

1. Select the Extras menu, then Documentation, then Failsafe/FM458 Activation States from the drop down
menus.
2. A dialog listing the Runtime Containers created in the system appears.

3. The columns show the compilation tasks. A selected field indicates that the user is required to carry out the
task.

Compile or Download is only allowed, if all Point Views are closed. Otherwise an error message will
occur.

The usernames using dynamic point views are listed in the FM458 operators documentation.

4. Select the desired Runtime Container and right mouse click to access the context menu.

5. The Compile/Download/Start Failsafe dialog box will appear.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 311 of 313
LKZ:DE AL:N ECCN:4E992

Procceed as discribed under Transaction Handling for Failsafe.

For FM458 the Compile/Download/Start FM458 dialog box will appear.

Procceed as discribed under Transaction Handling for FM458.

6. The status of the task will be updated in the Documentation Hardware Configuration States dialog.
7. The Result Compile/Download/Start dialog box will open. Click on either of the Open Protocol buttons to
view detailed information in a protocol report browser.
8. Click on OK to close the dialog.

The contents of the dialog box can be exported or printed.

4.9.15 FM458 Operators

This function shows the usernames using a point view of S7-CPU Automation Functions or Spezialized S7-CPU
Automation Functions.

The Project View is open.

1. Select the Extras menu, then Documentation, then FM458 Operators from the drop down menus.
2. A dialog listing the usernames appears.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 312 of 313
LKZ:DE AL:N ECCN:4E992

3. Click on Close to close the dialog.

The contents of the dialog box can be exported or printed.

4.9.16 Documentation of GSD Files

To find out which GSD Files are currently installed in SPPA-T3000 proceed as follows:

The Project View is open.

1. Select the Extras menu, then Documentation, then GSD files... from the drop down menus.
2. A window appears with the list of GSD files installed:

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45
 Engineering User Guide (1/3) Page: 313 of 313
LKZ:DE AL:N ECCN:4E992

The column order in the list can be rearranged by selecting and dragging a column to the left or right.

3. To Print the contents of the list, click on Print...

4. When complete, click on OK to close the window.

The GSD files window will close.

Copyright © Siemens AG 2005 Version:

All Rights Reserved Date: 2008_01_29 rel_4.40_en_2008_01_28_17_45