Asset Tree Hierarchy Best Practices

It is generally recommended to group assets with similar Disaster Recovery scheduling needs into the same containers. Doing so will allow schedule creation at the container level, which will propagate any container level changes (e.g., asset removal, asset insertion) to the already defined schedule automatically.

In some cases, it is desirable to group the assets and their respective configuration files in different logical areas of the asset tree. For instance, at the root of the asset tree there would exist a container for Files, and a separate container for Controllers. The former would hold all ACD files and the latter would hold all ControlLogix controller assets. This configuration can ease security settings, where access to the Files container is more open than access to the Controllers folder, which should not need to be modified by an average user.