checklist configuration

56
Checklist PCS 7 Configuration Programming Manual on which this document is based PCS 7 Compendium Part A - Configuration Guidelines Details on preparing the checklist Date Name Company / Dept Phone E-Mail Details on the project Customer Plant Project name Location Contact Brief description of project

Upload: neozeruel

Post on 25-Oct-2015

55 views

Category:

Documents


6 download

DESCRIPTION

The most important installation and configuration sequences involved in creating a PCS 7 project, together with appropriate parameter settings, are provided here in checklist format, sothey can be checked and recorded easily.In terms of both content and structure, this checklist relates to the "PCS 7 Compendium Part A – Configuration Guidelines" Manual, but also makes reference to other SIMATIC system manuals and other sources.

TRANSCRIPT

Page 1: Checklist Configuration

Checklist

PCS 7 Configuration

Programming Manual on which this document is based

PCS 7 Compendium Part A - Configuration Guidelines

Details on preparing the checklist

Date

Name

Company / Dept

Phone

E-Mail Details on the project

Customer

Plant

Project name Location

Contact

Brief description of project

Page 2: Checklist Configuration

Contents

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 2/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Contents

1 Introduction..................................................................................................... 4 1.1 Subject of the document ................................................................................... 4 1.2 References to other sources............................................................................. 5 1.3 Abbreviations .................................................................................................... 6

2 PC administration ........................................................................................... 7 2.1 PC settings ....................................................................................................... 7 2.2 Installing PCS 7 (including options) ................................................................ 11 2.3 Network settings ............................................................................................. 13 2.4 Creating a backup/image................................................................................ 14

3 Multiproject – Design and management..................................................... 15 3.1 Requirements ................................................................................................. 15 3.2 Creating the multiproject................................................................................. 18 3.2.1 Arranging and configuring the components .................................................... 18 3.2.2 Plant view ....................................................................................................... 21 3.3 Distributed engineering in the multiproject...................................................... 23

4 Configuration of the hardware (AS and I/O) ............................................... 24 4.1 Automation system ......................................................................................... 24 4.1.1 CP 443-1 for plant bus.................................................................................... 25 4.1.2 CP 443-5 Ext for fieldbus................................................................................ 26 4.2 IM 153-2, bus interface for S7-300 ................................................................. 27 4.3 I/O modules .................................................................................................... 27 4.4 Configuring field devices................................................................................. 29

5 Configuration of the network connections ................................................ 30

6 Configuration ................................................................................................ 31 6.1 AS configuration ............................................................................................. 31 6.2 Compiling and downloading............................................................................ 33 6.3 OS configuration ............................................................................................. 35

7 Changing projects in process mode........................................................... 42 7.1 Downloading changes online.......................................................................... 42 7.2 Complete online download to a redundant OS server pair ............................. 43

8 Asset management....................................................................................... 44 8.1 Requirement ................................................................................................... 44 8.2 Configuration .................................................................................................. 45 8.3 Runtime .......................................................................................................... 46

9 Installation guidelines .................................................................................. 47 9.1 Installation....................................................................................................... 47

Page 3: Checklist Configuration

Contents

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 3/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

9.2 Grounding concept ......................................................................................... 53 9.3 Lightning and overvoltage protection.............................................................. 56

Page 4: Checklist Configuration

Introduction

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 4/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

1 Introduction

1.1 Subject of the document

The most important installation and configuration sequences involved in creating a PCS 7 project, together with appropriate parameter settings, are provided here in checklist format, so they can be checked and recorded easily.

In terms of both content and structure, this checklist relates to the "PCS 7 Compendium Part A – Configuration Guidelines" Manual, but also makes reference to other SIMATIC system manuals and other sources.

NOTE The checklist represents a model which can be adapted to the individual requirements. She does not lay any claim to completeness.

Page 5: Checklist Configuration

Introduction

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 5/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

1.2 References to other sources

Table 1-1

Ref. no.

Name ID

[1] PCS 7 Process Control System Compendium Part A Configuration Guidelines

A5E02122386-01

[2] Process Control System PCS 7 V7.0 SP1 Engineering System Configuration Manual

A5E00808639-02

[3] PCS 7 - PC Configuration and Authorization A5E00783464-02 [4] SIMATIC Logon Configuration Manual A5E00496671-04 [5] Process Control System PCS 7 Time Synchronization A5E01216577-01 [6] Process Control System PCS 7 V7.0

Programming Instructions for Blocks A5E00978907-01

[7] Distributed I/O Device ET 200M EWA-4NEB780600601-08 [8] Automation System S7-300 Module Data A5E00105504-03 [9] Process Control System PCS 7 V7.0 SP1

Released PCS 7 Modules A5E01006283-02

[10] Industry PC SIMATIC Rack PC 547B A5E01127518-02 [11] Process Control System PCS 7 V7.0 SP1

PCS 7 OS Web Option A5E00808636-02

[12] Process Control System PCS 7 V7.0 SP1 Operator Station

A5E00808628-02

[13] SIMATIC NET Twisted-Pair and Fiber-Optic Networks C79000–G8900–C125–02 [14] SIMATIC NET PROFIBUS Networks 6GK1970–5CA20–0AA0 [15] Automation System S7-400 Hardware and Installation 6ES7498-8AA05-8AA0

PCS 7 V6.1: "PCS 7 Security Concept Recommenda-tions and Notes"

A5E00477558-01 [16]

PCS 7 V7.0: "Security Concept PCS 7 and WinCC - Basic Document"

A5E02128732-01

[17] Distributed I/O Device ET 200iSP A5E00247482-03 [18] Automation System S7-400 Module Data A5E00267833-03 [19] SIMATIC Principles of Explosion Protection A5E00206200-02 [20] Automation Systems

S7-300, ET 200M Ex I/O Modules A5E00172006-09

[21] DP/FF Link A5E01017498-01

Page 6: Checklist Configuration

Introduction

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 6/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

1.3 Abbreviations

The following abbreviations are used in this document: Table 1-2

Abbreviati-on

Meaning

