Common AECOO Data Stack

Common AECOO Data Stack

Common AECOO Data Stack

1. Purpose and Scope

This  Four BT (4BT)  methodology defines how to maintain a robust, rule-based environment across MasterFormat, OmniClass, and UniFormat for cost, BIM, IFC, and FM workflows. Static, one-to-one spreadsheets cannot keep pace with evolving standards, project variation, and the full MasterFormat catalog, and they often create misleading “equivalences” that do not hold under audit or lifecycle use.​

Instead of forcing single-target mappings, the 4BT applies a rule-based model that can express multiple valid classification relationships per cost line. This model scales to all 8,000+ MasterFormat titles, supports discipline-specific nuance, and preserves the distinction between systems, elements, work results, and products across the asset lifecycle.​

2. Classification Governance

4BT adopts a governance model that assigns a clear, canonical role to each classification standard. This prevents crosswalk misuse, avoids “overloading” any one standard, and keeps cost, BIM, and FM aligned over time.​

  • UniFormat™ – Systems and assemblies (WHAT exists). UniFormat organizes information around building systems and assemblies rather than trades, making it well suited to early design, asset breakdown structures, and lifecycle-oriented system thinking.​

  • OmniClass™ Table 21 – Element context (WHERE it belongs). Table 21 classifies elements by their functional role in the facility, providing a bridge between system-level thinking (UniFormat) and detailed work results and products.​

  • OmniClass™ Table 22 – Work results (HOW it is built). Table 22 focuses on work results delivered in the construction phase and closely aligns with the structure and intent of MasterFormat sections.​

  • MasterFormat® – Contractual and cost scope. MasterFormat organizes specifications and cost items by work results, materials, and trades, and is used to structure estimates, bids, and contracts.​

  • OmniClass™ Table 23 – Products and equipment (WITH WHAT). Table 23 provides a stable, lifecycle-oriented way to identify maintainable products and equipment, supporting FM, reliability analysis, and asset management.​

Within this governance model, MasterFormat is not treated as a system model and is not used to represent asset breakdown structures or spatial organization. UniFormat and OmniClass Tables 21 and 23 provide those roles, while Table 22 and MasterFormat focus on work results and contractual scope.​

3. Applicability Model

4BT uses an applicability model rather than a mandatory 1:1 mapping. Each MasterFormat section can have multiple valid classification relationships, each tagged according to its role in context.​

  • PRIMARY – The most common or canonical classification relationship for a given cost line or work package in typical building projects.​

  • SECONDARY – An additional relationship that is technically valid but less frequently used, discipline-specific, or context-specific.​

  • CONTEXT_DEPENDENT – A relationship that may or may not apply depending on project delivery method, system boundaries, or owner requirements.​

Applicability explicitly does not imply equivalence. A PRIMARY link indicates that a classification is usually appropriate, not that it is the only correct interpretation or that codes are semantically interchangeable. This distinction is critical for licensing, audit defensibility, and lifecycle data quality.​

4. Rule Hierarchy (The Engine)

The crosswalk is implemented as a layered rule engine rather than a flat spreadsheet. Each layer expresses a specific relationship that can be maintained, audited, and extended independently.​

  1. MasterFormat Division → OmniClass Table 22

    • Division-level rules define the allowable OmniClass Table 22 work result ranges for sections within that division.​

    • This captures the natural alignment between MasterFormat and Table 22 while allowing for exceptions and multi-division work packages.​

  2. OmniClass Table 22 → OmniClass Table 21

    • Rules at this layer connect work results to their corresponding elements, clarifying where a given work result “lives” in the facility context.​

    • This supports element-based reporting, scope definition, and BIM views that focus on building functions rather than trades.​

  3. OmniClass Table 21 → UniFormat Level 4

    • This layer links elements to system and assembly breakdown structures at UniFormat Level 4.​

    • It enables aggregation of costs and quantities by system, supports asset hierarchies, and provides a bridge from design-oriented elements to owner-facing system views.​

  4. Optional OmniClass Table 23 Linkage

    • Where appropriate, rules connect elements and systems to specific products and equipment in Table 23.​

    • This optional linkage is particularly valuable for COBie, CMMS, FCA/Capital Planning and Management, and reliability/maintenance planning, where product-level identifiers are required.​

Because rules are layered, 4BT can update or expand a single layer (for example, new Table 23 products or revised UniFormat codes) without rewriting the entire crosswalk. This design is what enables dynamic generation for all 8,000+ MasterFormat sections rather than fragile, one-off mappings.​

5. Automation and Scalability

The rule tables are designed to be consumed programmatically by scripting and BI tools such as Python and Power Query. When licensed 4BT cost data is supplied, the automation engine applies the rules to each cost line to generate classifications for the desired standards.​

  • Rules are stored in structured tables (division_to_oc22_rules, oc22_to_oc21_rules, oc21_to_uniformat_l4_rules), not hard-coded in macros or hidden logic.​

  • Scripts and queries read these tables, apply the PRIMARY / SECONDARY / CONTEXT_DEPENDENT logic, and write back enriched cost lines with attached UniFormat, OmniClass, and, where applicable, product-level codes.​

This approach allows the same methodology to be applied across multiple cost databases, project types, and client portfolios without duplicating crosswalk spreadsheets. It also supports continuous improvement: rule changes can be versioned, tested, and rolled out without disrupting existing client data.​

6. BIM / IFC / COBie Alignment

The methodology is explicitly designed to support BIM, IFC, and COBie handover requirements. By keeping systems, elements, work results, and products in their correct classification “homes,” the crosswalk ensures that downstream models and datasets remain coherent.​

  • Systems and assemblies (UniFormat) and elements (OmniClass Table 21) align with typical IFC object hierarchies and model views.​

  • Work results (OmniClass Table 22 and MasterFormat) align with specifications, trade packages, and construction-phase documentation.​

  • Products and equipment (OmniClass Table 23) align with COBie component records and FM/CMMS asset registers.​

This layered alignment supports consistent identifiers from early design through construction and into operations, reducing rework and manual recoding at handover. It also enables owners to define classification expectations once and reuse them across projects, regardless of the specific tools or authoring platforms in play.​

7. Disclaimer

This methodology defines an applicability-based crosswalk, not a set of semantic equivalences between classification codes. A PRIMARY, SECONDARY, or CONTEXT_DEPENDENT relationship indicates that a pairing is appropriate for use under defined conditions, not that the underlying standards share identical meanings, scopes, or licensing terms.​

Final assignment of classifications for any given project may vary based on scope, delivery method, owner requirements, or jurisdictional constraints, and should always be reviewed by qualified professionals. Use of this methodology does not alter the official definitions, ownership, or licensing requirements of any referenced standard.

​

Note:  All trademarks, logos, and brand names are the property of their respective owners. Their use does not imply endorsement, affiliation, or any relationship with the mark’s owner.

About Four BT, LLC (4BT)  www.4bt.us

We help to create environments where the best people come to do their best work. We all succeed together.

Join us as we pave the way toward a new future for public and private sector efficient project delivery.

4BT exclusively provides verifiable, objective, current, local market construction cost data organized using expanded CSI Masterformat and supporting technology.

-Estimate project costs comprehensively

-Ensure budgets reflect the actual current local market labor, material, and equipment costs for successful project delivery.

-Create detailed and realistic project timelines

-Identify key milestones, task dependencies, and critical paths.

-Minimize risks associated with delays and budget overruns

-Provide a clear project roadmap and cost control mechanisms.

-Enhance resource allocation and utilization

-Align resources and scheduling with budget constraints.