Configuration Instruction for Process Automation · MP Engineering with SB Entry ID: 23785345...

Configuration Instruction for Process Automation

PCS 7 V6.1+SP1 Configuration Instruction

Multiproject Engineering with SIMATIC BATCH

Warranty, Liability and Support

MP Engineering with SB Entry ID: 23785345

Warranty, Liability and Support

We accept no liability for information contained in this document.

Any claims against us - based on whatever legal reason - resulting from the use of the examples, information, programs, engineering and performance data etc., described in this document shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (“wesentliche Vertragspflichten”). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health. The above provisions do not imply a change in the burden of proof to your detriment.

The Application Examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. They do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are used correctly. These Application Examples do not relieve you of the responsibility in safely and professionally using, installing, operating and servicing equipment. By using this application example you accept that Siemens is not liable for any damages except for those specified in the above liability clause. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in this application example and other Siemens publications – e.g. Catalogs – the contents of the other documents have priority.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Copyright© 2006 Siemens A&D. It is not permissible to transfer or copy these Application Examples or excerpts of them without first having prior authorization from Siemens A&D in writing.

For questions about this document please use the following e-mail address:

mailto:[email protected]

1.0 15.09.06 2/49

mailto:[email protected]

Foreword


Foreword

Purpose of this document This document is based on the instructions “Multiproject Engineering“ (http://support.automation.siemens.com/WW/view/en/22258951) which focuses on the following:

• Multiproject principle and configuration options

• Activities during shared, decentralized project engineering

Building on this, the particularities when dealing with projects containing batch functions are described. This is the actual intention. Work steps already explained in the base document in detail are only roughly outlined here.

From a GMP (Good Manufacturing Practice) point of view, the document is meant to help communicating the correct procedure for multiproject engineering with SIMATIC BATCH to the respective project engineers.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Main contents The document focuses on the following points:

• Principle procedure and basic requirements

• Activities when dividing and merging the individual subprojects

Conventions The workflow of the project requires the implemented functions including batch functionality to be engineered and tested at different locations. It is necessary to include subprojects extracted from the multiproject, into another multiproject (MP of the decentralized Engineering environment).

For simplicity reasons, the following abbreviations are used in this document:

• CMMP (Central Master Multiproject)

• DMP (Decentralized Multiproject)

Further abbreviations are attached in the attached Abbreviation Directory.

Reference to Automation and Drives Service & Support This entry originates from the internet application portal of the A&D Service and Support. Clicking the link below directly displays the download page of this document.

http://support.automation.siemens.com/WW/view/en/4000024

1.0 15.09.06 3/49



Foreword


Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 4/49

Table of Contents


Table of Contents

Table of Contents ......................................................................................................... 5

1 Principle Procedure........................................................................................ 7 1.1 Overview........................................................................................................... 7 1.2 Chronological sequence ................................................................................... 8 1.3 Preconditions .................................................................................................. 12

2 Step-by-Step Instructions ............................................................................ 15 2.1 Transferring an AS project to a decentralized ES........................................... 15 2.1.1 Removing project components from the CMMP ............................................. 16 2.1.2 Merging the transferred project components into the DMP ............................ 17 2.2 Restoring the edited AS project into the CMMP ............................................. 30 2.2.1 Final project works on the decentralized ES................................................... 30 2.2.2 Reintegrating the project into the CMMP of the central ES ............................ 34

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

3 Additional Considerations ........................................................................... 46 3.1 Handling problems due to deviating procedures ............................................ 46 3.2 Further notes and recommendations.............................................................. 47

Abbreviation Directory ............................................................................................... 49

1.0 15.09.06 5/49

Table of Contents


Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 6/49

Principle Procedure


1 Principle Procedure

1.1 Overview

The following figure shows the different components during distributed project engineering.

Figure 1-1

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

For distributed processing, the AS projects are extracted from the CMMP and included into separate multiprojects (DMP) in further engineering environments. After editing, they are then reapplied into the central project engineering.

1.0 15.09.06 7/49

Principle Procedure

MP Engineering with SB Entry ID: 23785345 1.2 Chronological sequence

Table 1-1 gives the principle procedure in a graphic display. The colors of the shaded texts have the following meaning:

Project components marked red … must not be removed from the central multiproject as they contain central as well as distributed project engineering.

Project components marked yellow … can be temporarily included into another multiproject and be further engineered there. The AS, OS and batch functions can be tested on additional hardware.

Project components marked gray … are provided to each project engineer. Changes must only be made centrally hence valid for all.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Table 1-1

Step Activity Screen shot

1 Central project management On the central ES the multiproject is set up according to the given plant structure.

1.0 15.09.06 8/49

Principle Procedure


Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


2 Preparing the decentralized engineering environment One decentralized engineering environment each for every additional project engineer is set up for configuration and testing. The decentralized configuration needs not correspond with the final station setup. (An OS server with BATCH server functionality on the ES or as in the picture in addition to the ES is sufficient)

1.0 15.09.06 9/49

Principle Procedure


Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


3 Distributing the master data library Each project engineer must only work with the blocks of the master data library. Changes are only made to the master data library in the CMMP and are then again provided to all project engineers.

4 Distributing the subprojects The project engineers are provided with the respective AS projects from the CMMP.

5 Distributed project engineering

The project engineers generate the user program and test it with the BATCH/ OS server of their decentralized engineering environment.

1.0 15.09.06 10/49

Principle Procedure


Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


6 Reapplying the projects From a certain project state on, the AS projects with the user programs are remerged into the CMMP for tests, central works, or for completing the project. The entire project can thus be compiled and be loaded to a testing environment or into the productive station. In the mean time, the decentralized AS projects can be further worked at.

1.0 15.09.06 11/49

Principle Procedure


1.3 Preconditions

For the distributed engineering with SIMATIC BATCH, this chapter outlines basic preconditions and relevant project phases.

General rules for project engineering • All of the involved PC stations contain the same PCS 7 versions (also

Hotfix states and IT integration software).

• All actions such as Save as.., Delete, Archive, Retrieve, must be initiated via the SIMATIC Manager.

• Central settings can only be made in the CMMP.

• AS projects must only be processed decentrally. This means, that each AS must be managed in an individual subproject.

• The projects may not be renamed.

• Within a subproject (AS project) changes must not be made at the same time in the CMMP and in the DMP.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

• The process data library is located in the CMMP and is the master for all involved DMP. Changes must only be made in the master data library of the CMMP (also applies for SFC types and global declarations).

• For already created and instantiated SFC types, as well as the projects themselves, a change of names is not permitted.

• Only SFC types are used. Using the batch interface blocks EPH, IEPH, EOP, IEOP as well as the blocks of SIMATIC BATCH V4.2 (AF blocks) is not possible.

• The technological functions of a unit must not be distributed over several subprojects.

• The hierarchy folder of the plant and the batch process cell must have the same name in all batch relevant subprojects.

• Configurations in the SIMATIC BATCH dialog which are made in the DMP (equipment properties, units, references to WinCC archive, etc.), must be made again in the CMMP.

1.0 15.09.06 12/49

Principle Procedure


1.0 15.09.06 13/49

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Project phases For each project it must be determined individually up to which project phase the decentralized engineering can take place. The following requirements must therefore be met:

• Entire download of the plant is possible

• Resetting the batch database as well as the OS message archive possible

The arrow head in Figure 1-2 may vary towards left or right accordingly. From this moment on AS projects may not be merged any more into other multiprojects. A decentralized engineering is then only possible as a single project. To this a project will have been removed from the multi-project with the function “Remove for Editing…” (without the possibility to modify the batch types).

Note You find further explanations to this in the document "Multiproject Engineering" in the chapter 2.3 “Distributing the projects “ under “Removing a project from the multiproject assembly”.

(http://support.automation.siemens.com/WW/view/en/22258951)


Principle Procedure


1.0 15.09.06 14/49

Copyright © Siemens AG 2006 All rights reserved 2006-09-15_MP_BATCH_e.doc

The following figure illustrates the phases of a batch project engineering in which the options of multiproject engineering can be used.

Figure 1-2

Step-by-Step Instructions


2 Step-by-Step Instructions

Here the activities for distributing and remerging of subprojects necessary within the framework of multiproject engineering with SIMATIC BATCH are explained.

! Attention

Dangers due to deviating procedures:

o The batch data in the CMMP and all subprojects may become implausible.

o The batch data in the batch database may become implausible.

2.1 Transferring an AS project to a decentralized ES

The AS project is archived together with the master data library and copied to the decentralized ES for processing.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Note The following step by step instructions refer mainly to transferring a subproject. The same procedure applies to the master data library.

The following work steps are regarded as a prerequisite:

• All AS/OS projects are created within the CMMP and the contained SIMATIC or PC stations are configured.

• Already known measuring locations have been filed in the master data library.

• A TH is created and updated across all subprojects.

• Cross-project networks and connections have been created.

Note Detailed instructions are available in the “Multiproject Engineering“ document in chapter 2.2 “Preparatory project works“.

(http://support.automation.siemens.com/WW/view/en/22258951)

1.0 15.09.06 15/49




2.1.1 Removing project components from the CMMP

The AS project is archived together with the master data library and copied to the decentralized ES for processing.

Table 2-1

Step Activity Screenshot

1 In order to transfer an individual project to an external medium, it must be archived. In the SIMATIC Manager you select “File“ > “Archive...“. Note: The project to be archived must not be opened in the SIMATIC Manager.

2 Perform the procedure for the AS project (register ”User projects“) as well as for the master data library (register ”Libraries“).

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 16/49



2.1.2 Merging the transferred project components into the DMP

The transferred AS project is merged into a separate multiproject together with the master data library and processed there.

Deleting a subproject of identical name (if existing) Table 2-2


1 If an AS subproject of identical name already exists in the DMP target path, it must be deleted. For a closed project you select ”File“ > ”Delete...“ in the SIMATIC Manager.

2 Choose the project you want to delete. If it is not listed in the right-hand dialog box, it must be selected via the file browser with “Browse...“. Acknowledge the following warning messages.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 17/49



Dearchive the individual project of the library in the DMP target path Table 2-3


1 The archived project is copied, for example, from the central ES to a remote ES using a mobile data carrier. In the SIMATIC Manager you select “File“ > ”Retrieve...“.

2 Select the zip file, as well as the DMP target path to which the project is to be retrieved and start the retrieve process.

3 Acknowledge the query asking

whether the previous multiproject is to be eliminated with “Yes“.

4 Acknowledge the following query

with “Yes”. The retrieved project is opened.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 18/49


MP Engineering with SB Entry ID: 23785345 Adapt the retrieved subprojects (batch data and addresses) Table 2-4


1 Remove the batch process cell from the drive.

2 Remove S88 type definition of the TH of the project. Open the Properties dialog of the TH and set the object type in the “S88 Type Definition“ to ”<Standard>“.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 19/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


3 Check the parameterized MAC address of the AS station. Open the “General“ tab in the object properties of the CP 443-1. If necessary, adjust the address to your hardware on site. Ensure the uniqueness of the addresses at the bus. Close the project.

1.0 15.09.06 20/49


MP Engineering with SB Entry ID: 23785345 Including the subproject / library into the DMP Table 2-5


1 To include an individual project into the DMP, open the MP in the SIMATIC Manager. Select the multiproject and select “Multiproject“ > ”Insert into Multiproject...“ from the context menu.

2 Then select the desired source and confirm with “OK“.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 21/49


MP Engineering with SB Entry ID: 23785345 Generate S7 connections Table 2-6


1 Creating cross-project S7 connections requires the subnets of the individual projects to be merged. To do this, call the following menu options for the selected multiproject: “File“ > “Multiproject“ > “Adjust projects in multiproject“ Select the Ethernet and confirm with “Execute“.

2 In the “Subnets in the multiproject“ list you successively select the subnets of all subprojects and move them to the ”Merged“ list via the “ “ button.

3 All connections located in the “Merged“ list, are merged into one network as soon as the settings are confirmed. Then close the network dialogs.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 22/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


4 In NetPro the required S7 connection between AS and OS for the local configuration (DMP) can be created now. Note: Interproject connections already created in the CMMP cause warnings during compiling and downloading in NetPro. These refer to not-available connection partners, however, they have no negative effect on the configuration of new connections.

Adding the batch process cell and the S88 type definition Table 2-7


1 In the technology view you select the AS project and select it in the ”Insert New Object“ > ”Batch process cell“ context menu. Note: Ensure that the name of the batch process cell is identical in all individual projects.

2 Then assign the S88 type definition to the highest hierarchy folder of the TH. To do this, open the Properties dialog of the TH.

1.0 15.09.06 23/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Step Activity Screenshot 3 In ”S88 Type Definition“ set

the object type to ”<Plant>“. After acknowledging the setting with “OK“ the hierarchy folders become green and are defined as “Plant” in ISA S88.

Compiling / loading the AS projects and the OS project Prior to generating the batch data, the S7 program and the OS must be compiled and loaded into the respective stations.

1.0 15.09.06 24/49



Generating and transferring the batch data Table 2-8


1 Select the multiproject in the SIMATIC Manager and select “SIMATIC BATCH“ from the context menu. Here you select the highest hierarchy folder, as well as the multiproject and confirm the “Settings“ button.

2 Update the status of the entire plant

by acknowledging the ”Update“ button in the “Distribution“, “OS objects“ and “Process cells“ tabs. Then quit “Settings” dialog box with “OK“.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 25/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


3 For generating and propagating the batch data select the hierarchy folder “Batch types“. Press the “Generate“ button and select all individual projects in the window that opens. Press “Start“ and then “Close“. Then press the “Propagate…“ button and proceed accordingly.

1.0 15.09.06 26/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


4 To merge batch data, select the hierarchy "Batch instances" and acknowledge with the "Merge" button. In the dialog which opens you select the batch relevant projects, whose plant data should be included and press “Start“. Then the quit dialog box with “Close“.

5 Any batch relevant data (messages and user data types) are now accepted to the respective OS. Select the batch process cell and acknowledge the ”Transfer to OS…“ button. In the window which opens press “Start“ after the status has changed to “Transferred“ press ”Closed“.

1.0 15.09.06 27/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


6 Finally the plant data is loaded to the BATCH server, the DB server (data storage) and the BATCH clients. Open the respective dialog for selected batch process cell via the “Load…“ button. If prompted whether you want the system data to be loaded, you answer with “Yes”. Start the load process and close the BATCH dialog after the status of all components has been changed to ”loaded“.

1.0 15.09.06 28/49



Update the batch data in the Batch Control Center After the download of new batch relevant process cell data to the BATCH server, the changes must also be introduced in SIMATIC BATCH.

Table 2-9


1 Open the Batch Control Center on the BATCH Runtime computer and for selected batch process cell you select the menu item ”Edit“ > ”Update process cell“.

2 Select the line with the changed process cell project and confirm with “OK“.

3 If necessary (at change of names) you adjust the allocation between the objects and start the update with “OK“.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Subsequently the Runtime and test recipe can be started. If everything is OK the actual project engineering and testing on the decentralized engineering environment can start.

1.0 15.09.06 29/49



2.2 Restoring the edited AS project into the CMMP

After the decentralized engineering of the individual projects, they are remerged for completing the overall engineering on the central ES.

2.2.1 Final project works on the decentralized ES

After editing, the AS project is prepared for remerging into the CMMP of the central ES.

Note If after the transferal the subproject is to be further edited in the decentralized engineering environment, it is better not to make the subsequent changes in the DMP. The subproject should in this case be archived under a different project path as an individual project and be adjusted there for the CMMP according to the following sections.

Removing the S88 type definition and the batch process cell

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Table 2-10


1 Remove S88 type definition of the TH of the AS project. Open the Properties dialog of the TH and set the object type in the “S88 Type Definition“ to ”<Standard>“.

1.0 15.09.06 30/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


2 Delete the batch process cell from the AS project.

Reset the communication settings Table 2-11


1 In NetPro you delete the S7 connection between AS and OS specially created for the DMP. Save the changes and close NetPro.

1.0 15.09.06 31/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


2 Check the parameterized MAC address of the AS station. Open the “General“ tab in the object properties of the CP 443-1. If the address was changed in the DMP then reset the original address of the CP of the central engineering environment here. Close the HW Config window.

1.0 15.09.06 32/49



Archiving the AS project The AS project can subsequently be archived and copied back to the central ES.

Table 2-12


1 To transfer the project to an external medium you need to activate it. Select “File“ > “Archive...“ from the SIMATIC Manager. Note: The project to be archived must not be opened in the SIMATIC Manager.

2 Select the AS project in the “User projects“ tab and start the archiving project.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 33/49



2.2.2 Reintegrating the project into the CMMP of the central ES

The transferred AS project is merged back into the multiproject for further central engineering steps.

Delete the old project status (if still existing) If the original AS project, according to this instruction, still exists in the CMMP of the central ES it must be deleted.

Table 2-13


1 At closed project select ”File“ > ”Delete...“ in the SIMATIC Manager.

2 Then select the project you want to delete. If it is not listed in the right-hand dialog box, it must be selected via the file browser with “Browse...“. Acknowledge the resulting warning message with ”Yes“ / ”OK“.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 34/49



Retrieving the subproject and applying into the CMMP The archived project was previously copied from the remote ES to the central ES using a mobile data carrier, for example.

Table 2-14


1 Select “File“ > “Retrieve…“ in the SIMATIC Manager.

2 Select the zip file, as well as the CMMP target path to which the project is to be retrieved and start the retrieve process.

3 Acknowledge the query asking

whether the previous multiproject is to be removed with “Yes“. Note: This query will not appear if the AS project was not part of the multiproject at the time of retrieving.

4 If you are sure that the instructions

were followed from chapter 2.2.1 “Final project works on the decentralized ES”, you can adjoining query, whether the retrieved project shall be opened, replay with “No”. Otherwise you should open this single project, check the points and this close You should elsewhere this open single project, check the points and afterwards close the project again.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 35/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


5 Following this open the CMMP. Select the multiproject and select “Multiproject“ > ”Insert into Multiproject...“ from the context menu.

6 Then select the retrieved project and confirm with “OK“.

1.0 15.09.06 36/49



Interproject network update For interproject S7 connections the subnets of the subprojects must have been merged.

Table 2-15


1 To check this, call the following menu options for the selected multiproject: “File“ > “Multiproject“ > “Adjust projects in multiproject“ Select the Ethernet and confirm with “Execute“.

2 Ensure that the “Merged“ list contains all required subnets. In this case, quit the dialog with “Cancel“. Otherwise, successively select the subnets in the “Subnets in the multiproject“ list and move them to the “Merged“ list using the “ “ button. Then acknowledge the new configuration.

3 Check the S7 connections referring to the merged AS project. Compile and save NetPro.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 37/49


MP Engineering with SB Entry ID: 23785345 Adding the batch process cell and the S88 type definition Table 2-16


1 In the technology view you select the AS project and select it in the ”Insert New Object“ > ”Batch process cell“ context menu. Note: Ensure that the batch process cell name is identical in all individual projects.

2 Then assign the S88 type definition to the highest hierarchy folder of the TH. To do this, open the Properties dialog of the TH.

3 In ”S88 Type Definition“ set the object type to ”<Plant>“. After acknowledging the setting with “OK“ the hierarchy folders become green and are defined as “Plant” in ISA S88.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 38/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


Updating blocks across all individual projects The “Update block types” function is used for controlling whether the blocks in all individual projects of the CMMP are identical and have the same version. The components for updating older versions can be selected here.

Note SFC types and its FBs cannot be compared or updated with this function. On demand, they must be manually copied from the master data library into the individual S7 programs.

Table 2-17


1 Select one or several blocks in the blocks folder of the master data library. Select the menu item “Options“ > “Charts“ > “Update Block Types…“.

2 Select the S7 programs to be checked for differences and start the check with ”Continue“.

1.0 15.09.06 39/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


3 If differences were detected, you can select block types to be updated according to the program. Start the update with “Finish“. If no differences were detected, the right hand window remains empty. In this case, quit the dialog with “Cancel“.

4 Finally you receive a protocol with the completed actions.

Compiling / loading the AS projects and the OS project Prior to generating the batch data, the S7 program and the OS must be compiled and loaded into the respective stations.

Generating and transferring the batch data Table 2-18


1 Select the multiproject in the SIMATIC Manager and select “SIMATIC BATCH“ from the context menu. Here you select the highest hierarchy folder, as well as the multiproject and confirm the “Settings“ button.

1.0 15.09.06 40/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Step Activity Screenshot 2 Update the status of the entire plant

by acknowledging the ”Update“ button in the “Distribution“, “OS objects“ and “Process cells“ tabs. Then quit “Settings” dialog box with “OK“.

3 For generating and propagating the batch data select the hierarchy folder “Batch types“. Press the “Generate“ button and select all individual projects in the window that opens. Press “Start“ and then “Close“. Then press the “Propagate…“ button and proceed accordingly.

1.0 15.09.06 41/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


1.0 15.09.06 42/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


4 To merge batch data, select the hierarchy "Batch instances" and acknowledge with the "Merge" button. In the dialog which opens you select the batch relevant projects, whose plant data should be included and press “Start“. Then the quit dialog box with “Close“.

5 Any batch relevant data (messages and user data types) are now accepted to the respective OS. Select the batch process cell and acknowledge the ”Transfer to OS…“ button. In the window which opens press “Start“ after the status has changed to “Transferred“ press ”Closed“.

1.0 15.09.06 43/49



Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc


6 Finally the plant data is loaded to the BATCH server, the DB server (data storage) and the BATCH clients. Open the respective dialog for selected batch process cell via the “Load…“ button. If prompted whether you want the system data to be loaded, you answer with “Yes”. Start the load process and close the BATCH dialog after the status of all components has been changed to ”loaded“.

1.0 15.09.06 44/49



Update the batch data in the Batch Control Center After generating new batch relevant process cell data, the changes must also be introduced in SIMATIC BATCH.

Table 2-19


1 Open the Batch Control Center on the BATCH Runtime computer and for selected batch process cell you select the menu item ”Edit“ > ”Update process cell“.

2 Select the line with the changed process cell project and confirm with “OK“.

3 If necessary (at change of name) you adjust the allocation between the objects and start the update with “OK“.

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

Subsequently the Runtime and test recipe can be started. If everything is OK, the central engineering can be continued or completed (e.g. further central settings, test in central engineering or FAT).

1.0 15.09.06 45/49

Additional Considerations


1.0 15.09.06 46/49

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

3 Additional Considerations

3.1 Handling problems due to deviating procedures

If the described procedures were not followed, or if basic requirements were not met, there may be inconsistencies in the batch data base. The following table describes the steps for regenerating the batch data.

Table 3-1

Step Activities on the ES

1 Open the multiproject in the SIMATIC Manager. 2 Remove the S88 type definition and delete the batch process cell in all AS projects

of the multiproject. 3 Now perform the following activities:

• Updating the batch process cell • Generating and propagating the batch data • Merging the batch data • Transferring data to the OS The batch types now only contain the manually created types. The batch instances are also empty (If the recommendation 2 from Table 3-2 was followed).

4 Add the batch process cell and the S88 type definition to all AS projects of the multiproject.

5 Perform the following activities again: • Updating the batch process cell • Generating and propagating the batch data • Merging the batch data • Transferring data to the OS • Loading the batch The batch types now only contain the manually created types. The batch instances are also merged.

Activities on the BATCH server

6 Delete the batch data base and then load the batch data from the ES into the target station. Proceed according to the following FAQ: http://support.automation.siemens.com/WW/view/en/18794587

7 Start the start coordinator of SIMATIC BATCH. 8 Execute “New process cell“ in the BCC and update the process cell data. 9 Import the basic recipes, the libraries and formulas from a current export file or a

restore file.

Activities on the OS server

10 Reset the message archive.




MP Engineering with SB Beitrags-ID: 23785345

3.2 Further notes and recommendations

The following table provides you with tips and tricks on how to effectively perform selected activities around batch project engineering.

Table 3-2

Step Activities to be noted Recommendation

1 Central settings of the configured equipment properties are lost during removing and reapplying.

Only perform the batch process engineering without conditions via class view (select the unit via checkmark), if other conditions such as different container sizes are not used. Configure the equipment properties at a later point in time.

2 Types, units of measure, operator dialogs created in the batch types manually are lost during removing and reapplying.

In the OS project at the highest hierarchical folder of the PH set the S88 type definition “process cell” (only this) and add a batch process cell. When removing the AS project the objects created manually remain unchanged in the batch objects of the OS and therefore in the MP. A recreating is not necessary.

Permission management and materials in batch cannot be archived, exported or imported separately. If it becomes necessary to build upon a new database, permission management and materials cannot be imported anymore without a Restore. Importing the permission management and materials into an empty database causes an enormous work load.

When first creating the batch database it is recommended to save the project as backup after configuring the permissions, in order to avoid the enormous expenses for reconfiguring the permissions. Doing this in the beginning gives you a clean backup to perform a Restore.

4 When changing existing unit names… The new or renamed unit names should be allocated after updating the batch process cell in the configuration dialog of SIMATIC BATCH. If this is not done in the dialog, the recipes become implausible and the allocation of the units must be readjusted for each individual recipe.

1.0 15.09.06 47/49


MP Engineering with SB Beitrags-ID: 23785345

1.0 15.09.06 48/49


Step Activities to be noted Recommendation

5 When changing names of existing equipment modules (EM) …

The new or renamed equipment module should be allocated after updating the batch process cell in the configuration dialog of SIMATIC BATCH. If this is not done in the dialog, the recipes become implausible and the new allocations must be readjusted for each individual recipe.

6 When changing / adding setpoint values or control strategy at the SFC type…

Renamed setpoint values should be allocated after updating the batch process cell in the configuration dialog of SIMATIC BATCH. If this is not done in the dialog, the recipes become implausible and the new allocation must be readjusted for each individual recipe. If nominal values or run modes are being added or deleted, in each recipe the functions to which changes have been made must be selected and saved, as otherwise, no plausibility of the recipes is possible.

Abbreviation Directory


Abbreviation Directory

Abbreviation Meaning

AS Automation System BCC Batch Control Center DMP Decentralized Multiproject EOP Equipment Operation EPH Equipment Phase ES Engineering Station FAT Factory Acceptance Test IEOP Interface Equipment Operation IEPH Interface Equipment Phase CMMP Central Master Multiproject OS Operator Station SAT Side Acceptance Test EM Equpment module PH Plant hierarchy

Cop

yrig

ht ©

Sie

men

s A

G 2

006

All

right

s re

serv

ed

2006

-09-

15_M

P_B

ATC

H_e

.doc

1.0 15.09.06 49/49

Date post:	22-Aug-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

Configuration Instruction for Process Automation · MP Engineering with SB Entry ID: 23785345...

Documents