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
Contents
Checklist "PCS 7 Configuration"
Contents
1 1.1 1.2 1.3 2 2.1 2.2 2.3 2.4 3 3.1 3.2 3.2.1 3.2.2 3.3 4 4.1 4.1.1 4.1.2 4.2 4.3 4.4 5 6 6.1 6.2 6.3 7 7.1 7.2 8 8.1 8.2 8.3 9 9.1
Introduction..................................................................................................... 4 Subject of the document ................................................................................... 4 References to other sources............................................................................. 5 Abbreviations .................................................................................................... 6 PC administration ........................................................................................... 7 PC settings ....................................................................................................... 7 Installing PCS 7 (including options) ................................................................ 11 Network settings ............................................................................................. 13 Creating a backup/image................................................................................ 14 Multiproject Design and management ..................................................... 15 Requirements ................................................................................................. 15 Creating the multiproject................................................................................. 18 Arranging and configuring the components .................................................... 18 Plant view ....................................................................................................... 21 Distributed engineering in the multiproject...................................................... 23 Configuration of the hardware (AS and I/O) ............................................... 24 Automation system ......................................................................................... 24 CP 443-1 for plant bus.................................................................................... 25 CP 443-5 Ext for fieldbus................................................................................ 26 IM 153-2, bus interface for S7-300 ................................................................. 27 I/O modules .................................................................................................... 27 Configuring field devices................................................................................. 29 Configuration of the network connections ................................................ 30 Configuration ................................................................................................ 31 AS configuration ............................................................................................. 31 Compiling and downloading............................................................................ 33 OS configuration ............................................................................................. 35 Changing projects in process mode........................................................... 42 Downloading changes online.......................................................................... 42 Complete online download to a redundant OS server pair ............................. 43 Asset management....................................................................................... 44 Requirement ................................................................................................... 44 Configuration .................................................................................................. 45 Runtime .......................................................................................................... 46 Installation guidelines .................................................................................. 47 Installation....................................................................................................... 47
Copyright Siemens AG 2009 All rights reserved
V 1.0
26.03.2009
2/56
Contents
9.2 9.3
Grounding concept ......................................................................................... 53 Lightning and overvoltage protection.............................................................. 56
V 1.0
26.03.2009
3/56
Introduction
1
1.1
Introduction
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.
V 1.0
26.03.2009
4/56
Introduction
1.2
Table 1-1
References to other sources
Ref. no. [1] [2] [3] [4] [5] [6] [7]

Name PCS 7 Process Control System Compendium Part A Configuration Guidelines Process Control System PCS 7 V7.0 SP1 Engineering System Configuration Manual PCS 7 - PC Configuration and Authorization SIMATIC Logon Configuration Manual Process Control System PCS 7 Time Synchronization Process Control System PCS 7 V7.0 Programming Instructions for Blocks Distributed I/O Device ET 200M Automation System S7-300 Module Data Process Control System PCS 7 V7.0 SP1 Released PCS 7 Modules Industry PC SIMATIC Rack PC 547B Process Control System PCS 7 V7.0 SP1 PCS 7 OS Web Option Process Control System PCS 7 V7.0 SP1 Operator Station SIMATIC NET Twisted-Pair and Fiber-Optic Networks SIMATIC NET PROFIBUS Networks Automation System S7-400 Hardware and Installation PCS 7 V6.1: "PCS 7 Security Concept Recommendations and Notes" PCS 7 V7.0: "Security Concept PCS 7 and WinCC Basic Document"
ID A5E02122386-01 A5E00808639-02 A5E00783464-02 A5E00496671-04 A5E01216577-01 A5E00978907-01 EWA-4NEB780600601-08 A5E00105504-03 A5E01006283-02 A5E01127518-02 A5E00808636-02 A5E00808628-02 C79000G8900C12502 6GK19705CA200AA0 6ES7498-8AA05-8AA0 A5E00477558-01 A5E02128732-01 A5E00247482-03 A5E00267833-03 A5E00206200-02 A5E00172006-09 A5E01017498-01
[8] [9] [10] [11] [12] [13] [14] [15] [16]
[17] [18] [19] [20] [21]
Distributed I/O Device ET 200iSP Automation System S7-400 Module Data SIMATIC Principles of Explosion Protection Automation Systems S7-300, ET 200M Ex I/O Modules DP/FF Link
V 1.0
26.03.2009
5/56
Introduction
1.3
Abbreviations
The following abbreviations are used in this document:
Table 1-2
Abbreviation APDiag AS OCV CFC CiR EMC ES

Meaning WinCC diagnostic tool Automation system Outputs have no current or voltage Continuous function chart Configuration in Run Electromagnetic compatibility Engineering station Electrostatic sensitive device Use substitute value Factory acceptance test Hardware design specification Commissioning Industry PC (preinstalled PC bundle) Keep last value Marshaled termination assembly Operator station Protective earth Archiving tool available in PCS 7 Acknowledgment-triggered reporting Software design specification Sequential function chart Simple network management protocol SIMATIC Security Control (tool at end of setup) Plant hierarchy Unit of measurement
ESD USV FAT HDS Comm. IPC KLV MTA OS PE PKZIP ATR SDS SFC SNMP SSC PH UoM
V 1.0
26.03.2009
6/56
PC administration
2
2.1
PC administration
PC settings
Using IPCs If using non-IPCs, please go to Table 2-2.

