Development system architecture

This section describes three basic system architectures for multi-user development, each with its own set of advantages and disadvantages. The recommended multi-user environment leverages AVEVA™ Integration Studio, a cloud-based development environment that provides high allows a virtually unlimited number of concurrent users, without negatively impacting performance.

In addition to the recommended architecture, two alternative basic system architectures for multi-user development are described in the following sections. Each has its own set of advantages and disadvantages, including the recommended architecture. The basic system architectures are:

• Shared GR with local IDE nodes (alternative architecture)

• Shared GR and IDE node (alternative architecture)

• Local GR nodes plus shared GR (recommended)

Object wizards: best practices

Regardless of the architecture that you implement, it is recommended that you have a set of hierarchical object wizards to use as the basis for your galaxy, and ensure that best practices for object wizard usage are observed. The most important of these are to develop a three-tier hierarchy of object wizards:

• Top-level object wizards define corporate standards, and serve as templates for derived object wizards.

• Second-level derived object wizards contain refinements that take into account, for example, regional differences or the requirements for different business units.

• Third-level object wizards contain additional refinements, as needed for a particular site or facility.