APDiag WinCC diagnostic tool AS Automation system OCV Outputs have no current or voltage CFC Continuous function chart CiR Configuration in Run EMC Electromagnetic compatibility ES Engineering station ESD Electrostatic sensitive device USV Use substitute value FAT Factory acceptance test HDS Hardware design specification Comm. Commissioning IPC Industry PC (preinstalled PC bundle) KLV Keep last value MTA Marshaled termination assembly OS Operator station PE Protective earth PKZIP Archiving tool available in PCS 7 ATR Acknowledgment-triggered reporting SDS Software design specification SFC Sequential function chart SNMP Simple network management protocol SSC SIMATIC Security Control (tool at end of setup) PH Plant hierarchy UoM Unit of measurement

Page 7: Checklist Configuration

PC administration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 7/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

2 PC administration

2.1 PC settings

Using IPCs If using non-IPCs, please go to Table 2-2.

Table 2-1

Action Note/Reference Done Explanation/Reason

Define computer names correctly prior to installation. • No special characters • Max. 15 characters • Capital letters only • First character must be a letter

[1], section titled "Installation" The computer name cannot be changed once PCS 7 has been installed. Can be checked via the following registry: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent" (for IPCs, "OldName" must be "SIMATIC").

Yes

No

Define bus addresses (IP and MAC). Create a list of all components which are assigned a separate address. [1], section titled "Network settings"

Yes

No

When operating the PCS 7 plant within a domain: Agree the security settings to be used throughout the domain with the relevant administrator.

[3], general

Yes

No

Optional: Allocate a separate partition (NTFS format) for images on the computers.

Image files can be stored here. [3], section titled "Hard disk partitioning"

Yes

No

Page 8: Checklist Configuration

PC administration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 8/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

Optional: Allocate a separate partition (NTFS format) for licenses on the computers.

This partition should be excluded from defragmentation programs.

Yes

No

Optional: Install other Microsoft security patches and hotfixes (as advised by IT Security).

You must install the patches and hotfixes in the same language as that of the oper-ating system used. [3], section titled "Installing security pat-ches"

Yes

No

If using SIMATIC Logon: Create user groups in the user administra-tion system of Windows or the domain.

[3], section titled "Preparing PC stations" [4], general

Yes

No

Check/adjust the time settings on every PC.

"Control Panel > Date and Time" [1], section titled "Time synchronization"

Yes

No

Page 9: Checklist Configuration

PC administration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 9/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Using non-IPCs Table 2-2

Action Note/Reference Done Explanation/Reason

Define computer names correctly prior to installation. • No special characters • Max. 15 characters • Capital letters only • First character must be a letter

[1], section titled "Installation" The computer name cannot be changed once PCS 7 has been installed.

Yes

No

Define bus addresses (IP and MAC). Create a list of all components which are assigned a separate address. [1], section titled "Network settings"

Yes

No

Check the PCS 7 installation requirements. [3], general [4], section titled "Installation of software, software requirements"

Yes

No

When operating the PCS 7 plant within a domain: Agree the security settings to be used throughout the domain with the relevant administrator.

[3], general

Yes

No

Allocate a separate partition (NTFS format) for the system on the computers.

System data (installation) is saved on this partition. [3], section titled "Hard disk partitioning"

Yes

No

Allocate a separate partition (NTFS format) for data on the computers.

Project data should be saved on this parti-tion. [3], section titled "Hard disk partitioning"

Yes

No

Page 10: Checklist Configuration

PC administration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 10/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

Optional: Allocate a separate partition (NTFS format) for images on the computers.

Image files can be stored here. [3], section titled "Hard disk partitioning"

Yes

No

Optional: Allocate a separate partition (NTFS format) for licenses on the computers.

This partition should be excluded from defragmentation programs.

Yes

No

Optional: Install other Microsoft security patches and hotfixes (as advised by IT Security).

You must install the patches and hotfixes in the same language as that of the oper-ating system used. [3], section titled "Installing security pat-ches"

Yes

No

If using SIMATIC Logon: Create user groups in the user administra-tion system of Windows or the domain.

[3], section titled "Preparing PC stations" [4], general

Yes

No

Check/adjust the time settings on every PC.

"Control Panel > Date and Time" [1], section titled "Time synchronization"

Yes

No

Page 11: Checklist Configuration

PC administration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 11/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

2.2 Installing PCS 7 (including options)

ES, OS server, OS clients Table 2-3

Action Note/Reference Done Explanation/Reason

Administrator rights (as a minimum) are required to log on at the Windows level.

Yes

No

Install the Microsoft patches supplied. Yes

No

Install the appropriate SQL server (take the PCS 7 version into account).

Yes

No

Installation using the PCS 7 setup. The steps in the installation menu must always be followed. All the required packages (PCS 7 Engi-neering, Batch Engineering, etc.) must be selected via the "Package Installation" menu command. Any other necessary programs must be selected via the "Programs Options" menu command.

[3], section titled "How to install the PCS 7 software"

Yes

No

<Enter the versions, if necessary>

The following applies to PCS 7 V7.0: SSC settings successfully accepted at the end of the installation procedure (confirmation message from SSC).

Yes

No

Page 12: Checklist Configuration

PC administration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 12/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

The PCS 7 software must be kept up to date.

Install any newly released service packs and updates. You can find information about delivery releases at: Industry Automation Service&Support http://support.automation.siemens.com (by subscribing to the newsletter, for example)

Yes

No

Authorizations/Licenses Table 2-4

Action Note/Reference Done Explanation/Reason

Check that the PC is free of viruses prior to installing/uninstalling all authorizations.

In order to transfer the authorization, the authorization medium's write protection must be disabled. This does mean that there is a possibility of transmitting vi-ruses between the hard disk and the me-dium. [3], section titled "Virus scanners"

Yes

No

Transfer licenses via the Automation Li-cense Manager (ALM).

"Start > SIMATIC > License Management > Automation License Manager"

Yes

No

Page 13: Checklist Configuration

PC administration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 13/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Documentation Table 2-5

Action Note/Reference Done Explanation/Reason

