Archibus Extensions for BUILDERTM SMS
Comparing Archibus and BUILDER™ SMS Tables
For successful data transfers, Archibus Extensions for BUILDER™ SMS must map BUILDER™ SMS asset categories to Archibus asset categories. The table below compares asset hierarchies between BUILDER™ SMS and Archibus. Both platforms use asset hierarchies to organize inventory data.
| Table in BUILDER™ SMS | Table in Archibus | Notes |
|---|---|---|
|
Organization |
Organizational Units ( |
In BUILDER™ SMS and Archibus, organizations are hierarchically organized in an n-tier hierarchy. |
|
Site |
Sites |
In BUILDER™ SMS, a site is a type of organization, yet distinguished from those at the top of the hierarchy. |
|
Building or Facility |
Buildings |
In BUILDER™ SMS, a building is also called a facility. The two categories are equivalent. |
|
System |
Building Systems |
In BUILDER™ SMS, systems equal building systems. Flooring and walls are examples of building systems. |
|
Component |
Equipment Systems - top level |
Components in BUILDER™ SMS are the highest level equipment systems in Archibus. |
| Section | Equipment - parent |
Sections do not stand alone. They are hierarchically linked to parent components, as components are linked to parent systems. Each BUILDER™ SMS section might be:
Section type is based on the parent component's category. For asset inventory mapping purposes, we assume all sections are the equivalent of Archibus equipment. |
| Section Details | Equipment - child | Each BUILDER™ SMS section can have multiple details. Each section detail is equivalent to a child piece of equipment in Archibus. |
See also