Distributed multiproject engineering 5.2.3.6 Overview and important remarks

Introduction

In this document, we explain distributed multiproject engineering with SIMATIC BATCH. This involves the exchange of projects between central and several distributed multiprojects. These projects can only contain SIMATIC AS stations.

These projects are exchanged by removing them from a central multiproject, inserting them into a distributed multiproject, editing them in the distributed multiproject, removing them from the distributed multiproject and finally inserting them back into the central multiproject.

Since BATCH multiproject configuration was only designed for editing within the context of a single multiproject, a few important rules and restrictions must be taken into consideration for distributed multiproject engineering with SIMATIC BATCH. These rules are described in this section.

Central multiproject engineering: scope

In contrast to distributed multiproject engineering, central multiproject engineering is used for centralized tasks. Central multiproject engineering is, therefore, not a topic in this documentation.

Note:

The procedure for multiproject engineering is described in the document "PCS7 V6.1+SP1 Configuration Guide for Multiproject Engineering" with the article ID 22258951 (http://support.automation.siemens.com/WW/view/de/22258951).

Definition of terms

Term Meaning Abbreviation

in the text Transfer project A transfer project is part of a multiproject and only contains

SIMATIC AS components (CPU stations).

Multiproject A multiproject is the linkage of several projects and libraries to form a comprehensive automation solution. The project data continues to be stored in the projects.

MP

Multiproject Engineering Project configuration in a multiproject. MPE Central multiproject A multiproject stored on the central ES. CMP Central multiproject

engineering

A multiproject created on a central ES PC with its individual S7 projects. These are configured in synchronization on different ES PCs in the network.

CMPE

Distributed multiproject A multiproject in which a project is inserted for further editing and subsequent testing.

DMP

Distributed multiproject engineering

An example for this is when work is contracted to several engineering firms that develop and test the desired function at different locations. They perform the engineering in a distributed engineering environment.

DMPE

Engineering station PC on which the SIMATIC PCS 7 configuration software is used.

ES

Requirements for distributed multiproject engineering with SIMATIC BATCH The following requirements must be fulfilled to perform DMPE with SIMATIC BATCH.

• The projects to be exchanged may only contain AS stations.

• The transfer project can be used in any environment regardless of the hardware configuration. Only the connections need to be adapted.

• The same PCS 7 version, including the corresponding hotfixes and IT

integration software must be installed on the involved PCs or on all PCs in the project.

• All configurations, such as Save as, Delete, Archive, Retrieve etc., must be performed in the SIMATIC Manager.

• The master data library is located in the CMP and may only be modified here.

It is a template for all involved DMPs. The master data library must always be transferred to all involved DMPs.

• You can only use the SFC types in your CMP. You cannot use the BATCH interface blocks EPH, IEPH,EOP, IEOP, EPAR, IEPAR and AF blocks in the

SIMATIC BATCH

A5E00495287-01 5-13

• A unit cannot be distributed over several projects.

• The unit name must be identical in all Batch-relevant projects.

Possible configurations in the central multiproject

All configurations that result in changes or additions to the master data library must be performed in the CMP.

• Shared declarations:

- Units of measure

- Equipment properties in the shared declarations - Enumerations in the shared declarations

• Create and test SFC types (typicals)

Typicals are phase types, for example, heating, cooling, dosing, etc. When these phase types are created, they are thoroughly tested so they can be later duplicated as instances. Any subsequent changes implies an enormous amount of work, because the duplicate type instances may already be in use and all instances may have to be inserted again.

• Create models

• Create and test custom blocks

• Create and test models

• Create and test units

• Test individual units

Possible configurations in the distributed multiproject

• CFC charts

• WinCC process pictures

• Import, create, change and export recipes

What can be tested in the DMP?

• Recipes, batch sequences

• Process pictures

Up to which point in time can DMPE be performed?

The point in time at which the commissioning phase for DMPE with SIMATIC BATCH is completed, depends on your own decision for the most part.

Caution:

You determine the point in time at which any unconfigured data can lead to inconsistencies in the Batch database when you perform the "Update process cell"

function. The procedures described here must stop at the latest at the point when data consistency must be guaranteed in the Batch database.

In general, this is the point at which the acceptance test with parameter fine adjustment is closed or, at the latest, the start of production.

Overview of the configuration tasks

Step 1: Archiving and removing project(s) and the master data library in the CMP.

Step 2: Restoring and inserting project(s) and master data library in the DMP, and adapting the project.

Step 3: Editing, testing and archiving project(s) in the DMP.

Step 4: Restoring and inserting project(s) in the CMP.

Additional information

• Multiproject engineering: In the SIMATIC Manager, click on help and enter

"Multiproject engineering" in the index.

• "Multiproject Engineering" is describe in section 5.3 of the manual Process Control System PCS 7 Engineering System.

5.2.3.7 Step 1: Archiving and removing project(s) and the master data