File all the software which has been sup-plied and installed, together with the rele-vant descriptions/manuals, in a well-ordered manner. Make a record of the documentation in the computer logbook.

"C:\Windows\Citamis.str" (all installations of SIMATIC components) "C:\Windows\PCS7TOOLS_LOG.TXT" (all details relating to the most recent PCS 7 installation procedure) "C:\Windows\WinCCInstallation.log" (all details relating to the most recent WinCC installation procedure)

Yes

No

2.3 Network settings

Table 2-6

Action Note/Reference Done Explanation/Reason

Configure the terminal bus. Yes

No

Check the availability of all partners on the bus using SIMATIC Shell.

Yes

No

The name resolution of all computers is available.

Yes

No

Address the network switches on the ter-minal bus.

[1], section titled "Configuring the terminal bus"

Yes

No

Page 14: Checklist Configuration

PC administration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 14/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

Configure the plant bus (CP 1613, BCE cards).

Yes

No

Address the network switches on the plant bus.

[1], section titled "Configuring the plant bus"

Yes

No

2.4 Creating a backup/image

Table 2-7

Action Note/Reference Done Explanation/Reason

Create an image of the installation. We recommend that you use the "SIMATIC PC/PG Image & Partition Crea-tor" utility software (order number 6ES7648-6AA01-0YX0).

Yes

No

Page 15: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 15/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3 Multiproject – Design and management

3.1 Requirements

Table 3-1

Requirement Note/Reference Adhered to Explanation/Reason

Plant planning • Specify all the components used in

PCS 7. • Estimate the utilization for the AS and

OS (cycle time, memory requirements) and allow for appropriate reserves.

• Take concepts and supplementary conditions into account (for example, number of clients per server, engineer-ing concept, operating concept).

[2], section titled "Planning the plant engi-neering"

Yes

No

Create the Hardware Design Specification. The requirement specification forms the basis for developing the HDS. It defines the hardware of the process control system used for the production facility in the project and the software components needed to configure this hardware.

Taking integration and diagnostics into account: • Use standard configurations. • If possible, use hardware modules

which have been released for PCS 7 [9].

• Use add-ons where possible (e.g. Simocode Pro).

• Plan for the creation of diagnostics driver blocks, if necessary; see [1], sec-tion titled "Creating user-defined driver blocks".

Yes

No

Page 16: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 16/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Note/Reference Adhered to Explanation/Reason

Create the Software Design Specification. The SDS defines the structure of the multi-project and all the SW types to be created.

The multiproject is divided into various subprojects based on technological and local conditions, as well as configuration-specific requirements such as the number of project engineers, or job-specific condi-tions. [1], section titled "Creating and managing the PCS 7 project"

Yes

No

Define the naming conventions. Naming conventions for the multiproject, projects, hierarchy folders, symbols, server data, connections, and hardware, for example. Define the location identifier and plant des-ignation. [1], section titled "General project rules"

Yes

No

Define the area overview. Define the number and layout; plan for reserves.

Yes

No

Define the plant structure. Requirement for creating the plant hierar-chy

Yes

No

Define process tag lists. Requirement for creating process tags Yes

No

Define symbolic address lists. Requirement for hardware and connection configurations

Yes

No

Define the network structures for terminal buses, plant buses, and fieldbuses.

Requirement for the hardware configuration Yes

No

Page 17: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 17/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Note/Reference Adhered to Explanation/Reason

All engineering work must be performed on the ES (or multiple engineering stations) before the OS projects are downloaded to the OS computers.

No engineering work must be carried out on the OS servers or OS clients, with the exception of the following: • Activation of time synchronization for

the servers, if the ES does not have access to a CP 1613

• Checking/verifying the redundancy setting on OS server pairs

Yes

No

The OS project must not be activated on the ES.

The OS project can be called in simulation mode using the "Start OS Simulation" op-tion. In cases such as this, the OS project is duplicated on the ES and the copy is activated. Online access requires a con-nection to be available between the ES and the OS in NetPro.

Yes

No

Define the concept for the master data library.

All users of the project use the same blocks and process tag types.

Yes

No

Define the concept for time synchroniza-tion.

Only one (redundant) time server is avail-able in the system and all stations (PCs and CPUs) use this time server as the master. [3], section titled "General project rules" and [5], general

Yes

No

Optional: Define the concept for multipro-ject/multiuser engineering.

[2], general and [1], section titled "Sharing out engineering work"

Yes

No

Page 18: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 18/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3.2 Creating the multiproject

3.2.1 Arranging and configuring the components

Multiproject Table 3-2

Action Note/Reference Done Explanation/Reason Creating a multiproject, together with all required subprojects, in the SIMATIC Man-ager. • AS • OS servers and OS clients • ES • Master data library

[1], sections titled "Automatically creating a multiproject" and "Integrating additional ES/OS subprojects" [2], section titled "Basic concepts of engi-neering"

Yes

No

Assign unique names to the subprojects and stations.

[1], section titled "Integrating additional ES/OS subprojects"

Yes

No

Set the language of the display devices for all subprojects.

The language of the display devices is relevant for transferring messages from the engineering system to the OS (compi-lation of the OS). If you have not selected the required language, the message texts will be transferred to the wrong column of the text library and will not appear in pro-cess mode. [1], section titled "Automatically creating a multiproject"

Yes

No

Page 19: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 19/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Engineering station Table 3-3

Action Note/Reference Done Explanation/Reason

Insert the PC station. Yes

No

Set and address the HW configuration with a WinCC application and CP 1613 or gen-eral IE.

Yes

No

Assign parameters for CP 1613 or general IE time synchronization.

Yes

No

Download the engineering station's HW Config to the Station Configuration Editor using the "Configure Target System" func-tion (take note of the "PC internal" setting).

[1], section titled "Arranging components" [2], section titled "Basic concepts of engi-neering" and [5], general

Yes

No

Automation system Table 3-4

Action Note/Reference Done Explanation/Reason Insert the AS (standard and fault-tolerant). [1], section titled "Arranging components"

Yes

No

