‘Applications Guide ‘ypes of projects, For example, to identity alternate specification Sections for diferent types of projects, 23.61 16 Reciprocating Refrigerant Compressors could be subdivided by designating institutional project specications withthe addtion ofthe number 11 and commercial project specifications by the number 22. The mutiple versions of the Section \would then be electronically fled under 23 61 16.11 and 23 61 16.22 respectively. When the Sections are used in a Project manual, they would have the same number and tile -23 61 16 Reciprocating Refrigerant Compressors. The Level 4 numbers would only be used forthe identification and interling of the mutiple versions of the same Section It the standard subject is @ Level 4 number and the, the user may create any addtional subdivided Sections at Level § as desired. tis recommended that any actional extensions at Level 5 be preceded by another decimal point or other delimiter, flowing the dscussion above, RELATIONSHIP TO OMNICLASS ‘OmniClass™ is designed to provide a standardized basis for classifying information created and used by the North ‘American architectural, engineering, and construction industry, throughout the full facility life cycte from conception to demolition of reuse, and encompassing all ofthe dtferent types of construction that make up the built environment. ‘OmniGlass's intended to be the means for organizing, sorting, and retrieving information, and standardizing diltal information exchanges. OmniClass' scope is designed to encompass objects at every scale through the entire built ‘environment, from completed structures, vast projects, and mult-structure complexes to individual products and component materials. Omnilass also addresses actions, people, tools, and information that are used or take part inthe design, construction, and maintenance of these structures, OmniClass Table 22 — Work Results is based upon the content provided in MasterFormat. At the same time, the indexes and explanations of MasterFormat draw information from OmniGiass Table 23 - Products and Table 21 - Elements, making it an application of OmniClass. Reference to other OmniClass tables is also made in the Applications Guide, For information on OmniClass, visit omniclass.ora RELATIONSHIP TO UNIFORMAT CSIICSC UniFormat™ is designed to provide a standardized basis for classifying the physical elements ofa facility by thei primary function without regard tothe particular work results that wil be used to aohieve the function. Substructure, shell, interiors, and services are examples of basic functional elements. The functional elements are often referred to as systems or assembles. The shell element can be broken down into superstructure (.. structural frame). exterior vertical enclosures (i, exterior wall assemblies), and exterior horizontal enciosures (ie. roofing assemblies). The services element can be broken down to conveying (i.e. elevator systems), plumbing (i.e. domestic water distribution}, heating, venting, and arr consdtioning (ie. heat generation), fre protection (.. fre sprinkler systems), and electrical (.e.ighting systems). UniFormatis an application of Table 21 — Elements of OmniClass, and much as MasterFormat provides the basis for OmniClass Table 22 - Work Results, UniFormat provides the basis for Table 21 ‘UniFormatis a companion organizational tool to MasterFormat. UniFormatis most commonly used atthe earlier stages of a project before particule work results have been selected. UniFormat provides @ means to organize design criteria, perforniance requirements, cost data, and descriptive requirements for systems and assembles before the particular solutions or work results have been selected. UniFormatis used to organize preliminary project descriptions, preliminary cost estimates, and reference details. MasterFormats used to organize outine specifications, full speatications, detaled cost data, and crawing notations. tis aperopriate to change from UniFormat to MasterFormat as a means to classity the piysical elements ofa project atthe time in the project development when particular work results are being selected. MasterFormat has modeled the organizational structure of 01 80 00 Performance Requirements after UniFormat. Ina Project manual application, a user may use tis location in MasterFormat to provide performance or other type Fequirements forthe functional elements ofa project thal may include elements from multiple les, multiple Divisions, or both Introduction and Applications Guide 2