The features in this article are available only in Enterprise Edition.
Relationships between assets are key to understanding how various elements within a building system interact. Relationships within Virtual Facility help define and visually map the state of assets that operate together for improved troubleshooting and work response when events of one asset affect another.
Summary
When defining the relationship of an asset there are four different types one can have:
- Feeds: defines the assets that receive an output from this asset
- Is Fed By: inverse to “Feeds”, this defines the assets that provide an input to this asset
- Is Part Of: defines the larger system asset that this asset is a part of
- Has Part: inverse to "is part of,” this defines the assets that make up the larger system of assets
Definitions
Feeds
The "feeds" relationship describes how one asset provides essential service or output to another. This is common in systems like HVAC (Heating, Ventilation, and Air Conditioning) or electrical systems. For example, the CHILLED WATER SYSTEM “FEEDS” AIR HANDLING UNITS 1, 2 and 3 because the output of the chilled water system, chilled water, is an essential input for an AHU to provide its output, conditioned air. The "feeds" relationship essentially identifies the direction of resource flow.
Defining a “Feeds” relationship of asset A to asset B, automatically defines the inverse “Is Fed By” relationship for asset B to asset A.
It is important to note that when defining relationships, only 1-degree of freedom is considered, for example Chilled Water System to AHU or AHU to space. Defining more degrees of freedom prevents Virtual Facility from developing the proper hierarchy of relationships and flow of resources from one asset to another. For instance, it would NOT be correct when defining relationships of a chilled water system to include a “space feeds relationship” in addition to the “AHU feeds relationship”. The appropriate location to define this space relationship would be in the AHU because the AHU has a 1-degree of freedom relationship operation with the space; AHU feeds space 1,2,3, and ; AHU-1 Feeds rooms 1,2, and 3.
Is Fed By
The "is fed by" relationship is the inverse of "feeds." It describes how an asset receives input or services from another asset. Using the previous example, the AIR HANDLING UNIT (AHU) “IS FED BY” the CHILLED WATER SYSTEM. Understanding "is fed by" ensures clarity about the origin of resources for a particular system.
Defining a “Is Fed By” relationship of asset A to asset B, automatically defines the inverse “Feeds” relationship for asset B to asset A.
Is Part Of
This relationship describes how an asset fits within a larger system or structure. For example, a CHILLER-1 “IS PART OF” the CHILLED WATER SYSTEM asset. It helps to outline how individual assets are nested within larger system assets, allowing for a clear hierarchy and organizational structure when trying to understand the operational state of the components of a system when the system as a whole is not performing as intended.
Defining a “Is Part of” relationship of equipment asset A to system asset B, automatically defines the inverse “Has Part” relationship for system asset B to equipment asset A.
Has Part
The "has part" relationship is the inverse of "is part of." It describes how an asset contains other components or sub-assets. For example, a CHILLED WATER SYSTEM “HAS PARTS” of CHILLERS, COOLING TOWERS, and PUMPS. This type of relationship is used to break down large systems into smaller, more manageable assets, illustrating how the operation state of individual assets contribute to the operational state of the system as a whole.
Defining a “Has Part” relationship of system asset B to equipment asset A, automatically defines the inverse “Is Part Of” relationship for equipment asset A to system asset B.