Configuring Hardware and Communication Connections STEP 7.pdf

Working With Projects in the Multiproject
16.2 Multiproject - Requirements and Recommendations
Different methods of working with the multiproject
Basic requirements
The multiproject lets you configure a flexible system. In the foreground is timesaving,
parallel creation of projects that can be merged by the system.
Basically we can differentiate between two working methods:
• Several members of a user group in a network environment share a
multiproject. The projects of the multiproject are stored in different network
folders.
- In this case, all communication partners are available online for the
configuration of connections, for example.
- Only the execution of cross-project functions on the networks must be
agreed upon between the partners, because read/write access to the
projects is not permitted while these functions are active.
• The project administrator manages the multiproject at the master database,
defines the structure of projects (locally, if required), controls distributed
transactions for external authors, then transfers the incoming projects to the
multiproject, adjusts the cross-project data via the system functions ( file update
synchronization ) and executes necessary cross-project functions.
- In this case, for example, you must declare connection names, because
during the adjustment of projects the S7 connections could easily be
merged due to identical names.
- The user can also combine those two working methods. STEP 7 supports
the distribution of projects across the network as well as the simple
insertion and removal of projects of the multiproject, regardless of the
method used.
Prerequisite for the distribution of projects to different network folders is:
• The projects are stored in folders with read/write attribute. This implies in
particular:
- Read/write access to drives storing the multiproject or projects must have
been granted prior to the creation of the multiproject.
- Release names must be unique within the network. We recommend you
choose a release name that consists of the computer name and the drive
name (e.g. PC52_D).
- Access rights and release names must not be modified for any resources
(folders) participating in the multiproject. The reason is: When a project is
inserted into the multiproject, STEP 7 will generate a reference to the
location of this project. This reference is determined by access rights and
the release name of the corresponding resources.
- A project can only be found under the release name it was assigned when
it was implemented in the multiproject.
Configuring Hardware and Communication Connections with STEP 7
16-4 A5E00706939-01