TMS on Global

TMS can operate in an AVEVA Global environment. It is possible to set up a TMS-enabled project as a Global project, such that TMS managed tags can be created and updated by a TMS service running at the hub. The new and updated tags are sent back immediately to the requesting location. The updates are propagated to other locations using scheduled global updates (update events). Refer to the AVEVA Global User Guide for help on setting up a Global project.

Once a TMS-enabled project has been made global, the following actions are needed to set up the TMS service and databases:

• Install the Engineering Service (TMS) at the hub.

• Install and configure Shared Services at each location.

• Allocate the TMS primary database to all locations. This must remain primary at the hub.

• Create a separate TMS consumer extract for each location and allocate it as primary at the location.

Creating TMS Consumer Extracts for Locations

Create an extract database from the TMS primary database, assigned to the appropriate team (TMS consumer extracts typically have their own team, TMSCX). Navigate to the new extract database in the explorer and run the command to make the extract a consumer extract:

> LConsumer true

Allocate and add the consumer extracts to the required Engineering Multiple Databases (MDBs) at the locations. The default TMS consumer extract can be used for clients running at the hub but should be deallocated from any other satellites. There should be only one TMS consumer extract at any location.