Insert additional CPs used for PROFIBUS and Ethernet.

Multiple PROFIBUS DP master systems, for example.

Yes

No

Assign unique names for all S7 programs in the multiproject in the SIMATIC Man-ager.

Do not use blanks. Yes

No

Page 20: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 20/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

OS servers Table 3-5

Action Note/Reference Done Explanation/Reason

Insert the PC station. Yes

No

Set the HW configuration with a WinCC application and CP 1613.

Yes

No

CP 1613 - time synchronization: Activate "Time-of-day mode" and "Send slave keep alive for connections".

Yes

No

Assign a unique MAC address to the CP 1613.

Yes

No

Assign meaningful symbolic computer na-mes (no special characters).

Yes

No

Specify the download path to the target OS computer.

Yes

No

For redundant servers: Assign redundancy partners.

[1], section titled "Arranging components"

Yes

No

Page 21: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 21/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

OS clients Table 3-6

Action Note/Reference Done Explanation/Reason

Insert the PC station. Yes

No

Set the HW configuration with a WinCC application client.

Yes

No

Specify the download path to the target OS computer.

Yes

No

For reference clients (as of PCS 7 V7.0): Enter a reference to the client project.

[1], section titled "Arranging components"

Yes

No

3.2.2 Plant view

Table 3-7

Action Note/Reference Done Explanation/Reason

Create the plant hierarchy for each subpro-ject.

Yes

No

Define the maximum number of hierarchy levels and characters, as well as the inte-gration into the designation system (HID).

Yes

No

Select "Derive picture hierarchy from the plant hierarchy" in the plant hierarchy set-tings.

[1], section titled "Creating the plant hier-archy"

Yes

No

Page 22: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 22/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

Every chart folder of the AS subprojects must be assigned to an AS.

Yes

No

Update the PH in the multiproject. Yes

No

Every chart folder of the OS subprojects must be assigned to an OS.

Yes

No

Insert pictures (*.pdl) into the appropriate chart folders of the OS subprojects.

The picture hierarchy (Picture Tree) is automatically generated in the OS during OS compilation in accordance with the settings in the SIMATIC Manager.

Yes

No

Check the PH consistency. [1], section titled "Creating the plant hier-archy"

Yes

No

Page 23: Checklist Configuration

Multiproject – Design and management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 23/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

3.3 Distributed engineering in the multiproject

Table 3-8

Requirement Note/Reference Adhered to Explanation/Reason

Supplementary conditions are met. [2], section titled "Conditions for additional editing in the multiproject"

Yes

No

The projects are located in folders which have been enabled for read and write ac-cess.

Yes

No

The share names are unique within the network.

Yes

No

Permissions and share names for the re-sources (folders) involved in the multipro-ject must not be changed.

Reason: When a project is inserted into the multipro-ject, PCS 7 generates a reference to the location of this project. The reference de-pends on the permission and the share name associated with this particular re-source.

Yes

No

PCS 7 must be installed on the computers where the folders with the projects are located.

PCS 7 provides the database server func-tions required to access the projects.

Yes

No

Page 24: Checklist Configuration

Configuration of the hardware (AS and I/O)

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 24/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

4 Configuration of the hardware (AS and I/O)

4.1 Automation system

General settings (H system and standard) Table 4-1

Action Note/Reference Done Explanation/Reason

Configure the interfaces (MPI, DP). Yes

No

"Startup" dialog Do not change the default settings for the CPU startup characteristics (restart).

Yes

No

"Cycle/Clock Memory" dialog Do not change the default settings.

Yes

No

"Cyclic Interrupts" dialog Set/configure the process image partitions.

Yes

No

"Memory" dialog Configure the local data.

Yes

No

"Diagnostics/Clock" dialog Configure time synchronization in the AS as a slave. Switch off ATR (after commissioning, at the latest).

Yes

No

Optional: Define the protection level/password.

[1], section titled "General CPU settings (H system and standard AS)"

Yes

No

<Specify password, if applicable>

Page 25: Checklist Configuration

Configuration of the hardware (AS and I/O)

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 25/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Special settings for H systems Table 4-2

Action Note/Reference Done Explanation/Reason

"H Parameters" dialog Set the "TROUBLESHOOTING" RAM/PIQ comparison error.

Yes

No

Calculate the monitoring times for updating the standby CPU.

Yes

No

Optional: "H Parameters" dialog Set the passivation scheme.

[1], section titled "Special settings for H systems"

Yes

No

4.1.1 CP 443-1 for plant bus

Table 4-3

Action Note/Reference Done Explanation/Reason

Assign a unique MAC address. Yes

No

"Options" dialog Select "Automatic setting" as the "Trans-mission medium/duplex".

Yes

No

"Time-of-Day Synchronization" dialog Activate time synchronization based on the SIMATIC procedure.

[1], section titled "Configuration of the Industrial Ethernet CP 443-1"

Yes

No

Page 26: Checklist Configuration

Configuration of the hardware (AS and I/O)

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 26/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

4.1.2 CP 443-5 Ext for fieldbus

Table 4-4

Action Note/Reference Done Explanation/Reason

"General" dialog Assign a PROFIBUS network (address "2").

Yes

No

"Network Settings" dialog Leave the default settings unchanged. • Transmission Rate:

1.5 Mbps • Profile: DP

Yes

No

"Operating Mode" dialog Set the "DP master" to "DPV1" DP mode.

Yes

No

"Options" dialog Activate time synchronization and data record routing.

[1], section titled "PROFIBUS settings on the CP 443-5 Ext"

Yes

No

Page 27: Checklist Configuration

Configuration of the hardware (AS and I/O)

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 27/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

4.2 IM 153-2, bus interface for S7-300

Table 4-5

Action Note/Reference Done Explanation/Reason

Observe the technical data, application information, and commissioning information contained in [7].

Yes

No

Operating parameters: Activate the "Replace modules during op-eration" option.

Yes

No

Assign PROFIBUS addresses. Yes

No

Optional: Set the time synchronization.

[1], section titled "I/O configuration"

Yes

No