Table 2-1
Action Define computer names correctly prior to installation. No special characters Max. 15 characters Capital letters only First character must be a letter Define bus addresses (IP and MAC).
Note/Reference [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"). Create a list of all components which are assigned a separate address. [1], section titled "Network settings" [3], general
Done
Explanation/Reason
Yes
No
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. Optional: Allocate a separate partition (NTFS format) for images on the computers. V 1.0
Yes Image files can be stored here. [3], section titled "Hard disk partitioning"
No
Yes
No
26.03.2009
7/56
PC administration
Action Optional: Allocate a separate partition (NTFS format) for licenses on the computers. Optional: Install other Microsoft security patches and hotfixes (as advised by IT Security).
Note/Reference This partition should be excluded from defragmentation programs. You must install the patches and hotfixes in the same language as that of the operating system used. [3], section titled "Installing security patches" [3], section titled "Preparing PC stations" [4], general "Control Panel > Date and Time" [1], section titled "Time synchronization"
Done
Explanation/Reason
Yes
No
Yes
No
If using SIMATIC Logon: Create user groups in the user administration system of Windows or the domain. Check/adjust the time settings on every PC.
Yes
No
Yes
No
V 1.0
26.03.2009
8/56
PC administration
Using non-IPCs
Table 2-2
Action Define computer names correctly prior to installation. No special characters Max. 15 characters Capital letters only First character must be a letter Define bus addresses (IP and MAC).
Note/Reference [1], section titled "Installation" The computer name cannot be changed once PCS 7 has been installed.
Done
Explanation/Reason
Yes
No
Create a list of all components which are assigned a separate address. [1], section titled "Network settings" [3], general [4], section titled "Installation of software, software requirements" [3], general
Yes
No
Check the PCS 7 installation 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. Allocate a separate partition (NTFS format) for the system on the computers. Allocate a separate partition (NTFS format) for data on the computers.
Yes System data (installation) is saved on this partition. [3], section titled "Hard disk partitioning" Project data should be saved on this partition. [3], section titled "Hard disk partitioning" 26.03.2009
No
Yes
No
Yes
No
V 1.0
9/56
PC administration
Action Optional: Allocate a separate partition (NTFS format) for images on the computers. Optional: Allocate a separate partition (NTFS format) for licenses on the computers.
Note/Reference Image files can be stored here. [3], section titled "Hard disk partitioning" This partition should be excluded from defragmentation programs. You must install the patches and hotfixes in the same language as that of the operating system used. [3], section titled "Installing security patches" [3], section titled "Preparing PC stations" [4], general "Control Panel > Date and Time" [1], section titled "Time synchronization"
Done
Explanation/Reason
Yes
No
Yes
No
Optional: Install other Microsoft security patches and hotfixes (as advised by IT Security).
Yes
No
If using SIMATIC Logon: Create user groups in the user administration system of Windows or the domain. Check/adjust the time settings on every PC.
Yes
No
Yes
No
V 1.0
26.03.2009
10/56
PC administration
2.2
Installing PCS 7 (including options)
ES, OS server, OS clients

Table 2-3
Action
Note/Reference [3], section titled "How to install the PCS 7 software"
Done Yes Yes No No No
Explanation/Reason
Administrator rights (as a minimum) are required to log on at the Windows level. Install the Microsoft patches supplied. Install the appropriate SQL server (take the PCS 7 version into account). Installation using the PCS 7 setup. The steps in the installation menu must always be followed. All the required packages (PCS 7 Engineering, 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. The following applies to PCS 7 V7.0: SSC settings successfully accepted at the end of the installation procedure (confirmation message from SSC).
Yes
<Enter the versions, if necessary>
Yes
No
Yes
No
V 1.0
26.03.2009
11/56
PC administration
Action The PCS 7 software must be kept up to date.
Note/Reference 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)
Done
Explanation/Reason
Yes
No
Authorizations/Licenses
Table 2-4
Action Check that the PC is free of viruses prior to installing/uninstalling all authorizations.
Note/Reference 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 viruses between the hard disk and the medium. [3], section titled "Virus scanners" "Start > SIMATIC > License Management > Automation License Manager"
Done
Explanation/Reason
Yes
No
Transfer licenses via the Automation License Manager (ALM).
Yes
No
V 1.0
26.03.2009
12/56
PC administration
Documentation
Table 2-5
Action File all the software which has been supplied and installed, together with the relevant descriptions/manuals, in a wellordered manner. Make a record of the documentation in the computer logbook.
Note/Reference "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)
Done
Explanation/Reason
Yes
No
2.3
Table 2-6
Network settings
Action Configure the terminal bus. Check the availability of all partners on the bus using SIMATIC Shell. The name resolution of all computers is available. Address the network switches on the terminal bus.
Note/Reference [1], section titled "Configuring the terminal bus"
Done Yes Yes Yes Yes No No No No
Explanation/Reason
V 1.0
26.03.2009
13/56
PC administration
Action Configure the plant bus (CP 1613, BCE cards). Address the network switches on the plant bus.
Note/Reference [1], section titled "Configuring the plant bus"
Done Yes Yes No No
Explanation/Reason
2.4
Table 2-7
Creating a backup/image
Action Create an image of the installation.
Note/Reference We recommend that you use the "SIMATIC PC/PG Image & Partition Creator" utility software (order number 6ES7648-6AA01-0YX0).
Done Yes No
Explanation/Reason
V 1.0
26.03.2009
14/56
Multiproject Design and management
3
3.1
Table 3-1

Requirements
Requirement
Note/Reference [2], section titled "Planning the plant engineering"
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, engineering concept, operating concept). 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.
Yes
No
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], section titled "Creating user-defined driver blocks". 26.03.2009
Yes
No
V 1.0
15/56
Requirement Create the Software Design Specification. The SDS defines the structure of the multiproject and all the SW types to be created.
Note/Reference The multiproject is divided into various subprojects based on technological and local conditions, as well as configurationspecific requirements such as the number of project engineers, or job-specific conditions. [1], section titled "Creating and managing the PCS 7 project" Naming conventions for the multiproject, projects, hierarchy folders, symbols, server data, connections, and hardware, for example. Define the location identifier and plant designation. [1], section titled "General project rules" Define the number and layout; plan for reserves. Requirement for creating the plant hierarchy Requirement for creating process tags
Adhered to
Explanation/Reason
Yes
No
Define the naming conventions.
Yes
No
Define the area overview. Define the plant structure. Define process tag lists. Define symbolic address lists. Define the network structures for terminal buses, plant buses, and fieldbuses.
Yes Yes Yes
No No No No No
Requirement for hardware and connection configurations Requirement for the hardware configuration
Yes Yes
V 1.0
26.03.2009
16/56
Requirement All engineering work must be performed on the ES (or multiple engineering stations) before the OS projects are downloaded to the OS computers.
Note/Reference 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 The OS project can be called in simulation mode using the "Start OS Simulation" option. In cases such as this, the OS project is duplicated on the ES and the copy is activated. Online access requires a connection to be available between the ES and the OS in NetPro. All users of the project use the same blocks and process tag types. Only one (redundant) time server is available 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 [2], general and [1], section titled "Sharing out engineering work"
Adhered to
Explanation/Reason
Yes
No
The OS project must not be activated on the ES.
Yes
No
Define the concept for the master data library. Define the concept for time synchronization.
Yes
No
Yes
No
Optional: Define the concept for multiproject/multiuser engineering.
Yes
No
V 1.0
26.03.2009
17/56
3.2
3.2.1
Creating the multiproject

