Hole Management in a Global Project

If the project has been configured to use AVEVA Global then you must consider the scenario described in this section. Refer to Global Mode of Operation for further information.

If the originator of a hole and the reviewer of that hole are in different locations (a hub and satellite), then association data must be held in an extract database and extracted and issued depending upon the hole management task.

The association world that stores the hole associations must reside in a database that has an extract database allocated to each location because both the originator and the reviewer must be able to write to that data.

Note:
The virtual hole (FIXING) does not need to reside in an extract database. The storage areas for virtual holes need only reside in a database that the originator can write to.