4.3 I/O modules

Table 4-6

Action Note/Reference Done Explanation/Reason

Observe the technical data, application information, and commissioning information for S7-300 modules.

[8], general Yes

No

Analog input module: Set the measuring range via a measuring range module on the analog input module

The identification letter for the setting of the measuring range module can be vie-wed in the object properties for the rele-vant module, on the "Inputs" tab, to the

Yes

No

Page 28: Checklist Configuration

Configuration of the hardware (AS and I/O)

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 28/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason too. right of "Position of Measuring Range

Selection Module". The channel-specific setting "Reaction to CPU STOP" (OCV, KLV, USV) of a module within the ET 200M distributed I/O must be set identically for all channels.

OCV = Outputs have no current or voltage KLV = Keep last value USV = Use substitute value

Yes

No

Set the channel-specific diagnostics (wire break, short circuit) and signal limits of the I/O accordingly.

Yes

No

Define the symbolic names for the in-puts/outputs in the hardware configuration.

The driver blocks are assigned to the channels on the modules by means of symbolic names.

Yes

No

Activate the CiR capability for all PROFIBUS master systems.

[2], section titled "Configuring distributed I/O for configuration changes in RUN (CiR)" Only if using standard AS.

Yes

No

If using CiR: Take the number of CiR objects into ac-count when defining the process image (address range).

[2], section titled "Configuring distributed I/O for configuration changes in RUN (CiR)"

Yes

No

Page 29: Checklist Configuration

Configuration of the hardware (AS and I/O)

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 29/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

4.4 Configuring field devices

Table 4-7

Action Note/Reference Done Explanation/Reason

The field devices used meet the relevant international standards.

Yes

No

All the field devices used can be integrated via STEP 7, GSD, and EDD.

Yes

No

Install device files (GSD and EDD) for all devices.

[1], section titled "Basic information about device integration"

Yes

No

Activate the PDM check box for DP/PA links.

[1], section titled "Configuring and assign-ing parameters for field devices"

Yes

No

Observe the layout criteria for DP/PA. Yes

No

Observe the layout criteria for the Y link.

[1], section titled "Information on configur-ing field devices on the H system"

Yes

No

Observe the layout criteria for the DP/FF link.

[17], general Yes

No

Page 30: Checklist Configuration

Configuration of the network connections

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 30/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

5 Configuration of the network connections Table 5-1

Action Note/Reference Done Explanation/Reason

"Merge subnets" for Industrial Ethernet. [1], section titled "Merging networks in the multiproject"

Yes

No

Configure AS-OS connections. Yes

No

Configure AS-ES connections. Yes

No

Configure AS-AS connections.

The connections should be named for the AS involved. Connections from redundant OS servers, as well as from the ES, to the same AS must have the same name (e.g. "Connection_AS1"). [1], section titled "Configuring connecti-ons"

Yes

No

Download the connections (download complete stations from NetPro).

Always start with the engineering station when downloading stations. [1], section titled "Downloading connecti-ons"

Yes

No

Page 31: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 31/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

6 Configuration

6.1 AS configuration

Master data library Table 6-1

Action Note/Reference Done Explanation/Reason

Only blocks from the master data library may be used for configuration.

[2], section titled "Using the master data library"

Yes

No

Supply the master data library with data. [2], section titled "How to copy objects from other libraries to the master data library"

Yes

No

Save user-defined blocks in the master data library.

Yes

No

Adapt the message configuration of the blocks to the project in question.

[1], section titled "Changing the message class, priority, and message text"

Yes

No

Adapt the attributes of the blocks to the project in question.

[1], section titled "Changing attributes" Yes

No

Plan for a feedback strategy for the pa-rameters.

[1], sections titled "Downloading the user program with PCS 7 V7.0" and "Downloa-ding the user program with PCS 7 V6.1"

Yes

No

Enter and update the shared declarations for the entire multiproject in the master data library.

Declarations deleted from the master data library are not removed from the subpro-jects during updating.

Yes

No

Page 32: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 32/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

Update the block versions in the S7 pro-grams throughout the entire multiproject.

[1], section titled "Updating blocks in the S7 programs" If different programs contain various block versions, this can lead to conflicts in OS runtime mode. This is due to the fact that tags of the same block type (type name) have the same structure.

Yes

No

CFC Table 6-2

Action Note/Reference Done Explanation/Reason

Define ranges for separate blocks (FC and DB).

[1], section titled "Requirements for con-figuration in CFC"

Yes

No

Do not change/increase the number of blocks installed in each runtime group.

This can cause the SCL compiler to abort the compilation process.

Yes

No

Optimize the run sequence (property for each runtime group, depending on whether the project is old or new).

[2], section titled "How to optimize the run sequence" [1], section titled "Run sequence"

Yes

No

Enter the cycle load of the AS. [1], section titled "Cycle load and memory utilization of the AS"

Yes

No

Generate messages from I/O devices. [1], section titled "Enabling messages from I/O devices"

Yes

No

Create process tag types (templates) in the master data library.

[1], section titled "Process tag types (tem-plates)"

Yes

No

Page 33: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 33/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

SFC type Table 6-3

Action Note/Reference Done Explanation/Reason

Make general changes relating to an SFC type centrally at the type.

[1], section titled "Creating SFC charts" Changes are forwarded to the instances automatically, provided that the interfaces (e.g. input) to the instances have not been modified.

Yes

No

Transfer the UoM of the individual setpoints from the shared declarations.

Yes

No

6.2 Compiling and downloading

Compiling and downloading the user program Table 6-4

Action Note/Reference Done Explanation/Reason

Compilation options in PCS 7 V6.1: • Generate module drivers • Update sampling time • Delete empty runtime groups • Make textual interconnections Compilation option as of PCS 7 V7.0: • Generate module drivers

Yes

No

Only download the program to the AS from an open CFC or SFC.

[1], section titled "Downloading changes online"

Yes

No

Page 34: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 34/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

Prior to a full download: Ensure that the parameters are read back.

[1], section titled "Compiling and downlo-ading" This must be done before changes are made in CFC.