Arranging and configuring the components
Multiproject
Table 3-2
Action
Note/Reference [1], sections titled "Automatically creating a multiproject" and "Integrating additional ES/OS subprojects" [2], section titled "Basic concepts of engineering"
Done
Explanation/Reason
Creating a multiproject, together with all required subprojects, in the SIMATIC Manager. AS OS servers and OS clients ES Master data library Assign unique names to the subprojects and stations. Set the language of the display devices for all subprojects.
Yes
No
[1], section titled "Integrating additional ES/OS subprojects" The language of the display devices is relevant for transferring messages from the engineering system to the OS (compilation 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 process mode. [1], section titled "Automatically creating a multiproject"
Yes
No
Yes
No
V 1.0
26.03.2009
18/56
Engineering station
Table 3-3
Action Insert the PC station. Set and address the HW configuration with a WinCC application and CP 1613 or general IE. Assign parameters for CP 1613 or general IE time synchronization. Download the engineering station's HW Config to the Station Configuration Editor using the "Configure Target System" function (take note of the "PC internal" setting).
Note/Reference [1], section titled "Arranging components" [2], section titled "Basic concepts of engineering" and [5], general
Done Yes Yes Yes No No No
Explanation/Reason
Yes
No
Automation system
Table 3-4
Action Insert the AS (standard and fault-tolerant). Insert additional CPs used for PROFIBUS and Ethernet. Assign unique names for all S7 programs in the multiproject in the SIMATIC Manager. V 1.0
Note/Reference [1], section titled "Arranging components"
Done Yes No No No
Explanation/Reason
Multiple PROFIBUS DP master systems, for example. Do not use blanks.
Yes Yes
26.03.2009
19/56
OS servers
Table 3-5
Action Insert the PC station. Set the HW configuration with a WinCC application and CP 1613. CP 1613 - time synchronization: Activate "Time-of-day mode" and "Send slave keep alive for connections". Assign a unique MAC address to the CP 1613. Assign meaningful symbolic computer names (no special characters). Specify the download path to the target OS computer. For redundant servers: Assign redundancy partners.
Done Yes Yes No No
Explanation/Reason
Yes
No
Yes Yes Yes Yes
No No No No
V 1.0
26.03.2009
20/56
OS clients
Table 3-6
Action Insert the PC station. Set the HW configuration with a WinCC application client. Specify the download path to the target OS computer. For reference clients (as of PCS 7 V7.0): Enter a reference to the client project.
Done Yes No No No No
Explanation/Reason
Yes Yes Yes
3.2.2
Table 3-7
Plant view
Action Create the plant hierarchy for each subproject. Define the maximum number of hierarchy levels and characters, as well as the integration into the designation system (HID). Select "Derive picture hierarchy from the plant hierarchy" in the plant hierarchy settings. V 1.0
Note/Reference [1], section titled "Creating the plant hierarchy"
Done Yes Yes No No
Explanation/Reason
Yes
No
26.03.2009
21/56
Action Every chart folder of the AS subprojects must be assigned to an AS. Update the PH in the multiproject.
Note/Reference
Explanation/Reason
Every chart folder of the OS subprojects must be assigned to an OS. 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. [1], section titled "Creating the plant hierarchy"
Yes
Yes
No
Check the PH consistency.
Yes
No
V 1.0
26.03.2009
22/56
3.3
Table 3-8
Distributed engineering in the multiproject
Requirement Supplementary conditions are met.

Note/Reference [2], section titled "Conditions for additional editing in the multiproject"
Adhered to Yes Yes Yes No No No
Explanation/Reason
The projects are located in folders which have been enabled for read and write access. The share names are unique within the network. Permissions and share names for the resources (folders) involved in the multiproject must not be changed. Reason: When a project is inserted into the multiproject, PCS 7 generates a reference to the location of this project. The reference depends on the permission and the share name associated with this particular resource. PCS 7 provides the database server functions required to access the projects.
Yes
No
PCS 7 must be installed on the computers where the folders with the projects are located.
Yes
No
V 1.0
26.03.2009
23/56
Configuration of the hardware (AS and I/O)
4
4.1

Automation system
General settings (H system and standard)

Table 4-1
Action
Note/Reference [1], section titled "General CPU settings (H system and standard AS)"
Done Yes No
Explanation/Reason
Configure the interfaces (MPI, DP). "Startup" dialog Do not change the default settings for the CPU startup characteristics (restart). "Cycle/Clock Memory" dialog Do not change the default settings. "Cyclic Interrupts" dialog Set/configure the process image partitions. "Memory" dialog Configure the local data. "Diagnostics/Clock" dialog Configure time synchronization in the AS as a slave. Switch off ATR (after commissioning, at the latest). Optional: Define the protection level/password.
Yes
No
Yes Yes Yes
No No No
Yes
No
<Specify password, if applicable> Yes No
V 1.0
26.03.2009
24/56
Special settings for H systems

Table 4-2
Action "H Parameters" dialog Set the "TROUBLESHOOTING" RAM/PIQ comparison error.
Note/Reference [1], section titled "Special settings for H systems"
Done
Explanation/Reason
Yes
No
Calculate the monitoring times for updating the standby CPU. Optional: "H Parameters" dialog Set the passivation scheme.
Yes
No
Yes
No
4.1.1
Table 4-3
CP 443-1 for plant bus
Action Assign a unique MAC address. "Options" dialog Select "Automatic setting" as the "Transmission medium/duplex". "Time-of-Day Synchronization" dialog Activate time synchronization based on the SIMATIC procedure.
Note/Reference [1], section titled "Configuration of the Industrial Ethernet CP 443-1"
Done Yes No
Explanation/Reason
Yes
No
Yes
No
V 1.0
26.03.2009
25/56
4.1.2
Table 4-4
CP 443-5 Ext for fieldbus
Action "General" dialog Assign a PROFIBUS network (address "2").

Note/Reference [1], section titled "PROFIBUS settings on the CP 443-5 Ext"
Done
Explanation/Reason
Yes
No
"Network Settings" dialog Leave the default settings unchanged. Transmission Rate: 1.5 Mbps Profile: DP "Operating Mode" dialog Set the "DP master" to "DPV1" DP mode. "Options" dialog Activate time synchronization and data record routing.
Yes
No
Yes
No
Yes
No
V 1.0
26.03.2009
26/56
4.2
Table 4-5
IM 153-2, bus interface for S7-300
Action Observe the technical data, application information, and commissioning information contained in [7].
Note/Reference [1], section titled "I/O configuration"
Done
Explanation/Reason
Yes
No
Operating parameters: Activate the "Replace modules during operation" option. Assign PROFIBUS addresses.
Yes
No
Yes Optional: Set the time synchronization. Yes
No No
4.3
Table 4-6
I/O modules
Action Observe the technical data, application information, and commissioning information for S7-300 modules. Analog input module: Set the measuring range via a measuring range module on the analog input module V 1.0 [8], general
Note/Reference
Done
Explanation/Reason
Yes The identification letter for the setting of the measuring range module can be viewed in the object properties for the relevant module, on the "Inputs" tab, to the 26.03.2009
No
Yes
No
27/56
Action too. 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.
Note/Reference right of "Position of Measuring Range Selection Module". OCV = Outputs have no current or voltage KLV = Keep last value USV = Use substitute value
Done
Explanation/Reason
Yes
No
Set the channel-specific diagnostics (wire break, short circuit) and signal limits of the I/O accordingly. Define the symbolic names for the inputs/outputs in the hardware configuration. Activate the CiR capability for all PROFIBUS master systems. The driver blocks are assigned to the channels on the modules by means of symbolic names. [2], section titled "Configuring distributed I/O for configuration changes in RUN (CiR)" Only if using standard AS. [2], section titled "Configuring distributed I/O for configuration changes in RUN (CiR)"
Yes
No
Yes
No
Yes
No
If using CiR: Take the number of CiR objects into account when defining the process image (address range).
Yes
No
V 1.0
26.03.2009
28/56
4.4
Table 4-7
Configuring field devices
Action The field devices used meet the relevant international standards.
Note/Reference [1], section titled "Basic information about device integration"
Done Yes Yes Yes No No No No No No No
Explanation/Reason
All the field devices used can be integrated via STEP 7, GSD, and EDD. Install device files (GSD and EDD) for all devices. Activate the PDM check box for DP/PA links. Observe the layout criteria for DP/PA. Observe the layout criteria for the Y link. [1], section titled "Configuring and assigning parameters for field devices" [1], section titled "Information on configuring field devices on the H system"
Yes Yes Yes
Observe the layout criteria for the DP/FF link.
[17], general Yes
V 1.0
26.03.2009
29/56
Configuration of the network connections
5
Table 5-1
Configuration of the network connections

Action Note/Reference [1], section titled "Merging networks in the multiproject" 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 connections" Always start with the engineering station when downloading stations. [1], section titled "Downloading connections" Done Yes Yes Yes No No No Explanation/Reason
"Merge subnets" for Industrial Ethernet. Configure AS-OS connections. Configure AS-ES connections. Configure AS-AS connections.
Yes
No
Download the connections (download complete stations from NetPro).
Yes
No
V 1.0
26.03.2009
30/56
Configuration
6
6.1
Configuration
AS configuration
Master data library

Table 6-1
Action
Note/Reference [2], section titled "Using the master data library" [2], section titled "How to copy objects from other libraries to the master data library"
Done Yes Yes Yes No No No No No No
Explanation/Reason
Only blocks from the master data library may be used for configuration. Supply the master data library with data.
Save user-defined blocks in the master data library. Adapt the message configuration of the blocks to the project in question. Adapt the attributes of the blocks to the project in question. Plan for a feedback strategy for the parameters. Enter and update the shared declarations for the entire multiproject in the master data library. [1], section titled "Changing the message class, priority, and message text" [1], section titled "Changing attributes"
Yes Yes
[1], sections titled "Downloading the user program with PCS 7 V7.0" and "Downloading the user program with PCS 7 V6.1" Declarations deleted from the master data library are not removed from the subprojects during updating.
Yes
Yes
No
V 1.0
26.03.2009
31/56
Configuration
Action Update the block versions in the S7 programs throughout the entire multiproject.
Note/Reference [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.
Done
Explanation/Reason
Yes
No
CFC
Table 6-2
Action Define ranges for separate blocks (FC and DB). Do not change/increase the number of blocks installed in each runtime group. Optimize the run sequence (property for each runtime group, depending on whether the project is old or new). Enter the cycle load of the AS. Generate messages from I/O devices. Create process tag types (templates) in the master data library. V 1.0
Note/Reference [1], section titled "Requirements for configuration in CFC" This can cause the SCL compiler to abort the compilation process. [2], section titled "How to optimize the run sequence" [1], section titled "Run sequence" [1], section titled "Cycle load and memory utilization of the AS" [1], section titled "Enabling messages from I/O devices" [1], section titled "Process tag types (templates)" 26.03.2009
Done Yes Yes No No
Explanation/Reason
Yes
No
Yes Yes Yes
No No No 32/56
Configuration
SFC type
Table 6-3
Action Make general changes relating to an SFC type centrally at the type.
Note/Reference [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.
Done
Explanation/Reason
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 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 Only download the program to the AS from an open CFC or SFC. V 1.0
Note/Reference
Done
Explanation/Reason
Yes
No
[1], section titled "Downloading changes online" 26.03.2009
Yes
No 33/56
Configuration
Action Prior to a full download: Ensure that the parameters are read back.
Note/Reference [1], section titled "Compiling and downloading" This must be done before changes are made in CFC.
Done
Explanation/Reason
Yes
No
Compiling the OS
Table 6-5
Action We recommend using the "Area-oriented" compilation mode.
Note/Reference [1], section titled "Compiling and downloading"
Done Yes No
Explanation/Reason
Downloading the OS
Table 6-6
Action Always download OS projects via the SIMATIC Manager (PLC Download). Complete the download procedure successfully. Download to redundant OS servers promptly. Server data from the redundant OS servers must have the same time stamp.
Note/Reference [1], section titled "Downloading the OS projects"
Done Yes Yes Yes No No No No
Explanation/Reason
This must be checked on the target computer (in the WinCC Explorer under "Server data").
Yes
V 1.0
26.03.2009
34/56
Configuration
6.3
General
Table 6-7
OS configuration
Action Derive a project-specific "@PCS7Typicals.pdl" from the default. Supplement with customized symbols Adapt the available layouts Set the computer's properties. Startup characteristics Language Graphics runtime Make settings in the OS project editor.
Note/Reference Software design specification
Done
Explanation/Reason
Yes
No
Yes [1], section titled "Working with the OS project editor"
No
Yes
No
V 1.0
26.03.2009
35/56
Configuration
User administration
Table 6-8
Action Optional: Use SIMATIC Logon.

Note/Reference [4], general Only the user groups need to be configured. The users are managed in the user administration system of Windows or the domain. 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. Activate "Automatic logoff" in the SIMATIC Logon configuration. Advantage: A notice appears before the user is actually logged off.
Done
Explanation/Reason
Yes
No
Define user groups with permissions.
Yes
No
If using SIMATIC Logon: Do not activate the automatic logoff function in the User Administrator.
Yes
No
V 1.0
26.03.2009
36/56
Configuration
Redundancy
Table 6-9
Action Establish a physical connection between the redundant partners. Serial interface, or Additional network I/O Activate the redundancy options in accordance with your requirements.
Note/Reference "Redundancy" editor [1], section titled "Redundancy settings in the server project"
Done
Explanation/Reason
Yes
No
Yes
No
Time synchronization
Table 6-10
Action Make the settings for synchronizing the process bus. Make the settings for synchronizing the OS clients.
Note/Reference [1], section titled "Time synchronization"
Done Yes Yes No No
Explanation/Reason
Graphics Designer (GraCS)

Table 6-11
Action Set a uniform picture size. Check the language settings in the picV 1.0
Note/Reference Adapted to the monitors of the OS clients
Done Yes No
Explanation/Reason
You can check the language settings by 26.03.2009 37/56
Configuration
Action tures. Check: Under Options -> Settings -> "Paste/copy object(s)" options "To previous layer" must be selected.
Note/Reference opening a picture and selecting the "View" menu command. 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 original picture.
Done Yes No
Explanation/Reason
Yes
No
OS client project
Table 6-12
Action Assign the server data for every OS client project.
Note/Reference [1], section titled "Defining the server assignment" OS server data only has to be downloaded to the OS clients once. The OS server data is updated automatically each time an OS client is started in process mode or when changes are downloaded to the OS servers. [1], section titled "Selecting a preferred server" [1], section titled "Selecting and configuring a standard server"
Done
Explanation/Reason
Yes
No
For redundant OS servers: Select the preferred server. For redundant OS servers: The standard server is selected for each OS client. Configure the User Administrator for each OS client project. V 1.0
Yes
No
Yes
No
Yes 26.03.2009
No 38/56
Configuration
Archiving (take the performance of the OS servers into account)

Table 6-13
Action The mean value for saving all archive tags must not exceed 1,000/s for each OS server. (TagLogging Fast + TagLogging Slow <= 1,000 values/s) Evaluate the frequency of individual messages and the average volume of message traffic as a "continuous load" during the FAT/commissioning phase. Max. 10 messages per server.
Note/Reference 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"
Done
Explanation/Reason
Yes
No
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 Check that the scripts are correct using APDiag during the commissioning/FAT phase.
Note/Reference WinCC Information System search string: APDiag
Done
Explanation/Reason
Yes
No
V 1.0
26.03.2009
39/56
Configuration
Web option
Table 6-15
Action Use the relevant manual to find and implement a concept for integrating the Web server into the existing plant (router, firewall settings, IPsec transfer).
Note/Reference [16], general
Done
Explanation/Reason
Yes [11], 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. 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). Logon for Web access created in the User Administrator with start screen "@Screen.pd_" and language selection. Make security settings in Internet Explorer according to the instructions contained in the relevant manual.
No
Yes
No
Yes
No
Yes
No
V 1.0
26.03.2009
40/56
Configuration
Action Install the WebNavigator client for Internet Explorer with administrator rights (download from Web server or install from the PCS 7 Toolset DVD). Install up-to-date plug-ins in Internet Explorer.
Note/Reference
Done
Explanation/Reason
Yes
No
Central archive server (CAS)

Table 6-16
Requirement 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
Note/Reference
Adhered to
Explanation/Reason
Yes
No
V 1.0
26.03.2009
41/56
Changing projects in process mode
7
7.1
Table 7-1

Downloading changes online
Requirement
Note/Reference [1], section titled "Downloading changes online" [1], section titled "Downloading changes online" A temporary data inconsistency arises between AS and OS data while the "Download changes" function is being executed.
Adhered to Yes No
Explanation/Reason
Only download the AS from an open CFC or SFC. The AS and the OS must be downloaded promptly.
Yes
No
V 1.0
26.03.2009
42/56
7.2
Complete online download to a redundant OS server pair

The following order must be observed:
Table 7-2
Action
Note/Reference [1], section titled "Complete online download to a redundant OS server pair"
Done Yes No
Explanation/Reason
Compile the project of the master OS (complete or changes only). 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. Download the OS project to the OS server ("Entire OS" is the only option which can be selected). Wait for the message indicating that the download has been completed successfully. Start the OS server (> stdby mode).
Yes
No
Yes
No
Yes Yes
No No
Wait for the redundancy update to be performed (> process control message). Proceed in exactly the same way for the other server.
Yes
No
Yes
No
V 1.0
26.03.2009
43/56
Asset management
8
8.1
Table 8-1
Asset management
Requirement
Requirement
Note/Reference [1], section titled "Integrated asset management"
Adhered to Yes Yes Yes Yes Yes Yes No No No No No No
Explanation/Reason
All the projects of the multiproject use the same message concept. Component names are restricted in the hardware configuration to a maximum of 14 characters. Driver blocks from PCS 7 library V6.1 SP1 or earlier are used. Module drivers have been generated for all AS without any errors. OS compilation mode is set to "Areaoriented" for all subprojects of the multiproject. All field devices are assigned with the PDM. A maintenance project is entered in the PDM settings. All projects in the multiproject have the same PH settings. The six PH levels required for asset manV 1.0
Yes
No
Yes
No
26.03.2009
44/56
Asset management
Requirement agement are set. The names of the S7 programs are unique throughout the entire multiproject and do not contain any blanks. The picture hierarchy is derived from the PH.
Note/Reference
Adhered to Yes Yes Yes Yes No No No No
Explanation/Reason
NDIS driver is installed on the MS server, if CP 1613 is used.
8.2
Table 8-2
Configuration
Action MS stations (MS client, MS server) are inserted in the multiproject. Configure the monitoring of network objects and the PC via SNMP in the SIMATIC NET OPC server. Update the diagnostic screens.
Note/Reference [1], section titled "Integrated asset management"
Done Yes Yes Yes No No No No No
Explanation/Reason
Export the SNMP tags for WinCC. Yes Compile the OS once the diagnostic screens have been updated. V 1.0 26.03.2009 Yes
45/56
Asset management
Action Download the PC configuration of the MS server (OPC server). Download the OS server and MS server.
Note/Reference
Explanation/Reason
Activate "detailed diagnostics" on the OS client computer (as of PCS 7 V7.0).
Yes
8.3
Table 8-3
Runtime
Requirement The MS client is an OS client on the master ES. The project which is valid for operating the plant must be stored on the MS client.
Note/Reference
Adhered to Yes Yes No No
Explanation/Reason
V 1.0
26.03.2009
46/56
Installation guidelines
9
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 EMC/ESD Handling of modules during installation and testing Suitability of Floor Storage areas/tables Cabinet (where spare parts are stored) ESD set available (grounding bracelet, ESD mat, shoe grounding strips, etc.) Staff training
Note/Reference Record this information, as noncompliance could cause a warranty to become void. See the ESD inserts for the relevant modules.
Adhered to
Explanation/Reason
Yes
No
V 1.0
26.03.2009
47/56
Requirement Cabinet configuration Voltage supply isolated from signal cables Shield plates for transformers, reactors, busbars, line filters Shield support at the entrance to the cabinet Cable entry Cable grip Sealing/dust protection/temperature Marking of all elements PE for doors, side walls, and support plates Contact washers Cross-section of PE connection Overvoltage protection Power consumption Diagnostics (undervoltage, fuse blown, faulty devices) Standby/CiR preparation PC and server Adhere to the installation guidelines for PCs provided in the relevant operating instructions. Stability/mounting Connecting cable Bending radii Mounting/fuses V 1.0
Note/Reference
Adhered to
Explanation/Reason
Yes
No
[10], sections titled: "Application planning" "Mounting" "Connecting"
Yes
No
26.03.2009
48/56
Requirement 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
Note/Reference
Adhered to
Explanation/Reason
AS/rack Adhere to the installation guidelines for automation systems provided in the relevant software installation manual. Installation Ambient and environmental conditions Backup batteries OK? PROFIBUS connection for diagnostics I/O Adhere to the installation guidelines for the ET 200M/iSP/S. Installation V 1.0
[15], sections titled: "Installing the S7-400" "Wiring the S7-400" "Appendix A, Assembling and installing systems" [18], section titled "General technical specifications" [11], sections titled: "Application planning" "Installing" [17], section titled "Installing" 26.03.2009
Yes
No
Yes
No
49/56
Requirement Ambient and environmental conditions CiR preparations and standby PROFIBUS connection for diagnostics
Note/Reference [18], section titled "General technical specifications"
Adhered to
Explanation/Reason
MTA Grounding (shields, PE) Red. voltage supply/UPS Network (LAN) Adhere to the installation guidelines for Ethernet 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 galvanic isolation) Diagnostics Documentation, marking Access Cable test logged Redundant voltage supply/UPS PROFIBUS (fieldbus) Adhere to the installation guidelines for PROFIBUS networks. Installation Equipotential bonding and shielding V 1.0 [13], sections titled: "Guidelines for installing networked automation systems in buildings" "Installing network components in cubicles"
Yes
No
<Cross-section, length, terminal for grounding>
Yes
No
[14], sections titled: "Appendix C, Installing LAN cables" "Appendix D" "Appendix E, Installing network 26.03.2009
Yes
No
50/56
Requirement CiR preparations
Note/Reference components in cubicles" PROFIBUS Installation Guideline and PROFIBUS Commissioning Guideline (from PNO: www.profibus.de)
Adhered to
Explanation/Reason
Other data connections Serial connections, e.g. measuring or diagnostic devices, third-party systems, RK512 Modbus Printers Package units Voltage supply Shield plates Line filters Compensation equipment Lightning and overvoltage protection Neutral/ground Ground connection/PE UPS concept Server Backup and automatic shutdown Controlled plant shutdown AS, I/O, MTA, sensors, actuators Protection Documentation Battery V 1.0 26.03.2009 Is a measuring log available?
Yes
No
<Rated voltage, voltage peaks, harmonic content, rated power, reserve>
Yes
No
Yes
No
51/56
Requirement
Note/Reference
Adhered to
Explanation/Reason
Power, bypass time, reserve UPS bypass Diagnostics Emergency unit Emergency supply for pressurized air used for operation [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) <Specify the class for Ex signals>
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 relevant approval PROFIBUS RS485iS installed For installation in zone 2, manufacturer's declaration available for the enclosure
Yes
No
V 1.0
26.03.2009
52/56
9.2
Table 9-2
Grounding concept
Requirement Grounding concept with ground strip covering the entire factory/building
Adhered to Yes No No No No No No No No No No
Explanation/Reason
Check of other neutral points with insecure/no connections Yes Steel structure included Yes Pipeline network included Yes Cable routes included Yes Other metal parts (railings, concrete reinforcements, frames, door frames, false-floor structures, etc.) included Flow sensors correctly grounded/insulated Yes Transmitter enclosure grounded Yes Danger of circulating currents due to large magnetic fields, inductances, or current lines assessed Grounding points in different parts of the plant or different buildings sufficiently connected to one another Yes Yes Yes
V 1.0
26.03.2009
53/56
Requirement N and PE connected (PEN)
Adhered to Yes No No
Explanation/Reason
Voltage supply and UPS connected to the same ground electrode Yes
Installation with non-grounded reference potential If your installation has a grounded reference potential, please go to Table 9-4.
Table 9-3
Requirement Adhere to the wiring guidelines contained in the relevant manuals.
Adhered to Yes No No No No No No
Explanation/Reason
Remove the jumper from reference potential M and the rack on the programmable controllers. Remove the jumper from reference potential M and the functional ground at the ET 200M/iSP power supply. Galvanic isolation in place for the PCs
Yes Yes Yes
Cabinet/mounting structure connected to the central grounding point (e.g. main ground line) via a PE cable 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 V 1.0 26.03.2009
Yes Yes
54/56
Requirement PROFIBUS shield insulated in the connector to the nodes (modules)
Adhered to Yes No
Explanation/Reason
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 Adhere to the wiring guidelines contained in the relevant manuals.
Adhered to Yes No No No No
Explanation/Reason
Insert a jumper for reference potential M and the rack on the programmable controllers. Yes Insert a jumper for reference potential M and the functional ground at the ET 200M/iSP power supply. Cabinet mounting structure connected to the central grounding point (e.g. main ground line) via a PE cable 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 V 1.0 26.03.2009 Yes Yes
Yes
No
55/56
9.3
Table 9-5
Lightning and overvoltage protection
Requirement Measures for lightning and overvoltage protection have been put in place as per the relevant installation manuals.
Adhered to Yes Yes No
Explanation/Reason
Coarse protection used No Fine protection used Yes All components are located within the building/inside the conductor electrode around the building. Lightning conductor grounded (reactions on PE restricted) Yes Available aerials (WLAN, GSM, etc.) and cameras are integrated in the concept/insulated. Yes No No Yes No
<Specify the type of protection used> <Specify the type of protection used> <If "no", list the components affected> No <Where grounded/connected to conductor electrode around the building>
V 1.0
26.03.2009
56/56

Checklist Configuration

Uploaded by

Copyright:

Available Formats

Checklist Configuration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Checklist Configuration

Uploaded by

Copyright:

Available Formats

Checklist

PCS 7 Compendium Part A - Configuration Guidelines

Details on preparing the checklist

Details on the project

Checklist "PCS 7 Configuration"

Copyright Siemens AG 2009 All rights reserved

Checklist "PCS 7 Configuration"

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

Copyright Siemens AG 2009 All rights reserved

Checklist "PCS 7 Configuration"

Copyright Siemens AG 2009 All rights reserved

Checklist "PCS 7 Configuration"

References to other sources

Ref. no. [1] [2] [3] [4] [5] [6] [7]

[8] [9] [10] [11] [12] [13] [14] [15] [16]

[17] [18] [19] [20] [21]

Checklist "PCS 7 Configuration"

Abbreviation APDiag AS OCV CFC CiR EMC ES

Checklist "PCS 7 Configuration"

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

Checklist "PCS 7 Configuration"

Checklist "PCS 7 Configuration"

Copyright Siemens AG 2009 All rights reserved

Check the PCS 7 installation requirements.

Checklist "PCS 7 Configuration"

Checklist "PCS 7 Configuration"

Installing PCS 7 (including options)

ES, OS server, OS clients

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

Done Yes Yes No No No

<Enter the versions, if necessary>

Checklist "PCS 7 Configuration"

Action The PCS 7 software must be kept up to date.

Copyright Siemens AG 2009 All rights reserved

Transfer licenses via the Automation License Manager (ALM).

Checklist "PCS 7 Configuration"

Copyright Siemens AG 2009 All rights reserved

Note/Reference [1], section titled "Configuring the terminal bus"

Done Yes Yes Yes Yes No No No No

Checklist "PCS 7 Configuration"

Note/Reference [1], section titled "Configuring the plant bus"

Done Yes Yes No No

Copyright Siemens AG 2009 All rights reserved

Action Create an image of the installation.

Multiproject Design and management

Checklist "PCS 7 Configuration"

Multiproject Design and management

Note/Reference [2], section titled "Planning the plant engineering"

Multiproject Design and management

Checklist "PCS 7 Configuration"

Copyright Siemens AG 2009 All rights reserved

Define the naming conventions.

Yes Yes Yes

Multiproject Design and management

Checklist "PCS 7 Configuration"

Copyright Siemens AG 2009 All rights reserved

The OS project must not be activated on the ES.

Optional: Define the concept for multiproject/multiuser engineering.

Multiproject Design and management

Checklist "PCS 7 Configuration"