OmniClass® 2.2 · OIR 26.1

Start with the classification purpose

OmniClass organizes information about the built environment across multiple tables. Before searching for a classification, identify the kind of information you need to describe. A product, a work result, and an asset-related record are different information contexts, even when they are associated with the same physical component on a project.

In CDS, select the standard, edition, and OIR separately. Then inspect the relevant hierarchy and related records. This preserves context when a team shares a reference with software developers, designers, contractors, or facilities staff. A bare number or copied title can lose the table and release information needed to interpret it correctly.

What OIR 26.1 improves

The release notes describe more than 900 corrections across the combined digital environment, including formatting, terminology, metadata, and classification corrections. This is a release-wide total, not an OmniClass-only count. Corrections to identifiers, spacing, punctuation, and terminology can improve search and relationship matching without appearing as a prominent new feature in the interface.

The platform also adds a division-view button across the supported standards and a navigation guide to help users understand Divisions, Entities, and Tables. For OmniClass, use the hierarchy to understand a record's position and table context. The 26.1 navigator guide explains how browsing complements keyword and number searches.

Relationships with MasterFormat and UniFormat

OIR 26.1 represents classification information with relationships between a UniFormat element, associated MasterFormat work results, and OmniClass information. This helps users move from planning context to work-result and lifecycle information without conducting every lookup independently.

A crosswalk should be interpreted as a relationship to review, not automatic proof that two classifications mean exactly the same thing. Check the table, scope, and purpose of each target reference before using it in a BIM property, product record, or handover dataset. Our crosswalk guide explains this review approach and the new General, PPD Track - UniFormat, and OmniModel groupings.

Do not confuse the UniFormat framework with OmniClass tables

The release notes list transportation and utility/service entities in the proposed UniFormat expansion. Those numbered framework headings need to be read within the UniFormat section of the release notes. Their appearance in a release that also includes OmniClass does not mean they are newly issued OmniClass tables.

For that development scope, use the UniFormat 2010 Edition · OIR 26.1 guide. For work-results references, use MasterFormat 2026 Edition · OIR 26.1. Keep the standard name with each classification in shared records so a similar-looking number is not interpreted in the wrong system. For an existing asset or product database, review a small set of representative records and their relationships before changing a wider dataset.

Release date, standards authority, and access

CIN published OIR 26.1 on September 22, 2026 for information delivered through CSI Dynamic Standards. An Operational Information Release updates the digital information environment. CSI continues to govern, develop, and approve the underlying standard editions through its established consensus process. An OIR number should therefore be recorded separately from the standard name and edition when documenting a project reference.

Use the full release notes for the published scope and the September 22 changelog for the platform changes. The announcement from Chris Anderson explains the release's purpose. These public guides provide orientation; verify individual classifications and relationships in the licensed environment before applying them to project documents. Existing customers can log in, and teams evaluating access can review CSI Dynamic Standards pricing.