Yes

No

Compiling the OS Table 6-5

Action Note/Reference Done Explanation/Reason

We recommend using the "Area-oriented" compilation mode.

[1], section titled "Compiling and downlo-ading"

Yes

No

Downloading the OS Table 6-6

Action Note/Reference Done Explanation/Reason

Always download OS projects via the SIMATIC Manager (PLC Download).

Yes

No

Complete the download procedure suc-cessfully.

Yes

No

Download to redundant OS servers promptly.

[1], section titled "Downloading the OS projects"

Yes

No

Server data from the redundant OS servers must have the same time stamp.

This must be checked on the target com-puter (in the WinCC Explorer under "Ser-ver data").

Yes

No

Page 35: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 35/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

6.3 OS configuration

General Table 6-7

Action Note/Reference Done Explanation/Reason

Derive a project-specific "@PCS7Typicals.pdl" from the default. • Supplement with customized symbols • Adapt the available layouts

Software design specification

Yes

No

Set the computer's properties. • Startup characteristics • Language • Graphics runtime

Yes

No

Make settings in the OS project editor. [1], section titled "Working with the OS project editor"

Yes

No

Page 36: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 36/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

User administration Table 6-8

Action Note/Reference Done Explanation/Reason

Optional: Use SIMATIC Logon.

[4], general Only the user groups need to be config-ured. The users are managed in the user ad-ministration system of Windows or the domain.

Yes

No

Define user groups with permissions. Notice: The emergency user becomes active if a user who does not belong to any of the configured user groups logs on. No (or very few) permissions should be granted to the emergency user.

Yes

No

If using SIMATIC Logon: Do not activate the automatic logoff func-tion in the User Administrator.

Activate "Automatic logoff" in the SIMATIC Logon configuration. Advantage: A notice appears before the user is actu-ally logged off.

Yes

No

Page 37: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 37/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Redundancy Table 6-9

Action Note/Reference Done Explanation/Reason

Establish a physical connection between the redundant partners. • Serial interface, or • Additional network I/O

Yes

No

Activate the redundancy options in accor-dance with your requirements.

"Redundancy" editor [1], section titled "Redundancy settings in the server project"

Yes

No

Time synchronization Table 6-10

Action Note/Reference Done Explanation/Reason

Make the settings for synchronizing the process bus.

Yes

No

Make the settings for synchronizing the OS clients.

[1], section titled "Time synchronization"

Yes

No

Graphics Designer (GraCS) Table 6-11

Action Note/Reference Done Explanation/Reason

Set a uniform picture size. Adapted to the monitors of the OS clients Yes

No

Check the language settings in the pic- You can check the language settings by

Page 38: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 38/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason tures. opening a picture and selecting the "View"

menu command. Yes No

Check: Under Options -> Settings -> "Paste/copy object(s)" options "To previous layer" must be selected.

Define the system characteristics when configuring the picture (layer 0 to 15). Objects are pasted back into the layer from which they were copied for the origi-nal picture.

Yes

No

OS client project Table 6-12

Action Note/Reference Done Explanation/Reason

Assign the server data for every OS client project.

[1], section titled "Defining the server as-signment" OS server data only has to be downloa-ded to the OS clients once. The OS server data is updated automati-cally each time an OS client is started in process mode or when changes are downloaded to the OS servers.

Yes

No

For redundant OS servers: Select the preferred server.

[1], section titled "Selecting a preferred server"

Yes

No

For redundant OS servers: The standard server is selected for each OS client.

[1], section titled "Selecting and configur-ing a standard server"

Yes

No

Configure the User Administrator for each OS client project.

Yes

No

Page 39: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 39/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Archiving (take the performance of the OS servers into account) Table 6-13

Action Note/Reference Done Explanation/Reason

The mean value for saving all archive tags must not exceed 1,000/s for each OS ser-ver. (TagLogging Fast + TagLogging Slow <= 1,000 values/s)

When compiling the OS, set the minimum cycle to the slowest possible value. Check the current values with runtime activated in tag management. "Internal Tags > TagloggingRT > @TLGRT_AVERAGE_TAGS_PER_SECOND"

Yes

No

Evaluate the frequency of individual mes-sages and the average volume of message traffic as a "continuous load" during the FAT/commissioning phase. Max. 10 mes-sages per server.

Use interrupt control in a process picture and assign parameters to it as a hit list. WinCC Information System search string: Hit list

Yes

No

Script functions Table 6-14

Action Note/Reference Done Explanation/Reason

Check that the scripts are correct using APDiag during the commissioning/FAT phase.

WinCC Information System search string: APDiag

Yes

No

Page 40: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 40/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Web option Table 6-15

Action Note/Reference Done Explanation/Reason

Use the relevant manual to find and imple-ment a concept for integrating the Web server into the existing plant (router, fire-wall settings, IPsec transfer).

[16], general

Yes

No

Assign parameters for the IIS (Internet Information Service) on the target computer (OS client = Web server) or the OS single station via the Web Configurator.

Yes

No

Publish pictures and scripts (in the case of a server/client structure, the Web server and connected OS servers must be run through multiple times).

Yes

No

Logon for Web access created in the User Administrator with start screen "@Screen.pd_" and language selection.

Yes

No

Make security settings in Internet Explorer according to the instructions contained in the relevant manual.

[11], general

Yes

No

Page 41: Checklist Configuration

Configuration

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 41/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

Install the WebNavigator client for Internet Explorer with administrator rights (downlo-ad from Web server or install from the PCS 7 Toolset DVD). Install up-to-date plug-ins in Internet Explorer.

Yes

No

Central archive server (CAS) Table 6-16

Requirement Note/Reference Adhered to Explanation/Reason

The archive segments in the "ArchiveDir" folder, which have been swapped out from the OS servers, must always be smaller than an individual segment in the CAS (size of the backup medium).

[12], general

Yes

No

Page 42: Checklist Configuration

Changing projects in process mode

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 42/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

7 Changing projects in process mode

7.1 Downloading changes online

Table 7-1

