Database Allocation

The following example illustrates how databases need to be allocated in a small project with three locations:

In terms of parent and child locations:

• A is the parent of B

• B is the child of A and the parent of C

• C is the child of B

There are five databases:

• A Pipework Catalogue, CATA/PIPE.

• A Steelwork Catalogue, CATA/STEEL.

• A Pipework Design Database, PIPE/PIPE.

• A Steelwork Design Database, STEEL/STEEL.

• A Drawing Database, DRAW/DRAW

Catalogue creation and Pipework design are carried out at Location A, and so the Catalogue databases and the Pipework Design database must be primary at Location A.

Steelwork design is carried out at Location B, and so the Steelwork Design database must be primary at Location B. Users at Location B need read access to the Steelwork Catalogue, so this must exist at Location B as a secondary database.

Drawing production is carried out at Location C. Users at Location C need to have read access to the Design databases, and write access to the Drawing database, and so the Drawing database must be primary at Location C.

Isometric Production is carried out at Location B. The Pipework Design and Catalogue databases will be available at Location B, and the Isodraft database must be primary at Location B. It will not be required at Location C.

The databases need to be allocated, and their primary locations set. The databases which are primary at a location are marked with a +. This is the convention which is used on the forms in the GUI.

Location B needs the Steelwork Catalogue and the Steelwork Design database. Because it is also the link in the communication chain between the Hub and Location C, Location B must also have the Pipework and Drawing databases present, because it is the route by which updates are transferred between the Hub and Location C.