Archibus Extensions for BUILDERTM SMS
Guidelines for Entering Organizational and Asset Data
Follow these guidelines to ensure that organizational and asset data, entered in Archibus or BUILDER™ SMS, appears properly after transfer via inbound or outbound connectors.
Entering Data in BUILDER SMS for Import
These guidelines and precautions safeguard transfer of valid asset data from BUILDER™ SMS to Archibus. To avoid the possibility of importing inconsistent or faulty data:
- Before you create data in Archibus, use the inbound master connector to import organizational and asset data initially created in BUILDER™ SMS, along with background data located there.
- For BUILDER™ SMS contact data, enter a state abbreviation that also exists in Archibus. If the correct state abbreviation does not exist in Archibus, enter it in Archibus before you import data from BUILDER™ SMS. In Archibus, use the state abbreviation from BUILDER™ SMS as the state code.
- When you enter a city name in BUILDER™ SMS contact data, enter the state abbreviation as well.
- Sections in BUILDER™ SMS map to equipment in Archibus. Archibus creates only one equipment record per section, even if the BUILDER™ SMS section's quantity is greater than one.
- Archibus truncates strings longer than the corresponding field size in Archibus. For example, Archibus may truncate long comments.
Caution: After you import data from BUILDER™ SMS to Archibus, do not alter primary keys in Archibus. To avoid duplication of records when you run inbound connectors multiple times, leave primary keys in Archibus as is. In BUILDER™ SMS, you cannot edit primary keys for organizations and assets; in Archibus, these primary keys are both visible and editable. To ensure referential correspondence between the two platforms, do not modify the values of primary keys in Archibus.
Entering Data in Archibus for Export
These guidelines and precautions safeguard transfer of valid asset data from Archibus to BUILDER™ SMS.
Organizational, site, and building data
Note the following for export of organizational, site, and building data from Archibus to BUILDER™ SMS:
- Always assign a building to Archibus building systems, to avoid errors when you export data to BUILDER™ SMS.
- Before you export organizational, site, and building data to BUILDER™ SMS, check Archibus data to verify that all three levels of data link together hierarchically.
- Archibus organizations without a parent organization are assigned to the highest possible organization in BUILDER™ SMS.
- Archibus sites not linked to an organization are not transferred to BUILDER™ SMS.
- Archibus buildings not assigned to a site are not transferred to BUILDER™ SMS.
- Archibus building systems without a BUILDER™ SMS classification code are not transferred to BUILDER™ SMS.
Note: In the hierarchy of asset inventory categories, you must assign sections and their details to building systems and components. Reference information for asset categories always resides in BUILDER™ SMS.
Equipment system and equipment data
Note the following for export of equipment system and equipment data to BUILDER™ SMS:
- Assign each equipment system in Archibus to a building system. BUILDER™ SMS cannot display unassigned equipment systems, called components in BUILDER™ SMS.
- When Archibus equipment represents a component in BUILDER™ SMS, set the field Builder SMS Level to Component.
- When Archibus equipment represents a section in BUILDER™ SMS, set the field Builder SMS Level to Section.
- When Archibus equipment represents a section detail in BUILDER™ SMS, set the field Builder SMS Level to Section Detail.
- Before you export asset data to BUILDER™ SMS, check Archibus data to verify that assets link together hierarchically, and that BUILDER™ SMS classification codes are assigned as necessary.
- Archibus equipment that may represent components, sections, or section details in BUILDER™ SMS, but are not assigned to corresponding equipment systems in Archibus, are not transferred correctly to BUILDER™ SMS.
- Archibus equipment that represents components or sections in BUILDER™ SMS, but without a valid UNIFORMAT II classification code, are transferred correctly to BUILDER™ SMS.
See also