Consider a scenario where a user assigned to Site X creates a Global record, Route X.
The user then adds a new ML to Route X, but does not link the ML to an asset. The new ML inherits the site reference from the user, which is Site X.
Site filtering in Rounds is achieved by specifying a value in the Site Reference Key for a record. Users must have privileges for the relevant site to access records for the specified site. Users can be assigned to one or many sites. They will be able to view global data, and the data for each of the sites to which they are assigned.
Site filtering behavior is applied to all areas where data is handled in Rounds including data loaders, asset hierarchy, global search, and queries throughout Rounds Designer and Rounds Data Collection modules.
IMPORTANT: To modify a Route containing data for multiple sites, the Rounds Designer user must have access to all the included sites, since changing the order of checkpoints may update the sequence value stored on any other checkpoint on the Route.
In Rounds, site filtering affects the following records:
If a Measurement Location or Lubrication Requirement record is linked to an asset, the record will inherit the site from the Equipment and Functional Location to which it is linked. If a Measurement Location or Lubrication Requirement is not linked to an asset, the record will inherit the site from its parent record (i.e. Route or Condition). This takes priority over inheritance of the user's default site, except in the case where the parent record is a Global record.
Template Group records are enabled for site filtering. When a Template Group record has a site specified, you can only add ML Templates that belong to the same site, or are global records. For a global Template Group record, you can add ML Templates from any of the sites.
Note: When a global Template Group is applied to an asset, any ML Templates within the Template Group that are assigned to a specific site that is different to the site of the Equipment or Functional Location will not be applied.
Route records are enabled for site filtering.
If no site is specified for a Route, you can add a Measurement Location or Lubrication Requirement records for any site to the Route.
IMPORTANT: Although you can assign a Route to any user, the Route will only be accessible in Rounds Data Collection to users who have access to the Route's site.
Lubricant, Lubrication Component, Lubrication Method and Lubricant Manufacturer records are enabled for site filtering.
If a Lubricant is assigned to a specific site, the records to which it can be linked are limited as follows:
Lubricant Manufacturer records that are assigned to the same site or have no site (i.e., global records).
Lubrication Method records that are assigned to the same site.
Lubricant Requirement or Lubricant Requirement Template records that are assigned to the same site.
If a Lubrication Component is assigned to a specific site, it can only be used in Lubricant Requirement or Lubricant Requirement Template records that are assigned to the same site.
If you want to use site filtering to limit the available Lubricant records to only locally approved lubricants, note that you may need to create duplicate records for the same lubricant if you want it to be available for more than one site (this is because a given record can belong to only one site).
We recommend, in general, that you create Lubricant Manufacturer, Lubrication Method, and Lubrication Component records with no site (i.e., as global records) rather than duplicating them across sites.
Consider a scenario where a user assigned to Site X creates a Global record, Route X.
The user then adds a new ML to Route X, but does not link the ML to an asset. The new ML inherits the site reference from the user, which is Site X.
Consider an example where a Route X is not assigned to any site. Route X is a global record, and contains the following records:
Scenario 1: User assigned to only one site.
When a user who is assigned to only Site X views Route X in Rounds Designer or Rounds Data Collection, he or she will see the following records:
The records for Site Y or Site Z will not appear for a user assigned to Site X. The user sees data for the assigned Site X and global data.
When a user who is assigned to only Site Y views Route X in Rounds Designer or Rounds Data Collection, he or she will see the following records:
The records for Site X or Site Z will not appear for a user assigned to Site Y. The user sees data for the assigned Site Y and global data.
When a user who is assigned to only Site Z views Route X in Rounds Designer or Rounds Data Collection, he or she will see the following records:
The records for Site X or Site Y will not appear for a user assigned to Site Z. The user sees data for the assigned Site Z and global data.
Scenario 2: User assigned to two sites.
When a user who is assigned to Site X and Site Y views Route X in Rounds Designer or Rounds Data Collection, he or she will see the following records:
The record for Site Z will not appear for a user assigned to Site X and Site Y. The user sees data for both the assigned sites and global data.
When a user who is assigned to Site X and Site Z views Route X in Rounds Designer or Rounds Data Collection, he or she will see the following records:
The record for Site Y will not appear for a user assigned to Site X and Site Z. The user sees data for both the assigned sites and global data.
When a user who is assigned to Site Y and Site Z views Route X in Rounds Designer or Rounds Data Collection, he or she will see the following records:
The record for Site X will not appear for a user assigned to Site Y and Site Z. The user sees data for both the assigned sites and global data.
Scenario 3: Super User
If a Super User views Route X, he or she will see the following records:
Copyright © 2018 General Electric Company. All rights reserved.