Archibus SaaS / Assets / Background Data - Assets
Assets / Assets / Background Data - Assets
Assets / Enterprise Assets / Background Data - Assets
Assets / Telecom Assets / Background Data - Facilities

Defining Equipment Systems

To most effectively track your equipment assets, you can use Archibus to group your assets hierarchically, so that you have an easy way to locate assets, and to visualize the relationships between equipment items. The application enables you to map equipment items to systems (the top level) and to assemblies and componentsso that dependencies are clear, and to assign the various teams that support the asset, and the space that depends on the asset to the equipment system.

Note: You can also define equipment systems using the Equipment Systems Console.

Defining stakeholder groups

Each stakeholder group (facilities management, IT, and department managers) has a unique perspective on how to organize the asset information. Since stakeholders might have different definitions for systems, assemblies or components for a given set of equipment, there can be multiple mapping records for the same equipment - one for each assignment in the system assignment tree.

For these different perspectives, you can define different system assignments that provide the information needed for that particular stakeholder. You then associate the equipment system record with the Stakeholder Type. Users can filter the Equipment Systems Console by Stakeholder Type, so they see the assignments relevant to their work. You can assign a single stakeholder type to an equipment system record, but you can also assign a combination of stakeholders types, such as facilities management and IT, so that both stakeholder views can see those assignments.

When working from the Equipment Systems Console, users can then select this stakeholder group from the Filter Console to see the hierarchy relevant to their work.

Defining functional and mission criticality

There are two types of criticality: functional and mission. Domain experts assign the functional (mechanical) criticality based on the type of asset (for example, HVAC, Security, or Lab Equipment). Space planners, architects, or the owner of the asset assign the mission (process) criticality.

Establishing these criticalities is important to your assessment of the effects of taking equipment off line, such as when moving or repairing it. For example, with mission critical assets that support mission critical assemblies and / or mission critical systems, it is often best to minimize down time for all the connecting assets and systems by performing planned activities at the same time. For example, you might consider coordinating on demand or preventive maintenance work, assessments, asset refurbishment or replacement, or moves for this equipment.

About defining equipment systems

When you define an equipment system record, you are defining the relationship between two equipment records: a master equipment and a dependent equipment. The one exception is when you define the highest level of the tree, that is, when you define the record for the equipment system itself; in this case, the master and dependent have the same value. There are two ways to set up the relationship between assets:

• Using the Define Equipment Systems task to define records in the Equipment Systems (eq-systems) table. These records define the relationship between two assets. You can create multiple records to link different assemblies to the same equipment system, or to link different components to assemblies. This method is described in this topic.
• Working from the Equipment Systems Console, you can also define the dependencies between equipment assets by clicking and dragging to make the assignment. You can click and drag either unassigned assets or assemblies or components that you have already defined and want to assign to a different position in the system assignment tree. This clicking and dragging action is another way to create an Equipment Systems record.

There is one record in the Equipment System mapping table for each entry in the System Assignment tree. The same equipment record can appear multiple times in the system tree. For example, a piece of equipment may be shared between two or more systems.

Procedure: Define equipment systems using the Define Equipment Systems task

To define equipment systems:

1. Select the Define Equipment Systems task from a path listed at the top of this topic.
   • The Equipment Systems list shows the equipment systems you have already defined.
2. To add a new equipment system, click the plus sign .

   The Equipment System form appears for you to enter the new equipment system record.

3. Enter the following required information:

   Equipment Code Master. Select the equipment on which other equipment relies.

   Equipment Code Dependent. Select the equipment that is dependent on the Equipment Code Master in order to operate. An Equipment Code Master can have several dependent equipment assets that it is dependent on to function properly or efficiently.

   Note: To define the top level for a system, put the same Equipment Code in the Equipment Code Master and Equipment Code Dependent fields, and then select the System Level as System.

4. Enter the following additional information:

   Tree Label / System Name. The Tree Label is a virtual field, and is the default label the database assigns for the asset in the tree. Review this label to determine if you want to overwrite it by entering a different value in the System Name field. The System Name you enter replaces the Tree Label set by the system.

   Criticality Mission. Select the description of how important the asset is to the support of mission processes.

   Criticality Function. Select how important the mechanical dependency between the two assets is. For example, between the system and its assembly, or between an assembly and its components.

   For example: An HVAC system is comprised of an air handler unit (AHU), chiller, boiler, duct work, valves, and diffusers. The AHU assembly has a fan assembly which is comprised of the fan, the fan motor, a fan belt, and a filter. The fan motor is functionally critical to the AHU. The diffusers are not functionally critical to the HVAC system or the AHU assembly.

   System Level. Select whether this record is for a system (the equipment system itself to which you will assign assemblies and perhaps components.), a component or an assembly. The level applies to the dependent record.

   Stakeholder Type. Select from the list of stakeholders whether this system is shown for All (shown for all stakeholders) IT, DP (Department Manager), or FM (Facility Managers), or some combination of these groups shown in the list.

   Building System ID. Select the building system, such as HVAC, lab, or emergency lighting, that this equipment system is associated with. You define building systems using the Define Building Systems task.

5. Click Save.

   To add more levels to the hierarchy, you can create another record that links to this record, or you can click and drag to create the assignment when working from the Equipment Systems Console. See Making System Assignments from the Equipment Systems Console.