TIMS3 Project Replication

TIMS3 Project Replication is a powerful multi site collaboration tool. Using the TIMS Cleanup utility, businesses can replicate project files between offices, or with other companies. Project replication is used to maintain a local pseudo-synchronized copy of a remote project, including all files and database records.

The purpose of a local copy of a remote project is to promote document collaboration through sharing of document files and specifications. The local copy of project documents is intended for review purposes only and is copied locally only to provide fast access to up-to-date documents.

Project replication will copy all project information, including both database records and files, from one TIMS3 site to another. The replication process is part of the TIMS Cleanup utility which is normally scheduled to run once each evening hence the term pseudo-synchronized.

The TIMS Cleanup utility will clean up files stored on local client workstations as its usual maintenance and security feature. Project replication takes place at the tail end of the TIMS Cleanup process. TIMS Cleanup will take the updated projects, and transfer copies of these folders and files to an offsite TIMS3 server. The offsite TIMS3 server will automatically update its own 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. Remote projects can be replicated to any local project location or name, usually under the same project name locally as 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 at the next scheduled replication.

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.