Requirement Note/Reference Adhered to Explanation/Reason

Only download the AS from an open CFC or SFC.

[1], section titled "Downloading changes online"

Yes

No

The AS and the OS must be downloaded promptly.

[1], section titled "Downloading changes online" A temporary data inconsistency arises be-tween AS and OS data while the "Download changes" function is being exe-cuted.

Yes

No

Page 43: Checklist Configuration

Changing projects in process mode

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 43/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

7.2 Complete online download to a redundant OS server pair

The following order must be observed: Table 7-2

Action Note/Reference Done Explanation/Reason

Compile the project of the master OS (complete or changes only).

Yes

No

Close the OS project on the master OS (> redundancy switchover). We recommend that you restart the PC ("master") at this point. Keep the OS project data on the server.

Yes

No

Download the OS project to the OS server ("Entire OS" is the only option which can be selected).

Yes

No

Wait for the message indicating that the download has been completed success-fully.

Yes

No

Start the OS server (> stdby mode). Yes

No

Wait for the redundancy update to be per-formed (> process control message).

Yes

No

Proceed in exactly the same way for the other server.

[1], section titled "Complete online down-load to a redundant OS server pair"

Yes

No

Page 44: Checklist Configuration

Asset management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 44/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

8 Asset management

8.1 Requirement

Table 8-1

Requirement Note/Reference Adhered to Explanation/Reason

All the projects of the multiproject use the same message concept.

Yes

No

Component names are restricted in the hardware configuration to a maximum of 14 characters.

Yes

No

Driver blocks from PCS 7 library V6.1 SP1 or earlier are used.

Yes

No

Module drivers have been generated for all AS without any errors.

Yes

No

OS compilation mode is set to "Area-oriented" for all subprojects of the multipro-ject.

Yes

No

All field devices are assigned with the PDM.

Yes

No

A maintenance project is entered in the PDM settings.

Yes

No

All projects in the multiproject have the same PH settings.

Yes

No

The six PH levels required for asset man-

[1], section titled "Integrated asset man-agement"

Page 45: Checklist Configuration

Asset management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 45/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Note/Reference Adhered to Explanation/Reason agement are set. Yes No The names of the S7 programs are unique throughout the entire multiproject and do not contain any blanks.

Yes

No

The picture hierarchy is derived from the PH.

Yes

No

NDIS driver is installed on the MS server, if CP 1613 is used.

Yes

No

8.2 Configuration

Table 8-2

Action Note/Reference Done Explanation/Reason

MS stations (MS client, MS server) are inserted in the multiproject.

Yes

No

Configure the monitoring of network objects and the PC via SNMP in the SIMATIC NET OPC server.

Yes

No

Update the diagnostic screens. Yes

No

Export the SNMP tags for WinCC. Yes

No

Compile the OS once the diagnostic screens have been updated.

[1], section titled "Integrated asset man-agement"

Yes

No

Page 46: Checklist Configuration

Asset management

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 46/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Action Note/Reference Done Explanation/Reason

Download the PC configuration of the MS server (OPC server).

Yes

No

Download the OS server and MS server. Yes

No

Activate "detailed diagnostics" on the OS client computer (as of PCS 7 V7.0).

Yes

No

8.3 Runtime

Table 8-3

Requirement Note/Reference Adhered to Explanation/Reason

The MS client is an OS client on the master ES.

Yes

No

The project which is valid for operating the plant must be stored on the MS client.

Yes

No

Page 47: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 47/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

9 Installation guidelines

Note You can find other F-specific installation guidelines in the "Configuration" checklist relating to the PCS 7 Compendium Part B "Process Safety".

9.1 Installation

Table 9-1

Requirement Note/Reference Adhered to Explanation/Reason

EMC/ESD • Handling of modules during installation

and testing • Suitability of

– Floor – Storage areas/tables – Cabinet (where spare parts are sto-

red) • ESD set available (grounding bracelet,

ESD mat, shoe grounding strips, etc.) • Staff training

Record this information, as non-compliance could cause a warranty to become void. See the ESD inserts for the relevant modules.

Yes

No

Page 48: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 48/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Note/Reference Adhered to Explanation/Reason

Cabinet configuration • Voltage supply isolated from signal cables • Shield plates for transformers, reactors,

busbars, line filters • Shield support at the entrance to the ca-

binet • Cable entry • Cable grip • Sealing/dust protection/temperature • Marking of all elements • PE for doors, side walls, and support pla-

tes • Contact washers • Cross-section of PE connection • Overvoltage protection • Power consumption • Diagnostics (undervoltage, fuse blown,

faulty devices) • Standby/CiR preparation

Yes

No

PC and server Adhere to the installation guidelines for PCs provided in the relevant operating instructions. • Stability/mounting • Connecting cable

– Bending radii – Mounting/fuses

[10], sections titled: • "Application planning" • "Mounting" • "Connecting"

Yes

No

Page 49: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 49/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Note/Reference Adhered to Explanation/Reason • Ambient and environmental conditions

– Dust (deposits) – Moisture – Vibration (yes/no) – Temperature (measured value) – Chem. influences – Air conditioning system (with/without

recorder/signaling device) • Sufficient aeration and ventilation • Equipotential bonding • Access

– Safety – Maintenance/replacement

• Protection, see also section on UPS AS/rack Adhere to the installation guidelines for auto-mation systems provided in the relevant soft-ware installation manual. • Installation • Ambient and environmental conditions • Backup batteries OK? • PROFIBUS connection for diagnostics

[15], sections titled: • "Installing the S7-400" • "Wiring the S7-400" • "Appendix A, Assembling and in-

stalling systems" [18], section titled "General technical specifications"

Yes

No

I/O Adhere to the installation guidelines for the ET 200M/iSP/S. • Installation

[11], sections titled: • "Application planning" • "Installing" [17], section titled "Installing"

Yes

No

Page 50: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 50/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Note/Reference Adhered to Explanation/Reason • Ambient and environmental conditions • CiR preparations and standby • PROFIBUS connection for diagnostics

[18], section titled "General technical specifications"

