MasterFormat for Archibus

Where MasterFormat fits

MasterFormat organizes construction work results and specification sections. It is useful when your destination needs a specification reference or a work-result mapping. A company cost code or asset identifier may have a different structure, so preserve that identifier and map the classification alongside it.

The standard you choose should follow the information requirement. Using Archibus does not, by itself, mean your project needs every CSI classification system. Confirm the classification, edition, and destination field before preparing the data.

Working with Archibus

Carry classification references into configured facilities or equipment records. Archibus Data Transfer can import and export table data, subject to the schema and validation rules of the selected view.

An equipment import is not automatically a taxonomy-library import. A table must have the appropriate fields and relationships before it can carry your chosen classification.

Access the data through the platform or an API

The Construction Standard provides licensed access to CSI Dynamic Standards through its web platform. Search for a number or title, review the classification in context, and use the applicable edition when preparing your project references.

For larger workflows, API-style and data access can be made available to companies on request under the applicable plan and terms. Tell us which standard, edition, dataset, and destination you need so the access method and scope can be confirmed. This may support an administrator preparing an import file or a developer building a repeatable data-transfer process.

Platform lookup, bulk data delivery, and API access serve different workflows. Confirm the format and scope for the access route you choose before designing an importer. Your team configures the mapping and transfer into Archibus; these pages describe data use rather than a prebuilt TCS connector or automatic synchronization service.

Prepare the data for Archibus

Export a sample from the target table, map the licensed classification values to the appropriate fields, then prepare a supported CSV or Excel XML import. Confirm the classification destination and parent records with the Archibus administrator. Use comparison and error reports to review the load.

A practical preparation sequence is:

1. Choose the destination. Identify the record type, parameter, reference table, or import template that will hold the classification. Where the software already contains classification data, compare it first instead of creating a second competing list.
2. Map the fields. Include MasterFormat number, title, edition, and the local record or cost-code identifier it references. Preserve code punctuation and leading zeros. Keep the authoritative classification value separate from local record IDs, display labels, and accounting keys.
3. Prepare the hierarchy. Where the destination supports parents and children, load or identify parent records before linking descendants. Where it only accepts flat references, retain the hierarchy in the source mapping rather than inventing unsupported nesting.
4. Load a small sample. Use the destination's documented import process, supported API, or configured entry fields. Check required fields, duplicate handling, code lengths, and whether the operation creates records or updates existing ones.
5. Review the result. Compare the imported numbers and titles with the licensed source and inspect their links to project records. Keep the field mapping and edition with the import so a later update can be reviewed and repeated.

Keep classifications aligned with your project

A code import does not automatically update when a new standards edition is published. Assign an owner for reviewing changes and decide when an existing project should retain its agreed edition. Replacing local identifiers without reviewing their relationships can disrupt estimates, model references, or asset records.

When information moves between specifications, estimates, models, and operations, document how the classifications relate. A work result can contribute to several building systems, and a building system can involve several specification sections. Treat these relationships as mappings to review, rather than assuming that all three standards use the same codes or a one-to-one conversion.

Start with the workflow you already use

Explore MasterFormat in the platform for individual references. For a planned import or recurring data feed, review MasterFormat API and data access and access options. Share the target software, required fields, and expected update process so the data-access route can be matched to the work.

Sources for this workflow

• [CSI: MasterFormat](https://www.csiresources.org/standards/masterformat2026)
• [The Construction Standard: API and data access](https://theconstructionstandard.com/CSI-standards-api)
• [Archibus: Data Transfer overview](https://www.archibus.net/ai/abizfiles/v26.2_help/archibus_help/user_en/Subsystems/webc/Content/fim/managing_wc/data_transfer/import_export_over.htm)

Vendor documentation describes the referenced product or version. Confirm the available fields and transfer tools in your own deployment before preparing a full import.