Rockwell Automation 9307 FactoryTalk EnergyMetrix - Manual (Page 49)

49
C
HAPTER
4
Set up Your System Architecture
We suggest that you set up a system configuration that helps you visualize and understand
the energy use patterns of your plant or enterprise.
A project is organized in a familiar tree-structured fashion. The user constructs a tree made
up of domains and groups in a hierarchy. A typical and popular way to organize a project
tree is shown below.
At the ‘root’ of the tree is a top-level domain that represents a plant named ‘Efficient
Industries Plant 1’. Under the top-level domain are two sub-domains, ‘Accounting’ and
‘Engineering’. These are set up to address two groups of system users, those interested in
energy usage by department or process (Accounting), and those interested in usage by
utility type (Engineering).
Before we move on, let’s define some terms.
 A Group, shown as a folder in the tree, is simply a collection of Devices and Meters
(we’ll define these a little later).
 A Domain is a special group with security assigned. Domains also may contain
Devices, Meters, and other objects, such as Reports, Rate Schedules, and Multi-
purpose Report Scripts.
The main reason you would create a Domain rather than a Group is to control user access
to the meters and other objects in the group.
There is a lot of flexibility in setting up the project structure. For instance, a corporate user
with multiple locations can create a top-level domain for corporate, and sub-domains for
each plant. The security configuration might permit plant users access only to the plant
domains, while corporate users would have access to the corporate domain and all sub-
domains.