MTA • Grounding (shields, PE) • Red. voltage supply/UPS

Yes

No

<Cross-section, length, terminal for grounding>

Network (LAN) Adhere to the installation guidelines for Ether-net networks. • Installation • Bending radii • Equipotential bonding and shielding

(shared grounding for all cabinets and components which are connected by means of power supply cords without gal-vanic isolation)

• Diagnostics • Documentation, marking • Access • Cable test logged • Redundant voltage supply/UPS

[13], sections titled: • "Guidelines for installing networked

automation systems in buildings" • "Installing network components in

cubicles"

Yes

No

PROFIBUS (fieldbus) Adhere to the installation guidelines for PROFIBUS networks. • Installation • Equipotential bonding and shielding

[14], sections titled: • "Appendix C, Installing LAN

cables" • "Appendix D" • "Appendix E, Installing network

Yes

No

Page 51: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 51/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Note/Reference Adhered to Explanation/Reason • CiR preparations components in cubicles"

PROFIBUS Installation Guideline and PROFIBUS Commissioning Guideline (from PNO: www.profibus.de)

Other data connections • Serial connections, e.g. measuring or

diagnostic devices, third-party systems, RK512

• Modbus • Printers • Package units

Yes

No

Voltage supply • Shield plates • Line filters • Compensation equipment • Lightning and overvoltage protection • Neutral/ground • Ground connection/PE

Is a measuring log available?

Yes

No

<Rated voltage, voltage peaks, har-monic content, rated power, reserve>

UPS concept • Server – Backup and automatic shutdown • Controlled plant shutdown • AS, I/O, MTA, sensors, actuators • Protection • Documentation • Battery

Yes

No

Page 52: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 52/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Note/Reference Adhered to Explanation/Reason • Power, bypass time, reserve • UPS bypass • Diagnostics • Emergency unit • Emergency supply for pressurized air

used for operation Ex signals • Disconnected cable channel blue • Lightning protection • Shield grounding • Transmitter grounding • ET 200M thread distance:

– Barrier – Cable guide – Cover and marking

• ET 200iSP cabinet, take note of the rele-vant approval

• PROFIBUS RS485iS installed • For installation in zone 2, manufacturer's

declaration available for the enclosure

[11], section titled "Using modules in zone 2 areas at risk of explosions" [19], general [20], general [17], section titled "Installing" ET 200iSP Intrinsic Safety Control Drawing A5E00455287-0 PROFIBUS Guideline (from PNO: www.profibus.de)

Yes

No

<Specify the class for Ex signals>

Page 53: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 53/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

9.2 Grounding concept

Table 9-2

Requirement Adhered to Explanation/Reason

Grounding concept with ground strip covering the entire factory/building Yes

No

Check of other neutral points with insecure/no connections Yes

No

Steel structure included Yes

No

Pipeline network included Yes

No

Cable routes included Yes

No

Other metal parts (railings, concrete reinforcements, frames, door frames, false-floor structures, etc.) included

Yes

No

Flow sensors correctly grounded/insulated Yes

No

Transmitter enclosure grounded Yes

No

Danger of circulating currents due to large magnetic fields, inductances, or current lines assessed

Yes

No

Grounding points in different parts of the plant or different buildings sufficiently connected to one another

Yes

No

Page 54: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 54/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Adhered to Explanation/Reason

N and PE connected (PEN) Yes

No

Voltage supply and UPS connected to the same ground electrode Yes

No

Installation with non-grounded reference potential If your installation has a grounded reference potential, please go to Table 9-4.

Table 9-3

Requirement Adhered to Explanation/Reason

Adhere to the wiring guidelines contained in the relevant manuals. Yes

No

Remove the jumper from reference potential M and the rack on the programmable con-trollers.

Yes

No

Remove the jumper from reference potential M and the functional ground at the ET 200M/iSP power supply.

Yes

No

Galvanic isolation in place for the PCs Yes

No

Cabinet/mounting structure connected to the central grounding point (e.g. main ground line) via a PE cable

Yes

No

Rack connected to the central grounding point via a cable with a minimum cross-section of 10 mm2, if racks are not installed in the cabinet and not connected to one another by means of large-surface ferrous parts

Yes

No

Page 55: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 55/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

Requirement Adhered to Explanation/Reason

PROFIBUS shield insulated in the connector to the nodes (modules) Yes

No

Ground-fault monitoring available/tested/diagnostic message Calculate the following measured values: • Resistance between M and PE • Voltage between M and PE during operation • Common mode voltage of signals from 4-wire transmitters

Yes

No

Installation with grounded reference potential Table 9-4

Requirement Adhered to Explanation/Reason

Adhere to the wiring guidelines contained in the relevant manuals. Yes

No

Insert a jumper for reference potential M and the rack on the programmable controllers. Yes

No

Insert a jumper for reference potential M and the functional ground at the ET 200M/iSP power supply.

Yes

No

Cabinet mounting structure connected to the central grounding point (e.g. main ground line) via a PE cable

Yes

No

Rack connected to the central grounding point via a cable with a minimum cross-section of 10 mm2, if racks are not installed in the cabinet and not connected to one another by means of large-surface ferrous parts

Yes

No

Page 56: Checklist Configuration

Installation guidelines

Checklist "PCS 7 Configuration"

V 1.0 26.03.2009 56/56

Cop

yrig

ht ©

Sie

men

s A

G 2

009

All

right

s re

serv

ed

9.3 Lightning and overvoltage protection

Table 9-5

Requirement Adhered to Explanation/Reason

Measures for lightning and overvoltage protection have been put in place as per the rele-vant installation manuals.

Yes

No

Coarse protection used Yes

No

<Specify the type of protection used>

Fine protection used Yes

No

<Specify the type of protection used>

All components are located within the building/inside the conductor electrode around the building.

Yes

No

<If "no", list the components affected>

Lightning conductor grounded (reactions on PE restricted) Yes

No

<Where grounded/connected to conduc-tor electrode around the building>

Available aerials (WLAN, GSM, etc.) and cameras are integrated in the concept/insulated. Yes

No