Introduction

Project replication will copy all project information from one TIMS3 site to another (database records and files). The replication process is part of the TIMS3 Cleanup utility that is normally scheduled to run once each evening (hence the term pseudo-synchronized). Project replication takes place at the tail end of the TIMS3 Cleanup process. The replication procedure can be thought of as TIMS3 Cleanup PASS 3 and PASS 4, naturally occurring after PASS 1 and 2. TIMS3 Cleanup PASS 1 is when all client workstations update the TIMS3 file server and PASS 2 is when the server updates all client workstations. In PASS 3, the local TIMS3 server and the TIMS3 database is updated with the data from an offsite TIMS3 server. In PASS 4, the local TIMS3 server will update its local client workstations with any of the files that have been copied out permanently from a replicated project.

Replicated project directories can be setup as root level projects or sub-projects of an overall project. If you choose to replicate to a root level project be sure to name the project appropriately so that it sorts close to its local sister project. Remote projects can be replicated to any local project location or name, but for consistency it is recommended that you use the same project name locally as the name used on the remote site. Remote projects can also be replicated to a sub-project of the local sister project so that the replicated project will remain associated to local project. See below for a pictorial view.

Any user can view the files downloaded from the remote site by simply viewing the replica project in Project Navigator. The file list that appears will show the last modification date on each document within the replica project. As the original file gets updated on its home TIMS3 server the replica will get updated the following evening. When and update occurs the last modification date of the document record will be updated to reflect the file change.

The AGC-TORONTO and AGC-DUBAI projects are each replicated at their opposite remote site (i.e. AGC-TORONTO is replicated at the AGC UAE TIMS3 site, and AGC-DUBAI is replicated at the GIFFELS TORONTO TIMS site). Each site has a copy of the opposite's site data for the AGC project.